Dashboard Old

The FIO dApp product has been renamed Dashboard.

In Progress

This project is in progress, see:

Initiative Committee

@Pawel Mastalerz @David Gold @Luke Stokes @Eric Butz @George Worrell @Kaitie Zhee @James Haft @Nick Nayfack

Table of Contents


The FIO Community believes that an end user web application is needed to streamline interactions with the FIO Protocol.

Even though it will be a web application running on centralized servers, we call it a Dashboard, because it’s open source, runs ran on top of a decentralized FIO Chain and requires private keys for many interaction.

Who is the customer?

  • The end-user of the FIO Protocol.

    • New/potential user of FIO.

    • Existing user of FIO currently using another wallet.

What problem of the customer are we trying to solve?

  • It’s hard to onboard to FIO.

    • User have to typically download some other app.

    • Many FIO integrations are sub-par.

  • It’s hard to access full FIO Protocol functionality.

    • Most FIO integrations do not offer complete set of FIO features, such as register on private domain, set domain public, purchase address/domain for someone else, etc.

    • New functionality may take a while to be adopted across many wallets

  • Domain shopping is unfriendly, unengaging, uninspiring and difficult to find.

  • No path to earn money with FIO, e.g. via referral program or FIO Staking.

  • Make sending and receiving crypto easy using FIO Protocol.

Why is it important this problem is solved?

Without solving the problem FIO adoption growth may be stifled.

Historically FIO has relied primarily on integrators (wallets/exchanges/payment processors) to integrate and promote FIO. This strategy is not as successful as hoped, because many integrators have limited ability to “talk” to their users and promoting FIO is not high on their priority list. The Foundation had struggled to promote FIO directly to the user as it does not have a product users can use and instead has to promote other wallets, which creates friction.

How will this product/initiative solve this problem?

By delivering the desired functionality in an easy to use interface.

What KPIs will you track to determine if you are solving this problem?

  • FIO Address/Domain registration.

  • FIO Addresses/Domains transferred to other wallets.

  • Monthly Active FIO Addresses created or accessed via the Dashboard.

  • Missing functionality delivered fast.

  • Referrals.

Internal objectives

  • Get user contact information to have a way to communicate with them.

  • Reference implementation, show off integration.

  • Tracking marketing initiatives.


Feature set

Account creation/log-in

  • Email address and password will be used to create an account and log-in.

    • Email address will be verified.

  • Private keys

    • FIO Private Key(s) will be generated using EDGE stack.

    • FIO Private Key(s) will be encrypted and stored on using EDGE stack.

  • Importing of private keys

  • Security

    • Account recovery will be done using EDGE stack.

FIO Domains and Addresses

  • Register/renew FIO Domain/Address.

    • FIO Address on private domain.

    • Pay with FIO.

  • Transfer FIO Domain/Address.

  • View owned FIO Addresses/Domains including expiration address and bundled transaction count.

  • Manage Public Address mappings.

    • May require copy pasting from wallet.

  • Set domain public.

FIO Requests

  • Send FIO Requests.

    • May require copy pasting from wallet.

  • View FIO Requests.

  • Reject FIO Requests.

FIO Token

  • Balance.

  • Lock status.

  • Link to Explorer for history.

  • Transfer tokens with memo.

  • Receive tokens.

  • Staking tokens.


  • Allow signing of passed in NFT data - Pass in NFT data and have the Dashboard sign it. See

Future functionality


Challenges and open questions

Product positioning

Having a FIO Address or domain without the ability to use it in a wallet has no value outside of speculation.

However, it can be positioned as a supporting tool to wallets to allow for easy on-boarding and FIO Address/Domain management, especially if user’s wallet does not yet support FIO. It should be actively promoting FIO-integrated product and offer a path to move content (FIO private/public keys and seed phrases, other blockchain public addresses) between the Dashboard and wallet.

User acquisition

Do we believe we can acquire enough users with the budget we have to make it meaningful?

Perhaps not, but this is table stakes and supports existing users.

Dashboard vs FIO Protocol website

Does not have to be integral part of FIO Protocol website.

Co-branding support

No, but promote partners.


Handling private keys creates liability for the entity that builds and hosts the software. Is the Foundation ok with that liability? Yes, subject to implementation review. Prefer Github hosting.

Functionality not supported by the Dashboard

The following functionality cannot be supported in the Dashboard due to its nature and would still have to be implemented in wallet natively.

  • FIO integration for send as it lives in the send area for other crypto currencies (though an address lookup functionality with QR code may be useful for some wallets and tokens).

  • Approval of FIO Request as it involves pre-populating information in the send area for other crypto currencies (though some wallets and tokens may support a QR code approach to pre-populate a token and amount)

  • Cross-wallet memo as it involves calls made when other crypto currencies are sent.

Supporting documentation

Initiative links