Update jolocom-lib to 3.0, and fix SoftwareKeyProvider usage

Fixes #18
jolocom · Aug 3, 2019 · 627fc2e · 627fc2e
1 parent 650d5fd
commit 627fc2e
Show file tree

Hide file tree

Showing 3 changed files with 1,304 additions and 409 deletions.
diff --git a/package.json b/package.json
@@ -21,7 +21,7 @@
     "history": "^4.7.2",
     "isomorphic-fetch": "^2.2.1",
     "jest": "22.4.2",
-    "jolocom-lib": "^2.2.9",
+    "jolocom-lib": "^3.0.0",
     "material-ui": "^0.20.2",
     "promise": "8.0.1",
     "react": "^16.4.2",

diff --git a/server/server.ts b/server/server.ts
@@ -20,7 +20,7 @@ app.use(cors())
 
 const { getAsync, setAsync, delAsync } = configureRedisClient()
 const registry = JolocomLib.registries.jolocom.create()
-const vaultedKeyProvider = new JolocomLib.KeyProvider(seed, password)
+const vaultedKeyProvider = JolocomLib.KeyProvider.fromSeed(seed, password)
 
 registry.authenticate(vaultedKeyProvider, {derivationPath: JolocomLib.KeyTypes.jolocomIdentityKey, encryptionPass: password})
 .then(identityWallet => {