> For the complete documentation index, see [llms.txt](https://shinechain.gitbook.io/shine-chain-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinechain.gitbook.io/shine-chain-whitepaper/security-and-validators.md).

# SECURITY AND VALIDATORS

Security is the foundation of any decentralized blockchain, and that's where Proof of Stake (POS), one of the pillars of Shine Chain, comes in. This innovative approach ensures that our network remains solid and reliable, without the need for excessive energy expenditure like other models, such as Proof of Work (POW).

<div align="left"><figure><img src="/files/UNEQLxQY4mT37gWXqtIc" alt="" width="375"><figcaption></figcaption></figure></div>

What is Proof of Stake (POS)?

Proof of Stake (POS) is a consensus mechanism that operates based on the investment of validators in the network. Our blockchain relies on a random selection of validators who lock up your assets as collateral for your commitment. These validators are responsible for validating transactions and ensuring network security. However, what sets our approach apart is the long-term commitment of validators.


---

# 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://shinechain.gitbook.io/shine-chain-whitepaper/security-and-validators.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.