Quote from: JasperDX7 on December 03, 2013, 12:44:11 AM

Quote from: IGHOR on December 02, 2013, 07:10:24 PM

Quote from: JasperDX7 on November 30, 2013, 05:19:29 AM

@IGHOR - have you looked into how btcrobot does their auto trading? I think this video gives a general idea. I'm not sure if it does anything else behind the scenes but it seems like something you could easily implement into your bot. http://www.youtube.com/watch?feature=player_detailpage&v=hopbhC4OKtU#t=80

Also, thanks for making this bot open source and free. I'm hoping to donate some coin your way once I start actually making some haha.

You will be able to do this on Qt Open Trader.
Currently multi exchange monitoring is not supported due high API load.

Any idea on when Qt Open Trader will be released?

I think one solution for the high API load would be to reduce the number of checks. From what I can gather you're doing everything in real time right? For multi exchange monitoring why not set a timeout that the user can change in options? Set it so that if multi exchange monitoring is on, only check both exchanges every 10+ seconds by default instead of real time.

Will the next version have auto trading support for EMA(10) and EMA(21) signals?

Also, tossing another idea your way. An experimental price dip detector would be an excellent feature to add. You could probably bake this into your current rule set so users can easily adjust the values to their liking. Here goes how I envision it, have the bot check the price, if it's 30+ points lower than the last market price then trigger a dip alert and buy however many coins the user wants (this would also have to be added into options). Another option would be to sell if the price raises 30+ points (another value that the user can change) from the price you bought at. An option to limit how many times the dip alert can be triggered would be needed to prevent multiple buys if the value drops more after the first buy. To prevent confusion you'd have to save multiple "sell" points just in case the market takes a large dump. See example.

Example 1.
Options that are set
max number of dip buys = 2 (Number of buy ins when a dip is detected.)
dip drop value = 30 (When a dip should be detected)
dip raise value = 30 (When a raise should be detected)
Amount to trade = 1 (this value will be used for all currencies BTC, LTC, NMC..etc)

1) Last market price was 1btc = $1080
2) Current price is 1btc = $1050 (went down 30 points triggers first dip buy alert)
3) Bot: buy 1btc at $1050 (Bot saves this value in local database as dip1=1050)
4) Current price is now 1btc = $1020 (went down another 30 based off of the previous buy price you made (ie. $1050), triggers second dip buy alert)
5) Bot: buy 1btc at $1020 (Bot saves this value in local database as dip2=1020)
6) Current Price is now 1btc = $990 (Went down a third time by 30 but because we have "max number of dip buys" set to 2, the bot will do nothing)
7) Current price is now 1btc = $1085 (Which is 30 points more than dip 1 ($1050) and dip 2 ($1020), this triggers a dip sell alert for both previous dip buys)
Cool

Bot: sells 2btc at $1085 ($65 profit, both dips where sold so we remove them from the local database and return to the first step of watching the last market price).

Example 2.
Options that are set
max number of dip buys = 2 (Number of buy ins when a dip is detected.)
dip drop value = 30 (When a dip should be detected)
dip raise value = 30 (When a raise should be detected)
Amount to trade = 1 (this value will be used for all currencies BTC, LTC, NMC..etc)

1) Last price was 1btc = $1080
2) Current price is 1btc = $1050 (went down 30 points triggers first dip buy alert)
3) Bot: buy 1btc at $1050 (Bot saves this value in local database as dip1=1050)
4) Current price is now 1btc = $1020 (went down another 30 based off of the previous buy price you made (ie. $1050), triggers second dip buy alert)
5) Bot: buy 1btc at $1020 (Bot saves this value in local database as dip2=1020)
6) Current Price is now 1btc = $1050 (Went up by 30 for dip2, this triggers a dip sell alert)
7) Bot Sells 1btc at $1050 ($30 profit, bot removes dip2=1020 from the local database. Now only dip1=1050 is there.)
8 ) Current price is now $1000 (triggers a buy order since it's more than 30 points different from dip1's value of 1050).
9) Bot: buy 1btc at $1000 (saves to local database as dip2=1000)
10) Current price is now 1btc = $1085 (Which is 30 points more than dip 1 ($1050) and dip 2 ($1000), this triggers a dip sell alert for both previous dip buys)
11) Bot: sells 2btc at $1085 ($120 profit, both dips where sold so we remove them from the local database and return to the first step of watching the last market price).

I think I'll tell you right release date within 1 month.
Thanks for detailed information. I'll explore the ways to implement this.
Also in Qt Open Trader you will be able to program your own indicator.

Quote from: ellard on December 03, 2013, 09:21:00 AM

Any compile howto available for windows? Compile for linux is simple.
The interface gui is different and code seems different from git linux to beta 1.0.7.95 src windows.
Nice program.

Any idea what metatrader uses for timing for receiving data? It appears to be real time or close to it without the constant downloading of data. Two different systems so it may not relate.

Just open pro file via Qt Creator and compile.
Same code for all OS.
Realtime data streaming planted to Qt Open Trader.

Quote from: Netprofits on December 03, 2013, 03:13:53 PM

IGHOR, You will definitely receive a contribution from me for this excellent app! I have been using it for only a month or so and absolutely love it.

I am having an issue with Bitstamp however. I tried creating a new API and used Notepad to C&P the info. I am not sure where to go from here.

http://imgur.com/pzc2uW4

Any assistance would be appreciated.

Regards

Send me debug file to my email (from about window). And I'll fix this or tell you hot to fix this.