-
Notifications
You must be signed in to change notification settings - Fork 12
Asset reissuance #107
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
Comments
Given the Elements issue above, and stated that similar to This error should suggest the user move his reissuance token to a confidential address otherwise he will never be able to reissue his asset. |
It is mandatory that the input that contains the reissuance of the asset is the token output generated when this was issued. Given tehese constrains, maybe it would be better that we provide a function that adds an input and a reissuance to it, and an output (the token output), rather than expecting them to be already present in the partial transaction and just add a reissuance? cc @tiero |
ACK |
Could you split among the tickets you are working on already? @altafan |
This must be taken into account for adding support for creating reissuance transaction:
ElementsProject/elements#259
It will be mandatory to check that the input used for reissuing the asset (actually must be a token prev output) is confidential.
The text was updated successfully, but these errors were encountered: