# Implementation Coordination with Transcript 540ae663
**Purpose:** Coordinate all implementations with the work completed in agent transcript **540ae663** (PMM/DEX routing, tokens, GRU registration, cW* deployment, Chain 138 deployments, and related scripts/docs). Use this document so that:
- Implementations do not duplicate or conflict with what was already done.
- The same scripts, env vars, addresses, and flows are used where applicable.
- The [DBIS Rail and Project Completion Master](DBIS_RAIL_AND_PROJECT_COMPLETION_MASTER_V1.md) task list reflects completed vs remaining work.
When implementing from [DBIS_RAIL_AND_PROJECT_COMPLETION_MASTER_V1.md](DBIS_RAIL_AND_PROJECT_COMPLETION_MASTER_V1.md), use this mapping. **Done** = completed in transcript 540ae663. **Partial** = partly done; finish per Master. **Open** = not done in transcript.
| C5 | Partial | Blockscout verification run in transcript; update CONTRACT_ADDRESSES_REFERENCE and LIQUIDITY_POOLS_MASTER_MAP as needed. |
| C6 | Open | Reconcile Multicall vs Oracle Aggregator at documented address. |
### D. Project deployment — Optional
| Task | Status | Coordination note |
|------|--------|-------------------|
| D1 | Open | EnhancedSwapRouter not deployed; deploy when Uniswap/Balancer on 138. |
| D2 | Open | Trustless stack (InboxETH, BondManager, etc.) not deployed. |
| D3 | Open | CCIP other chains per DEPLOYMENT_ORDER. |
| D4 | Open | LINK relay support per runbook. |
| D5 | Partial | cWUSDT/cWUSDC deployed on 9 chains; runbook and mapping in place; other cW* (cWEURC, etc.) and edge pools per pool-matrix still optional. |
| D6–D7 | Open | R1–R24 and full recommendations list. |
### Token deployment (TODOS_CONSOLIDATED T1–T7)
| Task | Status | Coordination note |
|------|--------|-------------------|
| T1 DeployCompliantFiatTokens | Done | 10 tokens deployed on 138; optional cCADT in script (commented). |
| T2 Optional cCADT | Partial | Uncomment in script and re-run when needed. |
| T3–T7 | Open / Partial | cAUSDT, ACADT, cW* (cWUSDT/cWUSDC done; others mapping only), D-WIN W on 138/651940, vault ac*/vdc*/sdc* per TOKEN_CONTRACT_DEPLOYMENTS_REMAINING. |
### DBIS Rail (A, B)
All DBIS Rail tasks (A1–A9, B1–B7) remain **open** in the transcript: no DBIS Rail contracts (RootRegistry, ParticipantRegistry, SignerRegistry, SettlementRouter, GRU_MintController) were implemented; owner mint on c* not locked to router. Implement per Completion Master and [Audit Readiness Results](DBIS_RAIL_AUDIT_READINESS_RESULTS_V1.md).
---
## 3. How to Use This for New Work
1.**Before changing deployment or token flow:** Check §1 for what’s already done; use the same scripts and env (Core RPC IP:port, run-all-next-steps-chain138.sh, set-dotenv-c-tokens-and-register-gru.sh, run-cw-remaining-steps.sh).
2.**Before adding a new “completion” task:** Check §2; if marked Done or Partial, update the Completion Master or this doc when you finish the remainder.
3.**When implementing DBIS Rail (A/B):** Follow the Completion Master and Spec/Rulebook/Threat Model; ensure new rail contracts and mint path do not conflict with existing GRU registration or c* usage (e.g. UniversalAssetRegistry, RegisterGRUCompliantTokens, explorer GRU policy).
4.**Addresses and .env:** Use CONTRACT_ADDRESSES_REFERENCE, CHAIN138_TOKEN_ADDRESSES, and smom-dbis-138/.env as populated by the transcript’s scripts; do not overwrite with placeholders.
---
## 4. Document Control
| Field | Value |
|-------|-------|
| Title | Implementation Coordination with Transcript 540ae663 |
| Version | 1 |
| Status | Active |
| Related | [DBIS_RAIL_AND_PROJECT_COMPLETION_MASTER_V1.md](DBIS_RAIL_AND_PROJECT_COMPLETION_MASTER_V1.md), [DBIS_RAIL_AUDIT_READINESS_RESULTS_V1.md](DBIS_RAIL_AUDIT_READINESS_RESULTS_V1.md), [DEPLOYMENT_ORDER_OF_OPERATIONS](../03-deployment/DEPLOYMENT_ORDER_OF_OPERATIONS.md) |
