> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.5.1/guardian/readme/getting-started/how-to-configure-hedera-local-node.md).

# How to Configure Hedera Local Node

1. [Step By Step Process](#step-by-step-process)
2. [Demo Video](#demo-video)

### Step By Step Process

1. Install a Hedera Local Network following the [official documentation](https://github.com/hashgraph/hedera-local-node#docker)
2. Configure Guardian's configuration files `.env/.env.docker` accordingly:

```
OPERATOR_ID=""
OPERATOR_KEY=""
LOCALNODE_ADDRESS="11.11.11.11"
LOCALNODE_PROTOCOL="http"
HEDERA_NET="localnode"
```

{% hint style="info" %}
Note:

1. Set **LOCALNODE\_ADDRESS** to the IP address of your local node instance. The value above is given as example.

2. Set **HEDERA\_NET** to **localnode**. If not specified, the default value is **testnet.**

3. Configure **OPERATOR\_ID** *and* **OPERATOR\_KEY** accordingly with your local node configuration.

4. Remove **INITIALISATION\_TOPIC\_ID** as the topic will be created automatically.

5. Set **LOCALNODE\_PROTOCOL** to **http** or **https** accordingly with your local node configuration (It uses HTTP by default).
   {% endhint %}

6. OPERATOR\_ID: The ID of the operation

7. OPERATOR\_Key: Private key of the operator\_

8. LOCALNODE\_ADDRESS : The address of the localnode server. This can be its IP address or a domain name

9. LOCALNODE\_PROTOCOL : Communication protocol for interactions with the local node, can be http or https.

10. HEDERA\_NET : Type of the Hedera node to transact.

### Demo Video

[Youtube](https://www.youtube.com/watch?v=EpCOI31iMoI\&list=PLnld0e1pwLhqdR0F9dusqILDww6uZywwR\&index=1)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guardian.hedera.com/docs/3.5.1/guardian/readme/getting-started/how-to-configure-hedera-local-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.