Overview
A turbo channel (also called a zero-conf channel) is a Lightning Network channel that becomes usable immediately upon creation, without waiting for the funding transaction to be confirmed on-chain. Normally, a Lightning channel requires at least one on-chain confirmation (typically three or six) before it can route payments. Turbo channels bypass this waiting period by having the channel partner accept the risk of the unconfirmed funding transaction.
How It Works
Standard Channel Opening:
Fund Tx broadcast --> Wait for 3 confirmations --> Channel usable
(~30 minutes)
Turbo Channel Opening:
Fund Tx broadcast --> Channel immediately usable
(0 confirmations)
The trust model works because the party offering the turbo channel (typically a Lightning Service Provider, or LSP) is the one who created the funding transaction. Since they control the transaction, they know it is valid and are unlikely to double-spend their own funding transaction.
Trust Assumptions
Turbo channels involve an asymmetric trust relationship:
- The funder (usually an LSP) trusts that their own funding transaction will confirm. This is reasonable since they constructed it.
- The receiver trusts that the funder will not double-spend the funding transaction before it confirms. This trust is acceptable because the funder has a business reputation to maintain and the amounts are typically limited.
This is distinct from general zero-confirmation transactions on-chain, where the receiver has no relationship with or trust in the sender.
Use Cases
Turbo channels are particularly valuable for onboarding new Lightning users:
- A new user downloading a mobile wallet can receive a Lightning payment immediately through a turbo channel opened by the wallet's LSP.
- Lightning service providers use turbo channels to provide seamless "just-in-time" liquidity.
- Merchants can start receiving payments without waiting for on-chain confirmations.
Risks and Mitigations
The primary risk is that the funding transaction does not confirm (due to low fees or intentional double-spending). LSPs mitigate this by using appropriate fee rates, monitoring the mempool, and limiting the value of turbo channels. If the funding transaction is dropped, the channel ceases to exist and any routed payments through it could be lost.