What happened
On 31 August 2026 the EmpoorioChain public testnet was launched from a new genesis:
0xe973931eb0041952249c6a5f6d66537ced5acfe7e1334c44b531ddbbffeae7aa
Earlier chains — including one launched on 25 August with genesis 0x6b325e39… — were retired. Any node still following one of them is on a dead chain and will see Genesis mismatch from the live bootnodes.
Why relaunch instead of upgrade
Because until 4 September the chain had never been upgraded in place. Every runtime change had shipped by regenerating the genesis and starting over. The 31 August chain was launched at spec 207 with the intention of being the last such restart — and it was: runtime 208 was applied to it in place on 4 September, the first real upgrade in the network's history, and every runtime since (211, 213, 215, 217, 218, 219, 220) has been applied to the same genesis.
What a relaunch costs
Everything on chain: balances, DIDs, staking history, the transaction record. For a testnet whose tokens have no value that is acceptable once. For a network aspiring to a mainnet it is exactly what the upgrade policy exists to make unnecessary — the history of blocks and confirmed balances is never rewritten. The 31 August genesis is meant to be the testnet's last.
What was carried over
Nothing on chain. Off chain: the validator accounts (the same two), the RPC hosts, the documentation — and the lesson that a chain relaunched three times in a fortnight cannot be integrated against. The relaunch was accompanied by the creation of RED.json, so that the genesis hash, spec version and hosts would have one authoritative source from that day on.
If you were on the old genesis
- Stop the node.
- Delete its database (
--base-pathcontents), keep its network key if you want the same peer id. - Use the repository's
chainspec.raw.json— do not runbuild-spec. - Start and confirm
header-hash: 0xe973…e7aaand(2 peers)within seconds.
Older documents quoting a different genesis are stale; RED.json and scripts/verificar_red.py are the check.
Testnet allocation
The relaunch distributed 1,000,000,000 DMS equally among the funded development and validator accounts as a test fixture. That is not the mainnet allocation, which is a separate chain spec with founder, AI, treasury, liquidity and public-sale lines. Test DMS resets on major upgrades with 72 hours' notice.
Since
Fifteen days after the relaunch the chain had its first signed transaction (7 September), first accepted EVM transaction (runtime 211), first storage migration (213), first swap and first DID (14 September). All on one genesis. That is the point of the relaunch: to be the last one.
Based on RED.json, chainspecs/testnet/LEEME_CHAINSPEC.md and the runtime upgrade records.