Skip to main content
Flipside provides two complementary systems for identifying and enriching blockchain addresses: labels and tags. These make raw blockchain data human-readable and enable more sophisticated analysis.

​
Labels vs Tags

Labels

One-to-one identifiers for addresses.A label gives an address a single, definitive name—like “Coinbase Hot Wallet” or “Uniswap V3: USDC-WETH Pool”. Labels are a source of truth added by Flipside.

Tags

Many-to-one descriptors for addresses.Tags describe behaviors or characteristics—an address can have multiple tags like “NFT Transactor Top 1%” or “DeFi Power User”. Tags have start and end dates.

​
Why this matters

Without labels, blockchain analysis requires interpreting raw addresses: 
0x1ab7...3f2c → 0x2bc9...8d4e
With labels, the same transaction becomes immediately understandable: 
Whale Wallet → Uniswap V3: USDC-WETH Pool
Labels make data human-readable and analysis much easier. Tags make addresses (especially EOAs that don’t have labels) more robust and analytics more accessible.

​
Labels

Labels are one-to-one names for addresses. Each labeled address has a single, authoritative identifier added by Flipside.

​
Label hierarchy

Flipside applies a 2-level hierarchy to all labeled addresses using these fields:
FieldDescriptionExamples
creatorName of the label creatorflipside, token terminal
label_typeHigh-level categorycex, dex, defi, nft, bridge
label_subtypeSpecific classificationhot_wallet, treasury, pool, contract_deployer
project_nameParent project/entityCoinbase, Uniswap, Aave
address_nameSpecific address descriptionCoinbase Hot Wallet 1, Uniswap V3: USDC-WETH
Event and balance tables are automatically enriched with label columns for any address-type column, following the naming pattern: {address_function}_{label_attribute}

​
Label types

There are 12 label types used across all blockchains:
Addresses belonging to centralized exchanges.
SubtypeDescription
hot_walletAddresses that collect funds from deposit wallets, send withdrawals, and hold the majority of exchange funds
deposit_walletCustomer deposit addresses
cold_walletRarely used wallets for long-term fund storage
chadminAdministrative addresses
contract_deployerContracts used to create other contracts
general_contractGeneral use contracts
multisigMultisig wallets
token_contractToken contracts owned by the exchange
Addresses belonging to centralized financial services (non-exchange).
SubtypeDescription
fundInvestment funds, hedge funds, and asset management entities
governmentGovernment-controlled or regulatory addresses
otcOver-the-counter trading desks and brokers
individualKnown individuals or high-profile entities
custodyCustodial service providers
contract_deployerContracts used to create other contracts
lendingCentralized lending and borrowing platforms
general_contractGeneral use contracts
treasuryTreasury addresses
token_contractToken contracts
Addresses belonging to decentralized exchanges.
SubtypeDescription
swap_contractContract used to facilitate token exchanges
poolFarming, staking, or liquidity pool addresses
vaultVault controlled by the DEX
fee_walletWallet for collected fees
daoDAO-controlled addresses
chadminAdministrative addresses
contract_deployerContracts used to create other contracts
foundationFoundation addresses
governanceGovernance addresses
rewardsReward distribution addresses
strategyStrategy control addresses
token_distributionSupply distribution addresses
token_saleInitial token sale addresses
token_contractToken contracts
general_contractGeneral contracts
multisigMultisig contracts
Addresses belonging to DeFi protocols.
SubtypeDescription
poolFarming, staking, or liquidity pool addresses
vaultVault controlled by the protocol
fee_walletWallet for collected fees
daoDAO-controlled addresses
votingVoting addresses
chadminAdministrative addresses
contract_deployerContracts used to create other contracts
treasuryTreasury addresses
governanceGovernance addresses
rewardsReward distribution addresses
oracleOracle contracts
token_saleInitial token sale addresses
token_contractToken contracts
general_contractGeneral contracts
multisigMultisig contracts
Addresses belonging to NFT projects or marketplaces.
SubtypeDescription
nf_token_contractNon-fungible token contracts
token_contractFungible token contracts owned by the project
marketplaceMarketplace contracts for sales and trades
contract_deployerContracts used to create other contracts
fee_contractFee collection contracts
general_contractGeneral contracts
Addresses belonging to bridge protocols and Layer 2 projects.
SubtypeDescription
token_contractToken contracts
general_contractGeneral contracts
Addresses belonging to blockchain games.
SubtypeDescription
nf_token_contractNon-fungible token contracts
token_contractToken contracts
marketplaceIn-game marketplace contracts
airdrop_contractAirdrop distribution contracts
chadminAdministrative addresses
contract_deployerContracts used to create other contracts
daoDAO-controlled addresses
oracleOracle contracts
rewardsReward distribution addresses
treasuryTreasury addresses
general_contractGeneral contracts
Addresses necessary for blockchain function.
SubtypeDescription
validatorAddresses that run nodes and/or validate blocks
mining_poolKnown mining pools
solo_minerIndividual addresses that received block rewards
Addresses used for blockchain-wide administrative purposes.
SubtypeDescription
genesisMint or burn addresses (e.g., the all 0’s address on Ethereum)
foundationChain foundation addresses
general_contractOther administrative contracts
Stand-alone token contracts not belonging to a larger project.
SubtypeDescription
token_contractFungible token contracts (e.g., WETH, stablecoins)
General decentralized applications not fitting other categories.
Junk, spam, or uncategorized addresses.

​
How we source labels

Our labels team manually researches and verifies addresses through:
  • Protocol documentation — White papers, official docs, and GitHub repositories
  • Community channels — Discord servers, governance forums, and Twitter
  • On-chain analysis — Tracing contract deployments and fund flows
  • Partner data — Collaborations with foundations and ecosystem teams (Solana FM, NEAR Foundation, etc.)
  • Subgraph queries — Using The Graph and Messari subgraphs for liquidity pools
  • User submitted labels — Labels submitted by our community members

​
Contributing labels

While labels are curated by the Flipside team, you can submit label suggestions:

Submit a label

Use our label submission tool to suggest new address labels. Submissions are reviewed by our labels team before being added. Be sure to add your contact information so we can reach out with questions.

​
Tags

Tags are many-to-one descriptors that capture behaviors, characteristics, or group memberships. A single address can have multiple tags that change over time.

​
Tag structure

FieldDescriptionExamples
tag_typeCategory of behavioractivity, holdings, trading
tag_nameSpecific descriptornft_transactor_top_1pct, defi_power_user, whale
start_dateWhen the tag first appliedDate of first qualifying behavior
end_dateWhen the tag expired (if applicable)NULL for active tags

​
Time-based tags

Unlike labels, tags have temporal boundaries. An address might be tagged as “NFT Whale” during a bull market but lose that tag when their holdings decrease. This enables:
  • Historical analysis — See what tags an address had at any point in time
  • Behavioral tracking — Monitor how address activity patterns change
  • Cohort analysis — Group addresses by tags during specific periods

​
Contributing tags

Tags are open source—anyone can contribute new tag definitions:

Contribute tags

Submit a pull request to add new tag definitions. You can view existing tag logic and propose new behavioral classifications.

​
Accessing labels and tags

Labels and tags are available in every blockchain schema.

​
Labels table

SELECT
    address,
    label_type,
    label_subtype,
    address_name,
    project_name
FROM ethereum.core.dim_labels
WHERE label_type = 'cex'
LIMIT 10;

​
Tags table

SELECT
    address,
    tag_type,
    tag_name,
    start_date,
    end_date
FROM crosschain.core.dim_tags
WHERE tag_name LIKE '%whale%'
    AND end_date IS NULL  -- Currently active tags
LIMIT 10;

​
Cross-chain labels and tags

For analysis spanning multiple blockchains, use the crosschain schema: 
-- Labels across all chains
SELECT * FROM crosschain.core.dim_labels;

-- Tags across all chains
SELECT * FROM crosschain.core.dim_tags;

dim_labels

Cross-chain address labels

dim_tags

Cross-chain address tags

address_labels

Legacy labels table

address_tags

Legacy tags table