-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
not enough funds #13
Comments
Tested it using this updated rgb-sandbox branch. Compared to the original branch it updates to I also updated the sandbox run to better stimulate the issue, it now:
With this setup I still see the issue. |
Tested with an updated rgb-sandbox branch that uses the current |
I have updated #17 on top of master with all past changes. Can you pls test it once again and provide me with the exact message it generates like in the original issue (all outputs etc)? I do not see why it may not be working... |
Tested it again (rgb-sandbox branch) using the updated
These are the unspents before the transfer:
|
Alright, I finally get it: there were two issues here:
The first one was (most probably) fixed by #17. The second one is the one which remains. I am re-opening #113 changing its description to indicate the second issue. I am closing this one and merging #17 since I believe the first issue is fixed. Let me know if you can't do a transfer for 4000 sats when two 3000 sat inputs are present (it should work, but just if not we will re-open this issue) |
Re-opening here, as indicated in RGB-WG/rgb#113
Trying to execute a few transfers using this branch of rgb-sandbox I run into the following error:
The wallet should have enough bitcoins as the unspents come up as:
I guess this happens because the input selection is not adding more inputs if needed to cover fees (or outputs), but I haven't dug deeper than this.
The text was updated successfully, but these errors were encountered: