Zipper Architecture
Last updated
Last updated
Zipper is designed as a minimalistic, high-security asset zipping (wrapping) and unzipping (unwrapping) protocol within the Fabric ecosystem. Unlike traditional cross-chain bridges, Zipper does not facilitate swaps or liquidity pooling - its sole function is to issue 1:1 backed zAssets by securely storing the original assets in vaults on their native blockchains.
Zipper’s architecture ensures:
Immutable zAsset minting/burning: zAssets are only created when external assets are deposited and are destroyed upon withdrawal.
No liquidity risk: Every zAsset is fully backed 1:1, eliminating risks of over-minting or under-collateralization.
Maximum transparency: Every transaction is recorded on-chain and can be verified by users.
Zero reliance on third-party custodians: Assets are secured via multi-signature vaults protected by a Trusted Execution Environment (TEE).
Vault Contracts: Maintain on-chain tracking of assets held in external vaults.
Mint/Burn Contracts: Handle zAsset issuance and destruction when deposits/withdrawals are processed.
User Authentication Contracts: Verify and authorize users interacting with Zipper, ensuring they have the correct permissions.
Zipper vaults are multi-signature wallets governed by a TEE-protected security model.
Every vault is isolated per asset and chain, meaning ETH-based USDT is stored in a separate vault from Solana-based USDT.
Vault operations require multi-party approval, ensuring no single entity controls funds.
Funds can only be withdrawn via an authorized unzipping event, preventing unauthorized access.
Each zAsset is issued with a unique Fabric contract address to differentiate between identical tickers from different chains.
Users can verify the origin of their zAssets via FabricScan.
Zipper itself does not verify asset legitimacy - it simply mints and burns assets based on deposit/withdrawal activity. Verification occurs at the application layer (e.g., Polyester DEX).
All Zipper transactions occur on-chain, meaning no off-chain validators or secondary approval processes exist.
Fabric consensus finalizes all minting/unzipping events, ensuring transactions are immutable once confirmed.
TEE and multi-sig models prevent unauthorized vault access even in worst-case scenarios.
Vault transactions require signatures from multiple independent parties.
Private keys are distributed across a TEE-secured environment, ensuring no single entity has full access.
Users can track all deposits and withdrawals on-chain using FabricScan.
The protocol is non-custodial - users do not need to trust intermediaries to access their funds.
Zipper contracts are immutable once deployed, meaning no entity (including developers) can alter contract behavior post-launch.
This protects users from governance takeovers, malicious updates, and regulatory pressure.
Zipping Process:
User initiates a deposit on Zipper.trade.
Zipper generates a unique deposit address based on the selected token and network.
User sends the external asset to this address.
Once received and confirmed on the originating chain, the equivalent zAsset is minted on Fabric.
The zAsset appears in the user’s connected Fabric wallet.
Unzipping Process:
User initiates an unzip request on Zipper.trade.
They select the zAsset and enter a destination address on the correct external chain.
Zipper confirms the burn request, destroying the zAsset on Fabric.
The original asset is released from the corresponding on-chain vault and sent to the user’s external wallet.
Zipper’s security-first design avoids common pitfalls seen in bridges and cross-chain protocols: ✅ No liquidity pools → No risk of impermanent loss, rug pulls, or liquidity drain exploits. ✅ Immutable contracts → Reduces attack vectors from contract upgrades. ✅ TEE and multi-sig protection → No single point of failure in vault operations. ✅ 1:1 backing model → Fully collateralized zAssets, with zero over-minting risk.
Zipper’s architecture prioritizes security, transparency, and simplicity, offering users a safe and efficient way to bring external assets into the Fabric ecosystem. By eliminating trust dependencies, relying on on-chain verification, and securing funds through TEE and multi-signature vaults, Zipper provides a robust foundation for cross-chain asset interoperability within Fabric.
