Generating your Elrond identity - Windows

[Iulian Pascalau 2]

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.

[zillabytes 13]

i got error on this file..

[Iulian Pascalau 2]

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

[zillabytes 13]

Also this error..

[josefcoap 6]

After creating the node identity, must be instructions to run the node. People that read this are asking me what they don't see node running after key generation 

[Sorin Pop 22]

2 hours ago, josefcoap said:

After creating the node identity, must be instructions to run the node. People that read this are asking me what they don't see node running after key generation 

Yep, generated pems are not copied in the node's config folder, I'm getting the same feedback and I was sending some people chasing green horses on the walls :)) Romanian saying

[josefcoap 6]

Yes, for me it's better to add those final 2 steps, copy them to config and how to execute the node. It seems obvious but people ask me on windows how to run it and stop it.

[Slave4E 0]

On 9/30/2019 at 6:47 AM, Iulian Pascalau said:

when i open a new git-bash window and use the commands start>run>cmd, another window opens?

 

 

[Jose 0]

How do I read the files to find out the node identity?

[alwin05 14]

Hi guys, please beware of changing tags/versions!

You can find the latest versions here:
elrond-go (BINTAG): https://github.com/ElrondNetwork/elrond-go/releases/latest (right now: v1.0.20)
elrond-config: https://github.com/ElrondNetwork/elrond-config/releases/latest (right now: dry-run-02-BoN)

Edited October 5, 2019 by alwin05
switched go and config