-
Notifications
You must be signed in to change notification settings - Fork 109
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
Scheme configuration system and unchained randomness #816
Conversation
2ecc7e4
to
d260411
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.
Hey - great start. I think I made a lot of similar comments, so please excuse me if I'm being redundant. My main point here is that we should treat this PR as already adding a new protocol to drand, and not just a tweak. And we give a version flag to identify the logic with this new way of doing things. If we get that, then any further updates will be simpler because we can "just" create a new version flag. Obviously I'm not asking for the most generic thing already, but let's start to employ the right mindset to think about this: we are creating a new protocol version here.
Sorry for the large comments, I hope it's all right with you, and thanks for taking care of this <3
Go version update
9574eeb
to
95dca4d
Compare
95dca4d
to
a61736f
Compare
a61736f
to
bed664d
Compare
* create a scheme configuration system * refactor unchain randomness feature to use scheme configuration, making it more easy to set up * add a new CLI command to list scheme ids available
f1e0703
to
c8f78c1
Compare
No description provided.