RT @ndrchvzz: @lopp @pwuille And if you run a full node you can also check my cool script to view version stats https://t.co/7C6hM0JiDr
@pwuille Sure, it’s probably what people are more concerned about since any significant reorg would be incredibly disruptive.
@theonevortex @aantonop @pwuille lowest point in the past year was 180 - 200 days depending upon how you estimate. bitcoin.sipa.be/powdays-50k.png
@theonevortex @aantonop @pwuille I think it’s neat because it shows how thermodynamic security changes along w/hashing tech improvements.
@theonevortex @aantonop @pwuille We added a description along w/charts to bitcoin.sipa.be/index.html - please let us know if it’s still unclear
A gem I found in @pwuille’s code: amount of time it would take for an attacker w/100% of current hashrate to rewrit… https://t.co/fmvXTEYe3p
SegWit signaling starts soon, so I helped @pwuille expose more of his charts. Check them out at bitcoin.sipa.be/versions.html
Higher fees price inefficient / low value transactions off the blockchain. Interesting quote from @wences at @xapo.… https://t.co/WwNOfQy53Q
@timpastoor @alansilbert The “unfairness” is generally the fee discrepancy between sending and receiving funds; segwit rebalances it some.
@alansilbert They may receive large numbers of low value transactions, then have to pay high fees to spend all the UTXOs.
@alansilbert Like payment processors and remittance providers… not sure how to quantify it but I see this problem regularly.
@alansilbert It becomes a bigger issue if your business model results in you collecting massive numbers of low value UTXOs.