> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/how-coti-works/introduction/coti-architecture.md).
# COTI Architecture
The COTI network is comprised of several core components:
1. **Full Nodes**: These nodes are responsible for validating transactions and ensuring the integrity of the COTI blockchain network. They act as the decentralized foundation of the network.
2. **Sequencer**: This component processes transactions (TXs) and organizes them into blocks. It coordinates transaction flow and ensures orderly addition to the chain.
3. **Executors**: Two separate executors that process blocks in a MPC manner:
* **Red Blocks**: incoming blocks processed from the sequencer to the executors.
* **Black Blocks**: outgoing blocks processed from the executor to the sequencer.
4. **GC Manager**: Stores the generated garbled circuits in data warehouse, these circuits are used by the executors for on-chain computation.
5. **Garbler**: Generates garbled circuits that are stored into the DB Manager to be used later on during on-chain computation.
The network uses a multi-tier architecture to optimize transaction flow and ensure scalability, with the sequencer bridging full nodes to the execution layer and the database manager and garbler handling persistence and post-processing.
---
# 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://docs.coti.io/coti-documentation/how-coti-works/introduction/coti-architecture.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.
.png?alt=media)