> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/2.-architecture-overview.md).
# 2. Architecture Overview
FreCx is designed as a role-based Layer-1 blockchain architecture, where network responsibilities are distributed across specialized node types to ensure scalability, security, and deterministic execution. Unlike traditional blockchain systems where all nodes perform identical functions, FreCx introduces a structured separation of concerns, enabling optimized performance without compromising decentralization.
This architecture is built around three primary node roles:
* Cluster nodes (block production layer)
* Sync nodes (validation and state layer)
* Vault nodes (verification and integrity layer)
Together, these roles form a coordinated system where transaction processing, validation, and verification are handled independently but cohesively, ensuring high throughput and strong security guarantees.
Cluster nodes are responsible for aggregating transactions, ordering them, and producing blocks. These nodes operate under strict performance and staking requirements, ensuring that only high-quality infrastructure participates in block production.
Sync nodes maintain a complete copy of the blockchain state and independently validate every transaction and block. Their role ensures that all state transitions are deterministic and consistent across the network.
Vault nodes provide an additional layer of verification by performing cryptographic validation of blocks before they are finalized. This introduces redundancy in validation and significantly reduces the risk of invalid state transitions or malicious activity.
This layered approach ensures that execution is efficient and scalable, validation is decentralized and redundant and finality is secure and verifiable.
---
# 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.frequencychain.org/2.-architecture-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.