grammer fixes
This commit is contained in:
parent
a2fd85dc50
commit
ba83828004
|
@ -6,11 +6,11 @@ JavaScript Elliptic curve cryptography library for both browserify and node.
|
||||||
|
|
||||||
## Motivation
|
## Motivation
|
||||||
|
|
||||||
There is currently no any isomorphic ECC library which provides ECDSA, ECDH and ECIES for both Node.js and Browser and uses the fastest implementation available (e.g. [secp256k1-node](https://github.com/wanderer/secp256k1-node) is much faster than other libraries but can be used only on Node.js). So `eccrypto` is an attempt to create one.
|
There is currently not any isomorphic ECC library which provides ECDSA, ECDH and ECIES for both Node.js and Browser and uses the fastest implementation available (e.g. [secp256k1-node](https://github.com/wanderer/secp256k1-node) is much faster than other libraries but can be used only on Node.js). So `eccrypto` is an attempt to create one.
|
||||||
|
|
||||||
## Implementation details
|
## Implementation details
|
||||||
|
|
||||||
With the help of browserify `eccrypto` provides different implementations for Browser and Node.js with the same API. Because WebCryptoAPI defines asynchronous promise-driven API, implementation for Node needs to use promises too.
|
With the help of browserify `eccrypto` provides different implementations for Browser and Node.js with the same API. Because WebCryptoAPI defines asynchronous promise-driven API, the implementation for Node needs to use promises too.
|
||||||
|
|
||||||
* Use Node.js crypto module/library bindings where possible
|
* Use Node.js crypto module/library bindings where possible
|
||||||
* Use WebCryptoAPI where possible
|
* Use WebCryptoAPI where possible
|
||||||
|
|
Loading…
Reference in New Issue
Block a user