-
Notifications
You must be signed in to change notification settings - Fork 117
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
asset wallet: introduce coin locking and coin selection mutex #261
Comments
May also want to have a bit that says if an output has been fully spent or not. Either that, or we need to delete it. |
related issue #374 |
This was referenced Jul 25, 2023
This was referenced Aug 8, 2023
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Taproot-Assets Project Board
Aug 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The asset wallet introduced in #244 does not allow a coin to be marked as being used (=locking), which needs to be done at the database layer.
Once we can mark asset coins as being used/locked, we also need to make sure that access to coin selection and the locking APIs are covered by a single coin selection mutex similar to how it's done in
lnd
.The text was updated successfully, but these errors were encountered: