You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -22,22 +21,60 @@ At least 2-Core (4-Thread) Intel i7/Xeon equivalent
22
21
At least 16GB RAM
23
22
At least 100GB SSD (Note: HDD will not work)
24
23
```
25
-
## Create a wallet on GuildNet
26
-
You will need a wallet.
27
-
To create a [guildnet wallet](https://wallet.openshards.io) go to: [https://wallet.openshards.io](https://wallet.openshards.io) be sure to record your wallet address and seed phrase (12 words)
28
-
_Tip: You may request 75,000 faucet from Near team for staking test._
29
-
30
-
## Install Near-Cli
31
-
NEAR CLI is a Node.js application that relies on near-api-js to generate secure keys, connect to the NEAR platform and send transactions to the network on your behalf.
32
-
_note that Node.js version 10+ is required to run NEAR CLI_
33
-
34
24
35
-
**Near-Cli doesn't need to be installed on the same machine as the validator, which is recommend to installed on a separate machine for increased security and performance. However it still can be installed on the same machine.**
25
+
You'll be working with two machines, a server for the validator node, and your personal machie/monitor machine to install near-cli, create the wallet, monitor and control the validator node.
Nearup automatically adds itself to PATH: **restart the terminal**, or issue the command: . ~/.profile. On each run, nearup self-updates to the latest version.
43
+
44
+
### Step 2. Choose a staking-pool AccountId
45
+
On the first run, nearup will ask you to enter a staking-pool AccountId, please choose a name for your staking-pool AccountId, it must end with ".stake.guildnet", e.g. *MyStakingPool.stake.guildnet*.
46
+
47
+
You should go to [https://near-guildnet.github.io/staking-pool-factory](https://near-guildnet.github.io/staking-pool-factory/) to check if the name is available. Don't create your staking-pool contract yet, just check if the name is available.
48
+
49
+
### Step 3. Start nearup guildnet
50
+
We recommand to use Officially Compiled Binary to launch a validator node, which is suitable to run on VPS. Then, input your staking pool ID in the prompt by this command:
51
+
```bash
52
+
nearup guildnet --nodocker
53
+
```
54
+
55
+
Check validator_key.json is generated for staking pool.
56
+
```bash
57
+
ls ~/.near/guildnet
58
+
validator_key.json node_key.json config.json data genesis.json
Check running status of validator node. If "V/" is showning up, your pool is selected in current validators list.
68
+
```bash
69
+
nearup logs -f
70
+
```
71
+
72
+
## Create a wallet on GuildNet
73
+
*On your personal machine:*
74
+
You will need a wallet.
75
+
To create a [guildnet wallet](https://wallet.openshards.io) go to: [https://wallet.openshards.io](https://wallet.openshards.io) be sure to record your wallet address and seed phrase (12 words)
76
+
_Tip: You may request 75,000 faucet from Near team for staking test._
77
+
41
78
#### Install Node Version 12.x and npm
42
79
Nodes.js and npm can be install by
43
80
```bash
@@ -59,12 +96,19 @@ npm -v
59
96
##### Alternative
60
97
If "n" is not working for you to upgrade node (node -v doesn't change) you can try [nvm](https://github.com/nvm-sh/nvm/blob/master/README.md) to manage node versions
61
98
62
-
### Install near-cli
99
+
## Install Near-Cli
100
+
*On your personal machine:*
101
+
NEAR CLI is a Node.js application that relies on near-api-js to generate secure keys, connect to the NEAR platform and send transactions to the network on your behalf.
102
+
_note that Node.js version 10+ is required to run NEAR CLI_
103
+
104
+
**Note: You don't need to install Near-Cli on the server. We reccomend to install near-cli on your personal machine or a separate machine for increased security and performance. However it still can be installed on the same machine.**
Nearup automatically adds itself to PATH: restart the terminal, or issue the command source ~/.profile. On each run, nearup self-updates to the latest version.
119
157
120
-
## Launch validator node
121
-
We recommand to use Officially Compiled Binary to launch a validator node, which is suitable to run on VPS.
122
-
Then, input your staking pool ID in the prompt by this command.
123
-
```bash
124
-
nearup guildnet --nodocker
125
-
```
126
-
Check validator_key.json is generated for staking pool.
127
-
```bash
128
-
ls ~/.near/guildnet
129
-
validator_key.json node_key.json config.json data genesis.json
130
-
```
131
-
Check running status of validator node. If "V/" is showning up, your pool is selected in current validators list.
132
-
```bash
133
-
nearup logs -f
134
-
```
158
+
## Create your staking pool
159
+
You need to setup a staking pool, the easiest way is to go back to [https://near-guildnet.github.io/staking-pool-factory/](https://near-guildnet.github.io/staking-pool-factory/) with the staking-pool AccountId you selected, and the **validator public_key** you got while starting nearup and complete the process to create the staking-pool contract.
135
160
136
-
##Create staking pool
137
-
You need to setup a staking pool which can be generated by create_staking_pool command.
138
-
Check public key from ~/.near/guildnet/validator_key.json
161
+
#### Alternative:
162
+
You can also setup a staking pool from the command line using the *create_staking_pool* method.
163
+
Check public key from ~/.near/guildnet/validator_key.json on your validator server:
0 commit comments