FIO App Account Types

• Standard

  • Keys are stored on /wiki/spaces/DAO/pages/151879691.

• Alternative

  • Keys are stored in another Wallet

    • Metemask

Alternative Account

• Alternative Account should only contain

  • FIO Public Key

  • Account Type

    • Primary

    • Alternative

• Alternative Account

  • Always contain

    • FIO Public Key for index 0

  • Will not initially contain

    • Email address, but it may be added later

  • Will never contain

    • Password

    • PIN

    • 2FA

    • Password Recovery

  • See https://fioprotocol.atlassian.net/wiki/spaces/DAO/pages/310608242/Settings#Main-Settings

• FIO Public Key in Account Conflict Resolution

  • The same FIO Public Key could exist in Primary account and Alternative account and those would be considered separate accounts

    • Example:

      • User A creates Primary Account using email and password

      • User A imports seed phrase ABC

      • User A connects to FIO App using Metamask which has seed phrase ABC installed

      • User A has 2 different accounts:

        • Primary Account

          • Key generated by EDGE

          • Key imported using seed phrase ABC (Account index 0)

        • Alternative Account

          • Key imported using seed phrase ABC (Account index 0)

• Multiple Wallets

  • For Alternative Accounts, users can Create New Wallets. When they do each additional Wallet is the next index in the derivation path (same as for Dashboard Ledger Wallet)

  • For Alternative Accounts, users can add a Ledger Wallet.

Sign-in

• The Sign-in and Account creation process is transparent to the user

• Process

  • User signs a nonce using FIO Public Key for index 0

  • FIO App fetch FIO Public Key for index 0

  • Create Account - if FIO Public Key is not associated to an account, create account

  • Log user in

Sign Transaction

• Transaction signing occurs in specific wallet

• Transaction json should be shown

FIO Handle Resolution

• Overview

  • When user has the FIO Snap installed, FIO Handles will be resolved inside MetaMask on send.

• Manifest spec - this ensures OnNameLookupHandler receives any data typed for any chain

"endowment:name-lookup": {}

• Look-up logic

  • Verify that the string received matches the FIO Handle format

  • Convert chainID to chain_code and token_code - DEV NOTE: mapping static file TBD, e.g. eip155:1 is chain_code: ETH, token_code:ETH

  • Execute /get_pub_address

  • Return public address

  • Example OnNameLookupHandler

export const onNameLookup: OnNameLookupHandler = async (request) => {
  const { chainId, address, domain } = request;

  if (domain) {
    const resolvedAddress = '0xc0ffee254729296a45a3885639AC7E10F9d54979';
    return {
      resolvedAddresses: [{
        protocol: 'FIO Handle',
        resolvedAddress: resolvedAddress,
        domainName: domain,
      }]
    };
  }

  return null;
};

DEV NOTE: specification: https://metamask.github.io/SIPs/SIPS/sip-12

SNAP Home Page

No FIO Handle and No FIO Tokens and No Pending FIO Requests

1+ FIO Handles and >0 FIO Tokens and 1+ FIO Requests

• Display SNAP Home Page per SNAP spec

  • FIO Token Balance

    • Fetch balance using /get_fio_balance and FIO Public Key stored in MetaMask

      • Show balance

      • If 0 display “Get FIO”

        • On click

          • Open https://fio.net/token/overview#get-fio

  • FIO Handles

    • Fetch using /get_fio_addresses and FIO Public Key stored in MetaMask

      • If 1 or more returned display first returned handle

      • If more than 1 returned display Display first returned“See more handles”

        • On click

          • Open https://app.fio.net/fio-handles

      • If 0 handles returned display enter a handle text box and button

        • On click

          • Open https://app.fio.net/fio-handles-selection?address=bob where bob was entered

  • Pending FIO Requests

    • Fetch using /get_pending_fio_requests and FIO Public Key stored in MetaMask

      • If 1 or more returned display the section and number of pending FIO Requests and “View requests”

        • On click

          • Open https://app.fio.net/fio-wallet?publicKey=snappubkey where snappubkey is FIO Public Key stored in MetaMask and default to FIO Requests Received tabs

Authenticate

• Set-up SNAP

  • Install FIO SNAP

  • Grant SNAP Permissions

• Sign-in

  • Have user sign nonce with FIO Private Key

    • SNAP Message

      • Title: Sign-in to FIO App

      • Description:
        Please approve this nonce signature to sign-in to the FIO App. Nonce signature proves that you are the owner of the associated FIO Public Key.
        ------------------------------------
        Random nonce: XXX

• If user rejects any of these steps display error message

Sign Transaction

• Trigger transaction sign in Metamask

• SNAP Message

  • Title: Sign FIO Transaction

  • Description:
    Please approve the following transaction.
    Transaction name: trnsfiopubky
    ------------------------------------
    FIO Chain: FIO Mainnet
    ------------------------------------
    Transaction details:
    tpid: dashboard@fiouat
    max_fee: 1500000000000
    amount: 100000000000000
    payee_public_key: FIO68bYHgYTqc17jz9MuprzvUY9D7Ud9UmLzruiNiFGkaHMZNUDv5

Decrypt Content

• When decrypting content of FIO Request or FIO Data, trigger decrypt content transaction in Metamask. If

• SNAP Message

  • Title: Decrypt FIO Data

  • Description:
    Please approve the decryption of FIO Data. For your security and privacy, FIO Data is always encrypted and has to be decrypted before viewing.

Sign out

• Replace Sign out with Disconnect button with icon