Buyback tracker and Claim panel

www.quaiaxe.com/supply/buyback (Turkish: /tr/supply/buyback) lists every time a Hartii company wallet bought or sold QAXE, in both directions, read from the Quai Cyprus-1 chain in your browser. It shipped in quaiaxe.com 1.4.0 (2026-10-08). Nothing on it is reported to you by Hartii: every row carries the transaction hash, so you can re-check it.

On 2026-10-08 the page showed roughly 2.33 million QAXE bought back in 33 purchases, 928 QAXE sold in 8 sales, and about 152,843 QAXE still held by the company wallets. These are live figures that move; the page is the authority, not this paragraph.

#What "ours" means

"Ours" is the short list of public company addresses in the site's companyWallets config:

Nothing else counts. Owner personal wallets are never on the list (a test fails the build if one is added), and personal addresses are never printed on the page or in the snapshot; rows show a role, not an address. The market-maker engine currently runs in dry-run with no vault and no published signer, so it has no entry; it is added the day its signer is published.

#How a trade is classified

Each QAXE Transfer to or from a company wallet is matched against the logs of the same successful transaction (receipt status 0x1 only; reverted transactions never count):

• a bonding-curve Buy / Sell with the same token amount is a buyback / sale;
• a Quainance V2 pair Swap (QAXE is token0 on both pairs) is a buyback / sale, with the WQUAI side shown as QUAI;
• a pair Mint / Burn is adding / removing liquidity: it is listed but not counted as a buyback or a sale;
• anything else is a neutral move (for example a transfer between company wallets, or a burn); it is tallied without showing the other party and not counted as a buyback or a sale.

#What is not counted

• Purchases by the QaxeBurnVault. Those are protocol burns funded by miners' deposits, not company buybacks. They appear on the supply tracker as burns.
• Liquidity adds and removes, plain moves between company wallets, and anything by a wallet that is not on the list above.
• Anything the chain cannot show: the page does not know what is planned, only what has been mined into a block.

#How the snapshot plus live scan works

Scanning the chain from QAXE's launch takes about ten minutes against the public RPC, so the page does not do it on every visit:

1. A snapshot (/assets/data/buyback-snapshot.json, same origin) holds every classified event up to a block. npm run snapshot:buyback in the site repo is the only thing that writes it; it is read-only against the chain and resumes from its last block. The build never touches the network. Visitors without JavaScript see the snapshot.
2. In your browser the page then scans only the blocks after the snapshot, in chunks of at most 10,000 blocks (the public RPC rejects larger ranges and concurrent log queries, so it asks one at a time and retries when told to wait; up to 40 chunks per visit), and appends what it finds. Holdings are read live with balanceOf on each company wallet.
3. Block times come only from the block header's woHeader.timestamp; every address sent to the RPC is checksummed.
4. As a cross-check, the page GETs the newest curve trades from the Hartii Labs API and compares those of the company wallets by transaction, side and amount. DEX pair trades have no such second source and are chain-only.

The only network hosts are the public Quai RPC, the same-origin snapshot and hartiilabs.com for the cross-check.

#The Claim panel on /supply

The Claim panel in the "Releases and unlocks" section of /supply exists for one thing only:

• Claim = the bonding curve's withdraw(): a pull-payment of the QUAI that the curve parked for your address because a payout to you failed when you sold. Normal sales pay out instantly, so for almost everyone the amount is zero and the button is disabled.
• You connect an injected wallet, the panel reads pending(your address) from the curve, and if it is non-zero you can send withdraw() yourself. You pay the network fee. The page re-reads account, chain and amount just before the single send and only treats receipt status 0x1 or 0x0 for the submitted hash as final.
• There is no faucet. The panel never sends you anything and never asks you to approve a token.

What it deliberately does not do:

• Creator vesting needs no claim. The creator allocation unlocks by time (unlockedCreatorAllocation()) and has been fully unlocked since about 2026-09-13; nothing is left to claim.
• Mining rewards unlock by Quai's own rule, about 14 days after the share (see the 14-day lock); there is no QuaiAxe claim for them either.

#Related

• Supply tracker and the guide QuaiAxe: trade and supply
• Burn vault and running a keeper
• Versions