-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
d4b67d7
to
b4ef43a
Compare
fedcda6
to
16d55a3
Compare
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.
Cool!
I still have to look through the proving code in more detail, but have some comments on the rest of the changes already.
uni-stark/src/proof.rs
Outdated
} | ||
|
||
#[derive(Debug, Serialize, Deserialize)] | ||
pub struct Commitments<Com> { | ||
pub(crate) trace: Com, | ||
pub(crate) stages: Vec<Com>, |
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.
pub(crate) stages: Vec<Com>, | |
pub(crate) traces_by_stage: Vec<Com>, |
uni-stark/src/proof.rs
Outdated
pub(crate) stages_local: Vec<Vec<Challenge>>, | ||
pub(crate) stages_next: Vec<Vec<Challenge>>, |
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.
Hmm, again, I would still include "trace" in the name. traces_by_stage_local
?
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 guess that's more a general comment: What's a stage? To me it's just a number, for anything else I think it would be better to give a more specific name.
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.
LGTM, but clippy is failing.
Support for challenges: main additions will include
prove()
intorun_stage()
andfinish()
to handle higher stage trace generation.NextStageTraceCallback
andCommittedData
to handle multiple traces.Folder
,check_constraints
, andSymbolicAirBuilder
for compatibility with assertions over traces of different stages.