From 86bbf9970672dd6653a6479ce7c2676a793970da Mon Sep 17 00:00:00 2001 From: Raul Jordan Date: Wed, 3 Oct 2018 15:33:29 -0400 Subject: [PATCH] Update README.md (#615) --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2428ed4ffd..0763cd49b5 100644 --- a/README.md +++ b/README.md @@ -130,6 +130,7 @@ With the binary executable: ``` ./validator \ --beacon-rpc-provider http://localhost:4000 \ + --datadir /path/to/uniquevalidatordatadir \ --pubkey CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC ``` @@ -138,13 +139,14 @@ With Bazel: ``` bazel run //validator --\ --beacon-rpc-provider http://localhost:4000 \ + --datadir /path/to/uniquevalidatordatadir \ --pubkey CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC ``` This will connect you to your running beacon node and listen for shard/slot assignments! The beacon node will update you at every cycle transition and shuffle your validator into different shards and slots in order to vote on or propose beacon blocks. -if you want to run multiple validator clients, each one needs to have its own data directory where it will persist information, so create a new one each time and pass it into the validator command with the flag `--datadir /path/to/datadir`. +if you want to run multiple validator clients, **each one needs to have its own data directory where it will persist information, so create a new one each time** and pass it into the validator command with the flag `--datadir /path/to/validatordatadir`. ## Running Via Docker