ZKrise is the largest upgrade in ZKas history. At one block the developer fee is gone for good — miners keep 100% of every reward — and the network's deepest security hardening goes live in the same activation.
No privacy, supply or transaction changes. Funds never move and no wallet re-syncs. Nodes, pools and wallets must run the release before the block above.
Since genesis, 5% of every block's subsidy funded development. From block 6,983,500 that cut drops to zero — the miner keeps the whole reward, and no dev output ever appears again.
Total issuance is unchanged — the 5% simply stays with miners. The carried dev balance is paid out exactly once, by the first block past activation, then never again.
Every change came out of adversarial code audits of the live network, re-checked in code, tested as a property, and rehearsed across the fork on live test networks.
The 5% developer cut stops at block 6,983,500. From there the miner keeps 100% of the subsidy, enforced by consensus — not a promise.
Full freedomA shielded spend now commits to the exact block its proof anchors to. The same spend can no longer replay on both sides of a chain split.
No replayThe recent-anchor window is committed to proof of work, so a freshly synced node proves its imported state against PoW instead of trusting the peer that served it.
Verify, don't trustMerged mining is bound so a single Kaspa solution backs exactly one ZKas block. The double-credit weakness — one solution, two blocks — is closed.
Double-credit killedInstead of minting a note per block, a miner's rewards accrue into one slot. In rehearsal: ~1 reward note per 100 blocks instead of 100 — far less for every wallet to scan.
~100× lighterThe proving stack moves up with a byte-identical circuit, parameters and verifying key. The node refuses to start on a different verifier — a divergent build can't join silently.
Same verifierNode, wallet and pool hardening that needs no activation: bad proofs disconnect peers, synced state is bound before use, forked wallet trees self-heal, and RPC panics became errors.
Live nowEvery fork-class change that was ready ships in a single activation, so operators upgrade one time instead of chasing a string of forks.
One forkBlocks built by the old rules stop being valid after activation. Upgrading is safe — nothing is lost, spends are refused not destroyed, and funds never move.
Install the ZKrise release before the block. An un-upgraded node fails closed — it stops at the first post-fork block and stays up, then re-syncs after you update.
Required before 6,983,500Rebuild the merge-mining bridge from the release. After the block, parents must use the new bound ZKM1 commitment; the legacy form is rejected.
Update the app, desktop, web or SDK. An older wallet's spends are refused after the block — refused, not lost. The update fixes it instantly.
Required before 6,983,500