Open letter to core devs (reflections/questions from the op_return saga and proposal to establish a well-organized channel/link between devs and users)

These modifications address the inefficacies of previous limitations that not only failed to prevent certain actions but also led to more problematic methods that could degrade network performance. For example, retaining the OP_RETURN limit did not stop users from embedding data into the blockchain; instead, they found alternative, less efficient ways to do so. By allowing data storage within OP_RETURN, it benefits both the user and the network by avoiding the need for additional transactions to reveal this data. The email argues against arbitrary limits on data size, suggesting that the maximum transaction size should be the only limit. It further discusses the discrepancies between node and miner policies, particularly how nodes' enforcement of certain rules does not prevent miners from adopting different practices, leading to potential issues with block propagation and compact blocks.

Moreover, the email addresses the challenges in communication and organization among volunteer developers within open-source projects like Bitcoin. It mentions avenues such as mailing lists, forums, and GitHub where interested parties can learn about the technical rationales for these changes. However, it critiques the engagement level of developers with the broader community, especially on social media platforms, suggesting that developers often prioritize technical work over debating skeptics who are unlikely to be persuaded.

In addition to technical explanations, the email broaches concerns about the perceived attitudes and behaviors of core developers towards non-technical users and configurability issues. It critically examines incidents where core developers have been accused of forcing changes without considering community input, dismissing non-technical criticisms, and engaging poorly with the public. These actions, according to some community members, contravene the foundational ethos of Bitcoin, which emphasizes verification over trust and authority. The sender invites core developers to reflect on these perceptions and suggests better organization for public engagement to clarify the team's unified stance on various issues.

The necessity for a spokesperson or a dedicated forum to articulate the majority views of the core development team is proposed as a solution to improve dialogue between developers and users. This approach aims to prevent the dispersion of conversations across multiple platforms, which can lead to confusion and inefficiency. Additionally, the email touches on concerns regarding conflicts of interest within the development team and private communications between core developers and businesses, raising questions about transparency and integrity within the ecosystem.

Overall, the email seeks to foster a more inclusive and structured dialogue between Bitcoin core developers and the wider community, emphasizing the importance of addressing both technical and non-technical concerns to bridge the growing divide.