You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
const message = JSON.stringify({
"@type": "did:example:1234567890;spec/test",
data: "I AM A SIGNED MESSAGE"
})
I would expect this library to assist implementers in crafting messages that are formatted correctly, in addition to packing / unpacking.
The code used to construct a valid message, is undoubtably in other repo, can establish a clearer understanding of the message format this library should be used with?
The text was updated successfully, but these errors were encountered:
OR13
changed the title
Message Validation
How to construct valid messages according to a protocol version?
Aug 16, 2019
The message format isn't a concern of this layer. As long as it's a string, this library can be used to encrypt the message.
However, with that said, "DIDComm semantic messages" are assumed to be the common messages used in this format. This is the reason that I included some with the format of DIDComm semantic messages and some without.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The readme shows:
I would expect this library to assist implementers in crafting messages that are formatted correctly, in addition to packing / unpacking.
The code used to construct a valid message, is undoubtably in other repo, can establish a clearer understanding of the message format this library should be used with?
The text was updated successfully, but these errors were encountered: