At the moment, if you want to rebroadcast a transaction, say, to a new node, you need to getrawtransaction, take the output of that, and use it with sendrawtransaction after restarting the client. If you try this without the restart, you'll get this: "TX rejected (code -22)" If a transaction is already in the client's memory, it should return a more specific error message, the way "transaction already in block chain (code -5)" is returned for one of those transactions. In addition, there should be a way to force a rebroadcast, whether that's simply making a would-be rebroadcast go through rather than rejecting, or adding a command that will push it through anyway.
Allow force-rebroadcasting of a transaction, make sendrawtransaction return a unique message if transaction is already known #2512
issue Michagogo opened this issue on April 11, 2013-
Michagogo commented at 6:54 PM on April 11, 2013: contributor
-
Michagogo commented at 4:36 PM on June 9, 2013: contributor
Actually, in general it would be nice if sendrawtransaction would be more verbose about what exactly failed whan a TX is rejected...
-
yhaenggi commented at 6:35 AM on August 7, 2013: none
was nobody interested in this?
- laanwj added the label Improvement on Feb 21, 2014
-
- laanwj closed this on Feb 22, 2014
-
Michagogo commented at 5:01 PM on February 22, 2014: contributor
Heh, I'd completely forgotten about this issue...
Also, is it a common practice to close issues before the fix is actually pulled?
On Saturday, February 22, 2014, Wladimir J. van der Laan < notifications@github.com> wrote:
— Reply to this email directly or view it on GitHubhttps://github.com/bitcoin/bitcoin/issues/2512 .
-
laanwj commented at 8:32 AM on February 23, 2014: member
Yes, any discussion can happen in that issue now (There were a lot of issues about this. One is enough).
- MarcoFalke locked this on Sep 8, 2021
Labels