-
Notifications
You must be signed in to change notification settings - Fork 0
Configurations Explained
Set to either true or false to enable or disable paper trading. Paper trading is 'pretend' trading that allows you to test your strategies without having to risk your crypto.
If this is changed from 'True' to 'False' or vice-versa Bearpuncher must be restarted for the change to take effect.
This setting determines how much you want Bearpuncher to trade with if Paper Trading is enabled. If my Market is set to 'ETH' and I set Paper_Balance to 100 then it will act as if it has 100 ETH to trade with.
This determines what base currency you will be using to trade. Valid options are ETH, BTC, and USDT.
The indicators you want to use in your trading strategy.
See Strategy Setup for more information.
Set to True to enable the bot, or False to disable it.
Set to True to disable buying new pairs, or False to set bot to buy/sell normally.
Candle period defines how long each candle is, valid options are 1m, 5m, 15m, 30m, 1h, 2h, 4h, 1d, 1w.
If this is changed Bearpuncher must be restarted for the change to take effect.
This should be 0.019 if you're trading against ETH, or 0.0019 if you're trading against BTC.
The max amount of trades you want to have open at any one time. If this is set to '10' then once 10 pairs are being held the bot will stop buying more new pairs, but WILL continue to DCA on currently held pairs.
List of pairs you do not want the bot to trade. List the pairs separated by commas as seen here: Syntax: BNBETH, BNBUSDT, BCNETH, BCNBTC
An alternative to blacklisting. If you'd rather trade only a few pairs simply add them to the whitelist and the bot will trade ONLY those pairs. Unless you're intending to whitelist make sure this is set to ALL.
The port you will access the bot on. If it's set to '5000' then you would navigate to your.server.ip:5000 in your web browser to access the bot.
This can be set to Debug, Info, or Critical.
Debug - Verbose logging. Set this if you want to see everything. WARNING: This will result in a very large log file!
Info- Market info logging, buy/sell logging. This information can all be seen through the web interface as well.
WARN - Minimal logging. Only errors that cause a crash will be logged. Recommended
This sets the maximum amount a coin can be up over the past 24H. Let's say it's set to '10'. This would mean if a pair is up over 10% in the past 24 hours the bot would not buy it.
This sets the maximum amount a coin can be down over the past 24H. Setting it to -10 would mean that if a pair is down more than 10% in 24 hours the bot would not buy it.
Set this to disable buying if ETH/BTC/USDT (whichever you're using) is up over x% in the past hour.
Set this to disable buying if ETH/BTC/USDT is up over x% in the past 24 hours.
Set this to disable buying if the overall crypto market is down more than x% over the past 24 hours. Set this to a negative value (-1 for 1% down)
This sets how much ETH/BTC/USDT you want to spend when initially purchasing a pair.
The bot will stop buying new pairs once this balance is reached. Setting this appropriately is important to make sure you have remaining balance to DCA with.
Sets a minimum 24 hour trade volume filter. Example: We set 'Min_Volume = 500' - the bot will now only buy pairs that have 500 or greater 24 hour trade volume, blacklisting anything with less than that.
Sets the minimum price per coin the bot will buy it. If it's set to 0.00000005 then it won't buy a coin that's 0.00000004 in price.
BearPunchTrader works using 'condition groups', each condition group is defined by buy_condition = condition1, condition2, etc
There are 2 general types of conditions - comparison operators and cross conditions
A Comparison operator is structured as: Indicator - Operator - Number or Indicator A syntax example would be RSI < 40 to indicate RSI less than 40. Another example would be MFI_24 for Money Flow Index over 24 hour period. Usage: MFI_24 < 35
RSI < 40 would make the bot start looking for buys when the RSI value of a pair is below 40 The example above is using a default RSI time period, to use a 12 period RSI you would enter
RSI_12 < 40Now we can leave it at this or we can add more conditions to this 'condition group'
For example one might use:
buy_condition = RSI_12 < 40, RSI_CHANGE > 1
This will look for buys when RSI is less than 40 AND the RSI change since the last candle (or n lookback candles) is greater than 1, this may indicate a 'reversion' of momentum.
You can add as many conditions here as you'd like.
Note: candlestick patterns are evaluated in this form, CDLDOJISTAR > 0 would indicate a DOJISTAR, and a CDLDOJISTAR < 0 would indicate an inverted DOJISTAR
The second type of condition is a cross condition, denoted as CROSS_UP or CROSS_DOWN, there are many strategy possibilities here.
For example we could use:
buy_condition = RSI CROSS_UP 20 to buy when RSI crosses above 20 You could also do 2 indicators, MA_12 CROSS UP MA_24
Now say we want more than one condition group.
Let's use the first example:
buy_condition = RSI < 40, RSI_CHANGE > 1
buy_condition_1 = RSI CROSS_UP 20
This will look for buys when (RSI < 40 AND RSI_CHANGE > 1) OR (RSI CROSS_UP 20)
This is not a strategy recommendation, it is simply an example.
You can add as many condition groups as you'd like, the first one has to be just buy_condition and every one after that just needs a unique number or letter at the end like buy_condition_1 and then also use the second set of conditions (these same options will be applied to sell_conditions next update)
Trailing buy looks for a price bottom once your buy conditions are met then performs a buy when it begins to come back up by the amount you have set Trailing_Value_Buy to.
Example: All of your buy indicator conditions are true. You have trailing_value_buy = .1 - the bot will now follow the price of a pair down further until it begins to correct back up by .1%.
This setting also affects DCA. Let's assume your DCA trigger is -3 and your trailing_value_buy is .25 for this example
Example: Pair dips to -3%, the bot begins trailing. Pair drops to -4%, still trailing. Pair comes up to -3.75% - trigger and trailing conditions have been met so the bot triggers a buy.
Spread is the % difference between the ask and the bid.
A value of 1 will not buy if there is more than a 1% gap between ask and bid.
The minimum number of days a coin must be listed on the Exchange before the bot will buy it. This is used to avoid buying coins right as they are listed.
Set to True to enable selling of pairs, or False to disable selling.
The percent profit to trigger a sell at. Sell_Value = 1 would sell when the pair was at 1% profit.
The percent at which the bot will force a sell regardless of trailing. This is helpful for triggering a sell when something is pumped and then quickly dumped 5-10% by a single large sell preventing trailing from triggering until after that 5-10% sell.
Trailing sell looks for a price top once your sell conditions are met then follows it up x %.
Example: All of your sell indicator conditions are true. You have trailing_sell_value = .1, and the price on a pair has increased to 1% profit, the bot will now wait for the price to increase further until corrects back down by .1%
The negative percentage at which the bot will sell a pair to avoid further losses.
True to enable DCA, False to disable it.
This works the same as buy_condition. If you don't want it to meet any conditions to DCA other than DCA trigger, delete this line. Just like buy condition you can have as many groups as desired DCA_buy_condition, DCA_buy_condition_1, ... DCA_buy_condition_n
This is negative percent at which the bot will double down. If it's set to '-3' then the bot will double down when a pair reaches -3%.
The minimum balance at which the bot will continue to DCA. If your balance dips below this number the bot will stop DCA'ing.
The max number of times you want the bot to double down on any given pair.
The amount of time in minutes the bot will wait before doubling down again, assuming the DCA conditions are met.