lly processing large numbers of transactions on chain. What undermines that story is complaining about spam, setting cautious limits and particularly for the de facto reference implementation to set the default maximum at 2MB - what story does that tell?

2. There's an old adage - "You get what you measure". If we want higher capacity on BCH, we've got to be able to measure what the current capacity is. At the moment we really don't know. And that means we don't know if it is going up or even down. If we operate close to capacity, we'll be able to measure capacity, and that means we'll get more capacity.

3. We don't want to coddle the network too much - it has got to operate in an environment that we can expect to become ever more hostile as it grows. If it can't handle 'spam' from users who are trying to use the network, it won't handle attacks trying to bring it down. Increased usage helps the network to build and generate its immune response.

4. It's harder to do a DOS attack if we are operating at a larger capacity. Like you need a bigger bot army to DDOS a web server with a lot of capacity, you need to pay for a lot more transactions to DOS the BCH network if it is operating at a higher capacity.

More transactions on BCH? I say, 'Bring it on'.