Hi, I have a few concerns with respect to the draft of this EIP.
First is that it seems like capabilities as returned by wallet_getCapabilities are per-chain, but capabilities as specified for wallet_sendCalls is chain agnostic. Since a wallet_sendCalls request can include calls to multiple chains, I think it would make more sense to move the capabilities parameter into the call structure so that each call can specify its own capabilities based on what its chain actually provides.
My second concern is that some functionality such as the atomicBatch capability might be provided by default on all every chain a wallet supports, which could be numerous, especially for smart contract wallets. So I think it also makes sense to add a special wildcard * in place of the chain ID for those cases where a capability is universally available.
Lastly, are there any wallet implementations of this specification in the wild at this moment? It seems like this EIP addresses a missing piece of the UX puzzle, but it sounds like it’s been in development for a couple of years so it would be good to know if it’s on the road to being finalized.