RTBTC is now live! Go check it out at https://rtbtc.com/The service is not free, but you can subscribe for 15 days for less than 0.05 BTC. |
|
|
|
Did anyone noticed something similar. And does anyone has any ideas about this problem? How is it possible to detect those lost messages orders and fix them?
Well there was a $1M bid wall that got removed right before the selling started yesterday. I don't believe that large drop was an error. |
|
|
|
Is that RTBTC?
But of course |
|
|
|
 That is all  |
|
|
|
Ah, yes. The server stores 1-min, 15-min, and 1-day bars, constructing the other time frames from those bars. The chart widget loads 15-min bars to create the 4H candles, so there is a reduction ratio of 16. This leads to the dearth of candles in the 4H time frame. Sorry about that. Here's what you're looking for, courtesy RTBTC (which will be going public Soon TM).  |
|
|
|
And combining exchanges should just be the beginning. I mean.. we don't even have a trading plattform with indicators, fibonacci etc. besides SierraChart afaik.
Have you checked out RTBTC? https://rtbtc.com/In private beta now. Public release Coming Soon TM |
|
|
|
Could you be more specific?  |
|
|
|
I've noticed something funny about the way bitcoin.clarkmoody.com colors the candles... it seems that the candle is colored not based on whether the open is greater or less than the close, but whether the close is greater or less than the previous close. Typically the open of one period will be close to the close of the previous period, but it can be different. There's an example of a strangely colored candle now: the 2013-5-22 22:15:00 (Chicago time, if it matters) candle for the M15 view is colored red even though the open is 124.40000 and the close is 124.40002. (The previous close is 124.43900.) Is this intentional behavior? It seems counterintuitive.
First post of this thread describes the candle shading/coloring scheme. Color is based on this close vs. previous close. Shading is based on up/down during this period. |
|
|
|
By "bid higher than inside ask" you mean if the lowest ask is 115 and an "order" comes in for a bid at 115.01 you ignore it since it's higher than the lowest ask?
Actually, I trust the incoming data over the socket more than I do the data that's already on the book. So if that bid came in, then I eliminate the conflicting asks off the book, since it's likely that they are incorrect. |
|
|
|
=> is MtGox selecting which orders get broadcasted?
=> does CM miss some of those "updates" ?
a) I don't know. b) I'm certainly not filtering out any updates that make sense: for instance, since there is the order book syncing issue, I won't update the book if I get a bid that's higher than the inside ask; things like that. @Clark: I don't have data to reproduce this, but I have noticed a few occasions where I placed an order via a POST with my MtGox API, and then I see the order show up in MtGox, but it doesn't show up in the bid/ask depth data. Even though I see other data adding and removing itself from the bid/ask still. Eventually my order fills, and I see the trade entry in the trade list, but it never showed up on the ask/bid depth. (These are often 0.1 or 0.05 BTC orders.)
I'll try to keep a closer eye on it to see if I can get more valuable reproduceable details. Take this from me with a grain of salt right now though because who knows what it could be.
If your order is the same price as an existing order on the book, then it will add to that order, not show up as a distinct issue. You probably know this, but it could factor into the behavior. |
|
|
|
They look great! Wish I could build my own charts like that. Any pointers?
Go slow and solve lots of little problems. Build yourself lots of helper functions to do simple things and put them together to create complex behavior. |
|
|
|
Pardon me if this has been answered already. What are you using for your charting tools?
The charts are custom built by me |
|
|
|
Just a note here for you guys: RTBTC has entered private beta, and everything is working properly on the production server  |
|
|
|
Please don't tell me the site is down at the moment, thanks. I'm working to get it back online |
|
|
|
This may have already been asked here, but what is "slippage"? thanks
Slippage is the difference between the value of your buy/sell whether calculated with the inner bid/ask or calculated based on the orders on the book. Simple example: say you want to sell 2 BTC. The inner Bid is 1 @ $10. The next highest bid is 1 @ $8 (thin book). The face value of your 2 BTC is $20, but the actual sale price you can get is $18, since you would take both bid orders to fill your sale. Thus, the slippage would be $2. |
|
|
|
Is the "Time & Sales" only updated for USD? ..When I switch to EUR, it doesn't show any data.
It might start working once you reload, after you've chosen another currency. There are still some issues with the socket.io client library and reconnection. |
|
|
|
site api keeps going down is this normal?
What API? |
|
|
|
Thanks, but is this the same API that Clark Moody uses? I use the direct MtGox API for trades and compute the bars. There is no CSV file for the exact data I display, but that Bitcoin Charts resource should be pretty good. |
|
|
|
It appears that the Real Time Charting, Order Book and Time and Sales are all broken in IE 10 (Win7 64bit).
On Win8 64bit (with IE10) it works just fine. I have a perpetual "Attempting to connect via FlashSocket".
07:28:19 > Attempting connection over flashsocket
07:28:18 > Opening streaming data connection.
07:28:18 > Error loading depth of market data.
07:28:18 > Loading full depth of market table.
07:28:18 > Changing depth display to 100 rows.
07:28:18 > Resizing console to 5 lines.
It works fine in every other browser from Firefox to Chrome.
I have avoided IE support on purpose, since it's been such a bad browser for so long. I will probably need to look at IE10 when I get the time, but don't expect anything older to work. |
|
|
|
But sometimes I have a trouble recognizing sound signals (not sure if anybody mentioned it).
Probably not everybody has perfect ear to distinguish sound tones if there is a significant time interval between them. Could you please use more complicated sound samples so that it is easier to distinguish them? Or you could just combine the existing two (instead of "high" and "low" you could play "low-high" and "high-low"). Should be easy to implement.
I could look into this. Down sounds could have a downward pitch ramp, and upward for Up. That way it's not just the same two sounds at different pitch. |
|
|
|
|
Show Posts
