proxmox/docs/07-ccip/RECOMMENDED_COMPLETION_CHECKLIST.md

# Recommended Completion Checklist

**Last Updated:** 2026-02-16  
**Purpose:** Operator checklist to complete all recommended improvements from [MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md](MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md).  
**Full consolidated list (all next steps + remaining TODOs):** [NEXT_STEPS_AND_REMAINING_TODOS.md](../00-meta/NEXT_STEPS_AND_REMAINING_TODOS.md).  
**Run completable mapper tasks + see operator checklist:** `./scripts/run-remaining-mapper-tasks.sh`

---

## High priority

### 1. Wemix (1111) token addresses

- [x] **Scan checked (2026-02-16):** [scan.wemix.com/tokens](https://scan.wemix.com/tokens) fetched; WWEMIX at `0x7d72b22a74a216af4a002a1095c8c707d6ec1c5f`. [WEMIX_TOKEN_VERIFICATION.md](WEMIX_TOKEN_VERIFICATION.md) updated with scan check; our mapping uses WETH `0x5adc...` (wrapped Ether).
- [ ] Operator: Confirm WETH, USDT, USDC on scan and with Tether/Circle/Wemix; if different official addresses exist, update `config/token-mapping-multichain.json` and WEMIX_TOKEN_VERIFICATION.md.
- [x] **Validation:** Run `bash scripts/run-remaining-mapper-tasks.sh` (runs `validate-config-files.sh` + on-chain check + prints operator checklist). Once operator has confirmed Wemix addresses, no further change needed; note in multichain JSON is "Operator: verify on scan.wemix.com before production".

**Ref:** [WEMIX_TOKEN_VERIFICATION.md](WEMIX_TOKEN_VERIFICATION.md), [MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md](MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md) § Gaps (Wemix token addresses).

---

### 2. Gnosis, Celo, Wemix — CCIP bridges (config-ready → ✅)

- [ ] Confirm [Chainlink CCIP supported networks](https://docs.chain.link/ccip/supported-networks) include Gnosis (100), Celo (42220), Wemix (1111). If any chain is not supported, skip that chain.
- [ ] **Per chain (Gnosis, Celo, Wemix):**
  - [ ] Set RPC_URL, CCIP Router address (from CCIP directory), LINK token address, WETH9/WETH10 addresses (or deploy), and deployer private key with native gas (xDAI / CELO / WEMIX).
  - [ ] From `smom-dbis-138/`: run `forge script script/deploy/bridge/DeployWETHBridges.s.sol:DeployWETHBridges --rpc-url "$RPC_URL" --broadcast -vvvv` (or equivalent per chain).
  - [ ] Record deployed CCIPWETH9Bridge and CCIPWETH10Bridge addresses.
- [ ] **On Chain 138:** Add each new chain as destination on CCIPWETH9_Bridge and CCIPWETH10_Bridge (`addDestination(selector, receiverBridge)`). Use selectors: Gnosis `465200170687744372`, Celo `1346049177634351622`, Wemix `5142893604156789321`.
- [ ] **On each new chain:** Add Chain 138 as destination on the new bridges (`addDestination(CHAIN138_SELECTOR, chain138Bridge)`).
- [ ] Fund each new bridge with LINK (e.g. ~10 LINK per bridge).
- [ ] Update env / docs with new bridge addresses.

**Ref:** [CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md](CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md).

---

## Medium priority

### 3. Token-aggregation / UIs using multichain mapping

- [x] **Done:** Token-aggregation exposes `GET /api/v1/token-mapping?fromChain=&toChain=`, `GET /api/v1/token-mapping/pairs`, `GET /api/v1/token-mapping/resolve?fromChain=&toChain=&address=` (uses `config/token-mapping-loader.cjs` when run from monorepo).
- [x] **Done:** Bridge UIs / Snap: `GET /api/v1/bridge/routes` now returns `tokenMappingApi` (basePath, pairs, resolve); Snap has `get_token_mapping` RPC (fromChain, toChain, address for resolve). REST_API_REFERENCE documents token-mapping for bridge UIs.
- [x] **Done:** Token-mapping API documented in token-aggregation README and REST_API_REFERENCE.

**Ref:** [MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md](MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md) § Recommended (wire token-aggregation).

---

### 4. LINK support on Mainnet relay bridge

- [ ] Choose **Option A** (extend CCIPRelayBridge to accept LINK) or **Option B** (deploy separate LINK receiver). See runbook.
- [ ] Implement contract changes and deploy (or deploy LINK receiver).
- [ ] Fund the bridge (or LINK receiver) with Mainnet LINK.
- [ ] In `config/token-mapping.json`, set `relaySupported: true` for the LINK token entry.
- [ ] Update [TOKEN_MAPPING_AND_MAINNET_ADDRESSES.md](TOKEN_MAPPING_AND_MAINNET_ADDRESSES.md) and [CCIP_BRIDGE_MAINNET_CONNECTION.md](CCIP_BRIDGE_MAINNET_CONNECTION.md) to state LINK is accepted.

**Ref:** [RELAY_BRIDGE_ADD_LINK_SUPPORT_RUNBOOK.md](RELAY_BRIDGE_ADD_LINK_SUPPORT_RUNBOOK.md).

---

## Low priority

### 5. AddressMapper on other chains (e.g. Cronos)

- [x] **Cronos done:** Deployed at `0x6F521cd9FCF7884cD4E9486c7790e818638e09Dd`; `config/smart-contracts-master.json` → `chains["25"].mapper` and `contracts.Address_Mapper` updated.
- [ ] For other chains: from `smom-dbis-138/`, run **DeployAddressMapperOtherChain** (set RPC to target chain, e.g. CRONOS_RPC), then add deployed address to `config/smart-contracts-master.json` for that chain (`mapper` and `contracts.Address_Mapper`).

**Ref:** [OPTIONAL_DEPLOYMENTS_START_HERE.md](OPTIONAL_DEPLOYMENTS_START_HERE.md) §A, [MAPPER_COVERAGE_BRIDGES_AND_LIQUIDITY_POOLS.md](MAPPER_COVERAGE_BRIDGES_AND_LIQUIDITY_POOLS.md).

---

### 6. DODO PMM on Chain 138

- [ ] Deploy DODOPMMIntegration on Chain 138 (env: DODO_VENDING_MACHINE_ADDRESS, COMPLIANT_USDT_ADDRESS, COMPLIANT_USDC_ADDRESS). Set `CHAIN_138_DODO_POOL_MANAGER`, `CHAIN_138_DODO_VENDING_MACHINE` in env after deploy.
- [ ] Create cUSDT/cUSDC and related pools (e.g. `createCUSDTUSDTPool`, `createCUSDCUSDCPool`) when design is ready.
- [ ] Document deployed addresses and pool IDs in [LIQUIDITY_POOLS_MASTER_MAP.md](../11-references/LIQUIDITY_POOLS_MASTER_MAP.md).

**Ref:** [OPTIONAL_DEPLOYMENTS_START_HERE.md](OPTIONAL_DEPLOYMENTS_START_HERE.md) §B, [LIQUIDITY_POOL_CONTROLS_RUNBOOK.md](../03-deployment/LIQUIDITY_POOL_CONTROLS_RUNBOOK.md).

---

### 7. Mainnet trustless stack (LiquidityPoolETH, InboxETH, BondManager, etc.)

- [ ] Deploy Lockbox138 on Chain 138; deploy Mainnet stack (InboxETH, BondManager, ChallengeManager, LiquidityPoolETH) per [OPTIONAL_DEPLOYMENTS_START_HERE.md](OPTIONAL_DEPLOYMENTS_START_HERE.md) §C.
- [ ] Configure Lockbox138↔InboxETH, fund liquidity; update env and docs with Mainnet trustless addresses.

**Ref:** [OPTIONAL_DEPLOYMENTS_START_HERE.md](OPTIONAL_DEPLOYMENTS_START_HERE.md) §C, [OPTIONAL_FUTURE_DEPLOYMENTS_RUNBOOK.md](../03-deployment/OPTIONAL_FUTURE_DEPLOYMENTS_RUNBOOK.md).

---

## Summary

| Item | Priority | Status |
|------|----------|--------|
| Wemix token addresses in multichain JSON | High | ☐ Operator |
| Gnosis, Celo, Wemix CCIP bridges deploy + config + fund | High | ☐ Ops / runbook |
| Token-aggregation / UIs use multichain mapping | Medium | ☑ Done (API + bridge response + Snap get_token_mapping) |
| LINK support on Mainnet relay | Medium | ☐ Runbook |
| AddressMapper on other chains | Low | ☑ Cronos done; others as needed |
| DODO PMM on 138 | Low | ☐ |
| Mainnet trustless stack | Low | ☐ |

---

## References

- [MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md](MAPPER_GAPS_DEPLOYMENTS_AND_IMPROVEMENTS.md)
- [MAPPER_COVERAGE_BRIDGES_AND_LIQUIDITY_POOLS.md](MAPPER_COVERAGE_BRIDGES_AND_LIQUIDITY_POOLS.md)
- [CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md](CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md)
- [RELAY_BRIDGE_ADD_LINK_SUPPORT_RUNBOOK.md](RELAY_BRIDGE_ADD_LINK_SUPPORT_RUNBOOK.md)
- [OPTIONAL_FUTURE_DEPLOYMENTS_RUNBOOK.md](../03-deployment/OPTIONAL_FUTURE_DEPLOYMENTS_RUNBOOK.md)
- [LIQUIDITY_POOL_CONTROLS_RUNBOOK.md](../03-deployment/LIQUIDITY_POOL_CONTROLS_RUNBOOK.md)