Error when "veramo did add-key" #862
Comments
|
@weippig it's not recommended to use your metamask private key for this, but you likely need to send some rinkeby ETH to the DID controller. I assume you are trying to add a key to a This means you have to fund the controller address of that DID. If the error message doesn't indicate the address, then you can discover it by running I hope this helps |
|
Sorry, I have too many question:( |
It's OK to ask questions, no need to apologize :) |
|
Your answer helped me a lot! But I still have some questions:
Thank you!!! |
|
I'm glad to hear that this is helping, let me try to answer some more:
I hope this helps. |
|
Hello! I did some implementation: import { agent } from './veramo/setup'
import { Wallet } from '@ethersproject/wallet'
import { computePublicKey } from '@ethersproject/signing-key'
async function main() {
const wallet = Wallet.createRandom()
const mnemonic = wallet.mnemonic.phrase
const publicKeyHex = wallet.publicKey.substring(2)
const privateKeyHex = wallet.privateKey.substring(2)
const address = wallet.address
const compressedPublicKey = computePublicKey(`0x${publicKeyHex}`, true)
const identifier = `did:ethr:rinkeby:${compressedPublicKey}`;
console.log('mnemonic:', mnemonic)
console.log('publicKeyHex:', publicKeyHex)
console.log('privateKeyHex:', privateKeyHex)
console.log(`send Rinkeby ETH to ${address} to be able to update ${identifier}`);
try {
const identity = await agent.didManagerImport({
did: identifier,
provider: 'did:ethr:rinkeby',
controllerKeyId: publicKeyHex,
keys: [
{
kid: publicKeyHex,
kms: 'local',
type: 'Secp256k1',
publicKeyHex: publicKeyHex,
privateKeyHex: privateKeyHex,
},
],
services: [],
});
console.log(`New identity created`)
console.log(identity)
} catch (err) {
console.log(err);
}
}
main().catch(console.log)
And I use these code to create first DID : Then I create second DID, but change const identity = await agent.didManagerImport({
did: identifier,
provider: 'did:ethr:rinkeby',
controllerKeyId: '04c35d5374f8541dc09a739766f10349d1699490dfff4caeeb2d1e922fcc7c185a80dc91518b355a1707f5115c18855986eab5e25d0860c1d290519516bd476395',
keys: [
{
kid: publicKeyHex,
kms: 'local',
type: 'Secp256k1',
publicKeyHex: publicKeyHex,
privateKeyHex: privateKeyHex,
},
],
services: [],
});result Then I use
I seem to have a lot of misconceptions. |
|
@weippig nice work digging into this. Indeed there are some misconceptions that I should try to clarify. I will have to start with some basics.
In the most basic case, the When you call Also, since the There is a proposal ( #583) to add a plugin to Veramo that will allow you to change the There is another option, but it also requires some implementation. Now, to answer your second question, which is perhaps some good news for you. You do not have to call
Wow, that is a lot of text, I hope it gives you a better idea about what is going on. |
|
Thank you for the detailed explanation！I only read the W3C official documentation before and didn't know Veramo use ERC1056, I think that's why I have so many misconceptions. In conclusion:
Still have some problem: Thank you! |
|
I'm glad we're making some progress. Let me try to answer the rest.
I hope these answers make things clearer for you. If you think you got all your answers please close this issue. |
|
Thank you for your answer, it helped me a lot! 👍 |
|
Already got the answer, close the issue, thanks again. |
When I use the command
veramo did add-key，encountering this error :Where to setup my metamask account private key? I can't find it.
Thanks!
The text was updated successfully, but these errors were encountered: