Author: Pan Zhixiong
Bitcoin Optech's annual summaries have long been regarded as the technical barometer for the Bitcoin ecosystem. They do not on price fluctuations, but on recording the most authentic pulse of the Bitcoin protocol and its critical infrastructure.
The 2025 report reveals a clear trend: Bitcoin is undergoing a paradigm shift from "passive defense" to "active evolution."
Over the past year, the community is no longer content with merely patching vulnerabilities; instead, it has begun systematically addressing existential threats (like quantum computing) and is aggressively exploring the boundaries of scalability and programmability without sacrificing decentralization. This report is not just a memo for developers; it is a key index for understanding Bitcoin's asset attributes, network security, and governance logic for the next five to ten years.
Core Conclusions
Throughout 2025, Bitcoin's technical evolution has exhibited three core characteristics, which are also the key to understanding the following 10 major events:
- Proactive Defense: The defense roadmap against quantum threats has, for the first time, become clear and actionable. Security thinking has extended from the "present" to the "post-quantum era."
- Layered Functionality: The high-density discussion of soft fork proposals and the "hot-swappable" evolution of the Lightning Network show that Bitcoin is achieving the architectural goal of a "stable base layer, flexible upper layers" through layered protocols.
- Infrastructure Decentralization: From mining protocols (Stratum v2) to node validation (Utreexo/SwiftSync), significant engineering resources have been invested in lowering participation barriers and enhancing censorship resistance, aiming to counter the gravitational pull of centralization in the physical world.
Bitcoin Optech's annual report covers hundreds of code commits, mailing list debates, and BIP proposals from the past year. To extract the true signal from the technical noise, I have filtered out updates limited to "local optimizations" and selected the following 10 events that have a structural impact on the ecosystem.
1. Systematic Defense Against Quantum Threats and the "Hardening Roadmap"
【Status: Research & Long-term Proposals】
2025 marks a qualitative change in the Bitcoin community's attitude towards the threat of quantum computing, shifting from theoretical discussion to engineering preparation. BIP360 was assigned a number and renamed P2TSH (Pay to Tapscript Hash). This is seen as a crucial stepping stone for the quantum hardening roadmap and more generally serves certain Taproot use cases (e.g., commitment structures that don't require an internal key).
Simultaneously, the community delved into more specific quantum-safe signature verification schemes. This includes, under the premise of potentially introducing corresponding scripting capabilities in the future (e.g., reintroducing OP_CAT or adding new signature verification opcodes), constructing Winternitz signatures using OP_CAT, discussing making STARK verification a native scripting capability, and optimizing the on-chain cost of hash-based signature schemes (like SLH-DSA / SPHINCS+).
This issue ranks first because it touches the mathematical foundation of Bitcoin. If quantum computing were to weaken the elliptic curve discrete logarithm assumption in the future (thus threatening the security of ECDSA/Schnorr signatures), it would trigger systemic migration pressure and a security stratification of historical outputs. This forces Bitcoin to prepare an upgrade path at the protocol and wallet layers in advance. For long-term holders, choosing custody solutions with an upgrade roadmap and a culture of security audits, as well as paying attention to potential future migration windows, will become essential lessons for asset preservation.
2. Proliferation of Soft Fork Proposals: Building the Foundation for "Programmable Vaults"
【Status: High-Density Discussion / Draft Stage】
This year saw high-density discussions on soft fork proposals, focusing primarily on how to unleash scripting expressiveness while maintaining minimalism. Covenant-like proposals such as CTV (BIP119) and CSFS (BIP348), along with technologies like LNHANCE and OP_TEMPLATEHASH, are all attempting to introduce more secure "covenants" to Bitcoin. Furthermore, OP_CHECKCONTRACTVERIFY (CCV) became BIP443, and various arithmetic opcodes and script recovery proposals are also queuing for consensus.
These seemingly obscure upgrades are, in reality, adding new "physical laws" to the global value network. They hold the promise of making native "Vaults"-like constructions simpler, safer, and more standardized, allowing users to set mechanisms like delayed withdrawals and revocation windows, achieving "programmable self-custody" at the level of protocol expressibility. Simultaneously, these capabilities are expected to significantly reduce the interaction costs and complexity of Layer 2 protocols like the Lightning Network and DLCs (Discreet Log Contracts).
3. "Censorship-Resistant" Restructuring of Mining Infrastructure
【Status: Experimental Implementation / Protocol Evolution】
The decentralization of the mining layer directly determines Bitcoin's censorship resistance. In 2025, Bitcoin Core 30.0 introduced an experimental IPC interface, significantly optimizing the interaction efficiency between mining pool software/Stratum v2 services and Bitcoin Core's validation logic, reducing reliance on inefficient JSON-RPC, and paving the way for Stratum v2 integration.
A key capability of Stratum v2 is (when mechanisms like Job Negotiation are enabled) to further devolve transaction selection power from pools to the more dispersed miner side, thereby enhancing censorship resistance. At the same time, the emergence of MEVpool attempts to address the MEV problem through template blinding and market competition: ideally, multiple marketplaces should coexist to avoid a single marketplace becoming a new centralized hub. This directly relates to whether ordinary users' transactions can still be fairly included in blocks under extreme conditions.
4. Immune System Upgrade: Vulnerability Disclosure and Differential Fuzzing
【Status: Ongoing Engineering Operations】
Bitcoin's security relies on self-examination before real attacks occur. In 2025, Optech documented numerous vulnerability disclosures targeting Bitcoin Core and Lightning implementations (like LDK/LND/Eclair), ranging from stuck funds to privacy deanonymization, and even serious fund theft risks. This year, Bitcoinfuzz utilized "Differential Fuzzing" technology, comparing the reactions of different software to the same data, uncovering over 35 deep-seated bugs.
This high-intensity "stress testing" is a sign of ecosystem maturity. It acts like a vaccine; while it exposes weaknesses in the short term, it significantly enhances the system's immunity in the long run. For users relying on privacy tools or the Lightning Network, this also serves as a wake-up call: no software is absolutely perfect, and keeping critical components updated is the most fundamental rule for ensuring the safety of deposits.
5. Lightning Network Splicing: "Hot Updates" for Channel Funds
【Status: Cross-Implementation Experimental Support】
The Lightning Network (LN) witnessed a major usability breakthrough in 2025: Splicing (channel hot updates). This technology allows users to dynamically adjust channel funds (depositing or withdrawing) without closing the channel. It currently has experimental support in the three major implementations: LDK, Eclair, and Core Lightning. Although the relevant BOLTs specifications are still being refined, significant progress has been made in cross-implementation compatibility testing.
Splicing is the key capability for "adding or subtracting funds without closing the channel." It is expected to reduce payment failures and operational friction caused by the inconvenience of adjusting channel funds. In the future, wallets are expected to significantly lower the learning curve of channel engineering, allowing more users to use the LN as a payment layer closer to a "balance account," which is a crucial piece for Bitcoin payments moving towards mass daily use.
6. Validation Cost Revolution: Running Full Nodes on "Common Devices"
【Status: Prototype Implementation (SwiftSync) / BIP Draft (Utreexo)】
The moat of decentralization lies in validation cost. In 2025, two technologies, SwiftSync and Utreexo, directly tackled the "full node barrier." SwiftSync optimizes the UTXO set write path during IBD (Initial Block Download): it only adds an output to the chainstate if it is confirmed as still unspent at the end of IBD, and with the help of a "minimally trusted" hints file, it accelerated the IBD process by over 5x in sample implementations, while also opening space for parallel validation. Utreexo (BIP181-183), on the other hand, uses a Merkle forest accumulator, allowing nodes to validate transactions without storing the full UTXO set locally.
The advancement of these two technologies means that running a full node on resource-constrained devices will become practically feasible, increasing the number of independent verifiers in the network.
7. Cluster Mempool: Reshaping the Underlying Scheduling of the Fee Market
【Status: Nearing Release (Staging)】
Among the expected features for Bitcoin Core 31.0, the implementation of Cluster Mempool is nearing completion. It introduces structures like TxGraph, abstracting complex transaction dependency relationships into an efficiently solvable "transaction cluster linearization/ordering" problem, making block template construction more systematic.
Although this is an underlying scheduling system upgrade, it is expected to improve the stability and predictability of fee estimation. By eliminating abnormal inclusion orders caused by algorithmic limitations, the future Bitcoin network will behave more rationally and smoothly during congestion, and users' transaction acceleration requests (CPFP/RBF) can also take effect under more deterministic logic.
8. Fine-Grained Governance of the P2P Propagation Layer
【Status: Policy Updates / Continuous Optimization】
In response to the surge in low-fee transactions observed in 2025, the Bitcoin P2P network experienced a policy inflection point. Bitcoin Core 29.1 lowered the default minimum relay fee to 0.1 sat/vB. Meanwhile, the Erlay protocol continued to advance to reduce node bandwidth consumption; additionally, the community proposed ideas like "block template sharing" and continued to optimize compact block reconstruction strategies to cope with an increasingly complex propagation environment.
With more consistent policies and lower default node thresholds, the feasibility of propagating low-fee transactions across the network is expected to improve. These directions are expected to lower the hard bandwidth requirements for running a node, further maintaining the network's fairness.
9. The OP_RETURN and the "Tragedy of the Commons" Debate Over Block Space
【Status: Mempool Policy Change (Core 30.0)】
Core 30.0 relaxed the policy restrictions on OP_RETURN (allowing more outputs, removing some size limits), which sparked a fierce philosophical debate about Bitcoin's purpose in 2025. Note that this is a Bitcoin Core Mempool Policy (default relay/standardness policy) change, not a consensus rule change; however, it significantly affects whether a transaction is easily propagated and seen by miners, thus genuinely impacting the competition for block space.
Proponents argue it corrects incentive distortions, while opponents worry it could be seen as an endorsement of "on-chain data storage." This debate reminds us that block space, as a scarce resource, has its usage rules (even at the non-consensus level) subject to ongoing博弈 (game theory/negotiation) among various interests.
10. Bitcoin Kernel: "Componentization" Refactoring of Core Code
【Status: Architectural Refactoring / API Release】
Bitcoin Core took a key step towards architectural decoupling in 2025: introducing the Bitcoin Kernel C API. This marks the separation of "consensus validation logic" from the massive node program into an independent, reusable standard component. Currently, this kernel can support external projects in reusing block validation and chain state logic.
"Kernelization" will bring structural security benefits to the ecosystem. It allows wallet backends, indexers, and analysis tools to directly call the official validation logic, avoiding consensus divergence risks caused by reinventing the wheel. This is like providing the Bitcoin ecosystem with a standardized "OEM engine"; applications built on top of it will be more robust.
Appendix: Terminology Glossary (Mini-Glossary)
To aid reading, here are brief definitions of key terms in the article:
- UTXO (Unspent Transaction Output): The basic unit of the Bitcoin ledger state, recording who owns how many coins.
- IBD (Initial Block Download): The process where a new node synchronizes historical data when joining the network.
- CPFP / RBF: Two transaction acceleration mechanisms. CPFP (Child Pays For Parent) uses a new transaction to pull an old one; RBF (Replace-By Fee) directly replaces a low-fee transaction with a higher-fee one.
- Mempool (Memory Pool): A buffer used by nodes to store transactions that have been broadcast but not yet included in a block.
- BOLTs: The series of technical specifications for the Lightning Network (Basis of Lightning Technology).
- MEV (Maximal Extractable Value): The maximum value that can be extracted by miners through reordering or censoring transactions.
