Error while send transaction: Data push larger than necessary












1















Looks like transaction decodes fine. But when I use sendrawtransaction I got



Data push larger than necessary



What's wrong with this tx?



bitcoin-cli -testnet decoderawtransaction 020000000149d4a5f520ded6fa94f79cd268f0334baeec9a7732c9d946d1cdee58d81e7aad00000000020101ffffffff01904c96000000000017a914f45d94733d430261962932e0c847075195916a048700000000
{
"txid": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
"hash": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
"version": 2,
"size": 85,
"vsize": 85,
"weight": 340,
"locktime": 0,
"vin": [
{
"txid": "ad7a1ed858eecdd146d9c932779aecae4b33f068d29cf794fad6de20f5a5d449",
"vout": 0,
"scriptSig": {
"asm": "1",
"hex": "0101"
},
"sequence": 4294967295
}
],
"vout": [
{
"value": 0.09850000,
"n": 0,
"scriptPubKey": {
"asm": "OP_HASH160 f45d94733d430261962932e0c847075195916a04 OP_EQUAL",
"hex": "a914f45d94733d430261962932e0c847075195916a0487",
"reqSigs": 1,
"type": "scripthash",
"addresses": [
"2NFXJy8mvz7ZiT4VVN29xPGC38hTygd3AyJ"
]
}
}
]
}









share|improve this question



























    1















    Looks like transaction decodes fine. But when I use sendrawtransaction I got



    Data push larger than necessary



    What's wrong with this tx?



    bitcoin-cli -testnet decoderawtransaction 020000000149d4a5f520ded6fa94f79cd268f0334baeec9a7732c9d946d1cdee58d81e7aad00000000020101ffffffff01904c96000000000017a914f45d94733d430261962932e0c847075195916a048700000000
    {
    "txid": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
    "hash": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
    "version": 2,
    "size": 85,
    "vsize": 85,
    "weight": 340,
    "locktime": 0,
    "vin": [
    {
    "txid": "ad7a1ed858eecdd146d9c932779aecae4b33f068d29cf794fad6de20f5a5d449",
    "vout": 0,
    "scriptSig": {
    "asm": "1",
    "hex": "0101"
    },
    "sequence": 4294967295
    }
    ],
    "vout": [
    {
    "value": 0.09850000,
    "n": 0,
    "scriptPubKey": {
    "asm": "OP_HASH160 f45d94733d430261962932e0c847075195916a04 OP_EQUAL",
    "hex": "a914f45d94733d430261962932e0c847075195916a0487",
    "reqSigs": 1,
    "type": "scripthash",
    "addresses": [
    "2NFXJy8mvz7ZiT4VVN29xPGC38hTygd3AyJ"
    ]
    }
    }
    ]
    }









    share|improve this question

























      1












      1








      1








      Looks like transaction decodes fine. But when I use sendrawtransaction I got



      Data push larger than necessary



      What's wrong with this tx?



      bitcoin-cli -testnet decoderawtransaction 020000000149d4a5f520ded6fa94f79cd268f0334baeec9a7732c9d946d1cdee58d81e7aad00000000020101ffffffff01904c96000000000017a914f45d94733d430261962932e0c847075195916a048700000000
      {
      "txid": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
      "hash": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
      "version": 2,
      "size": 85,
      "vsize": 85,
      "weight": 340,
      "locktime": 0,
      "vin": [
      {
      "txid": "ad7a1ed858eecdd146d9c932779aecae4b33f068d29cf794fad6de20f5a5d449",
      "vout": 0,
      "scriptSig": {
      "asm": "1",
      "hex": "0101"
      },
      "sequence": 4294967295
      }
      ],
      "vout": [
      {
      "value": 0.09850000,
      "n": 0,
      "scriptPubKey": {
      "asm": "OP_HASH160 f45d94733d430261962932e0c847075195916a04 OP_EQUAL",
      "hex": "a914f45d94733d430261962932e0c847075195916a0487",
      "reqSigs": 1,
      "type": "scripthash",
      "addresses": [
      "2NFXJy8mvz7ZiT4VVN29xPGC38hTygd3AyJ"
      ]
      }
      }
      ]
      }









      share|improve this question














      Looks like transaction decodes fine. But when I use sendrawtransaction I got



      Data push larger than necessary



      What's wrong with this tx?



      bitcoin-cli -testnet decoderawtransaction 020000000149d4a5f520ded6fa94f79cd268f0334baeec9a7732c9d946d1cdee58d81e7aad00000000020101ffffffff01904c96000000000017a914f45d94733d430261962932e0c847075195916a048700000000
      {
      "txid": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
      "hash": "1bbf569b281f2cd9d948e4273120a9bc3bb2c21e31bc9786682c0a22d8feb76c",
      "version": 2,
      "size": 85,
      "vsize": 85,
      "weight": 340,
      "locktime": 0,
      "vin": [
      {
      "txid": "ad7a1ed858eecdd146d9c932779aecae4b33f068d29cf794fad6de20f5a5d449",
      "vout": 0,
      "scriptSig": {
      "asm": "1",
      "hex": "0101"
      },
      "sequence": 4294967295
      }
      ],
      "vout": [
      {
      "value": 0.09850000,
      "n": 0,
      "scriptPubKey": {
      "asm": "OP_HASH160 f45d94733d430261962932e0c847075195916a04 OP_EQUAL",
      "hex": "a914f45d94733d430261962932e0c847075195916a0487",
      "reqSigs": 1,
      "type": "scripthash",
      "addresses": [
      "2NFXJy8mvz7ZiT4VVN29xPGC38hTygd3AyJ"
      ]
      }
      }
      ]
      }






      bitcoind raw-transaction






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 16 '18 at 1:31









      AndrewAndrew

      816




      816






















          2 Answers
          2






          active

          oldest

          votes


















          2














          Your scriptSig uses a data push to push 0x01 onto the stack. It could use OP_1 instead.






          share|improve this answer
























          • Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

            – Andrew
            Nov 16 '18 at 2:09



















          2














          Your transaction is failing validation with SCRIPT_VERIFY_MINIMALDATA, which is described in BIP 62 rule 3 protections against malleability. CheckMinimalPush() requires a push of 0x01 to be done using OP_1.



          This standardness rule avoids the case where someone takes a transaction from the network and a push with a longer encoding of the same push and as a result creates a malleated form of the transaction.






          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%2f81066%2ferror-while-send-transaction-data-push-larger-than-necessary%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Your scriptSig uses a data push to push 0x01 onto the stack. It could use OP_1 instead.






            share|improve this answer
























            • Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

              – Andrew
              Nov 16 '18 at 2:09
















            2














            Your scriptSig uses a data push to push 0x01 onto the stack. It could use OP_1 instead.






            share|improve this answer
























            • Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

              – Andrew
              Nov 16 '18 at 2:09














            2












            2








            2







            Your scriptSig uses a data push to push 0x01 onto the stack. It could use OP_1 instead.






            share|improve this answer













            Your scriptSig uses a data push to push 0x01 onto the stack. It could use OP_1 instead.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 16 '18 at 1:34









            Pieter WuillePieter Wuille

            47.9k3100162




            47.9k3100162













            • Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

              – Andrew
              Nov 16 '18 at 2:09



















            • Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

              – Andrew
              Nov 16 '18 at 2:09

















            Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

            – Andrew
            Nov 16 '18 at 2:09





            Thank you! But now I got "Script evaluated without error but finished with a false/empty top stack element)" Is this something wrong with my redeem script or scriptpubkey ?

            – Andrew
            Nov 16 '18 at 2:09











            2














            Your transaction is failing validation with SCRIPT_VERIFY_MINIMALDATA, which is described in BIP 62 rule 3 protections against malleability. CheckMinimalPush() requires a push of 0x01 to be done using OP_1.



            This standardness rule avoids the case where someone takes a transaction from the network and a push with a longer encoding of the same push and as a result creates a malleated form of the transaction.






            share|improve this answer




























              2














              Your transaction is failing validation with SCRIPT_VERIFY_MINIMALDATA, which is described in BIP 62 rule 3 protections against malleability. CheckMinimalPush() requires a push of 0x01 to be done using OP_1.



              This standardness rule avoids the case where someone takes a transaction from the network and a push with a longer encoding of the same push and as a result creates a malleated form of the transaction.






              share|improve this answer


























                2












                2








                2







                Your transaction is failing validation with SCRIPT_VERIFY_MINIMALDATA, which is described in BIP 62 rule 3 protections against malleability. CheckMinimalPush() requires a push of 0x01 to be done using OP_1.



                This standardness rule avoids the case where someone takes a transaction from the network and a push with a longer encoding of the same push and as a result creates a malleated form of the transaction.






                share|improve this answer













                Your transaction is failing validation with SCRIPT_VERIFY_MINIMALDATA, which is described in BIP 62 rule 3 protections against malleability. CheckMinimalPush() requires a push of 0x01 to be done using OP_1.



                This standardness rule avoids the case where someone takes a transaction from the network and a push with a longer encoding of the same push and as a result creates a malleated form of the transaction.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 16 '18 at 1:48









                G. MaxwellG. Maxwell

                5,3312839




                5,3312839






























                    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%2f81066%2ferror-while-send-transaction-data-push-larger-than-necessary%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

                    Florida Star v. B. J. F.

                    Danny Elfman

                    Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues