Spark Program | CKB Developer Onboarding Guide

English
,
1

CKB Developer Onboarding Guide

Lightweight onboarding and developer setup guide for CKB builders

1. Project Overview

CKB Developer Onboarding Guide is a structured, documentation-first onboarding resource designed to help developers successfully set up and start building on the Nervos CKB blockchain from zero.

The project focuses on reducing onboarding friction by providing a clear, step-by-step guide covering environment setup, configuration, first interactions, and troubleshooting.

Many developers entering the CKB ecosystem must configure multiple components such as:

  • Node.js and development tools
  • CKB node
  • RPC endpoints
  • Indexer services
  • configuration files

Misconfiguration or missing dependencies frequently lead to confusion and slow onboarding.

Unlike CLI-based tools, this guide is immediately accessible without requiring any pre-installed tooling, directly addressing the bootstrapping limitation.

The project focuses on:

  • step-by-step onboarding
  • environment setup guidance
  • RPC and indexer configuration
  • troubleshooting and remediation
  • first working developer workflow
  • AI-assisted debugging usage

Target users:

  • new developers onboarding to CKB
  • hackathon participants
  • early-stage builders

The project is a documentation and onboarding resource, not a software tool.

A successful onboarding is defined as the developer being able to execute a valid RPC request and receive a correct response from the CKB network.

This guide does not replace official documentation, but provides a structured, beginner-first path that consolidates fragmented onboarding steps.

2. Team Information

Milan Matejic, GitHub: @Mateja3m

Independent software engineer specializing in developer tooling, SDK development, and open-source infrastructure for Web3 ecosystems.

Relevant experience includes:

  • More than 2 years contributing to the Intersect Member Area (Cardano ecosystem)
  • 18 published npm packages focused on developer tooling and CLI utilities
  • Experience building tooling across Cardano, Solana, Fuel, Starknet, Aptos, and Sui

Previous work includes:

  • developer onboarding tooling
  • validation frameworks
  • SDK integrations
  • CLI developer tools

This background directly supports the creation of structured onboarding and troubleshooting content.

3. Technical Architecture and Interaction Flow

The project is designed as a documentation-first system, not a CLI tool.

Core components:

Documentation Structure

A structured onboarding guide organized into logical modules.

Content Modules

Step-by-step instructions, examples, and troubleshooting scenarios.

Troubleshooting Matrix

A structured mapping of issues → causes → solutions.

AI-Assisted Layer

Optional structured prompts and examples for AI-assisted debugging.

3.1 Developer Interaction Flow

  1. Developer accesses the onboarding guide.
  2. Follows step-by-step setup instructions.
  3. Configures environment (Node.js, CKB node, RPC, indexer).
  4. Executes first working interaction (RPC call or query).
  5. Uses troubleshooting sections if issues occur.
  6. Optionally uses AI-assisted prompts for debugging.

3.2 Core Modules

The guide will include:

Prerequisites

  • system requirements
  • Node.js installation
  • required tools

Environment Setup

  • installing dependencies
  • verifying environment

CKB Node Setup

  • installing and running node
  • verifying node status

RPC and Indexer Setup

  • configuration steps
  • connectivity validation

Configuration Setup

  • example config files
  • validation steps

First Developer Workflow

  • first RPC call
  • querying data
  • basic interaction with CKB

Common Errors and Remediation

  • categorized issues
  • causes and fixes

Troubleshooting Matrix

  • issue → cause → solution

AI-Assisted Debugging

  • structured prompts
  • how to use AI tools effectively

Quick Start Path

  • minimal steps to first success without local node
  • use of public RPC endpoint
  • copy-paste commands
  • expected output examples

CKB Mental Model

  • high-level architecture overview (node, RPC, indexer)
  • explanation of how components interact
  • basic explanation of the cell model

Common Misconceptions

  • RPC working does not mean indexer is working
  • node sync state affects query results
  • incorrect network configuration leads to silent failures

4. Project Milestones (5 Weeks)

Milestone 1 (Weeks 1-2)

  • define structure
  • create prerequisites and setup sections
  • draft node and RPC setup

Deliverables:

  • initial documentation structure
  • environment setup guide

Milestone 2 (Weeks 3-4)

  • develop troubleshooting sections
  • create remediation content
  • build first workflow guide
  • add AI-assisted debugging section

Deliverables:

  • troubleshooting matrix
  • remediation guide
  • workflow examples

Milestone 3 (Week 5)

  • finalize documentation
  • translate to Chinese
  • publish repository

Deliverables:

  • full guide (EN + CN)
  • public repository

5. Budget: $1,000

Total requested budget: $1,000

Payment structure:

  • 50% in CKB
  • 50% in USD-denominated stable asset (e.g. USDI equivalent)

Allocation:

  • research and writing - $700
  • bilingual translation - $200
  • docs and publishing - $100

6. Core Deliverables

6.1 Documentation Repository

A public GitHub repository containing:

  • full onboarding guide
  • structured modules
  • troubleshooting content

6.2 Bilingual Guide

  • English version
  • Chinese translation

6.3 Troubleshooting Matrix

  • structured issue mapping
  • quick lookup format

6.4 Example Configurations

  • ready-to-use examples
  • validation steps

6.5 Known Limitations

  • focused on onboarding, not advanced topics
  • does not replace full documentation
  • no automation tools included

6.6 Remediation Guidance

Each issue includes:

  • explanation of cause
  • step-by-step fix
  • example commands with expected outputs

Example:

FAIL RPC endpoint unreachable

Possible causes:

  • node not running
  • incorrect port
  • network issue

Suggested fix:

  • run ckb run
  • verify port (8114)
  • check configuration

6.7 AI-Friendly Support

The guide includes:

  • structured prompts
  • troubleshooting examples
  • AI usage instructions

No external AI integration is required.

7. Relevance to the CKB Ecosystem

This project improves onboarding by:

  • reducing setup friction
  • providing structured guidance
  • enabling faster first success
  • supporting AI-assisted workflows

The guide reduces trial-and-error during onboarding and provides deterministic steps toward a successful initial setup.

8. How to Verify

The deliverables can be verified using the following criteria:

  • All commands in the Quick Start Path can be executed on the CKB testnet and produce the outputs described in the guide

  • A developer with no prior CKB experience can follow the guide and successfully perform a first RPC call

  • Each entry in the Troubleshooting Matrix includes:

    • root cause
    • fix steps
    • reproducible commands

  • Configuration examples (RPC, indexer) are tested and confirmed to work

  • The guide is publicly accessible and structured according to the defined modules

9. Current State vs Funded Work

Current State

  • Prerequisites Module
    High-level outline defined; installation steps and commands not yet documented or validated

  • Quick Start Path
    Flow structure defined; commands identified but not tested on CKB testnet

  • Troubleshooting Matrix
    Common issue categories identified; no documented solutions or reproducible examples

  • Common Misconceptions
    Key topics identified; explanations and examples not yet written

  • Configuration Setup (RPC, Indexer)
    Structure planned; configuration examples not yet validated in real environment

Final State at Project Completion

  • Prerequisites Module
    Complete setup guide including:

    • verified installation steps
    • tested commands
    • expected outputs for each step

  • Quick Start Path
    Step-by-step onboarding flow where:

    • all commands are tested on CKB testnet
    • expected outputs are documented
    • a developer with no prior CKB experience can complete their first RPC call within 30 minutes

  • Troubleshooting Matrix
    Covers common onboarding issues across key categories:

    • root cause explanation
    • step-by-step resolution
    • reproducible commands
    • expected outputs

  • Common Misconceptions
    Documented explanations for common developer mistakes, including:

    • incorrect assumptions
    • why they occur
    • correct approach with examples

  • Configuration Setup (RPC, Indexer)
    Fully validated configuration examples including:

    • working RPC endpoints
    • indexer setup
    • tested configuration files
    • example requests and responses

10. CKB-Specific Relevance

The guide focuses on:

  • CKB node setup
  • RPC interaction
  • indexer usage
  • cell model basics
  • development workflow

11. Web5 Alignment

Supports:

  • open infrastructure
  • developer accessibility
  • decentralized ecosystem growth

12. AI-Assisted Developer Experience

The guide enhances AI usage by:

  • providing structured context
  • enabling better prompts
  • improving troubleshooting accuracy

CKB 开发者入门指南

面向 CKB 开发者的轻量级入门与环境搭建指南

1. 项目概述

CKB 开发者入门指南 是一个以文档为核心的结构化入门资源，旨在帮助开发者从零开始完成 Nervos CKB 区块链的环境搭建并顺利开始开发。

该项目通过提供清晰的分步骤指导，降低开发者在环境配置、初始交互和问题排查过程中的复杂性。

进入 CKB 生态的开发者通常需要配置多个组件，例如：

  • Node.js 和开发工具
  • CKB 节点
  • RPC 端点
  • Indexer 服务
  • 配置文件

配置错误或依赖缺失通常会导致困惑并延缓上手过程。

与 CLI 工具不同，该指南无需任何预安装环境即可访问，从根本上解决了启动依赖（bootstrapping）问题。

本项目重点包括：

  • 分步骤入门流程
  • 环境配置指导
  • RPC 与 Indexer 配置
  • 故障排查与修复
  • 第一个可运行的开发流程
  • AI 辅助调试使用方法

目标用户：

  • 新加入 CKB 的开发者
  • 黑客松参与者
  • 早期阶段构建者

本项目是一个文档与入门资源，而非软件工具。

成功的入门定义为：开发者能够执行一个有效的 RPC 请求，并从 CKB 网络获得正确响应。

本指南不会替代官方文档，而是提供一个面向初学者的结构化路径，将分散的信息整合为统一的入门流程。

2. 团队信息

Milan Matejic，GitHub: @Mateja3m

独立软件工程师，专注于开发者工具、SDK 开发以及 Web3 生态的开源基础设施。

相关经验包括：

  • 在 Intersect Member Area（Cardano 生态）贡献超过 2 年
  • 发布了 18 个 npm 包，专注于开发者工具和 CLI 工具
  • 在 Cardano、Solana、Fuel、Starknet、Aptos 和 Sui 等生态中开发工具

过往工作包括：

  • 开发者入门工具
  • 验证框架
  • SDK 集成
  • CLI 开发工具

这些经验直接支持结构化入门与故障排查内容的构建。

3. 技术结构与交互流程

本项目采用文档优先（documentation-first）架构，而非 CLI 工具。

核心组件：

文档结构

按逻辑模块组织的结构化入门指南

内容模块

包含分步骤说明、示例和故障排查场景

故障排查矩阵

问题 → 原因 → 解决方案 的结构化映射

AI 辅助层

提供结构化提示与 AI 调试示例

3.1 开发者交互流程

  1. 开发者访问入门指南
  2. 按步骤完成环境配置
  3. 配置环境（Node.js、CKB 节点、RPC、Indexer）
  4. 执行第一个成功的交互（RPC 请求或查询）
  5. 出现问题时使用排查指南
  6. 可选使用 AI 提示进行调试

3.2 核心模块

指南将包括：

前置条件

  • 系统要求
  • Node.js 安装
  • 必需工具

环境配置

  • 安装依赖
  • 验证环境

CKB 节点配置

  • 节点安装与运行
  • 状态验证

RPC 与 Indexer 配置

  • 配置步骤
  • 连通性验证

配置文件设置

  • 示例配置
  • 验证步骤

第一个开发流程

  • 第一个 RPC 请求
  • 数据查询
  • 基础交互

常见错误与修复

  • 分类问题
  • 原因与解决方法

故障排查矩阵

  • 问题 → 原因 → 解决方案

AI 辅助调试

  • 结构化提示
  • AI 使用方法

快速启动路径

  • 无需本地节点的最小步骤
  • 使用公共 RPC
  • 可复制粘贴的命令
  • 预期输出示例

CKB 心智模型

  • 高层架构说明（节点、RPC、Indexer）
  • 组件交互方式
  • Cell 模型基础说明

常见误区

  • RPC 正常不代表 Indexer 正常
  • 节点同步状态影响查询结果
  • 错误网络配置会导致静默失败

4. 项目里程碑（5 周）

里程碑 1（第 1–2 周）

  • 定义结构
  • 编写前置条件与环境配置
  • 初步节点与 RPC 文档

交付内容：

  • 初始文档结构
  • 环境配置指南

里程碑 2（第 3–4 周）

  • 完成故障排查模块
  • 编写修复指南
  • 完成首个开发流程
  • 添加 AI 调试部分

交付内容：

  • 故障排查矩阵
  • 修复指南
  • 工作流程示例

里程碑 3（第 5 周）

  • 完成文档
  • 翻译为中文
  • 发布仓库

交付内容：

  • 完整指南（中英文）
  • 公共仓库

5. 预算：$1,000

总预算：$1,000

支付方式：

  • 50% CKB
  • 50% 稳定资产（如 USDI 等）

预算分配：

  • 研究与撰写：$700
  • 双语翻译：$200
  • 文档整理与发布：$100

6. 核心交付

6.1 文档仓库

包含：

  • 完整指南
  • 模块结构
  • 故障排查内容

6.2 双语指南

  • 英文版本
  • 中文版本

6.3 故障排查矩阵

  • 结构化问题映射
  • 快速查询

6.4 示例配置

  • 可直接使用的配置
  • 验证步骤

6.5 已知限制

  • 仅聚焦入门，不覆盖高级内容
  • 不替代官方文档
  • 不包含自动化工具

6.6 修复指导

每个问题包含：

  • 原因说明
  • 分步骤解决方法
  • 带预期输出的命令

示例：

RPC 端点不可达

可能原因：

  • 节点未运行
  • 端口错误
  • 网络问题

解决方法：

  • 运行 ckb run
  • 检查端口（8114）
  • 检查配置

6.7 AI 支持

包括：

  • 结构化提示
  • 故障排查示例
  • AI 使用方法

无需集成外部 AI

7. 与 CKB 生态的相关性

本项目通过以下方式改进入门体验：

  • 降低配置难度
  • 提供结构化指导
  • 加快首次成功
  • 支持 AI 调试流程

该指南减少试错过程，并提供确定性的入门路径。

8. 验证方式

交付成果可通过以下标准进行验证：

  • 快速入门路径（Quick Start Path）中的所有命令均可在 CKB 测试网上执行，并产生与文档描述一致的输出

  • 无任何 CKB 经验的开发者可以按照指南成功完成首次 RPC 调用

  • 故障排查矩阵（Troubleshooting Matrix）中的每个条目均包含：

    • 根本原因说明
    • 修复步骤
    • 可复现的命令

  • 配置示例（RPC、Indexer）已测试并确认可正常运行

  • 指南已公开发布，并按照既定模块结构组织

9. 当前状态与资助内容

当前状态

  • 前置条件模块（Prerequisites Module）
    已定义高层结构；安装步骤和相关命令尚未编写或验证

  • 快速入门路径（Quick Start Path）
    流程结构已确定；相关命令已识别，但尚未在 CKB 测试网上验证

  • 故障排查矩阵（Troubleshooting Matrix）
    常见问题类别已识别；尚未提供解决方案或可复现示例

  • 常见误区（Common Misconceptions）
    关键主题已确定；解释和示例尚未编写

  • 配置设置（RPC、Indexer）
    结构已规划；配置示例尚未在真实环境中验证

项目完成时的最终状态

  • 前置条件模块（Prerequisites Module）
    完整的环境搭建指南，包括：

    • 已验证的安装步骤
    • 已测试的命令
    • 每一步的预期输出

  • 快速入门路径（Quick Start Path）
    分步骤的上手流程，包括：

    • 所有命令已在 CKB 测试网上验证
    • 所有步骤均提供预期输出说明
    • 无任何 CKB 经验的开发者可在 30 分钟内完成首次 RPC 调用

  • 故障排查矩阵（Troubleshooting Matrix）
    覆盖关键类别中的常见上手问题，包括：

    • 问题根因说明
    • 分步骤解决方案
    • 可复现的命令示例
    • 预期输出

  • 常见误区（Common Misconceptions）
    针对开发者常见错误提供说明，包括：

    • 错误认知
    • 产生原因
    • 正确方法及示例

  • 配置设置（RPC、Indexer）
    完整验证的配置示例，包括：

    • 可用的 RPC 端点
    • indexer 配置
    • 已测试的配置文件
    • 示例请求与响应

10. CKB 相关性

重点包括：

  • 节点配置
  • RPC 使用
  • Indexer 使用
  • Cell 模型
  • 开发流程

11. Web5 对齐

支持：

  • 开放基础设施
  • 开发者可访问性
  • 去中心化生态增长

12. AI 开发体验

通过以下方式增强 AI 使用：

  • 提供结构化上下文
  • 提供更优提示
  • 提高调试准确性

3 Likes
2

Hi @Mateja3m,

Glad to see your new proposal. The content direction looks good, and the module design in Section 3.2 shows good research (Quick Start Path with public RPC, Common Misconceptions, Troubleshooting Matrix, etc.).

Before bringing it to the committee, I’d suggest improving Sections 8 and 9 using the same approach that worked well in your previous proposal.

Section 9 (Current State vs Funded Work)

Right now it reads: “research completed, structure defined” vs “full guide creation.” This is too general for the committee to evaluate the scope.

You already have a detailed module list in Section 3.2. I’d suggest restructuring Section 9 around those modules, for example:

Current state:

  • Prerequisites module: outline completed, content not yet written
  • Quick Start Path: structure defined, commands not yet tested
  • Troubleshooting Matrix: issue categories identified, solutions not yet drafted
  • etc…

Final state at project closure:

  • Prerequisites module: complete guide with verified commands and expected outputs
  • Quick Start Path: a developer with no CKB experience can complete first RPC call within 30 minutes following the guide
  • Troubleshooting Matrix: covers X categories, each with cause/solution/example commands
  • …

This way the committee can see exactly what each module delivers and what “done” looks like.

Section 8 (How to Verify)

The current four lines are goals, not verification steps. For a documentation project, verification could focus on the deliverables themselves being checkable, for example:

  • Every command in the Quick Start Path can be executed against CKB testnet and produces the output documented in the guide
  • Every entry in the Troubleshooting Matrix includes cause, fix steps, and example commands that are reproducible
  • etc…

These two changes will make the proposal much easier for the committee to evaluate.

Looking forward to your revision!

很高兴看到新提案。内容方向很好，3.2 节的模块设计能看出做了认真的调研（Quick Start Path 用公共 RPC、Common Misconceptions、Troubleshooting Matrix 等）。

在提交委员会评审之前，建议用上一版提案中效果很好的方法来改进第 8 节和第 9 节。

第 9 节（当前状态 vs 资助范围）

目前的写法是“research completed, structure defined”对“full guide creation”，太笼统了，委员会无法评估具体范围。

你在 3.2 节已经有了详细的模块列表。建议围绕这些模块来重组第 9 节，例如：

当前状态：

  • Prerequisites 模块：大纲已完成，内容未写
  • Quick Start Path：结构已定，命令未经测试
  • Troubleshooting Matrix：问题分类已确定，解决方案未起草
  • …

结项时的最终状态：

  • Prerequisites 模块：完整指南，命令已验证，附有预期输出
  • Quick Start Path：没有 CKB 经验的开发者照着走，能在30分钟内完成第一次 RPC 调用
  • Troubleshooting Matrix：覆盖 X 个问题类别，每个都有原因/解决方案/示例命令
  • …

这样委员会就能清楚看到每个模块交付什么、什么算完成。

第 8 节（验收方式）

目前的四句话是项目目标，不是验收步骤。文档项目的验收应该关注交付物本身是否可检查，例如：

  • Quick Start Path 中的每条命令都能在 CKB testnet 上实际执行，产出与文档描述一致的结果
  • Troubleshooting Matrix 中的每个条目都包含原因、修复步骤和可复现的示例命令
  • 。。。

这两个调整会让委员会评估起来顺畅很多。

期待您的修改！

3 Likes
3

Hi @zz_tovarishch

Thank you for the detailed and very helpful feedback.

I’ve updated Sections 8 and 9 to make the scope and deliverables more explicit and aligned with the module structure from Section 3.2.

Thanks again

Hi @zz_tovarishch，

感谢您提供的详细且非常有帮助的反馈。

我已经更新了第 8 节和第 9 节，使项目范围和交付内容更加清晰，并与第 3.2 节的模块结构保持一致。

再次感谢

3 Likes
4

Hi @Mateja3m ,

Thank you for the updates to Sections 8 and 9. Before moving into formal committee review, there are two follow-up questions we’d like you to address:

  1. CKB development experience

For documentation projects, first-hand knowledge of real development workflows is critical to ensuring the guide’s accuracy and usefulness. Therefore the committee would like to know whether you have practical development experience on CKB. If your CKB experience is limited, please state that candidly — we are willing to share relevant experience with you.

  1. Confirmation of content scope

As a supplement to the first point, the current module list focuses on environment setup, node/RPC/Indexer configuration, and basic RPC calls. The committee would like to know whether the guide will also cover subsequent practical development topics, such as:

  • Contract development (for example, writing, compiling, and deploying a simple on-chain script)
  • CCC SDK integration (for example, using the CCC SDK to construct, sign, and submit transactions)
  • Configuration checks beyond basic connectivity (for example, verifying that the development environment fully meets the requirements for contract deployment)

If any part of this content is intentionally excluded from the current scope, please state that explicitly so the committee can assess whether the guidelines cover enough to support a meaningful onboarding experience.

Looking forward to your reply.

嗨 @Mateja3m ，

感谢你对第 8 和第 9 节的更新。在进入正式委员会评审之前，有两个跟进问题希望你能补充：

1. CKB 开发经验

对于文档类项目而言，对真实开发流程的第一手了解对确保指南的准确性和实用性至关重要。因此委员会希望能了解你是否具备 CKB 的实际开发经验，如果你的 CKB 经验有限，请坦诚说明，我们愿意与你分享相关经验。

2. 内容覆盖范围确认

作为第一点的补充，目前的模块列表聚焦于环境搭建、节点/RPC/Indexer 配置和基础 RPC 调用。委员会希望了解指南是否还会涵盖后续实际开发内容，比如：

  • 合约开发（例如编写、编译和部署一个简单的链上脚本）
  • CCC SDK 集成（例如使用 CCC SDK 进行交易构建、签名和提交）
  • 超越基础连通性的配置检查（例如验证开发环境是否完全具备合约部署条件）

如果其中部分内容有意不在本次范围内，请明确说明，以便委员会评估指南的覆盖面是否足以支撑一个有意义的入门体验。

期待你的回复。

Best regards，
xingtian
On behalf of the Spark Program Committee

2 Likes
5

Hi @xingtianchunyan

Thank you for the thoughtful follow-up questions.

  1. CKB Development Experience

My direct hands-on experience with CKB is currently at an early stage, and I want to state that transparently.

However, my background is focused on developer onboarding, diagnostics, and tooling across multiple ecosystems (Cardano, Solana, Aptos, Sui, Arbitrum, Flow etc.), where the main challenge is reducing onboarding friction and making first success deterministic.

For this project, I will approach the guide in a practical, validation-first way:

  • all commands and steps will be tested directly on CKB testnet
  • expected outputs will be verified and documented
  • common failure cases will be reproduced and included in the troubleshooting matrix

Additionally, the guide will be closely aligned with official CKB documentation and iteratively validated against real development workflows, ensuring accuracy despite my initial stage of direct CKB experience.

I’m also open to incorporating feedback and best practices from the CKB ecosystem to ensure accuracy.

  1. Confirmation of Content Scope

The current proposal is intentionally focused on onboarding and early-stage developer setup, not full application development.

Included in scope:

  • environment setup
  • node / RPC / indexer configuration
  • first working RPC interaction
  • troubleshooting and remediation
  • common misconceptions and configuration validation

Explicitly out of scope for this phase:

  • contract development (writing, compiling, deploying scripts)
  • CCC SDK integration
  • advanced deployment readiness validation beyond basic environment correctness

This scope is intentionally designed to address the highest-friction part of onboarding, which is environment setup and achieving the first successful interaction.

Based on experience across multiple ecosystems, this stage is where most developers drop off, and improving this step has the highest impact on developer adoption.

The goal of this guide is to reduce time-to-first-success and provide a reliable starting point for new developers.

Once a developer successfully reaches this stage, they can continue with official documentation or more advanced guides.

If needed, this project could be extended in a future phase to cover contract development and SDK usage.

Looking forward to your feedback.

Hi @xingtianchunyan

感谢您提出的这些深入且有价值的后续问题。

  1. CKB 开发经验

我目前在 CKB 上的直接实践经验仍处于早期阶段，这一点我希望坦诚说明。

不过，我的背景主要集中在多个区块链生态（Cardano、Solana、Aptos、Sui、Arbitrum、Flow 等）的开发者入门、诊断工具和开发者工具领域，其中核心问题始终是降低上手门槛，并让开发者能够以确定性的方式完成首次成功。

在本项目中，我将采用以实践验证为核心的方法来构建指南：

  • 所有命令和步骤都会在 CKB 测试网上进行实际验证
  • 所有预期输出都会被确认并记录
  • 常见失败场景会被复现并纳入故障排查矩阵

此外，该指南将严格对齐 CKB 官方文档，并基于真实开发流程进行迭代验证，从而在我当前 CKB 经验阶段的基础上依然保证内容的准确性。

我也非常愿意结合 CKB 社区的反馈和最佳实践，持续优化内容质量。

  1. 内容范围确认

当前提案刻意聚焦于开发者入门和早期环境搭建阶段，而不是完整的应用开发流程。

本阶段包含的内容：

  • 开发环境搭建
  • 节点 / RPC / Indexer 配置
  • 首次可用的 RPC 交互
  • 故障排查与修复指南
  • 常见误区与配置验证

本阶段明确不包含：

  • 合约开发（编写、编译、部署脚本）
  • CCC SDK 集成
  • 超出基础环境正确性验证范围的高级部署检查

该范围是有意设计的，重点解决开发者入门过程中摩擦最大的阶段，即环境搭建和首次成功交互。

根据我在多个生态中的经验，这一阶段是开发者最容易流失的环节，而优化这一过程对开发者增长具有最大影响。

本指南的目标是缩短“首次成功时间”（time-to-first-success），为新开发者提供一个可靠的起点。

一旦开发者完成这一阶段，他们可以继续使用官方文档或更高级的开发指南深入学习。

如有需要，该项目也可以在后续阶段扩展，涵盖合约开发和 SDK 使用等内容。

期待您的进一步反馈。

1 Like