Why should SUAVE implement RIP-7560 or consider running a 4337 bundler inside SGX?
Shill me on why SUAVE should implement RIP-7560?
7
Before we begin, I want to clarify that I am not an expert in MEV or someone who has an in-depth understanding of SUAVE. I only had an opportunity to work on SUAPP during a hackathon and had a chance to speak with Daniel to learn more about SUAVE.
Let's delve into the mechanism details and explore how we aim to solve it
github.com/getclave/sucla…
My view about SUAVE as a researcher on the team that builds consumer-facing crypto applications is SUAVE should be the gateway for users to interact with the blockchain world. We have enough rollups and L1s but MEV and interop area are still lacking.
SUAVE is an orderflow machine which can give users the best execution path while giving the highest profit possible for validators. This is possible via their SGX-based architecture, so I highly believe that SUAVE can be used as a source of trust across the blockchain world.
The best part of SUAVE for developers is the ability to abstract the chains, which is a real thing (not like other "chain abstraction" buzzwords). However, Ethereum's current account model is not designed for the best user experience, making it difficult to build abstracted apps.
Without account abstraction, SUAVE is like a Ferrari with an old chair inside. Because users should not care about the seed phrases, the gas token, or even the chains themselves. And the best part? We can solve the multi-chain AA problems if accounts are settled on SUAVE.
I don't think that RIP-7560 or 4337 differs a lot because I can not see any trust assumption changes with an ERC-4337 bundler running inside SGX and RIP-7560. But AA is a must for SUAVE, not something that good to have.