#v2.1

Upgrading from v2.0 to v2.1 is fairly straightforward if you follow the instructions. Even though we try to ensure backward compatibility (BC) as much as possible, sometimes it is not possible or very complicated to avoid it and still create a good solution to a problem.

Upgrading, in general, is as simple as updating your installation through the commander or by running git pull && yarn setup inside the installation directory. In a big application, however, there may be more things to consider, which are explained in the following.

This guide assumes you have Core installed inside the ~/ark-core directory with your configuration being located at ~/.ark. If you are using different locations, you will need to adjust those inside the examples which can be found below.

Upgrading a complex software project always comes at the risk of breaking something, so make sure you have a backup.

#Notes

It is recommended to start your relay and forger through the Core Commander . If you wish to run them on your own, you should take a look at how commander executes them via pm2.

After upgrading you should check whether your application still works as expected and no plugins are broken. See the following notes on which changes to consider when upgrading from one version to another.

#Upgrade Steps

#Upgrade Script

You can either run bash <(curl -s https://raw.githubusercontent.com/ArkEcosystem/core/master/upgrade/2.1.0/normal.sh) or run below commands manually.

#Relay Runners & Delegates

 1#!/usr/bin/env bash
 2 
 3cd ~/ark-core
 4pm2 delete all
 5git reset --hard
 6git pull
 7git checkout master
 8yarn run bootstrap
 9yarn run upgrade
10 
11# If You Do Not Use Core Commander You Can Skip This Step.
12cd ~/core-commander
13git reset --hard
14git pull
15git checkout master
16bash commander.sh

#Exchanges

You can either run bash <(curl -s https://raw.githubusercontent.com/ArkEcosystem/core/master/upgrade/2.1.0/exchange.sh) or run below commands manually.

 1#!/usr/bin/env bash
 2 
 3cd ~/ark-core
 4pm2 delete ark-core
 5pm2 delete ark-core-relay
 6git reset --hard
 7git pull
 8git checkout master
 9yarn run bootstrap
10yarn run upgrade
11 
12pm2 --name 'ark-core-relay' start ~/ark-core/packages/core/dist/index.js -- relay --network mainnet

#Notes

• The yarn setup command will upgrade Core and its direct dependencies. Without yarn setup the upgrade will fail as Core is written in TypeScript and the files need to be run through the TypeScript Compiler (tsc).

#Changes

#Configuration

• If you have been using custom dynamic fees, open the ~/.config/ark-core/<network>/plugins.js file and locate the @arkecosystem/core-transaction-pool plugin. Add below code to it and enter your desired values.

 1dynamicFees: {
 2    enabled: true,
 3    minFeePool: 3000,
 4    minFeeBroadcast: 3000,
 5    addonBytes: {
 6        transfer: 100,
 7        secondSignature: 250,
 8        delegateRegistration: 400000,
 9        vote: 100,
10        multiSignature: 500,
11        ipfs: 250,
12        timelockTransfer: 500,
13        multiPayment: 500,
14        delegateResignation: 400000,
15    },
16},

#Path

From version 2.1 onwards Core will make use of system specific paths to support as many platforms as possible in the long-term.

You can read more about those paths at https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html .

#Conclusion

Once all these changes have been made you will need to restart your relay and forger (if you are a delegate) for these changes to take effect.

If you’ve been running your relay and forger manually you need to change packages/core/bin/ark to packages/core/dist/index.js to ensure that the JavaScript files, created by the TypeScript Compiler, are executed.

Also make sure that you are no longer passing in the --data and --config flags so core can pick up the system paths. Those flags are only intended for development or custom setups.