Author: Hiroshi Ueno 2018-05-15 14:04:15
Published on: 2018-05-15T14:04:15+00:00
Nayuta-ueno is currently implementing the `r` field to `ptarmigan` and has a query regarding the `r` field's signature. The `r` field does not contain a signature like the `channel_update`, and Nayuta-ueno is curious about whether c-lightning checks something in the `r` field from payee's invoice. ZmnSCPxj replies to this, stating that the temporary `channel_update`s are sent after `funding_locked` has been sent by both sides, as well as reconnection (only if both sides have sent `funding_locked`). After announcement depth, "normal" `channel_update` should get sent after a `channel_announcement`, and not the temporary ones.ZmnSCPxj also mentions that while implementing support for the `r` field in invoices, he stumbled upon some issues regarding creating invoices with `r` fields. In order to receive via an unpublished channel, we need to know what onLightning fees the other side of that channel wants to charge. In case of an unpublished channel, we do not send `channel_announcement`, and in that case, we do not send `channel_update`. The other side of the channel never informs us of the onLightning fees they want to charge if we would receive funds by this channel. An idea that was considered for this was to simply send `channel_update` as soon as we lock in the channel. ZmnSCPxj asks other LN implementations like lnd, eclair, ucoin, lit if we should consider standardizing this behavior.
Updated on: 2023-05-24T23:39:12.285603+00:00