You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
@aakilfernandes currently it's meant to be the assetPairs where currently have maker orders. We do see the value in having an endpoint for assetPairs that are supported. We have been thinking about adding an additional endpoint to the SRA spec for this. Thoughts on this approach?
Got it. I think its fine to have asset_pairs have only current pairs, but it would be good to have an additional endpoint with supported pairs. The reason is that UIs and can (if supported pairs is made public) allow users access to different relayers depending on which asset pairs they support. One trickiness with showing supported pairs is that some relayers will accept anything, and some relayers may want a "blacklist" instead of a "whitelist"
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey, is asset_pairs supposed to give a list of supported asset pairs, or a list of asset_pairs which currently have maker orders
The text was updated successfully, but these errors were encountered: