> 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/configuration.md).

# Configuration

Configure your Block Node for your network, storage strategy, and integration requirements.

<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>Configuration Reference</strong></td><td>Complete reference for all Block Node configuration properties, environment variables, and Helm chart values.</td><td><a href="/block-node-home/configuration/configuration.md">Configuration Reference</a></td></tr><tr><td><strong>Network Ports and Protocols</strong></td><td>Port assignments, traffic directions, TLS posture, and production exposure for all Block Node services.</td><td><a href="/block-node-home/configuration/network-ports-and-protocols.md">Network Ports and Protocols</a></td></tr><tr><td><strong>Streaming from Consensus Nodes</strong></td><td>Configure Consensus Nodes to stream block data to your Block Node via the publish gRPC API.</td><td><a href="/block-node-home/configuration/consensus-node-to-block-node-configuration.md">Streaming from Consensus Nodes</a></td></tr><tr><td><strong>On-Chain Registration</strong></td><td>Register your Block Node on-chain to make it discoverable by Consensus Nodes and other network participants.</td><td><a href="/block-node-home/configuration/block-node-on-chain-registration.md">On-Chain Registration</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/configuration.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.
