-
Notifications
You must be signed in to change notification settings - Fork 59
Issues: decentralized-identity/didcomm-messaging
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Thread sync with gossip-about-gossip and Cordial Dissemination
#456
opened Apr 27, 2024 by
andrewzhurov
Move libraries and implementations from the README to the didcomm-book
#448
opened Dec 4, 2023 by
TheTechmage
Out of band as an URI fragment
newminorversion
This would require a new minor version update
#443
opened Aug 4, 2023 by
FabioPinheiro
Incompatibility with the did peer specs in the 'serviceEndpoint'
#438
opened Apr 5, 2023 by
FabioPinheiro
Clarify "json": "<json of protocol message>" as input for encoding example
#423
opened Dec 21, 2022 by
tdiesler
Routing protocol doesn't explain where to put the encrypted message in the attachment
data
properties
#414
opened Nov 10, 2022 by
brianorwhatever
DIDCommMessaging reference in did-spec-registries needs updating
#412
opened Oct 13, 2022 by
brianorwhatever
recommend check for the all-zero value after key agreement
defer
won't target for v2.0
#378
opened Apr 23, 2022 by
dhh1128
shortened oob invitation and the won't target for v2.0
didcomm://
protocol scheme
defer
#351
opened Mar 25, 2022 by
TimoGlastra
Suggestion: look at implementing Crystals-Kyber as a key exchange algorithm in the spec
defer
won't target for v2.0
#315
opened Nov 26, 2021 by
marek-lach
attachments - multiple representations present?
defer
won't target for v2.0
#311
opened Nov 8, 2021 by
TelegramSam
We need a terminology section
defer
won't target for v2.0
documentation
Improvements or additions to documentation
#285
opened Sep 13, 2021 by
TelegramSam
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.