NEAR/My NEAR wallet to use local private key to verify owner

[tituszban]

Description

The NEAR web wallet stores the function access private keys it used to sign in, in local storage. Instead of having to go to a redirect, it would be much better, if it just used those, to sign the requested message.

If applicable add: Relates to #318

Acceptance Criteria

Update the NEAR and My NEAR (and other web wallets where applicable) to use the local storage keys to sign a message.

Alternatively, allow verifyOwner to specify if a function access or full access key should sign the message, and only redirect to the wallet if full access keys were requested.

[AmmarHumackicSQA]

Hey @tituszban , thanks for raising this issue! We will take a look at this, as we are already investigating the reuse of the LAK (limited access key) stored in local storage.

Regarding verifyOwner (and the #318 you mentioned), there is a NEP in the works that should be raised soon. You can check the draft of it here: https://github.com/near/NEPs/pull/413

[amirsaran3]

@tituszban The current implementation of verifyOwner in wallet-selector is not right. verifyOwner should be used before signing in without a wallet. We are working on a standard and implementation for this.

NEP: https://github.com/near/NEPs/pull/413

If you have other questions feel free to reopen this issue.