<p>Your concern is genuine but the decision to open a channel is not a part of the core <a href="https://github.com/lightningnetwork/lightning-rfc" rel="nofollow noreferrer">specifications</a>. The decision to open a channel with a node is up to the user. </p>

CC BY-SA 3.0
2018-02-16T00:43:47.643Z
@trampster sorry, edited the answer.
skang404
CC BY-SA 3.0
2018-02-16T00:47:47.653Z
I guess it will be the individual wallet implementation rather then the user that does this, I don't expect most users will choose a channel the wallet will do it for them. I wonder if reliability info/up time is something that a wallet implementation would be able to discover about a node.
trampster
CC BY-SA 3.0
2018-02-15T23:07:25.633Z
2018-02-16T00:43:29.243Z
2018-02-16T00:43:29.243Z
skang404
<p>Lets say I open a lightning network channel and the other party goes offline. Lets say I haven't actually used the channel yet. What if I want my bitcoin back from that channel so I can use it.</p>

<p>I payed an on chain transaction fee to open the channel, I can close the channel again but will have to pay another on chain transaction fee to close the channel. Effectively I will have payed for two on chain transactions without actually transferring any bitcoin.</p>

<p>If I go to pay and the other end of my channel is down. It would take me two on chain transactions to be able to make the payment (one to close the channel and one to open a new one) my instant and almost free payment has now become extremely expensive and slow.</p>

<p>What steps do the lightning network implementations take to limit the impact of this kind of thing? When your lightning wallet choses a node to open a channel with, does it take into account how reliable that node is, IE how long it has been online for / how much down time it has had?</p>

<lightning-network>
Lightning network avoiding bad channels
trampster
# Lightning network avoiding bad channels

(Asked by: username_0 on 2018-02-15)

Lets say I open a lightning network channel and the other party goes offline. Lets say I haven't actually used the channel yet. What if I want my bitcoin back from that channel so I can use it.

I payed an on chain transaction fee to open the channel, I can close the channel again but will have to pay another on chain transaction fee to close the channel. Effectively I will have payed for two on chain transactions without actually transferring any bitcoin.

If I go to pay and the other end of my channel is down. It would take me two on chain transactions to be able to make the payment (one to close the channel and one to open a new one) my instant and almost free payment has now become extremely expensive and slow.

What steps do the lightning network implementations take to limit the impact of this kind of thing? When your lightning wallet choses a node to open a channel with, does it take into account how reliable that node is, IE how long it has been online for / how much down time it has had?

**Tags:** lightning-network


---

## 1 answers

### Answer by username_1 on 2018-02-15. Score: 2

Your concern is genuine but the decision to open a channel is not a part of the core [specifications](https://github.com/lightningnetwork/lightning-rfc). The decision to open a channel with a node is up to the user.

> **Comments:**
> **username_1**: @username_0 sorry, edited the answer.  
> **username_0**: I guess it will be the individual wallet implementation rather then the user that does this, I don't expect most users will choose a channel the wallet will do it for them. I wonder if reliability info/up time is something that a wallet implementation would be able to discover about a node.  

---

