TL;DR - the most popular way for banks to send money to each other works by sending text files via SFTP. https://t.co/zVshaurwjd
There are no metrics that define what rules comprise the real Bitcoin b/c you’d first need to come to consensus about what metrics to use.
@kristovatlas Users who only intend to transact on fork Y have no incentive to protect users who remain on original… https://t.co/2psxxCvwwH
@nikzh @santisiri @Blockchair Satellites, Ham radio, Twitter, carrier pigeons… The more comms channels, the more robust the system.
@nikzh @santisiri @Blockchair Folks are moving forward 😎 https://t.co/Zf5AgQBcvm
@nikzh @santisiri @Blockchair Good luck tracking fees for transactions conducted via payment channels.
@JonathanVaage @kristovatlas Not children, users who are sending real money. If you make it easy for users to make… https://t.co/Rr5WD32pNo
@dagur @21 @BitPay Satoshis per weight. But it’s effectively still satoshis per (legacy) bytes. It’s not that hard.
@kristovatlas When you say “doesn’t share the concern” I hear: has a perspective that creates a moral hazard b/c th… https://t.co/pUXv3G7jtH
Price increased 60% in the 2 months since this tweet. I rest my case. https://t.co/htJzAdzqQq
@kristovatlas Argument has been made numerous times. If group X is making changes to fork off, onus is on X to make… https://t.co/zgYToHaWF6
Sure is odd that @AntPoolBITMAIN is mining smaller blocks than are allowed… pic.twitter.com/n0AlzjZeBo
@alistairmilne @BitGo There’s a SegWit transaction chart available at oxt.me/charts
The first multisig SegWit spend, brought to you by @BitGo!
OP_RETURN 🎉 BitGo â¤âš¡https://t.co/wz0J2jRCZZ
@checksum0 This issue is unrelated to replay protection.
Cross-chain address confusion costs continue 🔈. Imagine 3 Bitcoin forks that all use indistinguishable addresses… https://t.co/EXXZro8Egl
This #SegWit party is legit. pic.twitter.com/g29BlmjLiR