connecting to the API…
For The Auditor · Prepared 2026-09-30

QUSD Attestation Request Pack

Everything an auditor needs to begin, and nothing an auditor has concluded. Every verification cell is empty because filling it is the engagement. The evidence beneath each section is read from public chain data and can be reproduced without asking QVTX for anything.

No Auditor EngagedEvidence AttachedVerification Blank By Design

The template this replaces shipped with every verification cell already ticked — fiat reserves, token supply, reserve ratio, all four wallets and all three contracts — plus “Multisig confirmed”, “Audit Status: Secure” and a statement of MiCA, AMLD6 and GDPR conformity, before any auditor had looked at anything. Three of those are measurably untrue today and are listed in section 7. A template that answers its own questions produces a false attestation by default, so this version answers none of them.

1. Header

Auditor Completes
  • Report title: QUSD Reserve & Wallet Attestation
  • Reporting period: — auditor to complete —
  • Auditor (firm, licence number): — auditor to complete —
  • Date of issue: — auditor to complete —
  • Audit type (full / limited / interim): — auditor to complete —
  • Networks in scope: XRP Ledger, BNB Smart Chain, Polygon, Base, Arbitrum, QVTX 42000 — six, not the two the template named

2. Reserve Verification

Evidence Attached
  • Fiat reserves — custodian bank balances: — auditor to complete —
    QVTX cannot evidence this line. No live custodian bank feed exists. Backing is carried in the mint ByteID rather than as a bank float, and a coin is never issued past it: the mint API refuses a deposit with no registered fiat behind it. An auditor confirming this line needs the institutions, not us.
  • Anchored treasury backing: $11,000,000,000.00, read live from chain 42000 — committedValue(bytes8) selector 0x4058baa5 on MasterRegistry 0x7ca575a297f3276934098f9d13fa5b027a5cab9b, head 03a151d702f5b734, 6 decimals. This is on-chain and reproducible; it is not a bank statement.
  • Token supply — per contract, never summed:
    • BNB Smart Chain (chain 56): 0.250000 QUSD · code 19,338 bytes · 0xb57bf3c50f20096723b46645f741f632aef220fa
    • Polygon (chain 137): 1,101,000,602.519078 QUSD · code 19,338 bytes · 0xb57bf3c50f20096723b46645f741f632aef220fa
    • Base (chain 8453): 0.000000 QUSD · code 19,338 bytes · 0xb57bf3c50f20096723b46645f741f632aef220fa
    • QVTX 42000 (chain 42000): 1,000,200,005.000000 QUSD · code 19,338 bytes · 0xb57bf3c50f20096723b46645f741f632aef220fa
    • Arbitrum One (chain 42161): 0.000000 QUSD · code 19,338 bytes · 0xb57bf3c50f20096723b46645f741f632aef220fa
    The template summed XRPL and Ethereum into one figure. Supply is reported per contract and never aggregated by ticker — adding them would double-count a bridge that does not exist.
  • Reserve ratio: — auditor to complete —
    Not asserted here. It is the quotient of the two lines above, and the first of them is the one QVTX cannot evidence.

3. Wallet Verification

Addresses Given, Conclusions Not
  • Treasury (EVM): 0x60D021B8949bFd0FB7ac0c695d9a389181D49eBd — verified: — auditor to complete —
    The template’s note said “Multisig confirmed”. It is not. Treasury signs with a single key, and that key’s material was exposed. This is the largest control gap in the estate and an auditor must be told it before starting.
  • XRPL issuer: rJqjwDAwuSVoppQkrwjJSPzXivspYxZ239 — verified: — auditor to complete —
    Rippling is enabled, which is what makes QUSD paths flow on that ledger.
  • XRPL operational: rEVSCgctdEJQRpn2eC4Uuu5AEvgpAZmG51 — verified: — auditor to complete —
  • Liquidity pool wallets: the pair contracts themselves, listed in section 4. Reserve-versus-balance reconciliation is attached there.
  • Cold storage / operational: — auditor to complete —
    The template pre-ticked “Cold storage verified” and “Admin fees reconciled”. Neither has been verified by anyone.

4. Liquidity Pools

Measured
  • QuickSwap, chain 137 0x763aff9d01fa6412ea762659d8c8896515434ce5
    Reserves 1.39118881 QUSD / 1.39397000 USDC. Reserve-versus-balance delta: zero on both legs. QUSD side is canonical.
  • PancakeSwap, chain 56 0xe848f417b7b91e381ccfedeba27ff2f6c4a1fa8c
    Reserves 4.09946280 QUSD / 3.93704503 USDT. Reserve-versus-balance delta: zero on both legs. QUSD side is superseded. This pool quotes the superseded contract; a buyer there receives the deprecated token.
  • Total real dollar depth: $5.33, counting the stable side only. The template called this line “Matches on-chain reserves ✓”. It does match — the delta is zero — but the figure it matches is small, and that is the material fact.

5. Smart Contract Integrity

Audit Status Blank
  • QUSD token 0xb57bf3c50f20096723b46645f741f632aef220fa, six networks — audit status: — auditor to complete —
    Identical 19,338-byte runtime bytecode on every EVM chain. Source verified on BscScan (contract QUSD, solc 0.8.30, 35,877 bytes): no imports, and no OpenZeppelin, ERC20, Ownable or SafeMath code — it is self-contained. Known defect: it answers TRUE to supportsInterface(0x80ac58cd).
  • XRPL issuance rJqjwDAwuSVoppQkrwjJSPzXivspYxZ239 — audit status: — auditor to complete —
    Native issued currency with trustline enforcement. There is no "XRPL liquidity pool contract" to audit; the XRPL books are ledger objects, not contracts.
  • Bridge contract — audit status: does not exist. The template listed a cross-chain bridge and pre-ticked it Secure. There is no bridge. The token is deployed separately per chain, which is exactly why supply is never aggregated.
  • Third-party AMM contracts (QuickSwap, PancakeSwap) — out of scope. They belong to their own programmes.

6. Compliance Statement

To Be Written By The Auditor
!The template supplied a finished statement: “The auditor confirms that QUSD reserves are fully backed by fiat assets held in regulated institutions… This attestation complies with MiCA, AMLD6, and GDPR standards.” No auditor wrote that, and a conformity claim against three regimes is not something the audited party drafts for its own auditor. The space is left empty.
  • What QVTX asserts, and stands behind: QUSD is backed 1:1; the backing is carried in the mint ByteID rather than a pool or a float; a coin is never issued past it.
  • What QVTX does not assert: that any auditor has confirmed the above, that fiat sits in a named regulated institution under a live feed, or that any regime’s requirements have been assessed.

7. Before You Start

Stated, Not Buried
  • High Multi-sig is not implemented. Treasury signs with one key and its material was exposed.
  • High A live pool quotes a superseded QUSD contract, so a buyer on that venue receives the deprecated token.
  • High Total pool depth is $5.33. Any trade of size executes nowhere near par.
  • Medium No custodian bank feed is evidenced. Two files described as a live feed contain zero entries.
  • Medium No bridge, and no mint/burn rate limiting. The only brake on issuance is the registered-fiat gate.
  • Medium The ERC-165 defect causes some explorers to file QUSD as an NFT collection.
✓Handing an auditor the problems on page one is cheaper than having them find them on page forty, and it is the only version of this document that is worth signing.

8. Signatures & Publication

Blank
  • Lead auditor: — auditor to complete —
  • Compliance officer: — auditor to complete —
  • Treasury manager: — auditor to complete —
  • Report hash (SHA-256): — auditor to complete — — computed over the finished report, by whoever signs it.
  • On-chain proof: — auditor to complete —
  • Transparency portal: the measured pages this pack draws on are published at qusd.quantvestrix.io/audit, /risk-disclosure, /risk and /avis, and the same figures are served at api-direct.quantvestrix.io/api/compliance/attestations, which currently returns an empty list.