[Khrafts]

Syncs the fork with Recon-Fuzz/safe-utils (we were 1 ahead, 3 behind) and re-expresses our chain support against the new API.

This is a port, not a merge

Upstream 34a5fbf removed the per-instance urls and multiSendCallOnly mappings and replaced them with pure functions driven by safe-core-sdk's network list. 7f16d67 wrote to fields that no longer exist, so the one conflict resolved in upstream's favour and its chains were rebuilt against the new API.

Chains

Resolved through the third-party override in getApiKitUrl, each host confirmed 200 on /api/v1/about/:

chainId	chain	host
1329	Sei	transaction.sei-safe.protofire.io
1868	Soneium	transaction-soneium.safe.protofire.io
2288	Moca	transaction-mocachain.safe.protofire.io
4114	Citrea	transaction.safe.citrea.xyz
25363	Fluent	api.safe.global/tx-service/fluent

• Soneium's host is corrected from trx-soneium, which does not resolve.
• Mantra (5888) is dropped — no reachable host on any candidate name.
• Monad, 0G and Plasma need no entry; they arrive with upstream's SDK sync.
• Fluent is served by Safe's own infrastructure but is absent from safe-core-sdk, so it needs the override rather than a getNetworkShortName slug — adding a slug not in the SDK would fail SafeDifferentialTest.

MultiSend

Sei and Soneium are in safe-deployments, so they join SUPPORTED_THIRD_PARTY_CHAIN_IDS and are covered by the differential test.

Moca, Citrea and Fluent have no safe-deployments record. Their v1.4.1 canonical was confirmed by eth_getCode against each chain's public RPC and is pinned in a dedicated test instead. The FFI helper was deliberately not taught to author those addresses — that would assert only that two hand-edited files agree, while reading green.

Citrea is why this cannot default to the v1.3.0 canonical: 0x40A2… is not deployed there, only v1.4.1 0x9641….

Verification

forge test — 29/29 pass. Consuming repo (evm-m-suite-deployment) builds clean against this branch with no call-site changes; initialize, proposeTransaction(s), getNonce and sign all kept their signatures.

Note

PR #2 should be closed rather than merged: its diff targets the removed mappings, and its Citrea entry maps to the v1.3.0 canonical that is not deployed on that chain — batched proposals would have built cleanly and failed at execution. Its reachable chains are all included here.

Rise (4153), Nexus (3946) and Mantra (5888) remain unsupported — tracked separately.

[Khrafts]

Split into two stacked PRs so the upstream sync and our own changes review separately:

• Merge upstream/main (no local changes) #4 — Merge upstream/main, no local changes, tree byte-identical to upstream (+399 in Safe.sol)
• Add M0 chain support against the new config API #5 — Add M0 chain support, stacked on Merge upstream/main (no local changes) #4 (+58 / -3 total)

Same end state: #5's tree is identical to this branch's HEAD. Closing in favour of those.