Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

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 going forward, but which have not been included in the DAO-49 - Getting issue details... STATUS worker proposal.

Areas of Focus -

Address key deficits of the present FIO design.

-Clean up state (removal of old/out-dated data)

-Limits of the present design

reduce on chain state size and complexity.

provide a standard, performant, easily used set of readers for FIO state.

eliminate the need for FIO Core update for reader access

Ease the deployability of the FIO Protocol.

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

Address key deficits of community engagement

Training, documentation, and best practices

For block producers.

For API node hosting

For exchange integration.

For contract development

For FIO (core C++) development

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.

Strategic Objectives

Risks of not addressing project (in terms of the KPIs of the core tech team and integration 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 area of the strategic objectives 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 the strategic objectives.

Tell a Compelling Story

Ensure FIO Chain performance & security

Increase FIO Contributor engagement

Increase FIO Protocol utilization

also describe risks in terms of the perceived impacts they will have in the following areas.

Chain availability

FIO tech team reputation

FIO token price

BP function

Community and BP Governance

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 strategic objectives.

Tell a Compelling Story

Ensure FIO Chain performance & security

Increase FIO Contributor engagement

Increase FIO Protocol utilization

also describe benefits in terms of how the project will help in the following areas.

Chain availability

FIO tech team reputation

FIO token price

BP function

Ease of deployment/release

Ease of BP node maintenance.

Community and BP Governance

List of Candidate projects

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

  • No labels