> For the complete documentation index, see [llms.txt](https://docs.onyx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyx.org/developer-guide/overview.md). # Network Architecture 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.onyx.org/developer-guide/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.