Bitcoin Forum
March 19, 2024, 11:53:59 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 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 77 78 79 80 81 82 83 »
  Print  
Author Topic: Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux]  (Read 383257 times)
idee2013
Sr. Member
****
Offline Offline

Activity: 407
Merit: 250


View Profile
October 23, 2014, 11:22:00 PM
 #1201

does anybody know that?

Hi. Thanks for bug report. I can confirm that this is bug and it happens with low chance.
It will be fixed in upcoming update.

HI,

low chance? this are 2 rule options
"buy btc" and "spend usd"
1710849239
Hero Member
*
Offline Offline

Posts: 1710849239

View Profile Personal Message (Offline)

Ignore
1710849239
Reply with quote  #2

1710849239
Report to moderator
1710849239
Hero Member
*
Offline Offline

Posts: 1710849239

View Profile Personal Message (Offline)

Ignore
1710849239
Reply with quote  #2

1710849239
Report to moderator
1710849239
Hero Member
*
Offline Offline

Posts: 1710849239

View Profile Personal Message (Offline)

Ignore
1710849239
Reply with quote  #2

1710849239
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1710849239
Hero Member
*
Offline Offline

Posts: 1710849239

View Profile Personal Message (Offline)

Ignore
1710849239
Reply with quote  #2

1710849239
Report to moderator
1710849239
Hero Member
*
Offline Offline

Posts: 1710849239

View Profile Personal Message (Offline)

Ignore
1710849239
Reply with quote  #2

1710849239
Report to moderator
IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
October 23, 2014, 11:24:38 PM
 #1202

HI,

low chance? this are 2 rule options

Sorry, mistyped messages.
There is low chance to get 383.80 instead of 383.81.

"buy btc" is exact btc amount and "spend usd" btc amount depends on price.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
idee2013
Sr. Member
****
Offline Offline

Activity: 407
Merit: 250


View Profile
October 23, 2014, 11:27:44 PM
 #1203

HI,

low chance? this are 2 rule options

Sorry, mistyped messages.
There is low chance to get 383.80 instead of 383.81.

"buy btc" is exact btc amount and "spend usd" btc amount depends on price.

i am trading exactly now and its happening about 80% of the orders. really
IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
October 23, 2014, 11:29:06 PM
 #1204

i am trading exactly now and its happening about 80% of the orders. really

This bug will be fixed in upcoming update in few days.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
idee2013
Sr. Member
****
Offline Offline

Activity: 407
Merit: 250


View Profile
October 23, 2014, 11:31:34 PM
 #1205

"buy btc" is exact btc amount and "spend usd" btc amount depends on price.

could you please describe it with an example.i  dont  understand it. thank you.

IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
October 23, 2014, 11:36:03 PM
 #1206




"buy btc" is exact btc amount and "spend usd" btc amount depends on price.

could you please describe it with an example. dont  understand it. thank you.



Sell 1 BTC at 400 USD will place 1 BTC order.
Spend 400 USD will place 1 BTC order only if price is equal to 400 USD
So if you configure "Spend 50% my USD" than you will don't know exact amount of received btc (depends on price), but you will know exact % of usd.
Spend 20 USD will get 0.1BTC at 200 USD price and 0.2 BTC at 100 USD price.
Usage depends on your strategy.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
Askit2
Hero Member
*****
Offline Offline

Activity: 981
Merit: 500


DIV - Your "Virtual Life" Secured and Decentralize


View Profile
October 24, 2014, 05:13:28 AM
 #1207

I'm Still having troubles with the % up and down not calculating correctly. I had another thought as to why they didn't work. I was looking at failed trades and winning trades and noticed a likely arbitrary coincidence that the short time span ( 28 seconds or less) trades all failed to be at least 1% apart as the rule should require. I have noted nothing in the log pointing towards the API lag being the cause of this. Apparently that too was a red herring.

So after noticing that the short turn around trade pairs always ended in failure and that long delays between the two usually an hour at least ended with a successful trade I got to thinking. What if the last buy or last sell isn't immediately correct? So I added first a 30 second delay into the rule that did the trading (wow random trade data). I eventually looked at the code and noticed that it doesn't delay testing it delays execution. Well that was a no go for me. So I add a rule before the rule that trades just to have a 30 second delay in it. At this point 5 of 6 rules had been put at 30 seconds delay before trying to buy or sell. I had to, a while later, ratchet it up to 45 seconds of delay on 5 of 6. Apparently I forgot one of them.

It seemed to work for a couple of days I had maybe 1 failed trade in 20. Not both a buy and sell just a buy or just a sell. The market was relatively flat though. Today I had another cluster of bad trades. 4 fail 2 success. This also pointed me to the fact that the maximum time on failures was 58 seconds. Orders farther then 58 seconds apart actually managed to be at least 1% apart. I have changed the starting delay up to 60 seconds but I don't believe this will be of help. On failures the order seems to nearly immediately execute and will do so regardless of prices and its relation to the other price.

I'm not sure what is going wrong nothing that is actually logged by default will help me find the answer. On the auto generated version of the new system the rules as it where, could you add a variable trace inside execute? That being the baseVariable. It would show what the number as calculated should be above of below.

          ▄▄
        ▄█▀▀█▄
      ▄█▀ ▄▄ ▀█▄
      ▀ ▄████▄ ▀
   ▄▀ ▄ ▀████▀ ▄ ▀▄
 ▄▀ ▄███▄ ▀▀ ▄███▄ ▀▄
█  ███████  ███████  █
 ▀▄ ▀███▀ ▄▄ ▀███▀ ▄▀

   ▀▄ ▀ ▄████▄ ▀ ▄▀
      ▄ ▀████▀ ▄
      ▀█▄ ▀▀ ▄█▀
        ▀█▄▄█▀
          ▀▀
███████████████████████████████████████████████████████████████████
██████▀▀▀▀▀▀▀▀▀▀▀██████████▀▀▀▀▀████▀▀▀▀▀█████▀▀▀▀█████▀▀▀▀▀███████
██████            ▀████████     ████     █████    █████     ███████
██████     ▄▄▄▄▄    ▀██████     █████    ████      ████    ████████
██████     ██████▄    █████     █████    ▀██▀  ▄▄  ▀██▀    ████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████     █   ██   █     █████████
██████     █████▀    ██████     ███████       ████       ██████████
██████     ▀▀▀▀▀    ▄██████     ████████     ██████     ███████████
██████            ▄████████     ████████     ██████     ███████████
██████▄▄▄▄▄▄▄▄▄▄▄██████████▄▄▄▄▄█████████▄▄▄▄██████▄▄▄▄████████████
███████████████████████████████████████████████████████████████████
.DIWtoken.com.
▄██████████████████▄
███       ▀███████
███       █████████
███       █████████
███       █████████
███              ██
███   ▄▄▄▄▄▄▄▄   ███
███   ▄▄▄▄▄▄▄▄   ███
███              ███
███▄▄▄▄▄▄▄▄▄▄▄▄▄▄███
██████████████████▀

▄██████████████████▄
███████████▀ ███████
█████████▀   ███████
███████▀     ██▀ ███
███ ▀▀       █▄▄████
███          █▀▀▀▀██
███ ▄▄       ███████
██████▄     █▄ ▀███
█████████▄   ███▄███
███████████▄ ███████
▀██████████████████▀

▄██████████████████▄
████████████████████
███████████████▀▀ ██
█████████▀▀     ███
████▀▀     ▄█▀   ███
███▄    ▄██      ███
█████████▀      ▄██
█████████▄     ████
█████████████▄ ▄████
████████████████████
▀██████████████████▀
......SECURITY DECENTRALIZED...
Askit2
Hero Member
*****
Offline Offline

Activity: 981
Merit: 500


DIV - Your "Virtual Life" Secured and Decentralize


View Profile
October 27, 2014, 09:32:03 PM
Last edit: October 31, 2014, 10:44:39 AM by Askit2
 #1208

Here are some trades from today.
11:16:03 0.010025 Bought 344.774
2:59:12   0.01        Sold     350.00
4:13:20   0.01        Sold     348.565  (wasn't manual but seems odd it happened there. I know one of these was manual I believe it was 3.50)
1:42:31   0.01        Sold     353.508  (manually started this one to force it to move into a new range. It seems I don't have up buy then sell working correctly yet.)
2:42:45   0.010021 Bought 349.92    (that should be about 1% lower then 353.508)
2:43:46   0.01        Sold     349.157  (I believe this trade keyed its price off of the 11:16:03 PM price last night not the 2:42:45 Price this afternoon.)
The lack of a following buy tells me that 62 minutes 15 seconds is long enough to use that price as a last. That isn't super helpful but is closer to an answer then nothing.

I'm not sure the Delays will help as it should pull the last buy price automatically when it starts that rule. The delay would likely give the order more time to actually clear but the order cleared 61 seconds before the next Sell. I'm not sure how big to go on delay I am sure it helps somewhat because eventually it should pull the last trade as the one that happened a while ago. I know it either works or sometimes works as I can go back and put the sell rule back on and it doesn't sell immediately when the delay runs out. I am not sure that I have found a workable solution. Eventually I should have a high enough delay that the trade will happen long enough ago that the last buy or sell gets pulled in correctly. I'm just not sure how long that will take.

As an aside. Although upping the delay would help as long as said delay is before the actual trade test portion I am not sure its a good answer. At some point the delay will force the bot to miss valid trades in a volatile market. Precisely when it would be the most logical to have a cold calculating piece of software looking for trades to make.

I have increased my pre test delay to 90 seconds. This seems excessive but hopefully no more mistakes or very very rare mistakes.
I wonder if it would be possible to export trade data to a csv file. It would seem easier to color the buys and sells and maybe mistakes differently. It would be easier to see the differences on working vs not working. Then again I could just go through manually and check each one looking for the shortest time that worked.

Thank You for your hard work. I am sorry I am having so much trouble with it. I shouldn't be I don't think but maybe its OS or something else related.
Exchange BTCe, OS win 7 64 bit, currency pair BTC/USD. Delay seems to be less then 0.1 frequently listed as 0.0.


Today the same thing happened. I am starting to think there is a definite pattern. That pattern is the last buy or sell isn't the actual last buy or sell for some time after the buy or sell. I was sure the manual trade caused problems but it seems not.

2:09:26AM   0.010000  sold       353.443 (automatic sell that the miss seems to be keyed off of)
9:53:45AM   0.010021  bought   349.624 (automatic buy)
8:46:33PM   0.010025  bought  345.00 (manual trade)
8:58:41PM   0.010021  bought  344.78 (automatic buy)
10.26.26PM  0.010000  sold      348.34 (automatic sell)
10:27:58PM 0.010021  sold       348.81 (automatic buy) Swing and a miss.

Ok math time. 1:32 I do believe is the time to beat. Odd. It took 2 seconds more then the initial 90 second delay. It paid more then the last sell...

Added more info:
Another day another similar occurrence. I have again an big move outside the 1% trading window. This time up. I have a buy then 2 sells ( I started the second one manually). Then a buy at a profitable price (it has to wait either to be below the actual last or below the one before it that is even lower). Now after that buy finishes after maybe an hour there is a sell nearly immediately. Well after 240 seconds of delay but immediate enough and the sell is below the last buy.

I have upped the delay to 300 hoping that waiting for 5 minutes after the sell or buy happens will give me that buy or sells price as the last price. For now I am using trial and error. If anyone knows a delay that will work I would love to know. Increasing by 60 seconds per mistake and hoping it will eventually at least make money rather then flushing quite a few trades profits down the exchanges coffers.

          ▄▄
        ▄█▀▀█▄
      ▄█▀ ▄▄ ▀█▄
      ▀ ▄████▄ ▀
   ▄▀ ▄ ▀████▀ ▄ ▀▄
 ▄▀ ▄███▄ ▀▀ ▄███▄ ▀▄
█  ███████  ███████  █
 ▀▄ ▀███▀ ▄▄ ▀███▀ ▄▀

   ▀▄ ▀ ▄████▄ ▀ ▄▀
      ▄ ▀████▀ ▄
      ▀█▄ ▀▀ ▄█▀
        ▀█▄▄█▀
          ▀▀
███████████████████████████████████████████████████████████████████
██████▀▀▀▀▀▀▀▀▀▀▀██████████▀▀▀▀▀████▀▀▀▀▀█████▀▀▀▀█████▀▀▀▀▀███████
██████            ▀████████     ████     █████    █████     ███████
██████     ▄▄▄▄▄    ▀██████     █████    ████      ████    ████████
██████     ██████▄    █████     █████    ▀██▀  ▄▄  ▀██▀    ████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████     █   ██   █     █████████
██████     █████▀    ██████     ███████       ████       ██████████
██████     ▀▀▀▀▀    ▄██████     ████████     ██████     ███████████
██████            ▄████████     ████████     ██████     ███████████
██████▄▄▄▄▄▄▄▄▄▄▄██████████▄▄▄▄▄█████████▄▄▄▄██████▄▄▄▄████████████
███████████████████████████████████████████████████████████████████
.DIWtoken.com.
▄██████████████████▄
███       ▀███████
███       █████████
███       █████████
███       █████████
███              ██
███   ▄▄▄▄▄▄▄▄   ███
███   ▄▄▄▄▄▄▄▄   ███
███              ███
███▄▄▄▄▄▄▄▄▄▄▄▄▄▄███
██████████████████▀

▄██████████████████▄
███████████▀ ███████
█████████▀   ███████
███████▀     ██▀ ███
███ ▀▀       █▄▄████
███          █▀▀▀▀██
███ ▄▄       ███████
██████▄     █▄ ▀███
█████████▄   ███▄███
███████████▄ ███████
▀██████████████████▀

▄██████████████████▄
████████████████████
███████████████▀▀ ██
█████████▀▀     ███
████▀▀     ▄█▀   ███
███▄    ▄██      ███
█████████▀      ▄██
█████████▄     ████
█████████████▄ ▄████
████████████████████
▀██████████████████▀
......SECURITY DECENTRALIZED...
Askit2
Hero Member
*****
Offline Offline

Activity: 981
Merit: 500


DIV - Your "Virtual Life" Secured and Decentralize


View Profile
November 03, 2014, 03:31:56 AM
 #1209

Another set of mistakes. The errors only show up in a non range bound situation. My last range was higher so I have a sell significantly above where the 1% back and forth rules should work the following seems to happen. I have a sell at 335 a buy at 330 and 324 (another rule serves to buy back as the market moves down) then a sell at 327 then a buy at 327 then a sell at 327. This is with a 5 minute delay.

So it appears the new Last Sell isn't the actual last sell for around 10 minutes. Possibly 10 minutes would work I am testing that now.  It shouldn't have more then 2 mistakes if I am wrong. At 5 minutes there ended up being 3 and at 1 second there could be more then 20. Obviously 3 is a huge improvement. Now for the problem I am currently seeing. Assuming 10 minutes works and there are 0 mistakes (I can't prove it yet) the maximum trades per hour is 6. Realistically I should bet 5 maybe would complete. As long as they are profitable I guess it is ok. If the market gets busy though I will see potentially many possibilities to have made money and the bot waiting for the Last Buy or Sell to be the actual Last Buy or Sell that was filled.

I'm not sure how you can reproduce the problem but I can see something happening.

          ▄▄
        ▄█▀▀█▄
      ▄█▀ ▄▄ ▀█▄
      ▀ ▄████▄ ▀
   ▄▀ ▄ ▀████▀ ▄ ▀▄
 ▄▀ ▄███▄ ▀▀ ▄███▄ ▀▄
█  ███████  ███████  █
 ▀▄ ▀███▀ ▄▄ ▀███▀ ▄▀

   ▀▄ ▀ ▄████▄ ▀ ▄▀
      ▄ ▀████▀ ▄
      ▀█▄ ▀▀ ▄█▀
        ▀█▄▄█▀
          ▀▀
███████████████████████████████████████████████████████████████████
██████▀▀▀▀▀▀▀▀▀▀▀██████████▀▀▀▀▀████▀▀▀▀▀█████▀▀▀▀█████▀▀▀▀▀███████
██████            ▀████████     ████     █████    █████     ███████
██████     ▄▄▄▄▄    ▀██████     █████    ████      ████    ████████
██████     ██████▄    █████     █████    ▀██▀  ▄▄  ▀██▀    ████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████     █   ██   █     █████████
██████     █████▀    ██████     ███████       ████       ██████████
██████     ▀▀▀▀▀    ▄██████     ████████     ██████     ███████████
██████            ▄████████     ████████     ██████     ███████████
██████▄▄▄▄▄▄▄▄▄▄▄██████████▄▄▄▄▄█████████▄▄▄▄██████▄▄▄▄████████████
███████████████████████████████████████████████████████████████████
.DIWtoken.com.
▄██████████████████▄
███       ▀███████
███       █████████
███       █████████
███       █████████
███              ██
███   ▄▄▄▄▄▄▄▄   ███
███   ▄▄▄▄▄▄▄▄   ███
███              ███
███▄▄▄▄▄▄▄▄▄▄▄▄▄▄███
██████████████████▀

▄██████████████████▄
███████████▀ ███████
█████████▀   ███████
███████▀     ██▀ ███
███ ▀▀       █▄▄████
███          █▀▀▀▀██
███ ▄▄       ███████
██████▄     █▄ ▀███
█████████▄   ███▄███
███████████▄ ███████
▀██████████████████▀

▄██████████████████▄
████████████████████
███████████████▀▀ ██
█████████▀▀     ███
████▀▀     ▄█▀   ███
███▄    ▄██      ███
█████████▀      ▄██
█████████▄     ████
█████████████▄ ▄████
████████████████████
▀██████████████████▀
......SECURITY DECENTRALIZED...
IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
November 03, 2014, 03:50:47 AM
 #1210

I'm not sure how you can reproduce the problem but I can see something happening.

Thanks for detailed descriptions, I'll try to reproduce it and fix soon.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
ecosystems
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
November 04, 2014, 07:04:14 AM
 #1211

I dont know if its a bug or not, but i would like you to know, when i revoked the API key in my BTC-e account, the Qt Bitcoin Trader could still use it, i mean i still had the ability to trade.
May be it's a BTC-e's bug... Just want to point that it is not secure...
idee2013
Sr. Member
****
Offline Offline

Activity: 407
Merit: 250


View Profile
November 04, 2014, 02:27:51 PM
 #1212




"buy btc" is exact btc amount and "spend usd" btc amount depends on price.

could you please describe it with an example. dont  understand it. thank you.



Sell 1 BTC at 400 USD will place 1 BTC order.
Spend 400 USD will place 1 BTC order only if price is equal to 400 USD
So if you configure "Spend 50% my USD" than you will don't know exact amount of received btc (depends on price), but you will know exact % of usd.
Spend 20 USD will get 0.1BTC at 200 USD price and 0.2 BTC at 100 USD price.
Usage depends on your strategy.

ah ok..thank you
drhelmutp
Sr. Member
****
Offline Offline

Activity: 440
Merit: 250


View Profile
November 07, 2014, 07:35:53 PM
 #1213

Okcoin integration is really important since their web interface is laggy as hell.

I'm impatient about this! Smiley
Inopa
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 08, 2014, 08:39:41 PM
 #1214

Hi Ighor,
Love QT.
I have a question - I'm having some trouble getting bitfinex up and working with the following code, The console outputs: "20:20:06> starting
20:20:06> LTCUSD: Sell 3 at 4" but i don't see orders entered at bitfinex:

//code start:

var lastVAR=0;
var VAR=0;



trader.get("Time")
{
trader.log("starting")
trader.sell("LTCUSD",3,4)
}

//VAR and lastVar are used later
//code end

It looks simple what would you say is wrong here? have you had issues for example between the bitfinex exchange/trading subdivision of accounts, or any other idea of why the order does not go through?
IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
November 08, 2014, 09:07:46 PM
 #1215

Hi Ighor,
Love QT.
I have a question - I'm having some trouble getting bitfinex up and working with the following code, The console outputs: "20:20:06> starting
20:20:06> LTCUSD: Sell 3 at 4" but i don't see orders entered at bitfinex:

//code start:

var lastVAR=0;
var VAR=0;



trader.get("Time")
{
trader.log("starting")
trader.sell("LTCUSD",3,4)
}

//VAR and lastVar are used later
//code end

It looks simple what would you say is wrong here? have you had issues for example between the bitfinex exchange/trading subdivision of accounts, or any other idea of why the order does not go through?

Looks like you have used trader.get("Time") as event? This is a function and you should use event "trader.on("Time").changed()" instead.
Anyway make the same order every second is not a good idea.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
Inopa
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 08, 2014, 09:23:58 PM
 #1216

yes i agree with that not being smart, i was simply using it as a placeholder event trigger. regardless, my order does not reach the bitstamp exchange even though it shows in the console. have you seen such behavior? I've tried other pairs, etc. I am able to enter orders manually on the bitstamp website, and I see these orders show up in the QT dashboard. I really don't understand why the ordering doesn't get though....
IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
November 08, 2014, 09:48:12 PM
 #1217

yes i agree with that not being smart, i was simply using it as a placeholder event trigger. regardless, my order does not reach the bitstamp exchange even though it shows in the console. have you seen such behavior? I've tried other pairs, etc. I am able to enter orders manually on the bitstamp website, and I see these orders show up in the QT dashboard. I really don't understand why the ordering doesn't get though....

Manual placing order via Qt Bitcoin Trader works?
If not, than press Alt+Shift+D and send me debug output after open order attempt.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
Askit2
Hero Member
*****
Offline Offline

Activity: 981
Merit: 500


DIV - Your "Virtual Life" Secured and Decentralize


View Profile
November 10, 2014, 07:17:52 AM
 #1218

My trading issues with the 1% up and 1% down seemed to keep pointing me to a previous to the expected buy or sell. The 600 second delay didn't work after a restart and forgetting for about an hour to enable the rules I still got a buy above the should be 1% higher sell.

This left me thinking that it was definitely using an older buy price and older sell prices then 10 minutes. That makes me think maybe the time isn't so important. Unfortunately my next idea wasn't successful either. I added another sell to the sell rules and another buy to the buy rules excluding the going down buy rule. This puts 2 sells in 10 minutes before the buy rule will even start. Now the odd thing is I was still able to have sells coming below my last buy (since the market was heading up). I don't know if adding a third buy would be of any help at all. I can't imagine it would do much more then delay potentially through the next range to get to its required price. Of course if it was profitable using 6% of my test amount maybe it would be better then 2 round trip trades executing upside down. If only I could divine why it was doing this.

I have increased some rules to 900 seconds or 15 minutes delay before it starts executing. I can't imagine it helping. Maybe I should only add the really big delay by delaying the start of the enables on trades that end up in a loss after. I'm still trying to get you a better answer as I can easily duplicate the issue but I can't wrap my head around why it happens.

          ▄▄
        ▄█▀▀█▄
      ▄█▀ ▄▄ ▀█▄
      ▀ ▄████▄ ▀
   ▄▀ ▄ ▀████▀ ▄ ▀▄
 ▄▀ ▄███▄ ▀▀ ▄███▄ ▀▄
█  ███████  ███████  █
 ▀▄ ▀███▀ ▄▄ ▀███▀ ▄▀

   ▀▄ ▀ ▄████▄ ▀ ▄▀
      ▄ ▀████▀ ▄
      ▀█▄ ▀▀ ▄█▀
        ▀█▄▄█▀
          ▀▀
███████████████████████████████████████████████████████████████████
██████▀▀▀▀▀▀▀▀▀▀▀██████████▀▀▀▀▀████▀▀▀▀▀█████▀▀▀▀█████▀▀▀▀▀███████
██████            ▀████████     ████     █████    █████     ███████
██████     ▄▄▄▄▄    ▀██████     █████    ████      ████    ████████
██████     ██████▄    █████     █████    ▀██▀  ▄▄  ▀██▀    ████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████     █   ██   █     █████████
██████     █████▀    ██████     ███████       ████       ██████████
██████     ▀▀▀▀▀    ▄██████     ████████     ██████     ███████████
██████            ▄████████     ████████     ██████     ███████████
██████▄▄▄▄▄▄▄▄▄▄▄██████████▄▄▄▄▄█████████▄▄▄▄██████▄▄▄▄████████████
███████████████████████████████████████████████████████████████████
.DIWtoken.com.
▄██████████████████▄
███       ▀███████
███       █████████
███       █████████
███       █████████
███              ██
███   ▄▄▄▄▄▄▄▄   ███
███   ▄▄▄▄▄▄▄▄   ███
███              ███
███▄▄▄▄▄▄▄▄▄▄▄▄▄▄███
██████████████████▀

▄██████████████████▄
███████████▀ ███████
█████████▀   ███████
███████▀     ██▀ ███
███ ▀▀       █▄▄████
███          █▀▀▀▀██
███ ▄▄       ███████
██████▄     █▄ ▀███
█████████▄   ███▄███
███████████▄ ███████
▀██████████████████▀

▄██████████████████▄
████████████████████
███████████████▀▀ ██
█████████▀▀     ███
████▀▀     ▄█▀   ███
███▄    ▄██      ███
█████████▀      ▄██
█████████▄     ████
█████████████▄ ▄████
████████████████████
▀██████████████████▀
......SECURITY DECENTRALIZED...
IGHOR (OP)
Legendary
*
Offline Offline

Activity: 1035
Merit: 1065



View Profile WWW
November 10, 2014, 11:28:52 AM
 #1219

My trading issues with the 1% up and 1% down seemed to keep pointing me to a previous to the expected buy or sell. The 600 second delay didn't work after a restart and forgetting for about an hour to enable the rules I still got a buy above the should be 1% higher sell.

This left me thinking that it was definitely using an older buy price and older sell prices then 10 minutes. That makes me think maybe the time isn't so important. Unfortunately my next idea wasn't successful either. I added another sell to the sell rules and another buy to the buy rules excluding the going down buy rule. This puts 2 sells in 10 minutes before the buy rule will even start. Now the odd thing is I was still able to have sells coming below my last buy (since the market was heading up). I don't know if adding a third buy would be of any help at all. I can't imagine it would do much more then delay potentially through the next range to get to its required price. Of course if it was profitable using 6% of my test amount maybe it would be better then 2 round trip trades executing upside down. If only I could divine why it was doing this.

I have increased some rules to 900 seconds or 15 minutes delay before it starts executing. I can't imagine it helping. Maybe I should only add the really big delay by delaying the start of the enables on trades that end up in a loss after. I'm still trying to get you a better answer as I can easily duplicate the issue but I can't wrap my head around why it happens.

I'm currently working to make all variables saved after restart rule and app.
Also you will able to store any data in database and view values of all variables realtime.
It will helps to understand where is issue and how to make it works.

Qt Bitcoin Trader
Verify digital signature of the app in the file properties every time you download it.
Askit2
Hero Member
*****
Offline Offline

Activity: 981
Merit: 500


DIV - Your "Virtual Life" Secured and Decentralize


View Profile
November 11, 2014, 10:34:31 AM
Last edit: November 12, 2014, 05:47:17 AM by Askit2
 #1220

My trading issues with the 1% up and 1% down seemed to keep pointing me to a previous to the expected buy or sell. The 600 second delay didn't work after a restart and forgetting for about an hour to enable the rules I still got a buy above the should be 1% higher sell.

This left me thinking that it was definitely using an older buy price and older sell prices then 10 minutes. That makes me think maybe the time isn't so important. Unfortunately my next idea wasn't successful either. I added another sell to the sell rules and another buy to the buy rules excluding the going down buy rule. This puts 2 sells in 10 minutes before the buy rule will even start. Now the odd thing is I was still able to have sells coming below my last buy (since the market was heading up). I don't know if adding a third buy would be of any help at all. I can't imagine it would do much more then delay potentially through the next range to get to its required price. Of course if it was profitable using 6% of my test amount maybe it would be better then 2 round trip trades executing upside down. If only I could divine why it was doing this.

I have increased some rules to 900 seconds or 15 minutes delay before it starts executing. I can't imagine it helping. Maybe I should only add the really big delay by delaying the start of the enables on trades that end up in a loss after. I'm still trying to get you a better answer as I can easily duplicate the issue but I can't wrap my head around why it happens.

I'm currently working to make all variables saved after restart rule and app.
Also you will able to store any data in database and view values of all variables realtime.
It will helps to understand where is issue and how to make it works.

I am a little concerned about saving the variables through a restart. Assuming they are being calculated correctly having a few calculations pulled at start up shouldn't be a huge issue. In my case I maybe shouldn't have said anything about the restart. The thing I was pondering out loud was if I restart the computer and enable the rules after the last buy and last sell printed on the tab with the orders is correct I should get a buy or a sell based on that price point. What I am at a loss for is why after so long it didn't use that price as it did clearly show a last sell that was what my actual last sell was. So since in over an hour the amount shown in the easy place to see it was "correct" but the trade price was not correct I concluded that time delays are not really a good answer for this. I then stupidly assumed since the only value that explained the trade as being "correct" was the trade preceding the last trade. This sent me wrongly it seems to the answer of just sell 2 or buy 2 and it will follow the last number before the last trade making it track off the trade I want in the first place and the second place just sets up an additional trade at the same price.

I think possibly I am not going about solving this well as until I have another (wrong) eureka moment I really can't say why it trades off very old trades some over 1 hour old for the last trade data. I'm not saying don't save it between runs just that given the delay that I had I would have needed a more then hour delay between a buy and a sell.... That would in theory make the reverse also true. So 12 round trip trades a day if the market is staying around the price it works itself into. Honestly had I not restarted I would have had another 10 minute mistake. The only difference of any importance is that it would show a mistake at over an hour. Not useful mind you as that isn't a correct trade. It does make me think starting over an hour might work but I really shouldn't need to.

The problem always shows up the same way even with 2 nearly identical buys and sells. I have a stable range and the bot does great. It will keep doing great until the market goes up or down too much. At this point I have found 0 solutions that adequately fix the problems I am having. Once the market is up triggering a buy manually will not cause a new last buy price to show up. An hour will not allow the bot to use the price that I just made viable. As soon as anything is able to sell after that buy will be whatever the price is when the sell rule is started not 1% above that buy. In effect I had hoped adding another buy would force it to use the wrong buy before the last buy value..... It really doesn't I just get 2x the mistakes. Since it does 2x as good when it wins I can't say I'm in a worse boat. I am exactly where I started. Even starting a sell and letting the buy show up under doesn't seem to fix it. The only change is what the bot is doing at the time of the mistake. If I sell first the buy will likely be correct or below the sell before that making it either profitable or even more profitable. Sounds great. Then it will (ignoring delay) get a sell immediately at whatever the price changes to on the next tick unless the buy was below the sell before the high sell I put in. At some point though that sell will be used as a last sell and then any price at least 1% below that price will be acceptable to the bot. Even if I am bothered by it suddenly buying above the last sell.....

If I gave up on the stop loss portions of the rules I generated I could expect a profit. This profit would last precisely until I have to start the bot in a new range. I then am stuck unable to fix the bot until I have some unknown amount of trade data in the new range started and executed manually until the bot can correctly discern it is actually in a range.

EDIT: I am sorry it seems I have a bad habit of not being nice when I post. I appreciate what you have done and are doing. I am more then a little concerned when my last buy on my orders page isn't 1% less then my listed last sell when the buy logic dictates it has to be at least that low to buy.

After thinking more on it today do the values of the trade logs last buy and last sell prices come from the same place the scripting engine would pull the data from?

          ▄▄
        ▄█▀▀█▄
      ▄█▀ ▄▄ ▀█▄
      ▀ ▄████▄ ▀
   ▄▀ ▄ ▀████▀ ▄ ▀▄
 ▄▀ ▄███▄ ▀▀ ▄███▄ ▀▄
█  ███████  ███████  █
 ▀▄ ▀███▀ ▄▄ ▀███▀ ▄▀

   ▀▄ ▀ ▄████▄ ▀ ▄▀
      ▄ ▀████▀ ▄
      ▀█▄ ▀▀ ▄█▀
        ▀█▄▄█▀
          ▀▀
███████████████████████████████████████████████████████████████████
██████▀▀▀▀▀▀▀▀▀▀▀██████████▀▀▀▀▀████▀▀▀▀▀█████▀▀▀▀█████▀▀▀▀▀███████
██████            ▀████████     ████     █████    █████     ███████
██████     ▄▄▄▄▄    ▀██████     █████    ████      ████    ████████
██████     ██████▄    █████     █████    ▀██▀  ▄▄  ▀██▀    ████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████    ██   ██   ██    █████████
██████     ███████    █████     ██████     █   ██   █     █████████
██████     █████▀    ██████     ███████       ████       ██████████
██████     ▀▀▀▀▀    ▄██████     ████████     ██████     ███████████
██████            ▄████████     ████████     ██████     ███████████
██████▄▄▄▄▄▄▄▄▄▄▄██████████▄▄▄▄▄█████████▄▄▄▄██████▄▄▄▄████████████
███████████████████████████████████████████████████████████████████
.DIWtoken.com.
▄██████████████████▄
███       ▀███████
███       █████████
███       █████████
███       █████████
███              ██
███   ▄▄▄▄▄▄▄▄   ███
███   ▄▄▄▄▄▄▄▄   ███
███              ███
███▄▄▄▄▄▄▄▄▄▄▄▄▄▄███
██████████████████▀

▄██████████████████▄
███████████▀ ███████
█████████▀   ███████
███████▀     ██▀ ███
███ ▀▀       █▄▄████
███          █▀▀▀▀██
███ ▄▄       ███████
██████▄     █▄ ▀███
█████████▄   ███▄███
███████████▄ ███████
▀██████████████████▀

▄██████████████████▄
████████████████████
███████████████▀▀ ██
█████████▀▀     ███
████▀▀     ▄█▀   ███
███▄    ▄██      ███
█████████▀      ▄██
█████████▄     ████
█████████████▄ ▄████
████████████████████
▀██████████████████▀
......SECURITY DECENTRALIZED...
Pages: « 1 ... 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 77 78 79 80 81 82 83 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!