Well.... Welcome to the technical (and legal, and moral, and ??) side of Bitcoin.

Just what I know (rather limited):

You probably picked up the Op_Return discussion.

The Op_Return is an existing feature that used to be limited to 80 bytes to include a short message (80 bytes of data) to a transaction.

With the v30 release that limit is scaled to 4 Mb.

One of the things that make the discussion more complex is that there are other ways to add data.

Those other ways have plusses and minuses.

One of the arguments is that if the new 4Mb is used, the way data is include is more straight foreward (I think this is not guaranteed btw).

Another thing is what will be allowed to put in that data.

Plain text or pictures etc (and that could be porn etc)

This could have legal implications (if you run a node you store data on your node and thus possible illegal stuf).

If a picture is split in sets of 80 bytes and submitted via multiple transactions any picture (extrapolation is allowed 😇) can be stored on chain.

What is the difference between a program showing you a picture stored in one .jpg file or a program showing you a picture (or whatever) by combining many 80 bytes Op_Return data.

So if we filter we have the what should we filter discussion.

What we think or believe does not mean a judge or legislation will agree....

We should asume this kind of data is already onchain making things even more complicated.

So we have voices that say nodes should be able to select what they store (and if so we can ask: what should that be)..

It becomes a complex system if different nodes run different versions so what is stored or not could become unclear.

My estimate would be that above is less than 5% of what needs to be discussed related to the Op_Return aspects.

And that is just one change...