CKB DevLaunch Kit

DAOs & Funding Spark Program
,
1

CKB DevLaunch Kit

Project Overview

CKB DevLaunch Kit is an open-source developer onboarding toolkit designed to simplify the process of building on Nervos CKB by transforming existing ecosystem resources into structured, beginner-friendly development templates.

The project will integrate existing CKB resources such as official CKB examples, Spore SDK resources, and community tutorials into practical starter kits that help developers understand the Cell Model, build applications, deploy contracts, and move from learning to production faster.

Team Information

The project is led by Gerald Hemstone Otieno (CryptoHead) , a blockchain developer and ecosystem contributor focused on developer education, Web3 tooling, and blockchain adoption.

The team has experience building and documenting blockchain applications across ecosystems including CKB, Stacks, Arbitrum, and other EVM-based networks. Previous work includes developer-focused resources, blockchain application prototypes, and ecosystem onboarding initiatives.

The team’s focus is creating accessible educational resources that reduce technical barriers for developers entering emerging blockchain ecosystems.

Problem Statement

While Nervos CKB provides a powerful and flexible architecture, new developers often face challenges when starting because:

  • The Cell Model differs significantly from account-based blockchain models.
  • Existing examples are distributed across multiple repositories and resources.
  • Developers lack structured beginner-to-intermediate learning paths.
  • Setting up development environments and deployment workflows can be challenging.

This creates friction for developers who want to experiment and build applications on CKB.

Proposed Solution

The CKB DevLaunch Kit will organize existing ecosystem resources into reusable starter templates with clear documentation, deployment workflows, and practical examples.

The toolkit will focus on solving specific onboarding challenges:

1. Understanding CKB Fundamentals

Provide examples that demonstrate:

  • Cell Model concepts
  • Transaction structure
  • Capacity management
  • Script interaction

2. Building Practical Applications

The initial templates will include:

xUDT Token Template

Based on the established xUDT standard.

Deliverables:

  • Complete example repository
  • Token issuance workflow
  • Minting and transferring functionality
  • Deployment instructions

NFT Template (Spore/DOB)

Based on the Spore ecosystem standards.

Deliverables:

  • NFT creation example
  • Metadata handling
  • Minting workflow
  • Testnet deployment guide

Payment/Escrow Template

Deliverables:

  • Simple contract interaction example
  • Transaction flow explanation
  • Frontend integration example

Deliverables

1. Starter Templates

Format:

  • Public GitHub repositories
  • Complete source code
  • README documentation
  • Environment configuration files

Repository structure:

ckb-devlaunch-kit/

├── xudt-template/
│   ├── contracts/
│   ├── scripts/
│   ├── frontend/
│   └── README.md

├── spore-nft-template/
│   ├── contracts/
│   ├── examples/
│   ├── deployment/
│   └── README.md

└── payment-template/
    ├── contracts/
    ├── frontend/
    ├── tests/
    └── README.md

2. Deployment Scripts

Deliverables:

  • Automated environment setup
  • Testnet deployment scripts
  • Configuration examples
  • Deployment documentation

Developers should be able to clone the repository and deploy examples with minimal setup.

3. Documentation

Deliverables:

  • Beginner setup guide
  • CKB development workflow explanation
  • Cell Model introduction
  • Contract interaction tutorials
  • Troubleshooting guide

Documentation format:

  • Markdown documentation
  • GitHub README files
  • Short tutorial videos

Verification Methods

The community and committee will be able to verify the project through:

  • Public GitHub repositories
  • Working CKB testnet deployments
  • Automated tests demonstrating functionality
  • Demo videos showing:
    • Environment setup
    • Contract deployment
    • Token/NFT creation
    • Application interaction

All examples will include reproducible instructions so developers can independently verify functionality.

Timeline

Duration: 6 Weeks

Milestone 1 – Research, Setup & Initial Templates

Budget: $250

Deliverables:

  • Repository setup
  • Integration of existing CKB resources
  • xUDT starter template
  • Development environment setup

Completion: Week 2

Milestone 2 – Templates Development & Documentation

Budget: $450

Deliverables:

  • Spore NFT template
  • Payment/Escrow template
  • Deployment scripts
  • Developer documentation

Completion: Week 5

Milestone 3 – Testing & Public Release

Budget: $250

Deliverables:

  • Automated testing
  • Testnet deployments
  • Demo videos
  • Public release announcement

Completion: Week 6

Budget Breakdown

Category Amount
Development & Template Creation $550
Documentation & Tutorials $150
Testing & Quality Assurance $100
Project Management & Maintenance $150
Total $950

Maintenance & Long-Term Commitment

The toolkit will be maintained as CKB evolves.

Maintenance activities include:

  • Updating dependencies when CKB tooling changes
  • Updating templates according to ecosystem standards
  • Fixing reported issues
  • Accepting community contributions

All examples will follow recommended CKB practices and leverage established standards such as xUDT and Spore rather than introducing experimental patterns.

Success Metrics

The project will measure success through:

  • 3 complete developer templates released
  • Public GitHub repository available
  • 50+ developers accessing resources
  • Successful testnet deployments
  • Community feedback and contributions

Conclusion

CKB DevLaunch Kit will provide a practical entry point for developers by transforming existing CKB resources into structured, reusable templates. By combining official examples, community knowledge, and clear deployment workflows, the project will reduce onboarding friction and encourage more developers to build within the Nervos ecosystem.

2 Likes
CKB Ecosystem Biweekly Update
CKB Ecosystem Biweekly Update
2

Hey, @CrptoHead,

I’m glad to see you’re interested in the Spark program!

Before submitting this document to the committee for review, I have set out some of my personal views below for your reference. These views reflect only my personal understanding of the document and do not represent the committee’s position.

  1. Proposal Formatting: I see that you have made an effort to follow the proposal template, but several key pieces of information are still missing.
  • Please provide at least some information about your team. If the committee has no idea who you and your team are, it will be difficult for them to decide whether to allocate valuable community resources to you.

  1. Scope and Priorities: Since this toolkit is an integration of existing work, I believe both the committee and the community would like to understand how it integrates existing resources (such as the official CKB examples, the Spore SDK, or community tutorials), and what specific problems in which specific scenarios this integration is designed to solve.

  2. Clarification of Deliverables: The deliverables are listed as “Getting Started Templates,” “Deployment Scripts,” and “Documentation.” To clarify the acceptance criteria, please specify exactly what each template will contain (including the format of the deliverables). Providing a detailed outline of the codebase structure will help the review committee understand the expected output.

  3. Verification Method: How can the committee or community verify, through non-code review methods, that these templates function as intended? Please consider providing a link to a working testnet deployment, a recorded demonstration video, or working automated tests to confirm their functionality. Ideally, a low-cost and repeatable verification method should be used.

  4. Budget Explanation: The post mentions a total budget of $950, but the budget breakdown is as follows: development ($550), documentation ($15), testing ($100), and administration ($150). Please clarify the correct total amount.

  5. Relevance to CKB: This project is directly related to the onboarding efforts of CKB developers. Please confirm that these templates are based on the latest CKB mainnet/testnet versions and specify whether they will be continuously maintained as CKB evolves. Additionally, please ensure that the examples adhere to rigorously audited standards (such as xUDT and Spore) to promote best practices.

Please make your changes and reply to this post.

Sincerely,
xingtian

3

Hi @xingtian,

Thank you for taking the time to review my proposal and for providing such detailed feedback. I appreciate your suggestions and have addressed each point below.

  1. Team Information

The project will be developed by a small team with experience building developer tooling, documentation, and open-source projects.

Team

Cypto head (Project Lead & Developer):Responsible for project architecture, template development, documentation, testing, and overall project coordination. I have experience preparing developer tooling and educational resources for multiple blockchain ecosystems.
Technical Reviewer (Part-time):Will review templates, verify deployment scripts, and ensure alignment with current CKB development standards.
Community Tester:Will validate the onboarding experience from a new developer’s perspective and provide feedback before release.

The DevLaunch Kit is not creating new protocols or smart contract standards. Instead, it packages existing, officially recommended CKB resources into a beginner-friendly toolkit.

The project will integrate resources including:

  • Official CKB example repositories
  • Official xUDT examples
  • Spore SDK examples
  • Lumos/CCC SDK tooling where appropriate
  • Existing community documentation and tutorials

The primary goal is to solve the common onboarding challenge where developers must navigate multiple repositories and documentation sources before deploying their first application.

The toolkit consolidates these resources into a consistent project structure with unified setup instructions, deployment scripts, and practical examples.

  1. Deliverables (Detailed)

The repository will follow a structure similar to:

ckb-devlaunch-kit/
│
├── templates/
│   ├── xudt-token/
│   ├── spore-nft/
│   └── payment-escrow/
│
├── scripts/
│   ├── setup.sh
│   ├── deploy-testnet.sh
│   └── verify.sh
│
├── docs/
│   ├── getting-started.md
│   ├── cell-model.md
│   ├── deployment-guide.md
│   └── troubleshooting.md
│
├── tests/
│
└── README.md

Each starter template will include:

  • Complete source code
  • Project configuration
  • Build instructions
  • Deployment scripts
  • Example transactions
  • Test cases
  • README documentation
  1. Verification Method

To make verification simple and repeatable, the project will provide:

  • Public GitHub repository
  • Automated test suite
  • Successful CI test results
  • Testnet deployment links/transaction hashes
  • Recorded walkthrough demonstrating setup and deployment of each template

This allows both the committee and community members to verify functionality without conducting a detailed code review.

Thank you for pointing out the calculation error.

The correct budget breakdown is:

Category Amount

Development $550
Documentation $150
Testing & QA $100
Project Management $150
Total $950

The documentation budget was mistakenly written as $15 instead of $150.

Relevance to CKB

Yes.

The toolkit will target the latest supported CKB testnet and mainnet tooling available during development.

The starter templates will be based on officially recommended implementations, including audited standards such as xUDT and Spore, following current CKB best practices.

The repository will remain open source under the MIT License, and I intend to maintain it with updates for future CKB releases where required. Community contributions will also be encouraged through documented contribution guidelines.

Thank you again for your constructive feedback. I will update the proposal to incorporate these clarifications before it proceeds to committee review. I appreciate your time and suggestions.

1 Like
4

Hi @CrptoHead ,

I’m very sorry—I missed your message last week due to my oversight.

Please integrate the changes into the main proposal post; both the committee and the community will view the latest content directly from the main proposal post.

Once you’ve integrated the changes into the main post, please @ me and I will submit the proposal to the committee for formal approval as soon as possible.

Best,
xingtian

5

hello @xingtianchunyan The changes have been intergrated as requested.
Regards
Cryptogead

1 Like
6

Hi @CrptoHead,

Thank you for taking the time to prepare and submit your proposal for the CKB DevLaunch Kit to the Spark Program.

After careful review and discussion, the committee regrets to reject the proposal at this time.

We want to be transparent about the reasoning behind this decision:

  1. Misunderstanding of CKB fundamentals:
    The proposal references deploying contracts, but CKB transactions do not require contract deployment in the traditional sense. This indicates a need for deeper familiarity with CKB’s core concepts, which is essential for creating accurate and reliable educational resources.

  2. Insufficient identity information:
    The proposal does not provide clear and verifiable identity details for the project lead. This makes it challenging for the committee to assess the proposer’s background and credibility, which is important for trust and accountability.

  3. Lack of key educational project requirements:
    The Spark Program places high importance on educational projects that combine firsthand experience of new developers with quality assurance from seasoned community members. The current proposal does not demonstrate these elements, making it difficult for the committee to ensure the quality and relevance of the deliverables.

Thank you very much for all the hard work your team has put in. Keep building, and feel free to reach out anytime!

Best,
xingtian
On behalf of the Spark Program Committee