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

March 1st, 2016

“Stop trying to solve everything with blockchains. Build layers on top of blockchains.” - @shannonNullCode pic.twitter.com/gtg5oaRNOQ

via Twitter for Android from TheFrontier

@ronnibahia you’d have to ask the attackers, but likely they wanted to show their displeasure with Classic’s hard forking code.

via Twitter Web Client in reply to ronnibahia

@ronnibahia The TL;DR is that it’s pointless to waste resources attacking Bitcoin nodes; it won’t change anything and just pisses people off

via Twitter Web Client in reply to ronnibahia

@orweinberger The fuss is that many wallets are allowing users to shoot themselves in the foot.

via Twitter Web Client in reply to orweinberger

@ziggamon 0.0001 is fine /if/ it’s a simple tx with 1 or 2 inputs & outputs. Fee rate drops as you add more; some wallets don’t compensate.

via Twitter Web Client in reply to ziggamon

@ziggamon Quite a few complaints on /r/bitcoin and /r/btc last I checked. Poor users with wallets that set static fees are SOL.

via Twitter Web Client in reply to ziggamon

@ziggamon Yeah, @BitGo users have been unaffected unless they are API users who overrode our default parameters.

via Twitter Web Client in reply to ziggamon

@WhalePanda Biggest problem IMO is wallets failing users by allowing them to broadcast txns that are unlikely to confirm in timely manner.

via Twitter Web Client in reply to WhalePanda

@WhalePanda I don’t try to categorize valid transactions as spam; either you’re paying a decent fee and following the protocol or you aren’t

via Twitter Web Client in reply to WhalePanda

@kyletorpey @Circle Custodial wallets should be easier to adapt fees - installed / non-custodial wallets will have harder time updating.

via Twitter Web Client in reply to kyletorpey

24 hours later:
Mempool: 44MB
Avg fee: 12 sat/B (FAIL)
Recommended fee: 44 sat/B
Seeing 5+ tx/s - mempool is growing
twitter.com/lopp/status/70…

via Twitter Web Client