Hello Nervos community,
I’m sharing an early look at Cellbet — a Web3 betting platform on Nervos CKB built to host multiple games over time. We’re starting with Crash (multiplier rises until it crashes; players try to cash out in time) as the first game while we harden the shared stack.
Where things stand: Active development — Next.js frontend, NestJS backend, and RISC-V type scripts for the crash round, with CCC-style CKB wallet integration.
Source code: github.com/chukwuma619/cellbet
What we’re trying to solve
Real-time games shouldn’t force a false choice between signing every move (slow UX) and opaque off-chain play (harder to reason about funds and rules). The aim is clear on-chain state where it matters — commits, escrow, settlement — and a snappy experience in the client.
Technical snapshot
- On-chain: A crash-round type script in Rust (
ckb-std): commit cells for round identity and a seed hash; escrow cells with user / house / platform locks, stake, and fee (bps); defined witness paths for wins and losses. - Off-chain: Shared TypeScript (
@cellbet/shared) so client and backend stay aligned with what the script validates. - Platform: Crash ships first; the layout is meant so future games can plug into the same patterns instead of one-offs.
Why CKB
The cell model and RISC-V scripts are a good fit for explicit, auditable game state and native CKB flows.
Rough roadmap
- Crash — solid loop, clear fairness story, reliable CKB flows.
- Funding UX — e.g. pooled balance for fast entry vs per-bet escrow, with clear deposit / withdraw semantics.
- More games on Cellbet as the platform layer stabilizes.
I’d love input
- What would make you try an early build (testnet/devnet, docs, short demo)?
- For real-time play on CKB, what tradeoffs do you care about most between escrow-per-bet and balance-backed betting?
- Anything you’d want to see documented up front (seeds, fees, operational model)?
Thanks for reading — replies and questions are welcome.