One of the most interesting parts of Ethereum’s post-quantum roadmap isn’t the specific PQ signature schemes it’s researching.
It’s crypto-agility.
Today, ordinary Ethereum accounts are tied to ECDSA/secp256k1. Ethereum’s proposed Frame Transactions (EIP-8141) would change that by making authentication programmable at the account level.
In simple terms, Ethereum would stop mandating a single signature scheme for ordinary accounts and instead let accounts define their own verification logic.
With Frame Transactions, a user could migrate from ECDSA to a post-quantum signature scheme, and later from that scheme to another one, without Ethereum needing a hard fork every time the cryptography changes.
This is what crypto-agility is all about, and what we’ve been raving about for some time now. If a PQ scheme is weakened, broken, or simply superseded, you want to be able to replace it without redesigning the protocol.
What Ethereum is trying to introduce at the account layer is conceptually very similar to something CKB already gets from its architecture.
On CKB, ownership isn’t hardcoded to one signature algorithm. Instead, Cells are protected by Lock Scripts: verification programs executed by the RISC-V-based CKB-VM.
A Lock Script can verify secp256k1 or SPHINCS+/SLH-DSA today, or some entirely different signature scheme introduced in the future.
The base layer doesn’t need to be redesigned around each new scheme. It simply executes the verification program.
It’s very cool to see a leading chain like Ethereum converging on the same conclusion CKB arrived at seven years ago:
Blockchains shouldn’t be built around the assumption that today’s cryptography will still be tomorrow’s cryptography.
Learning to build on CKB takes time. The tooling is different enough from most ecosystems that new developers often hit walls that take days to get past.
The CKB AI Scholarship is a direct response to that.
CKBuilders get access to the Share-AI platform for shared AI model access at Level 1, and personal Claude accounts for more intensive development work at Level 2, with access tied to specific output and reporting requirements.
Alongside this, a CKB-specific MCP server is in development, trained on CKB documentation and tooling, with the aim of giving the models enough context to be genuinely useful on CKB-specific problems.
The hypothesis is straightforward: better AI tools, trained on the right material, should substantially reduce the time from onboarding to shipping.
More than 40 developers are already using the platform.
Full Q3 report 👉 https://t.co/XyfTZwzao2
🔗 [RECAP] BPSC KNOWLEDGE SHARING — EXPLORING NERVOS CKB
What makes CKB different? Our latest online session brought BPSC members together to explore Nervos Network and its approach to blockchain design! 💻
From the blockchain trilemma to CKB’s technical foundations, we covered:
🔹 UTXO & the Cell Model
🔹 Lock Scripts & Type Scripts
🔹 CKB-VM & RISC-V
🔹 Learning resources and the CKBuilders community
More learning, more sharing, and more steps toward becoming Web3 builders. 🚀
#BPSC #Nervos #CKB #CKBuilders
@NervosNation
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!
https://t.co/Du1JCwRp9g
Last Day of CAMP is Today 🏕️
Received so much amore at CAMP Plan ₿ Forum so far.
The story of Bitcoin, told by ten artists and one blank ape.
Each work one of one. Last chance to say ciao today.
Villa Ciani, Room 215 · until 18:30
→ https://t.co/3SsiGX7upl
@LuganoPlanB #PlanBForum #Bitcoin #BitcoinArt #NervapeCAMP
Tomorrow 🏕️ Nervape CAMP Lugano
Ten themes told by ten artists and one blank ape.
Each work connected to a place in Bitcoin’s history.
@LuganoPlanB, Villa Ciani, Room 215
Oct 23–24, 09:00–18:30
→ https://t.co/3SsiGX7upl
Also a secret surprise sits in the room awaiting visitors… 🗿
#art #NervapeCAMP #PlanBForum #Bitcoin
🟠 Plan ₿ Week starts today.
Where Bitcoin left a trace:
Berkeley · Berlin · Prague · Sichuan · Taipei · Hong Kong · Buenos Aires · Chiang Mai · El Salvador · Lugano
Ten artists. One blank ape. Each one-of-one.
CAMP opens Friday at Villa Ciani, Room 215.
→ https://t.co/3SsiGX7upl
#Lugano #PlanBForum #Bitcoin #art @LuganoPlanB
Aped in. 🪂 Landed at Plan ₿.
Seed. Gather. Sovereignty. Vanish. Build. Bridge. Resistance. Drift. Daily. Welcome.
Ten places Bitcoin passed through. Ten artists. One blank ape.
Villa Ciani, Room 215 · Oct 23–24
→ https://t.co/x9DZbhtJdP
@LuganoPlanB#PlanBForum#Bitcoin #art
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! 😄
🟠 Ten artists. Ten cities...
where Bitcoin left a trace.
One blank Nervape each,
one word to start from.
CAMP is live → https://t.co/GvhVEsbkYv
First stop: @LuganoPlanB Forum. Oct 23–24.
#Bitcoin#art
CKB Off-Chain Hanoi concluded yesterday, and it was an event that brought together CKBuilders, external developers and students.
There was a wealth of information and experiences shared, which shows just how far the CKB developer community in Vietnam has come, and reflects the continuing surge in developer activity on CKB in 2026.
Many thanks to our partners at @bps_club and @texlabsorg for helping it come together!
Read more here
https://t.co/LgEzINWT1B
Kaze took the stage at Hack in the Hills
Your keys. Your CKB. Your Bitcoin.
We walked a room full of student builders through how a self-custodial wallet can work for real people, from sending and receiving to cashing out locally.
@HackInHills@NervosNation@NervosNetwork@ckbsamurai
https://t.co/zRCoJCSA1V
Aba showed up and showed out! 🇳🇬🚀
Last Saturday, we teamed up with @NervosCatalyst And @Abia_Web3Net to bring CKB Off Chain to Aba for the very first time.
The rain came down heavy, but the builders came through anyway. The room was alive with curiosity, good conversations, and a genuine hunger to learn and build.
We , heard from CKB developers sharing real projects, and watched new connections form right in front of us.
This is what it looks like when a community comes together. Not just to talk, but to build something real.
Aba is now part of the global CKB story. And we are just getting started.
Until next time, Aba! 🧡🖤
#CKB #Nervos #Aba #Web3 #CKBuilders #Blockchain
[1/7] 👀 Tracking #Nervos CKB Community Fund DAO proposals shouldn’t mean jumping between forum threads, voting pages & update posts.
So I built a dashboard, with #AI turning my requirements into a working product.
Explore it 👇
https://t.co/F39rgcZGSs
In 7 years of being in crypto I don’t think I’ve seen so many active builders on nervos network, glad to see devs are paying attention to a tech that’s been ahead of its time. $ckb bitcoin:native
⚠️ Notice for UTXOSwap Liquidity Providers: Withdraw Before 10 October 2026, 16:00 UTC
UTXOSwap has announced that its service will shut down on 10 October 2026 at 16:00 UTC.
If you have liquidity in UTXOSwap pools, remove all of it before this deadline. Please act well in advance.
CKBA does not operate UTXOSwap and is not managing its shutdown. We are sharing UTXOSwap’s notice to raise awareness and help liquidity providers act in time.
Read the original notice on the UTXOSwap website 👉 https://t.co/0DZdvqnN4u
Blackbox Devlog #9: Bitcoin support added! Plus, a purpose-built PCB
Three developments this fortnight at three different distances from a shipping product: the new board is running, #Bitcoin is in as a new payment rail, and for the first time Blackbox has a custom-designed circuit board.
Bitcoin payment support:
- Receive-only, with no private key on the device; the merchant scans their Bitcoin wallet's public key and each sale derives a fresh receive address
- Two distinct settlement states: SEEN means unconfirmed on the network; VERIFIED means the terminal has validated a cryptographic proof against block headers it audited itself, from a firmware checkpoint upward through proof of work and consensus rules. A connected server can help locate a payment; it cannot fabricate one
- Sixteen test suites run against real mainnet and signet vectors
- Disabled by default; running on signet until the hardware checkpoint passes
First purpose-built PCB:
- A circuit board designed around Blackbox's own requirements rather than repurposed from a development board
- ESP32-S3, 5-inch 800x480 display, 4 layers, single 3.3V rail, printer, scanner, NFC, and microSD; 193 footprints, 125 nets, ERC clean and routed
- Design generated from a source model: schematic, PCB, BOM, placement file, pinout doc, and firmware pin header all produced from two Python files, with automated checks re-validating pin assignments on every build
- Errors caught before copper include a level translator wrong on all five signals, a shorted eFuse footprint, a printer inrush of 200A resolved with a Miller capacitor ramping it to 1.4A over 6.6ms, and over-voltage protection set to the printer's 9V limit
- Not yet sent for fabrication; six blockers remain
The new board is running:
- The VIEWE S3 boots, renders, takes touch, and talks to the testnet indexer
- First real action: resolved a merchant address to its funding block, verified against a prediction rather than accepted at face value
- Printer confirmed working via its own self-test print before any firmware interaction
- Scanner driver reworked: a non-responsive handshake no longer marks the scanner absent; the driver falls back to listen-only mode and reads decoded barcodes as plain text
Light client sync start:
- A light client needs to know where on the blockchain to begin; too low wastes hours, too high silently misses incoming funds while reporting healthy
- Start height now has explicit provenance: pulled from the provisioning bundle if present, otherwise a one-time setup screen offers a live indexer lookup or manual entry
- Manual entry validated asymmetrically: above the chain tip is refused, just under it warns; a failed lookup sets nothing rather than defaulting to zero
Next: re-run light client bootstrap checks through a real scanner, complete the Phase 1 hardware checkpoint, take the first Bitcoin payment on the device over signet, and measure a panel for the PCB.
Full devlog: https://t.co/6KKOMVDEI5
Some ideas got tested in the real world. Some moved onto testnet. Some took a different turn entirely. 👀
Dular wrapped up its pilot after testing Fiber payments with 30 users in Kenya, FiberNuts (by @Code3ks) opened its Fiber + Cashu community market demo, and @LusoCryptoLabs tried using `.cell` names as human-readable Fiber payment endpoints.
There are also new experiments around P2P trading, payment + service delivery, and node recovery tools.
⚡ Catch up on what Fiber builders have been working on: https://t.co/1OXQPjiAz7