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! 👉 https://t.co/xAOuNLya0X

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. ⚡🤝 Thanks @RunningCKB @matt_bitcoin @c_hongzhou

🚴 Fiber Dev Log 19 🚴 Quick rundown of what we've been building this sprint: Cross-Chain Hub (CCH) can now to process multi-hop payments directly. We've unified order management: SendBTC and ReceiveBTC orders are now a single CCH Order, simplifying BTC-CKB swaps. We've also

If the text style looks off for you on X, please check here:

🧪 Curious how Fiber handles liquidity? Here's a complete survey of all the solutions we've reviewed and what we plan to implement. Surveyed Solutions 01 Shaduf++ Paper: Shaduf++: Non-Cycle and Privacy-Preserving Payment Channel Rebalancing ( https://t.co/VpERzMD8Lm) The

🚴 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,

What's Up with Fiber? A Status Check-In Lately, we've seen some folks in the community wondering about Fiber's recent progress. Fair question. Payment channel networks are one of the toughest areas in blockchain — progress doesn't always make headlines. Fiber kicked off in June

🚴 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

🚴 Fiber Dev Log 16 🚴 A quieter sprint for releases, as we focus on polishing and testing under the hood. ⚒️👷 We've been revisiting multi-hop cross-chain payment logic and experimenting with max-flow algorithms for smarter multi-path payments (MPP) routing. On the atomic

🚴 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

🚴 Fiber Dev Log 14 🚴 Last two weeks have been busy — and Fiber v0.6.0-rc5 is now out with a big focus on stability and reliability. We've spent time on large-scale testing and fixed watchtower log issues, RPC timeouts, and tweaked payment expiry defaults. We've also improved

🚴 Fiber Dev Log 13 🚴 We just dropped Fiber v0.6.0-rc4 — getting closer to the stable 0.6. ⚡ Atomic MPP (multi-path payments) is now in! On the bug fix side, we tackled issues like channels getting stuck or payment failures not being logged properly. TLC expiry checks and

🚴 Fiber Dev Log 12 🚴 Our recent work has centered on reliability — more end-to-end testing for funding tx verification, better shutdown handling, and perf improvements. The Cross-Chain Hub (CCH) got a major update too: it now runs independently with persistent state storage.

🚴 Fiber Dev Log 11 🚴 Time again to share what we've been working on in the last sprint: Core WASM support is complete, and the Fiber dashboard backend is underway with four basic APIs already ready. Multi-Part Payments support has been merged and will be released after