Failing to get where you wanted to go doesn't mean you weren't trying.
They want to take away options for transaction types.
Discussion
Transaction types like what? Are you referring to OP_RETURN because that is an entirely unspendable output so THAT can't be a transaction. Unless you think 40 bytes isn't enough for a 32 byte imprinted hash anchor.
It isn't enough for whirlpool. Do we believe users deserve privacy or not?
Because one implementation of coinjoining needs 4 more bytes of data (which you can set in your node BTW unless you suddenly think filters work) that's why OP_RETURN needs 100KB?
Do you want everyone to run knots filters?
If not you don't want anything about bitcoin to change you are just selfish and externalizing costs and risks demanding I do it for you.
If so, you would ban whirlpool.
What I want is irrelevant. What I do is the matter. Also, nothing about whirlpool REQUIRES 46 bytes. They are just not good at using metadata hashes efficiently.