-
Notifications
You must be signed in to change notification settings - Fork 384
feat: Elastic verifier, that allows owner to set multiple VKs #1599
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
Conversation
@@ -191,7 +191,7 @@ contract GatewayCTMDeployer { | |||
_isZKsyncOS: _config.isZKsyncOS, | |||
_deployedContracts: contracts | |||
}); | |||
_deployVerifier(salt, _config.testnetVerifier, contracts); | |||
_deployVerifier(salt, _config.testnetVerifier, contracts, _config.aliasedGovernanceAddress); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you provide the aliased address of the main governance.
however, this file is now used only locally so what is provided there does not really matter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, do we have any place in the config where we have CTM owner?
@@ -104,16 +125,25 @@ contract DualVerifier is IVerifier { | |||
/// @inheritdoc IVerifier | |||
/// @dev Used for backward compatibility with older Verifier implementation. Returns PLONK verification key hash. | |||
function verificationKeyHash() external view returns (bytes32) { | |||
return PLONK_VERIFIER.verificationKeyHash(); | |||
return plonkVerifiers[0].verificationKeyHash(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
always 0, is it intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I wanted it to return a 'default' verification key hash...
…_elastic_verifier
Support multiple verifiers (VKs) in a single dual verifier.
This will allow us to iterate quickly in stage & testnets with the new zkos system.
Admin will be able to add/remove verifiers based off their Ids.