Gravity v1.10.1
Gravity v1.10.1 is the recommended mainnet upgrade after v1.9.1 / v1.9.3. It contains bugfixes and optimizations only: no hardfork and no new activation time on any network. It supersedes the v1.10.0 pre-release and carries everything in it.
What's changed since v1.10.0
RPC replays committed blocks with Gravity's rules
#848 bumps gravity-reth to gravity-reth#453 and assembles the node with EthereumNode::gravity_components().
Endpoints that re-execute a committed block (debug_trace*, trace_*, eth_callMany, reth_getBlockExecutionOutcome, …) now follow the chain's execution rules: system/user precompile sets, the Alpha gas exemption for SYSTEM_CALLER, activation-block state changes, EIP-2935 fed the consensus parent id, and the onBlockStart that pre-Alpha DKG epoch blocks omit (gravity-reth#440). Tracing such blocks no longer fails with nonce too high.
Behavior changes:
debug_executionWitness*is refused for every block.- Replay endpoints targeting
pendingfail; only committed blocks can be replayed.
Block production and state transition are unchanged.
Startup ordering
gravity-reth#446: the pipe event bus creates its channels eagerly, removing a 120 s startup timeout panic.
Consensus recovery at epoch boundaries
#847: after a validator restart, an epoch-boundary block that was ordered but not yet committed could be rejected as already ordered, leaving the epoch unable to commit. Recovery now replays the uncommitted path from the commit root, and blocks past an epoch boundary no longer write or overwrite randomness.
Forward epoch sync is on by default
#841: forward epoch sync (opt-in in v1.9.2 / v1.9.3 / v1.10.0) is now enabled by default. Set ENABLE_FORWARD_EPOCH_SYNC=false to keep the legacy reverse sync. Peers that do not serve forward sync still fall back to the legacy path.
Carried from v1.10.0
Pruned-node recovery of Gravity system-tx senders (gravity-reth#437), the mempool poll-reconcile broadcast timeline (#808), the Oracle generic relayer runtime (#803), forward epoch sync hardening (#819 / #832 / #834) and the genesis generate-account fix (#829). See the v1.10.0 notes.
Compatibility and operator notes
- No hardfork, no deadline. Mainnet Alpha and Beta/Osaka stay at their v1.9.1 times; Gamma is not scheduled on mainnet. Nodes may upgrade one at a time and run mixed with v1.9.1 / v1.9.3.
- Forward epoch sync default changes. Validators and VFNs that ran with the v1.9.x default (off) will run with it on after upgrading unless
ENABLE_FORWARD_EPOCH_SYNC=falseis set. - Testnet-only code (TestnetOwnerFix) does not run on mainnet.
- Rollback: <to be filled from devnet acceptance — whether a v1.10.1 data directory can be reopened by v1.9.x>.
Validation
<to be filled from devnet acceptance: rolling upgrade v1.9.2 → v1.10.1 from checkpoint A-v1.9.2, mixed-version window, bridge exactly-once, RPC replay of pre-Alpha DKG epoch blocks, forward epoch sync on/off, rollback; checkpoint B-v1.10.1.>
Assets
gravity_node, gravity_cli and their .sha256 files are built by the release workflow from the tagged commit. Docker image: ghcr.io/galxe/gravity_node:v1.10.1.