> For the complete documentation index, see [llms.txt](https://pijschain.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pijschain.gitbook.io/whitepaper/system-architecture/node-roles/full-node.md).

# Full Node

A Full Node is the default role for any machine running the PIJSChain client. Full Nodes represent the base infrastructure of the network.

Their core capabilities include:

* fully synchronizing blockchain data,
* independently verifying all blocks,
* validating consensus signatures, system transactions, and reward distributions.<br>

At the network level, Full Nodes contribute by relaying blocks and transactions across the P2P layer, thereby improving data availability and decentralization.

Importantly, Full Nodes are also the required operational foundation for staking participation. A user’s staking rights only remain effective if they are associated with a continuously online Full Node capable of running heartbeat services. If the node goes offline, heartbeat proofs are missed, and the staking participant may lose reward eligibility for the current period. In this sense, infrastructure stability is directly tied to economic outcomes.

A Full Node can be upgraded at any time into a Staking Node by submitting a valid staking order, and may later be promoted into the Block Producer set through protocol-defined voting processes.


---

# 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:

```
GET https://pijschain.gitbook.io/whitepaper/system-architecture/node-roles/full-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.