davide/palladiumcore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: correct Taproot activation threshold from 90% to 75% in documentation

Browse Source 
Update documentation to reflect actual BIP9 deployment parameters:
- Activation threshold: 540/720 blocks (75%) vs incorrectly documented 90%
- Confirmation window: 720 blocks (Palladium custom) vs Bitcoin's 2016
- Add explanatory notes about Palladium's lower threshold for faster coordination
This commit is contained in:
Davide Grilli
2026-02-08 14:07:41 +01:00
parent 130b0e4e31
commit a1aa5755c9
3 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/TAPROOT.md
View File

@@ -273,10 +273,12 @@ This implementation is a backport of Taproot functionality from **Bitcoin Core v
Taproot activates via BIP9 signaling: Taproot activates via BIP9 signaling:
1. Miners signal readiness by setting bit 2 in block version 1. Miners signal readiness by setting bit 2 in block version
2. When 1815 of 2016 blocks in a retarget period signal (90% threshold), deployment is LOCKED_IN 2. When 540 of 720 blocks in a confirmation window signal (75% threshold), deployment is LOCKED_IN
3. After LOCKED_IN period ends, deployment becomes ACTIVE for all subsequent blocks 3. After LOCKED_IN period ends, deployment becomes ACTIVE for all subsequent blocks
4. Timeout on March 1, 2027 if insufficient signaling 4. Timeout on March 1, 2027 if insufficient signaling
**Note**: Palladium uses a 75% activation threshold (540/720 blocks) compared to Bitcoin's 90% (1815/2016 blocks), with a shorter confirmation window to facilitate faster network coordination while maintaining security.
### Script Verification Flags ### Script Verification Flags
**Standard transaction validation** (mempool/relay): **Standard transaction validation** (mempool/relay):

4
doc/release-notes/release-notes-2.0.0.md
View File

@@ -83,8 +83,10 @@ Taproot will activate via BIP9 miner signaling:
- **Mainnet**: BIP9 soft fork activation using bit 2 - **Mainnet**: BIP9 soft fork activation using bit 2
- Signaling starts: February 14, 2026 00:00:00 UTC (block time 1771027200) - Signaling starts: February 14, 2026 00:00:00 UTC (block time 1771027200)
- Signaling timeout: March 1, 2027 00:00:00 UTC (block time 1803859200) - Signaling timeout: March 1, 2027 00:00:00 UTC (block time 1803859200)
- Activation threshold: 1815 of 2016 blocks (90%) must signal readiness - Activation threshold: 540 of 720 blocks (75%) must signal readiness
- Confirmation window: 720 blocks (vs Bitcoin's 2016)
- Status: Once locked in, Taproot activates in the next period - Status: Once locked in, Taproot activates in the next period
- Note: Palladium uses a 75% threshold to facilitate faster network coordination
- **Testnet**: Same parameters as mainnet for realistic testing - **Testnet**: Same parameters as mainnet for realistic testing

4
doc/taproot-guide.md
View File

@@ -225,11 +225,11 @@ Taproot uses Schnorr signatures instead of ECDSA:
Taproot activates via miner signaling (BIP9): Taproot activates via miner signaling (BIP9):
- **Signaling period**: February 14, 2026 - March 1, 2027 - **Signaling period**: February 14, 2026 - March 1, 2027
- **Activation threshold**: 90% of blocks in a 2016-block period (1815 blocks) - **Activation threshold**: 75% of blocks in a 720-block period (540 blocks)
- **Activation method**: BIP9 soft fork using bit 2 - **Activation method**: BIP9 soft fork using bit 2
**What this means**: **What this means**:
- Once 90% of miners signal readiness, Taproot will "lock in" - Once 75% of miners signal readiness, Taproot will "lock in"
- After lock-in, there's a grace period before activation - After lock-in, there's a grace period before activation
- Once activated, everyone must follow Taproot consensus rules - Once activated, everyone must follow Taproot consensus rules