Conversation
|
update this |
|
logo link given |
|
what is the goal of this PR |
|
This PR updates the blockchain name and logo to reflect the new branding. No changes to chain ID or RPC endpoints. |
|
Hi maintainers, |
|
update Pr i tell you Reason |
Hi maintainers, |
|
resolve conflict file code update |
|
Please update code check I resolve remove code
…On Mon, Feb 23, 2026, 3:23 PM Define101 ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In utils/fetch.js
<#2512 (comment)>:
> @@ -51,13 +51,11 @@ export function populateChain(chain, chainTvls) {
if (chainSlug !== undefined) {
const defiChain = chainTvls.find((c) => c.name.toLowerCase() === chainSlug);
- return defiChain === undefined
remove this change
—
Reply to this email directly, view it on GitHub
<#2512 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYJXGD7PISQHJWQ37FJB62T4NLE23AVCNFSM6AAAAACVHYWVKGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTQNBQGA3DQNJSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
please update my pr |
|
today no update |
|
please update PR 3 daily no response form your Side |
|
i am waiting so many daily to live show my chain rename my chain name |
|
please review this |
If you are adding a new RPC, please answer the following questions.
Link the service provider's website (the company/protocol/individual providing the RPC):
Provide a link to your privacy policy:
If the RPC has none of the above and you still think it should be added, please explain why:
Your RPC should always be added at the end of the array.