Nostr notes by FiberDevs

🌊The last two weeks brought a wave of new projects, with more ...

2026-04-13T06:55:35Z

🌊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: https://www.fiber.world/blog/pulse/issue-03

While the Fiber Dashboard shows you that Fiber is alive, Echo ...

2026-04-03T10:02:22Z

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: https://echo-web-eight-alpha.vercel.app
Designer's note: https://talk.nervos.org/t/echo-a-sonic-and-visual-demo-for-fiber/10152
GitHub repo: https://github.com/yfeng2824/echo

🚴 Fiber Dev Log 26 🚴 We're moving toward the v0.8.0 ...

2026-04-02T06:46:59Z

🚴 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: https://github.com/nervosnetwork/fiber/discussions/1243
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: https://github.com/nervosnetwork/fiber/discussions/1245

⚡️Builders lead. Community ships. Tracking the latest ...

2026-03-30T03:59:14Z

⚡️Builders lead. Community ships.
Tracking the latest contributions driving Fiber forward in Pulse.
Explore Issue #02 →
https://x.com/FiberDevs/status/2038465810994442571

New UI ✨ Aligned with Fiber's DNA: calm, precise, and ...

2026-03-27T01:31:16Z

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: https://fiber.world/docs/how-it-works
Designer's Note: https://talk.nervos.org/t/fiber-website-docs-update/10132

We shipped Fiber Dashboard. Why? Because we kept getting asked: ...

2026-03-19T02:41:57Z

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: https://dashboard.fiber.channel
and the notes from one of the builders: https://talk.nervos.org/t/fiber-network-dashboard/10105

🚴Fiber Dev Log 24 🚴 A major focus recently has been on ...

2026-03-05T03:47:31Z

🚴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: https://github.com/nervosnetwork/fiber/discussions/1170

Just dropped two demos showing how Fiber eliminates trust ...

2026-02-27T03:13:40Z

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!
https://github.com/quake/fiber-demo

Fiber v0.7.1 just dropped. We've introduced observable ...

2026-02-26T12:20:20Z

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: https://github.com/nervosnetwork/fiber/releases/tag/v0.7.1

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: https://github.com/nervosnetwork/fiber/discussions/1149

🚴Fiber Dev Log 22 🚴 We're getting v0.7.0 ready, with ...

2026-02-05T09:40:06Z

🚴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: https://github.com/nervosnetwork/fiber/discussions/1104

🚴 Fiber Dev Log 21 🚴 Just dropped the latest dev log: ...

2026-01-22T08:08:24Z

🚴 Fiber Dev Log 21 🚴
Just dropped the latest dev log: https://github.com/nervosnetwork/fiber/discussions/1072

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 👇
https://talk.nervos.org/t/fiber-protocol-complete-network-tested-development-status-challenges-and-2026-outlook/9827/2

🚴 Fiber Dev Log 20 🚴 We've been working on making ...

2025-12-25T04:20:13Z

🚴 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 👇
https://github.com/nervosnetwork/fiber/discussions/1024

Just got back from CKCon in beautiful Chiang Mai🌴! Our dev ...

2025-12-09T08:59:30Z

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://fiber-world.vercel.app/simulate.html

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

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.

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: https://github.com/nervosnetwork/fiber

Here is the full presentation from the Chiang Mai talk CKB Fiber Network Engineering Updates: https://docs.google.com/presentation/d/1aKhG0ebR-UV4SqOWOd_Xjlz15hGVmmRUMLzIkwcUWeY/edit?usp=sharing

Wonderful to be back in Chiang Mai — great energy at this ...

2025-12-02T15:39:59Z

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. ⚡🤝

🚴 Fiber Dev Log 18 🚴 Multi-hop payments and hold-invoice ...

2025-11-13T02:41:06Z

🚴 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 👉 https://notion.so/cryptape/Survey-Liquidity-Solutions-for-Fiber-Report-2778f0d3781e80aa9c5ef75a1fb7e8dc?source=copy_link
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: https://github.com/nervosnetwork/fiber/discussions/951

🚴 Fiber Dev Log 17🚴 In this sprint, much of the work went ...

2025-10-30T05:35:52Z

🚴 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: https://github.com/nervosnetwork/fiber/discussions/940

By the way, we've heard the community wondering what's going on with Fiber. More details coming soon.

🚴 Fiber Dev Log 15 🚴 Hey folks, here's what we've ...

2025-10-02T05:24:03Z

🚴 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: https://github.com/nervosnetwork/fiber/discussions/920

🚴 Fiber Dev Log 13 🚴 We just dropped Fiber v0.6.0-rc4 — ...

2025-09-04T07:51:48Z

🚴 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 fuzz testing are also more reliable.

On the performance side, payment hop data deserialization is now faster. 🚀

Coming up next:
- Fiber v0.6 stable release — right around the corner.
- Ongoing work on multi-hop cross-chain payments
- Planning support for disabling intermediate hops

Full dev log: https://github.com/nervosnetwork/fiber/discussions/882

🚴 Fiber Dev Log 12 🚴 Our recent work has centered on ...

2025-08-21T08:52:52Z

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

And Fiber 0.6.0-RC 2 is ready: https://github.com/nervosnetwork/fiber/releases/tag/v0.6.0-rc2

Looking forward, we're working on Atomic Multi-Path Payments (MPP) and continuing DAO discussions.

Dev log: https://github.com/nervosnetwork/fiber/discussions/848

🚴 Fiber Dev Log 11 🚴 Time again to share what we've ...

2025-08-21T08:52:29Z

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

On the infrastructure side, Watchtower RPC has been improved.

We also fixed several important bugs related to TLC handling, invoice timeouts, and peer dialing issues in Tentacle. Benchmark testing has been stabilized, and some MPP and WASM bugs were addressed, too.

We've been teaming up with JoyID and #USDI to unlock more possibilities together.

Check out the full devlog for the details: https://github.com/nervosnetwork/fiber/discussions/823

🚴 Fiber Dev Log 10 🚴 We've added Biscuit auth to RPC ...

2025-07-24T11:17:20Z

🚴 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 Payments (MPP): Fixed concurrency bugs, node restart, and stress test issues. Sending is stable now.

Also improved panic handling in Fiber WASM runtime.

Check out for the full log: https://github.com/nervosnetwork/fiber/discussions/795

🚴 Fiber Dev Log 09 🚴 Time for another update — here's ...

2025-07-10T07:05:28Z

🚴 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 coming up next

Performance & stability
- Fixed bottlenecks during stress tests
- Tackled channel disconnect issues

🩵 And major shout-out to Magickbase for building the Fiber Explorer: https://github.com/Magickbase/fiber-explorer

They've got graph queries working, and a web UI for local node management is on the way, which will support channel management, transaction history, payments and invoice sharing, etc.

We're excited to see tools like this taking shape — and we'd love to see more teams join in and build on Fiber.
Let's grow the ecosystem together 💪

Full update here: https://github.com/nervosnetwork/fiber/discussions/779

🚴 Fiber Dev Log 08 🚴 Things are moving — here's the ...

2025-06-26T08:42:58Z

🚴 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 refactored, held HTLC settlement is implemented, and path-finding has been improved.

Meanwhile, the IndexedDB implementation for Fiber WASM and cross-chain support for multi-hop payments are both in active testing and review.

Security-wise: added limits to accepted channels and fixed an issue involving mismatched channel IDs.

Full dev log: https://github.com/nervosnetwork/fiber/discussions/753

Fiber's new docs site is live! https://docs.fiber.world — ...

2025-06-20T01:35:33Z

Fiber's new docs site is live! https://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, references, and other tools

We built this site to make it easier for dApp developers to explore, learn, and build on Fiber.

It will keep growing — and so will the network.
A thriving ecosystem needs both a solid foundation and creative applications. As infrastructure developers, we’re here to support your ideas and learn from what you’re building.

Got feedback, ideas, or something cool in the works?
Let's build together ⚡️

🚴 Fiber Dev Log 07 🚴 Init Compatibility Check, Multi-Part ...

2025-06-12T08:12:33Z

🚴 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 messages and check for feature compatibility before opening channels—this helps make connections safer and more reliable.
- Basic Multi-Part Payments (MPP) support has landed. It now covers path-finding, HTLC hold settlement, and a refactored attempt mechanism.
And we're continuing work on more advanced MPP features.

Full log: https://github.com/nervosnetwork/fiber/discussions/735

🚴 Fiber Dev Log 05: WASM support is shaping up nicely on ...

2025-05-29T12:25:16Z

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

More in dev log: https://github.com/nervosnetwork/fiber/discussions/721

And it’s great to see teams like JoyID (https://joy.id)
building on Fiber--their Fiber testnet is coming soon!
Glad to support them and excited to see more teams testing, building, and growing together! 🦾

🚴 Fiber Dev Log 05 🚴 Hi, we know it’s been a while since ...

2025-05-15T04:12:28Z

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

Here’s what we’ve been up to:
- Fiber v0.5.1 is out, fixing connection retries and channel reestablishment for a more reliable experience.
- We’ve also completed the initial work for Fiber WASM migration.
Meanwhile, Watchtower is being refactored into a standalone service with WASM compatibility, making it more modular and adaptable.
Plus, work on multi-hop cross-chain features is back on track to enhance interoperability between blockchains.

Full log: https://github.com/nervosnetwork/fiber/discussions/704

🚴 Fiber Dev Log 04 🚴 - Docs are updated for v0.5. Try it ...

2025-05-01T02:02:54Z

🚴 Fiber Dev Log 04 🚴
- Docs are updated for v0.5. Try it out and let us know what breaks: https://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: https://github.com/nervosnetwork/fiber/discussions/690

🚴 Fiber Dev Log #3 🚴 Yes, we’ve seen your questions in ...

2025-04-17T03:32:25Z

🚴 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 files
- upgrades on performance, Watchtower, and channel handling.
➡️ The dev log: https://github.com/nervosnetwork/fiber/discussions/668

Thanks to everyone in the community asking questions and following along!🩷
We're here NOT to chase trends or flood the timeline with hype, but for the long game—scalable, privacy-by-default P2P finance on the #Bitcoin principles.

Fiber v0.5.0 is released, including these breaking changes: - ...

2025-04-14T01:56:08Z

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: https://github.com/nervosnetwork/fiber/releases/tag/v0.5.0

🚴‍♂️ Fiber Dev Log #2 🚴‍♂️ Still young, still ...

2025-04-03T08:48:05Z

🚴‍♂️ 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 supports Type ID and UDT cell_dep

Full dev log: github.com/nervosnetwork/fiber/discussions/632

Thanks to everyone following along! 🙌

🪵 Hi folks, we’re kicking off Fiber’s bi-weekly dev log ...

2025-03-20T02:30:46Z

🪵 Hi folks, we’re kicking off Fiber’s bi-weekly dev log series! This is where we’ll keep you posted on what we’ve been building. And we’d love to hear your feedback and see what you’re trying out.
First update here: https://github.com/nervosnetwork/fiber/discussions/604

Before the launch, we shared dev logs alongside CKB's—now Fiber has its own.
You can find the pre-mainnet logs compiled here: https://github.com/nervosnetwork/fiber/discussions/601

🧪 We've open-sourced a testnet demo for setting up and ...

2025-03-14T01:44:15Z

🧪 We've open-sourced a testnet demo for setting up and testing Fiber on a CKB-based testnet!
Whether you're curious about Fiber or ready to build on top of it, this hands-on guide covers:

- Compile and run Fiber nodes
- Connect to a Lightning Network LSP node
- Establish multi-hop payment channels (similar to how the LN routes payments)
- Transfer CKBytes and UDT (user-define tokens) over Fiber
- Close channels and finalize transactions

Try it out and let us know what you think! Feedback is always welcome 🙌
🔗 ENG: https://github.com/sunchengzhu/fiber/blob/develop/docs/testnet-nodes.md
🔗 CHN: https://github.com/sunchengzhu/md/blob/main/docs/fiber-testnet.md

👀 And for a quick peek, real-time info of nodes, channels, and paths are visualized here: http://16.162.99.28:8120/view.html
🚧 Note: This is a temporary dev tool. A more polished one coming soon

👷 While we’re working on Fiber’s documentation, here’s ...

2025-03-07T03:39:30Z

👷 While we’re working on Fiber’s documentation, here’s something for those who love digging into the technical details!
Written by the dev team, we unpack Fiber’s architecture, key modules, and future plans—with source code explained: https://yakihonne.com/naddr1qvzqqqr4gupzqjvpfs8lg4k8nale070cppm4z2rg70fz8z6h7ly7uucgnded2n4pqq2k7wzytfx4x3m4dar9ynpk0ycygdmp94kk7lagk77

What is Fiber and Why Does It Matter? 👇 1/ What is Fiber Fiber ...

2025-03-01T01:07:46Z

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.

🚀 Fiber is live on mainnet! Fiber v0.4.0 marks the first-ever ...

2025-02-28T14:42:44Z

🚀 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: https://github.com/nervosnetwork/fiber/releases/tag/v0.4.0

Let’s scale P2P finance together! 💙

Hello, World? Or more like, Hello, Web 5! ⚡ This is Fiber ...

2025-02-26T16:23:16Z

Hello, World? Or more like, Hello, Web 5! ⚡

This is Fiber Network—not a rollup, not a sidechain, but a channel network taking another shot at scaling Satoshi’s P2P eCash vision!

Fully Lightning-compatible and enhanced with new features, Fiber brings fast, flexible, and efficient off-chain transactions for multi-asset payments to the Bitcoin ecosystem.

Stay tuned for updates and insights as we keep building!

#LightningNetwork #Bitcoin #nervos #ckb #utxo #web5