Edits
This commit is contained in:
yslcrypto
parent
eddb4fe250
commit
ba215706fa
|
|
@ -6,15 +6,13 @@ The easiest way to get your deposit in is to follow the Ethereum Foundation's la
|
|||
|
||||
**Mainnet**: [https://launchpad.ethereum.org/](https://launchpad.ethereum.org/)
|
||||
|
||||
> ⚠️ : If you are making a mainnet deposit make sure you verify that the deposit contract you are interacting with is the correct one.
|
||||
> ⚠️ If you are making a mainnet deposit make sure you verify that the deposit contract you are interacting with is the correct one.
|
||||
>
|
||||
> You should verify that the address is indeed: [0x00000000219ab540356cBB839Cbe05303d7705Fa](https://etherscan.io/address/0x00000000219ab540356cBB839Cbe05303d7705Fa)
|
||||
|
||||
You may notice that there have been considerable improvements to the launchpad process since the summer.
|
||||
|
||||
In particular, the Key Generation section is now much clearer, and you no longer have to install dependencies to get the command line app working.
|
||||
|
||||
|
||||
|
||||
We won't elaborate on each individual step here, since they are well explained on the site itself. However, there are two points of note:
|
||||
|
||||
|
|
@ -45,5 +43,3 @@ It's a good idea to bookmark this page.
|
|||
## Expected waiting time (the queue)
|
||||
Once you send off your transaction(s), your validator will be put in a queue based on deposit time. Getting through the queue may take a few hours or days (assuming the chain is finalising). No validators are accepted into the validator set while the chain isn't finalising.
|
||||
|
||||
*If you've made a mainnet deposit, your validator will be activated when mainnet launches, regardless of how many deposits are made before then: this will be **Dec 1st 2020, 12pm UTC***
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Network stats and monitoring
|
||||
|
||||
> ⚠️ This page concerns the [Pyrmont](https://pyrmont.launchpad.ethereum.org/) testnet. This page will be updated for mainnet very soon.
|
||||
> ⚠️ This page concerns the [Pyrmont](https://pyrmont.launchpad.ethereum.org/) testnet. It will be updated for mainnet soon.
|
||||
|
||||
eth2stats is a network monitoring suite for your beacon node + validator client.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ Note that in order to process incoming validator deposits from the eth1 chain, y
|
|||
|
||||
For example, you'll need at least another **290GB SSD** to run [geth fast sync](/eth1.md) on mainnet.
|
||||
|
||||
> **Tip:** It's possible to [tell a Raspberry Pi 4 to use a 64-bit kernel](/pi-guide.md#10-64-bit-kernel).
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Nimbus is an Ethereum 2.0 client focused on offering the best user experience possible for low-resource devices.
|
||||
|
||||
This book explains all the ways in which you can use Nimbus to either monitor the eth2 chain or become a fully-fledged validator.
|
||||
This book explains the ways in which you can use Nimbus to either monitor the eth2 chain or become a fully-fledged validator.
|
||||
|
||||
> The reality is that we are very early in the eth2 validating life cycle. Validating is not for everyone yet, and it comes with both risks and responsibilities. It isn't a particularly easy way to make money. You'll need to put effort into updating your software, researching hard-forks, having a robust setup... . As such, you should only stake if you are genuinely interested in securing the protocol.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Troubleshooting
|
||||
|
||||
> ⚠️ This page concerns the Pyrmont testnet. If you have made a mainnet deposit, you do not need to connect to eth2 quite yet. Mainnet [Genesis](https://hackmd.io/@benjaminion/genesis) date has been set to [December 1st](https://blog.ethereum.org/2020/11/04/eth2-quick-update-no-19/). This page will be updated nearer the time.
|
||||
> ⚠️ This page concerns the Pyrmont testnet. If you're running mainnet, replace `pyrmont` with `mainnet` in the commands below.
|
||||
|
||||
|
||||
As it stands, we are continuously making improvements to both stability and memory usage. So please make sure you keep your client up to date! This means restarting your node and updating your software regularly from the `master` branch. If you can't find a solution to your problem here, feel free to hit us up on our [discord](https://discord.com/invite/XRxWahP)!
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Perform a voluntary exit
|
||||
|
||||
> ⚠️ : Voluntary exits are **irreversible**. You won't be able to validate again with the same key. And you won't be able to withdraw your stake until the Eth1 and Eth2 merge. *Note that voluntary exits won't be processed if the chain isn't finalising.*
|
||||
> ⚠️ Voluntary exits are **irreversible**. You won't be able to validate again with the same key. And you won't be able to withdraw your stake until the Eth1 and Eth2 merge. *Note that voluntary exits won't be processed if the chain isn't finalising.*
|
||||
|
||||
To perform a voluntary exit, with your beacon node running, run:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue