Launch terms
Pad mechanism
Snipe protection
If you buy in the first second, almost all of it goes to the tax. Wait three seconds. This is a launchpad setting, not a policy of ours, and it applies to everyone equally.
Pre-launch
Contract address
There is no $SHERIFF contract address until launch. Anything presenting one before it appears here is not $SHERIFF. When it exists, it will appear on this page with the block it was deployed at.
Published
Dev wallet
One address, published before the launch block. No second wallet and no bundling. Nothing bought inside the three-second snipe window. No lock binds this address. It is published so you can watch it. Its size and its share of supply will be printed here as a number at a pinned block.
Why the pair is ETH
On pons you choose the paired asset from about 55 tokenized assets, and the chart is denominated in whatever you choose. It is the most under-used lever on the launchpad. In the last 24 hours of graduated launches, 71 paired to native ETH, 30 to USDG, 6 to SPY, 2 to SPCX and effectively nothing to the other fifty.
We took ETH for one reason that follows directly from entry 002. SPY and SPCX sit behind a beacon whose role holders we have not enumerated. We are not going to denominate our own chart in a dependency we just told you we had not finished checking.
USDG is the second-deepest pair and it does not share that beacon. We read its implementation separately and it exposes privileged selectors of its own. Unread, therefore unused, was the position before that read; after it, the position is that we are not denominating in an issuer-controlled asset while publishing entries about issuer control.
The $SHERIFF market row
Pre-launch
$SHERIFF has not launched. There is no contract address, no pool and no price, so there is no holder count, no volume and no market cap to print. Nothing is estimated in their place.
Source: third-party market API. Not measured by us and not covered by any pin on this page.