> 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-teranode-microservices-and-infrastructure-solutions/hash-based-sharding.md).
# Hash-Based Sharding
To efficiently distribute transaction data across the network, Teranode employs a technique known as **hash-based sharding**. Each transaction is assigned a unique identifier through the **SHA-256 hashing algorithm**, which ensures that every transaction ID is distinct and minimizes the risk of collisions.
The sharding process involves:
1. **Hashing the Transaction**: Each transaction's inputs, outputs, and metadata are hashed to generate a unique transaction ID.
2. **Distributing Data**: The transaction ID is used to determine which shard (or node) will store the transaction data, ensuring an even distribution across the network.
3. **Scalability**: This method allows Teranode to achieve a throughput of approximately **3.5 million database transactions per second**, accommodating the influx of one million Bitcoin transactions while efficiently managing updates and deletions.
By utilizing hash-based sharding, **Teranode enhances its scalability and performance**, making it well-suited for high-demand environments.
---
# 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-teranode-microservices-and-infrastructure-solutions/hash-based-sharding.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.
