eth_accounts method triggering connection request about enkrypt HOT 5 CLOSED

Actually 'eth_requestAccounts' is mentioned on EIP-1193 and 1102:

The return value of eth_accounts is ultimately controlled by the Wallet or Client. In order to protect user privacy, the authors recommend not exposing any accounts by default. Instead, Providers should support RPC methods for explicitly requesting account access, such as eth_requestAccounts (see EIP-1102) or wallet_requestPermissions (see EIP-2255).

Yes thats why we have support for both, you'd be surprised how many dapps dont use eth_requestAccounts

from enkrypt.

eth_accounts is also a call to get user accounts, I would suggest to use eth_requestAccounts before doing eth_accounts, you can detect whether user is using enkrypt by either checking window.ethereum.isEnkrypt or window.enkrypt

from enkrypt.

eth_accounts is used to get the user account but not for requesting permission, that's requestAccounts method. Otherwise why having two method that do the same thing?

I'm using eth_accounts to get the user account silently in case is connected since I'm not saving sessions on localStorage I need a way to know whether the user is connected or not without requesting a connection

from enkrypt.

eth_accounts is the standard way of getting user accounts, and eth_requestAccounts is something metamask introduced along the way and is not part of the standard. We want to make sure our users are aware whenever a dapp try to get user accounts using either way.

from enkrypt.

Actually 'eth_requestAccounts' is mentioned on EIP-1193 and 1102:

The return value of eth_accounts is ultimately controlled by the Wallet or Client. In order to protect user privacy, the authors recommend not exposing any accounts by default. Instead, Providers should support RPC methods for explicitly requesting account access, such as eth_requestAccounts (see EIP-1102) or wallet_requestPermissions (see EIP-2255).

from enkrypt.