Database inventory

Overview

The current microservices use helper-backed PostgreSQL databases. From the inspected daemon wiring these are chaindb, opsdb, extdb, intdb, and comptrollerdb.

This page summarises the known purpose and contents of the current databases from the supplied source material.

extdb (schema version 4)

extdb stores external market and reference data, together with compliance-derived transaction flags.

  • t_metadata: generic key/value JSONB metadata, including schema version
  • t_fx: provider/base/counter timestamped exchange rates
  • t_benchmark_rates: named benchmark rates by currency and timestamp
  • t_overnight_rates: Attestant overnight rate calculations by date and percentile, with notes
  • t_eth_breaks: Ethereum compliance break events keyed by relay/height/tx/address
  • t_eth_breaks.f_source: text array indicating source list(s), for example OFAC SDN

intdb (schema version 2)

intdb is a small internal workflow and summary database for reward distribution job tracking and AUM rollups.

Schema metadata

  • t_metadata: generic key/value JSONB metadata, including schema version

Reward distribution jobs

  • t_solana_reward_distributions: Solana reward distribution requests, stored distributions payload, status, optional error, and lifecycle timestamps

AUM summaries

  • t_aum_summary: timestamped asset-under-management summary rows by asset and denomination, with total stake and own-stake amounts

opsdb (schema version 25)

opsdb is the application and operations database for customers, users, validator assignments, configuration, and customer-facing financial records across multiple networks.

Core metadata

  • t_metadata: schema and process metadata

Users and authentication artifacts

  • t_users: user profile, authentication flags, timezone/currency, UI preferences, and reporting and billing configuration JSON fields
  • t_user_tokens: API and access tokens scoped to users
  • t_user_files: user-published files such as invoices, reports, and statements, with MIME and data payloads
  • t_audit: audit trail of user operations, including IP, action, success or failure, and error

MEV and proposer configuration

  • t_eth_mev_relays: catalog of MEV relays
  • t_proposer_config_histories: time-ranged proposer config history per customer and subaccount

Validator and customer relationship model

  • t_customer_validators: validator assignment state per customer, including proposer config and optional Rocket Pool or EigenLayer JSON attachments
  • t_unassigned_validators: lifecycle pool for unassigned validators
  • t_rejected_validators: lifecycle pool for rejected validators
  • t_customer_epoch_metrics: per-customer, per-epoch aggregated performance metrics

Financial and accounting records

  • t_customer_financials: primary customer financial ledger-style entries for capital and income deltas, balance, and notes
  • t_near_financials: NEAR-specific financial entries with epoch metadata and NEAR price

Staking and delegation by ecosystem

  • t_customer_rocketpool_node_operators
  • t_customer_eigenpods
  • t_customer_starknet_delegators
  • t_customer_solana_delegators
  • t_customer_near_delegators: includes validator address

Chain metadata reference

  • t_chainmeta: network constants such as deposit contract addresses, genesis roots, fork versions, minimum deposit, and genesis timestamp for networks including Mainnet, Sepolia, Holesky, and Hoodi

comptrollerdb (schema version 1)

comptrollerdb is a MEV relay and comptroller analytics database centred on registrations, bids, and block payment outcomes.

Schema metadata

  • t_metadata: generic key/value JSONB metadata, including schema version

Relay registration data

  • t_validator_registrations: validator registrations sent to relays, including fee recipient, gas limit, timestamp, and signature

Bid comparison and bid flow

  • t_alternate_bids: chosen relay/value versus best available relay/value for a slot
  • t_received_bids: bids received by relays, including proposer/builder identities, block hashes, gas fields, timestamp, and bid value
  • t_delivered_bids: bids actually delivered by relays, with proposer/builder identities, block hashes, gas fields, and bid value

Block payment outcomes

  • t_block_payments: proposer and builder payment information per execution block, including expected proposer payment and fee recipients

chaindb (schema version 16)

chaindb is the Ethereum consensus and execution chain data warehouse used for indexing, analytics, and reward and accounting derivations.

Chain identity and metadata

  • t_metadata
  • t_chain_spec
  • t_genesis
  • t_fork_schedule

Validator state and balances

  • t_validators: canonical validator registry and lifecycle epochs
  • t_validator_balances: per-epoch balances and effective balances

Block-level canonical chain and execution payload data

  • t_blocks: beacon blocks with canonical marker and blob KZG commitments
  • t_block_execution_payloads: execution payload fields including block number/hash, fee recipient, gas/base fee, timestamp, and blob gas fields

Consensus duties and events

  • t_beacon_committees
  • t_proposer_duties
  • t_attestations
  • t_sync_aggregates
  • t_sync_committees
  • t_attester_slashings
  • t_proposer_slashings
  • t_voluntary_exits
  • t_deposits
  • t_eth1_deposits

Execution and withdrawal transition data

  • t_block_bls_to_execution_changes
  • t_block_withdrawals
  • t_block_deposit_requests
  • t_block_withdrawal_requests
  • t_block_consolidation_requests
  • t_blob_sidecars

Derived summaries for analytics and reporting

  • t_validator_epoch_summaries
  • t_validator_day_summaries
  • t_block_summaries
  • t_epoch_summaries