FIO Worker Proposal funding change proposal

Decision has been made by the Steering Committee to abandon this approach and focus on improving the existing, function-based Worker Proposal system.


The following document describes a proposed change to how the Foundation operates and funds worker proposals. The change proposal does not imply that the existing process is broken, but rather attempts to make it better.

For the most part the Foundation has been operating as a centralized company. Even though it funds multiple independent worker proposals, the individual workers operate in a functional hierarchy, e.g. Business Development, Marketing, Development, Product, etc. The Steering Committee sets the priorities which are then executed by the individual functional areas. A Product Owner is picked to own the initiative and relies on the bandwidth of the other functional areas to execute their initiative. The “reporting structure” of Product Owners is not clear. It’s also not clear how other core team members' input should be considered by Product Owners. KPIs are not typically set or monitored for any of the initiatives. In many centralized organization, centrally-led Product organization acts as the execution group. However, the Product organization at FIO does not have such a role nor resources required to undertake it. The result is less-than-optimal execution of initiatives funded by the Foundation.

In addition, the existing structure is hard to scale as it requires proportional and coordinated growth of each functional area in order to avoid bottlenecks. It also makes every worker proposal which does not fit the functional area, seem like an outsider and hence makes it harder to organically attract workers.


  • The Foundation Board hires Steering Committee members. This is funded with a stand-alone worker proposal for each member and is paid with locked FIO (or model similar to future FIO grants) to incentivize the Steering Committee to make decisions positively impacting future value of FIO token and hence inherently spur adoption of the FIO Protocol.

  • The Steering Committee reviews and approves worker proposals for complete initiatives with clear KPIs, rather than functions. In other words not “Development”, but “Launch, hosting and maintenance of Dashboard with clearly set KPIs (what is expected and what would be considered failure or raging success)”. The entity which wins that worker proposal is responsible for all elements required for success including Product Management, Design, Development, Hosting, Marketing, etc. It may, in turn hire additional resources to fulfill those needs and pay them directly. As a results the worker proposal includes enough funds to cover all required resources.

  • Some initiatives would intentionally be funded only for initial development with the idea of them becoming self-funding businesses. For others, the Steering Committee reviews each worker proposal against forecasted KPIs and decides if it wants to continue funding it.

  • As an example, here’s a self-contained project to develop Crypto Badges NFT website. It would include:

    • Product work

      • FIP definition

      • Website design and specification of MVP and future versions

    • Development and Dev-ops

      • Development, testing and launch of FIP functionality

      • Hosting of website

    • Marketing

      • Marketing of new Website


  • Foundation can more easily approve new initiatives, because it does not have to worry about operationalizing it, i.e. “great idea, but we don’t have resources to build it now”, and therefore should increase the amount of activity the Foundation can efficiently fund.

  • Entities winning worker proposals have a clear set of KPIs and funds to achieve them and do not have to rely on other “functional areas”. They are also truly CEOs of their worker proposal deciding how to best spend the funds to achieve the objective.

  • Organization-wide coordination should be reduced as each entity is in control of its own destiny.

  • The “core team” no longer has to be involved in every initiative.

  • This “VC-like” model should attract more entities willing to submit worker proposals.


  • Domain expertise is still critical and there are only so many resources that have it. It will take time for new resources to come up to speed.

  • Some work may end up being duplicated due to lack of central control structure.

  • Cost may end up being higher as entities undertaking worker proposals may have more risk and subcontracting overhead.


Existing entities would submit worker proposals for delivering of specific tasks/projects the Foundation wants to fund, rather than staff (FTE) worker proposals. Those entities would then be free to hire, and pay for, any resource they require to execute on the objective. It’s likely that initially the resources would be existing staff members as they have domain expertise, but over time new resources may be brought in. For example, if an entity is awarded the “FIO Dashboard” worker proposal, they may higher existing developer resources for building and development and existing marketing resources for promoting it.

Worker proposals are not exclusive. For example, there could be more than one entity which has an independently run “Promote FIO Protocol” worker proposal. This allows the Foundation to more easily test out new entities/teams.


Here’s an example of how the work currently being funded by the Foundation could be organized under the new system. It’s a quick draft to facilitate conversation, rather than a specific proposal.

Worker proposal



Worker proposal



Promote FIO Protocol

Objective: To drive awareness, adoption, and utilization of FIO Protocol via a full-transparency marketing program designed for scalability, replication, and efficient communal re-use of proven best practices


Acquire FIO integrations

  • Reach out to and sign-up integration partners

  • Design, build, and host website(s) supporting FIO Protocol integrations (currently Dev Hub)

  • Support integration process

  • Integration partners

    • Contacted

    • Signed MOUs

    • Integration started

  • Self-guided integrations

  • On-chain metrics, e.g. FIO Crypto Handle registrations or MAA

  • Partner integration process satisfaction, e.g. NPS

  • Website uptime SLA

Maintain FIO Chain health

  • Ensure FIO Chain is running uninterrupted

  • Develop, test, and launch stability improvements and EOSIO upgrades

  • Maintain FIO Chain SDKs

  • Chain up-time

  • Developer/BP satisfaction, e.g. NPS

FIO Chain Development (FIPs)

Core chain and contract development

  • Development of Foundation-led FIPs


  • QA for all FIPs

  • Devnet, Testnet, and Mainnet release testing

Release management

  • Release Management for all FIPs

  • Develop and maintain integration pipeline

  • Define and manage the software development lifecycle

  • Oversee internal launch and operation of the FIO Devnet, Testnet, and Mainnet and coordinate with FIO team to ensure that internal elements work seamlessly with community run nodes

Documentation and knowledge sharing

  • Promote documentation and knowledge sharing across team to ensure redundancy

FIO Chain and Contract Security

  • Contract and chain audits

  • Work with FIO security team to research and implement secure engineering best practices

EOSIO compatibility and community support

  • Work with EOSIO community to ensure FIO compatibility with evolution of EOSIO

  • Contribute to EOSIO code and tools

Developer outreach and community building

  • Ensure FIO development community has the resources, motivation and tools they need to excel and deliver high quality software

  • Ensure that FIO development community is always focused on ease of implementation and ease of use as high priorities

  • Community bounty program

  • Chain up-time

  • Developer/BP satisfaction, e.g. NPS


Core chain and contract development

  • Maintain release dashboard for FIP development: estimated release dates, current status


  • Timely delivery of automated tests for new features. TBD on this process.

  • Maintain QA dashboard

    • summary of test coverage

    • tests in development with estimated release dates

  • Testnet testing completed within 2 hours of new releases

  • Mainnet testing completed within 2 hours of new releases

Release management

  • Timely delivery of Devnet, Testnet, and Mainnet releases. TBD on this process.

  • Maintain Release dashboard

    • Release pipeline

    • Release history and versioning

Documentation and Knowledge sharing

  • Update Devhub with new feature info within 2 weeks of release

FIO Chain and contract security

  • Maintain security playbook

  • Security response KPIs (TBD)

EOSIO compatibility and community support

  • TBD

Developer outreach and community building

  • TBD

Integration - Technology and Tools

Integration documentation / Devhub

  • Develop and maintain Devhub to support integration

Integration development support

  • Work with FIO integration partners to develop efficient integration processes

Integration IT support

  • Work with integrators to facilitate setting up and running FIO API nodes

  • Maintain releases and docker images

Tools and libraries to support the integration experience

  • FIO SDKs

    • Development, QA and Release Management for SDKs

  • Registration Site

    • See: Registration Site

  • FIO Data Services

    • Development, maintenance, hosting, and monitoring of FIO services (e.g., staking service)


Devops and Secops

  • Hosting of FIO applications and services

  • Maintenance of AWS infrastructure

  • Oversee IT vendor relationships, contracting and billing

  • Promote documentation and knowledge sharing across team to ensure redundancy

  • Security for hosted applications


FIO Dashboard

  • Design, build, and host FIO Dashboard website

  • Promote FIO Dashboard to acquire new users

  • Monthly Active FIO Dashboard users

  • On-chain metrics, e.g. FIO Crypto Handle registrations or MAA

  • User satisfaction, e.g. NPS

  • Website uptime SLA

Hey FIO Dashboard

  • Design, build, and host Hey FIO Dashboard website

  • Promote Hey FIO Dashboard to acquire new users

  • Monthly Active Hey FIO Dashboard users

  • On-chain metrics, e.g. FIO Crypto Handle registrations or MAA

  • User satisfaction, e.g. NPS

  • Website uptime SLA

FIO Marketplace

  • Design, build, and host FIO Marketplace website

  • Promote FIO Marketplace to acquire new users

  • Monthly Active FIO Marketplace users and transactions

  • Website uptime SLA

Registration Site

  • Design, build, and host registration site

  • Support inbound customer, partner inquiries

  • User/partner satisfaction, e.g. NPS

  • On-chain metrics, e.g. FIO Crypto Handle registrations or MAA

  • Website uptime SLA

Reporting Site

  • Design, build, and host reporting site

  • User satisfaction, e.g. NPS

  • Website uptime SLA

Primary Block Explorer

  • Design, build, and host primary explorer

  • User satisfaction, e.g. NPS

  • Website uptime SLA

Foster FIO Community

  • Design, build, and host community tools

    • Community Website

    • Task management tools

    • Foundation emails

  • Attract users to participate in FIO Community and submit worker proposals

  • Active Worker Proposals

  • Open Opportunities

  • User satisfaction, e.g. NPS

  • Website uptime SLA


FIO Support in Ledger

  • Design, build, and launch Ledger FIO App

  • Time

    • Launch within 12 months

Wrapping of FIO Tokens and Domains

  • Design, build, and launch of functionality and platforms enabling wrapping

  • Support inbound customer, partner inquiries

  • Launch WFIO on Uniswap

  • Enable FIO Domains on OpenSea

  • Time

    • Launch within 6 months

Crypto Badges

  • Time

    • Launch MVP within 6 months

  • NFTs minted 3 months after launch

    • Expected: 10,000 - 15,000

    • Failure: < 1,000

    • Mediocre: 1,000 - 10,000

    • Raging success: 15,000+

Steering Committee Member

  • Execute FIO Board’s vision

  • Oversee Foundation funds

  • Approve and fund worker proposals

  • Report on Foundation finances

  • Board satisfaction