Bitcoin Forum
December 18, 2017, 03:58:18 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 »
  Print  
Author Topic: Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux]  (Read 356100 times)
JasperDX7
Jr. Member
*
Offline Offline

Activity: 37


View Profile
February 17, 2014, 12:02:45 AM
 #861


bump, IGHOR can you please answer this. I need to know how this statement would be treated "if my orders Last Buy price > 0.6% (trailing) sell amount .01btc at market bid price."

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.


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
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513569498
Hero Member
*
Offline Offline

Posts: 1513569498

View Profile Personal Message (Offline)

Ignore
1513569498
Reply with quote  #2

1513569498
Report to moderator
1513569498
Hero Member
*
Offline Offline

Posts: 1513569498

View Profile Personal Message (Offline)

Ignore
1513569498
Reply with quote  #2

1513569498
Report to moderator
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
February 17, 2014, 12:04:58 AM
 #862

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

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

Qt Bitcoin Trader, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
February 17, 2014, 04:03:31 AM
 #863

Bugfix #3 released

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

Qt Bitcoin Trader, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
JasperDX7
Jr. Member
*
Offline Offline

Activity: 37


View Profile
February 17, 2014, 04:09:58 AM
 #864

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

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

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

Activity: 63


View Profile
February 17, 2014, 11:25:27 AM
 #865

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

Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
February 17, 2014, 12:37:19 PM
 #866

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



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.


███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █

█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
●  Whitepaper
●  ANN Thread
●  Reddit
●  Telegram
●  Twitter
●  Facebook

███
███
███
███
███
███
███
███
███
███
███
███
███
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
February 17, 2014, 12:53:34 PM
 #867

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.


███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █

█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
●  Whitepaper
●  ANN Thread
●  Reddit
●  Telegram
●  Twitter
●  Facebook

███
███
███
███
███
███
███
███
███
███
███
███
███
wuke
Member
**
Offline Offline

Activity: 63


View Profile
February 17, 2014, 03:28:41 PM
 #868

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.

IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
February 17, 2014, 05:08:12 PM
 #869

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 should re-create rules after bugfix #4. Or edit ini file to change ids you want.

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.

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

Qt Bitcoin Trader, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
February 17, 2014, 05:10:14 PM
 #870

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

I'll make pause soon.

Qt Bitcoin Trader, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
Wilma
Newbie
*
Offline Offline

Activity: 10


View Profile
February 17, 2014, 08:26:33 PM
 #871

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.

 
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
February 17, 2014, 08:27:23 PM
 #872

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.

Thank you. I'll debug this.

Qt Bitcoin Trader, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
TheTommyD
Sr. Member
****
Offline Offline

Activity: 304


View Profile
February 17, 2014, 10:06:46 PM
 #873

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



I'll make pause soon.



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


BTC: 1DEj5mbjoYXqvRKfoS4yqtdvSKHpQ4hFLu
JasperDX7
Jr. Member
*
Offline Offline

Activity: 37


View Profile
February 18, 2014, 01:20:29 AM
 #874

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

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

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

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.
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
February 18, 2014, 10:05:20 AM
 #875

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.


███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █

█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
●  Whitepaper
●  ANN Thread
●  Reddit
●  Telegram
●  Twitter
●  Facebook

███
███
███
███
███
███
███
███
███
███
███
███
███
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
February 18, 2014, 10:21:52 AM
 #876

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

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.

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.

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.


Qt Bitcoin Trader, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
February 18, 2014, 10:59:34 AM
 #877

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.

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.


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.


███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █
███ █ █

█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
█ █ ███
●  Whitepaper
●  ANN Thread
●  Reddit
●  Telegram
●  Twitter
●  Facebook

███
███
███
███
███
███
███
███
███
███
███
███
███
JasperDX7
Jr. Member
*
Offline Offline

Activity: 37


View Profile
February 18, 2014, 03:11:53 PM
 #878

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.

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.


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.

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
kalross
Member
**
Offline Offline

Activity: 85


View Profile
February 18, 2014, 05:47:47 PM
 #879


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



+1  I got no idea what the conditional statement is referring to.
jatajuta
Sr. Member
****
Offline Offline

Activity: 365



View Profile
February 18, 2014, 09:25:53 PM
 #880

Is it possible to give market orders with this software?

I only found limit orders.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!