# The Problem Traditional blockchain transfers expose every sender, receiver, and amount to public view. While this ensures transparency, it often limits practical use cases such as salary payments, DAO distributions, or peer-to-peer transfers where identity exposure is unnecessary or even risky. At the same time, complete anonymity solutions often fall outside regulatory tolerance or lack transparency. There is a gap between being fully exposed and being fully hidden, and TWIFT is designed to fill that gap. --- # Agent Instructions: 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: ``` GET https://twift.gitbook.io/twift-docs/about/quickstart.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.