release(v1.36.21): C-Chain EVM plugin EVM_VERSION v1.104.9 -> v1.104.9-hotfix.2

Flag-day image. Node binary builds from the v1.36.17 tag (d83191e286) — byte-identical
to v1.36.17, NO proposervm/consensus churn from main (v1.36.18/.19 excluded). The ONLY
change vs v1.36.17 is the baked luxfi/evm C-Chain plugin (vmID mgj786NP…):
v1.104.9-hotfix.2 = deployed+proven v1.104.9 (geth v1.17.12; G4 execution unchanged) +
startup RLP-import consensus-refresh + idempotency guard. Supersedes v1.36.20 (which
built hotfix.1, missing the audit's blocking idempotency guard). GOWORK off by
construction (no go.work in repo; plugin builds from an isolated /tmp/evm clone).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
This commit is contained in:
zeekay
2026-07-16 11:11:03 -07:00
co-authored by Hanzo Dev
parent d83191e286
commit 8e6102feea
+1 -1
View File
@@ -265,7 +265,7 @@ RUN . ./build_env.sh && \
# and EVERY EVM chain (C + L2s hanzo/zoo/pars/spc, all mgj786) fails to
# initialize. The api bump is code-free for plugins (chains v1.7.4->v1.7.5
# adopted it with a go.mod-only diff), so v1.104.9 = v1.104.8 + api alignment.
ARG EVM_VERSION=v1.104.9
ARG EVM_VERSION=v1.104.9-hotfix.2
ARG EVM_VM_ID=mgj786NP7uDwBCcq6YwThhaN8FLyybkCa4zBWTQbNgmK6k9A6
# the pinned evm go.mod may pin a dead luxfi/upgrade pseudo-version
# (v1.0.1-0.20260603055252-f51810805436 — commit pruned from origin). Heal it to