Live update: NKN mining software (1-click, GUI, guides, video)

Regarding 1-click images on cloud platforms (right now):

  • DO: existing machines on v0.8 can auto-update; fresh install see below instruction
  • GCP: existing machines on v0.8 can auto-update; fresh install see below instruction
  • AWS: existing machines on v0.8 can auto-update; fresh install see below instruction

Are you updating cloud images to mainnet v1.0?
Yes! We are submitting new 1-click images to all the three platforms, but it might take a couple of days to get approved and become available.

Regarding mainnet mining documentation and guides

  • Allen from our team is updating all documentation.
  • Main changes are two: config.dat change to config.json; how to use BeneficiaryAddress which is optional but recommended
  • You can help! We encourage community member to create step-by-step video guides to share with other newcomer miners. We will pick one of the best video for each platform, and provide NKN award (token or NKN brand merchandise)

Regarding GUI 1-click on local machine (Windows/Mac OS/Linux)

  • Still under development, and we will provide estimated release time at a later time

Essential tools for mainnet

If you do a fresh new install of 1-click on DO, GCP or AWS, and the NKN software is not working (by checking IP address in https://explorer.nknx.org/ips/), please log into your machine and do the following one line which will update your Upgrade Script and reboot your machine:

sudo curl https://raw.githubusercontent.com/nknorg/nkn-cloud-image/master/scripts/launch_node.sh > /tmp/launch_node.sh && sudo mv /tmp/launch_node.sh /home/nkn/launch_node.sh && sudo chown nkn:nkn /home/nkn/launch_node.sh && sudo chmod +x /home/nkn/launch_node.sh && sudo service supervisor stop && sudo service supervisor start

It takes a bit time (because it need to download the latest source code, compile them, create wallet, sync up to latest blockchain, and more), but we have tested it works on all three cloud platforms.

1 Like

Yesterday, I did a short video to my friends to update from Testnet to Mainnet.
Maybe like it to somebody too…

2 Likes

how is the supervisor.service file created? could you give relevant context here? or it is not 1-click actually.

1 Like

Can I do the DO one click installation and then update to the mainnet or do I need to wait for the new documentation? Where would I find this documentation?

Online Documents in Medium for DO, GCP, and AWS have been updated.

You can do the DO one click. After it has finished being deployed, you will need to login to the console and issue the script provided above which will update the Upgrade script and reboot the machine. Please give it some time after reboot to make sure all actions are completed for the upgrade and setup.

Hi Everyone,

I’m new here - and yesterday, I just tried running the NKN node on 4 VPS (running CentOS7)
I downloaded the nknd and nknc binary from the official github, copied the sample config.json (entered a beneficiary wallet address) and started the nknd daemon.

Checking the log files - I get messages like the one below:

2019/07/05 17:11:27.713406 [INFO ] GID 481509, Start saving blocks accepted during sync
2019/07/05 17:11:27.715401 [INFO ] GID 481509, # current block height: 22023, block hash: 0f77cfb37bb44e1b21ab0da501a6886c4353bc43bb5dbff36e62d7402f7ef213
2019/07/05 17:11:27.715529 [INFO ] GID 481509, Saved 1 blocks accepted during sync
2019/07/05 17:11:27.715637 [INFO ] GID 481509, Set min verifiable height to 22027
2019/07/05 17:11:27.715716 [INFO ] GID 481509, Set sync state to PERSIST_FINISHED
2019/07/05 17:11:27.771194 [ERROR] GID 362, Get next block signer error: timestamp 1562361087 is earlier than previous block timestamp 1562378617
2019/07/05 17:11:28.271720 [ERROR] GID 362, Get next block signer error: timestamp 1562361088 is earlier than previous block timestamp 1562378617
2019/07/05 17:11:28.772211 [ERROR] GID 362, Get next block signer error: timestamp 1562361088 is earlier than previous block timestamp 1562378617
2019/07/05 17:11:29.272774 [ERROR] GID 362, Get next block signer error: timestamp 1562361089 is earlier than previous block timestamp 1562378617
2019/07/05 17:11:29.357297 [INFO ] GID 361, Change expected block height to 22025
2019/07/05 17:11:30.980343 [WARN ] GID 481417, Decrypt message from <180.125.115.48:32666> error: cannot decrypt message: no shared key yet
2019/07/05 17:11:30.999485 [WARN ] GID 481426, Remote node <180.125.115.48:32666> stops because of error: Get node error: Wait for reply timeout
2019/07/05 17:11:34.935608 [WARN ] GID 447518, Ping c[email protected]tcp://221.225.190.137:30001<221.225.190.137:46883> error: Wait for reply timeout

Is it normal? Esp the one about “error: cannot decrypt message: no shared key yet”

Do we need to download a shared key from somewhere?
(each of my VPS has its own wallet.json, and the config.json all points to a beneficiary wallet address)

Also, do I need to set a specific timezone on my VPS to address the ‘earlier timestamp’ error?

Many thanks!

Welcome to the party!

error: cannot decrypt message: no shared key yet is normal, however, Get next block signer error: timestamp xxx is earlier than previous block timestamp xxx is NOT normal, it means your node’s local time is wrong (regardless of timezone, any timezone should work as long as time in that timezone is correct). You would definitely want to fix that, otherwise this node will not be able to earn any mining reward…

Our NKN 1-click full node software on @digitalocean marketplace has been updated to v1.0 #Mainnet. Tested fully working, took about 10 minutes to fully sync, with BeneficiaryAddr configured during droplet creation. Now you can launch an army of droplets in a few clicks!

Our $NKN 1-click full node software on @GCP marketplace has been updated to v1.1 #Mainnet. Tested fully working, took about 10 minutes to fully sync. BeneficiaryAddr can be configured in command line after node is running. Guide here:

Thanks YiLun.
The binary that I had downloaded was 1.0.1b-beta - I will try the current/latest one (1.0.2-beta).

I read that I have to create a new wallet for each node that runs the ‘nknd’ daemon.
But I can specify the ‘beneficiary wallet’ address in the ‘config.json’ file for each of these 3 nodes.

Question - in this scenario, where each of my 3 VPS has its own wallet, but all pointing to the same beneficiary wallet, is it correct to say that all rewards/mined from my 3 nodes will go to the beneficiary wallet?

And to backup my wallet, I only need to backup the ‘beneficiary wallet’ and not the individual wallet on my VPSes?

Thanks!

Question - in this scenario, where each of my 3 VPS has its own wallet, but all pointing to the same beneficiary wallet, is it correct to say that all rewards/mined from my 3 nodes will go to the beneficiary wallet?

Yes that’s right.

And to backup my wallet, I only need to backup the ‘beneficiary wallet’ and not the individual wallet on my VPSes?

Yes, that’s right, unless there are tokens in those wallets on VPS.

1 Like