> For the complete documentation index, see [llms.txt](https://bzl.gitbook.io/bzl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bzl.gitbook.io/bzl-docs/byzanlink.md).
# Byzanlink
## Welcome to Byzanlink
{% hint style="success" %} **Byzanlink** is an **institutional tokenisation infrastructure platform** for structured real-world financial products. It provides **neutral, non-custodial** on-chain representation and lifecycle management for instruments such as treasury-backed products, investment-grade funds/structured products, and private credit—while preserving institutional expectations around **governance, control, and risk management**.
Our vision (roadmap): [Here](/bzl-docs/ecosystem/participation.md)
{% endhint %}
Visit Byzanlink.comProductWhitepaperBlogContact
### What we build
**Byzanlink** is built as a **modular, layered architecture** that separates core tokenisation from liquidity enablement and market access, allowing institutions to adopt tokenisation incrementally:
> 1. **Tokenisation Infrastructure Layer:** Standardised frameworks to **issue, transfer, and redeem** tokenised instruments and manage **in-life asset events** and lifecycle operations.
> 2. **DeFi Enablement & Liquidity Abstraction Layer (optional):** Vault and wrapper mechanisms that can make tokenised instruments **compatible with on-chain financial systems** for use cases such as liquidity routing, yield abstraction, or collateralisation—enabled only when issuers choose.
> 3. **Distribution & Access Layer:** An **external, adaptable interface** where **issuers and distributors define access models** (eligibility, permissions, jurisdictional constraints) and integrate tokenised assets into existing financial platforms and workflows, without assuming open markets or retail distribution.
{% embed url="" %}
**Social links**
cookie.communityDiscordTelegramCookie DAO X
**All official links**
Cookie DAO linktree
---
# 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://bzl.gitbook.io/bzl-docs/byzanlink.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.