Skip to content

Conversation

@Mrtenz
Copy link
Member

@Mrtenz Mrtenz commented Aug 13, 2024

This removes wallet_switchEthereumChain from the BLOCKED_RPC_METHODS list.

Closes MetaMask/MetaMask-planning#2938.
Closes #2654.

Blocked by:

@codecov
Copy link

codecov bot commented Aug 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.08%. Comparing base (2dcaecd) to head (03a3b7e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2634   +/-   ##
=======================================
  Coverage   98.07%   98.08%           
=======================================
  Files         398      399    +1     
  Lines       10976    10991   +15     
  Branches     1728     1731    +3     
=======================================
+ Hits        10765    10780   +15     
  Misses        211      211           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Mrtenz Mrtenz marked this pull request as ready for review August 13, 2024 07:27
@Mrtenz Mrtenz requested a review from a team as a code owner August 13, 2024 07:27
@Mrtenz Mrtenz force-pushed the mrtenz/unblock-wallet_switchEthereumChain branch from 2a66d50 to fd11f16 Compare August 21, 2024 11:01
@Mrtenz
Copy link
Member Author

Mrtenz commented Aug 21, 2024

@metamaskbot update-pr

@socket-security
Copy link

socket-security bot commented Aug 21, 2024

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

@Mrtenz
Copy link
Member Author

Mrtenz commented Aug 21, 2024

@SocketSecurity ignore npm/@metamask/[email protected]

This is ours.

@Mrtenz Mrtenz marked this pull request as draft August 21, 2024 11:36
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future we could consider full support for wallet_switchEthereumChain, and actually updating the provider configuration etc., but for now this simply makes the wallet_switchEthereumChain method always return null.

Mrtenz added a commit that referenced this pull request Oct 8, 2024
This adds a `isSnapId` function which accepts any value, and returns a
boolean if the input is a valid Snap ID or not.

This is extracted from #2634.
@Mrtenz Mrtenz force-pushed the mrtenz/unblock-wallet_switchEthereumChain branch from f2aa83e to 1dcbeda Compare January 15, 2025 11:46
@Mrtenz
Copy link
Member Author

Mrtenz commented Jan 15, 2025

@SocketSecurity ignore npm/[email protected]

Only used for development / testing, and pending update in another PR.

@SocketSecurity ignore npm/@metamask/[email protected]

This is ours.

*/
export const onRpcRequest: OnRpcRequestHandler = async ({ request }) => {
const { chainId = '0x1' } = (request.params as BaseParams) ?? {};
await switchChain(chainId);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably not a problem, but i think always using mainnet makes it possible in the extension e2e tests that use this snap to try to hit the mainnet infura endpoint, but I think that's probably only the case if something triggers getGasPrice and i'm not certain there is an extension e2e test that does that. Just pointing this out in case I am wrong

@jiexi
Copy link

jiexi commented Jan 21, 2025

sorry, I realize this PR is still marked as draft, so sorry for the early nit comments

@Mrtenz Mrtenz force-pushed the mrtenz/unblock-wallet_switchEthereumChain branch from 736f8f1 to afa3bc5 Compare February 12, 2025 10:49
@Mrtenz Mrtenz force-pushed the mrtenz/unblock-wallet_switchEthereumChain branch from 607162c to 5e27ac2 Compare February 12, 2025 12:54
@Mrtenz Mrtenz marked this pull request as ready for review February 13, 2025 09:34
@Mrtenz Mrtenz force-pushed the mrtenz/unblock-wallet_switchEthereumChain branch from 3612252 to ff78991 Compare February 21, 2025 09:37
@Mrtenz Mrtenz force-pushed the mrtenz/unblock-wallet_switchEthereumChain branch from 838ce80 to 31ffcbf Compare May 15, 2025 14:16
@FrederikBolding FrederikBolding added this pull request to the merge queue May 15, 2025
Merged via the queue into main with commit da0d581 May 15, 2025
115 checks passed
@FrederikBolding FrederikBolding deleted the mrtenz/unblock-wallet_switchEthereumChain branch May 15, 2025 18:22
Mrtenz added a commit to MetaMask/metamask-extension that referenced this pull request May 19, 2025
Like with websites, we want to support a custom network per Snap rather
than relying on the globally selected network. For Snaps, the permission
for the network to switch to is automatically granted.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/26389?quickstart=1)

1. Copy the build files for `@metamask/selected-network-controller` from
[this PR](MetaMask/core#4602).
2. Copy the build files for `@metamask/snaps-controllers` and
`@metamask/snaps-execution-environments` from [this
PR](MetaMask/snaps#2634).
3. Run `test-snaps` for the PR above (`yarn start` in
`packages/test-snaps`).
4. Install the Ethereum Provider Example Snap.
5. Switch the chain ID using the `test-snaps` button for the Ethereum
Provider example.
6. The Snap should now use the new network, without any permission
requests.

Step 1 and 2 are no longer necessary once these PRs are merged and
released.

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

<!-- [screenshots/recordings] -->

<!-- [screenshots/recordings] -->

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet