quantus/asset/chainspec/README.md at main - quantus - Gitea: Git with a cup of tea

lair/quantus

Files

T

Rob ThijssenandClaude Fable 5.1 f515c8057b

deploy: chain spec from a repo path, with a sha256 check

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

2026-09-09 11:38:44 +03:00

6 lines

367 B

Markdown

Raw Permalink Blame History

 Chain spec files the node deploy can run from (`CHAINSPEC_URL` / the
 `chainspec_url` input as a repo path, e.g. `asset/chainspec/mainnet.json`).
 Commit only a file verified against the publisher's checksum, and record that
 checksum in `CHAINSPEC_SHA256` so the deploy re-verifies it; the started node's
 genesis hash is asserted separately against `EXPECTED_GENESIS`.