DeviaVir / zenbot

Zenbot is a command-line cryptocurrency trading bot using Node.js and MongoDB.
MIT License
8.23k stars 2.04k forks source link

Sticky: Poll: What do you want to see in Zenbot 3.6? #41

Closed carlos8f closed 7 years ago

carlos8f commented 8 years ago

Greetings Zenbot users!

After a gazillion commits over the weekend Zenbot 3.5.x is fairly stable now. However there's much more Zenbot is capable of, and only so much time to implement it. I need help prioritizing!

Please comment below with what features you'd like to see in the next release, 3.6.0.

Cheers, Carlos

grigio commented 8 years ago
grigio commented 8 years ago
grigio commented 8 years ago
itsgarryb commented 8 years ago

If it works properly, this would be great to have.

xangma commented 8 years ago

Definitely this:

I know this is a bit of specific request, but if I wanted to run this on multiple markets on the same exchange, I would set the trade amount to: default trade amount/number of markets. I.e. 3 markets, trade 0.3 of my total each time. This would be to make sure there is enough money in the bank for every market. But this would only work if there were no double buy/sell signals on any single market. This is something I think deserves looking into.

More markets, more trading opportunities, more potential profit?

tehGoti commented 8 years ago

Especially support for EUR trades

BarnumD commented 8 years ago

New indicators such as MACD..

BarnumD commented 8 years ago

Email Text notifications

backenders-game commented 8 years ago

Generic default_trade.js usable with any exchange Guides/documentation how to use it with exchanges other than gdax.

Guides/documentation how to develop and tweak own strategies

JeffUberman commented 8 years ago

This may be a 4.0 or beyond, but I'd like to see 'smart portfolio diversification' across various cryptocurrencies (say, the 5 or 10 with the highest market cap or trading volume) and to intelligently shift portions of --but not entire- allocations to currencies that are deemed more favorable at present, making zenbot more tactical. For example, maybe current portfolio is 55% BTC, 25% ETH, 10% LTC, 10% mix of others...then some news breaks and BTC is on the downtrend (either more risky than an alternative or less of an expected ROI) so zenbot shifts allocation to 30% BTC, 45% ETC, 20% LTC, 5% other.

carlos8f commented 8 years ago

@JeffUberman Zenbot is already capable of that, I am currently using Zenbot 3.5.13 to trade ETH-BTC-USD on GDAX which is similar to what you're describing. It will buy/sell ETH or BTC depending on which is trending at the moment.

totomaze commented 8 years ago

Maybe a repair mode to find gaps in the data (missing data visible in the graph). I may be the only one to see this problem as I am running zenbot on an atom processor with 2gb of ram. The backfill seems ok but the reducer seems to skip some data.

JFD3D commented 8 years ago

A function for monitoring the top 5 or so highest 24 hour volume pairs on any given exchange would be nice :)

What @JeffUberman said is interesting. I haven't had a chance to test this yet so I will just ask, does zenbot currently trade multiple pairs and switch to another alt if for example you are running two scripts, ETH-BTC and LTC-BTC, the ETH-BTC pair is holding BTC and suddenly LTC trend triggers rs.op 'buy' will it will automatically switch to that pair (as in buy LTC)?

It would be awesome to have functionality that would predict pair profitability based on past performance and current trend data and switch to a more profitable currency while taking into account a 24 hour balance (and orderbooks?) to total user balance ratio. If the profitability margin is high enough maybe zenbot could even sell an asset where it stands and immediately buy into the more profitable opportunity. Also triangular arbitrage is fun although it probably lies outside the realm of this project.

In my opinion the more features/strategies/options parameters there are the less likely zenbot will suffer from "dilution syndrome" and lose it's profitability due to everyone using it although this may be more unlikely thanks to zenbrain.

Keep up the good work!

carlos8f commented 8 years ago

@JFD3D yes, in that scenario the bot would buy LTC, as long as the pairs are traded on the same exchange and share the same account balance.

I agree it would be awesome if Zenbot could analyze the entire crypto portfolio for the most profitable things to focus on, this is out of scope for Zenbot 3 though, perhaps in 4 :)

buzztiaan commented 8 years ago

bittrex support ^_^

lyn168 commented 8 years ago

More exchanges: bitstamp, bitfinex, CEXio

wupeng1211 commented 8 years ago

More exchanges: btcc

jltrade commented 8 years ago

bollinger bands please!

totomaze commented 8 years ago

Have a option to prevent buy after buy or sell after sell.

hlboys commented 8 years ago

no error no bug Programs that can be used

michaldev commented 8 years ago

More exchanges or better support for EUR :) Coinbase exchange isn't anonymous. They follow transactions, check id etc. In coinbase person outside the USA can not trade USD. (Only EUR)

carlos8f commented 8 years ago

bump

carlos8f commented 8 years ago

mila

D4rk4 commented 8 years ago

Please add BTC-e.com exchange to zenbot.

JFD3D commented 8 years ago

@carlos8f Yes, pls Mila Kunis in 3.6 :P

totomaze commented 8 years ago

Set the start balance by Asset or by Currency. or Set the first action of the Simulation (start with buy only).

wiscokidd commented 7 years ago

an option to place limit orders instead or market orders to avoid fees.

coinchirp commented 7 years ago

"an option to place limit orders instead or market orders to avoid fees" this 100x over, i was really surprised having only worked with/on HFT bots that this was not an option. Market fees always seem to kill bots over time and this logic applied could save some money, and help increase trading volume more reasonably

kingo55 commented 7 years ago

Poloniex too please!

carlos8f commented 7 years ago

Alas, 3.6 never came, but Zenbot 4 is out, so I'm cleaning up 3.x issues. Please use and test 4, thanks!