Skip to content
This repository was archived by the owner on Oct 31, 2023. It is now read-only.

feat: implement taper challenge handling, and upate proofs #43

Merged
merged 2 commits into from
Apr 4, 2019

Conversation

dignifiedquire
Copy link
Contributor

@dignifiedquire dignifiedquire commented Mar 15, 2019

Ref #38

@dignifiedquire
Copy link
Contributor Author

@nicola @porcuquine need the default values for tapering, to finish this

src/bin/game.rs Outdated
.long("taper")
.help("fraction of challenges by which to taper at each layer")
.default_value("0.0"),
)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be an option, tapered should be the default zigzag

src/bin/game.rs Outdated
.default_value("0.0"),
)
.arg(
Arg::with_name("taper-layers")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be an option, tapered should be the default zigzag

layers: val.layers.map(|v| v as i32),
expansion_degree: val.zigzag.as_ref().map(|v| v.expansion_degree as i32),
layers: val.zigzag.as_ref().map(|v| v.layers as i32),
is_tapered: val.zigzag.as_ref().map(|v| v.is_tapered),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should never run a non-tapered zigzag

@porcuquine
Copy link

@dignifiedquire Default taper is 0.3.

@nicola
Copy link
Collaborator

nicola commented Mar 16, 2019

see my comments ^

@nicola
Copy link
Collaborator

nicola commented Mar 17, 2019

I will approve this only when this either becomes the only way to run zigzag or the default way (with updated readme)

@dignifiedquire
Copy link
Contributor Author

@nicola @porcuquine updated to have fixed values for tapering and challenges, please recheck those values

@porcuquine
Copy link

@dignifiedquire I am sorry, it is supposed to be 1.0 / 3.0 not 0.3. My mistake.

@porcuquine porcuquine changed the title feat: implement taper challenge handeling, and upate proofs feat: implement taper challenge handling, and upate proofs Mar 19, 2019
@nicola nicola requested review from porcuquine and nicola March 19, 2019 01:18
@dignifiedquire dignifiedquire merged commit 026f840 into master Apr 4, 2019
@dignifiedquire dignifiedquire deleted the fix-challenges branch April 4, 2019 14:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants