Why is 𝗥𝗚𝗕++ best for Bitcoin builders? 🔸Issue assets on Bitcoin 🔸Fully usable in smart contracts 🔸No bridges, no EVM 🔸Pure proof-of-work + UTXO 🔸Interoperable with UTXO chains 🔸Trustless, decentralized, secure 🔸Supported by major Bitcoin wallets This video explains

CKB is bigger than a ticker. There's an entire ecosystem to unpack. Anything & Everything CKB The tech. The builders. The breakthroughs. The big ideas. What's working, what's next, and what CKB could unlock. Nov 14 | 8 PM EAT No surface-level takes. Let's get into it.

Is cellula.id another name registrar? Watch a name get paid in 2 seconds. Then tell us. cellula.id

We're running an AMA with Gone in 60ms hackathon winner, Drey @dreyethh! 🏆 His Clasp won 1st place for letting you securely connect apps & AI agents to your Fiber wallet with full control over permissions and spending limits. Drop by, say hi, and leave your questions! teddit.net/r/NervosNetwork/c…

The Q3 2026 Nervos Community Catalyst report is out. @NervosCatalyst been running this program since 2025, and the compounding is starting to show: close to 100 builders and alumni, a project tracker that grew from 45 to 59 entries over the quarter, and community members now organizing independent events in Nigeria, Kenya, and Vietnam. Full report 👉 talk.nervos.org/t/nervos-com…

Leading cryptographers met in Cambridge last month for Ethereum's second annual post-quantum research workshop. The recap is worth four minutes, and it doesn't soften the stakes: quantum computers were expected to break cryptography by 2035. "The new estimate is 2029." AI is a big part of why. @GiacomoFenzi of EPFL: "It is almost certain that AI accelerates timelines. It is uncertain by how much it will accelerate it." Despite that uncertainty, the tone is upbeat. Ethereum's researchers have settled on hash-based signatures, and as one puts it near the end: "we just need to put it in place and done." So what does "done" look like? On Bitcoin, it means agreeing a soft fork. Taproot, its last major upgrade, took nearly four years from proposal to activation, and it had broad support. Then every holder has to move their coins, on a network with room for only a few thousand transactions every ten minutes. On Ethereum, standard accounts are tied to one signature scheme checked by the protocol, so it means a hard fork. Then every holder has to move their coins. A proposal called Frame Transactions (EIP-8141) would let accounts set their own verification, so later changes or additions of signature schemes wouldn't need another fork. And if Bitcoin's new scheme ever needs replacing, it goes through it all again. On CKB, signature schemes were never written into the rules every node enforces. Each one is a small program called a lock script, so adding a new scheme is just a software release. Anyone can do it at any time, no forks needed. SPHINCS+, a hash-based scheme, is already live on the network, with an audited lock. "Done" means moving your coins under it in an ordinary transaction. Whichever schemes stand the test of time, CKB can carry them without a protocol upgrade.

Here are the key crypto categories and projects worth knowing 👇 🟢 Quantum Resistant $QRL $CKB $QANX $NAORIS $QTC 🔵 Layer 1 $SOL $ICP $KAS $SUI $ALGO $INJ $SEI $APT $PROS $KTA 🔴 RWA $ONDO $CFG $ZBCN $SYRUP $RE $PLUME $PENDLE $PROPS $EDEN $CPOOL 🟩 Robinhood Ecosystem $PONS $ORBIO $EDEL $STANDARD $TORCH $DELTA $SFI $STATICS $PRIORS $PRISM 🟠 AI $TAO $QUBIC $AKT $SENT $FET $VIRTUAL $VVV $DATA $TRAC $KITE 🟡 Privacy $XMR $ZEC $ZANO $ARX $ANYONE Bookmark this for reference 🔖 NFA, DYOR

HELLO, CKB. We’re building an open-source portable reputation layer for @NervosNetwork CKB. We received a community-approved $7,000 grant from the CKB Community Fund DAO to extend did:ckb from identity into verifiable reputation. Our goal is simple: turn contributions, quest completions and community participation into issuer-backed Claim Cells that builders can carry across applications. Our first two delivery milestones are complete on CKB Testnet. We’ll use this account to share build logs, integrations and live evidence as we continue. Explore Vellum: usevellum.xyz Grant and public reports: talk.nervos.org/t/dis-vellum… @CkbDaoUpdates @ckba_build

🚴 Fiber Dev Log 40 🚴 Peer reconnects, node storage, and browser payments all got some attention this round! 🔧 Here's what's new: - Reconnect recovery: Better handling of interrupted payment updates, plus a fallback for stalled V1 channels. - Node storage: Operators can now opt into synchronous database writes for stronger durability. - Browser apps: More reliable shutdowns and an improved multi-hop tutorial covering payment recovery. - Testnet: An updated commitment-lock contract is now deployed for integration work. What's coming next: Channel V2 is ready for review, while Hosted LSP is adding signing notifications for external clients. Both are still in progress. Full dev log: github.com/nervosnetwork/fib…

📢 A new Build on CKB campaign is live! For this campaign, you'll explore Fiber's multi-hop tutorial, sending payments and managing liquidity. The best submissions receive CKB prizes, so what are you waiting for? Check out the campaign here ckboost.netlify.app/campaign…

SHA-256, the hash function securing Bitcoin, isn't broken. Researchers test its safety margin on simplified versions. For 12 years it didn't budge. This year it has shrunk repeatedly, once thanks to @FutureDies. AI is helping to find weak spots faster. Managing that risk means planning cryptographic upgrades early, before anything breaks.

We're just getting started

A year on from our last CKBuilders article, we return to follow the journeys of old and new faces in our developer community: their experiences, challenges, and successes. The future of CKB is bright! nervos.org/knowledge-base/CK…

Nice to see more Fiber projects moving from prototypes to public testing! @ebubedev opened Twine's P2P trading app for testnet testing, @Code3ks opened the FiberNuts Community Market (and already shipped fixes based on feedback), and @truthixifi turned hackathon feedback into Fiber Forge v0.4.0, with new SDK, CI, and CCH testing tools. Meanwhile, @Dean8IX shared new recovery evidence for FNN Safeguard, and @LusoCryptoLabs opened the Cellula Wallet testnet beta. If you're trying out any of these projects, let the builders know what works or breaks, and what you'd like to see next!⚡ Catch up with the community in Pulse 17: fiber.world/blog/pulse/issue…

This is what real growth looks like. If you really want to know if a project's healthy, you don't look at the chart. You look at who's building on it. And on that front, CKB just had a brilliant quarter. Their community developer programme has grown to nearly a hundred active builders, with over 25 new ones joining just this quarter. Their project tracker jumped from 45 projects to 59. And they ran a hackathon focused on Fiber, their payments tech, that pulled in around a hundred participants and 66 submissions. But here's the part I love most. Look at where this growth is coming from. Not just the usual Silicon Valley crowd. We're talking real, in-person meetups in Kenya, Nigeria, and Vietnam. Nairobi, Mombasa, Hanoi. Developers in emerging markets, where fast, cheap payments can really make an impact. And it's not just solo devs either. Teams from other ecosystems, Cardano, Bitcoin, Lightning, are now showing up to explore building on CKB too. A lot of these are still early prototypes and there is still a lot of work to do. But a growing, global, grassroots community of actual builders? That's the strongest foundation any project can have. Price comes and goes. But people building, all over the world? That's how something lasts. $CKB @NervosNetwork @ckba_build

CKB's work just got academic recognition. Their developer team just had a paper accepted at a proper IEEE conference: the International Conference on Distributed Ledger Technologies. CKB has a tool called CCC, a toolkit that helps developers build apps and connect wallets on CKB easily. Here's the clever bit. Most crypto building tools are designed for Ethereum. But CKB works differently under the hood, more like Bitcoin, so a lot of the usual Ethereum shortcuts just break. So the CKB team figured out how to solve that, and wrote up three reusable patterns for doing it properly: • Handling transactions • Signing • Connecting wallets All built for a chain that doesn't play by Ethereum's rules. That work has now been accepted to present at a respected IEEE conference, alongside actual academics and researchers. Getting your engineering recognised by people whose whole job is scrutiny means the work is being taken seriously at the highest level. Does academic recognition matter in crypto? 👇 $CKB @NervosNetwork

Blackbox Devlog #10: prepaid card and tap-to-pay support added Prepaid card support: - A tap reads the card’s balance and counter, checks whether the sale is allowed, writes the new balance back, and signs the result; no server, no live transaction - The terminal holds a debit key that can spend down a card but cannot create value; issuing and loading stay in the Vault, which holds the on-chain reserve behind each card - Settlement is a separate, later act: the terminal journals every completed tap and batches them to the Vault when it can; until then it runs on an unsettled cap, bounding the worst case of a terminal that never phones home - Currently a demo tier running on cheap NTAG cards with a custom MAC rather than the DESFire EV3 secure element the shipping card will use; disabled by default behind a compile-time flag Handling failed taps: - Every debit is written to a journal as an intent before the card is touched, removed only once the card write is confirmed; a card pulled mid-write, a power loss, a reader glitch each land in a state the terminal can name and recover from - A write known not to have landed charges nothing; a write whose outcome is unknown parks until the same card is tapped again, resolving to exactly one charge or none - Cards were yanked mid-write deliberately five times at the bench; the ledger came out with five charges, no doubles, no losses - A sale cancelled at the instant of card write raises a flag the cashier must acknowledge, and the same card is refused a second tap until they do; the guard is held until cleared, not on a timer Vouchers and staff keys: - Item vouchers put a product rather than a balance on a tag, each backed by a chain cell that closes automatically once settlement lands - Staff keys use the cryptographic originality signature NXP puts on genuine NTAG silicon; a price override requires a staff tag. The demo cards turned out to be counterfeit and cannot produce this signature, which is precisely why staff authorisation uses it Bug: UI freeze under concurrent flash writes: - The confirmation screen began freezing hard after a successful card debit followed immediately by a settlement sync - Cause: an SPI flash write on the ESP32-S3 briefly stalls the other CPU core; the journal task was unpinned, so it ran on the core opposite the UI, dropping the UI’s clock tick mid-sleep - Fix: pin flash-writing tasks to the same core as the UI, so the stall lands on the networking core; seventeen hours of uptime and a full bench run with no recurrence. The same latent bug was found and fixed in the Bitcoin header path before it surfaced Also: Add Item form now has a Scan barcode button that arms the scanner in place and drops the code into the field, keeping name and price already typed Space bar on the Add Item keyboard was hidden under the footer bar; fixed Next: watchdog for a genuinely wedged terminal, certificate pinning so settlement cannot be spoofed on a hostile network, on-device voucher and staff key support, and the DESFire secure-element card once stock arrives. Full devlog: blackbox.wyltekindustries.co…

🎉 Three CKB Community Fund DAO proposals are now open for voting! (Image 1) ckbcommunityfunddao.xyz/proj… Whether you’re for or against, your vote matters. Open each proposal’s details page to find the voting link (Image 2). Have your say!

when you hear industry leaders talking about quantum computing, it is because bad players are leveraging it to threaten the security of so many blockchain networks. but @NervosNetwork already prepared from day 1. CKB is built with cryptographic abstraction which makes it possible to secure and replace security models without breaking the CKB fundamental rules.

Great AMA recap with @Hanssen0 ! Love the honest take on CKB's tooling evolution, from smoothing out wallet connections with CCC to tackling data indexing. Plus some great points on why AI won't replace solid protocol architecture anytime soon. Worth a 5-minute read if you're building in the ecosystem: talk.nervos.org/t/ckb-dev-re…

Another reason to avoid relying on an ever-growing list of cryptographic precompiles is that each one embeds a cryptographic operation in the protocol’s consensus rules. Introducing a new signature scheme this way requires the network to reach social consensus around a fork. There is a consistent direction in Vitalik’s proposals, from exploring RISC-V as a replacement for the EVM to now advocating “EIP-8288 maximalism”: give Ethereum room to support new cryptography without continually expanding the protocol. EIP-8288 would open a path to supporting different signature schemes without a dedicated precompile for each. Signature verification would be proven off-chain, and those proofs aggregated for the chain to check, reducing the associated data and verification costs. The broader idea is one we've discussed extensively: blockchains are for verification, not computation. Vitalik is reframing the "world computer" along precisely these lines: "any data/computation that does not need to be in the 'main thread' of data/execution should not be put into the main thread." This is the reasoning CKB was built around from the beginning. Its accounting model (the Cell model, which is a generalized version of the UTXO model) separates off-chain state generation from on-chain verification. CKB also launched without cryptographic precompiles. Signature verification runs as ordinary software on its RISC-V VM, so developers can introduce new schemes as Lock Scripts and users can adopt them without waiting for a protocol upgrade. That's how an audited post-quantum lock, SPHINCS+, is already live on mainnet. The idea is simple: keep the base layer simple and stable while giving the cryptography and applications built on it room to evolve. It's the essence of crypto-agility, and it's becoming more appreciated amid the looming threat of cryptographically relevant quantum computers and AI.