CIP-0127? | Integration of ripemd_160 into Plutus

[paluh]

(rendered latest version of proposal)

[rphair]

@paluh thanks for submitting this & we'll introduce it at our next CIP editor's meeting (https://hackmd.io/@cip-editors/89).

Since this is modelled on

• CIP-0101 | Integration of keccak256 into Plutus #524

as reported in af924ad#commitcomment-142326398... @michaelpj is this curve addition on the implementation schedule in a way similar to what you reported in #524 (comment)? (edit, p.s.: cc @zliu41)

[rphair]

@zliu41, following up on my earlier question in #826 (review) ... if I remember correctly from the just-finished CIP meeting, @paluh@perturbing says he was informed this is coming in the hard fork after Chang... can you verify?

[paluh]

Minor comment from my side - @rphair I think that @perturbing suggested this timeline. I think that the exact timeline is not yet known but I hope that just by following the keccak256 path I can help streamline the process - I already started working on it.

[Crypto2099]

This looks fairly straight forward and aligned with the direction of previous introduction of new signature or hashing methods to Plutus. We have at least introductory "team" acceptance of the goal although no clear timeline yet so I think this one should be relatively easy to slap a number on and advance through the stages towards merging and eventual acceptance.

[paluh]

Quick update:

• RIPEMD160 was added to cardano-base: Add RIPEMD160 hashing function (backport) IntersectMBO/cardano-base#480
  and released on CHaP
• The Plutus PR was opened and it is discussed here

[rphair]

Good news @paluh about #826 (comment). To help document that progress, I fixed the formatting of the Acceptance Criteria tickboxes... can you update & keep updated those box ticks (adding GitHub links, if you agree it's appropriate) with the inclusion of IntersectMBO/cardano-base#480 and the outcome of IntersectMBO/plutus#6147?

[paluh]

Hi @rphair, thanks a lot for the fixes. I will update the PR tomorrow if that is ok and keep you informed about the further progress as well.

[rphair]

@paluh we are still looking forward to the evidence of support from Cardano projects as outlined above & hope the number assignment will help with these community & stakeholder discussions. In the meantime please rename the containing directory to CIP-0127 🎉

[rphair]

@paluh how would you describe what we are waiting for, as I tried to express in #826 (review)? Is it the Plutus team?

If so we are trying to find a way to tag such PRs appropriately — according to issue #883, with a GitHub label — that indicates we might be waiting for something out of the author's hands (such as Waiting for Project). For now I'll mark it Waiting for Author & if appropriate then I'll create a new tag & apply it here.

In any case please let us know how this stands with Plutus endorsement (cc @zliu41) if you have any further information about how this is progressing.

[rphair]

@paluh with no response to #826 (review) after over 2 months, it looks like this CIP is no longer being pursued (not saying anything about the integration itself, which may well be proceeding independently). As I understand it, work by the Plutus implementors is driven by CIPs rather than pull requests: so this should either be finalised according to their satisfaction (cc @zliu41) or closed.

[perturbing]

@rphair, this cip is already implemented quite a bit, and is expected (and on track) to be added to plutus next hf (chang + 1).

It has been integrated into plutus here. With this done, we can check off the first four acceptance criteria :)

I believe there may have been a lack of communication due to the rapid pace at which this was implemented. I would like to express my gratitude to @paluh for his outstanding work and perseverance!

[rphair]

Thanks @perturbing for the update on the context & @paluh for the great work in the background ⭐ ... should therefore be able to merge at next meeting or earlier so marking Last Check.