-
Notifications
You must be signed in to change notification settings - Fork 484
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
RIPEMD-160 builtin #6155
Comments
Thanks a lot for putting this together @kwxm! Let me add some context to your points:
The binding which was just added to
This addition was done in few places: primitive binding, builtin definition, fake cost model params, test case
This is still missing :-(
Implemented here
Implemented in #d7470ca8cc4e664c7e21ec79de1c0a961ad1c6b7
Could you please point me to some examples which I can follow. I'm testing this new builtin in the context of Bitcoin pubkeyhash<->pubkey hash verification so I'm happy to turn this into a test case.
I think this is done here: https://github.com/IntersectMBO/plutus/pull/6147/files#diff-0edb07d418229734a515c575977b4866dccdfee4aadeeee116b4dda09999639dR225
Happy to do this by following |
Please note that I rebased and reopened the PR from my fork (due to permission problems). The links from the previous post should still work and are relevant but some of them don't point to my latest rebased version of the PR: #6252 |
It's been proposed that the RIPEMD-160 hash function should be added to Plutus Core, and a CIP is currently being prepared.
To do this we'll need to
cardano-base
.plutus-conformance
, and perhaps they should all go there.plutus-metatheory
We already have a number of hash functions in Plutus Core and this will be very similar, so it shouldn't be too difficult to add it
The text was updated successfully, but these errors were encountered: