Governance participation collides with demands for accountable communication

Administrator Diablo directed contributors toward proposals and warned that passive fear-spreading could lead to bans. Tommo objected to the moderation approach and asked what concrete information or guidance holders had received over the preceding 3-6 months. He described owning thousands of keys and criticized the delivery of partner rewards. Those holdings and project-failure claims were his account, not a verified portfolio or an audited count of failed partners.

Diablo later said he was reminding participants of the rules rather than threatening them. Tommo maintained that the comments had broken no rule. The message that prompted the initial warning had been deleted, leaving the disagreement's full opening context unavailable. What remains clear is the distinction between conduct enforcement and answering substantive holder questions: directing someone to governance does not itself resolve a request for delivery milestones or explain missed follow-up.

The discussion also pointed to Keith's developing esXAI proposal. A follow-up praised the proposal while questioning how it could advance without dependable feedback from the team. The governance issue was therefore broader than whether an idea existed. A credible process needs a way to evaluate that idea, communicate a decision and report implementation. None of these messages supplied an adoption vote or evidence that the proposed participation mechanism was operating.