This repository has been archived by the owner on Oct 19, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Documentation Feature Request: Explain me how to "Generate a validator public / private key" when building with Bazel #82
Comments
+1 to this, definitely worth implementing. The Gitbook will also be featuring an 'Activating a Validator' section early next week, and this information would be good to include with that update. 🙂 |
Can anyone tell me how to do this, so that I can make progress with setting up a validator node? |
@chrishobcroft to generate the keys using bazel, you can run
|
Cool, thanks @prestonvanloon that seems to have worked. |
Hey @chrishobcroft, it's basically the same idea. Replace We should definitely offer instructions on building and running from source.
|
Implemented into the Gitbook: https://prysmaticlabs.gitbook.io/prysm/activating-a-validator |
Woop! 👍 🥇 💯 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Explanation of the problem:
In the process of setting up as a validator, step 3 is to "Generate a validator public / private key"
The site currently explains what docker commands to run in order to do this (see screenshot below).
I am following the method which involves building from source using bazel, and there is no explanation for how to generate a validator public / private key via this approach.
Proposed solution
To include an explanation for how to generate a validator public / private key without using
docker
.Perhaps there is some bazel command that can be run, assuming that I have already run
bazel build //validator:validator
andbazel build //beacon-chain:beacon-chain
?Screenshots
The text was updated successfully, but these errors were encountered: