What Are the Limitations of Account Abstraction?
What are the limitations of account abstraction? There are four main ones: it works only on Ethereum and EVM-compatible chains, smart accounts cost more gas than standard transfers, account security depends on contract code while signing keys still need protection, and it relies on infrastructure such as bundlers and paymasters. Understanding these limits is the only way to judge whether account abstraction fits your business.
Which Chains Support Account Abstraction?
ERC-4337 and EIP-7702, the two main routes to account abstraction, are both built on Ethereum’s contract capabilities and are used mainly on Ethereum mainnet and EVM-compatible chains. Bitcoin does not support this kind of programmable account, and other blockchains each have their own account models. Even across EVM chains, a smart account has to be deployed on each chain separately, and support for different versions of the standard varies from chain to chain. A business that needs to cover multiple chains has to prepare different solutions for different chains.
What Extra Costs Does Account Abstraction Add?
A smart account has to be deployed on-chain the first time it is used, and every operation after that adds signature verification and EntryPoint execution steps, so it uses more gas than a standard transfer. Sponsored gas hides fees from users, but the cost does not disappear; it moves to the app. At scale, businesses need to decide which actions to sponsor and how much, and guard against abuse that drains the budget.
What Security and Dependency Risks Does Account Abstraction Carry?
A smart account’s rules live in its contract, so a bug in the contract puts the account at risk, and the signing keys themselves still need proper protection, which account abstraction does not solve. EIP-7702 also introduces a new phishing risk: if a user is tricked into signing a malicious delegation, the assets at that address can be drained.
On top of that, user operations depend on bundlers to reach the chain and sponsored gas depends on paymasters to settle. If those services go down or stop sponsoring, transactions can stall. Smart accounts also sign differently from ordinary accounts, and some apps and protocols still do not fully support them.
How Can Businesses Work Around These Limitations?
A common approach is to combine account abstraction with MPC: use MPC to protect signing keys, use smart accounts to improve the experience on EVM chains, and keep ordinary addresses on chains such as Bitcoin. Sponsorship rules and high-risk actions can be checked by an off-chain policy engine, and critical infrastructure should have backup providers.
Conclusion
Account abstraction greatly improves the wallet experience, but it is limited by chain coverage, higher costs, contract risk, and dependence on infrastructure. Safeheron’s MPC Wallet-as-a-Service provides multi-chain MPC key management and a policy engine for businesses.
Wondering whether account abstraction fits your product? Contact Safeheron’s Sales Team to Book a 1:1 Demo
