> For the complete documentation index, see [llms.txt](https://docs.hiero.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hiero.org/block-node-home.md).

# Hiero Block Node

Hiero Block Nodes form the decentralised data layer of a Hiero network — receiving, verifying, storing, and serving the block stream produced by Consensus Nodes.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Block Node Introduction</strong></td><td>New to Block Nodes? Start here - what a Block Node is, who it is for, and where to go next based on your role.</td><td><a href="/block-node-home/block-node-introduction.md">Block Node Introduction</a></td></tr><tr><td><strong>Block Node Overview</strong></td><td>What a Block Node is, how it fits in the Hiero network, tiers, deployment profiles, and operator responsibilities.</td><td><a href="/block-node-home/block-node-overview.md">Block Node Overview</a></td></tr><tr><td><strong>Block Node Types and Tiers</strong></td><td>Full taxonomy of Block Node types: Rolling-History, Full Node, Light Node, Private-Cloud, Archive Server, and Community Node.</td><td><a href="/block-node-home/block-node-types.md">Block Node Types and Tiers</a></td></tr><tr><td><strong>Deployment</strong></td><td>Hardware requirements, Solo Provisioner setup, Kubernetes deployment, and local development quickstart.</td><td><a href="/block-node-home/deployment.md">Deployment</a></td></tr></tbody></table>


---

# 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.hiero.org/block-node-home.md?ask=<question>&goal=<user_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.