pull down to refresh
0 sats \ 1 reply \ @gregtonoski 30 Sep \ on: All the other stuff happening in Bitcoin bitcoin
And there is the proposal to discontinue OP_RETURN (consensus rule) to reduce spam.
Apples 🍏 to oranges 🍊 comparison.
Spam and monetary Bitcoin transactions are two completely different beasts, "ain't the same ballpark, ain't the same league, ain't even the same f* sport". If you run a genuine node you accept monetary Bitcoin transactions flow and reject spam.
Calle is seeking attention (and grants $$$) only.
It wouldn't have been difficult to support his simple claims if they had been true. The wall of his text is lacking substance.
Everlasting "best we can do is attack Bitcoin Knots and call Luke crazy" by malicious actors from Bitcoin™ COREporation:

There isn't interactive CLI mode (except terminal in GUI in bitcoin-qt). Instead,
curl
or other CLI tools are used to send commands to the daemon bitcoind
(over http). The daemon must be started with the "-server" option beforehand in order to accept the commands."You can't have nothing burger without word salad". TL;DR Run Bitcoin Knots https://bitcoinknots.org/ if you like.
What is "data transactions" according to your definition?
I provided link to the description of the vulnerability (and there are more of them) and not "inscriptions".
Lookup CVE database and the GitHub repo, e.g. "https://github.com/bitcoin/bitcoin/issues/29187".
There is a serious, well-known vulnerability in the announced Bitcoin Core v29.1. Why don't they fix it like it is done in Bitcoin Knots: "https://github.com/bitcoinknots/bitcoin/releases/tag/v29.1.knots20250903"?