Per the Quantus Insiders update: the package arrives as files (mainnet chain spec, bootnodes, genesis hash, checksum file, readme) and the node stays on 0.11.1 with --chain mainnet.json. The deploy now also takes the spec as a repo path (e.g. asset/chainspec/mainnet.json, committed after verification against the publisher's checksum) and re-verifies it against CHAINSPEC_SHA256 / the chainspec_sha256 input in fetch. The fetch job checks the repo out for that. Merging runs a no-op deploy on planck (nothing on the hosts changes, checksum gate).
Per the Quantus Insiders update: the package arrives as files (mainnet chain spec, bootnodes, genesis hash, checksum file, readme) and the node stays on 0.11.1 with `--chain mainnet.json`. The deploy now also takes the spec as a repo path (e.g. `asset/chainspec/mainnet.json`, committed after verification against the publisher's checksum) and re-verifies it against `CHAINSPEC_SHA256` / the `chainspec_sha256` input in fetch. The fetch job checks the repo out for that. Merging runs a no-op deploy on planck (nothing on the hosts changes, checksum gate).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5
The mainnet package arrives as files (spec, bootnodes, genesis, checksum
file, readme) with the node staying on 0.11.1, so the spec is committed
under asset/chainspec/ after verification and the deploy takes a repo
path as well as a URL. CHAINSPEC_SHA256 / chainspec_sha256 re-verifies the
file in fetch. The fetch job now checks the repo out.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5
grenade
merged commit f56d94400b into main2026-09-09 08:39:08 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Per the Quantus Insiders update: the package arrives as files (mainnet chain spec, bootnodes, genesis hash, checksum file, readme) and the node stays on 0.11.1 with
--chain mainnet.json. The deploy now also takes the spec as a repo path (e.g.asset/chainspec/mainnet.json, committed after verification against the publisher's checksum) and re-verifies it againstCHAINSPEC_SHA256/ thechainspec_sha256input in fetch. The fetch job checks the repo out for that. Merging runs a no-op deploy on planck (nothing on the hosts changes, checksum gate).🤖 Generated with Claude Code
https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5