Are you going to run Core 30?

[MakerAZ]

Are you going to run Core 30?

[BitMaxz]

Depending on what you mean by Core 30?
If it's Bitcoin Core, the most recent release is version 29.1 directly from GitHub. This version is not added yet on bitcoincore.org, and there is no version 30 yet; maybe in a few months.

[MakerAZ]

I mean the Core version 30, that is going to remove OP_Return filter and allow 100KB non-monetary data.

[BitMaxz]

I mean the Core version 30, that is going to remove OP_Return filter and allow 100KB non-monetary data.

Well, there were people debating about the OP_Return limit a few months ago; this is due to other assets like ordinals. But I don't think it can harm the blockchain; it can be beneficial.
We already have a discussion about this here: https://bitcointalk.org/index.php?topic=5539943.0

But if you are planning not to use this version on the next major release, you can go switch to Bitcoin Knots to overwrite them. Honestly, it shouldn't be harmful since it's not a consensus rule.

[achow101]

is going to remove OP_Return filter and allow 100KB non-monetary data.

The option is still there in v30 (and probably a while afterwards too) so you can disable that if you want. The change is that the limit is increased by default, and it applies over multiple outputs rather than restricted to a single output. But you can still lower the limit and disable relay of those transactions if you really want to.

[d5000]

allow 100KB non-monetary data.

Obligatory remark here: You can already include around 100 kB non-monetary data with other mechanisms, for example using fake public keys.

Here's a still relatively small example with 1,4 kB (way more than the current -- 0.29 -- OP_RETURN standardness limit): https://www.blockexplorer.com/bitcoin/tx/7774b4d7717e46160a2e37816c50384b29133b6aa842035e140b68338df1fbbf#overview - its "payload" is a Pepe image

But you can add thousands of outputs to your transaction (there are known transactions with 3000+ outputs, and in each fake pubkey you can stuff 33 bytes, so yes 90 kB should be possible).

Or just use the Taproot "exploit" permitting up to 400 kB. Yeah, Knots "protects" a bit from relaying these if you use their defaults, but once they're in the blockchain they're there forever.

Only adding this because there seem to be some who really believe that "only with 0.30 it becomes possible to put such big data blobs in the blockchain" .... which is completely false.

PS: If I run Core (currently I don't but don't rule it out for the near future), I'd upgrade to 0.30 but run it with a datacarriersize of 512 B or 1 kB.

[BitGoba]

Are you going to run Core 30?

No, I’m not going to run Bitcoin Core 30. I’ve switched to Bitcoin Knots. Bitcoin is money and a monetary protocol  not a crypto blockchain for data storage.In my opinion, Bitcoin Core 30 could very easily destroy Bitcoin. If Bitcoin turns into a crypto blockchain like Ethereum, where it becomes centralized and only large companies can run full nodes, that would be the end of decentralization.And if that happens, Bitcoin can no longer be good money. If only a small group of people  like in Ethereum  get to make decisions, then we’re just recreating a central committee, like a central bank in the fiat system.

I hope that what's happening now will ultimately strengthen Bitcoin, and that we’ll see more strong implementations of Bitcoin software emerge.Bitcoin Core is compromised but what if Knots also gets compromised one day? That’s why it would be good to have dozens of independent implementations and developers maintaining them.

[Cookdata]

In my opinion, Bitcoin Core 30 could very easily destroy Bitcoin. If Bitcoin turns into a crypto blockchain like Ethereum, where it becomes centralized and only large companies can run full nodes, that would be the end of decentralization.And if that happens, Bitcoin can no longer be good money. If only a small group of people  like in Ethereum  get to make decisions, then we’re just recreating a central committee, like a central bank in the fiat system.

Core 30 is simply increasing size limit of OP_RETURN, it's not about centralization, rather it's still about doing decentralization without censorship of any transactions kind.

You can run Bitcoin core 30 and choose not to relay transactions with OP_RETURN, you will still be fine instead of running to knots but it's still not bad.

The concern here is, the developers are trying to make alternatives for people that want to send and store an arbitrary data into Bitcoin blockchain, there are so many people spamming different data on Bitcoin UTXOs, they are expected to be spent but the trick is, the UTXO are fake pubkey without private keys. So they remain there forever and if this continues, the UTXOs will keep growing with spam of fake pubkeys.

We can only hope this upcoming upgrade makes people to use OP_RETURN instead of this continues spam but my opinion, this upgrade doesn't change anything.

[henry_of_skalitz]

You can still configure the limits manually, so, everything should be good even sitting on Core 30.