zora-mainnet-op-reth-pruned-trace on rpc-de-33 is stuck at block 0 / DRPC EU-West shows 100% unavailable.
Root cause (confirmed by cursor on rpc-de-33):op/zora/mainnet/genesis.json config block only contains regolithTime: 0 (Bedrock/Regolith only). Op-reth starts at block 0 and op-node feeds current-head payloads (~block 47,708,000) which include withdrawals (Canyon activates Shanghai). Op-reth rejects every payload with "withdrawals pre-Shanghai" → 10,000+ failures → node stays stuck at block 0 forever.
Fix
Added the following hardfork timestamps to the config section of op/zora/mainnet/genesis.json:
After merge: deploy to rpc-de-33 via deploy-compose-repo. The datadir volume (rpc_zora-mainnet-op-reth-pruned-trace) is only 2.7 MB (never synced), so wiping on force-recreate is safe. Node will start fresh from genesis with correct fork schedule and begin syncing normally.
## Problem
`zora-mainnet-op-reth-pruned-trace` on rpc-de-33 is stuck at block 0 / DRPC EU-West shows 100% unavailable.
**Root cause (confirmed by cursor on rpc-de-33):** `op/zora/mainnet/genesis.json` config block only contains `regolithTime: 0` (Bedrock/Regolith only). Op-reth starts at block 0 and op-node feeds current-head payloads (~block 47,708,000) which include withdrawals (Canyon activates Shanghai). Op-reth rejects every payload with "withdrawals pre-Shanghai" → 10,000+ failures → node stays stuck at block 0 forever.
## Fix
Added the following hardfork timestamps to the `config` section of `op/zora/mainnet/genesis.json`:
```json
"shanghaiTime": 1704992401,
"canyonTime": 1704992401,
"deltaTime": 1708560000,
"ecotoneTime": 1710374401,
"fjordTime": 1720627201,
"graniteTime": 1726070401,
"holoceneTime": 1736445601,
"isthmusTime": 1746806401,
"jovianTime": 1764691201,
"karstTime": 1783526401
```
Also added/updated the `optimism` config section:
```json
"optimism": {
"eip1559Elasticity": 6,
"eip1559Denominator": 50,
"eip1559DenominatorCanyon": 250
}
```
Values sourced from the superchain-registry zora.toml and the rollup.json already present on rpc-de-33 (which has the correct fork schedule).
## Verification
- `./update.sh` (filtered `op.zora.mainnet` and full run) completed with 0 errors
- Generated compose files correctly include the `/config` mount for `./op/zora/mainnet:/config` serving the updated genesis.json
- rpc branch commit: `afafaea4299d9c95a80e91665e47d6832fe5468c`
## Deploy notes
After merge: deploy to rpc-de-33 via `deploy-compose-repo`. The datadir volume (`rpc_zora-mainnet-op-reth-pruned-trace`) is only 2.7 MB (never synced), so wiping on force-recreate is safe. Node will start fresh from genesis with correct fork schedule and begin syncing normally.
(vibe-node issue #189)
Closing without merge — dropping zora archive (operator decision, Sebastian 2026-06-28). We're no longer maintaining zora, so this fix won't be deployed.
Closing without merge — dropping zora archive (operator decision, Sebastian 2026-06-28). We're no longer maintaining zora, so this fix won't be deployed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
zora-mainnet-op-reth-pruned-traceon rpc-de-33 is stuck at block 0 / DRPC EU-West shows 100% unavailable.Root cause (confirmed by cursor on rpc-de-33):
op/zora/mainnet/genesis.jsonconfig block only containsregolithTime: 0(Bedrock/Regolith only). Op-reth starts at block 0 and op-node feeds current-head payloads (~block 47,708,000) which include withdrawals (Canyon activates Shanghai). Op-reth rejects every payload with "withdrawals pre-Shanghai" → 10,000+ failures → node stays stuck at block 0 forever.Fix
Added the following hardfork timestamps to the
configsection ofop/zora/mainnet/genesis.json:Also added/updated the
optimismconfig section:Values sourced from the superchain-registry zora.toml and the rollup.json already present on rpc-de-33 (which has the correct fork schedule).
Verification
./update.sh(filteredop.zora.mainnetand full run) completed with 0 errors/configmount for./op/zora/mainnet:/configserving the updated genesis.jsonafafaea4299d9c95a80e91665e47d6832fe5468cDeploy notes
After merge: deploy to rpc-de-33 via
deploy-compose-repo. The datadir volume (rpc_zora-mainnet-op-reth-pruned-trace) is only 2.7 MB (never synced), so wiping on force-recreate is safe. Node will start fresh from genesis with correct fork schedule and begin syncing normally.(vibe-node issue #189)
Closing without merge — dropping zora archive (operator decision, Sebastian 2026-06-28). We're no longer maintaining zora, so this fix won't be deployed.