> For the complete documentation index, see [llms.txt](https://docs.rubyscore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubyscore.io/overview/problems-rubyscore-solves.md).

# Problems RubyScore Solves

**Bots distort metrics.** Up to 70–80% of airdrop and campaign participants can be fake accounts. RubyScore filters them out, keeping only real users.

**Unfair campaigns.** Rewards are often distributed equally even when contributions differ. RubyScore accounts for real activity and fairly rewards genuine contributors—within a single blockchain and across multiple chains.

**High acquisition costs.** Teams spend budgets on click-through tasks that don’t create real engagement. With RubyScore, projects can target users who actually interact with the ecosystem.

**Fragmented identity.** A single user’s activity is scattered across different blockchains. RubyScore unifies it into a single, reputation layer.

**In short, RubyScore builds the trust foundation for Web3:**

* users build on-chain reputation and unlock new opportunities,
* projects protect budgets, find real participants, and distribute rewards fairly,
* ecosystems grow through authentic on-chain activity.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.rubyscore.io/overview/problems-rubyscore-solves.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.
