Open theblockstalk opened 10 months ago
I have tested did:key with the Veramo SDK: https://github.com/theblockstalk/learning/tree/master/veramo
Results
using did:key
using did:jwk
Also noted that it looks like did:key with Secp256k1
key does not currently support the keyAgreement needed to support DIDComm. See here https://discord.com/channels/878293684620234752/890207307433136178/1172839857006055484
currently blocked by this to implement did:key https://github.com/Tonomy-Foundation/Tonomy-ID/issues/758
so to achieve this task we might need to make some big multi-repo build changes :( in
currently blocked by this to implement did:key https://github.com/Tonomy-Foundation/Tonomy-ID/issues/758
so to achieve this task we might need to make some big multi-repo build changes to use the @veramo framework instead of directly with did-jwt :( in
And then application changes
last sprint: 1 next sprint: 2
When a URL with a wallet request, or wallet response is sent by the URL it can be very long. With 2x login request + 2x data sharing request the length was >9000 characters
Different servers and browsers support maximum limits:
We need to reduce the length of our URL. We could do this in A few obvious ways to me at the moment ( there may be other ways):