What is account abstraction? Why can it make wallets more like ordinary internet apps?
A traditional wallet is more like a key: the private key determines who can operate the account, and users also have to prepare native tokens to pay gas and complete operations such as approvals and swaps one by one.
Account abstraction turns account verification, fee payment, and execution rules into programmable logic, allowing smart accounts to support:
Passkeys, multisig, and custom verification
Social recovery and recovery across multiple devices
Spending limits, allowlists, and session permissions
Batch execution of operations such as approvals and swaps
Gas sponsorship by apps or Paymasters according to defined rules
Take ERC-4337 as an example: users submit a UserOperation, Bundlers collect, simulate, and package it, and the EntryPoint performs unified verification, settles fees, and calls the smart account to execute—all without modifying Ethereum’s core protocol.
However, keep in mind that “gas-free” does not mean the fees disappear; they are paid by the app, a Paymaster, or another party. Smart account code, recovery rules, upgrade permissions, plugins, and Bundler and Paymaster infrastructure can also introduce new security and availability risks.
The essence of account abstraction is not to eliminate security responsibilities, but to turn account rules that were once “hard-coded” into programs that can be designed for different scenarios.
Coming next:
Friday | Trading Technology Class | Episode 007
“What Is a Divergence Between Volume and Price? When Is It a Trend Warning, and When Is It Just Noise?”
A traditional wallet is more like a key: the private key determines who can operate the account, and users also have to prepare native tokens to pay gas and complete operations such as approvals and swaps one by one.
Account abstraction turns account verification, fee payment, and execution rules into programmable logic, allowing smart accounts to support:
Passkeys, multisig, and custom verification
Social recovery and recovery across multiple devices
Spending limits, allowlists, and session permissions
Batch execution of operations such as approvals and swaps
Gas sponsorship by apps or Paymasters according to defined rules
Take ERC-4337 as an example: users submit a UserOperation, Bundlers collect, simulate, and package it, and the EntryPoint performs unified verification, settles fees, and calls the smart account to execute—all without modifying Ethereum’s core protocol.
However, keep in mind that “gas-free” does not mean the fees disappear; they are paid by the app, a Paymaster, or another party. Smart account code, recovery rules, upgrade permissions, plugins, and Bundler and Paymaster infrastructure can also introduce new security and availability risks.
The essence of account abstraction is not to eliminate security responsibilities, but to turn account rules that were once “hard-coded” into programs that can be designed for different scenarios.
Coming next:
Friday | Trading Technology Class | Episode 007
“What Is a Divergence Between Volume and Price? When Is It a Trend Warning, and When Is It Just Noise?”
