Bitcoin Forum
December 18, 2017, 03:58:09 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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)
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



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

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, JL Script
Centrabit AG | Check out digital signature of every app you have download and use only official download sources.
1513569489
Hero Member
*
Offline Offline

Posts: 1513569489

View Profile Personal Message (Offline)

Ignore
1513569489
Reply with quote  #2

1513569489
Report to moderator
1513569489
Hero Member
*
Offline Offline

Posts: 1513569489

View Profile Personal Message (Offline)

Ignore
1513569489
Reply with quote  #2

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

Posts: 1513569489

View Profile Personal Message (Offline)

Ignore
1513569489
Reply with quote  #2

1513569489
Report to moderator
1513569489
Hero Member
*
Offline Offline

Posts: 1513569489

View Profile Personal Message (Offline)

Ignore
1513569489
Reply with quote  #2

1513569489
Report to moderator
1513569489
Hero Member
*
Offline Offline

Posts: 1513569489

View Profile Personal Message (Offline)

Ignore
1513569489
Reply with quote  #2

1513569489
Report to moderator
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


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

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.


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

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

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

Activity: 900



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

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, 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
November 11, 2014, 10:34:31 AM
 #1224

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?


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

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

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

Activity: 669


INS Ecosystem


View Profile
November 13, 2014, 06:12:28 AM
 #1225

After thinking longer on the issue I got the idea that maybe I should use the script engine. Aside from problems with a script starting other scripts I think I have it working somewhat normally. This line doesn't work on script engine codes.
Code:
trader.delay(0.2, "trader.groupStop('S_Up Buy then Sell')");

Maybe I did that part wrong. Currently I have a group running that does start and stop all the other scripts and groups based on what has already run. I just took the trading parts out from my non-script versions. I have all scripts named correctly unless I missed one somewhere. It does happen to me more then I would like. I am assuming given the huge move up today I should have had it up and running sooner. Today would have been a great day to test.

I can't say it will work better but it may work better. Starting the script engine after the up buy then sell ran I didn't get an identical trade for the next sell I actually got to wait until the price was high enough.


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

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

███
███
███
███
███
███
███
███
███
███
███
███
███
upup
Jr. Member
*
Offline Offline

Activity: 42


View Profile
November 15, 2014, 11:06:48 AM
 #1226

Have some one got working scripts?
IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
November 16, 2014, 04:11:12 PM
 #1227

After thinking longer on the issue I got the idea that maybe I should use the script engine. Aside from problems with a script starting other scripts I think I have it working somewhat normally. This line doesn't work on script engine codes.
Code:
trader.delay(0.2, "trader.groupStop('S_Up Buy then Sell')");

Maybe I did that part wrong. Currently I have a group running that does start and stop all the other scripts and groups based on what has already run. I just took the trading parts out from my non-script versions. I have all scripts named correctly unless I missed one somewhere. It does happen to me more then I would like. I am assuming given the huge move up today I should have had it up and running sooner. Today would have been a great day to test.

I can't say it will work better but it may work better. Starting the script engine after the up buy then sell ran I didn't get an identical trade for the next sell I actually got to wait until the price was high enough.


English is not my native language, so sometime I have problem in understanding.
Please make short description how to reproduce problem and I'll fix it faster.

Have some one got working scripts?

Scripts is working.

Bitcoin QT is no longer working for me. I'm on a Windows 32 machine.

It worked a few weeks ago. Now, all it does is let me log on... and then nothing.

Each instance appears in Task Processes and uses up a hella load of CPU power, but nada. No window, no dialog, no error message..... it just doesn't load the main app.

:-S

Looks like you have catch some malware file. Does digital signature from Centrabit presists in exe file properties?
"Bitcoin QT" you talking about Bitcoin p2p client and not "Qt Bitcoin Trader"?

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

Activity: 42


View Profile
November 17, 2014, 05:18:41 AM
 #1228

No I am saying about some good strategies
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
November 17, 2014, 08:13:56 AM
 #1229

After thinking longer on the issue I got the idea that maybe I should use the script engine. Aside from problems with a script starting other scripts I think I have it working somewhat normally. This line doesn't work on script engine codes.
Code:
trader.delay(0.2, "trader.groupStop('S_Up Buy then Sell')");

Maybe I did that part wrong. Currently I have a group running that does start and stop all the other scripts and groups based on what has already run. I just took the trading parts out from my non-script versions. I have all scripts named correctly unless I missed one somewhere. It does happen to me more then I would like. I am assuming given the huge move up today I should have had it up and running sooner. Today would have been a great day to test.

I can't say it will work better but it may work better. Starting the script engine after the up buy then sell ran I didn't get an identical trade for the next sell I actually got to wait until the price was high enough.


English is not my native language, so sometime I have problem in understanding.
Please make short description how to reproduce problem and I'll fix it faster.

The code snippet should after the condition has happened simply stop another script The start code was virtually the same. I have a set of rules now that that a similar snippet of code does start and those rules will start the asked for scripts.

As an example my range trading scripts are S_1% Up and S_1% Down. They each run once then stop.

If I manually start S_1% Down I expect the code to start the script named S_1% Up.
Code:
trader.groupStart("S_1% Up");
This script never starts.

If I manually start S_1% Up I expect the code to start the script named S_1% Down.
Code:
trader.groupStart("S_1% Down");
This script never starts.


For the moment I have instead added rules groups or used the old rules groups named 1% Up and 1% Down to execute the starts and stops for me. I'm not sure why I can't get that code to start the scripts. I have definitely created a workaround for this issue. I mostly wanted to know if that code was even close to correct now. It worked before one of the updates and for me has not worked since.


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

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

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

Activity: 669


INS Ecosystem


View Profile
November 18, 2014, 10:16:59 AM
 #1230

I did notice one thing after a restart. If a last my buy or last my sell price is used but the one queried is not the very last trade a 0 will be returned. This just caused an sell up 1% to happen below the last buy price from before my bot restart. I have added a simple piece of code to find and eliminate this error.
Code:
if(baseVariable = 0)
 {
 return;
 }

That should fix this specific issue from now on as it wont trade with a last price of 0.

This does not fix the issue. The following should.
Replace the execute(); with the following.

Code:
if(baseVariable != 0)
 {
 execute();
 }


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

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

███
███
███
███
███
███
███
███
███
███
███
███
███
Dwayne
Jr. Member
*
Offline Offline

Activity: 39



View Profile
November 23, 2014, 02:31:13 PM
 #1231

I am trying to compile QtBitcoinTrader Version 1.08 on my Raspberry Pi (Debian Wheezy).
I got the following error:

Code:
g++ -c -pipe -O2 -D_REENTRANT -Wall -W -Wno-deprecated-declarations -Wno-unused-function -DQT_WEBKIT -DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtScript -I/usr/include/qt4 -I. -I/usr/src/3rdparty/zlib -I.moc -I.ui -o .obj/feecalculator.o feecalculator.cpp
feecalculator.cpp:118:6: error: prototype for ‘void FeeCalculator::profitLossChanged(qreal)’ does not match any in class ‘FeeCalculator’
feecalculator.h:57:7: error: candidate is: void FeeCalculator::profitLossChanged(double)
feecalculator.cpp:167:6: error: prototype for ‘void FeeCalculator::buyBtcReceivedChanged(qreal)’ does not match any in class ‘FeeCalculator’
feecalculator.h:61:7: error: candidate is: void FeeCalculator::buyBtcReceivedChanged(double)
Makefile:1422: recipe for target '.obj/feecalculator.o' failed
make: *** [.obj/feecalculator.o] Error 1

QtBitcoinTrader 1.07.97 BETA works on Raspberry Pi.
On my Ubuntu the 1.08 works.

What I can do ?
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
November 24, 2014, 08:29:32 PM
 #1232

False Alarm on real time calculation. I caused it myself.  Huh I changed the function to not reuse the variable that is created outside the function to calculate the value then return the value to the variable outside the calculation. In other words I renamed the variable in the calcBaseVariable() and forgot to get the value later with baseVariable = calcBaseVariable(). I used this calcBaseVariable();.  Shocked Grin

Sorry for that complaint.


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

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

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

Activity: 900



View Profile WWW
November 25, 2014, 12:38:58 AM
 #1233

QtBitcoinTrader 1.07.97 BETA works on Raspberry Pi.
On my Ubuntu the 1.08 works.

Fixed, please confirm it.

False Alarm on real time calculation. I caused it myself.  Huh I changed the function to not reuse the variable that is created outside the function to calculate the value then return the value to the variable outside the calculation. In other words I renamed the variable in the calcBaseVariable() and forgot to get the value later with baseVariable = calcBaseVariable(). I used this calcBaseVariable();.  Shocked Grin

Sorry for that complaint.

That great. Any bugs left? Please list them.

I'm happy to tell that low latency engine is working now, and private beta is starting soon.

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

Activity: 756



View Profile
November 25, 2014, 02:09:54 AM
 #1234

Umm....I'll be starting off with this soon. Seems to be great, I've already been trading successfully over the past few days.

Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
November 25, 2014, 09:31:21 AM
 #1235

I only have 2 bugs left.

1. The code that will start a rules group fails to start a script. I change the name of the rules group to the script name. (code is just up from this post in a code block)

2. The LastMyBuyPrice doesn't return the price of my last buy. The UI shows the correct price as the last buy price just by the days high and days low price boxes.

3. The LastMySellPrice doesn't return the price of my last sell. The UI shows the correct price as the last sell price just by the days high and days low price boxes.

Numbers 2 and 3 are only corrected by the bot trading wrong until the scripts pull the correct last sell and last buy prices.


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

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

███
███
███
███
███
███
███
███
███
███
███
███
███
Dwayne
Jr. Member
*
Offline Offline

Activity: 39



View Profile
November 25, 2014, 09:12:28 PM
 #1236

QtBitcoinTrader 1.07.97 BETA works on Raspberry Pi.
On my Ubuntu the 1.08 works.

Fixed, please confirm it.



It works now  Smiley

Thank you for the quick support
Askit2
Hero Member
*****
Offline Offline

Activity: 669


INS Ecosystem


View Profile
December 04, 2014, 09:20:16 AM
 #1237

First I know there was no update yet to fix the bugs I have tried to explain. One of the bugs stuck its head up again today.

12/2
5:25 B 0.010000  Sold       380        manual
8:30 B 0.010000  Sold       382        manual
11:31 B 0.010025 Bought  378        automatic
11:31 B 0.010025 Bought  378        automatic (I started doubling the trades for range trading)
12/3
12:52 B 0.010022 bought  375        manual
12:59 B 0.010022 bought  372.9     manual
4:43   B 0.010022 bought  370        manual
7:29   B 0.010000 sold      375        automatic
7:29   B 0.010000 sold      375        automatic
7:30   B 0.010025 bought  375.013 automatic (The last one that fit the price was 382. The calculated value for That price - (that price * (0.004 + 0.004)) was 378.
7:30   B 0.010025 bought  375.013 automatic (duplicate trade was my plan)

The sell at 375 was profitable. The sell at 375 was 36 seconds before the Buy at 375.013.

Because of this  last sell price being wrong the bot traded wrong. Maybe another way to look at it is if the bot hadn't just sold at 375 the buy at 375 would have been profitable. This mistake isn't new to me. When the mistake happens the bot seems to be in a profitable range. This time the range lasted more then 12 hours. I did not wait for 375 to come up again and sell then. I sold after watching the price come up from 367 to 370 at 370 hoping it would start moving into a range there. The rest of the day being wrong was my fault.

When I get another sell at 375 I doubt the range will still be between 370 and 375. I don't mind that I am not seeing many trades happen per day. It does bother me when the bot gets both a sell and a buy at the same price. With enough cash waiting to trade I could just manually put in a buy at 370 or so and have had the bot back on track. I didn't have enough left. I should have as it is only supposed to buy 2 times if the USD balance / price is > 3 * 0.010025. This should always leave me one trade to make.

Except for the range trading portion taking 1 trade to break even for each mistake it works great. If it could trade more often at that same profit margin I would be happy. As is I am losing money frequently on bad trades. Given enough time it would make the money back. My thought on the above trades is that I only use 1 buy or sell to move the automatic scripts into a new range. This was so that the initial trade was wrong and small. The later trades would be profitable and are larger. It should have a bad trade at a loss. Then 2 good trades at a profit. Making 1 trade of profit in total for 3 complete trades. This is not ideal. Ideal would be each trade was profitable by calculation based on correct data. Since I am not getting correct data I can not get to ideal results. 


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

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

███
███
███
███
███
███
███
███
███
███
███
███
███
Ronan-
Jr. Member
*
Offline Offline

Activity: 52


View Profile
December 05, 2014, 09:48:41 PM
 #1238

Where can I find old versions of the software?

IGHOR
Hero Member
*****
Offline Offline

Activity: 900



View Profile WWW
December 06, 2014, 04:53:47 PM
 #1239

Where can I find old versions of the software?

I keep only source code of old versions on sourceforge.net

First I know there was no update yet to fix the bugs I have tried to explain. One of the bugs stuck its head up again today.

12/2
5:25 B 0.010000  Sold       380        manual
8:30 B 0.010000  Sold       382        manual
11:31 B 0.010025 Bought  378        automatic
11:31 B 0.010025 Bought  378        automatic (I started doubling the trades for range trading)
12/3
12:52 B 0.010022 bought  375        manual
12:59 B 0.010022 bought  372.9     manual
4:43   B 0.010022 bought  370        manual
7:29   B 0.010000 sold      375        automatic
7:29   B 0.010000 sold      375        automatic
7:30   B 0.010025 bought  375.013 automatic (The last one that fit the price was 382. The calculated value for That price - (that price * (0.004 + 0.004)) was 378.
7:30   B 0.010025 bought  375.013 automatic (duplicate trade was my plan)

The sell at 375 was profitable. The sell at 375 was 36 seconds before the Buy at 375.013.

Because of this  last sell price being wrong the bot traded wrong. Maybe another way to look at it is if the bot hadn't just sold at 375 the buy at 375 would have been profitable. This mistake isn't new to me. When the mistake happens the bot seems to be in a profitable range. This time the range lasted more then 12 hours. I did not wait for 375 to come up again and sell then. I sold after watching the price come up from 367 to 370 at 370 hoping it would start moving into a range there. The rest of the day being wrong was my fault.

When I get another sell at 375 I doubt the range will still be between 370 and 375. I don't mind that I am not seeing many trades happen per day. It does bother me when the bot gets both a sell and a buy at the same price. With enough cash waiting to trade I could just manually put in a buy at 370 or so and have had the bot back on track. I didn't have enough left. I should have as it is only supposed to buy 2 times if the USD balance / price is > 3 * 0.010025. This should always leave me one trade to make.

Except for the range trading portion taking 1 trade to break even for each mistake it works great. If it could trade more often at that same profit margin I would be happy. As is I am losing money frequently on bad trades. Given enough time it would make the money back. My thought on the above trades is that I only use 1 buy or sell to move the automatic scripts into a new range. This was so that the initial trade was wrong and small. The later trades would be profitable and are larger. It should have a bad trade at a loss. Then 2 good trades at a profit. Making 1 trade of profit in total for 3 complete trades. This is not ideal. Ideal would be each trade was profitable by calculation based on correct data. Since I am not getting correct data I can not get to ideal results. 


I have started work on fixes, but I'm ill now and I'll finish work once I'll feel better.

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

Activity: 52


View Profile
December 06, 2014, 07:49:52 PM
 #1240

I hope you feel better soon!

I was looking for older versions due to a bug in which I think the ticker always functions under exchange rather than trading on finex, only for rules. I can specify trading in the overall window, and trade through the buy and sell buttons, however if I make a rule, even if it says trading I think it operates (or doesn't work at all) under exchange. Also once you edit the rule it reverts to exchange in the view of a rules group.

Unfortunately I don't know how to compile source code, if someone could point me to a quick and relatively easy tutorial or something, much appreciate.

Again, get well soon! Smiley

Pages: « 1 ... 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!