Product Working Group 1 (PWG1)

The PWG1 proposal for a Product Working Group for a two term period (12 months) to fund and deliver on our DAO's Product Roadmap. 

PWG1 Proposes a team made up of Hinchy, Rake & Tuesdays along with a DAO Multisig

Current DAO Development Needs

Phonon technical roadmap has been developed in sync with GridPlus, and Phonon DAO needs to have the following accomplished in time for our upcoming Beta:


Task 1: Fully Defined Technical Roadmap & Project Plan

Task 2: Functioning “Change-Maker” (Proof of Concept, Design, +Beta)

Task 3: On/Off-Ramp (Onboarding new Cryptocurrencies into Phonon)

Task 4: CA Process Documentation + Tokenomics Design

Task 5: eSim Feasibility Study

To accomplish these tasks, I propose the DAO form a funded Product Working Group (PWG).

We as a community have decided to double down on our community and bet on ourselves, a number of DAO members have stepped up to help fill this working group.

Instead of forming a permanent Product Working Group, I propose we align each product working group with the leadership terms (Two 6 Month Terms) and focus on defined outcomes like the Tasks identified above.

PWG 1 will fund the initial DAO Development Roadmap (Tasks 1-5).

Organizational Structure:

These tasks require developers with knowledge of the protocol and the ability to execute the tasks that the Phonon Community requires to progress.

  • Lead Community Developer: Hinchy

  • Lead Community Hardware Engineer: Rake

  • DAO Representative: Tuesdays

  • The Multi-Sig

  • DAO Leader

Lead Community Developer (LCD):

The Lead Community Developer will have lead responsibility in accomplishing the tasks outlined by the DAO. They will have broad authority to define requirements, identify people/resources needed and work directly on product. They will work with the DAO leader on a process to add new features to the protocol and how to achieve the goals set out in the roadmap.

The LCD will define a detailed product roadmap for the organization, develop a robust and scalable architecture, lead the development of key Phonon infrastructure, ensure that the codebase is organized and useful and helpful to onboard new developers and extend future iterations to support different languages.

  • (ie. Go CodeBase, Rust CodeBase, JS/TS CodeBase)

The LCD will be responsible for leading the Phonon software development team to build and maintain the source-code, while working closely with GridPlus’ engineers. The LCD will also ensure that all community bounties are listed and available to community developers.

The LCD will need to clearly communicate his/her choices, code, build and design language. This also assures that builds can be reproduced within different environments and by other programmers.

Community Hardware Engineer (CHE)

The CHE will be responsible for the hardware-based requirements for the DAO, namely our certificate authority process. They will be responsible for completing the CA process document and forming a team to define Tokenomics for the benefit of the DAO.

The CHE will also develop and present an eSim feasibility study to determine the feasibility of a DAO-based Mobile Virtual Network Operator-based eSim process, or if there are any avenues open to the DAO to leverage an eSim.

DAO Representative

The DAO representative is a named and trusted DAO community representative who will attend development meetings on behalf of the DAO to ensure the LCD and CHE are both accountable to their timeline. The DAO Representative will make recommendations to the multi-sig with regards to the progress of the DAO development roadmap.

The DAO representative will attend weekly stand-up meetings with the community devs and report findings to the community.

The Multi-Sig

The PWG1 Multi-sig will be made up of a group of 5 trusted DAO members responsible for overseeing the disbursement of funds to the PWG team members.

The DAO Leader

The DAO Leader will collaborate with the PWG1 team to ensure the DAO’s roadmap and products are aligned, and to ensure the interests of the DAO community are protected.


The budget requested is for two 6-month terms, all members have agreed to be paid 100% in Phonon, which is a fantastic statement of belief in our project and provides meaningful relief to our treasury.

Lead Community Developer

Disbursements for the LCD will be made monthly via SuperFluid or some other DAO tooling application to ensure prompt and accountable payment. Given the broad nature of this role, I believe a monthly payment is the fairest, given that many of the requirements are not going to be well defined and will require flexibility and agility.

Lead Community Developer Annual Comp: $180,000 paid in monthly disbursements of $15,000

Community Hardware Engineer (CHE)

The requirements for PWG1 for CHE are two crucial deliverables, which have been outlined by the DAO Leader and GridPlus. Given that these are deliverable requirements, I believe the PWG1 Multi-Sig should compensate the CHE + Team (DAO is in discussion with a number of eSim/Javacard/Security Experts) based on the completion of the tasks outlined in the product roadmap.

Task 4: CA Process Documentation + Tokenomics Design Compensation: $40,000

Task 5: eSim Feasibility Study Compensation: $10,000

An additional Bonus of $5,000 worth of Phonon should be paid to the CHE for the successful completion of these tasks on time and on budget.

DAO Representative

The DAO Representative is an oversight role with broadly defined responsibilities; therefore I suggest this role also be paid in a monthly stipend.

DAO Representative Compensation: $24,000, paid in monthly disbursements of $2,000.


Thanks for putting this proposal together, Mickey. If anyone has any questions for me don’t hesitate to post them here or get in contact on Discord.



Outlined in the DAO Product Group proposal are the following tasks:

Task 1: Fully defined technical roadmap and Project Plan

Task 2: Functioning “Change-Maker” (Proof of Concept, Design, +Beta)

Task 3: On/Off-Ramp (Onboarding new Cryptocurrencies into Phonon)

Task 4: CA Process Documentation + Tokenomics Design

Task 5: eSim Feasibility Study


This document outlines a high level roadmap for Tasks 1 - 4

The DAO Product Team is expecting significant changes to the code-base, meaning that the applications outlined in tasks 2 & 3 will probably be nonfunctional in a few months due to the changes. To avoid wasting unnecessary development time

Proposed Steps:

  1. Produce Single Document for on card functionality. (GridPlus Team + Phonon DAO coordination is essential for this)

a. Spec out a CA, transactions v2, advanced transactions, posted phonons?, flexible phonons?.

b. Spend a few weeks focusing 100% of our effort into finalizing these ideas and how they could work.

c. Discuss the pros and cons of these features. Different implementations.

  1. Consult Javacard experts on our spec. Refine.

  2. Develop all these features into a mock card. Look for security issues. Write an extensive testing suite.

  3. Start developing javacard. Hire javacard experts.

a. In parallel, start developing services (change maker, NFT market, cross chain bridge) against the mock cards.

b. Cards can be developed against the test suit used to test the mock cards.

  1. First test net is testing these services using the mock cards. Anyone can participate because it doesn’t require hardware.

  2. Second testnet is testing the javacards and the services.

  3. Launch Beta

Project Board

1 Like