Tony D’Addeo
@deodad
ditching wallet_switchEthereumChain 🔚 the stateful model of wallet connections where a wallet is connected to an application on a single chain feels broken wallets are moving towards programmatic switching and displaying all assets for all chains all the time which delivery a much better UX applications are moving towards using their own Ethereum RPC providers for public rpc requests and are only sending actions that require a signature to the wallet given this can we get rid of `wallet_switchEthereumChain` entirely and specify the chain on individuals requests like `eth_sendTransaction`? it's a common stumbling block for devs and adds a cognitive overhead since transactions needs to be wrapped in logic to inspect the current chain and switch
5 replies
7 recasts
34 reactions
Tony D’Addeo
@deodad
https://warpcast.com/manan/0xee752ea7
1 reply
0 recast
5 reactions
horsefacts
@horsefacts.eth
related: https://x.com/_jxom/status/1815144665148203139
1 reply
1 recast
5 reactions
Darryl Yeo 🛠️
@darrylyeo
This seems like a behavior /walletbeat ought to track. Under the Ecosystem category perhaps. cc @polymutex.eth
1 reply
0 recast
1 reaction
Frederik Bolding 🦊
@frederik
There is an experimental CAIP-based API for this available in MetaMask Flask, some details are available here: https://github.com/MetaMask/metamask-improvement-proposals/blob/main/MIPs/mip-5.md
0 reply
0 recast
1 reaction
carter
@carter
strong agree, had to write this the other day for bringing clanker to monad- basically a shim so all our interactions are chain agnostic and handles all the switching/network/etc really annoying though and look forward to when we can get rid of it. think it’s one of the main things holding l2s back from competing with solana
0 reply
0 recast
1 reaction
