Common Knowledge Base Association (CKBA) (@ckba_build): While Fiber and Lightning are two separate payment channel networks, we figured there doesn’t need to be a hard boundary between them.

While Fiber and Lightning are two separate payment channel networks, we figured there doesn’t need to be a hard boundary between them. Fiber’s Cross-Chain Hub can connect the two and let payments move atomically across both networks. Here’s how it works 👇 A hub operator runs a node on Fiber and a node on Lightning, maintaining liquidity on both sides. If you want to pay a Lightning invoice from Fiber, you send a conditional payment to the hub. The hub then uses its own BTC liquidity to pay the recipient over Lightning. The same process works in reverse for payments coming from Lightning into Fiber. Crucially, these are not two unrelated payments. Both sides are tied to the same payment hash. Lightning uses an HTLC, while Fiber uses its own time-locked contract. When the recipient claims the outgoing payment, they reveal a secret preimage that also allows the hub to claim the incoming payment. So the hub can’t simply take your payment and fail to settle the other side. Its ability to collect is cryptographically linked to successful settlement of the outgoing payment. If the payment never completes, the timelocks provide a recovery path for the locked funds. Currently, the Cross-Chain Hub supports one configured pairing: a wrapped-BTC token on Fiber ↔ BTC on Lightning. Support for native CKB and other user-defined tokens is in the works :) 👉 https://www.fiber.world/