Merge bitcoin/bitcoin#35183: doc: recommend script_flags instead of deployments.taproot

f24a7b5f75 doc: recommend script_flags instead of deployments.taproot (Sjors Provoost)

Pull request description:

  #26201 removed `taproot` from `getdeploymentinfo` (not yet in a release, slated for v32), which it turns out Lnd relies on: https://github.com/lightningnetwork/lnd/pull/10683

  Expand the release doc note to recommend the same solution they used: check for `TAPROOT` in the `script_flags` array. This was added in v31.

ACKs for top commit:
  maflcko:
    Stakeholder-aligned SLA-compliant production-ready enterprise-grade lgtm ACK f24a7b5f75
  sedited:
    ACK f24a7b5f75

Tree-SHA512: 5c21300ce3140eb1dd122e007b2f2cfafa3de83db4fb7c699312d6886d4c8fea56d9602390c1931fc640bf9364b2274dde85b38da4957311ddc07721cbc924a7
This commit is contained in:
merge-script
2026-05-11 11:52:17 +02:00

View File

@@ -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)