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… https://t.co/wW6lpFwX4L

via Twitter Web Client

Full validation sync of zcashd 2.0.1 took my machine 6 hours 11 minutes with dbcache=24000. Zcash was CPU bound the… https://t.co/XektEJr3kX

via Twitter Web Client

@AriDavidPaul @arjunblj @lawmaster Are you saying that Bitcoin is fundamentally insecure if its hashrate drops to 1… https://t.co/PKvtfHR605

via Twitter Web Client

RT @PeterMcCormack: WBD053 with Michael Cordner, @yeastplume, a developer working on Grin’s implementation of Mimblewimble is available. We…

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… https://t.co/rVA7IFGgJw

via Twitter for Android

@Xor231 Yeah this is why I didn’t run the test originally, but then several folks requested it after I posted my im… https://t.co/014jbf4Xr2

via Twitter Web Client

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… https://t.co/FWrlW5QJqN

via Twitter Web Client