Each goal has clear leads, ensuring the EF’s resources are allocated towards maximal impact. 

- Scale L1: @ansgar.eth & me
- Scale L2: @fradamt & @ralexstokes 
- Improve UX: @rudolf & @barnabe 

To top it off, @dankrad will set strategy alongside each of us!

Talk (crosschain) UX to me!

We’re looking to identify, build and support pragmatic solutions to fix some of the most common user problems on Ethereum, with an amplified focus and the means to deliver.

walletbeat

Protocol::Improve UX at Ethereum Foundation

https://protocol.ethereum.foundation

What criteria should /walletbeat require of wallets for cross-chain UX?
Currently we look for ERC-7828 or ERC-7831 address support when sending tokens and copying the user's own address.
Is there more we should look for?
(Transparent bridging support perhaps?)

Contributor @ /walletbeat.

Censorship resistance requires privacy.

By transparent do you mean exposing the vendor/trust assumptions if you allow the user to bridge from the wallet?

I can also think of consolidated balances/asset discovery functions

Well, we've been prioritizing expanding and finalizing the attribute set prior to digging into each and every wallets, as the attribute informs what to look for when researching wallets. So haven't done that much wallet review, as reflected by all the "unrated" pie slices on https://beta.walletbeat.eth.limo 😅

That said, off the top of my head, a global cross-chain balance view is fairly commonplace nowadays. It is implemented by at least Rabby, Rainbow, and Coinbase Wallet. Metamask also has a "portfolio" view which essentially implements the same thing. However, while they all show a total account figure which sums up the account value across all chains, each entry in the breakdown is about a specific single-chain token balance. So if you have USDC on 2 chains, that shows up as 2 entries, there's no consolidated "USDC cross-chain balance" entry.

I also haven't yet seen any wallet that implements seamless bridging, though manual bridging options do exist within these wallets.

Yes! Any wallet in your review offering this already?

I guess I meant "seamless" rather than "transparent". Something like: if a dapp requests a payment for 5 USDC on chainID X, but the user's USDC balance on chain X is insufficient, automatically offer the user to bridge 5 USDC from chain Y to chain X before going ahead with the original transaction. (And yes, it should show the trust assumptions of the bridging method being used for the bridging transaction.)

Such a feature and consolidated balance view seems like they should be mutually required, because only implementing one without also implementing the other would probably lead to even more user confusion than it solves.

Filed issue about this here: https://github.com/walletbeat/walletbeat/issues/164