Content
@
0 reply
0 recast
2 reactions
evmBrahmin
@evmbrahmin.eth
Working on collecting feedback & pain points for both 4337 (AA) and 6900 (modular smart accounts) If you’re a builder (dev, product, design, etc) and have feedback or questions please reach out either here or in DMs Let’s improve standards and infrastructure together 🦾
1 reply
1 recast
5 reactions
Samuel ツ
@samuellhuber.eth
lack of getting started for app developers wanting to use 4337. sample case: App dev wants to have smart account (social wallet) in their app and pay gas via Paymaster for their users - build userOp as "easy" as current Transactions - let user choose bundler if they want and have a default missing a nice starter imo
1 reply
0 recast
4 reactions
xh3b4sd ↑
@xh3b4sd.eth
I was wondering whether I can make use of AA in an app I am working on but right now I wouldn't even know where to start and had to dig quite a bit. Is it that paymasters only cover the gas and the user still has to sign a transaction or is the signing also done on behalf of the user? Trust assumptions would differ.
1 reply
0 recast
1 reaction
Samuel ツ
@samuellhuber.eth
User Wallet is signing then you pass that as userOp to your bundler and say which paymaster will cover gas For our NFT-protecting wallet, for most user ops we’d pass a signature of the rest of the op signed by our main key. https://www.alchemy.com/blog/account-abstraction
1 reply
0 recast
1 reaction
xh3b4sd ↑
@xh3b4sd.eth
Thank you so much for the blog post. I will dig into it later. Pressing the lazy button here. Would it be possible for a user to "authorize" an app to schedule certain transactions on my behalf so that the user signs once and the app can fan out multiple transactions later? Or is it that the user must sign every time?
1 reply
0 recast
0 reaction
rahul
@phenomenon
you can use session keys in combination with smart accounts to perform transactions without needing the user to sign each transaction. users can give the session keys “permissions” to perform select actions on their behalf a web2 analogy for this is oauth style permissions
1 reply
0 recast
3 reactions
evmBrahmin
@evmbrahmin.eth
https://docs.zerodev.app/blog/session-keys-are-the-jwts-of-web3
0 reply
0 recast
1 reaction
