TRAXR
TRAXR-SOLANATRAXR-SOLANA | Architecture

TRAXR-SOLANA Architecture

NodeZero snapshots, local enrichments, and deterministic CTS scoring.

Architectural Overview

TRAXR-SOLANA is a read-only indexing layer for Solana pools. It prioritizes correctness, reproducibility, and explicit separation between raw source data, local enrichments, and scoring logic.

TRAXR SNAPSHOTSStamped · Enriched · DeterministicSolana PoolsNodeZeroLocal EnrichmentCTS ScoringUI + API

Read-only pipeline: NodeZero ingest, local enrichment, CTS scoring, and distribution

Core Data Pipeline

  1. NodeZero Ingestion
    Latest stamped Solana pool datasets for AMM, CLMM, CPMM, Orca Whirlpool, PumpSwap, Meteora DLMM, Meteora DAMM v2, and other tracked pools.
  2. Normalization & Enrichment
    Raw inputs are mapped into deterministic pool metrics, then enriched with exact quote-based signals where supported.
  3. CTS Scoring (Embedded)
    Pool-only CTS logic mirrors the backend scorer and computes depth, activity, impact, stability, trust, and fee posture.
  4. Presentation & Distribution
    Scores and warnings are surfaced via the UI and read-only API.

Read-Only by Design

TRAXR-SOLANA never signs transactions, never interacts with wallets, and never holds custody. All components operate in strict read-only mode.

Current Operating Architecture

  • Snapshot-based ingestion from NodeZero
  • Stamped JSON cache for repeatable runs and trend history
  • Fetch-time local enrichments before final write
  • Exact impact currently supported for AMM, CPMM, CLMM, Orca, and Meteora DLMM
  • Meteora DAMM v2 currently uses estimated local $1k impact modeling
  • PumpSwap currently uses estimated local $1k impact modeling
  • CTS scoring logic embedded in-app

Roadmap (Optional)

  • On-chain pool address resolution
  • CLMM impact performance optimization
  • Protocol-specific contract decoding
  • Historical snapshots for trend analysis
  • Cross-chain expansion

Design Principles

  • Indexing never guesses
  • Scoring never rewrites facts
  • Minimal scope and explicit TODOs
  • Incremental, auditable rollout

Architecture is introduced incrementally. Some protocol-specific depth paths still remain estimated until exact routing support is available.

Know the system. Know the risk.