pull down to refresh
The illegal content argument is an argument against arbitrary data so far as I'm aware.
When I bring up structured data, it is a reference to PBAs such as those that do make use of quadratic signature verification techniques, oftentimes leveraging legacy sigops accounting rules.
1500s for a block that normally takes 1s is pretty bad in the one public demo I did see, and there are others.
I imagine the Great Consensus Cleanup (which also addresses many of these cases) could probably get more widespread support than BIP 110.
Given that BIP 110 has been mostly marketed as reducing arbitrary data, it feels like a strange way to go about dealing with quadratic hashing et al concerns.
BIP 54 mitigates the threat but does not provide sufficient protection.
It takes 1500s to verify a block down to 5s, which is still 500% worse than what most are used to in IBD so far.
We should be restricting scriptPubKey length. 520b was good, 34b is even better.
Are you referring to something like a transaction that is designed to have quadratic hashing and take other nodes a very long time to verify, or are you referring to people embedding "illegal" content?
Probably there are other things of which I am not even aware. But I'd be grateful if you were willing to expand on this a bit.