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

August 25th, 2015

BitGo BitGo responds to customer demands by supporting increased block sizes. ow.ly/Rn16m

via Hootsuite (retweeted on 8:10 PM, Aug 25th, 2015 via Twitter for Android)

/r/Bitcoin moderators have implemented CSS to conceal their censorship and completely alter the meaning of comments. https://t.co/5QiXG1tS6A

via Twitter Web Client

RT @DanSpuller: NC Bitcoin Enthusiasts Rally for Better Cryptocurrency Legislation | @ExitEvent http://t.co/QKpP65paCV @rcsherwo @Bill_Warn…

via Twitter Web Client

@mikestable I don’t think that’s what pugs were designed for. RTFM!

via Twitter Web Client in reply to mikestable

@Satoshi_N_ Last I checked, @ButtCoin doesn’t even /have/ an exchange rate. Come back when you create something valuable.

via Twitter Web Client in reply to Satoshi_N_

@pierebel It’s unlikely because the median of miner votes would have to be to double the hard cap every 3 months.

via Twitter Web Client in reply to pierebel

“Multisig on steroids using tree signatures” via @pwuille https://t.co/oeL1XIvdwx

via Twitter Web Client

@pierebel Updating p2p code won’t cause a hard fork, though not updating your node would cause you to reject blocks > 32 MB.

via Twitter Web Client in reply to pierebel

@pierebel I believe further modifications would be required; BIP101 would give us 4 years to make the mods & test them.

via Twitter Web Client in reply to pierebel

BIP101: miners create fee market by setting individual soft caps and competing against other miners as hard cap grows to 8GB by 2036.

via Twitter Web Client in reply to lopp

BIP100: miners create fee market by voting on adjustable system-wide hard cap that maxes out at 32MB. Unlikely, but could reach 32MB in 1yr.

via Twitter Web Client

@01101O10 xtnodes.com is back and better than ever. Don’t forget xt.coin.dance; good luck taking them all down.

via Twitter Web Client in reply to 01101O10