Skip to content

fix(registry): repoint 12 moved node repos (+migrate polygon-zkevm to cdk-erigon)#11

Merged
tazhate merged 2 commits into
masterfrom
fix/moved-repos-batch-12
Jun 14, 2026
Merged

fix(registry): repoint 12 moved node repos (+migrate polygon-zkevm to cdk-erigon)#11
tazhate merged 2 commits into
masterfrom
fix/moved-repos-batch-12

Conversation

@tazhate

@tazhate tazhate commented Jun 14, 2026

Copy link
Copy Markdown
Owner

What

versioncheck flagged 12 chains whose VersionPolicy pointed at repositories that now 404. Each was repointed to its current, live-verified home (VersionPolicy + pinned default image). polygon-zkevm additionally gets a full client migration.

Chain Old (404) New
kava kava-labs/kava kava/kava:v0.28.2-goleveldb
sei seiprotocol/seid ghcr.io/sei-protocol/sei:v6.5.2
dymension dymensionxyz/dymd ghcr.io/dymensionxyz/dymension:4.0.1
solana solanalabs/agave anzaxyz/agave:v3.1.14 (Anza org)
core coredao/core-chain ghcr.io/coredao-org/core-chain:1.0.22
metis metisprotocol/l2geth metisdao/l2geth:v0.3.9
taiko taikoxyz/taiko-geth us-docker.pkg.dev/evmchain/images/taiko-geth:v2.5.0
manta-pacific mantanetwork/op-geth public.ecr.aws/i6b2w2n6/op-geth:7.1.0
plasma plasma-next/node ghcr.io/plasmalaboratories/plasma-consensus-public:0.15.0
boba-eth bobanetwork/op-geth upstream op-geth GAR :v1.101702.2
hashkey hashkeychain/hashkey-geth upstream op-geth GAR :v1.101702.2
polygon-zkevm 0xpolygonhermez/zkevm-node (archived) ghcr.io/0xpolygon/cdk-erigon:v2.64.2 — migrated client

polygon-zkevm: zkevm-node → cdk-erigon

zkevm-node is archived; mainnet operators now run cdk-erigon (an Erigon fork — a different client, not just a repo move). The adapter is rewritten:

  • config → cdk-erigon hermez-mainnet yaml (http 8545 with eth/debug/net/trace/web3/erigon/zkevm, externalcl, l2-chain-id 1101, sequencer https://zkevm-rpc.com, datastreamer stream.zkevm-rpc.com:6900, canonical L1 contract addresses)
  • ContainerArgs: --config=/config/hermezconfig.yaml --zkevm.l1-rpc-url=$(L1_RPC_URL) (image ENTRYPOINT is cdk-erigon); L1 URL still defaults to http://ethereum:8545 via env
  • resources bumped to 8 CPU / 16Gi / 2Ti

Config values taken from the upstream hermezconfig-mainnet.yaml example. The datastreamer/sequencer endpoints are the public Polygon ones — worth a live re-sync check before prod.

Other notes

  • boba-eth, hashkey — own fork image gone; both are OP-Stack L2s now riding the shared upstream op-geth GAR image (like base/optimism).
  • kava tags carry a -goleveldb suffix; dymension/core/plasma/manta-pacific publish bare semver (no v) — patterns adjusted.

Verification

  • Every replacement re-checked by hand against Docker Hub / GHCR (OCI Accept header) / GAR / ECR-public APIs.
  • versioncheck --chain <x> for all 12 resolves with no registry error.
  • go build ./..., go vet, go test ./internal/adapters/ ./internal/controller/ green.

🤖 Generated with Claude Code

tazhate added 2 commits June 14, 2026 10:50
versioncheck flagged 12 chains whose VersionPolicy pointed at dead repos
(404). Found and live-verified the current home for each via the
registry tag APIs:

  kava           docker.io kava-labs/kava   -> kava/kava (v…-goleveldb tags)
  sei            docker.io seiprotocol/seid -> ghcr.io sei-protocol/sei
  dymension      docker.io dymensionxyz/dymd-> ghcr.io dymensionxyz/dymension (no v)
  solana         docker.io solanalabs/agave -> docker.io anzaxyz/agave (Anza org)
  core           docker.io coredao/core-chain -> ghcr.io coredao-org/core-chain (no v)
  metis          docker.io metisprotocol/l2geth -> docker.io metisdao/l2geth
  taiko          docker.io taikoxyz/taiko-geth -> GAR evmchain/images/taiko-geth
  manta-pacific  docker.io mantanetwork/op-geth -> ECR i6b2w2n6/op-geth
  plasma         docker.io plasma-next/node -> ghcr.io plasmalaboratories/plasma-consensus-public

OP-Stack chains whose own fork image vanished now ride the shared upstream
op-geth GAR image (geth-compatible, same as base/optimism):
  boba-eth (Boba dropped its op-geth fork), hashkey (no HashKey image; its
  own fullnode-sync pulls upstream op-geth).

polygon-zkevm: zkevm-node is archived (deprecated for cdk-erigon, a
different client). Dropped its VersionPolicy to stop the 404 churn rather
than blind-swap the image — a real cdk-erigon migration needs new adapter
args and is tracked separately. Default image left pinned.

Context: spun up four parallel research passes over the 12 chains, then
re-verified every replacement myself against Docker Hub / GHCR (with the
OCI Accept header) / GAR / ECR-public tag APIs before touching code. Ran
versioncheck per chain — all 11 now resolve with no registry error,
polygon-zkevm drops out. Build, vet and adapter tests green. ~2h total.
zkevm-node is archived; Polygon mainnet zkEVM operators now run cdk-erigon
(an Erigon fork). The prior commit only dropped version tracking — this
actually migrates the adapter to the new client:

- image -> ghcr.io/0xpolygon/cdk-erigon:v2.64.2, VersionPolicy re-added
- config rewritten to cdk-erigon hermez-mainnet yaml (datadir /data, http
  on 8545 with eth/debug/net/trace/web3/erigon/zkevm apis, externalcl,
  l2-chain-id 1101, sequencer https://zkevm-rpc.com, datastreamer
  stream.zkevm-rpc.com:6900, canonical L1 contract addresses)
- ContainerArgs: --config=/config/hermezconfig.yaml plus
  --zkevm.l1-rpc-url=$(L1_RPC_URL); image ENTRYPOINT is cdk-erigon so flags
  append cleanly. L1 URL still defaults to http://ethereum:8545 via env.
- resources bumped to 8 CPU / 16Gi / 2Ti for a mainnet zkEVM node

Context: pulled the canonical hermezconfig-mainnet.yaml from the upstream
cdk-erigon repo, traced how the operator mounts ConfigTemplate (/config,
read-only) and applies ContainerArgs/Env in internal/controller, and
confirmed the image entrypoint from its Dockerfile. Build, vet, adapter +
controller tests green; versioncheck --chain polygon-zkevm resolves
cdk-erigon with no error. Datastreamer/sequencer endpoints are the public
Polygon ones — worth a live re-sync check before prod. ~1.5h.
@tazhate tazhate changed the title fix(registry): repoint 11 moved node repos, drop polygon-zkevm tracking fix(registry): repoint 12 moved node repos (+migrate polygon-zkevm to cdk-erigon) Jun 14, 2026
@tazhate
tazhate merged commit e9c0636 into master Jun 14, 2026
0 of 9 checks passed
@tazhate
tazhate deleted the fix/moved-repos-batch-12 branch June 14, 2026 10:39
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.

1 participant