Appreciate it wiser! That simplicity is exactly what we would like for the users of DNotes Trading Bot.
1) Absolutely, we are working on that now. The next release should be about a week.
2) I agree that would be a cool feature. Importing from an external source could be a source for concern because of all of the variables to be considered. What do you think of a batch bot creation form instead?
3) That could be helpful, though canceling the bot needs to send a cancel request and confirm the order being canceled. For the sake of not flooding the API and getting temporarily throttled/blocked (the API's have limits enforced) from the exchange, it might be best to leave it as individually cancel.
To answer your question, it will the payment page will pop up and display it to the user, suspending bot activity. I do like idea of a warning though, that allows you to pay ahead of time.
I'll work on signature for it, thank you!
Great signature! I added it to my profile. Here are some follow up questions:
1. When a new release comes out, how does that affect the current release, in terms of keeping track of the subscription? The last time you updated I just started all over, but wouldn't want to do that every time. This time I want to preserve all my existing bots
2. There are only 7 variables to import, so I don't think it would be too difficult. There would need to be instructions provided on how the spreadsheet should be laid out and proper formatting for headings, markets, etc. There would also need to be an error message if the file cannot import properly. One way I've seen it done is to provide a template with the first line filled in (that the user could then replace with his own data). The user could also convert the spreadsheet to .csv for importing. I imagine the template with headings and first line would look something like this (but in excel format):
Exchange,Market,Type,BuyAmount,BuyPrice,SellAmount,SellPrice
Bittrex,BTC-ARDR,100.00000000,0.00001410,100.00000000,0.00001430
On a similar note, I haven't personally found a need for it, but it might be nice to also have the ability to export data from any of the bot screens (bots, fulfilled orders, open orders, canceled orders) as well.
A bot batch creation form might be nice if an all out import winds up being too complicated (and if all else fails, would make data entry into the trading bot much easier). The reason I would like an import option is that I first input my bot ideas into a spreadsheet (it's a google doc, actually but could be easily converted into whatever spreadsheet would be necessary for importing), and my spreadsheet has some fields which calculate costs and profits for me. I play with my numbers until I like the results and then I enter them into the DNotes Trading Bot. I'd love to be able to simply import them all so as to not manually enter twice. However, if the batch form allows for certain calculations, that might serve the purpose of the spreadsheet followed by import. Some basic calculations that would be helpful include trading fee calculations, if I want to accumulate the altcoin and start by buying 100 altcoin at low price, then how many altcoins do I need to sell at high price to return the amount of BTC needed for the next buy, or if I'm wanting to accumulate BTC, then how much BTC profit will I make on each cycle. Those are the sorts of questions I have in my spreadsheet formulas. The main variable I have to consider is how much spread do I need to make it all worth it? It would be *nice* to just sell at the top of the ask side and buy at the top of the buy side, but often the spread is so small that you'd pay more in trading fees than you'd earn in churning. The higher the spread the more profit to be made on a single cycle, but too much spread and you don't turn over very often. So... I'm looking for the right balance between adequate spread and likely to cycle frequently, and of course that is going to vary with coin and price, and spreadsheets are really great at figuring those things out.
3. I wonder if a good solution to the flooding issue might be to allow the user to batch cancel or batch reinstate bots, so he does it once and he's done, but have the API communicate this in stages to the exchange. So, let's say I batch cancel 20 bots. For me it's a one or two click thing. But once I'm done, the program tells the exchange to cancel five of them at a time, and then in ten seconds, sends the exchange the command to cancel the next five, and so on until it's done--whatever amount and time interval is needed to not flood the API. For the trading I do, a few seconds or even an entire minute delay isn't going to make a big difference to me. But I'd love to be able to not have to individually cancel 20 bots one right after the other.
With all the above said, I do not know how much complexity these suggestions would add to the program. Since keeping the program simple and straightforward is a priority, let's not compromise that! But I will keep providing feedback based on the user perspective and some of my ideas might really not make things too complicated and instead be really nice features. I can work with the bot as it is now, and that's the important thing. None of these "feature requests" are necessary in the sense that I can't work with the bot without them. We already have a working product, which is awesome.
Appreciate it wiser!
For the update, you should be able to just run the latest version without interruptions to the data. I can foresee some future upgrades requiring a reset though, or unusual situations, but for the most part just open the updated version and you are good to go.
The above might be a good case for having an import/export process, which would also help with batch creation. But I would limit it to text format rather than excel. From my own experience with excel and .net there are far too many variables in formatting, versions, and keeping up with Microsoft.
Of course! Always appreciate the feedback and suggestions.
