@shannonNullCode yeah
@shannonNullCode No luck :-/
@kristovatlas @shannonNullCode A book cipher of some kind
@abbydactyl @shannonNullCode Not if they’re encrypted :)
You’re probably not as cypherpunk as @shannonNullCode pic.twitter.com/hw3RqBHPqC
“Stop trying to solve everything with blockchains. Build layers on top of blockchains.” - @shannonNullCode pic.twitter.com/gtg5oaRNOQ
@morcosa It’s 0.12, technically master
Ask and ye shall receive! https://t.co/brPclqKKct
https://t.co/EG07QipZvp
@ronnibahia you’d have to ask the attackers, but likely they wanted to show their displeasure with Classic’s hard forking code.
@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
@orweinberger The fuss is that many wallets are allowing users to shoot themselves in the foot.
@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.
@ziggamon Quite a few complaints on /r/bitcoin and /r/btc last I checked. Poor users with wallets that set static fees are SOL.
@ziggamon Yeah, @BitGo users have been unaffected unless they are API users who overrode our default parameters.
@WhalePanda Biggest problem IMO is wallets failing users by allowing them to broadcast txns that are unlikely to confirm in timely manner.
@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
@kyletorpey @Circle Custodial wallets should be easier to adapt fees - installed / non-custodial wallets will have harder time updating.
24 hours later:
Mempool: 44MB
Avg fee: 12 sat/B (FAIL)
Recommended fee: 44 sat/B
Seeing 5+ tx/s - mempool is growing
https://t.co/Dyilp0GvsD