After a lot of internal discussions with Ed Rotthoff and bringing Stan (cc32d9) into the discussion, Casey Gardiner is going to code up a solution without the vector storage. Though the lookup would be much faster for most users with few FIO Requests, vectors storage does not scale well in eosio so it could hit problems with users with large numbers of Requests. You do not want to code to the 2% of users, but in this case we think it makes sense to go a more eosio standard route and use a single table and rely on paging as it grows.

These updates could impact timing of the Bravo contract release. The goal was to get it out by the first week of December, but that is looking aggressive given the changes we are making, the size of this release, and the amount of testing we need to do with table migrations. We have had 12/21 as the target on the Roadmap and will keep it at that for now, but stay tuned.

FIO release 2.2 was deployed on Mainnet on November 5th. This release includes the following new features:

• Adds the ability to burn FIO Addresses

• Makes FIO Addresses optional when voting for a block producer or proxying a vote

• Updates Block Producer Fee setting to make it easier to respond to changes in the price of the FIO Token

For more information please read our detailed overview below, or refer to the Version 2.2 Release Notes.

Detailed Overview

FIP-7
An owner should be able to burn their FIO Address ahead of expiration if they no longer wish to use it and want to purge all associated data. There are many reasons why someone would want to burn their FIO Address including business/personal requirements, cost effectiveness, or spam prevention. FIP-7 adds a new burnaddress contract action that enables the burning of a FIO Address.

FIP-9
Currently voting for a block producer or assigning your votes to a proxy requires that a user have a FIO Address. The FIO Address is needed to allow payment with bundled transactions instead of FIO tokens. FIP-9 makes voting and proxying votes easier for FIO users by allowing voting and proxying even when the token holder does not have a FIO Address. The FIO Address field can now be left blank when calling vote_producer and proxy_vote.

FIP-10
It is critical that fees associated with transactions on the FIO blockchain are set appropriately. Fee setting can be difficult for FIO Block Producers, who are in charge of fee setting for the protocol, due to fluctuations in the price of the FIO Token. FIP-10 updates the FIO fee voting functionality and enables Block Producers to set fee ratios (the relative cost of different transactions on the FIO blockchain) and fee multipliers (a single number that can be adjusted to track the price of the FIO Token). Subsequently, the multiplier can be adjusted in response to FIO Token price fluctuations.