Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 33913. (Read 26714004 times)

I use the Chrome web browser. Its tools permit the monitoring of the TCP traffic between client and server - and so I watch Clark Moody's app to confirm the socket.io API that Mt. Gox uses. I likewise found Mt.Gox performance to be annoying.

Monday volatility is here. Now we start to see where the price really wants to go.

Bear in mind that the market cap is somewhat meaningless. It doesn't mean that if you dump all the bitcoins on the market, you end up with $3 trillion.

Price drops to 117, and he clears out the asks to 124, hmmm....

HAHA someone is desperately buying trying to prevent this from looking like the top.

I think $124 was the top. Rocket is out of fuel, and even the manipulator(s) could not tow it.
Now heading back to a lower orbit

I wanted to do the socket.io thing (and still do for another project) but found it poorly documented and jumped on the http in the end. I still need to figure out why I appear to be regularly missing the first few minutes each hour from Gox. It's not always but it's often enough to be annoying.

the pain

And begin!

It doesn't so much apply to bubbles as much as when, in a rising market, you get flash crashes and bear traps which cause people to panic sell and generally try and chase the market. Stronger hands will carry through such short-term dips (and even buy during them) because they believe the longer term trend is up.

Conversely, it is likely that bubbles and crashes are actually caused by weak hands, those who rush in when they think they can make a profit then bail when it all looks a bit pear-shaped.

Of course, this implies that those who believe in long-term growth are correct. It's a matter of perspective.

I also like $125'ish for the top ... I just don't trust this rally at all and am not convinced it's got much more life in it

That just about sums up trend-following TA.

I pretty much agree with you again. If we go again to $160 I would be puzzled. Heck, I think the normal thing would be not going over $125 before the final bottom.

Have you ever seen a medium perform where they're saying they hear a voice, it's Susan, maybe Sarah. She's your mother, no grandmother, maybe a childhood friend?

Gotta be able to turn on a dime in the prediction business.

I would feel even more confident about my bitcoin bubble assumptions if the price did not exceed $145 again before the final bottom.

So much bad math on this board.

3e5 * 1e7 = 3e12 = $3,000,000,000,000 = 3 trillion.

But I agree, in general, with the sentiment. I don't see the market cap of bitcoin being 3 trillion by the end of the year. I think we could see $10k, which is a market cap of ~$100 billion.

I say 150

In the Erisian Archives is an old memo from Omar to Mal-2: "I find the Law of Fives to be more and more manifest the harder I look."

A few months ago I wrote a Java websocket/socket.io client for Mt. Gox that processes the depth chart to explore my notions about depth and tick data. The ChartBuddy 3-D depth chart periodically posted here shows the time dimension like I wanted - so no point in going further. But I did learn enough about the Mt. Gox API to very deeply appreciate the cleverness employed by Clark Moody who ties together Mt. Gox trades and depth changes.

The Mt. Gox HTTP API allows the client to poll the server in order to obtain partial or the full depth list of bids and asks. Then its websocket/socket.io API allows the client to subscribe to trades, depth changes, and lag. Subsequently the client receives notification of depth changes, which is the change and new amount of the limit bid or ask orders at a certain price at a certain time, i.e. the time the limit order was issued/cancelled. What is crazy is that Mt. Gox drops the connection, or otherwise loses synchronization between the trades and the depth chart. Clark Moody's realtime charting app dynamically fixes all this up. Its not precise - but it is very satisfactory, by polling the server to replace the client depth info when it gets out of sync.

I can answer detailed protocol questions about the Mt. Gox API as regard to charting data, but not much at all regarding the trading functions.

I say Wednesday is the day in which we will see where we are heading at.