Reserves and attestation
The Reserves dashboard proves each asset's circulating supply from Bitcoin and compares it with your attested reserves. Auditors read the same data through the auditor API, regulators get read-only access, and any divergence raises an alert.
Open Issuance › Reserves.
#The dashboard
| Figure | Where it comes from |
|---|---|
| Circulating | Recomputed from Bitcoin at every block, independently of SQRL's records, with the block height shown |
| Attested reserves | Your reserve attestation feed, with the time of the latest attestation |
| Coverage | Attested reserves divided by circulating supply |
| Divergence alert | Whether supply and reserves differ beyond your tolerance, and when it was last checked |
Below the strip, each asset shows circulating supply against its cap and attested reserves against supply, with its reconciliation status.
#Divergence alerts
When circulating supply and attested reserves differ by more than your tolerance, SQRL Enterprise raises an alert and notifies the compliance role. The alert and its resolution are recorded in the audit log.
#Auditor API
Select Auditor API to issue read-only credentials to your auditor. They read the same circulating supply, attestations and history that the dashboard shows.
#Regulator access
Select Regulator access to give a regulator a read-only view of the Reserves dashboard for the assets you choose.
Key takeaway
Circulating supply is a fact on Bitcoin, not a number in SQRL's database. Coverage compares that fact with your attested reserves at every block, and anyone you authorise can check it.