|
| 1 | +--- |
| 2 | +title: From Protocol Completion to Real-World Usability |
| 3 | +description: Fiber 2025 Review & 2026 Outlook |
| 4 | +author: Quake |
| 5 | +date: 2026-01-22 |
| 6 | +--- |
| 7 | + |
| 8 | +Fiber has made significant strides over the past year. As we move further into 2026, it’s a good moment to reflect on what we accomplished in 2025 and share our plans for the year ahead. |
| 9 | + |
| 10 | +## Current Status |
| 11 | + |
| 12 | +Fiber has moved well beyond the design and single-channel validation stages. It is now protocol-complete, increasingly network-tested, and steadily moving toward broader integration and adoption. |
| 13 | + |
| 14 | +### Protocol Completion |
| 15 | + |
| 16 | +- The **full channel lifecycle** (open, update, close, and dispute) is defined. |
| 17 | +- **Multi-hop payments** across channels are supported at the protocol level. |
| 18 | +- **State commitment, forwarding rules**, and **failure handling** are specified with real network behavior. |
| 19 | + |
| 20 | +### Engineering Progress |
| 21 | + |
| 22 | +- A working Rust-based core implementation is in place. |
| 23 | +- Channel state machines and routing-related logic are implemented. |
| 24 | +- The corresponding on-chain contracts and scripts have been implemented to support channel settlement, state verification, and dispute handling. |
| 25 | + |
| 26 | +In addition, we have been running extensive multi-node, multi-hop network tests over the past year. These tests focused on realistic network scenarios and revealed real issues, including: |
| 27 | + |
| 28 | +- Fund safety edge cases |
| 29 | +- Performance bottlenecks under load |
| 30 | +- Node stability and recovery issues |
| 31 | + |
| 32 | +A significant portion of recent work has been dedicated to fixing these issues and hardening the system. As a result, Fiber is not just protocol-complete, but increasingly network-tested. |
| 33 | + |
| 34 | +## Positioning Fiber: Lessons from the Lightning Network |
| 35 | + |
| 36 | +To set expectations, it’s useful to compare Fiber’s development with that of the Lightning Network. |
| 37 | + |
| 38 | +Lightning went through several phases: |
| 39 | + |
| 40 | +1. A proposal |
| 41 | +2. Single channel implementation |
| 42 | +3. Multi-hop routing and real network engineering |
| 43 | +4. Broader wallet adoption and ecosystem maturity |
| 44 | + |
| 45 | +Fiber today is closer to Lightning’s early network phase. This means Fiber is beyond validating basic channel correctness — we are actively validating network behavior under realistic conditions. |
| 46 | + |
| 47 | +At the same time, we remain careful not to prematurely lock in higher-level assumptions. Lessons from Lightning remain valid: early decisions may impose long-term constraints. |
| 48 | + |
| 49 | +Our guiding principle is: **advance network capability while keeping the protocol flexible enough to evolve**. |
| 50 | + |
| 51 | +## Key Challenges |
| 52 | + |
| 53 | +Fiber’s progress has not been without hurdles. We are carefully managing two main areas: |
| 54 | + |
| 55 | +**Protocol complexity** |
| 56 | + |
| 57 | +Features like routing, multi-asset support, and watchtowers introduce significant complexity. We focus on stabilizing the core first before layering additional functionality. |
| 58 | + |
| 59 | +**Designing for a more expressive base layer** |
| 60 | + |
| 61 | +Unlike Bitcoin, CKB is Turing-complete, which gives us much more room to experiment. This also means assumptions from Bitcoin or Lightning do not always apply. We keep the protocol design and implementation flexible, avoiding patterns that might be unnecessarily restrictive. |
| 62 | + |
| 63 | +## 2026 Outlook: Bringing Fiber to Users |
| 64 | + |
| 65 | +Looking forward, our work focuses on three main areas: |
| 66 | + |
| 67 | +**Wallet Integration** |
| 68 | + |
| 69 | +We are actively integrating Fiber with JoyID, making Fiber usable for a real wallet. This helps validate our API design, UX assumptions, and end-to-end flow under realistic user scenarios. |
| 70 | + |
| 71 | +**Business-Facing Enablement** |
| 72 | + |
| 73 | +We will improve documentation and build demos to showcase Fiber’s advantages, particularly in scenarios such as high-frequency payments, low-latency interactions, and off-chain coordination that would be inefficient on-chain. |
| 74 | + |
| 75 | +These demos are not marketing material but concrete references that help wallets, developers, and potential partners understand when and why to use Fiber. |
| 76 | + |
| 77 | +**Liquidity Solutions** |
| 78 | + |
| 79 | +Liquidity remains a core challenge for both Lightning and Fiber. We will study and reuse the proven solutions from Lightning Network where applicable (e.g., channel management, rebalancing techniques, and liquidity pools). We will also explore Fiber-specific liquidity designs to see what works best in our environment. |
| 80 | + |
| 81 | +## Final Remarks |
| 82 | + |
| 83 | +2025 has been a year of solidifying Fiber’s foundation — from protocol design to real-world network testing. Building on this strong foundation, we are now focusing on real-world usability, developer enablement, and liquidity solutions. In 2026, we aim to bring Fiber closer to users, wallets, and developers while continuing to explore innovations that make off-chain payments more practical, efficient, and flexible. |
0 commit comments