Dara DocsAdmin console
What each page does and who may request or approve.
The console is English-only for the MVP. Staff log in with a password and two-factor authentication. Every administrative and financial action is written to an append-only audit log.
The rule behind every high-risk action
The person who requests can't be the person who approves. The service and a database CHECK both enforce this.
flowchart LR R["Requested"] --> A["Approved by someone else"] R --> X["Rejected or expired"] A --> S["Awaiting signatures"] S --> E["Executed"] S --> F["Expired or failed"]
Actions with no on-chain signature, such as a backing change, stop at approval.
Pages
| Page | Use it to | Main roles |
|---|---|---|
| Overview | See supply against backing | All |
| Assets | Define assets, suspend or resume trading | Platform Admin |
| Reserves | Record and approve backing. An attestation counts for 35 days | Reserve Manager requests, Reserve Approver approves |
| Supply | Issue, burn and refill. These touch only the cold Treasury | Treasury Operator requests, Reserve Approver approves |
| Prices | Set the reference price. A large move needs a second approver, and a stale price closes trading for the asset | Treasury Operator |
| Cash | Record deposits and payouts. Deposits above the threshold need a second person, and payouts need the bank reference | Treasury Operators, each approving the other |
| Customers | KYC, freeze and unfreeze. Every action needs a reason | Compliance Officer. Unfreeze needs a second officer |
| Orders | Follow buys, sells and transfers | All operations roles |
| Clawbacks | Court orders and key recovery only | Two different Compliance Officers, then the signer |
| Signing | Review proposals and upload signatures | The human signer |
| Chain operations | Follow on-chain intents and attempts, and resolve stuck operations | Operations |
| System | See whether trading is open, and why. Any failed check closes it | All |
| Reconciliation | Run checks and handle findings. Checks with operations in flight are skipped, not failed | Reconciliation Operator |
| Ledger | Read the double-entry ledger | Finance, Auditor |
| Audit log | Read every recorded action | Auditor |
| Emergency | Act when funds or keys may be at risk | Platform Admin |
| Staff | Add staff. A different Platform Admin approves each account | Platform Admin, Security Admin |
Roles and limits in full: authority matrix.
Issuing GOLD, step by step
- Reserve Manager: on Reserves, record the backing with its attestation reference and date.
- Reserve Approver: approve it.
- Treasury Operator: on Supply, request the issuance. It can't exceed backing minus supply and pending issuance.
- Reserve Approver: approve it. A signing proposal is created, valid for 24 hours.
- Human signer: on Signing, verify and sign (how).
- System: submits it. When it applies, the cold Treasury grows and reconciliation checks the result.
When something goes wrong
| What you see | Go to |
|---|---|
| Trading closed | System, then the incident response guide |
| A reconciliation finding | Reconciliation, then its runbook. Findings are never auto-corrected |
| An order stuck | Orders, then Chain operations |
| Funds or keys at risk | Emergency |