FiberDevs's avatar
FiberDevs
npub1fxq5...tahv
Building a scalable, privacy-by-default P2P payment & swap network⚡
FiberDevs's avatar
FiberDevs yesterday
Call remote AI agents from your browser. P2P Decentralized. Passkey login. And settled instantly and trustlessly via Fiber. ⚡️🔐 Try it out: 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: #fibernetwork #nervos #AgenticEconomy
FiberDevs's avatar
FiberDevs 5 days ago
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!
FiberDevs's avatar
FiberDevs 1 week ago
🚴 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:
FiberDevs's avatar
FiberDevs 2 weeks ago
Heading to Bitcoin 2026 ✈️ First time attending—excited to be there! 🤩 Stop by Booth K4 if you want to chat about: - Payment channels beyond Lightning - Programmable off-chain execution (--not just payments) - Autonomous AI agents x Off-chain payments - Multi-asset payment channels interoperable with Lightning Or just swing by, say hi, and grab a flyer. Vegas soon 🫡 📆April 27–29 📍Booth K4, The Venetian Expo #Bitcoin2026 #FiberNetwork #Nervos #LasVegas #CKB
FiberDevs's avatar
FiberDevs 3 weeks ago
🌊The last two weeks brought a wave of new projects, with more builders stepping in to try things out (shout out to NervosCatalyst for hosting the hackathon 🫡) Beyond the hackathon, projects keep evolving and shipping: - Fiber Checkout is live for web apps. - Fiber Link is now open for public testing - Fiber Audio Player brings pay-per-second audio to the browser - Fiber Pay: v0.2.1 makes AI payments even simpler Check out Pulse 03 to see the community innovations:
FiberDevs's avatar
FiberDevs 1 month ago
While the Fiber Dashboard shows you that Fiber is alive, Echo gives that quietness a pulse—letting you experience the network through motion, rhythm, and sound. 🎶😌 Vibe-coded by our UI designer (who also designed the Fiber Dashboard—and sings great karaoke😍), Echo is a visual and sonic take on network liveness. As for the name, an echo only exists when there's connection, response, something beyond yourself. That felt right for Fiber. A network only becomes alive when people join, connect, and interact. Sense Fiber's pulse: Designer's note: GitHub repo:
FiberDevs's avatar
FiberDevs 1 month ago
🚴 Fiber Dev Log 26 🚴 We're moving toward the v0.8.0 release and have been working on: - Upstream Ractor Integration: Switched to the upstream Ractor implementation to keep things clean and standardized. - Privacy Boost: Onion + SOCKS5 routing is well underway - Stability & Protection: Improved gossip protocols and new inbound/reconnect protections to keep the network resilient against resource-heavy peers. We're also in research for agent payment flows and shared a deeper look into CCH (Cross-Chain Hub)—the bridge for atomic BTC ↔ CKB swaps: We're moving from simple 1:1 swaps to a multi-asset future with P2P negotiation and LND-style swap acceptors. The CCH plan is open for discussion! Check out the full dev log:
FiberDevs's avatar
FiberDevs 1 month ago
New UI ✨ Aligned with Fiber's DNA: calm, precise, and credible. Landing Page - Interactive Node Graph: Click to trace multi-hop routing paths. - Live Stats: Real-time protocol data integrated. Visual Simulators in Docs - Payment Channels: Open a channel & lock funds on-chain to enable off-chain txs. - Multi-hop Routing: Payment traversing multiple nodes to reach the receiver. - Interactive Network Simulation: See L1 & L2 activities in action. Check it out Site: https://fiber.world Docs—How it works: Designer's Note:
FiberDevs's avatar
FiberDevs 1 month ago
We shipped Fiber Dashboard. Why? Because we kept getting asked: "Is Fiber dead?"/"Anything actually happening?"/"Hello??" ...fair questions, honestly. Fiber is running, but to most people, it's just invisible. Data is scattered across on-chain txs and individual nodes, with no unified view. Getting a clear picture of the real state has always been a challenge. We believe a truly usable L2 shouldn't just live in code, logs, or RPC interfaces. It should be seen, understood, and trusted. So here is the dashboard, a real-time view of the network: node distribution, channel activity, overall health, etc. Now check out what's happening on Fiber: and the notes from one of the builders:
FiberDevs's avatar
FiberDevs 2 months ago
🚴Fiber Dev Log 24 🚴 A major focus recently has been on channel reliability. We've hardened our TLC settlement handling to prevent duplicate states and dangling TLC in invoice flow. Also persisted the TLC commitment replay state so channel recovery after restarts is deterministic, preserving strict replay ordering. On the architecture side, we're splitting core types into standalone crates like fiber-types and fiber-json-types. This means: - Developers can reuse Fiber's protocol, channel, payment, and invoice data structures without embedding a full node - Easier SDK and tooling integration for external Rust projects Also working on external wallet signing, where users can keep keys securely in their own wallets while still using Fiber channel workflows. Check out the full breakdown in the DevLog:
FiberDevs's avatar
FiberDevs 2 months ago
Just dropped two demos showing how Fiber eliminates trust dependencies by routing payments directly between nodes. 🚀 A fully decentralized architecture where the backend never touches user funds: 🎮 fiber-game: P2P wagering where an Oracle + adaptor signatures act as the ultimate ref. The winner claims the pot directly. Zero intermediary custody. 🤝 fiber-escrow: Escrow without escrow agent. Payments are held by the network via Hold Invoices, released on delivery, and arbitrated if things get weird. You can launch both demos locally with a single command!
FiberDevs's avatar
FiberDevs 2 months ago
Fiber v0.7.1 just dropped. We've introduced observable channel opening and improved network safety with configurable CORS and smarter balance checks to catch payment issues before they start. 🚀 v0.7.1 Release note: It's the follow-up to the major work of the previous version 0.7.0. This release brings significant structural changes, including trampoline routing and improved data privacy for debug outputs. We managed to boost payment performance by about 60% this time—mostly by being more efficient with how we handle secp256k1 contexts and pathfinding. Beyond routing, we've also overhauled the Cross-Chain Hub (CCH) with a proper finite-state machine to make order handling much more resilient. It feels good to see these architectural pieces finally click into place! You can check out the full breakdown in the DevLog:
FiberDevs's avatar
FiberDevs 3 months ago
🚴Fiber Dev Log 22 🚴 We're getting v0.7.0 ready, with one-way channels and trampoline routing. Here's a quick look at what's new in Fiber over the past two weeks: Trampoline routing payments are now merged and coming in the next release. Instead of calculating the entire payment route upfront, senders only need to reach a trampoline node. From there, the rest of the route is carried hop-by-hop inside an inner onion. The receiver only sees their own payment — nothing about the path it took. The result is simpler routing, better privacy, and fewer failure points as the network scales. Path finding got faster. We discovered that path finding was slowed down by repeated pubkey comparisons. Each comparison triggered expensive serialization work, and since routing checks many channels, this overhead added up quickly. By switching to map-based lookups and storing already-serialized pubkeys, we replaces the sequential iteration with map indexing. The result: 10x faster with map indexing, plus 2x faster with serialized pubkey storage. For a deeper dive into all the changes and fixes, take a look at the full dev log:
FiberDevs's avatar
FiberDevs 3 months ago
🚴 Fiber Dev Log 21 🚴 Just dropped the latest dev log: In this sprint, we shipped v0.6.1 and finished the draft implementation of two new features: one-way channels and trampoline routing — both are now under testing. Most of the other work went into corner cases, concurrency fixes, Cross-Chain Hub order persistence, and some dashboard improvements as well. Also linking the 2025 review & 2026 outlook here, in case you missed the Nervos Talk post 👇
FiberDevs's avatar
FiberDevs 4 months ago
🚴 Fiber Dev Log 20 🚴 We've been working on making payments, cross-chain swaps, and the dashboard more reliable and maintainable: ・Payment Actor Decoupling We identified a performance bottleneck in the path routing algorithm that could block the Network Actor. To address this, we moved the send payment logic into a dedicated Payment Actor. This decoupling ensures that routing and payment execution no longer delay core network message processing. Additionally, we improved the performance of the MPP routing algorithm. ・Cross-Chain Hub (CCH) CCH has been refactored around a clear FSM-based architecture, making order handling and state transitions deterministic and easier to reason about. Backend-specific effects (Fiber/LND payments, invoice tracking, settlement) are now properly encapsulated and driven by persisted actions instead of ad-hoc handlers. We also strengthened input validation for cross-chain swaps, adding checks for expiry timing, hash consistency, and invoice compatibility to prevent unsafe or failing swaps early. This improves correctness, reliability, and debuggability across the CCH flow. ・Other improvements Dashboard backend updated for new frontend structure, more logging added for debugging, and routing logic is being fine-tuned for flexibility and scalability. Full dev log & PRs here 👇
FiberDevs's avatar
FiberDevs 5 months ago
Just got back from CKCon in beautiful Chiang Mai🌴! Our dev gave a talk on Fiber and hacked an interactive visual simulation to show how it works. If you couldn't make it, below is a shorter version. But first, try playing with the dots yourself! 👉 image ## Why Layer 1 Isn't Enough We all love Layer 1 blockchains like Bitcoin or CKB for their security, but let's be honest: they aren't exactly built for speed. Every transaction has to be shouted out to the entire world and written down by thousands of nodes. On CKB, you're waiting about 8 seconds for a block; on Bitcoin, it's 10 minutes! Plus, the fees can get nasty if you're just trying to buy a coffee. ☕️ So how to fix this? ## Lightning Network 101 The Lightning Network is a scalable, low-fee, and instant micro-payment solution for P2P payments. The secret sauce isn't actually new. Even Satoshi Nakamoto hinted at this "high-frequency" magic in an early email: "Intermediate transactions do not need to be broadcast. Only the final outcome gets recorded by the network." (https://gnusha.org/pi/bitcoindev/CANEZrP2PEB8n_Ov1bXi_ZoAkLwfz7_JtM9PPHr+8ei5KCgwdEg@mail.gmail.com/) A Lightning Network consists of Peers and Channels. A peer can send, receive, or forward a payment. A Channel is used for communication between two peers. image Imagine you and a friend want to trade money back and forth quickly: 1. Opening the Channel: You both put some money into a pot and sign a Funding Tx. This goes on the blockchain (L1). 2. The Fun Part (Off-Chain): Now that the channel is open, you can send money back and forth a million times instantly! You just update the balance sheet between you two (using HTLCs and signatures). No one else needs to know, and no blockchain fees are paid yet. 3. Closing the Channel: When you're done, you agree on the final balance, sign a Shutdown Tx, and tell the blockchain. Everything in the middle? That's off-chain magic. ✨ ## The Power of the Network Now, if Fiber was just about paying your direct neighbor, it would be boring. The real power comes from the Network. image This means Alice can pay Bob even if there's no direct channel between them. The payment can travel through one or more intermediate nodes. As long as there is a path with enough liquidity, the payment will reach its destination instantly. All data is wrapped in Onion Packets (yes, like layers of an onion). The nodes in the middle serve as couriers, but they are blindfolded: - They don't know who sent the money. - They don't know who is receiving it. - They only know "pass this to the next guy." They simply follow a basic rule: they forward the Hash Time Lock, and if the payment succeeds, they earn a tiny fee for their trouble. Easy peasy. ## The Not-So-Easy Part 😅 While the idea is simple, building it is... well, an engineering adventure. We're dealing with cryptography, heavy concurrency, routing algorithms, and a whole jungle of edge cases. But hey, that's what makes it fun! We've poured the last two years into building Fiber, and I'm proud to say it’s finally GA-ready. If you want to geek out on the details, check these out: - Mastering the Lightning Network (https://github.com/lnbook/lnbook) and Basis of Lightning Technology (https://github.com/lightning/bolts) - Fiber's GitHub: Here is the full presentation from the Chiang Mai talk CKB Fiber Network Engineering Updates:
FiberDevs's avatar
FiberDevs 5 months ago
Wonderful to be back in Chiang Mai — great energy at this year's CKCon! 😎🥥 Our Fiber dev presented the latest engineering updates, and it's always a joy to reconnect with other Nervos teams and share what we've been building. ⚡🤝
FiberDevs's avatar
FiberDevs 5 months ago
🚴 Fiber Dev Log 18 🚴 Multi-hop payments and hold-invoice are now supported in the Cross Chain Hub, making payment routing and tracking smoother. We also put out a Liquidity Solutions Survey, going through 11 approaches for improving liquidity in Fiber. After evaluating them, we found: - 4 solutions that work well for Fiber: Submarine Swaps, Liquidity Ads, JIT Channels, and a Liquidity Pool Marketplace -- Each with different trade-offs between flexibility, complexity, and user experience. - Three others (Shaduf++, Cycle, and Split) remain on watchlist as we keep exploring. The full report is available online 👉 Always open to feedback or discussion! We also fixed performance issues found in large-scale tests, improved observability, and finalized the dashboard UI design. Next up: Fiber v0.6 with HTLC RPC and extended test coverage. Full dev log:
FiberDevs's avatar
FiberDevs 6 months ago
🚴 Fiber Dev Log 17🚴 In this sprint, much of the work went into tasks such as refactoring multi-hop cross-chain payments, single-funded channels, and performance improvements ☕🍵☕🍵 Some features are complex and security-sensitive, so extensive tests and audits are necessary 🛡️ Meanwhile, research continues on liquidity solutions, concurrent payment issues, and memory/CPU usage in large-scale tests. Progress is happening on Fiber Dashboard, profiling support, and networking metrics ✅ Checkout the dev log: By the way, we've heard the community wondering what's going on with Fiber. More details coming soon.