It all points to the possibility that those illogical devs have being compromised somehow.... π€
Thread
Login to reply
Replies (5)

See the compromised Core devs who rejected Luke's PR that fixes inscription spam. They are the bad actors (the NACKers)
They revealed themselves with their public comments on OP_RETRUN being dishonest and manipulative.
The guys that ACKed are the good guys we have.
https://github.com/bitcoin/bitcoin/pull/28408
https://github.com/bitcoin/bitcoin/issues/29187
Bitcoin Knots has fixed those issues.
View quoted note →
https://github.com/bitcoin/bitcoin/pull/28408
https://github.com/bitcoin/bitcoin/issues/29187
Bitcoin Knots has fixed those issues.Didn't they tell you that filter don't work? Well see the current OP_RETRUN filter limiting data to less than 83 Bytes.


Letβs do a quick thought experiment. Imagine a government wants to attack Bitcoin. What could they do?
They can compromised a number of developers. The developers could start slowly degrading Bitcoin.
They could change the definition of Bitcoin being "digital currency that uses peer-to-peer technology" to just be a "peer-to-peer network".
They could change the definition of the datacarriersize.
Using that as argument they could deny fixing the inscriptions spam.
Then they could use the inscriptions spam as an argument that spam is unstoppable so they better blow up OP_RETURN and invite even more spam.
Just like BSV did after which someone uploaded CSAM to the BSV blockchain.
View quoted note β

View quoted note →

Core devs are compromised. Run your Bitcoin Knots nodes and protect Bitcoin Monetary network.
View quoted note β
View quoted note →
