# Transaction Finality

#### **How Transaction Finality Works**

1. **Consensus on Fabric**:
   * Fabric uses a deterministic consensus mechanism to confirm transactions. This guarantees that once a transaction is validated and added to the blockchain, it cannot be reversed or tampered with.
2. **Confirmation Thresholds**:
   * For wrapping:
     * The original asset must be fully deposited in Zipper’s vault before the equivalent zAssets are minted.
   * For unwrapping:
     * The zAsset must be fully burned before the original asset is released from the vault.
3. **On-Chain Transparency**:
   * All transactions are recorded on Fabric’s blockchain, allowing users to verify the status and finality of their operations in real-time using FabricScan.

***

Here’s the draft for the **Transaction Finality** page:

***

### **Transaction Finality**

Transaction finality ensures that every wrapping (zipping) and unwrapping (unzipping) operation processed by Zipper is secure, irreversible, and fully backed by the original assets. This section explains how Zipper leverages Fabric’s consensus mechanism to maintain trust and reliability.

***

#### **How Transaction Finality Works**

1. **Consensus on Fabric**:
   * Fabric uses a deterministic consensus mechanism to confirm transactions. This guarantees that once a transaction is validated and added to the blockchain, it cannot be reversed or tampered with.
2. **Confirmation Thresholds**:
   * For wrapping:
     * The original asset must be fully deposited in Zipper’s vault before the equivalent zAssets are minted.
   * For unwrapping:
     * The zAsset must be fully burned before the original asset is released from the vault.
3. **On-Chain Transparency**:
   * All transactions are recorded on Fabric’s blockchain, allowing users to verify the status and finality of their operations in real-time using FabricScan.

***

#### **What Happens During Network Congestion?**

1. **Wrapping Transactions**:
   * If the source chain experiences congestion, Zipper waits until the deposit is confirmed before minting the zAsset on Fabric. This ensures no double-spending or over-minting occurs.
2. **Unwrapping Transactions**:
   * Similarly, Zipper will only release the original asset after confirming the burn of the corresponding zAsset on Fabric.
3. **User Notifications**:
   * The Zipper interface provides estimated transaction times during periods of network congestion, ensuring users remain informed.

***

#### **Fail-Safe Mechanisms**

* **Reconciliation Processes**:
  * Zipper continuously monitors transactions to identify and resolve discrepancies between vault balances and zAsset supplies.
* **Fallback Systems**:
  * In case of unexpected failures (e.g., network outages), Zipper’s operations pause temporarily to prevent asset mismatches.


---

# 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/transaction-finality.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.