> For the complete documentation index, see [llms.txt](https://remittix-organization.gitbook.io/remittix-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://remittix-organization.gitbook.io/remittix-whitepaper/30.4-smart-contract-risk.md).

# 30.4 Smart Contract Risk

Blockchain-based products rely on software that may contain technical vulnerabilities.

The RTX smart contract has undergone independent review by CertiK, providing an additional level of external scrutiny over the contract. An audit does not, however, guarantee that a smart contract is free from every possible vulnerability or future technical risk.

Other smart contracts and blockchain protocols accessed through the Remittix ecosystem may have separate security models and risks.

{% hint style="warning" %}
Blockchain transactions can also be irreversible once confirmed. Users should therefore review transaction details carefully before authorising them.
{% endhint %}


---

# 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://remittix-organization.gitbook.io/remittix-whitepaper/30.4-smart-contract-risk.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.