> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-developer-tools/protocol/network-layer/nodes.md).

# Nodes

æternity nodes are the backbone of the blockchain network, responsible for maintaining the distributed ledger, processing transactions, and participating in consensus. Each node can serve different purposes - from full nodes that maintain the complete blockchain state and validate transactions, to mining nodes that participate in block creation, to API nodes that provide interfaces for applications. Nodes communicate with each other using various protocols for synchronization, gossip-based message propagation, and mining coordination, enabling the decentralized operation of the æternity network.\
\
The [Nodes Documentation](broken://pages/SyXp6S4ZN4IwShTtdkxH) describes how to install, configure and operate an aeternity node. One can install it from a package, run a docker image or build it themselves. There is also additional documentation on mining with CUDA and build and/or join a Stratum pool.\
\
The [Node API Documentation](/developer-documentation/aeternity/docs/api.md) provides comprehensive coverage of the node's API functionalities, including the core API that enables interaction with the blockchain, the specialized Channels WebSocket API for state channel operations, and detailed guidance on utilizing the user API for common blockchain interactions. This documentation serves as an essential reference for developers working with æternity nodes, whether they're building applications, implementing state channels, or integrating with the blockchain.\
\
The [Node API ](https://api-docs.aeternity.io/#/)can be found on its own webpage. 

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Protocol Node Documentation</td><td><a href="/spaces/yxhRUAwn7tH8JUboTur7/pages/qyWdSw7WddqOhoc48Udh">/spaces/yxhRUAwn7tH8JUboTur7/pages/qyWdSw7WddqOhoc48Udh</a></td><td><a href="/files/Mn0raWPCGdVF9LgIRfVj">/files/Mn0raWPCGdVF9LgIRfVj</a></td></tr><tr><td>Node API Reference</td><td><a href="/spaces/yxhRUAwn7tH8JUboTur7/pages/gW39QxLj0Jrf6BfyTrQl">/spaces/yxhRUAwn7tH8JUboTur7/pages/gW39QxLj0Jrf6BfyTrQl</a></td><td><a href="/files/vZyGDyzw08V42czk9Gxx">/files/vZyGDyzw08V42czk9Gxx</a></td></tr><tr><td>Node API Swagger site</td><td><a href="https://api-docs.aeternity.io/#/">https://api-docs.aeternity.io/#/</a></td><td><a href="/files/60QmGVxDyAZeLFAtGHRM">/files/60QmGVxDyAZeLFAtGHRM</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 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.aeternity.com/aeternity-developer-tools/protocol/network-layer/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.