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

"drand get private" does not say who it contacted #93

Closed
jeffallen opened this issue Nov 1, 2018 · 1 comment
Closed

"drand get private" does not say who it contacted #93

jeffallen opened this issue Nov 1, 2018 · 1 comment
Labels
ux Area: UX wont-fix Status: Won't fix

Comments

@jeffallen
Copy link
Contributor

It takes the --nodes whitespace separated list. And also a group file to know the public keys of the nodes.

It returns:

{
    "Randomness": "d15e24aa8b0f1c20df0ef5e005c4b607f9448d420d550a1fb6e3bd768640b1ab"
}

I think there should be a "Node" in there, to tell me which server it ended up getting data from.

And I'd like, if --nodes is empty, that it defaults to all nodes in the group file.

And I'd like that items from --nodes are tried in a random permutation order.

With all those changes, then repeated calls to "drand get private" will talk to all the servers in the network.

Another possibility: an -all option, that causes each of the servers in the --nodes option to be tried. Then I can use "drand get private --all" to try talking to each of the servers and see which ones work.

@yiannisbot yiannisbot added the P3 label Sep 16, 2021
@github-actions github-actions bot removed the P3 label Mar 21, 2022
@AnomalRoil AnomalRoil added the ux Area: UX label Mar 21, 2022
@AnomalRoil AnomalRoil added the wont-fix Status: Won't fix label Sep 13, 2022
@AnomalRoil
Copy link
Member

Drand is really about public distributed randomness, so we are not supporting private randomness anymore, I'm afraid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ux Area: UX wont-fix Status: Won't fix
Projects
None yet
Development

No branches or pull requests

4 participants