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

Further optimize size of Prio3PrepareState #1128

Open
divergentdave opened this issue Nov 1, 2024 · 0 comments
Open

Further optimize size of Prio3PrepareState #1128

divergentdave opened this issue Nov 1, 2024 · 0 comments

Comments

@divergentdave
Copy link
Collaborator

Prio3PrepareState currently stores a measurement share, represented as a seed for the helper or a vector of field elements for the leader. This is a space savings for the helper over the specification, which describes the prepare state as always containing the output share. An implementation note lays out this very optimization.

We could go a step further, and save some space on the leader side with selected VDAFs, if we stored the output share for leaders and the measurement share for helpers. The output share may be smaller than the input share for Prio3Sum, Prio3SumVec with bits > 1, etc. This would be a breaking change to the prepare state, which we expect users to encode and save to disk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant