How to Deploy ThorChain BEPSwap on Akash DeCloud ⚡️


Dec 09, 2020

7 min read

How to Deploy ThorChain BEPSwap on Akash DeCloud ⚡️

This guide was originally published on Github Awesome Akash repo. It is based on the guidelines provided by Serum on Akash. If you’re not familiar with Decentralized Cloud (DeCloud) and Akash, I recommend you take a look at my past article: Why DeCloud is important for DeFi. DeCloud is a blockchain-based alternative to traditional cloud providers which brings several advantages and competitive pricing. It’s also quite easy to get started, and that’s what we will see here.

In this article, you will see how to deploy ThorChain BEPSwap web UI using Akash. Many more Dapps can be easily deployed on Akash, as you can see in the Awesome Akash repo. I chose to build a guide with ThorChain BEPSwap because I am a big fan of their cross-chain liquidity network, and it’s built on Cosmos, just like Akash. It’s worth exploring more about ThorChain if you’ve not done so yet.

This guide is divided into 8 steps. You can skip step 4 if you want to re-use my Docker image. Do not forget to close your deployment if you are running on testnet, as resources are limited, see Step 8 on how to close.

  1. Prerequisites
  2. Set-up your environment
  3. Verify your environment
  4. Build Thorchain BEPSwap UI container
  5. Create the deployment
  6. Deploy
  7. Service logs
  8. Close your deployment

1. Prerequisites

You will need some basic command line and Linux knowledge to go through the guide. Please set-up the below before going further:

If you intend to containerize your own web app (Step 4):

2. Set up your Environment

We will be using shell variables throughout this guide. Ensure you have the below variables set-up by using export VARNAME=…

AKASH_NET=... See latest Akash network doc to choose your network. We will be using edgenet with:

export AKASH_NET=""

AKASH_CHAIN_ID=... We will be using edgenet-1 which is the recommended edgenet chain at the time of this article.

export AKASH_CHAIN_ID="$(curl -s "$AKASH_NET/chain-id.txt")"

AKASH_NODE=… We will be using a recommended RPC endpoint based on the chosen Akash network .

export AKASH_NODE="$(curl -s "$AKASH_NET/rpc-nodes.txt" | shuf -n 1)"

KEY_NAME=yourkeyname for example:

export KEY_NAME=edouard

ACCOUNT_ADDRESS=… We will be getting the account address based on the key.

export ACCOUNT_ADDRESS="$(akash keys show $KEY_NAME -a)"

3. Verify your Environment

We will now verify that we have set-up the environment correctly and that we are ready to move forward.

Verify that you have the correct node and chain id.


this should return something similar to. These values might differ depending on the network to which you are connecting

tcp:// akash-edgenet-1

Verify key name

echo $KEY_NAME

my local key is called edouard


Verify the account address



Check that you have sufficient balance on your Akash wallet

akash query bank balances --node $AKASH_NODE $ACCOUNT_ADDRESS

You should see a response similar to

- amount: "93000637"
  denom: uakt
  next_key: null
  total: "0"

If you don’t have a balance, check out Funding your account and look for the Faucet URL.

4. Build Thorchain BEPSwap UI Container

You can skip this process and go to 5. Create the Deployment if you’d like to use my already existing docker image edouardl/thorchain-bepswap-web-ui

The docker image set in this guide edouardl/thorchain-bepswap-web-uiwill deploy the testnet version of BEPSwap. The guide explains how to build and push your own image to the Docker registry. If you want to deploy Mainnet, you will need to change the variables accordingly before building your own image.

Get the source code:

git clone bepswap-web-ui

Install dependencies using:yarn install

Add serve dependency using:yarn add serve

Create a Procfile to define the web process:

cat > Procfile <<EOF
web: yarn serve -s build

We will be using Heroku Buildpacks with to build our container. Pick an image name and store it in IMAGE environment variable. I chose edouardl/thorchain-bepswap-web-ui as my image name, you should choose <docker-id>/thorchain-bepswap-web-ui as yours. If you don’t have yet a Docker ID you’ll need to signup.

export IMAGE=edouardl/thorchain-bepswap-web-ui

To build the container, run:

pack build $IMAGE --builder heroku/buildpacks:18

Run the docker image locally to verify it works:

docker run -it --rm -e NODE_ENV=production -p 5000:5000 $IMAGE

Verify by visiting http://localhost:5000 on your browser.

Push the image to Docker Hub (Container Registry) using:

docker push $IMAGE

5. Create the Deployment

Create a deployment configuration thorchain.yml to deploy the edouardl/thorchain-bepswap-web-ui for ThorChain BEPSwap Web UI Node JS app container using SDL.

You can use curl to download the thorchain.yml file directly.

curl -s > thorchain.yml

Or copy/paste the below

version: "2.0"
    image: edouardl/thorchain-bepswap-web-ui
      - port: 5000
      as: 80
        - global: true
          units: 0.1
          size: 512Mi
          size: 512Mi
          - "akash1vz375dkt0c60annyp6mkzeejfq0qpyevhseu05"
          denom: uakt
          amount: 3000
      profile: web
      count: 1

6. Deploy

In order to deploy, run the below command

akash tx deployment create thorchain.yml --from $KEY_NAME --node $AKASH_NODE --chain-id $AKASH_CHAIN_ID --fees 5000uakt -y

This posts the deployment to the Akash DeCloud marketplace where you will get matched with a provider.

After a few seconds ⏱, your lease becomes active. You can query the status of the lease using the below command.

akash query market lease list --owner $ACCOUNT_ADDRESS --node $AKASH_NODE --state active

Once it is active, you should see something similar to below

- lease_id:
    dseq: "160398"
    gseq: 1
    oseq: 1
    owner: akash1j8s87w3fctz7nlcqtkl5clnc805r240443eksx
    provider: akash1uu8wfvxscqt7ax89hjkxral0r2k73c6ee97dzn
    amount: "51"
    denom: uakt
  state: active
  next_key: null
  total: "0"

In the information above, the price amount denotes how many uakt (akt 10^-6) the lease is costing per block.

We will now export the values for Provider, Dseq, Oseq and Gseq in order to upload the manifest and deploy the image. Use the values you get from your own lease, not the below ones.

export DSEQ=160398
export OSEQ=1
export GSEQ=1
export PROVIDER=akash1uu8wfvxscqt7ax89hjkxral0r2k73c6ee97dzn

We can verify that the values are populated by running


You should see a response similar to:

akash1uu8wfvxscqt7ax89hjkxral0r2k73c6ee97dzn 160398 1 1

Upload the manifest using the values from the above step:

akash provider send-manifest thorchain.yml --node $AKASH_NODE --dseq $DSEQ --oseq $OSEQ --gseq $GSEQ --owner $ACCOUNT_ADDRESS --provider $PROVIDER

Your image is now deployed, once you uploaded the manifest. You can retrieve the access details by running the below:

akash provider lease-status --node $AKASH_NODE --dseq $DSEQ --oseq $OSEQ --gseq $GSEQ --provider $PROVIDER --owner $ACCOUNT_ADDRESS

You should see a response similar to:

  "services": {
    "web": {
      "name": "web",
      "available": 1,
      "total": 1,
      "uris": [""],
      "observed-generation": 0,
      "replicas": 0,
      "updated-replicas": 0,
      "ready-replicas": 0,
      "available-replicas": 0
  "forwarded-ports": {}

You can access the application by visiting the hostnames mapped to your deployment. In the above example, it is

The link might lead to 404 since I closed the deployment to keep resources for others on the testnet.

If your deployment went well, you should see something like that.

7. Service Logs

You can view the logs for your application using akash provider service-logs, for example:

akash provider service-logs --node $AKASH_NODE --dseq $DSEQ --oseq $OSEQ --gseq $GSEQ --provider $PROVIDER --owner $ACCOUNT_ADDRESS --service web

You should see a response similar to:

[web-7447d7769-c6t4f] yarn run v1.22.10[web-7447d7769-c6t4f] $ /workspace/node_modules/.bin/serve build[web-7447d7769-c6t4f] INFO: Accepting connections at http://localhost:5000

8. Close your deployment

When you are done with your application, close the deployment. This will free up your container and stop the token transfer. Close deployment by creating a deployment-close transaction:

akash tx deployment close --node $AKASH_NODE --chain-id $AKASH_CHAIN_ID --dseq $DSEQ --owner $ACCOUNT_ADDRESS --from $KEY_NAME -y --fees 5000uakt

Additionally, you can query the market to check if your lease is closed:

akash query market lease list --owner $ACCOUNT_ADDRESS --node $AKASH_NODE

You should see a response similar to:

  - lease_id:
      dseq: "160398"
      gseq: 1
      oseq: 1
      owner: akash1j8s87w3fctz7nlcqtkl5clnc805r240443eksx
      provider: akash1uu8wfvxscqt7ax89hjkxral0r2k73c6ee97dzn
      amount: "186"
      denom: uakt
    state: closed
  next_key: null
  total: "0"

Congrats 🥳

You managed to deploy an awesome DeFi application using Akash DeCloud. Many more projects can be deployed on Akash, and the long list on Awesome Akash is more like initial inspiration. Akash has the potential to break the current cloud oligopoly and make web infrastructure more decentralized and more resilient. Another application I am very interested in is blockchain nodes. Some PoS networks have around 70%+ of their nodes running with the same cloud provider, which somehow creates a single point of failure. Akash supports blockchain nodes and Akash on Akash is a good guide to get started for Cosmos SDK nodes.

Get to know more

DISCLAIMER: This guide is intended for developers and for testnet deployments only. This is not financial advice. Blockchain and cryptocurrencies involve a high degree of risk, and there is always the possibility of loss, including the loss of all staked digital assets.

Subscribe to Stakin Newsletter

Stay informed about the latest trends in the blockchain ecosystem and gain expert insights from a leading Web3 operator.