mirror of
https://github.com/sigp/lighthouse.git
synced 2026-04-16 20:39:10 +00:00
Remove Pyrmont testnet (#2543)
## Issue Addressed N/A ## Proposed Changes Removes all configurations and hard-coded rules related to the deprecated Pyrmont testnet. ## Additional Info Pyrmont is deprecated/will be shut down after being used for scenario testing, this PR removes configurations related to it. Co-authored-by: Zachinquarantine <zachinquarantine@yahoo.com>
This commit is contained in:
@@ -110,7 +110,7 @@ You can run a Docker beacon node with the following command:
|
||||
$ docker run -p 9000:9000/tcp -p 9000:9000/udp -p 127.0.0.1:5052:5052 -v $HOME/.lighthouse:/root/.lighthouse sigp/lighthouse lighthouse --network mainnet beacon --http --http-address 0.0.0.0
|
||||
```
|
||||
|
||||
> To join the Pyrmont testnet, use `--network pyrmont` instead.
|
||||
> To join the Prater testnet, use `--network prater` instead.
|
||||
|
||||
> The `-p` and `-v` and values are described below.
|
||||
|
||||
|
||||
@@ -124,7 +124,7 @@ testnet configuration settings. Ensure that the network you wish to connect to
|
||||
is correct (the beacon node outputs the network it is connecting to in the
|
||||
initial boot-up log lines). On top of this, ensure that you are not using the
|
||||
same `datadir` as a previous network. I.e if you have been running the
|
||||
`pyrmont` testnet and are now trying to join a new testnet but using the same
|
||||
`prater` testnet and are now trying to join a new testnet but using the same
|
||||
`datadir` (the `datadir` is also printed out in the beacon node's logs on
|
||||
boot-up).
|
||||
|
||||
|
||||
@@ -42,9 +42,9 @@ items, starting at one easy-to-backup mnemonic and ending with multiple
|
||||
keypairs. Creating a single validator looks like this:
|
||||
|
||||
1. Create a **wallet** and record the **mnemonic**:
|
||||
- `lighthouse --network pyrmont account wallet create --name wally --password-file wally.pass`
|
||||
- `lighthouse --network prater account wallet create --name wally --password-file wally.pass`
|
||||
1. Create the voting and withdrawal **keystores** for one validator:
|
||||
- `lighthouse --network pyrmont account validator create --wallet-name wally --wallet-password wally.pass --count 1`
|
||||
- `lighthouse --network prater account validator create --wallet-name wally --wallet-password wally.pass --count 1`
|
||||
|
||||
|
||||
In step (1), we created a wallet in `~/.lighthouse/{network}/wallets` with the name
|
||||
|
||||
@@ -46,7 +46,7 @@ When using Lighthouse, the `--network` flag selects a network. E.g.,
|
||||
|
||||
- `lighthouse` (no flag): Mainnet.
|
||||
- `lighthouse --network mainnet`: Mainnet.
|
||||
- `lighthouse --network pyrmont`: Pyrmont (testnet).
|
||||
- `lighthouse --network prater`: Prater (testnet).
|
||||
|
||||
Using the correct `--network` flag is very important; using the wrong flag can
|
||||
result in penalties, slashings or lost deposits. As a rule of thumb, always
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
# Become a Testnet Validator
|
||||
|
||||
[mainnet-validator]: ./mainnet-validator.md
|
||||
[pyrmont-launchpad]: https://pyrmont.launchpad.ethereum.org/
|
||||
[prater-launchpad]: https://prater.launchpad.ethereum.org/
|
||||
|
||||
Joining an Eth2 testnet is a great way to get familiar with staking in Phase 0. All users should
|
||||
@@ -11,15 +10,12 @@ To join a testnet, you can follow the [Become an Eth2 Mainnet Validator][mainnet
|
||||
instructions but with a few differences:
|
||||
|
||||
1. Use the appropriate Eth2 launchpad website:
|
||||
- [Pyrmont][pyrmont-launchpad]
|
||||
- [Prater][prater-launchpad]
|
||||
1. Instead of `--network mainnet`, use the appropriate network flag:
|
||||
- `--network pyrmont`: Pyrmont.
|
||||
- `--network prater`: Prater.
|
||||
1. Use a Goerli Eth1 node instead of a mainnet one:
|
||||
- For Geth, this means using `geth --goerli --http`.
|
||||
1. Notice that Lighthouse will store its files in a different directory by default:
|
||||
- `~/.lighthouse/pyrmont`: Pyrmont.
|
||||
- `~/.lighthouse/prater`: Prater.
|
||||
|
||||
>
|
||||
|
||||
@@ -50,8 +50,7 @@ OPTIONS:
|
||||
The GWEI value of the deposit amount. Defaults to the minimum amount required for an active validator
|
||||
(MAX_EFFECTIVE_BALANCE)
|
||||
--network <network>
|
||||
Name of the Eth2 chain Lighthouse will sync and follow. [default: mainnet] [possible values: medalla,
|
||||
altona, spadina, pyrmont, mainnet, toledo]
|
||||
Name of the Eth2 chain Lighthouse will sync and follow. [default: mainnet] [possible values: prater, mainnet]
|
||||
--secrets-dir <SECRETS_DIR>
|
||||
The path where the validator keystore passwords will be stored. Defaults to ~/.lighthouse/{network}/secrets
|
||||
|
||||
@@ -75,7 +74,7 @@ The example assumes that the `wally` wallet was generated from the
|
||||
[wallet](./wallet-create.md) example.
|
||||
|
||||
```bash
|
||||
lighthouse --network pyrmont account validator create --wallet-name wally --wallet-password wally.pass --count 1
|
||||
lighthouse --network prater account validator create --wallet-name wally --wallet-password wally.pass --count 1
|
||||
```
|
||||
|
||||
This command will:
|
||||
@@ -86,6 +85,6 @@ This command will:
|
||||
- An encrypted keystore containing the validators voting keypair.
|
||||
- An `eth1_deposit_data.rlp` assuming the default deposit amount (`32 ETH`
|
||||
for most testnets and mainnet) which can be submitted to the deposit
|
||||
contract for the Pyrmont testnet. Other testnets can be set via the
|
||||
contract for the Prater testnet. Other testnets can be set via the
|
||||
`--network` CLI param.
|
||||
- Store a password to the validators voting keypair in `~/.lighthouse/{network}/secrets`.
|
||||
|
||||
@@ -39,13 +39,13 @@ The exit phrase is the following:
|
||||
|
||||
|
||||
|
||||
Below is an example for initiating a voluntary exit on the Pyrmont testnet.
|
||||
Below is an example for initiating a voluntary exit on the Prater testnet.
|
||||
|
||||
```
|
||||
$ lighthouse --network pyrmont account validator exit --keystore /path/to/keystore --beacon-node http://localhost:5052
|
||||
$ lighthouse --network prater account validator exit --keystore /path/to/keystore --beacon-node http://localhost:5052
|
||||
|
||||
Running account manager for pyrmont network
|
||||
validator-dir path: ~/.lighthouse/pyrmont/validators
|
||||
Running account manager for Prater network
|
||||
validator-dir path: ~/.lighthouse/prater/validators
|
||||
|
||||
Enter the keystore password for validator in 0xabcd
|
||||
|
||||
|
||||
@@ -59,11 +59,11 @@ OPTIONS:
|
||||
|
||||
## Example
|
||||
|
||||
Creates a new wallet named `wally` and saves it in `~/.lighthouse/pyrmont/wallets` with a randomly generated password saved
|
||||
Creates a new wallet named `wally` and saves it in `~/.lighthouse/prater/wallets` with a randomly generated password saved
|
||||
to `./wallet.pass`:
|
||||
|
||||
```bash
|
||||
lighthouse --network pyrmont account wallet create --name wally --password-file wally.pass
|
||||
lighthouse --network prater account wallet create --name wally --password-file wally.pass
|
||||
```
|
||||
|
||||
> Notes:
|
||||
|
||||
Reference in New Issue
Block a user