đŸ”Ŧ
Chainex Whitepaper
  • 👋ChainEx Overview
  • Technological Foundations
    • 💡Account Abstraction: The New Horizon
    • ✨ERC-4337
    • 👩‍🏭User Operations
    • 💡Usecases
  • ChainEx Fundamentals
    • đŸ“ĒDApps Suite
    • đŸ› ī¸Roadmap
    • đŸĒ™Tokenomics
    • â„šī¸ChainEx Token Utility
    • ❓FAQs
  • Revenue
    • 💸Revenue Sharing
    • đŸ’ĩRevenue Generation Stratergy
    • 💲Paymaster Fees
  • SDK Integration Docs
    • 👨‍đŸ’ģGetting started
    • 🌟Initializing SDK
    • 💸Making transactions
    • đŸ•šī¸Demos
  • Community
    • 🌐Website
    • 📞Telegram
    • đŸĻTwitter
Powered by GitBook
On this page
  1. Technological Foundations

Usecases

Some of the use cases of account abstraction

Last updated 1 year ago

Smart contracts are infinitely more flexible in their capabilities than EOAs. Each smart contract can define different rules and configurations within its code.

Some examples of use cases can be seen below:

Use Case

EOAs

Contract Accounts

Permission controls

Private key grants full access to everything.

Define a list of tiered permission levels. e.g. Require 3 out of 5 signers to approve a transaction.

Batch transactions

Each individual action requires a separate signature.

Capable of batching transactions together; e.g. approving a token transfer and transferring a token in the same operation.

Account Recovery

Loss or exposure of private key means full loss of control over the wallet.

There is no private key. You can write any arbitrary logic in code that allows you to recover the funds in the wallet.

Transaction limits

Any transaction your wallet signs is what occurs. You cannot restrict anything.

Write any logic to control how funds can be transferred. E.g. a function to halt transactions to other addresses while you recover your account.

These are just a few of the capabilities that contract accounts offer over traditional EOAs. The key thing is; that contract accounts are code.

This means anything you can write in code is therefore possible in a contract account.

💡