zero-gravity: init guard must check the CONFIG volume, not a data-volume proxy

aristotle @ rpc-de-32 crash-looped after its build was fixed: priv_validator_state.json found in /root/.0g. Continuing! Already initialized, continuing! panic: ProvideBlsSigner (node-core/components/signer.go:46): key file does not exist at path: /root/.0g/config/priv_validator_key.json $DATA_DIR and $CONFIG_DIR are SEPARATE docker volumes (<node>_zerog and <node>_config), but the guard tested only $DATA_DIR/priv_validator_state.json — inferring the state of the config volume from a file on the data volume. Worse, the copy order wrote that guard file BEFORE the two key files, so an init interrupted between them left the data volume with the guard and the config volume without the keys. Every later start then took the 'Already initialized' branch, copied nothing, and panicked. Unrecoverable by restarting: the node wedges permanently. aristotle got there via the repeated build failures earlier today. Fix, two parts: - guard on everything 0gchaind needs to boot (both config keys AND the data state file), not one proxy file on the wrong volume; - write the keys FIRST and the guard file LAST, so an interrupted init re-runs on the next start instead of latching into the wedged state. Tested locally against the real 0gchaind binary (aristotle v1.0.6), sandboxed HOME: scenario before after fresh volumes keys created keys created (no regression) wedged (state, no keys) keys MISSING keys created (unwedges) partial (state+node_key) keys MISSING keys created healthy (all present) no re-init no re-init, and a SENTINEL written into priv_validator_key.json survives -> never clobbers an initialized node The 'wedged' row reproduces aristotle's production failure exactly. Note this regenerates node identity on an affected node (node_key.json, priv_validator_key.json). These are RPC nodes that never sign, so a fresh identity is harmless; chain data on the _zerog volume is untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
deploy: regenerate compose from vibe-node main 3c848087f5c8
2026-08-12 19:33:48 +00:00 · 2026-08-12 17:37:46 +00:00 · 2026-08-12 16:53:00 +00:00 · 2026-08-12 11:09:51 +00:00 · 2026-08-12 08:38:04 +00:00 · 2026-08-11 06:21:38 +00:00
23 changed files with 151 additions and 57 deletions
--- a/arc/reth/arc-mainnet-reth-archive-trace.yml
+++ b/arc/reth/arc-mainnet-reth-archive-trace.yml
@@ -45,7 +45,7 @@ services:
  arc-mainnet-archive-sockets-init:
    image: debian:bookworm-slim
    entrypoint: [/bin/sh, -c]
-    command: [rm -f /sockets/*.ipc && chown 999:999 /sockets]
+    command: [chown 999:999 /sockets]
    restart: no
    depends_on:
      arc-mainnet-archive-consensus-init:
--- a/arc/reth/arc-mainnet-reth-pruned-trace.yml
+++ b/arc/reth/arc-mainnet-reth-pruned-trace.yml
@@ -45,7 +45,7 @@ services:
  arc-mainnet-sockets-init:
    image: debian:bookworm-slim
    entrypoint: [/bin/sh, -c]
-    command: [rm -f /sockets/*.ipc && chown 999:999 /sockets]
+    command: [chown 999:999 /sockets]
    restart: no
    depends_on:
      arc-mainnet-consensus-init:
--- a/arc/reth/arc-testnet-reth-archive-trace.yml
+++ b/arc/reth/arc-testnet-reth-archive-trace.yml
@@ -45,7 +45,7 @@ services:
  arc-testnet-archive-sockets-init:
    image: debian:bookworm-slim
    entrypoint: [/bin/sh, -c]
-    command: [rm -f /sockets/*.ipc && chown 999:999 /sockets]
+    command: [chown 999:999 /sockets]
    restart: no
    depends_on:
      arc-testnet-archive-consensus-init:
--- a/arc/reth/arc-testnet-reth-pruned-trace.yml
+++ b/arc/reth/arc-testnet-reth-pruned-trace.yml
@@ -45,7 +45,7 @@ services:
  arc-testnet-sockets-init:
    image: debian:bookworm-slim
    entrypoint: [/bin/sh, -c]
-    command: [rm -f /sockets/*.ipc && chown 999:999 /sockets]
+    command: [chown 999:999 /sockets]
    restart: no
    depends_on:
      arc-testnet-consensus-init:
--- a/arc/reth/arc-testnet-reth-pruned.yml
+++ b/arc/reth/arc-testnet-reth-pruned.yml
@@ -45,7 +45,7 @@ services:
  arc-testnet-sockets-init:
    image: debian:bookworm-slim
    entrypoint: [/bin/sh, -c]
-    command: [rm -f /sockets/*.ipc && chown 999:999 /sockets]
+    command: [chown 999:999 /sockets]
    restart: no
    depends_on:
      arc-testnet-consensus-init:
--- a/ethereum/reth/ethereum-mainnet-reth-minimal-trace--blsync.yml
+++ b/ethereum/reth/ethereum-mainnet-reth-minimal-trace--blsync.yml
@@ -123,7 +123,7 @@ services:
      - pruning

  ethereum-mainnet-reth-minimal-node:
-    image: ${ETHEREUM_BLSYNC_IMAGE:-ethereum/client-go}:${ETHEREUM_MAINNET_BLSYNC_VERSION:-alltools-v1.17.4}
+    image: ${ETHEREUM_BLSYNC_IMAGE:-ethereum/client-go}:${ETHEREUM_MAINNET_BLSYNC_VERSION:-alltools-v1.17.5}
    ports:
      - 19286:19286
      - 19286:19286/udp
--- a/linea/besu/linea-mainnet-besu-pruned-bonsai.yml
+++ b/linea/besu/linea-mainnet-besu-pruned-bonsai.yml
@@ -54,6 +54,7 @@ services:
      - 9545
    command:
      - --Xbonsai-full-flat-db-enabled=true
+      - --bonsai-historical-block-limit=4096
      - --bootnodes=enode://069800db9e6e0ec9cadca670994ef1aea2cfd3d88133e63ecadbc1cdbd1a5847b09838ee08d8b5f02a9c32ee13abeb4d4104bb5514e5322c9d7ee19f41ff3e51@3.132.73.210:31002,enode://a8e03a71eab12ec4b47bb6e19169d8e4dc7a58373a2476969bbe463f2dded6003037fa4dd5f71e15027f7fc8d7340956fbbefed67ddd116ac19a7f74da034b61@3.132.73.210:31003,enode://97706526cf79df9d930003644f9156805f6c8bd964fc79e083444f7014ce10c9bdd2c5049e63b58040dca1d4c82ebef970822198cf0714de830cff4111534ff1@18.223.198.165:31004,enode://24e1c654a801975a96b7f54ebd7452ab15777fc635c1db25bdbd4425fdb04e7f4768e9e838a87ab724320a765e41631d5d37758c933ad0e8668693558125c8aa@18.223.198.165:31000,enode://27010891d960f73d272a553f72b6336c6698db3ade98d631f09c764e57674a797be5ebc6829ddbb65ab564f439ebc75215d20aa98b6f351d12ea623e7d139ac3@3.132.73.210:31001,enode://228e1b8a4931e46f383e30721dac21fb8fb4e5e1b32c870e13b25478c82db3dc1cd9e7ceb93d302a766466b55638cc9c5cbfc43aa48fa41ced19baf365951f76@3.1.142.64:31002,enode://c22eb0d40fc3ad5ea710aeddea906567778166bfe18c157955e8c39b23a46c45db18a0fa2ba07f2b64c81178a8c796aec2a29151533920ead06fcdfc6d8d03c6@47.128.192.57:31004,enode://8ce733abe39fd7ae0a278b9893f85c1193c611a3886168690dd843435460f22cc4d61f9e8d0ace7f5905836a665319a31cccdaacdada2acc69972c382ecce7db@3.1.142.64:31003,enode://b7c1b2bed65a855f7a2104aac9a14674dfdf018fdac763415b373b29ce18cdb81d36328ba4e5c9f12629f3a50c3e8f9ee048f22dbdbe93a82813da89c6b81334@51.20.235.126:31004,enode://95270e0550848a72fb141cf27f1c4ea10714edde365b411dc0fa06c81c0f282ce155eb9fa472b6b8bb9ee98395eeaf4c5a7b02a01fe58b37ea98ba152eda4c37@13.50.94.193:31000,enode://72013391755f24f08567b932feeeec4c893c06e0b1fb480890c83bf87fd277ad86a5ab9cb586db9ae9970371a2f8cb0c96f6c9f69045abca0fb801db7f047138@51.20.235.126:31001
      - --data-path=/opt/besu/database
      - --data-storage-format=BONSAI
--- a/linea/besu/linea-sepolia-besu-pruned-bonsai.yml
+++ b/linea/besu/linea-sepolia-besu-pruned-bonsai.yml
@@ -54,6 +54,7 @@ services:
      - 9545
    command:
      - --Xbonsai-full-flat-db-enabled=true
+      - --bonsai-historical-block-limit=4096
      - --bootnodes=enode://6f20afbe4397e51b717a7c1ad3095e79aee48c835eebd9237a3e8a16951ade1fe0e66e981e30ea269849fcb6ba03d838da37f524fabd2a557474194a2e2604fa@18.221.100.27:31002,enode://ce1e0d8e0500cb5c0ac56bdcdafb2d6320c3a2c5125b5ccf12f5dfc9b47ee74acbcafc32559017613136c9c36a0ce74ba4f83b7fb8244f099f3b15708d9d3129@3.23.75.47:31000,enode://1b026a5eb0ae74300f58987d235ef0e3a550df963345cb3574be3b0b54378bd11f14dfd515a8976f2c2d2826090e9507b8ccc24f896a9ffffffcabcfd996a733@3.129.120.128:31001
      - --data-path=/opt/besu/database
      - --data-storage-format=BONSAI
--- a/op/geth/celo-mainnet-op-geth-archive-leveldb-hash.yml
+++ b/op/geth/celo-mainnet-op-geth-archive-leveldb-hash.yml
@@ -267,7 +267,7 @@ services:
      - EIGENDA_PROXY_S3_CREDENTIAL_TYPE=public
      - EIGENDA_PROXY_S3_ENDPOINT=storage.googleapis.com
      - EIGENDA_PROXY_S3_PATH=blobs/
-      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V1,V2
+      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V2
      - EIGENDA_PROXY_STORAGE_FALLBACK_TARGETS=s3
    restart: unless-stopped
    networks:
--- a/op/geth/celo-mainnet-op-geth-pruned-leveldb-hash.yml
+++ b/op/geth/celo-mainnet-op-geth-pruned-leveldb-hash.yml
@@ -266,7 +266,7 @@ services:
      - EIGENDA_PROXY_S3_CREDENTIAL_TYPE=public
      - EIGENDA_PROXY_S3_ENDPOINT=storage.googleapis.com
      - EIGENDA_PROXY_S3_PATH=blobs/
-      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V1,V2
+      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V2
      - EIGENDA_PROXY_STORAGE_FALLBACK_TARGETS=s3
    restart: unless-stopped
    networks:
--- a/op/geth/celo-mainnet-op-geth-pruned-pebble-hash.yml
+++ b/op/geth/celo-mainnet-op-geth-pruned-pebble-hash.yml
@@ -264,7 +264,7 @@ services:
      - EIGENDA_PROXY_S3_CREDENTIAL_TYPE=public
      - EIGENDA_PROXY_S3_ENDPOINT=storage.googleapis.com
      - EIGENDA_PROXY_S3_PATH=blobs/
-      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V1,V2
+      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V2
      - EIGENDA_PROXY_STORAGE_FALLBACK_TARGETS=s3
    restart: unless-stopped
    networks:
--- a/op/geth/celo-mainnet-op-geth-pruned-pebble-path.yml
+++ b/op/geth/celo-mainnet-op-geth-pruned-pebble-path.yml
@@ -264,7 +264,7 @@ services:
      - EIGENDA_PROXY_S3_CREDENTIAL_TYPE=public
      - EIGENDA_PROXY_S3_ENDPOINT=storage.googleapis.com
      - EIGENDA_PROXY_S3_PATH=blobs/
-      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V1,V2
+      - EIGENDA_PROXY_STORAGE_BACKENDS_TO_ENABLE=V2
      - EIGENDA_PROXY_STORAGE_FALLBACK_TARGETS=s3
    restart: unless-stopped
    networks:
--- a/op/geth/fraxtal-mainnet-op-geth-archive-leveldb-hash.yml
+++ b/op/geth/fraxtal-mainnet-op-geth-archive-leveldb-hash.yml
@@ -45,9 +45,6 @@ services:
    ulimits:
      nofile: 1048576    # Max open files (for RPC/WS connections)
    user: root
-    ports:
-      - 13290:13290
-      - 13290:13290/udp
    expose:
      - 8545
      - 6060
@@ -64,7 +61,6 @@ services:
      - GETH_ROLLUP_SEQUENCERHTTP=https://rpc.mainnet.frax.com
    entrypoint: /bin/sh -c '[ -f /config/genesis.json ] && geth --db.engine=leveldb --gcmode=archive --datadir /data init --state.scheme=hash /config/genesis.json; [ -f /config/static-nodes.json ] && cp -f /config/static-nodes.json /data/static-nodes.json; exec geth "$@"' --
    command:
-      - --bootnodes=enr:-J24QI8QR7VIgvQFuvLl09b9ocugoQ1WkS_AOMWKFgNX48-4P1hjgDKGeMFXZmKtfjYA2aEehxKT066riaktnxhh92OGAY5Sw_QsgmlkgnY0gmlwhCztZu2Hb3BzdGFja4P8AQCJc2VjcDI1NmsxoQM2KM0mkdH97Ze8AqwxLeqc934PKj8-xoKsyP6mAptWwIN0Y3CCdl2DdWRwgnZd,enr:-J24QGD1J-g2EPY9b7XiuwLhIoGocVp2qx2gWSfDI_CdftiPSHlgi7G6LtzkQlDskuSvRj4OXTg3vXLISubphXNNhqyGAY5Sw8GxgmlkgnY0gmlwhCzW_iGHb3BzdGFja4P8AQCJc2VjcDI1NmsxoQPvMYlJHJUsEyciuJCTkKHLE2ogZ6cs2xuPI28CGq0CTIN0Y3CCdl2DdWRwgnZd,enr:-J24QCA5I3xroUXt7Ge_Kf04VCRBnI-GbZeyBxOkkpIDGGLrVsonrbngQG1hAEnufRb1TgS6sNFCGtaZ2ZpRx7AgciGGAY5SxEy0gmlkgnY0gmlwhCLzRQyHb3BzdGFja4P8AQCJc2VjcDI1NmsxoQOaHzrtPQWYcwAcFJWFrbGlbNUsBC0VEhCcH02RbgEIwIN0Y3CCdl2DdWRwgnZd
      - --datadir=/data
      - --db.engine=leveldb
      - --gcmode=archive
@@ -72,9 +68,8 @@ services:
      - --metrics
      - --metrics.addr=0.0.0.0
      - --metrics.port=6060
-      - --nat=extip:${IP}
      - --networkid=252
-      - --port=13290
+      - --nodiscover
      - --rpc.gascap=600000000
      - --rpc.txfeecap=0
      - --state.scheme=hash
@@ -145,7 +140,7 @@ services:
      - OP_NODE_RPC_ADDR=0.0.0.0
      - OP_NODE_RPC_PORT=9545
      - OP_NODE_SNAPSHOT_LOG=/tmp/op-node-snapshot-log
-      - OP_NODE_SYNCMODE=execution-layer
+      - OP_NODE_SYNCMODE=consensus-layer
      - OP_NODE_VERIFIER_L1_CONFS=0
    entrypoint: [op-node]
    restart: unless-stopped
--- a/op/geth/fraxtal-mainnet-op-geth-pruned-pebble-path.yml
+++ b/op/geth/fraxtal-mainnet-op-geth-pruned-pebble-path.yml
@@ -45,9 +45,6 @@ services:
    ulimits:
      nofile: 1048576    # Max open files (for RPC/WS connections)
    user: root
-    ports:
-      - 10282:10282
-      - 10282:10282/udp
    expose:
      - 8545
      - 6060
@@ -64,7 +61,6 @@ services:
      - GETH_ROLLUP_SEQUENCERHTTP=https://rpc.mainnet.frax.com
    entrypoint: /bin/sh -c '[ -f /config/genesis.json ] && geth --db.engine=pebble --gcmode=full --datadir /data init --state.scheme=path /config/genesis.json; [ -f /config/static-nodes.json ] && cp -f /config/static-nodes.json /data/static-nodes.json; exec geth "$@"' --
    command:
-      - --bootnodes=enr:-J24QI8QR7VIgvQFuvLl09b9ocugoQ1WkS_AOMWKFgNX48-4P1hjgDKGeMFXZmKtfjYA2aEehxKT066riaktnxhh92OGAY5Sw_QsgmlkgnY0gmlwhCztZu2Hb3BzdGFja4P8AQCJc2VjcDI1NmsxoQM2KM0mkdH97Ze8AqwxLeqc934PKj8-xoKsyP6mAptWwIN0Y3CCdl2DdWRwgnZd,enr:-J24QGD1J-g2EPY9b7XiuwLhIoGocVp2qx2gWSfDI_CdftiPSHlgi7G6LtzkQlDskuSvRj4OXTg3vXLISubphXNNhqyGAY5Sw8GxgmlkgnY0gmlwhCzW_iGHb3BzdGFja4P8AQCJc2VjcDI1NmsxoQPvMYlJHJUsEyciuJCTkKHLE2ogZ6cs2xuPI28CGq0CTIN0Y3CCdl2DdWRwgnZd,enr:-J24QCA5I3xroUXt7Ge_Kf04VCRBnI-GbZeyBxOkkpIDGGLrVsonrbngQG1hAEnufRb1TgS6sNFCGtaZ2ZpRx7AgciGGAY5SxEy0gmlkgnY0gmlwhCLzRQyHb3BzdGFja4P8AQCJc2VjcDI1NmsxoQOaHzrtPQWYcwAcFJWFrbGlbNUsBC0VEhCcH02RbgEIwIN0Y3CCdl2DdWRwgnZd
      - --datadir=/data
      - --db.engine=pebble
      - --gcmode=full
@@ -72,13 +68,12 @@ services:
      - --metrics
      - --metrics.addr=0.0.0.0
      - --metrics.port=6060
-      - --nat=extip:${IP}
      - --networkid=252
-      - --port=10282
+      - --nodiscover
      - --rpc.gascap=600000000
      - --rpc.txfeecap=0
      - --state.scheme=path
-      - --syncmode=snap
+      - --syncmode=full
      - --http
      - --http.addr=0.0.0.0
      - --http.api=eth,net,web3,debug,admin,txpool,engine
@@ -145,7 +140,7 @@ services:
      - OP_NODE_RPC_ADDR=0.0.0.0
      - OP_NODE_RPC_PORT=9545
      - OP_NODE_SNAPSHOT_LOG=/tmp/op-node-snapshot-log
-      - OP_NODE_SYNCMODE=execution-layer
+      - OP_NODE_SYNCMODE=consensus-layer
      - OP_NODE_VERIFIER_L1_CONFS=0
    entrypoint: [op-node]
    restart: unless-stopped
--- a/op/reth/zircuit-garfield-op-reth-pruned-trace.yml
+++ b/op/reth/zircuit-garfield-op-reth-pruned-trace.yml
@@ -30,7 +30,7 @@ x-logging-defaults: &logging-defaults

 services:
  zircuit-garfield-op-reth-pruned:
-    image: ${ZIRCUIT_RETH_IMAGE:-ghcr.io/conduitxyz/conduit-op-reth}:${ZIRCUIT_GARFIELD_RETH_VERSION:-v2.1.1}
+    image: ${ZIRCUIT_RETH_IMAGE:-ghcr.io/conduitxyz/conduit-op-reth}:${ZIRCUIT_GARFIELD_RETH_VERSION:-v2.1.2}
    sysctls:
      # TCP Performance
      net.ipv4.tcp_slow_start_after_idle: 0       # Disable slow start after idle
--- a/op/reth/zircuit-mainnet-op-reth-pruned-trace.yml
+++ b/op/reth/zircuit-mainnet-op-reth-pruned-trace.yml
@@ -30,7 +30,7 @@ x-logging-defaults: &logging-defaults

 services:
  zircuit-mainnet-op-reth-pruned:
-    image: ${ZIRCUIT_RETH_IMAGE:-ghcr.io/conduitxyz/conduit-op-reth}:${ZIRCUIT_MAINNET_RETH_VERSION:-v2.1.1}
+    image: ${ZIRCUIT_RETH_IMAGE:-ghcr.io/conduitxyz/conduit-op-reth}:${ZIRCUIT_MAINNET_RETH_VERSION:-v2.1.2}
    sysctls:
      # TCP Performance
      net.ipv4.tcp_slow_start_after_idle: 0       # Disable slow start after idle
--- a/reference-rpc-endpoint.json
+++ b/reference-rpc-endpoint.json
@@ -216,6 +216,7 @@
      "https://bsc-dataseed3.ninicoin.io",
      "https://bsc-dataseed4.ninicoin.io",
      "https://bsc-rpc.publicnode.com",
+      "https://bsc-rpc-public.chainpulse.cc",
      "https://bsc.drpc.org"
    ]
  },
@@ -233,6 +234,7 @@
      "https://data-seed-prebsc-1-s3.bnbchain.org:8545",
      "https://data-seed-prebsc-2-s3.bnbchain.org:8545",
      "https://bsc-testnet-rpc.publicnode.com",
+      "https://bsc-rpc-public.chainpulse.cc/testnet",
      "https://bsc-testnet.drpc.org"
    ]
  },
@@ -3366,6 +3368,16 @@
      "https://mova.drpc.org"
    ]
  },
+  "mova-mainnet-v2": {
+    "protocol": "eth",
+    "id": 61901,
+    "block_time_ms": 2000,
+    "lagging_lag": 10,
+    "syncing_lag": 20,
+    "urls": [
+      "https://mova-mainnet-v2.drpc.org"
+    ]
+  },
  "mova-testnet": {
    "protocol": "eth",
    "id": 10323,
@@ -3635,6 +3647,7 @@
    "lagging_lag": 10,
    "syncing_lag": 20,
    "urls": [
+      "https://rpc.pharos.xyz",
      "https://pharos.drpc.org"
    ]
  },
@@ -3720,6 +3733,7 @@
    "lagging_lag": 20,
    "syncing_lag": 40,
    "urls": [
+      "https://humanity-main.g.alchemy.com/public",
      "https://humanity.drpc.org"
    ]
  },
--- a/tempo/reth/tempo-mainnet-reth-archive-trace.yml
+++ b/tempo/reth/tempo-mainnet-reth-archive-trace.yml
@@ -32,7 +32,7 @@ x-logging-defaults: &logging-defaults

 services:
  tempo-mainnet-reth-init:
-    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_CONSENSUS_KEYGEN_VERSION:-1.10.2}
+    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_CONSENSUS_KEYGEN_VERSION:-1.12.0}
    entrypoint: [/bin/sh, -c]
    command:
      - if [ ! -f /secrets/validator_key.json ]; then tempo consensus generate-signing-key --output /secrets/validator_key.json; fi
@@ -44,7 +44,7 @@ services:
    logging: *logging-defaults

  tempo-mainnet-reth:
-    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_MAINNET_RETH_VERSION:-1.10.2}
+    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_MAINNET_RETH_VERSION:-1.12.0}
    sysctls:
      # TCP Performance
      net.ipv4.tcp_slow_start_after_idle: 0       # Disable slow start after idle
--- a/tempo/reth/tempo-mainnet-reth-pruned-trace.yml
+++ b/tempo/reth/tempo-mainnet-reth-pruned-trace.yml
@@ -32,7 +32,7 @@ x-logging-defaults: &logging-defaults

 services:
  tempo-mainnet-reth-pruned-init:
-    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_CONSENSUS_KEYGEN_VERSION:-1.10.2}
+    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_CONSENSUS_KEYGEN_VERSION:-1.12.0}
    entrypoint: [/bin/sh, -c]
    command:
      - if [ ! -f /secrets/validator_key.json ]; then tempo consensus generate-signing-key --output /secrets/validator_key.json; fi
@@ -44,7 +44,7 @@ services:
    logging: *logging-defaults

  tempo-mainnet-reth-pruned:
-    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_MAINNET_RETH_VERSION:-1.10.2}
+    image: ${TEMPO_RETH_IMAGE:-ghcr.io/tempoxyz/tempo}:${TEMPO_MAINNET_RETH_VERSION:-1.12.0}
    sysctls:
      # TCP Performance
      net.ipv4.tcp_slow_start_after_idle: 0       # Disable slow start after idle
--- a/zero-gravity/geth/zero-gravity-aristotle-geth-pruned-pebble-path.yml
+++ b/zero-gravity/geth/zero-gravity-aristotle-geth-pruned-pebble-path.yml
@@ -35,7 +35,7 @@ services:
      context: ./zero-gravity
      dockerfile: zerog.Dockerfile
      args:
-        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_ARISTOTLE_ZEROG_VERSION:-3.0.3}
+        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_ARISTOTLE_ZEROG_VERSION:-1.0.6}
        ZERO_GRAVITY_CHAIN_SPEC: aristotle
    sysctls:
      # TCP Performance
@@ -118,7 +118,7 @@ services:
      context: ./zero-gravity
      dockerfile: zerog.Dockerfile
      args:
-        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_ARISTOTLE_ZEROG_VERSION:-3.0.3}
+        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_ARISTOTLE_ZEROG_VERSION:-1.0.6}
        ZERO_GRAVITY_CHAIN_SPEC: aristotle
    ports:
      - 19914:19914
--- a/zero-gravity/geth/zero-gravity-galileo-geth-pruned-pebble-path.yml
+++ b/zero-gravity/geth/zero-gravity-galileo-geth-pruned-pebble-path.yml
@@ -35,7 +35,7 @@ services:
      context: ./zero-gravity
      dockerfile: zerog.Dockerfile
      args:
-        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_GALILEO_ZEROG_VERSION:-3.0.3}
+        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_GALILEO_ZEROG_VERSION:-3.0.8}
        ZERO_GRAVITY_CHAIN_SPEC: galileo
    sysctls:
      # TCP Performance
@@ -62,7 +62,7 @@ services:
      - CHAIN_NAME=galileo
    entrypoint: [/usr/local/bin/init.sh, geth]
    command:
-      - --bootnodes=enode://de7b86d8ac452b1413983049c20eafa2ea0851a3219c2cc12649b971c1677bd83fe24c5331e078471e52a94d95e8cde84cb9d866574fec957124e57ac6056699@8.218.88.60:30303
+      - --bootnodes=enode://4c94b9ab893ee17f58505b48b53d6c02d52bd5567e5fc6c028a29ad25ce1d553286a7fe3a6c051ba18c466b196762ab0e92695d6abbaf7f70afcca2e165bca8c@34.82.252.10:30303
      - --config /0g/geth-config.toml
      - --datadir=/root/.ethereum
      - --db.engine=pebble
@@ -118,7 +118,7 @@ services:
      context: ./zero-gravity
      dockerfile: zerog.Dockerfile
      args:
-        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_GALILEO_ZEROG_VERSION:-3.0.3}
+        ZERO_GRAVITY_VERSION: ${ZERO_GRAVITY_GALILEO_ZEROG_VERSION:-3.0.8}
        ZERO_GRAVITY_CHAIN_SPEC: galileo
    ports:
      - 16172:16172
@@ -140,7 +140,7 @@ services:
      - --chaincfg.node-api.logging
      - --home=/root/.0g
      - --p2p.external_address=${IP}:16172
-      - --p2p.seeds=${ZERO_GRAVITY_GALILEO_ZEROG_SEEDS:-85a9b9a1b7fa0969704db2bc37f7c100855a75d9@8.218.88.60:26656}
+      - --p2p.seeds=${ZERO_GRAVITY_GALILEO_ZEROG_SEEDS:-e0750abc061d276894a593c7b671913c14aa4ecc@34.82.252.10:26656}
      - --pruning=default
      - --rpc.laddr=tcp://0.0.0.0:16172
    restart: unless-stopped
--- a/zero-gravity/scripts/init.sh
+++ b/zero-gravity/scripts/init.sh
@@ -61,23 +61,41 @@ env

 # seems to be the same for all the 0g chains

-if [ ! -f "$DATA_DIR/priv_validator_state.json" ]; then
-    echo "priv_validator_state.json not found in $HOME_DIR. Proceeding with initialization steps..."
+# $DATA_DIR and $CONFIG_DIR are SEPARATE docker volumes (<node>_zerog and <node>_config),
+# so the presence of a file in one says nothing about the other. Guard on everything
+# 0gchaind actually needs to boot, and write the copies so the LAST file written is the
+# one that would make a re-run skip.
+#
+# The previous version guarded solely on $DATA_DIR/priv_validator_state.json and copied it
+# BEFORE the two key files. An init interrupted between those copies therefore left the
+# data volume with the guard file and the config volume without the keys, so every later
+# start took the "Already initialized" branch, copied nothing, and 0gchaind panicked:
+#
+#   panic: error calling provider ProvideBlsSigner (node-core/components/signer.go:46):
+#          key file does not exist at path: /root/.0g/config/priv_validator_key.json
+#
+# That state is unrecoverable by restarting - the node wedges permanently. Hit on
+# aristotle @ rpc-de-32 on 2026-08-12 after repeated build failures interrupted its init.
+if [ ! -f "$CONFIG_DIR/priv_validator_key.json" ] || \
+   [ ! -f "$CONFIG_DIR/node_key.json" ] || \
+   [ ! -f "$DATA_DIR/priv_validator_state.json" ]; then
+    echo "0g: node identity incomplete (config keys and/or priv_validator_state.json). Initializing..."
    TMP_DIR=$(mktemp -d)
    # You can add any additional initialization logic here if needed
    if /0g/bin/0gchaind init ${MONIKER} --chaincfg.chain-spec ${CHAIN_SPEC} --home $TMP_DIR; then
        cp -r /0g/0g-home/0gchaind-home/config/* $CONFIG_DIR
-        cp $TMP_DIR/data/priv_validator_state.json $DATA_DIR
+        # Keys first, guard file last: if this is interrupted the next start re-runs
+        # initialization instead of latching into the wedged state described above.
        cp $TMP_DIR/config/node_key.json $CONFIG_DIR
        cp $TMP_DIR/config/priv_validator_key.json $CONFIG_DIR
+        cp $TMP_DIR/data/priv_validator_state.json $DATA_DIR
    else
        echo "Already initialized, continuing!" >&2
    fi
    rm -rf $TMP_DIR # delete tmp dir

 else
-    echo "priv_validator_state.json found in $HOME_DIR. Continuing!" >&2
-    echo "Already initialized, continuing!" >&2
+    echo "0g: node identity complete (config keys + priv_validator_state.json). Continuing!" >&2
 fi

 exec /0g/bin/0gchaind $@
--- a/zero-gravity/zerog.Dockerfile
+++ b/zero-gravity/zerog.Dockerfile
@@ -8,22 +8,92 @@ RUN chmod +x /usr/local/bin/init.sh

 ARG ZERO_GRAVITY_VERSION
 ARG ZERO_GRAVITY_CHAIN_SPEC
-RUN if [ "${ZERO_GRAVITY_CHAIN_SPEC}" = "aristotle" ]; then \
-        curl -sL https://github.com/0gfoundation/0gchain-Aristotle/releases/download/${ZERO_GRAVITY_VERSION}/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}.tar.gz -o /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}.tar.gz; \
+
+# 0G publishes each network from a DIFFERENT repository, and the release-tag format is not
+# consistent within either of them. The asset filename is always "<spec>-v<version>.tar.gz";
+# only the tag varies:
+#
+#   aristotle -> 0gchain-Aristotle   1.0.4 = "1.0.4"      1.0.6 = "v1.0.6"
+#   galileo   -> 0gchain-NG          3.0.3 = "v3.0.3"     3.0.7 = "galileo-v3.0.7"   3.0.8 = "v3.0.8"
+#
+# So the tag cannot be hardcoded. Resolve it by trying the known forms in order and taking
+# the first that actually yields the asset.
+#
+# curl uses -f (fail on HTTP error). Without it a 404 HTML body is written into the .tar.gz
+# and the build dies several layers later at "tar: not in gzip format" -- an error that
+# points nowhere near the real cause. That has cost three separate misdiagnoses.
+RUN set -eu; \
+    ASSET="${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}.tar.gz"; \
+    if [ "${ZERO_GRAVITY_CHAIN_SPEC}" = "aristotle" ]; then \
+        REPO="0gfoundation/0gchain-Aristotle"; \
+        TAGS="${ZERO_GRAVITY_VERSION} v${ZERO_GRAVITY_VERSION} ${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}"; \
    else \
-        curl -sL https://github.com/0gfoundation/0gchain-NG/releases/download/v${ZERO_GRAVITY_VERSION}/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}.tar.gz -o /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}.tar.gz; \
-    fi
-RUN tar -xzf /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}.tar.gz -C /tmp
-RUN if [ "${ZERO_GRAVITY_CHAIN_SPEC}" = "galileo" ]; then \
-        mv /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}/rpc /0g; \
-    else \
-        mkdir -p /0g && \
-        cp -a /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}/* /0g/ 2>/dev/null || true; \
-        cp -a /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}/.[^.]* /0g/ 2>/dev/null || true; \
-        rm -rf /tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}; \
+        REPO="0gfoundation/0gchain-NG"; \
+        TAGS="v${ZERO_GRAVITY_VERSION} ${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION} ${ZERO_GRAVITY_VERSION}"; \
+    fi; \
+    for TAG in ${TAGS}; do \
+        URL="https://github.com/${REPO}/releases/download/${TAG}/${ASSET}"; \
+        echo "0g: trying tag '${TAG}' -> ${URL}"; \
+        if curl -fsSL "${URL}" -o "/tmp/${ASSET}"; then \
+            echo "0g: resolved ${ZERO_GRAVITY_CHAIN_SPEC} ${ZERO_GRAVITY_VERSION} from tag '${TAG}'"; \
+            break; \
+        fi; \
+        rm -f "/tmp/${ASSET}"; \
+    done; \
+    if [ ! -s "/tmp/${ASSET}" ]; then \
+        echo "0g: FATAL - no release asset '${ASSET}' found in ${REPO} under any of: ${TAGS}" >&2; \
+        echo "0g: aristotle and galileo are SEPARATE repos on SEPARATE version lines" >&2; \
+        echo "0g: aristotle = 0gchain-Aristotle (1.0.x), galileo = 0gchain-NG (3.0.x)" >&2; \
+        echo "0g: check that version '${ZERO_GRAVITY_VERSION}' exists for '${ZERO_GRAVITY_CHAIN_SPEC}'" >&2; \
+        exit 1; \
    fi

-RUN chmod +x /0g/bin/0gchaind
-RUN chmod +x /0g/bin/geth
+# Extract by DETECTING the layout rather than assuming one per chain. 0G has shipped
+# three shapes so far and changed between them without notice:
+#
+#   galileo <= 3.0.3  <root>/{rpc,validator,archive,seed}/bin/ + configs   (168 MB)
+#                     -> binaries duplicated inside every profile dir
+#   galileo >= 3.0.8  <root>/bin/  shared, + <root>/{rpc,...}/ configs      (69 MB)
+#                     -> binaries DEDUPLICATED to the tarball root; rpc/ is configs-only
+#   aristotle 1.0.x   <root>/bin/ + configs, no profile dirs at all
+#
+# So "does <root>/rpc exist" is NOT sufficient: 3.0.8 still has rpc/, it just no longer
+# holds bin/. Take configs from the profile dir when present, then top the binaries up
+# from the shared root bin/ if the profile dir didn't supply them.
+#
+# The old code hardcoded "galileo -> mv <root>/rpc /0g", so 3.0.8 yielded configs but no
+# binaries and the build died two layers later at
+# `chmod: cannot access '/0g/bin/0gchaind'` — an error naming neither the chain, the
+# version, nor the layout. Assert on the binaries here so the NEXT upstream reshuffle
+# reports itself at the point of failure instead.
+RUN set -eu; \
+    SRC="/tmp/${ZERO_GRAVITY_CHAIN_SPEC}-v${ZERO_GRAVITY_VERSION}"; \
+    tar -xzf "${SRC}.tar.gz" -C /tmp; \
+    mkdir -p /0g; \
+    if [ -d "${SRC}/rpc" ]; then \
+        echo "0g: profile dir found -> ${SRC}/rpc"; \
+        cp -a "${SRC}/rpc/." /0g/; \
+    else \
+        echo "0g: no profile dir -> using tarball root ${SRC}"; \
+        cp -a "${SRC}/." /0g/; \
+    fi; \
+    if [ ! -f /0g/bin/0gchaind ] && [ -d "${SRC}/bin" ]; then \
+        echo "0g: binaries not in the profile dir -> topping up from ${SRC}/bin"; \
+        cp -a "${SRC}/bin" /0g/; \
+    fi; \
+    rm -rf "${SRC}"; \
+    missing=""; \
+    for b in 0gchaind geth; do \
+        [ -f "/0g/bin/${b}" ] || missing="${missing} bin/${b}"; \
+    done; \
+    if [ -n "${missing}" ]; then \
+        echo "0g: FATAL - missing after extraction:${missing}" >&2; \
+        echo "0g: ${ZERO_GRAVITY_CHAIN_SPEC} v${ZERO_GRAVITY_VERSION} tarball layout not recognised." >&2; \
+        echo "0g: known layouts are '<root>/rpc/bin/' (per-profile) and '<root>/bin/' (flat)." >&2; \
+        echo "0g: contents of /0g were:" >&2; \
+        ls -la /0g >&2 || true; \
+        exit 1; \
+    fi; \
+    chmod +x /0g/bin/0gchaind /0g/bin/geth

-ENTRYPOINT [ "init.sh" ]
+ENTRYPOINT [ "init.sh" ]
Author	SHA1	Message	Date
Claude Agent	92cdb31d17	zero-gravity: init guard must check the CONFIG volume, not a data-volume proxy aristotle @ rpc-de-32 crash-looped after its build was fixed: priv_validator_state.json found in /root/.0g. Continuing! Already initialized, continuing! panic: ProvideBlsSigner (node-core/components/signer.go:46): key file does not exist at path: /root/.0g/config/priv_validator_key.json $DATA_DIR and $CONFIG_DIR are SEPARATE docker volumes (<node>_zerog and <node>_config), but the guard tested only $DATA_DIR/priv_validator_state.json — inferring the state of the config volume from a file on the data volume. Worse, the copy order wrote that guard file BEFORE the two key files, so an init interrupted between them left the data volume with the guard and the config volume without the keys. Every later start then took the 'Already initialized' branch, copied nothing, and panicked. Unrecoverable by restarting: the node wedges permanently. aristotle got there via the repeated build failures earlier today. Fix, two parts: - guard on everything 0gchaind needs to boot (both config keys AND the data state file), not one proxy file on the wrong volume; - write the keys FIRST and the guard file LAST, so an interrupted init re-runs on the next start instead of latching into the wedged state. Tested locally against the real 0gchaind binary (aristotle v1.0.6), sandboxed HOME: scenario before after fresh volumes keys created keys created (no regression) wedged (state, no keys) keys MISSING keys created (unwedges) partial (state+node_key) keys MISSING keys created healthy (all present) no re-init no re-init, and a SENTINEL written into priv_validator_key.json survives -> never clobbers an initialized node The 'wedged' row reproduces aristotle's production failure exactly. Note this regenerates node identity on an affected node (node_key.json, priv_validator_key.json). These are RPC nodes that never sign, so a fresh identity is harmless; chain data on the _zerog volume is untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-12 19:33:48 +00:00
Claude Agent	4a060bee0d	deploy: regenerate compose from vibe-node main 3c848087f5c8	2026-08-12 17:37:46 +00:00
Claude Agent	4db13b2fc4	deploy: regenerate compose from vibe-node main 0415567d141c	2026-08-12 16:53:00 +00:00
Claude Agent	6df9f0f17a	zero-gravity: detect tarball layout; galileo 3.0.8 moved binaries to a shared root bin/ Fixes the de-32 build break introduced by vibe-node #2912 (galileo 3.0.3 -> 3.0.8, merged as bc4cecf). Job ad580587: #16 chmod: cannot access '/0g/bin/0gchaind': No such file or directory The Dockerfile hardcoded 'galileo -> mv <root>/rpc /0g'. That held for 3.0.3, where every profile dir carried its own copy of the binaries. 3.0.8 DEDUPLICATED them into a shared <root>/bin/ (168 MB -> 69 MB), leaving rpc/ as configs-only — so the move produced configs and no binaries, and the build died two layers later on a chmod. Note 'does <root>/rpc exist' is not a sufficient test: 3.0.8 still ships rpc/, it just no longer holds bin/. Verified layouts: galileo 3.0.3 <root>/{rpc,validator,archive,seed}/bin/ + configs galileo 3.0.8 <root>/bin/ shared + <root>/{rpc,...}/ configs aristotle 1.0.6 <root>/bin/ + configs, no profile dirs So: take configs from the profile dir when present, then top the binaries up from the shared root bin/ if the profile dir did not supply them. Also asserts both binaries exist immediately after extraction, naming the chain, the version and the known layouts — so the next upstream reshuffle reports itself at the point of failure rather than as an anonymous chmod error. Verified against the real artifacts — all three now yield an identical /0g (bin/0gchaind 76M, bin/geth 46M, geth-config.toml, geth-genesis.json, kzg-trusted-setup.json, 0g-home/, rollback_cl.sh), and a synthetic unknown layout exits 1 with the diagnostic instead of reaching chmod. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-12 11:09:51 +00:00
Claude Agent	561ff43828	deploy: regenerate compose from vibe-node main bc4cecf1a74f	2026-08-12 08:38:04 +00:00
Claude Agent	cfac32736e	zero-gravity: resolve release tag by probing known forms; fail loudly on 404 0G publishes aristotle and galileo from two different repos, and neither uses a consistent release-tag format. The asset filename is always <spec>-v<version>.tar.gz; only the tag varies: aristotle -> 0gchain-Aristotle 1.0.4 = "1.0.4" 1.0.6 = "v1.0.6" galileo -> 0gchain-NG 3.0.3 = "v3.0.3" 3.0.7 = "galileo-v3.0.7" 3.0.8 = "v3.0.8" The hardcoded formats meant aristotle could not go past 1.0.4 and galileo could not reach 3.0.7. Resolve the tag by trying the known forms in order instead. Also switch curl -sL to -fsSL. Without -f a 404 HTML body was written into the .tar.gz and the build failed several layers later at 'tar: not in gzip format', an error pointing nowhere near the cause. That has now caused three separate misdiagnoses, including a de-32 build blocker. Verified end-to-end against the real artifacts: aristotle 1.0.4/1.0.6 and galileo 3.0.3/3.0.7/3.0.8 all resolve; aristotle 3.0.3 and galileo 9.9.9 fail immediately with an actionable message. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-11 06:21:38 +00:00
Claude Agent	799209b5d2	zero-gravity-aristotle: fix node version to 1.0.4 (was 3.0.3 which doesn't exist for Aristotle repo)	2026-08-10 21:56:44 +00:00
Claude Agent	17cd0d5f23	deploy: regenerate compose from vibe-node main c5e4641499ff	2026-08-07 12:13:22 +00:00
Claude Agent	d57fd2e644	tempo-mainnet: bump reth to 1.12.0 (T9 hardfork requires v1.12.0, node crash-loop at block 33513646)	2026-08-06 16:24:58 +00:00
Claude Agent	e1427de966	ethereum: bump blsync to alltools-v1.17.5 for go-ethereum v1.17.5 patch (2026-07-27); includes polygon-amoy bor 2.10.0-private for hardfork at block 44,120,000	2026-08-06 11:48:53 +00:00
Claude Agent	db38905bfe	polygon-amoy: bump bor from 2.9.0 to 2.10.0-private for private Amoy hardfork at block 44,120,000 (ExtraData layout change) Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>	2026-08-05 22:35:04 +00:00
Claude Agent	699723d742	berachain: upgrade bera-reth to v1.4.4 for Osaka1 hardfork support Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>	2026-08-05 21:15:20 +00:00