-
Notifications
You must be signed in to change notification settings - Fork 0
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 poc changes for #177 #1
Conversation
poc/flp_generic.py
Outdated
@@ -658,6 +658,12 @@ class SumVec(Valid): | |||
JOINT_RAND_LEN = 1 | |||
OUTPUT_LEN = None # Set by constructor | |||
|
|||
@classmethod |
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.
I choose to this approach, instead of making field
a __init__
parameter because
- Follow existing patterns in
vdaf_prio3.py
where we usingPrio3
as a template to createPrio3SumVec
etc. SumVec.Field
is closer to template/generic parameters than instance properties, to me
@@ -483,6 +510,41 @@ class Prio3HistogramWithLength(Prio3Histogram): | |||
return Prio3HistogramWithLength | |||
|
|||
|
|||
class Prio3SumVecWithMultiproof(Prio3SumVec): |
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.
This is the Prio3SumVec variant with configurable PROOFS
parameter.
44b4ea8
to
8b74ffc
Compare
length: Unsigned, | ||
bits: Unsigned, | ||
chunk_length: Unsigned, | ||
num_proofs: Unsigned, |
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.
One feedback we got in issue 177 is the algorithm identifier needs to commit to the choice of field and number of proofs. I think that means one code point needs to map to a particular choice of field and number of proofs. The current Prio3 does so by including the algorithm identifier in the domain separation tag.
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.
OK. I just pushed a commit to make it clear that algorithm ID is dependent on (field, num_proofs). Let me know.
e880a21
to
71f242a
Compare
* Support multiproofs in Prio3 * Add new Prio3SumVec variant, i.e. Prio3SumVecWithMultiproof, with configuration (field size, number of proofs) * Add with_field class methods to introduce new SumVec with configurable field size
2ee0feb
to
e11c788
Compare
#177