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

October 18th, 2017

khannib Introducing forks.network: monitoring the activity off all current and future forks of Bitcoin. pic.twitter.com/aJt4f7djlp

via Twitter Web Client (retweeted on 2:48 PM, Oct 18th, 2017 via Twitter Web Client)

@Ragnarly Nope, can’t recall any failures to eject. Probably because I slapped the foregrip on it as soon as I boug..twitter.com/i/web/status/9…Aw

via Twitter Web Client in reply to Ragnarly

@StrikerBee Coinbase outputs and possibly a single manual locktime tx that we then fan out into a ton of UTXOs to seed wallets with.

via Twitter Web Client in reply to StrikerBee

My theory: someone at Benton County Sheriff’s Office came up with a fake excuse to mine BTC on the taxpayer’s dime…twitter.com/i/web/status/9…3u

via Twitter Web Client

@cm0nt0y4 It’s motivation to work harder 🙃

via Twitter Web Client in reply to cm0nt0y4

@eric_lombrozo @mikebelshe Meh, there’s no evidence that this has anything to do with SegWit2X - that’s pure specul..twitter.com/i/web/status/9…wH

via Twitter Web Client in reply to eric_lombrozo

@Bilthon Native replay protection, no. Each wallet will be responsible for writing their own hacky replay protection logic.

via Twitter Web Client in reply to Bilthon

@Bilthon For the upcoming SegWit2X fork of Bitcoin.

via Twitter Web Client in reply to Bilthon

@CryptoEthan Local PD isn’t going to send out the SWAT team again without calling me first.

via Twitter Web Client in reply to CryptoEthan

When assholes are making threats against your life but this replay protection code ain’t gonna write itself. pic.twitter.com/d4MLox4kwd

via Twitter for Android