WHAT IS ASKED
Twelve readings,
one token
Each one is a question put to the chain and answered by scripts alone. On Solana it is put to the mint account and its extensions; on an EVM chain, to the deployed bytecode and storage. The questions stay the same either way.
Where each one is read on Solana
the mint account| reading | what is read |
|---|---|
| ownership | every live authority over the mint, and which of them touch a balance |
| mint_authority | mintAuthority: can supply still grow, and who can grow it |
| burn_authority | the permanentDelegate extension: a key that can move or burn any holder’s balance |
| pause | the pausableConfig extension and its authority |
| freeze | freezeAuthority: can any holder’s account be frozen |
| upgradeable | the transferHook extension: a program every transfer runs, and who can repoint it |
| trading_switch | defaultAccountState set to frozen, or nonTransferable |
| transfer_tax | the transferFeeConfig extension: basis points, the cap, and who can change the rate |
| transfer_limits | the token programs keep none |
| owner_holdings | what share of supply the live authority holds |
| burned_supply | what share sits at the incinerator, 1nc1nerator…1111 |
| liquidity | how much of the token the declared pool owns |
The name, symbol and who may rewrite them come from the mint’s own
metadata on Token-2022, or from its Metaplex account on the classic program.
What each one asks, on any chain
generated from the reader itself| reading | the question | why it matters |
|---|
This table is written out of the same definitions the reader uses,
so the page and the command line ask the same questions of the same
functions.
Two units, and only one is invented
A fee is printed as read
- A fee getter answers an integer, say
5 - Whether that is five percent, half a percent or five basis points is a convention of a source this program never saw
- So the reading is printed with the function it came from, and left alone
- What the desk does report is whether a setter exists — whether the figure can still be moved while you are holding
A cap is divided, because that is exact
- A cap is denominated in the token’s own units
- Dividing it by
totalSupplyassumes nothing - So transfer limits print a percentage and a cut on transfer does not
- The same reasoning covers the owner’s balance, the burnt supply and the pool
What is never guessed
The pool
- A pool is read only when you name it — none is ever discovered
- Before a single number is believed,
token0andtoken1are asked whether the pair trades this token - A pair that does not is refused outright, rather than quietly reporting somebody else’s liquidity
- A pool with no
totalSupplyis not a UniswapV2-shaped pair, so its LP cannot be read — and the reading says that
Who counts as a holder
- A burn address is removed: nobody holds the key, so the balance is not a position
- An AMM pool is removed: those tokens are the liquidity itself, not one holder’s stack
- A locker or a program vault is removed on Solana: an address no key controls cannot decide to sell
- Both are reported separately rather than quietly subtracted
- Ordinary contracts stay. A treasury or a multisig is real concentration of control, and dropping every contract would hide it