How the record is made
The creator record states what we can see on-chain about the person behind a coin: what they launched before, how those coins did, and what they hold and sold of this one. This page is its method, for researchers, tools and callers who cite it. Every figure on the record is a count of facts with a one-line definition. None is a score, a prediction or a judgement of anyone, and the record is never complete: it holds what our sources reach.
What it reads
| Source | What is read | What it feeds |
|---|---|---|
| Chain Daddy's launches and registrations | Coins launched here, with the creator wallet each launch names, its date, the wallet that made the dev buy and any team or fee wallets it named; coins registered here, with the wallet that holds the registration | Who the creator is; their launches here |
| Mobula deployer pages | For each creator wallet, on the chains below: the coins it deployed, each with its launch date, last trade, liquidity and whether it left its launch curve; the wallet's first funder, that funder's label and the date of the first funding | Their launches elsewhere; funding links; Wallet age; First funded from |
| The creator watch | Every 5 minutes, from the chains: what the creator's wallets hold of the coin, what they sold or moved out of it, and the coin's supply | Holdings, Creator sold, Creator exited |
| The opening blocks | The buys in a launch's first blocks, from our own trade feed, and the first funders and Mobula labels of its 25 largest buyers | Bundled at open; First buyers |
| Chain Daddy's trade feed | Trades on coins launched or registered here, read from the chains by our own indexer | Last trades of coins launched here; the price check behind a confirmed extraction |
Pages and the public read only read what is stored. No page view calls a provider.
Who the creator is
- A coin launched here: the wallet the launch names as its creator, a wallet on the launching account. Never the wallet that sent the launch transaction: Chain Daddy sends some launches itself.
- A coin registered here: the wallet that holds its registration, which proved it controls the coin.
A coin nobody registered
On staging, not yet in prod.
The record names the wallet the chain names, and the card says where the chain names them ("Creator: 0xa96a…dEa2 · sent its creation transaction"):
| The card says | The wallet that |
|---|---|
| sent its creation transaction | sent the transaction that created the coin |
| called the contract that made it | sent the transaction that made a launch contract create it |
| the coin's payout recipient | the coin's own payoutRecipient() names, when the launch contract was called by a bot |
| its launch pool | created the coin's launch pool |
| its launchpad's record | the launchpad's own record names as creator |
| the coin's creator-fee config | is the sole or largest claimer in the coin's creator-fee config |
| the mint's authority | holds the mint's authority, when that is a wallet |
A bot that sends launches for many people is never named as their creator. When the chain names no one in a way we read, the record says Unknown. The card adds Other launches: "Coins this creator launched besides this one, on the chains and launchpads we read. A launch we cannot see is not counted."
Such a coin is read by its address (/api/v2/public/coins/{chain}/{tokenAddress}/creator-record). Its creator is read from the chain the first time a person's browser asks; a script, crawler or agent gets what is already computed, which is pending until then.
How wallets are linked
The record follows the creator, not one wallet. It counts the coins launched by the wallets on the creator's account, the wallet that made the launch's dev buy, a deployer wallet the creator proved when they registered a coin launched elsewhere, and wallets linked to theirs by on-chain funding. Exchanges, bridges, other named services and Chain Daddy's own wallets link nobody.
Wallets the creator only names, for a team, fees or a fee share, are shown and never counted. Holdings, Creator sold and Creator exited count the same wallets the record counts.
How a funding link is found, and the lines it is held to, are not published: they are tuned over time, and a person's reply to a contest gives the specifics.
What each line means
Quoted exactly as the public read returns them, in definitions and labels[].definition:
| Field or label | Definition |
|---|---|
state: first_launch | The creator's first coin. |
state: on_record | Coins this creator launched before, and how many still trade. |
state: serial | Most of this creator's launches stopped trading in their first week. |
state: blocked | Under our launch rules, this creator can't launch or verify ownership of coins here. |
state: pending | Pending: we are still reading this creator's launches from the chains. |
still_trading | Still trading: a trade in the last 7 days. |
unknown | Unknown: no trade on record, and no word on whether the coin left its launch curve. |
stopped_within_7d | Stopped within 7 days: the coin's last trade came within 7 days of its launch, or it never left its launch curve. |
creator_sold | Creator sold: the creator sold or moved 25% or more of their coins in 24 hours. |
creator_exited | Creator exited: the creator holds 10% or less of what they launched with. |
new_identity | New identity: the creator's X account is under 30 days old, or their wallet is under 7 days old and was first funded by a wallet with no label, and the coin shares a ticker, a name or a logo with a coin trading now. |
history_unavailable_at_launch | History unavailable at launch: when this creator launched here, their launches elsewhere could not be read, so that launch was not checked against them. |
A blocked record names the kind of rule it matched in ruleHit (the block rule), and its definitions.rule is the same line for every rule:
This creator's record matches a pattern we refuse. Contest: support@chaindaddy.io.
First buyers (GET /api/v2/public/coins/{chain}/{symbol}/first-buyers) defines its labels the same way:
| Label | Definition |
|---|---|
creator_linked | Creator-linked: the creator's own wallet, a wallet they control, or one funded by the creator's wallets or their funder. |
fresh_wallet | Fresh wallet: first funded less than 7 days before this buy. |
bundled | Bundled: bought in the same block as 2 or more other wallets, or as another wallet with the same funder. |
known_sniper | Known sniper: labelled a sniper by our wallet-data provider from its past trades. |
The lines the read carries as figures, with the definitions the coin page shows:
| Line | Definition |
|---|---|
| Bundled at open | Supply bought in the first blocks by 3 or more wallets in the same block (or 2 with the same funder), and how many first buyers the creator controls or funded. |
| Wallet age | Days since the creator wallet first received funds. |
| First funded from | Where the creator wallet received its first funds, as the chain shows it. |
| Identity | What the creator proved they control: an X account, with the year it was created, and a wallet Coinbase attests belongs to a verified Coinbase account. |
| Backed forfeited | Earlier launches this creator Backed whose fees went to holders: the creator's wallets didn't record or keep the holding they committed. |
Confirmed extraction
The lists that state these rules, and the import rows, are on staging, not yet in prod.
A coin carries the Confirmed extraction label under the rule of whatever filed it, which every row of the lists states (setBy, rule):
setBy | rule |
|---|---|
watcher | Confirmed extraction: the creator exited, holding 10% or less of what they launched with, and within 24 hours the price closed 80% or more below its high of the day before, on Chain Daddy's own trades. |
admin | Confirmed extraction: confirmed by a person at Chain Daddy from the coin's on-chain record; the reason names the evidence. |
import | Confirmed extraction: the wallet that opened the pool removed 90% or more of its liquidity within 24 hours of opening, taking out more than it put in. |
A Creator exited row carries the creator_exited definition above.
Still trading, stopped within 7 days
Each launch in the history is judged on its own, from its launch date and its last trade. Liquidity is shown as its own figure and never decides it.
- Still trading: a trade in the last 7 days.
- Stopped: not trading, with a last trade on record more than 7 days ago; or a launch over 7 days old with no trade on record that our source says never left its launch curve (never bonded or migrated).
- Unknown: every other launch: no trade on record and no word on its curve, or one under 7 days old with no trade yet. It is counted on its own, never as stopped.
- Stopped within 7 days: a stopped launch with a known date whose last trade came less than 7 days after it launched, or that never left its launch curve.
launchesTotal counts every launch found: launchesAlive still trading, launchesUnknown unknown, and the rest stopped. launchesDead7d counts the ones that stopped within 7 days, and the serial rule weighs them against every launch with a known date, so an unknown launch never counts against the creator. first_launch means no earlier launch was found for the wallets we count, here or on the chains we read; while offPlatformPending is true, the chains have not been read yet.
What it cannot see
| Chain | Launches here | Launches elsewhere |
|---|---|---|
| Solana, Ethereum, Base, BNB Chain, Arbitrum, Robinhood Chain | read | read |
| Polygon | read | read, but when we measured we found no coin our provider names a deployer for |
| Avalanche | read | not read |
| Testnets | read | not read: our provider covers no testnet |
- Older coins on every chain may carry no deployer in our provider's data, so a creator whose earlier coins are old can read as a first launch. An empty history means nothing was found, not that there was nothing.
- A lookup reads up to 200 coins per wallet on each chain, and a wallet keeps its 200 newest launches.
- The last trades of coins launched here are on record from Oct 1, 2026. For coins elsewhere, the launch date and last trade are our provider's figures: the last trade is often missing on a coin that stopped, which then reads unknown unless our source says it never left its launch curve (on record from Oct 28, 2026).
- Holdings, Creator sold and Creator exited are watched on coins registered or launched here that traded in the last 7 days. Bundled at open and First buyers exist for launches here whose opening blocks we saw; nothing shows when they were not.
When it is computed
- Every launch build and every ownership verification computes the creator's record from what is stored, and queues the lookup of their launches elsewhere. A launch waits up to 3 seconds for a lookup that is due, so the rule judges a creator's history on their first launch here. If that lookup cannot finish, the launch goes ahead and the record says History unavailable at launch.
- An hourly pass refreshes the records that are due: daily while any of the creator's coins trades, weekly when none does. A wallet's lookup is kept for 24 hours.
- The lookups spend a daily budget. Once it is spent, a record that needs one reads
pending(offPlatformPending: true) until the next UTC day.
The block rule
The rule is published once, on the customer page: Who can't launch here. It runs when a creator launches a coin or verifies ownership of one; a coin already registered is never removed by it, and gets labels instead.
A blocked record names the kind of rule it matched in ruleHit:
ruleHit | The kind of rule |
|---|---|
confirmed_extraction | A wallet the record counts launched a coin labelled a confirmed extraction |
serial_rule | A launch history that is mostly coins that stopped trading in their first week |
admin_block | Support stopped the creator after a review |
The lines each rule draws are not published; a person's reply to a contest gives the specifics. Missing history and provider gaps never block. If the record cannot be read at that moment, the creator is asked to try again in a minute.
Our creator watch labels a confirmed extraction under the watcher rule above, and each one alerts a person at Chain Daddy to review it. A person can also label a coin from its on-chain record.
Confirmed extractions read from pool histories
On staging, not yet in prod.
The extraction import labels a coin a confirmed extraction from its pool's own transactions, under the import rule above. Moving the liquidity to another pool and leaving it there is not an extraction. When the remover deployed the coin, the label goes on the coin; when someone else seeded and drained a pool for another's coin, it goes on the pool's address and that wallet, never on the coin's deployer. Each row keeps its proof: the pool, the removal transaction, how much was taken and how soon.
| Chain | Pools read, each once it is 24 hours old |
|---|---|
| Solana | Raydium CPMM and AMM v4, PumpSwap, Meteora DAMM v2 and DLMM; launchpad graduations are skipped |
| Base | Uniswap V2 pairs, and Uniswap V4 pools with no hook, with an ETH or USDC side |
| BNB Chain | PancakeSwap V2 pairs with a BNB, USDT or USDC side |
Not read: Raydium CLMM, Meteora DAMM v1, Uniswap V3, hooked V4 pools, Aerodrome and the other V2 forks. A row's flaggedAt is when the import filed it; evidence.removedAt is when the liquidity left.
Contest and correction
A creator who is refused, or anyone who finds the record wrong about their wallet or coin, writes to support@chaindaddy.io with the coin or wallet; a creator writes from the account that launched. Support reads the same record the rule judged. When the record is wrong, support corrects it: the wallet can launch again, or the label comes off. If the record is wrong
A signed dispute, and the correction log
On staging, not yet in prod.
- A dispute needs no account: anyone who holds a wallet signs a message saying what the record, or a label on a coin, gets wrong, and sends it to
POST /api/v2/record/disputes, 3 a day per wallet. A person reviews every one; a dispute changes nothing by itself. Disputing the record - The correction log lists every override, every label cleared and every dispute decided, newest first, each with the reviewer's note:
GET /api/v2/public/record/corrections. It is append-only, and it names the role, never the person. Corrections
How to cite it
The record is a keyless read: no key and no sign-in, the same answer for every caller.
https://api.chaindaddy.io/api/v2/public/coins/{chain}/{symbol}/creator-record{chain} is the chain as it appears in the coin page's address (base, solana) and {symbol} its ticker. The coin's page is https://chaindaddy.io/{symbol}/{chain}.
- Cite the counts with their definitions, and the time you read them: the record changes as coins trade and lookups finish.
- Say what it is: "what Chain Daddy can see on-chain", never a verdict on a person.
- A registration you can prove: a coin's registration, signed says which wallet holds a ticker's registration, as a signed answer anyone checks against Chain Daddy's keys.
The lists and their dated snapshots
On staging, not yet in prod.
- The lists: every coin labelled Confirmed extraction or Creator exited, newest first, with the rule it was filed under and its evidence, as JSON, CSV or RSS:
GET /api/v2/public/record/extractionsand/record/exits(Record feeds). They hold what we have found, not every coin that ever did either. - Dated snapshots: each list as it stood at the end of a UTC day, oldest row first:
GET /api/v2/public/record/extractions/snapshots/{YYYY-MM-DD}.csv(and/record/exits/…), with the days there are at/record/extractions/snapshots. A finished day keeps its rows for good, so a count cited from one can be checked later; a row cleared afterwards stays in the days it stood, and the correction log says why it left. Dated snapshots - Cite a count from a snapshot with its day: "confirmed extractions on Chain Daddy's list at the end of Oct 29, 2026 (UTC)".