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

final changes for v0.5 #89

Merged
merged 2 commits into from
Nov 4, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aggregator_server/aggregator_server.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ static void load_keypair(
keypair_file.c_str(), std::ios_base::in | std::ios_base::binary);
in.exceptions(
std::ios_base::eofbit | std::ios_base::badbit | std::ios_base::failbit);
return wsnark::keypair_read_bytes(keypair, in);
wsnark::keypair_read_bytes(keypair, in);
Copy link
Contributor

Choose a reason for hiding this comment

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

LGTM, this return isn't needed.
We could stick to the approach used in Zeth though and change the returned type to a snark:keypair and declare the keypair in the function. However, we would have some copy of the keypair when return.
TL;DR is: this change looks good to me but we have some slight inconsistency between similar functions in Zeth and Zecale, so that would be valuable to clear that out (and probably move these functions in a namespace like libzeth::server that could then be used on zecale as libzeth::server::load_keypair)

(see: https://github.com/clearmatics/zeth/blob/develop/prover_server/prover_server.cpp#L44-L54 for ref)

Copy link
Contributor

Choose a reason for hiding this comment

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

This is not strictly a blocker for the release, but better code factorization will mean, less code to maintain and less inconsistencies.

}

static void write_keypair(
Expand Down