Someone please rebroadcast this Transaction.

[ShakinHandz]

Guys I am out of Town , and this transaction is struck!
Can someone rebroadcast it?

[1715121115]

1715121115

[1715121115]

1715121115

[1715121115]

1715121115

[shorena]

link: https://blockchain.info/tx/70f63e662a4e08b4984244ece8103854627c3e960ebea9ca3d9c33c40264f4eb
raw:

Code:

01000000017ca61d7474a3845767988bb58ea5bb0490e4257e98fd2acbaa86bf2eb6164b64010000006a47304402200d116eeff77227e2d17b652d86e6979d067e17f0e832493a0acae2cc300fd2160220337609ed360bb6ba7561db89e2dc281cba3de9455c452f5980f9c30db4b065b8012103fa554feabcfe32db72e44e82000790ee63dd3150901f0060e4bcc65b2df0c5beffffffff026ae02700000000001976a91439ae9f854d806a6f34d8c0e8ce55175a7891dcfc88ac16045203000000001976a9147a0df932a3d0caf0893efb32fe2fedfd26be63bd88ac00000000

error from core:

Code:

error: {"code":-27,"message":"transaction already in block chain"}

Its confirmed while writing this.

[ShakinHandz]

Thanks mate , You did that or what?

[mexxer-2]

Thanks mate , You did that or what?

Seem the fee was enough, and as shorena said, it confirmed before he could rebroadcast it

[shorena]

Thanks mate , You did that or what?

Nope, it was unconfirmed when I copied the raw TX to clipboard and confirmed on my node a few seconds later when I tried to rebroadcast it.

I wish this was something I could do though.

[bill gator]

Thanks mate , You did that or what?

Nope, it was unconfirmed when I copied the raw TX to clipboard and confirmed on my node a few seconds later when I tried to rebroadcast it.

I wish this was something I could do though.

This thread is slightly confusing to me.. Is rebroadcasting a "stuck" transaction something that can be done from a third-party?

[mexxer-2]

This thread is slightly confusing to me.. Is rebroadcasting a "stuck" transaction something that can be done from a third-party?

Yup Blockchain(.info) has the function , you can do it with your node(if you have one that is)
Edit: Being more clear

[bill gator]

This thread is slightly confusing to me.. Is rebroadcasting a "stuck" transaction something that can be done from a third-party?

Yup Blockchain has the function , you can do it with your node(if you have one that is)

I do have a node, but I seem to be clueless about 99% of it's functionality.. I'm sure this is neatly written out somewhere though..

Where can I find all the documentation on "rebroadcasting" and similar functions?

[Alaki]

Where can I find all the documentation on "rebroadcasting" and similar functions?

-> https://blockchain.info/tx/70f63e662a4e08b4984244ece8103854627c3e960ebea9ca3d9c33c40264f4eb?format=hex (https://blockchain.info/tx/tx-id?format=hex) -> copy code -> paste @ https://blockchain.info/pushtx . simple & as easy as that.

[ranochigo]

This thread is slightly confusing to me.. Is rebroadcasting a "stuck" transaction something that can be done from a third-party?

Yup Blockchain has the function , you can do it with your node(if you have one that is)

I do have a node, but I seem to be clueless about 99% of it's functionality.. I'm sure this is neatly written out somewhere though..

Where can I find all the documentation on "rebroadcasting" and similar functions?

To rebroadcast from Bitcoin Core, go to Help>Debug Window>Console and type in this

Code:

sendrawtransaction [Raw TX in hex here]

.
To get the raw transaction, this is the command

Code:

getrawtransaction [TXID]

or follow the steps that the user above me has described.

[bill gator]

Where can I find all the documentation on "rebroadcasting" and similar functions?

-> https://blockchain.info/tx/70f63e662a4e08b4984244ece8103854627c3e960ebea9ca3d9c33c40264f4eb?format=hex -> copy code -> paste @ https://blockchain.info/pushtx . simple & as easy as that.

I suppose I'm looking for a more thorough explanation as to what it means to rebroadcast, because it sounds like something that could be abused or at least disruptive. I probably just don't fully understand it, yet.

Thanks for not shoo'ing me away & Thanks for the walk-through.

Gonna go peak through the Github repo, try to see how well C++ explains it.

[ranochigo]

Where can I find all the documentation on "rebroadcasting" and similar functions?

-> https://blockchain.info/tx/70f63e662a4e08b4984244ece8103854627c3e960ebea9ca3d9c33c40264f4eb?format=hex -> copy code -> paste @ https://blockchain.info/pushtx . simple & as easy as that.

I suppose I'm looking for a more thorough explanation as to what it means to rebroadcast, because it sounds like something that could be abused or at least disruptive. I probably just don't fully understand it, yet.

Thanks for not shoo'ing me away

It cannot be used for abusive purposes. It is basically a method to broadcast the signed transaction to the network.

Modifying any parts of the raw TX would render it useless. If I understand it correctly, someone could potentially modify the TXID to another random one and thus invalidating the newer transaction using the UXTO from that TX.

This isn't an issue since it doesn't modify the value, address or anything else in the transaction. This was a problem with unconfirmed TXes. However, with majority of the network refusing to relay transactions with high s value, this wouldn't work anymore.

[bill gator]

Where can I find all the documentation on "rebroadcasting" and similar functions?

-> https://blockchain.info/tx/70f63e662a4e08b4984244ece8103854627c3e960ebea9ca3d9c33c40264f4eb?format=hex -> copy code -> paste @ https://blockchain.info/pushtx . simple & as easy as that.

I suppose I'm looking for a more thorough explanation as to what it means to rebroadcast, because it sounds like something that could be abused or at least disruptive. I probably just don't fully understand it, yet.

Thanks for not shoo'ing me away

It cannot be used for abusive purposes. It is basically a method to broadcast the signed transaction to the network.

Modifying any parts of the raw TX would render it useless. If I understand it correctly, someone could potentially modify the TXID to another random one and thus invalidating the newer transaction using the UXTO from that TX.

This isn't an issue since it doesn't modify the value, address or anything else in the transaction. This was a problem with unconfirmed TXes. However, with majority of the network refusing to relay transactions with high s value, this wouldn't work anymore.

Thanks for the further explanation, I appreciate it and I think I understand it pretty thoroughly now. My worries have been put to rest.

[ShakinHandz]

Well , i can see a lot of helping People! Guys you cleared my doubts also..

[shorena]

The easiest explanation I can think of for rebroadcasting is:

#1 ShakinHandz wants to sell socks on a market and shouts "ShakinHandz selling socks for 0.01 BTC each" once.
#2 Market network all pick up the message and shout it again once for each node of the network. Thus all participants quickly know the message (within seconds).
#3 Some time passes and market participants forgot about the message. Other messages come in constantly.
#4 I (or anyone else with a full node or using the above sites) can pick up the old message and shout it again, causing a new wave of market network shout outs.
#4.1 If I would modify the message (malleability aside for a second) to say "ShakinHandz selling rocks for 0.01 BTC each" the network would detect it as invalid and possible exclude me from the market if I do it too often.
#4.2 If I would not modify the message (it stays exactly the same), but modify the signature slightly (malleability attack) while keeping it valid, the network would confirm the message under a different TX ID. This can be a problem for follow up message (somewhere here the metaphor horribly breaks). Currently nodes do not allow for this modification so its very difficult and only works on old nodes.

I hope it helps even though the metaphor was only good for the rebroadacasting itself, not the possibly modified TX.

[bill gator]

The easiest explanation I can think of for rebroadcasting is:

#1 ShakinHandz wants to sell socks on a market and shouts "ShakinHandz selling socks for 0.01 BTC each" once.
#2 Market network all pick up the message and shout it again once for each node of the network. Thus all participants quickly know the message (within seconds).
#3 Some time passes and market participants forgot about the message. Other messages come in constantly.
#4 I (or anyone else with a full node or using the above sites) can pick up the old message and shout it again, causing a new wave of market network shout outs.
#4.1 If I would modify the message (malleability aside for a second) to say "ShakinHandz selling rocks for 0.01 BTC each" the network would detect it as invalid and possible exclude me from the market if I do it too often.
#4.2 If I would not modify the message (it stays exactly the same), but modify the signature slightly (malleability attack) while keeping it valid, the network would confirm the message under a different TX ID. This can be a problem for follow up message (somewhere here the metaphor horribly breaks). Currently nodes do not allow for this modification so its very difficult and only works on old nodes.

I hope it helps even though the metaphor was only good for the rebroadacasting itself, not the possibly modified TX.

It definitely does help, because I was trying to wrap my head around where malleability comes into play, and the different manipulations that might take place. I appreciate the explanation