Topic: Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux] - page 70. (Read 383267 times)
November 05, 2013, 11:19:04 AM
BTC China Trade API v1.1 is released.. http://btcchina.org/api-trade-documentation-en#trade_api_v11
November 05, 2013, 08:14:52 AM
Also, another bug that is when you place an order and it appears as you placed it 2 times, with a few seconds difference betweeen requests.
This is bitstamp bug. Order received from API with same order id, but next request received with different date time.
I'll make exception and fix it.
Reported it to Bitstamp support.
November 05, 2013, 07:56:22 AM
Also, another bug that is when you place an order and it appears as you placed it 2 times
Just reproduced this bug. Fixing.
November 05, 2013, 07:41:54 AM
Also, another bug that is when you place an order and it appears as you placed it 2 times, with a few seconds difference betweeen requests. If you check the Open orders on Stamp's website, you see there is only one order opened. If you restart Qt Bitcoin Trader, then it reloads the Open Orders correctly. However, it does not fix that in real time.
Thank you for description. How often it happens?
Tested again. Now it seems to appear one out of 4-5 times... Hard to reproduce, it has variance. Now it appears almost every time, now it doesn't. I think Stamp's API is unreliable as well...
ALSO. There are times (again... one out of every 4-5 times) when I put an order and it does not reach Stamp... The order is ok value-wise (smaller, with enough money available), because after one or two attempts it is working... Just testing it now, and it's unreliable.
So, please test it right now. Put some orders (for me, selling orders won't work every time), see the debug info...
EDIT: Your software might work, it may just be Stamp's unreliable API. But it's up to you to figure that out.
Thanks again for the good work!
Bitstamp have match slower API then Mt.Gox.
Are you sure order is not reach bitstamp first time? Can you try wait 10-30 seconds and report is it apears?
November 05, 2013, 07:35:21 AM
Also, another bug that is when you place an order and it appears as you placed it 2 times, with a few seconds difference betweeen requests. If you check the Open orders on Stamp's website, you see there is only one order opened. If you restart Qt Bitcoin Trader, then it reloads the Open Orders correctly. However, it does not fix that in real time.
Thank you for description. How often it happens?
Tested again. Now it seems to appear one out of 4-5 times... Hard to reproduce, it has variance. Now it appears almost every time, now it doesn't. I think Stamp's API is unreliable as well...
ALSO. There are times (again... one out of every 4-5 times) when I put an order and it does not reach Stamp... The order is ok value-wise (smaller, with enough money available), because after one or two attempts it is working... Just testing it now, and it's unreliable.
So, please test it right now. Put some orders (for me, selling orders won't work every time), see the debug info...
EDIT: Your software might work, it may just be Stamp's unreliable API. But it's up to you to figure that out.
Thanks again for the good work!
November 05, 2013, 07:16:30 AM
Yes, it happens to me on Stamp in the case of me already having multiple Bid orders in place. Let's say I have 3 existing bids, and $100 remaining in my account. In that case, the All In button puts a value that is higher than the available to buy. So to "fix" this, I have to manually edit the value to a few dollars lower so the Bid is accepted by Stamp's API. Unfortunately I have no dollars on Stamp to test this at the moment, but this happened a few times so I can confirm.
I'll fix this, but I need to test it with different amounts. So I'll make some updates and ask you to test it.Ok, I'll test.
Also, another bug that is when you place an order and it appears as you placed it 2 times, with a few seconds difference betweeen requests. If you check the Open orders on Stamp's website, you see there is only one order opened. If you restart Qt Bitcoin Trader, then it reloads the Open Orders correctly. However, it does not fix that in real time.
Thank you for description. How often it happens?
Not always. I will look for this and try to asses and give back more feedback in the next days.
November 05, 2013, 06:49:55 AM
Yes, it happens to me on Stamp in the case of me already having multiple Bid orders in place. Let's say I have 3 existing bids, and $100 remaining in my account. In that case, the All In button puts a value that is higher than the available to buy. So to "fix" this, I have to manually edit the value to a few dollars lower so the Bid is accepted by Stamp's API. Unfortunately I have no dollars on Stamp to test this at the moment, but this happened a few times so I can confirm.
I'll fix this, but I need to test it with different amounts. So I'll make some updates and ask you to test it.Also, another bug that is when you place an order and it appears as you placed it 2 times, with a few seconds difference betweeen requests. If you check the Open orders on Stamp's website, you see there is only one order opened. If you restart Qt Bitcoin Trader, then it reloads the Open Orders correctly. However, it does not fix that in real time.
Thank you for description. How often it happens?
November 05, 2013, 06:43:33 AM
There are one situation when calculated Buy value of BTC is higher then available to buy. I'm still fixing this.
Yes, it happens to me on Stamp in the case of me already having multiple Bid orders in place. Let's say I have 3 existing bids, and $100 remaining in my account. In that case, the All In button puts a value that is higher than the available to buy. So to "fix" this, I have to manually edit the value to a few dollars lower so the Bid is accepted by Stamp's API. Unfortunately I have no dollars on Stamp to test this at the moment, but this happened a few times so I can confirm.
Also, another bug that is when you place an order and it appears as you placed it 2 times, with a few seconds difference betweeen requests. If you check the Open orders on Stamp's website, you see there is only one order opened. If you restart Qt Bitcoin Trader, then it reloads the Open Orders correctly. However, it does not fix that in real time. I have only tested this on Stamp.
November 05, 2013, 06:28:56 AM
My only issue with the latest BETA (1.07.91) is that the sound alerts do not work anymore. I don't hear any BEEPs while the program does flash when hitting a new high or low. Maybe just on my PC.
This is a small bug. Already fixed in v1.07.92. Soon I'll publish it.
When configuring a rule, when trying to buy bitcoins, it would be better if we could select how many money we want to exchange into bitcoins instead of how many bitcoins we want to buy, because we always know how many money we have but not always know how many bitcoins we can buy.
It would be great to be able use select how many money we can to exchange.. But exchanges API does not supports this.
There are one situation when calculated Buy value of BTC is higher then available to buy. I'm still fixing this.
Please make sure is this happens for Sell or for Buy and let me know.
November 05, 2013, 06:17:02 AM
The problem with the certificate is fixed, but i think there may be still issues with Bitstamp, it shows me a error message saying my key and secret are not correct, i double checked and allowed the correct permissions for the api access, also followed the troubleshooting list. Currently i use Google athenticator, may that be the problem?
I tried accessing to mtgox and it works fine.
Windows (x64)
I tried accessing to mtgox and it works fine.
Windows (x64)
I had the same "issue". After you create the API on Bitstamp you need to do additional steps to be able to use it.
After creating the API go back to API menu and click on Activate. An e-mail will be sent to you.
After you click on the link in the e-mail the API will be activated and it will then work with IGHOR's program.
Thanks, that wasn't the problem, it was a technical issue, IGHOR is already aware.
On the other hand, i'm rarely able to place an open order, most of the time the "SELL" or "BUY" order doesn't get to bitstamp. Is anyone having the same issue? i normally click on the Sell order button, it asks me if i'm sure to sell, and then nothing happens even if i wait for a while.
Suggestion:
When configuring a rule, when trying to buy bitcoins, it would be better if we could select how many money we want to exchange into bitcoins instead of how many bitcoins we want to buy, because we always know how many money we have but not always know how many bitcoins we can buy.
November 05, 2013, 06:04:47 AM
My only issue with the latest BETA (1.07.91) is that the sound alerts do not work anymore. I don't hear any BEEPs while the program does flash when hitting a new high or low. Maybe just on my PC.
November 05, 2013, 06:01:30 AM
The problem with the certificate is fixed, but i think there may be still issues with Bitstamp, it shows me a error message saying my key and secret are not correct, i double checked and allowed the correct permissions for the api access, also followed the troubleshooting list. Currently i use Google athenticator, may that be the problem?
I tried accessing to mtgox and it works fine.
Windows (x64)
I tried accessing to mtgox and it works fine.
Windows (x64)
I had the same "issue". After you create the API on Bitstamp you need to do additional steps to be able to use it.
After creating the API go back to API menu and click on Activate. An e-mail will be sent to you.
After you click on the link in the e-mail the API will be activated and it will then work with IGHOR's program.
November 04, 2013, 04:53:18 PM
Hey Ighor, you said nothing about my previous message.
Just posting to make sure you are aware of the issue. Thanks!
Just posting to make sure you are aware of the issue. Thanks!
Hi. Thanks for this. I read everything. Just back home and I'll fix it soon.
November 04, 2013, 04:43:21 PM
Hey Ighor, you said nothing about my previous message.
Just posting to make sure you are aware of the issue. Thanks!
Just posting to make sure you are aware of the issue. Thanks!
November 04, 2013, 04:20:55 PM
Would be awesome if we could get into the supported exchanges.
I'll add support of campbx, icbit, bitfinex and many others.
Currently it hard make changes in all exchanges, but I have learned enough to make base class of all exchanges.
When I'll finish base classes I'll start adding many exchanges vary fast.
November 04, 2013, 03:58:19 PM
Would be awesome if we could get CampBX into the supported exchanges.
November 03, 2013, 09:55:33 PM
When you remove profile, it completely remove data.
You can see this folder %localappdata%\QtBitcoinTrader or ~/.config/QtBitcoinTrader (Linux)
You can see this folder %localappdata%\QtBitcoinTrader or ~/.config/QtBitcoinTrader (Linux)
I reinstalled and created new key and secret, everything seems correct, however now i get "API Key not Found: 202", i double checked the key and secret.
Please email me and we will debug it.
November 03, 2013, 09:51:13 PM
When you remove profile, it completely remove data.
You can see this folder %localappdata%\QtBitcoinTrader or ~/.config/QtBitcoinTrader (Linux)
You can see this folder %localappdata%\QtBitcoinTrader or ~/.config/QtBitcoinTrader (Linux)
I reinstalled and created new key and secret, everything seems correct, however now i get "API Key not Found: 202", i double checked the key and secret.
November 03, 2013, 08:59:20 PM
Did you correctly enter your Client ID when created profile? (I don't know why, but it required by API access)
Yeah, i still get "Invalid Signature: 202". Maybe there are some remanents of the last version, can you let me know were does the "system installation" (non-portable) stores the data? So i can erase and retry.
When you remove profile, it completely remove data.
You can see this folder %localappdata%\QtBitcoinTrader or ~/.config/QtBitcoinTrader (Linux)
November 03, 2013, 08:56:27 PM
Did you correctly enter your Client ID when created profile? (I don't know why, but it required by API access)
Yeah, i still get "Invalid Signature: 202". Maybe there are some remanents of the last version, can you let me know were does the "system installation" (non-portable) stores the data? So i can erase and retry.
Jump to: