Nostr Web Client

This is not correct. All core developers are focused on payments. If there is a narrative out there that "Bitcoin Core supports inscriptions and Knots doesn't" that is wildly disingenuous.

The most important mistake specifically in your post is that looser op return limits mean there will be more inscriptions on chain. Inscriptions are very happy living in witness data already where they have been for years. It is much cheaper to store data there.

The goal of the v30 policy change is to match the behavior we *already observe* in miners, the consensus engine. This improves block propagation, fee estimation, and reduces the advantage larger miners have over smaller miners. In a word: decentralization.

Here's some more posts:

https://delvingbitcoin.org/t/addressing-community-concerns-and-objections-regarding-my-recent-proposal-to-relax-bitcoin-cores-standardness-limits-on-op-return-outputs/1697

https://delvingbitcoin.org/t/a-comprehensive-op-return-limits-q-a-resource-to-combat-misinformation/1689

Ronin 4mo ago

That alone is already stupid, miners can include/exclude whatever they want, on one side you have Mara doing out of band txs, on the other you have ocean not including data, did they follow what we were already seeing with ocean? no, they went with miners Out Of Band services, wich means they go around what the network wants. Core should be represented what we(nodes) as a network desire, not miners, i thought that lesson was already learned from the blocksize wars.

Reply to this note

Please Login to reply.

Discussion

CitizenPedro 4mo ago

Exactly. This is a fundamental point right here.

And this seems to be the biggest argument of the "other" side, in other words, "you can't do anything about it, etc".

Bitcoin is a monetary network and it should be kept that way.