# Account Abstraction

**Published by:** [krishn](https://paragraph.com/@krishn14/)
**Published on:** 2024-07-12
**URL:** https://paragraph.com/@krishn14/account-abstraction

## Content

Issues with Current Wallet ManagementDifficulties in handling private keysCosts associated with gas feesPrivacy preservation challengesDependency on middleman smart contracts for multiple transactionsIntroduction to Account AbstractionTraditional transactions require private key to sign dataAccount abstraction allows signing data with various methodsPossible authentication methods:Google accountGitHub accountSocial confirmation (friends' approval)Time-based limitationsSpending limitsFlexibility: Private key equals wallet changes to anything as walletBenefits of Account AbstractionCustomizable wallets (parental controls, approval systems)Third-party payment for transactions (no need for personal gas fees)How Account Abstraction WorksTwo implementations: Ethereum (Entrypoint smart contract) and ZK Sync (native support)Overview of the Entrypoint on EthereumDeploy smart contract to define signing methodsSign with approved method (Google, friends, etc.)Send user operation to alt mempool instead of Ethereum nodeAlt mempool nodes validate and send transaction on-chainAlt mempool nodes pay for gas (with conditions)ERC 4337 framework and handleOps function of entrypoint smart contractZK Sync's native Account AbstractionDefault accounts assume smart contracts for all addressesNo need for separate alt mempool nodesSimplified process compared to EthereumAdditional Components of Account AbstractionSignature Aggregator: Aggregates multiple signatures for multi-sig setupsPay Master: Allows defining who will pay for transactions, not necessarily the account owner

## Publication Information

- [krishn](https://paragraph.com/@krishn14/): Publication homepage
- [All Posts](https://paragraph.com/@krishn14/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@krishn14): Subscribe to updates