I'm starting preliminary implementation of this CIP. It proposes RIPEMD-160 addition to plutus-core (so to cardano-crypto-class as well). I have preliminary implementation which introduces this change on top of cardano-crypto-class-2.1.4.0 because it is much easier to test this across the ecosystem (I want to use cardano-api etc.) and cardano-crypto-class-2.2.0 is market in the CHANGLOG as non accepted pre-release.
Do you think that it could be introduced to both: 2.2.0.0 and backported to 2.1.5.0 when finally accepted?
Hi,
I'm starting preliminary implementation of this CIP. It proposes RIPEMD-160 addition to
plutus-core(so tocardano-crypto-classas well). I have preliminary implementation which introduces this change on top of cardano-crypto-class-2.1.4.0 because it is much easier to test this across the ecosystem (I want to use cardano-api etc.) and cardano-crypto-class-2.2.0 is market in the CHANGLOG as non accepted pre-release.Do you think that it could be introduced to both: 2.2.0.0 and backported to 2.1.5.0 when finally accepted?