Search results

...onents (clusters) and orders them by linearized chunk feerate. It replaced ancestor-and-descendant limits with cluster limits. Bitcoin Core 31.0 shipped the de ...r each transaction, its unconfirmed ancestors and descendants. Mining used ancestor feerate as a proxy for whether a transaction would be selected soon. Replac ...

...hild is invalid in isolation. The package feerate is the total fees of the ancestor set divided by the total virtual size. ...set containing it and all unconfirmed ancestors. Mining code selects high ancestor-feerate sets first, so a well-paying child can pull a low-fee parent into a ...

...saction chunks, so quoting sat/vB remains the user-facing metric even when ancestor score is no longer the sole ranking key. ...exposes fee-rate estimates through <code>estimatesmartfee</code> and uses ancestor score when assembling blocks. Block explorers and mempool visualizers displ ...

Title: Ancestor Package Relay ...peer protocol messages enabling nodes to request and relay the unconfirmed ancestor package ...

...ts from other unconfirmed transactions, but restrict package sizes through ancestor and descendant limits ...ansaction that pays more fees and is higher feerate, but has a low feerate ancestor and would confirm slower than the original transaction. As a result, all tr ...

[[File:Ancestor-feerate1.png|center]] [[File:Ancestor-feerate2.png|center]] ...

...policy limits each cluster to 64 transactions and 101 kB of virtual size. Ancestor and descendant limits are no longer enforced. Replacements are accepted onl ...

...eability are replaceable under this policy for as long as any one of their ancestors signals replaceability and remains unconfirmed. for as long as any ancestor opt-in full-RBF transactions remain ...

...ures the degree to which the code has validated this block, as well as its ancestor blocks. Multimap containing "all pairs A->B, where A (or one if its ancestors) misses transactions, but B has transactions." (comment at <u>main.cpp:125 ...

...hat a block's state never depends on its own nVersion; only on that of its ancestors. current retarget period (i.e. up to and including its ancestor with height block.height - 1 - (block.height % 2016)), ...

...hat a block's state never depends on its own nVersion; only on that of its ancestors. current retarget period (i.e. up to and including its ancestor with height block.height - 1 - (block.height % 2016)), ...

clock defined by a chain, and evaluated on the ancestor of a block, i.e. only on that of its ancestors. ...

...ilters</code> request, and BlockHash must correspond to a block that is an ancestor of StopHash with height greater than or equal to StartHeight. ...

...r to treat PayToBareDefaultCheckTemplateVerifyHash chains with a confirmed ancestor as ...

...transaction, and TOTAL_FEES is the total fees (in BTC) for all unconfirmed ancestors of your stuck transaction. ...

...ology limits. Eligible packages are a parent-child pair with no in-mempool ancestors. Direct conflicts must sit in mempool clusters of size at most two. Absolu ...

Unconfirmed TRUC ancestors and descendants must themselves be TRUC. CPFP carve-out is not granted to ...