Game on! 🎮⚡ Integrate Fiber for real-time, gas-free micro-transactions. Instant payments, seamless gameplay

🚴‍♂️ Fiber Dev Log #2 🚴‍♂️ Still young, still growing! Here’s what’s been cooking in the past weeks: - Migration check tool: helps to determine whether a change needs a manual migration - RPC updates: new `list peer` added, unit tests & implementation - Better script parsing: now

👀 Fiber dev on stage, speaking fluent Lightning @ #HKWeb3Festival Web3Festival

Fiber v0.5.0 is released, including these breaking changes: - Type ID support for Fiber scripts & udt_whitelist dependencies - Empty cell_deps before computing signing messages - Channel RPC updates changed Release notes: github.com/nervosnetwork/… CKB DevRel CKB Dev↾⇃

🚴 Fiber Dev Log #3 🚴 Yes, we’ve seen your questions in the recent Nervos AMA on Reddit— “Is Fiber still alive?” “Why so quiet?” “Any actual updates coming?” Fair. We’ve been just building—and dropped Fiber v0.5, including: - breaking changes to contract behavior & config

georgie ↾⇃ No finished product yet—Fiber v0.5 is a protocol-level release. That said, we do plan to provide better docs and support for app/product builders. More on that soon. There’s already a demo game built on Fiber: fiber.world/docs/getting-s… Also, JoyID Passkey｜BTC⚡️ supports Fiber testnet—if

🚴 Fiber Dev Log 04 🚴 - Docs are updated for v0.5. Try it out and let us know what breaks: fiber.world/docs 😄 - v0.5.1 is on the way with some fixes & improvements. - We're also exploring atomic multi-path payments and getting Fiber to run in browser via WASM. Full log:

🚴 Fiber Dev Log 05 🚴 Hi, we know it’s been a while since our last update, and we really appreciate your patience and support! Just took some days off for the holiday and now back at it. 🏕️ Progress hasn’t been lightning fast, but we’re focused on getting things right. :)

Thank you for the question. Fiber focuses on protocol building, not products like a DEX for RGB++. That said, we provide the foundation for others to build, and we’d love to see something like that come to life!

🚴 Fiber Dev Log 05: WASM support is shaping up nicely on Fiber🚴 We’re working to get Fiber running in WASM environments, bringing better support across platforms. - WASM async-trait for Ractor and Stage 2 are under review - Stages 3 & 4 (DB support & unit tests) are in the

🚴 Fiber Dev Log 07 🚴Init Compatibility Check, Multi-Part Payments Support, and Audit Fixes We recently got the code audit report—been heads-down fixing issues and leveling up Fiber. A couple of updates from this sprint: - FeatureVector support is in. Nodes now exchange Init

Fiber's new docs site is live! docs.fiber.world — it's just the beginning, but we want to share the progress with you! Inside you'll find: - Documentation for quick start, tutorials, key concepts, and more - Blog for dev updates & blogs - Showcase for demos, tests,

🚴 Fiber Dev Log 08 🚴 Things are moving — here's the latest Still going through the audit feedback. Will keep posting updates here as we go. We're working on Multi-Part Payments (MPP) support, with several key components already in place — the HTLC attempt mechanism has been

Fiber Network on Nervos: Fiber Brings Lightning-Style Payments to $CKB FiberDevs

🚴 Fiber Dev Log 09 🚴 Time for another update — here's what we've been working on lately: WASM tests - Successfully completed pressure tests with 10,000 txs - Now building automatic testing scripts Multi-path payments (MPP) - Code is under review - More unit test coverage

🚴 Fiber Dev Log 10 🚴 We've added Biscuit auth to RPC server. Similar to macaroons, Biscuit enables fine-grained, distributed permission control. When the RPC binds to a public address, Biscuit-based authorization is now required to prevent unauthorized access. Multi-Path

🚴 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

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