🚴 Fiber Dev Log 31 🚴 This cycle was mostly about getting Fiber ready for v0.9.0. We shipped v0.9.0-rc3 and spent a lot of time on security hardening, bug bounty fixes, and an AI-assisted code review to help make the final release as solid as possible. Key updates: - Security fixes from bug bounty reports - AI-assisted code review across the codebase - Backup & Restore ready for the next release - Stronger validation for payments, routing, invoices, and gossip - Better tooling and operator UX Meanwhile, work continues on CCH, Atomic MPP, x402 payment proofs, backup/recovery tooling, and CLI/TUI improvements. By the way, the Nervos Bug Bounty program is always open. If you want to help us audit, identify, and report potential vulnerabilities, you can find the rules and rewards details here: bounty.nervos.org/ Shoutout to everyone testing, reviewing, and helping us catch those edge cases! 🙌 Full devlog: github.com/nervosnetwork/fib…

📃 Fiber Desktop Proposal Voting has now closed 📊 Preliminary outcome: PASSED (Approval: 100%, Total voting weight: 65,057,521 CKB). Next, the coordinator will run a post-close verification using CKB DAO Watchdog to cross-check Metaforo-recorded voting weights against on-chain Nervos DAO deposit weights, along with a manual check, and will then share the verification logs with the committee for final confirmation that the result is valid per the process.

Imagine moving assets between two #blockchains with no bridge in the middle, no custodian, no committee holding your funds. Just #Cardano and #Nervos verifying each other on-chain, ADA → CKB and CKB → ADA, both ways. It's called Chiral. 👉bit.ly/4orrsqf #Cardano #CKB

Hey Israel, you are done. You are NOT the chosen people. There is no Prophecy. There is no Messiah. The world hates you. You are done.

Here's a fun little exercise for crypto bros: Open the quantumtracker.org/ website by the legends @tectonicxyz Select "Blockchains" in the sidebar. Sort by "Tier." Notice who sits at the top with the most green check marks :) Cheers 🍻

$CKB Blackbox Upgrades @NervosNetwork

Open Letter to the President of the Russian Federation: president.gov.ua/en/news/vid…

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.

roadmaps are for products. blockchains age better when the core becomes boring enough to distrust everyone equally. ossification is not stagnation; it's the point where users stop needing permission from future committees x.com/ckba_build/status/2061…

Okay, let’s talk about roadmaps. It’s a question we’ve had to deal with for years now. “What is CKB’s future plan? Is there a clear roadmap? What’s on the roadmap?” CKB is not a product operated by a company. It’s public infrastructure. And the fact that people think about blockchains in ‘roadmap’ terms is worrying. Years of high-time-preference teams shilling centralized products as “decentralized” have conditioned the industry to think about blockchains in corporate terms: Who’s the CEO? Who’s on the cap table? What’s the roadmap? These teams use “the roadmap” as an upselling technique—a product in itself, used to capture attention, manufacture hope, and ultimately distract from the task of improving the safety, user-friendliness and utility of these systems. What’s worse, it worked. They brainwashed much of the industry to see blockchains as products in need of constant iteration, when precisely the opposite is the goal. But getting that point across has now become almost impossible. CKB was designed from the start to evolve without hard forks, to accommodate changing requirements without intervention from a specialized group of developers. We can all realize the potential of CKB today, and it’s important to start thinking in these terms.

Built on #CKB

If 80-90% of your networth is in crypto, you’re simply a retard

We recently announced the formation of the Common Knowledge Base Association, or CKBA. Naturally, there are questions. Why are we doing this? What are our plans? What does this mean for CKB? We’ll answer all of these in time. But before we do, it’s worth clarifying something important: These questions are loaded with assumptions about CKB and our relationship to it. The confusion is understandable. Somewhere along the way, the industry became comfortable treating blockchains like products—operated by companies. CKB is not that. CKB is public infrastructure—maintained and advanced by people who share a common set of ideas. Like Bitcoin, it is not dependent on, owned by, or controlled by any one entity. And that includes us. We’re old school; to us, a blockchain that can be halted, reorged, restarted, or have its assets seized by a controlling entity is not a blockchain. It may be marketed as one, it may be treated as one, the market may even believe it is one. But not us. To us, decentralization, security, immutability, and permissionlessness are non-negotiable. They are what make blockchains blockchains; everything else is a glorified database. So when we say that “CKBA is the new coordination layer for the CKB ecosystem,” we mean something that may surprise many people. Heavily inspired by Bitcoin, CKB is based on Nakamoto consensus. And, in Nakamoto consensus-based systems, there’s no (need for) coordination. They still produce order, but that order emerges from the behavior of independent and free entities that pursue their own incentives by following an optimal strategy introduced by the system’s constraints. In simple terms, CKB doesn’t need CKBA. The system works because everyone minds their own business, and everyone minds their own business because the system works. We have no control over that. CKBA operates somewhere else entirely: at the social layer. Our role is not to govern CKB; it’s to support the diverse and decentralized ecosystem of contributors around it. To coordinate resources, improve communication, support contributors, and help aligned people find each other. We’re a group of cypherpunks and misfits defined, perhaps most of all, by low time preference. This has its downsides—and it’s unfortunate that this has become a contrarian position—but for better or worse, we can’t help ourselves. We’re painfully aware that we’re building public infrastructure that should outlive us. And we’re not the only ones building. We have our vision and all, but we’re not calling the shots. If you don’t like our vision, impose your own. Build on CKB. Who’s stopping you? CKB will keep ticking, block by block, from one state transition to another, whether we’re here or not. Whether we, or you, approve of it or not. And if you are aligned with our vision, join us 👇 ckba.build/

New grant recipient, pay-per-read platform, desktop node tool, and privacy ideas continue to emerge across the Fiber ecosystem 🌱 - Grant Approved: Dular Connects Fiber to Mobile Money Infrastructure - Scryve Reads: A Live Demo of Pay-As-You-Read Content Streaming @ScryveHQ - Fiber Desktop: Simplifying Local Node Management - Proposal: Fiber Payjoin Kit for Native, Collaborative Privacy - Discussion: Mapping the LSP Link Between Bitcoin Lightning and Fiber Tracking the recent progress and new activities across Fiber community-led projects in Pulse 06: fiber.world/blog/pulse/issue…

⚠️ALERT: FT reports that the crypto industry is now bracing for quantum computing threat. Here's the brutal truth nobody in CT wants to hear: Only ~15 crypto projects on Earth are seriously building for quantum. If your favorite coin isn't one of them, you're holding a wallet with a death clock. The list 👇 PROTOCOL-NATIVE QUANTUM RESISTANT (mainnet, today): 🔷 QRL (XMSS, mainnet since 2018) 🔶 Abelian (lattice-based, mainnet 2022) 🔷 Cellframe (Dilithium Picnic) 🔶 Mochimo (WOTS , audited by Dr. Hülsing) 🔷 xx Network (David Chaum, PQ BFT consensus) 🔶 Nexus (FALCON Signature Chains) PQC LIVE IN PRODUCTION (partial): 🔷 Algorand — Falcon state proofs since 2022, first Falcon mainnet tx Nov 2025 (consensus still Ed25519) 🔶 Hedera — SEALSQ QS7001 chip, shipped Nov 2025 ACTIVELY IMPLEMENTING (testnet): 🔷 QANplatform — Dilithium, EVM-compatible testnet 🔶 Tron — QuantumShield hybrid signatures on testnet 🔷 Circle's Arc — USDC-native L1, opt-in Dilithium Falcon at mainnet (2026) ROADMAP ONLY (still vulnerable today): 🔷 Bitcoin — BIP-360 BIP-361 (7-year migration) 🔶 Ethereum — $2M PQ team, pq.ethereum .org, 2029 target 🔷 Cardano — IO Research "Vision 2026: Post Quantum Secure" proposal 🔶 Solana — Falcon roadmap (April 2026), Winternitz Vault live 2 yrs 🔷 Ripple/XRP — 4-phase roadmap, ML-DSA on AlphaNet, 2028 target Not listed = not building = your funds, eventually someone else's. Harvest now, decrypt later.

Another example of Nervos’ layered approach. RGB , inspired by its namesake, uses isomorphic binding to map Bitcoin UTXO’s to $CKB cells. This brings additional programability to Bitcoin, It also proves a pathway for other UTXO chains to interoperate the same way.

🔄 DAO Proposal Sync (Discussion Phase) Project: fiber-payjoin-kit - Collaborative Privacy for the Nervos Fiber Network Applicant: ILE Labs (Rust infrastructure team, 4 developers) Core deliverable: An open-source Rust library letting the receiver of a Fiber channel contribute input Cells to the funding transaction (Payjoin-style), aimed at breaking the common-input heuristic on CKB L1. Ships with a CLI, Fiber SDK integration, and a non-interactive fallback. Background: The applicant states the team maintains lightning-payjoin-kit for Bitcoin Lightning and is porting that architecture to CKB's Cell model. Discussion points: The community is asking whether lightning-payjoin-kit is itself finished, and how a delay on that upstream library would affect the Fiber port. Structure: 3 milestones over 10 weeks - core Rust port, Fiber SDK integration, CLI and docs. Budget request: $5,000 down payment (20%) $8,000 $8,000 $4,000 = $25,000 total, paid in CKB. Process status: Discussion Stage (7 days), 30 likes advances it to Voting Stage. Proposal link: talk.nervos.org/t/10296

1/5 When Fiber meets EV charging ⚡🚗 After exploring AI-powered "Chat-and-Pay" micropayments, developer Sonny Wu pushed Fiber into a new real-world scenario: EV charging in a real-time "Charge-as-You-Go" streaming experience. Why EV charging? It's a continuous action where costs accumulate in real time by energy consumed, perfectly fitting a "Pay-as-You-Use" streaming model. More importantly, it reveals the exact design details of Fiber Network that usually go unnoticed—multi-hop routing, hubs, and how they naturally emerge in a decentralized network.