hmm, I guess you want this to be tied to account request to avoid yet another back and forth for wallet connect protocol, right ?
Is wallet_accounts the equivalent of eth_requestAccounts (https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1102.md) or is wallet_accounts to be called after the user enabled access via eth_requestAccounts ?
If it is the former, I see the benefit in proving ownership in one call, instead of having to do it with another call.
If it is not, I would say such ownership proof should be added to eth_requestAccounts instead.
I would still advocate for another variant, that can be used any time after the wallet authorized the application via eth_requestAccounts
This is what I wanted to propose as autoSign so application can continuously request data to be signed by the wallet without requiring user input. This can be used to communicate to a verifying endpoint without requiring sessions for example.
So we would have
{
"id": 1,
"jsonrpc": "2.0",
"method": "wallet_accounts",
"params": ["cbaff650-8d35-4106-8c28-394615d62e2c"]
}
OR if wallet_accounts is to be called after user authorized access, we should do that there instead with :
{
"id": 1,
"jsonrpc": "2.0",
"method": "eth_requestAccounts",
"params": ["cbaff650-8d35-4106-8c28-394615d62e2c"]
}
And on top of that we would also have :
{
"id": 1,
"jsonrpc": "2.0",
"method": "wallet_autoSign",
"params": ["<account address>", "<payload>"]
}