NKN MainNet v2.0.8 Release

We released a new mainnet version v2.0.8 at https://github.com/nknorg/nkn/releases. This version optimizes database operation when processing subscribe transaction. We recommend everyone to upgrade as soon as possible for better performance.

Starting from previous version v2.0.5, minimal Golang version required is 1.13. If you are running old 1-click node from DO/GCP/AWS, you can ssh into the machine, copy and paste this line to terminal to upgrade Golang:

curl https://gist.githubusercontent.com/yilunzhang/2f5edffc16c2b6a999c33cb1c13d6728/raw/4101eee4b5e4a1406accbdf3ddeb1dc40189c484/nkn-old-1-click-upgrade-golang.sh | sh

How to Upgrade

  • If you are using nkn-commercial or nknx fast deploy, you don’t need to do anything.
  • If you are using one-click on DO/AWS/Google Cloud, you just need to stop and restart and miner and it will upgrade automatically.
  • If you downloaded the release version, you just need to download it again at https://github.com/nknorg/nkn/releases , replace files and start nknd again
  • If you build from scratch, you just need to do the build again.
  • If you are using some scripts or tutorials that has auto-updater, then it should be automatic if the auto-updater is working properly.

We don’t recommend anyone to download the ChainDB snapshot manually, but if you really want or need, you can use https://nkn.org/ChainDB_pruned_latest.zip or https://nkn.org/ChainDB_pruned_latest.tar.gz for pruned ChainDB.

1 Like

Is golang needed on the server to run NKN-commercial node?

How to check which version of NKN node is running on server?

Golang is not needed for nkn-commercial.

nknx, nstatus or nknc info -s will all show nknd version.

Not even one of those commands worked on my NKN-commercial server. Ubuntu 20.04

Commercial will update itself then?

Do I have to make another ChainDB archive for faster distribution? after commercial updates?

Ah those are not command :joy:

nknx means https://nknx.org

nstatus means http://nstatus.org

Commercial will update itself (actually they already did, you will see your node running v2.0.7-1-g37bc which is the same as v2.0.8).

I don’t think you need ChainDB unless you need to deploy new nodes.

I already have ChainDB archive I made myself.

I want to know if I need to update it, aka get it again from a node that is already updated or is the old one still ok.

Yes my nodes have updated. Good

Old one is still OK, just a bit outdated. Because blockchain data is constantly being generated, it’s better to create a snapshot right before you deploy new nodes if you want to update it.

1 Like