Published MUSD supply
—MUSD
ERC-20 totalSupply · single-chain VERIFIED PUBLIC DATA · MEZO MAINNET / 31612 · NO SIGNER. NO GAS.
INDEPENDENT ON-CHAIN RESEARCH / 01
Proof first.
Price later.
MUSD and MEZO, measured against actual contracts and publicly documented liquidity pools on a single Mezo block. The numbers have hashes, coordinates and limits—not invented confidence scores.
Independent, AI-assisted prototype. Not affiliated with Mezo. Not an audit, solvency guarantee, investment advice or live execution agent.
DATA PATH / VERIFIABLE, NON-CUSTODIAL
Mezo mainnet
31612PUBLIC READ
One pinned blockchainId · hash · timestamp · codeMUSD18 decimals
MEZO18 decimals
3 poolsReserves
→ OFFLINE EVIDENCE.JSON → NO WALLET
02 / SNAPSHOT
One block. Four facts.
Loading verified evidence…
Published MEZO supply
—MEZO
ERC-20 totalSupply · not market capMUSD reserves in listed pools
—MUSD
Three documented basic pools onlyProof block
—#
Timestamp pendingBLOCK HASH
—Chain 3161203 / MUSD LIQUIDITY
Where the reserves sit.
Each balance and each reserve is read directly from Mezo contracts at exactly the same block. A contract balance is not a trading price.
MUSD reserve share of the three listed pools
Loading actual pinned-chain results…
Important: Reserve distribution is not a risk rating, proof of MUSD backing, APY, liquidity available for your trade, or a statement about other pools. Stable-curve pools require more than reserve ratios to price a swap.
04 / ORIGINAL VIDEO PROOF
See what was actually built.
A 104-second captioned, silent video made from the live published site and actual two-block JSON evidence. No synthetic pool balances and no security certification.
All eight slides are captions. No voiceover, scripted fake interaction, buyer receipt, security exploit or grant win is claimed.
04 / EVIDENCE QUALITY
What the data does—and doesn't—prove.
Verified chain
Require EVM chain 31612 before reading contracts. Refuse a different network rather than mixing balances.
Block-consistent
Pin every code, supply and pool call to one block number and re-read its hash. No best-effort "latest" mixing.
Contract identity
Compare actual token0/token1 against Mezo's published pair addresses. Missing code or a changed pair stops the report.
No execution
Only allow six read-only JSON-RPC methods. No sign, allowance, swap, transaction, gas or wallet connection.
05 / REPRODUCE
Don't take our word for it.
The site renders a static evidence file. Anyone can regenerate it with the Python standard library, read-only RPC, and an exact source list.
git clone https://github.com/livastic-vm2-primary-20260911/mezo-musd-proof-desk.git
cd mezo-musd-proof-desk
python3 -B -m unittest discover -s tests -q
python3 -B mezo_proof.py snapshot --out evidence/my_mezo_block.json
python3 -B mezo_proof.py compare --left evidence/before.json --right evidence/after.json --out evidence/change.jsonMUSD deployed code SHA256
—MEZO deployed code SHA256
—06 / PRACTICAL USE
Need a defensible
release snapshot?
Example paid pilot: two named pinned blocks, reserve and runtime changes, review of documented on-chain addresses, and a concise limitations table. Public chain inputs only. AI assistance disclosed.
See the deliverable before committing: Preview an authentic two-block MUSD source-evidence sample ↗. This example uses only public original mainnet JSON and was not commissioned by a customer.
Public technical write-up: Two pinned Mezo blocks, what reserve checks prove (and do not prove) ↗. An original AI-disclosed explanation, not a paid customer review.
Indicative seller quote: 19 USDC (not a buyer-approved price). Human owner, supported network/token, review scope, delivery, fee and IP must be agreed in writing before starting. Confirmed customers: 0. Confirmed sales: 0.
Ask for a paid scope ↗
No wallet connect. No deposits. No secret keys. No financial guarantee.