> For the complete documentation index, see [llms.txt](https://zchains.gitbook.io/zchains-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zchains.gitbook.io/zchains-whitepaper/architecture/overview.md). # Architecture Overview We started with the idea of making software that is *modular*. This is something that is present in almost all parts of the ZChains. Below, you will find a brief overview of the built architecture and its layering. ### ZChains Layering ![Polygon Edge Architecture](https://github.com/ZChain-168168/zchain-docs/blob/main/img/Architecture.jpg) ### Libp2p It all starts at the base networking layer, which utilizes **libp2p**. We decided to go with this technology because it fits into the designing philosophies of ZChains. Libp2p is: * Modular * Extensible * Fast Most importantly, it provides a great foundation for more advanced features, which we'll cover later on. ### Synchronization & Consensus The separation of the synchronization and consensus protocols allows for modularity and implementation of **custom** sync and consensus mechanisms - depending on how the client is being run. ZChains is designed to offer off-the-shelf pluggable consensus algorithms. The current list of supported consensus algorithms: * IBFT PoS ### Blockchain The Blockchain layer is the central layer that coordinates everything in the ZChains system. It is covered in depth in the corresponding *Modules* section. ### State The State inner layer contains state transition logic. It deals with how the state changes when a new block is included. It is covered in depth in the corresponding *Modules* section. ### JSON RPC The JSON RPC layer is an API layer that dApp developers use to interact with the blockchain. It is covered in depth in the corresponding *Modules* section. ### TxPool The TxPool layer represents the transaction pool, and it is closely linked with other modules in the system, as transactions can be added from multiple entry points. ### GRPC The GRPC layer is vital for operator interactions. Through it, node operators can easily interact with the client, providing an enjoyable UX. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://zchains.gitbook.io/zchains-whitepaper/architecture/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.