March Bitcoin Update: Mempool Upgrades and BIP-360 Progress
A focused March Bitcoin technology update covering mempool upgrades, progress on quantum-resistance via BIP-360, and why these changes matter now.
A closer March Bitcoin technology update shows three separate engineering tracks moving at once: shipped mempool policy changes in Bitcoin Core, a relay proposal around taproot annex usage, and a still-draft quantum-resistance proposal. That mix matters because the concrete work is happening at node policy level today, while any deeper cryptographic redesign remains contested and unfinalized.
What Changed in Bitcoin’s Mempool Stack During March
The mempool, the holding area for unconfirmed bitcoin transactions, moved back into focus because Bitcoin Core’s 29.0 release notes document policy changes that affect how small outputs and incomplete transaction trees move across the network.
TL;DR Keypoints
- Bitcoin Core shipped concrete mempool-policy changes rather than just opening another design discussion.
- Libre Relay’s annex plan shows relay experimentation is continuing at the policy layer.
- Quantum-resistance work has a named draft in P2MR, but the cited evidence still shows design debate, not deployment.
In Bitcoin Core 29.0, ephemeral dust lets a transaction create a dust output in a zero-fee package if that output is spent within the same package. That is a narrow policy change, but it gives package-based transaction construction more room without reopening ordinary dust spam policy.
The same release notes say nodes now try to download missing parents from every peer that announced an orphan transaction. For node operators, that matters because orphan recovery becomes more reliable when transactions propagate out of order, which is exactly the kind of edge case that can distort fee estimation and confirmation expectations.
For market context, the research brief’s snapshot had bitcoin trading at $68,578. That matters because mempool policy work is being shipped while the asset still commands broad market attention, not in a period of network irrelevance.
That separation from market storytelling matters because price-led coverage, including Defiliban’s earlier look at whether Bitcoin could revisit $55K before a $100K breakout, answers a different question than the 29.0 release notes. One is about market structure, while the other is about transaction policy that operators can act on immediately.
Why BIP-360 Matters for Bitcoin’s Quantum-Resistance Roadmap
BIP-360 is the official Draft proposal for Pay-to-Merkle-Root, or P2MR, in the Bitcoin BIPs repository. Its significance is not that Bitcoin has settled on a post-quantum migration path, but that the discussion now has a concrete soft-fork design that other developers can critique line by line.
Technical Scope Is Clearer Than the Timeline
The BIP-360 abstract says P2MR removes Taproot’s key-path spend and targets long-exposure attacks, but it does not solve the short-exposure window while a transaction is waiting in the mempool unless additional post-quantum signature work arrives. That makes the proposal forward-looking, but also narrower than a headline about “quantum-resistance” can imply.
That is why the idea of March “progress” needs restraint. The strongest verified signal is that BIP-360 remains Draft, while discussion on Delving Bitcoin shows substantive disagreement over whether the design materially improves Bitcoin’s quantum posture in its current form.
“the current proposal achieves nothing in my mind.”
Pieter Wuille on Delving Bitcoin
Given that Draft status and the criticism captured in the forum debate, the most defensible reading is that Bitcoin’s quantum-resistance track is still in design review. Developers can analyze the proposal today, but the cited materials do not establish a deployment path or activation timeline.
How These March Developments Shape Bitcoin’s Next Technical Narrative
Relay experimentation also continued outside Bitcoin Core. On March 20, 2025, Peter Todd wrote that Libre Relay planned to relay taproot-annex transactions only if non-empty annexes start with 0x00 and every input includes an annex. That proposal belongs in the same conversation as mempool work, but it is a relay-policy experiment rather than a Bitcoin-wide consensus change.
“All inputs have an annex. This ensures that use of the annex is opt-in, preventing transaction pinning attacks in multi-party protocols.”
Peter Todd on the Bitcoin development mailing list
The same market snapshot put bitcoin’s market capitalization at about $1.37T. For node operators and investors alike, that scale explains why even narrowly scoped relay policy decisions attract scrutiny once they touch transaction propagation and mempool behavior.
The clearest contrast in the cited material is between Bitcoin Core 29.0, which already changed ephemeral dust handling and orphan fetching, and BIP-360, which remains a debated draft. One track changes how transactions move through today’s network, while the other asks what kind of cryptographic assumptions Bitcoin may need years from now.
No single official March-dated source in the cited set, spanning the Bitcoin Core release notes, Peter Todd’s mailing-list post, and the BIP-360 draft, ties all three threads into one coordinated roadmap update. The evidence supports a narrower conclusion: Bitcoin shipped practical mempool refinements, saw relay experimentation around annex usage, and kept quantum-resistance work in the design-review stage.
For developers, the actionable material is in release notes, policy rules, and draft text rather than in activation planning. For readers trying to understand Bitcoin beyond price, March mattered because it exposed where shipping code ends and unresolved design begins.
Disclaimer: This article is for informational purposes only and is not financial advice.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
Defiliban · Oliver Benjamin
Oliver Benjamin
@oliver-benjamin