BTCtoOblivion on Nostr: https://m.primal.net/IIEN.jpg Let's deep dive into one more method of spamming the ...

Let's deep dive into one more method of spamming the #bitcoin network.

IT'S CALLED OP_RETURN METHOD.



OP_RETURN is a special transaction output type that allows embedding a small amount of data (up to 83 bytes) directly into a transaction.

This data is not part of the transaction's inputs or outputs, but is included as a separate, provably unspendable output hence it does not bloat UTXO set but hold on, I will explain you later in this thread how it's still bad for #bitcoin network.

OP_RETURN is like attaching a sticky note to a bank-cheque.

For example, Carol wants to post a short message on the #bitcoin blockchain for all to see. She creates a transaction with an OP_RETURN output containing her message: "I love Bitcoin" This message is now part of the blockchain record, visible to anyone who examines the transaction.




While OP_RETURN is less harmful than other methods since it doesn't create unspendable UTXOs, it still contributes to #bitcoin blockchain bloat. OP_RETURN abuse is already make running a full node more expensive.

As you can see a majority or at least half of blockspace has been filled with OP_RETURN transactions which add almost no value to anyone other than some high time preference mining pools (& miners)



https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.9.0.md#op_return-and-data-in-the-block-chain

Prior to version 0.9 of #bitcoin core, people had started to use ridiculously inefficient methods to embed small amounts of arbitrary data in transactions, so a consensus emerged to create a strictly limited, but TOLERATED way to add arbitrary data to transactions - that's how op_return was implemented into #bitcoin blockchain.

Some of the pro-spammers or whoever is neutral is on this subject might make an argument that "why don't you prune these OP_RETURN transactions since they are provably unspendable UTXO".

Well pruning just adds to the work of a full node, IT DOES NOT ELIMINATE IT so, you can't basically use this argument against spam.

cc Luke Dashjr (npub1lh2…a9nk) giacomozucco (npub1au2…t53j)

Same applies for inscriptions (another type of spamming the #bitcoin network). If you want to read more about this spam, then read below thread I made on inscriptions.

https://primal.net/e/note1jk4h07an7rq2wt6dtnst6wjzzfcwmd9978ld7hv4e9v9ellt5v9qznrqyk



If you are really concerned about this issue on #bitcoin blockchain then I would strongly recommend running Knots instead of #bitcoin core with disabled Datacarrier size option in your configuration. It will stop relaying runes through your node once you disable this option.

Newer version of Knots might already have this option already disabled.

If you are miner then point your has to OCEAN (npub1qtv…7dze) since they always mine almost spam free block and they are the only mining pool who cares about health of the #bitcoin network.

cc GrassFedBitcoin (npub1wnl…n3wr)

I will cover one more type of spamming the #bitcoin network in my next nostr post which is called "Stamps". One of the worst ways to spam the #bitcoin network.

Stay Tuned...!!!