> For the complete documentation index, see [llms.txt](https://doc.datagram.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.datagram.network/datagram-node-sale/introduction/why-run-a-full-core-node.md).

# Why Run a Full Core Node?

Operating a Full Core node in the Datagram network gives you a front-row seat to the evolution of decentralized infrastructure. Full Cores are not just nodes - they are the backbone of Datagram’s performance, resilience, and scalability.

By running a Full Core node, you enable:

* **Decentralization That Matters**: Help keep the network distributed, trustless, and resistant to centralized control.
* **Verified Integrity**: Contribute by verifying that Partner Core nodes are authorized to access the network and earn rewards through the Datagram Core Substrate.
* **Infrastructure Contribution**: Host and route essential data while maintaining high uptime and throughput.
* **Token Rewards**: Earn $DGRAM tokens for your contributions and unlock deeper participation in Datagram’s growth.

Running a Full Core node is more than supporting the network - it means becoming a critical part of it.


---

# 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://doc.datagram.network/datagram-node-sale/introduction/why-run-a-full-core-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.