doc: record the mainnet cutover as it happened #32
@@ -1,5 +1,18 @@
|
||||
# Mainnet cutover runbook
|
||||
|
||||
**Outcome, 2026-09-09.** Cut over at 09:01 UTC, eight minutes before the
|
||||
announced 09:09, by hand from roosta (`ssh` + `sudo`) because the `infra`
|
||||
runner and the metrics host (kosherinata site) were unreachable from
|
||||
08:45. Sequence as below, with the genesis assertion skipped since no hash
|
||||
had been published; bob reported genesis
|
||||
`0xfb5487c0be6ae4ade2d41d16e50465129861636c2b8d61fa94d7a19631626fba`,
|
||||
spec id `mainnet`, and that hash is now `EXPECTED_GENESIS`. Miners had
|
||||
mainnet credentials and job 1 by 09:01:49. Blocks 1–4 were imported from
|
||||
the network by 09:03:40 at difficulty ~9.7e10, so other miners were live
|
||||
before the hour. lair/quantus#31 and quantus/miner#21 commit the values;
|
||||
the node stayed on 0.11.1 (`--chain mainnet.json`, as the foundation said).
|
||||
|
||||
|
||||
Launch announced for **2026-09-09 09:09 UTC** (12:09 EEST; the plan was posted on Quantus Insiders on 2026-09-08). The foundation's
|
||||
sequence: node binary release on GitHub, genesis hash published, their
|
||||
bootnodes up, then chain spec + bootnodes + verification instructions shared,
|
||||
|
||||
Reference in New Issue
Block a user