> For the complete documentation index, see [llms.txt](https://whitepaper.ivault.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.ivault.io/ivaults-blockchain-ecosystem/the-ivault-chain/key-functions.md).

# Key functions

The ivault Chain is crucial for storing and securing user data, supporting a host of functions in the ivault app.

1. **Secure data storage**: The ivault Chain acts as a distributed ledger, creating an immutable track record of transactions and activities on the blockchain. This means no one can hack or manipulate the data.
2. **Encrypting and protecting user data**: details about items, transaction history, ratings and other data is stored securely on the blockchain, safeguarding user privacy.
3. **Secure transactions**: records peer-to-peer transactions on the blockchain and users have a record for their payments.
4. **Genuine ratings and reviews**: no more fake feedback. ivault’s ratings and reviews are anchored to verified transactions recorded on the blockchain, so users can trust their authenticity. 
5. **Seamless experiences**: securely automate escrow services and transactions using smart contracts. For example, releasing funds after an item has been dropped off, or even resolving disputes.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.ivault.io/ivaults-blockchain-ecosystem/the-ivault-chain/key-functions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.