Bridge Node (Lightning)

A bridge node is a Lightning node that maintains channels across what would otherwise be disconnected segments of the Lightning Network graph - acting as connective tissue between regions of nodes that wouldn't have direct routing options without it.

In practice, "bridge node" overlaps heavily with "routing node" - the distinction is more about position in the network topology than about role. A node with many high-capacity channels connecting otherwise sparsely-connected parts of the gossip graph is a bridge whether or not it advertises itself that way.

Who runs bridge nodes:

• Commercial routing operators. River, Voltage, hosted-Lightning services, and dedicated routing-as-a-business operations. They optimize for fee revenue and uptime.
• Major exchanges and Lightning service providers. Coinbase, Strike, Cash App run large Lightning infrastructure for their own user flow plus opportunistic routing.
• Power users with serious capital. Some self-custody operators run substantial routing nodes essentially as a hobby with positive expected return.

What bridge nodes earn vs. cost:

• Routing fees - small per-payment, but at scale across thousands of daily payments, real revenue.
• Capital costs - BTC locked into channels can't be spent or staked elsewhere. The opportunity cost matters.
• Operational costs - server uptime, monitoring, liquidity rebalancing, watchtower services.

The economics for bridge nodes have been tight historically. Some operators run them profitably; others run them at marginal cost to support the network. Either way, well-connected bridge nodes are part of what makes Lightning's routing reliable - a sparsely-bridged graph means more failed payments.

See Lightning Routing for how bridge nodes get used and Lightning Node for the broader landscape.