WHAT IS ASKED
Twelve readings,
one contract
Each one is a question put to the deployed bytecode and storage, answered by scripts alone. Six of them are the documents profile’s own power slots, reused rather than rewritten: the same questions about the same bytecode.
What each one asks
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
- 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