Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Figure out rebroadcasting / RBF strategy #22

Closed
tnull opened this issue Sep 22, 2022 · 1 comment · Fixed by #205
Closed

Figure out rebroadcasting / RBF strategy #22

tnull opened this issue Sep 22, 2022 · 1 comment · Fixed by #205
Milestone
0.2

Comments

@tnull
Copy link
Collaborator

tnull commented Sep 22, 2022 •
edited
Loading

Currently we just panic on broadcasting failure, we should figure out a good rebroadcasting strategy and implement it.
@tnull tnull mentioned this issue Sep 22, 2022
Closed
@tnull tnull mentioned this issue Jan 4, 2023
Merged
@tnull
Copy link
Collaborator Author

tnull commented Jan 4, 2023

In order to accommodate unreliable network connections, we probably should cache any failed broadcasts and only drop them after they have been retried a couple of times (with exponential back-off).

@tnull tnull mentioned this issue May 22, 2023
Closed
9 tasks
@tnull tnull added this to the 0.2 milestone May 22, 2023
@tnull tnull mentioned this issue Jun 29, 2023
Closed
@tnull tnull mentioned this issue Nov 27, 2023
Merged
@tnull tnull closed this as completed in #205 Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.2
Development

Successfully merging a pull request may close this issue.

Move transaction broadcasting and fee estimation to dedicated modules tnull/ldk-node
1 participant
@tnull