I got a "Your browser sucks" message because I had scripts disabled. Poor form.
Off topic... is this a correct ranking of preferred form in handling this situation? blank page or other such confusing non-function : bad "your browser sucks" - page still doesn't work : poor "please enable scripts or get a newer browser" - page still doesn't work : fair "please enable scripts or get a newer browser" - page works for non-js users but is somewhat crippled : good page works perfectly without js : exce…
Realtime Bitcoin Stats
61–70 of 152 posts
Re: Realtime Bitcoin Stats
#62Re: Realtime Bitcoin Stats
#63I think the buy/sell prices are reversed. Bid/ask is of course common terminology and the buying price will be higher than the selling price.
Perhaps switching to bid/ask would be a good idea to clear up the confusion, but it's potentially more confusing to people unfamiliar with financial markets.
Re: Realtime Bitcoin Stats
#64I love the visualization, but wow almost $200. Greater fool theory is at work here: http://en.wikipedia.org/wiki/Greater_fool_theory
Re: Realtime Bitcoin Stats
#65I love the visualization, but wow almost $200. Greater fool theory is at work here: http://en.wikipedia.org/wiki/Greater_fool_theory
Note they also use the Ƀ (B with stroke) to represent Bitcoin. Kudos to ECOGEX for their discussion a few weeks ago that set this in motion (https://news.ycombinator.com/item?id=5451084).
Re: Realtime Bitcoin Stats
#66I love the visualization, but wow almost $200. Greater fool theory is at work here: http://en.wikipedia.org/wiki/Greater_fool_theory
Definitely a bubble forming - bitcoins marketcap was 1B only a week ago ( http://blockchain.info/charts/market-cap ). Note they also use the Ƀ (B with stroke) to represent Bitcoin. Kudos to ECOGEX for their discussion a few weeks ago that set this in motion ( https://news.ycombinator.com/item?id=5451084 ).
Re: Realtime Bitcoin Stats
#67How do you get all that data? I am super interested in knowing how something like this is built. How do you connect to the bitcoin network and serve the stats via this app. I am butchering my question but I hope it makes atleast some sense.
For price/trade data most (all?) exchange have APIs (e.x. https://en.bitcoin.it/wiki/MtGox/API)
Re: Realtime Bitcoin Stats
#68All this hype and speculation gives me a bit of pause, and worries me about actually mining. However, I keep wondering, what opportunities are there left to "sell the shovels" ?
Re: Realtime Bitcoin Stats
#69All this hype and speculation gives me a bit of pause, and worries me about actually mining. However, I keep wondering, what opportunities are there left to "sell the shovels" ?
Re: Realtime Bitcoin Stats
#70How do you calculate the hash rate? I have spent some time trying to understand the various hash rate estimates people come up with. Basically, I've determined that they're all 100% bogus. People like to work from the difficulty using bad/incorrect statistics since that's the most obvious way to get to something in the units of hashes/s, but I can never understand exactly what the process is. I'm genuinely curious to…
The network collaborates to adjust the mining difficulty, to keep the rate of new coins approximately the same over time: https://en.bitcoin.it/wiki/Difficulty There is a linear relationship between the hash rate and the difficulty (there is further discussion at that link).
It's in your last sentence that you go wrong. There's a relationship between the number of expected hashes per new block and the difficulty. That tells you something about the hash rate, but not the rate itself. Actually, it tells you something about the number of unique hashes being tried per new block (in expectation). And for some applications, that may, in fact, be what you care about.
Specifically, the appearance of new blocks is, if you like, a random variable with an exponential distribution. You can, in principle, estimate the rate parameter for this distribution using the difficulty and the timestamps in the Bitcoin log, but it's not straightforward. The last time I got into it, I was halfway through building a Bayesian estimator for the rate parameter using the log before I had to give up and move on to real work. I'll do it soon.