[DIS] Community Fund DAO v1.1 Web5 优化提案/ Community Fund DAO v1.1 Web5 Optimization Proposal

matt_ckb · November 16, 2025, 12:14am

no legitimate votes were removed. Let’s talk about the future

matt_ckb · November 19, 2025, 6:10am

Can someone provide an update on the tool development? It has been under development for a few months now?

zz_tovarishch · December 1, 2025, 5:07am

DAO v1.1 更新：Milestone 1 (Testnet MVP) 交付

按照提案承诺，DAO v1.1 提案团队在CKCON 25期间交付Milestone 1 (Testnet MVP) 。
同时，团队在部分方面超出了原计划，比如为了让社区成员有更好的体验，我们已完成移动端大部分页面的响应式适配。

具体交付物：
测试环境 https://ccfdao.dev
代码仓库 (GitHub Workspace: CKB Community Fund DAO 1.1 · GitHub)

ckb-dao-vote：投票合约
web5-components：投票系统、Nervos DAO地址绑定系统
ckb-fund-dao-ui：前端代码（持续开发中）
app_view：后端代码（持续开发中）
ccfdao-v1.1-docs：文档（持续建设中）

核心功能：

支持Web5 did:ckb 注册、扫码及导入登录
提案发起、详情浏览、社区讨论（评论）及投票
用户个人中心，支持绑定Nervos DAO地址
首页提案列表、金库信息展示
中英文双语支持

经费使用透明度： Milestone 1阶段的详细经费使用明细将在近日单独发布，将包含服务器、域名等基础设施支出的完整披露。

欢迎访问测试环境体验，并反馈问题和建议。感谢社区的支持与信任。

DAO v1.1 Update: Milestone 1 (Testnet MVP) Delivered

As committed in the proposal, the v1.1 proposal team deliveres the Milestone 1 (Testnet MVP) during CKCon 25.

The team also exceeded the original scope in some areas. For example, to provide a better experience for community members, we have completed responsive adaptation for most mobile pages.

Deliverables:

Test Environment https://ccfdao.dev
Code Repositories (GitHub Workspace: CKB Community Fund DAO 1.1 · GitHub)

ckb-dao-vote: Voting contract
web5-components: Voting system, Nervos DAO address binding system
ckb-fund-dao-ui: Frontend code (ongoing development)
app_view: Backend code (ongoing development)
ccfdao-v1.1-docs: Documentation (ongoing)

Core Features:

Web5 did:ckb registration, QR code scanning, and import login
Proposal creation, detail browsing, community discussion (comments), and voting
User profile center with Nervos DAO address binding
Homepage proposal list and treasury information display
Bilingual support (Chinese/English)

Budget Transparency: Detailed expense reports for Milestone 1, including infrastructure costs such as servers and domains, will be published separately in the coming days.

Welcome to explore the test environment and provide feedback.
Thank you for your support and trust throughout the process.

zz_tovarishch · December 4, 2025, 2:51pm

DAO v1.1 Milestone 1 基础设施支出明细

按照提案中的透明度承诺，现公布 Milestone 1 阶段的基础设施支出情况。

域名费用：
ccfdao.org：$7.5 (¥55.35)
ccfdao.dev：$12.2 (¥90.03)
小计：$19.7 (¥145.38)

服务器费用：
为优化资源使用并控制成本，测试环境目前与 BBS 复用服务器，暂未单独购买。
这一安排适合当前的 MVP 测试阶段。在 Milestone 2 (主网上线与试运行) 交付前，我们将按提案预算为 DAO v1.1 购买独立的测试环境、生产环境服务器，确保平台稳定运行并为社区正式运营做好准备。届时将公布完整的服务器配置和支出明细。

提案中为基础设施预留的总预算为 $10,000，当前支出占比 0.2%。所有节余将按承诺在项目结束时退还 DAO 金库。

DAO v1.1 Milestone 1 Infrastructure Expense Report

In accordance with the transparency commitment in our proposal, we hereby disclose infrastructure expenses for Milestone 1.

Domain Costs:
ccfdao.org: $7.5 (¥55.35)
ccfdao.dev: $12.2 (¥90.03)
Subtotal: $19.7 (¥145.38)

Server Costs:
To optimize resource utilization and control costs, the test environment currently shares servers with BBS and has not been separately purchased.
This arrangement is appropriate for the current MVP testing phase. Before Milestone 2 (Mainnet Launch & Trial Operation) delivery, we will purchase dedicated test environment and production servers for DAO v1.1 as budgeted in the proposal, ensuring stable platform operation and readiness for official community use. Complete server configuration and expense details will be disclosed at that time.

The proposal allocated $10,000 for infrastructure. Current expenses represent 0.2% of this budget. All savings will be returned to the DAO treasury as committed.

zz_tovarishch · December 20, 2025, 4:51pm

Dear community, a quick update, DAO V1.1’s kick-off (10%) and M1 (52%) funds have been paid by the DAO Treasury:
Kick-off: https://explorer.nervos.org/transaction/0x1cc067b60fe869704d48ab537b36f15ecdf8851b27b93b6bb2e67be79681675b
Details: 29,231,218*0.1 = 2,923,121.8 CKB

M1: https://explorer.nervos.org/transaction/0x2238842cbff411e10c63c316ca9bd4efabcd0e3861d29d1cf9a483b6631eb97e
Details: 29,231,218*0.52 = 15,200,233.36 CKB

Additionally, according to Transitional Policy Statement (Community Fund DAO v1.1), Terry subsidized the funds:

https://explorer.nervos.org/transaction/0xcfa0de3fb54e91ff583570551861818b423462019662ca39504d27d00d56c7df

Details: (100000*(10%+52%)-(2,923,121.8+15,200,233.36)*0.002287)/0.002287 = 8,986,395.61 CKB

亲爱的社区成员，快速更新一下，DAO V1.1 的启动资金和M1资金已由 DAO 金库支付：Kick-off: https://explorer.nervos.org/transaction/0x1cc067b60fe869704d48ab537b36f15ecdf8851b27b93b6bb2e67be79681675b
Details: 29,231,218*0.1 = 2,923,121.8 CKB

M1: https://explorer.nervos.org/transaction/0x2238842cbff411e10c63c316ca9bd4efabcd0e3861d29d1cf9a483b6631eb97e
Details: 29,231,218*0.52 = 15,200,233.36 CKB

此外，根据 Transitional Policy Statement (Community Fund DAO v1.1) 的信息，Terry 提供了资金补贴：
https://explorer.nervos.org/transaction/0xcfa0de3fb54e91ff583570551861818b423462019662ca39504d27d00d56c7df

Details: (100000*(10%+52%)-(2,923,121.8+15,200,233.36)*0.002287)/0.002287 = 8,986,395.61 CKB

zz_tovarishch · December 24, 2025, 9:52am

DAO V1.1 Weekly Progress Reports (12.24)

Dear community, we are launching regular updates on project progress. Starting this week, we will:

Publish weekly progress reports, including Dev Logs, steward team formation progress, and other important matters
Organize bi-weekly AMAs to answer community questions and discuss project directions

These updates will continue until v1.1 mainnet officially launches and the DAO Stewards team formally takes over the platform’s daily operations. Through this approach, we hope to give the community complete visibility into the project’s progress and enable timely feedback.
Here is our first weekly report:

CKB Community Fund DAO v1.1 Weekly Dev Log

Reporting Period: 2025-12-17 ~ 2025-12-23

Published: 2025-12-24

GitHub Organization: CCF-DAO1-1

1. Last Week Overview

Repository	Commits	Main Contributors
ckb-fund-dao-ui	7	Jack
app_view	5	JLer
web5-components (dev)	1	rink1969
ccfdao-v1.1-docs	2	yixiu
Total	15	-

2. ckb-fund-dao-ui (Frontend)

Repository: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

Live Preview: https://ccfdao.dev

Branch: main

2.1 Security Updates

[3863db4] Fix React Server Components CVE vulnerabilities
- Updated next, react-server-dom-webpack and other dependencies to secure versions
- Patched all package.json files based on official React security advisory

2.2 Feature Development

2.2.1 Management Center Enhancement

[7beef10] Add pagination and error handling
- Task list now supports pagination
- Auto-redirect to dedicated error page on 403 status code
- Improved pagination controls UI/UX styling
[71f99f1] Refactor task data processing logic
- Map task types using backend enum values
- Optimize deadline formatting and task data adaptation
- Enhance task list fetching and processing logic

2.2.2 Proposal Module Optimization

[fa079b7] Refactor proposal components and optimize API requests
- Extract voting logic into ProposalVoting component
- ProposalTimeline component now handles its own data fetching
- Optimize API request order to avoid duplicate calls
- Add user info caching mechanism
- Implement JWT Token auto-refresh
[12d03a8] Improve image insertion in proposal editor
- Enhanced Quill editor cursor position save and restore
- Fixed image insertion position issues
[c9b9f8a] Enhance proposal validation rules
- Funding proposals: budget and milestones are now required
- Governance proposals: milestones required when budget is provided
- Updated error messages in both English and Chinese

3. app_view (Backend Service)

Repository: GitHub - CCF-DAO1-1/app_view

Branch: main

3.1 Feature Development

[d602818] Vote time range and completion status check (WIP)
- Added get_vote_time_range API
- Added check_vote_finished API
[a1321b2] Supplemented API documentation
**[a14c394] [38db205]** Task management feature development
- Implemented task-related APIs
[0b7e32d] Timeline API
- Added api/timeline endpoint

4 web5-components (Web5 Component Library)

Repository: GitHub - CCF-DAO1-1/web5-components: Demonstrates decentralized, blockchain-based solutions for address binding and voting with cryptographic verification.

Development Branch: dev

4.1 Feature Development

[449d599] Implement unbind functionality (12-23)
- Added unbind API implementation

5 ccfdao-v1.1-docs (Documentation Site)

Repository: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

Live Preview: https://docs.ccfdao.org

Branch: main

5.1 Documentation Updates

[4284296] Add DAO v1.1 meta-rules documentation (bilingual: Chinese/English)
- Treasury Management: Two-tier treasury system, budget denomination, fund flow rules
- Governance Framework: Process overview (with Mermaid diagrams), governance scope, general rules
- Proposal Lifecycle: Community deliberation, voting, execution oversight, crisis handling
- Voting Mechanism: Approval thresholds and quorum requirements for different vote types
- Updated index page card descriptions

5.2 Feature Enhancement

[a81ab04] Mermaid diagram click-to-enlarge feature
- Support fullscreen modal view for flowcharts
- Support ESC key and backdrop click to close
- Optimized diagram centering display

6. This Week’s Plan

Handle milestone delivery governance process
Develop address unbinding feature
Relayer development (for data synchronization between different Web5 applications)
Integrate web5did-indexer for cross-PDS login, enabling BBS users to log into the DAO platform
Develop image upload feature
Optimize PDS JWT Token refresh mechanism
Add FAQ and Nervos DAO staking tutorial to documentation
Fix known bugs
Improve user experience

7. Related Links

Frontend Preview: https://ccfdao.dev
Documentation Preview: https://docs.ccfdao.org
GitHub Organization: CKB Community Fund DAO 1.1 · GitHub
Project Repositories:

8. Feedback & Discussion

We welcome all forms of feedback:

Technical Suggestions: If you have development experience, feel free to open issues or PRs on GitHub
Bug Reports: Found issues on the test environment (https://ccfdao.dev)? Please report them promptly
Steward Recruitment: Interested in serving the DAO? Welcome to apply for the Steward Team 招募 Recruitment | DAO v1.1 首届物业团队成员 Inaugural Steward Team Members

Thank you for your continued attention and support.

DAO v1.1 Proposal Team

DAO V1.1 周进展报告 (12.24)

亲爱的社区成员，我们启动定期的项目进展同步。从本周开始，我们将：

每周发布进展报告，包括开发日志（Dev Log）、物业团队组建进度、以及其他重要事项
每两周组织一次AMA，回答社区问题并讨论项目方向

这些同步将持续到v1.1主网正式上线和DAO 物业团队全面接管平台的日常运营。我们希望通过这种方式，让社区完整了解项目的推进过程，并随时提供反馈。

以下是我们第一周的进展报告：

CKB Community Fund DAO v1.1 开发周报

报告周期: 2025-12-17 ~ 2025-12-23

发布日期: 2025-12-24

GitHub 组织: CCF-DAO1-1

1. 上周概览

仓库	提交数	主要贡献者
ckb-fund-dao-ui	7	Jack
app_view	5	JLer
web5-components (dev)	1	rink1969
ccfdao-v1.1-docs	2	yixiu
合计	15	-

2. ckb-fund-dao-ui (前端平台)

仓库地址: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

在线预览: https://ccfdao.dev

分支: main

2.1 安全更新

[3863db4] 修复 React Server Components CVE 漏洞
- 更新 next、react-server-dom-webpack 等依赖至安全版本
- 根据官方 React 安全公告完成所有 package.json 文件的漏洞修补

2.2 功能开发

2.2.1 管理中心增强

[7beef10] 新增分页功能与错误处理
- 任务列表支持分页浏览
- 403 状态码自动跳转至专用错误页面
- 优化分页控件 UI/UX 样式
[71f99f1] 重构任务数据处理逻辑
- 使用后端枚举值映射任务类型
- 优化截止日期格式化与任务数据适配
- 增强任务列表获取与处理逻辑

2.2.2 提案模块优化

[fa079b7] 重构提案组件与 API 请求优化
- 将投票逻辑抽离至 ProposalVoting 组件
- ProposalTimeline 组件内置数据获取
- 优化 API 请求顺序，避免重复调用
- 新增用户信息缓存机制
- 实现 JWT Token 自动刷新
[12d03a8] 改进提案编辑器图片插入体验
- 增强 Quill 编辑器光标位置保存与恢复
- 修复图片插入位置异常问题
[c9b9f8a] 增强提案验证规则
- 资金类提案：强制要求预算和里程碑
- 治理类提案：有预算时需填写里程碑
- 更新中英文错误提示信息

3. app_view (后端服务)

仓库地址: https://github.com/CCF-DAO1-1/app_view**分支**: main

3.1 功能开发

[d602818] 投票时间范围与完成状态检查 (WIP)
- 新增 get_vote_time_range 接口
- 新增 check_vote_finished 接口
[a1321b2] 补充 API 文档
**[a14c394] [38db205]** 任务管理功能开发
- 实现任务相关 API
[0b7e32d] 时间线 API
- 新增 api/timeline 接口

4 web5-components (Web5 组件库)

仓库地址: GitHub - CCF-DAO1-1/web5-components: Demonstrates decentralized, blockchain-based solutions for address binding and voting with cryptographic verification.

开发分支: dev

4.1 功能开发

[449d599] 实现解绑功能 (12-23)
- 新增 unbind 接口实现

5 ccfdao-v1.1-docs (文档站点)

仓库地址: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

在线预览: https://docs.ccfdao.org

分支: main

5.1 文档更新

[4284296] 新增 DAO v1.1 元规则文档 (中/英双语)
- 金库管理: 两级金库体系、预算计价方式、资金流转规则
- 治理框架: 流程概览 (含 Mermaid 图)、治理范围、通用规则
- 提案生命周期: 社区审议、投票、执行监督、危机处理
- 投票机制: 各类投票的通过阈值与法定人数要求
- 更新索引页卡片描述

5.2 功能增强

[a81ab04] Mermaid 图表点击放大功能
- 支持全屏模态框查看流程图
- 支持 ESC 键和背景点击关闭
- 优化图表居中显示效果

6. 本周计划

处理里程碑交付的治理流程
取消地址绑定功能开发
Relayer开发（用于不同Web5应用之间的数据同步）
接 web5did-indexer 跨PDS登录，使得BBS用户也可以登录DAO平台
图片上传功能开发
优化 PDS JWT Token 的刷新机制
文档里增加FAQ、存NervosDAO的教程
修复已知bug
优化用户体验

7. 相关链接

前端预览: https://ccfdao.dev
文档预览: https://docs.ccfdao.org
GitHub 组织: CKB Community Fund DAO 1.1 · GitHub
项目仓库:

8. 反馈与讨论

我们欢迎所有形式的反馈：

技术建议：如果你有开发经验，欢迎直接在GitHub提issue或PR
Bug报告：在测试环境（https://ccfdao.dev) 发现问题，请及时反馈
物业招募：如果你对服务DAO感兴趣，欢迎申请物业团队招募 Recruitment | DAO v1.1 首届物业团队成员 Inaugural Steward Team Members

感谢您的持续关注与支持。

DAO v1.1 提案团队

NightLantern · December 24, 2025, 7:22pm

I Love the transparency you guys are providing! excellent work so far

zz_tovarishch · December 30, 2025, 9:39pm

DAO v1.1 进展报告 #2

报告周期：2025-12-24 ~ 2025-12-30 发布日期：2025-12-31

AMA 回顾

12月30日，我们举办了v1.1项目启动以来的首次双周AMA。会议时长约1小时，讨论内容包括：

开发进度详细同步
物业团队组建进展
社区关心的技术与治理问题

感谢所有参与的社区成员。

下次AMA：2025年1月中旬（具体时间另行通知）

本周开发进度

CKB Community Fund DAO v1.1 开发周报

报告周期: 2025-12-24 ~ 2025-12-30

发布日期: 2025-12-31

GitHub 组织: CCF-DAO1-1

1. 上周计划完成情况

计划项	状态	备注
处理里程碑交付的治理流程	进行中 50%	后端已实现，前端本周接入 `submit_milestone_report` 接口
取消地址绑定功能开发	已完成	前端钱包解绑功能已上线
Relayer 开发	进行中：30%	-
接 did-indexer 跨 PDS 登录	进行中： 80%	待测试验证
图片上传功能开发	已完成	重构为 `useImageUpload` hook，增强错误处理
优化 PDS JWT Token 的刷新机制	已完成	已在提案组件重构中实现
文档里增加 FAQ、存 Nervos DAO 的教程	已完成	新增 FAQ 文档和 Nervos DAO 存款指南
修复已知 bug	已完成	修复多项问题（404 处理、文件格式、搜索本地化等）
优化用户体验	已完成	新增搜索功能、刷新按钮、富文本编辑器升级等

计划完成率: 6/9 (67%)
为了提升编辑提案的体验，上周新增了对富文本编辑器的升级和测试，完成了 Lexical 和 Vditor 编辑器的对比测试。

2. 上周概览

仓库	提交数	主要贡献者
ckb-fund-dao-ui	24	Jack
app_view	3	JLer
ccfdao-v1.1-docs	6	yixiu
合计	33	-

3. ckb-fund-dao-ui (前端平台)

仓库地址: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

在线预览: https://ccfdao.dev

分支: main

3.1 富文本编辑器升级 (12-28 ~ 12-30)

[3f6a853] 新增 Lexical 和 Vditor 富文本编辑器选项（预览版）
- 添加 LexicalRichTextEditor 组件，支持自定义图片节点和完整工具栏
- 添加 VditorRichTextEditor 组件，支持 Markdown 编辑和即时渲染
- 在不同提案步骤中使用不同编辑器进行对比测试
- 两种编辑器均集成图片上传功能
[1e160a7] 修复 RichTextEditor 中的 TypeScript ESLint 错误
[3c4da4e] 移除 Quill 编辑器集成，更新为 RichTextEditor
[77c24c1] 在提案组件中集成 VditorRichTextEditor，增强草稿管理
[438e3e0] 集成 Tiptap 编辑器扩展，增强 VditorRichTextEditor 功能
[3145e3b] 增强 VditorRichTextEditor 初始化和图片处理

3.2 管理中心功能 (12-29 ~ 12-30)

[9e64c0c] 实现钱包地址管理功能
[e64af73] 新增发送资金功能
[a24d87e] 增强提案状态处理和本地化更新
[566a418] 统一提案组件中的日期格式处理

3.3 钱包解绑功能 (12-25)

[0bba845] 实现用户中心钱包解绑功能
- 添加解绑钱包的 UI 组件，包括确认弹窗和成功提示
- 新增解绑按钮的 CSS 样式
- 实现解绑信息生成和解绑交易处理逻辑

3.4 图片上传优化 (12-25 ~ 12-26)

[fcc1032] 重构提案编辑器和评论中的图片上传处理
- 使用可复用的 useImageUpload hook 替代内联逻辑
- 增强图片上传失败时的错误提示
[f950107] 增强 useImageUpload hook 的错误处理和验证
- 添加返回图片 URL 的空值验证
- 改进各种上传失败场景的错误处理

3.5 DID 文件导入导出 (12-25)

[5a402f6] 更新文件下载扩展名和本地化
- 将文件下载扩展名从 .key 改为 .txt
[fbd5d25] 更新 ImportDidModal 支持的文件格式本地化
[085b8b5] 更新 ImportDidModal 组件的文件输入 accept 属性

3.6 其他改进

[6ebbcd2] 新增提案列表搜索功能 (12-24)
[b326962] 修复搜索输入框的占位符和无障碍标签本地化 (12-24)
[dc9ebbf] 新增投票权和钱包绑定刷新功能 (12-26)
[c72493e] 增强 API 响应错误处理，添加 404 页面跳转 (12-25)
[5db24ac] 更新 useImageUpload hook 中的 Quill 工具栏上下文类型 (12-25)
[64228b2] 移除 UserCenter.css 并更新导入路径 (12-25)
[4da1d1a] 规范化账户创建和验证中的 userHandle 为小写 (12-25)
[face2c7] 增强评论引用功能和草稿管理 (12-30)

4. app_view (后端服务)

仓库地址: GitHub - CCF-DAO1-1/app_view

分支: main

4.1 功能开发

[a8bd840] 新增里程碑报告提交接口 (12-30)
- 实现 api/task/submit_milestone_report 接口
[48a9408] 新增发送资金功能 (12-29)
- 实现 send_funds 接口
[c01f3b7] 投票逻辑更新 (12-29, WIP)
- 添加 test_get_vote_time_range 测试
- 更新投票逻辑

5. ccfdao-v1.1-docs (文档站点)

仓库地址: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

在线预览: https://docs.ccfdao.org

分支: main

5.1 新增文档

[7a3930a] 新增 Nervos DAO 存款指南 (12-30)
- 解释为何投票需要存入 Nervos DAO
- 对比两种存款渠道：NervDAO（网页版）和 Neuron（桌面版）
- 提供两种方式的分步指南和截图
- 说明锁定期、提款流程和投票权重规则
- 中英文版本同步

[45f919d] 新增 DAO 平台 FAQ 文档 (12-30)
- 涵盖钱包设置、投票权、提案、CKB 获取等常见问题
- 使用 Fumadocs Accordion 组件实现可折叠问答
- 包含社区联系渠道和支持资源
[42c3c3c] 新增 DAO 物业文档 (12-26)
- 定义物业团队概念及其在 DAO 中的应用
- 说明定位、使命和权限范围
- 详述核心职责：提案管理、监督、透明度
- 描述团队组建、轮换和选举机制
- 概述运营资金和问责框架

5.2 文档更新

[fbec9e2] 更新钱包设置指南 (12-30)
- 替换为 CCC 支持的钱包列表（EVM、Bitcoin、CKB、Nostr）
- 添加 JoyID 作为新用户推荐钱包（无需下载）
- 添加投票前置条件：连接钱包、创建 Web5 DID、存入 Nervos DAO
- 添加钱包类型和设置步骤的图片
[c7f1711] 重构概览章节结构 (12-26)
- 将索引页重命名为"快速开始"
- 移除导航中的冗余快速开始页面
- 修复内部链接路径

5.3 功能增强

[2ae2e5b] 启用目录的 clerk 样式 (12-30)
- 为 DocsPage 添加连接线导航样式

6. 本周计划

继续开发治理相关业务流程
继续 Relayer 开发和测试
继续优化富文本编辑器体验
开发个人治理记录功能（个人提案记录、讨论记录、投票历史）
首页提案列表的搜索和筛选功能
将文档站点集成进dao平台中
补充更多用户指南文档
修复已知 bug
优化用户体验

7. 相关链接

前端预览: https://ccfdao.dev
文档预览: https://docs.ccfdao.org
GitHub 组织: CKB Community Fund DAO 1.1 · GitHub
项目仓库:

物业团队招募进展

自12月20日发布首届物业团队招募信息以来，我们收到了11份申请。首先，我们要向所有申请者表示衷心的感谢。你们对DAO治理建设的热情和参与意愿，正是CKB社区最宝贵的资产。

关于物业团队的定位

在此我们想再次重申：物业团队（Steward Team）是为DAO提供程序性服务的团队，没有特权投票权，没有提案审批权。物业成员作为社区一员保留个人投票权，但团队本身没有特殊权力。物业的核心职责是促进信息流和行动流，让治理流程更透明、更高效，但所有实质性决策权始终在社区手中。

遴选过程

首届物业团队的组建在由Baiyu领导的DAO v1.1提案团队主导下进行。我们会综合考虑申请者的：

专业经验与技能背景
对DAO治理的理解深度
对物业角色定位的认知
服务社区的动机与承诺

来择优遴选最合适的团队成员。

首位物业团队成员确认

我们很高兴在今天的AMA中宣布：Haoyang @_magicsheep 正式加入首届物业团队。

Haoyang是一位全栈开发者，曾在Polkadot DAO生态有丰富的治理参与经验。他的理念与物业团队的定位高度契合：协助社区成员做好治理决策，通过群体智慧让DAO的资源分配到最合适的地方。

在接下来的工作中，Haoyang会与Hongzhou一起更多地参与到社区沟通协调以及各项事务的透明同步当中。

招募持续进行

物业团队招募将持续到2025年1月15日。如果你对服务DAO治理感兴趣，依然欢迎投递申请。

感谢社区的持续关注与支持。

DAO v1.1 提案团队
2025年12月31日

DAO v1.1 Progress Report #2

Reporting Period: December 24-30, 2025 Published: December 31, 2025

AMA #1 Recap

On December 30, we held our first bi-weekly AMA since the v1.1 project launch. The meeting lasted about one hour, covering:

Detailed development progress update
Steward team formation progress
Technical and governance questions from the community

Thank you to all community members who participated.

Next AMA: Mid-January 2026 (specific time TBA)

This Week’s Development Progress

CKB Community Fund DAO v1.1 Weekly Dev Log

Reporting Period: 2025-12-24 ~ 2025-12-30

Published: 2025-12-31

GitHub Organization: CCF-DAO1-1

1. Last Week’s Plan Status

Plan Item	Status	Notes
Milestone delivery governance process	In Progress 50%	Backend implemented, frontend to integrate `submit_milestone_report` API this week
Address unbinding feature	Completed	Frontend wallet unbinding feature is live
Relayer development	In Progress: 30%	-
did-indexer cross-PDS login	In Progress 80%	Pending testing and verification
Image upload feature	Completed	Refactored to `useImageUpload` hook with enhanced error handling
Optimize PDS JWT Token refresh	Completed	Implemented in proposal component refactoring
Add FAQ and Nervos DAO deposit guide to docs	Completed	Added FAQ documentation and Nervos DAO deposit guide
Fix known bugs	Completed	Fixed multiple issues (404 handling, file formats, search localization, etc.)
Improve user experience	Completed	Added search functionality, refresh button, rich text editor upgrade, etc.

Planned Items Completion Rate: 6/9 (67%)
To improve the proposal editing experience, we added rich text editor upgrades and testing last week, completing comparison tests between Lexical and Vditor editors.

2. Last Week Overview

Repository	Commits	Main Contributors
ckb-fund-dao-ui	24	Jack
app_view	3	JLer
ccfdao-v1.1-docs	6	yixiu
Total	33	-

3. ckb-fund-dao-ui (Frontend Platform)

Repository: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

Live Preview: https://ccfdao.dev

Branch: main

3.1 Rich Text Editor Upgrade (12-28 ~ 12-30)

[3f6a853] Add Lexical and Vditor rich text editor options (preview)
- Add LexicalRichTextEditor component with custom image node and full toolbar
- Add VditorRichTextEditor component with Markdown editing and instant rendering
- Use different editors in different proposal steps for comparison testing
- Both editors integrate image upload functionality
[1e160a7] Fix TypeScript ESLint errors in RichTextEditor
[3c4da4e] Remove Quill editor integration, update to RichTextEditor
[77c24c1] Integrate VditorRichTextEditor in proposal components, enhance draft management
[438e3e0] Integrate Tiptap editor extensions, enhance VditorRichTextEditor functionality
[3145e3b] Enhance VditorRichTextEditor initialization and image handling

3.2 Management Center Features (12-29 ~ 12-30)

[9e64c0c] Implement wallet address management functionality
[e64af73] Add send funds functionality
[a24d87e] Enhance proposal status handling and localization updates
[566a418] Standardize date format handling in proposal components

3.3 Wallet Unbinding Feature (12-25)

[0bba845] Implement wallet unbinding functionality in user center
- Add UI components for unbinding wallets, including confirmation modal and success message
- Add CSS styles for unbind button
- Implement unbind info generation and unbinding transaction handling logic

3.4 Image Upload Optimization (12-25 ~ 12-26)

[fcc1032] Refactor image upload handling in proposal editor and comments
- Replace inline logic with reusable useImageUpload hook
- Enhance error messages for image upload failures
[f950107] Enhance error handling and validation in useImageUpload hook
- Add empty value validation for returned image URL
- Improve error handling for various upload failure scenarios

3.5 DID File Import/Export (12-25)

[5a402f6] Update file download extension and localization
- Change file download extension from .key to .txt
[fbd5d25] Update supported file formats localization in ImportDidModal
[085b8b5] Update file input accept attribute in ImportDidModal component

3.6 Other Improvements

[6ebbcd2] Add search functionality to proposal list (12-24)
[b326962] Fix search input placeholder and aria-label localization (12-24)
[dc9ebbf] Add refresh functionality for voting power and wallet binding (12-26)
[c72493e] Enhance API response error handling, add 404 page redirect (12-25)
[5db24ac] Update Quill toolbar context type in useImageUpload hook (12-25)
[64228b2] Remove UserCenter.css and update import path (12-25)
[4da1d1a] Normalize userHandle to lowercase in account creation and validation (12-25)
[face2c7] Enhance comment quoting functionality and draft management (12-30)

4. app_view (Backend Service)

Repository: GitHub - CCF-DAO1-1/app_view

Branch: main

4.1 Feature Development

[a8bd840] Add milestone report submission API (12-30)
- Implement api/task/submit_milestone_report endpoint
[48a9408] Add send funds functionality (12-29)
- Implement send_funds endpoint
[c01f3b7] Vote logic update (12-29, WIP)
- Add test_get_vote_time_range test
- Update voting logic

5. ccfdao-v1.1-docs (Documentation Site)

Repository: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

Live Preview: https://docs.ccfdao.org

Branch: main

5.1 New Documentation

[7a3930a] Add Nervos DAO deposit guide (12-30)
- Explain why depositing to Nervos DAO is required for voting
- Compare two deposit channels: NervDAO (web) and Neuron (desktop)
- Provide step-by-step guides with screenshots for both methods
- Document lock-up period, withdrawal process, and voting weight rules
- Sync Chinese and English versions

[45f919d] Add DAO platform FAQ documentation (12-30)
- Cover wallet setup, voting rights, proposals, CKB acquisition FAQs
- Use Fumadocs Accordion component for collapsible Q&A
- Include community contact channels and support resources
[42c3c3c] Add DAO Stewards documentation (12-26)
- Define Stewards team concept and its application in DAO
- Describe positioning, mission, and scope of authority
- Detail core responsibilities: proposal management, oversight, transparency
- Describe team formation, rotation, and election mechanisms
- Outline operational funding and accountability framework

5.2 Documentation Updates

[fbec9e2] Update wallet setup guide (12-30)
- Replace with CCC-supported wallet list (EVM, Bitcoin, CKB, Nostr)
- Add JoyID as recommended wallet for new users (no download required)
- Add voting prerequisites: connect wallet, create Web5 DID, deposit to Nervos DAO
- Add images for wallet types and setup steps
[c7f1711] Refactor overview section structure (12-26)
- Rename index page to “Quick Start”
- Remove redundant quick-start page from navigation
- Fix internal link paths

5.3 Feature Enhancement

[2ae2e5b] Enable clerk style for table of contents (12-30)
- Add connected line navigation style for DocsPage

6. This Week’s Plan

Continue developing governance-related business processes
Continue Relayer development and testing
Continue optimizing rich text editor experience
Develop personal governance records feature (personal proposal records, discussion records, voting history)
Search and filter functionality for homepage proposal list
Add more user guide documentation
Fix known bugs
Improve user experience

7. Related Links

Frontend Preview: https://ccfdao.dev
Documentation Preview: https://docs.ccfdao.org
GitHub Organization: CKB Community Fund DAO 1.1 · GitHub
Project Repositories:

Steward Team Recruitment Progress

Since launching the inaugural Steward Team recruitment on December 20, we have received 11 applications. First, we would like to express our heartfelt gratitude to all applicants. Your enthusiasm and commitment to DAO governance are the most valuable assets of the CKB community.

About the Steward Team’s Role

We would like to reiterate: the Steward Team provides procedural services to the DAO and has no privileged voting power, no proposal approval authority. Steward members retain their individual voting rights as community members, but the team itself has no special powers. The core responsibility of stewards is to facilitate information flow and action flow, making governance processes more transparent and efficient, while all substantive decision-making power remains with the community.

Selection Process

The formation of the inaugural Steward Team is led by the DAO v1.1 proposal team under Baiyu’s leadership. We will comprehensively consider applicants’:

Professional experience and skill background
Depth of understanding of DAO governance
Recognition of the steward role positioning
Motivation and commitment to serving the community

to select the most suitable team members.

First Steward Team Member Confirmed

We are pleased to announce in today’s AMA: Haoyang @_magicsheep has officially joined the inaugural Steward Team.

Haoyang is a full-stack developer with extensive governance participation experience in the Polkadot DAO ecosystem. His philosophy aligns highly with the Steward Team’s positioning: assisting community members in making governance decisions and allocating DAO resources to the most suitable places through collective wisdom.

Moving forward, Haoyang will join Hongzhou in engaging more with community communication, coordination, and transparent updates on various matters.

Recruitment Continues

Steward Team recruitment will continue until January 15, 2025. If you are interested in serving DAO governance, applications are still welcome.

DAO v1.1 Proposal Team
2025-12-31

_magicsheep · January 5, 2026, 3:05pm

Hey Nervos community, I’m Haoyang. Moving forward, I’ll try to engage with the community as much as possible. I’m relatively new to the Nervos ecosystem, but I’m not unfamiliar with community management (and the drama it can create ).

Hope my past experiences can help Nervos allocate money more effectively to sincere builders through the DAO v1.1 system: less drama, more communication

zz_tovarishch · January 7, 2026, 3:25am

DAO v1.1 进展报告 #3

Dear community，

这是DAO v1.1的第三周进展报告。本周主要聚焦在平台功能开发和用户体验优化上。

值得一提的是，从本周开始，我们的首位物业团队成员 Haoyang @_magicsheep (TG: @haoyang94) 将参与到社区同步中。他会在Telegram群组中转发并协助回答大家的问题。

以下是本周的开发进度：

CKB Community Fund DAO v1.1 开发周报

报告周期: 2025-12-31 ~ 2026-01-06

发布日期: 2026-01-07

GitHub 组织: CCF-DAO1-1

1. 上周计划完成情况

计划项	状态	备注
继续开发治理相关业务流程	进行中60%	新增会议管理功能（创建会议、提交会议报告、延期报告）
继续 Relayer 开发和测试	进行中70%	开发人员的Demo运行正常，但DAO环境下信息同步存在问题，正在深入调查中
继续优化富文本编辑器体验	已完成	VditorRichTextEditor 新增多语言支持和工具栏优化
开发个人治理记录功能	已完成	实现个人提案记录、讨论记录、投票历史功能
首页提案列表的搜索和筛选功能	已完成	新增提案状态筛选功能
将文档站点集成进 DAO 平台中	已完成	根据 DAO 里选择的语言切换到与之对应的文档页面
补充更多用户指南文档	已完成	新增 Neuron 钱包地址绑定指南
修复已知 bug	已完成	修复分页处理、Markdown 渲染等问题
优化用户体验	已完成	评论和提案组件 Markdown 支持、UI 改进

计划内事项完成率: 7/9 (78%)

2. 上周概览

仓库	提交数	主要贡献者
ckb-fund-dao-ui	6	Jack
app_view	2	JLer
ccfdao-v1.1-docs	1	yixiu
web5-components	0	rink1969
合计	9	-

3. ckb-fund-dao-ui (前端平台)

仓库地址: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

在线预览: https://ccfdao.dev

分支: main

3.1 提案筛选功能 (01-06)

[f046b87] 新增提案状态筛选和本地化更新
- 在 Treasury 组件中引入提案状态筛选功能
- 更新提案获取逻辑，在 API 请求中包含选中的状态
- 新增"整改投票"等提案状态的中英文本地化
- 优化 UI 以反映新的筛选选项
- 集成 docs.ccfdao.org 文档站点

3.2 Markdown 支持增强 (01-04)

[f8ee98e] 将 Markdown 渲染逻辑整合到工具模块
- 将 Markdown 渲染函数（isMarkdown 和 markdownToHtml）从多个组件移至新的工具模块（markdownUtils）
- 提高代码复用性和可维护性
[e7ba08c] 增强评论和提案组件的 Markdown 支持和 UI 改进
- 在 CommentItem、CommentReply 和 ProposalContent 组件中集成 Markdown 渲染
- 更新 RecordsTable 和 DiscussionRecordsTable 以支持 Markdown 内容
- 增强评论和提案的 UI 样式，包括响应式图片处理和布局改进

3.3 投票和分页优化 (01-04)

[3c0691c] 增强提案投票可见性和分页处理
- 更新 ProposalSidebar 以在多种提案状态下显示投票组件
- 改进 useRepliedList、useSelfProposalList 和 useSelfVoteList hooks 的总页数计算
- 添加 API 未返回总页数时的回退逻辑

3.4 富文本编辑器优化 (01-03)

[db73b08] 增强 VditorRichTextEditor 的多语言支持和工具栏更新
- 添加多语言支持，根据用户设置动态配置语言
- 更新初始化逻辑，在语言切换时重新初始化编辑器
- 优化不同模式下的工具栏配置

3.5 会议管理功能 (01-03)

[5f12d13] 在管理中心新增会议管理功能，增强用户中心组件
- 新增创建会议、提交会议报告、提交延期报告的弹窗
- 更新用户中心组件，使用 hooks 获取个人提案和投票数据
- 新增会议相关功能的中英文本地化
- 重构 RecordsTable 和 VotingRecordsTable 以处理动态数据获取

4. app_view (后端服务)

仓库地址: GitHub - CCF-DAO1-1/app_view

分支: main

4.1 功能开发与修复

[cfa8bd6] 修复查询参数问题 (01-05)
[ae9d566] 清理 action 代码 (01-07)

5. ccfdao-v1.1-docs (文档站点)

仓库地址: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

在线预览: https://docs.ccfdao.org

分支: main

5.1 新增文档

[5865de9] 新增 Neuron 钱包地址绑定 Web5 DID 指南 (01-06)
- 解释为何需要绑定 Neuron 钱包地址
- 提供绑定流程的分步指南和截图
- 说明如何在 Neuron 钱包中找到 NervosDAO 地址
- 包含签名和验证步骤
- 记录绑定后的效果和注意事项

6. 本周计划

支持 PW-Lock 锁仓用户的投票权重（早期通过 Portal Wallet 存入 NervosDAO 的用户）
继续治理流程的业务处理
继续 Relayer 开发和测试
开发危机处理相关接口
补充首页所需的提案统计数据接口
优化提案筛选和搜索体验
文档里补充英文版 Neuron 钱包绑定指南
文档里补充更多常见问题及解答
修复已知 bug
优化用户体验

7. 相关链接

前端预览: https://ccfdao.dev
文档预览: https://docs.ccfdao.org
GitHub 组织: CKB Community Fund DAO 1.1 · GitHub
项目仓库:

DAO v1.1 提案团队
2026年1月7日

DAO v1.1 Progress Report #3

Dear community,
This is the third weekly progress report for DAO v1.1. This week focused primarily on platform feature development and user experience optimization.

It’s worth noting that starting this week, our first Steward Team member Haoyang @_magicsheep (TG: @haoyang94) will participate in community updates. He will share updates in Telegram groups and help answer questions.

Here’s this week’s development progress:

CKB Community Fund DAO v1.1 Weekly Dev Log

Reporting Period: 2025-12-31 ~ 2026-01-06

Published: 2026-01-07

GitHub Organization: CCF-DAO1-1

1. Last Week’s Plan Status

Plan Item	Status	Notes
Continue developing governance-related business processes	In Progress 60%	Added meeting management features (create meeting, submit meeting report, delay report)
Continue Relayer development and testing	In Progress 70%	Developer’s demo runs normally, but there are issues with data sync in DAO environment, under investigation
Continue optimizing rich text editor experience	Completed	VditorRichTextEditor added multi-language support and toolbar optimization
Develop personal governance records feature	Completed	Implemented personal proposal records, discussion records, voting history
Search and filter functionality for homepage proposal list	Completed	Added proposal status filtering feature
Integrate documentation site into DAO platform	Completed	Switch to corresponding documentation page based on language selected in DAO
Add more user guide documentation	Completed	Added Neuron wallet address binding guide
Fix known bugs	Completed	Fixed pagination handling, Markdown rendering issues
Improve user experience	Completed	Markdown support for comments and proposal components, UI improvements

Planned Items Completion Rate: 7/9 (78%)

2. Last Week Overview

Repository	Commits	Main Contributors
ckb-fund-dao-ui	6	Jack
app_view	2	JLer
ccfdao-v1.1-docs	1	yixiu
web5-components	0	rink1969
Total	9	-

3. ckb-fund-dao-ui (Frontend Platform)

Repository: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

Live Preview: https://ccfdao.dev

Branch: main

3.1 Proposal Filtering Feature (01-06)

[f046b87] Add proposal status filtering and localization updates
- Introduce proposal status filter in Treasury component
- Update proposal fetching logic to include selected status in API requests
- Add localization for new proposal statuses including “Rectification Vote” in English and Chinese
- Optimize UI to reflect new filtering options
- Integrate docs.ccfdao.org documentation site

3.2 Markdown Support Enhancement (01-04)

[f8ee98e] Consolidate Markdown rendering logic into utility module
- Move Markdown rendering functions (isMarkdown and markdownToHtml) from multiple components to new utility module (markdownUtils)
- Improve code reusability and maintainability
[e7ba08c] Enhance comment and proposal components with Markdown support and UI improvements
- Integrate Markdown rendering in CommentItem, CommentReply, and ProposalContent components
- Update RecordsTable and DiscussionRecordsTable to support Markdown content
- Enhance UI styles for comments and proposals, including responsive image handling and layout improvements

3.3 Voting and Pagination Optimization (01-04)

[3c0691c] Enhance proposal voting visibility and pagination handling
- Update ProposalSidebar to display voting components for multiple proposal states
- Improve total pages calculation in useRepliedList, useSelfProposalList, and useSelfVoteList hooks
- Add fallback logic when API does not return total pages

3.4 Rich Text Editor Optimization (01-03)

[db73b08] Enhance VditorRichTextEditor with multi-language support and toolbar updates
- Add multi-language support with dynamic language configuration based on user settings
- Update initialization logic to reinitialize editor on language switch
- Optimize toolbar configuration for different modes

3.5 Meeting Management Feature (01-03)

[5f12d13] Add meeting management features in ManagementCenter, enhance user center components
- Add modals for creating meetings, submitting meeting reports, and submitting delay reports
- Update user center components to use hooks for fetching personal proposal and voting data
- Add localization for meeting-related features in English and Chinese
- Refactor RecordsTable and VotingRecordsTable to handle dynamic data fetching

4. app_view (Backend Service)

Repository: GitHub - CCF-DAO1-1/app_view

Branch: main

4.1 Feature Development and Fixes

[cfa8bd6] Fix query parameter issue (01-05)
[ae9d566] Clean up action code (01-07)

5. ccfdao-v1.1-docs (Documentation Site)

Repository: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

Live Preview: https://docs.ccfdao.org

Branch: main

5.1 New Documentation

[5865de9] Add guide for binding Neuron wallet address to Web5 DID (01-06)
- Explain why binding Neuron wallet address is needed
- Provide step-by-step guide with screenshots for the binding process
- Describe how to find NervosDAO address in Neuron wallet
- Include signing and verification steps
- Document effects and notes after binding

6. This Week’s Plan

Support voting weight for PW-Lock depositors (users who deposited to NervosDAO via Portal Wallet)
Continue governance process business handling
Continue Relayer development and testing
Develop crisis handling related APIs
Add proposal statistics data APIs for homepage
Optimize proposal filtering and search experience
Add English version of Neuron wallet binding guide to documentation
Add more FAQs to documentation
Fix known bugs
Improve user experience

7. Related Links

Frontend Preview: https://ccfdao.dev
Documentation Preview: https://docs.ccfdao.org
GitHub Organization: CKB Community Fund DAO 1.1 · GitHub
Project Repositories:

DAO v1.1 Proposal Team
2026-1-7

zz_tovarishch · January 15, 2026, 4:20pm

DAO v1.1 进展报告 #4

报告周期：2026-01-07 ~ 2026-01-15

发布日期：2026-01-16

大家好，

按照 DAO v1.1 提案的透明度承诺，我们继续做周度文字同步。本周我们已经完成了双周 AMA，AMA 中涉及的开发进度内容会在本帖中同步归档，方便大家在一个地方追踪信息流和行动流的推进。

1）CKB Community Fund DAO v1.1 开发周报

报告周期: 2026-01-07 ~ 2026-01-13

发布日期: 2026-01-14

GitHub 组织: CCF-DAO1-1

1. 上周计划完成情况

计划项	状态	备注
支持 PW-Lock 锁仓用户的投票权重	暂缓	优先联调治理流程
继续治理流程的业务处理	进行中 70%	提案各种状态下的治理组件已开发完成，目前正在联调将这些治理组件串起来形成自动化的治理流程
继续 Relayer 开发和测试	已完成	已完成独立的 demo 验证，并修复了信息不同步的问题，待治理相关的业务流程开发完成之后集成到 DAO 里
开发危机处理相关接口	进行中 50%	4 个接口，已完成 2 个
补充首页所需的提案统计数据接口	暂缓	优先联调治理流程
优化提案筛选和搜索体验	已完成	-
文档里补充英文版 Neuron 钱包绑定指南	已完成	-
文档里补充更多常见问题及解答	已完成	新增投票资格、白名单机制等 FAQ
修复已知 bug	已完成	-
优化用户体验	已完成	-

计划内事项完成率: 6/10 (60%)

2. 上周概览

仓库	提交数	主要贡献者
ckb-fund-dao-ui	10	Jack
app_view	6	JLer
ccfdao-v1.1-docs	5	yixiu
web5-components	0	-
合计	21	-

3. ckb-fund-dao-ui (前端平台)

仓库地址: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

在线预览: https://ccfdao.dev

分支: main

3.1 里程碑投票功能增强 (01-13)

[3048311] 增强里程碑投票功能，新增投票详情和错误处理
- 集成 VotingDetailsModal 用于显示投票详情
- 重构 ProposalVoting 防止重复请求
- 在 SendFundsModal 中添加交易哈希输入
- 改进 SubmitMeetingReportModal 的错误处理和验证
[c1fa246] 优化提案组件数据获取，防止重复请求
[c49c42c] 增强提案时间线和投票组件

3.2 代码重构与架构优化 (01-10 ~ 01-13)

[1cb2a19] 移除 tailwind，修复类型定义并更新图标
[a390705] 使用统一日志工具替换 console 日志
- 在各组件和 hooks 中集成集中式日志工具
- 更新 API 路由、hooks 和 UI 组件的错误处理
[e268573] 重组 CSS 文件至组件目录
- 将 4 个 CSS 文件从 src/styles/ 移至各自组件目录
- 遵循组件共置最佳实践
[8b6e234] 实现统一 HTTP 请求错误处理架构
- 添加统一 Logger 工具（环境感知日志）
- 添加标准化错误处理（handleAPIError）
- 添加错误类型定义和用户友好错误消息
- 消除 102 处重复错误处理代码
[55c9f91] 移除未使用的富文本编辑器组件和依赖
- 删除 ReactQuill、Lexical、TipTap 三个未使用的编辑器
- 移除 16 个未使用的依赖，清理 104 个 npm 包
- 减少代码约 1,575 行，预计包体积减少 800KB - 1.2MB

3.3 会议管理功能优化 (01-07 ~ 01-08)

[75edb12] 重构会议管理弹窗，增强日期/时间选择
- 更新 CreateMeetingModal 使用独立的日期和时间选择器
- 增强 SubmitMeetingReportModal 使用新的 MeetingSelect 组件
- 集成签名生成用于 API 调用
[0918339] 移除 UserCenter.css 文件，精简组件样式

4. app_view (后端服务)

仓库地址: GitHub - CCF-DAO1-1/app_view

分支: main

4.1 投票功能开发

[7cfed8e] 实现 create_vote_tx 函数并集成到提案和任务工作流 (01-09)
[ff2f337] 更新 test_get_vote_time_range 函数，改进 check_vote_meta_finished 注释 (01-13)

4.2 代码重构与修复

[775aa06] 从 ProposalState 中移除 ReviewVote 状态及相关逻辑 (01-09)
[05471f1] 添加 ProposalUriQuery 结构体，更新 get 函数以验证提案查询参数 (01-08)
[4dc8d5a] 移除 check_vote_meta_finished 函数中的调试日志 (01-09)
[ae9d566] 清理 action 代码 (01-07)

5. ccfdao-v1.1-docs (文档站点)

仓库地址: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

在线预览: https://docs.ccfdao.org

分支: main

5.1 新增文档

[0374e66] 新增英文版 NervosDAO 地址绑定 Web5 DID 指南 (01-09)
- 翻译中文绑定指南为英文
- 添加分步说明和截图引用
- 涵盖 Neuron 钱包签名和验证流程

5.2 FAQ 更新

[c888599] 更新 FAQ，新增投票资格和绑定教程链接 (01-09)
- 在治理准备 FAQ 中添加绑定教程链接
- 新增三个 FAQ：谁可以投票、白名单机制、确保参与
- 同步中英文版本

5.3 文档优化

[97f06f1] 在元规则文档中添加参考链接 (01-13)
- 在所有元规则文档末尾添加原始提案讨论链接
- 涵盖中英文版本的治理框架、提案生命周期、投票机制、资金管理
[119bc17] 在 why-dao-v1-1 和 dao-stewards 文档中添加 Talk 论坛参考链接 (01-09)
[5b05d0e] 更新 bind-nervosdao-address 的下一步链接指向 FAQ (01-09)

6. 本周计划

完成常规治理流程的联调测试（危机处理部分暂不包含在内）
文档里补充系统架构说明
文档里补充更多常见问题及解答
修复已知 bug
优化用户体验

7. 相关链接

前端预览: https://ccfdao.dev
文档预览: https://docs.ccfdao.org
GitHub 组织: CKB Community Fund DAO 1.1 · GitHub
项目仓库:

2）双周 AMA（2026-01-15）纪要与链接

我们在 2026-01-15 举办了 DAO v1.1 双周 AMA，议程包含平台开发进度、Web5 基础设施进展、以及物业团队组建进度和社区问答。

AMA 双语文字稿（Notion）：

视频回放：

3）物业团队（Steward Team）招募进展

在 2026-01-15 的 AMA 中，Haoyang 同步了物业团队的最新进度：当天是申请提交的最后一天，从这一天之后将不再接受新的申请。目前团队已经开始对部分入围申请人进行面试，后续会在面试基础上推进名单确定。

在时间安排上，Haoyang 也给出了明确计划：最终选出的 Steward 团队名单将会与 DAO v1.1 平台上线同步公布。这样做的目的很直接，就是让物业团队的就位和平台治理流程的落地在同一条节奏线上推进，减少中间的空转期。

同时需要再次强调物业团队的角色边界。Haoyang 在 AMA 中重申，DAO Steward 团队对任何提案都没有特权的投票权。更合适的理解方式是把 Steward 看作一个“高级的 AI 代理”，其核心职责不是替社区做决定，而是帮助提案团队把流程推进得更顺畅，让治理步骤更可执行，也让信息同步更及时。

测试环境与文档入口也放在这里，方便新朋友直接上手：
https://ccfdao.dev
https://docs.ccfdao.org

感谢大家持续关注。

DAO v1.1 提案、物业团队

DAO v1.1 Progress Report #4

Reporting Period: 2026-01-07 ~ 2026-01-15

Published: 2026-01-16

Hello everyone,

As part of our transparency commitment under the DAO v1.1 proposal, we continue the weekly written updates. We also just completed our bi-weekly AMA. The dev progress covered in the AMA will be archived here as well, so the community can track both information flow and execution flow in one place.

1) CKB Community Fund DAO v1.1 Weekly Dev Log

Reporting Period: 2026-01-07 ~ 2026-01-13

Published: 2026-01-14

GitHub Organization: CCF-DAO1-1

1. Last Week’s Plan Status

Plan Item	Status	Notes
Support voting weight for PW-Lock depositors	Deferred	Prioritizing governance flow integration
Continue governance-related business processing	In Progress 70%	Governance components for various proposal states are complete, currently integrating these components to form an automated governance flow
Continue Relayer development and testing	Completed	Completed standalone demo verification and fixed data sync issues, pending integration into DAO after governance flow development is complete
Develop crisis handling related APIs	In Progress 50%	4 APIs total, 2 completed
Add proposal statistics data APIs for homepage	Deferred	Prioritizing governance flow integration
Optimize proposal filtering and search experience	Completed	-
Add English version of Neuron wallet binding guide to documentation	Completed	-
Add more FAQs to documentation	Completed	Added FAQs on voting eligibility, whitelist mechanism, etc.
Fix known bugs	Completed	-
Improve user experience	Completed	-

Planned Items Completion Rate: 6/10 (60%)

2. Last Week Overview

Repository	Commits	Main Contributors
ckb-fund-dao-ui	10	Jack
app_view	6	JLer
ccfdao-v1.1-docs	5	yixiu
web5-components	0	-
Total	21	-

3. ckb-fund-dao-ui (Frontend Platform)

Repository: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

Live Preview: https://ccfdao.dev

Branch: main

3.1 Milestone Voting Enhancement (01-13)

[3048311] Enhance milestone voting functionality with new voting details and error handling
- Integrated VotingDetailsModal for displaying voting details
- Refactored ProposalVoting to prevent duplicate requests
- Added transaction hash input in SendFundsModal
- Improved error handling and validation in SubmitMeetingReportModal
[c1fa246] Optimize data fetching in proposal components to prevent duplicate requests
[c49c42c] Enhance proposal timeline and voting components

3.2 Code Refactoring and Architecture Optimization (01-10 ~ 01-13)

[1cb2a19] Remove tailwind, fix types and update icons
[a390705] Replace console logging with unified logger across components
- Integrated centralized logging utility in various components and hooks
- Updated error handling in API routes, hooks, and UI components
[e268573] Reorganize CSS files to component co-location pattern
- Moved 4 CSS files from src/styles/ to respective component directories
- Follows component co-location best practices
[8b6e234] Implement unified HTTP request error handling architecture
- Add unified Logger utility (environment-aware logging)
- Add standardized error handling (handleAPIError)
- Add error type definitions and user-friendly error messages
- Eliminated 102 duplicate error handling instances
[55c9f91] Remove unused rich text editor components and dependencies
- Deleted ReactQuill, Lexical, TipTap - three unused editors
- Removed 16 unused dependencies, cleaned up 104 npm packages
- Reduced codebase by ~1,575 lines, estimated bundle size reduction: 800KB - 1.2MB

3.3 Meeting Management Optimization (01-07 ~ 01-08)

[75edb12] Refactor meeting management modals and enhance date/time selection
- Updated CreateMeetingModal with separate date and time pickers
- Enhanced SubmitMeetingReportModal with new MeetingSelect component
- Integrated signature generation for API calls
[0918339] Remove UserCenter.css file to streamline component styling

4. app_view (Backend Service)

Repository: GitHub - CCF-DAO1-1/app_view

Branch: main

4.1 Voting Feature Development

[7cfed8e] Implement create_vote_tx function and integrate into proposal and task workflows (01-09)
[ff2f337] Update test_get_vote_time_range function and improve comment clarity in check_vote_meta_finished (01-13)

4.2 Code Refactoring and Fixes

[775aa06] Remove ReviewVote state from ProposalState and related logic (01-09)
[05471f1] Add ProposalUriQuery struct and update get function to validate proposal query parameter (01-08)
[4dc8d5a] Remove debug logging from check_vote_meta_finished function (01-09)
[ae9d566] Clean up action code (01-07)

5. ccfdao-v1.1-docs (Documentation Site)

Repository: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

Live Preview: https://docs.ccfdao.org

Branch: main

5.1 New Documentation

[0374e66] Add English guide for binding NervosDAO address to Web5 DID (01-09)
- Translated Chinese binding guide to English
- Added step-by-step instructions with screenshot references
- Covered Neuron wallet signing and verification process

5.2 FAQ Updates

[c888599] Update FAQ with voting eligibility and binding tutorial links (01-09)
- Added binding tutorial links to governance preparation FAQ
- Added three new FAQs: who can vote, whitelist mechanism, ensure participation
- Synced Chinese and English versions

5.3 Documentation Improvements

[97f06f1] Add reference links to meta-rule documents (01-13)
- Added original proposal discussion links at the end of all meta-rule documents
- Covered governance framework, proposal lifecycle, voting mechanism, fund management in both Chinese and English
[119bc17] Add Talk forum reference links to why-dao-v1-1 and dao-stewards documents (01-09)
[5b05d0e] Update next steps in bind-nervosdao-address to link FAQ (01-09)

6. This Week’s Plan

Complete integration testing of governance flow (excluding crisis handling)
Add system architecture documentation
Add more FAQs to documentation
Fix known bugs
Improve user experience

7. Related Links

Frontend Preview: https://ccfdao.dev
Documentation Preview: https://docs.ccfdao.org
GitHub Organization: CKB Community Fund DAO 1.1 · GitHub
Project Repositories:

2) Bi-weekly AMA (2026-01-15): Notes & Links

We hosted the DAO v1.1 bi-weekly AMA on 2026-01-15, covering platform development progress, Web5 infrastructure updates, steward team formation progress, and community Q&A.

Bilingual AMA script (Notion):

Video recording:

3) Steward Team Recruitment Update

In the 2026-01-15 AMA, Haoyang shared the latest status of the steward team formation: that day marked the final deadline for applications, and no new applications will be accepted afterwards. The team has already started interviewing a subset of shortlisted applicants, and will proceed to finalize the roster based on the interview outcomes.

Haoyang also clarified the timeline: the final Steward team roster will be announced together with the DAO v1.1 platform launch. The intent is straightforward: align team readiness with the actual governance flow rollout, and reduce any “gap period” where processes exist but execution capacity is missing.

Haoyang reiterated the boundary of the role as well. Stewards have no privileged voting power over any proposal. A better mental model is to view stewards as an “advanced AI agent”: their core responsibility is not to decide for the community, but to help proposal teams move smoothly through the DAO process, making steps more executable and information sync more timely.

Quick entry points:
https://ccfdao.dev
https://docs.ccfdao.org

Thank you for your continued attention.

DAO v1.1 Proposal / Stewards Team

zz_tovarishch · January 21, 2026, 2:09pm

DAO v1.1 进展报告 #5

报告周期：2026-01-16 ~ 2026-01-20

发布日期：2026-01-21

大家好，
这是 DAO v1.1 的本周开发周报。本周计划项完成率 5/5（100%），并额外完成了首页提案统计与包含危机处理在内的治理流程补全。

本周几个核心变化值得社区关注。第一，常规治理流程联调已完成。第二，治理异常分支开始落到产品里。第三，平台可用性继续提升。第四，文档侧新增了 DAO v1.1 技术概览。

下方为本周开发周报全文，包含前端、后端、文档的提交摘要与下周计划。测试入口与文档入口也在文末保留，欢迎直接体验。

CKB Community Fund DAO v1.1 开发周报

报告周期: 2026-01-14 ~ 2026-01-20

发布日期: 2026-01-21

GitHub 组织: CCF-DAO1-1

1. 上周计划完成情况

计划项	状态	备注
完成常规治理流程的联调测试（危机处理部分暂不包含在内）	已完成	治理流程联调完成
文档里补充系统架构说明	已完成	新增 DAO v1.1 技术概览文档
文档里补充更多常见问题及解答	已完成	-
修复已知 bug	已完成	修复投票数据、预算显示等问题
优化用户体验	已完成	提案草稿自动保存优化、UI 改进

计划内事项完成率: 5/5 (100%)

计划外完成事项

事项	备注
首页提案数据统计功能	集成提案状态 API，显示进行中项目和预算
包括危机处理在内的治理流程	实现整改投票、整改流程等功能

2. 上周概览

仓库	提交数	主要贡献者
ckb-fund-dao-ui	17	Jack
app_view	9	JLer
ccfdao-v1.1-docs	1	yixiu
web5-components	0	rink1969
合计	27	-

3. ckb-fund-dao-ui (前端平台)

仓库地址: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

在线预览: https://ccfdao.dev

分支: main

3.1 提案状态术语更新 (01-20)

[402ccd9] 更新提案状态术语
- 将 “Draft” 改为 “Community Review”
- 将 REVIEW_VOTE 改为 WAITING_REEXAMINE

3.2 投票功能优化 (01-19)

[86afef0] 修复投票相关问题
- 移除禁用投票信息初始化
- 修正用户投票权重显示
- 优化投票详情弹窗样式
[5827f19] 移除 MilestoneVoting 组件，将里程碑投票逻辑整合到现有组件中

3.3 投票和提案管理增强 (01-16)

[8c173da] 增强投票和提案管理功能
- 集成整改投票功能及新 API 支持
- 更新 TaskProcessingModal 处理不同任务类型
- 改进 Header 组件管理钱包断开连接
- 重构 ManagementCenter 使用统一弹窗管理
- 新增投票和提案状态的本地化
[7b4c43d] 简化会话包装，利用 PDS 客户端内置会话刷新
[8f396da] 修改存储清除函数以保留访问令牌
[68e2c5b] 改进日志记录和类型安全性

3.4 首页数据统计功能 (01-15)

[5859cd3] 集成提案状态 API 并更新仪表盘 UI
- 添加 getProposalStatus API 定义
- 创建 useProposalStatus hook
- 更新仪表盘显示进行中项目和预算
- 样式化仪表盘卡片
- 添加本地化支持
[9bf0636] 防止投票数据被本地初始化覆盖，简化 API 响应处理
[0527f84] 移除进行中预算显示的 CKB 单位转换

3.5 项目钱包和提案 UI 优化 (01-14)

[4410ec2] 优化项目钱包表格和首页 UI
- Treasury：实现钱包列表，显示 CKB 余额和浏览器链接
- Home：更新状态筛选，条件性显示投票/里程碑进度
[1aef17c] 添加项目钱包列表并优化提案 UI
- 实现 ProjectWalletsTable，获取链上 CKB 余额
- 更新提案列表根据状态显示投票进度和里程碑
[a5d4f5c] 增强报告功能并修复投票记录
- 支持报告提交和显示的 URL/富文本模式
- 修复 VotingRecordsTable 数据映射和投票权重计算
[90e30d4] 优化提案草稿自动保存（1s → 500ms 防抖）
- 添加保存状态 UI 和本地化消息
- 提高数据持久化可靠性
[94def39] 移除 tailwind，修复类型和构建错误

4. app_view (后端服务)

仓库地址: GitHub - CCF-DAO1-1/app_view

分支: main

4.1 整改流程开发

[7d65caf] 实现整改投票和整改流程 (01-14)
[eb9272a] 允许在 WaitingRectification 状态下更新提案 (01-16)
[b751045] 在整改时间线消息中添加记录差异 (01-15)

4.2 提案状态 API

[cebaa01] 新增 api/proposal/status 接口 (01-15)

4.3 投票逻辑增强

[186c102] 增强投票逻辑，添加详细失败原因并更新投票结果结构 (01-14)

4.4 Bug 修复

[c442e2a] 任务清理和添加任务 (01-15)
[71e2948] 修复 budget_amount_in_progress (01-15)
[95e6a24] 提交报告时添加时间线 (01-14)
[f45f6cd] 修复拼写错误 (01-14)

5. ccfdao-v1.1-docs (文档站点)

仓库地址: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

在线预览: https://docs.ccfdao.org

分支: main

5.1 新增文档

[030a2c7] 新增 DAO v1.1 技术概览文档 (01-18)
- 系统架构说明
- 技术栈介绍

6. 本周计划

支持 PW-Lock 锁仓用户的投票权重
第一轮内部走查测试
文档里增加用户注册 Web5 DID 的教程
文档里补充更多常见问题及解答
修复 bug
优化用户体验

7. 相关链接

前端预览: https://ccfdao.dev
文档预览: https://docs.ccfdao.org
GitHub 组织: CKB Community Fund DAO 1.1 · GitHub
项目仓库:

感谢大家持续关注。

DAO v1.1 提案、物业团队

DAO v1.1 Progress Report #5

Reporting Period: 2026-01-14 ~ 2026-01-20

Published: 2026-01-21

Hello everyone,

This is the weekly dev log for DAO v1.1. We completed 5/5 planned items (100%), and also delivered additional work including homepage proposal statistics and a more complete governance flow with crisis handling.

A few changes are especially relevant. First, integration testing for the standard governance flow is now complete. Second, governance exception handling is landing in product behavior. Third, usability and correctness improved across the board. Fourth, docs now include a DAO v1.1 technical overview.

The full dev log is pasted below, with frontend, backend, and docs changes plus next week’s plan. Links to the test environment and documentation are included at the end for hands on exploration.

CKB Community Fund DAO v1.1 Weekly Dev Log

Reporting Period: 2026-01-14 ~ 2026-01-20

Published: 2026-01-21

GitHub Organization: CCF-DAO1-1

1. Last Week’s Plan Status

Plan Item	Status	Notes
Complete integration testing of governance flow (excluding crisis handling)	Completed	Governance flow integration completed
Add system architecture documentation	Completed	Added DAO v1.1 technical overview documentation
Add more FAQs to documentation	Completed	-
Fix known bugs	Completed	Fixed voting data, budget display issues
Improve user experience	Completed	Optimized proposal draft auto-save, UI improvements

Planned Items Completion Rate: 5/5 (100%)

Additional Completed Items

Item	Notes
Homepage proposal statistics feature	Integrated proposal status API, displaying ongoing projects and budget
Governance flow including crisis handling	Implemented rectification voting, rectification process, etc.

2. Last Week Overview

Repository	Commits	Main Contributors
ckb-fund-dao-ui	17	Jack
app_view	9	JLer
ccfdao-v1.1-docs	1	yixiu
web5-components	0	rink1969
Total	27	-

3. ckb-fund-dao-ui (Frontend Platform)

Repository: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend

Live Preview: https://ccfdao.dev

Branch: main

3.1 Proposal Status Terminology Update (01-20)

[402ccd9] Update proposal status terminology
- Changed “Draft” to “Community Review”
- Changed REVIEW_VOTE to WAITING_REEXAMINE

3.2 Voting Feature Optimization (01-19)

[86afef0] Fix voting-related issues
- Remove disabled voting info initialization
- Correct user voting power display
- Refine voting details modal styling
[5827f19] Remove MilestoneVoting component and consolidate milestone voting logic into existing components

3.3 Voting and Proposal Management Enhancement (01-16)

[8c173da] Enhance voting and proposal management features
- Integrate rectification voting functionality with new API support
- Update TaskProcessingModal to handle different task types
- Improve Header component to manage wallet disconnection
- Refactor ManagementCenter to utilize unified modal management
- Add localization for new voting and proposal statuses
[7b4c43d] Simplify session wrapping by leveraging PDS client’s built-in session refresh
[8f396da] Modify storage clear function to preserve access token
[68e2c5b] Improve logging and type safety

3.4 Homepage Statistics Feature (01-15)

[5859cd3] Integrate proposal status API and update dashboard UI
- Add getProposalStatus API definition
- Create useProposalStatus hook
- Update dashboard to show ongoing projects and budget
- Style dashboard cards
- Add localization support
[9bf0636] Prevent vote data from being overwritten by local initialization and simplify API response processing
[0527f84] Remove CKB unit conversion from ongoing budget display

3.5 Project Wallets and Proposal UI Optimization (01-14)

[4410ec2] Refine project wallets table and home page UI
- Treasury: Implement wallet list with CKB balance and explorer links
- Home: Update status filter and conditionally show voting/milestone progress
[1aef17c] Add project wallet list and refine proposal UI
- Implement ProjectWalletsTable with on-chain CKB balance fetching
- Update proposal list to show voting progress and milestones based on state
[a5d4f5c] Enhance reports and fix voting records
- Support URL/Rich Text modes for report submission and display
- Fix VotingRecordsTable data mapping and vote weight calculation
[90e30d4] Optimize proposal draft auto-save (1s → 500ms debounce)
- Add save status UI with localized messages
- Improve data persistence reliability
[94def39] Remove tailwind, fix types and build errors

4. app_view (Backend Service)

Repository: GitHub - CCF-DAO1-1/app_view

Branch: main

4.1 Rectification Process Development

[7d65caf] Implement rectification voting and rectification process (01-14)
[eb9272a] Allow update proposal in WaitingRectification state (01-16)
[b751045] Add record diff in rectification timeline message (01-15)

4.2 Proposal Status API

[cebaa01] Add api/proposal/status endpoint (01-15)

4.3 Voting Logic Enhancement

[186c102] Enhance voting logic with detailed failure reasons and update vote results structure (01-14)

4.4 Bug Fixes

[c442e2a] Task clean and add task (01-15)
[71e2948] Fix budget_amount_in_progress (01-15)
[95e6a24] Add timeline when submit report (01-14)
[f45f6cd] Fix typo (01-14)

5. ccfdao-v1.1-docs (Documentation Site)

Repository: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.

Live Preview: https://docs.ccfdao.org

Branch: main

5.1 New Documentation

[030a2c7] Add comprehensive technical overview for DAO v1.1 (01-18)
- System architecture documentation
- Technology stack introduction

6. This Week’s Plan

Support voting weight for PW-Lock depositors
First round of internal testing walkthrough
Add Web5 DID registration tutorial to documentation
Add more FAQs to documentation
Fix bugs
Improve user experience

7. Related Links

Frontend Preview: https://ccfdao.dev
Documentation Preview: https://docs.ccfdao.org
GitHub Organization: CKB Community Fund DAO 1.1 · GitHub
Project Repositories:

Thank you for your continued attention.

DAO v1.1 Proposal / Stewards Team

phroi · January 22, 2026, 12:27pm

Hey @zz_tovarishch, I’d like to do short review on this Community platform (since we gonna use it, I may as well review it now while it’s being built).

Where can I ask technical questions about workings and procedures?

Phroi

P.S: I already read the available the docs, these questions do not have a clear answer over there

zz_tovarishch · January 22, 2026, 2:18pm

Hi Phroi, thanks for taking the time to review. Please feel free to post your questions right here so the answers stay public and searchable.

@yixiu.ckbfans.bit and @david-fi5box can help answer the technical / procedure questions.

phroi · January 22, 2026, 4:53pm

Thank you for your availability @zz_tovarishch, @yixiu.ckbfans.bit & @david-fi5box, please keep in mind that these are questions from me personally, as part of the Community.

Let’s start with address binding: https://docs.ccfdao.org/en/docs/developer-docs/architecture/address-binding

Workflow Steps:

Generate BindInfo: Create a message containing the target Script and the current timestamp (Unix milliseconds)

Serialize to Hex: Convert the BindInfo to a molecule-encoded hex string with 0x prefix

Sign Message: Use an offline wallet (e.g., Neuron) to sign the hex string

Combine BindInfoWithSig: Combine bind_info and sig into a single structure

Submit Transaction: Use a web wallet to transfer CKB to yourself, placing BindInfoWithSig in the witness field

Backend Verification: Scanner verifies the signature and checks if the timestamp is within ±20 minutes of the block time

Store Binding: If valid, store to database; later timestamps from the same source address will update the existing binding

Query API: Frontend retrieves binding relationships through REST endpoints

My questions are:

Which kind of addresses / locks are currently supported or forecasted?
Who decides which kind of addresses / locks are supported?
Is this decision arbitrary or there are some reasonable rules and the lock just need to satisfy them?
Can a lock integration be developed as a Github Pull Request by third parties devs?

Let’s make a few examples, how and why the following locks could be supported or not?

Quantum Resistant Lock
SECP256k1/Multisig Lock
Quantum Resistant Lock in Multisig configuration
Lock Proxy Lock
RGB++ Lock
Single Use Lock

Any single one of these locks can hold a user (or possibly multiple users in multisig) NervosDAO deposit and (while arguably technically difficult) it could make sense for CommunityDAO to allow them to vote.

At this point one could argue that any lock should be supported, not so fast. Let’s make some counter-examples:

CEX NervosDAO deposits
Foundation NervosDAO deposits
Well-known Nervos organizations NervosDAO deposits
iCKB Logic Lock holding NervosDAO deposits

These counter-examples commingle assets from multiple users (which could be ok in itself, see multisigs). The issue is more in how these individual users are able to express their own vote intention.

At this point I see two opposite solutions regarding voting on Community DAO proposals for these categories:

Allow them to have their own internal vote and then report the result as a single representative vote. This internal voting doesn’t need to follow Community DAO rules: say for example that all the members decide of their own free will to delegate to a representative (say for example an internal rule clear when joining such group), nothing wrong with that.
Alternatively, do not allow these addresses where the individual owner voting disposition cannot be reasonably determined at the time of vote using Community DAO rules. If this path is chosen, then the rules must be clear and sensible, determined well-ahead of time.

Phroi

david-fi5box · January 26, 2026, 7:31am

The issue of address binding was discussed in the first AMA, and I’d like to clarify it again here.

First, the term “address binding” doesn’t accurately reflect its actual purpose; a more precise name would be “vote delegate”.

We still use “address binding”, however, because this technology applies not only to DAO voting scenarios but also to others—it’s a more technical, neutral term.

DAO voting is a serious process, much like the US presidential election: voting is a fundamental right of every citizen.

Under normal circumstances, everyone should cast their vote in person, and only those unable to do so due to physical or other reasons would entrust someone else to vote on their behalf.

Delegate is not a standard procedure, but an emergency process designed for extreme cases.

Bringing this back to DAO voting: currently, all wallets and locks supported by CCC can participate in voting directly.

The only users who face difficulties voting directly are early adopters who used Neuron for Nervos DAO operations.

For this reason, address binding now only supports Neuron (secp256k1) as the from side, while the other end of the binding—the to side—can be any wallet or lock supported by CCC.

By the way, this is also aligned with DAO 1.0.

for your questions:

Neuron (secp256k1) as the from side, the to side can be any wallet or lock supported by CCC.
Aligned with DAO 1.0.
fix extreme cases.
For new kind of locks, maybe a PR to CCC is better. Address binding aimed to fix extreme/historical cases not new features.

phroi · January 27, 2026, 3:10am

Hey @david-fi5box, nice to meet you, thank you for taking your time to reply and explaining the reasoning

Feel free to correct me, in short:

Binding/Delegation: Legacy standard, backward compatible v1.0 (Neuron)
Direct Vote: New standard (CCC-compatible wallets)

Side Note: From the Docs this distinction is not clear enough, please improve them to clearly reflect this message.

On the choice itself, I’d like to point out that this is a reasonable, yet arbitrary. That said, being myself a CCC contributor, I’m biased towards supporting it

Understood that binding is the legacy standard and direct voting is the new standard, these docs are the source to understand how voting happens: https://docs.ccfdao.org/en/docs/developer-docs/architecture/vote#casting-votes

Reading thru, it all seems pretty reasonable, except one crucial detail:

Each proposal is created with an associated authorized voter whitelist.
Each whitelist is created by the Vote Administrator at the beginning of a Vote.
An user lock to be able to vote directly must be in the authorized voter whitelist.

This has a few consequences:

Vote Administrator has the full arbitrary power to decide who gets to vote and who doesn’t!
New voters cannot join the vote on a proposal, after the vote already started (explained nicely in the FAQ)

The tech underpinning this whitelist is explained cleanly enough, yet the Docs do not explain the basic rules that bounds its usage by Vote Administrator, so currently the Community cannot judge if a future use of such whitelist is a misuse or not.

For example, Vote Administrator can fully ban a Voter at his own arbitrary choice. Pretty sure this doesn’t happen in US presidential elections.

So my additional questions are:

Why do we even need a Voter Whitelist?
By which rules is bound the use of an all powerful tool such as Voter Whitelist?
How can the Community Audit that no mismanagement is done in the Voter Whitelist administration?

Feel free to take inspirations from my previous questions/examples,
Phroi

PS: There seems to be a misunderstanding about whitelists. Team is clarifying on Telegram, so we are discussing over there Telegram: View @NervosNetwork

PPS: Copy-pasting relevant messages:

@_magicsheep Telegram: View @NervosNetwork

Hey Phroi and Matt, thanks for the scrutiny! I’m haoyang, one of the DAO steward team member, yeah the name does sound scary , but I can assure you that this is just a naming issue, it works like this:

If you just staked your CKB, the DAO 1.1 platform needs a bit time to pull this information (currently set as once per day, UTC time); the “whitelist” is to speed up this process so testers (like me) can start testing without waiting. We just finished a meeting and agreed that the name is quite misleading, maybe “voter snapshot” would be better.

But rest assured, this does not mean only people in the whitelist can vote, everyone who staked CKB can, you can verify this once the platform is launched on testnet for community testing

@phroi Telegram: View @NervosNetwork

Hey Haoyang, nice to meet you and congratulations on the steward role Name change is welcomed. That said, I would try to explain more the:

Why do we even need a snapshot/whitelist of voters in the first place?

Issue: potential for long-term abuse and centralization is really high, so there must be an even better reason to introduce it in the first place (V1.0 indeed doesn’t have it)

Hypothetical Example:

In 2 years Cao Cao is elected in the yearly election for Community DAO v1.1 Roles as Vote Administrator and the other roles are filled by his evil lackeys

Now Cao Cao is the one controlling both the Voter Snapshot tool and the on-chain cell representation.

Cao Cao decides to ban all voters except for voters he controls.

Cao Cao updates the on-chain representation of whitelist, cause he is the one who has the power to so and there is no rule saying that he cannot do that.

Now Cao Cao fully controls CommunityDAO v1.1 until the next Community DAO v1.1 election

Cao Cao wins all upcoming elections, cause they are gonna be based on Community DAO v1.1 votes he controls (right?)
…

Result: Cao Cao owns Community DAO v1.1 treasury

I’m sure that you have pretty good reason to introduce it, so please explain to the Community your reasoning and the rules that underpins its usage. Also, what happens if these rules are violated?

Love & Peace, Phroi

@_magicsheep Telegram: View @NervosNetwork

Hi Phroi, totally valid scenario, and I just asked the dev team, they said this feature is only there for testing purpose, and it will be removed after the mainnet launch.

Although one thing I think worth clarifying is that the current whitelist mechanism doesn’t ban anyone from voting, it’s not like only the whitelisted addresses can vote, anyone with staked CKB can, the whitelist only accelerate the speed for the current system to find the information about who has staked CKB, it doesn’t prevent any addresses from voting.

@phroi Telegram: View @NervosNetwork

Hey Haoyang That’s very reassuring, thank you!! So glad to see this cleared up! Just to make sure that we are all on the same page, could your team update the Docs to reflect this change?

Feel free to update:

Documentation > Developer Docs > Architecture > Vote System:

Vote Creation Workflow

Casting Votes

SMT Whitelist Tool

Vote Data Models

Documentation > Developer Docs > Architecture > Technical Overview

Documentation > User Guide > Frequently Asked Questions:

Voting Rights & Eligibility > Who can vote?

Voting Rights & Eligibility > I just registered a Web5 DID. Why can’t I participate in the current vote?

Documentation > User Guide > Getting Started:

Important Notes

May I additionally suggest that if something exists only for testing purpose and it will not be in production, clearly label it as non-production / testing-only in Docs. This way by reading the Docs all the Community can clearly understand how CommunityDAO v1.1 is gonna work.

Also please, remember to tag me on the progress made to clear up this misunderstanding, I’d like to keep an eye on this.

Love & Peace, Phroi

david-fi5box · January 29, 2026, 5:35am

Okay, thank you for your suggestion.

The document indeed omits details on how the whitelist is generated.

Currently, the whitelist is created by scheduled tasks in the backend of the DAO 1.1 system: these tasks collect information for all users who have logged into the DAO 1.1 system and filter out those with a voting weight of 0.

For security: while Vote Meta is created by the proposer, the user whitelist, voting start/end times, and other such details are all provisioned by the DAO 1.1 backend—the proposer has no ability to modify this information at will.

That said, there are additional considerations for the whitelist to note. Since the backend’s scheduled tasks run daily at 00:00 UTC, users must complete their DAO staking no later than the day before a proposal is initiated to be eligible to vote on that proposal.
We will add this relevant information to the document and display corresponding prompts on the interface.

_magicsheep · January 29, 2026, 10:49am

DAO v1.1 进展报告 #6

报告周期：2026-01-21 ~ 2026-01-27
发布日期：2026-01-29

各位社区成员好，

这是 DAO v1.1 本周进展同步。本周除了开发日志之外，我们也按提案中的节奏向社区宣布两件关键事项：

DAO v1.1 将从本周开始进入正式开放社区公测，周期预计约 1 个月，用于在最终交付前集中收集反馈并完成收敛。
首届物业团队名单已确定并在本帖公布，以便社区在公测期间有明确的协作与沟通对象。

首届物业团队的组建在 Baiyu 领导的 DAO v1.1 提案团队主导下进行。在其运作的第一年，物业团队是 DAO v1.1 提案交付的一部分。 Baiyu提供整体领导，Haoyang 负责日常执行。物业团队的工作重点是推进流程、组织信息同步、促进协作，并不拥有任何投票特权。

另外，我们将于以下时间组织双周 AMA，用于同步开发进展、公测规划与回答社区疑问：

Fri, Jan 30 · 8:00–9:00am（Asia/Singapore, UTC+8） / Jan 29 16:00–17:00（PST）
Google Meet：https://meet.google.com/hxz-giiy-xji

一、DAO v1.1 平台社区公测

从本周开始，DAO v1.1 平台将进入面向社区的公开测试阶段。我们希望社区成员把它当作一次上线前的压力测试，重点关注可用性、流程是否顺、以及文档是否足够让新用户自助完成关键操作。

测试入口：https://ccfdao.dev
文档入口：https://docs.ccfdao.org

反馈方式：您可以在本帖留言，也可以在 GitHub 提 issue。我们会及时跟进问题并提供协助和反馈。另外后续周报也会把高频问题与处理进展做持续同步。

二、首届DAO物业成员

Haoyang @_magicsheep (TG@haoyang94)（日常执行负责人）: 全栈开发者，曾在Polkadot DAO生态有丰富的治理参与经验。他的理念是协助社区成员做好治理决策，通过群体智慧让DAO的资源分配到最合适的地方。

Nightlantern @NightLantern (TG@NightLantern100): 自 2023 年以来一直是 Nervos 社区的活跃成员，积极在X上倡导 CKB。作为 Nervos Talks 的Mod，他支持社区讨论和发展，并致力于生态系统的长期繁荣。

Hongzhou @zz_tovarishch (TG: @zz_tovarishch): DAO v1.1 提案团队成员，v1.0-V1.1过渡期协调员，熟悉DAO运作流程。

三、开发日志

1. 上周计划完成情况

计划项	状态	备注
支持 PW-Lock 锁仓用户的投票权重	已完成	后端已支持 pw_lock
第一轮内部走查测试	已完成	-
文档里增加用户注册 Web5 DID 的教程	已完成	新增完整的 Web5 DID 注册指南，含 11 张分步截图
文档里补充更多常见问题及解答	已完成	-
修复已知 bug	已完成	修复投票金额计算、UI 样式等问题
优化用户体验	已完成	QR 码下载功能、身份验证弹窗重设计、评论数本地化显示

计划内事项完成率: 6/6 (100%)

2. 上周概览

仓库	提交数	主要贡献者
ckb-fund-dao-ui	6	Jack
app_view	3	JLer
ccfdao-v1.1-docs	1	yixiu
web5-components	0	rink1969
合计	10	-

3. ckb-fund-dao-ui (前端平台)

仓库地址: https://github.com/CCF-DAO1-1/ckb-fund-dao-ui
在线预览: https://ccfdao.dev
分支: main

3.1 国际化和 UI 优化 (01-27)

[99fe87f] 国际化"更新提案"按钮文本，添加对应翻译键
[3259871] 调整 CKB 投票金额计算和显示
- 添加"投票已结束"消息
- 优化 UI 样式
[42e0dad] 添加本地化感知的评论数显示，改进导入 DID 弹窗的样式和布局
[7273379] 实现 QR 码下载功能，重新设计身份验证弹窗

3.2 投票记录功能增强 (01-22)

[4e0c2a4] 使投票记录表中的提案名称可点击
- 使用 next/link 和 postUriToHref 链接到提案详情

3.3 治理流程完善 (01-21)

[b036b3a] 添加复审会议和整改时间线事件
- 移除 review vote
- 更新相关本地化和 UI 文本

4. app_view (后端服务)

仓库地址: https://github.com/CCF-DAO1-1/app_view
分支: main

4.1 PW-Lock 支持

[79cec0b] 支持 pw_lock (01-21)
- 早期通过 Portal Wallet 存入 NervosDAO 的用户，可使用其 EVM 钱包注册 web5did 后参与投票，权重会累计其 Omnilock + pw_lock下的NervosDAO。

4.2 投票结果优化

[19cbb38] VoteResult Voting 0 (01-21)
[11fce57] 重构 VoteResult (01-21)

5. ccfdao-v1.1-docs (文档站点)

仓库地址: https://github.com/CCF-DAO1-1/ccfdao-v1.1-docs
在线预览: https://docs.ccfdao.org
分支: main

5.1 新增文档

[810ba72] 完成 Web5 DID 注册指南 (01-27)
- 新增中英文版本的完整 Web5 DID 注册教程
- 包含 11 张分步截图展示完整注册流程
- 记录前置条件：CKB 钱包设置和最低 450 CKB 要求
- 涵盖从登录到账户创建成功的 7 个主要步骤
- 添加查看/管理 Web5 身份和导出 DID 信息的章节
- 包含保护导出 DID 文件的安全警告
- 链接到下一步：绑定 Neuron 钱包地址

6. 本周计划

全功能测试
补充投票详细结果展示（包括投票人详情：投票选项、昵称、投票权重等）
正式开放社区公测
收集社区反馈，文档里补充更多常见问题及解答
修复社区提出的 bug
优化用户体验

7. 相关链接

前端预览: https://ccfdao.dev
文档预览: https://docs.ccfdao.org
GitHub 组织: https://github.com/CCF-DAO1-1
项目仓库:
- 前端: https://github.com/CCF-DAO1-1/ckb-fund-dao-ui
- 后端: https://github.com/CCF-DAO1-1/app_view
- Web5 组件: https://github.com/CCF-DAO1-1/web5-components
- 文档: https://github.com/CCF-DAO1-1/ccfdao-v1.1-docs

感谢大家持续关注。

DAO v1.1 提案、物业团队

DAO v1.1 Progress Report #6

Reporting Period: 2026-01-21 ~ 2026-01-27
Published: 2026-01-29

Hi community,

This is our weekly DAO v1.1 progress update. In addition to the dev log, we are announcing two key items this week, aligned with the proposal timeline:

DAO v1.1 will enter the official public community beta starting this week. The beta is expected to run for about one month, so we can collect feedback and converge before final delivery.
The inaugural Steward Team roster is finalized and published in this post, so the community has clear coordination points during the beta.

The inaugural Steward Team formation is led under the DAO v1.1 proposal team’s accountability, with overall leadership by Baiyu, and Haoyang leading day-to-day execution. The Steward Team focuses on moving processes forward, keeping information synchronized, and supporting coordination. It has no privileged voting power.

We will also host a bi-weekly AMA at the time below to share dev progress, beta planning, and answer community questions:

Fri, Jan 30 · 8:00–9:00am (Asia/Singapore, UTC+8) / Jan 29 16:00–17:00 (PST)
Google Meet: https://meet.google.com/hxz-giiy-xji

I. DAO v1.1 Public Community Beta

Starting this week, the DAO v1.1 platform enters the official community beta phase. We hope community members treat this as a pre-launch stress test, focusing on usability, end-to-end flow smoothness, and whether the documentation is sufficient for new users to complete key actions without assistance.

Test environment: https://ccfdao.dev
Documentation: https://docs.ccfdao.org

Feedback: Please leave comments in this thread, or open a GitHub issue. We will follow up and provide support. Future weekly reports will also summarize recurring issues and progress.

II. Inaugural DAO Steward Team Members

Haoyang @_magicsheep (TG @haoyang94) (Day-to-day execution lead): A full-stack developer with strong governance participation experience in the Polkadot DAO ecosystem. His focus is to help the community make better governance decisions, so collective wisdom allocates DAO resources to the right places.

Nightlantern @NightLantern (TG @NightLantern100): an active member of the Nervos community since 2023, advocating for CKB on X. As a moderator on Nervos Talks, he has supported community discussions and growth, and is committed to the longevity of the ecosystem.

Hongzhou @zz_tovarishch (TG: @zz_tovarishch): DAO v1.1 proposal team member and the v1.0–v1.1 transitional period coordinator, familiar with DAO operations and governance workflows.

III. CKB Community Fund DAO v1.1 Weekly Dev Log

1. Last Week’s Plan Status

Plan Item	Status	Notes
Support voting weight for PW-Lock depositors	Completed	Backend now supports pw_lock
First round of internal testing walkthrough	Completed	-
Add Web5 DID registration tutorial to documentation	Completed	Added complete Web5 DID registration guide with 11 step-by-step screenshots
Add more FAQs to documentation	Completed	-
Fix known bugs	Completed	Fixed voting amount calculation, UI styling issues
Improve user experience	Completed	QR code download, identity verification modal redesign, locale-aware comment count display

Planned Items Completion Rate: 6/6 (100%)

2. Last Week Overview

Repository	Commits	Main Contributors
ckb-fund-dao-ui	6	Jack
app_view	3	JLer
ccfdao-v1.1-docs	1	yixiu
web5-components	0	rink1969
Total	10	-

3. ckb-fund-dao-ui (Frontend Platform)

Repository: GitHub - CCF-DAO1-1/ckb-fund-dao-ui: CKB Community Fund DAO v1.1 Frontend
Live Preview: https://ccfdao.dev
Branch: main

3.1 Internationalization and UI Optimization (01-27)

[99fe87f] Internationalize “Update Proposal” button text and add corresponding translation keys
[3259871] Adjust CKB vote amount calculations and display
- Add “voting ended” message
- Refine UI styling
[42e0dad] Add locale-aware comment count display and improve import DID modal’s styling and layout
[7273379] Implement QR code download functionality and redesign the identity verification modal

3.2 Voting Records Enhancement (01-22)

[4e0c2a4] Make proposal names in the voting records table clickable
- Link to proposal details using next/link and postUriToHref

3.3 Governance Flow Improvements (01-21)

[b036b3a] Add reexamine meeting and rectification timeline events
- Remove review vote
- Update related localization and UI texts

4. app_view (Backend Service)

Repository: GitHub - CCF-DAO1-1/app_view
Branch: main

4.1 PW-Lock Support

[79cec0b] Support pw_lock (01-21)
- Users who deposited to NervosDAO via Portal Wallet can now register Web5 DID with their EVM wallet to participate in voting. Voting weight will accumulate NervosDAO deposits from both Omnilock and pw_lock.

4.2 Vote Result Optimization

[19cbb38] VoteResult Voting 0 (01-21)
[11fce57] Refactor VoteResult (01-21)

5. ccfdao-v1.1-docs (Documentation Site)

Repository: GitHub - CCF-DAO1-1/ccfdao-v1.1-docs: A comprehensive, multilingual documentation hub for CKB Community Fund DAO v1.1, featuring developer guides, user manuals, and protocol specifications.
Live Preview: https://docs.ccfdao.org
Branch: main

5.1 New Documentation

[810ba72] Complete Web5 DID registration guide (01-27)
- Add comprehensive Web5 DID registration tutorial for both Chinese and English versions
- Include 11 step-by-step screenshots showing the complete registration flow
- Document prerequisites: CKB wallet setup and minimum 450 CKB requirement
- Cover 7 main registration steps from login to account creation success
- Add sections on viewing/managing Web5 identity and exporting DID information
- Include security warnings about protecting exported DID files
- Link to next step: binding Neuron wallet address

6. This Week’s Plan

Full feature testing
Add detailed voting results display (including voter details: voting option, nickname, voting weight, etc.)
Official community beta launch
Collect community feedback, add more FAQs to documentation
Fix bugs reported by community
Improve user experience

7. Related Links

Frontend Preview: https://ccfdao.dev
Documentation Preview: https://docs.ccfdao.org
GitHub Organization: CKB Community Fund DAO 1.1 · GitHub
Project Repositories:

Thank you for your continued attention.

DAO v1.1 Proposal / Stewards Team