Is it possible to trigger a contract with a not prunable public trigger message?












7















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?










share|improve this question

























  • Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message?

    – Owen Delahoy
    Jan 23 at 11:37






  • 2





    This question is related to the Ardor blockchain and its lightweight contract system.

    – atzen
    Jan 23 at 11:44






  • 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.

    – Anonymous
    Jan 23 at 11:54











  • 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 at 12:10











  • 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 at 16:21
















7















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?










share|improve this question

























  • Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message?

    – Owen Delahoy
    Jan 23 at 11:37






  • 2





    This question is related to the Ardor blockchain and its lightweight contract system.

    – atzen
    Jan 23 at 11:44






  • 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.

    – Anonymous
    Jan 23 at 11:54











  • 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 at 12:10











  • 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 at 16:21














7












7








7


0






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?










share|improve this question
















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?







ardor






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 23 at 11:26







atzen

















asked Jan 23 at 11:16









atzenatzen

1155




1155













  • Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message?

    – Owen Delahoy
    Jan 23 at 11:37






  • 2





    This question is related to the Ardor blockchain and its lightweight contract system.

    – atzen
    Jan 23 at 11:44






  • 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.

    – Anonymous
    Jan 23 at 11:54











  • 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 at 12:10











  • 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 at 16:21



















  • Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message?

    – Owen Delahoy
    Jan 23 at 11:37






  • 2





    This question is related to the Ardor blockchain and its lightweight contract system.

    – atzen
    Jan 23 at 11:44






  • 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.

    – Anonymous
    Jan 23 at 11:54











  • 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 at 12:10











  • 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 at 16:21

















Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message?

– Owen Delahoy
Jan 23 at 11:37





Which blockchain? What kind of contract? An ethereum contract? A bitcoin UTXO? What do you mean by trigger message?

– Owen Delahoy
Jan 23 at 11:37




2




2





This question is related to the Ardor blockchain and its lightweight contract system.

– atzen
Jan 23 at 11:44





This question is related to the Ardor blockchain and its lightweight contract system.

– atzen
Jan 23 at 11:44




2




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.

– Anonymous
Jan 23 at 11:54





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 at 11:54













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 at 12:10





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 at 12:10













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 at 16:21





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 at 16:21










1 Answer
1






active

oldest

votes


















6














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.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "308"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f83934%2fis-it-possible-to-trigger-a-contract-with-a-not-prunable-public-trigger-message%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    6














    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.






    share|improve this answer




























      6














      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.






      share|improve this answer


























        6












        6








        6







        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.






        share|improve this 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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 23 at 15:26









        lyaffelyaffe

        1,422411




        1,422411






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Bitcoin Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f83934%2fis-it-possible-to-trigger-a-contract-with-a-not-prunable-public-trigger-message%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Human spaceflight

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

            張江高科駅