Skip to content
This repository has been archived by the owner on May 10, 2021. It is now read-only.

Cannot deploy all the uPort smart contracts #232

Open
epm-bt opened this issue Oct 30, 2018 · 0 comments
Open

Cannot deploy all the uPort smart contracts #232

epm-bt opened this issue Oct 30, 2018 · 0 comments

Comments

@epm-bt
Copy link

epm-bt commented Oct 30, 2018

I run a permissioned Ethereum network at my lab and I am trying to spin a uPort server to run some tests with a relay client.

I am faced with an issue when I create the identity and deploy the smart contracts of uPort. I can see from my block explorer that the two of the contracts (registry and Identity Manager) are perfectly created but I get stuck somewhere on the creation of the remainders. Here is my error code:

 Then the contracts can be deployed and identity created 

? Press y to continue:  Yes

 Deploying uPort platform contracts...

 uPort registry contract configured and deployed at 0x19d1515d602b499e9531dc02a8d56e7c12296c8d 

 uPort Identity Manager contract configured and deployed at 0x22d64d2c8adcdb38afbd2b0b9df72b06ec65f5a1 

Initializing identity... 

(node:8192) UnhandledPromiseRejectionWarning: Error: To address must be MNID
    at buildRequestURI (/usr/lib/node_modules/uport-cli-client/node_modules/uport/lib/Contract.js:128:46)
    at Contract.contractMethod [as createIdentity] (/usr/lib/node_modules/uport-cli-client/node_modules/uport/lib/Contract.js:110:29)
    at UPortClient.initializeIdentity (/usr/lib/node_modules/uport-cli-client/node_modules/uport-client/index.js:318:33)
    at inquirer.prompt.then.then.then.appDDO (/usr/lib/node_modules/uport-cli-client/uport-id.js:154:28)
(node:8192) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8192) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I don't understand which 'to address' is and why it is not MNID (as of yet, specially because I don't input any address in the process). I played with the txt.js file at /usr/lib/node_modules/uport-cli-client to add the default custom network parameters to the uport-id console, but it was failing to the Ganache-cli deployment too.

Any help is greatly appreciated!

Cheers,

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant