Coin Brief ENDE

Labels catching up: a Deployed status, a hit rate and a mempool rule

On 17 November the Miniscript specification, BIP-379, moved from Draft to Deployed. The pull request gave one reason: support "was released in Bitcoin Core v26 as well as other implementations". The day before, its test vector section, which had said "TBD", was filled with cases extracted from rust-miniscript.

The same day, rippled merged #8660, which makes key-only caches count their hits, misses and removals. Its author describes it as "reporting only, with no behavior change in what the cache holds or returns": until then, the hit rate those caches reported did not reflect what they did. And in Bitcoin Core's new 31.3 and 30.5 tags, the only networking change is a backport whose pull request says there "should be no change in observable behavior".

EIP-8151's new "Public Mempool" section draws a similar line. It states that its rules on recovered signers apply only to mempool validation of frame transactions and "do not affect consensus", separating what nodes may choose to do from what every node must agree on.

Labels catching up: a Deployed status, a hit rate and a mempool rule
Labels catching up: a Deployed status, a hit rate and a mempool rule — Coin Brief

Why it matters

None of these changes alters how software behaves for a user. Each makes the description accurate - of a specification's status, of a cache's statistics, of which rules bind the network - and an accurate description is what the next implementer or operator relies on.

Primary source
BIPs repository
https://github.com/bitcoin/bips/pull/2240
Written by Victoria Shinder.