Disclaimer

DEXBOT IS NOT A RISK-FREE ENDEAVOR AND ANY TRADING BOT CARRIES SIGNIFICANT RISK. THE DEXBOT TEAM DO NOT GIVE TRADING ADVICE AND RELY ON USERS TO DO THEIR OWN RESEARCH AND EVALUATE THE RISKS BEFORE PARTICIPATING IN THE PROJECT OR USING ANY PRODUCT FUNDED, CREATED, OR MENTIONED BY THE DEXBOT TEAM.

Progress since last report

Last report here

• 2018-05-23 Staggered Orders strategy released
• 2018-05-22 documentation for the Staggered Orders strategy created
• 2018-05-21 user-documentation for DEXBot’s version of Relative Orders and it’s configuration options created
• 2018-05-20 feature to display latest log message for each worker separately, plus improved logging
• 2018-05-18 center price calculation method improved to return exactly “same” result regardless of which way the market is looked at.
• 2018-05-14 failure method changed to soft-failure; allowing the bot to retry failed operation a few times before admitting failure.
• 2018-05-14 Relative Orders strategy logic changed to reset orders only once one or both orders are completely filled. Previously even a partial fill triggered reset
• 2018-05-14 ihaywood adds code to track down a specific bug occurring only on some machines (not developers machines, which makes it hard)
• 2015-05-09 Add exception to exception in worker.py. It should make workers crash less.
• 2015-05-08 improved error logging for more information for tracking bugs.
• 2018-05-04 automatic center price offset based on asset balances added to Relative Orders
• 2018-05-03 difficult bug which caused the bot to halt when an order was canceled found and fixed. The common error message was “Object cannot be found”
• 2018-05-02 several minor bugs fixed
• 2018-05-01 node latency measurement and indicator added to gui
• 2018-04-26 bug with cancelling earlier orders after editing worker parameters fixed
• 2018-04-26 bug crashing the bot when editing worker name fixed
• 2018-04-25 bug intermittently causing errors in buy/sell operations located and fixed
• 2018-04-23 svdevx creates docker image of DEXBot with remote desktop for easy deployment in the cloud
• 2018-04-23 ihaywood delivers code for controlling the bot via chat messages. Code waiting for merge
• 2018-04-22 orelmely publishes two articles about DEXBot in Spanish
• 2018-04-21 permie presents DEXBot on the BitShares Open Source hangout
• 2018-04-21 Python library causing extreme slowness on Windows found and fixed
• 2018-04-20 don_gabriel shows how to use monit and telegram to monitor DEXBot remotely
• 2018-04-20 Several articles and guides created by crypto-kong on how to set up a Worker
• 2018-04-17 fixed problem where orders are filled just before they are cancelled, which confused the bot. Now if cancel orders aren’t confirmed when done in a batch (faster and cheaper), they are cancelled separately (slower and cost more).
• 2018-04-16 opt-in statistics collection tool for monitoring the liquidity provided with DEXBot
• 2018-04-16 Community votes for Staggered Orders strategy as the next improvement
• 2018-04-13 Arch Linux package created so you can install DEXBot with the native package management
• 2018-04-13 Directory structure changed to better suit standards
• 2018-04-11 Relative Order Size feature
• 2018-04-11 Slider fixed to show strategy balance properly
• 2018-04-09 Windows fix
• 2018-04-09 Fix for Linux machines with Intel graphics
• 2018-04-06 Save logfile of all actions of dexbot gui and cli

For a detailed list of code commits look here

This is the Staggered Orders strategy configuration dialog

This is not an extensive list. Work has been done on the website, on public relations / marketing, user support, community engagement, etc. DEXBot, and thus BitShares, is beginning to be noticed by other communities, even by pretty unrelated ones. Although the main responsibility for the work lies with the contractor, Codaone, much work has been done by volunteers, for which we are grateful.

Money spent

• $9940 spent on development work
• $1150 spent on project management related work
• $1000 spent on PR, including domain, server, and work on website
• $0 spent on UX.

We are currently $22,678 under our budget, some of which will be spent in a few days to pay for the last few weeks of work. For more details on spent money, please contact me or have a look at the worker account: dexbot-worker-escrow

What's next

As usual, critical bugs always take precedence.

Features and enhancements will be developed in accordance to community voting. We will constantly have voting open for the next feature to be implemented. We think this is a great way of having the community involved, and to make sure we make progress that is meaningful and beneficial to the community.

We are also trying to improve our "Open Source workflow" -whatever you call it- to make it easier and a more pleasant experience to contribute to the development. From now on we will always prioritize pull-requests over development work in order to maximally benefit from, and include, voluntary work. This will also serve to prepare the project to an eventual handover to the community once the Worker expires. There are a few pull-requests that have been waiting since the beginning, and these will be processed next. They will improve the flexibility of the software and improve development efficiency.

Guides, articles, documentation, and website will continue to be worked on. We intend to create a good complete experience to the user, which is much more than just the software.

Conclusion

The DEXBot multisig escrow team (which we call the dexbot cabinet), consists of the members: @Permie, @MarkoPaasila, @Kimchiking, Cryptick, Taconator

DEXBot is an approved BitShares Worker Proposal receiving funding equivalent to $667 per day to build an open-source and simple to use trading bot to help provide liquidity to the DEX. Liquidity is the life-blood of an exchange and we believe that a widely distributed trading bot will help crowd-source the provision of liquidity.

The DEXBOT team welcomes any new developer talent to continue colloborating on this open-source project.

Join the conversation with Telegram in our “DEXBot” channel

Visit dexbot.info

There are still bugs, and DEXBOT is by no means a finished product but it is ready for user testing. It is available to install on all computer operating systems. The bot has two strategies to choose from, and it can run 10 "workers" simultaneously in the gui. Make sure to check out the website and github wiki for more information.