> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/essentials-of-bsvs-mandala-network-architecture/teranode-core.md).
# Teranode Core
The Mandala architecture is structured into three distinct yet interconnected components, each serving a unique purpose within the overall ecosystem:
**Component 1: The Core Node Network (Teranode)**
At the heart of the Mandala architecture lies the **Teranode**, an ultra-small world network that forms a complete graph. This core network is responsible for handling massive transaction volumes, maintaining the global ledger, and ensuring the smooth and efficient operation of the network.
Teranode is capable of processing over **one million transactions per second**, providing the BSV blockchain with a significant advantage over other blockchain systems. This capability enables an ultra-scalable layer-1 blockchain characterized by high throughput, security, resiliency, hyper-connectivity, and global accessibility.
[**Learn more about Teranode**](https://bsv-blockchain.github.io/teranode/)
---
# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/essentials-of-bsvs-mandala-network-architecture/teranode-core.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.
