Batch Transactions (AA) and State Diffs are more powerful than you think. With Clave's batchcaller Contract , users can perform batch transactions while reducing data availability fees tanks to state diffs! How? Let me explain:

If you're not familiar with state diffs, you can refer to my previous blog post where I have explained the details of state diffs and why Account Abstraction is more powerful with state diffs.

Dogan (∎, ∆)

@doganeth_en

1/4337 (Account Abstraction) is gaining momentum, but it has a problem: high calldata costs. Fortunately, @zksync's state diff model offers a solution. It allows for reduced calldata costs for complex verification mechanisms on @getclave's account model

mirror.xyz

State Diff and Account Abstraction

The concept of Account Abstraction (AA) is gaining significant momentum in the blockchain space. Despite the promise it holds, AA faces a major challenge: the high costs associated with calldata. In...

261

5:49 PM • Dec 17, 2023

The TLDR of state diff is, some of rollups such as zkSync and Starknet only post state differences to L1 instead of sending all transaction data. This reduces the calldata costs, which make up almost 90% of a transaction's total cost. To explain it, let's give a simple example: Imagine a scenario where Alice sends 1 ETH to Bob and Bob sends 1 ETH to Charlie. State diff rollup only posts that Alice's balance is down 1 ETH and Charlie's balance is up 1 ETH, whereas TX data rollup posts all TX data.

In a DEX swap, the user first calls approve function and then transfer function. However, this UX is not efficient as it involves multiple steps, and users cannot perform a one-click swap. Also, this has a problem that resulting in users sending unnecessary data to L1.

Batch Transactions allow for the execution of two transactions at once, reducing gas fees and improving the user experience. Using Clave Account's BatchCaller contract, users can perform multiple transactions in a single transaction. This means that users approve the transaction and then do the swap by calling the transferfrom function in one transaction. The L2's storage slot, which lives in L1, only changes with User's changed balance and never learns about approval, reducing the call data cost.

Baki

@LibraryDefi

A little experiment on batching.

Currently, if you're swapping on @zksync:

- With EOA, the difference btw swap (2 tx: approve + swap) and ERC-20 transfer is 0.14-0.18$.

- With Clave, the difference btw swap (1 tx: approve + swap) and ERC-20 transfer is 0.02$.

Why are you…

61

3:10 PM • Jan 28, 2024

These contracts are open-source and accessible to all Smart Contract wallets in zkSync. If you're a dapp or a wallet looking to integrate BatchCaller into your project, our DMs are open!

clave-contracts/contracts/batch/BatchCaller.sol at master · getclave/clave-contracts

Clave Smart Contracts on zkSync. Contribute to getclave/clave-contracts development by creating an account on GitHub.

https://github.com