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.

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.

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

I had started putting together a doc for you on this! I can send it over next week

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

Is there a list of these wallets? I don’t think this is a criterion on Walletbeat yet

multi-address resolution for ENS names! currently a lot of wallets make a pretty unsafe assumption that the ETH address a name resolves to is accessible across chains, which is not always true in the case of smart contracts

happy to explain this further, or luc would know the details if he's still helping out with walletbeat