NKN MainNet v1.0.1b-beta Release

Research & Dev Releases
#1

We released a new version v1.0.1b-beta. This version disables register name transaction for now due to the recent abuse. It will come back later when there is a proper economic mechanism. We also enhanced txn verification when proposing block and remove invalid txn from pool.

This is an incompatible upgrade, so upgrade is required.

  • If you are using one-click on DO/AWS/Google Cloud or one-click GUI, you don’t need to do anything.
  • If you downloaded the release version, you just need to download it again https://github.com/nknorg/nkn/releases , replace your nknd and nknc and run 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-updator, then it should be automatic if the auto-updator is working properly.

The old version is deprecated to accelerate the upgrade process.

You probably don’t need to download the ChainDB snapshot manually, but if you really want or need, you can use https://nkn.org/ChainDB_latest.zip.

To update to the new version, please stop your nknd, rebuild (or download the latest binary from https://github.com/nknorg/nkn/releases ), and then restart. If you are using the GUI miner or auto-updater, then you just need to stop and restart and miner and it will upgrade automatically.

1 Like
#2

I was hoping to set up my node tonight, so glad this has happened today and not tomorrow. Good work on patching the name issues.

#3
#4

I have a problem with drops on DigitalOcean. 10 drops work, but not a single token I have not yet accrued. This is not my first drops on the testnet on DigitalOcean I have already set up nodes! And with nodes at more closely, everything was fine!


img-2019-07-07-09-53-38 img-2019-07-07-09-54-47

#5

Hi,

Have you checked your node status on https://explorer.nknx.org/ips/ ?
It should look something like this:

"relayMessageCount": [a non-zero number]
"syncState": "PERSIST_FINISHED"

Also, we can no longer simply clone droplet on DO.

  • In Mainnet, each node MUST have a unique wallet and cannot share the same wallet with other nodes, otherwise the node will not be able to join. It is recommended to use BeneficiaryAddr (in config.json) for both better security and convenience (if you run multiple nodes).
#6

I understand correctly, for each Drop needs to be your wallet! And Snapshots for the propagation of the GBR is already impossible to do!?img-2019-07-08-21-03-33

#7

Yes each node in mainnet need its own unique wallet, and cannot clone to multiple nodes.

But you can configure the BeneficiaryAddr to the same wallet address, so all your nodes will transfer mining reward to that single address automatically.