igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

release 0.3.13: the state reset stated plainly (empty EVM state at chain block 27,276, what is gone and what re-derives), the line for the project lead

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 14:54:22 +00:00
parent 253e8d0b01
commit 44b86c46ee
1 changed files with 28 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
docs/plans/release-0.3.13.md
View file

@ -27,6 +27,25 @@ files at step 2; `exec_restart_trust_daa` 200,000 pending the coordinator's word
PROTOCOL_VERSION 15 to 16: the handshake takes the lower version, a 0.3.12 and a 0.3.13 node peer during the window.
### 1a. The devnet's one-time state reset (the coordinator's question, answered plainly)
No verified snapshot at chain block 27,276 exists. The executor starts at chain block 27,276 (DAA 45,537, the pruning point of 11:40Z) from an
EMPTY EVM state (`daemon.rs`: "Exec restart from the override file: the EVM state restarts empty at chain block {}"; 3dd9b2c9: "with
header-only records below it") and executes forward from the stored bodies; `exec_restart_hash` bb45cf0d... is that chain block's hash (where,
not a state root), and nothing is verified against a header's state root because there is no prior state to verify. Gone: every balance,
contract and nonce from before chain block 27,276 (the coinbase credits of the chain's first 45,537 DAA, the txgen harness wallets' transfers
from the relay tests, any contract state). Back, re-derived: coinbase credits from 27,276 on, every shard payout record (proving v0 began at
DAA 84,100, above the restart, so the proving ledger re-derives whole) and the fee flows after it.
| Reading | Before 11:37Z (node 1) | After the restart (the copy, 13:43Z) |
|---|---|---|
| `igneum_getProvingStatus` paidShards / paidWei | 663 / 814.64 IGN at 00:3xZ; 1,261 / 1,573 IGN at 08:30Z | 1,482 / 1,825.70 IGN (higher: it grows with the chain, nothing of it is lost) |
| PC 2's payout address | (the proving agent's before figure pending) | 267,648 IGN |
| node 1's, PC 1's payout addresses | (pending) | (pending) |
| chain block 1 to 27,275 on the explorer | bodies and state | header-only; history below 27,276 is honest only as headers |
The chain, the finality locks and the hash are untouched; the reset is of the execution layer's state, once.
## 2. The order at the go (the coordinator relays it; nothing below runs before)
Runbook: the session scratchpad's `r0313/rollout-0313.sh`. The 0.3.12 shape: publish 1 the binary with the TEN-field object (digest
@ -56,4 +75,12 @@ Runbook: the session scratchpad's `r0313/rollout-0313.sh`. The 0.3.12 shape: pub
## 4. The rollout (to fill at the go)
## 5. Owed
## 5. The one line for the project lead
When he says go: the execution layer comes back on every node at its restart (the hands and the seed by hand, the Mac, PC 2 and PC 1
through two update-nows each, the node restarting once for the switch), with the state restarted empty at chain block 27,276 (6 October
11:40Z) and re-derived forward, so every IGN earned since then by mining and proving is back on the ledger and everything before it is gone
from it, once; the chain, the finality locks and the hash are untouched; a fresh node joining the devnet no longer loses the seed every
checkpoint once the seed runs this.
## 6. Owed