sjors @sjors@m.sprovoost.nl

@waxwing @Firedragon888 @kekcoin probably not hot until it hits blocks from 2019. The assumevalid feature causes it to not verify signatures up to a fairly recent block, so CPU isn't a bottleneck. Memory/disk reads run less hot. Downloading <0.5 MB per second (typical verification speed I've seen on ARM chips) might cause more heat though. Maybe put it on your sink so heat can dissipate. Not in your pants: I've a phone explode, it's not good for your legs 🙂

@waxwing @jon well there seems to be at least one VC out there who gets it: https://youtube.com/watch?v=zFN__b6ARH4 (final talk on day 2 of #MCC2019)

@emzy I got mine pretty quickly. I paid on chain, because I didn't want to risk missing out while opening a new Lightning channel. Next year I should either just pre-fund a channel or hope Atomic Multi Path is done by then. The latter would be better for privacy.

@waxwing I actually stopped listening to the A16Z podcast a year ago because indeed they seem either utterly clueless or willfully ignorant (bags).

@waxwing this was indeed a particularly good one.

@haakon pretty good progress in the first day... And it works with ⚡️

@waxwing I move most new contacts to Signal and just try to avoid using that phone number for 2FA. I wish Signal just let you register an arbitrary user id. It's strictly better than WhatsApp privacy wise, since that also requires a phone number.

I use Slack for very few things.

It shouldn't be hard to make IRC suck less, but there's not much incentive. Maybe Casa can add a bouncer?

Twitter is a timesuck, so I don't have DM open. My email is easy to find if it's important enough to bother me.

I wanted something bigger to run my node on. Is it overkill? Yes! Do you really need that much CPU cooling for a server? Maybe.

Before: Khadas VIM2 Max with 256 GB SD card for blockdir, which ran out of space a week ago. It was also just unstable: randomly declaring blocks invalid and crashing, especially when connected to network cable. https://www.khadas.com/vim

After: Intel i5, 32 GB RAM, 512 GB SSD (using PCIe connector at the bottom of the motherboard). Case: Thermaltake Core V1

I gave an updated presentation at Advancing Bitcoin last month: https://vimeo.com/316634495

Slides: https://github.com/Sjors/presentations/blob/master/2019-02-08%20London%20-%20Advancing%20Bitcoin/2019-02%20London%20Advancing%20Bitcoin.pdf

HWI (works with Bitcoin Core 0.18.0 which is still pending release): https://github.com/bitcoin-core/HWI

@htimsxela at the time transactions were pay to public key, rather than pay to public hash. So the pubkey would have been known with or without spending. But yeah, CSW and friends really seem to love fake cryprographic proof.

How to use a hardware wallet directly with Bitcoin Core: https://youtu.be/SUDkYbkcTsQ

Slides (with source in Markdown): https://github.com/Sjors/presentations/blob/master/2018-09-19%20London%20Bitcoin%20Devs/2018-09%20London%20Bitcoin%20Devs%200.5.pdf

@kallewoof it appears he apologized for this: https://twitter.com/earlzdotnet/status/1043247878829834240

My five seconds of fame: "Sjors is actually, like he’s a dev"

@notmandatory if your hourly rate isn't outpacing inflation you're doing something wrong :-)

The link is hi-res, but if I look at the image attached to my toot it seems blurry.