CKB Pulse

All lessons · Developer tooling · Start here · Glossary

Release asset names differ per CKB toolWorkingFrom one fix

From one fix · Check: partly right · Checked 2026-11-19

ckb, ckb-cli and ckb-debugger use `<tool>_<tag>_<triple>[-portable].<ext>`, while fnn and ckb-light-client use `<tool>_<tag>-<arch>-<os>[-portable].tar.gz`. ckb-debugger ships .tar.gz on every OS with a `<stem>-sha256.txt` and has no x86_64 macOS build, and ckb-cli ships .zip on macOS and Windows with no sums file. Try an ordered list of candidate names, including portable variants, against the release's actual asset list.

Why it matters: A single fixed asset name returns nothing for fnn, ckb-light-client, zip-packaged ckb or ckb-cli, and portable-only builds, so the installer fails even though a usable binary is published.

Concepts
Other
Evidence
From one fix: from one project, checked against its commit
First seen
2026-11-11
Last changed
2026-11-14
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, "Release asset names differ per CKB tool", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/release-asset-names-differ-per-ckb-tool, CC BY 4.0, last changed 2026-11-14.

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.