Skip to content

chore(deps): bump gravity-reth to acc45884 (rocksdb durability fix)#730

Merged
nekomoto911 merged 1 commit into
mainfrom
update-greth
May 25, 2026
Merged

chore(deps): bump gravity-reth to acc45884 (rocksdb durability fix)#730
nekomoto911 merged 1 commit into
mainfrom
update-greth

Conversation

@nekomoto911

@nekomoto911 nekomoto911 commented May 25, 2026

Copy link
Copy Markdown
Contributor

What

Bump the gravity-reth git dependency:

  • 41c0b7092ad578abcfb59b3aeb0ce9ec43f5fcf7acc458846c2f1fc684fa4344cf02ae9488efd252

Updates bin/gravity_node/Cargo.toml and the regenerated Cargo.lock. No SDK source changes.

Why

Pulls in gravity-reth#340 — a RocksDB durability fix. The rev range is exactly one commit ahead (ahead 1, behind 0); this bump introduces #340 and nothing else.

provider_rw.commit() called rocksdb::DB::write() without fdatasync(). With wal_bytes_per_sync=4MB, the low-traffic account_db/storage_db could go 2000+ blocks without syncing, risking large trie data loss on power failure and a state-root mismatch panic during consensus re-execution after a crash.

The fix:

  1. All write() calls in commit_view() use write_opt(sync=true) — every commit() is fsync-durable before returning.
  2. Disable pipelined write and drop wal_bytes_per_sync (redundant with per-commit sync).
  3. Recovery always re-checks every stage checkpoint (no early return), repairing only stages that are behind.

Ref: Galxe/gravity-reth#340

@nekomoto911 nekomoto911 changed the title chore(deps): update greth chore(deps): bump gravity-reth to acc45884 (rocksdb durability fix) May 25, 2026
@nekomoto911 nekomoto911 merged commit 9d6cfee into main May 25, 2026
9 of 10 checks passed
@nekomoto911 nekomoto911 deleted the update-greth branch May 25, 2026 11:09
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