> ## Documentation Index
> Fetch the complete documentation index at: https://docs.webacy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Label Types

> Reference for Webacy address label types including cex, dex, defi, nft, operator, and chadmin classifications used to identify wallet purpose.

## Overview

The Webacy API categorizes blockchain addresses into label types to help identify the nature and purpose of addresses.

## Primary Label Types

| Type       | Description                           |
| ---------- | ------------------------------------- |
| `cex`      | Centralized Exchange                  |
| `dex`      | Decentralized Exchange                |
| `operator` | Chain Operations (validators, miners) |
| `chadmin`  | Chain Administration                  |
| `defi`     | Decentralized Finance Applications    |
| `nft`      | NFT Contracts & Applications          |
| `bridge`   | Layer 2/Alt L1 Bridge Dapps           |
| `dapp`     | Decentralized Applications            |
| `games`    | Gaming Dapps                          |
| `token`    | Token Contracts                       |
| `flotsam`  | Junk or Uncategorized                 |

***

## Label Subtypes

### Centralized Exchange (cex)

| Subtype             | Description                                                  |
| ------------------- | ------------------------------------------------------------ |
| `hot_wallet`        | Addresses that collect funds from deposits, send withdrawals |
| `deposit_wallet`    | Exchange deposit addresses                                   |
| `cold_wallet`       | Rarely-used fund storage                                     |
| `chadmin`           | Exchange administration                                      |
| `contract_deployer` | Contract creation contracts                                  |
| `general_contract`  | General-purpose contracts                                    |
| `multisig`          | Multi-signature wallets                                      |
| `token_contract`    | Exchange-owned tokens                                        |

### Decentralized Exchange (dex)

| Subtype              | Description                       |
| -------------------- | --------------------------------- |
| `swap_contract`      | Token exchange facilitation       |
| `token_contract`     | DEX-associated tokens             |
| `pool`               | Farming, staking, liquidity pools |
| `vault`              | DEX-controlled vaults             |
| `fee_wallet`         | Fee collection                    |
| `dao`                | DAO control addresses             |
| `chadmin`            | Administrative addresses          |
| `contract_deployer`  | Contract creators                 |
| `foundation`         | Foundation addresses              |
| `governance`         | Governance contracts              |
| `rewards`            | Reward distribution               |
| `strategy`           | Strategy contracts                |
| `token_distribution` | Token distribution contracts      |
| `token_sale`         | Token sale contracts              |
| `general_contract`   | General contracts                 |
| `multisig`           | Multi-signature wallets           |

### Operator

| Subtype       | Description                                  |
| ------------- | -------------------------------------------- |
| `validator`   | Addresses that run nodes and validate blocks |
| `mining_pool` | Known mining pools                           |
| `solo_miner`  | Individual block reward recipients           |

### Chain Admin (chadmin)

| Subtype            | Description                |
| ------------------ | -------------------------- |
| `genesis`          | Mint/burn addresses        |
| `foundation`       | Chain foundation addresses |
| `general_contract` | Other chadmin contracts    |

### DeFi

| Subtype             | Description          |
| ------------------- | -------------------- |
| `token_contract`    | DeFi tokens          |
| `pool`              | Liquidity pools      |
| `vault`             | Vaults               |
| `fee_wallet`        | Fee collection       |
| `dao`               | DAO addresses        |
| `voting`            | Voting contracts     |
| `chadmin`           | Admin addresses      |
| `contract_deployer` | Contract deployers   |
| `treasury`          | Treasury addresses   |
| `governance`        | Governance contracts |
| `rewards`           | Reward contracts     |
| `oracle`            | Price oracles        |
| `token_sale`        | Token sales          |
| `general_contract`  | General contracts    |
| `multisig`          | Multi-sig wallets    |

### NFT

| Subtype             | Description        |
| ------------------- | ------------------ |
| `token_contract`    | Fungible tokens    |
| `nf_token_contract` | NFT contracts      |
| `contract_deployer` | Contract deployers |
| `fee_contract`      | Fee contracts      |
| `marketplace`       | NFT marketplaces   |
| `general_contract`  | General contracts  |

### Flotsam (Risky/Junk)

| Subtype | Description                         |
| ------- | ----------------------------------- |
| `toxic` | Scams, attacks, malicious addresses |
| Other   | Uncategorized addresses             |

***

## Using Labels in Risk Assessment

Labels provide context for risk evaluation:

```javascript theme={null}
function assessRisk(address, labels) {
  // Known exchanges are generally lower risk
  if (labels.type === 'cex' && labels.subtype === 'hot_wallet') {
    return 'low';
  }

  // Toxic flotsam is high risk
  if (labels.type === 'flotsam' && labels.subtype === 'toxic') {
    return 'high';
  }

  return 'medium';
}
```

## Response Example

```json theme={null}
{
  "address": "0x...",
  "labels": {
    "type": "cex",
    "subtype": "hot_wallet",
    "name": "Binance",
    "confidence": 0.99
  }
}
```

<Tip>
  Need more granular labels? Contact our team at [info@webacy.com](mailto:info@webacy.com) to discuss custom label solutions.
</Tip>