fix(registry): repoint 12 moved node repos (+migrate polygon-zkevm to cdk-erigon)#11
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
versioncheckflagged 12 chains whoseVersionPolicypointed 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.kava-labs/kavakava/kava:v0.28.2-goleveldbseiprotocol/seidghcr.io/sei-protocol/sei:v6.5.2dymensionxyz/dymdghcr.io/dymensionxyz/dymension:4.0.1solanalabs/agaveanzaxyz/agave:v3.1.14(Anza org)coredao/core-chainghcr.io/coredao-org/core-chain:1.0.22metisprotocol/l2gethmetisdao/l2geth:v0.3.9taikoxyz/taiko-gethus-docker.pkg.dev/evmchain/images/taiko-geth:v2.5.0mantanetwork/op-gethpublic.ecr.aws/i6b2w2n6/op-geth:7.1.0plasma-next/nodeghcr.io/plasmalaboratories/plasma-consensus-public:0.15.0bobanetwork/op-gethop-gethGAR:v1.101702.2hashkeychain/hashkey-gethop-gethGAR:v1.101702.20xpolygonhermez/zkevm-node(archived)ghcr.io/0xpolygon/cdk-erigon:v2.64.2— migrated clientpolygon-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:
hermez-mainnetyaml (http 8545 witheth/debug/net/trace/web3/erigon/zkevm,externalcl, l2-chain-id 1101, sequencerhttps://zkevm-rpc.com, datastreamerstream.zkevm-rpc.com:6900, canonical L1 contract addresses)ContainerArgs:--config=/config/hermezconfig.yaml --zkevm.l1-rpc-url=$(L1_RPC_URL)(image ENTRYPOINT iscdk-erigon); L1 URL still defaults tohttp://ethereum:8545via envConfig values taken from the upstream
hermezconfig-mainnet.yamlexample. The datastreamer/sequencer endpoints are the public Polygon ones — worth a live re-sync check before prod.Other notes
op-gethGAR image (likebase/optimism).-goleveldbsuffix; dymension/core/plasma/manta-pacific publish bare semver (nov) — patterns adjusted.Verification
Acceptheader) / 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