I'm adding value to compensate exchange rounding.
For example price have 3 decimals 0.000, I get minimum of this decimals value 0.001 and add this value to zero profit price for buy and subtract from sell profit price.
Rounded value exact 3.481.

You can test rules without risk right now, just use sound instead of order placing.


Zero profit step depends only by price.
Formula is: Price*Fee*2

Hi all.
I have read all new messages.
I understand you want to use rules like "If %INDICATOR_1%<%INDICATOR_2% Then.." and I'll work on it.
First of all I'll make changes to UI to make you able to see what is going on in rules realtime.

Also I'll add Logs tab to see what and when was triggered.

Askit2, thank you for detailed description, I'll make update to better debugging and contact you.
I'll be glad if you will help me to test your examples and we will make it better.

About Cryptsy: I'll add it in upcoming update.
About other exchanges: I have updated base exchange class to make easier add new exchanges, but for now it still takes a time to add and debug each exchange, I'm thinking how to make engine better for easier adding. First of all I want to make it stable and rules working well. So other exchanges will be added later.

Thank you all for bug reports, feedbacks and donations!

PS: I was in Kyiv, was near revolution 8 Km and there was quiet.

Sorry, I was in Kyiv. I'll read all your messages and replay soon.

Спасибо. Подтверждаю баг редактирования.
Бага в расчетах нет. Данные сохраняются но при редактировании не заполняются.
В формуле после сохранения все вычисляется корректно.
Исправлю в следующем обновлении.

I'll work on it, but currently there is no way to wait order executed, or cancel specified order id. I'll implement it on script language, but maybe not on rules.


There is a "indicator" variable is any number displayed in the interface. It can be last price, balance or any other.
You create a rule by selecting one indicator as "IF", then the rule compare values only with selected indicator on every value change or if it don't changing, than half of second interval.
There is "Base value" based on selected indicator what will be compared to current indicator value.

Every time rule enabled/re-enabled than base value store current indicator value.
If you use "Trailing value" option, than base value will store current indicator value when trend goes to another direction too.
So it works this way: IF "Base Value"*6%>"Current Value".

Example of not trailing rule: "If price goes more 5% than sell all":
1) Current price $1000 (base value stored as $1000)
2) Price goes down to $980 (nothink happend)
3) Price goes to $1029 (nothink happend)
4) Price goes $1050 (rule executed)

Example of trailing rule: "If price goes more 5% (trailing) than sell all":
1) Current price $1000 (base value stored as $1000)
2) Price goes down to $980 (base value changed to $980)
3) Price goes to $1029 (rule executed - 980+5%)

Note: you should add fee to trailing value percentage, because it compare exact values.

Soon I'll add "base value" to interface, but there is no space and I need more time to make changes.
And yes, there was bugs in trailing value, they fixed in Bug Fix 4.

Thank you. I'll debug this.

Пока добавление бирж все-еще трудоемкий процесс.
Но в будущем добавлю большинство популярных.


В программе есть понятие "индикатор", это любое число отображаемое в интерфейсе.
Вы создаете правило выбрав один индикатор, далее правило работает по условию только с ним.
Во время включения правила сохраняется текущее значение выбранного индикатора, и последующие изменения индикатора с учетом процентов сравниваются с базовым. Если вы используете трейлинг значение, то если тренд уходит в противоположную сторону - базовый индикатор меняет значение на новое.
Я добавлю отображение базового значения в правила, но там нет места и придется переделать интерфейс, а я хотел быстрее поделиться с вами апдейтом, потому отложыл на потом.


Спасибо, исправил, обновляйтесь.

I'll make pause soon.

You should re-create rules after bugfix #4. Or edit ini file to change ids you want.


I'm thinking about all variants, and I'll make improvements to make rules more flexible.

Обменял 1300$ на Приват24.
Все быстро как обычно, спасибо!

Bugfix #3 released

Critical trailing value bugfix
Fixed my last order buy price
Added Templates, Save/Load for rules
Fixed translations

Thanks for detailed descriptions.
I see there is a bug at "my orders last buy" indicator.
I'll fix it soon.

I want to tell everyone:

Exchanges APIs is not perfect, and many of them have not optimized methods and it cause a lot of traffic.

Reasons that exchanges takes a lot of traffic:

Bitstamp API

Last Trades: can not be limited by last date received, there is only hour and minute. So hour data downloaded every request. So if at last hour happend a lot of transactions, it will takes a lot of traffic.
Order Book: Bitstamp order book can not be limited by count. So every request download all data every time.
Bitstamp Does not allow HTTP gzip compression, so it takes more traffic than other exchanges.

BTC-e API

Last Trades: can not be limited by last date received, they added count limit, but it useles. We need last received date and get only new rows!

Bitfinex

Does not allow HTTP gzip compression, so it takes more traffic than other exchanges.
After every request their server close HTTP connection, it cause big lag often.

Mt.Gox

Order book: can not be limited by count. But this will be not important when I'll release websocket engine.
Mt.Gox Does not allow HTTP gzip compression, so it takes more traffic than other exchanges.

This not optimized methods not only make traffic larger, but it makes exchange works slower.
If you want your favorite exchange works faster, than send report to them for making more optimal methods.
And if I have something missed, or you will get updated info about API, please send to me, and I'll make it better!
Also please note, Order Book requests send only when Order Book tab is visible.
If you want make traffic smaller, than make HttpRequestInterval larger.

My ideal exchange API methods requirements:

Order Book: can set count limit for each asks and bids. So if user will choose small count of depth, it will be not just visual limitation, but received data will be much smaller.
Last Trades: each trade in request result should have timestamp, so we remember last received timestamp and new request will use this value as parameter to prevent receiving already received data.
HTTP gzip compression support: it will cause 5 time lower traffic, and users who have slow internet will receive much faster updates.

Every exchange have minimum amount to trade limitation. For example btc-e minimum values described here: https://btc-e.com/api/3/info


Moved to rules. Now you can create sound notification to any indicator via rules.


Working to fix it now.


Base value saved at same time as rule enabled. So it will be used BASE_VALUE + 0.6%. If trailing enabled and trend goes in another direction, base value is changing.


Of course, this problem caused by three instances. There is minimum interval for bitstamp 600. And your three copies make this interval 200. You should make same interval for all profiles: 600*3=1800 to prevent IP ban.

Also I'm working on two solutions for this situations. I'll make it works even with 100 interval without IP bans. So keep tracking changelog.


You should use QtBitcoinTrader_Mobility.pro instead of Desktop as described in first message of this thread.



Thanks, I'll debug this.


Answered one message below.


If I don't answered for someone message, don't worry, I read all and will debug all situations.
Upcoming update will bring rule detailed explanation and templates. You will be able to share your rule groups and load it from file.

Thanks for your bug reports, donations and support!
Have a nice trade!

This works for me:

All Ok, you updated. I'll fix this message on next update.

Бип переехал в правила, теперь вы можете создавать звуковые оповещения на любое событие.

Какое разрешение монитора и DPI?