Proof, not exposure.

01

Reserve Seal: solvency for everyone

1. 1

   The ledger arranges all account commitments in a Merkle sum tree. Each parent holds the sum of its children, so the root commits to total liabilities, L.

2. 2

   Dragon Reserve opens the root to reveal L, the total grams owed, and nothing else.

3. 3

   The custodians sign the current bar list. The fine gold in that list is the reserve, R.

4. 4

   The Seal publishes L, R, the bar list hash, the tree root and the custodian signatures, and proves that L is no greater than R.

5. 5

   The Seal is written into the ledger block, verified by Dragon Net, and checkpointed on public chains at L5.

The liability side updates with every block that changes a balance. The reserve side refreshes with each custodian attestation, at least daily, and is reconciled against physical audits.

02

Inclusion Seal: proof that you are counted

1. 1

   Your app receives the path from your leaf to the published root.

2. 2

   It opens your own leaf with your balance and blinding factor, then recomputes the path.

3. 3

   It checks that the root matches the latest Reserve Seal and that the Seal is anchored on public chains.

The siblings on the path are commitments, so the path reveals nothing about other holders. Leaves are reshuffled every epoch, so paths cannot be linked over time. Every transaction also returns a signed receipt: if your app ever fails this check, that receipt proves you were left out.

03

Holder Seal: one fact, shared on your terms

• Facts at launch: balance of at least a chosen amount; that amount held since a chosen date; verified holder, without identity.

• How it is built: the app produces a zero-knowledge proof that some leaf in a recent root belongs to your key and satisfies the fact. The verifier learns the fact and its time, not the amount and not which leaf.

• Safe to share: each Seal names its audience and an expiry, so a forwarded Seal fails and an old one lapses. Two Seals from the same holder cannot be linked unless the holder chooses.

• How it travels: as a link or QR code, verified on a public page or through an open API.

04

Audit Seal: exactly what a named party may see

• A holder can grant a viewing key scoped to one account and one period, for an accountant or a lender.

• Where the law requires it, Dragon Reserve discloses specific records to a regulator under that legal process.

• Every disclosure is logged on the ledger, so access itself can be audited later.