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

Earlier days exactly when?
Yes new version is coming soon.

i downloaded fromn official site but it is very slow to update...laggy but earlier days it was much better.....

new version coming anytime soon >?

Vote to add new Exchange https://twitter.com/QtBitcoinTrader/status/669493447263428609

can this trader support huobi ?
https://github.com/huobiapi/API_Docs_en/wiki

Do this qt bitcoin trader supports all major exchanges?

I have no knowledge that this is correct but I am fairly sure no new exchanges are being added because of existing run time errors. Since the bot has some formatting errors making certain math need a workaround like negative numbers. Also there is an apparently nearly exclusive to me shutdown problem wherein your handshake information for  you API key pair is not correctly saved. Since it does not move to the correct number delivered by the server or allow a user to accept the servers number to allow a fully working API key pair to actually work this renders the bot useless after a required shutdown. Of course some people don't run the bot 24/7 so maybe that is why others aren't bothered or don't mention the issue.

Another thought is that the API work to actually setup new exchanges does take some time. Maybe IGHOR is busy with something. I'm not sure what. Personally I am hoping for the bug fix release that has been indicated to be soon but is now over 2 months later. I am guessing the bug fix got rolled into a fairly major rewrite and since indicators and junk are being added it will take time to get a version rolled out with just the fixes. I am not sure what is going on and am hoping IGHOR comes back to let us know about something good happening. For now I am just hoping that actual usability issues are fixed before more exchanges and trading language changes are rolled in. I'm not against those changes but problems that have already been fixed for private should be simple to fix for public unless the private is doing a lot of beta testing to hopefully avoid more of the same kind of issues.

Why doesnt this app support OKCoin both .cn/.com spot and futures trading?

I know you are trying to help. Github lists Latest commit a51dc1c  on Jul 4 for testing and july 5th for master. That was the day the version I am using came out(7-5-2015 or 5-7-2015 depending on local July 5th at any rate). It is the version I built on the Linux box that has the same problem. I'm not sure where the data for the "Private Beta" is. With the updated code base at least 1 instance would be less problematic to shut off. Of course I haven't ever had QT Creator work for me. I wish I had better information but 1.07.01 is where the change log ends and I am running 1.10.01. I have no idea what actually changed between them except if I shut down I have to generate new key pairs. Shut downs are now about weekly and take about 10 mins or so. It isn't all bad. I just don't restart as often as I would like because it's a pain.

Thank You though. I had hoped more current code was available then the last time I pulled github.

EDIT: added date from executable.

The source code is on the github which can be loaded into QT Creator.

I've tried doing it myself but I'm getting a compile error on build. Something about OpenSSL being missing.

Triple check what you download because some version have been mined with Trojans and Keyloggers malwares. I had an issue with a copy named CryptoTrader QT.

I suppose IGHOR is gone. I was going to wait for 3 days to post this again. The reason would be by then it will be 2 months since not only was the bug known but it had been fixed. Well for anyone in the private beta. How one gets into the private beta I have no idea. How one gets the code to fix it themselves I also have no idea. When soon is again I am not knowing.

I did notice when the power went out my raspberry pi running arch Linux was unintentionally restarted. The odd thing was there was no problem when it came back up. No nonce-sense. No new key pairings. I logged in and it just worked. Once doesn't prove anything but it does make me wonder if the actual shut down code that runs isn't messing things up. Maybe a true force killing will fix it. It likely won't but who knows maybe I can get less trouble just killing it off rather then letting it close cleanly.

of course taskkill /IM qtbitcointrader.exe /F doesn't get what I want. So another key pair away!

aaaand he's gone

does anyone know where i can download older versions of Qt trader. It is sucking now 450kb/s 24/7. i dont know why

Hello, I still am a big fan of your beautiful piece of code!
But I am waiting to use it with Kraken.com since over a year now. 
Would be nice to see things finally go forward, I'd really really love to use it with Kraken..
 
 
And I think I speak for a lot of people.
 
Thank you..!

Any news on Poloniex support?

Hey,
I'm forced to restart again. Even getting the network interface up doesn't fix WMC's brilliant disabling system. So another restart. Another new API key pair. Any news on when soon is?

If you quote the question when answering it then it is frequently easier for people to find the information. It will make the post grow a bit. I guess I missed your reply or didn't relate the two. I did read all the posts. That is not entirely common for people to do. My point was and still is if you make things easy to find by linking related conversations then people don't have to try to find it. Then when you reposted your request the exchange information would be with it. Don't get me wrong I can't force anyone to do anything. I have just noticed when people don't have to search for information they usually have a better response.

 

Ok so last night the Digital cable tuner got disabled in that the "network interface" it uses was disabled. Both UI and command prompt where attempted to get it back running. Renaming the connection did momentarily fix it but the next recording failed to work. The only thing that will actually get that "network interface" up is a full restart. I put network interface in "" because it is a USB device hard wired to the computer but uses a fake network interface to communicate.

So I had to restart. I have no way to use the bot until I have them setup again. Since it was late that encouraged me to wait until I was rested. I know that fix and some other changes are in a private beta. Could you release a bug fix release just for the API key pair issue?

Edit: So everything went well and getting both running took about 9 minutes. I think this is the second new key pair set since I found out about the beta. So I guess I only used maybe 27 minutes of my time fixing the lack of restart in a month. This does ignore times I would have preferred to restart and didn't because of a lack of time to fix or the 8 or so hours the bot is down when it is late. The delay because it is late is my fault but I found I make more mistakes when I am half asleep.

EDIT October 4, 2015: Some additional thoughts. Going back to a reply from September 8, 2015 you said you would put out a bug fix release soon. It is say 4 days short of a month. When is soon? I found this error in early July. I mentioned it on or near the 10th of July. After two months of difficult restarts I finally had crash logs that showed what I wanted to show: before and after results. This did end with you mentioning the bug being fixed in private beta. The bothersome part to me is that it is getting close to 3 months of these crashes/failures. At this point I wonder if the private beta didn't have more bugs. I just want it to work as it always had. No weird API key pair failures on every restart. No trying to calculate how long it will take to get everything up and running if I do restart to fix or install something. Maybe I am just overly interested in news.

I think the request for your exchange that you use might shed some light on why its higher. It would be best if you desire a fix that you do answer the questions that get asked. Sometimes to fix an issue the problem isn't locally on your trading bot but remotely on their server.

HI, could you please look for that issue. Qt is downloading around 42GB in 70 hours. Sorry, but this is really to much.
The rowcount change had 0 effect , too.