XPHX is deployed as three separate contracts, so circulating supply is the sum across chains. The BNB Chain figure is totalSupply() minus the balances of the addresses below, every one read live on this request. Check any of them on BscScan and total them yourself.
XPHX supplied into its own lending market counts as circulating. Somebody supplied it, they still own it, they earn on it, and they can withdraw it whenever the market has cash. The cXPHX contract holds it the way a counterparty holds it, not the way a treasury does, so no exclusion applies. What every address below has in common is control: each is one PhoenixCo controls, or one nothing can ever leave. A lending market is neither.
BNB Chaincomputed live18,141,967
TRONcomputed live2,416,697
Polygoncomputed live589,57412,400,001 SZNX was transferred to the SZNX token contract address itself rather than to a wallet, and that is its balance there on this request. Ownership of that contract has been renounced, so there is no function and no key that can move those tokens back out. They are gone, and no future event recovers them. We count them as burned, because that is what they are: an address nobody can spend from is a burn whether or not it was chosen. Calling it anything softer, such as “held by the contract”, “temporarily inaccessible”, would imply a recovery that cannot happen.
This was our mistake, not an attack and not a design decision. It is recorded here because a supply figure is only worth reading if the losses are in it too.
These 4 holdings are ours to disclose but not ours to withhold from the count. Together they are 4,156,928 XPHX, 19.7% of circulating supply.
This wallet holds two different things and we cannot cleanly separate them on chain: XPHX deposited by users of the PhoenixCo centralised staking product, which belongs to those users and is theirs to withdraw, and pre-allocated staking rewards that release to them on the published unlock schedules. The user deposits are unambiguously circulating. Rather than split the balance on an assumption, we count the whole wallet.
The wallet the day runs out of. It pays XPHX out to individual addresses, tops those addresses up with BNB for gas, and moves XPHX into the XPHX/WBNB pair when liquidity is added. It holds a working balance rather than an allocation: nothing is scheduled out of it and nothing vests from it, and because the address is public it also collects unsolicited spam tokens that have nothing to do with us. Counted as circulating, because everything in it has already been issued and is spent rather than held back.
The XPHX contract holds XPHX. That is not an error and not a treasury wallet: the token has an auto-liquidity mechanic, and the deployer sent it tokens to feed it. Nobody can trade them, because they are inside the contract rather than in any wallet, so they are excluded from circulating supply.
On a qualifying transfer the contract sells half of a fixed threshold for WBNB and pairs the other half back into the primary XPHX/WBNB pool. The threshold is 33.632 XPHX, so each firing moves about 16.8 XPHX to each side.
swapAndLiquifyEnablednumTokensSellToAddToLiquidityuniswapV2PairuniswapV2RouterEvery value above is read from the contract on this request, not quoted from a document.
Transfers to and from all three staking pools that stake or pay XPHX are fee-exempt: the contract's own isExcludedFromFee() returns true for each of them on this request. Whether the liquidity trigger sits inside the fee branch, in which case staking never fires it, cannot be answered from the code, because this contract is not verified on BscScan and has no Sourcify match. We will not guess at a control flow we cannot read.
What the chain does settle: the contract holds 22.1 XPHX on this request, against a threshold of , and no WBNB at all.
A staking pool holds two different things in one balance: user-staked principal, which belongs to the stakers and can be withdrawn at any moment, and undistributed reward budget, which is ours until someone earns it. Only the second is excluded.
Excluding the whole balance would understate circulating supply by everything users have staked. Excluding none of it would overstate supply by the entire unpaid budget. Both are wrong, in opposite directions.
| Pool | Holds | Principal | Excluded |
|---|---|---|---|
| PhoenixCo pool P1: stake XPHX, earn SZNXStakes XPHX, so its principal is XPHX and stays circulating. | 282,807 | 282,807 | 0 |
| PhoenixCo pool P2: stake SZNX/ASTER LP, earn XPHXDoes not stake XPHX, so none of the XPHX it holds is principal. | 34,574 | 0 | 34,574 |
| PhoenixCo pool P3: stake PHSUN, earn XPHXDoes not stake XPHX, so none of the XPHX it holds is principal. | 36,551 | 0 | 36,551 |
The split is derived from each pool's own stakingToken(), read on this request, so it cannot drift from the contract. A pool that stakes XPHX has principal equal to its ; a pool that stakes something else holds no XPHX principal at all, and its whole XPHX balance is reward budget. That distinction matters: is denominated in the stake token, so subtracting it from an XPHX balance is only meaningful when the two are the same token.
Project-controlled and undistributed. These tokens exist but have never been released to the market.
4 addresses · 25.43% of total supply
Held in a third-party locker contract on a release schedule. Not movable by us before it elapses.
1 address · 11.20% of total supply
Held by a third party under an agreement that prevents sale. Not in circulation while the restriction stands.
1 address · 4.31% of total supply
Sitting in staking and farming contracts, earmarked for emission but not yet earned or claimed by anyone.
24 addresses · 4.08% of total supply
Sent to an address with no known private key. Provably unrecoverable by anyone.
2 addresses · 0.00% of total supply
| Holding | Address | Balance | % of supply |
|---|---|---|---|
Burn address Standard dead address. Tokens sent here are unrecoverable by anyone. | 232.24 | 0.00% | |
Zero address Burns sent to address(0) rather than the dead address. | 0 | 0.00% | |
PhoenixCo deployer (retired) The wallet that deployed XPHX and held the treasury until the treasury moved to a new wallet on 8 September 2026. Its BNB Chain balance moved to treasury-2026 and only dust remains, but it is kept excluded. Dust is still undistributed supply, and removing the entry would move the circulating figure a second time for no reason on chain. It still holds the Polygon balance, which is covered in the Polygon list. |
totalSupply() on the XPHX contract.balanceOf() for each address in the table.Newly deployed staking pools holding unreleased rewards are added as a data entry, not a code change. This page and the API both pick it up on the next request.
Balances read 9/25/2026, 9:00:36 PM UTC.
NOT A COMPANY WALLET, AND THIS PAGE USED TO SAY IT WAS. It was published here as the PhoenixCo hot wallet; it is a person's own wallet, and the hot wallet is the address above. What it does is what any holder does: it holds XPHX and other ecosystem tokens, supplies and borrows in the lending markets, holds a VIP lock, and sits in liquidity pairs. Those positions are readable at the address like anyone else's. It is counted as circulating for the plainest reason on this page: the tokens belong to an individual, who can sell them, which is what circulating means.
Lodged with the P2B exchange as listing collateral. P2B has since delisted XPHX, and these tokens are no longer under any PhoenixCo control or contractual restriction we can enforce, so they could be sold at any time. We count what can move, not what we hope to recover.
That submission excluded both of the holdings above. We now count them, which raises our reported circulating supply by roughly 4,156,928 XPHX and lowers every ratio computed against it. We are stating the change rather than letting the figure drift, because a supply methodology is only worth anything if the reasoning is published alongside the number, including when the reasoning moves against us.
The company-owned treasury holding remains excluded. It has never been released to the market and is under our direct control, which is the same test applied in both directions.
totalSupply()totalSupply()When a staker claims, tokens move from the reward budget into their wallet: the excluded amount falls by exactly what was claimed and circulating supply rises by exactly the same amount. Nothing else in this table changes.
| 7,195.23 |
| 0.02% |
PhoenixCo treasury The project treasury wallet since 8 September 2026, holding what the deployer held before it. Undistributed supply; anything it has not released is not circulating. Same treatment as the address it replaced. | 8,128,104.07 | 24.63% |
DXsale liquidity lock Third-party locker contract. Tokens are held to a release schedule and cannot be moved before it. | 3,696,780.92 | 11.20% |
Farm campaign, pIRTX suppliers Undistributed farm reward budget, funded up front and paid per second to holders of the source token. Falls as farmers claim, and what leaves becomes circulating then. The budget and the pair it pays on are readable from the address beside it, by calling budget() and source(). | 54,231.19 | 0.16% |
Farm campaign, liquidity pair Undistributed farm reward budget, funded up front and paid per second to holders of the source token. Falls as farmers claim, and what leaves becomes circulating then. The budget and the pair it pays on are readable from the address beside it, by calling budget() and source(). | 110,550.91 | 0.34% |
Farm campaign, liquidity pair Undistributed farm reward budget, funded up front and paid per second to holders of the source token. Falls as farmers claim, and what leaves becomes circulating then. The budget and the pair it pays on are readable from the address beside it, by calling budget() and source(). | 130,581.87 | 0.40% |
Farm campaign, locked XPHX Undistributed farm reward budget, funded up front and paid per second to holders of the source token. Falls as farmers claim, and what leaves becomes circulating then. The budget and the pair it pays on are readable from the address beside it, by calling budget() and source(). | 72,010.4 | 0.22% |
Farm campaign, liquidity pair Undistributed farm reward budget, funded up front and paid per second to holders of the source token. Falls as farmers claim, and what leaves becomes circulating then. The budget and the pair it pays on are readable from the address beside it, by calling budget() and source(). | 50,250.41 | 0.15% |
DODO staking contract Holds XPHX staked by users plus rewards not yet claimed. | 493,995.48 | 1.50% |
BabyDogeSwap reward mining Unreleased XPHX rewards for the BabyDogeSwap farm. | 98,808.87 | 0.30% |
DODO reward pool 1 Unreleased farming rewards held by the pool contract. | 70,318.91 | 0.21% |
DODO reward pool 2 Unreleased farming rewards held by the pool contract. | 22,495.63 | 0.07% |
DODO reward pool 3 Unreleased farming rewards held by the pool contract. | 57,390.5 | 0.17% |
DODO reward pool 4 Unreleased farming rewards held by the pool contract. | 13,627.53 | 0.04% |
DODO reward pool 5 Unreleased farming rewards held by the pool contract. | 25,632.93 | 0.08% |
DODO reward pool 6 Unreleased farming rewards held by the pool contract. | 23,100.73 | 0.07% |
DODO reward pool 7 Unreleased farming rewards held by the pool contract. | 10,023.86 | 0.03% |
DODO reward pool 8 Unreleased farming rewards held by the pool contract. | 9,973.18 | 0.03% |
DODO reward pool 9 Unreleased farming rewards held by the pool contract. | 8,315.98 | 0.03% |
DODO reward pool 10 Unreleased farming rewards held by the pool contract. | 6,633.35 | 0.02% |
DODO reward pool 11 Unreleased farming rewards held by the pool contract. | 3,840.76 | 0.01% |
DODO reward pool 12 Unreleased farming rewards held by the pool contract. | 5,722.18 | 0.02% |
DODO reward pool 13 Unreleased farming rewards held by the pool contract. | 4,207.53 | 0.01% |
DODO reward pool 14 Unreleased farming rewards held by the pool contract. | 3,740.82 | 0.01% |
Partner collateral (restricted) Held by a partner as collateral under a contractual restriction on selling. The tokens originate from the PhoenixCo treasury and are not in circulation. The restriction is under review on 1 November 2026, after which they may or may not enter circulation. This entry will be revisited on that date. under review 2026-11-01 | 1,421,679.87 | 4.31% |
Company-owned tokens Company holdings, never released to the market. Declared in the CoinMarketCap submission. | 257,441.02 | 0.78% |
PhoenixCo pool P1: stake XPHX, earn SZNX Stakes XPHX itself, so almost the whole balance is user principal and stays circulating. Only any XPHX above totalSupply() would be reward budget, and this pool pays SZNX, so that is normally zero. | 0 | 0.00% |
PhoenixCo pool P2: stake SZNX/ASTER LP, earn XPHX Stakes an LP token, not XPHX, so none of the XPHX it holds is user principal. The whole balance is undistributed reward budget and is excluded. It falls as stakers claim. | 34,573.71 | 0.10% |
PhoenixCo pool P3: stake PHSUN, earn XPHX Stakes PHSUN, not XPHX, so none of the XPHX it holds is user principal. The whole balance is undistributed reward budget and is excluded. It falls as stakers claim. | 36,550.93 | 0.11% |
XPHX contract, auto-liquidity buffer The token contract holds tokens sent by the deployer for its auto-liquidity mechanic. They are not tradeable by anyone and are not in any wallet, so they are not circulating. The balance is read live and shown in the table below. | 22.1 | 0.00% |
| Total excluded | 14,858,033.12 | 45.02% | |
1 entry is configured but not counted: . Skipped entries are never subtracted, so the figure above is at or above true circulating supply.