As was specified in: https://github.com/ZenGo-X/curv/pull/128#discussion_r684750324
This will allow the user to choose their own hash function when using our hash and related commitments,
it also removes deprecated hashing traits that are no longer in use.
I added a macro to run all the related tests over multiple hash functions (right now: sha256, sha512, sha3_256, sha3_512, blake2b, blake2s)
This is based on #128 so for now I made try-and-increment the base branch but will change that if and when #128 will get merged.
Things that still use explicit hash funciton:
merkle trees (we use a library that only supports Sha3, should probably just implement this ourselves).
Creating a second generator point (doesn't make sense to make this generic somehow)
As was specified in: https://github.com/ZenGo-X/curv/pull/128#discussion_r684750324 This will allow the user to choose their own hash function when using our hash and related commitments, it also removes deprecated hashing traits that are no longer in use.
I added a macro to run all the related tests over multiple hash functions (right now: sha256, sha512, sha3_256, sha3_512, blake2b, blake2s)
This is based on #128 so for now I made try-and-increment the base branch but will change that if and when #128 will get merged.
Things that still use explicit hash funciton: