> 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/readme.md).

# Vayyl

![Vayyl](https://2374024446-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUmZFHzWBi2AN0HMaPj9C%2Fuploads%2Fgit-blob-73e575b7f45e7b306549066b60977d5b333544c6%2Fvayyl-logo.png?alt=media)

## The private financial layer for Stellar

Vayyl is building a self-custodied private balance that can move through payments, positions, orders, and automated settlements without turning a user's entire financial history into public data.

Stellar already provides fast settlement, issued assets, and programmable Soroban contracts. Vayyl adds the privacy state between a public deposit and a public withdrawal: value is represented by encrypted notes, ownership is proven with zero knowledge, and spent notes are invalidated without revealing which note was used.

{% hint style="info" %}
Vayyl is under active development. The XLM Vault is the first live product surface; private transfers and application integrations described in these docs are the protocol direction and are labeled by delivery stage.
{% endhint %}

## One balance, several private actions

The target Vayyl wallet presents one private balance while managing notes underneath.

```mermaid
flowchart LR
    A[Public Stellar assets] -->|Shield| B[Private balance]
    B --> C[Send privately]
    B --> D[Open a private position]
    B --> E[Place a conditional order]
    C --> B
    D --> B
    E --> B
    B -->|Settle| F[Public Stellar recipient]
```

The same note system is intended to support:

* **Private payments** — transfer value to another shielded address and return change privately.
* **Private positions** — prove collateral, health, and authorization without publishing the full position.
* **Conditional settlement** — commit an order privately and reveal only the proof needed for execution.
* **Programmable payouts** — let applications settle rewards or obligations into a private balance.
* **Selective disclosure** — give a chosen auditor or institution scoped visibility without publishing activity globally.

## Why Vayyl exists

A public ledger is useful for verifying system integrity, but it should not force payroll, treasury movements, trading strategy, or commercial relationships into a permanent public profile. Stellar's own privacy roadmap identifies privacy pools, confidential tokens, and onchain zero-knowledge verifiers as complementary tools for these use cases.

Vayyl's design follows that direction: preserve public verification and asset integrity while minimizing the financial metadata exposed by ordinary use.

## Start here

* [How Vayyl works](/vayyl-docs/concepts/how-vayyl-works.md)
* [The private balance](/vayyl-docs/concepts/private-balance.md)
* [Product capabilities](/vayyl-docs/product/overview.md)
* [Protocol architecture](/vayyl-docs/architecture/overview.md)
* [Delivery roadmap](/vayyl-docs/direction/roadmap.md)


---

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