doc: recommend script_flags instead of deployments.taproot
What changed, and why it matters
This is a small documentation-only change to Bitcoin Core release notes. It clarifies how developers should check for Taproot support after the 'taproot' field was removed from the getdeploymentinfo RPC. No code behavior changed, and there is no security vulnerability in the commit itself.
No security action required. Reviewers may want to verify that the release-note guidance accurately reflects the intended RPC behavior in Bitcoin Core v31.0, but this is a documentation quality matter, not a security issue.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit edits doc/release-notes-26201.md to update guidance for downstream applications that previously used deployments.taproot from getdeploymentinfo. It now recommends either assuming Taproot is always active (from v24.0 onward) or checking for TAPROOT in the script_flags array (from v31.0 onward). The diff contains only markdown text changes; no RPC logic, consensus code, or script validation rules were modified.
Changed components
doc/release-notes-26201.mdInspect captured patch +6 / −1
diff --git a/doc/release-notes-26201.md b/doc/release-notes-26201.md
index 66c9da54..108b1bfd 100644
--- a/doc/release-notes-26201.md
+++ b/doc/release-notes-26201.md
@@ -1,4 +1,9 @@
RPC
---
-- 'taproot' has been removed from 'getdeploymentinfo' because its historical activation height is no longer used anywhere in the codebase. (#26201)
+- 'taproot' has been removed from 'getdeploymentinfo' because its historical
+ activation height is no longer used anywhere in the codebase.
+ Applications that rely on `deployments.taproot` to detect Taproot support
+ should either assume Taproot to be always active (since Bitcoin Core v24.0),
+ or check for `TAPROOT` in the `script_flags` array returned by
+ `getdeploymentinfo` (since Bitcoin Core v31.0). (#26201)
Why this scored 20/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.