Spark Program 2025 Annual Report | 星火计划 2025 年度报告

English
1

A Single Spark Can Start a Prairie Fire

1. Foreword
On April 29, 2025, we launched the Spark Program. Our intention was simple: to create a low-barrier, fast-paced, developer-centric micro-grant channel (approximately $1,000 - $2,000) outside of the large-scale Community Fund DAO grants.

We wanted to support those perhaps imperfect but brilliant small ideas to land quickly. Amidst the market volatility of 2025, Spark witnessed the resilience of ecosystem builders. By the end of the year, we received a large volume of high-quality proposals. This represents not just a growth in numbers, but a testament to the vitality of the CKB developer community.

2. 2025 Data Overview
Over the past 8 months, the Spark Program has maintained efficient operations and prudent fund management:

  • Applications: Received 19 formal applications.
  • Grants: Approved 7 projects (Approval rate approx. 36.8%), covering Wallets, Payments, GameFi, Hardware Terminals, and Tools.
  • Project Status:
    • :white_check_mark: Completed: 3
    • :counterclockwise_arrows_button: Ongoing: 4
  • Financial Overview:
    • Initial Allocation: 1,886,792 CKB + 10,000 USDI
    • Disbursed Funds: 1,760,155 CKB + 1,360 USDI
    • Remaining Available: 126,637 CKB + 8,640 USDI

Please find more details:
CKB | Spark Program Dashboard

Please find the open-source files for completed projects here:

3. Project Review: Achievements & Lessons
Every Spark project is an exploration. This year’s 7 projects have accumulated valuable experience for us:

  • :trophy: Benchmark Case: Quantum Purse
    • Status: Completed (Evaluation: Excellent)
    • Highlights: Developer @Tung_Pham not only delivered the Nervos DAO integration and Electron desktop version functionality for the quantum-resistant wallet, but also proactively adapted the ccc connector during development, solving tricky issues like macOS signing.
    • Value: This was the opening success"of the Spark Program, proving that micro-grants can produce highly polished technical products and setting a benchmark for professional delivery.
  • :trophy: Practical Tool: Project Progress Tracking Platform
    • Status: Completed (Evaluation: Good)
    • Highlights: Developer @BuildUnion and his team Build Union targeted a pain point—the opacity of ecosystem project progress. By aggregating GitHub and Discord data, they delivered a visual progress tracking Dashboard.
    • Value: This reflects Spark’s support for ecosystem governance tools; communication and iteration during the delivery process were very smooth.
  • :chequered_flag: Lesson Learned: SoMo - Pixel Territory
    • Status: Concluded (Evaluation: Qualified, but with a penalty on non-technical aspects)
    • Situation: The technical MVP (Spore protocol combined with Pixel Territory) was delivered successfully by @T_Silva, but the promised “Seed User Testing” and “Community Operations” were barely conducted.
    • Resolution: The committee decided to pay only the technical portion of the funding and deduct 10% of the total funding. This demonstrates Spark’s attitude: We encourage exploration, but promises must be kept. While technical delivery is good, a complete closed-loop validation of the application is equally important.
  • :rocket: Ongoing Projects (Worth Anticipating)
    • Blackbox: @wyltek and @neon.bit team up to explore a POS Hardware Terminal supporting Fiber/CKB L2 payments, pushing for real-world offline adoption. Spark funds the project’s HCI seed testing on hardware devices.
    • AirFi: A CKB-based decentralized WiFi sharing platform verifying the application potential of payment channel technology. (By @BuildUnion)
    • WarSpore · Saga: A full-chain GameFi attempt, deeply integrating the Spore protocol to explore the gamified expression of native CKB features. (By @Crybaby)
    • HashThis: aiming to prove that data existed at a specific time and has not been altered. (By @oiclid on Discord)

4. Mechanism Review & Transparency
The Spark Program adopts a semi-centralized governance model of Committee Review + Community Public Display. Current committee members include Hanssen, Yixiu, and Zhouzhou, and coordinator Xingtian.

  • 4.1 Transparency and Knowledge Accumulation is Our Bottom Line
    To balance “decision-making efficiency” and “decentralization,” we insist on:
    • Full Process Disclosure: All applications, dialogues, approval rationales, payment hashes (multi-sig), and completion reports are synced across Discord, TG, and Nervos Talk. Please view all transactions and decision records on the dashboard CKB | Spark Program Dashboard. Our goal is to let the community see: Spark is not just distributing money, but building trust.
    • Public Code Knowledge Base: To better accumulate technical achievements and facilitate learning and reuse for community developers, we have established that all completed Spark projects’ open-source code repositories will be forked into a unified Spark GitHub organization (Spark Program · GitHub). We hope this will gradually accumulate into another “Common Knowledge Base” of code and a collection of best practice examples for the CKB ecosystem.
  • 4.2 Responding to Community Concerns: CKB/USDI Payment Ratio
    This year, voices in the community pointed out: “Since the grant is denominated in USD, why do a 50% CKB + 50% USDI split? This seems awkward and lacks confidence.”
    We heard you, and here is our explanation and improvement:
    • Context: When Spark launched (April), DAO v1.0 did not yet support stablecoin payments. We introduced 50% USDI in the Spark “experimental field” as an attempt to explore diversified funding under the technical constraints of the time. While imperfect, it gathered data for future work.
    • Improvement: Starting in 2026, Spark plans to support 100% CKB or 100% USDI payment options, resolving the fragmented experience caused by “mixed payments.”
  • 4.3 A “Sweet Burden”: Application Volume & Review Pressure
    Receiving 19 applications during a market downturn was both a surprise and an added pressure.
    • Challenge: The committee has limited manpower, making it difficult to conduct line-by-line code reviews for every project.
    • Improvement: We kindly require applicants to explicitly state “How to Verify.” In addition to listing deliverables, applicants must provide a low-cost, reproducible verification scheme. This not only reduces review pressure but also makes it easier for community members to participate in acceptance testing.
  • 4.4 2026 Platform Migration: From Discord to Nervos Talk
    Starting in 2026, the Spark Program plan to migrate from Discord to Nervos Talk.

    • Why the change: When Spark launched in 2025, we chose Discord to minimize disruption to Nervos Talk during an experimental phase. Now that Spark’s mechanisms have gradually matured, it’s time to bring it into the broader ecosystem conversation.

    • What this means:
      Application discussions, progress updates, and completion reports will be posted on Nervos Talk.
      This aligns Spark with the our effort to make Nervos Talk the central venue for ecosystem coordination and governance.
      Community members can more easily discover, follow, and engage with Spark projects.

    • Timeline: Migration will begin after the current cycle of ongoing projects concludes.

5. 2026 Technical Outlook
Spark always welcomes projects that seamlessly integrate Web2 and Web3, creating a symbiosis of technology and community. We champion applications that are small yet practical, authentic, and rooted in a human-centric philosophy. In 2026, we look forward to seeing more proposals based on the following tech stacks (but not limited to):

  • 5.1 Web5
    Web5 infrastructure is becoming increasingly mature. We encourage developers to explore scenarios combining Decentralized Identity (DID), Data Sovereignty, and On-chain Verification.
  • 5.2 CCC (CKBer’s Codebase)
    CCC aims to be the “One-Stop Solution” for CKB JS/TS ecosystem development, drastically lowering the barrier for wallet connection and transaction construction.
    • Expectation: Various dApps developed based on CCC, fully utilizing its interoperability.
    • Reference: CCC Github
  • 5.3 Spore DOB & Fiber
    • Spore/DOB: Continue exploring Digital Object innovations based on the Spore protocol (as SoMo and WarSpore are doing).
    • Fiber Network: Although projects like Blackbox have started laying the groundwork, Fiber’s maturity is still improving. We suggest developers keep a close watch on Fiber infrastructure development progress.

6. Conclusion
Spark is just the starting point.
A challenge we saw in 2025 is: Where do projects go after Spark concludes?
Currently, there is still a gap between Spark and the Community Fund DAO or even external funding. In 2026, we’d like to solve this problem: not just provide funds, but also offer Post-Spark Support. Through regular Showcases, technical guidance, and resource matchmaking, we aim to help outstanding Spark projects grow into the backbone of the ecosystem.

Thank you to the developers and the community for your continued attention and support.
In 2026, the Spark continues, and the prairie fire is expected.

Spark 2026
Spark 20261024×1536 204 KB

Spark Committee

January 2026

9 Likes
2

星星之火，可以燎原

1. 前言

2025年4月29日，我们启动了 Spark Program（星火计划）。我们的初衷非常简单：在大型 Community Fund DAO 资助之外，开辟一条低门槛、快节奏、以开发者为中心的小额资助通道（约 $1,000 - $2,000）。

我们希望支持那些或许不完美、但充满灵光的“小创意”迈出第一步。在市场起伏不定的2025年，Spark 见证了生态建设者的韧性。截止年底，我们收到了大量高质量的提案，这不仅是数字的增长，更是 CKB 开发者社区生命力的证明。

2. 2025年度数据概览

在过去的8个月里，Spark 计划保持了高效的运转和审慎的资金管理：

  • 申请情况：共收到 19 份正式申请。
  • 资助情况：批准立项 7 个（通过率约 36.8%），涵盖钱包、支付、GameFi、硬件终端及工具类。
  • 项目状态：
    • :white_check_mark: 已结项：3 个
    • :counterclockwise_arrows_button: 进行中：4 个
  • 资金概况：
    • 初始划拨：1,886,792 CKB + 10,000 USDI
    • 已分配资金：1,760,155 CKB + 1,360 USDI
    • 剩余可用：126,637 CKB + 8,640 USDI

更多细节请查看：

CKB | Spark Program Dashboard

已结项项目开源文件请查看：

3. 项目盘点：成果与经验

Spark 的每个项目都是一次探索。批准立项的7个项目为我们积累了宝贵的经验：

:trophy: 标杆案例：Quantum Purse

  • 状态：Completed（评价：优异）
  • 亮点：开发者 @Tung_Pham 不仅完美交付了抗量子钱包的Nervos DAO集成和Electron桌面版功能，更在开发过程中主动适配了 ccc 接口，解决了 macOS 签名等棘手问题。
  • 价值：这是 Spark 计划的“开门红”，证明了小额资助也能产出极高完成度的技术产品，树立了专业交付的标杆。

:trophy: 实用工具：Project Progress Tracking Platform

  • 状态：Completed（评价：良好）
  • 亮点：开发者 Emmanuel 及其团队 Build Union 瞄准了一个痛点——生态项目进度不透明。通过聚合 GitHub 和 Discord 数据，交付了一个可视化的进度追踪 Dashboard。
  • 价值：体现了 Spark 对生态治理工具的支持，项目交付过程中的沟通与迭代非常顺畅。

:chequered_flag: 经验教训：SoMo - Pixel Territory

  • 状态：Concluded（评价：合格，但在非技术层面有扣款）
  • 情况： @T_Silva 顺利交付了技术 MVP（Spore协议结合像素领地），但原本承诺的种子用户测试和社区运营几乎未开展。
  • 处理：委员会决定只支付技术部分的资助，并扣除总资助额的 10%。这表明了 Spark 的态度：我们鼓励探索，但必须信守承诺。技术交付虽好，但完整的应用闭环验证同样重要。

:rocket: 进行中项目（值得期待）

  • Blackbox： @wyltek 和 @neon.bit 联手，探索支持 Fiber/CKB L2 支付的 POS 硬件终端，推动线下的真实采用。该项目在Spark资助下进行硬件设备的HCI种子测试。
  • AirFi：基于 CKB 的去中心化 WiFi 共享平台，验证支付通道技术的应用潜力。(By @BuildUnion)
  • WarSpore · Saga：全链 GameFi 尝试，深度结合 Spore 协议，探索 CKB 原生特性的游戏化表达。 (By @Crybaby)
  • HashThis：旨在证明数据在特定时间点已存在且未被篡改。(By @oiclid on Discord)

4. 机制复盘与透明度
Spark 计划采用的是 Committee（委员会）评审 + 社区公示 的半中心化治理模式。目前的委员会成员包括 Hanssen, Yixiu，舟舟 以及协调员 Xingtian。

  • 4.1 透明度和知识沉淀是我们的底线
    为了在“决策效率”和“去中心化”之间取得平衡，我们坚持：

    • 全流程公开：所有的申请、对话、审批理由、打款哈希（多签）、结项报告，均在 Discord 、TG 和 Nervos Talk 同步。请在 CKB | Spark Program Dashboard 上查看所有交易和决策记录。我们的目标是，让社区看见：Spark 不只是发钱，更是在建立信任。
    • 代码公共知识库：为了更好地沉淀技术成果，方便社区开发者学习和复用，所有成功结项的 Spark 项目，其开源代码仓库将被 Fork 到官方统一的 GitHub 组织下。我们希望这里能逐步积累成为 CKB 生态的又一个公共代码知识库和最佳实践范例集合。

  • 4.2 回应社区关切：关于 CKB/USDI 支付比例
    今年，社区有声音指出：“既然是以美元计价的资助，为什么要搞 50% CKB + 50% USDI？这显得别扭且不自信。”
    我们听到了，并在此做出解释与改进：

    • 背景：Spark 启动时（4月），DAO v1.0 尚未支持稳定币支付。我们在 Spark 这个“试验田”中引入 50% USDI，是在当时的技术限制下，为探索多样化资助做出的尝试。这虽然不完美，但为后续工作积累了数据。
    • 改进：从2026年起，Spark 将支持 100% CKB 或 100% USDI 的支付选项，解决“混合支付”带来的体验割裂问题。

  • 4.3 甜蜜的烦恼：申请量与审核压力
    在市场低迷期，收到 19 份申请让我们既惊喜又压力倍增。

    • 挑战：委员会人力有限，难以对每个项目的代码进行逐行 Review。
    • 改进：我们恳请申请人明确“如何验证（How to Verify）”。即除了列出交付物，申请人需提供一套低成本、可复现的验证方案。这不仅减轻了审核压力，也让社区成员能更容易地参与验收。

  • 4.4 2026 年平台迁移：从 Discord 迁移到 Nervos Talk
    从 2026 年开始，Spark 项目将逐步从 Discord 迁移到 Nervos Talk。

    • 迁移原因：Spark 于 2025 年启动时，我们选择 Discord 是为了在实验阶段最大限度地减少对 Nervos Talk 的影响。现在 Spark 的各项机制已相对成熟，是时候将其纳入更广泛的生态系统对话中了。
    • 具体内容：申请讨论、进度更新和完成报告将发布在 Nervos Talk 上。这符合将 Nervos Talk 打造成生态系统协调和治理中心平台的愿景。社区成员可以更轻松地发现、关注和参与 Spark 项目。
    • 时间表：迁移将在当前进行中的项目周期结束后开始。

5. 2026 技术展望
Spark 始终欢迎任何 将Web2和Web3有机结合、技术与社区共生、小而真实、以用为纲、以人为本的项目申请。在2026年，我们期待看到更多基于以下技术栈 (不限于) 的提案：

  • 5.1 拥抱 Web5
    Web5 基础设施日益完善。我们鼓励开发者探索去中心化身份（DID）、数据主权与链上验证结合的场景。

  • 5.2 CCC (CKBer’s Codebase)
    CCC 旨在成为 CKB JS/TS 生态开发的“一站式解决方案”，极大地降低了钱包连接、交易构建的门槛。

    • 期待：基于 CCC 开发的各类 dApp，充分利用其互操作性。
    • 资源参考：CCC Github

  • 5.3 Spore DOB & Fiber

    • Spore/DOB：继续探索基于 Spore 协议的数码物创新（如 SoMo 和 WarSpore 正在做的）。
    • Fiber Network：虽然如 Blackbox 等项目已经开始布局，但目前 Fiber 成熟度尚在提升中，我们建议开发者密切关注 Fiber 基础设施的开发进展。

6. 结语
Spark 只是起点。
我们在2025年看到的一个挑战是：Spark 结项后，项目去哪儿？ 目前，从 Spark 到 Community Fund DAO 甚至外部 funding 之间，仍存在断层。2026年，Spark Committee 将致力于解决这个问题：不仅仅是提供资金，更要提供Spark结项后的扶持。我们将通过定期的 Showcase、技术指导和资源对接，帮助优秀的 Spark 项目成长为生态的中坚力量。

感谢开发者以及社区一直以来的关注和支持。

2026，星火继续，燎原可期。

Spark 2026
Spark 20261024×1536 204 KB

Spark 委员会
2026.01

2 Likes
3

Highly effective use of funds and impressive results—great report.

One idea I’ve had recently is that small grants like Sparks could be far more effective by incorporating AI or vibe coding, which is an unstoppable trend anyway. From my own experience, vibe coding has reached a 100x efficiency point—it’s about 100 times faster than coding manually in certain areas, especially for application development. For example, what used to take me three months can now be done in a single day (verified by ckb-cli-tui-vibe, and another 2 hobby projects). I’m already convinced that traditional cost evaluations based on human-hours are outdated in the AI era, and vibe coding has become an essential factor for grant programs like this moving forward.

I suggest the program team reconsider what a $5,000 grant can achieve in these remarkable times. The questions I have include:

  • Should the program encourage vibe coding?
  • Would it be better for the program to explicitly separate human and AI costs by allocating X% of the grant as vibe coding (e.g. Claude API) credits?
  • What tools can we create to support vibe coding?

Just my two cents — Looking forward to Sparks 2026!

ps. I believe AI and vibe coding are tremendous gifts to CKB (I don’t mean the AI+Blockchain propaganda). If done right, they could significantly lower the barrier for developers working with CKB/UTXO/RISC-V programming.

CKB’s programming model also excels in vibe coding:

  • In CKB applications compute off-chain, verify on-chain. This separation leads to a pattern where we can vibe code everything off-chain and verify the results with manually coded on-chain scripts.
  • Each cell has separated lock and type scripts. It’s relatively safe to vibe code type scripts if the lock scripts are still manual coded / audited, or trusted, because exploiting a bug in a type script usually requires a valid witness for the lock script. Exceptions are cases in which the consumption of a cell doesn’t require unlock/witness, like certain type scripts + anyonecanpay lock.

I believe there’s still so much more for us to explore.

8 Likes
4

Thanks Jan, fully agree. In fact, many Spark builders already rely on AI in daily development, and it clearly compresses iteration cycles, especially for app-layer prototypes.

I also agree that human-hour based cost estimation is becoming less meaningful. For Spark, I think the right evolution is: we evaluate outputs, verification cost, and security risk, rather than time spent. “How to Verify” and reproducible deliverables become the true unit of accountability.

On whether we should encourage vibe coding: personally, I’d say yes, but with two guardrails:
(1) disclosure: projects should explicitly state what AI tools were used and for which parts (similar to how academia is starting to require LLM disclosure), and
(2) boundary control: keep critical on-chain scripts / lock logic manual-coded or at least audited, while allowing aggressive AI acceleration for off-chain components.

On the AI credits idea: rather than forcing an X% split for all grants, maybe we pilot an optional AI-assisted track in 2026: small budget cap, clear deliverables, and a simple rule that AI/tooling cost is an explicit line item (credits or invoices), so it’s transparent and comparable across projects.

Finally, I love the tools to support the vibe coding direction. This could even become a small research/tooling category later: e.g., templates, CCC-based scaffolds, test harnesses, and verifiable-by-default workflows that make vibe coding safer for CKB patterns.

Looking forward to thoughts from @Hanssen, @yixiu.ckbfans.bit, and the wider community. Happy to discuss within the committee and refine based on what makes sense for Spark 2026.

7 Likes
5

很赞成，只要官方文档和github库足够全面和可验证PASS，那其实AI编程完全没有问题，我的应用目前就是这样，采取CCC库等

6 Likes
6

等我们近期捋顺怎么把申请流程迁到Talk上进行
快来快来，申请Spark

5 Likes