CITU protocol paper

V35 pre-activation protocol model

V35 activation is scheduled at block 514291 but is not active yet. This page describes the reviewed V35 model, not the legacy pre-V35 mining formulas.

V35 NOT ACTIVE YET ACTIVATION SCHEDULED: 514291 NO FOUNDER BURN YET

Pre-activation boundary

V35 activation is scheduled in the reviewed release build at block 514291. It remains inactive until the chain reaches that height.

Official V35 1.0.0 GitHub Releases and public SHA256 checksums are published. Verify SHA256 before running. Do not use dry-run artifacts as a production release.

V35 network schedule

Target block time200 seconds
Blocks per day432
Total reward per block8 GOLD
Miner reward6 GOLD
Jackpot reserve2 GOLD
Founder reward after V350 GOLD

Reward and jackpot model

Each V35 block allocates 8 GOLD: 6 GOLD to the miner and 2 GOLD to the jackpot reserve. The founder reward becomes 0 GOLD after V35.

The jackpot reserve is a protocol allocation. It is not a permission to create an ad hoc payout transaction during activation. Any payout must follow the reviewed protocol path and its validation rules.

Mining and chain strength

Manual difficulty controls belong to the legacy / pre-V35 workflow. They are not the V35 public mining model.

After V35, stronger-chain selection uses cumulativeWork. Operators must use the final tagged build and must not manually edit protocol constants.

Read-only V35 status endpoints

These endpoints become production-relevant only after reviewed code is deployed:

Founder burn safety

No founder burn has occurred. The official burn address has not been published. Do not send funds to unofficial burn addresses or treat the internal sink placeholder as a public destination.

Founder burn remains separate from fork activation and requires its own approved runbook and public proof.

Legacy / pre-V35 documentation

Older pages may preserve multiplier logic, hybrid points, staking points, transaction points, deterministic random ranges, and manual-difficulty calculators for historical reference. Those mechanics are legacy / pre-V35 and are not the active V35 model.

Exchanges and operators must rely on this V35 protocol paper, the final tagged artifacts, final checksums, and the final activation notice.