Snipers & Holders

Step 6 of the pipeline promises visibility into external bots — this is that view.

How it works

The app scans the token's Transfer events and reconstructs the holder set (JBTerm.holders()):

• Circulating supply — minted minus burned/curve-held
• External holders — every EOA outside your bundle, with balance and % of circulating
• Sniper flag — holders above a threshold share are marked so you can see concentrated risk

Infrastructure addresses (curve contract, pool manager, Permit2-style spenders) are filtered out so the table shows actors, not plumbing. Contract addresses get flagged as such — an EOA and a bot contract read differently.

Reading it

• One external holding 100% means nobody else bought — you are alone on the curve.
• Several 2–5% externals appearing at launch are classic snipers; watch whether they add or unwind.
• Your own bundle wallets are listed separately — the table distinguishes your distribution from theirs.

In the browser

The whole reconstruction runs in the page against the public RPC — a backward scan from head in 9,000-block spans (shrinking on rate limits) that stops at the mint event, capped at ~150 spans to stay fast. No backend, no indexer: the chain is the database.