Today we talk Account Abstraction! 🥳 Let’s start from the end: UX, UX, UX. Account Abstraction is key for superior UX. We owe users maximum efforts for the best UX possible. Best UX requires suitable infrastructure. By “suitable infrastructure,” I mean one that will enable to customize and optimize apps/wallets UX. So - AA is a solution for the famous clunky and cumbersome experience that is the average crypto UX. But before we understand what this solution does, we need to understand the problem. Clunky UX In Ethereum, and EVM chains, and nearly all chains that came after, there are two types of accounts: user accounts and smart contracts. User accounts (aka EOAs): - Have a specific set of actions they can perform: They can make a payment or trigger a smart contract to run code (and a couple more things). - Users must sign with their private key each and every tx that their account issues. - You cannot customize their signature logic. You cannot have a customized recovery mechanism for these accounts. Smart contracts are accounts that run code (Let’s say apps). - When triggered (by user accounts or by another smart contract), they perform the action they were designed to do. - They can trigger other smart contracts, but they cannot trigger themselves. Even if you have a smart contract that triggers another smart contract, you must have a user account triggering the first transaction. So user accounts are needed to trigger smart contracts, and their behavior or operation logic lacks flexibility. This lack of flexibility is limiting the UX that apps can build and users can have. Account Abstraction Account Abstraction means that user accounts are also smart contracts (not EOAs). Not being limited by the specific logic that EOAs have, means that we are also not limited in the behavior/logic that we can create for users. We can abstract away the UX limitations. Now we come to the part of superior UX for wallets Okay, user accounts - wallets - are now smart contracts (we can call them smart wallets). This opens up a lot of room for UX creativity when it comes to wallet management. *For example*: - Use your smartphone’s biometrics and cryptography to authorize payments? Yes. - Have a smart wallet that is a multi-sig? Yes. - Authorize monthly payments, set a deadman switch that’ll automatically transfer funds to someone else in case of no activity (or lost keys)? At the risk of sounding repetitive - yes. - Batch together several calls to multiple contracts and send it as one transaction? Yes. - Moooar stuff that EOAs can't do? Yes. This sounds like a bunch of technical stuff, but it compiles into a smooth, custom-made flow that gets rid of the crypto-ish experience that drives users away from crypto. It is crucial that crypto UX will compete with any non-crypto app if we want to onboard my neighbor, and your aunt, and that friend from work. Account Abstraction is such an important element that Starknet was built with AA baked into its design (which we call Native Account Abstraction). 2 topics - Paymaster and Native Account Abstraction - are really worth explaining too, but this tweet is really quite long already. So Paymaster and *Native* Account Abstraction will wait for tomorrow (more or less). Hope this explanation makes it clear why AA is 🗝️

🚨 Gas UX on Starknet just changed. Forever. 🚨 Introducing the Starknet Paymaster - an open-source, production-ready, developer-first way to abstract gas fees. → Sponsor txs → Accept any token for gas → Run it yourself Let's talk 👇