AIE Chain
  • AIE Chain SoK
    • Introduction
    • Challenges
      • Blockchain Scalability
      • Gas Issues
      • Unfriendly UX
    • AIE Unique Propositions
    • AIE Chain
      • Building Blocks
      • AIE Chain Architecture
      • AIE Chain Specifications
        • Contracts
        • Contract addresses & RPCs
      • AIE Name Service
      • Bridges
      • AIE Block Explorer
    • AIE Embedded Wallet
      • Account Abstraction
      • Smart Wallet Creation
      • Privacy and Security
      • Gasless Transaction
      • ANS Compatible
      • Export & Import
      • Backup & Recovery
    • AIE Token
    • Onboarding the next billion Web3-users
      • Genesis Marketplace
        • Bring your imagination to life
        • Sign your creative works
        • Mint your creative works into NFT
        • NFTs Marketplace
      • RizzAI: Web3 AI-powered virtual companions
        • Register
        • Log-in
        • Create AI Character
        • View your AI characters
        • Edit your AI character
        • Chat with AI companions
        • Premium Subscription
        • Gallery
      • Rakis: Decentralized Verifiable Inference Network
        • Overview
        • Architecture
        • Data Flow
        • Consensus
      • Interactive AI LiveStreaming
      • Collaborative Content Creations
      • Decentralized Licensing
    • FAQs
Powered by GitBook
On this page
  1. AIE Chain SoK
  2. AIE Embedded Wallet

Account Abstraction

PreviousAIE Embedded WalletNextSmart Wallet Creation

Last updated 1 year ago

Account Abstraction lets users create non-custodial wallets as programmable smart accounts, which are independent smart contracts that can initiate and execute transactions without the need for an EOA.

The operation of smart accounts, or account abstracted wallets, is fairly simple. Instead of sending regular transactions as EOAs do, smart accounts use objects called UserOperations, which represent an operation that is to be conducted on behalf of the user.

The UserOperation object has multiple data elements that describe the type of transaction, the token, limit and price for gas at various steps of the transaction, the signature to validate the transaction, and other metadata.

Every time a smart account sends a UserOperation, it goes into the common waiting area for all UserOperations called the alt mempool.

These requests are then bundled by bundlers, who are similar to nodes verifying regular transactions. They even use the same logic as mining or validator nodes to prioritize transactions where they can extract the most value.

The bundled UserOperations are sent through a single whitelisted “Entry Point,” where every individual UserOperation is verified and executed by calling different functions.

As UserOperations can include any type of logic, it allows users to implement various customizations to how they want to manage their accounts and the funds in them.

The Paymaster component refers to smart accounts that enable third-party entities to sponsor and pay for transactions. With the use of paymaster, ****users will not need to own the blockchain’s native token to pay for transactions (i.e., gasless transactions), improving accessibility. The owner of the paymaster contract can further define the rules under which user operations can be sponsored.

Account Abstraction Overview

In sum, account abstraction improves on transaction flexibility and UX, allows designated smart contracts to cover gas fees, supports multiple signers for one account, and offers alternatives to seed phrases for account recovery, thereby simplifying the user experience.

ERC-4337