Any good podcast discussing this?
nostr:note1z89lj4u3qdxga859ranzje5feupcv3kuk76ekq7eusa8av7j923svsaar3
Discussion
The first I heard of it was here https://youtu.be/zgsiDAhq4d4 π§‘β¨
No, and I discourage listening to podcast on this topic with someone who never worked on bitcoin core. Here's good summary:
https://x.com/stevenroose3/status/1917554986826846703
Everything else are emotionally fueled strawman
Canβt see comments
You and 521 other people ,,,,β¦.
This doesnβt make sense to me
In short: people will attach stuff to bitcoin and we there is NO WAY for us to stop it.
They can do it in many different ways, and some of them are more harmful.
Using OP_RETURN for this purpose is less harmful for the network and noderunners than other methods, because it does not bloat UTXO set and has no validation cost.
But OP_RETURN has a limit which is too low for some of those protocols, so they need to use less efficient methods that increase the cost for everyone and do more harm.
Hence the idea to relax or remove the limit, to incentivise them to use less harmful method
Seems like the number of times someone attached garbage would be smaller over all and removing the filter would just do the opposite. Why cater to those people because abuse is possibleβ¦
No, the amount of spam will be the same as they will still do it by using p2tr outouts.
This is a thing I've been trying to pay attention. If there is no limit, couldn't someone eat entire blocks with arbitrary data fairly easily and at a relatively low cost because they could include all data into one trnasactions rather than the amiplified expense of having to do it through multiple transactions?
They could, but after 144kb it's cheaper to use those UTXO polluting method. So effectively this would be the limit
π―π―
Node Runners should be asked if they agree with this change and that isn't being done. Good bye Bitcoin Core. Arrogance beyond belief.
You might like this too https://primal.net/e/nevent1qqszkj5964ay87cs66fpfnen80rs58gs4zmjw8ejqjxznlnyhr9wk4cewkh66 π§‘β¨