NKN MainNet v2.0.9 Release

Research & Dev Releases
#1

We released a new mainnet version v2.0.9 at https://github.com/nknorg/nkn/releases. This version will prevent very long sigchain to gain additional advantage caused by sigchain bit shift. The new change is consensus incompatible and will be effective starting from block height 2543000. Please upgrade before this height to keep node running normally.

  • Add length limit for sigchain bit shift
  • Fix http json rpc request body not closed
  • Init log module in nknc to prevent panic

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.

Nodes on Amazon do not find blocks for the second day! 3000 nodes 0 blocks!
#2

Please use nstatus.org to check your node status and software version.

nknx.org is suspending all node updates, so the information there will be out of date.

As alternative for miners with a lot of nodes, you can also run your own dashboard:

#3

Here is the cheating address, the reward is still unfair.



2 Likes
#4

that’s really crazy, to get 23600 nkns (NKNGUHw4vfQkYJjbXtW4SpXEaAcwy1CoZgc6) in just 8 days. how many servers or IPs do you need there?

#5

Assuming (or estimating) that you generate 13.75 NKN per block per month, in 8 days it would be 3.66 NKN, so to get 23600 NKN in 8 days you would need approximately 6,500 nodes lol

#6

Our core developer team is continuously monitoring the situation and finding solutions. Please be assured that mining fairness is the most important goal of NKN.

1 Like
#7

Those are known to be some of the largest miners in the community, each with thousands of nodes using the same beneficiary address. We have confirmed this in our crawler data.