op-reth sepolia fixes: superseed Jovian fork times, Karst v2.3.1 bump, op-sepolia/soneium template fixes
- superseed-sepolia: add holocene/isthmus/jovian fork times to rollup.json (CL) and genesis.json (EL). jovian_time=1768978801 is superseed's chain-specific activation (verified live via sepolia.superseed.xyz optimism_rollupConfig); the official superseed-xyz/node repo + the old committed config both lacked it, causing op-node "failed to parse L1 info deposit tx ... unexpected length: 178". - op-reth v2.3.0 -> v2.3.1 across all op-reth composes (Karst-mandatory release, Sepolia activation Jun 17 2026 16:00 UTC). - op-sepolia: --chain=optimismsepolia -> optimism-sepolia (invalid chain spec prevented op-reth from starting). - soneium-minato-sepolia (reth/geth/erigon): L1 upstream vars now resolve to ETHEREUM_SEPOLIA_* (were ETHEREUM_MINATO-SEPOLIA_*, nonexistent -> no L1 RPC); state-cache shell var de-hyphenated; pectra blob-schedule override now emitted. NOTE: superseed karst_time not yet published by the chain; must be added before Jun 17 2026 once superseed announces it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -22,6 +22,9 @@
|
||||
"ecotoneTime": 1720195200,
|
||||
"fjordTime": 1720627201,
|
||||
"graniteTime": 1725984001,
|
||||
"holoceneTime": 1732633200,
|
||||
"isthmusTime": 1744905600,
|
||||
"jovianTime": 1768978801,
|
||||
"terminalTotalDifficulty": 0,
|
||||
"terminalTotalDifficultyPassed": true,
|
||||
"optimism": {
|
||||
|
||||
@@ -33,7 +33,9 @@
|
||||
"ecotone_time": 1720195200,
|
||||
"fjord_time": 1720627201,
|
||||
"granite_time": 1725984001,
|
||||
"isthmus_time":1744905600,
|
||||
"holocene_time": 1732633200,
|
||||
"isthmus_time": 1744905600,
|
||||
"jovian_time": 1768978801,
|
||||
"batch_inbox_address": "0x3a81f59e6bf4238d1ed202f3b06389454de3f204",
|
||||
"deposit_contract_address": "0x7a0db8c51432d2c3eb4e8f360a2eeb26ff2809fb",
|
||||
"l1_system_config_address": "0x4df2f170214198df84716b89c84b0c177c39f6c9"
|
||||
|
||||
Reference in New Issue
Block a user