Indexer

The Orica indexer is a background service that monitors the Solana blockchain and maintains a structured database of all protocol activity.

Purpose

The indexer solves fundamental challenges with blockchain data:

Challenge	Solution
No complex queries on-chain	Indexer writes to PostgreSQL with full SQL support
No historical data	Indexer stores snapshots at regular intervals
Slow RPC queries	Indexer pre-computes aggregations
Limited real-time updates	Indexer broadcasts via WebSocket

Data Pipeline

Indexed Data

The indexer tracks and stores:

Markets

Market creation events
Pool balances (outcome_pools)
Supply changes (outcome_supplies)
Status transitions
Resolution data

Trades

Buy transactions
Sell transactions
Redemption transactions
Fee calculations
Price at execution

Price Snapshots

Market cap per outcome
Supply per outcome
Volume per interval
Timestamp

Disputes

Dispute creation
Vote records
Messages and boosts
Resolution overrides

Snapshot Intervals

Price history is stored at configurable intervals:

Interval	Description
`1s`	Every second (raw data)
`1m`	Every minute
`5m`	Every 5 minutes
`15m`	Every 15 minutes
`1h`	Every hour
`4h`	Every 4 hours
`1d`	Every day

The API automatically aggregates and gap-fills snapshots based on the requested interval.

Real-Time Updates

The indexer broadcasts updates to connected WebSocket clients: Latency from transaction confirmation to WebSocket broadcast is typically 1-2 seconds.

Time Service

The indexer maintains an accurate representation of blockchain time:

Fetches current slot from Solana
Retrieves block time for that slot
Uses block time for all status computations

This ensures that market status (open/closed) is computed consistently across all clients, even if their system clocks differ.

Failure Handling

The indexer is designed for resilience:

Scenario	Handling
RPC disconnection	Automatic reconnection with exponential backoff
Missed transactions	Periodic full sync to catch gaps
Database downtime	Transaction buffering and retry
Invalid data	Logged and skipped without crashing

Health Monitoring

Check indexer status via the health endpoint:

curl https://api.orica.markets/health

Response:

{
  "status": "ok",
  "version": "1.0.0",
  "indexer_running": true,
  "websocket_connections": {
    "total": 42,
    "by_ip": { "..." }
  }
}

Getting Started

Core Concepts

Resolution

Technical Architecture

Purpose

Data Pipeline

Indexed Data

Snapshot Intervals

Real-Time Updates

Time Service

Failure Handling

Health Monitoring

Next Steps

API Reference

WebSocket

​Purpose

​Data Pipeline

​Indexed Data

​Snapshot Intervals

​Real-Time Updates

​Time Service

​Failure Handling

​Health Monitoring

​Next Steps

API Reference

WebSocket

Purpose

Data Pipeline

Indexed Data

Snapshot Intervals

Real-Time Updates

Time Service

Failure Handling

Health Monitoring

Next Steps