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.

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

Persist subscription status across reconnects #124

Open
tnull opened this issue Nov 11, 2023 · 1 comment
Open

Persist subscription status across reconnects #124

tnull opened this issue Nov 11, 2023 · 1 comment
Labels
new feature New feature or request

Comments

@tnull
Copy link
Contributor

tnull commented Nov 11, 2023

It would be nice if the client would re-subscribe to block headers/scripts if the connection was ever dropped and we're reconnecting.

Alternatively, script_pop/block_headers_pop could return an error indicating that the subscription has been cancelled in the meantime.

@notmandatory notmandatory added this to the Release 0.19.0 milestone Nov 12, 2023
@notmandatory notmandatory modified the milestones: Release 0.19.0, Release 0.20.0 Dec 12, 2023
@notmandatory notmandatory moved this to Todo in BDK Wallet Mar 18, 2024
@notmandatory notmandatory added the new feature New feature or request label Mar 18, 2024
@notmandatory notmandatory removed this from the Release 0.20.0 milestone Nov 22, 2024
@tnull
Copy link
Contributor Author

tnull commented Mar 7, 2025

Looking at the code I just realized we don't actually seem to reconnect in the first place, which would of course be a prerequisite for this (cf. #165).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature or request
Projects
Status: Todo
Status: Todo
Development

No branches or pull requests

2 participants