BitcoinIsFuture's avatar
BitcoinIsFuture 2 months ago
Compromised Core devs removed all policy filters on OP_RETURN size to make it 100 000 Bytes. Same change on BSV led to: image Their actions speak, not their believes. They deliberately allowed inscriptions and used it as excuse that spam can't be stopped. The are compromised and Core V30 is an attack on Bitcoin. View quoted note →
BitcoinIsFuture's avatar BitcoinIsFuture
Pieter Wuille says "data storage through other means is already possible (including through ways that are cheaper than through OP_RETURN)" image Core is completely captured and their actions speak vlolumes. Core devs deliberately allowed inscriptions spam by rejecting Luke's fix in 2024. They are now using that as excuse that "spam can't be reduced" or that "spam already exists on Bitcoin because of inscription spam". That is dishonest and an internal attack on Bitcoin. Core devs deliberately allow spam and then defend it like shitcoiners. They also maliciously changed the definition of datacarriersize. Bitcoin Knots has fixed those issues. https://github.com/bitcoin/bitcoin/pull/28408 https://github.com/bitcoin/bitcoin/issues/29187 https://bitcoin.stackexchange.com/questions/127895/implications-of-op-return-changes-in-upcoming-bitcoin-core-version-30-0/127903#127903 View quoted note →
View quoted note →

Replies (1)