> 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/product/assets-and-integrations.md). # Assets and Integrations Vayyl is intended to support approved Stellar assets through a common private-balance interface. ## Asset pools A pool factory can deploy or register a shielded pool per supported asset. Each pool needs explicit asset identity, verifier configuration, tree parameters, upgrade authority, and policy settings. A multi-asset wallet can then present balances together while proofs preserve asset conservation. Asset support is not only a deployment task. Issuer controls, authorization behavior, clawback semantics, decimals, liquidity, and public redemption paths must be reviewed for every asset. ## Confidential tokens Stellar describes confidential tokens as a complementary model: balances and amounts can be hidden while sender and receiver addresses remain public. Vayyl can integrate a mature standard at the public asset boundary or use it for applications where amount confidentiality is enough. It does not replace shielded addresses when counterparty unlinkability is required. The standard is still described by Stellar as implementation work in progress, so it is a research dependency rather than a production promise. See [Privacy on Stellar](https://developers.stellar.org/docs/build/apps/privacy#confidential-tokens). ## Application adapters An adapter connects a Soroban application to the Vayyl pool. The minimum safe interface is: * consume proof-authorized private inputs; * bind every public call parameter into the proof; * enforce application-specific state rules; * return value as valid Vayyl output commitments or an explicitly public payout; * make the value and state transition atomic. This is the integration point for positions, orders, private payroll, treasury workflows, and agent-authorized settlements. --- # 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/product/assets-and-integrations.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.