Illustrative figures — backend integration in progress. Not yet live reserve data.
All checks passing
Not a snapshot. A continuous record.
Most proof of reserve is one number, once. We check the vault against every customer balance every 15 minutes, and publish every single result — including any that fail.
Coverage · last 90 days—now
90 days agohover the line to read any daytoday
Coverage is vault gold ÷ gold customers own. The gold dashed line at the bottom is 100% — the point where every gram in the vault is already spoken for. Anything above it is spare metal. It has not been touched once in 90 days.
8,640
consecutive checks passed
90
days without a breach
—
lowest coverage in that window
Gold in the vault
0g
Owned by customers
0g
Spare cover —Coverage —
The heartbeat
96 checks per day · 90 days
Each bar is one day. Its height is that day's lowest coverage — the worst moment, not the best. Tap any bar to see the vault as it stood that day.
90 days ago45 days agotoday
check passed — covered selected day headroom above the 100% line
watch the book grow and coverage fall toward 100%
The vault, that day
1 cell = 1 g
One thousand cells, always. Bright gold is metal a customer owns, dim gold is metal we hold unsold, empty is metal not in the vault on that date. The box never grows — the cell does.
—Covered
Held in custody
—
Owned by customers
—
Unallocated
—
Coverage
—
Scale · 1 cell = 1 g
See it at scale:
How it works
Target architecture
Phase 2 — not live today
Where this is going: the gold is counted where it sits, that count is attested on-chain by an oracle we do not control, and the attestation sits insidethe mint path — so supply cannot outrun reserve even if we wanted it to. Today's live mechanism is the 15-minute reconciliation above.
Figure 1 — the gram-for-gram circuitasset & token flowwritten to the public logthe loop closing
Attested reserve
10,748.925g fine
Token supply
10,748.925AAUG
● 1 : 1 locked
Step 1 of 6
—
Why continuous, not a photograph
The usual way
A reserve figure published once a quarter, or a ratio that reflects one instant. The published criticism of this is well known: a gap between checks is a gap you can dress. It tells you nothing about the 89 days you didn't look.
What we publish instead
Every check, kept. The claim is not “we were covered when we looked” — it is “we were covered at every one of 8,640 consecutive checks, and here they all are.” A failed check would appear on this page too, as a gap in the row above.
What stands behind each number
Continuity is only as good as the figures being compared. Here is the basis of each, stated plainly.
Gold owned by customersSum of all balances on our ledger — double-entry, append-only
MeasuredContinuous
Custodian reconciliationEach balance compared against the custodian's own record
MeasuredEvery 15 min
Gold held in custodyOur custodian exposes per-customer records but no vault total, so we state it
DeclaredDaily
Independent attestationQuarterly, by an accounting firm — the standard for gold-backed products
Being arrangedNone yet
Bar serials and assay certificatesNot disclosed to us by the custodian
Not availableNot claimed
CustodianDigital gold is outside SEBI's remit; IBJA operates the sector framework
Vaulting provider · IBJA SRO compliant
What this does not prove
Continuity is not existence.8,640 passing checks prove our records and our custodian's records agreed at every one of them. Neither set of records is a physical count of metal.
The custody figure is declared by us. Until an independent attestation is published, no third party has confirmed it. That is the gap this page is most trying to close.
Custody is concentrated. A single vaulting provider holds all of the metal. A failure there is not diversified away.
Digital gold is not a regulated instrument in India and carries none of the protections attaching to securities.
Transaction log
24 events
Everything the platform does, in one list — gold loaded into custody, buys, sells, SIP installments, lease activity, account events and every solvency check. Filter by kind, and switch the last column between the reference we use today and the transaction hash each row will carry on-chain.
Look up a transaction
Paste the id from a purchase, sale, SIP installment or vault load and we will show you the record and its reconciliation state.