Skip to content
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

Support confidential EVM proxy deployments #530

Open
aefhm opened this issue Apr 3, 2024 · 0 comments
Open

Support confidential EVM proxy deployments #530

aefhm opened this issue Apr 3, 2024 · 0 comments

Comments

@aefhm
Copy link
Contributor

aefhm commented Apr 3, 2024

Is your feature request related to a problem? Please describe.
Current default proxy relies on a getStorageAt which does not work with confidential EVMs such as Sapphire.

Describe the solution you'd like
An integrated way to allow upgrades on confidential EVMs. #525 is one suggestion by using an exposed owner function.

Describe alternatives you've considered
An alternative would be to rewrite the proxy contract to conditionally check msg.data and compare against a list of values such as 0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103 and return the owner as requested.

Additional context
N/A. See proposed solution #525.

Happy to contain discussion on this issue or the suggested PR. Thanks for looking!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant