Forwarding GitHub comments:
Multiple Connections
Speaking on behalf of the larger Wagmi consumers, I would really appreciate if this supported multiple Accounts.
While the point of “By constraining the account return to a single address, this ERC simplifies developer experience while still supporting richer capability results.” is made, I don’t really see how supporting multiple accounts with their capabilities really degrades developer experience as 99% of the time applications will be using developer tooling that abstracts over these JSON-RPC methods (ie. Wagmi Connectors, etc).
Even if no developer tooling existed, I still don’t think DX would be degraded as applications could just use the first item in the array anyway, and ignore the others (this was Wagmi behavior pre-v1). In fact, user experience would be moreso degraded as users would have to
their current account, and then connect their other account" to achieve previous behavior.
I think capabilities per-account also makes sense, because you wouldn’t really be able to specify fine-grained capabilities (per-account) in the request anyway, so it would always be Should this just be an array of supported chains? Consumers can use wallet_getCapabilities to extract capabilities from a Wallet.implied that it is batched across all accounts (for example, a SIWE signature for each account).
supportedChainsAndCapabilities
Should the response of wallet_connect just return an array of chains instead of chains and capabilities (supportedChainsAndCapabilities)?
I wonder if it makes sense to omit the assumption that a Wallet “should” be connected to obtain it’s capabilities in ERC-5792 while it’s still in review because this limits the capabilities we can pass to wallet_connect if we don’t even know what capabilities the wallet supports (this is Kames’ point).