deploy: run the node from a chain spec file with genesis assertion, bootnodes as reserved peers, raised peer limits
Mainnet launches 2026-09-10 09:09 UTC with the chain spec published as a file before any binary embeds it. The node deploy can now run from /etc/quantus-node/chainspec.json (CHAINSPEC_URL or the chainspec_url input), asserts the started node's block-0 hash against EXPECTED_GENESIS (required with a spec: it is the only defence against a look-alike), and prints the spec id, which names <base-path>/chains/<id>/ and is what the miner deploy must be pointed at; validate checks the miner credentials exist under it. BOOTNODES are dialled and held as reserved peers. The unit raises --out-peers to 32 and --in-peers to 64: bob sits at the default cap of 40 peers today, and launch is a propagation race (quantus/chain#1). infra-setup grants the runner the chain spec path (applied to bob 2026-09-09). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
f3c026623e
commit
6276a0bf98
@@ -162,6 +162,7 @@ gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /usr/local/bin/quantus-node
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/systemd/system/quantus-node.service
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/sysusers.d/quantus-node.conf
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/quantus-node/node.env
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/quantus-node/chainspec.json
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/firewalld/services/quantus-node.xml
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/firewalld/services/quantus-node-miner.xml
|
||||
gitea_ci ALL=(root) NOPASSWD: /usr/bin/rsync * /etc/firewalld/services/quantus-node-metrics.xml
|
||||
|
||||
Reference in New Issue
Block a user