-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Blank state transitions do not update to state data #80
Comments
I was able to replicate the issue, thank you for the sandbox environment. From my debug information I see that the blank transition is created and the state is transferred correctly, i.e. stash state is correct and nothing is lost. The problem is that the blank transition is not indexed and not parsed to update cached state data in the inventory, so rgb can't "see" it. Investigating the reasons why it happens. |
Was this working correctly before the latest PRs? |
Unfortunately I can't tell. Checking a blank transfer was not part of rgb-sandbox before, as we were focusing on more basic transfer functionality, and has just been added in the attempt to cover more and more use cases. |
This error is the same of that #60 |
Fixed with #81. The tests with sandbox now pass for me (I updated the |
Using our rgb-sandbox I tried to issue 2 assets to the same UTXO, then transfer the first asset to another wallet and then check the the second asset's allocation, which I expect to be on the change outpout at that point.
What I find is that, after the transfer has completed, the second asset's allocation is still on the original issuance UTXO, which has now been spent.
To give an example, this is the situation after issuing the two assets:
Then a transfer (txid
296ab67bd423551c87229e9371b85ee5c62b60417d8015bed146d49d71bb784f
) sends 100 units of the first asset to another wallet and this is the resulting situation (on the issuer/sender side):This issue can be reproduced using this branch of rgb-sandbox.
The text was updated successfully, but these errors were encountered: