Zhouzhou

First of all, everyone, thanks for joining. Before we start, the translator is on, so feel free to use whichever language you are comfortable with. We have the recording and later we will share the video and transcript to our communities. Today's AMA agenda has been adjusted. As you know, today the community has published a review of the new platform, and the proposal and steward team has issued a statement in response. So today's AMA will focus on addressing these findings and the path forward. I will hand it over to Haoyang, who leads the daily operations for the steward team and represents the proposal team, to work us through the team's response. Haoyang, over to you.

首先感谢大家的参与。开始前提醒一下，翻译功能已经开启，请随意使用您觉得舒服的语言。我们正在录音，稍后会向社区分享视频和文字记录。今天的 AMA 议程有所调整。如您所知，今天社区发布了对新平台的审查，提案和物业团队也发布了回应声明。因此 今天的 AMA 将重点讨论这些发现以及未来的发展方向。我将把时间交给负责物业团队日常运营并代表提案团队的 Haoyang，由他为我们梳理团队的回应。Haoyang，交给你了。

Haoyang

Okay, thank you Zhouzhou. There are mainly 5 things I want to update on yesterday's events. First of all, about this DAO V1.1 launch. It's mainly supposed to be a delivery for milestone 2. But it turns out it's not meeting the quality for final submission. What we will do for this submission is that we are going to take the community's response into account. We are going to fix all the issues listed by Phroi and other community members, and we will also run another independent test again to make sure there is no residual testing code in the codebase.

好的，谢谢 Zhouzhou。关于昨天发生的事情，我主要有五点要更新。首先是关于 DAO V1.1 的发布。这本来应该是里程碑 2 的交付内容。但事实证明它没有达到最终提交的质量要求。对于这次提交，我们将充分采纳社区的反馈。我们将修复 Phroi 和其他社区成员列出的所有问题，并且会再次进行独立的测试，确保代码库中没有残留的测试代码。

Also about Phroi's concern regarding the whitelist and the bugs. I don't think I'm the qualified person to answer the whitelist mechanism, but David already responded to that on Nervos Talk. I will just try to summarize the mechanism. There are two whitelists. The first one is an inherent mechanism. The reason we have that whitelist is because this is the most suitable implementation strategy right now for the Nervos network. That part we cannot easily change, which will also introduce some sort of centralization.

另外关于 Phroi 对白名单和漏洞的担忧。我认为我不是回答白名单机制的合适人选，但 David 已经在 Nervos Talk 上做出了回应。我简单总结一下这个机制。这里有两个白名单。第一个是固有机制。我们之所以有那个白名单，是因为 这是目前 Nervos 网络最合适的实施策略。那部分我们无法轻易改变，这也会引入某种程度的中心化。

Matt

I think that would have benefited from having discussion around it. I am not a CKB developer, but I could see what I believe is a way to do it without introducing centralization. I don't want to say I have the solution and present it now as correct, but even within my opinion, I could share an idea for something else to explore. I feel like it would have really benefited to discuss the mechanism, especially since it introduces centralization with the community.

我认为围绕这一点进行讨论会很有帮助。我不是 CKB 开发者，但我认为有一种方法可以在不引入中心化的情况下实现它。我不想说我已经有了解决方案并把它当作正确答案提出来，但就我个人的观点而言，我可以分享一个探索其他方向的想法。我觉得讨论这个机制会非常有益，特别是因为它给社区引入了中心化。

David

But I think it's difficult to explain it very clearly here, because there are many tech details. It's there on Talk, and I think we can have the discussion there.

但是我觉得很难在这里解释得非常清楚，因为里面有太多技术细节。内容已经在 Talk 上了，我认为我们可以在那里讨论。

Matt

I was talking to Phroi a little bit earlier today to get an idea of exactly how the implementation operates. I understand the position that David is asserting about the way it's designed. My statement is really that it would have benefited from some review and discussion about how the mechanism operates. Then we could identify all the possible options and the tradeoffs with a number of different people looking at it. Because these things are community-driven, I think that's what we have to go through now. I think one outcome of this conversation may be that I agree with you that this is the best way. But for where things are, it's hard to say that today.

我今天早些时候和 Phroi 聊了一会儿，想确切了解该实现是如何运作的。我理解 David 对设计方式的主张。我的观点是，对该机制的运作方式进行审查和讨论会很有帮助。这样我们就能在多人的共同审视下找出所有可能的选项和权衡。既然这些都是社区驱动的项目，我认为这是我们现在必须要经历的过程。我认为这次对话的一个结果可能是，我同意你的看法，即这是最好的方法。但就目前的情况来看，今天还很难下定论。

Baiyu

Sorry to interrupt. I think what Matt said is very clear. Even though David thinks the design is the best way on CKB, we need to consider the community's response and communicate with the community. After that, we can decide which tradeoff is the best. David, I think the communication gap is caused by the language gap maybe. So you can write your design ideas on Nervos Talk, and then maybe we can have a communication with Phroi and other developers in the CKB community.

抱歉打断一下。我认为 Matt 说的非常清楚。尽管 David 认为这是 CKB 上的最佳设计方案，我们仍然需要考虑社区的反馈并与社区沟通。之后，我们才能决定哪种权衡是最好的。David，我认为沟通上的鸿沟可能是语言障碍造成的。你可以把你的设计思路写在 Nervos Talk 上，然后或许我们可以与 Phroi 以及 CKB 社区的其他开发者进行交流。