StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

lisk-mainnet: add Isthmus/Jovian/Karst fork times to genesis.json #18

Merged
sebastian merged 1 commits from issue-101 into main 2026-06-21 06:34:38 +00:00
Conversation 0 Commits 1 Files Changed 1 +3
claude commented 2026-06-21 06:30:48 +00:00
Collaborator
Copy Link

Summary

Adds three missing fork time entries to op/lisk/mainnet/genesis.json:

  • isthmusTime: 1746806401 (activated May 2025)
  • jovianTime: 1764691201
  • karstTime: 1783526401

Root cause

The lisk-mainnet-op-reth-pruned-trace containers on rpc-de-10 mount this genesis.json via --chain=/config/genesis.json. The file stopped at holoceneTime, so op-reth v2.3.1 crashed with Unsupported fork on every Isthmus-era block (activation ~33.6M). The node was stuck ~327k blocks behind chain head, earning $0.

op-reth v2.3.1 already supports all three forks correctly when given a complete chain config — confirmed via docker run --chain=lisk showing Isthmus/Jovian/Karst in startup. The timestamps are sourced from:

  1. op-node rollup config on rpc-de-10 (isthmus_time=@1746806401)
  2. the lisk-sepolia genesis.json in this same repo (already has isthmusTime for testnet)
  3. op-reth v2.3.1 built-in --chain lisk superchain registry

Verification

After this change, the lisk-mainnet-op-reth startup log will show Isthmus @1746806401 in the fork list and the Unsupported fork error stops. No other networks affected — this is a lisk-mainnet-only genesis file.

Asset commit: f7b585307e

(vibe-node issue #101)

## Summary Adds three missing fork time entries to `op/lisk/mainnet/genesis.json`: - `isthmusTime: 1746806401` (activated May 2025) - `jovianTime: 1764691201` - `karstTime: 1783526401` ## Root cause The `lisk-mainnet-op-reth-pruned-trace` containers on rpc-de-10 mount this genesis.json via `--chain=/config/genesis.json`. The file stopped at `holoceneTime`, so op-reth v2.3.1 crashed with `Unsupported fork` on every Isthmus-era block (activation ~33.6M). The node was stuck ~327k blocks behind chain head, earning $0. op-reth v2.3.1 already supports all three forks correctly when given a complete chain config — confirmed via `docker run --chain=lisk` showing Isthmus/Jovian/Karst in startup. The timestamps are sourced from: 1. op-node rollup config on rpc-de-10 (`isthmus_time=@1746806401`) 2. the lisk-sepolia genesis.json in this same repo (already has `isthmusTime` for testnet) 3. op-reth v2.3.1 built-in `--chain lisk` superchain registry ## Verification After this change, the lisk-mainnet-op-reth startup log will show `Isthmus @1746806401` in the fork list and the `Unsupported fork` error stops. No other networks affected — this is a lisk-mainnet-only genesis file. Asset commit: f7b585307eb0 (vibe-node issue #101)
claude added 1 commit 2026-06-21 06:30:49 +00:00
lisk/mainnet: add isthmusTime, jovianTime, karstTime fork timestamps to genesis.json f7b585307e
sebastian merged commit f7b585307e into main 2026-06-21 06:34:38 +00:00
sebastian deleted branch issue-101 2026-06-21 06:34:39 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#18
Delete Branch "issue-101"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?