QUSD Transparency Summary
One page, for anyone. Every figure here was read from public chain data when this page was built, and every one of them can be reproduced from a terminal without asking QVTX for anything. This is not an attestation and no auditor has issued one.
This replaces a draft headed “Attestation Summary Report” that named Hashlock Security as the auditor and marked every wallet and contract “Audited, Secure”. Hashlock reviewed Circle’s FiatToken contracts, not QUSD — verified against the live contract, where currency(), masterMinter(), pauser(), updateBlacklister() and updateRescuer() are all absent. Naming a firm that did not review us is a statement about them as much as about us. There is no attestation to summarise, so this summarises measurement instead.
1. Backing
What Stands Behind The Coin- QUSD is backed 1:1. The backing is carried in the mint record itself rather than in a pool or a float, and a coin is never issued past it — a deposit with no registered fiat behind it is refused outright.
- Anchored on chain: $11,000,000,000.00. Read live from chain 42000 —
committedValue(bytes8), selector0x4058baa5, registry0x7ca575a297f3276934098f9d13fa5b027a5cab9b, head03a151d702f5b734. Anyone can repeat that call. - What is not evidenced here: a custodian bank balance. There is no live bank feed, so no figure is shown. The draft this replaces stated “Fiat Reserves: Held in regulated custodian banks” as a verified line.
2. Supply, Per Contract
Never Summed- BNB Smart Chain (chain 56): 0.250000 QUSD · 19,338 bytes of code
- Polygon (chain 137): 1,101,000,602.519078 QUSD · 19,338 bytes of code
- Base (chain 8453): 0.000000 QUSD · 19,338 bytes of code
- QVTX 42000 (chain 42000): 1,000,200,005.000000 QUSD · 19,338 bytes of code
- Arbitrum One (chain 42161): 0.000000 QUSD · 19,338 bytes of code
- The same contract address
0xb57bf3c50f20096723b46645f741f632aef220facarries identical bytecode on every one of these chains. Supply is reported per contract and never added together — summing them would double-count a bridge that does not exist. - XRP Ledger: QUSD is also natively issued by
rJqjwDAwuSVoppQkrwjJSPzXivspYxZ239, confirmed live on the validated ledger with rippling enabled. That issuance is separate and is never added to the EVM figures.
3. Liquidity, Honestly Sized
Measured- QuickSwap, chain 137: 1.393970 USDC of real depth. Reserve-versus-balance delta zero.
- PancakeSwap, chain 56: 3.937045 USDT of real depth. Reserve-versus-balance delta zero. This pool quotes a superseded QUSD contract, so a buyer there receives the deprecated token.
- Total real dollar depth: $5.33. That counts the stable side only; a DEX aggregator’s figure counts our own QUSD as dollars and roughly doubles it. Pool depth and backing are different things — the pools are a listing, not the reserve.
4. Audit Status
None, Stated Plainly- No attestation No auditor has reviewed these contracts. No firm is named here because none has looked.
- Not assessed No MiCA, AMLD6 or GDPR conformity is claimed. The draft this replaces asserted all three. No such assessment has been carried out.
- Does not exist There is no cross-chain bridge, so it cannot be audited or secure. The draft listed one as both.
- What an auditor would get on day one is published at
qusd.quantvestrix.io/attestation— the evidence we can produce, with every verification cell left blank because filling it is their work, not ours.
5. What Is Actually In Force
Built, Not Promised1
Reserve monitoring
Cached pool reserves are compared against the balance each pair actually holds, both legs, on demand. The delta is currently zero everywhere.
Cached pool reserves are compared against the balance each pair actually holds, both legs, on demand. The delta is currently zero everywhere.
2
An oracle that ignores the pools
The QUSD oracle returns exactly 1.00000000 and never reads pool spot price. At this depth spot is whatever the last trader left behind, which is why no system consumes it.
The QUSD oracle returns exactly 1.00000000 and never reads pool spot price. At this depth spot is whatever the last trader left behind, which is why no system consumes it.
3
A bug bounty
Open, with scope read from chain across contracts, wallet integrations and APIs.
Open, with scope read from chain across contracts, wallet integrations and APIs.
4
Published measurement
The pool audit, the risk disclosure, the community notice and this page are all rebuilt from live chain state, so none of them can drift from what is true.
The pool audit, the risk disclosure, the community notice and this page are all rebuilt from live chain state, so none of them can drift from what is true.
✓Everything above is either a number you can fetch yourself or a statement that something does not exist. Nothing here rests on trusting QVTX.
6. Check It Yourself
Reproducible- Full pool audit:
qusd.quantvestrix.io/audit - Risk disclosure:
qusd.quantvestrix.io/risk-disclosure - Plain-language notice:
qusd.quantvestrix.io/risk·/avis(EN/FR) - Live figures as JSON:
api-direct.quantvestrix.io/api/transparency/summary,/api/token/supply,/api/liquidity/poolsand/api/audits/summary/status. - Or skip us entirely: call
getReserves()on each pair andtotalSupply()on0xb57bf3c50f20096723b46645f741f632aef220faagainst any public RPC.