Skip to content

Document regenerated-on-restart events #2097

Closed

Description

@TheBlueMatt

Some events are regenerated on restart, others have the "you have to process this before you return" thing. We should document the ones where the return thing doesn't apply.

Separately, we need to make sure this applies to intercepted HTLCs (I think it does offhand) as you need to be able to open a channel and wait until it's 0conf live before forwarding to it.

Activity

  1. added this to the 0.0.115 milestone on Mar 10, 2023
  2. TheBlueMatt commented on Mar 15, 2023

    @TheBlueMatt
    CollaboratorAuthor

    also claimable events are/should be generated on restart, i believe?

  3. self-assigned this
    on Mar 15, 2023
  4. TheBlueMatt commented on Apr 17, 2023

    @TheBlueMatt
    CollaboratorAuthor

    Slipping to 116.

  5. modified the milestones: 0.0.115, 0.0.116 on Apr 17, 2023
  6. modified the milestones: 0.0.116, 0.0.117 on Jun 8, 2023
  7. TheBlueMatt commented on Jun 8, 2023

    @TheBlueMatt
    CollaboratorAuthor

    Really need to find time for this one, but it'll have to be 117.

  8. modified the milestones: 0.0.117, 0.0.118 on Aug 31, 2023
  9. modified the milestones: 0.0.118, 0.0.119 on Oct 12, 2023
  10. TheBlueMatt commented on Nov 28, 2023

    @TheBlueMatt
    CollaboratorAuthor

    Ugh

  11. modified the milestones: 0.0.120 , 0.0.121 on Jan 9, 2024
  12. modified the milestones: 0.0.122, 0.0.123 on Mar 18, 2024
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

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions