ARK is advancing and improving its core to prepare it for easily deployable custom blockchains and multiple network support, along with constantly improving the base code. Thus, we are happy to announce a new node.js core release moving from 1.0.0 to 1.0.1.

What has been implemented in this new version?

Major upgrade on the core code to support multiple networks. This code upgrade does not change any API features, but enables the deployment of custom networks — ARK becoming the 1st blockchain made for easily deployable custom blockchains based on project/customer/startup/enterprise needs (delegate numbers, transactions per block, block times, … ). A video showing how easy it will be to deploy your own blockchain will be available in the coming days.

(delegate numbers, transactions per block, block times, … ). A video showing how easy it will be to deploy your own blockchain will be available in the coming days. Resolved peers being broadcast forever, even when they are shut down, leading to lite clients having some transactions not entering the blockchain.

Resolved rebuilding from block 0, which caused a stop at block 93477 (read more here on this matter : https://blog.ark.io/march-ark-after-launch-update-and-bugs-fixed-6818d3e4e96f )

Hey, what do I, as ARK user, need to do?

Nothing, the only ones that need to update are delegates or people running ARK main net node on their server(s).

If you are using ARK Desktop wallet be sure you are already using the latest version (1.2.2 as of today) of ark-desktop : https://github.com/ArkEcosystem/ark-desktop/releases

Hey, I’m a delegate, or I have a relay node running, what do I need to do?

You will need to update your ARK node with new ARKcommander.sh.

Follow these simple steps (once connected to server running ARK node).

cd ~

rm ARKcommander.sh

wget https://ark.io/ARKcommander.sh

bash ARKcommander.sh

(input your sudo password if asked)

Option ‘3’ Update ARK (press number 3 + [enter]) — wait till it completes press [enter] and you are done — easy right?

Now you can get back to monitoring with ‘L’.

P.S. : Useful tip — if you are an active delegate (one of the 51st) before you update if you don’t want to miss a block look on ARK Explorer when its your turn to forge (https://explorer.ark.io/delegateMonitor) and do it in time before your turn (2–3 minutes should be enough for your node to update and get back to latest block).

New ARKcommander.sh as you can see has a neat feature when you start it if there is a new ARK core version it will let you know.

Before latest update:

After you update to latest version:

Hey, I am a developer, and I want to launch my own private/public blockchain?

Stay tuned as a lot of awesomeness is coming to help you get started!