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

Wrong Deposit and Withdraw Info. #120

Open
bilalhassan555 opened this issue Jun 15, 2022 · 5 comments
Open

Wrong Deposit and Withdraw Info. #120

bilalhassan555 opened this issue Jun 15, 2022 · 5 comments

Comments

@bilalhassan555
Copy link

https://api.gateio.ws/api/v4/spot/currencies
In this endpoint, MDX_BSC withdrawal is enabled.
gateio_api

But in website,
mdx_withdraw_page

No BSC chain present in this!!!!.
10SET, POLC, KTN - here are some examples in BSC chain that says deposit or withdrawal is available.

KABY, CNAME - here are some examples in MATIC chain that says deposit or withdrawal is available.

The list is not ending here. these are some examples.
This is so serious that API is misguiding users by providing false information.

@revilwang
Copy link
Collaborator

Yes, we're working on this to ensure the API's configuration is consistent with what's shown on the web page.

@bilalhassan555
Copy link
Author

As you are working on that endpoint, is there any other endpoint that shows correct deposit and withdraw info in certain chain?

@bilalhassan555
Copy link
Author

Yes, we're working on this to ensure the API's configuration is consistent with what's shown on the web page.

hey revilwang,
Its more than two months now. No correction is made. You are spreading misinformation here regarding deposit and you are responsible to release the token if anyone deposit a token via API information.

@revilwang
Copy link
Collaborator

revilwang commented Aug 23, 2022

Sorry for the trouble. Actually the issue has been addressed several times .I'll contact the implementation to confirm what causes the problem continuously appearing.

@bilalhassan555
Copy link
Author

Sorry for the trouble. Actually the issue has been addressed several times .I'll contact the implementation to confirm what causes the problem continuously appearing.

May I know how many Years you need to FIX this simple issue???

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