Dara DocsReferenceDeployment
Mainnet canary plan
Stage 39. Mainnet starts small and grows only after each step passes. Prerequisites: every item of
LAUNCH_CHECKLIST.md up to "UAT sign-off".
1. Asset creation ceremony (brief §147)
Verify, then create (../operations/ISSUER_OPERATIONS.md §1), then record in ../stellar/ASSET_REGISTRY.md:
| Verify | How |
|---|---|
| Asset code, unit definition | GOLD (decided 2026-10-31); unit definition approved in writing (Q-04); home domain chosen and serving stellar.toml |
| Issuer address | Generated on the offline machine during the ceremony; recorded |
| Signers and weights | One human signer = 10, AUTH = 1 (issuer 1 / 10 / 10); the signer confirms their own public key in person and has tested the encrypted backup (../security/KEY_MANAGEMENT.md §1a) |
| Thresholds | 1 / 20 / 30; any single signer removable without losing a threshold |
| Authorization flags | AUTH_REQUIRED, AUTH_REVOCABLE, AUTH_CLAWBACK_ENABLED (clawback decision: ../operations/CLAWBACK_POLICY.md) |
| Treasury | COLD (the same signer, 10 / 10 / 10) and HOT layouts; GOLD trustlines; 8 AUTO + 3 GOV channels |
| Network passphrase | Public Global Stellar Network ; September 2015 |
| Home domain and metadata | stellar.toml served and correct before activation |
| Key backups | Each signer's backup verified |
| Signer availability | The signer reachable with the signing laptop for the whole canary window |
| Approval | Signed ceremony plan |
2. Canary steps
| Step | Size | Pass when |
|---|---|---|
| Backing snapshot | Very small (e.g. 10 g) | EFFECTIVE |
| ISSUE | Equal to the backing | Supply = backing on Dara Scan; reconciliation PASS |
| REFILL | Small hot float | HOT on-chain = ledger |
| Internal operator customers | 2–3 staff acting as customers | Accounts sponsored, trustlines authorized |
| BUY, SELL, TRANSFER | Smallest amounts | Exact to the rial; COMPLETED |
| Freeze / unfreeze, clawback drill | One each | On-chain state as expected |
| Reconciliation | Every run for 7 days | PASS throughout |
| Monitoring and security | Alerts reach receivers; no unexplained movement | No CRITICAL incident |
3. Growth
Raise limits stepwise (backing, hot float, channel count, daily limits, customer admission) only after a clean week
at the previous step, with the product owner's written approval each time. Size channels for the expected peak
(../testing/evidence/SECURITY_PERF_20261030.md: ~1 settlement per channel per ledger).
4. Stop conditions
Any CRITICAL incident, any reconciliation failure, or any customer-visible error at the canary stage stops growth until resolved and reviewed.