Brian Richter

I think I have discovered that this only happens on signed messages. I haven't yet been able to reproduce though as I can't successfully create a signed message. It throws...

Are there test vectors testing multibase encoded keys? ie. `X25519KeyAgreement2020` and `Ed25519VerificationKey2020` this would be a great place to start as I believe I encountered a bug see #95

I believe this is the correct context url is https://didcomm.org/messaging/contexts/v2

ah yes sorry ignore me

I agree this should be changed to be more permissive and allow a service endpoint object. the DID spec does this all over so I don't think it's any more...

definitely would be good to have popularity metric like on npmjs.com and test vectors being included with protocols also seems like a good thing to include regardless of if we...

alternatively could setup an escape character as shown here https://www.gatsbyjs.com/plugins/gatsby-remark-emojis/

Yeah, it will definitely break existing implementations 😅 Wondering what the best path forward is as it's impossible to align with both this and didcommv2 at the moment. I may...

I would if we are going to revive this method. If not I don't think it's worth the effort. At this stage I'm just gathering information to figure out the...

Ultimately, this method to me is entirely captured by `static` and `numalgo=2`. Here is the reason I believe this to be true.. static: - numalgo 0 is identical to did:key...