This repository contains all the technical details about Phala's bounty projects. It records all the interactions between the project developers and the curators and is meant to help our community members and the Council to understand and track the progress of Phala improvements.
The Phala Treasury collects its funds mainly from transaction fees, slashing, and Secure Worker mining commission (20%). The Treasury is ultimately controlled by the Council and is used for the benefit of the Phala ecosystem.
For now, there are two kinds of Treasury spending: the Tip for minor contributions like a bug fix, code optimization, and document improvement, and the Bounty for more serious contributions like extending the capabilities of the Phala network.
To apply for the Phala Bounty, refer to our tutorial and create the Bounty Proposal through the on-chain Governance module.
- Create a Bounty Proposal on chain and follow the following steps for application.
- Fork this repository.
- In the newly created fork, create a new file under the
applicationsfolder and name it after your project:project_name.md. - Fill out the details of your project. Your document should at least include the following aspects:
- Motivation
- What improvement needs to be made on what shortcomings?
- Targets
- The objective and the key results of this project. We recommend a clear benchmark to evaluate the project.
- Design
- An overall design of your solution, could be better if with the necessary background knowledge and investigations.
- Milestones
- A project can be separated into several milestones to deliver, each with its own benchmark to evaluate.
- Motivation
- Once you're done, create a pull request. The pull request should only contain one new file—the Markdown file your created.
- Proposal Review and Revision.
- The Council and the Phala Team can (and usually does) issue comments and request changes on the pull request.
- Clarifications and amendments made in the comments need to be included in the application. You may address feedback by directly modifying your application and leaving a comment once you're done. Generally, if you don't reply within 2 weeks, the application will be closed due to inactivity, but you're always free to reopen it as long as it hasn't been rejected.
- The application will be accepted and merged as soon as it receives the required number of approvals, or closed after two weeks of inactivity. Unless specified otherwise, the day on which it is accepted will be considered the starting date of the project, and will be used to estimate delivery dates.
- Curator and Shepherd Assignment.
- Curator is the domain expert to whom the Council delegates the curation activity of a spending proposal.
- Shepherd is the project secretary who helps bounty applicants to format their proposal, arrange a discussion and promote the whole bounty process.
- Project Implementation
- Milestone Deliver
- Bounty Close
| Team | Project | Link | Terminated | First Delivery | Completed |
|---|---|---|---|---|---|
| Soptq | Private Geolocation Obtaining with GeoLite2 | Github | |||
| Soptq | Network Connectivity Improvement for Workers | Github | |||
| Soptq | Optimizing Latency Graph Off Chain |