Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.54
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 343 mandatory Taproot activation in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 343 proposed a BIP8 lock-in-on-timeout-true deployment for Taproot. It used signaling bit 2, a 90% threshold and a block-height schedule intended to mandate signalling only if miners had not already locked in the upgrade.
- Why it matters: BIP 343 records an important mandatory-activation proposal, but it did not activate Taproot. Its useful lesson is the distinction between consensus rules, proposed coordination mechanisms and the mechanism actually shipped and used.
- Current position: The specification is Closed, Consensus soft fork and assigned 25 April 2021.
BIP 343 mandatory Taproot activation in simple English
BIP 343 mandatory Taproot activation: Bitcoin Core 0.21.1 shipped Speedy Trial activation parameters. Taproot locked in through that path and activated at block 709632, leaving the mandatory fallback proposal unused.
Simple example
A node operator is checking BIP 343 mandatory Taproot activation. Full validation required software enforcing BIPs 340, 341 and 342 after activation. As a soft fork proposal, old nodes would continue but treat version-1 witness programs as anyone-can-spend.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Soft fork:
- A proposed tightening of Bitcoin rules that old nodes may not enforce themselves.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
Current status
The specification is Closed, Consensus soft fork and assigned 25 April 2021. Historical explanations must not call it active, deployed or the mechanism used by Bitcoin Core mainnet.
BIP8 proposal
The design set LOT=true so non-signalling blocks could be rejected in the final period if earlier threshold lock-in failed. That is a materially different coordination choice from an optional timeout.
Schedule
It proposed bit 2 from height 681408, minimum activation height 709632, a 90% threshold, timeout at 760032 and latest activation height 762048.
Compatibility
The document described compatibility with Core’s later Speedy Trial because both used bit 2 and their relevant height and median-time-past boundaries did not conflict in practice.
What happened
Bitcoin Core 0.21.1 shipped Speedy Trial activation parameters. Taproot locked in through that path and activated at block 709632, leaving the mandatory fallback proposal unused.
Node meaning
As a soft fork proposal, old nodes would continue but treat version-1 witness programs as anyone-can-spend. Full validation required software enforcing BIPs 340, 341 and 342 after activation.
Historical use
Use BIP 343 to study activation trade-offs, not as current deployment instructions. Preserve contemporaneous status, implementation choice, chain evidence and later closure when building timelines. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.
Frequently asked questions
What is the main point of BIP 343 mandatory Taproot activation?
BIP 343 mandatory Taproot activation: Bitcoin Core 0.21.1 shipped Speedy Trial activation parameters.
For BIP 343 mandatory Taproot activation, what should a beginner know about current status?
The specification is Closed, Consensus soft fork and assigned 25 April 2021.
For BIP 343 mandatory Taproot activation, what should a beginner know about bip8 proposal?
The design set LOT=true so non-signalling blocks could be rejected in the final period if earlier threshold lock-in failed.
For BIP 343 mandatory Taproot activation, what should a beginner know about schedule?
It proposed bit 2 from height 681408, minimum activation height 709632, a 90% threshold, timeout at 760032 and latest activation height 762048.
Conclusion
BIP 343 records an important mandatory-activation proposal, but it did not activate Taproot. Its useful lesson is the distinction between consensus rules, proposed coordination mechanisms and the mechanism actually shipped and used.
Primary sources
- BIP 343 Mandatory activation of Taproot deployment
- Bitcoin Core 0.21.1 Taproot Speedy Trial release notes
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.