Bitcoin Core v30 will for the first time allow transactions into the default mempool with more than one OP_RETURN output. The datacarriersize= setting is being repurposed so that numeric limits now allow more data than before, and the setting is being deprecated. Doesn’t this risk:
- Different node operators interpreting or configuring policies differently, leading to mempool fragmentation?
- Wallets / fee estimators breaking because they assume older standardness rules?
- Smaller node operators losing autonomy to enforce stricter standards,facing unexpected load?











