FIO Developer Blog

FIO ERC20/ERC721 Version 1.0 Releases

FIO ERC20 Token Wrapping 1.0 and ERC721 Domain NFT Wrapping 1.0 are companion releases to FIO Chain 3.4 / FIO Contracts 2.8. This release includes the Ethereum contract that enables the wrapping of FIO tokens to WFIO on the Ethereum chain. It also includes the Polygon contract that enables the wrapping of FIO Domain NFTs onto the Polygon chain.

FIO Version 3.4/2.8 Release Notes

FIO Chain 3.4 / FIO Contracts 2.8 is a major feature release from FIO. This release includes the FIO chain components to enable the wrapping of FIO tokens to WFIO on the Ethereum chain. It also enables the wrapping of FIO Domain NFTS onto the Polygon chain. Specifically, this release:

• Includes the FIO chain components required for FIO Wrapping
• Enables the sending of locked tokens to existing accounts

FIP-6 Advisory - Transfer locked tokens

FIP-6 introduced the ability to transfer tokens to an account and have them be locked based on a pre-determine schedule. If your integration looks for specific actions, e.g. trnsfiopubky, to determine which transactions to show as token transfers, you may want to add trnsloctoks as one of those transactions.

FIP-21 Advisory - FIO Staking

FIP-21 is planned to be launched to Mainnet in January 2022. Users will have the option to stake their FIO Tokens and earn staking rewards. The staking rewards are computed in such a way that the earlier you stake the higher the reward earning potential. Integrators are encouraged to launch staking integration before the activation date of 02/22/2022 to offer the greatest benefit to their users.

Please note that FIO Staking offers a new incentive to integrators which lets them earn 11% of the staking reward paid out to their users!

This Advisory is intended for wallets and exchanges wishing to integrate FIO Staking.

In addition, when staked or during unstaking, FIO Tokens in user’s account may be locked. If you allow users to import FIO Private Key or seed phrases, it’s possible that an account will be imported which contain locked FIO Tokens. You may consider evaluating user’s available balance and potentially showing in UI.

FIP-31 Advisory - FIO Addresses no longer expire

FIP-31 has been launched to Mainnet. FIO Address will no longer expire or be burned due non-payment of FIO Address renewal fee. Therefore, it will be fully functional indefinitely. FIO Address will still have limited functionality within 90 days after its FIO Domain was not renewed and will still be burned once its FIO Domain is burned. Users will still need to purchase bundled transactions or pay-per-call to continue to call actions on the FIO Address, such as adding public address mappings, creating new or responding to an existing FIO Request.

This Advisory is intended for wallets and exchanges which have integrated FIO Address registration and display functionality.

FIO Release 3.0 Mandatory Upgrade Checklist

FIO Chain release v3.0 is a mandatory update for all wallets and exchanges running a FIO API Node. This post outlines the steps FIO integration partners must take to upgrade their FIO API node from v2.0.x to v3.0.

FIO Version 3.0 Release Notes

(This release is currently in Testnet)

It has been awhile since we have posted out a development update. The reason is we have been heads down working on our next v3.0 chain release. V3 includes a lot of new API endpoints for recent FIO Improvement Proposals as wells as performance improvements for accessing FIO Request data. A few statistics on the FIO v3.0 release:

• Includes features for 11 FIPs (https://github.com/fioprotocol/fips) including: FIP-1.b (xfer address), FIP-6 (xfer locked tokens), FIP-7 (Burn FIO Address), FIP-9 (Vote and proxy without FIO Address), FIP-10 (Redesign fee computations), FIP-11.a (Add bundled transactions), FIP-13 (Retrieve all pub addresses), FIP-16 (clio enhancements), FIP-18 (Chain level public addresses), FIP-19 (Retrieve all received FIO Requests), FIP-25 (Return bundle transaction count in get_fio_names)
• 8 new API endpoints
• Modifications to 14 API endpoints

2021 ETHDenver Hackathon

FIO is sponsoring the ETHDenver Hackathon with $5,000 worth of bounties that will be rewarded to developers who use FIO to simplify their application.

Development Update January 2021

Introduction

The transition to 2021 finds FIO development also in a bit of a transition. In January we released the contract code updates targeting several FIO Improvement Proposals (FIPs) that have been on the list for awhile. Since September of 2020 we have been targeting monthly FIP-based releases and in January we added another four features (FIPs 1, 6, 11, and 18). Our upcoming chain code update in February will put the finishing touches on this round of FIPs by adding in all the new API endpoints and other chain plugin utilities. In the meantime, the development team is transitioning from core protocol features to working on larger FIO initiatives including staking, NFT wrapping, and a new dApp that will make it easy for users to interact with FIO. Of course, the team will also continue to work on core features–more FIPs are on the way.

FIO Domains and Addresses as NFTs

One of the main requests has been to enable the exchange of FIO Domains and Addresses. With our latest release it is now possible to transfer FIO Addresses to a new owner. This gets us one step closer towards providing FIO Domains and FIO Addresses that are tradeable NFTs. The next step will be to enable users to wrap their Domains onto the Ethereum chain to facilitate NFT exchanges. Work on wrapping is in progress.

Improving usability

Other improvements that made it to Mainnet this past month focused on usability. Most FIO users are familiar with FIO “bundles” which are the free transactions included when a FIO Address is purchased or renewed. As users have increased their use of FIO, it has become clear that there needs to be an easy way to purchase more bundles. The January release enables users to buy multiple sets of bundles in a single transaction.

If you have gone through the process of mapping your FIO Address to your ERC-20 tokens, you probably found it a bit tedious because a unique chain code and token code mapping was required for every ERC-20 token. The January release now allows you to enter a generic “*” token code that indicates all tokens for that chain are mapped to the same blockchain public key.

Secure your tokens in a locked account

While FIO is principally a utility token, there are occasions when you may want to add on an extra layer of security. The January release enables users to transfer tokens to a new account and lock those tokens on a pre-defined schedule. An added bonus: the ability to lock tokens is the first step to enabling FIO staking–a feature that is currently in design.

Developer Hub

Work continues on the updated FIO developer hub. This new Github site will facilitate community contributions with the goal of making it easier to use the FIO SDKs and integrate FIO features into wallets and other crypto applications.

Find out more here: https://devhub.fioprotocol.io

FIO Release 2.3 on Mainnet

FIO release 2.3 was deployed on Mainnet on January 14th. This release includes the following new features:

• Adds the ability to transfer FIO Addresses
• Enables users to transfer tokens to a new account and lock the tokens for a pre-defined period of time
• Adds the ability for wallets to map all tokens on a particular chain to a single public address
• Enables the purchase of multiple sets of bundled transactions