Skip to main content
Schema: near.core Table: dim_address_labels Type: View

​
Description

This table contains comprehensive address labeling and categorization data for the NEAR Protocol blockchain, providing human-readable names, project associations, and classification information for accounts and contracts. The data includes both manual and automated labeling from multiple sources, enabling enhanced analytics by providing context about wallet ownership, contract purposes, and project affiliations. This dimension table supports all other gold models by providing enriched address information for improved data interpretation and user experience.

​
Key Use Cases

  • Enhanced transaction analysis with human-readable address names
  • Project-specific activity tracking and protocol analysis
  • Whale and institutional wallet identification and monitoring
  • Contract categorization and smart contract ecosystem analysis
  • Compliance and regulatory reporting with entity identification
  • User experience improvement in analytics dashboards and reports
  • Cross-protocol address correlation and analysis

​
Important Relationships

  • Enriches all fact tables by providing address context and labels
  • Supports core.ez_token_transfers with sender and receiver labeling
  • Enhances defi.ez_dex_swaps with protocol and user identification
  • Improves defi.ez_bridge_activity with bridge protocol labeling
  • Enables better analysis in nft.ez_nft_sales with marketplace identification
  • Powers stats.ez_core_metrics_hourly with labeled activity metrics

​
Commonly-used Fields

  • address: Essential for joining with transaction and transfer data
  • address_name: Critical for human-readable analytics and reporting
  • project_name: Important for protocol-specific analysis and categorization
  • label_type and label_subtype: Essential for address categorization and filtering
  • l1_label and l2_label: Important for hierarchical classification analysis
  • creator: Useful for understanding label source and reliability

​
Columns

Column NameData TypeDescription
SYSTEM_CREATED_ATTIMESTAMP_LTZThe timestamp for when the label was created by the Flipside label tool.
BLOCKCHAINTEXTToken symbol (e.g., ‘wNEAR’, ‘SWEAT’). This field contains the abbreviated identifier for the token as commonly used in trading pairs, price feeds, and user interfaces. Token symbols are typically 2-6 characters long and provide a quick way to identify tokens without using their full contract addresses. Examples include ‘NEAR’ for the native token, ‘wNEAR’ for wrapped NEAR, and ‘USDC’ for USD Coin.
ADDRESSTEXTThe NEAR address that corresponds with a label.
ADDRESS_NAMETEXTThe name attributed to the address. This is a human-readable identifier that provides context about what the address represents, such as “Binance Hot Wallet”, “Uniswap V3 Router”, or “NEAR Foundation Treasury”. Address names help users understand the purpose and ownership of blockchain addresses without needing to memorize cryptographic addresses.
PROJECT_NAMETEXTThe associated project name, if applicable. This field identifies the specific protocol, application, or organization that the address is associated with. For example, addresses might be labeled with project names like “Ref Finance”, “Aurora”, “NEAR Foundation”, or “Binance”. This helps categorize addresses within the broader ecosystem and provides context about which protocol or organization they belong to.
LABEL_TYPETEXTA high-level category describing the address’s main function or ownership. This field provides broad classification of addresses into major categories such as “cex” (centralized exchange), “dex” (decentralized exchange), “dapp” (decentralized application), “games”, “defi” (decentralized finance), “infrastructure”, or “governance”. Label types help users quickly understand the primary purpose or category of an address within the blockchain ecosystem.
LABEL_SUBTYPETEXTA sub-category nested within label_type providing further detail. This field offers more specific classification within the broader label_type category. Examples include “contract_deployer”, “hot_wallet”, “token_contract”, “liquidity_pool”, “governance_contract”, “bridge_contract”, or “validator”. Label subtypes provide granular detail about the specific role or function of an address within its broader category.
L1_LABELTEXTDeprecating soon. This is the same column label type, but is being kept for compatibility until 3/1/2023. TODO - deprecate.
L2_LABELTEXTDeprecating soon. This is the same column label subtype, but is being kept for compatibility until 3/1/2023. TODO - deprecate.
CREATORTEXT
DIM_ADDRESS_LABELS_IDTEXTA unique identifier for the record.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe timestamp at which the record was initially created and inserted into this table.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe timestamp at which this record was last modified by an internal process.