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.

Sign up for GitHub

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

Jump to bottom

Handle both legacy and current @type values in forward messages #119

Open

mirgee opened this issue Sep 1, 2021 · 0 comments

Contributor

mirgee commented Sep 1, 2021

Currently, agency expects and uses legacy @type attribute for forward messages:

did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/routing/1.0/forward

However, as per aries spec (see here), a different value should be used for the attribute:

https://didcomm.org/routing/1.0/forward

Agency should support both formats for some time in order to remain backwards compatible.

Analogous change was already implemented in aries-vcx (see here).

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment