Check a wallet
What a wallet check can and cannot tell you
Nothing on this chain will let anyone list the tokens an address holds:
both public RPC endpoints refuse historical
eth_getLogs. So this page works the other way
round. It takes the contracts it already knows about — the tokens
the StockFactory issued, plus every forgery the background index has
catalogued so far — and asks each one what your balance is.
That means a holding this page does not show you is a contract that was never on the list, not a contract it cleared. The exact counts are printed with every result, and there is no “your wallet is safe” anywhere on this page, because this check cannot establish that.
How each holding is judged
The balance is one question; the token is another
A balance is easy: every contract is asked
balanceOf(your address), and thousands of those
questions are packed into a handful of requests through Multicall3 at
0xcA11bde0…76CA11, which this server reads the
bytecode of before it trusts it. Deciding whether the contract that
answered is the real token is the hard part, and that is not
answered from any list — every token you hold is put through the same
six on-chain checks the verifier runs, during the request.
Two consequences worth stating plainly. A token flagged in the index but not re-checked in time is shown as unverified with the earlier finding beside it, never as a forgery on the strength of a file. And a check that could not be completed — a busy endpoint, a spent budget — is unverified too. A slow RPC is not evidence of anything.
Where a corporate action has scaled a token, both numbers are shown: the
raw balance the contract stores and the effective balance
(raw × uiMultiplier / 1e18) a wallet would
display. They are different numbers and neither one is the whole truth on
its own.