How labels are worded
We say a wallet is linked to something. We never say a wallet is someone.
On-chain data shows what a wallet did: who sent it money, who it paid and when. It does not show who holds the private key. A label is our reading of that activity, and the wording keeps that clear.
| We write | We do not write |
|---|---|
| Linked to Bitget | Owned by Bitget |
| Linked to a tracked team | This is the token's developer |
| Funded by a wallet linked to OKX | Bought by an OKX user |
Where labels come from
Each label carries its source, which you can see by hovering over a tag:
- Label store: exchange, service, bridge and app wallets, compiled and checked by us.
- Funding heuristic and Mesh heuristic: links worked out from funding patterns. These are marked proven when a transaction ties the wallets together directly, and probable when the pattern is strong but indirect.
- Deposit heuristic: exchange deposit addresses, recognised by how money moves through them.
- Our own research: wallets we have traced by hand.
Flags
Flags describe behaviour rather than identity:
- Bot: the wallet acts like automated trading software.
- Service wallet: the wallet belongs to an app or service and handles many users' money.
- Exchange: the wallet is linked to an exchange.
- Team: the wallet is linked to a tracked team.
Bot and service wallets are never shown as team members, even when they sit in a team's funding tree. A trading bot that touched a team wallet is not part of the team.
If a label is wrong
Labels are opinions based on evidence, and evidence can mislead. If you think a label is wrong, tell us the address and why, and we will look again.