= 27d567bc2d48d9f40e9ccc20ea370b15)
SilasBarta comments on General Bitcoin discussion thread (June 2011) - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (102)
UPDATE: For those of you who are interested in comparing your hash-fast mining rig to FLOP-fast supercomputers out there, I just recently noticed that Bitcoin Watch reports both the network's hashrate per second and its FLOP rate per second. I don't know how they derived the second figure (see "User:"jimrandomh's comments on the difficulty of comparing hash-type and floating point computations).
Dividing the two, it's implicitly assuming ~12,700 floating point operation equivalents per computed SHA-256 hash. For the 2+ users among us that have a 1.6 GHash/sec rig, that makes it equivalent to a ~20 TFLOP/s supercomputer, comparable to the state of the art in supercomputing circa 2001-2002.
Again, I make no pretense of vouching for the 12,700 FLOP/SHA-256 hash figure.