This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
Update EmailAccountRecoveryRouter and SafeZkEmailRecoveryPlugin contracts. #230
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jacque006
approved these changes
Apr 5, 2024
jacque006
merged commit 01353c1
into
getwax:feature/email-recovery-circuits
2 checks passed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR doing?
I updated the EmailAccountRecoveryRouter and SafeZkEmailRecoveryPlugin contracts to implement all of the external functions of
EmailAccountRecoveryin EmailAccountRecoveryRouter. Besides, I added some requirements to SafeZkEmailRecoveryPlugin for better security.How can these changes be manually tested?
I confirmed that the test of
forge test --match-contract SafeZkEmailRecoveryPlugin_Integration_Test -vvpassed.