TRAXR-AVAXTRAXR-AVAX | Data Model

TRAXR-AVAX Data Model

Indexed AVAX pool entities used for normalization and scoring.

Data Model Overview

TRAXR-AVAX operates on a read-only data model derived from AVAX C-Chain pool inputs. The model separates source-backed fields from derived heuristics and external scoring signals.

Core Entities

  • Pool Contract
    Pool address, identifiers, DEX attribution, and fee metadata.
  • Token Metadata
    Token name, symbol, address, and decimals from the source feed.
  • Snapshot
    Point-in-time capture of liquidity and volume metrics.

Deterministic Data Model

All TRAXR-AVAX scores are derived from a single snapshot. No predictions, no trading features, and no wallet interactions.

SnapshotDeterministic AVAX statePool ContractReserve ImbalanceDerived MetricsProtocol Flags

Snapshot-based data model - deterministic inputs - reproducible metrics

Derived Metrics

From core entities, TRAXR-AVAX derives normalized heuristics such as liquidity depth, reserve imbalance, and execution resilience context. These are marked as best-effort and never presented as protocol guarantees.

Scoring Signals (External)

Advanced signals such as reserve imbalance, fee stability, and governance risk are produced from normalized pool state and the scoring engine package. Unknown values remain explicit when reserves or pricing context are insufficient.

Current Alpha Data Model

  • Avalanche RPC snapshots cached in JSON
  • Manual/operational refresh cycle for validation
  • Deterministic normalization over cached state
  • Scoring handled by npm package
  • Legacy Gecko snapshots retained for transparent comparison

Evolution

The target data model can evolve toward continuous indexing and automated ingestion without altering core entity definitions.

Data structures are intentionally minimal to preserve auditability and reduce complexity during alpha.

Know the data. Know the risk.