Some people are asking how the Bollinger Band's spot order placing works? Here is an explanation.
(...)
Great explanation, thanks Jonathan. By the way, I asked here in the forum and in an e-mail to support, some days ago, a more detailed explanation about the stop loss options, specially the buy one. Since I still didn't get an answer, it may be more interesting to reply here, because it for sure will be useful to others. Thanks. Thanks dbolivar, As for the stop loss. Both the buy and sell side are relative to the last trade. So for the most common stop loss case, the sell side, the percentage you set is relative to the last buy trade that the bot completed. A 5% stop loss will trigger if the price falls 5% below the price the buy trade went through. At that point the stop loss is trigger and the bot sells the same amount to avoid further losses and stops. It is an exact symmetry with the less common buy stop loss. The idea is that after a sell you might want to get back into a particular currency if the price rises. It is also relative and the trigger point is X% above the last sell trade the bot did. If the price continues to rise and triggers the stop loss the bot will buy the designated amount and stop. Best wishes, Jonathan |
|
|
|
Feature request: optionally play sound when bot sells or buys. This way you can switch to leonArdo app and check out what's happening.
We like this one as well! We are already looking into a desktop notification framework. Stay tuned  All the best, Rene |
|
|
|
Hi, i as a "newbie trader" am really really interested on gdax support as it gives me the possibilities to test the bot(s) without great risk of spending my money on trade fees. so i can run and test my strategies with minimalistic gains etc. does it make any sense ? And it has greater volumes than Bittrex or Poloniex. Also Coinbase / GDAX seems to manage still to register new users  all i can dream of is Gdax support + Bitstamp trailing stop or to be more specific a stop with shrinking gap (trail will catch up) (the closer i get to my desired price goal the tighter will be the trail) as bitcoin is very volatile my trail must be bigger than 100-150 euros as this candle "swing" is normal. so example i plan to sell bitcoins when price is about 12 000 so i start the trail from 11 000 with 300 euros then from 11500 trail will be 200 11800 / 100 so my "trail" is never too loose and i can profit even small changes / gains without fear that the sudden fall will eat my profit as "trail" was loose. and leave me with trading fees only. it saves up to 1%. Hi, GDAX is definitely on our list. Spot orders would have fees though, just limit orders on the book (maker) would be fee free. We will also implement further advanced order types over time. It is just all a matter of resource allocation Thanks for your support, Rene |
|
|
|
The past two updates have caused continuous runtime errors on Win10 x64. I can't keep the app running for more than an hour without a crash. No bots running.
Hey, Sorry about the crashes. How many pairs are you using? And are you using the latest upgrade? Are you maybe using Bitdefender on your System? Can you send the log and a description on which exchange and how many pairs you are using to support@marginsoftware.de? All the best, Rene |
|
|
|
|
Some people are asking how the Bollinger Band's spot order placing works? Here is an explanation.
It works like the following. There is a signal trigger line shown in the chart. If you have a Min effective gain set, it can mean the signal threshold is shifted but this is also visualised in the chart so you can see exactly where it is too.
This signal line is triggered when the opposite order book intersects it. That means for a sell signal line the top of the buy side order book has to hit it. The BB bot will then trigger a spot order. But wait, the spot order won’t necessarily go through at the exact price of the trigger. Why? Because the order book does not have infinite depth at that price. In fact the order book is fluid and in constant motion. Therefore by the time the sell spot order (actually a low price limit order as most APIs have no native support for spot orders) lands at the exchange the order book may may retreated back again or indeed advanced to a higher price. If it retreats back the spot order has to overcome the spread and a potentially shallow order book. That can mean a sell order becomes a completed trade at a price that is lower than that indicated by the original sell signal trigger. On the other hand if you are lucky the price will have increased and you will get a better price. There is no way to ensure a specific price with a spot order.
One thing you can do to mitigate the chance of the bot making a loss is to set a higher Min Effective Gain.
All the best,
Jonathan
|
|
|
|
Some nice action by the Bollinger Band bot |
|
|
|
Update patch version 3.7.7 availableSome more bug fixes - Raised log levels for http errors
- Fixed rounding error in Poloniex which prevented spot orders from being placed
- Some log corrections
- Tracking file for firstCurrency/secondCurrency errors
- Completed trades chart can be updated in hindsight. Fixes wrong amounts being shown for once partially filled orders for example on Bittrex
- Global spot order lock preventing two spot orders from being placed at the same time (which is impossible)
- Added fix to avoid that mac-tools windows are hiden when the main window looses focus
Click on the "update available!" link on the leonArdo login screen to download this new version. Jonathan The arm version download file of 0 MB size, please correct it Sorry about that guys. The Arm version is not fully integrated into our continuous integration build process. It might be the morning before we can get a version uploaded again. Best wishes, Jonathan Edit: New Arm version uploaded now. |
|
|
|
Update patch version 3.7.7 availableSome more bug fixes - Raised log levels for http errors
- Fixed rounding error in Poloniex which prevented spot orders from being placed
- Some log corrections
- Tracking file for firstCurrency/secondCurrency errors
- Completed trades chart can be updated in hindsight. Fixes wrong amounts being shown for once partially filled orders for example on Bittrex
- Global spot order lock preventing two spot orders from being placed at the same time (which is impossible)
- Added fix to avoid that mac-tools windows are hiden when the main window looses focus
Click on the "update available!" link on the leonArdo login screen to download this new version. Jonathan
|
|
|
|
OK So, Rene the issue with Poloniex is that the API key MUST have the 8-digit hyphen separation or it will not work It should be copy and paste from the Poloniex website or did they change anything at Poloniex? All the best, Rene |
|
|
|
Hey Rene,
I noticed on the demo that some of the funds would just disappear right after a gain.
This happens in all the exchanges that I have tried.
Thanks, Chris
Hi, could you send on a screenshot and logs to support@marginsoftware.de? All the best, Rene |
|
|
|
Are you saying the tarball version doesn't work on Arch? We didn't plan on updating the "naked" build, but in case the run-leonArdo.sh script doesn't work for you, executing just the binary should be the same as it was when we shipped just said binary. It would also be interesting to know that the wrapper script breaks things on Arch so I can fix it. Christian |
|
|
|
when version 3.7.6 for arm?
update only download version 3.7.5
We have a problem with the arm build server. Will let you know when the new build is ready! Thanks for your patience. All the best, Rene |
|
|
|
Update patch version 3.7.6 available
To accommodate the recent problems with Bittrex we introduced some market related limit recommendations and rolled out a patch where in some situations the stop-loss was causing leonardo to crash.
Click on the "update available!" link on the leonArdo login screen to download this new version.
I'm running the Raspberry arm version. It says update is available, however the version on the website is still 3.7.5. I'm a new user and trying to get some bots working on Bittrex. I've found that they can stop unexpectedly and now after a restart they are all missing. I'll try limiting the pairs, but 5 is not a lot. Being that bittrex does not allow subaccounts, would trading a different exchange, maybe hitbtc work better? I just checked. It shows 3.7.6 on http://marginsoftware.de/downloads.html . Are you sure you don't see it? The arm build will be updated asap. Sorry for the delay! All the best, Rene |
|
|
|
Update patch version 3.7.6 availableTo accommodate the recent problems with Bittrex we introduced some market related limit recommendations of simultaneously opened currency pairs into the product and rolled out a patch where in some situations the stop-loss was causing leonardo to crash. Click on the "update available!" link on the leonArdo login screen to download this new version. - The pair limit is by default set to 20, for bittrex, we set it to 6 to account for the most recent issues
- Increasing the minimum max order age of margin maker for Bittrex to 0.1 (6 minutes) and default value to 0.2 (12 minutes)
- The value is only a "suggestion" so more currency pairs can still be opened even though its not recommended
- Added a visual displays for this feature to the login window and within the product
- Fixed a serious bug that caused the BB-bot's stop-loss mechanism to crash leonArdo
- Fixed bug in HitBTC which caused that Fund data of some currency pairs (mainly XXX/USDT) was missing
- Market orders on HitBTC are now passed correctly and don't show up in the error log anymore
- Only replace a margin maker order, if the new order price deviates from the placed one by more than 0.1%
- Limit call quota for Bittrex to 50 calls per 10 seconds
EDITED Thanks for reporting issues and helping us! All the best, Rene I have pairs up which I'm not trading! So, are you saying to remove them if not planning to use them right now?Can't hurt right now. You can at least try if it improves speed/stability. All the best, Rene |
|
|
|
Hi,
to deal with Bittrex limitations we recommend to not use more than five concurrent pairs atm. We know it is frustrating but we also have to deal with the limitations.
Also when using margin maker on Bittrex please increase the max order age to a least 12 min to avoid too many non filled orders.
And yes we are working on supporting Binance asap.
All the best,
Rene
"not use more than five concurrent pairs " means via bots trading? Manual trading seems does not have such limitation, am I right? correct. It is mostly about the amount of unfilled orders places by the bots. To be sure please also limit current open tabs if possible at the moment to be on the safe side to not run into more polling limits of the exchanges. All the best, Rene |
|
|
|
Update patch version 3.7.6 availableTo accommodate the recent problems with Bittrex we introduced some market related limit recommendations and rolled out a patch where in some situations the stop-loss was causing leonardo to crash. Click on the "update available!" link on the leonArdo login screen to download this new version. - The pair limit is by default set to 20, for bittrex, we set it to 6 to account for the most recent issues
- Increasing the minimum max order age of margin maker for Bittrex to 0.1 (6 minutes) and default value to 0.2 (12 minutes)
- The value is only a "suggestion" so more currency pairs can still be opened even though its not recommended
- Added a visual displays for this feature to the login window and within the product
- Fixed a serious bug that caused the BB-bot's stop-loss mechanism to crash leonArdo
- Fixed bug in HitBTC which caused that Fund data of some currency pairs (mainly XXX/USDT) was missing
- Market orders on HitBTC are now passed correctly and don't show up in the error log anymore
- Only replace a margin maker order, if the new order price deviates from the placed one by more than 0.1%
- Limit call quota for Bittrex to 50 calls per 10 seconds
EDITED Thanks for reporting issues and helping us! All the best, Rene
|
|
|
|
|
Hi,
to deal with Bittrex limitations we recommend to not use more than five concurrent pairs atm. We know it is frustrating but we also have to deal with the limitations.
Also when using margin maker on Bittrex please increase the max order age to a least 12 min to avoid too many non filled orders.
And yes we are working on supporting Binance asap.
All the best,
Rene
|
|
|
|
|
Hi,
just to avoid confusion: When looking at the Bittrex Website the price you bought or sold is stated in the 'actual rate' column.
EDIT: the bid/ask differs as leonardo uses these prices to emulate the spot order. But of course buys from the top of the order book.
All the best,
Rene
|
|
|
|
|
Show Posts
