Broadcasting issue - [URG help] | Bitcointalksearch.org

nc50lc

legendary

Activity: 2394

Merit: 5531

Self-proclaimed Genius

Quote from: bitstonps on December 26, 2023, 11:54:40 AM

Hex:
-snip-
Any solution please ? Thank you for your responses.

Seems like the transaction is now invalid since the input was replaced with a transaction that replaced one input and output.

Original input: 0c3befe166b4f957a98e050f711c54bd5851716a38de6db1a8d0edc770fd68ed
Replaced by: 74419bc519df0bb513b6201908aca21f7fb33d59b03204daa30457aabc590260

Interestingly, the long transaction chain is a bunch of 1sat/vB fee rate txns as if it's intended.
Whatever the transaction is for, tell your friend to do not finish the deal without waiting for confirmations, no matter what.

odolvlobo

legendary

Activity: 4298

Merit: 3209

With so many unconfirmed inputs, my guess is that a successful CPFP transaction would cost you a fortune.

achow101

staff

Activity: 3374

Merit: 6530

Just writing some code

Your options are to either choose different inputs that do not have so many ancestors, or wait for some ancestors to become confirmed.

As the error says, there are too many unconfirmed ancestors, and the limit is 25. This is the default that most nodes have, so your transaction is unlikely to propagate even if blockcypher accepts your transaction. You need to reduce the number of ancestors, either by removing the inputs that have unconfirmed ancestors such that the number of unconfirmed ancestors is below the limit, or wait for some of those unconfirmed ancestors to confirm.

bitstonps

newbie

Activity: 15

Merit: 6

Hi,

My friend is facing a problem with a transaction where the payment was sent from numerous unconfirmed inputs. When attempting to use CPFP, we encountered an error during the broadcasting step.

I attempted manual broadcasting, but received the following error message from mmpool:
'too-long-mempool-chain, too many unconfirmed ancestors [limit: 25]'

(Here's a screenshot of the message: (https://prnt.sc/Cqk0-hmFPIOp) )

The transaction is successful only on blockcypher. - Broadcasting manually

Hex:

Quote

02000000000101ed68fd70c7edd0a8b16dde386a715158bd541c710f058ea957f9b466e1ef3b0c0 200000000fdffffff01eb62490000000000160014e38589ff4052139632b8dce33000776574304e 84024730440220166da38def7293eee85f1300c96613186325496baf68f8efcfff1ba962cf168b0 2201ac85a066581c0e4b468f264f0864f6b4809c923509df42ff4d7078f71043446012103206787 73057f7b48212dbac5621299e181bf0c7a5cace44898ec88d2c59c4ce6f68e0c00

Any solution please ? Thank you for your responses.

Regards,

Topic: Broadcasting issue - [URG help] (Read 85 times)