Skip to content


The following guide will teach you how to conduct a binary update for your validator. Binary updates are rare SwapDEX but essential from time to time to ensure that your validator can participate in the consensus mechanism and is able to function properly.

Learn more about the reasons behind this update in the following section.

Why is this update needed? (Announcement)


The anticipated launch of Kazama Swap on our Network has made a significant step forward.

Today we like to inform you that the dev teams have made fantastic progress in the background, testing, and innovating on the Kusari Network.

One outcome of the rigorous testing on Kusari was a significant improvement in our blockchain's underlying technology, namely the p2p network communication layer. The dev teams managed to enhance the standard substrate module to unleash the full potential of Kazama Swap on our EVM.

So what does this mean for you? Well, this improvement renders us even more unique than other projects that simply adapt the substrate framework, and for our validator community, there is now some action to do.

Since the P2P network layer is not part of the runtime, it cannot be updated automatically, meaning you need to download and install a new binary. This is not a fork because the old binaries will still work. However, the moment we update the runtime forklessly, your validators will have trouble interfacing with the new p2p network technology and won't be able to author blocks. To address any potential concerns, they won't suffer any slash penalties if they are not updated, but they will need to be updated to continue to author blocks.

We shall release step-by-step instructions on how to update your validators accordingly, but for now, we would like to take the time to appreciate the outstanding efforts of our partners and development team.

The Process



Make sure to update your OS to Ubuntu 21.10 since the new binaries are compiled for that Ubuntu version. You can follow our online guide to conduct the OS update. Other OS versions might work as well but are under your own risk.

Step 1 - Pause / Chill your Validator

Visit the substrate portal and navigate to the staking tab and select accounts.

Click the Stop Button and sign the transaction accordingly. img

After the transaction was signed you should see the following validation screen. img


You successfully paused / chilled your validator and can proceed to step 2

Step 2 - Purge current Session Keys

Navigate to the Developer Tab and select Extrinsic then select your controller account and the session pallet in the dropdown menu.

The session pallet offers two extrinsics:

  1. PurgeKeys()
  2. SetKeys()

Select PurgeKeys() and click hit Submit Transaction.



You successfully purged your current session keys and can proceed to step 3

Step 3 - Execute Update Command on your Server

Login to your server as root.


The following command will clean and delete the current binary and download and install a new but specific binary. If you are not sure about the version of your binary pls reach out to our validator community on Discord.

 service swapdex stop && wget && chmod 777 swapdex_ubuntu_21_10-swapdex-polkadot-v0.9.18-bdfbeb9e-980 && mv swapdex_ubuntu_21_10-swapdex-polkadot-v0.9.18-bdfbeb9e-980 /usr/bin/swapdex -f && runuser -l  swapdex -c 'swapdex purge-chain --chain swapdex -y'


You successfully deleted and cleared your old binary and installed the new binary

Step 4 - Start Validator Service on your Server

Execute the following command to start your validator and the sync process.

service swapdex start && journalctl -f -u swapdex


You successfully started the new binary

Since we cleared / purged the old binaries' data your validator need to download the full database / blocks again. This sync process should not take long thanks to the improvements in the P2P Network Layer.

However, make sure to fully sync your validator before you restart your validator on the substrate portal. If your validator is not in sync, and you get elected to the active set you will miss opportunities to author blocks and might get chilled as a consequence.

You can observe the progress either in the logs or on our telemetry UI : Telemetry UI


You successfully completed step 4

Step 5 - Generate new Session Keys

Login to your VPS server.

Session keys are needed to associate your node with your controller account. To generate the session keys you can run the following command in your terminal:


Hit Ctrl+C To exit the logs showing up on your server

curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params":[]}' http://localhost:9933

The output will have a hex-encoded "result" field. The result is the concatenation of the four public keys. Save this result for a later step. Copy the session key. It will look like this:



You successfully generated your new session keys

Step 6 - Restart Validator on Substrate Portal

Visit the substrate portal and navigate to the staking tab and select accounts.

Click the Session Key button and enter your key from the previous step.


Finally, set Session Keys and sign the transaction and your validator should join the active set without any issues.


Finally, click validate and set your validator preferences. Keep in mind that some users may nominate you because of your commission settings, so it's recommended to keep the former commission settings or inform your nominators that you plan to change the percentage.




You successfully finished the update process. Congrats mate!

Written by Masterdubs & Petar