<p>&quot;it's just for co-op close, the force close &quot;address&quot; is already locked in: the P2WSH script itself&quot; Roasbeef</p>
<p>Another note that dawned on me. For situations where you want to do a force close, your channel partner wouldn't be able to specify any new data.. So ofc you would need to know where the remote balance is going, and this is the same for the local balance.</p>

CC BY-SA 4.0
2021-09-14T21:45:54.993Z
2021-09-14T21:45:54.993Z
Michael Tidwell
<p>In <a href="https://github.com/lnbook/lnbook/blob/develop/07_payment_channels.asciidoc" rel="nofollow noreferrer">https://github.com/lnbook/lnbook/blob/develop/07_payment_channels.asciidoc</a></p>
<p>We see this block of text:</p>
<blockquote>
<p>Typically the addresses used in this cooperative close transaction are
generated freshly for each channel being closed. However, it’s also
possible for both sides to lock in a &quot;delivery&quot; address to be used to
send their cooperatively settled funds to. Within the TLV namespace of
both the open_channel and accept_channel messages, both sides are free
to specify an &quot;upfront shutdown script&quot;. Commonly, this address is
derived from keys that reside in cold storage. This practice serves to
increase the security of channels: if a channel partner is somehow
hacked, then the hacker isn’t able to cooperatively close the channel
using an address they control. Instead, the uncompromised honest
channel partner will refuse to cooperate on a channel closure if the
specified upfront shutdown address isn’t used. This feature
effectively creates a &quot;closed loop&quot;, restricting the flow of funds out
of a given channel.</p>
</blockquote>
<p>It seems like delivery addresses are only for cooperative closes based on this text. Can you still specify a delivery addresses for any close type, including force close?</p>

<address><lightning-network><lightning-network-daemon><hacking>
Specifying delivery addresses on channel closes - includes force closes?
Michael Tidwell
# Specifying delivery addresses on channel closes - includes force closes?

(Asked by: username_0 on 2021-09-11)

In <https://github.com/lnbook/lnbook/blob/develop/07_payment_channels.asciidoc>

We see this block of text:

> Typically the addresses used in this cooperative close transaction are
> generated freshly for each channel being closed. However, it’s also
> possible for both sides to lock in a "delivery" address to be used to
> send their cooperatively settled funds to. Within the TLV namespace of
> both the open\_channel and accept\_channel messages, both sides are free
> to specify an "upfront shutdown script". Commonly, this address is
> derived from keys that reside in cold storage. This practice serves to
> increase the security of channels: if a channel partner is somehow
> hacked, then the hacker isn’t able to cooperatively close the channel
> using an address they control. Instead, the uncompromised honest
> channel partner will refuse to cooperate on a channel closure if the
> specified upfront shutdown address isn’t used. This feature
> effectively creates a "closed loop", restricting the flow of funds out
> of a given channel.

It seems like delivery addresses are only for cooperative closes based on this text. Can you still specify a delivery addresses for any close type, including force close?

**Tags:** address, lightning-network, lightning-network-daemon, hacking


---

## 1 answers

### Answer by username_0 on 2021-09-14. Score: 0 | Accepted answer

"it's just for co-op close, the force close "address" is already locked in: the P2WSH script itself" Roasbeef

Another note that dawned on me. For situations where you want to do a force close, your channel partner wouldn't be able to specify any new data.. So ofc you would need to know where the remote balance is going, and this is the same for the local balance.


---

