-
Notifications
You must be signed in to change notification settings - Fork 7
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
Handle reorgs #14
Comments
Hey, can i work on this . |
1 similar comment
Hey, can i work on this . |
Extra help would be very much appreciated! The description of this issue is very outdated. There's basically 2 things that need to happen I think:
I think (1) is quite difficult requires some help from the blindbit developer (setavenger), but we could probably already do (2). So if you want to work on it, maybe you could start with (2)? |
I also added a similar issue to the Dana wallet repository (a wallet we're working on that consumes sp-client): cygnet3/danawallet#80. |
Sure, I would get started on working on (2), would also check out Dana Wallet |
We should handle block reorgs when managing our owned outputs. Nakamoto has some built-in stuff for tracking scripts across reorgs (https://docs.rs/nakamoto-client/0.4.0/nakamoto_client/handle/trait.Handle.html#method.watch), maybe we could use that. However, we also need to make sure that we reset the 'scan' progress when blocks get reorged.
The text was updated successfully, but these errors were encountered: