Update Taproot activation timeline: advance mainnet start date

Move Taproot signaling start date earlier to allow more time for miner
preparation and coordination before the March 2027 timeout.

Consensus changes:
- Mainnet activation start: February 14, 2026 (was March 1, 2026)
- Mainnet timeout: March 1, 2027 (unchanged)
- Update nStartTime: 1771027200 (was 1772323200)
- Applied to both mainnet and testnet deployments

This extends the signaling window from 12 months to 12.5 months, providing
miners additional time to upgrade and signal readiness for Taproot activation
This commit is contained in:
2026-02-08 11:45:19 +01:00
parent 24bf2eaae0
commit 97b520f1a1
6 changed files with 8 additions and 8 deletions

View File

@@ -16,7 +16,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Address type dropdown in GUI Receive tab for selecting legacy/P2SH-SegWit/bech32/bech32m
- `getnewaddress` RPC support for "bech32m" address type parameter
- XOnlyPubKey class for 32-byte x-only public key representation
- Taproot deployment via BIP9 soft fork (bit 2, mainnet activation March 2026-2027)
- Taproot deployment via BIP9 soft fork (bit 2, mainnet activation February 2026-March 2027)
- Functional test `feature_taproot.py` for end-to-end Taproot lifecycle validation
- Comprehensive technical documentation in doc/TAPROOT.md
- User-friendly Taproot guide in doc/taproot-guide.md

View File

@@ -202,7 +202,7 @@ This implementation is a backport of Taproot functionality from **Bitcoin Core v
**Mainnet**:
- Deployment: BIP9 soft fork
- Bit: 2
- Start time: 1772323200 (March 1, 2026 00:00:00 UTC)
- Start time: 1771027200 (February 14, 2026 00:00:00 UTC)
- Timeout: 1803859200 (March 1, 2027 00:00:00 UTC)
- Min activation height: Not specified (activation determined by signaling threshold)

View File

@@ -43,6 +43,6 @@ BIPs that are implemented by Palladium Core (up-to-date up to **v0.19.0**):
* [`BIP 174`](https://github.com/palladium/bips/blob/master/bip-0174.mediawiki): RPCs to operate on Partially Signed Palladium Transactions (PSBT) are present as of **v0.17.0** ([PR 13557](https://github.com/palladium/palladium/pull/13557)).
* [`BIP 176`](https://github.com/palladium/bips/blob/master/bip-0176.mediawiki): Bits Denomination [QT only] is supported as of **v0.16.0** ([PR 12035](https://github.com/palladium/palladium/pull/12035)).
* [`BIP 340`](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki): Schnorr Signatures for secp256k1 have been implemented as of **v2.0.0**. XOnlyPubKey class and SignSchnorr/VerifySchnorr methods integrated with secp256k1 extrakeys and schnorrsig modules from Bitcoin Core v24.2.
* [`BIP 341`](https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki): Taproot: SegWit version 1 spending rules have been implemented as of **v2.0.0**. Deployment via BIP9 on mainnet (bit 2, start: March 1 2026, timeout: March 1 2027), always active on regtest for testing.
* [`BIP 341`](https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki): Taproot: SegWit version 1 spending rules have been implemented as of **v2.0.0**. Deployment via BIP9 on mainnet (bit 2, start: February 14 2026, timeout: March 1 2027), always active on regtest for testing.
* [`BIP 342`](https://github.com/bitcoin/bips/blob/master/bip-0342.mediawiki): Tapscript: SegWit version 1 script validation rules have been implemented as of **v2.0.0**, including OP_CHECKSIGADD and validation weight constraints.
* [`BIP 350`](https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki): Bech32m format for v1+ witness addresses has been implemented as of **v2.0.0**. Taproot addresses use bech32m encoding with HRP "plm" and witness version 1.

View File

@@ -81,7 +81,7 @@ blockchain through:
Taproot will activate via BIP9 miner signaling:
- **Mainnet**: BIP9 soft fork activation using bit 2
- Signaling starts: March 1, 2026 00:00:00 UTC (block time 1772323200)
- Signaling starts: February 14, 2026 00:00:00 UTC (block time 1771027200)
- Signaling timeout: March 1, 2027 00:00:00 UTC (block time 1803859200)
- Activation threshold: 1815 of 2016 blocks (90%) must signal readiness
- Status: Once locked in, Taproot activates in the next period

View File

@@ -224,7 +224,7 @@ Taproot uses Schnorr signatures instead of ECDSA:
### Mainnet Deployment
Taproot activates via miner signaling (BIP9):
- **Signaling period**: March 1, 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 method**: BIP9 soft fork using bit 2
@@ -371,7 +371,7 @@ Taproot brings important privacy and efficiency improvements to Palladium:
- **Sending and receiving** work the same as with other address types
- **Completely optional**: Your existing addresses continue to work
- **Compatible** with modern wallets after they add bech32m support
- **Activated via miner signaling**: Expected March 2026 on mainnet
- **Activated via miner signaling**: Expected February 2026 on mainnet
Enjoy the enhanced privacy and efficiency of Taproot!

View File

@@ -92,7 +92,7 @@ public:
consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nStartTime = 1199145601;
consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nTimeout = 1230767999;
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].bit = 2;
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nStartTime = 1772323200; // March 1st, 2026
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nStartTime = 1771027200; // February 14th, 2026
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nTimeout = 1803859200; // March 1st, 2027
@@ -219,7 +219,7 @@ public:
consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nStartTime = 0;
consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nTimeout = Consensus::BIP9Deployment::NO_TIMEOUT;
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].bit = 2;
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nStartTime = 1772323200;
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nStartTime = 1771027200;
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nTimeout = 1803859200;