Data Processing & Normalization

Common guarantees:

Normalization removes upstream quirks. The goal is predictable, protocol-agnostic outputs.

Normalization rules (what clients should rely on)

• Aggregations (OHLCV, volumes, pool stats).

• Enrichment (token metadata, decoded instructions).

• Cross-source joins (DEX trade + price + metadata).

Services may also compute derived views:

• Solana RPC providers.

• Protocol-specific adapters.

• Redis caches for hot paths.

Services fetch from:

Fetch and derive

Domain services are responsible for correctness and normalization. They translate upstream-specific behaviors into stable Acceso schemas.

• Consistent field naming across endpoints.

• Standard timestamp representation.

• Stable numeric formatting rules.

• Unified pagination patterns.

Normalization happens before caching when possible. This keeps cached payloads consistent across upstream vendors.