Skip to main content
Schema: aptos.core Table: dim_aptos_names Type: View

Description

This table contains comprehensive information about Aptos Names, the blockchain’s naming service that allows users to register human-readable domain names linked to their wallet addresses. The table tracks all registered names including domains, subdomains, ownership details, registration status, and expiration information. Aptos Names function similarly to ENS on Ethereum, providing a user-friendly way to identify and interact with addresses on the Aptos network through memorable names rather than long hexadecimal addresses.

Key Use Cases

  • Aptos Name registration and ownership analysis
  • Domain name tracking and expiration monitoring
  • User identity mapping and address resolution
  • Subdomain management and hierarchical name analysis
  • Primary name identification for user profile analysis
  • Name service adoption and usage pattern analysis

Important Relationships

  • Enriches address information across core models by providing human-readable names
  • Links to transaction data in core.fact_transactions through owner and registered addresses
  • Supports transfer analysis in core.fact_transfers and core.ez_transfers with named addresses
  • Enables user-friendly analytics by resolving addresses to readable names
  • Provides context for user behavior analysis through named entity identification

Commonly-used Fields

  • token_name: Full Aptos Name identifier for display and filtering
  • domain: Primary domain name for categorization and analysis
  • owner_address: Address that owns the name for ownership analysis
  • registered_address: Address the name resolves to for address mapping
  • is_active: Status indicator for valid and active names
  • is_primary: Flag for identifying primary names for users
  • expiration_timestamp: Critical for name renewal and expiration analysis

Columns

Column NameData TypeDescription
TOKEN_NAMETEXTThe full Aptos Name identifier, representing the complete human-readable name registered on the Aptos blockchain.
Data type: String Example:
  • alice.apt
  • bob.test.apt
  • mydomain.apt
Business Context:
  • Primary identifier for Aptos Name registration and ownership analysis.
  • Essential for user identity mapping and address resolution.
  • Enables human-readable analytics and user-friendly reporting. | | DOMAIN | TEXT | The primary domain name component of an Aptos Name, representing the main identifier without subdomains or suffixes.
Data type: String Example:
  • alice
  • bob
  • mydomain
Business Context:
  • Essential for domain categorization and primary name analysis.
  • Critical for domain ownership tracking and registration analysis.
  • Enables domain-level analytics and trend analysis. | | DOMAIN_WITH_SUFFIX | TEXT | The domain name including the blockchain suffix, representing the complete domain identifier with the .apt extension.
Data type: String Example:
  • alice.apt
  • bob.apt
  • mydomain.apt
Business Context:
  • Essential for complete domain identification and suffix analysis.
  • Critical for domain registration tracking and ownership verification.
  • Enables suffix-based analytics and domain categorization. | | SUBDOMAIN | TEXT | The subdomain component of an Aptos Name, representing the hierarchical identifier below the primary domain.
Data type: String Example:
  • test
  • dev
  • staging
Business Context:
  • Essential for subdomain management and hierarchical name analysis.
  • Critical for organizational structure analysis and subdomain tracking.
  • Enables subdomain-level analytics and usage pattern recognition. | | OWNER_ADDRESS | TEXT | The account address that owns the Aptos Name, representing the entity with control over the name registration.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for ownership analysis and name control tracking.
  • Critical for ownership transfer analysis and registration management.
  • Enables owner-based analytics and name portfolio analysis. | | REGISTERED_ADDRESS | TEXT | The account address that the Aptos Name resolves to, representing the target address for name resolution.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for name resolution analysis and address mapping.
  • Critical for understanding the relationship between names and addresses.
  • Enables resolution-based analytics and address correlation. | | IS_ACTIVE | BOOLEAN | Boolean value indicating whether the Aptos Name is currently active and valid for use.
Data type: Boolean Example:
  • true (name is active)
  • false (name is inactive)
Business Context:
  • Essential for filtering active names and status analysis.
  • Critical for name lifecycle analysis and expiration tracking.
  • Enables active name analytics and status-based reporting. | | IS_PRIMARY | BOOLEAN | Boolean value indicating whether the Aptos Name is the primary name for the owner, representing their main identifier.
Data type: Boolean Example:
  • true (primary name for owner)
  • false (secondary name for owner)
Business Context:
  • Essential for identifying primary names and user profile analysis.
  • Critical for understanding name hierarchy and user preferences.
  • Enables primary name analytics and user identity analysis. | | TOKEN_STANDARD | TEXT | The token standard used for the Aptos Name, indicating the technical specification and implementation details.
Data type: String Example:
  • v1
  • v2
Business Context:
  • Essential for technical analysis and standard compliance tracking.
  • Critical for understanding name implementation and feature availability.
  • Enables standard-based analytics and technical categorization. | | EXPIRATION_TIMESTAMP | TIMESTAMP_NTZ | The timestamp when the Aptos Name registration expires, indicating when the name will become inactive.
Data type: Timestamp Example:
  • 2024-12-31 23:59:59.000000
Business Context:
  • Essential for expiration monitoring and renewal analysis.
  • Critical for name lifecycle management and expiration tracking.
  • Enables expiration-based analytics and renewal prediction. | | LAST_TRANSACTION_VERSION | NUMBER | The version number of the last transaction that modified the Aptos Name, representing the most recent update.
Data type: Integer Example:
  • 12345678
  • 98765432
Business Context:
  • Essential for tracking name modification history and update analysis.
  • Critical for understanding name lifecycle and change tracking.
  • Enables version-based analytics and modification pattern recognition. | | DIM_APTOS_NAMES_ID | TEXT | The unique primary key identifier for each row in the table, ensuring data integrity and uniqueness.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for data integrity and unique row identification.
  • Critical for join operations and data relationship management.
  • Enables precise data retrieval and referential integrity maintenance. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was inserted into the table, representing when the data was first recorded.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data lineage tracking and insertion timing analysis.
  • Critical for understanding data freshness and processing delays.
  • Enables data quality analysis and processing performance monitoring. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was last modified, representing when the data was most recently updated.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data freshness analysis and update tracking.
  • Critical for understanding data modification patterns and change frequency.
  • Enables data quality monitoring and update performance analysis. |