The below is an off-site archive of all tweets posted by @lopp ever

December 4th, 2018

@askpascalandy Nah, I’m running the processes directly on my bare metal beast. We do use docker for running service..twitter.com/i/web/status/1…4L

via Twitter Web Client in reply to askpascalandy

Full validation sync of zcashd 2.0.1 took my machine 6 hours 11 minutes with dbcache=24000. Zcash was CPU bound the..twitter.com/i/web/status/1…kX

via Twitter Web Client

@AriDavidPaul @arjunblj @lawmaster Are you saying that Bitcoin is fundamentally insecure if its hashrate drops to 1..twitter.com/i/web/status/1…05

via Twitter Web Client in reply to AriDavidPaul

PeterMcCormack WBD053 with Michael Cordner, @yeastplume, a developer working on Grin’s implementation of Mimblewimble is available..twitter.com/i/web/status/1…Qe

via Twitter Web Client (retweeted on 10:11 AM, Dec 4th, 2018 via Twitter Web Client)

@z000ao8q That’s an easy estimate: zero. Running a fully validating node requires no hashpower.

via Twitter Web Client in reply to z000ao8q

@Xor231 Did you set the coin cache to be several GB? If not, it runs fine with the defaults. The problems I hit wer..twitter.com/i/web/status/1…Jw

via Twitter for Android in reply to Xor231

@Xor231 Yeah this is why I didn’t run the test originally, but then several folks requested it after I posted my im..twitter.com/i/web/status/1…r2

via Twitter Web Client in reply to Xor231

I ran a comparison sync of Bitcoin Knots 0.16.3 to height 547100 and it took 327 minutes. I bet Knots 0.17 would be..twitter.com/i/web/status/1…qN

via Twitter Web Client