Skip to content

Auto-Close on update_fee delay #993

Closed

Description

@TheBlueMatt

If we intend to update the channel fee on an outbound channel (or if we just think our channel fee is really far off on an inbound channel) and its been a while since we've managed to connect with them (or they're not ack'ing our update_fee), we should probably force-close the channel out of fear for our inability to get the channel close confirmed. This does not apply to anchor.

Activity

  1. added this to the 0.1 milestone on Jul 12, 2021
  2. ariard commented on Aug 15, 2021

    @ariard

    Marking this 0.0.101 as otherwise it's a significant risk of stale feerate in case of emergency unilateral close.

    Note, I think we should only proceed to the auto-close in case of pending HTLC to solve. Otherwise should we really care about empty commitment transaction with staled feerate ? As long as it's committed with a mempool min fee high-enough.

  3. modified the milestones: 0.0.101, 0.1 on Sep 15, 2021
  4. TheBlueMatt commented on Sep 15, 2021

    @TheBlueMatt
    CollaboratorAuthor

    Moved back to 0.1 as with #1056 as we should block prod for this, but not user testing.

  5. added 2 commits that reference this issue on May 6, 2024
    986bc4a
    6a9dd2b
  6. added 2 commits that reference this issue on May 30, 2024
    c276b0a
    898f671
  7. added 2 commits that reference this issue on Jun 10, 2024
    77bea65
    5a1cc28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions