feat(gnoland): chain hardfork mechanism by moul · Pull Request #5411 · gnolang/gno

moul · 2026-04-01T15:24:28Z

Edit: see also #5511

Summary

Adds support for replaying historical transactions during genesis for chain hard forks (gnoland1 → gnoland-1).

Key changes

GnoGenesisState.OriginalChainID: specifies the chain ID used for verifying signatures of historical txs during genesis replay
GnoGenesisState.InitialHeight: block height the chain should start from after genesis
GnoTxMetadata.BlockHeight: original block height where the tx executed
GenesisDoc.InitialHeight (tm2): when > 1, the consensus Handshaker sets state.LastBlockHeight = InitialHeight - 1 after InitChain so the first produced block has the correct height
Genesis replay with chain ID override: when metadata.BlockHeight > 0 and OriginalChainID is set, the context chain ID is overridden so signature verification uses the original chain ID

How it works

Genesis txs WITHOUT metadata (or BlockHeight=0) → current genesis mode (package deploys, infinite gas, auto-account creation)
Genesis txs WITH metadata.BlockHeight > 0 → normal mode: the ante handler sees non-zero height, uses actual account numbers/sequences from store, and verifies signatures against OriginalChainID
Accounts must be seeded via genesis balances before historical txs replay
After all txs replay, the chain starts at InitialHeight (via GenesisDoc.InitialHeight → consensus Handshaker → state.LastBlockHeight)

Migration script

misc/deployments/gnoland-1/generate-genesis.sh — generates gnoland-1 genesis from a running gnoland1 node using tx-archive.

Related PRs

feat(node): add halt_height config field for coordinated chain upgrades #5334 — --halt-height CLI flag
feat(node): add GovDAO-based chain halt via r/sys/params #5368 — GovDAO-based halt height
WIP feat(deployments): gnoland-1.x hardfork content #5376 — gnoland-1 chain config
feat(gnoland): in-place block-replay migration (--migrate flag) #5377 — in-place block-replay migration
feat(gnoland): add block_height and chain_id to GnoTxMetadata #5390 — extended tx metadata (superseded by this PR)
feat: add block_height/chain_id to backup + genesis-assemble cmd tx-archive#70 — genesis-assemble command (companion)

Open items

End-to-end test with actual signature verification across chain ID switch
Account number preservation from old chain (currently auto-assigned during balance init; mitigated by preserving auth genesis state from old chain)
Integration with tx-archive genesis-assemble command

AI-assisted: code generated with Claude Code

…in ID

Gno2D2 · 2026-04-01T15:25:20Z

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

IGNORE the bot requirements for this PR (force green CI check)
Determine if infra needs to be updated before merging

✅ Automated Checks (for Contributors):

No automated checks match this pull request.

☑️ Contributor Actions:

Fix any issues flagged by automated checks.
Follow the Contributor Checklist to ensure your PR is ready for review.
- Add new tests, or document why they are unnecessary.
- Provide clear examples/screenshots, if necessary.
- Update documentation, if required.
- Ensure no breaking changes, or include BREAKING CHANGE notes.
- Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

Debug

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If
🟢 Condition met
└── 🟢 On every pull request
Can be checked by

Any user with comment edit permission

Determine if infra needs to be updated before merging

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Or
        ├── 🔴 A changed file matches this pattern: Dockerfile
        ├── 🟢 A changed file matches this pattern: ^misc/deployments (filename: misc/deployments/gnoland-1/.gitignore)
        ├── 🔴 A changed file matches this pattern: ^misc/docker-
        └── 🔴 A changed file matches this pattern: ^.github/workflows/release.*\.yml$

Can be checked by

team devops

codecov · 2026-04-01T15:28:03Z

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@tbruyelle

…es (#5334) ## Summary Adds a halt height mechanism for coordinated chain upgrades. The node stops after committing the specified block height. ### How to set it ```bash gnoland config set halt_height 352922 ``` Or edit `config.toml` directly: ```toml halt_height = 352922 ``` ### How it works 1. After `finalizeCommit`, consensus checks if `height >= halt_height` 2. If so, calls `osm.Kill()` for a graceful shutdown 3. The check is at the consensus level (not ABCI), following the same pattern as `WithEarlyStart` ### Scope and future direction This is a **temporary coordination tool** for the current chain upgrade. For the gnoland1 → gnoland-1 hard fork, validators set `halt_height` in their config, all nodes stop at the same block, then validators swap binary + config and restart. After the upgrade, the proper mechanism will be **GovDAO-based halting** (#5368), which adds: - On-chain `halt_height` param set via governance proposal (no manual config needed) - `halt_min_version` — prevents old binaries from restarting after halt - Version guard at startup so validators can't accidentally run the wrong binary Once #5368 is merged and active, `halt_height` in config becomes a **node operator tool** (e.g., "stop my node at height X for maintenance") rather than a coordination mechanism. Coordination should happen through governance. ### No CLI flag — config only Per @tbruyelle's suggestion, there's no `--halt-height` CLI flag. Config file is the single source of truth. This avoids the risk of validators missing the flag in duplicated command setups across their infrastructure. ### Related - #5368 — GovDAO-based halt height + version guard (Phase 2, replaces this for coordination) - #5376 — gnoland-1 chain config - #5411 — chain upgrade genesis replay <details> <summary>Contributors' checklist</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added `benchmarks` label to the PR or not needed </details>

@tbruyelle

…es (#5334) ## Summary Adds a halt height mechanism for coordinated chain upgrades. The node stops after committing the specified block height. ### How to set it ```bash gnoland config set halt_height 352922 ``` Or edit `config.toml` directly: ```toml halt_height = 352922 ``` ### How it works 1. After `finalizeCommit`, consensus checks if `height >= halt_height` 2. If so, calls `osm.Kill()` for a graceful shutdown 3. The check is at the consensus level (not ABCI), following the same pattern as `WithEarlyStart` ### Scope and future direction This is a **temporary coordination tool** for the current chain upgrade. For the gnoland1 → gnoland-1 hard fork, validators set `halt_height` in their config, all nodes stop at the same block, then validators swap binary + config and restart. After the upgrade, the proper mechanism will be **GovDAO-based halting** (#5368), which adds: - On-chain `halt_height` param set via governance proposal (no manual config needed) - `halt_min_version` — prevents old binaries from restarting after halt - Version guard at startup so validators can't accidentally run the wrong binary Once #5368 is merged and active, `halt_height` in config becomes a **node operator tool** (e.g., "stop my node at height X for maintenance") rather than a coordination mechanism. Coordination should happen through governance. ### No CLI flag — config only Per @tbruyelle's suggestion, there's no `--halt-height` CLI flag. Config file is the single source of truth. This avoids the risk of validators missing the flag in duplicated command setups across their infrastructure. ### Related - #5368 — GovDAO-based halt height + version guard (Phase 2, replaces this for coordination) - #5376 — gnoland-1 chain config - #5411 — chain upgrade genesis replay <details> <summary>Contributors' checklist</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added `benchmarks` label to the PR or not needed </details>

@tbruyelle

…es (#5334) ## Summary Adds a halt height mechanism for coordinated chain upgrades. The node stops after committing the specified block height. ### How to set it ```bash gnoland config set halt_height 352922 ``` Or edit `config.toml` directly: ```toml halt_height = 352922 ``` ### How it works 1. After `finalizeCommit`, consensus checks if `height >= halt_height` 2. If so, calls `osm.Kill()` for a graceful shutdown 3. The check is at the consensus level (not ABCI), following the same pattern as `WithEarlyStart` ### Scope and future direction This is a **temporary coordination tool** for the current chain upgrade. For the gnoland1 → gnoland-1 hard fork, validators set `halt_height` in their config, all nodes stop at the same block, then validators swap binary + config and restart. After the upgrade, the proper mechanism will be **GovDAO-based halting** (#5368), which adds: - On-chain `halt_height` param set via governance proposal (no manual config needed) - `halt_min_version` — prevents old binaries from restarting after halt - Version guard at startup so validators can't accidentally run the wrong binary Once #5368 is merged and active, `halt_height` in config becomes a **node operator tool** (e.g., "stop my node at height X for maintenance") rather than a coordination mechanism. Coordination should happen through governance. ### No CLI flag — config only Per @tbruyelle's suggestion, there's no `--halt-height` CLI flag. Config file is the single source of truth. This avoids the risk of validators missing the flag in duplicated command setups across their infrastructure. ### Related - #5368 — GovDAO-based halt height + version guard (Phase 2, replaces this for coordination) - #5376 — gnoland-1 chain config - #5411 — chain upgrade genesis replay <details> <summary>Contributors' checklist</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added `benchmarks` label to the PR or not needed </details>

- Revert premature doc references to gnoland-1 chain ID in gas-fees.md and explore-with-gnoweb.md (hardfork hasn't happened yet) - Remove premature "Note" callout from gnoland-networks.md - Update migrate-from-gnoland1.sh: reflect Scenario A decision (genesis tx-replay with InitialHeight), document blockers (#5411, #5390, Jae's InitialHeight tm2 work), reference issue #5374 for tracking - Update gnoland-1/README.md: reflect correct PR merge status, document Scenario A approach, list migration blockers explicitly

- Add ChainID field to GnoTxMetadata for tx provenance recording - Add InitialHeight validation (non-negative) to GenesisDoc.Validate and ValidateAndComplete - Add test cases: no chain ID override when BlockHeight=0, no override when OriginalChainID unset - Update ADR: document per-tx vs state-level design choice, mark InitialHeight as implemented end-to-end

…lay and ValidateAndComplete

…is.sh misc/hardfork/ — new Go binary with three source modes: - RPC: iterates blocks from a live/halted node, extracts txs with metadata - local dir: reads genesis.json + txs.jsonl from a stopped node data dir - genesis file: single .json source (no tx history) Produces a hardfork genesis with: - chain_id updated to new chain - initial_height set to halt_height + 1 (both at GenesisDoc level and app_state) - original_chain_id set for historical tx signature verification - historical txs appended with BlockHeight/Timestamp/ChainID metadata misc/deployments/gnoland-1/generate-genesis.sh is now a thin wrapper around hardfork genesis with gnoland-1 specific defaults (chain IDs, overlay directory).

…o worktree-hf-framework-5411

…ay smoke-test Adds a new 'hardfork test' subcommand that loads a hardfork genesis.json into an in-memory gnoland node and replays all transactions in-process. Key behaviors: - Generates a fresh single-validator identity (replaces genesis validators) so the node can produce blocks without requiring real validator keys - SkipGenesisSigVerification enabled for genesis-mode txs - Historical txs (block_height > 0) go through the normal ante handler using original_chain_id from genesis for signature verification - Progress reporting every 30s for long replays - --verbose flag logs each tx result - --keep-running flag keeps the node alive for manual RPC inspection - Exit code 0 on success, non-zero on failure Also adds: - Unit tests covering error paths and a full empty-genesis replay - Makefile 'preview-and-test' target for quick local smoke tests - Updated 'hardfork genesis' next-steps to reference 'hardfork test'

Adds misc/hf-glue/: a throwaway testbed that chains the tools from gnolang#5411 and gnolang#5376 to run a local, single-validator hardforked chain in docker, with state persisted on disk. Flow: make fetch # hardfork genesis --source rpc.gno.land -> out/genesis.json make init # gnoland secrets init + rewrite validator set to our key make up # docker compose up: single-validator gnoland node, RPC :26657 This exists only to find gaps in gnolang#5411/gnolang#5376 end-to-end. Do NOT merge. Fixes go back upstream.

…t fixes Workarounds real gnolang#5411 bug: gnoland RPC /genesis endpoint 502s on gnoland1-scale genesis (~80MB, server closes stream mid-transfer) and /genesis_chunked is not implemented. Until that's fixed upstream, rebuild the base genesis locally via misc/deployments/gnoland1/gen-genesis.sh and feed the file to 'hardfork genesis --source <file>'. Also fixes two init-node.sh bugs: - gnoland secrets init --data-dir expects the secrets dir directly, not the node home dir - fixvalidator needs gno.land/pkg/gnoland blank-imported for the GnoGenesisState amino registration

Adds misc/hf-glue/: a throwaway testbed that chains the tools from gnolang#5411 and gnolang#5376 to run a local, single-validator hardforked chain in docker, with state persisted on disk. Flow: make fetch # hardfork genesis --source rpc.gno.land -> out/genesis.json make init # gnoland secrets init + rewrite validator set to our key make up # docker compose up: single-validator gnoland node, RPC :26657 This exists only to find gaps in gnolang#5411/gnolang#5376 end-to-end. Do NOT merge. Fixes go back upstream.

…t fixes Workarounds real gnolang#5411 bug: gnoland RPC /genesis endpoint 502s on gnoland1-scale genesis (~80MB, server closes stream mid-transfer) and /genesis_chunked is not implemented. Until that's fixed upstream, rebuild the base genesis locally via misc/deployments/gnoland1/gen-genesis.sh and feed the file to 'hardfork genesis --source <file>'. Also fixes two init-node.sh bugs: - gnoland secrets init --data-dir expects the secrets dir directly, not the node home dir - fixvalidator needs gno.land/pkg/gnoland blank-imported for the GnoGenesisState amino registration

## Overview Chain hardfork mechanism for gno.land: export all state and historical transactions from the source chain, replay them during `InitChain` on the new chain, and start producing blocks at the halted height. Replaces the original single-`OriginalChainID` design from [#5411](#5411) with a more flexible multi-chain model (`PastChainIDs` allowlist + per-tx `ChainID`). **History:** - Original work: [#5411](#5411) - Jae's refinements: [feat/genesis-replay-upgrade2](https://github.com/gnolang/gno/tree/feat/genesis-replay-upgrade2) - This PR: builds on top of Jae's work, adds fixes from extensive review + end-to-end validation on the full gnoland1 chain via the [hf-glue testbed](#5486) ## What's in ### tm2 (consensus + SDK) - **`GenesisDoc.InitialHeight`** consensus starts block production at this height after `InitChain`; `Handshaker` sets `state.LastBlockHeight = InitialHeight - 1`. - **`BlockchainReactor`, `state`, `store`, validation** all updated to handle chains where `InitialHeight > 1` (empty block store, non-contiguous block save, validator set / consensus params persisted at InitialHeight, etc.) - **`BaseApp.lastBlockHeight` tracker** (this iteration): real chain height = `multistoreVersion + initialHeightOffset`, with the offset persisted under `mainInitialHeightKey` and restored on every restart. `validateHeight` now enforces strict contiguity against real chain height; the previous "allow monotonic jump" branch (which permanently bypassed contiguity for `InitialHeight > 1` chains) is gone. - **`BaseApp.Info` guard** handle calls before the multistore is loaded. - **`auth.SkipGasMeteringKey`** context flag that lets `SetGasMeter` bypass the new VM's gas meter (used for `GasReplayMode="source"`). - **`RequestInitChain.InitialHeight`** new ABCI field so the app can cross-check against `GnoGenesisState.InitialHeight`. Amino round-trip test added. ### gno.land - **`GnoGenesisState`** extensions: - `PastChainIDs []string` allowlist of past chain IDs valid for signature verification - `InitialHeight int64` cross-checked against `GenesisDoc.InitialHeight` - `GasReplayMode string` `""`/`"strict"` (default, new VM's gas meter) or `"source"` (bypass gas meter, preserve source-chain outcomes) - **`GnoTxMetadata`** extensions: - `BlockHeight int64` original block height - `ChainID string` originating chain ID - `Failed bool` tx had non-zero return code on source chain (skipped during replay) - `SignerInfo []SignerAccountInfo` per-signer account metadata (address, account number, pre-tx sequence) so signatures verify correctly even if earlier txs diverged - `GasUsed`, `GasWanted int64` source-chain gas (populated by tx-archive, used by replay report) - **`auth.NewAccountWithUncheckedNumber`** (this iteration, renamed from `NewAccountWithNumber`): create accounts with a specific number, bypassing the auto-increment counter. Doc comment now spells out the precondition that the caller must enforce uniqueness; the rename forces every call site to acknowledge it. - **`validateSignerInfo` preflight** (this iteration): scans every `SignerInfo` entry across all txs at the start of `loadAppState`. Rejects the genesis if two different addresses claim the same account number, or if a `SignerInfo` claims a number reserved by a balance-init account at a different address. Defense-in-depth against a malformed genesis silently corrupting state. - **`InitChainerConfig.StrictReplay`** (this iteration): opt-in fail-closed boot. Defaults to `false` for backwards compat. Hardfork operators set it to `true` so any non-skipped tx replay failure aborts `InitChain` instead of letting the chain boot in a corrupted state. Skipped txs (`metadata.Failed = true`) do not count. - **Genesis-mode tx sig verify with PastChainIDs[0]** genesis-mode txs (no metadata or `BlockHeight == 0`) use the first `PastChainIDs` entry for sig verify when a hardfork is in progress (PR #5540). The genesis-mode chain-ID branch is now gated on `metadata == nil` (this iteration) so migration txs (`metadata != nil`, `BlockHeight == 0`, `Timestamp != 0`) keep their metadata-driven `ctxFn` instead of being silently overwritten. - **`BaseApp.InitChain` error surfacing** (this iteration): when `InitChainer` returns `ResponseInitChain.Error`, return cleanly instead of falling through to the validators-count sanity check, which would otherwise panic with a misleading `"validators count mismatch"` and mask the real cause. - **Replay report** per-tx categorization emitted via logger after `InitChain`: `ok` / `ok_gas_differs` / `failed` / `skipped_failed`. Exposes `Outcomes()` and `FailedCount()` for external tooling. ### Hardfork tooling (`contribs/gnogenesis/internal/fork/`) - **`gnogenesis fork generate`** generate a hardfork genesis from a source chain (RPC URL, local data dir, or exported tarball). - **`gnogenesis fork test`** local genesis replay smoke-test. - **`--patch-realm PKGPATH=SRCDIR`** (repeatable) rewrite a genesis-mode `addpkg` tx in-place with files from `SRCDIR`. Lets you deliver realm upgrades as part of the fork (e.g. adding a new `.gno` file to an existing realm) since you cannot re-addpkg post-deploy (PR #5540). - **`--migration-tx`** inject a single migration tx at the end of the historical replay. - **`bruteForceSignerSequence`** resolve signer sequences during export by trying candidate values against the signature. ## Bugs found and fixed during review ### tm2 consensus (all fixed) 1. **Fast-sync broken with InitialHeight > 1** `BlockPool` started at `store.Height()+1 = 1` instead of `state.LastBlockHeight+1 = InitialHeight`. Nodes trying to fast-sync would request non-existent blocks. 2. **Validator set / consensus params not saved at InitialHeight** `saveState` only saved validators when `nextHeight == 1`. With InitialHeight > 1, `LoadValidators` failed and `LoadConsensusParams` panicked at block InitialHeight+1. 3. **`ValidateBasic` bypass via zeroed `LastBlockID`** any block with `LastBlockID.IsZero()` could skip commit validation. Fixed: only allow skip when commit is also nil/empty. 4. **`BaseApp.validateHeight` permanent contiguity bypass** the previous "allow monotonic jump" branch compared real block height against the multistore version. After the first commit, `actual > prevHeight` is trivially true on every subsequent block, so the contiguity check was bypassed forever (an attacker or buggy consensus engine that skipped N blocks would be silently accepted). Fixed by tracking real chain height in `lastBlockHeight` (this iteration). 5. **`BaseApp.InitChain` masking real error** when `loadAppState` returned an error response, the validators-count sanity check fired with `"validators count mismatch"` masking the actual cause. Fixed: return cleanly on error response (this iteration). ### gno.land (all fixed) 6. **`loadAppState` returns nil even on N tx failures** chain booted in a corrupted state when historical-tx replay had failures. Fixed via opt-in `StrictReplay` in `InitChainerConfig` (this iteration). 7. **Migration-tx `ctxFn` overwrite** the genesis-mode chain-ID branch fired on any `metadata.BlockHeight == 0`, stomping the metadata-driven `Timestamp` override on migration txs. Fixed: tighten predicate to `metadata == nil` and compose with any prior `ctxFn` (this iteration). 8. **`NewAccountWithNumber` had no SignerInfo collision check** two `SignerInfo` entries with the same `AccountNum` but different addresses, or a `SignerInfo` colliding with a balance-init account, would silently zero the original account's balance. Fixed: rename to `NewAccountWithUncheckedNumber` (forcing every call site to acknowledge the precondition) plus `validateSignerInfo` preflight in `loadAppState` (this iteration). 9. **Failed-tx `ResponseDeliverTx` was empty (looked like success)** explicit error marker so indexers can distinguish. 10. **`GnoGenesisState.InitialHeight` wasn't cross-checked against `GenesisDoc.InitialHeight`** added `InitialHeight` to `RequestInitChain` and validate in `loadAppState`. 11. **`RequestInitChain.InitialHeight` had no amino round-trip test** silent registration regression would only surface during a real hardfork (this iteration). ### Hardfork tooling (fixed) 12. **`applyOverlay` silent no-op** listed scripts but didn't execute them, returned success. Fixed: returns error when scripts found but execution not implemented. 13. **JSONL serialization used `encoding/json` instead of amino** interface types (`std.Msg`) lost on round-trip. Fixed: both writer and reader now use amino. 14. **`verifyGenesisFile` failure returned success** tool could produce invalid genesis and exit 0. Fixed: failure aborts (opt out with `--no-verify`). 15. **Zero unit tests for `bruteForceSignerSequence`** fixed: 10 table-driven tests. ### Docs linter (side fix for green CI) - Skip `staging.gno.land`, `archive.org`, and add retry/timeout logic so transient remote-link failures don't block unrelated PRs. ## Still open (design / follow-up) - **RPC retry/resume** (`contribs/gnogenesis/internal/fork/source_rpc.go`) a single transient error during tx fetch aborts everything; needs exponential backoff + checkpointing. Architectural, follow-up PR. - **Streaming tx export** full tx history is held in memory; will OOM on large chains. Needs streaming writer, follow-up PR. - **`queryAccountAtHeight` silent nil** all error paths return nil with no indication; flaky RPC → wrong sequence metadata. ## Cherry-picked from [#5597](#5597) (this iteration) Three follow-ups originally staged in the master-based hardfork series, brought back to where they belong since they modify or extend code introduced here: - [`1babfe42a`](1babfe42a) `fix(consensus): skip phantom heights during replay when InitialHeight > 1` — ABCI handshake replay path used to assume heights `[1, appBlockHeight+1]` always have a stored block; for chains starting at `InitialHeight > 1`, heights below `InitialHeight` never had blocks and replay errored with "block not found for height 1". - [`5bf2fa53e`](5bf2fa53e) `fix(gnogenesis): default gas-storage params and gas_replay_mode in hardfork genesis` — `buildHardforkGenesis` now defaults the post-#5415 `vm.params` gas-storage fields from `vm.DefaultParams()` when the source has them all at zero, and sets `gas_replay_mode = "source"` when unset. Operator overrides preserved. 4 unit tests. - [`e31268467`](e31268467) `feat(gnogenesis): add --skip-failing-genesis-txs and --skip-genesis-sig-verification flags to fork test` — `make smoketest` now matches what production validators actually run. ## End-to-end validation The hf-glue testbed ([#5486](#5486)) runs `make fetch && make init && make up` against `rpc.gno.land` halt@704052 and produces a 192 MB hardfork genesis that replays with **0 / 2715 tx failures** and boots a live `gnoland-1` node. ## Dependencies / related PRs - **Depends on / pairs with:** [#5533](#5533) (`contribs/tx-archive` metadata + `SignerInfo` populator) for replay-ready backups - **Used in:** [#5486](#5486) (hf-glue testbed) - **Also fixed here:** [#5539](#5539) (docs-linter skip staging preemptive fix, committed here too to keep CI green) ## AI disclosure Developed with significant assistance from Claude Code for testing, review, and iterative fixes. --------- Co-authored-by: moul <noreply@moul.io> Co-authored-by: jaekwon <jae@tendermint.com> assisted-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: aeddi <antoine.e.b@gmail.com> merging for moul

moul added 2 commits April 1, 2026 15:23

feat(gnoland): support chain upgrade genesis replay with original cha…

f10bb36

…in ID

misc: add gnoland-1 genesis generation script

badb0bd

github-project-automation Bot added this to 💪 Bounties & Worx and 🧙‍♂️Gno.land development Apr 1, 2026

github-project-automation Bot moved this to Triage in 🧙‍♂️Gno.land development Apr 1, 2026

github-actions Bot added 📦 ⛰️ gno.land Issues or PRs gno.land package related 🐳 devops labels Apr 1, 2026

github-actions Bot assigned moul Apr 1, 2026

github-project-automation Bot added this to 😎 Manfred's Board Apr 1, 2026

github-project-automation Bot moved this to 📥 Inbox in 😎 Manfred's Board Apr 1, 2026

feat(tm2): add InitialHeight to GenesisDoc for chain upgrades

48c2cc0

github-actions Bot added the 📦 🌐 tendermint v2 Issues or PRs tm2 related label Apr 1, 2026

misc: rewrite generate-genesis.sh with 3-phase approach

60b558e

moul mentioned this pull request Apr 1, 2026

feat(node): add halt_height config field for coordinated chain upgrades #5334

Merged

5 tasks

Merge branch 'master' into feat/genesis-replay-upgrade

876fe1a

moul changed the title ~~feat(gnoland): chain upgrade genesis replay with original chain ID~~ feat(gnoland): chain hardfork Apr 3, 2026

Merge branch 'master' into feat/genesis-replay-upgrade

66ef0aa

Merge branch 'master' into feat/genesis-replay-upgrade

969b93c

moul changed the title ~~feat(gnoland): chain hardfork~~ feat(gnoland): chain hardfork mechanism Apr 8, 2026

moul mentioned this pull request Apr 9, 2026

WIP feat(deployments): gnoland-1.x hardfork content #5376

Open

4 tasks

moul added 2 commits April 9, 2026 16:16

test(tm2): add coverage for GenesisDoc.InitialHeight in consensus rep…

18963a7

…lay and ValidateAndComplete

moul marked this pull request as ready for review April 9, 2026 14:29

Merge branch 'master' into feat/genesis-replay-upgrade

c66db84

moul changed the title ~~feat(gnoland): chain hardfork mechanism~~ WIP feat(gnoland): chain hardfork mechanism Apr 9, 2026

moul added 3 commits April 9, 2026 17:34

chore(hardfork): gitignore built binary

aefa3ae

Merge remote-tracking branch 'origin/feat/genesis-replay-upgrade' int…

b22f514

…o worktree-hf-framework-5411

moul mentioned this pull request Apr 9, 2026

feat(gnoland): add block_height and chain_id to GnoTxMetadata #5390

Closed

3 tasks

github-actions Bot added the 🐹 golang Pull requests that update Go code label Apr 9, 2026

moul linked an issue Apr 9, 2026 that may be closed by this pull request

meta: chain hardfork #5374

Closed

21 tasks

moul mentioned this pull request Apr 9, 2026

meta: chain hardfork #5374

Closed

21 tasks

moul added a commit to moul/gno that referenced this pull request Apr 13, 2026

merge(glue): bring in gnolang#5411 genesis replay upgrade

e804681

moul mentioned this pull request Apr 13, 2026

test(hf-glue): hardfork end-to-end testbed (DO NOT MERGE) — integrates #5511 + #5376 #5486

Draft

This was referenced Apr 13, 2026

feat(gnoland): genesis tx metadata + chain replay at initial height #5489

Open

feat(gnoland): chain hardfork mechanism v3 #5511

Merged

moul changed the title ~~WIP feat(gnoland): chain hardfork mechanism~~ feat(gnoland): chain hardfork mechanism Apr 15, 2026

nemanjantic moved this from Triage to In Review in 🧙‍♂️Gno.land development Apr 15, 2026

nemanjantic added the a/gnops DevOps, Valopers, NetOps, Infra, Monitoring, Coordination team label Apr 15, 2026

moul marked this pull request as draft April 17, 2026 15:26

moul closed this Apr 17, 2026

github-project-automation Bot moved this from 📥 Inbox to ✅ Done in 😎 Manfred's Board Apr 17, 2026

github-project-automation Bot moved this from In Review to Done in 🧙‍♂️Gno.land development Apr 17, 2026

github-project-automation Bot moved this to Done in 💪 Bounties & Worx Apr 17, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(gnoland): chain hardfork mechanism#5411

feat(gnoland): chain hardfork mechanism#5411
moul wants to merge 14 commits into
masterfrom
feat/genesis-replay-upgrade

moul commented Apr 1, 2026 •

edited

Loading

Uh oh!

Gno2D2 commented Apr 1, 2026 •

edited

Loading

✅ Automated Checks (for Contributors):

☑️ Contributor Actions:

☑️ Reviewer Actions:

📚 Resources:

If

Can be checked by

If

Can be checked by

Uh oh!

codecov Bot commented Apr 1, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

moul commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Key changes

How it works

Migration script

Related PRs

Open items

Uh oh!

Gno2D2 commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🛠 PR Checks Summary

Manual Checks (for Reviewers):

✅ Automated Checks (for Contributors):

☑️ Contributor Actions:

☑️ Reviewer Actions:

📚 Resources:

If

Can be checked by

If

Can be checked by

Uh oh!

codecov Bot commented Apr 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

moul commented Apr 1, 2026 •

edited

Loading

Gno2D2 commented Apr 1, 2026 •

edited

Loading

codecov Bot commented Apr 1, 2026 •

edited

Loading