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

September 25th, 2017

@phildaian I think there’s room for improvement given that a tiny fraction of actual node operators (miners) get to..twitter.com/i/web/status/9…tm

via Twitter Web Client in reply to phildaian

@phildaian If said actors are able to impose a cost upon the ecosystem that is greater than the value of the operat..twitter.com/i/web/status/9…1M

via Twitter Web Client in reply to phildaian

@BeerdHead Not sure that’s a great example given that the use of Public Library resources is regulated by librarian..twitter.com/i/web/status/9…vM

via Twitter Web Client in reply to BeerdHead

@BeerdHead You mean, real-world examples of the Tragedy of the Commons? Check out dummies.com/education/scie…

via Twitter Web Client in reply to BeerdHead

@phildaian You can absolutely be economically rational and simultaneously inconsiderate of using shared resources… thus the tragedy.

via Twitter Web Client in reply to phildaian

4) A distributed append-only log has immense utility; if you offer cheap / free writing of data to other peoples’ hard drives, expect abuse.

via Twitter Web Client in reply to lopp

3) When asked why they were using the blockchain when any relational database would suffice, they answer “because it’s easy and we can.”

via Twitter Web Client in reply to lopp

2) I’ve seen companies create on-chain txns, sending within the same wallet, during low-fee periods, just for internal accounting purposes.

via Twitter Web Client in reply to lopp

1) If you make a public resource absurdly cheap / free then it will be abused by ignorant / inconsiderate people. Tragedy of the Commons.

via Twitter Web Client

@VinnyLingham I find it highly suspicious that @pmarca is listed at #2 when he hasn’t tweeted in what, over a year?

via Twitter Web Client in reply to VinnyLingham

@jgarzik It’s possible, though in my experience high txn volume enterprises tend to not really care about on-chain privacy.

via Twitter Web Client in reply to jgarzik

@PaytheTollman Creating room for more transactions means customers will pay lower fees and get faster confirmations..twitter.com/i/web/status/9…kK

via Twitter Web Client in reply to PaytheTollman

Same goes for Bitcoin companies that won’t batch transaction sends to create efficient many-output transactions. twitter.com/lopp/status/91…

via Twitter Web Client

Bitcoin companies that won’t add SegWit support but do push for larger blocks are trying to externalize their dev costs onto the network.

via Twitter Web Client

Wow, Greg Maxwell performed an audit of @armory’s fragmented backup functionality for funsies? twitter.com/kristovatlas/s…

via Twitter Web Client

I wonder if @Bitso @YourBTCC @RipioApp @ShapeShift_io are going to follow their own guidance for SegWit2X?..twitter.com/i/web/status/9…A9

via Twitter Web Client