@FiberDevsi
iAccount based inUnited States!
About this account
- Account based in
- United States
- Connected via
- China Android App
! X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
Building a scalable, privacy-by-default P2P payment & swap network⚡
Joined February 2025
- Tweets122
- Following14
- Followers558
- Likes66
🚲 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: github.com/nervosnetwork/fib…
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: fiber.world/blog/pulse/issue…
🚴 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: github.com/nervosnetwork/fib…
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 ↓
fiber.world/blog/pulse/issue…
🚴 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 ↓
github.com/nervosnetwork/fib…
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: fiber.world/blog/pulse/issue…
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 👉 fiber.world/docs/build/inter…
Behind the scenes 👉 talk.nervos.org/t/from-readi…
🚴 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: github.com/nervosnetwork/fib…
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: fiber-webln-docs-mu.vercel.a…
GitHub: github.com/HappySonnyDev/fib…
Dev's thoughts: talk.nervos.org/t/from-webln…
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 👇fiber.world/blog/pulse/issue…
FiberDevs retweeted
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 👇
nervos.org/knowledge-base/wh…
FiberDevs retweeted
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
talk.nervos.org/t/gone-in-60…
🚴 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: github.com/nervosnetwork/fib…
We are seeing a range of ideas taking shape in our dev community recently:
Streaming micropayments. AI-powered developer learning. RGB++ swaps. A Fiber–Lightning cross-chain demo. A liquidity marketplace. A WooCommerce payment plugin... just a snapshot 👀
Check out the latest community projects update 👇
fiber.world/blog/pulse/issue…
Devs are already hacking machine-native commerce on Fiber.
AI agents paying for API calls, pay-as-you-use streaming payment, metered inference, L402 paywalls...
If you're building any of this, Fiber is ready to handle it.
Wintermute is right. The machine economy won’t run on payment infrastructure designed for humans.
Machines will not fill out checkout forms or wait days for transactions to settle. They need to exchange value continuously and globally: paying per API request, per second of compute, per unit of energy, or whenever another machine completes a task.
It may begin with something as simple as one piece of software paying another for a single API call.
An agent purchasing data. A model paying for inference. A vehicle paying for electricity as it charges. A device buying bandwidth for the next ten seconds.
Millions of tiny economic interactions happening too quickly, too frequently, and in amounts too small for traditional payment rails.
Much of the infrastructure required to support this still needs to be built. But we are not starting from zero.
We believe next-generation payment channel networks like Fiber will provide the rails agents and machines use to transact autonomously.
Fiber combines Lightning-style speed and efficiency with multi-asset support and CKB’s programmability. It can support stablecoins and other assets, atomic swaps, conditional settlement, streaming payments, and more complex payment logic directly within channels.
That makes it better suited to a machine economy where agents may need to exchange assets, pay only when a task is completed, or stream value continuously as a service is consumed.
Developers are already using Fiber to experiment with machine-native commerce: autonomous agents paying for onchain data through x402, AI agents paying to call other agents, agent discovery, task-based settlement, and agent-to-agent marketplaces.
Other experiments include L402-style paywalls, metered AI inference, per-second streaming payments, escrow through hold invoices, and EV charging where payment flows alongside the energy being consumed.
The Fiber team is also working to integrate x402 more deeply into the network, allowing Fiber nodes to handle the payment flow from an HTTP 402 response through invoice payment, proof generation, verification, and settlement.
In simple terms, we are building the kind of payment infrastructure the machine economy will need.
Of course, Fiber does not solve the entire stack. Identity, reputation, service discovery, permissions, pricing, and legal and moral accountability remain open problems.
But the machine economy will not emerge from a single application, protocol, or blockchain. It will be an open stack built across AI, robotics, crypto, energy, connectivity, and payments.
The payment rails are already taking shape.
To the teams building the agents, APIs, devices, marketplaces, and services that will inhabit this economy: Fiber is an open environment where you can start testing it today 👇
fiber.world/
talk.nervos.org/
🚴 Fiber Dev Log 32 🚴
Still in v0.9 release-hardening mode.
Prioritized reliability, improved payment safety, fixed edge cases, and smoothed out the developer experience to get the final v0.9.0 release ready.
Key updates:
- Shipped v0.9.0-rc5, rc6, rc7
- Backup & restore landed, giving node operators a critical recovery capability—huge thanks to our community contributor for making it happen 🥳🙌
- Faster WASM and gossip sync
- Better CCH reconciliation and payment safety
- More robust watchtower and actor failure handling
- New Fiber Foreign Function Interface (FFI) docs for embedding Fiber into mobile and desktop apps
Thanks to everyone testing, reviewing, and reporting issues. It makes a real difference.🙏
Full dev log: github.com/nervosnetwork/fib…
Building real utility means hitting real roadblocks 🚧.
Love seeing how the Fiber community is navigating these hurdles head-on and keeping the momentum going:
- Fiber Desktop hit Milestone 2, bringing end-to-end testnet payments to a full desktop UI.
- Dular is working through production USSD challenges while refining its architecture with community feedback.
- Fiber-pay shipped v0.2.7, adding support for FNN v0.9, and launched a developer landing page.
New proposals are exploring a native Python SDK (Fiber Python SDK) and AI-powered developer education (VibeQuest). FiberLatch Access also builds on its earlier CKBuilders project (by @NervosCatalyst), now moving towards its DAO funding phase.
Read the latest community projects update 👇
fiber.world/blog/pulse/issue…
🚴 Fiber Dev Log 32 🚴
Getting Fiber ready for v0.9 ⚡
This cycle was all about release hardening. We shipped v0.9.0-rc4 and spent most of our time improving reliability, security, and stability across channels, watchtowers, routing, funding flows, and developer tooling.
Shipped:
• Fiber v0.9.0-rc4
• Security hardening across gossip, RPCs, and channel validation
• More reliable channel funding and recovery handling
• Watchtower stability improvements
• CCH payment and routing improvements
• fiber-js and npm release improvements
Polishing a few final pieces before v0.9 lands 🏁
Full dev log: github.com/nervosnetwork/fib…