Home

Welcome to the DEXBot wiki!

DEXBot is a Market Making Bot funded by a BitShares Worker. The purpose of the bot is to allow anyone to easily provide liquidity in any market in the BitShares Decentralized Exchange, the DEX. The software will be as easy to use as possible. There will be conservative and sane defaults for anyone to get easily started. Rather than simply holding, users can put their assets to work - adding value to the DEX - and hopefully doing so profitably. Of course no profit can be promised.

The goal of the project is to increase liquidity in the DEX and also increase the appeal of BitShares by providing more use-cases to the common cryptocurrency holder.

Since the bot is funded by the community as a whole the included strategies should increase the value of the whole. Thus, the bot will only include strategies that provide liquidity. Active trading strategies would decrease liquidity, adding value to the bot-operator but not the whole, and should be provided by other bots.

The bot doesn't have to be running non-stop. The placed orders will remain on the books, and once online again the bot will update orders according to strategy. This is intentional, so that any user can make use of the bot on their own laptop.

Usage

At this point the bot contains two strategies:

• Relative Orders, which places a buy order below, and sell order above the supposed center price. It is suitable for established and active markets with enough participants. In inactive and low-participance markets the bot will pretty surely make losses.
• **Staggered Orders, which is for all markets, and especially suitable for bootstrapping markets. It makes profit from volatility, and will make you lose all your money if you use it on a worthless asset.

Contributing

Request a feature

1. Check in issues if someone already has requested the feature
2. Create a new issue where you describe the feature

Report a bug

1. Check in issues if someone already has reported the bug
2. Create a new issue with a descriptive name.
3. Describe how to reproduce the bug. If possible, use images or GIF's.

Participate in development

We pay bounties for issues. Have a look at existing issues and pick any. The issues contain a cost estimate, which can be adjusted if necessary. Issues are prioritized and included in bi-weekly releases as the funding allows. Payments will be made at release.

Other supporting activities

Can you contribute

• documentation?
• UX?
• strategies?
• data analysis?
• graphics?
• infographs?
• videos?
• user help?

Reach out to the project group in Telegram. We are prepared to pay for meaningful contributions.

Development plan

• A new feature-release (minor version) will be made once every two weeks. This will include all new features that are ready.
• A bugfix-release will be made simultaneously. This will not include the new features, but only fix earlier bugs. This is for the more conservative who don't want to risk their money to untested software.
• Features and bugs will be prioritized by "lowest hanging fruit" first.
• The work required for each issue will be estimated and a bounty promised.
• Any person is free to claim a bounty by reserving an issue and providing the required code. Bounties are paid at each milestone.