Skip to content

docs: document deploy-config.json and verify all four derived files - #1

Open
memifonchain wants to merge 1 commit into
mainfrom
docs/deploy-config-and-verification
Open

docs: document deploy-config.json and verify all four derived files#1
memifonchain wants to merge 1 commit into
mainfrom
docs/deploy-config-and-verification

Conversation

@memifonchain

Copy link
Copy Markdown
Collaborator

deploy-config.json was committed in 6a8e93e but the README still said the deploy config is not stored as a separate file, listed no row for it in the Files table, and diffed only two of the four artefacts the verification recipe regenerates.

  • add a Files table row for deploy-config.json
  • replace the stale note with what actually holds: only genesis.json and rollup.json are read by a node, and all four derived files come back deterministically from state.json
  • diff deploy-config.json and l1-addresses.json as well, so every file the recipe regenerates is also compared
  • go back to shasum -a 256 testnet/*, so the output is byte-identical to the expected block printed under it

deploy-config.json was committed in 6a8e93e but the README still said the
deploy config is not stored as a separate file, listed no row for it in the
Files table, and diffed only two of the four artefacts the verification
recipe regenerates.

- add a Files table row for deploy-config.json
- replace the stale note with what actually holds: only genesis.json and
  rollup.json are read by a node, and all four derived files come back
  deterministically from state.json
- diff deploy-config.json and l1-addresses.json as well, so every file the
  recipe regenerates is also compared
- go back to `shasum -a 256 testnet/*`, so the output is byte-identical to
  the expected block printed under it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant