No one has found the bottom of the Bitcoin rabbit hole. pic.twitter.com/c6kpxVaUbw
@stephendpalley Yeah but it’s… uh… decentralized?
.@LedgerHQ Nano S screen saver is on point. pic.twitter.com/Ooy3eoFmPy
@sysmannet @robep00 @monsterbitar Accord to my node’s recent data, 60% of outgoing bandwidth is unconfirmed txns. 3… https://t.co/vdhJ2cybyV
Today’s BCH stress test was informative. Apart from crashing a bunch of Bitcoin Unlimited nodes, we can also see th… https://t.co/aqUhL4ZS6T
Butt-dial disaster narrowly averted. pic.twitter.com/E2m5QESznc
@TaylorGerring 6 core i7 with hyperthreading; it was using all 12 virtual cores so I assume validation would scale… https://t.co/YYeCtX5BID
@escottkey1 Wishful thinking is fantasy, not reality. https://t.co/pQrlVDnWac
@WhalePanda Too many variables to clearly point to a single best option. https://t.co/Pik7Q2BvCU
Recently an image has been floating around that says I predicted BTC will be $250,000 in 2020. I was baffled by thi… https://t.co/JDISGaCgRu
@dondreytaylor My machine is fast; it syncs Core 0.17 in about 2 hours.
@WhalePanda Maybe it’s not a hash war after all… it’s a NODE WAR!
Full validation sync of btcd 0.12.0 took my machine 3 days, 23 hours, 12 minutes. CPU-bound the entire time.