Kurt (kurtlarsen.eth)

This is an interesting perspective. I don’t think it needs to be an either or. The benefit of supporting EOA + 7702 is increased TAM for the developer. However, I would argue that there is no upside to giving new users an EOA + 7702, only downsides due to feature limitations and security. My recommendation would be to support a smart account that is 7702 compatible. Upgrade the existing EOA users and give the new users a full smart account.

• 6 replies
• 8 recasts
• 31 reactions

Introducing Rhinestone Protocol 1.0 🧩 The first smart account interoperability protocol Transforming smart accounts into the next open platform, aggregating and unifying the account stack to maximize distribution for devs. The foundations for the account-centric dev platform 🚀 For the full write up: https://blog.rhinestone.wtf/rhinestone-protocol-1-0-hits-mainnet-695469dce425 For the summary: https://x.com/rhinestonewtf/status/1851277911363633506

• 0 replies
• 3 recasts
• 8 reactions

ERC-7579. 35 modules, and we haven't even started! A slosh of compatible smart accounts inbound. erc7579.com/modules

• 0 replies
• 0 recasts
• 9 reactions

Disaster planning for your self-sovereign users? You need Social Recovery or the infamous Deadman Switch Both Smart Account features are part of our open-source Core Modules. Available to anyone and everyone building on Modular Smart Accounts. Check out our the guides ↓ Social Recovery https://docs.rhinestone.wtf/module-sdk/using-modules/social-recovery Deadman Switch https://docs.rhinestone.wtf/module-sdk/using-modules/deadman-switch

• 0 replies
• 0 recasts
• 8 reactions