DAO v1.1 提案通过：感谢社区的质疑与信任
为期7天的 DAO v1.1 提案投票结果公布后，社区提出了关于投票公正性的质疑。DAO 多签委员会随即启动调查，并于今日发布了完整的调查报告：
调查确认：Metaforo 平台存在技术漏洞，允许用户通过解绑和重新绑定地址进行重复投票。这个漏洞在本次投票中被实际利用，涉及权重超过7100万 CKB。在剔除重复投票后，提案以 75.2% 的赞成票通过，实际参投量超过456M CKB，峰值一度达到6.03亿 CKB。
感谢所有参与者
作为DAO v1.1提案团队，我们想说的第一句话是：感谢。
感谢提出质疑的社区成员。你们的警觉启动了这次调查，你们的勇气让问题得以暴露。在很多组织里，质疑会被视为麻烦或不信任，但在一个健康的 DAO 里，质疑是最宝贵的贡献之一。
**感谢 DAO 多签委员会、App5 团队、Metaforo 团队。**你们用一周时间完成了一次严谨的技术调查。在没有完整日志、没有数据库记录的情况下，通过前端实现细节和浏览器后端日志锁定证据，这本身就是专业能力的体现。更重要的是，你们建立了一个可信的争议解决机制的先例。
感谢所有投票者，无论赞成还是反对。这次投票的参与度创造了 CKB Community Fund DAO 的历史记录。我们同样感谢那些在审议期间提出尖锐批评的成员，关于预算、流程、团队独立性的质疑迫使我们不断完善方案。现在我们还要感谢你们对结果修正的接受，这种接受本身就是对治理机制的信任。
这次波折让我们更加确信：社区需要自己控制的治理基础设施。我们的提案从一开始就主张建立社区拥有的平台，而不是依赖第三方工具。这次 Metaforo 漏洞的暴露和利用，以痛苦但清晰的方式验证了这个论点。
重申我们的承诺
在接下来的执行阶段，我们将严格遵守在审议期间所作出的公开承诺，包括：
- 完全透明承诺： 每个里程碑都将发布详细的、逐项的资金使用明细。
- 成本控制承诺： 所有非人力成本的基础设施预算（域名、服务器等），将按“实报实销”处理，所有节余 100% 退还 DAO 金库，并保留票据供社区审计。
- 开源承诺： 平台所有核心组件（如投票合约、Web5相关通用组件）将完全开源，供未来社区项目复用。
接下来的工作
在社区审议和投票期间，为了增强社区对提案的信心，我们团队已经开启了部分工作。投票的结束，是全面推进工作的开始。我们将立即启动以下工作：
- MVP 开发与测试网上线 (即日 - 2025年11月底):
我们将确保在11月底完成包含核心功能的 MVP 版本，并在 CKCon 2025 前上线测试网，供社区进行第一轮的体验与测试。 - 主网上线与试运行 (2025年12月 - 2026年2月中旬):
完成所有规划功能的开发，将平台正式部署至主网，并开启社区试运行。 - DAO 物业团队招募 (近期启动):
我们将于近期正式面向全社区，公开邀请、招募第一届 DAO 物业团队的成员。物业团队将负责未来 DAO 的日常运营。这是一个服务社区的职位，我们真诚地欢迎所有有热情、有能力的朋友自荐或推荐。第一届DAO物业团队成员的遴选工作将由提案团队主持，本着公平和择优选择的原则，综合考虑物业团队成员组成。 - 起草《运营手册》 (即日 - 2026年2月中旬):
新组建的物业团队将与提案团队紧密合作，共同起草《DAO 物业运营手册》，以确保所有流程在主网上线前都清晰、透明。
这次投票的意义，不只是一个提案获得通过。它展示了当治理机制遭遇压力测试时，这个社区选择了调查真相而不是掩盖问题，选择了修正结果而不是维持表面共识，选择了从危机中学习而不是快速翻篇。这些选择定义了 CKB 社区的治理文化。
我们期待与整个社区一起，建设一个更高效、更透明、更具韧性的 DAO。
DAO v1.1 Proposal Passed: Gratitude for Community Scrutiny and Trust
Following the conclusion of the 7-day voting period for the DAO v1.1 proposal, community members raised concerns about voting integrity. The DAO Multisig Committee immediately launched an investigation and released a comprehensive report today:
The investigation confirmed that Metaforo platform contained a technical vulnerability allowing users to vote repeatedly by unbinding and rebinding addresses. This vulnerability was exploited during the voting process, involving over 71 million CKB in voting weight. After removing duplicate votes, the proposal passed with 75.2% approval, with actual participation exceeding 456M CKB and peak voting reaching 603 million CKB.
Thank You to All Participants
As the DAO v1.1 proposal team, the first thing we want to say is: thank you.
Thank you to the community members who raised concerns. Your vigilance initiated this investigation, and your courage brought the issue to light. In many organizations, questioning would be seen as trouble or distrust, but in a healthy DAO, scrutiny is one of the most valuable contributions possible.
Thank you to the DAO Multisig Committee, App5 team, and Metaforo team. You completed a rigorous technical investigation in one week. Without complete logs or database records, you pinpointed evidence through frontend implementation details and blockchain explorer backend logs. This demonstrates professional capability. More importantly, you established a precedent for credible dispute resolution mechanisms.
Thank you to all voters, whether for or against. This vote set a participation record in CKB Community Fund DAO history. We also thank those who raised sharp criticisms during the deliberation period. Questions about budget, process, and team independence pushed us to continuously refine our proposal. Now we also thank you for accepting the corrected results. This acceptance itself represents trust in governance mechanisms.
This experience reinforces our conviction: the community needs governance infrastructure it controls. Our proposal advocated from the beginning for building community-owned platforms rather than relying on third-party tools. The exposure and exploitation of the Metaforo vulnerability validated this argument in a painful but clear way.
Reaffirming Our Commitments
During the execution phase, we will strictly honor all public commitments made during the deliberation period, including:
- Full Transparency Commitment: After each milestone is completed, we will publish a detailed, itemized report of all fund usage alongside our delivery report.
- Cost Control Commitment: All non-labor infrastructure budgets (including domains, and others such as servers, etc.) will be handled on an “at-cost reimbursement” basis. All receipts will be kept for community audit at any time. Any and all surplus funds will be 100% returned to the DAO treasury.
- Open Source Commitment: All core platform components (such as voting contracts and Web5-related general components) will be fully open-sourced for future community project reuse.
Next Steps
During the community deliberation and voting period, our team began preliminary work to strengthen community confidence in the proposal. The voting conclusion marks the beginning of full-scale advancement. We will immediately initiate the following work:
- MVP Development and Testnet Launch (Now - End of November 2025):
We will ensure completion of an MVP version with core functionality by the end of November, launching the testnet before CKCon 2025 for the community’s first round of testing and feedback. - Mainnet Launch and Trial Operation (December 2025 - Mid-February 2026):
Complete development of all planned features, officially deploy the platform to mainnet, and begin community trial operations. - DAO Steward Team Recruitment (Starting Soon):
We will soon formally invite and recruit members for the first DAO steward team from across the community. The team will handle future DAO daily operations. This is a community service role, and we sincerely welcome all passionate and capable individuals to self-nominate or recommend others. The selection of the first DAO steward team members will be conducted by the proposal team based on principles of fairness and merit, with comprehensive consideration of team composition. - Drafting the Operations Handbook (Now - Mid-February 2026):
The newly formed property team will work closely with the proposal team to draft the DAO Property Operations handbook, ensuring all processes are clear and transparent before mainnet launch.
The significance of this vote extends beyond a proposal passing. It demonstrates that when governance mechanisms face stress tests, this community chose to investigate truth rather than cover up problems, to correct results rather than maintain surface consensus, to learn from crisis rather than quickly move on. These choices define CKB community governance culture.
We look forward to working with the entire community to build a more efficient, transparent, and resilient DAO.
v1.1 提案团队
The v1.1 Proposal Team