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.
Pre-activation boundary
V35 activation is scheduled in the reviewed release build at block 514291. It remains inactive until the chain reaches that height.
Recommended node 1.0.18 / wallet 1.0.2 GitHub Releases and public SHA256 checksums are published. Website/operator guide 1.0.10 contains the current Node 1.0.18 link update. Verify SHA256 before running. Do not use dry-run artifacts as a production release.
1.0.18 and wallet/miner 1.0.2.
Website/operator guide 1.0.10 contains the current Node 1.0.18 link update. V35 activation is scheduled at block 514291;
before that block, v35Active=false is expected and normal.
1.0.18 and Wallet 1.0.2.
Node/server 1.0.18
Update node infrastructure to 1.0.18 before V35 activation block 514291. This release removes full-chain hydration from V35 public supply endpoints and serves one bounded shared snapshot, preventing concurrent public API requests from exhausting node heap. It is not a consensus change.
Node 1.0.18 adds bounded shared V35 supply computation and keeps persisted winner snapshots, live diagnostics, self-peer protection, peer/network limits, bounded temporary tournament state, safer peer synchronization, and the hard node log cap. It does not change consensus, rewards, PoW, staking, V35 constants, or block validation.
Artifact: citu-node-v35-activation-514291-1.0.18.jar
SHA256: cde4be50c32d137ebcf5b1f9e61ac1a4a6356425d06434fb8c88ebee48b27866
java -Xms512m -Xmx1536m -XX:+UseG1GC -XX:MaxGCPauseMillis=500 -XX:+ExitOnOutOfMemoryError -Dlogging.file.path=C:\server\logs -Dlogging.level.root=INFO -Dserver.tomcat.threads.max=80 -Dserver.tomcat.accept-count=100 -Dserver.tomcat.max-connections=1024 -Dserver.port=82 -Dserver.address=194.87.236.238 -Dcitu.prePersistPeerPropagation.enabled=false -Dcitu.memoryForensics.enabled=false -Dcitu.memoryForensics.file.enabled=false -Dcitu.memoryForensics.verbose=false -Dcitu.diagnostic.traces.enabled=false -Dcitu.diagnostic.file.enabled=false -Dcitu.peer.maxPeersPerCycle=3 -Dcitu.peer.maxPeersPerTournamentCycle=3 -Dcitu.peer.maxPeersPerResolveCycle=3 -Dcitu.peer.maxPeersPerPropagationCycle=3 -Dcitu.peer.maxPeersPerReadinessCycle=3 -Dcitu.peer.maxRemoteCallsPerCycle=6 -Dcitu.peer.maxRemoteCallsPerMinute=60 -Dcitu.peer.maxHealthEntries=32 -Dcitu.peer.maxErrorEntries=32 -Dcitu.peer.maxBlockedHostEntries=32 -Dcitu.memoryGuard.skipPeerWorkPercent=70 -Dcitu.memoryGuard.emergencyPeerWorkPercent=85 -Dcitu.peer.connectTimeoutMs=2000 -Dcitu.peer.readTimeoutMs=3000 -Dcitu.resolve.maxDurationMs=5000 -jar C:\citu-node-v35-activation-514291-1.0.18.jar
Wallet/miner 1.0.2
Miners should update wallet/miner to 1.0.2. The wallet shows mining submission diagnostics for block found, submit URL, status, and response.
Artifact: citu-wallet-v35-activation-514291-1.0.2.jar
SHA256: b2ea4d41925326a8b44115177db17a06ee25e6bfab0e832d7da2153313196179
java -Xms256m -Xmx1024m -XX:+UseG1GC -XX:MaxGCPauseMillis=500 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\server\logs\citu-wallet-v35-514291.hprof -Dserver.port=8082 -jar C:\citu-wallet-v35-activation-514291-1.0.2.jar
BURN_ADDRESS is an internal placeholder only; do not send funds to it.
Founder burn is deferred until after the network fully transitions to V35 and remains stable.
V35 network schedule
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:
GET /v35/protocolGET /v35/supplyGET /v35/founderGET /v35/founder/burn-snapshotGET /v35/burnGET /v35/jackpot/status
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.