<p>I suggest we say channel balance instead of channel state (the state is encoded by a signed  commitment TX and if it leaks you could loose your funds)</p>

<p>As for the balance such a dilemma indeed exists. Indeed routing becomes more trial and error without public channel balances. Yet, there will probably be methods that allow to predict routes with higher probability. </p>

<p>On the other hand, there is not only the privacy aspect speaking against public channel balances. One would have to announce every balance update to the network which happens for every payment and  would result in an infeasible high payload of gossip messages.</p>

CC BY-SA 4.0
2019-01-11T14:27:09.107Z
2019-01-12T14:40:09.087Z
2019-01-12T14:40:09.087Z
Rene Pickhardt
<p>To add to Rene’s answer: The protocol design currently allows the probing of viable paths to leak just enough information to let you determine whether all channels along route provide adequate liquidity or not, without revealing the individual channel balances.</p>

<p>Note though that one could use probing (receiver and sender controlled by same individual) with different routes and amounts to derive/compute the exact or approximate liquidity in a given channel of interest.</p>

CC BY-SA 4.0
2019-01-11T15:07:25.300Z
However, this is only reveals the liquidity that a channel node is willing to offer for routing. There is nothing in the protocol that enforces a node to offer all its liquidity for routing.
James C.
CC BY-SA 4.0
2019-01-11T15:03:23.947Z
2019-01-12T14:41:23.900Z
2019-01-12T14:41:23.900Z
James C.
<p>I've heard that there is such a dilemma for LN: if channel states were not published, the payer will not able to find any viable path, unless he takes brute-force-like probing approach (which looks quite unscalable); if the channel states were meant to published, the economic privacy of LN users would be sacrificed.</p>

<p>Does such dilemma exist? If such idea is wrong, why?</p>

<lightning-network><privacy><lightning-routing>
Is there actually a dilemma of whether or not to publish channel states for LN nodes?
Chris Chen
# Is there actually a dilemma of whether or not to publish channel states for LN nodes?

(Asked by: username_0 on 2019-01-11)

I've heard that there is such a dilemma for LN: if channel states were not published, the payer will not able to find any viable path, unless he takes brute-force-like probing approach (which looks quite unscalable); if the channel states were meant to published, the economic privacy of LN users would be sacrificed.

Does such dilemma exist? If such idea is wrong, why?

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


---

## 2 answers

### Answer by username_1 on 2019-01-11. Score: 3 | Accepted answer

I suggest we say channel balance instead of channel state (the state is encoded by a signed commitment TX and if it leaks you could loose your funds)

As for the balance such a dilemma indeed exists. Indeed routing becomes more trial and error without public channel balances. Yet, there will probably be methods that allow to predict routes with higher probability.

On the other hand, there is not only the privacy aspect speaking against public channel balances. One would have to announce every balance update to the network which happens for every payment and would result in an infeasible high payload of gossip messages.


---

### Answer by username_2 on 2019-01-11. Score: 2

To add to username_1’s answer: The protocol design currently allows the probing of viable paths to leak just enough information to let you determine whether all channels along route provide adequate liquidity or not, without revealing the individual channel balances.

Note though that one could use probing (receiver and sender controlled by same individual) with different routes and amounts to derive/compute the exact or approximate liquidity in a given channel of interest.

> **Comments:**
> **username_2**: However, this is only reveals the liquidity that a channel node is willing to offer for routing. There is nothing in the protocol that enforces a node to offer all its liquidity for routing.  

---

