Ethereum Account Abstraction

I sketched out my "dream wallet" that would be 10x better than anything in web2 or onchain today

need to solve a bunch of hard challenges, but i think we can get there in the next ~6-12 months. 

onchain is going to be 100x better than online.

doing numbers podcast

more tactically speaking: 
- imagine if my 'every day wallet that i carry my history and have all my things in it, yaddyada' is a Safe that's set to 1/n
- thus any of the n number of keys signing can get the Safe to execute a transaction
- the safe is a little different such that there's a special role called 'the admin'. this is one of the n's and can get the safe to do regular transactions. but also, this is the only role that can add more n's. (whereas if a normal safe is 1/n the any of the n's can add another n).
- the admin role would be a passkey. this wallet now in and of itself with only 1/1 with the passkey is just Coinbase Smart Wallet. 
- but then if the user is signing into FT, they would create an EOA and leave it inside the FT app then sign a passkey saying that the FT EOA is now one of the n's. 

now the same wallet can be both a Coinbase Smart Wallet and an FT embedded wallet. just that the key embedded in FT isn't itself a wallet, but a signer on a smart wallet.

how would you enforce the spending limit in a smart wallet? isn't the wallet unaware of state change that's caused by the calldata that they pass through? 

separately, here's an idea i had for solving for the issue of having 200,000 dapp wallets. wdyt?

@base builder #001; onchain cities w/ OAK & city3

how would you enforce the spending limit in a smart wallet? isn't the wallet unaware of state change that's caused by the calldata that they pass through? 

separately, here's an idea i had for solving for the issue of having 200,000 dapp wallets. wdyt? https://warpcast.com/kia.eth/0xc0341ade

1. onchain policies for spending is a hard open challenge. we are working on it. there are offchain ways of doing it that still have ok properties (e.g. ability to exit if you don't like), but i think we can do better.

2. i think it's probably too complicated. why not just make a great unified wallet that works everywhere :)

1. curious how y'all will work through solving onchain policies. it's a tough a one. 

2. how would solve having a passkey wallet but not requiring a faceID for every onchain in select apps? FT and others who use embeds can't degrade experience but the 1 app 1 wallet model is not sustainable.

coinbasewallet

Coinbase Smart Wallet session key demo! Session keys combine the enhanced UX of embedded wallets with the benefits of a unified account.

This video shows a demo and goes over some of the thinking behind our approach.

We're excited to get this in the hands of developers, so reach out to me if you're interested in experimenting with this and I'd be happy to help you get setup.

1. stay tuned - lots of work to do

2. check this out from @lsr! already in alpha devs hands, going to audit soon. going to be incredible.

oh this is very similar to what i was saying. way more elegant though! this is the gwei

1. stay tuned - lots of work to do

2. check this out from @lsr! already in alpha devs hands, going to audit soon. going to be incredible.

https://warpcast.com/lsr/0xfd66a627