This is why we need Chain Abstraction... 
How do you explain this to the newbies? It’s the same asset, but not really the same.
Terrible UX!

Luckily, we're already working on fixing this at @reown 🫡

Toolkits to build onchain UX → /reown. Builders of the WalletConnect Network. For the WalletConnect Network, please visit @walletconnect

it used to be worse select chain -> select token, so it's getting better :)

I like how 1inch is visualising 👇🏻

but still the next step of fixing cross-chain payments: I want to send 10 usdc, and use 5 from base, and 5 from optimism e.g.:

Web Team Lead & Research Team Lead @reown

Founder @payflow /payflow payflow.me /crimea 🇺🇦

Step by step…
The goal is for the user to say “I want to send USDC” and the wallet figures out where to pull it from, bridge if necessary, and complete the request however it thinks is best.
Ultimately, user choosing a chain directly should be discouraged or left as an advanced use case.

software artist | building /outpaint | ex: @coinbase ex: bisontrails | seeker of the flow state

Totally! My thinking is dapps send a request, and the wallet figures out how to complete it, with all the intermediary steps. 
Steps could be bridging or something else…
We’re making this GA in WalletKit SDK in Q1 for wallets.

Dapps still need to stop displaying/thinking in terms of asset per chain and only rely on what can be queried on-chain. I’m also working on ERC-7811 in order to address that.

shouldn't this be consolidated on the wallet side? its costs so much to do eth -> l2 conversations. absolutely horrible. i had the same cast 6 months bk. i see we're still here.

@backpack put a bank in your pocket and use your money whenever, wherever, however without permission

/backpack
/notdevin
icebreaker.xyz/notdevin

Trick question! We don’t explain to them at all because there’s no reason to ever know the differences as a user and therefore no reason to show them this view