Page Comparison

Versions Compared

Key

This line was added.
This line was removed.
Formatting was changed.

...

Visual

Functionality

Create/Edit New Wallet

Connect

Modified https://fioprotocol.atlassian.net/wiki/spaces/PROD/pages/255591518/Dashboard+FIO+Token+FIO+Request+FIO+Data#Create%2FEdit-New-Wallet
- Connect
  - Use Ledger Hardware Wallet
    - When checked
      - Connect to Ledger Device using latest Ledger SDK and Hardware app being developed in
        Jira Legacy
        server System JIRA
        serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d
        key WP-91
        If Ledger device not connected, show Connect Page
      - The FIO wallet created will store private keys on the Ledger Device and not on the EDGE sub-system.
      - Public key should be stored in Dashboard back-end and/or EDGE sub-system to support look-ups.

Wallet List

Modified https://fioprotocol.atlassian.net/wiki/spaces/PROD/pages/255591518/Dashboard+FIO+Token+FIO+Request+FIO+Data#Create%2FEdit-New-Wallet
- Display Ledger icon next to Ledger Wallets

Wallet Details

Modified https://fioprotocol.atlassian.net/wiki/spaces/PROD/pages/255591518/Dashboard+FIO+Token+FIO+Request+FIO+Data#Wallet-Details
- Display Ledger icon for Ledger Wallets
- Hide Show Private Key icon
- Copy Button to copy the address
- Share Button to share the address
- View Public Address on Ledger Button
  - When Not Connected - Used clicks connect to the Ledger Device

Connect to Ledger Device

Modified https://fioprotocol.atlassian.net/wiki/spaces/PROD/pages/255591518/Dashboard+FIO+Token+FIO+Request+FIO+Data#Wallet-Details
- When not connected the user is show the connect dialog to connect their Ledger device

Wallet Details - Connected View

Image Removed

Image Added

Modified https://fioprotocol.atlassian.net/wiki/spaces/PROD/pages/255591518/Dashboard+FIO+Token+FIO+Request+FIO+Data#Wallet-Details
- Once connected, the user is shown a prompt to view and compare their public address

Signing with Ledger

Confirm Transaction

Signing not available

Ledger signing is supported for the following transactions (all currently supported in Dashboard)
When user triggers a Ledger-supported action the Confirm Transaction is shown instead of PIN code