CKB Pulse

All lessons · Developer tooling · Start here · Glossary

Derive devnet Spore and system script cell deps from a fresh OffCKB exportWorkingSeen again

Seen again · Check: partly right · Checked 2026-11-19

Do not hardcode devnet code hashes and cell dep out points (secp256k1, Spore, cluster) in an example: they come from the local OffCKB devnet and can drift when OffCKB's bundled scripts change. Export them with `offckb system-scripts --network devnet --export-style ccc` before start, fail if a needed script lacks codeHash, hashType or a cellDep outPoint, and build both the CCC client config and the Spore SDK lumos config from that one file.

Why it matters: Hardcoded devnet out points and code hashes go stale when the OffCKB devnet changes, so the CCC client and the Spore SDK end up pointing at wrong or missing cell deps and transactions fail.

A test changed in the same commit

It sits next to the fix. We did not run it.

Concepts
Cell deps and script lookup, Testing and devnet
Evidence
Seen again: seen in two or more projects
First seen
2026-09-29
Last changed
2026-09-29
Last checked
2026-11-19
Check against the commit
partly right: a true core, with a part that is loose or too wide

Sources (2)

More about Developer tooling

All 35 in this topic

Do you maintain a project this lesson came from? Confirm or correct it

Cite this lesson
LusoCryptoLabs, "Derive devnet Spore and system script cell deps from a fresh OffCKB export", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/derive-devnet-spore-and-system-script-cell-deps-from-a-fresh, CC BY 4.0, last changed 2026-09-29.

Drawn from public commits and checked against the commit each one came from and the project's code today. Read the source before you rely on one. Text under CC BY 4.0: credit LusoCryptoLabs, CKB lessons, with a link to the lesson. Want a lesson changed or removed? Open an issue.