In your opinion, is Bitcoin married to SHA-256 like it's married to other control variables like the 21e6 coin emission schedule, 10 minute block target, and 1MB blocks?
That's cute, equating limiting to 1MB blocks to being married to sha256. Don't try and take my one line comment as the opener for something completely unrelated on a completely different scale. This thread is about changing PoW, and I said clearly contentious is not the same as absurd.
Well of course changing PoW in anything but the most dire circumstances would be "absurd." But that is the SHTF scenario a ToominCoin 51% attack forces us to confront. So let's hope for the best while we plan for the worst.
Are you saying sha256 is a 'less arbitrary/more intrinsic' feature of Bitcoin than 1MB blocks?
I have no problem sacrificing sha256 in order to preserve 1MB blocks, unless you can demonstrate PoW change is more of a threat to our diverse/diffuse/defensible/resilient network than >1MB (2MB or whatever) blocks.
It seems you have reached the opposite conclusion, and say that 1MB blocks may be sacrificed in order to preserve sha256.
Is that correct, or was something lost in my translation from the Australian?
Characterizing Guy Corem & Co's POV as "absurd" only tells the rest of us you disagree with it, while leaving your audience wondering what your exact points of contention are.
Changing the proof of work that secures the system from hundreds of millions of dollars worth of mining hardware (whatever you make of the degree of centralisation) for a multi-billion dollar economy into one that will start again from scratch in the hands of a few thousands of dollars worth of GPUs at peoples' homes is as disruptive as increasing the block size?
It's a shame that you make me spell it out like this, clearly baiting me. I get sick of these discussions very quickly for that exact reason. I'll go hide in my mining corner while everyone continues their endless debate on that note.
There's no trick question here or lurking 'gotcha' waiting to pounce on you bro. I only asked you to spell it out because your highly-informed expert opinion is one of the most valuable to me.
I'm not sure you are getting what I'm saying, because you reference "hundreds of millions of dollars worth of mining hardware" that, in a contentious fork war, would have stopped being an asset to Bitcoin and started being a liability (or at least may have entered a grey zone where sha256's value is unclear and possibly zero or negative).
Catastrophic consensus failure would entail that Bitcoin must "start again from scratch." And facing headwinds of terrible publicity to boot.
In a DEFCON ZERO situation, by switching PoW we would have little to lose (despite the intrinsic chaos involved in moving from one stable state to another), much to gain by defending the blockchain from adversity, and maybe even mitigate the ASIC centralization problem in the process.
Perhaps where we disagree is on the impact of increasing block size on Bitcoin's antifragile aspect. IMO antifragility is an emergent property of the diverse/diffuse/defensible/resilient network, and anything over 1MB tx + SEGWIT blocks are too risky.
I know that's a controversial opinion, but being out on the fringe isn't so bad when I am in good company with the 'let's consider DECREASING max_block' crowd, to whom I am sympathetic in that I'd rather set max_block at too low a value than too high.
Thanks for stepping into the endless debate to LMK your POV. I think I got it now, so you can go back to making Bitcoin more awesome!