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.

What’s the missing piece of the digital economy?

[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 👇 ckbcommunityfunddao.xyz

⚠️ 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 👉 utxoswap.xyz/info/overview

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: blackbox.wyltekindustries.co…

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: fiber.world/blog/pulse/issue…

And thus we observe the return to verification-centric architectures (realized and idealized by UTXO chains like @NervosNetwork and Bitcoin). Whether by means of cryptography or other forms of succinct verification, the concept is the same: don’t replicate globally what need not be replicated globally.

🔄 DAO Proposal Sync (Discussion Phase) Project: Kaze × CKB UniTour - Kenya Stage 2 reached 35 likes within the 7-day discussion window and is now eligible to proceed to the Metaforo voting stage. Proposal link: talk.nervos.org/t/10736