As a blockchain developer
I want a light-weight crypto implementation
So that the attack surface of dependencies in minimised
noble-curves appears to be a lighter weight, more actively supported, better typed, and potentially faster crypto implementation than elliptic.
This issue is the same as #524, which was implemented in commit c040e5251670223c4d5f0142ef4f3205ac644c65 and then undone in commit f75f44020d5bec45b3d303267de8ab76c2cabaef due to lack of support for big-endian platforms. Once a version of noble-hashes >1.3.3 is available (including the big-endian support now committed in the main branch), and a version of noble-curves depending on that noble-hashes version is released, the signing implementation can be reimplemented to use noble-hashes.
As a blockchain developer I want a light-weight crypto implementation So that the attack surface of dependencies in minimised
noble-curves appears to be a lighter weight, more actively supported, better typed, and potentially faster crypto implementation than elliptic.
This issue is the same as #524, which was implemented in commit c040e5251670223c4d5f0142ef4f3205ac644c65 and then undone in commit f75f44020d5bec45b3d303267de8ab76c2cabaef due to lack of support for big-endian platforms. Once a version of noble-hashes >1.3.3 is available (including the big-endian support now committed in the main branch), and a version of noble-curves depending on that noble-hashes version is released, the signing implementation can be reimplemented to use noble-hashes.