FIO-enabled Bloks.io

Owned by Pawel Mastalerz
Jan 26, 2022
3 min read

Last updated April 23rd, 2020

Table of Contents

 

General

The objective of this project is to create a FIO-enabled Bloks.io for FIO Mainnet and Testnet. The following is a list of customizations requested.

A general requirement is to make all features of Bloks.io work with FIO, except as specifically stated below.

Home Page

  • Remove:

    • RAM Calculator

Account Page

Top section

  • Show FIO balance

  • Total balance should include locked tokens, see FIO-specific token locks and circulating supply.

Resources

Chain Data

  • Remove:

    • Tokens tab

    • Staked tab

    • RAM Explorer

    • Children

    • NFTs

  • Add:

    • FIO Addresses - list of FIO Addresses (available in fio.address → fionames) owned by the account, clickable and linking to FIO Address page.

    • FIO Domains - list of FIO Domains (available in fio.address → domains) owned by the account, clickable and linking to FIO Domain page.

Key Page

Currently the Pub Key Page only shows accounts which currently have the provided key associated with them at the time of query. However in FIO a public key hashes down always to a single account. That account should be added to the list of accounts (if not present there).

Wallet Page

  • Remove:

    • Airgrab tokens

    • Stake CPU/NET

    • Buy/Sell RAM

    • Create Account

    • Security

    • dApps

    • Earn

  • Change:

  • Add:

Vote Page

  • Remove:

  • Change:

    • Block producer should be identified with FIO Address, not account

    • Proxies should be identified with FIO Address, not account

dApps Page

Remove Page

Tokens Page

DEX Page

Remove Page

REX Page

Remove Page

Earn Page

Remove Page

Statistics

  • Add

    • FIO Domains - page which displays latest FIO Domains (by registration date) with paging and ability to search.

      • Should show:

        • Account (with link)

        • FIO Domain

        • Expiration date

        • Is Public flag

      • Data comes from: fio.address → domains

    • FIO Addresses - page which displays latest FIO Addresses (by registration date) with paging and ability to search.

      • Should show:

        • Account (with link)

        • FIO Address

        • Expiration date

      • Data comes from: fio.address → fionames

Top holders Page

Remove Page

Name Bids Page

Remove Page

DSP Portal Page

Remove Page

FIO Address Page (new)

  • This is a new page which is accessible when user types in a FIO Address in search or follows a link to specific FIO Address.

  • Data comes from: fio.address → fionames

  • Should show:

    • Account (with link)

    • FIO Address

    • Expiration date

FIO Domain Page (new)

  • This is a new page which is accessible when user types in a FIO Domain in search or follows a link to specific FIO Domain.

  • Data comes from: fio.address → domains

  • Should show:

    • Account (with link)

    • FIO Domain

    • Expiration date

    • Is Public flag

Exchange integration

  • Assumption is made that FIO will be traded on major exchange before the site is launched.

Wallet integrations

The following wallets currenty support FIO and should be enabled and tested on FIO-enabled Bloks.io:

  • Scatter

  • Anchor

  • clio (FIO version of cleos)

FIO token locks and circulating supply

Token locks

Some tokens in FIO were locked at Mainnet and continue to unlock over 990 days. Those accounts can be found in eosio → lockedtokens. Relevant fields:

  • owner - account actor

  • total_grant_amount - Amount of initial grant

  • remaining_locked_amount - amount of tokens which remain locked

Sum of remaining_locked_amount should be considered locked.

In addition tokens locked for BPs in fio.treasury → bprewards and fio.treasury → bpbucketpool should be considered locked.

Available tokens can be computed: current balance - remaining_locked_amount

Circulating supply

Circulating supply is computed by taking all FIO tokens minted and subtracting locked tokens.

Fee support in transactions

Most transactions in FIO require a fee to be passed in max_fee parameter. That fee can be obtained calling /get_fee. Anytime a transaction is being created get_fee should be called and proper transaction fee should be pre-populated.

Technical References