Content pfp
Content
@
0 reply
0 recast
2 reactions

horsefacts pfp
horsefacts
@horsefacts.eth
I wrote a short post on account abstraction wallet security for @code4rena. It was great to take a deeper look at the spec. Wallets are critical and it’s important to get them right, but I’m excited for 4337. https://medium.com/code4rena/smart-account-security-69b544c0da86
5 replies
4 recasts
20 reactions

phil pfp
phil
@phil
Can you help me understand how this changes the custody requirements for end-users? Today, I am responsible for managing my private keys. If I use a 3rd party service to generate an AA wallet, where does the burden of custody shift?
2 replies
0 recast
2 reactions

horsefacts pfp
horsefacts
@horsefacts.eth
Really good question. Curious to hear others chime in. It depends a lot on the specific wallet implementation. EOA wallets are just a secret number, but AA wallets are software. So as a user you'll need to know what features that software supports and whether it's any good.
2 replies
0 recast
1 reaction

horsefacts pfp
horsefacts
@horsefacts.eth
Burden of custody will be a spectrum, but there will still be offchain keys you have to manage somehow. The simplest possible AA wallet is something like a 1/1 multisig: a wallet contract with a single owner that's still an EOA account. You can rotate the owner key, but you're still stuck if you lose it.
1 reply
0 recast
1 reaction

horsefacts pfp
horsefacts
@horsefacts.eth
Next on the spectrum is an EOA-owned wallet with a guardian or social recovery system (like your Farcaster recovery address). Now you still need to keep your key safe, but you can recover it if you lose it, maybe guardian accounts can pause the wallet if it gets stolen.
1 reply
0 recast
0 reaction