feat: genesis ceremony controller orchestration#25
Draft
Conversation
Add group-level genesis ceremony support to SeiNodeGroup and per-node genesis configuration to SeiNode/ValidatorSpec. The node controller builds the full Init plan upfront (no deferred steps) and the group controller coordinates assembly, peer collection, and static peer injection. New CRD types: GenesisCeremonyConfig, GenesisCeremonyNodeConfig, GenesisS3Destination, GenesisS3Source. New group status fields: AssemblyPlan, GenesisHash, GenesisS3URI. Depends on seictl genesis ceremony client types (sei-protocol/seictl#40).
- Fix gofmt alignment in SeiNodeGroupPhase and genesis constants
- Fix goimports grouping (seictl is external, not local)
- Replace interface{} with any (modernize)
- Remove deprecated result.Requeue usage
- Suppress unused params in pollAssemblyTask stub (PR-3)
5047c1f to
a342413
Compare
- Remove GroupPhaseGenesisCeremony — genesis work runs during the existing Initializing phase, keyed off spec.genesis != nil - Rename AssemblyPlan to InitPlan for consistency with node-level naming and to avoid scoping the field to assembly-only workloads - Move design docs from tide/ to .tide/, remove tide/ and docs/
Remove the genesis-specific PreInit Job (sleep infinity + copy-seid), handleGenesisPreInitComplete, and all isGenesisCeremonyNode branches in pre_init.go and job.go. Genesis nodes now skip PreInit entirely. The full genesis InitPlan includes: generate-identity, generate-gentx, upload-genesis-artifacts, await-genesis-assembly (barrier), then the standard configure-genesis, config-apply, discover-peers, config-validate, mark-ready sequence. WIP: executePlan still uses the old submit/poll model. Next step is the TaskExecutionInterface refactor to support the await barrier natively.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SeiNodeGroup(GenesisCeremonyConfig,GenesisS3Destination) and per-node genesis config toValidatorSpec(GenesisCeremonyNodeConfig)New CRD types
GenesisCeremonyConfigSeiNodeGroupSpec.GenesisGenesisCeremonyNodeConfigValidatorSpec.GenesisCeremonyGenesisS3DestinationGenesisCeremonyConfig.GenesisS3Dependencies
/v0/node-idendpoint)sei-genesis-artifacts(PR 0, not yet created)Test plan
make generateproduces correct deepcopy methods for new typesmake testpasses (existing unit tests)copy-seidinit container,seictl serverestartable init,sleep infinitymaingenerateSeiNodeinjectsGenesisCeremonyandspec.Genesis.S3when group genesis is enabled