status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-11 06:46:10 +00:00
Code Issues Projects Releases Wiki Activity

change all :s to s (#4403)

Browse Source 
* change all :s to s

* edit one more :s
This commit is contained in:
cheny0 2022-12-09 17:42:52 +08:00 committed by GitHub
parent 1e2f9b2fb8
commit 6b5682df70
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/the_nimbus_book/src/eth1.md
View File

@ -81,7 +81,7 @@ It is safe to start the beacon node even if the execution client is not yet full
### 3. Pass the URL and JWT secret to Nimbus
The `--web3-url` option informs the beacon node how to connect to the execution client - both `http://` and `ws://` URL:s are supported.
The `--web3-url` option informs the beacon node how to connect to the execution client - both `http://` and `ws://` URLs are supported.
Once started, the execution client will create a file containing a JWT secret token. The token file is needed for Nimbus to authenticate itself with the execution client and perform trusted operations. You will need to pass the path to the token file to Nimbus together with the web3 URL.
@ -100,7 +100,7 @@ Once started, the execution client will create a file containing a JWT secret to
```
!!! tip "Multiple execution clients"
You can pass one or more `--web3-url` parameters to the node as long as they share JWT secret. Any additional web3 url:s will be used for backup, should the first one become unavailable:
You can pass one or more `--web3-url` parameters to the node as long as they share JWT secret. Any additional web3 URLs will be used for backup, should the first one become unavailable:
```sh
./run-mainnet-beacon-node.sh \

2
docs/the_nimbus_book/src/index.md
View File

@ -15,7 +15,7 @@ This book describes the consensus layer client, [`nimbus-eth2`](https://github.c
* [Beacon node](./quick-start.md) with integrated validator client, slashing protection and doppelganger detection
* Stand-alone [validator client](./validator-client.md) with [sentry node](./validator-client.md#sentry-node-setup) support
* Fast [Beacon](./rest-api.md) and [KeyManager](./keymanager-api.md) API:s with extensions
* Fast [Beacon](./rest-api.md) and [KeyManager](./keymanager-api.md) APIs with extensions
* [Web3Signer](https://docs.web3signer.consensys.net/en/latest/) remote signing
* [Validator monitoring](./validator-monitor.md) and [performance analysis](./attestation-performance.md) tooling
* [External block builder](./external-block-builder.md) (PBS / mev-boost) support with execution client fallback