AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 20 Bitcoin

Remove Taproot activation height

Public commit record

What the developer wrote

Authored by Sjors Provoost

80/100 · Strong
Remove Taproot activation height

Drop DEPLOYMENT_TAPROOT from consensus.vDeployments.

Bump MinBIP9WarningHeight.

Clarify what is considered a BuriedDeployment and
drop taproot from getdeploymentinfo RPC.

Add a test to getblocktemplate to ensure the taproot
rule is still set.

Co-Authored-By: MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit cleans up Bitcoin Core's code after Taproot has already activated. It removes Taproot's old activation parameters from the list of live BIP9 deployments and from the getdeploymentinfo RPC, because those parameters are no longer needed now that the rules are enforced. It also makes sure getblocktemplate still tells miners the 'taproot' rule is required. There is no direct security vulnerability here; it is routine post-activation maintenance, though any consensus-cleanup change carries a small risk of accidental behavior change.

Recommended action

Review as normal consensus-cleanup maintenance. Verify that getblocktemplate still advertises the taproot rule correctly and that no active consensus enforcement logic was accidentally removed. No urgent security action is indicated.

Security signals we found

01

Consensus deployment parameter removal for an activated soft fork

02

BIP9 warning threshold adjustment to suppress historical activation warnings

03

getblocktemplate rule list change affecting miner template compatibility

04

RPC output change (getdeploymentinfo no longer reports taproot)

05

No bug fix, boundary check, memory safety, or cryptographic change present

Risk score

Why this scored 20/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 3/15
Confidence 9/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.