0d29343941
- Added new deployment script references for Aave quote-push and treasury manager in .env.master.example. - Updated AGENTS.md to include information on GRU reference primacy versus public PMM mesh execution model. - Minor updates to various documentation files to reflect changes in policy and operational guidelines. Made-with: Cursor
2.6 KiB
Phase C — cW* Tokens and Edge Pools Runbook
Last Updated: 2026-03-04
Purpose: Execute Phase C of REMAINING_DEPLOYMENTS_FOR_FULL_NETWORK_COVERAGE: deploy or bridge cW* tokens and create/fund PMM edge pools on public chains for full SBS and arbitrage.
Prerequisites: Phase A (hub liquidity on 138) and Phase B (CCIP bridges + LINK) should be done or in progress.
C.1 Deploy or bridge cW* tokens per chain
Chains (current repo rollout scope): 1, 10, 25, 56, 100, 137, 42161, 42220, 43114, 8453, 1111.
Tokens (current pool-matrix): cWUSDT, cWUSDC, cWAUSDT, cWEURC, cWEURT, cWUSDW, cWGBPC, cWGBPT, cWAUDC, cWJPYC, cWCHFC, cWCADC, cWXAUC, cWXAUT.
Important update:
- the pool matrix now covers the full GRU Wave 1 wrapped set
- this closes the design/config gap for Wave 1 public liquidity
- it does not mark those pools live until addresses are written into
deployment-status.json
Steps: (1) Use cross-chain-pmm-lps config/chains.json and pool-matrix.json. (2) Deploy CompliantWrappedToken (cW*) per chain or use bridge; set addresses in deployment-status.json and smom-dbis-138/.env. (3) Ref: TOKEN_CONTRACT_DEPLOYMENTS_REMAINING §3, CW_DEPLOY_AND_WIRE_RUNBOOK.
C.2 Create and fund PMM edge pools per chain
Steps: (1) From pool-matrix poolsFirst (for example cWEURC/USDC, cWGBPC/USDT, cWXAUC/USDC), create DODO PMM or Uniswap pools per chain. (2) Add initial liquidity. (3) Record pool addresses in deployment-status.json chains[chainId].pmmPools. (4) Ensure token-aggregation/heatmap use deployment-status.
Use the deployment queue for the remaining operator breakdown:
bash scripts/verify/check-gru-v2-deployment-queue.sh
Ref: LIQUIDITY_POOLS_MASTER_MAP § Public-chain cW*, pool-matrix.json.
C.3 (Optional) Stabilization bot and peg bands
Run deviation watcher and peg-band config from cross-chain-pmm-lps when cW* and edge pools are live.
Policy: peg bands and bot behavior must follow reference-anchored GRU/FX rules (OMNL rate matrix, agreed oracles, reserve gates) — see GRU_REFERENCE_PRIMACY_AND_MESH_EXECUTION_MODEL.md. The mesh implements corridors; it does not replace institution-grade reference pricing.
Quick ref
- Pool matrix: cross-chain-pmm-lps/config/pool-matrix.json
- Deployment status: cross-chain-pmm-lps/config/deployment-status.json
- Recipe: cross-chain-pmm-lps/docs/06-deployment-recipe.md
- Reference primacy + mesh: GRU_REFERENCE_PRIMACY_AND_MESH_EXECUTION_MODEL.md