On Wed, Dec 13, 2023 at 04:41:46PM +0100, Bastien TEINTURIER wrote:
> Hi Peter,
>
> > it is more efficient to just open the channel with a dust-sized
> > balance on the to_remote output.
>
> Yes, that would work, basically whenever the `to_remote` output would
> disappear, then you add an anchor
Hi Peter,
> it is more efficient to just open the channel with a dust-sized
> balance on the to_remote output.
Yes, that would work, basically whenever the `to_remote` output would
disappear, then you add an anchor output instead paid by the channel
initiator. It isn't only at channel creation ti
On Wed, Dec 13, 2023 at 02:27:13PM +0100, Bastien TEINTURIER wrote:
> Hi Peter,
>
> No, we currently cannot get rid of the remote anchor in favor of the
> main remote output. That was considered during the design of anchor
> outputs, but that would create the following vulnerability.
>
> Alice op
Hi Peter,
No, we currently cannot get rid of the remote anchor in favor of the
main remote output. That was considered during the design of anchor
outputs, but that would create the following vulnerability.
Alice opens a channel to Bob: Bob doesn't have a main output in the
commit tx yet. Alice s
As per BOLT #3,
https://github.com/lightning/bolts/blob/8a64c6a1cef979b3f0cecb00ba7a48c2d28b3588/03-transactions.md#commitment-transaction-construction
9) If option_anchors applies to the commitment transaction:
* if to_local exists or there are untrimmed HTLCs, add a
to_local_anchor