New answers tagged

0 votes
Accepted

How to avoid "Unconfirmed UTXOs are available, but spending them creates a chain of transactions that will be rejected by the mempool"?

It sounds like your wallet’s UTXO pool is too small for the number of transactions you are making. Here are some possible ways to mitigate your issue: Dial-back consolidatory behavior If you are ...
Murch's user avatar
  • 75.4k
0 votes

How to avoid "Unconfirmed UTXOs are available, but spending them creates a chain of transactions that will be rejected by the mempool"?

Nothing, as you are not deciding the ancestor count for other nodes. See https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-limits.md Similar question: https://bitcoin.stackexchange.com/...
Rutger Versteegden's user avatar
0 votes

Can an unconfirmed transaction be confirmed several years later?

A Bitcoin transaction becomes immutable and irreversible only when it gets : (i) included in a candidate block (ii) the block in which it was included by a miner gets mined (iii) more blocks are ...
Faisal Qureshi's user avatar
6 votes

Can an unconfirmed transaction be confirmed several years later?

Yes, that is possible. If the UTXOs still exist and the transaction is otherwise valid, then it could still be confirmed after all of that time.
chytrik's user avatar
  • 18.3k
3 votes

I can't parse the UTXO from the chainstate

I got it :_) I used binary.ReadUvarint which not the same as ReadVarint in the Bitcoin Core (https://github.com/bitcoin/bitcoin/blob/0d509bab45d292caeaf34600e57b5928757c6005/src/serialize.h#L465) So ...
Novak's user avatar
  • 41

Top 50 recent answers are included