Skip to content

docs(cluster): note stale-output + contracts-ref pitfalls in genesis flow#757

Open
Richard1048576 wants to merge 1 commit into
mainfrom
docs/cluster-readme-genesis-gotchas
Open

docs(cluster): note stale-output + contracts-ref pitfalls in genesis flow#757
Richard1048576 wants to merge 1 commit into
mainfrom
docs/cluster-readme-genesis-gotchas

Conversation

@Richard1048576

Copy link
Copy Markdown
Contributor

Two gotchas hit when standing up a fresh local devnet from cluster/, both surfacing the same way — every node fails to bootstrap and sits at block 0 with The genesis transaction was not found / chain ID (None). Documents both in cluster/README.md so the next operator doesn't have to reverse-engineer them.

1. Reusing a stale ./output/

If ./output/ holds artifacts from a previous (or partial) run, make deploy_start alone happily distributes an incomplete genesis (no consensus genesis transaction), and nodes can't bootstrap. The fix is to always regenerate from scratch:

make clean && make init && make genesis

2. gravity_chain_core_contracts out of sync with the SDK

The existing note already says the contracts repo isn't auto-updated. Added that a stale ref in genesis.toml (vs the SDK's genesis-tool) makes generation fail with e.g. missing field minimumProposalStake — so keep the contracts checkout in sync.

Both notes go in the make genesis section next to the existing contracts-update warning. Docs only.

…flow

Two gotchas when standing up a fresh local devnet, both surfacing as nodes stuck
at block 0 with "The genesis transaction was not found":
- reusing a stale/partial ./output/ from a previous run. Always
  `make clean && make init && make genesis` for a fresh chain.
- a gravity_chain_core_contracts checkout out of sync with the SDK, so genesis-tool
  rejects the generated config (e.g. missing field `minimumProposalStake`). Keep
  the contracts ref in sync.
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.

2 participants