> 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/hardware-and-operational-recommendations/operational-recommendations.md).

# Operational Recommendations

To ensure stable and secure node operation, PIJSChain recommends the following operational practices:

* Key Security\
  Block producer signing keys and staking-node BLS keys should be stored securely, ideally in password-protected keystore files. Plain-text exposure must be strictly avoided.<br>
* Node Monitoring\
  Operators should deploy monitoring systems to track:\
  \
  &#x20;           i） block synchronization status,\
  &#x20;           ii）number of P2P peers,\
  &#x20;           iii） heartbeat broadcast status,\
  &#x20;           iv）storage and memory usage.\
  \
  A staking node that goes offline may lose reward eligibility for the corresponding period.<br>
* Data Backup\
  Chain data directories and key files should be backed up regularly to ensure disaster recovery readiness.<br>
* Containerized Deployment\
  The project supports Docker and Docker Compose-based deployment, enabling multi-node containerized setups and lowering operational complexity.<br>
* Upgrade Strategy\
  Operators should monitor protocol upgrade announcements and complete client version upgrades before feature activation heights to avoid network incompatibility or node divergence.


---

# 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/hardware-and-operational-recommendations/operational-recommendations.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.