-
Notifications
You must be signed in to change notification settings - Fork 27
Zeth client show parameters #263
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
Conversation
@@ -515,16 +515,17 @@ def mix( | |||
self, | |||
mix_params: contracts.MixParameters, | |||
sender_eth_address: str, | |||
pub_value: Optional[EtherValue] = None, | |||
sender_eth_private_key: Optional[bytes], |
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.
That's a general note, not related to this PR in particular.
As a general rule of thumb, passing secret keys/data around is not desirable (at all). That's something to be careful with - we want the "message to come to the sk" (not the other way around) (I comment here because I can see that we pass the private key to functions here)
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.
Sure. We can iterate in a future pass.
f614cb7
to
aa3c7b5
Compare
LGTM |
Make mpc server tests more verbose (depends on #263)
mix --show-parameters
flag and related refactor.fix for small output inconsistency when using
mix --wait