Going further #2: Native Account Abstraction
Overview of how Abstract is using Account Abstraction
What is Account Abstraction (AA) ?
Account abstraction (AA), from EIP-4337, enables the use of smart contracts as wallets, as opposed to EOAs like Metamask (EOA: External Owned Account : public/private key pair ). It provides a standardized way for smart contracts to act as a wallet and handle transactions.
It was implemented with ERC-4337 on Ethereum in March 2023, but got different "upgrades" like the EIP-7702 from May 2024.
Currently, AA is used to improve onboarding experience and UX, like paymasters functionalities (free gas fees or payment using ERC-20 tokens other than ETH).
How does Abstract use AA ?
Even though Abstract's AA and Ethereum's EIP-4337 both aim to enhance accounts' flexibility and user experience, they differ on 4 critical aspects :
Implementation Level - Abstract's approach to AA is to build it natively to the protocol which can be called Native Account Abstraction (NAA), whereas EIP 4337 avoids the implementation at the protocol level.
Account Types - On Abstract all accounts (even EOAs) behave like smart contract accounts; all accounts support paymasters.
Transaction Processing - On Abstract, there is a single mempool (waiting areas for transactions) and transaction flow.
Paymaster Support - Abstract allows both EOAs and smart contract accounts to benefit from paymasters thanks to its single transaction flow
To put it simply :
The main goal is to make the onboarding flow better for users and easier for devs.
Sources :
https://docs.abs.xyz/ https://x.com/jarrodWattsDev/status/1824447767030497701https://x.com/jarrodWattsDev/status/1788119041024168385 https://cryptoast.fr/account-abstraction/
Last updated
Was this helpful?