Start with the model, not the vocabulary
Most developers arriving at CKB are not starting from zero. They are bringing assumptions from Solana, Ethereum, Sui, or another chain. That background helps, but it also creates confusion when CKB organizes state, ownership, and validation differently. These docs start from that reality. The goal is not to throw isolated definitions at you. The goal is to give you a clean mental model for how CKB works so the rest of the technical material lands faster.Week 1: Solana to CKB
Learn the key shift from account mutation to cell-based state replacement and script verification.
Week 2: Scripts and State Machines
Lock scripts, type scripts, hash locks, debugging by exit code, and a counter as an on-chain state machine.
Week 3: Assets and Composability
xUDT, Spore, Omnilock, composability, and the cell-management discipline that follows from asset-first state.
Week 4: Infrastructure
RPCs, full nodes, and light clients as explicit trust settings rather than invisible defaults.
Week 5: Production Patterns
RGB++, order cells, Spore marketplaces, and mainnet operations as one production story about cells and scripts.
Week 6: Apps Are Cell Graphs
A milestone escrow and launchpad capstone covering protocol blueprints, capacity planning, refunds, indexing, monitoring, and audit readiness.
Week 7: App Integration Layer
Transaction builders, wallet previews, indexer revalidation, and frontend read models around the Week 6 cell graph.
Week 8: Fiber Infrastructure
A personal bridge from seven weeks of CKB learning into Fiber node dashboarding, monitoring, routing diagnostics, and hackathon scope.
Week 9: Source-Backed FiberOps
The first hackathon-build chapter: real FiberOps sources, read-only collectors, diagnostics from evidence, and visible source gaps.
Week 10: Reef on Fiber
The build week where Reef tied Fiber payment failures to routes, channels, peers, CKB funding evidence, CCH limits, and observation history.
Week 11: Replaying Fiber Failure
Incident replay from retained Fiber payment rows: baseline success, routed failure, route autopsy, CKB correlation, and recovery limits.
Week 12: Fiber to CKB Settlement
Follow Fiber channel state back to CKB: funding outpoints, commitment safety, close transactions, finality, and watchtower limits.
Week 13: Force-Close TLC Reconciliation
Reconcile force-closed TLCs with exact identities, CKB proof boundaries, correlation, idempotency, retention, and honest unknowns.
Week 14: Durable Recovery
Carry exact settlement state safely through crashes, schema migrations, backup/restore, and idempotent process restarts.
Week 15: Reestablishment and Resilience
Reconnect channels in order, retry only failed attempts, recover gossip safely, and bound adversarial peer work.
Week 16: Mobile to CKB Settlement
Synthesize tenant-isolated hosted Fiber, typed remote signing, offline TLC delivery, and exact CKB settlement evidence.
Week 17: Hosted LSP Production Readiness
Turn crash safety, semantic signer policy, tenant containment, and honest release classification into executable gates.
Week 18: Exact Force-Close Snapshot
Authenticate the commitment history CKB actually settled and scope preimages to the exact local or forwarded TLC outcome.
Week 19: CKB Release Integrity
Verify v0.210.0 artifacts, chain compatibility, assume-valid checkpoints, staged health, and rollback evidence.
Week 20: Fiber Multi-Address Operations
Carry one authenticated Fiber node identity across multiple configured, bound, advertised, and externally reachable endpoints.
Current focus
The twenty-week learning path moves from the CKB cell-model reset through scripts, assets, infrastructure, production, protocol/application design, Fiber diagnostics, settlement, recovery, hosted-mobile architecture, exact commitment history, release integrity, and multi-address operations. Week 20 separates configured, bound, advertised, reachable, and authenticated network facts. That means the content is intentionally opinionated:- blockchain is treated as a shared state machine
- the
cellis the base state object - transactions replace state instead of mutating it in place
- scripts validate transitions rather than acting like a direct copy of contract-centric execution models
Reading path
If you are new to CKB but not new to blockchains, start here:- Read the Week 1 bridge note.
- Work through the local exercises week by week from
week1/throughweek20/. - Use the docs pages as the conceptual spine and the local scripts as the concrete transaction walkthroughs.