FiberDevs's avatar
FiberDevs
npub1fxq5...tahv
Building a scalable, privacy-by-default P2P payment & swap network⚡
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 4 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 5 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 6 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 6 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 7 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.
FiberDevs's avatar
FiberDevs 8 months ago
🚴 Fiber Dev Log 15 🚴 Hey folks, here's what we've been working on over the past two weeks: - Cross-chain multi-hop payments are now completed. - Atomic multi-path payments (AMP) are fully designed and implemented. AMP improves on the current MPP (multi-path payments), where all shards share the same payment hash, making individual paths easy to correlate and prone to partial settlement. With AMP, a payment either settles in full or not at all, even when routed across multiple paths. - Fiber Dashboard APIs now let you monitor the full lifecycle of channels. For ongoing work, we're exploring liquidity solutions, analyzing payment scenarios, and investigating long-running tasks in Fiber's actor model using metrics. Also extending support for new contracts and continuing to track down other performance bottlenecks. The full log:
FiberDevs's avatar
FiberDevs 1 year ago
What is Fiber and Why Does It Matter? 👇 1/ What is Fiber Fiber is a privacy-by-default, scalable network for fast, low-cost payments and swaps between digital assets. Aligned with Bitcoin’s principles, Fiber connects peers decentrally, ensuring security and efficiency without external consensus or centralized validation. 2/ What makes Fiber different? - Beyond channel network like Lightning, Fiber natively supports stable-coin payment and assets swap, unlocking new Bitcoin-based financial use cases. - Unlike sidechains and rollups, Fiber is not a chain. It scales off-chain with Bitcoin-aligned decentralization, privacy, and security, while achieving high efficiency without relying on external trust assumptions or complex cryptographic proofs. 3/ Why Fiber matters: - Bitcoin-aligned: Expands Bitcoin’s use cases while staying rooted in its decentralization principles. - Lightning-compatible: Works seamlessly with Lightning while adding flexibility and multi-asset support for payments & swaps. - Privacy-by-default & Efficient: No network-wide consensus; transactions are only visible to involved parties and settle quickly via direct peer-to-peer communication. 4/ Features rundown: - Multi-asset support: Supports stablecoins, RGB++ assets on the Bitcoin ledger, and UDT assets on CKB. - Ultra-low fees: Micropayments as small as 0.0001 cents, with fees as low as 0.00000001 cents. - Instant asset swaps: Swap any asset pair as long as a channel path is available. - Cross-network payments & swaps: Seamless transactions between the Lightning Network and Fiber. - Watchtower support: Helps node operators monitor and secure the network. - Multi-hop payments: Run a Fiber node and earn fees by facilitating payments. - Low latency: Transactions process with minimum delay (e.g., 20ms for 0.0001 cent payments). - High throughput: Transactions handled by involved peers without requiring network-wide consensus. - Enhanced privacy: Transactions are only visible to involved peers. - Advanced cryptography: Uses PTLC instead of HTLC for stronger security and privacy. - Composable with CKB Scripts: Integrates with other contracts and Scripts on CKB.
FiberDevs's avatar
FiberDevs 1 year ago
🚀 Fiber is live on mainnet! Fiber v0.4.0 marks the first-ever Mainnet deployment of the Fiber contract, with two bootnodes set up. An updated contract is also deployed on Testnet. ⚠️ Security audit in progress—start with small amounts when testing! This release includes multiple bug fixes and improvements. Check the full details & share your feedback: Let’s scale P2P finance together! 💙