**Purpose:** Single list of all tokens and networks where tokens **can be minted** (or otherwise credited) to the deployer address for funding PMM liquidity pools and bridges. Use this to fund all operator/LAN-only items (add liquidity, CCIP bridges, etc.).
| **All other chains** | 1, 56, 100, 137, 10, 42161, 8453, 43114, 42220, 1111, 651940 | — | Acquire via wrap, bridge, or DEX (see § Acquire) |
---
## 1. Chain 138 — Owner mint (all compliant tokens)
On **Chain 138**, the deployer is **owner** of all compliant token contracts deployed by this repo. Each has `mint(address to, uint256 amount) public onlyOwner`. Mint to deployer by calling `mint(deployerAddress, amount)` from the deployer EOA.
### 1.1 Token addresses and decimals (Chain 138)
| Symbol | Contract address | Decimals | Use for |
| **WETH** | `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2` | No (standard wrap) | Wrap native ETH: send ETH to WETH contract and call `deposit()` (or use a wrapper script). |
| **LINK** | `0xb7721dD53A8c629d9f1Ba31a5819AFe250002b03` | Depends (mock vs canonical) | If Chain 138 LINK is a mock with `mint`, call `mint(deployer, amount)`. Otherwise acquire via bridge or CCIP. |
---
## 2. Cronos (Chain 25) — D-WIN W tokens (MintController)
D-WIN W tokens (USDW, EURW, GBPW, AUDW, JPYW, CHFW, CADW) on **Cronos** are **ISO4217WToken** contracts. Minting is done via **MintController**, which requires:
- Caller has **MINTER_ROLE** on the MintController.
- Token is **approved** in the controller (`isApprovedToken[token]`).
- **Reserve oracle** and **compliance guard** allow the mint (reserve ≥ new supply).
If the deployer (or an EOA you control) is the admin of the MintController and has MINTER_ROLE, you can mint to the deployer by calling:
**Note:** You must have the MintController address for Cronos, have MINTER_ROLE, and have updated the reserve oracle so that `canMint(token, amount)` returns true. If the D-WIN system on Cronos is operated by another party, request a mint to the deployer from them.
---
## 3. Tokens that must be acquired (not minted to deployer)
These are needed for liquidity pools and bridges but **cannot** be minted by the deployer; they must be obtained by wrap, bridge, or DEX.
### 3.1 By network
| Network | Chain ID | Tokens needed for pools/bridges | How to get |
For **CCIP bridges** (138 ↔ Mainnet, 138 ↔ Gnosis/Cronos/Celo/Wemix, etc.), the **bridge contract** on each chain must hold **LINK** to pay fees. The deployer does not mint LINK on public chains; you:
1. Acquire LINK on the target chain (e.g. from Mainnet and bridge, or DEX on that chain).
2. Transfer LINK from the deployer to the **bridge contract address** (e.g. `cast send ... transfer(bridgeAddress, amount)`).
Recommended: **~10 LINK per bridge** for initial operations. See [CONFIG_READY_CHAINS_COMPLETION_RUNBOOK](../07-ccip/CONFIG_READY_CHAINS_COMPLETION_RUNBOOK.md) § Fund bridges with LINK.
### 3.3 Official USDT / USDC on Chain 138 (PMM pools)
PMM pools **cUSDT/USDT** and **cUSDC/USDC** use an “official” USDT/USDC pair on Chain 138. If that pair is a separate contract (e.g. bridged or canonical), the deployer cannot mint it; acquire from a bridge or use the compliant side only. If the “official” address is set to cUSDT/cUSDC for testing, then mint cUSDT/cUSDC as in §1.
---
## 4. Suggested mint order for liquidity and bridges
1.**Chain 138 — Compliant tokens**
Mint cUSDT and cUSDC (and optionally cEURC, cEURT, etc.) to the deployer in the amounts needed for:
- [ADD_LIQUIDITY_PMM_CHAIN138_RUNBOOK](../03-deployment/ADD_LIQUIDITY_PMM_CHAIN138_RUNBOOK.md): base/quote for the three PMM pools (cUSDT/cUSDC, cUSDT/USDT, cUSDC/USDC).
- Use [check-deployer-balance-chain138-and-funding-plan.sh](../../scripts/deployment/check-deployer-balance-chain138-and-funding-plan.sh) to see current balances; mint additional so that half of (current + minted) can be allocated to liquidity per [DEPLOYER_WALLET_FUNDING_PLAN_PMM_POOLS](DEPLOYER_WALLET_FUNDING_PLAN_PMM_POOLS.md).
2.**Chain 138 — WETH**
Ensure deployer has enough native ETH, then wrap the portion needed for WETH-denominated use (e.g. future pools or bridge).
3.**Chain 138 — LINK**
If LINK on 138 is mintable (mock), mint to deployer for local testing. For production, acquire LINK and send to the deployer or directly to bridge contracts as needed.
4.**Cronos — D-WIN W**
If you operate MintController and reserve, mint USDW, EURW, etc. to the deployer for Cronos-side liquidity or testing.
5.**Other chains**
Acquire native gas and LINK (and any USDT/USDC) per §3; then run add-liquidity and fund-ccip-bridges scripts from the operator/LAN runbooks.
---
## 5. Quick reference — mint commands (Chain 138)
```bash
# Load env (from smom-dbis-138 or repo root with RPC_URL_138 and PRIVATE_KEY)
# (Repeat for cEURT, cGBPC, cGBPT, cAUDC, cJPYC, cCHFC, cCADC, cXAUC, cXAUT with their addresses from §1.1)
```
---
## 6. Tokens the deployer deployed on other chains
For a list of **token contracts** the deployer wallet deployed on blockchains **other than 138** (Cronos D-WIN W, WETH9/WETH10 on L2s), see [TOKENS_DEPLOYER_DEPLOYED_ON_OTHER_CHAINS](TOKENS_DEPLOYER_DEPLOYED_ON_OTHER_CHAINS.md).
---
## 7. References
| Document | Purpose |
|----------|---------|
| [TOKENS_DEPLOYER_DEPLOYED_ON_OTHER_CHAINS](TOKENS_DEPLOYER_DEPLOYED_ON_OTHER_CHAINS.md) | Tokens deployer deployed on other blockchains (Cronos, L2s) |
| [TOKEN_CATEGORIES_CANONICAL](TOKEN_CATEGORIES_CANONICAL.md) | Token categories and symbols |
