Join a custom DEX market

Overview

This guide assumes that the custom quote chain symbol will be foo - You should substitute foo with the relevant quote chain symbol everywhere (including all file names) as you go through this guide. The blockchain symbol (also called network symbol) is a unique symbol or acronym used to represent a blockchain (E.g. for listing on exchanges).

1. Requirements

1.1. Machine/instance requirements

• A machine/instance with a publicly exposed IP address (E.g. from a cloud service provider).
• 100GB of hard drive space is recommended (this should be enough for several years of data).
• Port 8001 needs to be open for inbound TCP traffic.
• All ports should be open for outbound TCP traffic.

1.2. A compatible LDEM node with the relevant chain modules installed

To create a custom DEX market, you first need to have an LDEM node - Any node which is based on the LDEM engine is fine; this includes a Leasehold node or a Capitalisk node. But for the purpose of this guide, it is recommended to use a Capitalisk node - So you should follow the Set up a new Capitalisk node guide to set up a node. Make sure that you also have the pm2 command installed globally on your node (sudo npm install -g pm2).

For a node to provide a DEX market between 2 different blockchains, it needs to participate in both of those blockchains - This means that your node needs to run an instance of both chain modules. Since a Capitalisk node already supports the clsk blockchain by default, you only need to set up 1 additional blockchain module.

You can join an existing blockchain by following the Join a custom blockchain guide.

Once you have set up the relevant chain module and your node is in sync with both blockchains (base chain and quote chain), you can start setting up your DEX market.

1.3. LDPoS Commander CLI

You need to install the ldpos-commander Node.js module using the following command:

npm install -g ldpos-commander

OR (if the above fails):

sudo npm install -g ldpos-commander

Check that the installation was successful using the command:

ldpos version

If the command outputs a version number, it means that the installation was successful.

2. Add the relevant custom module config object

You will need to open your node's config.json file (inside your main capitalisk-core directory). Inside this file, you should find a field called modules which is an array of module objects.

You will need to add the DEX market's module config object (which should be provided to you by existing DEX market participants) to the modules array. The object might look like this (though it will likely have some different values and properties):

"capitalisk_dex_foo_clsk": {
  "moduleEnabled": true,
  "modulePath": "node_modules/capitalisk-dex",
  "passiveMode": false,
  "dexEnabledFromHeight": 12345,
  "signatureBroadcastDelay": 15000,
  "transactionSubmitDelay": 5000,
  "multisigExpiry": 86400000,
  "multisigExpiryCheckInterval": 600000,
  "orderBookSnapshotFilePath": "./dex-snapshot-foo-clsk.json",
  "orderBookSnapshotBackupDirPath": "./dex-snapshot-foo-clsk-backups",
  "orderBookSnapshotFinality": 29,
  "orderBookSnapshotBackupMaxCount": 24,
  "baseChain": "clsk",
  "priceDecimalPrecision": 2,
  "readBlocksInterval": 3000,
  "components": {
    "logger": {
      "fileLogLevel": "debug",
      "consoleLogLevel": "debug"
    }
  },
  "chains": {
    "clsk": {
      "moduleAlias": "capitalisk_chain",
      "chainCryptoLibPath": "node_modules/ldpos-chain-crypto",
      "multisigAddress": "7929826179931699287L",
      "memberAddress": "4738410848285516033L",
      "passphrase": "gorilla fancy token now rabbit orphan exist orbit essay butter rug grape",
      "requiredConfirmations": 0,
      "orderHeightExpiry": 20250,
      "readMaxBlocks": 1000,
      "exchangeFeeBase": "20000000",
      "exchangeFeeRate": 0.01,
      "minOrderAmount": "1000000000",
      "dividendStartHeight": 0,
      "dividendHeightInterval": 20250,
      "dividendHeightOffset": 2,
      "dividendRate": 0.9,
      "minPartialTake": "200000000"
    },
    "foo": {
      "moduleAlias": "foo_chain",
      "chainCryptoLibPath": "node_modules/ldpos-chain-crypto",
      "multisigAddress": "6535469681290206175L",
      "memberAddress": "10670116278626911259L",
      "passphrase": "phrase reduce peanut industry zoo deny toilet gasp fancy material claw resist",
      "requiredConfirmations": 0,
      "orderHeightExpiry": 20250,
      "readMaxBlocks": 1000,
      "exchangeFeeBase": "20000000",
      "exchangeFeeRate": 0.01,
      "minOrderAmount": "1000000000",
      "dividendStartHeight": 0,
      "dividendHeightInterval": 20250,
      "dividendHeightOffset": 2,
      "dividendRate": 0.9,
      "minPartialTake": "200000000"
    }
  }
}

It's important that the properties and values in your module's config object match those of other nodes which participate in this DEX market or else your node will not be able to reach consensus with the rest of the network/federation and it will not be able to sign cross-chain trades or collect dividends.

After you've copied the DEX market config inside your config.json file, you will need to add your own memberAddress and passphrase entries for each blockchain/multisig account. There are 4 properties/values you need to change:

• chains.clsk.memberAddress
• chains.clsk.passphrase
• chains.foo.memberAddress (replace foo with the relevant blockchain symbol)
• chains.foo.passphrase (replace foo with the relevant blockchain symbol)

3. Set up DEX HTTP API

You should follow the Set up DEX HTTP API guide to expose your DEX market's HTTP API. The HTTP API is necessary if you want people to connect to your node and trade through it using the LDEX trading application.

4. Start your node

You can start the node using PM2:

pm2 start index.js --name "ldem-node" -o "/dev/null" -e "/dev/null"

If you get any errors, make sure that you don't have an existing node already running. If you do, you can shut it down using pm2 delete ldem-node.

You should check the logs using the following command:

pm2 logs ldem-node

Depending on your log level, you may see a lot of messages which indicate that your node is catching up with the network. If you see a lot of error messages, it could be an indication that something went wrong. Compare your logs with existing DEX market participants to verify that your node is running correctly.

Press Ctrl + C to stop reading the logs.