Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux]

[ionstorm]

Hi Ighor, do you have any plans on adding Coinsetter support soon? Thanks

I too would love coinsetter implemented and MtGox removed from Qt Trader, here is a link to coinsetters api:
https://www.coinsetter.com/api

Coinsetter allows me to trade on bitstamp without an account there.  Awesome new service imho, pm me if you need help testing beta code, i'll git it
Thnx

[1714205645]

1714205645

[1714205645]

1714205645

[1714205645]

1714205645

[1714205645]

1714205645

[1714205645]

1714205645

[1714205645]

1714205645

[VarDiff]

Just want to say thank you for great application.
Really simple and useful

[aplene]

Thanks so much, it works great...

[3KyNoX]

I'm not sure if someone asks this before but is it possible to trade on LTC Markets (BTCE - OKCOIN) ?

If not, what to change in source code ? globally

Thanks anyway

[ZDILLON]

I'm trying to get these "rules" to work as well.

Trying to say:
"If current price (last, bid or ask) drops 2% from Last Buy price... then Buy 0.01BTC at current price"
"And then also place a sell of 0.01 BTC at 2% Higher than last buy price)

I have this in the rules:
1. If my orders last buy price<2%  bid  0.01BTC  Last Price
2. If my orders last buy price < $1  ask  My Orders Last Buy +2%


So to test this, I bought manually at $566. Which means a 2% drop should be $554
Well the price has dropped to $535 and still no buy order has been placed.

So what am I doing wrong.
I just want to automatically set a buy order at 2% less than my last buy.
(and also a sell at 2% higher... but that is step 2)

[JasperDX7]

I'm trying to get these "rules" to work as well.

Trying to say:
"If current price (last, bid or ask) drops 2% from Last Buy price... then Buy 0.01BTC at current price"
"And then also place a sell of 0.01 BTC at 2% Higher than last buy price)

I have this in the rules:
1. If my orders last buy price<2%  bid  0.01BTC  Last Price
2. If my orders last buy price < $1  ask  My Orders Last Buy +2%


So to test this, I bought manually at $566. Which means a 2% drop should be $554
Well the price has dropped to $535 and still no buy order has been placed.

So what am I doing wrong.
I just want to automatically set a buy order at 2% less than my last buy.
(and also a sell at 2% higher... but that is step 2)

We pretty much all want this and none of us have gotten a straight answer about it lol.

[ZDILLON]

Quote from: ZDILLON on Today at 02:58:13 AM
I'm trying to get these "rules" to work as well.

Trying to say:
"If current price (last, bid or ask) drops 2% from Last Buy price... then Buy 0.01BTC at current price"
"And then also place a sell of 0.01 BTC at 2% Higher than last buy price)

I have this in the rules:
1. If my orders last buy price<2%  bid  0.01BTC  Last Price
2. If my orders last buy price < $1  ask  My Orders Last Buy +2%


So to test this, I bought manually at $566. Which means a 2% drop should be $554
Well the price has dropped to $535 and still no buy order has been placed.

So what am I doing wrong.
I just want to automatically set a buy order at 2% less than my last buy.
(and also a sell at 2% higher... but that is step 2)

We pretty much all want this and none of us have gotten a straight answer about it lol.

Yes I can see that there's a couple of queries about how the syntax works...
It's a shame the rule syntax isn't well explained here, because this would be some awesome software if it could do this.
Just needs to have a rule that says:

If "current price"    "goes less than"     "My Orders Last Buy Price  - (% or fixed amount)"   then "Sell ...."

Eveything is ALMOST there... except for the extra condition to compare current price with my last order price. 

Shouldn't be too hard a job to add that in, right?

[MasterCATZ]

can we please have some sort of data collection

say log

Highest / Lowest price / within a time period
Manually set in either Minutes or Hr

ie)

30 min Highest Price / Lowest Price
1 hr Highest Price / Lowest Price
24 hr Highest Price / Lowest Price
72 hr Highest Price / Lowest Price
168 hr Highest Price / Lowest Price



That way we can make a rule like

If, 24 hr Lowest Price, Goes Less Than, 10%, Spend All my USD, Market Ask Price

Followed by

If, 24 hr Highest Price, Goes More Than, 10%, Sell All my BTC, Market Ask Price

also can we have a % for sell amount

Sell All my BTC
Sell Half my BTC
Sell % my BTC

Spend All my USD
Spend Half my USD
Spend % my USD

Personally I like spreading with 10% or 25% of my Total Balance

Currently the rules will not catch a 600 % drop like $102 day
it will only buy in at a small drop and not be able to sell back to buy in at the very bottom

I normally have 25% of my Balance ready for annual flash crashes

[ZDILLON]

If, 24 hr Highest Price, Goes More Than, 10%, Sell All my BTC, Market Ask Price

What I just don't understand is "Goes More Than, 10%"

10% of what?
If it's current price then what is the tick time? Is it yesterdays low price? Is it price of my buy price? Is it the bid price of 10 minutes ago?
I can't see how these formulas can work without defining the "Goes more than, 10% of........."

[ZDILLON]

So I gave up on the % movements, and just thought I'd set fixed prices to execute buy and sell orders... but they don't seem to process either.
http://i62.tinypic.com/sg1fuw.jpg

Even though Last Price went from 562, 561,560,559... The rule did not execute.
I put the beeps on, and there was beeping... but then turned them off, and there was no ordering.
 
What I'm trying to do is say:
"If price gets to 560.. Put in a buy @ 550, and a sell @ 570"

But then if price goes to 550, Put in a buy @ 540, and a sell @ 560

So I used < and > to stop orders triggering that I don't want in other groups.
(ie, if I say price goes below 560, then...     Then all the groups like 550, 540, 520 etc will all trigger)

Anyone know what is wrong with this rule?

[SomeRandomDude]

Is there a way to get this running on a Raspberry Pi for Linux users that are not that experienced with Linux? (I already couldnt open the .desktop application in Ubuntu, would like to have it running 24/7 on my RPi anyway because it takes less power.)
 
The best solution would be to get it running on the original Raspberry Pi Linux distr. called "Raspbian, Release: "wheezy".
 
Thanks so much!

[b0du1]

Hi IGHOR,

There is new websocket API at Bitstamp...
I hope that with this one trafic will be lower..

https://www.bitstamp.net/websocket/

xx

[m0Ray]

OpenSuSE package available at OBS repo http://download.opensuse.org/repositories/home:/m0Ray
IGHOR, you can include this link to your announcenet, it is permanent.

[Askit2]

So I gave up on the % movements, and just thought I'd set fixed prices to execute buy and sell orders... but they don't seem to process either.


Even though Last Price went from 562, 561,560,559... The rule did not execute.
I put the beeps on, and there was beeping... but then turned them off, and there was no ordering.
 
What I'm trying to do is say:
"If price gets to 560.. Put in a buy @ 550, and a sell @ 570"

But then if price goes to 550, Put in a buy @ 540, and a sell @ 560

So I used < and > to stop orders triggering that I don't want in other groups.
(ie, if I say price goes below 560, then...     Then all the groups like 550, 540, 520 etc will all trigger)

Anyone know what is wrong with this rule?

I would guess the only problem I have had with rules I know that should trigger not triggering when I think they should was related to the delay between executing rules check box being checked. I'm not sure that it stops them entirely but it seems to add a sometimes significant delay. It should delay 5 seconds in that time the rule seems to need to stay true. I'm not sure if that is entirely correct but it seems like what I have noticed.

Hopefully the Last Buy/Sell by % gets working soon.

[IGHOR]

I'm not sure if someone asks this before but is it possible to trade on LTC Markets (BTCE - OKCOIN) ?

If not, what to change in source code ? globally

Thanks anyway

You can trade on BTCE with litecoins, BTC China litecoins support will be added on next update.

can we please have some sort of data collection

Planed to Qt Open Trader.

Is there a way to get this running on a Raspberry Pi for Linux users that are not that experienced with Linux? (I already couldnt open the .desktop application in Ubuntu, would like to have it running 24/7 on my RPi anyway because it takes less power.)
 
The best solution would be to get it running on the original Raspberry Pi Linux distr. called "Raspbian, Release: "wheezy".
 
Thanks so much!

You should find info how to compile Qt 4.8.5 on Raspberry Pi, if it done, you will be able to compile Qt Bitcoin Trader.

Hi IGHOR,

There is new websocket API at Bitstamp...
I hope that with this one trafic will be lower..

https://www.bitstamp.net/websocket/

xx

I'm working on websocket engine, when it done, I'll add websocket support of Bitstamp too.

OpenSuSE package available at OBS repo http://download.opensuse.org/repositories/home:/m0Ray
IGHOR, you can include this link to your announcenet, it is permanent.

Thanks!

I read all messages, and I'll fix this bugs as soon I can.

[elektrax]

To make the rules loop, add a rule that enables all rules in your group at same condition as your buy/sell.

Will try some more stuff and report back, great software.This is even more exiting than the last version. Thanks for new updates again!

I am even willing to pay a % trading fee to the creator once everything is smoothed out, and trading rules becomes almost 100% certain profits with % swings. Just awesome.

[Askit2]

Unless I am entirely wrong the last buy/sell trading indicator seems to only trip if the current buy is at least some percent different then the last buy before the one you just posted. At least on BTCe that's what I noticed.

Using last and greater or less then some % for buy or sell and that does almost exactly what I wanted. Just not the way I was hoping. I do like the idea of some % above or below the last buy or sell. Still it does work with last and limit orders.

[SomeRandomDude]

I got lost while creating a huge load of rules that enabled more rules and groups, which didn't really work in the end as soon as I was working with "when I have less/more btc than 50% do <action>". Somehow the 50% thing didn't work at all for me, didn't trigger once. Tried it with the trailing checkbox too. Same.
 
As far as I understood that right: Trailing is tracing my overall BTC/USD amounts so that a rule doesn't get triggered twice before a different rule for another pricerange.
 
Trading now again with 2 simple rules in just 1 group and nothing more. Works just like in the old version. Even though I have to edit the rules by hand every few hours.
But I would love to have the percent feature work for me. (Mac OS X)
 
I am also sure that it's possible to auto trade (when you have a decent amount of BTC) within any price range without editing rules or touching the trader again for weeks or even months.
For example: Creating a massive amount of rules and groups that trade a specific percentage of BTC/USD within every possible pricerange. 600, 650, 700, 750, 800, 850, 900, 950, 1000 etc.
I think it all depends on a perfect ruleset without _any_ errors at all and a high amount of BTC/USD to trade with. Problem there is (for me): To TEST that, you have to have a high amount of BTC/USD. Any if it goes wrong: well you are going to lose money because of testing. The more priceranges you'd like to autotrade with, the higher is the chance to lose money on testing the rules if there are any logical mistakes made by the trading person.
 
Ighor: I am not experienced enough for Linux to find out how to compile this on my RPi. Even had problems installing 1 or 2 dependencies that you mentioned, which I tried on Ubuntu. These just couldn't be found. (Forgot which one exactly.)
Was just wondering if you have some kind of precompiled version. I'd like to save some computer energy in the first place. Letting this run on a Raspberry Pi is also VERY interesting with the things mentioned above. (Setting up rulesets for never touching/editing the trader again and just let it run. If we see $1500 or $2000 this idea will go to waste, but that might take a while.)

[Buster]

Hi Ighor,

I would like to request a "viewing only" mode, that uses an API pair which only has permissions to view the order book and last trades.
It almost works with v1.07.97, but with an error message "Identification required to access private API" that appears sometimes.

With a "viewing-only" mode, it shouldn't even attempt to access the "trade" and "info" parts of the account, to avoid the error message being triggered.

Thanks

[MasterCATZ]

If, 24 hr Highest Price, Goes More Than, 10%, Sell All my BTC, Market Ask Price

What I just don't understand is "Goes More Than, 10%"

10% of what?
If it's current price then what is the tick time? Is it yesterdays low price? Is it price of my buy price? Is it the bid price of 10 minutes ago?
I can't see how these formulas can work without defining the "Goes more than, 10% of........."

That is why I want it to LOG the Price Range within a time frame
( excluding the current high price )

say if Yesterdays highest price was $700 ( 24 hr ago )
it will sell if it hits $770 today

Currently the % will only work if its achieved in a tick movement as the highest price will just keep going higher but it will have no idea what the target price is

bitcoinwisdom keeps track of opening , highest, lowest , closing prices
I am wanting QT trader to do the same thing

it only needs to log within the specified time frame