# Source To CEX Execution Plan

- Generated: `2026-04-17T15:11:49Z`
- Strategy frame: Chain 138 inventory -> canonical bridge -> Mainnet normalization -> CEX handoff
- Mainnet funding posture: `dual-rail` via `cWUSDC, cWUSDT`

## Operator Table

| Source Asset | Bridge Output | Preferred Normalization | CEX Deposit Asset | Fallback Path |
|---|---|---|---|---|
| `cUSDC` | cWUSDC on Ethereum Mainnet | cWUSDC -> USDC | `USDC` | bridge cUSDC -> cWUSDC, then use best available Mainnet USDC normalization route with capped public-pool usage |
| `cUSDT` | cWUSDT on Ethereum Mainnet | cWUSDT -> cWUSDC -> USDC | `USDC` | use direct cWUSDT -> USDT only for tiny packets or explicit override; otherwise route through USDC normalization |
| `LP:cUSDT/cUSDC` | cUSDT and cUSDC after LP withdrawal | withdraw LP -> prefer cUSDC feeder -> bridge -> cWUSDC -> USDC | `USDC` | withdraw LP, split outputs by best feeder path, avoid forcing whole ticket through direct USDT sink |
| `cWUSDC` | none | cWUSDC -> USDC | `USDC` | split size, cap pool usage, treat on-chain conversion strictly as deposit preparation |
| `cWUSDT` | none | cWUSDT -> cWUSDC -> USDC | `USDC` | direct USDT path is last-resort and tiny; practical size should flow through USDC-normalization |

## Notes

- `cUSDC` is the cleanest same-day corridor feeder.
- `cUSDT` should usually normalize through USDC until direct USDT depth improves.
- Stable LP claims are feeder-preparation assets.
- Mainnet `cWUSDC` and `cWUSDT` are immediate in mechanics, but not deep enough to absorb large tickets on-chain.