> For the complete documentation index, see [llms.txt](https://docs.byzanlink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.byzanlink.com/byzanlink-rwa-markets/introduction.md). # Introduction ### Launch tokenised RWA vaults in minutes Byzanlink RWA Markets is a non-custodial vault platform for tokenised RWA strategies. Partners can configure and deploy vaults quickly using standardized ERC-4626 and ERC-7540 frameworks, with synchronous and asynchronous flows. Developers and integrators can access vaults through a consistent onchain interface.\ \ **What is Byzanlink RWA Markets?** Byzanlink RWA Markets standardises how real-world asset strategies are packaged as onchain vaults. Instead of building vault contracts, async settlement flows, and integration patterns from scratch, partners configure vault parameters and deploy production-ready vaults designed for RWA workflows. **Vaults in RWA Markets are standardised onchain smart contracts that package a tokenised RWA strategy behind a consistent deposit and redemption interface.** RWA Markets is built to support multiple vault models so the vault mechanics match how the underlying strategy settles. ### What you can do with RWA Markets #### Launch vaults quickly Configure strategy inputs and deploy a vault without building an end-to-end vault system. * Vault setup in minutes * Production launch in a day with white-label support * Consistent vault behavior across multiple strategies and partners **White-label launch means partners can deploy vaults under their own brand and front-end experience while using the same standardized vault framework.** #### Choose the right vault model RWA strategies often require request-based withdrawals, batching, or settlement windows. RWA Markets supports vault types that match those operational realities. * **ERC-4626** vaults for standard flows * **ERC-7540** patterns for request-based, asynchronous flows * **Synchronous vaults** for liquid strategies * **Asynchronous vaults** for settlement-driven strategies #### Integrate through a consistent interface Integrate once and interface with multiple vaults and strategies through standardized vault primitives. * Standard interfaces for deposits and redemptions * Vault metadata for mechanics and constraints * Integration-ready primitives for applications and workflows ### How it works 1. **Define the strategy**\ Specify the tokenized RWA strategy the vault represents. 2. **Select vault type and flow**\ Choose ERC-4626 or ERC-7540-style behavior, and select sync or async flows. 3. **Configure vault parameters**\ Set strategy-specific parameters, settlement constraints, and operational limits. 4. **Deploy the vault**\ Deploy a standardized vault implementation with the configured parameters. 5. **Access and integrate**\ Users and integrators access vaults onchain through a consistent interface surface. ### Who it’s for * **RWA strategy partners** launching vault products without building vault infrastructure * **Platforms and integrators** offering consistent vault access across multiple strategies * **Protocol developers** building workflows on top of vault primitives ### Vault standards and modes RWA Markets supports multiple vault standards and operating modes: * ERC-4626-compatible vaults * ERC-7540-style asynchronous request flows * Synchronous vault operation * Asynchronous vault operation This flexibility allows vault behavior to match real-world settlement and liquidity constraints. ### Get started **For Partners** * **Launch a Vault**: configure parameters, choose sync or async flows, deploy, and white-label options **For Developers** * **Integrate**: interfaces, events, and example interaction flows **For Everyone** * **Vault Types**: ERC-4626 vs ERC-7540, sync vs async * **Security**: audits, assumptions, and scope --- # 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://docs.byzanlink.com/byzanlink-rwa-markets/introduction.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.