adelorenzo/stable
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix some stoploss documentation

Browse Source
This commit is contained in:
xmatthias 2018-06-26 20:26:28 +02:00
parent 257e1847b1
commit 9ac3c559b6
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/stoploss.md
View File

@ -1,11 +1,9 @@
# Stop Loss support # Stop Loss support
at this stage the bot contains the following stoploss support modes: At this stage the bot contains the following stoploss support modes:
1. static stop loss, defined in either the strategy or configuration 1. static stop loss, defined in either the strategy or configuration
2. trailing stop loss, defined in the configuration 2. trailing stop loss, defined in the configuration
3. trailing stop loss, custom positive loss, defined in configuration 3. trailing stop loss, custom positive loss, defined in configuration
## Static Stop Loss ## Static Stop Loss
@ -16,35 +14,37 @@ will overwrite the strategy definition. This will basically try to sell your ass
## Trail Stop Loss ## Trail Stop Loss
The initial value for this stop loss, is defined in your strategy or configuration. Just as you would define your Stop Loss normally. The initial value for this stop loss, is defined in your strategy or configuration. Just as you would define your Stop Loss normally.
To enable this Feauture all you have to do, is to define the configuration element: To enable this Feauture all you have to do is to define the configuration element:
``` ``` json
"trailing_stop" : True "trailing_stop" : True
``` ```
This will now actiave an algorithm, whihch automatically moves up your stop loss, every time the price of your asset increases.
This will now activate an algorithm, which automatically moves your stop loss up every time the price of your asset increases.
For example, simplified math, For example, simplified math,
* you buy an asset at a price of 100$ * you buy an asset at a price of 100$
* your stop loss is defined at 2% * your stop loss is defined at 2%
* which means your stop loss, gets triggered once your asset dropped below 98$ * which means your stop loss, gets triggered once your asset dropped below 98$
* assuming your asset now increases in proce to 102$ * assuming your asset now increases to 102$
* your stop loss, will now be 2% of 102$ or 99.96$ * your stop loss, will now be 2% of 102$ or 99.96$
* now your asset drops in value to 101$, your stop loss, will still be 99.96$ * now your asset drops in value to 101$, your stop loss, will still be 99.96$
basically what this means, is that your stop loss will be adjusted to be always be 2% of the highest observed price basically what this means is that your stop loss will be adjusted to be always be 2% of the highest observed price
### Custom positive loss ### Custom positive loss
due to demand, it is possible to have a default stop loss, when you are in the red with your buy, but once your buy turns positive, Due to demand, it is possible to have a default stop loss, when you are in the red with your buy, but once your buy turns positive,
the system will utilize a new stop loss, which can be a different value. For example your default stop loss is 5%, but once you are in the the system will utilize a new stop loss, which can be a different value. For example your default stop loss is 5%, but once you are in the
black, it will be changed to be only a 1% stop loss black, it will be changed to be only a 1% stop loss
this can be configured in the main configuration file, the following way: this can be configured in the main configuration file, the following way:
``` ``` json
"trailing_stop": { "trailing_stop": {
"positive" : 0.01 "positive" : 0.01
}, },
``` ```
The 0.01 would translate to a 1% stop loss, once you hit profit. The 0.01 would translate to a 1% stop loss, once you hit profit.