Block DX Trading

Block DX is the fastest, most secure, most reliable, and most decentralized exchange (DEX), built on the Blocknet Protocol. Follow the guides below to learn how to check your balances, select your market, make orders, take orders, check order status, and view order history. If Block DX has not been setup yet, please follow the setup guide.

Acquiring Initial BLOCK

When making a new order (i.e. creating a new offer to buy/sell some asset), there is no Exchange Fee on BlockDX. Therefore, it is possible to acquire BLOCK on the BlockDX exchange, even if you don't currently own any BLOCK. You simply make an offer to buy BLOCK on one of the more liquid trading pairs, like BLOCK/LTC, and wait for someone to take your order (i.e. wait for someone to accept your offer). However, if for some reason you can't wait for someone to accept your maker order to buy BLOCK, there are ways to acquire the small amount of BLOCK you need to pay the Taker Fee:

  1. Join Blocknet's Discord and ask in the #support or #trading channel if someone would be kind enough to tip you a small amount of BLOCK to get you started trading on BlockDX. Chances are you'll find a generous person who will be happy to send you a tip via the Discord Tip Bot. After receiving a tip you can withdraw your BLOCK from the Discord Server by going to the #tip-bot channel in Blocknet Discord and entering: !withdraw address amount coin where address is your BLOCK address, amount is the amount of BLOCK to withdraw, and coin is BLOCK.
  2. Another option for acquiring a small amount of initial BLOCK is to use the faucet.
Note: Taker Fee must be paid from the Blocknet core/native wallet; it cannot be paid with BLOCK stored in XLite. Having no BLOCK in your Blocknet core wallet will result in Insufficient Funds error from BlockDX when taking/accepting orders.

For this reason, it's a good idea to keep a few BLOCK in your Blocknet core/native wallet. In a soon-to-be-released version of BlockDX, it will be possible to pay the Taker Fee with BLOCK stored in XLite and it won't even be necessary to run Blocknet core wallet to trade on BlockDX.

IMPORTANT: Your Blocknet wallet and the wallets of the assets you are trading must remain open and unlocked during atomic swaps.

If any of these wallets goes offline in the middle of an atomic swap, it could result in loss of funds if you do not bring them back online immediately.

Explore Blocknet Network to see how many Service Nodes currently support each digital asset, and much, much more...

Before an asset can be traded on BlockDX, it must be supported by one or more Service Nodes. Blocknet community members have created several web based services to make it easy to discover which assets are currently supported by Service Nodes. Some of these websites actually offer much more information about the Blocknet Network than just how many Service Nodes support each digital asset:

Tip: How to stop your Blocknet wallet from staking while it's unlocked for trading.

To trade BLOCK on BlockDX from your Blocknet core wallet, your Blocknet core wallet must be fully unlocked. Normally, when your core wallet is unlocked, it automatically begins staking. If, while staking, one of the UTXOs in your wallet "hits a stake", it becomes immature for 101 confirmations, and it is unavailable for trading while it's immature. At times, it can interfere with trading when a large UTXO goes immature for 101 confirmations. Fortunately, there's a way to have your Blocknet core wallet unlocked, but not staking. The trick is simply to add staking=0 to the blocknet.conf file in your data directory, then restart your Blocknet core wallet. (If blocknet.conf doesn't already exist in your data directory, create it.)


Balances

The first thing you want to do when starting Block DX is to check your balances. Balances displays the connected wallets along with the available balance. A connected wallet is one that has been configured and is currently open and unlocked. The available balance is the balance of the funds in a wallet that are not locked up.

Balances

The Available balance may show a value different than what's displayed in the wallet if:

Select Market
  1. The market selection tool can be found in the upper-left corned.

    Select Market

  2. Click the Select market pair button.

  3. A downdown will appear with two lists: the assets of the wallets you have connected and all assets listed on Block DX.

    Select Market

  4. From Connected Tokens, select the asset you would like to trade.

  5. Select the asset you would like to trade the first asset with. The first asset will be priced in terms of this asset. This asset must have a wallet configured.

    Select Market

  6. Select Select to view the chosen market.

    Select Market

Market Information
Tip: To view currently active BlockDX orders from a browser, visit BlockNetMonitor
Warning: When opening BlockDX for the first time it can take up to 3 minutes for all currently active orders to display on the screen.

This is simply the nature of a fully decentralized, peer-to-peer network. If your XBridge client is connected to very few peers, it can even take slightly longer than 3 minutes.

Hint: Check your peer count.
  • Redesign Wallet:

    Peers Status

  • Classic Wallet:

    Peers Status

Within BlockDX, each market has a price chart, depth chart, and market stats available.

Market Data

The market stats are above the price chart and show the last trade price, percent in price change over the last 24 hour rolling period, and volume over the last 24 hour rolling period.

Stats

The chart has the ability to zoom. To zoom in, click and drag the pointer over the are you want to zoom in on.

Price Chart Zoom

You can hover over the candles to show the information of each data point in the legend.

Price Chart Zoomed

To reset the chart, select the Show All button in the upper-right corner of the chart.

Show All

To the right of the price chart there's also a depth chart. The depth chart shows how much market depth there is of orders at certain prices.

Depth Chart

Hover order the depth chart to view the data values.

Depth Chart Hover

Make Order

Make Order

  1. Review the trading fees for making orders.
  2. At the left side of Block DX you will find an order form.
  3. Select either the buy or sell tab.
  4. For Amount (the first input), enter the amount you would like to buy or sell.

    Note: There are no limit, market, or partial orders.
    At the moment there are just *Exact* orders, meaning that orders must be taken for the exact amounts. Due to this setup, if trading a large amount it may be best to instead break the order into a few smaller separate orders.
    
  5. For Price (the second input), enter the price (rate) for which you would like to trade the first asset. Note, there is also an option to enter Price in terms of BTC.

  6. Total shows the total amount of the 2nd asset that will be traded for the first asset.
  7. In the Address fields, enter the addresses the funds will be going to for each asset. In the above example, buying BLOCK with LTC, the BLOCK Address is the address where the BLOCK you buy will be sent, and the LTC Address is the change address where LTC change from the transaction will be sent. If you don't mind having funds sent to new/empty addresses in your BLOCK and LTC wallets, you can use the auto-generated addresses. However, if you want the asset you're acquiring or the change from the transaction to go to specific addresses in your wallet, you'll need to copy/paste those specific addresses from your wallets into these fields. (For now, these Address fields must be legacy addresses, not Segwit addresses.) See these hints for help finding specific addresses in XLite. Note, the address from which the trade is funded is chosen automatically by BlockDX. BlockDX funds the trade from the address with the smallest UTXO which can cover the expense of the trade.
  8. Ignore Order ID. That should be blank when creating an order.
  9. Review your order.
  10. Select the place order button.
  11. The trade will now be visible as Open under Active Orders.

    Active

The Blocknet wallet and the wallets that are being traded out of must remain open and unlocked during trading. If the Blocknet wallet is closed, any open orders will automatically be cancelled.

Take Order
  1. Review the trading fees for taking orders.
  2. On the right side of Block DX you will find the order book.

    Order Book

  3. Click on the order you would like to take.

    Note: There are no limit, market, or partial orders.
    At the moment there are just *Exact* orders, meaning that orders must be taken for the exact amounts. Due to this setup, you must have enough funds to cover the entire sell amount of the order selected.
    
  4. The order form on the left side of Block DX will auto-populate.

    Take Order

  5. Make sure Balances shows enough funds in the Available column to cover the order.

  6. In the Address fields, enter the addresses the funds will be going to for each asset. In the above example, selling BLOCK for LTC, the BLOCK Address is the change address where BLOCK change from the transaction will be sent, and the LTC Address is the address where the LTC you acquire from the sale will be sent. If you don't mind having funds sent to new/empty addresses in your BLOCK and LTC wallets, you can use the auto-generated addresses. However, if you want the asset you're acquiring or the change from the transaction to go to specific addresses in your wallet, you'll need to copy/paste those specific addresses from your wallets into these fields. (For now, these address fields must be legacy addresses, not Segwit addresses.) See these hints for help finding specific addresses in XLite. Note, the address from which the trade is funded is chosen automatically by BlockDX. BlockDX funds the trade from the address with the smallest UTXO which can cover the expense of the trade.
  7. Review your order.
  8. Select the place order button.
  9. The trade will now be visible under Active Orders.
  10. The trade should complete in about 20-30 seconds.

The Blocknet wallet and the wallets that are being traded out of must remain open and unlocked during trading. If the Blocknet wallet is closed, any open orders will automatically be cancelled.

Order Status

At the bottom of the screen is the Order Status section, where details can be found about the status of an order:

Order Status

If you hover your mouse over the ? symbol in this section, you'll see a chart of every possible status an order can have. The current status is displayed in the Status column on the right. Here is the list of every possible status of an order:

Order Status Table

Any orders that are open or in progress can be found in Active Orders.

Active

You can hover over the order to read the order state.

Active

Any orders that are cancelled, completed, or failed can be found in Inactive Orders

Inactive

Again, you can hover over the order to read the order state. There are different icons to represent each order state.

Inactive Complete Inactive Cancelled

If you have created an order, it will be indicated in the order book with a white dot.

Order Book

The Blocknet wallet and the wallets that are being traded out of must remain open and unlocked during trading. If the Blocknet wallet is closed, any open orders will automatically be cancelled.

Order History

At the bottom-right corner of Block DX you can find the trade history. The trade history information is gathered only for the wallets that are configured. Therefore, the trade history will only show the orders that have been completed since Blocknet wallet and wallets for the currently viewed market have been opened and unlocked. If the Blocknet wallet is restarted, this information will be cleared and no longer visible.

Trade History


Redeem/Refund Funds from Failed or Cancelled Transactions

Failed/Cancelled Transactions - How to redeem/refund lost funds.

For various reasons, a transaction on BlockDX can occasionally fail or get cancelled and get listed under INACTIVE ORDERS as either Failed: Failed Order or Cancelled: Inactive Cancelled When this occurs, BlockDX will attempt to refund both parties in the transaction for up to 2.5 hours. In most cases it will succeed. It's important to keep your Blocknet core wallet, and any wallets involved in the transaction, open and unlocked for 2.5 hours while the refund is attempted. (Blocknet wallet must remain open and unlocked for 2.5 hours no matter which coins were involved in the transaction because the code which manages the refund currently resides within the Blocknet wallet.) In the case of a Failed Order, if the Blocknet wallet is closed before all refunds are completed, or in the rare case that other factors prevent refunds from completing, the order will continue to display a Failed status as shown above, but it will be moved from the INACTIVE ORDERS catagory to the ACTIVE ORDERS category. If this occurs, or if your funds were not returned after 2.5 hours from a Cancelled order, you'll need to manually redeem your funds by issuing a sendrawtransaction <hexstring> command as follows:

Manually Redeem Funds
  1. Navigate to your data directory:

    Windows

    C:\Users\[YourUsername]\AppData\Roaming\Blocknet\
    
    Or paste %appdata%\Blocknet\ into the File Explorer path field.

    MacOS

    ~/Library/Application Support/Blocknet/
    
    Open Finder and in the program menu select Go > Go to Folder... and enter the above path.

    Linux
    ~/.blocknet/
    
  2. In the data directory there is a log-tx subdirectory which contain files named xbridgep2p_YYYYMMDD.log. The hexstring you'll need to use as the parameter for the sendrawtransaction <hexstring> command, will be found in one of the most recent of these .log files.

  3. Starting with the most recent .log file, use a text editor (e.g. NotePad on Windows; TextEdit on Mac) to search these files for information about the failed transaction. Search for text that says either, refund transaction for order or redeem counterparty deposit for order, followed shortly thereafter by the text, (submit manually using sendrawtransaction), followed by a brief description of the attempted transaction (which will include names of the two coins involved, along with amounts and addresses of each coin), followed by a very large hexadecimal string of over 100 characters. This large hexadecimal string is the hexstring you're looking for.
  4. If you find two such hexstrings for the failed transaction - one after the text, refund transaction for order, and one after the text, redeem counterparty deposit for order, make a note of both of them.
  5. Here is an example of the text patterns you're looking for. In this example, the transaction was a sale of 24.9 GLC at address Dw7WLmrifyH3KSsrtkXPQmQA8PrTmt6nxS in exchange for 1.1952 BLOCK at address Brh4VVgQeVtb1A3qroHittKemfDZjSY9Gm:
    refund transaction for order
    77bb55513d72be752ed68b39980cc2e3e821de0e0318a16a7da131840e1211bf
    (submit manually using sendrawtransaction) GLC(24.900000 -
    Dw7WLmrifyH3KSsrtkXPQmQA8PrTmt6nxS) / BLOCK(1.195200 -
    Brh4VVgQeVtb1A3qroHittKemfDZjSY9Gm)
    010000000139602e86db76a93f36293f8b19fbce009fdc68c7f7665cb93e7f37967307e8bd00000000c4483045022100b290e43343728d28dade75719450c8ff338e1431cb51ab05d47e79d76883a16102203f1c493923ed576d7f877470f8be0cc6690f3efe60869346caacd73b0b7d9e9001210399985zb8b14d4e466b89cb2f894c9b24f9c4d9f1fa8585634319ab17bd340ab4514c5663036f1915b17576a914dd4dbb870eeded2f9d4ad18588a470804258185088ac6776a9145779a2aa6ca981f478f6ad18a87e71225558d8d688ad82012188a9149ef2a00e90f13175e306db6d42b60e6c8411869d8768feffffff0181626a94000000001976a9142429537ff322fb00c37cc79aa7a2a1eab3e90dcb88ac6f191500
    2021-Mar-19 21:56:19 [0x0x70000a9c4000] redeem counterparty
    deposit for order
    77bb55513d72be752ed68b39980cc2e3e821de0e0318a16a7da131840e1211bf
    (submit manually using sendrawtransaction) GLC(24.900000 -
    Dw7WLmrifyH3KSsrtkXPQmQA8PrTmt6nxS) / BLOCK(1.195200 -
    Brh4VVgQeVtb1A3qroHittKemfDZjSY9Gm) 01000000014adf54bf3256d7ca69570cf2af50c7c2b23de75ceb29788b9bfbbdfdc49fc58100000000e6210216d45a58aadad62fd4b910a2b855434d1d2f2d64a9e08df5bc25503e76f7b46f48304502210090449659a2a430ca3a6c817be506e60f1b443903bc45dd91f5f136b94316148402201141a691fcc2a3ebb61887639ce21982dff95176260c8e79ad4e58e122cbe77401210399985ab8b14d4e466b89cb2f894c9b24f9c4d9f1fa8585634319ab17bd340ab4004c56630367e71cb17576a9145779a2aa6ca981f478f6ad18a87e71525558d8d688ac6776a914dd4dbb870eeded2f9d4ad18588a470804258185088ad82012188a9149ef2a00e90f13175e306db6d42b60e6c8411869d8768ffffffff0100bb1f07000000001976a914fb3aabbc7c8c0c581df57bd57625d72228be700588ac00000000
    
  6. The two hexstrings in the example above are:
    010000000139602e86db76a93f36293f8b19fbce009fdc68c7f7665cb93e7f37967307e8bd00000000c4483045022100b290e43343728d28dade75719450c8ff338e1431cb51ab05d47e79d76883a16102203f1c493923ed576d7f877470f8be0cc6690f3efe60869346caacd73b0b7d9e9001210399985zb8b14d4e466b89cb2f894c9b24f9c4d9f1fa8585634319ab17bd340ab4514c5663036f1915b17576a914dd4dbb870eeded2f9d4ad18588a470804258185088ac6776a9145779a2aa6ca981f478f6ad18a87e71225558d8d688ad82012188a9149ef2a00e90f13175e306db6d42b60e6c8411869d8768feffffff0181626a94000000001976a9142429537ff322fb00c37cc79aa7a2a1eab3e90dcb88ac6f191500
    
    and
    01000000014adf54bf3256d7ca69570cf2af50c7c2b23de75ceb29788b9bfbbdfdc49fc58100000000e6210216d45a58aadad62fd4b910a2b855434d1d2f2d64a9e08df5bc25503e76f7b46f48304502210090449659a2a430ca3a6c817be506e60f1b443903bc45dd91f5f136b94316148402201141a691fcc2a3ebb61887639ce21982dff95176260c8e79ad4e58e122cbe77401210399985ab8b14d4e466b89cb2f894c9b24f9c4d9f1fa8585634319ab17bd340ab4004c56630367e71cb17576a9145779a2aa6ca981f478f6ad18a87e71525558d8d688ac6776a914dd4dbb870eeded2f9d4ad18588a470804258185088ad82012188a9149ef2a00e90f13175e306db6d42b60e6c8411869d8768ffffffff0100bb1f07000000001976a914fb3aabbc7c8c0c581df57bd57625d72228be700588ac00000000
    
  7. Continuing with the example above, assuming the funds which were not refunded were GLC coin, you could attempt to recover them manually by opening the GLC core/native wallet, navigating to the Debug Console, then issuing the command:
    sendrawtransaction <hexstring>
    
    where <hexstring> is the large hexstring following the text, refund transaction for order. If you want to make sure this recovery attempt will work, you could use a blockchain explorer to explore the transaction of your funds being sent out of your wallet. If you see the output of that transaction shows, not yet redeemed then you should be able to redeem those funds via sendrawtransaction <hexstring> using the hexstring found after refund transaction for order.
  8. If it's not possible to refund the funds that were sent out of your wallet, then the counterparty of the transaction has likely already redeemed/spent those funds. In this case you can try to redeem the counterparty's deposit. In the example above, the counterparty's deposit would have been BLOCK, so to redeem it for yourself, open the BLOCK core/native wallet and issue the sendrawtransaction <hexstring> command from that wallet's Debug Console (or from the CLI if using the Command Line Interface). This time, the <hexstring> to use will be the one following the text, redeem counterparty deposit for order.
  9. If you don't have access to the native/core wallet of the coin for which you need to issue a sendrawtransaction command, the easiest way to send the raw transaction to the right blockchain network is to use the xrsendtransaction command. The xrsendtransaction command can be sent through the Blocknet core wallet under Tools->Debug Console of the GUI/Qt Blocknet, or it can be sent from the Blocknet CLI. As long as there is a Service Node on the Blocknet network which offers the XRouter service xrsendtransaction for free for the coin you need it for, you can use xrsendtransaction. For example, to send the transaction hex string to redeem lost GLC in the example above, you would issue the following command in Tools->Debug Console or from Blocknet CLI:

    xrsendtransaction GLC <hexstring>
    
    where <hexstring> would be the large hexstring following the text, refund transaction for order. In other words, it would look like this:
    xrsendtransaction GLC
    010000000139602e86db76a93f36293f8b19fbce009fdc68c7f7665cb93e7f37967307e8bd00000000c4483045022100b290e43343728d28dade75719450c8ff338e1431cb51ab05d47e79d76883a16102203f1c493923ed576d7f877470f8be0cc6690f3efe60869346caacd73b0b7d9e9001210399985zb8b14d4e466b89cb2f894c9b24f9c4d9f1fa8585634319ab17bd340ab4514c5663036f1915b17576a914dd4dbb870eeded2f9d4ad18588a470804258185088ac6776a9145779a2aa6ca981f478f6ad18a87e71225558d8d688ad82012188a9149ef2a00e90f13175e306db6d42b60e6c8411869d8768feffffff0181626a94000000001976a9142429537ff322fb00c37cc79aa7a2a1eab3e90dcb88ac6f191500
    

  10. If it turns out there is no Service Node offering an XRouter service xrsendtransaction for free for the coin you need it for, but the coin is supported by XLite, proceed as follows to issue the sendrawtransaction via curl to the CloudChains daemon:

    1. Open XLite if it's not already open.

    2. Record the necessary details for accessing your coin's XLite wallet as follows:

      1. Navigate to the CloudChains settings directory:

        • Windows:

          C:\Users\[YourUsername]\AppData\CloudChains\settings
          
          Or paste %appdata%\CloudChains\settings into the File Explorer path field.

        • MacOS:

          ~/Library/Application Support/CloudChains/settings
          
          Open Finder and in the program menu select Go > Go to Folder... and enter the above path.

        • Linux:

          ~/.config/CloudChains/settings
          

      2. In a text editor, open the config-<coin>.json file of the coin you want to redeem. For example, if you need to manually redeem BTC, open config-BTC.json in a text editor. It will look something like this:

        {
            "rpcPassword": "8vCaDSpOKJ8ZhJdukZxaU4Z4NGFFDa9mPy1b-ZT6tHA",
            "fee": 0.0001,
            "rpcUsername": "VMvT5inMA0841-458cOxSgz5V0mxJR8J",
            "rpcPort": 8332,
            "feeFlat": true,
            "rpcEnabled": true,
            "addressCount": 40
        }
        

      3. Make a note of the rpcPassword, rpcUsername and rpcPort values in this file. In this example these values are 8vCaDSpOKJ8ZhJdukZxaU4Z4NGFFDa9mPy1b-ZT6tHA, VMvT5inMA0841-458cOxSgz5V0mxJR8J and 8332, respectively.

    3. Open a Terminal window (Mac/Linux) or a Command Prompt (Windows) and issue the following command:

      curl -H "Content-Type: application/json" -d '{"method": "sendrawtransaction", "params": ["hexstring"]}' http://rpcUsername:[email protected]:rpcPort/
      
      where hexstring is the large hexadecimal string mentioned in steps 3-8 above, and rpcUsername, rpcPassword and rpcPort are the values found in step 9->b->iii above.

      For example, using the values from the examples above, the curl command would look like this:

      curl -H "Content-Type: application/json" -d '{"method": "sendrawtransaction", "params": ["010000000139602e86db76a93f36293f8b19fbce009fdc68c7f7665cb93e7f37967307e8bd00000000c4483045022100b290e43343728d28dade75719450c8ff338e1431cb51ab05d47e79d76883a16102203f1c493923ed576d7f877470f8be0cc6690f3efe60869346caacd73b0b7d9e9001210399985zb8b14d4e466b89cb2f894c9b24f9c4d9f1fa8585634319ab17bd340ab4514c5663036f1915b17576a914dd4dbb870eeded2f9d4ad18588a470804258185088ac6776a9145779a2aa6ca981f478f6ad18a87e71225558d8d688ad82012188a9149ef2a00e90f13175e306db6d42b60e6c8411869d8768feffffff0181626a94000000001976a9142429537ff322fb00c37cc79aa7a2a1eab3e90dcb88ac6f191500"]}' http://VMvT5inMA0841-458cOxSgz5V0mxJR8J:[email protected]:8332/
      

      Note, Windows users may need to install curl if it is not already installed.


Clear All Order History, including Stuck Orders

Clear All Order History, including Stuck Orders

There are two cases when you might want to clear all your BlockDX order history:

  1. If you've been placing a lot of orders, for example with a trading bot, the list of orders in the order history file can actually grow to the point where it slows down BlockDX performance.

  2. On rare occasion, an order can get into a "stuck" state where it fails to complete, but cannot be cancelled or deleted through the usual means. The main cause of this situation is when a new coin has been added to BlockDX and improperly configured. (Specifically, the culprit is usually that the FeePerByte value in the XBridge config for the coin is set too low. It should be set by looking in the wallet send function for the recommended fee per byte and then multiplying it by about 2.5.) If you have an order in a "stuck" state like this, the first thing you'll want to do is to recover any funds you might have tied up in the stuck order. For this, the first step is to wait at least 2.5 hours, keeping your Blocknet core wallet, and any wallets involved in the order, open and unlocked. XBridge code will attempt to refund any funds you have committed to a trade for up to 2.5 hours and your only responsibility during this time is to wait and keep all your wallets open and unlocked. Note, Blocknet wallet must remain open and unlocked for 2.5 hours no matter which coins were involved in the transaction because the code which manages the refund currently resides within the Blocknet wallet. If the funds you had committed to the order are not refunded to your wallet after 2.5 hours, redeem your funds the manual way.

  3. Now you're ready to clear your BlockDX order history by renaming the orders.dat file as follows:

    1. Close BlockDX and Blocknet wallet.
    2. Navigate to your data directory:
      • Windows
        C:\Users\[YourUsername]\AppData\Roaming\Blocknet\
        
        Or paste %appdata%\Blocknet\ into the File Explorer path field.
      • MacOS
        ~/Library/Application Support/Blocknet/
        
        Open Finder and in the program menu select Go > Go to Folder... and enter the above path.
      • Linux
        ~/.blocknet/
        
    3. Rename the file, orders.dat in your data directory.
    4. Restart Blocknet wallet and, after it has synced, restart BlockDX.
    Warning: Deleting orders.dat will delete all historical records of orders you've made.

    Instead of renaming orders.dat as instructed above, you can optionally delete it. Renaming is preferable because deleting cannot be undone.


Bug: If you used Generate New Address in BlockDX to generate the address to which the asset you just acquired should be sent, and the trade completed successfully but the asset didn't arrive in XLite as expected, click here for instructions what to do.
  1. Click on Receive in the upper right corner of XLite.
  2. Select the asset which did not arrive in XLite.
  3. Click Generate new address until the address to which the missing asset was sent appears in the Your address box.
XRouter Beta Released! Read more...
Required Wallet Update! View downloads...