> For the complete documentation index, see [llms.txt](https://docs.expanse.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expanse.tech/developer/what-are-the-static-trusted-and-boot-nodes.md).

# What are the static, trusted and boot Nodes?

Gexp supports a feature called static nodes if you have certain peers you always want to connect to. Static nodes are re-connected on disconnects. You can configure permanent static nodes by putting something like the following into \<datadir>/static-nodes.json (this should be the same folder that your chaindata and keystore folders are in)

\[\
&#x20;    “enode://f4642fa65af50cfdea8fa7414a5def7bb7991478b768e296f5e4a54e8b995de102e0ceae2e826f293c481b5325f89be6d207b003382e18a8ecba66fbaf6416c0\@33.4.2.1:30303”,\
&#x20;    “enode://pubkey\@ip:port”\
]

You can also add static nodes at runtime via the Javascript console using admin.addPeer()

\> admin.addPeer(“enode://f4642fa65af50cfdea8fa7414a5def7bb7991478b768e296f5e4a54e8b995de102e0ceae2e826f293c481b5325f89be6d207b003382e18a8ecba66fbaf6416c0\@33.4.2.1:30303”)

#### **COMMON PROBLEMS WITH CONNECTIVITY** <a href="#common-problems-with-connectivity" id="common-problems-with-connectivity"></a>

Sometimes you just can’t get connected. The most common reasons are:

* Your local time might be incorrect. An accurate clock is required to participate in the Expanse network. Check your OS for how to resync your clock (example sudo ntpdate -s time.nist.gov) because even 12 seconds too fast can lead to 0 peers.
* Some firewall configurations can prevent UDP traffic from flowing. You can use the static nodes feature or admin.addPeer() on the console to configure connections by hand.

To start gexp without the discovery protocol, you can use the –nodiscover parameter. You only want this if you are running a test node or an experimental test network with fixed nodes.\ <br>


---

# 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://docs.expanse.tech/developer/what-are-the-static-trusted-and-boot-nodes.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.