-
Notifications
You must be signed in to change notification settings - Fork 352
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
Make the Account setPublicKey function a two-steps process #469
Labels
Comments
Merged
What about an optimization: make it a single tx that takes the incoming pubkey's new signature to validate the process. |
Apparently I suggested that already 😅: #818 |
@martriay may i work on this issue? |
Same as #21 (comment), let's focus on the ongoing ones first. |
Closing in favor of #818 |
github-project-automation
bot
moved this from 👀 In review
to ✅ Resolved
in Contracts for Cairo
May 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cairo-contracts/src/openzeppelin/account/presets/Account.cairo
Lines 47 to 53 in b764660
This method can make the contract unusable if a wrong public key is set by mistake. Maybe it would be good to add a two steps process allowing to claim the new public key before removing the old one? (Similar to the two-step ownership transfer process in Solidity contracts).
Also applies for setEthAddress in EthAccount.cairo:
cairo-contracts/src/openzeppelin/account/presets/EthAccount.cairo
Lines 45 to 51 in b764660
The text was updated successfully, but these errors were encountered: