Skip to content

feat(tee-cli)!: authored network inputs under inputs/ - #81

Merged
samlaf merged 1 commit into
mainfrom
network-dir-inputs-layout
Jul 30, 2026
Merged

feat(tee-cli)!: authored network inputs under inputs/#81
samlaf merged 1 commit into
mainfrom
network-dir-inputs-layout

Conversation

@samlaf

@samlaf samlaf commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

A network directory now holds its three authored inputs under inputs/ (reth-genesis.json, summit-genesis-template.toml, measurements.json); manifest assemble derives the artifact set at the top level. Everything top-level is hash-pinned by network-manifest.json; everything under inputs/ is provenance. An input sharing its artifact's basename is the same format with derived fields filled at assemble time (registry storage into the genesis, eth_genesis_hash into the template); the raw measurements become measurement-policy.json because promotion is a format transformation.

The same-name in-place reth-genesis.json write and the INPUT_* filename special-casing are gone — authored inputs and shipped artifacts can no longer collide structurally. assemble fails closed with a pointer to inputs/ when the authored inputs are missing.

example-devnet is re-laid-out and re-assembled (--force, fresh network_id): its input genesis is refreshed from reth's committed dev.json — the old copy carried a stale registry runtime and a removed 0x…0003 predeploy — and the artifact set passes assemble + validate end-to-end with the real admission CLI and seismic-reth.

tee/networks/README.md now leads with a rendered diagram (network-dir.excalidraw + network-dir.png) of how assemble derives the artifact set, which manifest field pins which artifact, and where the genesis ceremony picks up the committed template. Remaining "chain spec" prose is reworded to "genesis" across CLI help strings and docstrings.

BREAKING: assemble --dir reads the authored inputs from inputs/; a directory laid out the old way fails with a pointer — move them in (summit-template.toml becomes inputs/summit-genesis-template.toml).

…p level

A network directory now holds its three authored inputs under inputs/
(reth-genesis.json, summit-genesis-template.toml, measurements.json);
`manifest assemble` derives the artifact set at the top level. Everything
top-level is hash-pinned by network-manifest.json; everything under
inputs/ is provenance. An input sharing its artifact's basename is the
same format with derived fields filled at assemble time (registry
storage into the genesis, eth_genesis_hash into the template); the raw
measurements become measurement-policy.json because promotion is a
format transformation.

The same-name in-place reth-genesis.json write and the INPUT_* filename
special-casing are gone — authored inputs and shipped artifacts can no
longer collide structurally. assemble fails closed with a pointer to
inputs/ when the authored inputs are missing.

example-devnet is re-laid-out and re-assembled (--force, fresh
network_id): its input genesis is refreshed from reth's committed
dev.json — the old copy carried a stale registry runtime and a removed
0x…0003 predeploy — and the artifact set passes assemble + validate
end-to-end with the real admission CLI and seismic-reth.

tee/networks/README.md now leads with a rendered diagram
(network-dir.excalidraw + network-dir.png) of how assemble derives the
artifact set, which manifest field pins which artifact, and where the
genesis ceremony picks up the committed template. Remaining "chain spec"
prose is reworded to "genesis" across CLI help strings and docstrings.

BREAKING: `assemble --dir` reads the authored inputs from inputs/; a
directory laid out the old way fails with a pointer — move them in
(summit-template.toml becomes inputs/summit-genesis-template.toml).
@samlaf
samlaf merged commit 0fb616c into main Jul 30, 2026
1 check passed
@samlaf
samlaf deleted the network-dir-inputs-layout branch July 30, 2026 17:57
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