| description |
|---|
Want to see what known entities like CEX, DEX, dApps, or NFT contracts are up to? Labels can help! |
Labels identify known addresses that are associated with a CEX, DEX, NFT project, liquidity pool, or other entity.
How are labels different from tags? Labels are a "source of truth" added by Flipside core contributors across all chains. Each known address receives only one label. Not every address has a label.
To contribute to our labels, go to our label submission form and follow the steps there to submit a label. We will review all submitted labels and add accurate labels to our tables. Be sure to add a discord handle so we can reach out to you if there are any questions!
There are 10 label types within any blockchain.
- cex (Centralized Exchange)
- dex (Decentralized Exchange)
- operator (Chain Operations)
- chadmin (Chain Administration)
- defi (Decentralized Finance Applications)
- nft (NonFungible Token Contracts & Applications)
- bridge (Layer 2/ alt L1 Dapps)
- dapp (Decentralized Applications)
- games (Gaming Dapps)
- token (Token Contracts)
- flotsam (Junk or Other)
See the Crosschain schema for the table containing all labeled addresses.
Flipside applies a 2-level hierarchy to all labeled addresses using 4 field attributes.
| creator | Name of the creator of the label |
|---|---|
| label_type | A high-level category describing the addresses main function or ownership (e.g. exchange) |
| label_subtype | A sub-category nested within label type providing further detail (e.g. exchange deposit wallet) |
| project_name (label) | The name of the entity that controls the address (e.g. Binance). |
| address_name | A description of the use of the address by the controlling entity (e.g. Binance deposit wallet) |
Note: on Event and Balance tables there is no need to join a secondary table to group or filter by label attributes .
{% hint style="info" %}
Events and Balance tables are automatically enriched with label columns corresponding to any column that contains an address type. The pattern for these columns names is: {address_function}_{label_attribute}
{% endhint %}
For example, in an events table, the following columns would be present to account for labels on the event_from . These would also exist for event_to, tx_from,tx_to, etc.
event_from_label_type
event_from_label_subtype
event_from_label
event_from_address_name