I just tried to pay for Farcaster Pro on mobile using USDC from my Daimo account, and I couldn’t because I don’t have ETH in my Farcaster wallet (I do have excess USDC) I don’t know how common that is, and the list should be built from wider inputs, not just what I believe/encounter :)

Your core mission will focus on cross chain ux ? Cause most new users get tons of friction before understanding the concept of crosschain My list : a. seed-phrase and the awful experience of creating & securing a wallet (“protect your keys cause they all going to steal it 🥷 o but also vs a fire hazard!”) b. the fact that a native app has to be downloaded to connect to dapps and suffer a. c. Once a new user crossed the chasm of foolishness and finished the wallet creation experience, they shall recieve the invitation to buy 100usd of “x coin” (eth included) so wallets can make a living d. After that you got wallet connect working 60% of the time to actually play with the dapp e. After d. you have the authenticate + sign (“wtf is signing and why should i login twice? And i dnt want to sign anything i want to play this cool stuff my friend told me”) f. All this suffering only to be able to connect, remember user has no funds to do nothing I would venture this churns 98% of new users.

How AA helps the following: A. There are a number of AA wallets using passkeys to control the account. B. Only partially. Using AA+embedded wallet can work for some use-cases, but native wallet apps will always be superior. C. Wallets will embed some for-profit integrations. The default Paymaster can be configured to be profitable for the user, but the money has to come from somewhere. D. NA for us but agree this experience sucks. Talk to @walletconnect team. E. Session keys let you keep a session active as long as you are interacting with a particular dapp so your wallet won't require re-signing for every action.

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 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.

Yes! Any wallet in your review offering this already?

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 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.

Intent based bridges like across etc. have severe limitations in terms of liquidity.

See this debate on the question x.com/barnabemonno...