UX: Switch assets based on address/invoice input

[michael1011]

When a Liquid address is entered/scanned, the frontend should switch the receiving symbol the L-BTC. Similar concept for Bitcoin addresses and lightning invoices/lnurls/sat domains

[kilrau]

Also gets rid of this error where web app should revalidate my liquid address when I am switchin to Liquid:
Screencast from 01-09-2024 04:31:44 PM.webm

[dni]

Also gets rid of this error where web app should revalidate my liquid address when I am switchin to Liquid: Screencast from 01-09-2024 04:31:44 PM.webm

unrelated opened a new issue

[dni]

        try {
            const assetName = asset();
            decodeAddress(assetName, address);
            input.setCustomValidity("");
            input.classList.remove("invalid");
            setAddressValid(true);
            setOnchainAddress(address);
        } catch (e) {

i dont like it, i think the natural flow is people will choose the asset first and then paste. maybe even people will be confused and trying to send liquid to a btc address and not noticing that the asset magically switched to btc, expecting lbtc to receive.

either way i think this optimisation is too much. and currently we validate the address by trying top decode the address with the asset the user selected.

[kilrau]

either way i think this optimisation is too much

It is not, I am 100% convinced we want to do this. You don't know the support cases that Michael and I handled where we explained folks to switch the asset to Liquid "because it said invalid address". I see virtually no chance of anyone pasting an liquid address expecting to use mainchain.