feature request: user favorite payment chains

[arilotter]

allow a user to publish a lexicon record indicating on which chains they'd prefer to receive payments

this could be exposed in the send UI as a suggestion

[stella3d]

yes, i agree. right now it just works via alsoOn, as a list. but i could see the user wanting to change the order.

do you have a proposal for the lexicon?

i think it could be simple - an array of integers, in order of descending preferences like

[8453, 1]

or maybe objects with an optional short text note

[
  {
    "chain": 8453,
    "note": "strongly preferred"
  },
  {
    "chain": 1
  }
]

[stella3d]

also - how should this interact with smart contract wallets?

as mentioned in the previous issue, the chainId from the sign in message is supposed to require that smart contract wallets only ever be resolved on that same chain.

currently we don't explicitly specify that a wallet is multisig / contract or not, so it's not easy to just ignore that record if it's a multisig. they'd have to sign in / link multiple times to have the contract work on multiple chains i think.

[arilotter]

yeah, there are a bunch of weird edge cases where technically a smart contract wallet address isn't "yours" unless you have a verified signature for that specific chain. a wallet could be constructed to allow different people to own the same address on different chains, and even e.g. always return true for some siwe is valid signature.

so, like you said, smart contract wallets would need one signature per chain, for safety, yeah 😭

the status quo for detecting a multisig is to check that there is no smart contract at the user's address on the chain they originally signed for, AND the signature doesn't have the 6492 wrapper (ends with 0x6492649264926492649264926492649264926492649264926492649264926492)

if there's no contract at the addr and the sign doesn't have the magic suffix, it must be an EoA, and you can (probably) safely assume their signature is valid for all chains.

wrt a chains list, I think a single list of numbers in descending order of preference is great.

[stella3d]

@arilotter ok, I think I will do a single ordered list in descending preference, with an optional short note, as I described above. that makes it easy and matches mostly with the existing alsoOn field in the addressControl record.

one advantage of doing it via that alsoOn field is that it means only one record has to be fetched. but it has the disadvantage of not being able to re-order the first one - the UI assumes it's the one you signed on.

what if we put this lexicon item into a optional field in the existing record called like chains, and I deprecate alsoOn? that way it's just one fetch and we get everything.

only issue would be if anything starts building on club.stellz.evm.addressControl records by referring to their CIDs in a strongRef - which I might do?

having said that, it makes me now lean back to having the chain list published as a separate record that's expected to mutate, and leave the original addressControl record unmutated so other things can refer to it by its CID (instead of having to specially understand that new group fields don't matter)