Lauda, so in addition to the 'quadratic' risk (for which you admit there is a fix but core is not implementing),
you're also giving us the 'nothing is better than something' argument.
So let's set the situation straight. We have two proposals: you're also giving us the 'nothing is better than something' argument.
1. 2MB Block size
- doubles the theoretical tps
- introduces a new attack vector
- Simple change
- Hard fork
2. SegWit
- Fixes transaction malleability
- Fraud proofs
- Simpler script upgrades
- Theoretical tps possibly equal or higher than with 2 MB blocks depending on adoption
- Somewhat complex; decent complexity for inexperienced users
- Soft fork
I'm definitely shilling for Core because obviously SegWit is not far superior to a 'simple' block size increase.
I 'don't seem to always support them'. Do I support them in 'Core vs Classic', 'SegWit vs 2 MB blocks'? Yes.