03:02:31 <m-relay> <n​obfg9000:matrix.org> hey i have a question about FCMPs. could it prevent users from storing arbitrary data in the transaction format? I remember that was an issue around the discussion of removing tx_extra in the whole mordinals situation, because the mordinals dev claimed they could just stuff their data in the outputs
03:06:18 <m-relay> <n​obfg9000:matrix.org> there was a big discussion on github around removing tx_extra last year and I think it ended talking about whether or not you could check to see if decoys were really decoys
03:07:01 <m-relay> <n​obfg9000:matrix.org> https://github.com/monero-project/monero/issues/6668
03:09:58 <m-relay> <n​obfg9000:matrix.org> This would be nice because it would allow controlling how much arbitrary data can be pushed on the chain (possibly allow some tradeoff wherein you can push arbitary non-transaction data, but it incurs extra fees)
10:47:04 <m-relay> <j​0j0xmr:monero.social> There seems to be political reasons to keep tx_extra, prioritizing projects that currently use it over the fungibility of the protocol.
17:42:29 <jeffro256> As has been discussed 100 times before, there are many other other ways to insert fingerprinting information besides tx_extra. Removing tx_extra by itself does not fix fingerprinting issues
17:43:16 <jeffro256> It's not an "either or" situation here, and not political
17:46:18 <jeffro256> We also use tx_extra for addressing information, so if we removed tx_extra, you wouldn't be able to use cryptonote addresses. We could try enforcing the contents of tx_extra to ONLY have addressing information, but now we're back at the same problem: how can an external observer prove that any stored crypto primitive anywhere in the tx isn't encoding additional information? Short answer: you can't