Update: Kairos 0.4.0 and testnet reset (testnet 2)0.4.0 is a hard fork, so the testnet has restarted from a new genesis block. Nodes running 0.3.x can no longer connect; please update.
What changed- Signatures now commit to the amounts and addresses of the coins being spent.
- Soft forks activate by miner signalling (version bits). The quantum-emergency switch is the first deployment, so the network itself can now turn it on.
- Headers-first sync with block download from several peers; a node won't download a chain that carries less work.
- Fast restart from a chainstate snapshot, and optional fast sync from a UTXO snapshot checked against a proof-of-work header commitment.
- Wallet: one-time Lamport keys are recorded before signing; rewards and change go to fresh addresses.
- 78 tests, up from 55, including hostile-peer and snapshot-tampering tests.
Testnet 2Genesis: 000008fa96a695a8e30751146a123e55ee730693362e0acba2c43ce704b73c51
Seed nodes are unchanged (Frankfurt, Singapore, Miami) and built in.
To updateIf you cloned with git:
cd kairos && git pull
.venv/bin/python -m kairos --testnet node --mine
If you downloaded the ZIP, download it again from GitHub.
Existing wallets and backup codes keep working; balances start at zero on the new chain. Testnet 1 coins are gone, but they never had any value.
Changelog:
https://github.com/Nimsalcade/kairos/blob/main/CHANGELOG.mdNote: the whitepaper still describes the 0.3 block header (124 bytes); in 0.4.0 the header is 132 bytes because it also commits to the next block's base fee, and a revised whitepaper will follow.