Skip to content
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

Request to add Xone Chain (XOC) to MetaMask popular networks #30425

Open
9 tasks
Mangosagos opened this issue Feb 19, 2025 · 0 comments
Open
9 tasks

Request to add Xone Chain (XOC) to MetaMask popular networks #30425

Mangosagos opened this issue Feb 19, 2025 · 0 comments

Comments

@Mangosagos
Copy link

What is this about?

As a user, I hope to be able to add Xone Chain through the popular network list when using Matamask, without having to operate through the custom network addition method.

In addition, any media information about Xone Chain in the custom added network cannot be effectively identified. I hope to make preliminary network information confirmation with the Xone Chain Logo.

Scenario

  • Users are able to add Xone network through the add popular network feature;
  • No tooltip is shown for Xone in the network list screen of the 'add popular networks' feature;
  • The network uses Infura's endpoint as we always want to use rpc endpoints that we know comply to our privacy policy.
  • The Infura key should not be revealed to users when users review the details for the Xone network in Settings > Networks.

Design

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

  • Users are able to add Xone network through the add popular network feature;
  • No tooltip is shown for Xone in the network list screen of the 'add popular networks' feature;
  • The network uses Infura's endpoint as we always want to use rpc endpoints that we know comply to our privacy policy.
  • The Infura key should not be revealed to users when users review the details for the Xone network in Settings > Networks.

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants