2

I sent a bare $1000 multisig transaction using sendrawtransaction with a too low fee.

When I create a new transaction with a higher fee, I m getting txn-mempool-conflict error, and when I use the bumpfee command, I m getting Transaction is not BIP 125 replaceable.

So given I sent it yesterday, in how much time I would be to access the money again?

Antoine Poinsot
  • 5,881
  • 2
  • 11
  • 28
user2284570
  • 286
  • 2
  • 14

1 Answers1

2

Assuming most of the nodes on the network run with the default configuration of maxmempoolexpiry, most of the network mempools will drop your transaction after 336 hours (2 weeks).

You should have crafted your transaction such that it signals BIP125 replaceability (by having at least one of the input nSequence <= 0xfffffffd).

At this point, you could use CPFP (spend the output you just created with a high fee-paying transaction paying for the whole package) or use a pool "transaction accelerator" to send a new version of your transaction paying higher fees.

See also Why is my transaction not getting confirmed and what can I do about it? .

Antoine Poinsot
  • 5,881
  • 2
  • 11
  • 28
  • Really annoying. For cpfp, I m getting `input does not exists`, it seems transactions accelerators don t accept bare multisig. Is there a way to get my money without facing such huge price volatility risk? – user2284570 Dec 31 '20 at 12:14
  • I personally think we should always signal for RBF: "you can't predict the block space market ":) For your CPFP issue it means your node isn't aware of your transaction yet (maybe there is hope here?), or you miscrafted your child transaction. – Antoine Poinsot Dec 31 '20 at 12:22
  • It appears in the transaction list, so I d rather say it considers the input as already spent because being in the mempool. – user2284570 Dec 31 '20 at 12:24
  • No, the error is not the same on conflicting transactions. – Antoine Poinsot Dec 31 '20 at 12:25