You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(polygon-zkevm): migrate from archived zkevm-node to cdk-erigon
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.
0 commit comments