# DBIS Rail and Project Completion Master — Status and Full Task List v1
**Purpose:** Single reference for (1) current project and deployment status and (2) the complete list of tasks to reach audit-ready DBIS Rail and full project completion — **including all optional items**.
**Companion:** [Audit Readiness Results v1](DBIS_RAIL_AUDIT_READINESS_RESULTS_V1.md), [Deployment Order of Operations](../03-deployment/DEPLOYMENT_ORDER_OF_OPERATIONS.md), [Complete Required/Optional/Recommended Index](../00-meta/COMPLETE_REQUIRED_OPTIONAL_RECOMMENDED_INDEX.md).
**Implementation coordination:** Align all implementations with [Implementation Coordination with Transcript 540ae663](IMPLEMENTATION_COORDINATION_WITH_TRANSCRIPT_540AE663.md). That transcript completed PMM/DEX (pools, DODOPMMProvider), 10 compliant fiat tokens on Chain 138, GRU registration for all 12 c*, UniversalAssetRegistry upgrade, cWUSDT/cWUSDC on 9 chains, and related scripts/docs. The coordination doc maps which tasks below are already done or partial.
| **Contracts (code)** | Not implemented | No DBIS_RootRegistry, ParticipantRegistry, SignerRegistry, SettlementRouter, GRU_MintController in repo. |
| **Mint path** | Gap | GRU/c* on 138 use owner mint (CompliantFiatToken, CompliantUSDT, CompliantUSDC). Rail requires router-only mint. |
| **Signer / ISO Gateway** | Documented only | Quorum (3-of-5, COMPLIANCE), EIP-712, accountingRef, isoHash defined in Spec/Rulebook; no on-chain signer registry or router. |
| **Validator layer** | Partial | QBFT documented; key segregation, multi-entity, monitoring, incident runbook to be confirmed in ops. |
| **Operator / Wave 0–3** | Partially done | NPMplus, backup, sendCrossChain, validation scripts; full Wave 2/3 and recommendations per index. |
| **Optional deployments** | Not done | EnhancedSwapRouter, trustless stack mainnet, CCIP other chains, cW* edge pools (Phase 4–5). |
| **Recommendations** | Many open | R1–R24; ~139 items in ALL_RECOMMENDATIONS_AND_IMPROVEMENTS_LIST; optional VLAN, HA, MetaMask/explorer. |
---
## Part 2 — Full Task List (Required and Optional)
Every task below is to be completed; optional items are explicitly marked so prioritization (required first, then optional) is clear.
---
### A. DBIS Rail — Required (audit readiness)
| # | Task | Evidence / reference |
|---|------|----------------------|
| A1 | Implement and deploy DBIS Rail contracts (RootRegistry, ParticipantRegistry, SignerRegistry, SettlementRouter, GRU_MintController) per [Technical Spec v1](DBIS_RAIL_TECHNICAL_SPEC_V1.md). | Spec §2.1, §6; [Audit Results](DBIS_RAIL_AUDIT_READINESS_RESULTS_V1.md) § Gap remediation. |
| A2 | Lock GRU/c* mint on Chain 138 to SettlementRouter only: revoke or remove owner mint for rail tokens; grant mint only to DBIS_GRU_MintController with Router as sole caller. | Audit Results §1; CompliantFiatToken.sol, CompliantUSDT, CompliantUSDC. |
| A3 | Add unit and integration tests: direct mint revert, EIP-712 and replay, quorum/category, pause, caps. | Audit Results §2, §5; Checklist §1, §2, §5. |
| B2 | Implement idempotency extension: allow resubmission of same messageId with duplicate-accepted event (or keep revert as default). | Spec §9; Rulebook. |
| B3 | Add periodic Merkle root of SettlementRecorded events for external proof exports / proof-of-reserves-style attestations. | Threat Model §3.C (recommendation); Spec. |
| B4 | Implement on-chain validator governance (rotation + emergency pause) or document operational governance and timelock path. | Spec §0, §3.2; Regulator Brief §2; Threat Model §3.E. |
| B5 | Publish DBIS Rail — Public Overview (2–3 page PDF) for business development and counterparties. | Prior conversation: optional, high signal. |
| B6 | Expand control mapping to full SOC 2 / ISO 27001–style matrix (control ID, control objective, evidence, owner). | [Control Mapping v1](DBIS_RAIL_CONTROL_MAPPING_V1.md); Checklist. |
| B7 | Commission independent code audit of DBIS Rail contracts after deployment. | Audit Results; institutional readiness. |
---
### C. Project deployment — Required (Chain 138 and verification)
| # | Task | Evidence / reference |
|---|------|----------------------|
| C1 | Ensure Phase 0 prerequisites: RPC 2101 writable, deployer funded, .env correct, POOL_MANAGER_ROLE, no stuck txs, forge build, test all contracts before deploy. | [DEPLOYMENT_ORDER_OF_OPERATIONS](../03-deployment/DEPLOYMENT_ORDER_OF_OPERATIONS.md) Phase 0. **Partial:** preflight, run-before-deploy-checks, test-all-contracts exist ([coordination](IMPLEMENTATION_COORDINATION_WITH_TRANSCRIPT_540AE663.md)). |
| C2 | Complete Phase 2 if not done: TransactionMirror, all three PMM pools, register c* as GRU; set addresses in .env. | DEPLOYMENT_ORDER_OF_OPERATIONS Phase 2. **Done** per [coordination](IMPLEMENTATION_COORDINATION_WITH_TRANSCRIPT_540AE663.md). |
| C3 | Complete Phase 3: DODOPMMProvider deploy and pool registration; token-aggregation env; optional liquidity and MCP allowlist. | DEPLOYMENT_ORDER_OF_OPERATIONS Phase 3. **Done** per [coordination](IMPLEMENTATION_COORDINATION_WITH_TRANSCRIPT_540AE663.md). |
| C5 | Run Blockscout verification: `./scripts/verify/run-contract-verification-with-proxy.sh`; update CONTRACT_ADDRESSES_REFERENCE and LIQUIDITY_POOLS_MASTER_MAP. | DEPLOYMENT_ORDER_OF_OPERATIONS Phase 6.2–6.3; R1–R3. |
| C6 | Reconcile Multicall vs Oracle Aggregator at `0x99b3511a2d315a497c8112c1fdd8d508d4b1e506` on explorer and document in CONTRACT_ADDRESSES_REFERENCE. | CONTRACT_ADDRESSES_REFERENCE note. |
---
### D. Project deployment — Optional (Phase 4–6 and beyond)
| D3 | CCIP other chains (Gnosis, Celo, Wemix): deploy WETH bridges per chain; add 138↔chain; fund LINK. | DEPLOYMENT_ORDER_OF_OPERATIONS Phase 4.3. |
| D4 | LINK on Mainnet relay: add LINK support per relay runbook. | DEPLOYMENT_ORDER_OF_OPERATIONS Phase 4.4. |
| D5 | Phase 5 — cW* edge pools: per-chain RPC/env; deploy or bridge cW* tokens; create and fund PMM pools per pool-matrix (11 public chains). | DEPLOYMENT_ORDER_OF_OPERATIONS Phase 5. **Partial:** cWUSDT/cWUSDC deployed on 9 chains; mapping and runbook in place ([coordination](IMPLEMENTATION_COORDINATION_WITH_TRANSCRIPT_540AE663.md)). |
| D7 | Optional: run full recommendations list (~139 items) per ALL_RECOMMENDATIONS_AND_IMPROVEMENTS_LIST; OPERATOR_READY_CHECKLIST for copy-paste commands. | [ALL_RECOMMENDATIONS_AND_IMPROVEMENTS_LIST](../00-meta/ALL_RECOMMENDATIONS_AND_IMPROVEMENTS_LIST.md); Phase 6.5. |
---
### E. Project operational — Optional (Wave 0–3 and infra)
| E8 | Schedule and install daily/weekly cron for maintenance (schedule-daily-weekly-cron.sh --install). | COMPLETE_REQUIRED_OPTIONAL_RECOMMENDED_INDEX. |
---
### F. Identity and chain metadata — Optional
| # | Task | Evidence / reference |
|---|------|----------------------|
| F1 | Update chain metadata so "DBIS Mainnet (Chain 138)" is the authoritative public identity (e.g. eip155-138.json, ChainList, explorer branding, token list name). | Regulator Brief; prior DBIS identity discussion. |
| F2 | Publish Regulator Brief (or Public Overview) as standalone PDF for examiners and counterparties. | Regulator Brief v1; optional Public Overview. |
---
## Part 3 — Suggested execution order
1.**DBIS Rail required (A1–A9):** Unblocks audit readiness; A1–A2 are prerequisites for A3, A7.
2.**Project deployment required (C1–C6):** Ensures Chain 138 and verification are current.
3.**DBIS Rail optional (B1–B7):** v1.5+ and institutional hardening as capacity allows.
4.**Project deployment optional (D1–D7):** Phase 4–6 and full recommendations.
