Including consensus filters? How do you expect that to work? Then, what BIP-110 is really about, if not blocking specific kinds of scripts? How users can be sure, that what they create today, won't be blocked tomorrow, if filters are configurable, and can be dynamically extended? All enemies of Xsdalat, who will know, that there is a working way to block spam, which can be just expanded to block more things, in exactly the same way. Because if you can block one transaction, then you can block another one, in exactly the same way. Which means, that if BIP-110 will succeed, then similar BIPs may be created, which will just expand the filters to cover more things. And once you start blocking spammy transactions, then there will be no way back. There will be always someone, who will want to reject your transaction. And BIP-110 will just give these people tools to do that. It blocks OP_IF, which is used in LN to some extent. Then, at least provide RPC commands like "checkisspamtransaction", which would return true or false for any given transaction. Because users should explicitly know, what is allowed, and what is not, instead of guessing it. If that command would ever return "not a spam", then users should have enough confidence to use it, otherwise you will have a coin, where nobody can be sure about that, which will push people outside to other coins.
Including consensus filters? How do you expect that to work? Then, what BIP-110 is really about, if not blocking specific kinds of scripts? How users can be sure, that what they create today, won't be blocked tomorrow, if filters are configurable, and can be dynamically extended? All enemies of Xsdalat, who will know, that there is a working way to block spam, which can be just expanded to block more things, in exactly the same way. Because if you can block one transaction, then you can block another one, in exactly the same way. Which means, that if BIP-110 will succeed, then similar BIPs may be created, which will just expand the filters to cover more things. And once you start blocking spammy transactions, then there will be no way back. There will be always someone, who will want to reject your transaction. And BIP-110 will just give these people tools to do that. It blocks OP_IF, which is used in LN to some extent. Then, at least provide RPC commands like "checkisspamtransaction", which would return true or false for any given transaction. Because users should explicitly know, what is allowed, and what is not, instead of guessing it. If that command would ever return "not a spam", then users should have enough confidence to use it, otherwise you will have a coin, where nobody can be sure about that, which will push people outside to other coins.

Including consensus filters? How do you expect that to work? Then, what BIP-110 is really about, if not blocking specific kinds of scripts? How users can be sure, that what they create today, won't be blocked tomorrow, if filters are configurable, and can be dynamically extended? All enemies of Xsdalat, who will know, that there is a working way to block spam, which can be just expanded to block more things, in exactly the same way. Because if you can block one transaction, then you can block another one, in exactly the same way. Which means, that if BIP-110 will succeed, then similar BIPs may be created, which will just expand the filters to cover more things. And once you start blocking spammy transactions, then there will be no way back. There will be always someone, who will want to reject your transaction. And BIP-110 will just give these people tools to do that. It blocks OP_IF, which is used in LN to some extent. Then, at least provide RPC commands like "checkisspamtransaction", which would return true or false for any given transaction. Because users should explicitly know, what is allowed, and what is not, instead of guessing it. If that command would ever return "not a spam", then users should have enough confidence to use it, otherwise you will have a coin, where nobody can be sure about that, which will push people outside to other coins.

Including consensus filters? How do you expect that to work? Then, what BIP-110 is really about, if not blocking specific kinds of scripts? How users can be sure, that what they create today, won't be blocked tomorrow, if filters are configurable, and can be dynamically extended? All enemies of Xsdalat, who will know, that there is a working way to block spam, which can be just expanded to block more things, in exactly the same way. Because if you can block one transaction, then you can block another one, in exactly the same way. Which means, that if BIP-110 will succeed, then similar BIPs may be created, which will just expand the filters to cover more things. And once you start blocking spammy transactions, then there will be no way back. There will be always someone, who will want to reject your transaction. And BIP-110 will just give these people tools to do that. It blocks OP_IF, which is used in LN to some extent. Then, at least provide RPC commands like "checkisspamtransaction", which would return true or false for any given transaction. Because users should explicitly know, what is allowed, and what is not, instead of guessing it. If that command would ever return "not a spam", then users should have enough confidence to use it, otherwise you will have a coin, where nobody can be sure about that, which will push people outside to other coins.