-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add FEG #1416
Add FEG #1416
Conversation
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
approve means, will the logo update ? |
I checked there's no change in Meta Mask |
Approved.
…On Mon, 27 Jan 2025 at 11:18 PM, michael - blurpesec < ***@***.***> wrote:
Merged #1416 <#1416>
into master.
—
Reply to this email directly, view it on GitHub
<#1416 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOZDSA7UWCYAOSVGQHFLKST2MZWPJAVCNFSM6AAAAABV5OHX6SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWGA4DCOJSGA3TEOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
We didn’t see any change
On Mon, 27 Jan 2025 at 11:53 PM, Contact ***@***.***>
wrote:
… Approved.
On Mon, 27 Jan 2025 at 11:18 PM, michael - blurpesec <
***@***.***> wrote:
> Merged #1416 <#1416>
> into master.
>
> —
> Reply to this email directly, view it on GitHub
> <#1416 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BOZDSA7UWCYAOSVGQHFLKST2MZWPJAVCNFSM6AAAAABV5OHX6SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWGA4DCOJSGA3TEOA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***
> com>
>
|
can anyone please explain the status, I'm really confused. I didn't see any changes yet |
@MRabenda we're in bsc 0xF3c7CECF8cBC3066F9a87b310cEBE198d00479aC(BEP-20) |
@RTR-code this repo supports only Ethereum contracts - if you want to add asset from another network would you guys be able to replace your token image in Coingecko list? |
we have updated logo since a year but Meta mask not updated token yet coin gecko link: https://www.coingecko.com/en/coins/feg-token |
actually before one month we're live in eth and base chain but unfortunately we paused trading in eth and base bcz of some reason now we're only live in bsc and in all crypto platforms our token is updated with new info since a year but only meta mask is showing our old logo, any guide would really appreciate @MRabenda |
@MRabenda any response please |
Hey @RTR-code we did some cache update - would you mind to check again? |
@MRabenda I just now checked no change has occurred for both bsc and eth chain, still displaying old logo |
@MRabenda can you please share if you see any change from your end |
@MRabenda it's changed thank you for kind support |
No description provided.