I just wanted to jot down an idea which occurred to me when skimming the EIP-7702 spec: we should be able to implement a “delegate contract” connected to the protocol adapter, such that a user could delegate (full or partial) control of an Ethereum EOA to logic executing inside the resource machine (such as a shielded multisignature, a more complex account authorization scheme implemented with the RM, an Anoma DAO, etc.).
Two great advantages of this approach are that:
- Users could “upgrade” their existing Ethereum EOAs (which own a lot of state) to “RM-enhanced EOAs” with a single signature.
- RM-control could add much more functionality to Ethereum EOAs than just basic account abstraction (as in e.g. ERC 4337), including, for example:
- Shielded authorization logic (e.g. a shielded multisignature). Many EOAs can be “swept” into unified control by a shielded RM app without revealing that they are controlled by one party.
- More complex authorization logic (e.g. different threshold limits and even per-transaction risk assessments with a selected set of providers) that would be expensive to run on the EVM (but for which we can make ZKPs of RM execution).
I think this could be interesting to further investigate in the context of future versions of the protocol adapter (perhaps depending in part on how EIP-7702 adoption seems to be going).