1.Team Profile & Contact
-
Applicant: WuodOdhis
-
GitHub: github.com/WuodOdhis
-
Role: Full-stack developer with experience in blockchain development, CKBuilders program participant, and active contributor to CKB developer education
-
Telegram: @Cyborgsil
-
Discord: alchemist_3970
2. Project Background
Context
In April 2026, I published “Your Ethereum Account Doesn’t Exist” as part of my CKBuilders learning journey. The article explains the CKB Cell model by contrasting it with the Ethereum account model and Bitcoin UTXOs framing it specifically for developers who already understand blockchain but are new to CKB.
The article is not for beginners. It is for developers who already know what a smart contract is, who have deployed on Ethereum or Solana, and who need to unlearn the account model before they can understand CKB.
At the CKB Nairobi Community Meetup on July 18, 2026, I spoke with builders from other ecosystems who had read the article. Their feedback was consistent:
“I finally understood what a Cell is after reading this.”
“Your article helped me connect the dots between UTXO and CKB.”
“I had been reading CKB docs for weeks and still didn’t get it until this.”
These were not isolated comments. Multiple developers from Ethereum and Solana backgrounds independently told me the article was what made the Cell model click for them.
The Problem
The official CKB documentation explains what a Cell is - capacity, data, lock script, type script. But it does not systematically explain why this model exists, how it differs from what developers already know, and what that difference enables. New developers must piece this together themselves.
This creates a specific onboarding failure: developers from other ecosystems understand CKB’s potential but cannot translate their existing knowledge into the Cell model. They read the docs, they understand the words, but they cannot think in Cells.
The Spark Program has funded educational projects before, including Cell Sandbox (interactive visual playground for the Cell model) and CKB Builder Lab (interactive developer onboarding with a Cell simulator). Each project addresses a different stage of learning, but none systematically translate the Cell model into the language of developers who already know blockchain. They assume the learner is starting from zero.
What This Project Does
This project extends the article into a complete documentation hub. It does not replace existing CKB documentation. It serves as the on-ramp for developers coming from other ecosystems, the resource that helps them unlearn the account model before they can learn the Cell model.
The format is written documentation with executable code snippets that can be run on a local devnet. It is designed for developers who learn by reading, by contrasting, and by running code.
Why Now
The Nairobi meetup demonstrated that there is an audience of experienced developers who want to build on CKB but need a bridge from what they already know. The Spark Program’s focus on developer onboarding and education aligns with exactly this need.
3. Project Description
Problem Statement
Developers from Ethereum, Solana, and other account-model blockchains struggle to understand CKB’s Cell model because they cannot map their existing knowledge to CKB’s architecture. Existing CKB documentation assumes a mental model that most blockchain developers do not have. This creates a barrier to entry that slows ecosystem growth.
Solution
A complete, structured documentation hub that:
-
Starts from what developers already know (Ethereum accounts, Solana accounts, Bitcoin UTXOs)
-
Maps those concepts to CKB’s Cell model systematically
-
Answers the question every experienced developer asks: “Why would I use this instead of what I already know?”
-
Provides executable code snippets that readers can run on a local devnet
-
Bridges the gap between understanding the model and actually building on it
Target Audience
The primary audience is blockchain developers with experience in other ecosystems (Ethereum, Solana, Bitcoin) who are new to CKB and want to understand the Cell model. Secondary audiences include educators, technical writers, and anyone who needs to explain CKB to other developers.
4. Expected Deliverables
The project will produce the following deliverables:
Documentation Hub: A structured, multi-module documentation site covering the Cell model from first principles. Each module will include code snippets, examples, and explanations. The hub will be published as a static site and as a GitHub repository.
GitHub Repository: A public repository containing all documentation, code examples, and scripts used in the hub. Users can clone the repository and run the examples on their own devnet.
Video Walkthrough: A 5-10 minute video demonstrating the documentation hub and walking through a live code example. This will be published alongside the documentation.
Executable Code Snippets: All code examples in the documentation will be runnable on a local devnet. The repository will include setup scripts to get users started quickly.
5. Required Funding and Budget Breakdown
Total Requested: $1,000 USD
The budget is broken down as follows:
Documentation Writing and Structure: $650
This covers writing and structuring all module content, including research, revision, and formatting. The documentation will be written in clear English with consistent structure across all modules.
Code Example Development and Testing: $250
This covers developing all executable code snippets and testing them on a local devnet. Code will be written in TypeScript using offckb.
Video Walkthrough Production: $100
This covers recording, editing, and publishing the video walkthrough. The video will be concise and focused on demonstrating the documentation hub in action.
Additional contributions will be provided through volunteer effort.
6. Estimated Completion Timeline
Total Duration: 4 weeks
The project is structured for completion within one month, with the following phases:
Week 1: Module structure and outline finalization. Research and content planning. Devnet environment setup.
Week 2: Documentation writing for all modules. Code example development begins.
Week 3: Code example testing and refinement. Documentation review and revision. Video script preparation.
Week 4: Video production. Final polish and formatting. Submission and publication.
7. Clear To-Do List
The following tasks will be completed:
Phase 1: Planning and Setup
-
Finalize module outline and structure
-
Set up documentation repository and framework
-
Configure local devnet environment for code examples
Phase 2: Documentation Writing
-
Write Module 1: The Mental Model Shift (Account vs UTXO vs Cell)
-
Write Module 2: The Cell as a Container (anatomy of a Cell)
-
Write Module 3: Lock Scripts and Ownership
-
Write Module 4: Type Scripts and State Transitions
-
Write Module 5: Building on the Cell Model
-
Develop companion glossary
Phase 3: Code Example Development
-
Write executable code examples for all modules
-
Test all examples on local devnet
-
Document setup and running instructions
Phase 4: Review and Publication
-
Review and revise all content
-
Record and edit video walkthrough
-
Publish documentation hub
-
Submit final deliverables
8. Relevance to the CKB Ecosystem
Meeting Actual Needs: The CKB ecosystem needs better developer onboarding for builders coming from other ecosystems. The Spark Program has funded multiple educational projects, including Cell Sandbox and CKB Builder Lab, which shows the committee values this type of work and recognizes the gap in developer education.
Demonstrated Demand: The feedback from developers at the Nairobi meetup proves there is demand for this type of resource. Multiple developers independently stated that the existing article helped them understand the Cell model in a way that official documentation did not.
Unique Competitive Advantage: This project uses CKB’s technical architecture as a differentiating factor- the Cell model is what makes CKB different, and this project helps developers understand and leverage that difference. It positions CKB as a viable alternative to account-model blockchains for developers who value parallelism, storage rent models, and programmatic ownership.
Complementary, Not Duplicative: Existing educational projects focus on simulation and interactive learning. This project focuses on structured, written documentation with executable code- a different format that serves a different learning style and a different stage of the developer journey.
Long-term Value: The documentation hub will remain a valuable resource for the CKB ecosystem, reducing onboarding friction for years to come. It will be open source and community-maintainable.