> 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/ultra-small-world-network-topology.md).
# Ultra-Small World Network Topology
At the core of the Mandala architecture is an **ultra-small world core node network** of Teranodes, which is essential for delivering operational efficiency, security, and speed. A **Small World Network** is a network topology optimized for the rapid dissemination of information, minimizing the number of hops required to synchronize the entire network. This characteristic is vital for optimizing the propagation of transactions from the network's edge to the core mining nodes.
This central topology forms a complete graph among the Teranodes, enabling them to disseminate transactional and block information swiftly while simultaneously verifying other Teranodes' block proposals. This capability allows the network to process millions of transactions per second, **significantly reducing the risk of double-spend attacks** and **distributing the read load** across Overlay Services, thereby **enhancing resilience**.
---
# 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/ultra-small-world-network-topology.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.
