Verification & contract records
One wallet deploys every Bellring token. It is published below, it was published before anything launched, and it is the only thing that makes an address real. If a contract was not created by that wallet, it is not ours — no matter whose name is on it.
Record version · generated · source: /records.json
Every Bellring token is created by this address. Whether it also receives that token’s creator fees depends on how the launch was signed, and the line below is read from the record rather than written here — so it cannot go stale the moment that changes.
reading…
This panel runs in your browser against the public RPC. It is not a screenshot and it is not cached by us — if the chain disagrees with anything written on this page, the chain is right and this page is wrong.
Impersonation is the normal failure mode here, not a hypothetical. These are the only places a Bellring address is ever announced.
Find it in the register below. If it is not there, or if the explorer shows a different creator than the deployer above, close the tab. There is no situation in which the real address is the one that reached you in a DM.
Every address we have ever published, in one place. An address appears here only once that listing has actually been signed on chain — until then the row says so, rather than showing a placeholder that could be mistaken for an address.
Subsidiaries are sealed until their slot: no ticker, no company name, nothing until the bell. That is not coyness. Names on the launchpad are first-come and are not reserved in advance, so a listing announced early is a listing somebody else can register out from under us. It also means nobody can have been told a subsidiary’s contract address before it appears here — if someone offers you one early, they are selling you something that does not exist.
Paired with — . Graduation threshold .
Every claim we make about a token is something you can read off the chain without asking us. Here is which call proves which claim.
Number of transactions the deployer has ever sent — a wallet with a history you can inspect, not a fresh one that appeared this morning:
And the one that matters — how much of the token the
deployer holds. 0x70a08231 is balanceOf(address); the deployer
address is padded to 32 bytes behind it. Swap in any Bellring token address. It returns
0x0:
If you would rather not use a terminal, the explorer's Read contract tab does the same thing with a text box.
Bellring does not write its own token contracts. Every launch goes through the Pons v2 launchpad, and these are its addresses. Each one was read off chain rather than copied out of documentation.