This is a meta-issue related to multiple possible improvements :
- (1) moving all crypto dependency at the same place
- (2) ability to run a test suite that is directly related to parity use
- (3) ability to run bench on different crates
- (4) traits over main parity crypto use, and hability to switch crates without to much efforts (not meant to be std crypto trait, more a convenient way to audit/check our crypto libs usage).
- (5) wasm32 compatibility/alternative
- (6) no_std compatibility/alternative
Following steps are proposed :
A previous PR covered first three steps is at #80 , I put it on ice in favor of smaller PRs. It contains lots of additional information.
This is a meta-issue related to multiple possible improvements :
- (1) moving all crypto dependency at the same place
- (2) ability to run a test suite that is directly related to parity use
- (3) ability to run bench on different crates
- (4) traits over main parity crypto use, and hability to switch crates without to much efforts (not meant to be std crypto trait, more a convenient way to audit/check our crypto libs usage).
- (5) wasm32 compatibility/alternative
- (6) no_std compatibility/alternative
Following steps are proposed :
A previous PR covered first three steps is at #80 , I put it on ice in favor of smaller PRs. It contains lots of additional information.