@polymutex.eth

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.

1 reply

0 recast

1 reaction