> For the complete documentation index, see [llms.txt](https://vayyl.gitbook.io/vayyl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vayyl.gitbook.io/vayyl-docs/direction/protocol-vision.md). # Protocol Vision Vayyl's end state is a privacy layer that feels native to Stellar applications. ## A private account, not a privacy detour Users should not need to reason about individual notes during ordinary use. They should see balances, recipients, positions, and transactions while the wallet handles commitments, witnesses, proofs, output discovery, and relayer selection. ## Private value that stays useful Privacy is weakest when users must immediately unshield to do anything. Vayyl therefore prioritizes a shared private balance and application adapters over a long list of disconnected privacy contracts. The intended loop is: ``` shield once -> pay, receive, trade, settle, or earn privately -> disclose selectively when required -> unshield only when public settlement is needed ``` ## Stellar-native settlement Vayyl does not introduce a separate consensus network or custodial bridge. Soroban contracts enforce the private state transition and Stellar assets remain the settlement assets. Relayers, indexers, keepers, and policy providers are replaceable services around that contract core. ## Configurable policy Different wallets, issuers, and applications have different obligations. Vayyl aims to support policy proofs and scoped viewing without turning one provider into a global identity gate or exposing every user to public surveillance. ## An integration layer The long-term product is both an end-user wallet experience and infrastructure for other Stellar products. Wallets integrate private balances and transfers; protocols integrate proof-bound inputs and outputs; institutions integrate policy providers and scoped disclosure. Success means privacy becomes an ordinary capability of Stellar applications, not a separate destination users visit only to deposit and withdraw. --- # 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://vayyl.gitbook.io/vayyl-docs/direction/protocol-vision.md?ask=&goal= ``` `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.