It doesn’t require trust if you are using joinmarket or joinstr. The coordination will be reduced further with covenants. I don’t know how AI or KYC is related to coinjoin.
The debate isn’t about censorship.
This has been observed on other chains as well.
Privacy is unrelated to OP_RETURN.
master ← tevador:tx_extra_limit
opened 10:03PM - 05 Feb 23 UTC
Related to #6668
This patch limits the maximum size of tx_extra that's allowe… d in the transaction pool. Mined transactions bypass this check, which means this is a non-consensus change.
I set the limit to 1060 bytes. A typical transaction with 16 outputs needs up to 547 bytes for the transaction public keys, which still leaves 32 bytes of space for some custom data to send to each recipient.
Note that Bitcoin also has a [limit](https://github.com/bitcoin/bitcoin/blob/e325e0fccba4981d28053b79473ddaa44355e6e8/src/kernel/mempool_options.h#L47-L54) for arbitrary data payloads that defaults to a much lower value of just 83 bytes per transaction.
The purpose of this change is to make it harder to "upload" large amounts of unprunable data onto the blockchain. [Here](https://xmrchain.net/tx/21d0218ba8141a07048986d9e74ce8a011d9d5fddc3283dce58339da74c4bacd) is an example of a transaction with a tx_extra size of 126 KB containing a PDF file. The limit of ~1 KB should be sufficient for useful content such as the metadata of decentralized exchanges.
Ping @kayabaNerve
opened 09:37AM - 20 Jun 20 UTC
First discussed here: https://github.com/monero-project/meta/issues/356
We sh… ould consider removing the tx_extra field from all non-coinbase transactions.
Main reasons:
1. Enhanced fungibility due to a more uniform transaction format.
2. Protection from the risks of arbitrary data on the blockchain, e.g. copyrighted material, privacy violations, politically sensitive or illegal content etc.
Required data that is currently stored in tx_extra (e.g. transaction public key) could be moved to a dedicated field.
Miner (coinbase) transactions could still allow the tx_extra field for the following reasons:
* coinbase transactions are already distinguishable
* the risk of harmful content is lower because it would require mining a block
* tx_extra is needed for merged mining
Disadvantages of removing the tx_extra field:
* losing the ability to soft-fork the transaction format