I have more in my head to write in response to your post than my time permits at the moment... So I'll try to reply to the part that seems most central to me:
Hehe, me too, but I can't resist to pull out a few minutes of my day ... hard forks are really bad ... At least I'm a very fast typer
I have so many things to say to each of your sentence. I try to keep it short, and I'll do the bad old game of quoting ... sorry for this ...
Just "lifting the limit" doesn't do the job, though. We saw in the field that 10 MB/10 minutes is about the throughput we can do without improving node software. Craig and Calvin showed us (through Peters excellent analysis of BSV big-block head-through-wall mining).
I am convinced that the network can process more. Especially when (if) we need a sustained throughput of more than 10mb in the future. Network infrastructure and software will have matured greatly to this time. Ironically, the CTOR fork pushed this farer into the future by harming adoption.
Some engineering is necessary and if a consensus rule change like CTOR that is relatively non-disruptive and economically irrelevant and doesn't change any monetary properties can greatly help this then I'm all *for* it. And in the end (trhough enabling scaling) it *does* even help adoption.
Some problems with CTOR (as it was done):
- it had no consensus, not in the larger world (see BU membership vote), not in the small world of developers (devs of BU, XT and SV have been against). This made it highly disruptive and economically relevant. It even changed monetary properties by doubling the number of coins ...
- it's benefit is said to increase the efficiency of graphene from 98% (achieved by BU) to 99.6%. With 10mb blocks this means block processing size of 40kb instead of 200kb. I don't think this is the bottleneck (Bitcoin was able to process 1mb blocks in 2015/16 without any block propagation compression).
- Andrew Stone said that similar efficiency increases can be achieved without a CTOR protocol change.
- it ignores the role of orphans to (1) be a natural limit, useful to keep capacity in a limit which allows to investigate and improve effects of scaling on other factors (CPU, storage, synchronization), and which can help to get a fee market, and (2) incentivize miners to invest in connectivity to earn more from fees.
- it guaranteed a chainsplit while other hardfork features could have been gradually activated by hashpower on one chain.
- there was not a single scientific paper or research about it. The best we got have been a couple of promotional block posts and a long video with seven developers around ABC.
It's not enough to just remove the limit (or push it to 128MB) in full knowledge that the network wont be able to digest those blocks without sky-high orphan rates. That's "selling shit you can't deliver" in my eyes and that is something I absolutely hate (maybe that's why I hate CSW so much).
That's exactly what my Lightning maximalist buddies tell me: "it's scam to promote Bitcoin as an universal payment system since it can't do this without Lightning". Going the path of ABC seems to lead back to what we should have left behind: Blocksize-limit != real blocksize. If orphans serve as a natural limit below the blocksize limit, I see no problem at all.
I want to react to one more issue you bring up: Schnorr sigs. If those put a huge burden on wallet and infrastructure devs (and also users need to be educated and helped and shit) then I'm against them. We've seen huge resource drain of this type with cashaddr and it didn't improve anything in my mind, like at all: users are still sending the wrong coin to the wrong address and they're even more confused than before.
If Amaury actually pushes through things (like schnorr sigs?) against major opposition I'll probably be on opposition side of a split that time. Haha: Norway can throw a party and have a new song made: "I'll splinter you bches to pieceeeeas!!! I'll fracture your every boooooune!!!". Dark!
Why do you think they will change their behaviour, after most of the oposition forked off? I hoped they grow up after the DAA-thing, after Cashaddr, after the May hardfork. After seing where the Nov fork is headed on, I gave up. There will be no major oposition. Neither CSW, nor CoinGeek, nor me, nor Norway, nor BU membership, nor XT will invest energy in oposing it. With the Nov fork BCH has become property of ABC and friends. In best case BU and XT will be asked, but like with CTOR, they will not count when they don't agree. There will be no split, the split already happened. You'll have no other choice than going with ABC or switching to SV. I know you will not like this