Questions: With his understanding.... "Bitcoin's blockchain (often referred to as the "timechain" due to its timestamping function) is fundamentally agnostic to the content of the data embedded in transactions, provided they adhere to the protocol's structural rulesβ€”like valid UTXO (Unspent Transaction Output) consumption and creation, proper cryptographic signatures, and fitting within the block weight limit (currently around 4 million weight units post-SegWit, equivalent to roughly 1-4 MB depending on transaction types). The network doesn't interpret or restrict the semantic meaning of the data; it simply validates the transaction's format and ensures no double-spends or invalid spends occur. This agnosticism enables various use cases for embedding arbitrary data, such as: OP_RETURN outputs: These allow up to 80 bytes of non-spendable data (e.g., text, hashes, or metadata) attached to a valid transaction, explicitly designed for this purpose without affecting UTXO set bloat. Script-based embedding: Data can be hidden in locking/unlocking scripts, multisig dummy outputs, or even the coinbase transaction (miners' reward input). SegWit witness data: Post-2017 upgrade, extra data can be stored in the witness field, which doesn't count toward the base block size limit. While this flexibility has sparked debates about chain bloat (e.g., from NFTs via Ordinals or large inscriptions), the protocol itself imposes no content-based filters beyond the mentioned caveatsβ€”miners choose what to include based on fees, and full nodes enforce only consensus rules. If data violates size limits or transaction validity, it's rejected, but otherwise, the blockchain treats it as neutral payload." It is imperative that the mempool policies enforce the culture of the Bitcoin ethos. Therefore, the node runners play a very important part in keeping spam off the timechian as they are one of only a few regulators keeping content that is out side the scope of monetary transactions from being cemented for a thousand years.
Agreed... image
After reading through the corev30 technical arguments.... I still land on NOT updating to v30 and using Knots. I do agree with this... image
This is very cool! https://xcancel.com/josebitcoiner/status/1976004041655320901
I am now reading this comprehensive list of the OP_RETURN issue.
Please create a github account and comment on this stating to not release this PR. Down vote it. Every comment and down vote helps. Also, it will show publicly you do not support it which will help legally if you would run your own node in the future.
We stack the sats, we run the knots!
A .iso is coming... image