> For the complete documentation index, see [llms.txt](https://info.tilox.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.tilox.cc/security/security-model.md).

# Security Model

Security responsibilities and transaction review guidance.

## Security Model

Tilox is designed to present execution information before authorization. Users remain responsible for reviewing every transaction they sign.

### User responsibilities

* Verify assets, amounts, networks, contracts, approvals, and transaction steps.
* Use only wallets, contracts, interfaces, and protocols you trust.
* Protect private keys and seed phrases. Tilox should never request them.

### Risk boundaries

Smart contracts and third-party protocols can introduce risk. Bridge, protocol, liquidity, oracle, and smart-contract risks may apply to a workflow.

Tilox does not eliminate underlying protocol risk. Audit status, security certifications, and security guarantees are not yet specified.

{% hint style="warning" %}
Do not treat a displayed strategy as a security assessment or investment recommendation.
{% 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 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://info.tilox.cc/security/security-model.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.