-
Notifications
You must be signed in to change notification settings - Fork 854
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
Extend Safe With Additional Signing Schemes #698
Comments
ZeroDev does something interesting by pulling signing logic using For v1.5 contracts, however, we do not want to fundamentally change the signing logic. |
This has been mentioned in https://forum.safe.global/t/safe-contract-v2/87 as |
Context / issue
It is currently possible to extend the Safe with additional signature schemes (such as P256 elliptic curve signatures) by deploying a signer contract per public key.
Proposed solution
Evaluate the required changes to the Safe account in order to support additional signing schemes internally without requiring a contract per public key. A possible solution would be for owners to not just be an address but also contain additional context.
While this proposal may not be the ideal way to implement it, it is worth investigating from a technical perspective how this could work, specifically geared towards the following two use-cases:
Additional Context
This is not expected to change in Safe v1.5 as it would require a major overhaul in the signing logic which is out of scope for v1.5
The text was updated successfully, but these errors were encountered: