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

fix all comments

This commit is contained in:
李婷婷 2020-06-10 00:50:10 +08:00
parent 62949301ac
commit 9c1da836f7
16 changed files with 24 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/src/beacon-chain.md
View File

@ -10,10 +10,9 @@ In traditional PoW, those that propose new blocks are called **_miners_**, where
## What it is Like to Be a Validator?
It is obvious that you must have enough computing power or a dedicated hardware in order to be a miner, but how about being a validator? Here is a breif overview:
It is obvious that you must have enough computing power or dedicated hardware in order to be a miner, but how about being a validator? Here is a brief overview:
1. A special smart contract named **_registration contract_** is deployed on the original Ethereum blockchain. Note that in this case, the new beacon chain and the original blockchain co-exists.
2. To "register" as a validator, you have to first deposit **_32 Etheres_** from your account to this smart contract.
1. A special smart contract named **_deposit contract_** is deployed on the original Ethereum blockchain. Note that in this case, the new beacon chain and the original blockchain co-exists.
2. To "register" as a validator, you have to first deposit **_32 Ether_** from your account to this smart contract.
3. Run the beacon node and wait for the network to sync before your validator is activated.
4. That's all! Remember to stay connected to the network, or you may lost your deposit. :P
4. That's all! Remember to stay connected to the network, or you may lose your deposit. :P

6
docs/src/contribute.md
View File

@ -1,7 +1,9 @@
# Contribute
Follow these steps to contribute to this book! <br>
We use a utility tool called mdBook to create online books from Markdown files.
Follow these steps to contribute to this book!
We use an utility tool called mdBook to create online books from Markdown files.
## Before You Start

6
docs/src/validator.md
View File

@ -35,13 +35,13 @@ make testnet0 # This will build Nimbus and all other dependencies
<img src="./img/connect_testnet.PNG" alt="" style="margin: 0 40 0 40"/>
7. The testnet should now be up and running. Then, you will be prompted to enter your private key of the account you want to deposit the 32 Etheres from. Find your private key from MetaMask as below:
7. The testnet should now be up and running. Then, you will be prompted to enter your private key of the account you want to deposit the 32 Ether from. Find your private key from MetaMask as below:
<img src="./img/export_pkey.PNG" alt="" width="200" style="margin: 0 40 0 40"/>
<img src="./img/enter_private_key.PNG" alt="" style="margin: 0 40 0 40"/>
8. Wait for a few seconds until you see your deposit has been sent:
8. Wait for a few seconds until you see that your deposit has been sent:
<img src="./img/deposit_sent.PNG" alt="" style="margin: 0 40 0 40"/>
@ -53,7 +53,7 @@ You can also get a brief estimate of the time remaining until your network gets
## Trouble Shooting
1. The directory that stores the blockchain data of the testnet is `build/data/testnet0` (replace `testnet0` with other testnet names). Delete this folder if you want to start over. For example, you can start over with a fresh storgae if you entered a wrong private key.
1. The directory that stores the blockchain data of the testnet is `build/data/testnet0` (replace `testnet0` with other testnet names). Delete this folder if you want to start over. For example, you can start over with a fresh storage if you entered a wrong private key.
2. Currently, you have to switch to the devel branch in order to run the validator node successfully.

2
vendor/nim-blscurve vendored

@ -1 +1 @@
Subproject commit 4f87e747d8c1310be5660d3e61674392206a91ea
Subproject commit 1a18d0dbea6f1f00409c660be58eb5206060cb3c

2
vendor/nim-chronicles vendored

@ -1 +1 @@
Subproject commit fc3f2d3755e035387ebcf20d87a45eb9dcefadbb
Subproject commit 3d7619b1f559c86b2ef026f386d6d872b9331c82

2
vendor/nim-chronos vendored

@ -1 +1 @@
Subproject commit bce0f878d16bea14395dc8944ff8dbdeffe33496
Subproject commit bedd1ded5edc3bfb6877f7025ca4b21f62492ffe

2
vendor/nim-confutils vendored

@ -1 +1 @@
Subproject commit 6e5d570490989c753d4645ba9173ef9358d302bb
Subproject commit 26667818be48d428892b26be9535c1f0a98d1510

2
vendor/nim-eth vendored

@ -1 +1 @@
Subproject commit d53cebcf5dd35728c27088d9c95923d7baad4ac4
Subproject commit 4e31a86533fcb29a40d05b6e497e9165f72f5218

2
vendor/nim-json-rpc vendored

@ -1 +1 @@
Subproject commit ecf49a06329f49f1993008b0ee08e3f3e13cc422
Subproject commit 271512c161706e08533690fdc8bbbbc54f1dc0ed

2
vendor/nim-json-serialization vendored

@ -1 +1 @@
Subproject commit aa51f6fed1715a91fd8b58072a1915422a133d4a
Subproject commit c478b7bbbab6ee298a25c29c7357783d94aaecaa

2
vendor/nim-libp2p vendored

@ -1 +1 @@
Subproject commit 7b6e1c06888a831d61d7019a07d2d59d5bd079ea
Subproject commit 130c64f33a493074a64d4e2af2ae57091f5a480e

2
vendor/nim-protobuf-serialization vendored

@ -1 +1 @@
Subproject commit 08c6db775f3daee35fee098c72c0e36b8ec57833
Subproject commit 879421b1216efb66aed5a7f4e14d02ff96db9123

2
vendor/nim-serialization vendored

@ -1 +1 @@
Subproject commit 501f94ad61ae22197d565ac39a00783a6e6f6faa
Subproject commit d8ca3daf3a788f357bf96b8e61b3ffce9a018ea2

2
vendor/nim-snappy vendored

@ -1 +1 @@
Subproject commit b4cd68e27a56dbda2a56d7b90e666b644cfd5be6
Subproject commit 676fa656d3a6f4e24691f3f48829c979b1b1bcdd

2
vendor/nim-stew vendored

@ -1 +1 @@
Subproject commit a99dafab420bcbbffee35e9bd847a9014eafaffe
Subproject commit bb2221ba8c8ea2d3fbbcfdb8d28796f8d3eff348

2
vendor/nim-testutils vendored

@ -1 +1 @@
Subproject commit fcc5aa3a532cf42f9f1074f29df36fd69b3d2920
Subproject commit 1601894ec1fd1c7095d405eb0c846cac212fb18f