This set of documents has been identified by the FIO Core Technology team as a candidate for attention in the 2022/2023 timeframe. These projects address areas that the core technology team has deemed critical to the “health and wellness” of the FIO Protocol, and which help to achieve the KPIs specific to the
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Project Areas of Focus -
Identify and address performance deficits in the present FIO design.
Permit the FIO Protocol to integrate and deploy releases more flexibly and rapidly.
Better Educate and inform the FIO community regarding all aspects of FIO operation and best practices.
Address critical deficit in (lack of security focus) Provide capabilities the FIO Protocol needs to observe, identify, and respond to security threats
Address Performance Deficits.
-Clean up state
Analyze the limits of FIOs state tables, understand when tables are getting close to limits, Create tools and processes that can be used to analyze the “state of state tables”. Create tools that can be used to clean tables. Stimulate discussion regarding what data should be cleaned and why.
create a set of projects for each major group of tables in FIO.
– Optimize size and complexity of FIO state model.
Analyze the limits of FIO state to better understand the functional limits of the protocol in relation to the amount of information that is contained in FIO state. Document options that will help the FIO Protocol to handle volume well beyond its' present functional limits.
Analyze the limits of the FIO read operations, Document options that might help the FIO Protocol to provide read access for integrators that functions well beyond FIOs present limits.
Analyze the overhead for block producers and community members regarding playbacks, snapshots, and other operations performed regularly by BPs. Document options that might be helpful to the FIO Protocol when significant load is experienced by the protocol
Provide more flexibility of project integration and deployment
make FIO more configuration oriented for
new contracts
new features
Soft forking changes to FIO repository
Modify contracts to ease contract deploy-ability
reduce number of contracts impacted by changes to common code.
reduce binary size of each FIO contract
create new release tools to aide in release management.
Encourage Community awareness and knowledge
Training, documentation, and best practices
For block producers.
For API node hosting
For exchange integration.
For contract development
For FIO (core C++) development
Provide a Security focus for the FIO Protocol
Address Deficits in Security processes and practices.
(see findings of Q’s playbook before making this project list)
For each project we will identify the following
Project Objective/Problem statement
background
motivations
detailed description
Note – all Risk, Cost, and Benefit analysis will attempt to identify and give a quantitive score in the terms of the strategic objectives of the FIO Protocol. These objectives are listed in the following document.
Risks of not addressing project
perceived chances of each risk happening (as a percentage)
At what point do the risks come to a critical tipping point.
Impact analysis
include a rating for each KPI 1-5, where 1 is minor risk and 5 is maximum risk
try to describe, quantify, and measure the amount of risk that is taken on in the terms of KPIs.
Cost analysis of the project
Including rating 1-5,where 1 Is minimal and 5 is maximal.
List of costs
number/complexity of unknowns
total duration time
design complexity
implementation complexity
QA complexity
integration complexity
total financial cost rating
ability to deliver in phases
Benefit analysis of the project
Including rating 1-5,where 1 Is minimal and 5 is maximal.
Try to describe, quantify, and measure the amount of benefit that is gained in the terms of the KPIs.
List of Candidate projects
FIO State size analysis
FIO performance Analysis
Off chain state Database for FIO
Establish processes for state maintenance.
Analyze contract dependencies.
Reduce contracts individual size.
BP hosting guidelines
API node hosting guidelines