Description
I think there's some interesting room for extensibility here and that this sort of protocol could open up many more use cases. Authentication is one use case out of many. One of the areas of extensibility is the ability to request data from the wallet.
We could add an optional scope property and different wallets can optionally support their own scopes. For example, a wallet could accept a query string of ?scope=nft and in the callback request body, list out all the NFTs that belong to that wallet. This would work for any sort of blockchain or smart contract data, as the user should trust their wallet. Wallets can allow other data to be requested, for example the name of the wallet. A dApp can then use this when displaying built transactions and display a personalized message, such as Scan this with your Stratis wallet or Copy this into your CoinVault wallet.
Alternatively you could integrate the ability to make transactions using different addresses in your wallet. A wallet that supports a query string of ?scope=addresses could return a list of addresses for the user. A dApp can then identify the user owns other addresses, allowing them to use it with a different address for each transaction, so privacy is not compromised.