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

Implement SigAgg component #184

Closed
corverroos opened this issue Mar 6, 2022 · 0 comments
Closed

Implement SigAgg component #184

corverroos opened this issue Mar 6, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@corverroos
Copy link
Contributor

Problem to solve

The architecture spec defines a SigAgg component, but it doesn't exist yet.

Proposed solution

Implement it according to the spec.

@corverroos corverroos added the enhancement New feature or request label Mar 6, 2022
@corverroos corverroos self-assigned this Mar 6, 2022
corverroos added a commit that referenced this issue Mar 7, 2022
Adds a static values providing beacon mock. This will be required for testing the SigAgg component since it depends on the eth2client.DomainProvider. It adds real world static value to the beaconmock by serving an embedded json file. A script is included to generate the json.

category: testing
ticket: #184
corverroos added a commit that referenced this issue Mar 7, 2022
To test signature aggregation, we need to create signatures. This add a validator client mock that performs attestations, including signatures as per spec. This will be used to test the SigAgg component.

category: testing
ticket: #184
corverroos added a commit that referenced this issue Mar 8, 2022
Implements the core workflow's signature aggregation component.

category: feature
ticket: #184
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
None yet
Development

No branches or pull requests

1 participant