Few questions regarding ListTransaction



Summary:

In a recent discussion on the bitcoin-dev mailing list, ZmnSCPxj clarified that miners can ignore nSequence when adding transactions to blocks, and unconfirmed transactions are not recorded in blocks. This means that if there are conflicting transactions with different fees, miners can include the one with the higher fee even if they learned about the other one first. As a result, "full replace-by-fee", where nSequence is ignored for replace-by-fee purposes, is expected to become the norm. The convention of nSequence=0xFFFFFFFF meaning opt-out of RBF is only followed by full nodes running standard bitcoind. Miners can run patched bitcoind that ignores this rule and connect with similar peers who also ignore it. Peter Todd mentioned that his full-replace-by-fee tree ignores nSequence=0xFFFFFFFF and does preferential peering to ensure it's well connected with likewise peers and thus the whole network.


Updated on: 2023-06-13T01:28:48.608422+00:00