Project based Worker Proposals

Owned by Pawel Mastalerz
Last updated: Apr 11, 2022 by George Worrell
9 min read

How does it work

Steering Committee

  • The Foundation Board approves each Steering Committee member as well as total number of members and sets compensation.

  • To ensure the Steering Committee’s incentives are aligned with the FIO community, each member of the Steering Committee is paid in locked FIO via a Worker Proposal.

  • The Steering Committee makes decision by simple majority vote.

  • Steering Committee responsibilities include:

    • Define and publish Strategic Objectives, focus areas and/or specific projects it is willing to fund.

    • Review, approve, and fund Worker Proposals that satisfy the Strategic Objectives and ensure every Worker Proposal has clearly define set of KPIs.

    • Meet at least monthly to review progress against KPIs of all funded Worker Proposals and to decide on continuation of funding.

    • Meet with Foundation Board at least quarterly to provide update on progress towards Strategic Objectives.

  • Steering Committee responsibilities specifically do not include:

    • Managing individual projects, its objectives, activities, staffing, etc., other than via setting KPIs and budgets.

    • Individual Steering Committee members may also be involved in specific project being funded and if they are their vote will not be considered when deciding on their Worker Proposals.

Project-based Worker Proposals

All Worker Proposals approved by the Steering Committee:

  • Must deliver complete project without any dependencies not in control of the Worker Proposal Lead.

    • The Worker Proposal Lead 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. As a results the Worker Proposal includes enough funds to cover all required resources.

    • Specifically, the Steering Committee is not a stakeholder to the projects executed as part of the Worker Proposal, other than KPI accountability and budget. If Steering Committee members are critical to the success of the projects, their time and compensation should be secured directly with the individual.

    • Some initiatives may intentionally be funded only for initial development with the idea of them becoming self-funding businesses. Others may contain recurring payment provisions for operations.

  • Must include specific KPIs which will be monitored and used as basis to determine if it will continue to be funded.

    • KPIs should state some expectations of what would be considered success, or failure, e.g. “Success: >1000 registered domains” and not “Domain registrations going up.”

  • Should specify USDT budget and FIO token budget separately. FIO token budget can be USDT or FIO denominated.

  • May be paid via multiple Payment Requests directly to individuals or vendors completing work for that Worker Proposal as long as payment is approved by Worker Proposal Lead. This would lift the burden of managing payments from Worker Proposal Lead.

  • The code and domain knowledge produced must be open-source unless specific exception is granted by the Steering Committee.

Transition

As part of the transition process, existing workers may be reassigned to multiple project-based Worker Proposal in such a way that their initial X month workload would be predetermine to avoid the stress of not knowing what they will be working on once this model is adopted. See Proposed Initial Worker Proposals.

Proposed Initial Worker Proposals

It is important to note that the description is intended to visualize what the Worker Proposal will likely cover, but ultimately it will be up to the Worker Proposal Lead to decide what they will work on to achieve stated KPIs.

Similarly Current initiatives are intended to represent which Worker Proposal would take over existing intative, but ultimately it would be up to the Worker proposal Lead to decide if that initiatives helps achieve stated KPIs.

Supporting Current initiatives

Project name

Description

Strategic Priority

Current initiatives

KPIs

Budget

Lead

Project name

Description

Strategic Priority

Current initiatives

KPIs

Budget

Lead

Run Steering Committee

See Steering Committee above

  • All

  • All

  • Board satisfaction

 

Members:
@Luke Stokes

@David Gold

@Pawel Mastalerz

@Eric Butz

@Ash Howe

Support FIO Chain stability, performance and security.

FIO Chain Core

  • Develop, test, and launch bug fixes in core FIO Chain functionality.

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

  • Anticipate, research, develop, test and launch improvements required for FIO Chain to handle the volume of transactions it receives.

FIO Chain and Contract Security

  • Contract and chain audits.

  • Research, publish and implement secure engineering best practices.

Release management

  • Manage FIO Chain Github repos, review and approve PRs.

  • Work with block producers to keep them updated on all new FIO Chain core developments and assist with deployment of new functionality.

  • Publish, maintain and enforce processes and best practices FIO Chain developers should follow to ensure their changes are accepted into the main branch code.

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.

  • Manage community bounty program.

Development IT support

  • Develop and maintain tools and services that support development, QA, and release (e.g., CI Pipeline)

FIO Chain Tools

  • Develop, test, and launch bug fixes in FIO Chain Tools.

    • keosd

    • Oracle software

What’s not included

  • New FIP development and testing.

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Protocol integrations (disputed) (100)

  • Increase number of NFT signatures (93)

  • Increase number of FIO Crypto Handle registrations (86)

  • Performant and secure blockchain (99)

  • Increase number of FIO Requests (94)

  • Staking APR service

  • FIO4 (EOSIO Upgrade + ABI)

  • Devops

  • Secops

  • Release management

  • QA

  • wallet support for exchanges (keosd)

  • Block producer relations

  • Chain up-time

  • Chain performance

  • Security breach incidents

  • Count of bug tickets created, count of bug tickets resolved

  • Bug to fix time

  • Code coverage (how much of your source code executes when it is being tested)

  • Defect escape rate (counts how many critical bugs make it past testing into production)

  • Community developer commits

  • Discord community developer chat activity

 

@Eric Butz

Technically support FIO Protocol integrators

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.

  • Develop and maintain tools and services that support integrations (e.g., Opera auto-add bundle service)

Tools and libraries to support the integration experience

  • FIO SDKs

    • Development, QA and Release Management for SDKs

  • FIO Data Services

    • Develop and maintain Staking APR service

    • Develop and maintain Circulating Supply service

    • Opera auto-add-bundle service

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Protocol integrations (disputed) (100)

  • Increase number of NFT signatures (93)

  • Increase number of FIO Crypto Handle registrations (86)

  • Increase awareness of FIO Protocol (113)

  • Dev Hub

  • Staking APR service

  • Integration support

  • Typescript SDK - Maintenance + new features

  • Kotlin SDK - Maintenance + new features

  • Devops

  • Secops

  • Release management

  • QA

  • Godot SDK

  • Contract audits

  • Developer outreach / Bounty management

  • Developer support

  • Integrator satisfaction, e.g. NPS

  • Acquire FIO Integrations team satisfaction, e.g. NPS

  • FIO Data Services uptime SLA

  • SDK time to integration of new features (after release to chain)

 

OLD:

  • Dev Hub uptime

  • Average dev time to integrate

  • Self-guided integrations completed

 

@Eric Butz

Operate Registration Site

  • Maintain and host Registration Site.

  • Develop, test, and launch bug fixes.

  • Set-up wallet profiles and support inbound partner inquiries.

  • Support customer inquiries and resolve issues for paid FIO Crypto Handle and Domain inquires.

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Protocol integrations (disputed) (100)

  • Increase number of FIO Crypto Handle registrations (86)

  • Registration Site

  • Devops

  • Secops

  • Release management

  • QA

  • Time to set-up wallet profile

  • Registration Site up-time

  • Time-to-resolution for customer inquiries

  • Bug to fix time

OLD:

  • On-chain activity by Registration Site

    • FIO Crypto Handle registrations

    • FIO Domain Registration

 

@Eric Butz

Support Wrapping of FIO Tokens and Domains

Objective: Ensure FIO Token/Domain infrastructure is operational

  • Coordinate with Oracles, Custodians, Users wrapping to ensure smooth operation

  • Report Oracle Software bugs to maintenance team (Support FIO Chain stability, performance and security)

  • List WFIO and FIO Domains on third-party platforms

  • No marketing paid with this WP or major development

  • Increase number of and value of domain sales (103)

  • Increase awareness of FIO Protocol (113)

  • Domain wrapping

  • Token wrapping

  • Average Time to wrap FIO Domain

  • Average Time to wrap FIO Token

  • Volume of wrapped FIO Tokens trading

  • Volume of FIO Domains on non-FIO NFT platforms traded

USDT: 3,750/mo

@Pawel Mastalerz

Ensure block explorer availability

Objective: Ensure at least two block explorers are operating and support FIO Chain functionality

  • Coordinate with block explorer providers

  • Report block explorer bugs to operators

  • No marketing or major development

  • Payment to providers

  • Increase number of FIO Protocol integrations (disputed) (100)

  • Blockchain explorer

  • Block explorer count

    • Target: 2

  • Explorers uptime

    • Target: 99.5+

  • Bug to fix time

    • Target: < 2 weeks

USDT: 6,500/mo

@Pawel Mastalerz

Maintain FIO Ledger App

Objective: Ensure FIO Ledger App is available in Ledger App Manager

  • Coordinate with Ledger

  • Fix minor app bugs

  • No marketing or major development

 

  • Ledger app

  • Availability of FIO Ledger App in Ledger Manager

    • Target: always

  • % of on-chain actions enabled in FIO Ledger App

    • Target: TBD

USDT: 1,500/mo

@Pawel Mastalerz

Foster FIO Contributor Community

Enable FIO Contributors collaboration

  • Design, build, and host Contributors and governance tools

    • Contributor website and free tools for teams (i.e. Atlassian)

    • Free Foundation emails for teams

    • DAO tools, e.g. voting

  • Attract users to participate as Contributor and submit worker proposals including some marketing

  • Increase number of active FIO Protocol contributors (105)

  • Manage Foundation tool access

  • Promote Opportunities

  • Developer outreach / Bounty management

  • Community contributor/governance tools

  • Voting tools

  • Active Contributors

    • Target: TBD

  • Contributor satisfaction, e.g. NPS

    • Target: TBD

  • Contributor Website uptime

    • Target: 99.5%

USDT: 10,000/mo

FIO: 10,000/mo

@Pawel Mastalerz

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.

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Crypto Handle registrations (86)

  • Increase awareness of FIO Protocol (113)

  • Website, knowledge base, blog

  • Content marketing

  • Community marketing

  • Email marketing

  • Event sponsorship

  • Public relations

  • Partner marketing

  • Local meetups

  • Contests

  • Owned properties KPIs

    • New Subscribers, New FCH Regs, New Domain Purchases, New BD Leads (?)

    • Time on Site, Bounce %

  • Content/SEO KPIs

    • Unique Reach, New Users to Site, Domain Authority and Ranking

  • Community KPIs

    • Awareness

      • Mentions, Profile Visits, New Followers

    • Engagement

      • CTR, Engagements, New Users to Site (Social)

    • Acquisition

      • New FCH Regs, New Domain Purchases

  • Email Marketing KPIs

    • Awareness

      • Open %, Click %, Unsub %

    • Acquisition

      • New FCH Regs, New Domain Purchases

  • Event & Sponsorship KPIs

    • Event

      • New Users to Site, New Social Followers (Time Series), New BD Leads

    • Paid Sponsorship

      • CTR, New FCH Regs, New Domain Purchases

  • Paid Media KPIs

    • CTR, New FCH Regs, New Domain Purchases

  • Public Relations KPIs

    • Backlinks, Unique Reach, Syndication Volume, New Users to Site (Referral)

  • Brand Identity KPIs

    • Brand Sentiment, Share of Voice

 

@Ash Howe

Acquire FIO integrations

  • Reach out to and sign-up integration partners.

  • Support integration process and maintain partner relationship.

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Protocol integrations (disputed) (100)

  • Increase number of NFT signatures (93)

  • Increase number of FIO Crypto Handle registrations (86)

  • Increase Domain & Crypto Handle Regstrations and Utilization with a Single Large Partner (e.g., Opera) (105)

  • Increase awareness of FIO Protocol (113)

  • Increase number of active FIO Protocol contributors (105)

  • Integration acquisition

  • Partner marketing

  • Opera

  • Integration partners

    • Contacted

    • Signed MOUs

    • Integration started

    • Active

  • FIO Crypto Handle and Domain registrations

  • Partner integration process satisfaction, e.g. NPS

  • Est. % of users which can use FIO Protocol functionality

 

@David Gold temporary until replacement found

Support Foundation in finance and legal matters

  • Maintain, update and publish Foundation budget

  • Review agreements signed by the Foundation

  • Maintain relationship with Market Makers

  • All

  • Foundation budget, financials, legal, agreements. etc. (e.g., CFO type responsibilities)

  • Budget published monthly

 

@David Gold

Increase Domain Sales

  • Increase the number and value of domains being sold.

 

  • Get people to buy domains

  • Number of FIO Domains registered

  • Value of FIO Domains transacted on secondary market

  • Foundation income from domain sale

 

@David Gold

Foundation treasury management

 

 

 

 

 

@Luke Stokes

Operate Hey FIO Dashboard

  • Design, build, and host Hey FIO Dashboard website

  • Develop, test, and launch bug fixes.

  • Promote Hey FIO Dashboard to acquire new users

  • Increase number of FIO Crypto Handle registrations (86)

  • Hey FIO

  • Monthly Active Hey FIO Dashboard users

  • FIO Crypto Handle registrations

  • FIO Domain registrations

  • User satisfaction, e.g. NPS

  • Website uptime SLA

  • Bug to fix time

 

Hey FIO Team

Operate FIO Dashboard

https://fioprotocol.atlassian.net/l/c/fNWGN3rP

Objective: To maintain & support the existing implementation of the dashboard and construct new features to support adoption & use by users as well as integration partners.

Primary

The primary dashboard effort will create a path to ensure:

  • The dashboard is hosted, maintained and continually running.

    • Existing features are maintained, supported and evolved based on feedback.

    • Paths to adoption and use through user base growth and business partner integrations are created in concert marketing and business efforts.

Secondary

The secondary dashboard effort will create a path to ensure:

  • New features are surfaced, prioritized and built to support additional use and integration opportunity

    • A scalable future for the dashboard into industry segments.

Strategy: The strategy for the dashboard is founded around three main areas of opportunity; the end user, integration partners, and new opportunities. Each of these areas will have use cases which will be used to support them and serve in helping to create the KPIs for this project.

  • End User

    • Increase number of and value of domain sales (103)

    • Increase number of FIO Crypto Handle registrations (86)

    • Increase awareness of FIO Protocol (113)

  • Integration

    • Increase Domain & Crypto Handle Registrations and Utilization with Partners

  • Opportunity

    • Support new creative ways FIO Protocol can increase usability across new segments.

  • Dashboard

KPIs: Dashboard KPIs must be actionable and measurable. Their success depends on objective, statement of detail and the “stake” in the ground. The following is a proposed schedule and topics for creation of initial KPIs.

  1. Schedule

    1. Q3 2022

      1. Create Initial KPIs

      2. Initial Measurement

    2. Q4 2022

      1. Measurement - TBD

      2. Refinement - TBD

    3. Q1 2023

      1. Measurement - TBD

      2. Refinement - TBD

    4. Q2 2023

      1. Measurement - TBD

      2. Refinement - TBD

  2. Topics

    1. Operational

      1. Uptime SLA

      2. Bug

    2. Success Measurement

      1. Handles

      2. Domains

      3. Use

    3. Roadmap Achievement

TBD

@George Worrell

Provide FIO Chain analytics data

  • Identify data requirements from other active Worker Proposal Leads and community members.

  • Design, build, maintain and host FIO Chain analytics website/tool (currently Grafana).

  • All

  • Data analytics (i.e. grafana reports / analytics)

  • Devops

  • Secops

  • Release management

  • QA

  • % of Worker Proposal on-chain KPIs available in tool

 

 

Explore new technologies and opportunities for FIO Protocol

 

  • Identify new creative ways FIO Protocol can increase crypto usability (gaming, DeFi, private key recovery, etc.)

  • Increase number of FIO Crypto Handle registrations (86)

 

 

 

 

Transition

Project name

Description

Strategic Priority

Current initiatives

KPIs

Budget

Lead

Project name

Description

Strategic Priority

Current initiatives

KPIs

Budget

Lead

https://fioprotocol.atlassian.net/browse/WP-297

  • Implement token locking into existing account (FIP-41)

 

  • Token locking (FIP 41 - locking to existing account)

 

 

@Eric Butz

https://fioprotocol.atlassian.net/browse/WP-949

  • Implement ability to register Domain/Address in one transaction(FIP-42)

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Crypto Handle registrations (86)

  • Register Domain/Address in 1 shot (FIP 42)

 

 

@Eric Butz

 

 

 

 

 

@Ash Howe

 

 

 

 

 

@Eric Butz

Objective: Add new actions to FIO Ledger App and enable them in Dashboard

 

 

  • Launch of new functionality in Ledger App and Dashboard within 6 mos

USDT: 24,030 EUR + 10,000

FIO: 10,000

@Pawel Mastalerz

 

 

 

 

 

@Eric Butz

TBD

  • Implementing wrapping of tokens on the dashboard

  • Provide the user the ability to wrap tokens utilizing the dashboard

  • Token Wrapping

  • Launch wrapping functionality within the dashboard

TBD

@George Worrell

New

Project name

Description

Strategic Priority

Current initiatives

KPIs

Budget

Lead

Project name

Description

Strategic Priority

Current initiatives

KPIs

Budget

Lead

Code Name Fly