Iulian Pascalau

The setup guide is available here: https://docs.elrond.com/start-a-validator-node/start-the-network If you are running under Windows or Linux, you might want to try our scripts: https://github.com/ElrondNetwork/elrond-go-scripts

yes, of course! This should have been copy-pasted from docs.elrond.com. Good catch, will fix!

Step 1: install & configure go: The installation of go should proceed as shown in official golang installation guide https://golang.org/doc/install . In order to run the node, minimum golang version should be 1.12.4. Step 2: clone the repository and build the binaries: The main branch that will be used is the master branch. Alternatively, an older release tag can be used. mkdir -p $HOME/src/github.com/ElrondNetwork cd $HOME/src/github.com/ElrondNetwork git clone https://github.com/ElrondNetwork/elrond-go cd elrond-go && git checkout tags/v1.0.20 git pull GO111MODULE=on go mod vendor cd cmd/node && go build -i -v -ldflags="-X main.appVersion=$(git describe --tags --long --dirty)" Step 3: creating the node’s identity: In order to be registered in the Elrond Network, a node must possess 2 types of (secret key, public key) pairs. One is used to identify the node’s credential used to generate transactions (having the sender field its account address) and the other is used in the process of the block signing. Please note that this is a preliminary mechanism, in the next releases the first (private, public key) pair will be dropped when the staking mechanism will be fully implemented. To build and run the keygenerator, the following commands will need to be run: cd $HOME/src/github.com/ElrondNetwork/elrond-go/cmd/keygenerator go build ./keygenerator Step 4: finding out node’s identity: Both .pem files generated in keygenerator directory have the same structure just like in the snippet bellow: -----BEGIN PRIVATE KEY for c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534----- MzdmMGU0MmU4MZDBl0OBkYjk0GZlMYlMTQ5zM0MTViOzA2ODFmZTEzRlMjGIwMjd NmQ5ODM1NmYxMzY4N2MwYg== -----END PRIVATE KEY for c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534----- Note that the public key is the text right after "-----BEGIN PRIVATE KEY for ", so in this case c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534 initialNodesSk.pem will contain a public key with a length of 256 hexadecimal characters. The public key from initialBalancesSk.pem is 64 hexadecimal characters long Please use the information in the above mentioned files to fill in this registration form.

Step 1: install & configure go: The installation of go should proceed as shown in official golang installation guide https://golang.org/doc/install . In order to run the node, minimum golang version should be 1.12.4. Step 2: install git: The installation of git should proceed as shown in official git installation guide https://git-scm.com/download/win . After git has been installed, a new bash command window will appear that has to be closed. The following steps should be carried in a new cmd window: start > run > cmd. Step 3: clone the repository and build the binaries: The main branch that will be used is the master branch. Alternatively, an older release tag can be used. SET BINTAG=v1.0.20 mkdir %GOPATH%\src\github.com\ElrondNetwork cd %GOPATH%\src\github.com\ElrondNetwork git clone https://github.com/ElrondNetwork/elrond-go cd elrond-go git checkout --force %BINTAG% git pull cd cmd\node SET GO111MODULE=on go mod vendor go build -i -v -ldflags="-X main.appVersion=%BINTAG%" Step 4: creating the node’s identity: In order to be registered in the Elrond Network, a node must possess 2 types of (secret key, public key) pairs. One is used to identify the node’s credential used to generate transactions (having the sender field its account address) and the other is used in the process of the block signing. Please note that this is a preliminary mechanism, in the next releases the first (private, public key) pair will be dropped when the staking mechanism will be fully implemented. To build and run the keygenerator, the following commands will need to be run: cd .. cd keygenerator go build keygenerator.exe Step 5: finding out node’s identity: Both .pem files generated in keygenerator directory have the same structure just like in the snippet bellow: -----BEGIN PRIVATE KEY for c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534----- MzdmMGU0MmU4MZDBl0OBkYjk0GZlMYlMTQ5zM0MTViOzA2ODFmZTEzRlMjGIwMjd NmQ5ODM1NmYxMzY4N2MwYg== -----END PRIVATE KEY for c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534----- Note that the public key is the text right after "-----BEGIN PRIVATE KEY for ", so in this case c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534 initialNodesSk.pem will contain a public key with a length of 256 hexadecimal characters. The public key from initialBalancesSk.pem is 64 hexadecimal characters long Please use the information in the above mentioned files to fill in this registration form.

Step 1: install & configure go: The installation of go should proceed as shown in official golang installation guide https://golang.org/doc/install . In order to run the node, minimum golang version should be 1.12.4. Step 2: clone the repository and build the binaries: The main branch that will be used is the master branch. Alternatively, an older release tag can be used. mkdir go && echo "export GOPATH=$HOME/go" >> ~/.profile source ~/.profile mkdir -p $GOPATH/src/github.com/ElrondNetwork cd $GOPATH/src/github.com/ElrondNetwork git clone https://github.com/ElrondNetwork/elrond-go cd elrond-go && git checkout --force tags/v1.0.20 git pull GO111MODULE=on go mod vendor cd cmd/node && go build -i -v -ldflags="-X main.appVersion=$(git describe --tags --long --dirty)" Step 3: creating the node’s identity: In order to be registered in the Elrond Network, a node must possess 2 types of (secret key, public key) pairs. One is used to identify the node’s credential used to generate transactions (having the sender field its account address) and the other is used in the process of the block signing. Please note that this is a preliminary mechanism, in the next releases the first (private, public key) pair will be dropped when the staking mechanism will be fully implemented. To build and run the keygenerator, the following commands will need to be run: cd ../keygenerator go build ./keygenerator Step 4: finding out node’s identity: Both .pem files generated in keygenerator directory have the same structure just like in the snippet bellow: -----BEGIN PRIVATE KEY for c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534----- MzdmMGU0MmU4MZDBl0OBkYjk0GZlMYlMTQ5zM0MTViOzA2ODFmZTEzRlMjGIwMjd NmQ5ODM1NmYxMzY4N2MwYg== -----END PRIVATE KEY for c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534----- Note that the public key is the text right after "-----BEGIN PRIVATE KEY for ", so in this case c751005bdd64a7f1a4dfd56937af732907c4ee3a405b05ea43dd84682285a534 initialNodesSk.pem will contain a public key with a length of 256 hexadecimal characters. The public key from initialBalancesSk.pem is 64 hexadecimal characters long Please use the information in the above mentioned files to fill in this registration form.