ethr-did-resolver - npm Package Compare versions

Comparing version 7.0.0 to 7.0.1

package.json

		{
		"name": "ethr-did-resolver",
		"version": "7.0.0",
		"version": "7.0.1",
		"description": "Resolve DID documents for ethereum addresses and public keys",
		@@ -116,4 +116,4 @@ "type": "commonjs",
		"@ethersproject/transactions": "^5.6.2",
		"did-resolver": "^4.0.0"
		"did-resolver": "^4.0.1"
		}
		}

README.md

		@@ -29,3 +29,3 @@ [![npm](https://img.shields.io/npm/dt/ethr-did-resolver.svg)](https://www.npmjs.com/package/ethr-did-resolver)
		For example:
		`did:ethr:0x4:0xf3beac30c498d9e26865f34fcaa57dbb935b0d74` gets resolved on the rinkeby testnet (chainID=0x4), and
		`did:ethr:0x5:0xf3beac30c498d9e26865f34fcaa57dbb935b0d74` gets resolved on the goerli testnet (chainID=0x5), and
		represents a distinct identifier than the generic one, with different DID documents and different key rotation history.
		@@ -118,3 +118,3 @@
		{ name: "mainnet", provider: web3.currentProvider },
		{ name: "0x4", rpcUrl: "https://rinkeby.infura.io/v3/<YOUR PROJECT ID>" },
		{ name: "0x5", rpcUrl: "https://goerli.infura.io/v3/<YOUR PROJECT ID>" },
		{ name: "rsk:testnet", chainId: "0x1f", rpcUrl: "https://did.testnet.rsk.co:4444" },
		@@ -133,3 +133,3 @@ { name: "development", rpcUrl: "http://localhost:7545", registry: "0xdca7ef03e98e0dc2b855be647c39abe984fcf21b" },
		- `did:ethr:0xabcabc03e98e0dc2b855be647c39abe984193675` (defaults to mainnet configuration)
		- `did:ethr:0x4:0xabcabc03e98e0dc2b855be647c39abe984193675` (refer to the rinkeby network by chainID)
		- `did:ethr:0x5:0xabcabc03e98e0dc2b855be647c39abe984193675` (refer to the goerli network by chainID)
		- `did:ethr:rsk:testnet:0xabcabc03e98e0dc2b855be647c39abe984193675`
		@@ -136,0 +136,0 @@ - `did:ethr:0x1f:0xabcabc03e98e0dc2b855be647c39abe984193675` (refer to the rsk:testnet by chainID)

New alerts