QuaiAxe docs

QuaiAxe

QAXE supply tracker

www.quaiaxe.com/supply (Turkish: /tr/supply) shows QAXE's supply read live from the Quai Cyprus-1 RPC. Every figure on the page has a provenance row — contract, call, block, raw return word and a copyable curl — so you can re-read it yourself.

One billion, only down

QAXE (0x0035187a7660f595d93cd53a4d16c635d6cffc8f) is a HartiiLabs V1 LaunchToken: the full 1,000,000,000 QAXE supply is minted once in initialize() and the contract has no mint(), so supply can never rise. burn() is the only path that lowers totalSupply(), and every burn emits Transfer(from, 0x0).

Since quaiaxe.com 1.7.0 the page never shows one combined "burned" number. QAXE burned by mining (the QaxeBurnVault, totalTokensBurned(), miners' QUAI) and QAXE burned outside mining (the creator, the curve treasury and holders) are two separate figures, each with its own share of the 1,000,000,000 supply, and are never added together on any page. Outside mining = 1,000,000,000 − totalSupply() − vault.totalTokensBurned(). The page still sums every Transfer → 0x0 log as an internal cross-check that it equals 1,000,000,000 − totalSupply().

On 2026-10-08: 33,442.0078 QAXE burned by mining (0.0033%) and about 125.09M QAXE burned outside mining (12.51%). totalSupply() is shown as Supply now, not as a burn total.

Since quaiaxe.com 1.10.0, a four-part pulse directly below the headline shows Supply now, Mining burn · 24h, Other burns · 24h and the exact Verified block. The two 24-hour burn figures follow the same separation rule as the rest of the page and are never combined. They are already present in the saved HTML snapshot, then update from the live chain read when it succeeds.

Where the billion is

The page splits the genesis supply live and checks the identity on every read:

text
genesis (1e9) = burned outside mining + burned by mining + held by the curve + creator-locked + circulating
BucketWhat it isRead from
Burned outside miningDestroyed with burn() by the creator, the curve treasury and holders1e9 − totalSupply() − vault.totalTokensBurned()
Burned by miningBought with miners' QUAI by the burn vault and destroyed; counted apartvault.totalTokensBurned()
Held by the curveThe curve's own pool reserve, plus anything sent to it outside tradingbalanceOf(curve)
Creator-lockedCreator allocation not yet vested (linear from lockedUntil)creator allocation − unlockedCreatorAllocation()
CirculatingEverything else — wallets and LP pairsthe remainder

The QAXE curve is 0x004bc407903a51506bcf0b1ab423958c5991c237 (V1, graduated: after graduation it trades as an x·y=k pool over its own reserves, fee taken from the QUAI in).

Burn scenario

A slider projects future burns using the QaxeBurnVault rules exactly — 0.5% fee, refund cap 3%, slice 0.5% with an absolute max of 1,000 QUAI, minimum sweep 100 QUAI, 120-block cooldown — and the curve's own pool maths. It is labelled a scenario, not a forecast. The mining burn vault's first sweep was on 2026-10-08: 33,442.0078 QAXE burned (totalTokensBurned() on the vault). The page reads the vault's own counters, so this figure moves on its own as sweeps happen.

As of block 10,509,809 (2026-10-08), totalSupply() is 874,872,153.389 QAXE, from the 1,000,000,000 initial supply: 33,442.0078 burned by mining and the rest of the burned QAXE (about 125.09M) outside mining. The "Every burn" section lists the burn vault's burns in their own table and keeps them out of the other burns' list, bars and chart.

Views and sharing

Holder, Analyst and Auditor views show progressively more detail (Auditor adds the raw calls). The chart switches between composition, cumulative and per-day burns over 24H / 7D / 30D / All, and a "the billion" ingot (1,000 cells, one per million QAXE) replays supply from launch to now. The URL keeps the view, range and timeline position, so a link reopens the same state.

Aggregated liquidity

The live Aggregated liquidity section compares the graduated curve, HartiiSwap, and Quainance at one shared Quai block. The QUAI-side total adds the curve's native QUAI reserve and the WQUAI reserve from each QAXE/WQUAI pair once; QAXE-side reserves are shown separately. Pair token order is checked before reserves are counted.

The 3D bars use logarithmic height only to keep the smaller venues visible. The adjacent ledger is the exact view. If one venue cannot be read at that block, the page names it and excludes it from the partial total. It does not substitute the historical supply snapshot or show an unreadable reserve as zero. The displayed block identifies the shared read point.

Buybacks and the Claim panel

Two additions in quaiaxe.com 1.4.0: the Claim panel in the "Releases and unlocks" section, and a companion page, /supply/buyback, listing every QAXE buyback and sale by the Hartii company wallets. How both work, what counts as "ours" and what is not counted: Buyback tracker and Claim panel. In short, the only claim on the QAXE contracts is the curve's withdraw() of sale proceeds that could not be delivered; creator vesting is fully unlocked (since about 2026-09-13) and mining rewards unlock by Quai's 14-day rule, so neither has a claim.

Data sources

Only the public Quai RPC (https://rpc.quai.network/cyprus1) and a same-origin snapshot (/assets/data/supply-snapshot.json; the buyback page adds /assets/data/buyback-snapshot.json, used for history and as the fallback if the RPC is down — the page then says it is showing the snapshot, with its block and time). No API keys, no third-party analytics.

Public-RPC transport reads have a 12-second timeout and one retry for network errors, HTTP 429 and server errors. If both attempts fail, the page keeps the committed snapshot and labels it with its block and time; it does not turn an unavailable value into zero or call a snapshot live.

Quai Network mainnet · chain 9 · Cyprus-1. Figures marked "read on" a date were read from the chain that day; re-read before relying on them.