Relax OP_RETURN standardness restrictions

The discussion centers around the policy regarding the size limit of transactions in the Bitcoin network, specifically addressing the rationale behind proposing an increase from 1KB to 99KB for transaction outputs. The argument put forth suggests that major miners already accept transaction sizes within this range, implying that the existing restrictions on relay by nodes (which do not directly mine transactions) serve little purpose other than to inconvenience users who prefer utilizing APIs over direct peer-to-peer network interactions. This scenario inadvertently supports a practice where miners must modify their software to accommodate these limits, fostering an environment conducive to private submissions.

Further examination of the issue reveals that the current policy limitations are seen as somewhat performative, considering miners can and do bypass them. This leads to situations where individuals determined to embed data within outputs between 1KB and 99KB might resort to creating fake outputs, ultimately harming the system's integrity. The critique extends to question the necessity of a marginal increase in the allowable size if it does not align with mining practices or significantly benefit the user base. The stance taken suggests skepticism towards adjusting the limit for what is perceived as minor conveniences that fail to address broader or more significant concerns within the network’s operational framework. This perspective highlights an ongoing debate within the development community about balancing technical constraints with user needs and the practical aspects of network operation, as illustrated in discussions among participants of the Bitcoin Development Mailing List.