Proposal for Integration of FEATURE, a Reward-Based Protocol, to Boost Open-Source Developer Participation and Bug-Fixing

Dear Kleros Community,

The purpose of this proposal is to present a strategy for boosting developer engagement and expediting bug resolution in the Kleros protocol, especially with the arrival of v2.

We propose to integrate FEATURE, a protocol to incentive developers to contribute to Open Source projects with crypto-rewards, see docs. We believe that the adoption of this rewards-driven protocol will foster increased participation, accelerate bug detection and rectification, and ultimately enhance the overall efficiency of our ecosystem.

We propose the following three-phase plan for the integration of the FEATURE protocol into the Kleros ecosystem:

  1. Phase One - Integration and Reward Setup: This involves initiating the integration process and setting up a reward system with our native token. Different rewards are assigned based on task difficulty, with special considerations in place for salaried core team members to prevent “double spending” (see PS for the set up of the rewards).
  2. Phase Two - Testing and Stability Evaluation: Upon successful integration, a three-month testing phase will be conducted to assess the stability of the application and the effectiveness of the reward system in increasing contributions.
  3. Phase Three - Monitoring and Continuous Improvement: In this phase, we will monitor the effectiveness of the integration, making necessary improvements based on feedback and performance data. Upon successful testing, we aim to extend the use of the protocol to other partnerships.

While considering this proposal, it’s important to keep in mind potential disadvantages. Some studies suggest that external rewards may demotivate individuals. However, we argue that economic incentives are necessary for long-term commitment.

Also, the division of our native token among various bug bounty protocols could be seen as a downside, but we ensure that the reserve is sufficient and that rewards are automatically reimbursed after the claim delay.

Given these considerations, we’ve compiled a summary table highlighting the pros and cons of this proposal:

Pros Cons
Increased Developer Participation Potential Demotivation from External Rewards
Enhanced Bug Detection and Resolution Our native token being split among multiple bug bounty protocols
Boosted System Efficiency and Evolution
Empowering Builders with More Governance Power
System Accommodates for Salaried Team Members

We invite the community to provide their valuable feedback on this proposal.

Upon positive reception, we look forward to transitioning this proposal to a snapshot vote for final approval.


Task difficulty determines the reward size, using a scale based on the Fibonacci sequence, a commonly used sizing strategy in Scrum methodology. This sequence provides a set of standardized difficulties that reflect the complexity and time required to complete a task.

The PNK rewards corresponding to each size are as follows:

  • Size 1 (700 PNK, approx. $15)
  • Size 2 (1400 PNK, approx. $30)
  • Size 3 (2100 PNK, approx. $45)
  • Size 5 (3500 PNK, approx. $75)
  • Size 8 (5600 PNK, approx. $120)
  • Size 13 (9100 PNK, approx. $195)
  • Size 21 (14700 PNK, approx. $315)

For the double escrow system, see double escrow.


Check this first:

This will require keeping the tasks up-to-date, synchronised, single source of truth.

Of course, Dework is a prominent players in the decentralized development arena as well.

I tried to see the tasks on Dework but without success. They seem to be a bit dated.

FEATURE holds several key advantages compare to Dework:

  1. Trustless Escrow System: FEATURE employs a trustless escrow mechanism that can be arbitrated by Kleros. This feature facilitates a secure and transparent transaction process that aligns well with our ethos of decentralization.
  2. GitHub-First Approach: Unlike other platforms, FEATURE places a significant emphasis on GitHub. As GitHub is currently the primary platform for open-source development, this approach enables developers to contribute to Kleros without needing to navigate and adapt to an entirely new platform.
  3. Ease of Bounty Setup: FEATURE allows the direct setting up of bounties within GitHub, removing the need for developers to transition between multiple platforms. This convenience could lead to increased participation and engagement from developers.

While Dework does offer a Kanban board for project management, we can achieve similar functionality using GitHub projects, which many of our developers are already familiar with.

Furthermore, I had an insightful conversation with representatives from OpenQ, another platform in the decentralized development space. You can read a transcript of our discussion here.

We must emphasize that these platforms - FEATURE, Dework, and OpenQ (see also Immunifi, Gitcoin…) - are not mutually exclusive. They each offer unique advantages, and their complementary use could potentially enhance our ecosystem as long as their setup and maintenance do not demand significant resources, particularly time, as long as there is a minimum return on investment.

However, it is important to note, unless I am mistaken, that as of now, only FEATURE allows the arbitration of disputes via Kleros, providing an additional layer of security and trust.

If there should be a single source of truth, it’s GitHub since the task management of Open Source projects is done predominantly via this platform.

From your screenshot, I see two tasks. Do you know if they have been completed?
Have you ever tried Dework or FEATURE and if so, can you give us some feedback?

1 Like

With the new platform - it will repeat the same problem.

Social problem, not technical problem. Real-life example: me attending Kleros dev calls and realising there is yet another call designated for scheduling that is not public.

My preference is towards SINGLE SOURCE OF TRUTH. Multiple platforms can cause confusion, add complexity, synchronising issues.

I think that the best option - not sure how possible - would be a direct GitHub integration. Attaching bounty to a task directly on GitHub.

No idea. I think it is dated / dead / not maintained.

Ask @jaybuidl and @xpriment626

That’s what FEATURE does.


upvoting this proposal :+1:

1 Like