Request for Direct Team Communication, Disclosure of Project Authority, Operational Support, and Regular Progress Reporting

Original Proposal Text

Summary: This is a non-binding signaling proposal. It does not change any on-chain parameter, move any funds, or execute any code. Its purpose is to formally record, on-chain, the Qubetics community collective request to project leadership regarding communication, transparency, operational support, and progress reporting. Context: A recent community poll asked what would most restore confidence in Qubetics. Only 10 percent of respondents considered nothing to be outstanding, meaning roughly 90 percent of engaged voters want something addressed. The most requested items were a realistic, dated roadmap (50 percent), direct communication from the team rather than through third parties (48 percent), correct circulating supply and market cap data on major aggregators (44 percent), direct answers to questions outstanding since June 5 (40 percent), and a public statement naming who holds ultimate authority over the project and treasury (39 percent). This proposal turns that sentiment into a formal, on-chain request. The community requests that project leadership: (1) Communicate directly and regularly with the community, rather than solely through third parties or intermediaries. (2) Provide direct, written answers to the substantive questions that have remained outstanding since June 5, and continue to do this moving forward. (3) Issue a public statement identifying who holds ultimate ownership and authority over the Qubetics project and its treasury. (4) Publish a realistic, dated development roadmap, and provide a written progress update no less than once every 30 days, including honest disclosure of blockers or delays where they occur. (5) Establish a defined support process for validators, solver node operators, and builders, with a target response time of no more than one week for technical support requests, and no more than one day for urgent operational support requests. New features introduced to the network should be accompanied by the documentation needed to operate or build on them, including relevant ABIs, transaction formatting, and integration guidance. (6) Provide timely incident communication: when a network issue occurs (such as a chain halt, critical bug, or major delay), publish a written acknowledgement and explanation within 48 hours, rather than remaining silent until the issue is resolved. (7) Hold at least one live AMA session with the community within a reasonable timeframe following the passage of this proposal, to cover all the subject matter of the proposal with appropriate responses. What this proposal is not: This proposal makes no accusation and demands no action beyond communication, disclosure, support, and reporting. It does not seek to remove, penalise, or bind any party. It is a good-faith request from token holders, validators, and builders who have committed capital, infrastructure, and belief to this network, and who are asking to be communicated with and supported directly and honestly. Voting: YES - You support the community request for direct communication, disclosure of project authority, operational support, and regular progress reporting. NO - You do not support this request. ABSTAIN - You wish to contribute to quorum without taking a position. NO WITH VETO - You believe this proposal is spam or made in bad faith.