Two Mezo blocks, identical reserves: what a read-only MUSD check actually proves

Description and use

Shows that unchanged MUSD and MEZO values across two blocks confirm data consistency but do not prove backing or security.

Problem

Assessing the reliability of a stablecoin dashboard when on-chain values remain unchanged across consecutive blocks.

Outcome

The checker demonstrates that MUSD totalSupply, MEZO totalSupply, and MUSD reserves in three selected pools are unchanged between blocks 12709282 and 12709416, but this does not confirm stablecoin backing, liquidity, or security.

Workflow

• 1. Pin target block number and hash to avoid inconsistent reads.
• 2. Verify chain ID matches expected mainnet (31612).
• 3. Read token0/token1 to confirm expected token pairs.
• 4. Retrieve getReserves and balanceOf for MUSD at the same block.
• 5. Record ERC‑20 decimals and totalSupply.
• 6. Reject any missing code, malformed results, or hash mismatches.
• 7. Generate a static JSON artifact for public inspection.

Evidence

The checker pinned contract reads to two different mainnet blocks on chain ID 31612:

Source

For both samples, these on-chain values were unchanged:

Source

Runtime-bytecode SHA-256 fingerprints for the sampled contracts and pools were also unchanged between these blocks.

Source

The original repository contains 40 offline regression tests across the collector and sample-report generator.

Source

That separation—evidence observed versus economic inference unproven—is the point of the exercise.

Source