Dashboard Wallet/Exchange Integration

Owned by George Worrell
Last updated: Mar 30, 2022
3 min read

Table of Contents

Initial Feedback

The main takeaway from meeting with dev on all of these points is yes, all of this can be built or modified and business could go to market with these offerings. It’s simply a matter of scope, order of priority for these and time (which is now being gone through to understand those elements). 

Specific feedback that has been received on each of these points:

Current State:

  1. Passing a TPID with the URL link that persists with the user in the Dashboard such that every time that user registers a FIO Crypto Handle or Domain the TPID will receive their FIO tokens on chain.

    1. We use referrer on NFT, but we do not use TPID , and we do not include TPID in the NFT flow currently.

    2. TPID is not used for Paid Crypto Handles currently, we only use TPID on for Free CH.

    3. We use RegSite API for storing the TPID, not Dashboard.

  2. A co-branded landing page can appear when a TPID is included in the web link to the dashboard.

    1. We have a co-branded landing page, but only some Images, some Titles and Links are custom. The colors, fonts etc are not customizable for now but could be going forward.

      1. https://dapp-dev.fioprotocol.io/ref/uniqueone?action=SIGNNFT&chain_code=ETH&contract_address=FIO5CniznG2z6yVPc4as69si711R1HJMAAnC3Rxjd4kGri4Kp8D8P&token_id=ETH&url=ifg://dfs.sdfs/sdfs&hash=f83klsjlgsldkfjsdlf&metadata=%7B%22creator_url%22:%22https://www.google.com.ua/%22%7D&r=https://www.google.com.ua/

  3. That co-branded landing page can be configured with whatever default FIO Domains are desired in the pull down menu so these can vary by the application linking to the Dashboard.

    1. This is possible now.

 

Needs to Be Built:

  1. System for limiting the number of free FIO Crypto Handles by TPID passed to prevent potential attack vector of an application registering bogus handles to get the blockchain reward.

    1. This logic exists on RegSite, but current logic filters by IP. We do requests from Dashboard API, thus we need to rewrite the logic.

  2. Ability for the application to optionally pass public addresses to the Dashboard so a user could then map via a checkbox or radio button UI versus cutting and pasting.

    1. Need to clarify this logic and what the use flow would look like.

  3. Co-branding that persists through out the Dashboard (beyond landing page)

    1. This is address above in number 2.

    2. Will need to specify what exactly should be customizable.

      1. I have indicated in a first pass that this would be:

        1. Branding

        2. Color

        3. Typeface

  4. Ability for users to buy FIO Tokens via Indacoin in the Dashboard (Indacoin is live... needs to be added to Dashboard).

    1. Need more tech details to determine the path. Could the API be consumed for example. Will need to link up the devs on this.

  5. Ability for users to register FIO Domains and paid (non-free) FIO Crypto Handles using tokens/coins other than FIO (similar to registration site).

    1. This already exists on Reg Site, but yes, it needs to be implemented on Dashboard as well.

 

Order of Priority

From an order of priority, and based on existing elements, this is how I broke it down from a potential implementation standpoint:

  1. Passing a TPID with the URL link that persists with the user in the Dashboard such that every time that user registers a FIO Crypto Handle or Domain the TPID will receive their FIO tokens on chain.

  2. A co-branded landing page can appear when a TPID is included in the web link to the dashboard.

  3. That co-branded landing page can be configured with whatever default FIO Domains are desired in the pull down menu so these can vary by the application linking to the Dashboard.

  4. System for limiting the number of free FIO Crypto Handles by TPID passed to prevent potential attack vector of an application registering bogus handles to get the blockchain reward.

  5. Ability for users to register FIO Domains and paid (non-free) FIO Crypto Handles using tokens/coins other than FIO (similar to registration site).

  6. Ability for the application to optionally pass public addresses to the Dashboard so a user could then map via a checkbox or radio button UI versus cutting and pasting.

  7. Ability for users to buy FIO Tokens via Indacoin in the Dashboard (Indacoin is live... needs to be added to Dashboard).

Use Case

TBD

UX

TBD

Settings

  • Visual

  • Functionality

Specifications

TBD

Must Haves

  • TPID - All instances of private label must provide their TPID in order to receive associated rewards.