We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
elements-fun
rust-elements
It turns out that there isn't as much need for most of the re-modelling that we did in elements-fun as we initially thought. See more here.
This is a tracking issue for moving all of what we did in elements-fun back into rust-elements (non-exhaustive list):
rust-secp256k1-zkp
TxOut
new_last_confidential
new_non_last_confidential
.unblind
ExplicitTxOut
ConfidentialTxOut
into_{explicit,confidential}
The text was updated successfully, but these errors were encountered:
This is so done.
Sorry, something went wrong.
luckysori
Successfully merging a pull request may close this issue.
It turns out that there isn't as much need for most of the re-modelling that we did in elements-fun as we initially thought. See more here.
This is a tracking issue for moving all of what we did in elements-fun back into rust-elements (non-exhaustive list):
rust-secp256k1-zkp
and model asset/value commitment using types fromrust-secp256k1-zkp
TxOut
constructors fornew_last_confidential
/new_non_last_confidential
.unblind
API onTxOut
ExplicitTxOut
andConfidentialTxOut
along withinto_{explicit,confidential}
onTxOut
The text was updated successfully, but these errors were encountered: