Nice catch, thank you!
Litecoin Global is also crying for a fix!  Edit: I was wondering, when 2 orders have the same price, the older one gets filled first right? |
|
|
|
Why doesn't assbot show BitFunder trades? Your assets are missing lots of free advertising!  I guess because BitFunder still doesn't offer an API. I'm currently getting login incorrect when trying to log into WeExchange, it also won't send me a recovery mail. I guess the system is "available", but you can't login once again? Edit: Okay, it also says login incorrect if the 2-Factor is missing or wrong. And the mails just arrived. |
|
|
|
I'm assuming you mean the CSV endpoints?
Sure, I just plugged it in. Note however that these trade_id's will not necessarily match up with the public trade id's from the tradeHistory endpoint. (db complexities, sorry.)
Cheers.
Hey, you forgot to change the header  Ticker,Operation,Quantity,Amount,Timestamp
23241,ASICMINER-PT,buy,1,1.22555000,"2013-04-30 13:12:26" |
|
|
|
|
How can I get a new BTC receiving address on WeExchange?
|
|
|
|
The system (at least WeExchange) was not available for over 6 hours. It would have been nice if you'd given a small notice before the downtime, but thanks for the heads up.
Weexchange should have been fine. The only issue caused by me was when both had login difficulties. -Ukyo Yes, thats what I meant with not available. |
|
|
|
|
The system (at least WeExchange) was not available for over 6 hours. It would have been nice if you'd given a small notice before the downtime, but thanks for the heads up.
|
|
|
|
|
Thats odd, so on both WeExchange and Bitfunder aren't working now?
|
|
|
|
|
I guess logging into WeExchange and nothing happening is business as usual?
|
|
|
|
Any progress on this? As I said the problem occurs when filling an existing bid/ask order via the API.
I think it may actually be working for you. Cheers. Yes I can confirm it works flawlessly on direct bid and direct ask. Awesome! |
|
|
|
|
Bitfunder has ridiculously high fees, also the site is not very responsive. (Why does it have to reload the market every time I switch back from a stock AND forget my sort setting?)
So even with the recent problems of BTCT, I think its far superior, but some stocks aren't available there.
|
|
|
|
I'm getting 'Access temporarily denied." errors when trying to log in. Anyone else having this issue?
Please make sure to use another username then on the forum. I guess there are some jokers blocking the accounts of others. |
|
|
|
|
Could also be related to stronger BTC. The rate never dropped below 100$/BTC.
|
|
|
|
Thank you. I have found two potential points of exit from the code where the security lock was not being released prior to exiting:
- One related to backend bitcoind failure, which I do not think was the cause here because there's logging that would have been seen if this were the case.
- Another which may be the smoking gun was a DDoS prevention piece that was intended to run once at init, but was being called twice because of a double layer of validation in the bid/ask processing methods. I've fixed it to only do the DDoS test the first call per run.
Hopefully it ends up being taken care of now, but I've also added more logging/debugging code a bunch of places to help out if this doesn't end up taking care of it.
Cheers.
Have you already applied the code. I just tested it and the problem occurred again.  yes.   Any progress on this? As I said the problem occurs when filling an existing bid/ask order via the API. |
|
|
|
Just got off the phone with a SEC specialist. He said that the SEC is looking into Bitcoin security exchanges, and if they are unregistered and offering unlicensed securities then they are violating the law and has advised me to not invest. I asked him about if being virtual and for educational purposes covers it and he said he cannot say. Oh and he asked me if I have lost any money in anything Ethan Burnside offered, I take that as burnside here If you don't believe me ask them here https://tts.sec.gov/oiea/QuestionsAndComments.html they called me back. Santa called, he said you won't get anything for christmas. |
|
|
|
Thank you. I have found two potential points of exit from the code where the security lock was not being released prior to exiting:
- One related to backend bitcoind failure, which I do not think was the cause here because there's logging that would have been seen if this were the case.
- Another which may be the smoking gun was a DDoS prevention piece that was intended to run once at init, but was being called twice because of a double layer of validation in the bid/ask processing methods. I've fixed it to only do the DDoS test the first call per run.
Hopefully it ends up being taken care of now, but I've also added more logging/debugging code a bunch of places to help out if this doesn't end up taking care of it.
Cheers.
Have you already applied the code. I just tested it and the problem occurred again. |
|
|
|
Just found another bug, every time you try to fill an order (at least bid) directly via OAuth you get an error Example: OAuth ->fetch (' https://btct.co/oauth/trade', array('act' => 'ask_submit', 'ticker' => 'S.MPOE-PT', 'ask_quantity' => '1', 'ask_price' => '0.0008607'), 'POST') Response: Invalid auth/bad request (got a 500, expected HTTP/1.1 20X or a redirect) Its also possible that it creates a deadlock. It seems that the system does not release the lock after this. (Just guessing) On second try I get: Array ( [status] => error [error_message] => Received Ask Order: 1 of S.MPOE-PT @ 0.0008607 BTC: Excessive wait trying to get lock on S.MPOE-PT. ) |
|
|
|
Bingo! [02:11:28] 1 ASK ACTIVEMINING @ 0,1
{"status":"success","response":"Received Ask Order: 1 of ACTIVEMINING @ 0.1 BTC: Placed Sale Order #959414: 1 @ 0.1 BTC. <br><br>"}
[02:11:16] 1 BID ACTIVEMINING @ 0,0001
{"status":"success","response":"Received Bid Order: 1 of ACTIVEMINING @ 0.0001 BTC: Placed Purchase Order #959404: 1 @ 0.0001 BTC. <br><br>"}
Sweet. Moved it from oauth/trade_new to oauth/trade. Thanks again! Just wanted to thank you for the fast fix. Great job! And thanks dexX7 for helping, great its working properly now. |
|
|
|
The order # is in the response string.
Thanks, haven't noticed that. Should be fine for now. |
|
|
|
|
I have 2 feature requests for the API:
1. Return Order ID in the response of submitting bid/ask
2. When excessive wait occurs, set status to fail and not success
|
|
|
|
@burnside: why not str_replace(" ", " ", $news_text); ?
because...:
Thats some amazingly formatted text |
|
|
|
|
Show Posts
