-
Notifications
You must be signed in to change notification settings - Fork 42
Invalid Frame on verification of a BBS signature #122
Comments
Can you publish the code that you're using to work with this? I'm thinking the issue here is that the verificationMethod used is only a fragment which means either an |
Thanks for reply @kdenhartog. Anywhere I can read about this @base property, or you know about any examples or helpers about that? There is btw a long thread going on here: https://difdn.slack.com/archives/C4X50SNUX/p1620313732057300, as it was relevant for some other questions I had up in the air. I will see if your pointer and the discussion leads to something working tomorrow, dont have the code at hand now. Will close tomorrow if successful |
@kdenhartog I do think I touched upon something bigger: w3c/did-imp-guide#3, not directly related but there are some mentions of BBS and documents without context there. |
I was not able to get past this issue, even if I change up things in the document loader: https://gist.github.com/vongohren/92753c7dc8e8be7ed219c2d184c624aa How shall I be able to verify this? |
I did get help from another DIF member: https://gist.github.com/S3bb1/ddd74704c0f9980d93e4e6302439594c But is this the stuff you have to deal with usually? Or since everyone is making their own things, they know their own libraries? |
@vongohren to be clear is this issue distinct from #114? |
@tplooker yeah thsi is different, as this is more related to the resolving. The other I believe is mainly related to the big gap in different versions for Json-ld signatures. |
Im uncertain where this fails but seems to me that it comes from this lib.
I have a strane error coming from trying to recreate the bbs signature sample with libraries that I want to use.
I try to great a keypair with did-key.js and use that to sign.
That works
Then I want to verify but get a strange JSON LD verification error, and dont know where to start.
Any thoughts?
The text was updated successfully, but these errors were encountered: