Treasury / Vault
Transparency
Explore MDC’s production contracts, their allocations and current on-chain state. Every live value belongs to one verified block snapshot.
49M is the formal production allocation, not current circulating supply.
STATUS UNAVAILABLE · Awaiting first verified snapshot
- Snapshot Block
- —
- Snapshot UTC
- —
- RPC Source
- —
- Last Updated
- —
Refreshes every 60 seconds while this page is visible. Values older than 120 seconds are marked STALE.
RPC reads only · Chain ID 1 · No account access required
Releasable does not mean automatically distributed. availableToReleaseNow means the maximum amount that can currently be released under the contract rules and current Vault balance.
Production instances
H1 — H9How to read this page
Treasury funds remain governed by the corresponding Safe. Vault Treasury address is immutable. Safe signer / threshold configuration is not necessarily immutable.
Funding status compares Vault balance, totalReleased and allocation. A smaller balance after a recorded release is not automatically a funding shortfall. Unknown values are shown as “—”, never as zero.
Source labels reflect the approved explorer verification record, independently of live reads. H1, H2, H7, H8 and H9: Verified Source. H3–H6: Similar Match / Verification pending re-verification.
This page checks source/runtime/parameter conformity. It does not certify security. Fixed parameters are checked against the canonical production record and cached in memory. Every refresh rechecks the complete runtime before reusing those immutable values; dynamic state is read at the new snapshot block.
Snapshot and source details
All calls in a refresh use one numbered Ethereum block. The block hash is checked again before publishing the complete snapshot. A failed refresh retains the previous whole snapshot; it never combines old and new values. Latest blocks may subsequently be reorganized.
Canonical configuration: contracts/treasury-vesting/spec/PRODUCTION-REGISTRY.md. ABI getters are extracted from the locked production artifacts. Runtime bytes include immutables and metadata.
Public RPC availability and browser access policies can interrupt reads. A transport failure may try the other listed public endpoint with a new full snapshot. Identity or integrity failures stop the refresh.