🚴Fiber Dev Log 30🚴
Recent work has focused mainly on reliability, security hardening, and edge-case handling as we move toward the v0.9 release.
That work is reflected in v0.9.0-rc2, including updates around migrations, funding persistence, parsing, routing behavior, and channel handling.
We're also continuing review and polish work around trampoline routing, forwarding behavior, amount validation, browser integrations, and developer tooling/docs.
This stage of the release cycle has focused more on improving behavior under failure cases and long-running operation than on introducing major new features.
Full dev log: 👇
https://t.co/6rkWYGUuLB
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: https://t.co/XTuRNNcHmd
5/5 Ready to see it in action? Claim your free test tokens from the CKB Testnet Faucet, fund your browser channel, and watch the live payment routing in action:
💻 Demo: https://t.co/5QtzLPaEtM
📦 GitHub: https://t.co/WK9EXGLqEn
🧠 Developer's notes: https://t.co/oj1epAz82r
🤖The earlier Chat-and-Pay demo: https://t.co/bxUxoUZRyl
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.
4/5 Fiber's value proposition isn't just "faster" or "cheaper" transactions. It's reinventing payments all together, making business models like "Pay-as-You-Use"—nearly impossible in Web2—practical for the first time.
When payments no longer depend on third-party services, approvals, delays, or meaningful per-transaction costs, and settlement becomes near-instant while users retain control of their funds, "Pay-as-You-Use" become viable at scale.
Experience the story (best on desktop):
https://t.co/jv3r3u9YDu
Yuqi's previous demo Echo:
https://t.co/xP8EiCwp8j
Creator's notes:
https://t.co/9v1Ym44V4L
Our UX designer Yuqi just published another interactive walkthrough. Follow Pico the duck through an airport and you'll see two of the things payment channels are actually good at:
1. Pay-by-the-minute via off-chain channels.
Pico naps for 20 minutes and pays for 20 minutes. The payment updates off-chain while he's napping and settles when he wakes; no fixed packages and no minimum charges.
2. Asset-agnostic routing through a single payment hub.
Pico's luggage storage accepts CKB; the massage chair accepts sats. He pays once and Fiber handles the liquidity routing and asset swaps in the background.
Both are hard and more expensive to do on traditional payment rails, which is exactly what Fiber's payment-channel architecture is built for.
It's the same technical move told through airport scenery, and that's the point: Yuqi's strength is making hard ideas legible.
🚴Fiber Dev Log 29🚴
We're moving through the v0.9.0 release cycle, with Fiber v0.9.0-rc1 out. This brings together updates across routing, funding, transport, and overall stability.
This release candidate also introduced a unified migration system, laying a clearer framework for future database and protocol upgrades.
We also improved the Network Actor stability, with updates to keep channel actors alive across peer disconnects.
Better observability is also now in place with the addition of debug and trace logs throughout the channel funding flow.
Community feedback continues to be a big help! Input from the WASM testnet recently helped us catch and fix an invoice payment rejection case involving zero-balance channels. Thanks to the community member who reported it.
Moving forward, our focus shifts more on security hardening and finalizing the x402 end-to-end flow.
Full log: https://t.co/Pjwoa7FPBg
Happy to see Fiber Link move from engineering prototype to product-ready!
It's now a fully deployable community tipping layer over CKB, allowing members to support each other without running their own nodes.
Product overview: https://t.co/RqQp80QUGJ
Fiber-Pay v0.2.5 also keeps evolving—simpler connect flows, passkey support, new demos, and AI agent use cases.
🏗️ More community-led experiments on Fiber here in Pulse 05: https://t.co/g0HHi35ROR
Call remote AI agents from your browser. P2P Decentralized. Passkey login.
And settled instantly and trustlessly via Fiber. ⚡️🔐
Try it out: https://t.co/MPGkIH90SB
This is a recent experiment by Retric, exploring what AI services could look like when agents are independently hosted, directly callable, and paid peer-to-peer.
The current pay-per-call model keeps things simple as a fixed-fee entry point, as low as 0.1 CKB per call on the Fiber testnet. Further plan includes transitioning to a more granular, token-based pricing (metering input/output usage).
And if you're curious about why and how this was built, here's the write-up: https://t.co/pJ4AgEzciq
#fibernetwork #nervos #AgenticEconomy
Fiber is moving from protocol ideas to real applications. Retric's been one of the builders exploring that shift firsthand.
If you're curious about how Fiber actually works for real-world apps, hit the link and ask away! https://t.co/U1yUUfQH4F
AMA time again! This time with Retric from the DevRel team 🛠️
Retric has been part of Nervos' journey since the early days of CKB. Lately he's been building fun experiments on Fiber, such as Fiber Audio Player (a self-hosted podcast with streaming micropayments) and Fiber L402 (L402 paywall demo).
Got any questions about CKB, Fiber, developer tooling, or what it's really like building these? Drop your questions on Reddit! https://t.co/IMSUNoNDl2
and we'll see you on May 12th 👋
@FiberDevs #ckb #nervosnetwork #fibernetwork
🚴 Fiber Dev Log 28 🚴
Sharing a few things we've been working through lately:
- Expanded Connectivity: added official Docker image support, plus Onion & Socks5. Also introduced transport type filtering to the connect_peer RPC, giving nodes more control over how they connect.
- x402 & Preimage Proofs: Fiber can now act as an x402 exact-payment backend. It verifies paid invoices and returns deterministic receipts via the RPC HTTP listener.
- Unified Migration Design: framework is now done. This is a key prerequisite for v0.9.0 and should make future protocol + database upgrades much smoother.
Right now we're shaping up v0.9.0 (bringing in that Migration Support) and working through CCH multi-asset swap implementation.
Also, great catching up with everyone at #Bitcoin2026 — heading back now and keeping pushing toward v0.9.0. 🚴
Full dev log: https://t.co/ENTYbrylw3
Back at our small booth on Day 2 of #Bitcoin2026
Good to see more builders stopping by and chatting!
Our friends from @Nervapes are still hanging out in the area—WAGMI!! 🦍🏴☠️
Dropping some more recent shots on site. 📸
#FiberNetwork#Nervos#BTC2026
Finally got a moment to post about Day 1 at #Bitcoin2026! 😅
Booth is small and a bit messy, but we've had the best time talking with everyone who stopped by!
Our neighbor @Nervape sent over their mascot to steal the spotlight. 🏴☠️🦍
Huge thanks to everyone who came to see us today. If you're in Vegas, come to Booth K4 and say hi tomorrow! ⚡️
#nervos #bitcoin2026 #lightningnetowrk