Gravity v1.10.2-pre

Gravity v1.10.2-pre

Gravity v1.10.2-pre is an urgent validator hotfix on top of v1.10.1. It adds one change, Oracle quorum certificate verification (#850), and keeps everything else in v1.10.1 unchanged: same gravity-reth, same dependency lock, same genesis and network configuration. It does not include the testnet genesis change from #849.

What's changed since v1.10.1

Verify Oracle quorum certificates before execution

#850: before an Oracle (ObservedJWKUpdate) validator transaction is converted into execution data, the node now verifies the full ProviderJWKs update against its validator multi-signature, using the validator set of the block's own epoch.

• An update whose certificate fails verification (empty or invalid signatures, insufficient voting power, invalid bitmap, or content changed after signing) is dropped. Only that update is dropped: other valid updates and user transactions in the same block still execute.
• Normal execution and restart/BlockStore recovery apply the same rule.
• Blocks whose Oracle certificates are valid execute exactly as in v1.10.1.

Compatibility and operator notes

• No hardfork and no new activation time. The check is always on.
• Upgrade every validator promptly, one at a time. v1.10.1 and v1.10.2-pre only disagree on a block that carries an invalid Oracle certificate: v1.10.1 executes the update and v1.10.2-pre drops it. Such blocks are not produced by honest proposers, but keep the mixed-version window short.
• Operators upgrading from v1.9.x also pick up all v1.10.1 changes, including forward epoch sync being on by default. See the v1.10.1 notes.
• Keep existing Safety Rules / last-vote data when upgrading. Do not restore older signing state.

Assets

gravity_node, gravity_cli and their .sha256 files are built by the release workflow from the tagged commit (2195a2d2, branch branch-v1.10). Docker image: ghcr.io/galxe/gravity_node:v1.10.2-pre.