Skip to content
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

Migrate from safeAppId to origin for messages #4420

Open
iamacook opened this issue Oct 24, 2024 · 0 comments
Open

Migrate from safeAppId to origin for messages #4420

iamacook opened this issue Oct 24, 2024 · 0 comments

Comments

@iamacook
Copy link
Member

iamacook commented Oct 24, 2024

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 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 list of requirements

  • Alter proposal of messages to submit the origin
  • Handle rendering of origin in message details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@iamacook and others