Methodology
How the site reads the archive
This page documents what the data can show, what it cannot show, and how the displayed figures are computed.
What is a declared exemption?
When a token launches on Pons, buyers in the first seconds pay a snipe tax — starting near 99% and decaying to zero within about three seconds. The rate decays after launch.
The creator can name wallet addresses in the launch transaction that skip this tax entirely. Those addresses are recorded on-chain by the contract itself.
Every launch automatically exempts the deployer. That is routine. This site tracks the other kind: wallets that are neither the deployer, the router, nor the curve, and were exempted in the launch transaction. We call those declared exemptions.
An exemption records eligibility to skip the snipe tax. It does not by itself establish that the address bought, what price it paid, or who controls it. We publish what the contract recorded and what the addresses did. We do not infer intent, ownership, or wrongdoing.
Relationship explorer
Connections, scale and comparison
Only canonical declared-exemption records enter these views. A connection counts distinct launch identities (block hash, transaction hash and token address), so repeated exemption logs do not multiply the launch count. Wallet views connect to distinct deployers; deployer and launch views connect to distinct declared wallets.
The map shows six connections per page, ordered by shared launch count then address. It is a paginated neighbourhood, not the whole archive graph. Line width scales with the square root of shared launch count within the visible page. The square display summarizes the total counterpart count at the labelled scale; squares are count units, not individual address nodes.
Timeline bars span the first and last observed launch blocks for each relationship. Gaps between launches are included; these bars do not imply continuous activity or approximate dates. Cluster bars share the selected group’s range. Starting-point bars compare counterpart counts within that page.
Comparison counts the intersection of counterpart addresses in the two indexed relationship sets. The first six shared addresses are shown in address order, with a launch receipt for each side. A shared receipt can legitimately support both sides when wallets were exempted in the same launch. No shared relationships means none in the indexed set, not that addresses are unrelated outside this coverage.
Focus, presets, comparisons and pagination are encoded in the URL. The same views render on the server without JavaScript. Shared relationships and overlapping block ranges do not establish common ownership.
Automatic vs declared exemptions
For each Pons V2 launch, an exemption is classified as automatic only when the exempted address exactly matches that launch's deployer, the configured router, or that launch's curve. The configured router is 0xe33e9e479df8802cb0866d5d05258bec4cf62948. The deployer and curve are launch-specific and are decoded from the launch evidence. Any other resolved exempted address is classified as declared. A distinct creator fee recipient remains declared under this rule.
Role matches and membership in the decoded exemption argument are stored separately from the automatic/declared label.
Coverage
The V2 dataset is indexed through block 64,205,558. Current indexed launch blocks run from 27027321 to 64205279. Launches after the captured head, V1 launches, failed transactions, off-chain agreements, and activity not emitted in the indexed logs are outside this dataset.
V1 is explicitly excluded. V1 factory: 0xa5aab3f0c6eeadf30ef1d3eb997108e976351feb. V2 factory: 0x7ed598bcef8bd9edd8c97a195c6d13f40801ec7e.
Most-cornered leaderboard denominator and filter
The leaderboard starts from the top 200 launches ranked by declared-exempt wallet count. It is not a full-archive trade metric. A launch must then have at least 10 distinct non-exempt buyers and at least 10¹⁸ raw quote units in total curve quote volume to appear in the ranked table.
The token percentage is declared-exempt recipients' share of tokens purchased on the bonding curve, divided by all tokens purchased on that bonding curve in indexed buy events. These are gross purchases: a token sold back and bought again appears in both buy events. This is not total supply or a current token balance. CurveBuy quoteIn records actual spend after refunds, including fees and taxes. CurveSell quoteOut is net returned quote; fees are not subtracted again. The quote percentage is declared-exempt buyers' quote paid into bonding-curve buys divided by all quote paid into bonding-curve buys for that selected launch. A token recipient and the quote-paying buyer can differ in a trade, so the two percentages can diverge.
Current bounded run status: paused; finished 2026-09-16T05:02:22.333Z.
Current USD valuation preview
The token header uses GeckoTerminal’s Robinhood token data for current USD market cap, with DEX Screener as an outage fallback. The fallback matches the token address and Robinhood chain, selecting the pair with the most reported liquidity. If only fully diluted valuation is reported, it is labeled FDV instead. Missing prices are unavailable, never zero. The checked time records retrieval, not the last trade. Stale values are marked. This external preview does not convert trade totals or historical flows to USD. Source documentation ↗
Launch stories and live watches
Token and wallet stories combine canonical curve trades with saved on-demand buys, sells and outgoing transfers. The same physical event is counted once using block hash, transaction hash and log position. Transfers recorded with a sale remain separate evidence and are not added to sold totals. Received tokens follow the recipient; quote paid follows the buyer. Quote returned follows the recipient, which can differ from the seller.
Share purchased is shown only where explicit per-curve coverage begins at launch. The numerator and denominator use the same cutoff and count gross tokens purchased on the curve, including repeat purchases. Later on-demand events can appear in the story but do not extend that denominator. Token amounts use the 18 decimals in the verified PonsV2LauncherToken implementation; rounded headlines use ≈ and expand to exact amounts. Quote units use the stored asset decimals when available. This is neither share of total supply nor a current holding. A current balance or full exit is not established.
Watching requires an explicit request. Recent activity is retrieved first; earlier history can arrive later or remain partial. A waiting watch joins the shared queue. The watch panel states its covered intervals, and gaps are never treated as no activity. Without JavaScript, the request form, saved events and evidence links still work; reload for updates.
Cluster grouping
Cluster groups indicate shared exemption relationships: wallets are grouped when they share a deployer and have overlapping declared-exemption block ranges. Overlap is transitive: A can overlap B and B overlap C without A overlapping C. That is not a claim that the wallets share an owner or purpose.
Independent check · 14 September 2026
The 83.82% leader, recomputed
0xfb0d…d868Blockscout. All 104 buys and 75 sells were fetched directly from the public RPC through block 62,284,009; 31 declared wallets were independently extracted from the launch receipt.
851967752518798573179619352 / 1016384250552337059333815227 × 100 = 83.82339179%
The quote share is 83.36061239%: 2.876611873213353383 / 3.450804631244082475 native quote units. This snapshot verifies the displayed calculation at that cutoff; later indexing can change the ranking.
What the data cannot show
The data cannot show intent, common ownership, private agreements, wallets controlled through undisclosed keys, or transfers and trades outside indexed scopes. Empty cells and absent rows are treated as coverage states unless the page has enough indexed evidence to state a confirmed absence, such as "No declared exemptions on this launch" for an indexed V2 token launch.