[ad_1]
Bitcoin Stack Alternate is a query and reply web site for Bitcoin customers, builders, and fanatics. It solely takes a minute to enroll.
Anyone can ask a query
Anyone can reply
The most effective solutions are voted up and rise to the highest
Requested
Considered
19 occasions
RBF (Full RBF, Decide-in Full RBF, FSS-RBF) is utilized to a transaction when one in every of its inputs “matches” one of many inputs within the substitute transaction.
Nonetheless, what occurs if the inputs of a substitute transaction “hit” the inputs of two (three or extra) totally different transactions?
-
Does the substitute transaction then exchange all these “hit” transactions (transactions lined by substitute)?
-
To ensure that substitute to happen, does the charge of substitute transaction need to be larger than the most important charge amongst all “lined” transactions, or maybe the charge of substitute transaction have to be larger than the sum of the charges of all “lined” transactions (or one thing else)?
-
What would occur if the node works in Decide-in Full RBF mode and a few of the transactions “included” in substitute don’t settle for the opportunity of substitute (nSequence of all inputs is
0xffffffff)? I assume that the substitute then is not going to even happen and the substitute transaction will likely be simply rejected.
For a substitute to be accepted into the mempool, it has to enhance the mempool for miners. Due to this fact, it has to pay extra charges than all of the ousted transactions, moreover should pay for its personal relay, and eventually can not oust too many transactions directly. Particularly:
- If the node works in Decide-in Full RBF mode, the instantly conflicting transactions should all sign replaceability, in any other case the substitute try fails.
- The substitute transaction should pay no less than as a lot charges as all changed transactions (together with the descendants of the instantly conflicting transactions!) plus its personal vsize occasions the node’s incremental relay feerate.
- The substitute transaction doesn’t spend any new unconfirmed inputs that weren’t already spent by one of many instantly conflicting transactions.
- The substitute transaction should pay a larger feerate than every instantly conflicting transaction
- The sum of the conflicting transactions’ descendant counts doesn’t exceed 100.
You’ll be able to learn extra about this subject for instance within the coverage documentation for Mempool Replacements for Bitcoin Core, and in glozow’s gist gathering her ideas on RBF Enhancements.
This reply omits FSS RBF, as a result of I’m not conscious of any nodes implementing that coverage on the community.
[ad_2]
Supply hyperlink