This requires some new associated type constraints, specifically what kind of messages and keys we can use for commitments. I don't thing Send + Sync are at all unreasonable assumptions for a cryptographic message type or a cryptographic key type, though.
The other thing I did was use cfg_iter! to parallelize a bunch of functions in ip_proofs. This conflicts with the more direct par_iter notation used in the sipp crate. I'm not sure which one you prefer, so let me know and I'll make the change.
Lastly, this does not compile without the most recent changes (https://github.com/arkworks-rs/utils/pull/16) to the utils crate. The issue is that the cfg_iter! wasn't using the rayon iter before the new changes.
This requires some new associated type constraints, specifically what kind of messages and keys we can use for commitments. I don't thing
Send + Sync
are at all unreasonable assumptions for a cryptographic message type or a cryptographic key type, though.The other thing I did was use
cfg_iter!
to parallelize a bunch of functions inip_proofs
. This conflicts with the more directpar_iter
notation used in thesipp
crate. I'm not sure which one you prefer, so let me know and I'll make the change.Lastly, this does not compile without the most recent changes (https://github.com/arkworks-rs/utils/pull/16) to the
utils
crate. The issue is that thecfg_iter!
wasn't using therayon
iter before the new changes.