TRAXR-SOLANA Docs

Reference pages for how TRAXR-SOLANA works, how data flows through the system, and how to query the read-only API.

TRAXR-SOLANA | Data Model

TRAXR-SOLANA Data Model

Indexed Solana pool entities used for normalization and scoring.

Data Model Overview

TRAXR-SOLANA operates on a read-only data model derived from Solana pool inputs. The model separates source-backed fields from derived heuristics and embedded scoring signals.

Core Entities

Pool Program
Pool address, identifiers, program attribution, and fee metadata.
Token Metadata
Token name, symbol, mint, decimals, and selected logo enrichment where available.
Snapshot
Point-in-time capture of liquidity and volume metrics.

Deterministic Data Model

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

Snapshot-based data model - deterministic inputs - reproducible metrics

Derived Metrics

From core entities, TRAXR-SOLANA derives normalized heuristics such as liquidity depth, snapshot-history stability, and $1,000 quote-based price impact.

Scoring Signals (Embedded)

Pool-only CTS signals (depth, activity, stability, trust, fee, impact) are computed in-app using the same logic as the backend scorer.

Exact impact is currently supported for AMM, CPMM, CLMM, Orca, and Meteora DLMM. Meteora DAMM v2 is currently modeled with local estimated impact.

Current Operating Data Model

NodeZero snapshots cached in stamped JSON files
Fetch-time local enrichment before final write
Deterministic normalization over cached state
CTS scoring handled in-app

Evolution (Optional)

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 integration complexity while coverage continues to expand.