deploy: chain id as a dispatch input for the miner credential path #19

Merged
grenade merged 1 commits from deploy/chain-input into main 2026-09-09 05:05:38 +00:00

1 Commits

Author SHA1 Message Date
9f41e0f3b9 deploy: chain id as a dispatch input for the miner credential path
All checks were successful
ci / fmt (pull_request) Successful in 46s
ci / clippy (pull_request) Successful in 2m56s
ci / test (pull_request) Successful in 6m49s
ci / doc (pull_request) Successful in 2m18s
The node generates the miner auth token and TLS pin per chain under
<base-path>/chains/<id>/, so the mainnet cutover needs one miner deploy
pointed at the new id (lair/quantus's node deploy prints it). The binary
is unchanged by a chain switch; only the credentials trigger the restart.
CHAIN stays the push-time default and is to be bumped after the cutover.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5
2026-09-09 08:05:04 +03:00