# Interoperability

#### **How Zipper Enables Interoperability**

1. **Cross-Chain Compatibility**:
   * Zipper supports assets from multiple blockchains, such as Ethereum, Solana, Binance Smart Chain, Avalanche, Dogecoin, and Litecoin.
   * Each asset is mapped to a unique contract address on Fabric, ensuring distinct identification.
2. **Chain-Specific Contracts**:
   * For every supported blockchain, Zipper establishes a dedicated contract on Fabric to handle wrapping and unwrapping transactions.
   * Example:
     * Ethereum-originating USDT → Fabric Contract A → zUSDT.
     * Solana-originating USDT → Fabric Contract B → zUSDT.
3. **Unified zAssets**:
   * Regardless of their originating chain, wrapped assets are presented as a unified zAsset (e.g., zUSDT) within the Fabric ecosystem.
   * On-chain metadata ensures that the source chain remains identifiable for security and compatibility.

***

#### **Compliance for Cross-Chain Transactions**

1. **Chain Monitoring**:
   * Zipper integrates with monitoring services to detect and block transactions involving:
     * Sanctioned wallets.
     * Assets flagged for theft or illicit activity.
2. **Transparency for Users**:
   * Users can verify both the Fabric and original chain contract addresses of their zAssets via FabricScan or the Zipper website.

***

Here’s the draft for the **Interoperability** page:

***

### **Interoperability**

Zipper is built to bridge assets across multiple blockchains, making it a vital component of the Fabric ecosystem’s cross-chain functionality. This section explains how Zipper ensures smooth asset integration while maintaining security and transparency.

***

#### **How Zipper Enables Interoperability**

1. **Cross-Chain Compatibility**:
   * Zipper supports assets from multiple blockchains, such as Ethereum, Solana, Binance Smart Chain, Avalanche, Dogecoin, and Litecoin.
   * Each asset is mapped to a unique contract address on Fabric, ensuring distinct identification.
2. **Chain-Specific Contracts**:
   * For every supported blockchain, Zipper establishes a dedicated contract on Fabric to handle wrapping and unwrapping transactions.
   * Example:
     * Ethereum-originating USDT → Fabric Contract A → zUSDT.
     * Solana-originating USDT → Fabric Contract B → zUSDT.
3. **Unified zAssets**:
   * Regardless of their originating chain, wrapped assets are presented as a unified zAsset (e.g., zUSDT) within the Fabric ecosystem.
   * On-chain metadata ensures that the source chain remains identifiable for security and compatibility.

***

#### **Compliance for Cross-Chain Transactions**

1. **Chain Monitoring**:
   * Zipper integrates with monitoring services to detect and block transactions involving:
     * Sanctioned wallets.
     * Assets flagged for theft or illicit activity.
2. **Transparency for Users**:
   * Users can verify both the Fabric and original chain contract addresses of their zAssets via FabricScan or the Zipper website.

***

#### **Interoperability Challenges and Solutions**

1. **Challenge**: Varying standards across blockchains (e.g., ERC-20, SPL, BEP-20).
   * **Solution**: Zipper normalizes these standards into Fabric-compatible zAssets, ensuring compatibility with Fabric-based dApps and DeFi protocols.
2. **Challenge**: Network Congestion or Delays.
   * **Solution**: Zipper incorporates user notifications and fallback systems to handle cross-chain delays effectively.
3. **Challenge**: Ensuring zAsset Verification.
   * **Solution**: Zipper uses metadata and unique contract addresses to verify zAssets’ origins and legitimacy.


---

# Agent Instructions: 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:

```
GET https://docs.zipper.trade/developer-information/interoperability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.