Files
proxmox/docs/11-references/CW_TOKENS_AND_NETWORKS.md
defiQUG 7ac74f432b chore: sync docs, config schemas, scripts, and meta task alignment
- Institutional / JVMTM / reserve-provenance / GRU transport + standards JSON
- Validation and verify scripts (Blockscout labels, x402, GRU preflight, P1 local path)
- Wormhole wiring in AGENTS, MCP_SETUP, MASTER_INDEX, 04-configuration README
- Meta docs, integration gaps, live verification log, architecture updates
- CI validate-config workflow updates

Operator/LAN items, submodule working trees, and public token-aggregation edge
routes remain follow-up (see TODOS_CONSOLIDATED P1).

Made-with: Cursor
2026-03-31 22:31:39 -07:00

5.0 KiB

cW* Tokens and Networks

Purpose: Single reference for all compliant wrapped tokens (cW*) and the networks where they are defined or deployed.

Source of truth: config/token-mapping-multichain.json (cToCwSymbolMapping), smom-dbis-138/script/deploy/DeployCWTokens.s.sol, and smom-dbis-138/.env (for recorded addresses).


1. All cW* tokens and deployability

All 12 cW* tokens are deployable via DeployCWTokens.s.sol (env flags DEPLOY_CWUSDT=1, DEPLOY_CWEURC=1, etc.; default all 1). Set DEPLOY_*=0 to skip a token.

cW* Token Deploy script Networks deployable (script) Deployed on (addresses in .env)
cWUSDT Yes 1, 25, 56, 137, 100, 43114, 8453, 42161, 10 All 9 chains (Mainnet, Cronos, BSC, Polygon, Gnosis, Avalanche, Base, Arbitrum, Optimism)
cWUSDC Yes 1, 25, 56, 137, 100, 43114, 8453, 42161, 10 All 9 chains
cWEURC Yes 1, 25, 56, 137, 100, 43114, 8453, 42161, 10 BSC, Polygon, Gnosis, Avalanche, Base, Optimism (Mainnet/Cronos/Arbitrum: deploy failed nonce/gas)
cWEURT Yes Same Same as cWEURC
cWGBPC Yes Same Same
cWGBPT Yes Same Same
cWAUDC Yes Same Same
cWJPYC Yes Same Same
cWCHFC Yes Same Same
cWCADC Yes Same Same
cWXAUC Yes Same Same
cWXAUT Yes Same Same

2. Network names (chain ID)

Chain ID Network name
1 Ethereum Mainnet
10 Optimism
25 Cronos
56 BSC (BNB Chain)
100 Gnosis Chain
137 Polygon
43114 Avalanche C-Chain
8453 Base
42161 Arbitrum One

Chains 42220 (Celo) and 1111 (Wemix) are in the token-mapping file for c*→cW* mapping but are not in the current deploy-tokens-and-weth-all-chains-skip-canonical.sh chain list for cW* deployment. 651940 (ALL Mainnet) is env-validation only; no cW* deploy from this repo.


2.1 Bridge support status

Chain(s) Bridge / receiver Bridge code mints cW*? Notes
43114 (Avalanche) Dedicated AVAX cW bridge 0x635002c5fb227160cd2eac926d1baa61847f3c75 Yes Proven live for the dedicated non-prefunded cUSDT -> cWUSDT corridor. Treat this as a chain-specific exception, not blanket proof for every cW destination chain.
Generic public-chain WETH receiver set (1, 25, 56, 137, 100, 43114, 8453, 42161, 10) CCIPRelayBridge (Mainnet), CCIPWETH9_BRIDGE_* (others) No Current suite is WETH-only; ccipReceive only transfers the received token. Granting MINTER/BURNER to these addresses allows DeployCWTokens to run but does not enable cross-chain mint until the receiver is extended or a dedicated cW* receiver (e.g. TwoWayTokenBridgeL2) is deployed. See CW_BRIDGE_APPROACH.md and CW_BRIDGE_TASK_LIST.md.
After Phase B or C Extended bridge or TwoWayTokenBridgeL2 / CCIPReceiverCW Yes (when implemented) Per CW_BRIDGE_APPROACH.md, Option 2 (dedicated receiver) is chosen; deploy TwoWayTokenBridgeL2 or equivalent per chain and point CW_BRIDGE_<CHAIN> to it for cW* mint/burn.

3. How to deploy cWUSDT / cWUSDC

  1. Bridge addresses: CW_BRIDGE_ADDRESS is left as default (zero). Per-chain CW_BRIDGE_<CHAIN> are set in smom-dbis-138/.env from the deployed bridge suite (Mainnet: CCIPRelayBridge; other chains: CCIPWETH9_BRIDGE_, or a dedicated cW receiver such as the proven AVAX cW bridge). That contract receives MINTER_ROLE and BURNER_ROLE when deploying cW; only a dedicated cW-capable receiver enables mint-on-receive.
  2. Run with --deploy-cw:
    cd smom-dbis-138 && ./scripts/deployment/deploy-tokens-and-weth-all-chains-skip-canonical.sh --deploy-cw
    
    Or deploy to a single chain (e.g. BSC):
    CW_BRIDGE_ADDRESS=0x... forge script script/deploy/DeployCWTokens.s.sol:DeployCWTokens \
      --rpc-url "$BSC_RPC_URL" --chain-id 56 --broadcast --private-key "$PRIVATE_KEY" --legacy
    
  3. Set CWUSDT_<CHAIN>, CWUSDC_<CHAIN> in .env from the script output, and update config/token-mapping-multichain.json addressTo for the corresponding Compliant_USDT_cW / Compliant_USDC_cW entries.

4. References