@@ -12,27 +12,33 @@ Before exploring the details of account abstraction, it's important to first und
12
12
limitations of Externally Owned Accounts (EOAs), like MetaMask and Rainbow, and how account
13
13
abstraction addresses these challenges.
14
14
15
- ## Problem with EOAs
15
+ ## Web3Auth's Native Account Abstraction
16
16
17
- Since the beginning of Web3, wallets have been a crucial component for interacting with the
18
- blockchain. The most common type of wallet is the Externally Owned Account (EOA), which is a wallet
19
- controlled by a private key .
17
+ Web3Auth offers seamless integration of Account Abstraction with just a few lines of code, making it
18
+ easier than ever to onboard users into decentralized applications. Our goal is to simplify and
19
+ streamline the entire process while ensuring users benefit from advanced functionality .
20
20
21
- Although it still fails to onboard new users due to non intuitive user experience of navigating the
22
- blockchain ecosystem and managing the wallets. EOA wallets, regardless of type, can only be accessed
23
- through private keys.
21
+ If you are already using the Web3Auth PnP Web SDK with
22
+ [ EthereumPrivateKeyProvider] ( /docs/sdk/pnp/web/providers/evm ) , you can now easily use account
23
+ abstraction by just configuring the
24
+ [ AccountAbstractionProvider] ( /docs/sdk/pnp/web/providers/aa-provider ) , and passing to the Web3Auth
25
+ instance. Previously to use account abstraction, developers had to maintain the additional flow for
26
+ account abstraction using third party packages.
24
27
25
- You must have heard the quote, “Not your keys, not your crypto”. The user is solely responsible for
26
- safeguarding the private key with the best practices, which can often be overwhelming for the
27
- general non tech savvy users. Once the private key is compromised or lost, EOA wallet cannot recover
28
- the account and can result in irreversible loss of assets .
28
+ With native account abstraction, you can create and manage smart accounts using your favorite
29
+ libraries like Viem, Ethers, and Web3.js. This allows you to effortlessly create ERC-4337 compatible
30
+ Smart Contract Wallets (SCWs), and give users the ability to perform batch transactions and
31
+ efficiently manage gas sponsorship .
29
32
30
- Moreover the EOA wallets doesn't support advanced transaction patterns like batch transactions,
31
- sponsored transactions, etc.
33
+ ### Getting Started
34
+
35
+ Web3Auth's native account abstraction gives you the flexibility to choose your preferred account
36
+ abstraction provider, configure your bundler client, and integrate your paymaster. Learn how to use
37
+ [ Web3Auth with Account Abstraction] ( /docs/sdk/pnp/web/providers/aa-provider ) .
32
38
33
39
## Why Smart Contracts Wallets?
34
40
35
- Smart contract wallets(SCWs) solve the problem of onboarding by allowing users to use social logins
41
+ Smart contract wallets(SCWs) solves the problem of onboarding by allowing users to use social logins
36
42
or other web2 authentication for account management, and recovery. Moreover, SCWs provide more
37
43
granular control and programmability like
38
44
@@ -166,25 +172,3 @@ allows bundler to submit multiple UserOperations in a single transaction.
166
172
167
173
For validating the aggregated signature, the Aggregator also has the ` validateSignatures ` function
168
174
used by the EntryPoint contract during the validation phase.
169
-
170
- ## Native Account Abstraction
171
-
172
- Web3Auth offers seamless integration of Account Abstraction with just a few lines of code, making it
173
- easier than ever to onboard users into decentralized applications. Our goal is to simplify and
174
- streamline the entire process while ensuring users benefit from advanced functionality.
175
-
176
- If you are already using the Web3Auth PnP Web SDK with
177
- [ EthereumPrivateKeyProvider] ( /docs/sdk/pnp/web/providers/evm ) , you can now easily use account
178
- abstraction by just configuring the
179
- [ AccountAbstractionProvider] ( /docs/sdk/pnp/web/providers/aa-provider ) , and passing to the Web3Auth
180
- instance. Previously to use account abstraction, developers had to maintain the additional flow for
181
- account abstraction using third party packages.
182
-
183
- With native account abstraction, you can create and manage smart accounts using your favorite
184
- libraries like Viem, Ethers, and Web3.js. This allows you to effortlessly create ERC-4337 compatible
185
- Smart Contract Wallets (SCWs), and give users the ability to perform batch transactions and
186
- efficiently manage gas sponsorship.
187
-
188
- Web3Auth's native account abstraction gives you the flexibility to choose your preferred account
189
- abstraction provider, configure your bundler client, and integrate your paymaster. Learn how to use
190
- [ Web3Auth with Account Abstraction] ( /docs/sdk/pnp/web/providers/aa-provider ) .
0 commit comments