You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 9, 2023. It is now read-only.
Trying to spend an asset which has been incorporated in a Blank transition fails when calling rgb20::transitions::transfer() with an UnrelatedInput error.
The issue seems to be that there is no method reading the DISCLOSURES table, which is where the blank transitons are stored (see here).
Once the txid is seen in blockchain, the node will enclose the disclosure to the stash automatically, updating the state of all smart contracts affected by the transfer
This automatic action is currently not happening and moreover I think that it's desirable to allow manual control of enclosing, since a wallet could prefer to enclose the disclosures only once the TX has reached a minimum number of confirmations.
I think we could add an API that gets the transfer TXID ad uses it to retrieve all associated disclosures that were part of that TX and encloses them. @dr-orlovsky what do you think?
The text was updated successfully, but these errors were encountered:
Trying to spend an asset which has been incorporated in a
Blank
transition fails when callingrgb20::transitions::transfer()
with anUnrelatedInput
error.The issue seems to be that there is no method reading the
DISCLOSURES
table, which is where the blank transitons are stored (see here).Looking at the transfer combine doc I read:
This automatic action is currently not happening and moreover I think that it's desirable to allow manual control of enclosing, since a wallet could prefer to enclose the disclosures only once the TX has reached a minimum number of confirmations.
I think we could add an API that gets the transfer TXID ad uses it to retrieve all associated disclosures that were part of that TX and encloses them. @dr-orlovsky what do you think?
The text was updated successfully, but these errors were encountered: