-
Notifications
You must be signed in to change notification settings - Fork 323
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
SEP-38: make SEP-10 token optional for some endpoints #1144
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, I think this change is good and very backwards compatible.
I make a couple suggestions below.
Could you also update the version by bumping the minor version number, and the updated field in the preamble?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with Leigh's points, but otherwise LGTM! Thanks for taking this on.
Co-authored-by: Leigh McCulloch <351529+leighmcculloch@users.noreply.github.com>
…ices` requests, to be compliant with the change made in stellar/stellar-protocol#1144.
…-38 (#79) ### What Update tests to make it compliant with the new version of [SEP-38](https://stellar.org/protocol/sep-38): * `QUOTE_SERVER` is actually meant to be `ANCHOR_QUOTE_SERVER`. * Since [stellar-protocol#1144](stellar/stellar-protocol#1144), only the `/quote(s)` endpoints require SEP-10 authentication.
What
Make SEP-10 token optional for the endpoints:
GET /info
GET /price
GET /prices
Why
Client applications may want to show rates from multiple liquidity providers to a user, or simply display the exchange rates of an anchor's pairs before the user has indicated they want to start a transaction.
Closes #1086.