> 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/consensus-mechanism-pos/data-consistency-guarantees.md).

# Data Consistency Guarantees

PIJSChain incorporates several mechanisms to guarantee deterministic state consistency across the network:

* Parameter Freezing\
  All reward-relevant parameters are frozen at epoch boundaries, eliminating state drift during reward computation.<br>
* Deterministic Calculation\
  Reward distribution batches are derived deterministically from block height, ensuring that all nodes independently compute the same outcomes.<br>
* StateRoot Verification\
  All state transitions—such as bitmap updates, reward distributions, and staking-order processing—are executed through the EVM and reflected in the stateRoot. Nodes with inconsistent results are automatically rejected by the network.<br>

On-Chain Order Records\
Every staking order, including creation, renewal, and redemption, is recorded as an on-chain state transition. This ensures full lifecycle traceability and strong trust guarantees.


---

# 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/consensus-mechanism-pos/data-consistency-guarantees.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.
