Deprecating Legacy Provider Properties, networkChanged event, and send() net_version support

[jiexi]

Currently the following properties are accessible on the MetaMask provider object:
* window.ethereum.chainId
* window.ethereum.networkVersion
* window.ethereum.selectedAddress

They allow for synchronous access to the last known value of these chain/network attributes. They are not part of the EIP-1193 spec and are not officially listed in our provider API documentation . Despite not being intended for public usage, these properties have been publicly available for some time and we can assume that there are some Dapps out there that now rely on these values being available on the MetaMask provider object. Given this, we should make a best effort to inform developers that usage of these properties is not supported, that these properties will be removed in the future, and what equivalents can be used instead.

Related to the above fields, we also plan on removing the following which have already been properly deprecated:
* networkChanged event
* net_version support in window.ethereum.send()

The above announcement can be ignored. As of September 6th 2024, we plan on continuing to support:

• window.ethereum.chainId
• window.ethereum.networkVersion
• window.ethereum.selectedAddress
• networkChanged event
• net_version support in window.ethereum.send()

In a few releases, you should stop seeing console warnings when accessing window.ethereum.chainId, window.ethereum.networkVersion, and window.ethereum.selectedAddress.

We still recommend the migrations specified in the comment below.

[Mattijah]

Before getting rid of these properties it should be make sure that eth_requestAccounts and others actually work when called. MetaMask/metamask-extension#7221

[vandan]

Please confirm whether the guidance from @jiexi on #7221 resolves the problem that had been reported there.

[vandan]

Adding some recommended alternatives for each property we intend to remove:

window.ethereum.chainId - use window.ethereum.request({method: 'eth_chainId'})
window.ethereum.networkVersion - if you actually need network version then use window.ethereum.request({method: 'net_version'}) , otherwise use eth_chainId
window.ethereum.selectedAddress - use window.ethereum.request({method: 'eth_accounts'})
networkChanged event - no exact equivalent, use the chainChanged event instead
net_version support in window.ethereum.send() - use window.ethereum.request({method: 'net_version'})

[u1x30]

To check if a MetaMask account is locked without triggering the metamask unlock popup, we currently use window.ethereum.selectedAddress. However, using window.ethereum.request({ method: 'eth_accounts' }) initiates the MetaMask popup to unlock account, and we want to avoid that. Anybody know if there an alternative method to determine if the account is locked and has an address without triggering the MetaMask popup?

[jiexi]

When called with MetaMask locked, window.ethereum.request({ method: 'eth_accounts' }) does not initiate a prompt from MetaMask to unlock the account for me. Are you able to provide steps to reproduce this behavior?

eth_accounts will return [] if no accounts are connected or if MetaMask is locked which should be equivalent to the window.ethereum.selectedAddress behavior.

[SaveSnowflake]

After one page updated and added new wallets top their page , now my hot wallet refuses to launch on it or when it does - it shows the issue, so i check the dev tools to find the exact issue

[Number000001]

With the recommended “window.ethereum.request({ method: ‘net_version’ })”, “await ethereum.request({ method: ‘eth_chainId’ });”, “await web3.eth.getChainId();”, and “await web3.eth.net.getId();”, if I change the network after connecting MetaMask to a DApp, only the network ID at the time of connection is returned, not the changed network ID.

As far as I know, if you change the network after connecting MetaMask to DApps, only “window.ethereum.networkVersion” can get the changed network ID, so I really hope it won’t be deleted.

With “window.ethereum.on(‘chainChanged’, async (chainId) =>”, I can obtain the changed network ID even if I change the network after connecting MetaMask to a DApp, but this is inconvenient, so “window.ethereum.networkVersion”, which allows me to actively obtain the changed network ID, is more convenient.

If I change the network after connecting MetaMask to a DApp, is there any other way to obtain the new network ID?

Thanks.

[elix1er]

bump

[Ryan-yang125]

Still MetaMask: 'ethereum.selectedAddress' is deprecated and may be removed in the future. Please use the 'eth_accounts' RPC method instead.
Anything update?

[stanleyseow]

How do I get rid of this metamask errors from the console ??

[Nichebiche]

Who is this

[jiexi]

Please see the updated announcement. Sorry for any inconvenience the original announcement may have caused.