Liquidity Triangle
A liquidity triangle is a three-node Lightning channel opening pattern that gives each participant balanced inbound and outbound capacity.
Key Takeaways
- A liquidity triangle is a coordinated channel opening pattern where three Lightning nodes each open a channel to the next in a loop, giving every participant both inbound and outbound liquidity from a single on-chain transaction.
- Triangles are more capital-efficient than acquiring inbound liquidity independently: each node funds one channel but receives channel capacity from two peers, doubling the connectivity per on-chain transaction.
- The pattern scales to larger rings (four, five, or more nodes) and is facilitated by coordination platforms like LightningNetwork.plus, though it requires all participants to fund on-chain transactions within an agreed timeframe.
What Is a Liquidity Triangle?
A liquidity triangle is a three-node channel opening arrangement on the Lightning Network. Node A opens a channel to Node B, Node B opens a channel to Node C, and Node C opens a channel back to Node A. The result is a closed loop where each participant has one channel with outbound capacity (the channel they funded) and one channel with inbound capacity (the channel funded by the node pointing at them).
This technique addresses one of the most persistent challenges in running a Lightning node: obtaining inbound liquidity. When a node opens a channel, all the capacity starts on its side as outbound liquidity. The node can send payments through that channel but cannot receive them until some capacity moves to the remote side. By coordinating with two other nodes in a triangle, each participant effectively trades outbound capacity in one direction for inbound capacity in the other.
The concept predates any single tool or platform. Early Lightning node operators organized triangles and larger rings informally through Reddit and Telegram groups. The community eventually coined the term "Ring of Fire" for these circular channel arrangements, with the triangle being the smallest and most common form.
How It Works
The mechanics of a liquidity triangle are straightforward, but the coordination requires all three participants to act within a reasonable window. Here is the process step by step:
- Three node operators agree on a uniform channel capacity (for example, 2,000,000 sats per channel) and a minimum channel duration (commonly 3 to 12 months)
- The participants are assigned a direction: A opens to B, B opens to C, C opens to A
- Each participant broadcasts an on-chain funding transaction to open their assigned Lightning channel
- Once all three funding transactions confirm, the triangle is complete
After the triangle is established, the channel balance state looks like this:
Node A:
Channel A→B: 2,000,000 sats outbound (A funded)
Channel C→A: 2,000,000 sats inbound (C funded)
Node B:
Channel B→C: 2,000,000 sats outbound (B funded)
Channel A→B: 2,000,000 sats inbound (A funded)
Node C:
Channel C→A: 2,000,000 sats outbound (C funded)
Channel B→C: 2,000,000 sats inbound (B funded)Each node committed one on-chain transaction worth 2,000,000 sats but gained two channels and two peers. Without the triangle, achieving the same inbound capacity would require either purchasing it through a marketplace like Liquidity Ads, performing a Loop Out operation, or waiting for another node to open a channel to you organically.
The Coordination Process
Platforms like LightningNetwork.plus (LN+) streamline the coordination. A typical swap listing specifies:
- Channel capacity (the amount each participant must commit)
- Minimum channel duration (how long channels must remain open)
- Participant requirements (minimum existing channels, total node capacity, uptime)
- Connection preferences (Tor-only, clearnet, or hybrid)
Once all three slots fill, the platform assigns the direction of channel openings and notifies participants. Each operator then opens their channel, and the platform tracks completion by detecting funding transactions on-chain.
Scaling to Larger Rings
The triangle is the smallest ring topology, but the same principle extends to four, five, or more nodes. A ring of N nodes creates N channels, with each node gaining one outbound and one inbound channel. Larger rings increase the number of unique peers each participant connects to, improving the node's position in the network graph and potentially attracting more routing fees.
However, coordination difficulty grows with ring size. If any single participant fails to open their channel, the ring is broken and the other participants have outbound channels that do not return inbound capacity as expected. Triangles strike a balance between connectivity gains and coordination overhead.
Why It Matters
Inbound liquidity is the bottleneck for new Lightning nodes. A freshly launched node can open channels and send payments, but it cannot receive payments until it has remote balance in at least one channel. This creates a chicken-and-egg problem: merchants need inbound capacity to accept payments, but established nodes have little incentive to lock up capital in channels to unknown peers.
Liquidity triangles solve this through mutual benefit. Each participant pays the same cost (one on-chain transaction plus the locked capital) and receives the same reward (inbound capacity from another participant). No one needs to trust a counterparty with funds: the channel openings are independent on-chain transactions, and each participant retains full custody of their sats within the channel.
From a network-wide perspective, triangles improve capital efficiency. Instead of three nodes each independently seeking inbound liquidity (potentially through expensive submarine swaps or marketplace purchases), a single coordinated action bootstraps bidirectional capacity for all three. This makes the Lightning Network more connected and reduces the tendency toward hub-and-spoke centralization, since smaller nodes can peer directly with each other rather than relying solely on large routing hubs.
For a deeper look at how inbound capacity affects node economics, see the research article on inbound liquidity acquisition costs.
Use Cases
New Node Bootstrapping
The most common use case is bootstrapping a new routing node. A fresh node has zero inbound capacity. Joining a triangle immediately provides inbound liquidity from one peer and a routing path through two peers. Many node operators join multiple triangles during their first week to build a diverse set of channels quickly.
Routing Node Expansion
Established routing nodes use triangles to expand their peer set efficiently. Opening a channel to a well-connected node is useful, but if that node does not reciprocate, you gain only outbound capacity. A triangle guarantees inbound capacity from at least one new peer, making the capital expenditure more predictable.
Circular Rebalancing Paths
Once a triangle is established, the closed loop enables circular rebalancing. A node can send a payment to itself around the triangle to shift liquidity from one channel to another without spending on-chain fees. For example, if Node A's outbound channel to B becomes depleted, A can route a self-payment A → C → B → A to push sats back to the A→B side.
Community and Geographic Clustering
Groups of node operators in the same region or community often form triangles to create low-latency, high-capacity paths between their nodes. This is especially useful for merchant networks in the same city or country, where most payments flow between local participants.
Risks and Considerations
Coordination Failure
The primary risk is that one or more participants fail to open their channel. If Node C never opens the channel back to Node A, then A has outbound capacity to B but no inbound capacity from the triangle. The committed on-chain fees are spent regardless. Coordination platforms mitigate this with reputation systems and participant requirements, but enforcement is limited to social pressure and platform bans: there is no on-chain mechanism to force a participant to open a channel.
Early Channel Closure
Even if all channels open successfully, a participant may close their channel before the agreed duration. This breaks the ring and reduces the other participants' inbound capacity. Dual-funded channels and channel leases (via Liquidity Ads) offer more enforceable commitments, but standard triangle swaps rely on voluntary cooperation.
On-Chain Fee Costs
Each participant must broadcast a funding transaction, which means paying on-chain fees. During periods of high fee market activity, the cost of opening a channel can be significant relative to the channel capacity. Timing triangle openings during low-fee periods (weekends, off-peak hours) can reduce costs substantially.
Liquidity Imbalance Over Time
Even a perfectly balanced triangle becomes imbalanced as payments flow through it. If most payments route in one direction, channels will deplete on one side and saturate on the other. Maintaining balance requires active management through circular rebalancing, Loop operations, or adjusting routing fees to incentivize traffic in the depleted direction.
Alternatives to Consider
Liquidity triangles are one of several approaches to the inbound liquidity problem. Other options include Liquidity Ads (on-chain enforceable channel leases), splicing (adding funds to existing channels), and sidecar channels (third-party-funded channels). Layer 2 protocols like Spark avoid the inbound liquidity problem entirely by using a different architecture that does not require pre-funded bilateral channels.
This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.