Yep, there are modules that exist in the ERC-7579 (modular smart account standard) ecosystem that can perform these functions. For (1) you will need an offchain service that watches for new token events on the wallet. But is trustless. (2) is easy byproduct of solving (1) (3) I don’t think is possible. You could use something similar to (1) to auto burn
Kurt
Co-Founder @rhinestone
Latest casts
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.
Yesterday, we announced the Resource Lock Hook for ERC-7579 smart accounts. This Hook Module enables any specialized execution layer to seamlessly integrate with ERC7579 accounts and execute any intent through a single signature. Launching Q1 2025, with more to come! https://x.com/rhinestonewtf/status/1869044965797773656
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
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
Hey Varun, We've done a lot of thinking about this at @fid:238075 and it's formed the basis for a lot of the open source work we've done with Safe, zkSync, Biconomy, ZeroDev, OKX, and a number of others. The standard is called ERC-7579. This is a minimal standard for modular smart accounts. Modules are self-contained smart contracts that extend the functionality of a Smart Account. This will allow you to continue to support existing features (passkeys, gas abstraction, secure recovery mechanisms etc) but also provide new tools for the problems you raise. 1. If a user wants to change apps they can import the account and enable a new signer dedicated to that app or enable a session key to give the app scoped access. 2. No direct solution, but scoped executor modules and session keys can make this secure, whilst still open and programmable for applications. 3. Any developer can build a module, which under the right permissioning framework, can allow apps/users to extend the functionality of their account