In the current state pruning is not implemented. Therefore an attached public trigger message should stay in the blockchain until pruning is enabled. When this is the case, will it be possible to make the trigger message unprunable? This could be useful for contract params validation. For example:

If I trigger a contract with the following attached message: {"contract":"ExampleContract","params":{"veryImportantParameter":"42"}}

I would like to make this message public (so everybody can validate that I've triggered the contract ExampleContract with the parameter veryImportantParameter and it's value 42) and not prunable (so that everybody can validate the message at any time in the future).

Is this going to be possible?

  • Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message? – Owen Delahoy Jan 23 '19 at 11:37
  • 3
    This question is related to the Ardor blockchain and its lightweight contract system. – atzen Jan 23 '19 at 11:44
  • 3
    I'm voting to close this question as off-topic because it is astroturfing. Many similar questions end up with implausibly detailed and fluffy responses from new users. It is not remotely related to Bitcoin. – Anonymous Jan 23 '19 at 11:54
  • 1
    This is a real question and I'm really interested in the answer. If I did something wrong, please tell me. I'll edit the question. All informations are just there to specify the question. I had really no intention to astroturf – atzen Jan 23 '19 at 12:10
  • 1
    There's multiple tags in this stackexchange site based on alternative cryptocurrencies and blockchain technology at large. Why is it an issue that this question is not related to Bitcoin itself? – Van B Jan 23 '19 at 16:21

Ardor has two levels of pruning. Pruning of messages (like the contract trigger message), data cloud items and shuffling artifacts are already implemented on each child chain. Child chain transaction pruning is scheduled for release later this year.

Only prunable trigger message are supported at the moment to reduce blockchain bloat.

Send your trigger message in plain text and setup an archival node to save it locally even after it is pruned. This will provide you unreputable proof that this message existed at the time when the contract was triggered and other nodes will be load this message automatically from your archival node at a later time.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.