Hey everyone,
So my buddy is having a tough time with a transaction. He sent it from a bunch of unconfirmed inputs, and now when we try to use CPFP, we hit a snag during the broadcasting phase.
I tried to broadcast it manually, but got this error from mmpool: 'too-long-mempool-chain, too many unconfirmed ancestors [limit: 25]'.
(I even grabbed a screenshot of the error: (https://prnt.sc/Cqk0-hmFPIOp))
The transaction seems to go through fine on blockcypher when broadcasting manually.
Here’s the hex:
Any ideas on how to fix this? Appreciate any help.
Thanks!
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.
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.