The FIO “Gemini” release was deployed on Mainnet on September 23rd. This release included fixes to the core chain code to facilitate the rapid release of new features and updates.
With this release behind us, the development team has begun focusing on rolling out the backlog of user and wallet requested features. We’re excited to announce the first of these rollouts with the deployment of FIO release 2.1, which includes the follow new features:
- FIO Domain transfer functionality
- Pagination for API calls that normally results in too much data
- Cancellation of FIO Requests
- Ability to remove public address mappings
For a more detailed list of bugs and enhancements, please read our detailed overview below, or refer to the Version 2.1 Release Notes.
Both FIO Domain and FIO Address are non-fungible tokens (NFTs) that are owned by a FIO Public Key. FIP-1 enables users to transfer their FIO Domain (e.g., @mydomain) to a new owner. This release does not include the ability to transfer FIO Addresses (e.g., alice@wallet).
There are inherent limitations in how much data can be returned in a single API call on the FIO protocol. Thus, if a table holds a large amount of data it can be difficult to access and sort through the data without the ability to page through the results.
For example, if an account has more FIO Domains or FIO Addresses than can be returned before table read timeout, only partial results will be returned without warning to the user or ability to retrieve the rest. FIP-2 adds the new get_fio_domains and get_fio_addresses API endpoints with support for paging, enabling efficient access to domains and addresses for accounts with a large number of names.
Previously, there was no way for a user to cancel a request for funds they had made. For example, users might want to cancel a request if they enter incorrect data or if the request is no longer valid. FIP-3 enables canceling a FIO Request and includes a new cancel_funds_request API endpoint, a new get_cancelled_fio_requests API endpoint that returns canceled FIO requests, and the addition of a new “canceled” status for a FIO request. In addition, get_sent_fio_requests has been modified to return canceled requests along with the other sent requests.
The previous FIO API did not provide any way for a user to remove public blockchain address mappings. Removing a mapping may be required if a certain token is no longer supported or a user desires to remove a mapping for privacy reasons. FIP-4 adds the ability to remove blockchain public addresses that have been mapped to a FIO Name. Changes include the addition of the new remove_pub_address and remove_all_pub_addresses API endpoints.