Relax OP_RETURN standardness restrictions

The discussion revolves around the evolution and adjustments made to Bitcoin's software, highlighting the importance of policy decisions that distinguish between what is beneficial for software maintainers versus the users. A particular focus is placed on the configuration option mempoolfullrbf, which was introduced in July 2022, as documented in a GitHub pull request. This feature became the default setting by August 2024, showcasing a decision aimed at refining the user experience or operational efficiency of Bitcoin transactions. However, it was noted that this option was subsequently removed in November 2024 through another pull request, suggesting a reevaluation of its utility or impact.

The conversation touches upon the design philosophy behind Bitcoin's development, particularly emphasizing the distinction between mining and relay policies. This differentiation is crucial because it underlines the software's architectural choices, hinting at an ongoing debate over the most effective way to govern such policies. The introduction and eventual removal of mempoolfullrbf serve as a case study in how certain features, after being monitored and assessed, may be deemed unnecessary or counterproductive, leading to their discontinuation.

Moreover, the mention of existing configurations such as datacarrier and datacarriersize raises questions about the significance of removing options after a period of observation. This indicates a broader dialogue within the Bitcoin development community about how to best adapt and refine the software's functionality in response to real-world usage and statistical analysis. Such decisions reflect a careful balance between innovating on one hand and maintaining stability and reliability on the other, underscoring the complexity of cryptocurrency software management.