Javieralv

[Javieralv]

Gunbot v21.4.0 Release Candidate

– Move annoying logs to debug level.

[Javieralv]

Gunbot v21.3.9 Release Candidate

– Compounding MVTS and KEEP_QUOTE in new breakeven function.

[Javieralv]

Gunbot v21.3.8 Release Candidate

– Fix immediate buy at futuresGrid.

[Javieralv]

Gunbot v21.3.7 Release Candidate

-Fix MOC for futuresGrid.

[Javieralv]

Gunbot v21.3.6 Release Candidate

– Fixes an issue that would show duplicate orders at trading history.

– Fix an issue that would calculate wrong ABP in case of partial sells.

– Experimental spotGrid to futures: set “futuresGrid”: true in your strategy or pair override and use this list of settings (adapt values to your needs):

“PERIOD”: “15”,
“TRADING_LIMIT”: “50”,
“MAX_BUY_COUNT”: 20,
“GRID_MULTIPLIER”: 1,
“STOP_AFTER_SELL”: false,
“AUTO_GAIN”: true,
“futuresGrid”: true

– “MAX_OPEN_CONTRACTS”: 1 (expressed in quote balance)

accepts the above MOC ^^

– make EWO swinging on sideways a bit more reactive.

Export config file (without api keys and sensitive data): Go to gui > settings > Export Settings and download a copy of your config.js file without api keys and other sensitive data.

– Autoconfig: performance improvement for using javascript in generic filter types.

– Pair names in main dashboard table now link to chart.

– Fix “unable to set “time” of undefined” error.

[Javieralv]

Gunbot v21.3.5 Release Candidate

– Implement MOC for 1scalper.

– Implement MARKET_BUY and MARKET_SELL for 1scalper, moto, grid, fib, supres.

– Implement proprietary TV indicator strategy: Elliot Waves Oscillator.

Elliot Waves Oscillator is a multi-purpose indicator that is able to signal the following:

– Entry points when crossing zero

– Swing trading when reversion happen

Created a strat that takes advantage of Elliot Waves Oscillator signals and joined it with one of my favourite closing strategies: TENKAN (Conversion line) from Ichimoku

Instructions:

– Set EWO true in futures MM strategy variants.

(in config.js you can manually set “EWO”: true in your strategy or pair override)

It will go LONG when EWO crosses up zero.

It will go SHORT when EWO crosses down zero.

If entry points were triggered by EWO crossing (as above): it will wait for TENKAN like to go above candles body (if LONG) or below candles body (if SHORT) and then will start the ROE scalper in the attempt to catch the max possible profit.

After an initial pump or dump that your bot closed at profit with TENKAN/ROE_SCALPER it is likely to happen a sideway swinging for some time in order for price to retrace/adjust.

During that time EWO will be useful again: the bot tries to catch the swinging by observing EWO and use these top/bottom to enter the trades.

LONG on bottom and then close at simple ROE_SCALPER (because during sideways movements TENKAN is not reliable) or SHORT on top and then close again at simple ROE_SCALPER.

If another breakout happens, EWO would help us again: it would lead toward the zero and we would start again the initial entry points with TENKAN+ROE_SCALPER.

DCA functions:

– It accepts DCA_SPREAD

The logic behind this kind of DCA is similar to TENKAN close:

If the price reverses against our entry point we wait for TENKAN going below candles body (if LONG) and then we DCA (assuming DCA_SPREAD is met).

In case of SHORTs if the price goes up against our entry point, we wait for TENKAN to go above candles body and then we DCA (assuming DCA_SPREAD is met).

Resuming:

1- This strat is able to catch breakouts and enter trades on them.

2.- After the pump/dump we expect sideways: we scalp on those swinging until the next breakout.

3.- We use the power of TENKAN to start ROE scalper or catch the lowest DCA point we can.

– Implement beaxy on error and on close websockets events in the attempt to reconnect if we got disconnected and we are not receiving trading history anymore

– Update tv charting library to v18

Other updates:

– Several fixes for mobile portrait views.

– Add ftx pair list to gui. Get rid of error when trying to fetch huobi pairs. Several small fixes for pair selection for other exchanges.

– Add some extra error handling for writing config.js and autoconfig.json after changes in gui.

– Add autoconfig.json to config backup function. A copy is saved in the /backups folder each time a config change is saved in the gui.

– Fix some tooltip errors.

 

[Javieralv]

Gunbot v21.3.4 Release Candidate

– Patch: some pairs at beaxy are returning wrong amount/price precision.

– Update to some modules in need of security updates: Update to this build.

– Kucoin precision amounts for V2 api users.

– A smoother throttle to ccxt rate limiter.

 

[Javieralv]

Gunbot v21.3.3 Release Candidate

– Fix beaxy orders, beaxy precision for both quantity and price for all pairs, beaxy “Pay with BXY” feature.

[Javieralv]

Hola.

Qué versión estás usando?

[Javieralv]

Gunbot v21.3.2 Release Candidate

– Fix kucoin upgrade broken balances.

[Javieralv]

Gunbot v21.3.1 Release Candidate

– Patch kucoin api version.

– Fix an issue where selected and disabled pair did not get strikethrough font.

[Javieralv]

Hola.

Para poder holdear una altcoin, en tu ejemplo, BNB, deberás usar el parámetro Keep Quote. Podrás encontrarlo en la pestaña Balance de la estrategia, pero aplicará a todos los pares que usen la misma. En tu ejemplo te recomiendo añadir el parámetro Keep Quote en el listado de override, y en Value usar 0.5, en ese caso, cuando venda, siempre guardará 0.5 BNB.

Para cuando se consuman esos BNB, volverá a comprar cuando la cantidad baje del valor que tengas en Min volume to Buy.

 

Saludos.

[Javieralv]

Hi. I made some tests and reserve pile up doesn’t save changes on json files. I will continue checking and I will update you.

 

Thank you.

• This reply was modified 4 years, 11 months ago by Javieralv.

[Javieralv]

Hi! I assume you are using tradingview alerts, and when you created a new alert for a other pair, may be it is wrong.

“needlock” means that the message that you are using in tradingview is not correct.

 

Check pair notation, exchange name, and other characters in alert message.

 

For example, BUY_BINANCE_USDT-BTC

[Javieralv]

Hola, por lo que comentas, simplemente te falta abrir el puerto 5000 (en caso de que ése sea el que estás utilizando para tu bot) .

Básicamente debes abrir el puerto 5000 para conexiones entrantes en tu VPS, de esa forma podrás ingresar desde cualquier ordenador conectado a internet, utilizando la IP de tu VPS y puerto 5000.

Para abrir el puerto 5000 en un VPS con Windows Server 2016:

 

En el menú Inicio , haga clic en Panel de control, en Sistema y seguridad y a continuación, en Firewall de Windows. El Panel de control no está configurado para la vista ‘Categoría’, solo necesita seleccionar Firewall de Windows.

Haga clic en Configuración avanzada.

Haga clic en Reglas de entrada

Haga clic en Nueva regla en la ventana Acciones.

Haga clic en Puerto en la sección Regla de entrada (o inbound)

Haga clic en Next.

En la página Protocolos y puertos, haga clic en TCP.

Seleccione Puertos locales específicos y escriba un valor de 5000.

Haga clic en Next.

En la p†gina Acción, haga clic en Permitir la conexión.

Haga clic en Next.

En la p†gina Perfil, haga clic en las opciones adecuadas para su entorno.

Haga clic en Next.

En la p†gina Nombre, escriba un nombre de Gunbot (TCP en el puerto 5000) .

Haga clic en Finalizar

 

En este momento ya podrá acceder externamente a su bot utilizando la IP de su VPS con el puerto luego de dos puntos, por ejemplo, si su VPS tiene la IP 160.134.63.156, entonces desde su navegador, computadora o aplicación, deber† ingresar la siguiente dirección:

 

160.134.63.156:5000

 

Saludos.

• This reply was modified 5 years, 1 month ago by Javieralv.

[Author]

Posts