Topic: Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux] - page 40. (Read 383536 times)

Thank you. I'll debug this.

Noticed another bug:

When copying the rules "Add Rules Group" > "Copy From Existing Group" does not copy properly.

I get totally different rules copied than in my source rule.

 

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.

IGHOR,

How do you know when you sold 1BTC on (my last bought price) +0.8% to HOLD the NEXT rule?
The moment you create the order, my balance is credited by 1BTC and the NEXT rule can not us the BTC balans as a reference.

As the money you get for this sell is always different or in multiple parts from multiple micro-sells, I don't find a rule to generate this pause.

V1.07.97 Bugfix 3 It looks like none of my rules are being enabled by the commands. Either they got renumbered or the command is failing to re-enable them. Since all the text boxes for the rules have the number 9 in them without regard for what the group number was when created it is very difficult to re-enable them if the numbers have changed.  Enable all rules in current group works just perfectly though.

2 Possible ideas. 1 make the group ID editable or have the box pull up the actual ID.

When I noticed the problem in the last version bugfix 2 I started naming rules with the ID then a name so as an example 33 wait for up.

All in all the % above or below the last sell or buy would be sweet if it worked properly. Without the rules being able to enable each other it would be more difficult to control what actions I want run at what time.

Thank You!
The software really is awesome. I know you work very hard on it. It is just about perfect. When the rules do work it works really well.

You are looking for Total to Buy at market price to be either = or > 1.

You then want BTC Balance More or Less by 0.1

Those should work. Though there is likely a better way if you look farther into it.

Hi,

Still a virgin. I have scrolled all 44 pages of the this tread, but I must be missing something.

I would like to trade at markt price and sell 1% above and wait and buy again at markt price in a loop.

-If I place a buy order on market price, this will be created, BUT I want the bot to wait until this order is filled in BEFORE it moves to the sell order.

How can I do that? As my dollars & BTC will change constantly, I can not create a rule in relation with it.

I would also be nice to have a pause rule, 1 sec - 3600 sec.

execute immediately  bid B0.1 last price
>>wait until B0.1 is bought
execute immediately ask B0.1 My orders Last buy +1.0%
>>wait until B0.1 is sold
>>pause for 60 sec
if BTC balance goes more than B0.01 enable group #3 Not used not used

Cool, when can this be fixed? I just checked the latest update but it appears I still cant do what I'm asking .

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'm still confused.

ok so if I buy at $500 then that means the BASE_VALUE is $500 right? So the above statement (without trailing) just adds 0.6% to $500 which makes it $503. What is it comparing that $503 to though (ask, bid)? The statement seems incomplete. I want to sell or buy when the current (ask/bid) price is 0.6% more or less than my last buy price.

This is how I'd like to see it.

ask = 620
bid = 615


If market bid price > .6% of my orders last buy price (plus exchange fee) sell amount .01BTC at Market bid Price
if 615 > 606+.02%fee sell .01BTC at 615


If market ask price < .6% of my orders last sell price (plus exchange fee) buy amount .01BTC at Market Ask Price
if 620 < 615+.02% buy .01BTC at 620

Ok, thanks...

I will send link of this conversation to Bitstamp and ask them to do something about it...

xx

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!

Hi

I have problem with downloading speed from Bitstamp. It is 300 kb/s what is 30GB Daily.
Download speed from BTC-e is OK.

Is this normal?

Thanks...

EDIT: I changed API key...now is OK

EDIT2: It was good for some time and it is high again...

Hello,
I am at a loss on the new % feature. It seems like the best idea ever. I can finally make the bot think semi-profitably. I have a rule to buy based on last selling price. I was sure that (if I understand it correctly) if last sell price > 1% should start a trade when ? ? ? ? ? goes about 1% below the last sell price. I had them both ways and greater than seems to buy below.

I have noticed a few things. Not all are terribly helpful mind you. I also have 2 stop loss rules. One setup for larger down trends. One for prolonged up trends. Both use trailing so I want them to wait until the number is opposite of my other strategy. I think anyways.

Why I wonder if its working. I have repeatedly noticed a number well under the price of the last sell or well above the price of the last buy. The bot has done no selling or buying as would be required based on the rules. I have also noticed If I force a sell sometimes down 60$ on a 300$ basis the bot will start trading again. As an example my last sell was at 309, no buys down to 245. I am pretty sure that is more then 1%. Of course I could be actually messing it up and it needs 99%. Unsure on that part as it normally did trade around a 1% range. Possibly some issue is either price is based off last price (MtGOX is not great at sane last prices). Or I have messed up where I want it to trade and it was really sometimes waiting for 309-3.09 I am unsure.

If I might suggest a "feature" unless it already does could you set the bot up to use the value you select in the far right box as its measurement. So say I select Ask price could we compare the last sell against the current ask price? I suppose it could cause some issues though.

Thank You for the great bot. If I ever manage to make money I will donate I promise!

Aaahhh...run nasd through padsp does it.

Great thanks

Thanks for the tip

sudo padsp nasd -local -b

plays wav files for me but "beep" still make just a crackling pop

tried loop:
    
      if market last price threshold $0.10 play wav
      enable all rules

seems that it triggers just once and stops the loop - just shows processing afterwards but:

     if market last price threshold %0.01 play wav
     enable all rules

works fine so it must be somthing with $ part..


  

Apparently routing audio to padsp is a way to get sound from OSS apps.

eg.  pacat /dev/urandom > padsp

Is there any way of tricking ubuntu to route audio from /dev/dsp to padsp?

padsp QtBitcoinTrader doesn't work.

Great software...just can't test out rules etc... until I can get audio working (Xubuntu 12.10)

Cheers.

K