Statement on DAO V1.1 Platform Launch

[_magicsheep]

哈咯感谢参与测试！

1. 关于白名单设计思路的问题：目前的设计方案所采取的trade-off是开发团队经过讨论确定的，这当然不意味着它就是最好的，所以这次公开测试的主要目的就是希望社区了解这后面的trade-off，如果社区有人可以提出更好的设计方案（比如Phroi在另一个帖子里提到他准备提出一个新的方案）我们可以一起讨论。

2. 关于社区验证工具：此工具将由社区主导开发。

@_magicsheep

关于审计工具：技术团队会提供详细的技术解释（文档），但是工具需要由社区主导开发，不然依然无法解决conflict of interest的问题（提案团队自己开发工具验证自己的解决方案）。

3. 关于核心问题1: 社区独立验证工具存在的意义之一就是社区可以不依赖开发团队的任何承诺自行进行验证。

@woodbury.bit

如果投票资格边界仍然依赖一份预先生成的名单，那么团队除了说明这份名单“按什么规则生成”，还应该进一步说明并证明：当前实现是否真的已经排除了后台人工 override、数据库改表、临时替换 root、或者在 proof 准备阶段人为影响名单的可能。

4. 关于测试成本问题：为了尽可能逼真的模拟最终产品，目前的版本部署在CKB主网上，这样当公开测试结束后开发团队只需要切换域名即可，避免了进一步修改环境产生的社区不信任和其它问题。

---

Thank you for participating in the testing!

1. Regarding the whitelist design approach : The trade-off in the current design was determined by the development team after discussion. This doesn’t mean it’s the best possible solution, so a key goal of this public test is to help the community understand the trade-offs involved. If anyone in the community can propose a better design (for example, Phroi mentioned in another post that they are planning to suggest a new approach), we can discuss it together.

2. Regarding the community verification tool : This tool will be developed under the leadership of the community.

@_magicsheep

Regarding the auditing tools : The technical team will provide a detailed technical explanation (documentation), but the tools themselves need to be developed and led by the community. Otherwise, the conflict-of-interest issue cannot be resolved (i.e., the proposal team developing the tools to verify its own solutions).

3. Regarding Core Question 1 : One of the purposes of having an independent community verification tool is to allow the community to conduct verifications on their own without relying on any commitments from the development team.

@woodbury.bit

If voting eligibility still depends on a pre-generated list, then in addition to explaining how that list is “supposed” to be generated, the team should also explain and demonstrate whether the current implementation has truly eliminated manual override, database-level list modification, temporary root replacement, or human intervention during proof preparation.

4. Regarding testing costs : To simulate the final product as realistically as possible, the current version is deployed on the CKB mainnet. This way, once the public testing is complete, the development team only needs to switch the domain, avoiding further environmental changes that could lead to community distrust or other issues.