Anywhere below 50 is fine.
this +++
I've been lurking here quite a while and have read most every post beginning to end. I find this "Virtual Entity" a fascinating experiment in unregulated, unverified, and anonymous business. I truly mean that in a positive way.
Though, there is one thing that's troubled me during this adventure.
The "network and psu" issues have happened before and there is this "we're selling surplus inventory because we don't want to scare the bitcoin community with a 51% attack" thing.
first I monitor the hash data very closely and personally verify the calculations and numbers. There is a "theoretical" 24 th/s deployed, but in general it hovers around 18 th/s with a 4th/s swing (2 above and 2 below) occasionally spiking another 2 in either direction. Now the network has consistently stays above 70 th/s and we haven't seen 50 th/s in ages (bitcoin time). AM could easily (theoretically) deploy 50 th/s without risking an approach to a 51% attack.
That being said, I can't accept the "we're selling surplus inventory because we don't want to scare the bitcoin community with a 51% attack" argument (not saying I'm right, I've just been running this around alone in my head and honestly am interested in hearing others views on the subject). With my experience with software and hardware, I can only see the network and power management complexity double with double the hashrate. At 200 th/s, it seems odd (in my mind) to think there is feasible infrastructure in place to deal with it.
It seems strange not see this discussed more and I'm honestly interested in a fruitful discussion about it.
