mirror of
https://github.com/FlipsideCrypto/gitbook.git
synced 2026-02-06 10:47:06 +00:00
65 lines
3.1 KiB
Markdown
65 lines
3.1 KiB
Markdown
---
|
|
description: >-
|
|
Want to see what known entities like CEX, DEX, dApps, or NFT contracts are up
|
|
to? Labels can help!
|
|
---
|
|
|
|
# Labels
|
|
|
|
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.
|
|
|
|
## Contribute to our labels
|
|
|
|
To contribute to our labels, go to our [label submission form](https://science.flipsidecrypto.xyz/add-a-label/) 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 your contact information so we can reach out to you if there are any questions!
|
|
|
|
## Label Types
|
|
|
|
There are 10 label types within any blockchain.
|
|
|
|
1. [**cex** (Centralized Exchange)](cex-label-type.md)
|
|
2. [**dex** (Decentralized Exchange)](dex-label-type.md)
|
|
3. [**operator** (Chain Operations)](operator-label-type.md)
|
|
4. [**chadmin** (Chain Administration)](chadmin-label-type.md)
|
|
5. [**defi** (Decentralized Finance Applications)](defi-label-type.md)
|
|
6. [**nft** (NonFungible Token Contracts & Applications)](nft-label-type.md)
|
|
7. [**bridge** (Layer 2/ alt L1 Dapps)](layer2-label-type.md)
|
|
8. [**dapp** (Decentralized Applications)](other-label-type.md)
|
|
9. [**games** (Gaming Dapps)](games-label-type.md)
|
|
10. [**token** (Token Contracts)](token-label-type.md)
|
|
11. [**flotsam** (Junk or Other)](flotsam-label-type.md)
|
|
|
|
See [the Crosschain schema](broken-reference) 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
|
|
```
|
|
|
|
|
|
|