Changelog
Changes to the API, the rules that decide labels, and the engine behind them. Rule changes carry a version, and every label records the version it was decided under.
A cloner can copy a project’s website and X account and show its own contract address, so a website showing an address is not enough on its own. When an older token with the same name links a different website and X account and describes the project in the same words, the newer website may be a clone, and the identity is Unresolved until the older channels confirm an address. Found on one identity; its label moved from Likely original to Unresolved.
/v1 request now needs an API key in the Authorization: Bearer header. Without one it returns 401 missing_api_key; with a wrong or revoked one, 401 invalid_api_key.X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; over the limit, 429 rate_limited with Retry-After.A token is Likely original only when the project’s own website shows its contract address. Every other token with the name from a different wallet is a Copy; tokens from the same wallet are Same creator. When no website confirms anything, the project gets no label (unconfirmed). Pages that list many addresses, or the tokens of several projects, are treated as listings and never confirm a token.
New project websites are read as soon as they are found, projects under three days old every 30 minutes, older ones daily and unreachable ones weekly. When a website changes, every token with the affected names is relabelled in the same pass.
GET /v1/tokens?ids= answers up to 100 tokens in one request.GET /v1/tokens/{reference}/history returns every label a token has had, newest first.{"error": {"code", "message"}} with stable codes.rule, rules_version, updated_at and identity.original, the token the project’s channels point to.For a project launch without a label, the basis now says that the project’s website does not show the address and that SEAL does not read X accounts yet. It used to suggest that X had been checked.
A new history entry is written when a label, its rule or its basis changes, not only the label.
The API reference, the first research report, the Pantheon case study and a status page that reads the engine directly.
SEAL labels project launches and the tokens that copy them. Memes, tweet plays and tokens from farm wallets (four or more launches) get no label. When two project tokens with the same name link different websites and X accounts, the label is Unresolved.
The earliest token with a name was Likely original and later ones from other wallets were Copies. Retired the next day: about half of all copies are launched before the project’s own token, so launch order labelled real projects as copies. See the Pantheon case study.
GET /v1/tokens/{reference}The first endpoint: the label, its basis in one sentence, the token’s identity and the onchain evidence.
Every launch since the first on 2 November is read from the chain, and new launches are followed block by block.