Flag-Day Values

This page is generated from xchain-indexer/src/protocol_changes.js and the time-keyed activation modules beside it. Do not edit it by hand: run node bin/generate-flag-days.js from the repository root and commit the result.

Every other page in this documentation set names the gate and links here instead of quoting a date, because a flag-day value is not a fact about the protocol, it is the current setting of a constant, and it has been repinned before. One generated page moves on a repin; a dozen sentences do not.

For what a flag day is, how isEnabled evaluates it, which cohort a gate belongs to, and what happens to a node that misses one, see Protocol Activation.

Contract-era flag day

The coordinated instant that the Cohort A contract-era rules switch on, simultaneously on Bitcoin, Litecoin, and Dogecoin.

5 gates do not ride it and carry a date of its own: BATCH_ISSUANCE_LIMITS at 2026-08-16 00:00:00 UTC, CONTRACT_DELEGATION_MATERIALIZE at 2026-09-15 00:00:00 UTC, DISPENSER_ORACLE_PER_TOKEN_PRICE at 2026-09-15 00:00:00 UTC, CROSS_CHAIN_ROYALTY at 2027-01-01 00:00:00 UTC, REST_PATTERN_METER at 2027-01-01 00:00:00 UTC. Each carries the reason it is armed separately in its registration comment, in the file the Declared in column names below. For how a gate is evaluated and what happens to a node that misses one, see Protocol Activation.

One gate is UNARMED on mainnet (UNCAPPED_MAX_SUPPLY_ZERO): each parks the sentinel rather than an instant, so mainnet has never run the post-activation behavior and will not until an operator names a date. They carry no row in the table below, because publishing the sentinel as a flag day would put a commitment on this page that nobody made. Each names its reason in its registration comment in protocol_changes.js. This note covers the registry only; a sibling *_activation.js module can park a mainnet sentinel too, and those are not enumerated here.

Testnet and regtest are genesis-active for the time-keyed gates: they carry threshold 0, so a testnet or regtest stack has always run the post-activation behavior. 4 gates are the exception: ISSUE_INHERITED_MINT_WINDOW arms testnet at 1787961600 (2026-08-29 00:00:00 UTC), DEPLOY_DEFERRED_ASSEMBLY arms testnet at 1788868800 (2026-09-08 12:00:00 UTC), CONTRACT_META_REQUIRED arms testnet at 1789257600 (2026-09-13 00:00:00 UTC), UNIFIED_FEES_SWEEP_CALLBACK arms testnet at 1790812800 (2026-10-01 00:00:00 UTC). The reason it cannot be genesis-active there is written in its registration comment in protocol_changes.js. The values on this page are otherwise mainnet values only.

Mainnet time-keyed gates

Thresholds keyed on a block height rather than a block time (the validator-era Cohort B rules and the per-chain Cohort C rules) are not listed here; they are inventoried on Protocol Activation.