Skip to content
This repository has been archived by the owner on Oct 19, 2022. It is now read-only.

Documentation Feature Request: Explain me how to "Generate a validator public / private key" when building with Bazel #82

Open
chrishobcroft opened this issue Nov 22, 2019 · 8 comments

Comments

@chrishobcroft
Copy link

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 and bazel build //beacon-chain:beacon-chain?

Screenshots

Screenshot from 2019-11-22 20-10-44

@har00ga
Copy link
Contributor

har00ga commented Nov 22, 2019

+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. 🙂

@chrishobcroft
Copy link
Author

Can anyone tell me how to do this, so that I can make progress with setting up a validator node?

@prestonvanloon
Copy link
Member

@chrishobcroft to generate the keys using bazel, you can run

bazel run //validator -- accounts create --keystore-path=$HOME/beacon-chain --password=changeme

@chrishobcroft
Copy link
Author

Cool, thanks @prestonvanloon that seems to have worked.

@chrishobcroft
Copy link
Author

So, following up on this, it also appears that step 4 assumes docker.

Can someone please tell me the command to run via bazel?

Screenshot from 2019-11-24 13-05-26

@prestonvanloon
Copy link
Member

Hey @chrishobcroft, it's basically the same idea.

Replace docker run ... with bazel run //beacon-chain --.

We should definitely offer instructions on building and running from source.

bazel run //beacon-chain -- --datadir=$HOME/beacon-chain --init-sync-no-verify
bazel run //validator -- --keystore-path=$HOME/beacon-chain --password=changeme

@har00ga
Copy link
Contributor

har00ga commented Nov 26, 2019

Implemented into the Gitbook: https://prysmaticlabs.gitbook.io/prysm/activating-a-validator

@chrishobcroft
Copy link
Author

Woop! 👍 🥇 💯

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants