-
Notifications
You must be signed in to change notification settings - Fork 4
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
First Release #1
Conversation
/// Given domain as `<g>`, `CosetOfDomain` represents `h<g>` | ||
/// | ||
/// Constraint equivalent is in `r1cs_std::poly::domain`. | ||
#[derive(Clone, Copy, Eq, PartialEq, Debug)] | ||
pub struct Radix2CosetDomain<F: PrimeField> { | ||
/// A non-coset radix 2 domain: `<g>` | ||
pub base_domain: Radix2EvaluationDomain<F>, | ||
/// offset `h` | ||
pub offset: F, | ||
} |
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 exists in r1cs-std
now, right?
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.
Nope... r1cs-std
contains the constraint code, but this one is native. (The reason I defined this is that coset domain is not in ark-poly yet. If coset domain is used elsewhere, I can move it to ark-poly)
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.
Oh completely missed that this is native. The difference from the coset_*
operations on the existing EvaluationDomain
s is that this allows specifying the choice of offset for the coset, right? If so, I think it's useful to have in ark-poly
. I think the approach in arkworks-rs/algebra#88 (comment) makes sense
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.
Exactly. It Sounds good! I may make a PR after I finished up BCS, but if anyone have time go ahead. (Until then I will keep this impl in ldt)
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.
Thanks for review!
I think we should also have an issue detailing that we need to make an LDT trait, and LDT Gadget trait. I think its fine to not block making the repo public on this, as the exact trait API will likely be informed by your bcs work |
Description
Feature included in first release:
DirectLDT
and its constraintsBefore we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
Pending
section inCHANGELOG.md
Files changed
in the Github PR explorer