- If I don't have the browser wallet installed, I see "get started" on the connect button, otherwise I see "Connect" there. (<aname="0002-WCON-002"href="#0002-WCON-002">0002-WCON-002</a>)
- If I don't have the browser wallet installed, when I press "Get started" I can see immediately a way to get the Vega wallet browser extension. (<aname="0002-WCON-0010"href="#0002-WCON-0010">0002-WCON-0010</a>)
- If I do have the browser wallet installed, I can easily choose to connect to it. (<aname="0002-WCON-0011"href="#0002-WCON-0011">0002-WCON-0011</a>)
- If the desktop wallet or CLI is detected as running, I can see that and choose to connect with my desktop / CLI wallet. (<aname="0002-WCON-0012"href="#0002-WCON-0012">0002-WCON-0012</a>)
- If there is not running desktop wallet or CLI detected, I can see that I need to open my wallet. (<aname="0002-WCON-0013"href="#0002-WCON-0013">0002-WCON-0013</a>)
- I can find out more about supported browsers i.e. there is a link (Issue "List compatible browsers" vegawallet-browser#360 has to be implemented). (<aname="0002-WCON-0013"href="#0002-WCON-0013">0002-WCON-0013</a>)
- I can find out more about the Vega Wallet and see what "other" versions there are i.e. there is a link to the page on the website (currently - https://vega.xyz/wallet#overview). (<aname="0002-WCON-0014"href="#0002-WCON-0014">0002-WCON-0014</a>)
- The browser extension you need is automatically detected if you are using Chrome or Firefox, presenting the specific call to action to install that browser extension in a visible way e.g. with a Chrome or Firefox icon. (<aname="0002-WCON-041"href="#0002-WCON-041">0002-WCON-041</a>)
- The browser extension store opens in a new tab on the Vega Wallet extension page (Chrome or Firefox). (<aname="0002-WCON-042"href="#0002-WCON-042">0002-WCON-042</a>)
- When the browser I am using is not Firefox or Chrome, there is a way to download the browser extension anyway but at my own risk i.e. I can see options for both the chrome and firefox extensions in the CTA. (<aname="0002-WCON-043"href="#0002-WCON-043">0002-WCON-043</a>)
- There is a way to understand the browser extension is an Alpha release e.g. there is a label / description. (<aname="0002-WCON-044"href="#0002-WCON-044">0002-WCON-044</a>)
- **must** submit attempt to connect to wallet (<aname="0002-WCON-005"href="#0002-WCON-005">0002-WCON-005</a>)
- if the dapp DOES already have a permission with the wallet: **must** see that wallet is connected (<aname="0002-WCON-007"href="#0002-WCON-007">0002-WCON-007</a>) note: if the user want to connect to a different wallet to the one that they were previously connected with, they will have to hit logout.
- if the app uses one key at a time: **should** show what key is active (re-use the last active key) (<aname="0002-WCON-008"href="#0002-WCON-008">0002-WCON-008</a>)
- if the wallet does NOT have an existing permission with the wallet: **must** prompt user to check wallet app to approve the request to connect wallet: See [Connecting to Dapps](0002-WCON-connect_vega_wallet.md#connect-wallet) for what should happen in wallet app (<aname="0002-WCON-009"href="#0002-WCON-009">0002-WCON-009</a>)
- if new keys are given permission: **must** show the user the keys have been approved (<aname="0002-WCON-010"href="#0002-WCON-010">0002-WCON-010</a>)
- if the dapp uses one key at a time: **should** prompt me to select key. See [select/switch keys](#select-and-switch-keys). (<aname="0002-WCON-014"href="#0002-WCON-014">0002-WCON-014</a>)
- if user rejects connection: **must** see a message saying that the request to connect was denied (<aname="0002-WCON-015"href="#0002-WCON-015">0002-WCON-015</a>)
- if the dapp is unable to connect for technical reason (e.g. CORS): **must** see an explanation of the error, and a method of fixing the issue (<aname="0002-WCON-016"href="#0002-WCON-016">0002-WCON-016</a>)
... so I can use the interface to read data about my key/party or request my wallet to broadcast transactions to a Vega network.
## Disconnect wallet
When wishing to disconnect my wallet, I...
- **must** see an option to disconnect wallet (<aname="0002-WCON-022"href="#0002-WCON-022">0002-WCON-022</a>)
- **must** see confirmation that wallet has been disconnected (<aname="0002-WCON-023"href="#0002-WCON-023">0002-WCON-023</a>)
... so that I can protect my wallet from malicious use or select a different wallet to connect to
## Select and switch keys
when looking to do something with a specific key (or set of keys) from my wallet, I...
- **must** see what key is currently selected (if any) (<aname="0002-WCON-025"href="#0002-WCON-025">0002-WCON-025</a>)
- **must** see a list of keys that are approved from the connected wallet (<aname="0002-WCON-026"href="#0002-WCON-026">0002-WCON-026</a>)
- for each key:
- **must** see the first and last 6 digits of the [public key](DATA-data_display.md#public-keys). (<aname="0002-WCON-027"href="#0002-WCON-027">0002-WCON-027</a>)
- **must** be able to copy to clipboard the whole public key (<aname="0002-WCON-029"href="#0002-WCON-029">0002-WCON-029</a>)
- **must** see the key name/alias (meta data) (<aname="0002-WCON-030"href="#0002-WCON-030">0002-WCON-030</a>)
- **must** see the option to trigger a re-authenticate so I can use newly created keys (<aname="0002-WCON-035"href="#0002-WCON-035">0002-WCON-035</a>)
...so that I can select the key(s) that I want to use.
