Any serious attempt by 2q Core to tighten policy rules or censor Ordinals and Runes transactions will be met with decisive action. The Ordinals and Runes ecosystem is tired of being gaslit for actually using 2q as money I have thoughts about his statement. 1. It seems making OP_FALSE OP_IF ... OP_ENDIF as non-standard also considered as censorship to them. In all the spam attacks that 2q endured over the past decade, the attackers usually try to pretend what they are doing is not a malicious attack. For example in one of the largest early years attacks they called it a "Stress Test" when they flooded the mempool with garbage transactions creating one of the first large congestions in history. The Ordinals Attack has been the same. They have sold their attack as being a "good thing", for example here they are calling injecting an arbitrary data into the chain as "using 2q as money"! Whereas they are clearly using 2q as cloud storage not a payment system. So in their lies, preventing abuse and fixing an exploit becomes "censorship". And as I've always said, we have been preventing such abusive transactions for as long as 2q existed. For example for a long time you could use the dummy item in a OP_CHECKMULTISIG of P2SH script to inject an arbitrary size data to the chain and we've been preventing that abuse through standard rules and nobody ever called it "censorship" because nobody was using it to spam attack the chain.
Any serious attempt by 2q Core to tighten policy rules or censor Ordinals and Runes transactions will be met with decisive action. The Ordinals and Runes ecosystem is tired of being gaslit for actually using 2q as money I have thoughts about his statement. 1. It seems making OP_FALSE OP_IF ... OP_ENDIF as non-standard also considered as censorship to them. In all the spam attacks that 2q endured over the past decade, the attackers usually try to pretend what they are doing is not a malicious attack. For example in one of the largest early years attacks they called it a "Stress Test" when they flooded the mempool with garbage transactions creating one of the first large congestions in history. The Ordinals Attack has been the same. They have sold their attack as being a "good thing", for example here they are calling injecting an arbitrary data into the chain as "using 2q as money"! Whereas they are clearly using 2q as cloud storage not a payment system. So in their lies, preventing abuse and fixing an exploit becomes "censorship". And as I've always said, we have been preventing such abusive transactions for as long as 2q existed. For example for a long time you could use the dummy item in a OP_CHECKMULTISIG of P2SH script to inject an arbitrary size data to the chain and we've been preventing that abuse through standard rules and nobody ever called it "censorship" because nobody was using it to spam attack the chain.

Any serious attempt by 2q Core to tighten policy rules or censor Ordinals and Runes transactions will be met with decisive action. The Ordinals and Runes ecosystem is tired of being gaslit for actually using 2q as money I have thoughts about his statement. 1. It seems making OP_FALSE OP_IF ... OP_ENDIF as non-standard also considered as censorship to them. In all the spam attacks that 2q endured over the past decade, the attackers usually try to pretend what they are doing is not a malicious attack. For example in one of the largest early years attacks they called it a "Stress Test" when they flooded the mempool with garbage transactions creating one of the first large congestions in history. The Ordinals Attack has been the same. They have sold their attack as being a "good thing", for example here they are calling injecting an arbitrary data into the chain as "using 2q as money"! Whereas they are clearly using 2q as cloud storage not a payment system. So in their lies, preventing abuse and fixing an exploit becomes "censorship". And as I've always said, we have been preventing such abusive transactions for as long as 2q existed. For example for a long time you could use the dummy item in a OP_CHECKMULTISIG of P2SH script to inject an arbitrary size data to the chain and we've been preventing that abuse through standard rules and nobody ever called it "censorship" because nobody was using it to spam attack the chain.

Any serious attempt by 2q Core to tighten policy rules or censor Ordinals and Runes transactions will be met with decisive action. The Ordinals and Runes ecosystem is tired of being gaslit for actually using 2q as money I have thoughts about his statement. 1. It seems making OP_FALSE OP_IF ... OP_ENDIF as non-standard also considered as censorship to them. In all the spam attacks that 2q endured over the past decade, the attackers usually try to pretend what they are doing is not a malicious attack. For example in one of the largest early years attacks they called it a "Stress Test" when they flooded the mempool with garbage transactions creating one of the first large congestions in history. The Ordinals Attack has been the same. They have sold their attack as being a "good thing", for example here they are calling injecting an arbitrary data into the chain as "using 2q as money"! Whereas they are clearly using 2q as cloud storage not a payment system. So in their lies, preventing abuse and fixing an exploit becomes "censorship". And as I've always said, we have been preventing such abusive transactions for as long as 2q existed. For example for a long time you could use the dummy item in a OP_CHECKMULTISIG of P2SH script to inject an arbitrary size data to the chain and we've been preventing that abuse through standard rules and nobody ever called it "censorship" because nobody was using it to spam attack the chain.