QTC on NEAR (qtc.omft.near) is minted only against QTC locked on Quantus by the bridge. So its supply can never legitimately exceed the QTC that exists outside the vesting pot: issuance less the pot balance, about 220,624 QTC at Quantus height 160,866 (2026-10-03). Supply above that would mean the bridge minted unbacked QTC, or that one of the two reads is wrong. Either way it is the most important thing the market page could say, and today nothing checks it.
QTC on NEAR Intents was announced for 2026-10-05, 17:00 in the poster's timezone ("48 Hours", @QuantusNetwork, 2026-10-03 17:00). This is the lite version of #27's phase 2 (the full custody cross-check needs the bridge's Quantus addresses), and it should be in place before the first mint.
What
The listing poll, every 5 minutes, also reads issuance outside the pot. It uses the same storage items and the same subtraction the network page uses (Balances::TotalIssuance less the balance at the Vesting::PalletId account), so the two figures cannot drift apart.
The ceiling is scaled from the chain's decimals to the NEAR token's (both 12 today) and compared with ft_total_supply.
IntentsListing carries backing_ceiling and exceeds_backing. A breach is logged as a warning and shown on the market page in words, not colour alone.
If either read fails there is no verdict: an unread ceiling must not pass for one that held.
Not this
The full custody reconciliation (supply on NEAR equals the bridge's custody on Quantus) is still #27 phase 2.
## Why
QTC on NEAR (`qtc.omft.near`) is minted only against QTC locked on Quantus by the bridge. So its supply can never legitimately exceed the QTC that exists outside the vesting pot: issuance less the pot balance, about 220,624 QTC at Quantus height 160,866 (2026-10-03). Supply above that would mean the bridge minted unbacked QTC, or that one of the two reads is wrong. Either way it is the most important thing the market page could say, and today nothing checks it.
QTC on NEAR Intents was announced for 2026-10-05, 17:00 in the poster's timezone ("48 Hours", @QuantusNetwork, 2026-10-03 17:00). This is the lite version of #27's phase 2 (the full custody cross-check needs the bridge's Quantus addresses), and it should be in place before the first mint.
## What
- The listing poll, every 5 minutes, also reads **issuance outside the pot**. It uses the same storage items and the same subtraction the network page uses (`Balances::TotalIssuance` less the balance at the `Vesting::PalletId` account), so the two figures cannot drift apart.
- The ceiling is scaled from the chain's decimals to the NEAR token's (both 12 today) and compared with `ft_total_supply`.
- `IntentsListing` carries `backing_ceiling` and `exceeds_backing`. A breach is logged as a warning and shown on the market page in words, not colour alone.
- If either read fails there is no verdict: an unread ceiling must not pass for one that held.
## Not this
- **The full custody reconciliation** (supply on NEAR equals the bridge's custody on Quantus) is still #27 phase 2.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
QTC on NEAR (
qtc.omft.near) is minted only against QTC locked on Quantus by the bridge. So its supply can never legitimately exceed the QTC that exists outside the vesting pot: issuance less the pot balance, about 220,624 QTC at Quantus height 160,866 (2026-10-03). Supply above that would mean the bridge minted unbacked QTC, or that one of the two reads is wrong. Either way it is the most important thing the market page could say, and today nothing checks it.QTC on NEAR Intents was announced for 2026-10-05, 17:00 in the poster's timezone ("48 Hours", @QuantusNetwork, 2026-10-03 17:00). This is the lite version of #27's phase 2 (the full custody cross-check needs the bridge's Quantus addresses), and it should be in place before the first mint.
What
Balances::TotalIssuanceless the balance at theVesting::PalletIdaccount), so the two figures cannot drift apart.ft_total_supply.IntentsListingcarriesbacking_ceilingandexceeds_backing. A breach is logged as a warning and shown on the market page in words, not colour alone.Not this