Thanks received
2 Likes
Hi @devnash ，
We have noticed that it has been some time since the last progress update, so we are reaching out to check on the latest developments.
First, I hope you and your team are doing well. Please take good care of your health and maintain a balance between work and rest.
From the project’s perspective, we are eager to understand the current progress—whether it is advancing smoothly, encountering any obstacles, or what the overall status is. Even a brief update can help the committee and the community stay informed and provide support when needed.
Please share the latest status at your earliest convenience. If there are any difficulties affecting progress, please do not hesitate to let us know—the committee is willing to provide every assistance.
Your weekly updates have been stable and excellent in the past. So we look forward to your new update.
Best,
xingtian
Hi xingtian,
Thank you for checking in and for your continued support.
The project is progressing well. At the moment, we are still waiting to gather more user feedback to better understand their experience, identify areas for improvement, and make sure the next updates are aligned with actual user needs.
We will continue collecting and reviewing feedback and will share a more detailed progress update once we have sufficient responses.
You can find the current updates/feedback here:
https://x.com/cryptogalaxy254/status/2090492110046638162
https://x.com/doctorethh/status/2090492054749016440
Thank you again for your patience and support. We really appreciate the committee’s continued encouragement.
Best,
devnash
3 Likes
We love the responses we are getting for this project tbh 
2 Likes
Hi @devnash ,
I’m glad to see that you’ve received recognition from everyone. I’m also pleased that you enjoyed the process. I am confident that this kind of feedback is exactly what Spark Program expects to see.
To help the committee and community gain a clearer understanding of the actual progress of the CKB Builder Lab project’s week-six user testing task, it would be ideal to provide more details in the weekly report.
Best,
xingtian
2 Likes
Hey @xingtianchunyan, thank you for checking in on our latest progress. We’re currently wrapping up the entire process and expect to have everything completed by next week.
1 Like
Hi @devnash, I hope everything is going smoothly with your wrap-up work. Looking forward to your update~~
Hi! @xingtianchunyan Thanks for checking in. Everything is going smoothly, and we’re wrapping things up on my end. We will share an update with you shortly. Appreciate your patience!
1 Like
CKB Builder Lab: Final Report
Hello everyone,
This is the final report for CKB Builder Lab, our Spark Program project delivering interactive developer onboarding infrastructure for the CKB ecosystem. The MVP is complete and publicly released.
Links
Live demo: (https://ckb-builder-lab.vercel.app)
Repository:( GitHub - devnash11/ckb-builder-lab · GitHub )
What Was Delivered
Deliverable 1: CKB Architecture Learning Simulator
A browser-based simulator where developers create Cells, compose transactions, and watch validation unfold. How to verify:
1. Open the demo URL
2. Create a Cell (Challenge 1, Genesis mode)
3. Modify capacity, owner, type, or data
4. Execute simulation
Expected result, confirmed working: a visual flow shows input state → validation → output state, with a 5-stage validation path, rule trace, and before/after Cell counts. No wallet, node, or sign-up required; progress persists in `localStorage`.
Deliverable 2: Builder Challenge System
Three auto-verified Cell Model challenges with per-criterion feedback:
1. Create Your First Cell — capacity, lock ownership, genesis creation
2. Execute State Transition — consume one Cell, create its replacement
3. Transfer Ownership — Alice’s witness unlocks, Bob’s lock receives
Sequential unlocking, progressive hints, pass/fail explanations, reset, and a `3/3` completion state. A valid transaction can still fail a mission (e.g. Alice-to-Alice when Bob is required) — proving the challenge engine checks learning objectives, not just simulator validity.
Weekly Path
Week 1: architecture, Cell state model, challenge framework, learning flow
Week 2: deterministic simulator engine + 20 tests
Week 3: interactive three-pane workbench, Cell Journey visualization
Week 4: challenge MVP — auto-evaluation, progression, persistence
Week 5: complete beginner content — overviews, key points, Ethereum/Solana comparisons, hint history, guided tour polish
Week 6: user testing (detailed below)
Verification
npm run typecheck # passed
npm test # 5 files, 35 tests passed
npm run build # production build successful
Manual acceptance flows verified on local and production: tour, genesis creation, witness failure and recovery, ownership-transfer gating, refresh persistence, and reset.
User Testing
Outreach across 7 X posts (~10K views, Aug 20 – Sep 6), including a feedback-form call. Representative feedback:
-
*“The cell ledger + predict-before-simulate thing made CKB click.”
-
*“I could see Alice’s cell, the 66 occupied, and why the draft failed.”
-
*“Occupied capacity vs value finally makes sense.”
-
*“Doesn’t pretend to be the real VM or a wallet, which I respect… the rule trace after sim is chef’s kiss.”
One actionable nit: the mobile validation path feels cramped — recorded as the top UI follow-up. Full sources, quotes, and method are documented in [`docs/week-6-testing-report.md`]( ckb-builder-lab/docs/week-6-testing-report.md at main · devnash11/ckb-builder-lab · GitHub ).
Screenshots
Attach the 4 images from `docs/screenshots/` when posting:
* `01-lesson.png` — Learn tab, Challenge 1 with Week 5 copy
* `02-build.png` — Genesis editor, 100 capacity / 66 occupied
* `03-review.png` — Cell Journey + 5-stage validation path
* `04-completion.png` — 3/3, Alice-consumed → Bob-live transfer
Thank You
Thank you to @xingtianchunyan and the Spark Program Committee for the guidance throughout. Thank you to everyone who tried the lab and shared feedback.
The lab is live, open-source, and ready for learners.
Best,
3 Likes
Spark Program｜CKB Builder Lab – 结项报告
1. 结项评价 / Final Evaluation
完成日期 / Completion Date：2025年9月11日
1.1 评价摘要 / Evaluation Summary：
CKB Builder Lab 是一个面向 CKB 生态的交互式开发者入门基础设施，通过浏览器端的 Cell 模型模拟器和自动验证的挑战系统，帮助开发者无需配置钱包、节点或环境即可理解 CKB 的核心架构概念。项目在约 10 周内（2025年7月1日 ~ 2025年9月中旬）完成了 MVP 交付，公开交付物包括：开源代码仓库、Vercel 部署的 Web Demo、完整的本地可复现环境、35 项单元测试覆盖的确定性模拟引擎，以及基于 X 平台 outreach 的用户测试反馈。
1.2 主要成果 / Key Achievements：
完整的 CKB 架构学习模拟器（Browser-based Simulator）：
实现了纯前端的 Cell 状态模型模拟器，开发者可在浏览器中创建 Cell、修改 capacity / owner / type / data 字段、组装交易并观察验证流程展开。模拟器覆盖了 5 阶段验证路径（input state → validation → output state），包含规则追踪（rule trace）和前后 Cell 计数对比，无需钱包、节点或注册，进度通过 localStorage 持久化。
Builder 挑战系统（Auto-verified Challenge System）：
实现了 3 个逐级解锁的 Cell Model 挑战，每个挑战配备逐条件反馈（per-criterion feedback）：
① Create Your First Cell — capacity 分配、lock ownership、genesis 创建
② Execute State Transition — 消耗一个 Cell 并创建其替换物
③ Transfer Ownership — Alice 的 witness 解锁，Bob 的 lock 接收挑战引擎不仅验证模拟器的正确性，还检查学习目标是否达成（例如 Alice-to-Alice 转账在模拟器层面合法，但因不符合"Transfer Ownership"任务要求而被判定失败）。
可复现的验证证据链：
- 开源代码仓库包含完整的 TypeScript 类型检查（npm run typecheck passed）、35 项单元测试（npm test, 5 files, 35 tests passed）、生产构建（npm run build successful）。审查者可克隆仓库并在本地一键运行完整验收流程：引导教程 → genesis 创建 → witness 失败与恢复 → ownership-transfer 门控 → 刷新持久化 → 重置。
面向新手的完整学习路径：
- 包含架构概览、关键概念讲解、与 Ethereum / Solana 的对比分析、提示历史（hint history）和引导式教程（guided tour），覆盖了从零基础到理解 Cell 模型的完整认知路径。
1.2 创新点与价值 / Innovation & Value：
CKB 生态首个纯前端交互式开发者教育平台：
- 填补了 CKB 生态在"零门槛开发者入门工具"领域的空白。相较于阅读文档或观看视频，CKB Builder Lab 通过"动手操作 + 即时反馈"的学习模式，让开发者在浏览器中直接体验 Cell 模型的核心机制，显著降低了理解 CKB 独特架构的认知门槛。
以教育目标为导向的验证引擎设计：
- 挑战系统不仅验证交易模拟的正确性，还检查学习者是否真正理解了概念（如 ownership transfer 要求 Bob 接收而非 Alice 自转）。这种"模拟器合法性 ≠ 任务通过"的设计，确保学习者不能通过试错蒙混过关，必须理解底层逻辑才能完成任务。
可扩展的模块化架构：
- 项目采用 React + TypeScript 构建，模拟引擎、挑战验证器和 UI 组件完全解耦，为后续添加更多挑战（如 Type Script、DAO 操作、UDT 发行等）预留了清晰的扩展路径。
2. 评审过程 / Review Process
2.1 申请审查
项目由开发者 devnash（GitHub: devnash11）于 2025 年 6 月 14 日提交申请。初始预算为 $1,950，涵盖 14 周的开发周期，包含 5 个交付阶段（Foundation / Core Mechanic / Education / Polishing / Long-term）。@xingtianchunyan 在预审审查中提出以下补充要求：
补充更具体的输出示例和可验证的验收标准
明确团队背景和开发经验
调整预算至符合 Spark Program 档位上限
2.2 批准与执行
- 2026 年 7 月 1 日： 星火计划委员会正式批准，预算 $950 USD（100% CKB 支付）
- 2026 年 7 月 3 日： 开发者发布第一周报告
- 结项申请： 2026 年 9 月 11 日提交结项申请，并发布交付物
2.3 委员会评审意见
2025 年 9 月，委员会对项目进行了验收审查。开发者提交了完整的最终报告，包括代码仓库、Web Demo、测试报告和用户反馈汇总。委员会确认项目已交付承诺的核心功能，但指出了以下关键问题：
作为开发者教育工具，来自开发者用户的反馈是衡量项目是否真正达成“降低 CKB 入门门槛”这一核心目标的关键依据。委员会在现有交付物中未能找到足够充分的证据来支持该项目的教育有效性。同时，项目的测试并不规范，没有流程，没有 AB 测，没有埋点等。在X中找到的问卷表单（ CKB Builder Lab feedback form ）中也仅有一个象征性的问题。
3. 资金发放详情 / Funding Details
总预算：990,615 CKB（约 $950 USD），100% CKB 支付。
项目总资金（核定后）：617.5 美元（643,900 CKB）
开发者 CKB 钱包地址：
ckb1qrgqep8saj8agswr30pls73hra28ry8jlnlc3ejzh3dl2ju7xxpjxqgqq8vz2g24arkjn5wslljsq97vtmmtlcm8hut4y06k
| 发放 / Installment | 比例 / % | 金额 / Amount (CKB) | 交易哈希 / Hash |
|---|---|---|---|
| 启动资金 | 20% | 198,123 | 0x16c176f33817d2803cf9555661609fa49b481bf36f0c75cd0fe5033bf5db9ff8 |
| 中期资金 | 20% | 198,123 | 0x16c176f33817d2803cf9555661609fa49b481bf36f0c75cd0fe5033bf5db9ff8 |
| 结项资金（根据交付物质量拨付） | 25% | 247,654 CKB | 0x2444ec3e79aacdfe155614ff1b91bd9348bf38baede9091d8ebc3efae2a3bfe1 |
4. 委员会复盘 / Spark Committee Reflection
经验 1：教育类项目必须建立结构化的用户测试与反馈机制
CKB Builder Lab 作为开发者教育工具，其核心价值在于是否真正帮助目标用户（新手开发者）理解 CKB 架构。然而项目在 Week 6 的用户测试仅依赖 X 平台的社交媒体 outreach（7 条推文，不超10条回复），缺乏系统性的测试流程：没有明确的测试目标人群筛选、没有标准化的测试任务设计、没有对照组或 A/B 测试、没有埋点数据支撑用户行为分析、没有量化的学习效果评估指标。这导致委员会无法判断产品的教育效果是否达到预期，只能凭借"完成度刚刚达到及格线"的模糊印象进行评审。
建议：
对于教育类项目，验收清单应强制包含"结构化用户测试计划"：明确的测试人群画像（如"有 1 年以上 Web2 开发经验但无区块链背景的开发者"）、标准化的测试任务（如"在 30 分钟内完成 Challenge 1 并解释 Cell 的 capacity 概念"）、量化的效果指标（如"测试前后概念理解度评分提升 40%"）、以及埋点或观察记录支持的行为数据。在项目启动阶段就将用户测试预算和资源纳入规划，而非结项前临时收集反馈。
经验 2：教育工具的反馈收集需要超越"定性好评"，建立可量化的效果证据
开发者提交的用户反馈主要是定性的社交媒体评论（如"The cell ledger + predict-before-simulate thing made CKB click"），虽然正面但缺乏系统性。委员会无法从中判断：用户是否真正理解了 Cell 模型？学习曲线是否合理？哪些概念点最容易混淆？产品相比阅读文档的学习效率提升多少？这些问题的答案对于教育工具的迭代和生态推广至关重要。
建议：
教育类项目的结项交付物应包含"学习效果评估报告"，至少涵盖：测试前后知识问卷对比、任务完成时间和错误率统计、用户流失节点分析（如"40% 的用户在 Challenge 2 尝试 3 次后放弃"）、以及对照组数据（如"使用 Builder Lab 的开发者 vs 阅读文档的开发者，在相同时间内对 Cell 模型的理解度差异"）。Spark Program 应在教育类项目的申请模板中增加"开发者用户测试计划"作为必填项。
5. 总结 / Conclusion
CKB Builder Lab 在约 10 周内完成了 MVP 交付，实现了一个基于 React + TypeScript 的纯前端交互式开发者教育平台，包含 CKB Cell 模型模拟器和 3 级自动验证挑战系统。项目完成了核心功能开发，部署于 Vercel 并开源，社区审查者可通过 npm run typecheck / npm test / npm run build 一键复现验证。
在技术实现上，CKB Builder Lab 实现了其声明的核心功能。然而，作为开发者教育工具，CKB Builder Lab 在用户测试环节存在明显不足：测试缺乏系统性流程、没有量化指标、没有 A/B 对照、没有埋点数据支撑。这使得委员会无法有效评估产品的教育效果，仅能根据最终评定为"完成度刚刚达到及格线"。这一教训对于 Spark Program 后续的教育类项目具有重要参考价值——教育工具的价值不仅在于功能实现，更在于能否证明其真正帮助用户达成了学习目标。
附：项目仓库和演示页面
GitHub 仓库：GitHub - devnash11/ckb-builder-lab · GitHub
Web Demo：https://ckb-builder-lab.vercel.app/
1 Like
Thank you for the detailed final evaluation and recommendations. I understand that the main gap identified is not the technical implementation of CKB Builder Lab, but the lack of structured and quantitative evidence demonstrating its educational effectiveness.
I agree with the recommendations and will focus on implementing a structured developer user-testing process with clearly defined tester profiles, standardized learning tasks, pre-test and post-test knowledge assessments, task completion times, error rates, completion rates, drop-off points, and structured feedback.
Where practical, I will also include a comparison group using existing CKB documentation to provide a baseline for evaluating learning outcomes.
The results will be compiled into an Educational Effectiveness Report covering the methodology, anonymized user-testing data, learning-score changes, task performance, user difficulties, and key findings. I will then use these findings to make targeted improvements to the onboarding experience and challenges.
This will allow us to move beyond qualitative feedback and provide measurable evidence of whether CKB Builder Lab improves understanding of the CKB Cell Model and reduces the barrier to entry for new developers.
I appreciate the committee’s feedback and will use these recommendations to strengthen the project and make future evaluation more rigorous and evidence-based.
1 Like