Was just reading the latest version of ERC-2525. A couple thoughts:
- Ensure either some measure of privacy about the user’s choice of which client they use, or a robustness to the paths of their choice such that the choice could not be faked by a malicious dapp in order to target them and their cryptocurrency. I’m not quite sure how one would go about doing this, but it is important if this preference were to live on-chain that there is guards against such malicious behavior on the user side.
- Internationalization choices might be nice to consider as a part of this standard. See ERC-1444 for inspiration or integration: EIP-1444: Localized Messaging with Signal-to-Text
- Not sure if this is the right place, but it seems related to the idea I’ve been considering with ERC for "Execute as". The basic idea of having a set of handlers that the user chooses for how their web3 connection should be handled (and how transactions are submitted, etc.) would integrate nicely here. Instead of maintaining a bunch of dapp-specific or wallet-specific functionality, this could serve as a common standard for translation of multi-party, smart-contract based accounts to the front-end user. If it makes sense, please consider that with this proposal.