User Resources
This page will detail out a ton of user resources that have been created by the community.
Last updated
Was this helpful?
This page will detail out a ton of user resources that have been created by the community.
Last updated
Was this helpful?
Wick Hunter VWAP For Tradingview chart. This will show Percentages Above and Below VWAP which can be used to spot entries and or fine-tune your VWAP settings. You will need to ensure that the Tradingview indicator settings match your bot settings. For example if you are on 15M Vwap Timeframe and 5 VWAP Period on the bot you will need to ensure you are on a 15 Minute Tradingview chart with 5 Period on the indicator. Please see below snippets.
Please note trades occur ONLY with the following conditions being met:
-Price ABOVE your VWAP % Setting for a SHORT Trade or Price BELOW your VWAP % Setting for a Long Trade
AND
-Liquidation occurring with a Liquidation value greater than your Liquidation Size setting.
The indicator will NOT show active liquidations so it is to be used more for reference for where to place VWAPS and to fine-tune vwaps. VWAPS Should be placed wherever the user is comfortable, but it is recommended to have VWAPS set so that you are catching the top for short trades, and bottoms for longs. Not every asset behaves the same, it may be necessary to adjust VWAPS over time.
Multi VWAP Indicator for non TV-premium users. Same premise as above, however it allows multiple VWAP Timeframes to be added to one chart to view multiple VWAP settings at one time.
To add these to your Tradingview chart please go to each script, and then click Add to favorite indicators.
From there, head back to a new Tradingview chart and click Indicators -> Favorites -> VWAP Script.
Once the script is loaded to your chart, be sure to SAVE the chart and you can rename it for ease of use. To rename and save the chart you will have to go to the Manage Chart Layouts dropdown to the left of the Settings tab on the upper right pane of Tradingview.
Any questions about the TV Indicators? Please do not hesitate to contact us on Discord via #support channel.
The PND Sim (Pump "n" Dump Simulator) aims to simulate a runaway trade - that is, a trade that does not have enough retracement for a counter-trend trade to take profit. It takes into account a variety of factors - initial buy %, DCA settings, stop loss, etc. to get an apprximate indication of how much % pump or dump the settings will "tolerate" before being liquidated or getting stopped out. It also shows how much retracement is required for you to exit the trade in profit, for a given % pump or dump.
The usual disclaimers apply - use at your own risk - the results are approximate only, it doesn't model insurance fees, slippage, potential exchange-side API issues under big market moves, whether the bot is allowed to DCA (with low TF settings, the VWAP band may catch up with the price and the bot may not DCA), etc. There may even be mistakes in the calculations (and there have been in the past versions which noone noticed).
This must be used in Excel as Google Sheets will not display it properly. (Soon, I will upload it onto Excel online and replace the link to that, for users that don't have Excel).
Below is a crash course on how to use the tool. If you are fairly comfortable with numbers and charts (perhaps you have STEM background?) this may be quite slow and you may want to just jump right into using the tool. The video is based on an older version, and is applicable to the Binance bot only. There will be a new more structured video, but until then, this is the one to watch.
Most of the inputs for the calculator is just a copy of what you would input into the bot. However, some notes must be made:
[Bybit] Margin Mode: supports cross margin mode only. (Isolated margin mode with high leverage is not recommended as it is easy to get liquidated with a bit of Bybit API lag and slippage.)
[Bybit] Leverage - on cross margin mode, the leverage setting doesn't matter, the input in the bot settings will not do anything (unlike in the Binance bot). Therefore it is essential that the max position size is limited using the total PBs. The actual max leverage is 100 for BTC and 50 for ETH/EOS/XRP but the sim ignores this for simplicity. All reasonable settings should not get anywhere near reaching the limits.
Max Allocation Per Pair: leave this at 100% and manage max allocation using the IPB and total DCA PBs. This setting is redundant as there is only one pair and the top range number of buys can be a fixed number.
---Work in progress---
Adjust settings for each pair you are trading as the volatility for each pair is different.
Keeping the distance between average price and price makes it easier to get out of trades as it reduces the retracement required to TP. But this uses margin faster and brings liquidation closer.
Aggressive DCA: keep the TP within 0.236 fib in the early ranges, and within 0.382 fib in the later ranges.
Loosey goosey DCA: keep the TP within 0.382 fib in the early ranges, and within 0.5 fib in the later ranges.
The fib anchor for the retracement is the VWAP value at the time of initial buy. This is not how fibs are usually used. However, it should be useful when reviewing charts and backtesting with the measure tool.
Alternatively, you can set the VWAP%s to 0%/0% and measure your retracements from the initial buy price.
Try changing the intial buy to 1% then 20%, see how the whole curve moves, and where the stop/liquidation prices move. High IPB makes more money but significantly hampers DCA ability.
Try changing leverage to 2, 3, 4, 5, 6, etc. - on isolated, it moves the liquidation price a lot, and on cross, it will stop making a difference after a certain leverage as liquidation will happen before max position can be taken.
You can duplicate the tabs like so, to keep all your different settings in one workbook:
Ask me some questions!
If after going through the above, you have questions, you can ask me in #settings-chat and tag honeybadger#5768. Please allow some time for me to respond (having a day job and all).
The tool is found here: