# Proof of Contribution

### Problem: Token Efficiency

Token distribution today is extremely inefficient.

This is because there is no way to know which users to reward - especially before TGE.&#x20;

The outcome is a reverse flywheel: teams give out tokens to mercenary capital and farmers, who immediately sell the token without adding value. Token price then reduces, and the incentive to contribute reduces, and so on.&#x20;

> Tokens are a $100 billion industry - imagine if we could improve how efficiently they were used?

### Solution: Proof of Contribution

Proof of Contribution (POC) is the engine that powers reputation and loyalty based economies. The core idea behind reputation tokens is that not all users are equal, and should not be rewarded equally.&#x20;

POC works by automatically assigning a reputation score for all users of an ecosystem or app based on their onchain and offchain behaviours. This score can then be used by first and third party app builders to attract and reward the best participants.&#x20;

Long term aligned users grow the ecosystem by net positive actions and selling is disincentivized.&#x20;

### **Bigger Picture**

Proof of Contribution enables smarter token distribution:

1. Rewards go to valuable users, not bots
2. Tokens are fairly and efficiently distributed
3. Sell pressure drops through dynamic, ongoing incentives&#x20;

If it works, we expect many more projects to adopt the core concept behind Proof of Contribution.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.fishingfrenzy.co/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
