TransparencyVerify, do not trust
Every number here survives you checking it.
Five things on this page are fixed forever and can be checked without us. Everything else is a live reading from a service that can fail, and when it fails it says so. Nothing here is estimated to fill a gap.
01 / Immutable
Set once, at deployment.
These five values cannot be changed by us or by anyone else. They are properties of the mint account, and the link below reads them straight off the chain.
Official LANDING mint
Immutable
DLGLMB3imJqnAwKjxY8ZFXoF7CPfTbCNL3j3Ag5M5vGZ
02 / Live
Who holds it, right now.
Positive owners
Awaiting source
Addresses holding a non-zero balance
Independent holders
Awaiting source
Excludes project, pool, founder-controlled and known exchange addresses
Project wallets
Awaiting source
The four identified addresses listed in section 04
Liquidity pools
Awaiting source
Pool accounts, counted separately from holders
Founder controlled
Awaiting source
Held under founder control, not distributed
Other known / exchange
Awaiting source
Operational and exchange addresses the backend can identify
Readings refresh while this page is visible. They are not a continuous chain feed, and the timestamp belongs to the source snapshot rather than to the moment you are reading it. A channel that cannot be reached stays labelled; it is never filled with an estimate.
03 / At launch
How the supply was divided.
This is the original allocation, not current balances. Tokens have moved since launch, and the explorer links in the next section are where you check where they are now.
404,000,000
Community
202,000,000
50%
Treasury
141,400,000
35%
Liquidity reserve
39,000,000
9.6535%
Creator
20,200,000
5%
Initial liquidity
≈1,400,000
≈0.3465%
04 / Identified
The four wallets we control.
Identified addresses, not balance statements. Each one links to its full transfer history.
Community / project controlled
CBPwvUZrDQThyM6a54shKPpywvpTyYQQ2Ng7FWPZPM88
Project controlled. The label says what it is set aside for, not who holds it today.
Treasury / project controlled
3JA9uuNqr5tqBxGP9sQTRTPtwmPAR2KxmJyXyietrQwS
Project controlled. Operating reserve.
Liquidity reserve / project controlled
34hUkC1XVGMHX64txhfTh7rDBMhtScK8cpCcP54u17vZ
Project controlled. Held against future pool depth.
Creator / project controlled
4fUtkW2LEZxLt2tgPJ9BitViNBqR3AUy58hyG81Q41hg
Project controlled. Creator allocation.
05 / Unlocked
Liquidity, stated plainly.
Liquidity is not locked
We are saying it here rather than letting you find out. The vault readings below describe what is in the pool right now. They do not imply a lock, and they are not a guarantee the liquidity will still be there later.
Pool vault / LANDING
Awaiting source
Token side of the pool
Pool vault / SOL
Awaiting source
SOL side of the pool
06 / Third party
What the market source says.
Price / USD
Awaiting source
Last traded price reported by the market source
Liquidity / USD
Awaiting source
Pool depth in dollar terms
24h volume / USD
Awaiting source
Traded value over the rolling day
24h transactions
Awaiting source
Swap count over the rolling day
24h buys
Awaiting source
Buy-side swaps
24h sells
Awaiting source
Sell-side swaps
A flat trace means the market source is not answering, not that the figure is zero. Market data comes from a different provider than the owner readings above, so one can fail while the other works.
07 / Check it
Don't take our word for it.
Configuration is separate from live readings. Coverage can be partial. Where a source is silent we leave the field empty.
Chain
Solscan
Token configuration and account state, read directly from the chain.
RecordDeployment record
The mint, pool and project addresses as they were set at launch.
SupplyAllocation table
The original allocation and what each line was set aside for.
RawBackend readings
The read-only JSON this page requests, with its own timestamps and coverage field.
Found something wrong?
Tell us publicly. A transparency page that quietly fixes its own mistakes is not a transparency page.