<p>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. </p>

<p>Only prunable trigger message are supported at the moment to reduce blockchain bloat.</p>

<p>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.</p>

CC BY-SA 4.0
2019-01-23T15:26:44.297Z
2019-01-23T15:26:44.297Z
lyaffe
<p>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:</p>

<p>If I trigger a contract with the following attached message: <code>{"contract":"ExampleContract","params":{"veryImportantParameter":"42"}}</code></p>

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

<p>Is this going to be possible?</p>

CC BY-SA 4.0
2019-01-23T11:37:28.617Z
Which blockchain?

What kind of contract? An ethereum contract? A bitcoin UTXO?

What do you mean by trigger message?
Owen Delahoy
CC BY-SA 4.0
2019-01-23T11:44:44.840Z
This question is related to the [Ardor](https://ardorplatform.org) blockchain and its lightweight contract system.
atzen
CC BY-SA 4.0
2019-01-23T11:54:09.787Z
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.
Claris
CC BY-SA 4.0
2019-01-23T12:10:25.740Z
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
CC BY-SA 4.0
2019-01-23T16:21:11.753Z
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
<ardor>
Is it possible to trigger a contract with a not prunable public trigger message?
atzen
# Is it possible to trigger a contract with a not prunable public trigger message?

(Asked by: username_0 on 2019-01-23)

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?

**Tags:** ardor

> **Comments:**
> **username_1**: Which blockchain?  What kind of contract? An ethereum contract? A bitcoin UTXO?  What do you mean by trigger message?  
> **username_0**: This question is related to the [Ardor](https://ardorplatform.org) blockchain and its lightweight contract system.  
> **username_2**: 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.  
> **username_0**: 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  
> **username_3**: 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?  

---

## 1 answers

### Answer by username_4 on 2019-01-23. Score: 7 | Accepted answer

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.


---

