eccrypto - npm Package Compare versions

Comparing version 1.1.5 to 1.1.6

package.json

		{
		"name": "eccrypto",
		"version": "1.1.5",
		"version": "1.1.6",
		"description": "JavaScript Elliptic curve cryptography library",
		@@ -54,3 +54,3 @@ "main": "index.js",
		"acorn": "7.1.1",
		"elliptic": "6.5.3",
		"elliptic": "6.5.4",
		"es6-promise": "4.2.8",
		@@ -57,0 +57,0 @@ "nan": "2.14.0"

README.md

		@@ -9,7 +9,7 @@ # eccrypto [![Build Status](https://travis-ci.org/bitchan/eccrypto.svg?branch=master)](https://travis-ci.org/bitchan/eccrypto)

		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

		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.

		@@ -16,0 +16,0 @@ * Use Node.js crypto module/library bindings where possible

New alerts