feat(chains): default to the v2.12 Portal and provers (ECO-2403)

[carlosfebres]

Summary

routes-cli builds intents that the production/staging solvers fill, so its per-chain Portal/prover defaults have to be on the generation the solvers run. eco-routes v2.12 (proven cancellation, ECO-2403) deployed under a new root SALT, and eco/eco-solver#1272 moves every solver deployment to it. This PR moves routes-cli's production defaults to v2.12 and drops the chains that have no v2.12 deployment (the same set the solver drops in its runbook §10.3).

This is an intent builder change: it replaces the old addresses and does not keep them alongside.

Merge order: merge only after every solver deployment this service targets has switched to v2.12 (eco/eco-solver#1272 §10.1). A solver can't fill an intent on the other generation.

Where these defaults are used

The normal publish path takes the source Portal, the prover and the destination Portal from the Eco API quote, so a quoted publish follows whatever generation the quoting solver serves. chains.config.ts is used for the manual fallback (quote fails → route.portal = the destination chain's configured Portal, prover auto-selected from the configured provers), --prover-type <name>, the portal prompt default, EvmPublisher when no Portal is passed, and the status/watch lookup when no quote is present. After the switch, the old defaults would publish unfillable intents through every one of those paths.

The 0x399D… "prod portal" decision

Ethereum, Optimism, Base, Arbitrum and Polygon had 0x399Dbd5D… labelled "prod portal", paired with LayerZero prover 0x0C4E3063…. They came in with #17 (LZ prover support). On eco-solver main that address appears only in helm/eco-solver/config/ephemeral.yaml (routes-ts 3.2 / ephemeral). The production and staging helm files use the fleet Portal 0xEC000064…. So the "prod" default already pointed at a Portal the production fleet doesn't serve, and it only worked through the quote path. On the #1272 branch every deployment, ephemeral included, goes to 0xEC000769…, so there's nothing left to target the old address. All five chains move to the v2.12 Portal. LayerZero is gone in v2.12, so each chain's prover default becomes the v2.12 HyperProver. With one common type (Hyperlane) between any two EVM chains, auto-selection in the manual fallback still works without a prompt.

What changed

• src/blockchain/chains.config.ts: V2_12_PORTAL / V2_12_HYPER_PROVER constants (one CREATE3 address on every v2.12 EVM chain).
  • Ethereum, Optimism, Arbitrum, Polygon: Portal 0x399D… → 0xEC000769…, prover LayerZero 0x0C4E… → Hyperlane 0xEC08fb46….
  • Base: same, plus Polymer 0xE3e4e6F2… → 0xEC0DeD08…. Polymer stays listed on Base only, the Tron-corridor endpoint, for the single-common-prover reason in the comment.
  • Arc: dedicated Portal 0xEC002CA1… → 0xEC000769…, HyperProver 0xec004Ab4… → 0xEC08fb46….
  • Tron: Portal TT6jKgnB… → TDYD42Vm…, Polymer TLvVHqZZ… → TU42qLG4…, still paired.
  • Removed BNB Smart Chain (56), Sonic (146), Celo (42220) and Ink (57073), none of which has a v2.12 deployment.
  • Unchanged: Ronin, HyperEVM, Unichain, World Chain, Plasma and Solana still carry no Portal/prover and rely on the quote, as before (Add Unichain, World Chain, Plasma, Celo, and Ink production chains #29). The development/testnet entries are unchanged too: v2.12 isn't deployed on any testnet and no fleet solver serves one.
• src/config/tokens.config.ts: removed the token entries for the four dropped chains (USDC on Sonic/Celo, USDT on Celo, USDT0/USDG on Ink) and the BSC-only bUSDC/bUSDT symbols.
• tests/blockchain/v2-12-mainnet-config.test.ts (new): pins the v2.12 Portal/provers per production chain and asserts that no production chain carries a pre-v2.12 Portal/prover or a LayerZero prover.
• tests/blockchain/arc-mainnet-config.test.ts: Arc now pins the shared v2.12 Portal/HyperProver.
• tests/blockchain/chains.config.test.ts, tests/config/tokens.config.test.ts, tests/cli/token-resolver.service.test.ts: dropped the Celo/Ink cases and added assertions that the four removed chains have no chain or token entry.
• tests/quote/quote.service.test.ts, tests/quote/gateway-quote.adapter.test.ts: quote-response fixtures moved to the v2.12 Portal/HyperProver. The adapter test's destination Portal keeps a different address on purpose, so the test can still tell tx.to apart from route.portal.
• tests/blockchain/evm-publisher.integration.test.ts, tests/integration/intent-publishing.test.ts, tests/integration/publish-non-interactive.test.ts: mocked Portal fixture 0x399D… → v2.12.
• tests/e2e/setup/anvil-helpers.ts: kept 0x399D… and added a comment. CI forks Base at FORK_BLOCK_NUMBER: 28000000, which predates the v2.12 Portal, so the address and the fork block have to move together.
• ARCHITECTURE.md: updated the production chain and token tables.
• .changeset/v2-12-portal-defaults.md: minor bump (user-facing default change plus removed chains).

Solana / Tron instruction compatibility

• Solana: routes-cli builds only the Portal fund instruction itself (plus an unused publish builder), from its vendored gen-1 IDL (src/commons/idls/portal.idl.ts). I diffed it against the gen-2 IDL vendored on the solver branch (src/modules/blockchain/svm/targets/idl/portal-v2.idl.ts). fund has the same discriminator, the same 7 accounts in the same order and identical FundArgs/Reward/TokenAmount/Bytes32 types. The only difference is that gen-2 marks payer writable. routes-cli always passes the same key as payer and funder, and funder is writable, so the compiled message is unchanged. publish, PublishArgs, Route and the IntentPublished/IntentFunded events are identical, and the vault PDA seed ("vault" + intent hash) is unchanged. The Solana program id comes from the quote or --portal-address, never from this config, so nothing is swapped under a gen-1 encoder. routes-cli doesn't build refund or close_fulfill_marker, the two instructions whose layout gen-2 changed. If someone later adds a separate fee payer, the vendored IDL's fund.payer needs writable: true.
• EVM/Tron: routes-cli calls only publishAndFund, via the EVM Portal ABI, including on Tron. The solver branch's v2.12 Portal ABI diff is additive only (cancellation), so publishAndFund is unchanged.

Validation

• pnpm -C <worktree> install --frozen-lockfile: ok
• pnpm typecheck: exit 0
• pnpm lint: 0 errors. The 30 warnings were already there before this change (no-unsafe-assignment in existing tests).
• pnpm format:check: all files pass
• pnpm test: 23 suites, 230 tests passed. That's the whole jest suite, since jest.config.ts excludes tests/e2e/.
• Not run: pnpm test:e2e (Anvil Base fork, needs live infra). Its Portal fixture is deliberately unchanged, see above.

Addresses verified on-chain 2026-09-29

• EVM Portal 0xEC000769A73b70e16f361a442292500b3BCf4A85: version() = "2.12.0" on Ethereum, Optimism, Base, Arbitrum and Polygon (public RPCs).
• HyperProver 0xEC08fb4647f3f50d1162a578d481266687C60fc5: PORTAL() = 0xEC000769… on the same five chains.
• PolymerProver 0xEC0DeD087Ee6C55991Bb4D4567ca1134c5353Ed6: PORTAL() = 0xEC000769… on Base.
• Tron Portal TDYD42VmbScmqYkqG97aLgRN74Dqq9Fuva (hex 0x27262594c6088865ac3e7ac20f401af3bd379b1b): version() = "2.12.0". PolymerProver TU42qLG4ixTZ56jYFVAke32DmTcEkiU4zv: PORTAL() = 0x27262594… (TronGrid).
• Arc (5042) was not re-queried here, because its RPC is IP-allowlisted. The shared-address deployment was verified on-chain in the #1272 cut-over brief.

Owed / not in this PR

• Nothing runtime. routes-cli has no deployed environment, and users pick up the new defaults when they upgrade the CLI.
• README.md documents PORTAL_ADDRESS_ETH/_BASE/_OPTIMISM/_SOLANA overrides that no source reads (already stale, left as is).

Related: eco/eco-solver#1272

https://claude.ai/code/session_01PVso5BBb8ZQGg6jBtTh4MG

[linear-code]

ECO-2403

[eco-ai-app]

Overview

This PR updates the default Portal and Prover addresses across all production chains to the eco-routes v2.12 generation and removes chains (BNB Smart Chain, Sonic, Celo, Ink) that lack a v2.12 deployment. The QA agent verified that comprehensive test coverage was added, including a new pinning test suite for the v2.12 addresses and explicit assertions for the removed chains. The review team identified no issues or regression risks.

QA & Test Coverage

No issues found in this domain.

Web Security

Skipped: not applicable to this PR — PR updates blockchain contract addresses and configuration; no web security concerns.

Blockchain Security

No issues found in this domain.

Performance

Skipped: not applicable to this PR — PR is a configuration update with no performance implications; no algorithmic or computational changes.

Stats

Metric	Value
Reviewers	4
Successful	2
Skipped	2
Failed	0
Total findings	0
Cross-domain	0
Tokens (in / out)	52257 / 1276

---

Automated review by Eco's specialized review team. Architecture, business logic, and correctness remain with the human reviewer.