FiberDevs

Building a scalable, privacy-by-default P2P payment & swap network⚡

[FiberDevs @FiberDevs]

Nice to see more Fiber projects moving from prototypes to public testing!

@ebubedev opened Twine's P2P trading app for testnet testing, @Code3ks opened the FiberNuts Community Market (and already shipped fixes based on feedback), and @truthixifi turned hackathon feedback into Fiber Forge v0.4.0, with new SDK, CI, and CCH testing tools.

Meanwhile, @Dean8IX shared new recovery evidence for FNN Safeguard, and @LusoCryptoLabs opened the Cellula Wallet testnet beta.

If you're trying out any of these projects, let the builders know what works or breaks, and what you'd like to see next!⚡
Catch up with the community in Pulse 17: https://t.co/jHQCMWYEMG

[FiberDevs @FiberDevs]

🚲 Fiber Dev Log 39 🚲
More groundwork for Fiber v0.10 this cycle, with improvements to database migration, payment settlement, and channel recovery.

Here's what's new:

- v0.10 migration: Database migration code has merged, helping existing channels retain their settlement format as Fiber moves toward v0.10.
- Payment handling: Forwarded payments are now kept separate from local invoices, preventing incorrect settlement updates.
- Channel V2: Work continues on signing and recovery, making it easier to resume interrupted channel operations.
- Hosted LSP: More progress on recovering interrupted updates, handling failed payments, and improving signer reliability.

Full dev log: https://t.co/TSH1tWDOPj

[CKB Dev↾⇃ @CKBdev]

A different kind of building at #CKCon 2026! 🇲🇾🌺
We're in Kuala Lumpur this week! Catching up, sharing ideas, and talking about what's next for CKB.

Great to hear updates and fresh ideas from people across the ecosystem, including @RunningCKB, @ckbsamurai, @JackyLHH, @aaaaaaaalive24, @kashortgirl, @aszepieniec, @teaplusplus11, @BitcoinLightApp, with @ebubedev and @rypto joining remotely. Lots of interesting work and discussions about what's next!

And finally we put the laptops aside and built miniature cities together. 🏙
Turns out we've got some pretty good city builders on the team too! 😄

[FiberDevs @FiberDevs]

Good ideas don't stop at the hackathon or the first grant.

We're seeing Fiber builders revisit earlier projects, try new things, and improve their work with feedback from the community:
Twine refined its P2P trading design after security feedback, FiberLatch extended its grant-funded work with a new FiberFlow integration, and FiberSurvivors turned a browser game experiment into a reusable Unity SDK.

⚡ See how these projects are evolving in Pulse 16: https://t.co/tkYaUx8Rtq

[FiberDevs @FiberDevs]

🚲 Fiber Dev Log 38 🚲
Quite a few practical fixes and improvements landed this cycle.

Fiber got better at recovering interrupted payments, dual-funded token channels picked up a round of fixes, and v0.10.0-rc1 is now available for testing.

There's also a new tutorial showing how an app can verify a result before releasing a payment.

Hosted Lightning Service Provider verification and v0.10 database migration are still in progress.

⚠️ If you're running an existing node, don't upgrade just yet. This RC still doesn't support older databases.

Full dev log: https://t.co/0pB7p5lo8J

[FiberDevs @FiberDevs]

Some ideas got tested in the real world. Some moved onto testnet. Some took a different turn entirely. 👀

Dular wrapped up its pilot after testing Fiber payments with 30 users in Kenya, FiberNuts (by @Code3ks) opened its Fiber + Cashu community market demo, and @LusoCryptoLabs tried using `.cell` names as human-readable Fiber payment endpoints.

There are also new experiments around P2P trading, payment + service delivery, and node recovery tools.

⚡ Catch up on what Fiber builders have been working on: https://t.co/1OXQPjiAz7

[FiberDevs @FiberDevs]

🚲 Fiber Dev Log 37 🚲

Fiber v0.9.1 is out, with another round node reliability improvements and bringing builders better hands-on learning resources.

This cycle brings:
Fiber v0.9.1 release: Fixes for payment settlement and more reliable channel closures.
Better diagnostics: Clearer error tracking for channel funding and adjustable node traffic limits.
New interactive tutorials: Hands-on labs for managing channel liquidity and building encrypted-data payments.

In the pipeline:
Continued progress on liquidity swaps (Loop In/Out) and Hosted Liquid Services Provider infrastructure.

Full dev log: https://t.co/xqKmkRUlJp

[FiberDevs @FiberDevs]

Hackathon's over, building definitely not. Ideas are bouncing between projects and winners keep evolving! 👀

We're seeing @ebubedev delivering beyond scope on Fiber Studio, @Code3ks refining the Cashu + Fiber, plus updates from CLASP's scoped, permissioned payments by @enochidx, and early prototypes & RFCs from @ILE_Labs on channel rebalancing and @midnightexplr on routed machine payment sessions.

⚡️ Catch up on what the community is building in Pulse 14: https://t.co/95Cqz5RwQN

[FiberDevs @FiberDevs]

🚴 Fiber Dev Log 36 🚴
Moving past the v0.9.0 release, this cycle covers release maintenance, creating better docs for builders, and laying the groundwork for the next batch of features.

This cycle brings:
- fiber-js default config for faster onboarding & fiber-pay v0.3.2
- Expanded docs w/ interactive tutorials for devs
- Ongoing designs for multi-tenant hosted LSP and liquidity management
- Listening on multi-address & QUIC support under review

Full dev log: https://t.co/TDb4aYezQU

[FiberDevs @FiberDevs]

The Fiber Infra Hackathon judging is finally over… and wow, there was a LOT to go through!
Huge thanks to neon @ckbsamurai and everyone who helped with the reviewing & evaluating!
Now find out what's been built and who took home the top spots among 66 projects 👀 🥳

@c_hongzhou and friends also unpacked where Fiber can make a real difference in the AI × machine payments landscape.

And don't forget to try the Fiber-style Counter-Strike! 🎮

Catch up on in the latest community projects update ↓
https://t.co/A9NhjB7SoJ

[FiberDevs @FiberDevs]

🚴 Fiber Dev Log 35 🚴
Post-v0.9.0, and the work keeps moving.

This cycle brings:
- Configurable peer-message rate limits
- fiber-pay moving to the stable v0.9.0 interface
- New interactive tutorials
- Liquidity management planning
- Multi-tenant hosted LSP design for mobile wallets

Full dev log ↓
https://t.co/VtVaWeJAQ5

[FiberDevs @FiberDevs]

Love seeing all the different ways the Fiber community is putting ideas into practice 💡
Collaborative channel funding (@ILE_Labs), Fiber Studio (@ebubedev), payment access control (@_ticoworld), cross-chain token swap, merchant payments, and more.
Check out what the community is building in Pulse 12: https://t.co/3loFQP06OK

[FiberDevs @FiberDevs]

Reading docs is helpful, but sometimes all you want is to run the thing. 🏃
So we made Fiber tutorials a little more hands-on.

Now you can: Start a WASM node in your browser → connect to a testnet peer → open a payment channel → send an off-chain payment.
Follow along with real code and real Testnet interactions.

Give it a try 👉 https://t.co/lXlemoJl2b
Behind the scenes 👉 https://t.co/az85O6igQh

[FiberDevs @FiberDevs]

🚴 Fiber Dev Log 34 🚴
v0.9.0 is live 🟢
After weeks of release hardening, the final milestone cleanup is complete, and Fiber v0.9.0 is released, making nodes more reliable, recoverable, and easier to operate.

Highlights:
- A unified database migration system with backup and restore support
- Stronger payment recovery with Cross-Chain Hub improvements
- More reliable reconnect and channel recovery flows
- Smoother node onboarding with new install and quick-start scripts

Full dev log: https://t.co/v7n5tltcxf

[FiberDevs @FiberDevs]

Great ideas are always worth learning from. ⚡️
Inspired by Lightning's WebLN, a new community experiment explores an important question:
When websites can request payments, how to make sure users remain in control?

A web payment interface is never just about making API calls easier. It also about building the right boundaries between websites and users:
→ What should a website be allowed to do?
→ Which actions need user confirmation?
→ How can users stay in control of their payment capabilities?

Fiber WebLN explores a browser-facing interface where websites can request: Fiber actions, while users decide what is allowed.
It creates a trust boundary between the page and the Fiber node: Fiber moves the money. Fiber WebLN governs how the web asks.
It also shows how different Fiber node setups can work through the same interface, so websites don't need to care where the user's node is running.

Try the demo: https://t.co/yWr90bIgdg
GitHub: https://t.co/60SxlSCFgb
Dev's thoughts: https://t.co/S4omYAqdg5

[FiberDevs @FiberDevs]

We're seeing so many cool ideas taking shape in our dev community recently 🛠️
Huge props to @NervosCatalyst for putting together the hackathon where 66 new open-source projects were born!
Check out the latest community projects update 👇https://t.co/ToxLlY1Hlk

[Common Knowledge Base Association (CKBA) @ckba_build]

Fiber is being built as an open network where people, businesses, applications, and machines can exchange value continuously, without a payment processor sitting at the center of every relationship.

In practice, that means creators can be paid as their work is consumed rather than waiting on monthly platform payouts.

Applications can charge a fraction of a cent per request instead of forcing subscriptions on occasional users. Devices can pay for the exact bandwidth or electricity they use, as they use it.

These are payments that card fees and per transaction settlement rule out today, and they become practical the moment value moves offchain and flows at internet speed.

How the network makes that possible 👇

https://t.co/MGRxWfQnXd

[Nervos Community Catalyst @NervosCatalyst]

The recent Fiber Network Infrastructure Hackathon yielded an unprecedented level of participation, with around 100 participants and 66 final submissions.

It might be a bear market, but developer activity on CKB and Fiber is surging. Read the full roundup and project summaries on Nervos Talk

https://t.co/uZr6bXxgpD

[FiberDevs @FiberDevs]

🚴 Fiber Dev Log 33 🚴
v0.9 is almost there — about 90% of the final milestone is done.
Over the past two weeks we've focused on release hardening: safer payments, smoother integrations, better tooling, and lots of edge-case fixes.

Highlights:
- CCH payment safety & recovery improvements
- Better operator-facing diagnostics and authorization reliability
- Continued gossip, channel recovery & release-hardening fixes
- Paying a Lightning invoice with CKB UDT via CCH Demo

Full dev log: https://t.co/VbJ4nyJcEY