status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

edit networking, remove references to pyrmont (#3027)

This commit is contained in:
sacha 2021-10-25 19:40:29 +02:00 committed by GitHub
parent 7c49d657a6
commit 07e4dd5f23
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 4 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/the_nimbus_book/src/beacon-node-systemd.md
View File

@ -45,7 +45,7 @@ Where you should replace:
> **N.B.** If you're running Nimbus on a Pi, your `<BASE-DIRECTORY>` is `/home/pi/nimbus-eth2/` and your `<USERNAME>` is `pi` > **N.B.** If you're running Nimbus on a Pi, your `<BASE-DIRECTORY>` is `/home/pi/nimbus-eth2/` and your `<USERNAME>` is `pi`
> If you want to run on mainnet, simply replace all instances of `prater` with `mainnet`. If you wish to run on `pyrmont`, replace all instances of `prater` with `pyrmont`. > If you want to run on mainnet, simply replace all instances of `prater` with `mainnet`.
### 2. Notify systemd of the newly added service ### 2. Notify systemd of the newly added service

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

@ -18,7 +18,7 @@ The `unstable` branch contains features and bugfixes that are actively being tes
* Features and bugfixes are generally pushed to individual branches, each with their own pull request against the `unstable` branch. * Features and bugfixes are generally pushed to individual branches, each with their own pull request against the `unstable` branch.
* Once the branch has been reviewed and passed CI, the developer or reviewer merges the branch to `unstable`. * Once the branch has been reviewed and passed CI, the developer or reviewer merges the branch to `unstable`.
* The `unstable` branch is regularly deployed to the Nimbus prater and pyrmont fleets where additional testing happens. * The `unstable` branch is regularly deployed to the Nimbus Prater fleet where additional testing happens.
### Testing ### Testing

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

@ -46,7 +46,7 @@ If there are no `dir=in` chronosstreams , incoming connections are not working.
> **N.B** you need to run the client with the `--metrics` option enabled in order for this to work > **N.B** you need to run the client with the `--metrics` option enabled in order for this to work
## Pass the extip option ## Pass the extip option
If you have a static public IP address, use the `--nat:extip:$EXT_IP_ADDRESS` option to pass it to the client, where `$EXT_IP_ADDRESS` is your public IP. For example, if your public IP address is `1.2.3.4`, you'd run: If you have a static public IP address, use the `--nat:extip:$EXT_IP_ADDRESS` option to pass it to the client, where `$EXT_IP_ADDRESS` is your public IP (see [here](./networking.md#determine-your-public-ip-address) for how to determine your public IP address). For example, if your public IP address is `1.2.3.4`, you'd run:
``` ```
./run-prater-beacon-node.sh --nat:extip:1.2.3.4 ./run-prater-beacon-node.sh --nat:extip:1.2.3.4

7
docs/the_nimbus_book/src/prater.md
View File

@ -16,17 +16,12 @@
</br> </br>
</br> </br>
The latest Eth2 testnet, [Prater](https://twitter.com/Butta_eth/status/1374383003011452937), is now open to the public. The latest Eth2 testnet, [Prater](https://twitter.com/Butta_eth/status/1374383003011452937), is open to the public.
Prater's objective is to ensure that the network remains stable under a higher load than we've seen so far on mainnet -- the genesis count for Prater was 210k (almost double the size of the Beacon Chain Mainnet). Prater's objective is to ensure that the network remains stable under a higher load than we've seen so far on mainnet -- the genesis count for Prater was 210k (almost double the size of the Beacon Chain Mainnet).
To elaborate a little, we want to make sure that the network is able to function properly with considerably more validators: increasing the number of validators increases the state size, increases the amount of work done to process that state, and increases the number of messages being gossipped on the network; blocks also become fuller, which explores a new kind of constraint as clients need to optimise better for attestation inclusion. To elaborate a little, we want to make sure that the network is able to function properly with considerably more validators: increasing the number of validators increases the state size, increases the amount of work done to process that state, and increases the number of messages being gossipped on the network; blocks also become fuller, which explores a new kind of constraint as clients need to optimise better for attestation inclusion.
Both Pyrmont and Prater will co-exist for the foreseeable future (we will be testing the [Altair](https://github.com/ethereum/consensus-specs/releases/tag/v1.1.2) fork on Pyrmont, for example). However, in the medium term we expect Prater to replace Pyrmont.
If you're already validating with Nimbus, you should start thinking about transitioning from Pyrmont to Prater at some point over the next few weeks. However, there is no immediate rush, so please do so at your own convenience. If you're new to Nimbus then you could try starting directly with Prater.

7
docs/the_nimbus_book/src/voluntary-exit.md
View File

@ -4,13 +4,6 @@
To perform a voluntary exit, make sure your beacon node is running with the `--rpc`option enabled (e.g. `./run-mainnet-beacon-node.sh --rpc`), then run: To perform a voluntary exit, make sure your beacon node is running with the `--rpc`option enabled (e.g. `./run-mainnet-beacon-node.sh --rpc`), then run:
**Pyrmont**
```
build/nimbus_beacon_node deposits exit \
--validator=<VALIDATOR_PUBLIC_KEY> \
--data-dir=build/data/shared_pyrmont_0
```
**Prater** **Prater**