> For the complete documentation index, see [llms.txt](https://thirdfi.gitbook.io/thirdfi.org-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thirdfi.gitbook.io/thirdfi.org-1/product/thirdfi-v2/technical-overview/consensus-and-security.md).

# Consensus and Security

### Consensus Mechanism

* **Proof of Stake (PoS)**: Nodes participate in the consensus process by staking a certain amount of tokens, which helps secure the network. Nodes are chosen to create new blocks based on their stake, promoting fairness and energy efficiency.
* **Slashing**: To discourage dishonest behavior, nodes that act maliciously or fail to fulfill their responsibilities can have a portion of their stake "slashed" or removed.

### Security Audits & Updates

* **Regular Audits**: Continuous security audits are conducted to identify and mitigate potential vulnerabilities in the smart contracts and node software.
* **Dynamic Updates**: The blockchain supports on-chain governance for dynamically updating network protocols and algorithms to respond to emerging security threats or performance bottlenecks.


---

# 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://thirdfi.gitbook.io/thirdfi.org-1/product/thirdfi-v2/technical-overview/consensus-and-security.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.