Closed goldxchain closed 7 months ago
This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.
bump
This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.
This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.
Describe the bug
Hi You are currently pulling price data for $GOLDX from the wrong Coin/Token This is my blockchain here:
https://explorer.goldxchain.io//
Here is the holders/accounts list of our $GOLDX Coin (not eToros where you are currently pulling the proce from) :
https://explorer.goldxchain.io/accounts
This is where you’re pulling our current price from which isn’t our Coin:
https://www.cryptocompare.com/coins/goldx/overview)
Please can you disable the endpoint from where you are pulling this data from as it is causing confusion in the community
Steps to reproduce
1. Open metamask
New RPC URL https://mainnet-rpc.goldXchain.io/
Chain ID 42355
Currency symbol GOLDX
Block explorer URL https://explorer.goldXchain.io/
Error messages or log output
No response
Version
10.29
Build type
None
Browser
Chrome
Operating system
Windows, MacOS, Linux
Hardware wallet
No response
Additional context
No response