We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
safeAppId
origin
The inclusion of an origin field for message proposals was requested, and subsequently implemented on the Transaction Service and Client Gateway.
It is now possible to propose the origin directly, instead of it being inferred by the safeAppId. The origin is now also returned in a message.
After the above has been tackled, safeAppId will be deprecated on the Transaction Service/Client Gateway.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the feature about
The inclusion of an
origin
field for message proposals was requested, and subsequently implemented on the Transaction Service and Client Gateway.It is now possible to propose the
origin
directly, instead of it being inferred by thesafeAppId
. Theorigin
is now also returned in a message.After the above has been tackled,
safeAppId
will be deprecated on the Transaction Service/Client Gateway.The list of requirements
origin
origin
in message detailsThe text was updated successfully, but these errors were encountered: