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

January 18th, 2016

mikebelshe My thoughts on the blocksize debate. belshe.com/2016/01/18/bit…

via Twitter Web Client (retweeted on 7:14 PM, Jan 18th, 2016 via Twitter Web Client)

bendavenport Just published my thoughts on one way to move forward towards resolution in the Bitcoin block size debate: medium.com/@bendavenport/…

via Twitter Web Client (retweeted on 7:14 PM, Jan 18th, 2016 via Twitter Web Client)

7) IMO each proposed change to Bitcoin’s consensus rules should be evaluated on its own regarding if it’s best suited as a hard or soft fork

via Twitter Web Client in reply to lopp

6) Hard forks can be used as a countermeasure against soft forks adopted by miners without the ecosystem’s consent.

via Twitter Web Client in reply to lopp

5) Soft forks can be used to counterbalance hard forks that remove too many restrictions from the previous version of the protocol.

via Twitter Web Client in reply to lopp

4) Soft forks degrade security for nodes that don’t upgrade.
Hard forks break security for nodes that don’t upgrade.

via Twitter Web Client in reply to lopp

3) Soft forks require a dozen entities (mining pools) to upgrade.
Hard forks require thousands of entities (nodes) to upgrade.

via Twitter Web Client in reply to lopp

2) Trade-offs between hard & soft forks are complex; neither type is inherently safer. Either can be detrimental to the ecosystem.

via Twitter Web Client in reply to lopp

1) “Soft forks are safer than hard forks!” - petertodd.org/2016/soft-fork…
“Not necessarily!” - chrispacia.wordpress.com/2016/01/17/rej…

via Twitter Web Client

RCasatta Updated stats. Protocols are now grouped. Here is the new pie. opreturn-976.appspot.com pic.twitter.com/kROTKLj4Ov

via Twitter for Mac (retweeted on 10:17 AM, Jan 18th, 2016 via Twitter Web Client)