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

Sequential runs the first in the list and once it completes moves to the second. Once the second completes the third. And so on

Concurrent will run all rules at the same time or concurrently. Rule 1 or 2 or 3 may execute first. Followed by any other rule. This example assumes 3 rules.

EDIT:
By completes it doesn't mean your money or BTC etc are credited. Just that the buy or sell order is posted or whatever else you may be doing.

Sequence and concurrent what's the differences ?

Gox is dead...

This popped up. I swore It already needed my U_ID but I suppose maybe it didn't.



Hopefully GoX isn't goxxing things up again.

I hope you went to Kyiv for fun not a bad reason.

I really have tried to figure out an answer. Some of my results seem to indicate at least to me that there is a logic error. It could be in my logic. I don't think it is though because the % from last buy/sell works great sometimes. It is just right for what I want it to do. Maybe there is a sanity check to avoid excessively high numbers. Like if I want buy < 1% it usually sells up about 1%. The actual number I have never seen less then 1%. I also have never seen it trigger over 1.5%. If the market moves quickly I suppose it is best not to buy right away. The problem I have is when it does move up a lot it doesn't resume trading by selling (the one not yet triggered) or buying (also not yet triggered on a down day).

I had assumed it was because the last trade had a bad value on it. That lead me to disabling and then re-enabling the rule. That failed.

I then thought maybe since it was requiring 1.2 and hit over 10% the numbers got off a decimal place somewhere. I reduced the %. That worked in a fashion. It would trade and actually at about the expected range but required moving down to ( I changed amounts) 0.006. Suddenly it would trade quickly on basically 0.6% swings. Eventually it started trading too close to the last buy/sell and I went back up to 1.0-1.5% suddenly those worked again.

This lead me to another thought. Maybe the rule required some % change and to be over or under the last buy or sell respectively. I can't verify this easily. I will say it does when range bound work ok. If I notice its up a lot and I enable the sell so that it will start a new range it will not trigger. I can manually sell and (unless my price is wrong) the buy will work once I enable that after the sell completes.

I have added rules to the buy/sell enabling logic to make sure the last trade completes but it seems like occasionally they don't react fast enough. Most of the time they work great.

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

I have tested with less "sane" percentages. at 0.006 it will trade about 0.6% swings. 0.012 I am testing now as each way should pay the fees.

It almost seems like the % isn't being treated as a % but a whole number on last buy/ last sell. I can't say why and likely I am wrong.

EDIT: After the small numbers worked for a few days I started getting trades without enough swing. I am at a loss. Sometimes 1%, 1.2% works and it trades around a price by around 1% or 1.2%. Other times its up 15-20% and it won't sell or down 50% and won't buy. When it trades it does ok. I have no idea why the 1% or so goes on hiatus periodically.  

EDIT 2: Is any code added so that last buy has to be the last action? What I mean is say I buy some and have a sell that manually triggers. Obviously if I disable then re-enable the buy code I have it should use the sell as long as the sell completes. If a buy followed that sell and I disable the buy logic then re-enabled that logic can the bot still get to the last sell. I only ask as I wonder if the last buy/sell has to be the last item to have posted as completed.

Any guidance on the rules using last buy/sell would be awesome. Like what the last buy/sell is compared to and if its ask, bid, or last < last sell or last sell < ask, bid,  last. Either way up from 284 to 348 should have traded only requiring last buy < 1% or I think it should. Unless that only works if the price clears 28401 or some such nonsense. It will not sell below the last buy so it seems that the < > issue isn't backwards. If I reverse them it will make trades where buy is higher then sell. I did that much checking. Still I can't wrap my head around why up a ton it won't sell.

Would love to see the new up and coming Vault Of Satoshi from Canada be included!
Virtex is a dinosaur that need's to die...

Ok It's been a while and I am going to try again. Maybe I didn't ask in a way that translates well. Maybe I wasn't able to convey my problem correctly. I don't know.

2 Questions.

1. If I use the last sell rule and less then and 1% what is the percentage of. By this I know that the bot looks for a drop of in theory only 1% from the last sell, What I don't know and can lose money on is what needs to go down 1% to trigger the rule. If I use ask in the last field (the one on the right) and the price is the last price as an example I have repeatedly seen on MTGoX last prices well over ask or below bid. So lets say I want to buy (bid) some bitcoins. I sold at 112.5$ now down 1% should be 112.5 -1.1125 or 111.3875 or so. My math may be off a bit. Lets say the ask price is at 112 but the last price is shown at 110. If the bot buys my bitcoins because the last price is plenty low but places the order at the ask price I will lose money. Knowing what yardstick I am measuring with helps a lot to avoid it. The only other way to figure it out would be to know precisely when the order triggers and math up what values are low or high enough to trigger the rule then after a lot of them and eliminating all the ones that don't appear every time I should know what one the rule compares to.

2. On percent's with more then and less than are the values based on 100%. They seem to be but I can't tell for sure as the rules that should work the most frequently don't frequently work. In other words is item to compare less then 1% going to trigger when the price is down 1% from where it starts as the trialing stop example shows or is it not based on 100% as my buy back based on last sell shows?

If question #1 was answered I could likely change the value in the final panel or far right panel and have it react the way I desire at least to calculate profitability.

If question #2 is that the % change on last buy/sell should mimic the way the trailing stops work then I would say there is a problem in the calculations.

I am really at a loss. Last sell 152.005, ask 132.2, bid 132.0 last 132 something No buy back. Set  last sell > 0.6% and its WAY BELOW THAT. Seriously everything but the high is way below. Why won't it buy back or sell? I mean I can do the trades manually well enough. I just figured a bot that could take the last price it sold/bought for and adjust by percentage would trade around a price range. I guessed that the >1% was encouraging it to wait for a drop of greater then 1% or increase of > then 1%. I don't understand but I am sure there is something wrong mathematically. It should trade. Disable and re-enable the rule doesn't fix it.

That trade that wouldn't go started at 1.2%. I bumped it down to anything over the fee. Still no trade. At 20$ on a 150$ basis I should be sitting pretty on a bit over 12.5%. Now even off a decimal place it should trade. What I mean is even if it was off by the power of 10 IE my 1.2% was 12% or in the final calculation it was based on a maximum of 10% it should have still traded. It also doesn't buy higher. I am sure I have the greater thens and less thens all correct. I have trailing stops that rely on the market changing direction. They work. These have the opposite sign as I want the market lower for a buy not going up some % to stop me out.

Hopefully some guidance on how to get it to work would be awesome. That or I have to drop % to where it does trade somewhat sanely and watch it like a hawk for correct function. All in all I prefer the % idea as I want to make some amount of money per trade and by dollar gets more profit down low and less up high. It would work but depending on when/if the gox price recovers I could have to adjust it big to take advantage of that too.

IGHOR, what about Kraken integration?

It's already now the best and largest exchange in EUR (well, besides MtGox, which does not count for me), and it's still growing fast.

If I add a new rule the deafult is: If Market price goes more than XY sell amount all my coins at markaet last price -> Rule enabled

Yesterday I accidently sold my whole coins because of this default rule. I bought them back without loss ;-) but it would be more secure if the rule are not enabled by default.

1/ The pause button would be a seperate rule, to play the market more random.
If I create a loop with buy -> sell orders get filled to fast in betweeen two buys. I would set the next buy on 15 minutes.

2/ Making the rules wait until the trade is done would also be very usefull.
You could add a column in the trade window with values like "group II, rule 3" , so we see what order got created by what rule.

grts,

Is it possible to give market orders with this software?

I only found limit orders.

+1  I got no idea what the conditional statement is referring to.

lol I've been trying to get this information out of him for the past 2 pages. The rule statement seems like it's missing something. If the rule was written like this (which is something we cant do since my orders last buy/sell price isn't in the second rule column) then I think we could easily get our desired results.

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

or

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

So Left to right
My Orders last buy price : Goes less than : Percentage 1% : Sell Amount : 0.01 : At Market Bid Price

What value is My Orders Last Buy Price compared to?
I see many potential indicators. Ask, Bid, Low, High, Last. Each has a separate and distinct number almost constantly.

As an example Lets say it compares Last buy to Last price. Now if I am selling at bid and last ask is more then the bid price My rules will not achieve my desired result. I will spend time looking for what actually triggers the rule. Since you wrote it I assume you would know what the actual base value is since it apparently isn't currently selectable.

I am glad you spelled out how to use a trailing rule. I have 4 all are running correctly for what I want them to do.

I hoped to setup something to avoid multiple rule sets that I had setup before. One for each range I wanted the bot to trade in. Each one taking yet another tab. All setup to make some money on price fluctuations. All blanked by a recent update that added percentages. I don't mind the loss of ~30 rules. They would lose a ton of money on the way up. I didn't like setting up another rule for every price drop that I might see over the next few hours. I mind I can't get 2 simple rules to work. Both stall at the same place. Both use a last buy or sell. Since putting a bell on it and hoping it will trigger is not terribly expedient I asked what the values I select are compared to. That way I know what should be in the last field.

Even then I either have the %s wrong as they don't reliably trade around a 1% range or there is a problem. Perhaps I have errored in what I want it to do. I want a rule that if the price goes more then 1% higher then the last buy price to place a sell that will sell. I set up another so that (its supposed to) if the last sell price is 1% lower it should buy back some amount of bitcoin. The problem is that those two rules refuse to work. I have sells occasionally. I never seem to get a buy. I have a trailing indicator looking for a greater then 1% move up to buy back an amount of bitcoins if the price turns on me. It can sell down 1% from the last sell. Leaving me with only a quandary as to what I messed up. I really want the rules to work. For the life of me I can't get one based on last buy or sell to work. I can't get a read on if less then 1% is actually from 500 to below 5 or below 495. It wont reliably trade. I suppose it could be that it is waiting for below 5 or below 3.50 or below 2.65. I don't know. Do I want less then 99%? I don't know. I do want it to work. I ask for some guidance on 2 things. ONE is new. The percentages have yet to be covered at all. Trailing was given as an example. It works. Just not for reliably making trades in a range. I want to make profitable trades. Down 1% to up 1% could be. It isn't always.

So far my stop loss and try to catch top and bottom trading using trailing stops has dropped me from 0.16 on the exchange to 0.132. I guess it could be worse but I know the market dropped far enough to trigger a down 1% rule if a trailing up 5% triggers 1$ above the last sell at 390$. I know this because each % is 3.90. To go up 5% or 19.50 I had to have dropped down 18.50 below the last sell. This tells me the rule won't trigger. It doesn't tell me why.

Thanks for your help.

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.

I know this question may seem a bit childish but honestly.

If Last buy price is less than ________ sell something.

It works but haphazardly.

The question I really desire an answer to is what fills in the blank? What are the last buy or sell compared to? I can't really effectively use the rule unless I know what it compares to. If the rules uses the Last price ticker then Likely I should use that price for what price to buy or sell at. If it uses an ask or a bid I should know what one. If its user selected that is perfect. Right now I don't know.

The second issue I see so far is that the rule in question doesn't seem to frequently work. I have a trailing stop if the ask goes up 1% that triggered about 1% below my last sell. That says to me that the price dropped 2%. It had to fall 1% below where it placed its buy. Its buy landed almost exactly 1% below the last sell. As a different rule should be buying back down 1% (unless I don't understand how it works) this rule never should have purchased anything.

Is the percentage raw or bound? By that I mean is <1% going to wait for less than 1% of the last price or is it going to wait for a drop of 1% from the last price.
As an example that never did get answered before. If I have last sell > 1% it seems to buy up a bit over 1%. If I have last buy < 1% it seems to sell at down 1%. The problem is that it doesn't always do anything. In other words is the % just an amount above or below 100%?

Bug Fix 4 installed and restarted so I should be using it and both last buy and last sell are broken. Or I misunderstand them. If you could take a moment and explain what the comparison is to and if the percent's are added or subtracted from 100% it would be awesome.

I see in the change log that you fixed the "my orders last buy" issue (I'm not even sure what the issue is) but I'm still not sure how to do the above that I was asking about. Is this something I'm gonna have to wait for? If possibly, it would be great if you could add "my orders last buy price" and "my orders last sell price" to the second column in the rule maker popup so I can write the rule as
If market bid price > .6% of my orders last buy price (plus exchange fee) sell amount .01BTC at Market bid Price.

Thanks.

I've been playing today with fractional amounts and noticed the same problem.

Any rules I create execute perfectly (Thanks) based on buy and sell at 1% and they move to the next rule, but if the order stays open I can end up with multiple open orders, even at Ask price.

Similar to what the OP stated "BUT I want the bot to wait until this order is filled in BEFORE it moves to the Next order."

What do you mean by "Pause"? A time delay, or actually see the previous order is actually filled before proceeding to the next rule?

Thanks