-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
sender see no balance after a transfer (tapret1st) #173
Comments
Looks like issue with detecting outputs containing tweaks... Can you please include the sender data directory? |
Here is the whole sender's data directory. |
Ok, this was trivial: tapret tweak was added to the wallet, but the wallet itself wasn't saved to the disk. Fixed in #175 |
Re-tested using branch The sender now fails to prepare the transfer with:
|
Ok, this means my fix from f9813b7#diff-f643199b78cd917deee88c751028d85bc710961b6f7b874f3c99cf6935fd68b0L109-L118 doesn't actually work. Finding another way to save using serde in a feature-gate aware way with no |
With the new fix from ac43eb2 using BP-WG/bp-core#87 and BP-WG/bp-std#24 this should be working now |
Using commit
|
moreover, I noticed the exit status of the command is |
Try with e05f6c75a1a150851a4b08fcec74f02230de6bb1 - just do |
Wallet creation now succeeds, but I get the error when syncing the wallet (
|
After including a fix in
|
Including fixes for bp-std ( |
Using commit
f9813b7
plus a cargo update to include rgb-std #193 I face an issue.This is what I'm doing (wallet 1 is the issuer/sender, wallet 2 is the recipient):
All operations are carried out using
tapret1st
closing method. The same issue doesn't manifest itself when usingopret1st
.After the 1st transfer, the sender doesn't see the assets allocated as RGB change.
These are the sender UTXOs after the transfer:
This is the sender's contract state after the transfer:
The text was updated successfully, but these errors were encountered: