Process question: external custom network icon PRs for MetaMask Extension and Mobile

Description:

I would like to ask about the correct process for external custom network icon contributions.

I opened two small PRs for KONET custom network icon support:

  • MetaMask Extension PR #41640
  • MetaMask Mobile PR #28642

Both PRs are UI-only icon mapping changes.

They do not touch:

  • RPC defaults
  • Transaction flows
  • Signing logic
  • Permission logic
  • Security-sensitive paths

Current status:

  • Both PRs have been open and ready for review since mid-April.
  • I have rebased them against the latest upstream/main.
  • I have resolved merge conflicts when they occurred.
  • I have left follow-up comments on the PRs.
  • No reviewer has been assigned yet.

I am not asking for an urgent merge.

I would like to confirm the correct process or owner for this type of contribution.

Purpose:

Confirm whether external custom network icon PRs are currently accepted for MetaMask Extension and Mobile.

Specifically, I would like to know:

  1. Are external custom network icon PRs currently accepted?
  2. If yes, is there a specific team, reviewer group, or process for this type of contribution?
  3. If no, should these PRs be closed or handled through another repository/process?

If MetaMask is not currently accepting this type of contribution, I can stop actively maintaining

Extension/Mobile/Both:

Both.

This affects:

  • MetaMask Extension
  • MetaMask Mobile

Images/Attachments:

No additional images are attached here.

Relevant GitHub PRs:

  • MetaMask Extension PR #41640 in MetaMask/MetaMask-extension
  • MetaMask Mobile PR #28642 in MetaMask/MetaMask-mobile

Hi @hong and thanks a lot for reaching out about this!

I can confirm that the 2 PRs approach is the right one, I’ll share below 2 example PRs from the past for mobile and extension so you can cross check them with your own.

Extension: fix: add mode logo by salimtb · Pull Request #29870 · MetaMask/metamask-extension · GitHub
Mobile: fix: add kaia logo by salimtb · Pull Request #12860 · MetaMask/metamask-mobile · GitHub

I’ll check with the team about this as well, we’ll let you know as soon as we have any updates! :smiley: :hot_beverage:

Hi @Coffee7643,

Thank you for confirming that the two-PR approach is the correct one.

I will cross-check my Extension and Mobile PRs against the Mode and Kaia examples you shared.

For now, I’ll stop actively rebasing the PRs unless the team asks me to resolve conflicts again or requests specific changes.

Thanks again for checking with the team.

Hi @Coffee7643,

Just following up on this.

I cross-checked my PRs against the Mode and Kaia examples you shared, and the overall approach still looks aligned: separate PRs for Extension and Mobile, limited to network/icon mapping changes.

The two PRs are still open with no reviewer assigned yet:

  • MetaMask Extension PR #41640
  • MetaMask Mobile PR #28642

I understand the team may be busy, so this is not an urgent merge request.

I just wanted to ask whether there is any update on the correct owner/process for this type of external custom-network icon contribution.

If there is a specific change needed in either PR, I’m happy to update them.

Thank you.

It’s likely your PRs are just in the review queue and may take some time. You could also follow up with MetaMask support to help get them reviewed sooner

Thanks for the suggestion. I’ll also check with MetaMask Support to see if there is a proper process or owner for external custom network icon PRs.

For context, the Extension and Mobile PRs are already rebased against the latest main branch and are currently waiting for review/workflow approval.

Thanks for the suggestion.

I checked the MetaMask Help Center, but it appears to be mainly for wallet/user support issues rather than GitHub PR review routing.

Since this is about external custom network icon PRs for MetaMask Extension and Mobile, would the community forum or GitHub PRs be the better place to continue asking for the proper owner/process?

Hey there Hong, both the forum here & Github would work fine as outlets for this process.

That said, I’ve pinged the team internally to see if they could check in on this – keep an eye on some progress there over the course of this week & definitely check in next week if things haven’t advanced.