First, there are many reasons someone would want to store all blocks and not just run a pruned node - see @FractalEncrypt's post about it.
Second, plebs are not normies. They may not be protocol devs but they know how nodes work. It's a bit insulting to assume plebs don't know the problem with the UTXO set ballooning.
Node runners don't want junk in the UTXO set OR in OP_RETURN. If the proponents of removing the limit took even 1 minute to listen to users, they would understand this. Instead, it's all tirades of "we know better" and "you don't understand."
At best, removing the limit on OP_RETURN does nothing to fix the situation. All of the Core dev reasoning to remove the limit is full of words like it "might" and "could" fix the problem.
At worst, we've introduced a new attack vector to crowd out financial transactions, as identified by @LaurentMT.
"The UTXO set used to be around 4GB. Due to inscriptions and BRC-20, it has grown to about 12GB."
Plebs are fully aware.
The question is what do we do about it.
I think the big disconnect is that most normies don't know what the UTXO set size is, they only understand "block size."
To put it simply, the size of the blockchain (i.e., the total size of all blocks) only affects the initial sync time when setting up a node from scratch. This can grow by a maximum of 4MB per block (realistically around 2MB).
In theory, you need to sync a node from scratch only once in your lifetime... for new nodes, you can skip the sync by downloading a UTXO Set then verifying that your new node has the same UTXO Set hash as one of your older nodes.
You DO NOT NEED to store all the blocks, nor should you, unless you have a pretty good reason.
So, optimizing blockchain size does not significantly reduce the minimum resources required to run a node. At best, it slightly reduces bandwidth usage. If you do store all the blocks, due to current consensus rule, you should anyway plan for a 2MB per blocks increase for planning your hardware upgrade.
More important than the blockchain size, it is what everyone MUST store: The UTXO set size.
Developers care far more about the size of the UTXO set because it determines the minimum storage required to run a full node. (A "full node" means you verify all blocks, not necessarily store them all.)
The UTXO set used to be around 4GB. Due to inscriptions and BRC-20, it has grown to about 12GB.
The UTXO set does not store OP_RETURN data or signatures.
If you want your node to keep running smoothly on small devices, focus on minimizing the UTXO set size, not the blockchain size. And this is why, lot's of devs don't really care about OP_RETURN limits.
558
60.85K
The content on this page is provided by third parties. Unless otherwise stated, OKX is not the author of the cited article(s) and does not claim any copyright in the materials. The content is provided for informational purposes only and does not represent the views of OKX. It is not intended to be an endorsement of any kind and should not be considered investment advice or a solicitation to buy or sell digital assets. To the extent generative AI is utilized to provide summaries or other information, such AI generated content may be inaccurate or inconsistent. Please read the linked article for more details and information. OKX is not responsible for content hosted on third party sites. Digital asset holdings, including stablecoins and NFTs, involve a high degree of risk and can fluctuate greatly. You should carefully consider whether trading or holding digital assets is suitable for you in light of your financial condition.