-
Notifications
You must be signed in to change notification settings - Fork 1
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
Implement SEP-10 2.1.0 Support #12
Comments
subscribing to issue notifications |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR
The SEP-10 protocol has been updated to relax the requirements of the single Manage Data operation included in SEP-10 challenge transactions, and should be implemented by October 21st. On this date the SDF will announce the SDK updates to Anchors and Wallets, urging them to update as soon as possible.
Background
To provide context, the SEP-10 2.0 changes replaced SEP-10 challenges' Manage Data operation
anchorName
key with ahome_domain
key. However, we quickly realized there was confusion and misunderstanding about the value of thehome_domain
parameter introduced in most SDKs earlier. Specifically, some users of the SDK believe thehome_domain
value is the home domain used to request the SEP-10 challenge, while others believe it is the home domain that requires the JWT authentication token.This is problematic because SDK's implemented equality checks on the
home_domain
value of the Manage Data operation, so mismatched domains would result in client-server (wallet-anchor) incompatibility.SEP-10 2.1.0 Changes
The following changes have been made to the SEP-10 protocol:
home_domain
value in a SEP-10 challenge's first Manage Data operationSIGNING_KEY
References
SEP-10 2.1.0 Changes
Go SDK SEP-10 2.1.0 Support
JavaScript SDK SEP-10 2.1.0 Support
Looking Forward
Soon after SEP-10 2.1.0 is implmenented and announced, the SDF will ask SDK's to upgrade to SEP-10 3.0, but no action needs to be taken for this yet.
The text was updated successfully, but these errors were encountered: