sendrawtransaction length limit need HELP

[no141]

If someone has a transaction that did not propagate through the network, mainly due to it's size and low fee added, how can it be fixed with the debug console limited to about 32,800 bytes?

For this example, there's about 200 inputs, so the size of the raw transaction is over 60,000 bytes. This will not all fit on the console line and it's too long for windows command line length.


There is no older wallet backup to go to, to remove the stuck transaction. So solutions are needed. Maybe the wallet.dat could be edited? Maybe there's some other way to input a really long raw transaction? Something else to either eliminate this stuck transaction or get it processed?

Actually this is not a problem with bitcoin, however the limit on the debug console line is the same, and that's the part causing the issue.

Thank you

[rapta]

What about through RPC?

[amaclin]

how can it be fixed with the debug console limited to about 32,800 bytes?

1) Isn't it possible to look into the client sources and change the constant?
2) May be it is possible to send transaction via the web-form https://blockchain.info/pushtx and other?
3) Create your own program for sending large txs

[theymos]

Break the transaction in half. You don't need to resend the exact same transaction if the network has already forgotten about the first one.

[no141]

@amaclin, I tried the blockchain.info send transaction, and it results in: "The Maximum number of inputs in a single transaction is 200"

Thank you for all the suggestions. And I will look into all of them after I try linux that has a command line length long enough to accommodate the long raw transaction.

@theymos, only one wallet knows about the transaction, as far as can be told. No idea how to remove it from the wallet.

[shorena]

@amaclin, I tried the blockchain.info send transaction, and it results in: "The Maximum number of inputs in a single transaction is 200"

Thank you for all the suggestions. And I will look into all of them after I try linux that has a command line length long enough to accommodate the long raw transaction.

@theymos, only one wallet knows about the transaction, as far as can be told. No idea how to remove it from the wallet.

If its your wallet use pywallet. If it belongs to someone else just ignore it. One node will not stop a pushtx.