Pieter Wuille says "data storage through other means is already possible (including through ways that are cheaper than through OP_RETURN)"
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.
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.
GitHub
datacarriersize: Match more datacarrying by luke-jr · Pull Request #28408 · bitcoin/bitcoin
Updates -datacarriersize to be effective with newer datacarrying styles.
GitHub
Witness scripts being abused to bypass datacarriersize limit (CVE-2023-50428) · Issue #29187 · bitcoin/bitcoin
The datacarriersize policy option is meant to limit the size of extra data allowed in transactions for relaying and mining. Since the end of 2022, ...
Bitcoin Stack Exchange
Implications of OP_RETURN changes in upcoming Bitcoin Core version 30.0
As you may know, there has been a debate around the upcoming release of Bitcoin Core. I hear the arguments against it and I agree that Bitcoin is m...
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.
GitHub
datacarriersize: Match more datacarrying by luke-jr · Pull Request #28408 · bitcoin/bitcoin
Updates -datacarriersize to be effective with newer datacarrying styles.
GitHub
Witness scripts being abused to bypass datacarriersize limit (CVE-2023-50428) · Issue #29187 · bitcoin/bitcoin
The datacarriersize policy option is meant to limit the size of extra data allowed in transactions for relaying and mining. Since the end of 2022, ...
