Network Architecture

High-level deployed architecture of Onyx Mainnet.

Onyx is an EVM-compatible Layer 1 secured by aBFT consensus.

Transactions
  -> public RPC/gRPC entry points
  -> consensus validators
  -> signed record streams
  -> regional mirror importers and databases
  -> Mirror REST/gRPC and JSON-RPC relays
  -> explorers, wallets, applications, and indexers

Consensus validators order transactions and produce the authoritative ledger record. Signed record streams feed regional mirror services, which provide query-oriented APIs and historical data. JSON-RPC relays translate EVM-facing requests and submit transactions through the network's native services.

This separation explains an important operational property: a read API or explorer can lag even while consensus remains healthy. Applications should compare independent signals and avoid treating one endpoint as proof of the entire network state.

Validator locations, private addresses, operator accounts, and deployment procedures are intentionally not published in user-facing documentation.