Scalaris DX Listings

Scalaris DX is the one of fastest, most secure, most reliable, and most decentralized exchange (DEX), built on the Blocknet Protocol. The exchange has over 90 digital assets trading (see below), with the number continuously growing as more are made compatible. There is complete trading pair freedom, meaning any two assets can be traded.


Listing Process

A Scalaris DX listing holds many benefits beyond just being traded on the exchange. Being listed means the asset has been integrated with the Blocknet Protocol, which powers Scalaris DX, and allows other services to be built utilizing the asset. This extends the demand, utility, and accessibility of the asset to the rest of the ecosystem.

Getting listed on Scalaris DX is 100% free. If you would like to have a digital asset listed, the first step is to confirm the asset meets the following requirements. If it doesn't currently meet all these requirements, please work with the developers of the project/asset to ensure they are all met. If you have questions about any of these requirements, please join Scalaris Discord Server or join Scalaris Telegram and ask your questions in the #scalaris-dx-listing channel.

Requirements

In order for for a blockchain to be compatible it must support JSON RPC, CLTV atomic swaps, and the following calls:

  • createrawtransaction
  • decoderawtransaction
  • getblock
  • getblockchaininfo (fallback getnetworkinfo, getinfo)
  • getblockhash
  • getnewaddress
  • getrawmempool
  • getrawtransaction
  • gettransaction
  • gettxout
  • listunspent
  • sendrawtransaction
  • signmessage
  • signrawtransaction (or signrawtransactionwithwallet)
  • verifymessage

Requirements Met

When all of the above requirements are met, you are ready to proceed to the next step in listing your asset. At this point, you basically have two options:

Option 1. Do it yourself.

This option is 100% free. It could be for you if...

  1. You are comfortable working with Git Fork-and-Branch workflow.
  2. You are comfortable editing JSON format files like this and creating configuration files like this.
  3. You can Thoroughly test your asset in ScalarisDX, and that requires a Service Node to host your asset's native wallet. The easiest way to have a Service Node host your asset's wallet is to own your own Service Node and host it yourself. However, if it's not feasible for you to run your own Service Node, you can probably find someone in the Scalaris Community who will host your asset on their Service Node at a very reasonable rate. (If you get lucky, or if your asset is expected to have high trade volume, you might even find someone to host it for free.) To look for someone to host your asset on their Service Node, join Scalaris Discord Server or join Scalaris Telegram and ask around in the #scalaris-dx-listing channel.

  4. If you can meet criteria 1, 2 & 3 above, use Git Fork-and-Branch workflow to:

    1. Create an XBridge Config. file for your asset in the directory, xbridge-confs.
    2. Create a Wallet Config. file for your asset in the directory, wallet-confs.
    3. Add an object for your asset in the file, manifest-latest.json.
    4. Add an object for your asset in the file, manifest.json. (This file is actually identical to manifest-latest.json; it may be eliminated someday.)

    The README.md in the blockchain-configuration-files directory contains full details on how to create & edit these files. It also contains detailed instructions for Testing a Blockchain for Compatibility, which you should be sure to follow before submitting a Pull Request to have your listing merged into the master branch of the Github repository.

    Tip: you may save some time by identifying an already listed asset which is closely related to your asset, then copying/pasting/modifying from that asset.
    Tip: How to determine config values for MinTxFee & FeePerByte in XBridge Config. file.

    MinTxFee & FeePerByte are two values set in an asset's XBridge Config. file which are sometimes confusing to people. MinTxFee can be used to set a minimum transaction fee, but most of the time it works best to keep this value set to 0 and instead adjust the value of FeePerByte. FeePerByte is how much to charge per byte for an exchange. This can be calculated by looking in the wallet send function for the recommended fee per byte and then multiplying it by 2-2.5 since there are 2 transactions that occur in an exchange: one transaction from one party's address to the P2SH address and then a second transaction from the P2SH address to the counterparty's address. This is one of the reasons why test trades are needed.

Option 2. Contract a member of the Scalaris Community to do it for you.

This option is obviously not 100% free, but there are Scalaris Community members who are willing to do the work of listing & testing your asset, and also willing to host your asset on their Service Node at very reasonable rates. To pursue this option:

  1. join Scalaris Discord Server or join Scalaris Telegram
  2. Navigate to the #scalaris-dx-listing channel in Scalaris Discord.
  3. Post a message requesting listing and hosting services, tagging

Listed Digital Assets

Note: Scalaris DX is not yet compatible with hardware wallets such as Ledger, web wallets such as MyEtherWallet (MEW), or lite wallets such as Jaxx. Desktop Qt wallets must be used. Below is a list of compatible assets and respective wallet versions.

DO NOT use a wallet version not listed here, it is either not compatible or hasn't been tested.

Compatible with Blocknet wallet v1.0.x

View Manifest

Digital Asset Ticker Supported Wallet Versions

XRouter Beta Released! Read more...
Required Wallet Update! View downloads...