Closed salimtb closed 1 month ago
Hey @salimtb. Thanks for reporting! I will pass this on to the team.
Hi @anaamolnar, I reported this issue previously. It has now been resolved. I was under the impression that Metamask would use the CoinGecko API for price data, but I later discovered that it uses data from CryptoCompare.
The issue can be closed, as the price displayed now accurately reflects BEAM.
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 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
[Bug]: Token price is not displayed correctly for some native tokens.
Expected behavior
should display this price
Screenshots/Recordings
No response
Steps to reproduce
Error messages or log output
No response
Version
11.5.0
Build type
None
Browser
Chrome, Firefox, Microsoft Edge, Brave
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response