| COIN_TYPE | TEXT | Fully qualified Move type identifier for coins/tokens. Format: {package}::{module}::{struct}. Example: 0x2::sui::SUI for native SUI token. Essential for DeFi analytics, token classification, and cross-asset analysis. |
| DECIMALS | NUMBER | Number of decimal places for the token. Integer value defining token precision (e.g., 9 for SUI means 1 SUI = 1,000,000,000 MIST). Essential for accurate token amount calculations, display formatting, and cross-token analytics. Example: 9. |
| SYMBOL | TEXT | Short string symbol for the token (e.g., ‘SUI’, ‘USDC’). Used for user-friendly token identification, UI display, and analytics grouping. Example: ‘SUI’. |
| NAME | TEXT | Full descriptive name of the token. Human-readable string for complete token identification, used in interfaces and analytics. Example: ‘Sui Token’. |
| DESCRIPTION | TEXT | Detailed description of the token’s purpose, features, and technical details. Used for documentation, analytics, and user interfaces. Example: ‘Native token of the Sui blockchain, used for gas and staking.‘ |
| ICON_URL | TEXT | Web URL pointing to the token’s icon image. Used for visual representation in wallets, dApps, and analytics dashboards. Example: ‘https://assets.sui.io/icons/sui.svg’. |
| OBJECT_ID | TEXT | Unique identifier for the token metadata record, linking metadata to on-chain token types. Used for metadata management, registry operations, and analytics joins. Example: ‘tokenmeta_123’. |
| DIM_TOKENS_ID | TEXT | Surrogate key for the tokens dimension table. Generated unique identifier for each token metadata record, typically derived from the coin type or on-chain metadata. Enables efficient token lookups, joins across fact tables, and lineage tracing from raw on-chain data to analytics-ready attributes. In Sui, this is critical for accurate token identification, decimal normalization, and cross-model analytics involving token flows and balances. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | Timestamp when the record was inserted into the analytics database. System-generated by the ETL pipeline, typically in TIMESTAMP_NTZ format. Used for data lineage, ETL monitoring, and freshness checks. In Sui analytics, this field is essential for tracking data ingestion latency, validating pipeline health, and supporting incremental model builds. Example: ‘2024-06-01 12:34:56.789’. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | Timestamp when the record was last modified in the analytics database. System-generated for change tracking, data versioning, and consistency verification. In Sui, this supports incremental processing, late-arriving data correction, and auditability of analytics workflows. Used to monitor data staleness and trigger downstream updates. Example: ‘2024-06-01 12:34:56.789’. |