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

Add config switch for primary network validator signature verification optimization #454

Closed
cam-schultz opened this issue Aug 21, 2024 · 0 comments · Fixed by #537
Closed
Assignees
Labels
enhancement New feature or request

Comments

@cam-schultz
Copy link
Collaborator

Context and scope
subnet-evm and coreth support an optimization for verifying Warp messages from the primary network in which only the validators of the receiving subnet need to sign the message. For example, this allows a subnet to "self sign" a message from the C-Chain, rather than having to verify an aggregate signature consisting of 1000's of individual BLS signatures.

ACP-77 removes primary network validation as a subnet validation requirement, so such "self signing" is no longer guaranteed to be meaningful. As such, subnet-evm and coreth are making this behaviour configurable at the Warp precompile level.

Discussion and alternatives
We'll need to support both signature aggregation methods. This new config option will be published in the chain config, so we can fetch it in the same way we fetch the Warp quorum configuration currently. When aggregating signatures for messages originating from the primary network, we'll need to take into account the destination's signature verification rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants