> For the complete documentation index, see [llms.txt](https://docs.zipper.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipper.trade/core-concepts/what-are-on-chain-vaults.md).
# What Are On-Chain Vaults?
On-chain vaults are the **core security mechanism** of Zipper, ensuring that every **zAsset on Fabric is fully backed 1:1 by its real counterpart** on its original blockchain. These vaults function as **transparent, decentralized storage** locations where users’ deposited assets remain securely held while their zAsset equivalent exists on Fabric.
#### **How Vaults Secure Funds**
Each external blockchain has a **dedicated vault** controlled by Zipper. When a user **zips an asset**, it is **deposited into the vault**, and a corresponding **zAsset is minted** on Fabric. When a user **unzips**, the corresponding zAsset is **burned**, and the original asset is **released from the vault** back to the user.
Vaults ensure:\
✅ **1:1 Backing** - Every zAsset on Fabric corresponds exactly to an asset stored in an on-chain vault.\
✅ **Trustless Security** - Users can verify the vault’s balance **on-chain** at any time.\
✅ **No Liquidity Pools** - Vaults are not used for lending or staking; funds remain **secure and untouched** until a user requests a withdrawal.
#### **Multi-Signature & TEE Security**
To prevent **single points of failure**, Zipper secures its vaults using a **multi-signature (multi-sig) model** combined with **Trusted Execution Environment (TEE) technology**.
* **Multi-Sig Protection** - Vault transactions require multiple signatures, ensuring that no single entity has full control over user funds.
* **TEE Security Model** - Trusted Execution Environments protect vault private keys, ensuring that **even Zipper’s operators cannot unilaterally access or move funds**.
This **redundant security architecture** ensures that **even in extreme scenarios, funds remain fully protected**.
#### **Full Transparency & Public Verification**
Zipper’s vaults are **completely auditable**, and users can verify:
* The total balance of assets stored in vaults.
* The contract addresses of zipped and unzipped assets.
* The history of deposits and withdrawals.
Users can **track all vault activity directly on-chain** using [**FabricScan**](https://scan.fabriclabs.org/) and block explorers for each original blockchain.
#### **Zipper’s Role in Vault Management**
Zipper **only facilitates vault deposits and withdrawals -** it does not verify asset legitimacy. The **best way for users to verify assets** is to **check contract addresses during the Zipping process and use FabricScan for confirmation**.
---
# 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.zipper.trade/core-concepts/what-are-on-chain-vaults.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.