Quote:
Originally Posted by TomCollins
It may be possible that someone does a contentious fork in the future, but that doesn't mean Bitcoin will have hard forked.
So you believe that bitcoin will be 1 MB forever? I don't think the majority of the bitcoin community agrees with that sentiment. That's why I quoted Heltok and NLNico noting that it's preposterous that that bitcoin will still have 1 MB blocksizes 50 years from now.
That's the crux of why bitcoin is stuck right now. 1 MB forever is such a stupid stance, we're obviously going to scale on chain at some point. So let's figure out the best way to make it happen.
BU is far from an optimal solution. I think there's better ways to handle the situation. But clearly, leaving the blocksize up to the developer community has been an utter disaster. That's why BU is gaining traction. Basically, it's core's own fault that there's a competing implementation that's gained enough support to block movement of any kind in the short term.
Quote:
Originally Posted by TomCollins
You lose all credibility if you suggest Tom Zander's broken proposal. It does not make anything more extensible. He is an amateur hack who is working solo on an alt-coin. No thanks.
I understand not liking Zander and/or not liking the FlexTrans implementation, but I haven't seen any good arguments against taking the well vetted concept of key-value pairs/JSON-like notation and applying it to bitcoin. That seems to be pretty much the way the bulk of data moves these days, so why not apply it to bitcoin.