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

[EFM] Minimal Data Model Change to Represent DKG key vectors as mapping #6235

Closed
jordanschalm opened this issue Jul 22, 2024 · 0 comments
Closed
Assignees
Labels
Protocol Team: Issues assigned to the Protocol Pillar.

Comments

@jordanschalm
Copy link
Member

Context

We need to update the Protocol State and related components to represent (and use) DKG key vectors as mappings. See full context here: #6214.

This functionality will be released with EFM Recovery as a Protocol HCU after the Crescendo Network upgrade.

This issue represents the minimal subset of changes associated with #6214 in order to avoid data model changes in that HCU (which would complicate deployment).

Definition of Done

  • All DKG data models persisted to disk include an IndexMap field (possibly empty for now)
@jordanschalm jordanschalm added the Protocol Team: Issues assigned to the Protocol Pillar. label Jul 22, 2024
@jordanschalm jordanschalm added this to the EFM-Q2 EFM Core updates milestone Jul 22, 2024
@jordanschalm jordanschalm self-assigned this Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Protocol Team: Issues assigned to the Protocol Pillar.
Projects
None yet
Development

No branches or pull requests

1 participant