The Reputation System for Predicting Earnings

We use a reputation system based on users' past performance to make predictions on how much Developers can earn for delivering Solutions.

The reputation system keeps track of how much a user pledged to ideas in the past, and what percentage of those pledges the user actually paid out.

There are two types of reputation:

• Pledge reputation based on the user's past Pledges.
• Developer reputation is based on the dev's past Solutions.

Pledge Predictions

Each topic or feature-request will displays two numbers:

• the total amount pledged by users
• and the estimated payout based on the involved users past performance

This system helps keep the platform safe, and gives developers better insight into what to expect. It also helps fight spam and manipulation of the platform.

How Solutio Calculates Reputations

Reputaitons are recalculated for users each time they accept/reject/pay for a Solution.

Example-A:

• A user pledged 100 ICP to an idea, accepted it, and paid the 100 ICP amount, resulting in a 100% score.
• For another idea, the same user pledged 100 ICP, accepted it, and tipped an extra 10 ICP, totaling 110 ICP and resulting in a 110% score.
• However, for a third idea, the user pledged 100 ICP but rejected it, paying 0 ICP, resulting in a 0% payout.

The user's resulting reputation score:

Total Pledged: 300
Total Paid: 210
Score: 210/300 = 0.7 = 70%

Example-B:

• The user pledged 150 ICP to an idea and accepted, paying the full amount of 150 ICP. 100% payout.
• Then, the user pledged 80 ICP to another idea, accepted it, but paid only 60 ICP because they weren't fully satisfied with the result. 75% payout.
• Next, the user pledged 120 ICP to a third idea, but rejected it, paying 0 ICP. 0% payout.

The user's resulting reputation score:

Total Pledged: 350
Total Paid: 210
Score: 210/350 = 0.6 = 60%

How Reputations Predict Pledge Payout

Solutio uses the reputation scores of pledging users to calculate better earn predictions for developers.

Using the two previous examples:

• user-A pledges 100 ICP to the idea, and has a score of 70%.
  His estimated payout is: 100 ICP * 70% = 70 ICP
• user-B pledges 100 ICP to the idea, and has a score of 60%.
  His estimated payout is: 100 ICP * 60% = 60 ICP

When a developer looks at that idea, it will display:

• Total ICP pledged: 200 ICP <- The sum of each user's pledge,
• Expected payout: 130 ICP <- The sum of each users expected payout.

How to handle new users (no score yet) and projects with few pledgers

Challenges:

• New users will not have a score yet, so they have no reputation score to use in payout predictions.
• Payout predictions work on average, but not individually. If a project doesn't have enough users pledging, it might mislead developers.

We will have to test the reputation system during the alpha and, based on the results, implement rules to better handle these cases. Currently, our options are:

• assign an average score to new users (average of all users on the platform)
• assign a very low score to new users (between 0-1%) and allow users to earn a better reputation over time.
• keep track of the score of new users after the first transaction, and apply the average of all those first transactions to new users.
• Extra Feature: Display a "safety level" on projects, based on how many different users are pledging and how many projects they have taken part in so far. This can be done independently of which approach is used.

Which option we decide for will heavily depend on the actions of the community.

Developer Reputation

We will also keep track of the developer's reputation, keeping track of what percentage of pledged funds end up being paid to Solutions he delivers. This will not be used in any price predictions, but rather as a badge of honor on the developer's profile.

Find out more

You can find out more info in the Reputation Calculation & Storage Documentation