These are the independent explorer’s computed figures from public Quantus chain data, not official Quantus project figures. We are not affiliated with or operated by the Quantus Network project. We have not submitted these figures to any aggregator on the project’s behalf.
Current finalized snapshot
Current supply figures require a successful, fresh snapshot. Use the plain-text endpoints below to retrieve them.
- Circulating · QTC
- Unavailable
- Total issued · QTC
- Unavailable
- Protocol maximum · QTC
- Unavailable
- Excluded pool · QTC
- Unavailable
Plain-number endpoints
- /supply/circulating — issued QTC outside the excluded vesting pool.
- /supply/total — Balances.TotalIssuance.
- /supply/max — MiningRewards.MaxSupply from runtime metadata.
Successful responses are HTTP 200 with Content-Type text/plain: one non-negative decimal number in QTC, followed by a newline. There are no thousands separators, ticker symbols, quotes, markup or exponent notation. Up to all 12 on-chain decimal places are retained; these endpoints do not round down to the four decimals used in the page display.
Inspect the computation snapshot for exact base-unit integers, finalized block hash and height, observation time, expiry, runtime version and exclusions. This explanatory JSON is separate from the three plain-number endpoints.
The circulating rule
Circulating = Balances.TotalIssuance − the vesting pallet account’s free and reserved balance, at the same finalized block. Methodology version 1, reviewed for Quantus runtime spec 152 on 11 September 2026.
This measures issued supply outside a known, undistributed protocol pool. It is a circulating-supply proxy, not a measurement of exchange liquidity or a guarantee that every included coin can be spent immediately. We use the chain’s issuance counter, not the sum of account balances, mining reward history, transfer volumes, unclaimed schedules or ZK-tree leaves. Those are different quantities and must not be added to issuance.
Every excluded account
Vesting pool (pallet account)
qzmviwoPJR19XovVwUYUoUKb2MoBygYgwYAevj5Br8JeunxW70x6d6f646c7176657374696e670000000000000000000000000000000000000000
This is the keyless PalletId-derived account whose bytes begin modlqvesting; the live Vesting.PalletId constant identifies it. Its coins remain in pallet custody until a pallet operation pays them out. The full live free-plus-reserved balance is excluded, including its account buffer and any additional funding, rather than a fixed genesis amount.
A schedule becoming claimable is not a transfer. Even an immediately claimable amount remains excluded while held in the pool. A finalized claim or other payout reduces the pool balance and increases this computed circulating supply, all else equal; funding the pool has the opposite effect. This deliberately conservative distribution rule follows settled on-chain balances, not an estimated unlock curve. It does not assert that all pool funds are time-locked. See current vesting schedules and releases.
Other protocol accounts and limits of the rule
The collector examines the complete finalized account sweep, not only the top 100. At review, the vesting pool was the only funded account beginning with the pallet modl prefix. No other funded module account is silently classified as circulating or automatically subtracted.
The configured TreasuryPallet.TreasuryAccount is qzjsuLN7Nhu4bjvmUbjSTr2ZTeZ7oRxXpQP9fdv6PcHUCRrVR (0x12d0296a85b56914dc8d29698974f07055e3ad82a7c40c6b0b38e15cb8c31cb7). It has no balance in the reviewed sweep, so there is no treasury amount to exclude. We do not infer its spendability from the name alone.
The MiningRewards/Wormhole minting sentinel is qzjUYyuN4L3HKmBPMxHvK2n8HYnaLZcQvLSQTgdwB2nQ1g2mc (0x0101010101010101010101010101010101010101010101010101010101010101). It marks mint-credit sources; it is not a funded reserve to subtract. ReversibleTransfers uses a pallet account as a scheduled-call origin, while multisig addresses are derived from their signer configuration; neither fact establishes an additional funded, unavailable pool.
A newly funded module account, treasury or minting sentinel stops publication pending a documented review. A changed treasury configuration or runtime version also stops publication. The reviewed exclusion list will be amended only with an on-chain reason, and every new excluded address will be named here.
Ordinary holders, miners, pool reward addresses, multisigs and vesting beneficiaries are not excluded merely because of their name, size or address appearance. We do not subtract their entire balances because of a reserve, freeze or pending operation: those restrictions do not establish an undistributed protocol reserve. This rule does not estimate lost keys, undisclosed ownership, private beneficial holdings or off-chain lockups. The snapshot reports aggregate reserved balances for inspection.
Finality, refresh and failure handling
The collector computes supply about once a minute from a complete Accounts generation and verifies issuance, runtime constants and the treasury setting at that exact finalized block. It follows live vesting pool changes without hardcoded balance or release amounts. The maximum is the on-chain MiningRewards.MaxSupply constant, currently 21,000,000 QTC.
The precomputed snapshot is cached in the collector; requests never call the chain. HTTP responses use Cache-Control: no-store, max-age=0 so a cache cannot keep returning a successful number after a failure. Account observations and the latest chain-head timestamp must be under 180 seconds old; an unchanged finalized snapshot expires after 600 seconds of observation. The finalized block’s own timestamp can be older because finality trails the head.
A missing, incomplete, corrupt, inconsistent or expired snapshot, failed verification, unreviewed protocol balance, zero circulating result, or stopped handler returns an error rather than a stale number or zero. The numeric endpoints use HTTP 503 with a plain-text error body, never a success-shaped substitute. Normal finalized supply may differ from newer unfinalized transactions.
Reproduce the calculation
Read the Accounts manifest and its complete generation of account records, then compare the supply snapshot’s block hash. At that block, read Balances.TotalIssuance and the vesting System.Account free and reserved fields; subtract only the named pool. Divide the exact integer results by 1012. Read MiningRewards.MaxSupply from that block’s runtime metadata for the maximum. Different snapshot generations must not be mixed.
The vesting pallet source describes its account derivation and payout transfers, and the runtime configuration identifies the protocol accounts. Live runtime metadata and finalized storage are the inputs to our figures. About this independent explorer.