Spark Program | Discourse Governance Widget for CKB Community Fund DAO v1.1

[DavidLen]

CKB DAO Live Widget, a Discourse Theme Component that surfaces real-time CKB Community Fund DAO v1.1 proposal status directly inside forum discussion threads.

---

Team Profile & Contact

David Len Background: Full stack developer, blockchain developer with Discourse Theme Components and REST/RPC integrations experience. Profile: https://in.linkedin.com/in/lesinwa-david-120580a3

Arkshine Background: Discourse Theme Component specialist based in France with an extensive public portfolio of 260+ repositories, the majority focused on Discourse plugin and component development. Profile: Arkshine (Arkshine) · GitHub

---

The Problem

With the launch of CKB Community Fund DAO v1.1 on mainnet, the community now has a live, on chain governance system. But participation still requires switching between two separate places: Nervos Talk where proposals are discussed under the [DIS] and [VOT] tags, and dao.ckb.community where the actual vote is cast and results are tracked.

This context switch is friction. A community member reading a [VOT] thread has no way to see, without leaving the page, whether the vote is active, how many CKB have been committed, or how many hours remain. Deadlines are missed. Quorum goes unmet. Participation suffers.

The Solution

A lightweight Discourse Theme Component that reads live data from the CKB DAO v1.1 public API (or on chain RPC) and renders a compact status card directly inside any [VOT] forum post.

The widget shows:
Field
Example
Proposal status
Active / Passed / Failed
Countdown timer
Ends in 14h 32m
Vote totals
For: 142M CKB · Against: 31M CKB
Quorum progress
████░░░░ 67% of threshold met
Direct action link

→ Vote on www.ccfdao.dev

No wallets are touched by the widget. No backend is deployed. It is display only, read only, and lives entirely in the Discourse theme layer.

---

Technical Approach

Data source: The CKB DAO v1.1 system exposes proposal state on chain. The widget will query either the dao.ckb.community public REST API (if available), or directly via CKB RPC (get_cells, get_transaction) against the DAO v1.1 contract’s cell structure, which is documented in the public repository. The exact data source will be confirmed in the first week of the project via a brief technical discovery spike, and documented openly on GitHub before any further development.

Linking mechanism: The widget auto activates on posts tagged [VOT] by reading a metadata field (e.g., a proposal ID in the post’s first line or a dedicated custom field) to look up the correct on chain proposal. No manual editor configuration needed after initial setup.

Stack:

• Discourse Theme Component (HTML + Handlebars + SCSS + vanilla JS)

• Fetch calls to CKB RPC or DAO REST endpoint (client side only)

• Responsive layout; tested on Chrome/Firefox desktop and iOS/Android mobile

• Open source: MIT License. All code published to GitHub under [your handle]/ckb dao discourse widget.

---

Deliverables

Working Theme Component, installable in Nervos Talk admin panel with one click GitHub repository, full source, MIT licensed, with README and install instructions Mobile test report, screenshots from iOS Safari and Android Chrome confirming responsive layout Completion report, posted publicly on Nervos Talk, including fund usage breakdown

---

To Do List

• [ ] Week 1: Discovery: Map existing API endpoints on ccfdao.dev using browser DevTools; identify exact fields for status, vote counts, deadline, quorum threshold. Document findings publicly on GitHub.

• [ ] Week 1: Scaffold: Initialize Discourse Theme Component repo; implement basic data fetch and console log output.

• [ ] Week 2: Core UI: Build status card (badge, countdown, vote bars, CTA button). Style to match Nervos green/dark brand palette.

• [ ] Week 3: Integration: Implement post linking logic (auto detect proposal ID from [VOT] posts). Test on local Discourse dev instance.

• [ ] Week 4: Polish & QA: Mobile testing (iOS + Android). Cross browser check. Error states (API down, proposal not found).

• [ ] Week 4: Delivery: Submit install request to Nervos Talk admin. Publish completion report on Nervos Talk.

---

Funding Request — Total: $1,400 USD

Item	Cost	Rationale
Discovery & API/RPC research (Week 1)	$100	dasasas
Core widget development (Weeks 1–3)	$650	Theme component scaffold, data fetch layer, status card UI, post linking logic
Mobile QA & cross-browser testing (Week 4)	$250	iOS Safari + Android Chrome, Firefox/Chrome desktop, error state coverage
Total	$1,000

---

Week	Milestone
Week 1	API confirmed, repo live, data fetching works
Week 2	Status card UI complete
Week 3	Post linking logic working on dev Discourse
Week 4	Mobile QA done, completion report submitted

---

CKB Ecosystem Relevance

This project directly serves the CKB Community Fund DAO v1.1, the on-chain governance system that was just deployed to mainnet. Increasing visibility of active votes addresses a concrete, known pain point: low voter turnout on time sensitive proposals. Every improvement to governance participation strengthens the decentralization and legitimacy of CKB ecosystem funding decisions. The widget requires no off-chain server, no new token, and no protocol change, just a smarter interface on top of infrastructure that already exists.

---

Alignment with Web5 Philosophy

The widget embodies the Web5 principle of putting real data in front of real users at the moment they need it, without intermediaries, logins, or additional app installs. It is transparent (open source, client side only), user centric (reduces friction for existing community members), and small but real (a concrete deliverable in under a month, not a roadmap).

We built the governance widgets for Aave (live implementation). Those implementations use Snapshot’s API. CKB DAO v1.1 uses a custom on chain structure, which is why Week 1 is explicitly a discovery sprint to map the existing ccfdao.dev API endpoints via browser DevTools before any UI work begins. The widget architecture is proven; the CKB integration layer is the known unknown we’ve budgeted for.

CKB 社区基金 DAO v1.1 的 Discourse 治理挂件

CKB DAO 实时挂件——一个 Discourse 主题组件，可在论坛讨论帖中直接呈现 CKB 社区基金 DAO v1.1 提案的实时状态。

---

团队介绍与联系方式

David Len 背景：全栈开发者、区块链开发者，具备 Discourse 主题组件及 REST/RPC 集成经验。个人主页：https://in.linkedin.com/in/lesinwa-david-120580a3

Arkshine 背景：总部位于法国的 Discourse 主题组件专家，拥有丰富的公开作品集，共计 260+ 个代码库，其中大多数专注于 Discourse 插件和组件开发。个人主页： Arkshine (Arkshine) · GitHub

---

问题与解决方案

问题

随着 CKB 社区基金 DAO v1.1 在主网上线，社区现在拥有了一套实时的链上治理系统。但参与治理仍需在两个独立平台之间来回切换：在 Nervos Talk 上通过 [DIS] 和 [VOT] 标签讨论提案，以及在 dao.ckb.community 上实际投票并追踪结果。

这种上下文切换带来了摩擦。正在阅读 [VOT] 帖子的社区成员，若不离开页面，根本无法知晓投票是否仍然活跃、已有多少 CKB 参与，以及还剩多少小时截止。截止日期因此被错过，法定人数无法满足，参与度随之下降。

解决方案

一个轻量级的 Discourse 主题组件，从 CKB DAO v1.1 公共 API（或链上 RPC）读取实时数据，并直接在任何 [VOT] 论坛帖子中渲染一张紧凑的状态卡片。

该挂件展示以下内容：

字段	示例
提案状态	进行中 / 已通过 / 已失败
倒计时	距结束还有 14 小时 32 分钟
投票统计	赞成：1.42亿 CKB · 反对：3100万 CKB
法定人数进度	████░░░░ 已达阈值的 67%
直接操作链接	[→ 前往 www.ccfdao.dev

投票]

该挂件不涉及任何钱包操作，无需部署后端，仅供展示和读取，完全运行在 Discourse 主题层。

---

技术方案

数据来源： CKB DAO v1.1 系统在链上公开提案状态。挂件将查询 dao.ckb.community 公共 REST API（如可用），或直接通过 CKB RPC（get_cells、get_transaction）访问 DAO v1.1 合约的 Cell 结构（已在公开代码库中记录）。确切的数据来源将在项目第一周通过简短的技术调研确认，并在后续开发开始前在 GitHub 上公开记录。

关联机制： 挂件通过读取元数据字段（例如帖子首行的提案 ID 或专用自定义字段）自动在 [VOT] 标签的帖子上激活，以查找正确的链上提案，无需初始设置后再进行手动配置。

技术栈：

• Discourse 主题组件（HTML + Handlebars + SCSS + 原生 JS）

• 调用 CKB RPC 或 DAO REST 端点（仅限客户端）

• 响应式布局，已在 Chrome/Firefox 桌面端及 iOS/Android 移动端测试

开源协议： MIT 许可证，所有代码发布至 GitHub。

---

交付成果

可工作的主题组件，可在 Nervos Talk 管理面板一键安装 GitHub 仓库，完整源代码，MIT 许可，含 README 及安装说明 移动端测试报告，含 iOS Safari 和 Android Chrome 的响应式布局截图 完成报告，公开发布于 Nervos Talk，包含资金使用明细

---

任务清单

• [ ] 第 1 周：探索阶段：通过浏览器 DevTools 映射 ccfdao.dev 上的现有 API 端点；识别状态、投票数、截止时间、法定人数阈值等字段。将发现公开记录于 GitHub。

• [ ] 第 1 周：搭建 — 初始化 Discourse 主题组件代码库；实现基础数据获取并输出至控制台。

• [ ] 第 2 周：核心 UI — 构建状态卡片（徽章、倒计时、投票进度条、CTA 按钮），样式采用 Nervos 绿色/深色品牌色调。

• [ ] 第 3 周：集成 — 实现帖子关联逻辑（自动从 [VOT] 帖子中检测提案 ID），在本地 Discourse 开发实例上测试。

• [ ] 第 4 周：优化与质量保障 — 移动端测试（iOS + Android），跨浏览器检查，错误状态处理（API 宕机、提案未找到）。

• [ ] 第 4 周：交付 — 向 Nervos Talk 管理员提交安装请求，在 Nervos Talk 上发布完成报告。

---

资金申请

资金申请 — 总计：1,000 美元

项目	费用	说明
探索与 API 研究（第 1 周）	100 美元	通过 DevTools 映射 ccfdao.dev 的 API 端点
核心组件开发（第 1-3 周）	650 美元	核心组件开发：数据获取、界面展示、跳转重定向
移动端质保与跨浏览器测试（第 4 周）	250 美元	iOS Safari + Android Chrome、Firefox/Chrome 桌面端、错误状态覆盖
合计	1,000 美元

时间表

周次	里程碑
第 1 周	API 确认，代码库上线，数据获取功能可用
第 2 周	状态卡片 UI 完成
第 3 周	帖子关联逻辑在开发版 Discourse 上正常运行
第 4 周	移动端质量保障完成，完成报告提交

预计完成时间： 批准后 4 周内。

---

与 CKB 生态系统的相关性

本项目直接服务于刚刚部署至主网的链上治理系统——CKB 社区基金 DAO v1.1。提升活跃投票的可见性，针对的是一个具体且已知的痛点：时效性提案的投票率偏低。对治理参与度的每一次改善，都将强化 CKB 生态系统资金决策的去中心化程度与合法性。该挂件无需链下服务器、新代币或协议变更，仅是在现有基础设施之上构建更智能的界面。

---

与 Web5 理念的契合

该挂件体现了 Web5 的核心理念：在用户需要的时刻，无需中间商、无需登录、无需额外安装应用，将真实数据直接呈现给真实用户。它是透明的（开源、纯客户端）、以用户为中心的（降低现有社区成员的参与门槛），并且务实可交付（不是路线图，而是一个月内可落地的具体成果）。

我们曾为 Aave 构建治理挂件（均已上线），这些实现使用了 Snapshot 的 API。CKB DAO v1.1 采用自定义链上结构，这正是为什么第 1 周明确设为探索冲刺，通过浏览器 DevTools 映射现有的 ccfdao.dev API 端点，然后再开始任何界面开发工作。挂件架构已经过验证，CKB 集成层是我们已预留预算的已知未知项。

[xingtianchunyan]

Hi @DavidLen ,

Thank you for submitting the “CKB Community Fund DAO v1.1 Discourse Governance Widget” project proposal. The idea is very practical — displaying real-time voting status directly within Nervos Talk posts will significantly boost community governance participation. We appreciate your creativity and technical plan.

Before formally moving into the Spark Program committee review, we would like to confirm several key points with you to ensure the proposal fully aligns with the current ecosystem:

The governance platform has moved to a new domain: https://www.ccfdao.dev. Since DAO v1.1 itself adopts a Web5-based architecture, we recommend primarily referring to the official documentation in week 1 at https://docs.ccfdao.org/en/docs to confirm the latest proposal data structures (including status, vote counts, deadlines, quorum thresholds, and any public API/RPC endpoints).

1. DAO v1.1 platform and data structure updates:
   We suggest designing your data scraping logic based on that documentation, and publicly documenting your research findings on GitHub before proceeding with UI development to ensure easier alignment and review later.
2. Deliverables and acceptance criteria:
   The current description of deliverables remains somewhat “conceptual” (available components, codebases, test reports, completion reports). Although these aspects are reflected in several places in the proposal, they are not consolidated in the deliverables section and lack reproducible acceptance criteria. To facilitate final acceptance and reduce communication costs, we recommend that you provide clearer mappings of “deliverables” to “acceptance criteria” in your revised proposal, for example:
   ① How to install and enable the theme component (provide a Theme Component link that can be imported directly or standard installation steps), and state that no backend services are required;
   ② Provide at least 3 example pages/posts that can be used for acceptance testing (test posts), and specify under which conditions (for example, proposal ID in the first line of the post, or a designated custom field) the widget will be automatically activated;
   ③ Include a field mapping and acceptance checklist showing the authoritative data sources for each field (status, deadline, for/against, quorum threshold, percentage) (dao.ckb.community API or on-chain RPC) and the corresponding fields;
   ④ Black-box acceptance method: specify the pages to be used for comparison and the allowable error range (e.g., time discrepancies caused by refresh intervals), and the graceful degradation behavior when the API is down or the proposal does not exist (displayed message or hide logic)

After you update the proposal, please continue replying in this thread and we will arrange a formal review as soon as possible.
Thanks again for your thorough preparation—we look forward to reviewing the revised version!

Sincerely,
Xingtian
On behalf of the Spark Review Committee

---

嗨 @DavidLen ，
感谢你们提交“CKB Community Fund DAO v1.1 Discourse Governance Widget”项目提案。这个想法非常实用——在 Nervos Talk 帖子中直接展示实时投票状态将显著提升社区治理参与度。我们感谢你们的创意和技术方案。

在正式进入 Spark Program 委员会评审之前，我们希望与您确认几个关键点，以确保提案完全符合当前生态系统：

1. DAO v1.1 平台与数据结构更新：
   治理平台已迁移到新域名 https://www.ccfdao.dev。由于 DAO v1.1 本身采用基于 Web5 的架构，我们建议在第 1 周主要参考官方文档 https://docs.ccfdao.org/en/docs，以确认最新的提案数据结构（包括状态、投票计数、截止时间、法定人数阈值以及任何公开的 API/RPC 端点）。
   建议基于该文档制定您的数据抓取逻辑，并在继续 UI 开发之前将您的研究结果公开记录在 GitHub 上，以保证后续方便对齐和复核。
2. 交付物与验收方式：
   当前交付物描述仍偏“概念化”（可用组件、代码库、测试报告、完成报告），尽管在提案中多处地方体现了相关内容，但并未在交付物中集中体现，并且也缺少可复现的验收口径。为便于后续结项验收，并减少沟通成本，特在此建议你们在修订后的提案中对“交付物”与“验收方式”做更清晰的对应说明，比如：
   ① 主题组件的安装与启用方式（提供可直接导入的 Theme Component 链接或标准安装步骤），并说明无需任何后端服务；
   ② 给出至少 3 个可用于验收的示例页面/帖子（测试贴），说明在满足哪些条件（例如帖子首行提案 ID、或指定自定义字段）时会自动激活挂件；
   ③ 补充一份字段映射与验收对照表，展示字段（状态、截止时间、赞成/反对、法定人数阈值、百分比）的权威数据来源（dao.ckb.community API 或链上 RPC）与对应字段；
   ④ 黑盒验收方法：指定对照页面与允许误差范围（如刷新间隔导致的时间差），以及 API 宕机/提案不存在时的降级表现（提示文案或隐藏逻辑）

更新提案后，请继续在此帖回复，我们会尽快安排正式评审。
再次感谢你的充分准备——我们期待审阅修改后的版本！

此致，
行天
谨代表 Spark 评审委员会

[DavidLen]

Thank you for the detailed feedback. I have updated the proposal to reflect the new domain (ccfdao.dev) and the official documentation at docs.ccfdao.org.

To address the request for reproducible acceptance criteria, I have defined the following 6 deliverables and their specific definition of done

Deliverable 1: Working Theme Component Acceptance criteria: A public GitHub repository containing the Theme Component. Installation requires only pasting the repository URL into the Nervos Talk admin panel under Customize > Theme Components. No backend service, server, or database is required. The component is confirmed installable and functional on a standard Discourse instance.

Deliverable 2: Automatic Widget Activation Acceptance criteria: The widget activates automatically on any post carrying the [VOT] tag that includes a valid proposal ID in the first line of the post body, formatted as Proposal: [ID]. Three test posts will be created and linked in the completion report for acceptance testing, covering the following states: one active proposal, one passed proposal, and one failed or expired proposal.

Deliverable 3: Field Mapping and Data Source Checklist

Display Field	Data Source	API/RPC Field	Notes
Proposal status	docs.ccfdao.org API	TBD in Week 1	Active / Passed / Failed
Countdown timer	docs.ccfdao.org API	TBD in Week 1	Derived from deadline timestamp
For votes (CKB)	docs.ccfdao.org API	TBD in Week 1
Against votes (CKB)	docs.ccfdao.org API	TBD in Week 1
Quorum threshold	docs.ccfdao.org API	TBD in Week 1	Used to calculate percentage
Quorum percentage	Calculated client-side	Derived field	(For + Against) / threshold

All TBD fields will be filled in and committed to GitHub at the end of Week 1 before any UI work begins, as a publicly reviewable discovery artifact.

Deliverable 4: Black-Box Acceptance Method Acceptance criteria: Each widget field will be compared against the corresponding live data shown on www.ccfdao.dev for the same proposal at the same time. Acceptable tolerances are as follows: countdown timer may differ by up to 60 seconds due to client-side refresh interval; vote totals and quorum percentage must match exactly. If the API is unavailable, the widget displays a single line reading “Vote data temporarily unavailable” and shows the direct link to www.ccfdao.dev. If the proposal ID is not found, the widget is hidden entirely with no error visible to the reader.

Deliverable 5: Mobile Test Report Acceptance criteria: Screenshots from iOS Safari and Android Chrome demonstrating correct rendering of all fields, submitted as part of the completion report.

Deliverable 6: Completion Report Acceptance criteria: A public post on Nervos Talk including the GitHub link, the three test post links, the field mapping table with all TBD fields resolved, the mobile screenshots, and a full breakdown of fund usage.

感谢您的详细反馈。我已更新提案，采用新域名（ccfdao.dev）并参考 docs.ccfdao.org 的官方文档。

针对可复现验收标准的要求，我定义了以下 6 项交付成果及其具体完成标准：

交付成果一：可工作的主题组件 验收标准：一个包含主题组件的公开 GitHub 仓库。安装方式仅需将仓库 URL 粘贴至 Nervos Talk 管理面板的「自定义 > 主题组件」中。无需任何后端服务、服务器或数据库。组件在标准 Discourse 实例上可确认安装并正常运行。

交付成果二：自动激活机制 验收标准：组件在任何带有 [VOT] 标签、且帖子正文第一行包含有效提案 ID（格式为 Proposal: [ID]）的帖子上自动激活。完成报告中将创建并链接三个测试帖子用于验收测试，分别对应以下状态：一个进行中的提案、一个已通过的提案、一个已失败或已过期的提案。

交付成果三：字段映射与数据来源清单

显示字段	数据来源	API/RPC 字段	备注
提案状态	docs.ccfdao.org API	第 1 周确认	进行中 / 已通过 / 已失败
倒计时	docs.ccfdao.org API	第 1 周确认	由截止时间戳推算
支持票数（CKB）	docs.ccfdao.org API	第 1 周确认
反对票数（CKB）	docs.ccfdao.org API	第 1 周确认
法定人数阈值	docs.ccfdao.org API	第 1 周确认	用于计算百分比
法定人数百分比	客户端计算	推算字段	（支持 + 反对）/ 阈值

所有待确认字段将在第 1 周结束前填写完毕并提交至 GitHub，作为可公开审查的探索成果，在任何界面开发开始之前完成。

交付成果四：黑盒验收方法 验收标准：每个组件字段将与同一时间 www.ccfdao.dev 上显示的同一提案的对应实时数据进行比对。可接受的误差范围如下：由于客户端刷新间隔，倒计时可相差最多 60 秒；投票总数和法定人数百分比必须完全一致。如果 API 不可用，组件显示一行文字「投票数据暂时不可用」并显示指向 www.ccfdao.dev 的直接链接。如果未找到提案 ID，组件完全隐藏，读者不会看到任何错误提示。

交付成果五：移动端测试报告 验收标准：提交 iOS Safari 和 Android Chrome 上所有字段正确渲染的截图，作为完成报告的一部分。

交付成果六：完成报告 验收标准：在 Nervos Talk 上发布一篇公开帖子，包含 GitHub 链接、三个测试帖子链接、所有待确认字段已填写完毕的字段映射表、移动端截图以及完整的资金使用明细。

[xingtianchunyan]

Hi @DavidLen,

Thank you for promptly updating the proposal based on the previous feedback. The added details on deliverables and acceptance criteria are generally clear and verifiable, and we appreciate your responsiveness and professionalism.

The committee has completed the formal review and is currently setting the project status to Pending. This is not a rejection, but an invitation for you to optimize the project with a more targeted approach.

The committee’s core opinion is: the project should take a more pragmatic direction, with clearer use cases and a reduced budget. The specific recommendations are as follows:

1. Use case description

Please further clarify the use case for this widget within Nervos Talk:

According to the design and implementation of DAO 1.1, community members no longer need to navigate to other websites to quickly determine whether a proposal is still in the voting period, how active the voting is, or whether it is nearing its deadline, and thus decide whether to participate in the discussion immediately or go to vote. Therefore, the committee believes the practical use case for this project within Nervos Talk is more akin to a real-time billboard aimed at community members.

2. Optimization of data retrieval methods

Your data source has been updated to use the API of https://docs.ccfdao.org. Although the documentation mentions many key APIs, the documentation itself was not designed as an API. Therefore, following the recommendation to “adjust project direction,” the committee further recommends that the real-time data required by the project be pulled directly from the API endpoints on https://www.ccfdao.dev using front-end developer tools (DevTools) (no need to reverse-engineer the RPC Cell structure), in order to further reduce the uncertainty and development risk of Week 1 research.

3. Budget adjustments due to functional differences

The current https://www.ccfdao.dev/ platform already provides a complete display of proposal statuses, so the committee suggests that the Discourse widget focus on three core functions: “fetch + display + redirect.”

• Fetch: client-side JS calls the API
• Display: card UI (e.g., status badges, countdowns, voting bars, progress bars, etc.)
• Redirect: CTA button links to ccfdao.dev
  Since the underlying data is already fully presented by the official platform, the widget is more of a “lightweight mirror + embedded notifier” rather than a complex system built from scratch.

The committee recommends reducing the budget accordingly to better match the actual scope of work.

After updating, directly @xingtianchunyan and reply here. Thank you for your enthusiasm—looking forward to seeing the revised version!

Best,
Xingtian
On behalf of the Spark Program Committee

---

Hi @DavidLen，

感谢你们根据之前的反馈及时更新了提案，新增的交付物细节和验收标准的内容都基本满足清晰且可验证的要求，我们很认可你们的响应速度和专业性。

委员会已经完成了正式评审，目前将本项目的状态设为 Pending，这不是拒绝，而是邀请你们对本项目进行更具针对性的优化。

委员会的核心意见是：项目整体方向应更加务实，需要进一步明确使用场景并缩减预算。具体建议如下：

1. 使用场景说明

   请进一步明确这个挂件在 Nervos Talk 中的使用场景：

   根据DAO 1.1 的设计和实现，社区成员已经无需再跳转到其它网站，即可快速判断提案是否仍在投票期、投票热度如何、是否接近截止，从而决定是否立即参与讨论或跳转投票。因此，委员会认为本项目在 Nervos Talk 中的实际使用场景更偏向于面向社区成员的实时的广告牌。

2. 数据获取方式优化

   你们的数据来源已更新为使用 https://docs.ccfdao.org 的 API。尽管在文档中提到了诸多关键的API，但文档本身没有设计API ，因此根据“项目方向调整“的建议，委员会进一步建议项目所需的实时数据直接通过前端开发者工具（DevTools）从 https://www.ccfdao.dev 直接抓取API接口，（无需自行逆向 RPC Cell 结构），以进一步降低 Week 1 调研的不确定性与开发风险。

3. 功能差异导致的预算调整

   当前 https://www.ccfdao.dev/ 平台已提供完整的提案状态展示，因此委员会建议 Discourse 挂件专注于“抓取 + 展示 + 跳转”三个核心功能：

   • 抓取：客户端 JS 调用 API
   • 展示：卡片 UI（比如：状态徽章、倒计时、投票条、进度条等）
   • 跳转：CTA 按钮链接到 ccfdao.dev
     由于底层数据已由官方平台完整呈现，挂件更多是“轻量镜像 + 嵌入式提醒”性质，而非从零构建复杂逻辑。

   委员会建议据此缩减预算到适当范围，以更好地匹配实际工作量。

更新后直接 @xingtianchunyan 并在此回复，感谢你们投入的热情，期待看到更新后的版本！

祝好，
行天
代表星火计划委员会

cc：@zz_tovarishch , @yixiu.ckbfans.bit , @Hanssen

[DavidLen]

Hi, Thank you for the detailed feedback.

1. Use case framing:Yes, widget does not replace ccfdao.dev, it is a governance visibility tool to increase proposal participation and community feedback. The widget reduces the friction between awareness and participation.

2. Data retrieval method: I have removed the RPC and cell structure language. The widget will call existing API endpoints on ccfdao.dev, identified via browser DevTools during Week 1. This eliminates the uncertainty originally associated with on-chain data exploration and makes the discovery sprint significantly more straightforward.

3. Budget reduction: In line with the simplified scope, we have reduced the total budget from $1,400 to $1000

你好，感谢您的详细反馈。

1. 使用场景说明 是的，该组件不会取代 ccfdao.dev，它是一个治理可见性工具，旨在提高提案参与度和社区反馈。该组件降低了社区成员从了解提案到实际参与之间的摩擦。

2. 数据获取方式 我已移除所有 RPC 和 Cell 结构相关的描述。组件将在第 1 周通过浏览器 DevTools 识别 ccfdao.dev 上的现有 API 端点，并直接调用这些端点。这消除了原本与链上数据探索相关的不确定性，使探索冲刺阶段更加简单直接。

3. 预算调整 根据简化后的项目范围，我们将总预算从 1,400 美元降低至 1,000 美元：

[xingtianchunyan]

Hi @DavidLen,

Thank you for your continued effort in refining the “Discourse Governance Widget for CKB Community Fund DAO v1.1” proposal. The committee appreciates your responsiveness throughout the review process — from incorporating our feedback on deliverables and acceptance criteria, to adjusting the data retrieval approach and reducing the budget. Your professionalism and enthusiasm for the CKB ecosystem have been evident at every step.

After careful deliberation, the committee regretfully decided to Reject this proposal. We want to be transparent about the reasons behind this decision:

1. DAO v1.1 Platform Launch Timeline Uncertainty

The committee has recently learned that the rollout schedule for the DAO v1.1 platform has slowed down. There is a realistic possibility that the platform may not yet be officially launched by the time this project would be completed. This creates a significant risk: a widget developed now may not be compatible with the final production version of the platform, potentially requiring substantial rework or rendering the deliverables unusable upon the platform’s eventual release.

2. Upcoming Changes to Nervos Talk

Additionally, the committee has recently learned that Nervos Talk itself is also planning adjustments at the structural and operational levels, which may include changes to forum sections and community governance rules. These upcoming changes introduce further uncertainty regarding the practical value and long-term applicability of the pendant under its current design.

Considering both points, the committee believes this is not the right time to advance the project; initiating it now would not be a responsible use of your efforts and community funds.

We sincerely apologize for this outcome, especially given the effort you put into revising your proposal. Please understand that this decision reflects external timing factors rather than any deficiency in the quality of your proposal or your personal ability. The committee genuinely values your enthusiasm for improving CKB governance tools and hopes you will continue to engage with the ecosystem and explore other avenues for contribution. You are also welcome to submit a new proposal once you have chosen a new direction.

Thank you again for your commitment to the CKB community and the Spark program.

---

Hi @DavidLen，

感谢你在"CKB 社区基金 DAO v1.1 Discourse 治理挂件"提案的优化过程中持续投入的努力。在整个评审流程中，从完善交付物与验收标准，到调整数据获取方式和缩减预算，委员会都非常认可你的响应速度和专业态度。

经过慎重讨论，委员会遗憾地决定拒绝本提案。我们希望坦诚地说明做出这一决定的原因：

1. DAO v1.1 平台上线节奏的不确定性

委员会近期获悉，DAO v1.1 平台的上线节奏有所放慢，可能在本项目完成时仍未正式上线。这带来了一个显著风险：现阶段开发的挂件可能无法适配平台的最终正式版本，后续可能需要大幅返工，甚至无法使用。

2. Nervos Talk 即将进行的调整

此外，委员会近期了解到 Nervos Talk 本身也在计划结构性和运营层面的调整，可能包括论坛板块和社区治理规则的变更。这些即将到来的变化对挂件在当前设计下的实用价值和长期适用性带来了进一步的不确定性。

综合以上两点，委员会认为当前并非推进该项目的合适时机，在此时启动将不是对你们的建设热情和社区资金的负责任使用。

对于这一结果，我们深表歉意，尤其考虑到你在修订提案中付出的心血。请理解，这一决定反映的是外部时机因素，而非你的提案质量或个人能力有任何不足。委员会真诚地珍视你对改善 CKB 治理工具的热情，希望你能够继续关注生态发展并探索其他方向的贡献，也欢迎你在选定新的方向后提交新的提案。

再次感谢你对 CKB 社区和 Spark 计划的投入。

Best regards,
Xingtian
On behalf of the Spark Program Committee

cc: @zz_tovarishch, @yixiu.ckbfans.bit, @Hanssen