Ecosystem gaps, uncatalogued.
CKB has powerful primitives — the Cell model, Spore/DOB, RGB++, Fiber — but the gaps between them aren't sorted, specced, or claimable.
dir is an open registry of CKB-native project ideas. Wish for them. Claim them. Stake on them. Ship them — on-chain.
CKB has powerful primitives — the Cell model, Spore/DOB, RGB++, Fiber — but the gaps between them aren't sorted, specced, or claimable.
Each idea carries a spec, CKB properties, difficulty, and acceptance criteria — the exact bar a build must clear to count as shipped.
Claim an idea publicly on-chain, optionally stake CKB to hold it exclusively, then ship against the criteria to release the bounty.
Open the catalog. 30+ ideas, mapped by CKB property.
Signal demand. The loudest ideas surface to the top.
Make it public, on-chain. Optionally stake CKB to claim exclusively.
Ship to a deadline. Lapse and the stake routes to the next builder.
A curator confirms acceptance criteria. The bounty releases.
Reputation compounds — across categories, properties, seasons.
Verifiable credentials — course completions, event attendance, skill certs, employment history — issued as Spore DOBs organized in Clusters. Fully on-chain and owned by the holder, each credential is backed by locked CKB the holder can reclaim by melting. Zero transfer fees mean credentials move freely between wallets and apps.
Share a CKB transaction as a clickable URL. One click to tip a creator, mint a DOB, attest a credential, or pay an invoice — the link encodes the transaction intent as a partial OTX, and the user's wallet (JoyID, etc.) previews and completes it. Embeddable anywhere; no dApp navigation needed.
An interactive GUI that visualizes Cell consumption/creation flows, script execution traces, and cycle costs. See exactly which Cells are consumed, which are created, what data changes, and why a script fails — graphically, not as raw terminal output.
Deploy audited CKB scripts on-chain once, then reference them via Cell Deps with versioning and dependency resolution. A searchable registry of Lock Scripts, Type Scripts, and Spawn-callable modules so developers run `ckb-pkg install multisig-lock` instead of copy-pasting code.
Pre-built, audited script building blocks using the Spawn syscall and pipes: multisig, time-locks, rate limiting, access control, escrow, oracle reading, token gating. Spawn shipped with Meepo (2025) but has almost no ecosystem libraries on top of it.
Automated fuzzing and property-based testing built for CKB scripts. Lock scripts are powerful but unforgiving — a bug can permanently freeze assets. This tool generates adversarial transactions and checks for freeze conditions, integer overflow, and replay vulnerabilities before code reaches mainnet.
Wished for the idea. A free on-chain demand signal — no commitment yet.
Public on-chain claim with a deadline. No stake — reputation only.
CKB locked behind a deadline. Claims the idea exclusively. Slash on lapse.
Staked plus a bounty funded. The fully loaded commitment.
An open directory of CKB-native project ideas, with on-chain commitments, stakes, and bounties. Ideas are CC0; the projects built from them belong to their builders.
Anyone — open a pull request that adds an ideas/ file. CI validates it against the schema. The idea enters the catalog under CC0.
Staking CKB claims an idea exclusively, with a deadline you set. Ship in time and your stake returns. Lapse and — if you chose slash-to-next — it funds the next builder.
A build is checked against the acceptance criteria attached to the idea and confirmed by a curator multisig. Funds live in user Cells and are never custodied by the platform.
A small protocol fee on bounty funding and payout. See SPEC.md for exact terms. Everything else flows to builders.
CKB testnet first — the escrow lock is audited before it holds real CKB on mainnet.
The catalog is open. The chain is watching. Your reputation starts now.