Activation Status

This page is the canonical source for whether a Tidecoin consensus feature is Live on mainnet, Built but not yet activated, or Planned. Individual protocol pages reference this status; live network statistics (block height, peers, hashrate) belong on the main website /status page.

This page is not a tutorial and does not define the rules by itself. For rule-level detail, use Consensus Rules, AuxPoW, Proof-of-Work, and the signature scheme pages.

Consensus activation heights

Tidecoin’s current consensus gates are height based. The controlling parameter is consensus.nAuxpowStartHeight in src/kernel/chainparams.cpp.

Network	AuxPoW start height	Meaning
Mainnet	Disabled	Mainnet remains in the pre-AuxPoW consensus phase.
Testnet	1000	Testnet uses post-AuxPoW rules from block 1000 onward.
Regtest	0	Regtest starts directly in the post-AuxPoW ruleset.

Mainnet feature status

Feature	Mainnet status	Activation rule
Falcon-512 signatures	Live	Allowed before and after AuxPoW.
YespowerTIDE proof-of-work	Live	Used while AuxPoW is disabled.
AuxPoW merged mining	Built, not active	Mainnet `nAuxpowStartHeight` is disabled.
Scrypt proof-of-work	Built, not active	Used only at and after AuxPoW activation height.
Falcon-1024 signatures	Built, not active	Allowed only at and after AuxPoW activation height.
ML-DSA-44/65/87 signatures	Built, not active	Allowed only at and after AuxPoW activation height.
Strict PQ signature validation	Built, not active	`SCRIPT_VERIFY_PQ_STRICT` is added only at and after AuxPoW activation height.
OP_SHA512	Built, not active	`SCRIPT_VERIFY_SHA512` is added only at and after AuxPoW activation height.
Witness v1 / P2WSH-512	Built, not active	`SCRIPT_VERIFY_WITNESS_V1_512` is added only at and after AuxPoW activation height.

Testnet and regtest feature status

Feature	Testnet	Regtest
Falcon-512 signatures	Live before and after block 1000	Live from genesis
YespowerTIDE proof-of-work	Live before block 1000	Not the active default phase
AuxPoW merged mining	Active from block 1000	Active from genesis
Scrypt proof-of-work	Active from block 1000	Active from genesis
Falcon-1024 signatures	Active from block 1000	Active from genesis
ML-DSA-44/65/87 signatures	Active from block 1000	Active from genesis
Strict PQ signature validation	Active from block 1000	Active from genesis
OP_SHA512	Active from block 1000	Active from genesis
Witness v1 / P2WSH-512	Active from block 1000	Active from genesis

Implemented non-consensus features

These features are implemented in the node or wallet, but they should not be read as mainnet consensus activation statements.

Feature	Status	Scope
PQHD wallet derivation	Implemented	Wallet derivation, wallet policy, seed management, descriptors, and PSBT metadata.
ML-KEM-512 V2 transport	Implemented	Peer-to-peer transport encryption; enabled by the node’s v2 transport configuration.
PQHD wallet RPCs	Implemented	`setpqhdpolicy`, seed import/list/select/remove RPCs.
AuxPoW RPCs	Implemented	`createauxblock` and `submitauxblock`; usable only where AuxPoW is active or scheduled.

Source of truth

The activation state above is derived from these source files in the node repository:

Source	What it defines
`src/kernel/chainparams.cpp`	Network-specific AuxPoW activation heights, ports, genesis, magic bytes, and chain IDs.
`src/pq/pq_scheme.h`	Signature scheme IDs and the rule that only Falcon-512 is allowed before AuxPoW.
`src/script/interpreter.h`	Script verification flags for PQ strict mode, witness v1 / P2WSH-512, and OP_SHA512.
`src/validation.cpp`	The validation path that adds post-AuxPoW script verification flags at activation height.
`src/pow.cpp`	The switch from pre-AuxPoW proof-of-work to scrypt proof-of-work at activation height.