I'm hitting this same problem. Does anyone know how to do this? Add an input transaction or fee to a MultiSig contract transaction?
On Thursday, May 18, 2017 at 7:19:44 AM UTC-6, Jameson Lopp wrote: > > Hm, "priority" is an outdated concept in Bitcoin since the emergence of > the fee market. I suspect that this older 0.12.1 node tried to use the > priority rules to decide whether or not to accept the transaction because > you did not pay a sufficient fee. I see in your debug output you paid 0 > fee: fee 0.00 BTC/kB > > Please note that as of today you will want to pay at least 200 satoshis > per byte, thus a 488 byte transaction should pay around 100,000 satoshis > if you want a timely confirmation. > > On Wed, May 17, 2017 at 10:01 PM, Ramez Az <[email protected] > <javascript:>> wrote: > >> Hi, >> >> When i am trying to do Assurance contract, the transaction is not getting >> added in blockchain and getting the below error. Please find the >> transaction detail also as below. >> Why the transaction is getting rejected and how to resolve the same. >> Please find the attached source code which i am using. >> >> >> *SEVERE: [2001:4800:7818:103:be76:4eff:fe05:f119]:18333 /Satoshi:0.12.1/: >> Received Reject: tx >> 239d75a563a5aeda81ce6396683c32d74858db9c1d871e1b928c0c2e871ea544 for reason >> 'insufficient priority' (66)* >> >> >> >> Paid {} satoshis in fees to create pledge tx {} >> 239d75a563a5aeda81ce6396683c32d74858db9c1d871e1b928c0c2e871ea544 >> updated: 2017-05-18T01:46:55Z >> in >> PUSHDATA(72)[3045022100fe582f3a3066295d14578506266aa99dbb7f08d0507a97a397026fc545b575fb02205bd9c84ad62e22f4c9fe6cf37389cf26ab7d1787341aeeec56ed77fe27bc560581] >> >> PUSHDATA(33)[025c66f18877f0ab7ed7f3cc2523cfdf86f1761c3d865181636b305fffa65e67a0] >> >> 0.0025 BTC >> >> outpoint:59d4a3cac34334c955a32266b5a215d3bb1e4155c90fef461e1e592303ecb8d1:1 >> hash160:54f50c0e5825a5463a579afdeeddd9dcb843274f >> in >> PUSHDATA(72)[304502210091404bc945fcb7023e7fd5132d944689fe79394ac080645219b6128d5ac00a5a0220374d09ebebfb306cceffc14026219bca4e482ad93d8135f6e457484bd1862bfe81] >> >> PUSHDATA(33)[024de0481f28e6ac8fff47252481edb0f0abdf9404d251393c531e61294c32d8ac] >> >> 0.0015 BTC >> >> outpoint:50bcea95914521dc4dcfdc210f45aee41dd35a17a21d58f9e54e245ad8d9a26d:0 >> hash160:ce0df459881561cf8c2bca7a97d8ed9810afe64d >> in >> PUSHDATA(72)[3045022100e17f6052cab558505a827c40e944ce4be3b1cbba594f13960a85c4f88a1cc1c80220633235e5f918df3fa3329548bbcea06afb9984fbe495ef8fe96a7da57cb2f66481] >> >> PUSHDATA(33)[02b4ac87132155e7c053c6e001a5b8b5110799300745878465d772f2c510d0812b] >> >> 0.001 BTC >> >> outpoint:4c3c3b6d1195a8b38c8d407dd76d27b5eb5fea7219c253b5df4a798718b1d7c4:0 >> hash160:25be6926978f89a7a7128855e2c3bc22dbc7e8ab >> out DUP HASH160 >> PUSHDATA(20)[0a7d4079480869b03982e8652abd502fae64042f] EQUALVERIFY CHECKSIG >> 0.005 BTC >> fee 0.00 BTC/kB, 0.00 BTC for 488 bytes >> prps ASSURANCE_CONTRACT_CLAIM >> >> >> Thanks, >> Ramesh A >> >> -- >> You received this message because you are subscribed to the Google Groups >> "bitcoinj" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
