chore: record arc v3.1 deployment (DEC-1841)

[clemsos]

Records the arc (chain 5042) v3.1 deployment in addresses.json

• RelayRouter 0xe6B730e58088884704CDF11cbE95c224d4D34154, RelayApprovalProxy 0x5A0fA369d634f49c76B08dC6C299800C1a2aF977 — the canonical v3.1 cancun addresses; owner() confirmed as 0x463cB782c8dd0a1887b77336DfF74D60F006F56E on-chain.
• Deployment funding note: Arc gas is native USDC; CCTP transfers to Arc were stuck (Circle-side attestation outage), so the deployer was funded by direct transfer.
• Contracts are NOT source-verified yet: Arc's explorer exposes no verification API and the chain is not on Etherscan v2 or sourcify. To be done when their explorer opens up.

With this, v3.1 is live on 58 of 59 target chains (syndicate dropped — chain dead).

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This change updates the Arc (chain ID 5042) V3.1 deployment registry with a new Cancun router and approval-proxy address pair. The registry contains exactly one Arc entry, and the changed router/proxy values are correctly paired in that entry.

T-Rex validation blocked

Live contract verification could not be completed because the RPC_URL_ARC credential/configuration is missing, and the discovered Arc QuickNode endpoint returned HTTP 401 Unauthorized. As a result, the new addresses' runtime bytecode and contract identity could not be confirmed on chain.

Confidence Score: 5/5

No merge-blocking defect was found in the registry change, but operational confidence in the recorded deployment addresses requires a live Arc RPC confirmation before relying on them.

No verified or publishable defect remains. The exact Arc entry, uniqueness, and updated address pairing were checked successfully; only the external on-chain identity check was unavailable.

Files Needing Attention: deployments/v3/addresses.json should be checked against an authenticated Arc RPC to verify runtime code and contract identity at the new router and approval-proxy addresses.

T-Rex Logs

What T-Rex did

• An executable validation program compared the Arc entry in the parent and updated registries and confirmed that the updated router/proxy pairing is recorded at lines 938-939.
• It then attempted chain-5042 eth_chainId and eth_getCode requests for both address pairs to observe deployed bytecode and contract identity.
• The chain requests could not complete because RPC_URL_ARC was absent and the Arc QuickNode endpoint returned HTTP 401 Unauthorized.
• Source locations for the affected Arc entries were identified at deployments/v3/addresses.json:938-939 (relayRouter and relayApprovalProxy), indicating a potential deployment-registry integrity issue.
• Evidence from before-change and after-change validation outputs and the exact entry check was collected to support reviewer inspection of the state and the blocked RPC attempt.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore: record arc v3.1 deployment" | Re-trigger Greptile}