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,
2 Likes