CKB Dev↾⇃

Cypherpunk · #PoW · #CKB Contributor
also on Nostr: npub1j7948t0lwa3vznttp55nl73funfrynnkwy3pj67xnxadhv6fy7rqq393v4

[CKB Dev↾⇃ @CKBdev]

A different kind of building at #CKCon 2026! 🇲🇾🌺
We're in Kuala Lumpur this week! Catching up, sharing ideas, and talking about what's next for CKB.

Great to hear updates and fresh ideas from people across the ecosystem, including @RunningCKB, @ckbsamurai, @JackyLHH, @aaaaaaaalive24, @kashortgirl, @aszepieniec, @teaplusplus11, @BitcoinLightApp, with @ebubedev and @rypto joining remotely. Lots of interesting work and discussions about what's next!

And finally we put the laptops aside and built miniature cities together. 🏙
Turns out we've got some pretty good city builders on the team too! 😄

[CKB Dev↾⇃ @CKBdev]

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:
https://t.co/iD757SCgtx

[tovarishch.bit @c_hongzhou]

Happy to share some news from @ckba_build CKBA’s DevRel and Ecosystem Support teams: our paper on CCC (https://t.co/ToqoPGVJcN), When EVM Defaults Break: Three SDK Patterns for UTXO-Family Wallets, has been accepted for poster presentation at IEEE International Conference on Distributed Ledger Technologies (ICDLT) 2026!

Through this collaboration, @Hanssen0 (@CKBDevrel) and I (Ecosystem) built on the CCC team’s existing engineering work to distill three reusable design patterns:
• Transaction composition: helping applications handle inputs, change, and fees.
• Unified signing: providing a common interface across different wallet signing methods.
• Reusable wallet connectors: sharing wallet connection and onboarding components across applications.

The conference brings together academia and industry, with organizers from Nova School of Business and Economics, NOVA Information Management School, and the IEEE Portugal Section. It is part of BLOCKCHAIN. PT, a project funded through Portugal’s Recovery and Resilience Plan and the EU’s NextGenerationEU programme.

For us, this is an opportunity to bring CKB’s experience in developer tooling and application development into a broader conversation with researchers and builders.

Thanks to Hanssen and everyone who has contributed to CCC!

[CKB Dev↾⇃ @CKBdev]

#CKB Monthly Development Log
CKB v0.210.0 is out, with more fixes and improvements to node reliability and networking. Work also continued on developer tools and DAO treasury voting.

v0.210.0 shipped with additional security checks to catch malformed requests and transactions earlier, helping nodes avoid unnecessary processing.

A few other highlights:
- CKB-VM added new validation modes, laying the groundwork for stricter checks in the future.
- Tentacle improved QUIC support and connection handling, while node-level QUIC integration remains under review.
- ckb-cli integrated a new terminal interface for interacting with CKB nodes, with a release still pending.
- Light-client work continued on stronger block verification and more reliable synchronization.
- DAO treasury voting moved from design into an experimental implementation, with smart contracts, an SDK, and tests.

Meanwhile, the transaction-pool redesign is still in progress, and preparation for CKB v0.211 is underway.

Full dev log: https://t.co/Y1QBrLU1SB

[CKB Dev↾⇃ @CKBdev]

CKBA DevRel covers a pretty wide range of work around developers and builders, from technical content and docs to developer support, feedback, and ecosystem projects.
And if you didn't know, the DevRel AMA on Reddit is still open. 👀
Ask away: https://t.co/qnjqBIfPRE

[CKB Dev↾⇃ @CKBdev]

We usually talk about code here. ⚙️🐛

But this time, got any questions about how what we build gets explained to everyone else?

Stefan, who leads CKBA's Content & Communications team, is doing an AMA.

Got questions for him? Drop them below ↓
https://t.co/ndZETxR75E

[CKB Dev↾⇃ @CKBdev]

The monthly #CKB development log is out:

This cycle focused on reducing failure cases across the node and light client, while several larger architecture changes continue to be reviewed.

CKB-VM v0.24.15 was released this month, with follow-up fixes to runtime behavior. The light client also added stricter checks for headers, proofs, and peer checkpoints, so invalid or inconsistent data can be rejected earlier.

On the node side, the team fixed issues around indexing rollback, networking edge cases, and dependency security. More protections are also being reviewed for transaction queues, sync responses, block relay, and request limits.

Some longer-term work is still in progress: the tx-pool redesign, a new RocksDB layout, and initial QUIC integration are all under review rather than released. DAO treasury and voting work also remains at the research and PoC stage.

There are also new docs for developers working with ckb-std and Rust script templates.

Full dev log: https://t.co/UFd6vE5eOH

[CKB Dev↾⇃ @CKBdev]

@VladimirKvale @NervosNation @CKBEcoFund @NervosNetwork @joy_protocol @utxostack @MessariCrypto @BitcoinMagazine @palmeconomy @rgbppfans @FiberDevs @CKBDevrel CKB is very much alive and building. We'll be sharing our dev log here @CKBdev on a monthly basis moving forward!

[CKB Dev↾⇃ @CKBdev]

#CKB monthly development log (August)

This cycle brought CKB v0.209.0, Tentacle 0.7.7, and a range of reliability and security improvements across the node, networking stack, and light-client.

- CKB v0.209.0 shipped with tx-pool, Tor, and memory-growth fixes
- Tentacle 0.7.7 fixed a QUIC compatibility issue
- Light-client verification got stricter around proofs and downloaded block data
- Improvements to ckb-cli and contract development tooling
- Advanced a batch tally settlement solution (currently in design/PoC) for DAO Treasury & Voting

We also closed the previous tx-pool pipeline prototype and the next tx-pool design is moving toward an invariant-driven validate → plan → apply → effects model.

Full dev log: https://t.co/rYhwGdFega

[CKB Dev↾⇃ @CKBdev]

Join us next week for an AMA with the @BitcoinLightApp team!
They'll talk about the move from CKBull to Bitcoin Light, their vision for a BTC-compatible wallet, and what's next for the project.⚡

🗓️ Aug 4, 11:00 AM GMT

Come by with your questions and we'll see you there: https://t.co/gyOQL0sAou

[CKB Dev↾⇃ @CKBdev]

#CKB monthly development log (July)

This development cycle focused on release stabilization, security hardening, and infrastructure improvements.
Highlights include:
- CKB v0.208.0 and Tentacle 0.7.6 releases
- Improved RPC and mining operator behavior
- Continued CKB-VM cleanup, plus light client bounds and panic-path hardening
- Advanced CKB DAO treasury and voting research into executable PoC work
- Three new CKB-VM write-ups on macro-ops fusion, B extension, and CFI concepts

We're also keeping key architecture items--tx-pool pipeline, Guix release flow, QUIC integration--moving through review.

Check out the full dev log: https://t.co/xMZt0pv7J7

[CKB Dev↾⇃ @CKBdev]

CKB monthly development log (June)

It's one of those months where you fix a bug, review a PR, merge a patch, and somehow come back to find the queue even longer than when you left... 🫣

Highlights include:
- CKB v0.207.0 release, security hardening across CKB, the light client, and the network
- Major progress on QUIC transport
- Continued DAO treasury and voting research
- A series of three educational write-ups on CKB-VM
- Security fixes reported through the bug bounty program--Shoutout to those who helped us find issues and make CKB stronger! 🙌

We also continued strengthening our security workflow. As AI-assisted security tools become more capable, the bar for code security keeps rising. We're integrating more of these tools into our development process to catch issues earlier.

But anyway, we're excited to finally share this month's dev log: https://t.co/84Gq38yc06

[CKB Dev↾⇃ @CKBdev]

We just launched a dedicated AI Resources page to make onboarding AI coworkers to CKB easier.

Everything in one place: LLM files, agent instructions and skills, starter prompts, and the CKB AI MCP server.

Send your agents here before they hallucinate: https://t.co/oGVyyI6hSE

[CKB Dev↾⇃ @CKBdev]

Reddit AMA Time again! This time we have Invisibook https://t.co/htgvPPp8JM

Invisibook is a privacy-preserving cross-chain order book, where prices are public but amounts remain private.
Built on three core cryptographic primitives:
• Poseidon hash function
• ZK proofs
• Malicious-secure secret-sharing multi-party computation

⏰ Submit your questions before June 25, 2026, 11:00 AM GMT.
Ask away on Reddit: https://t.co/uwOl1zkSu5

[Nervos Community Catalyst @NervosCatalyst]

Introducing: Build on CKB!

With the rapid growth of our CKBuilders programme, we've been devising new offerings to accommodate developers who are new to CKB and interested in learning.

We now have the Build on CKB telegram channel for new developers to participate in weekly competitions to win prizes, receive devrel support, participate in peer learning, and get pre-hackathon preparation and support!

We recently completed our first Build on CKB campaign, with 8 new developers all receiving CKB prizes!

If you missed out, don't worry! We have a new campaign live now. Check it out on CKBoost:

https://t.co/jdbZaBIXJ4

[Common Knowledge Base Association (CKBA) @ckba_build]

Straight from @Coinbase’s April paper on quantum computing and blockchains. 👇

“Crypto-agility is a highly recommended practice in general [...] even more so in the context of PQC.”

Now guess which chains were designed to switch cryptographic algorithms without disrupting operations🧠

Hint: there’s only one.

[CKB Dev↾⇃ @CKBdev]

CKB development log for May is out.

This month focused mainly on maintenance, infrastructure, and long-term improvements across the stack.
• CKB v0.206.0 release
• Progress on DAO / voting research
• Faster storage and sync optimization work
• Reproducible build pipeline progress
• QUIC networking integration in progress
• Continued CKB-VM and light client maintenance

Full dev log: https://t.co/qewhXuVZ5O