While I don't think spam on Bitcoin represent any existential technical treat, I *do* think the spread of these pseudo-philosophical fallacies and factual misrepresentations of the way Bitcoin works represents a tragic failure of Bitcoin-related education and popularization so far.
> There's no such thing as spam on Bitcoin.
Factually false. Spam is defined as unsolicited/unwanted digital messages in bulk, and in Bitcoin there are lots of unsolicited/unwanted digital messages in bulk, at all levels: general p2p networking messages among nodes, transactions, blocks, Lightning Network things, etc. This is hardly surprising: spam exists in all big digital platforms and systems, it's more present in pseudonymous and permissionless systems like Bitcoin, it's particularly incentivized in global-consensus systems like L1 "blockchains" where every node has to download every other node's onchain transactions forever (but spam in Bitcoin, as clarified above, is not limited to this kind: there are many ephemeral examples). The way a Bitcoin node (including a Core V30 node) deals with the very real problem or spam is multifaceted: with blacklists on the p2p level, with mempool policies, with consensus rules, etc. The latter include a rate limit (pow retarget plus wright cap) coupled with an open auction system (blockspace fees) that greatly mitigates the issue, otherwise pretty serious due to global consensus.
> There are only bits and bytes. Bitcoin doesn't care about content. [...] It does not matter whether those ~4 MB contain a payment, a poem, or something I personally disagree with.
Blatantly false. A Bitcoin node clearly and unequivocally does care for the content of said bits and bytes. It does so, just to name two trivial examples, when rejecting from blocks invalid transactions which create money out of thin air, or when rejecting from menpool valid but nonstandard transactions under the dust limit. In both cases, to node will semantically interpret bytes and bites, not just in format terms but also in content terms (economic). There are many not less trivial examples, also in upper layers like Lightning and in tools like JoinMarket, everywhere in the Bitcoin tech stack.
> Bitcoin does not allow me to selectively approve transactions, and that is a feature.
Blatantly false. Not only your node's defaults will selectively approve transactions in blocks, based on validity rules, and in mempool, based on standardness rule. But it also allows you to change such selective approval rules. The standardness rules are easy to change (just open the conf file and your node will follow them and you'll be fine). The validity rules are harder to change (you have to touch the code and if you're not careful you will not be able to correctly send and receive money).
> Anyone can use blockspace if they are willing to pay for it.
False. If Roger Ver wants to use 4 mb of contiguous blockspace for something different than a valid witness program (including the non-witness part of a valid transaction), all other nodes will selectively reject that use, *regardless* of how much he's willing to pay.
Time to put up or shut up.
We challenge @greenpeaceusa to a debate at @TheBitcoinConf.
You pick your best champion, we pick ours… winner keeps the skull.
1/18
Domani va in scena $ARB.
Vediamo insieme come agire per massimizzare le probabilità di non avere alcun problema in fase di claim e trasferimento!
(like e retweet per l'algoritmo e si vola. Inoltre ci impiegate un nano_secondo grazie)👇