-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ERC: Router Proxy #647
base: master
Are you sure you want to change the base?
Conversation
The commit cd1e5de (as a parent of 778ed6a) contains errors. |
I would like to clarify that EIP-2535 Diamond can be implemented with hardcoded module addresses and selectors, and this has been done by the Pendle project. In general I really like this idea and I would like to see a new standard that standardizes this kind of implementation but that also implements EIP-2535 Diamonds, which is not hard to do. An article that covers the minimum things required to comply with the EIP-2535 Diamonds standard is here: https://eip2535diamonds.substack.com/p/compliance-with-eip-2535-diamonds |
The Router Proxy Standard introduces a streamlined approach to managing multiple implementations behind a single proxy, similar to the Diamond Proxy Standard (ERC-2535). Unlike the latter, this method hardcodes module addresses within the proxy’s implementation contract, offering a simpler, more explicit, and gas-efficient mechanism. This design reduces complexity, making it easier to reason about and improving overall efficiency while retaining the flexibility to manage multiple modules.