Can NOT verify did:ether JWT token

I try to use Ether-DID library to create new jwt token and after that i can NOT verify it. Here is example code i used.

`const EthrDID = require(‘ethr-did’); const ethrDid = new EthrDID({ provider: web3.currentProvider, address: ‘address’, privateKey: ‘priv-key’ });

var jwt = await ethrDid.signJWT({ claims: { name: ‘Joe Lubin’ } }); //Problem here const { payload, issuer } = ethrDid.verifyJWT(jwt); console.log(payload); // return undefined console.log(issuer); // return undefined`

[gdollard]

I was hoping to use a key pair from one of my accounts via my web3 instance but for some reason JWT doesn’t like it.

web3 signatures are different from JWT signatures, even if the same private key is in use so it wouldn’t work with only your web3 provider.

For reference, in pseudocode web3 signatures are computed as signHash(privKey, keccak(message)) while JWT signatures are computed as signHash(privKey, sha256(message))

As a side-note, unfortunately there’s not enough bandwidth now to investigate the issues you are facing, not even to update docs for this library. PRs are still welcome, of course.

@mirceanis thanks for that information, much appreciated.

[mirceanis]

Just to be clear, the delay is needed somewhere between createSigningDelegate() and verifyJWT because createSigningDelegate() sends a transaction and that block needs to propagate to the node that responds to the calls made by verifyJWT (resolving the DID document).

So, if your flow requires some key delegation for signing but not immediately followed by verification, this delay will not be needed.