<p>Alex Bosworth discusses different kinds of routing nodes he has observed on the network in this <a href="https://diyhpl.us/wiki/transcripts/lightning-hack-day/2021-03-27-alex-bosworth-lightning-routing/" rel="nofollow noreferrer">presentation</a> at a Lightning Hack Day in March 2021. He classifies them as follows:</p>
<ul>
<li>Ping Pong Routing Node (Bi-Directional Payments)</li>
<li>Liquidity Battery Routing Node (Slow Ping Pong Payments)</li>
<li>Inbound Sourcing Routing Node (Provide Liquidity to Drains)</li>
<li>Liquidity Trader Routing Node (Predict the Future, Provide Reliability)</li>
<li>Last Mile Routing Node (Connect Users to the Network)</li>
</ul>
<p>A <strong>ping pong routing node</strong> stays balanced due to routing regular bidirectional payments and only requires operational costs. It avoids the fees required to rebalance channels. In reality, these are rare as there are at least delays between the bidirectional payments and hence periods where channels aren't balanced.</p>
<p>A <strong>liquidity battery routing node</strong> is more common as it routes bidirectional payments but encounters time delays and periods where channels aren't balanced. It needs sufficient capital to withstand these periods and avoid being drained. Due to the higher capital requirements they potentially have the opportunity to charge higher fees than <strong>ping pong routing nodes</strong>. These routing nodes also require monitoring of onchain fees to determine when it is affordable to use the chain to rebalance their channels.</p>
<p>An <strong>inbound sourcing routing node</strong> seeks opportunities to consistently provide liquidity to drains (ie exhausting their inbound capacity with regularity). Capital is only flowing in one direction and this routing node has to manage that and actively rebalance. However, this routing node does get to identify stable routing opportunities with medium fees where there is demand to route to the drains (e.g. merchants) and potentially buy channel capacity to serve periods of increased demand.</p>
<p>A <strong>liquidity trader routing node</strong> is the most opportunistic of routing nodes as it moves around the network opening channels or buying channel capacity in the short term to take advantage of information that isn't publicly available. It chases high routing fees and hence is information intensive as well as channel management intensive. If its information isn't accurate it risks making higher losses as the costs of channel opening and purchasing liquidity mount up.</p>
<p>A <strong>last mile routing node</strong> actively tries to connect end users to the Lightning Network rather than being one of the central nodes in the route. These routing nodes need to understand and monitor what the end users' needs are because otherwise they risk their capital being stuck in a channel that isn't being regularly utilized (i.e. no routing fees). It is also critical (even more so than for other routing nodes) that these routing nodes are online 24/7 as they may be the end users' only connection to the rest of the network.</p>
<p>(Being an effective routing node and generating profits from being a routing node is challenging and especially when starting out one should see it as experimentation rather than an investment with reliable returns. Do not experiment with more funds than you can afford to lose.)</p>
<p>In addition ZmnSCPxj <a href="https://lists.linuxfoundation.org/pipermail/lightning-dev/2022-June/003617.html" rel="nofollow noreferrer">posted</a> to the lightning-dev mailing list in June 2022 on different strategies for Lightning forwarding/routing nodes.</p>

CC BY-SA 4.0
2021-05-04T15:53:59.553Z
doing research in this topic I was already surprised by the question and what one would answer. Even though the answer comes from some source I find this a bit arbitrary and opinionated
Rene Pickhardt
CC BY-SA 4.0
2021-05-04T16:00:52.973Z
Interesting. You don't like Alex's classification? Obviously it isn't scientific/academically rigorous but I found it useful as a framing for how to think about the different kinds of routing nodes. Feel free to post an alternative answer :)
Michael Folkson
CC BY-SA 4.0
2021-05-04T15:34:17.843Z
2022-07-11T18:33:55.747Z
2022-07-11T18:33:55.747Z
Michael Folkson
<p>I understand that there are end users at the edge of the network (typically with private channels) and routing nodes (with public channels) doing the routing of payments. What are the different kinds of Lightning routing nodes?</p>

<lightning-network><lightning-routing>
What are the different kinds of Lightning routing nodes?
Michael Folkson
# What are the different kinds of Lightning routing nodes?

(Asked by: username_0 on 2021-05-04)

I understand that there are end users at the edge of the network (typically with private channels) and routing nodes (with public channels) doing the routing of payments. What are the different kinds of Lightning routing nodes?

**Tags:** lightning-network, lightning-routing


---

## 1 answers

### Answer by username_0 on 2021-05-04. Score: 1 | Accepted answer

Alex Bosworth discusses different kinds of routing nodes he has observed on the network in this [presentation](https://diyhpl.us/wiki/transcripts/lightning-hack-day/2021-03-27-alex-bosworth-lightning-routing/) at a Lightning Hack Day in March 2021. He classifies them as follows:

* Ping Pong Routing Node (Bi-Directional Payments)
* Liquidity Battery Routing Node (Slow Ping Pong Payments)
* Inbound Sourcing Routing Node (Provide Liquidity to Drains)
* Liquidity Trader Routing Node (Predict the Future, Provide Reliability)
* Last Mile Routing Node (Connect Users to the Network)

A **ping pong routing node** stays balanced due to routing regular bidirectional payments and only requires operational costs. It avoids the fees required to rebalance channels. In reality, these are rare as there are at least delays between the bidirectional payments and hence periods where channels aren't balanced.

A **liquidity battery routing node** is more common as it routes bidirectional payments but encounters time delays and periods where channels aren't balanced. It needs sufficient capital to withstand these periods and avoid being drained. Due to the higher capital requirements they potentially have the opportunity to charge higher fees than **ping pong routing nodes**. These routing nodes also require monitoring of onchain fees to determine when it is affordable to use the chain to rebalance their channels.

An **inbound sourcing routing node** seeks opportunities to consistently provide liquidity to drains (ie exhausting their inbound capacity with regularity). Capital is only flowing in one direction and this routing node has to manage that and actively rebalance. However, this routing node does get to identify stable routing opportunities with medium fees where there is demand to route to the drains (e.g. merchants) and potentially buy channel capacity to serve periods of increased demand.

A **liquidity trader routing node** is the most opportunistic of routing nodes as it moves around the network opening channels or buying channel capacity in the short term to take advantage of information that isn't publicly available. It chases high routing fees and hence is information intensive as well as channel management intensive. If its information isn't accurate it risks making higher losses as the costs of channel opening and purchasing liquidity mount up.

A **last mile routing node** actively tries to connect end users to the Lightning Network rather than being one of the central nodes in the route. These routing nodes need to understand and monitor what the end users' needs are because otherwise they risk their capital being stuck in a channel that isn't being regularly utilized (i.e. no routing fees). It is also critical (even more so than for other routing nodes) that these routing nodes are online 24/7 as they may be the end users' only connection to the rest of the network.

(Being an effective routing node and generating profits from being a routing node is challenging and especially when starting out one should see it as experimentation rather than an investment with reliable returns. Do not experiment with more funds than you can afford to lose.)

In addition ZmnSCPxj [posted](https://lists.linuxfoundation.org/pipermail/lightning-dev/2022-June/003617.html) to the lightning-dev mailing list in June 2022 on different strategies for Lightning forwarding/routing nodes.

> **Comments:**
> **username_1**: doing research in this topic I was already surprised by the question and what one would answer. Even though the answer comes from some source I find this a bit arbitrary and opinionated  
> **username_0**: Interesting. You don't like Alex's classification? Obviously it isn't scientific/academically rigorous but I found it useful as a framing for how to think about the different kinds of routing nodes. Feel free to post an alternative answer :)  

---

