cerc-io/lighthouse
10
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Correct book links (#1338)

Browse Source 
* Correct book links

* Add count to validator creation

* Correct more links
This commit is contained in:
Age Manning 2020-07-07 17:28:59 +10:00 committed by GitHub
parent f500b24242
commit ac2ce2ba6b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
book/src/become-a-validator-source.md
View File

@ -72,9 +72,9 @@ slot: 16835, ...
## 4. Generate your validator key
First, [create a wallet](./wallet-create) that can be used to generate
First, [create a wallet](./wallet-create.md) that can be used to generate
validator keys. Then, from that wallet [create a
validator](./validator-create). A two-step example follows:
validator](./validator-create.md). A two-step example follows:
### 4.1 Create a Wallet
@ -117,7 +117,7 @@ used to restore your validator if there is a data loss.
Create a validator from the wallet with:
```bash
lighthouse account validator create --wallet-name my-validators --wallet-passphrase my-validators.pass
lighthouse account validator create --wallet-name my-validators --wallet-passphrase my-validators.pass --count 1
```
The output will look like this:

4
book/src/faq.md
View File

@ -46,13 +46,13 @@ period. In times of very, very severe network issues, the network may even fail
to vote in new Eth1 blocks, stopping all new validator deposits!
> Note: you can see the list of validators included in the beacon chain using
> our REST API: [/beacon/validators/all](./http_beacon.md#beaconvalidatorsall)
> our REST API: [/beacon/validators/all](./http/beacon.md#beaconvalidatorsall)
### 2. Waiting for a validator to be activated
If a validator has provided an invalid public key or signature, they will
_never_ be activated or even show up in
[/beacon/validators/all](https://lighthouse-book.sigmaprime.io/http_beacon.html#beaconvalidatorsall).
[/beacon/validators/all](./http/beacon.html#beaconvalidatorsall).
They will simply be forgotten by the beacon chain! But, if those parameters were
correct, once the Eth1 delays have elapsed and the validator appears in the
beacon chain, there's _another_ delay before the validator becomes "active"