Problem
The new seictl nodedeployment CLI (design) ships v1 with two presets: genesis-chain and rpc. A third preset, fork-genesis, is needed to spin up an ephemeral chain initialized by forking the state of an existing chain (testnet/mainnet snapshot). Primary use case: QA testing against representative production state without a long-lived testnet.
Implementation depends on the upstream sei-k8s-controller fork-genesis feature, which is currently in development. This issue tracks the seictl-side preset; the upstream feature is tracked separately in sei-protocol/sei-k8s-controller.
Impact
- Unblocks the QA harness running tests against forked production state. Current alternative — maintain a long-lived testnet — was explicitly rejected.
- Closes the loop for any consumer that wants to bisect protocol behavior across snapshots without spinning up a real testnet.
Relevant experts
kubernetes-specialist — controller-side fork-genesis API shape.product-engineer — preset taxonomy / parameter surface.
Proposed approach
- Wait for
sei-k8s-controller fork-genesis feature to land and stabilize (tracked separately upstream).
- Add
fork-genesis to seictl's embedded preset directory.
- Required parameters (TBD, pending controller API):
- source-side:
--source-chain-id or --source-snapshot — what to fork from.
- target-side:
--chain-id — target ephemeral chain ID (consistent with genesis-chain).
- Output shape unchanged from
genesis-chain — native SND with provenance annotations (seictl.sei.io/preset: fork-genesis).
Out of scope
References
Problem
The new
seictl nodedeploymentCLI (design) ships v1 with two presets:genesis-chainandrpc. A third preset,fork-genesis, is needed to spin up an ephemeral chain initialized by forking the state of an existing chain (testnet/mainnet snapshot). Primary use case: QA testing against representative production state without a long-lived testnet.Implementation depends on the upstream
sei-k8s-controllerfork-genesis feature, which is currently in development. This issue tracks the seictl-side preset; the upstream feature is tracked separately insei-protocol/sei-k8s-controller.Impact
Relevant experts
kubernetes-specialist— controller-side fork-genesis API shape.product-engineer— preset taxonomy / parameter surface.Proposed approach
sei-k8s-controllerfork-genesis feature to land and stabilize (tracked separately upstream).fork-genesisto seictl's embedded preset directory.--source-chain-idor--source-snapshot— what to fork from.--chain-id— target ephemeral chain ID (consistent withgenesis-chain).genesis-chain— native SND with provenance annotations (seictl.sei.io/preset: fork-genesis).Out of scope
sei-protocol/sei-k8s-controller.References
docs/design/nodedeployment-cli.md— v1 design; this preset is in the deferred-presets table with "controller-side fork-genesis lands and stabilizes" as the un-defer trigger.cluster/teardown that triggered the rearchitecture.