> For the complete documentation index, see [llms.txt](https://docs.libertyswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libertyswap.finance/zkx-wallet/user-manual/using-batch-transactions.md).

# Using Batch Transactions

ZKX Wallet supports Batch Transactions, allowing users to combine multiple transactions into a single confirmation flow. This feature helps simplify transaction management and can reduce the number of separate approvals and gas payments required.

Batch Transactions are especially useful for:

* Multiple token swaps
* Sequential DeFi interactions
* Managing several transactions at once
* Improving transaction efficiency

### **How Batch Transactions Work**

Instead of confirming every transaction individually, ZKX Wallet allows you to group multiple actions together and sign them in a single batch.

#### **Step 1**

Whenever you initiate a transaction, the transaction confirmation window will appear.

#### **Step 2**

For the first transaction in the sequence, click **Start a Batch**.

#### **Step 3**

For each additional transaction, click **Add to Batch** instead of confirming individually.

#### **Step 4**

After adding all desired transactions to the batch, click **Sign** to approve and execute the batch transaction.

ZKX Wallet will then process all included transactions together.

### **Benefits of Batch Transactions**

#### **Single Confirmation Flow**

Approve multiple transactions at once instead of confirming each transaction separately.

#### **Improved User Experience**

Execute complex workflows more efficiently with fewer interruptions.

#### **Optimized Gas Usage**

Multiple actions can be bundled into a single execution flow, reducing unnecessary gas overhead.

> Multiple swaps. One confirmation. One gas payment.

### **Important Notes**

* Always review every transaction included in the batch before signing.
* Gas fees and execution results may vary depending on network conditions and transaction complexity.
* Failed transactions within a batch may affect the execution of the remaining transactions depending on protocol behavior.