> For the complete documentation index, see [llms.txt](https://twift.gitbook.io/twift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://twift.gitbook.io/twift-docs/readme.md).

# Welcome to Twift

<figure><img src="/files/BDIUcXyr5JuZh8BxatAX" alt=""><figcaption></figcaption></figure>

TWIFT brings a new standard for on-chain asset transfers. It unifies two essential principles of the decentralized world: trust and privacy.<br>

Every transfer is fast, secure, and non-custodial, yet users have the freedom to decide how visible their transaction trail should be.<br>

TWIFT exists for those who believe that privacy should not come at the cost of transparency. The protocol is designed so that all activities remain verifiable and auditable, allowing users to meet their own transparency and reporting needs while still giving users the ability to obscure direct sender-recipient links when desired.


---

# 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://twift.gitbook.io/twift-docs/readme.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.