Hi everyone,
I recently made Fiber Storybook, a small interactive demo that explains Fiber Network through Pico’s airport journey.
Preview: https://fiber-storybook-seven.vercel.app/
GitHub: GitHub - yfeng2824/fiber-storybook · GitHub
(A small note before you try it: the demo is currently best viewed on desktop. It works as a visual story, so making every scene feel good on smaller screens will take more layout work. I may work on a follow-up PR for responsiveness later.)
I wanted to make this because Fiber has a lot of interesting technical ideas, but I think some of its value is easier to feel through a simple everyday story. So instead of starting with payment channels, routing, or multi-asset swaps, I started with a familiar situation: Pico is at the airport.
Airports are full of small services. You might need a nap pod, luggage storage, or a massage chair before boarding. International travelers also naturally deal with different currencies and assets. That makes the airport a useful setting to explain what Fiber can improve.
The storybook currently has two chapters:
Chapter 1: Pay Only for What You Use
The first chapter is about streaming service at a nap pod. Today, many services still ask users to choose a fixed package: 30 minutes, 1 hour, 2 hours, and so on.
That works, but it can feel a little unfair. If Pico only sleeps for 17 minutes, paying for 30 minutes is not ideal. This kind of package model is often used because very small continuous payments are hard to make smooth with traditional payment systems. Card payments can have fixed transaction costs, and repeated checkout flows would feel terrible for users.
Fiber offers a different model. With Fiber, Pico can open a payment channel once. After that, the nap pod can update the payment off-chain while Pico is sleeping. When the session ends, the final result is settled. This makes pay-by-use services feel much more natural.
Chapter 2: One Pass for Multiple Services
Chapter 2 is about using one pass for multiple airport services. Today, many small services still feel like separate payment moments. Luggage storage may ask for one approval. A massage chair may ask for another. Different services might accept different assets. That works, but it can feel clunky. If Pico only wants to use a few small services before boarding, stopping each time to approve, confirm, and think about the right asset is not ideal. The services are simple, but the payment flow can become heavier than the actual experience.
Fiber offers a different model. With Fiber, Pico can open one payment channel to the Fiber Airport Pass. The pass acts like a hub node with routes and liquidity connected to different airport services. After that, Pico can use multiple services through the same pass, while Fiber routes the payments behind the scenes.
The asset part matters too. In the story, Pico has CKB. Luggage storage accepts CKB, so that part is straightforward. The massage chair accepts sats, so the hub bridges Pico’s CKB payment to a sats payment over a supported Lightning route. This is also the direction Fiber is actively moving toward: broader asset swaps, more flexible routes, and a smoother payment experience for users.
What I Hope This Shows
Fiber has many technical ideas behind it, but I think its value becomes easier to understand when we look at everyday situations.
With Fiber Storybook, I wanted to show what payments could feel like if they were smaller, smoother, and less interruptive. Of course, this is still a simplified demo. Some parts are based on the direction Fiber is actively moving toward, especially around broader asset swaps and cross-chain routing. But I hope the story makes the user experience easier to imagine.
I’d love to hear what you think. Feedback on the story, technical accuracy, or other real-world scenarios for Fiber would be very welcome. If there are other everyday payment problems where you think Fiber could help, please share them too. I might be able to turn those ideas into another Pico story.
