Batched execution
Pali smart accounts support batched execution through wallet_sendCalls. This lets the user approve multiple calls with one wallet review and one smart-account authorization. Depending on the active validator, that authorization may be a passkey proof, an ECDSA signature, or a composite policy.

Example: approve and transferFrom
const result = await window.ethereum.request({
method: 'wallet_sendCalls',
params: [
{
version: '2.0.0',
from: smartAccount,
chainId: '0x39',
atomicRequired: true,
calls: [
{
to: erc20Token,
value: '0x0',
data: erc20Interface.encodeFunctionData('approve', [
spender,
amount,
]),
},
{
to: spender,
value: '0x0',
data: spenderInterface.encodeFunctionData('transferFrom', [
smartAccount,
recipient,
amount,
]),
},
],
},
],
});
Atomic UX
For every wallet_sendCalls request, the user approves or rejects the full batch; individual calls cannot be deselected. A supported Pali smart account prepares the complete batch as one account execution. EOA calls run sequentially, and already broadcast calls cannot be rolled back if a later call fails.
Gas payment
The current Pali flow submits smart-account executions with a wallet gas payer. Dapps should plan for wallet-paid gas instead of presenting the flow as gasless.
Unsupported call type
Smart-account wallet_sendCalls does not support contract deployment calls expressed as empty target transactions. Deploy contracts separately or use a target contract call.