> 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/key-use-cases-include.md).

# Key use cases include

* **Protecting reward distribution** – Ensuring testnet faucets, airdrops, and quests reach real users.

  \
  **Airdrop Security**

  * Validates legitimate recipients to prevent multiple claims by the same user.
  * Ensures fair distribution of tokens within the community.
  * Enables tiered airdrop allocation based on ID or **humanity scores** for trusted users.

  \
  **Quest Reward Protection**

  * Prevents automated farming of quests and point-based rewards.
  * Validates task completion before distributing rewards.
  * Allows scaling of rewards based on a user’s humanity verification level.

  \
  **Testnet Faucet Protection**

  * Prevents bots from mass-claiming testnet tokens.
  * Ensures testnet resources are fairly distributed among real developers.
  * Filters out automated accounts while maintaining accessibility.

* **Verifying community participation** – Authenticating on-chain interactions, governance, and contributions.

  **Governance Authentication**

  * Ensures only verified users participate in governance decisions.
  * Validates voting participants and proposal submissions.
  * Protects decision-making from fake or duplicate identities.
  * Enables **weighted voting** based on verification levels.

* **Controlling platform access** – Managing early access, feature gating, and beta testing.

  \
  **Testnet Participation**

  * Manages early access programs by verifying genuine users.
  * Controls the quality of the testing environment.
  * Ensures only real developers and testers contribute feedback.
  * Prevents misuse of limited testnet resources.

  \
  **Feature Access Management**

  * Restricts verified users access to beta or premium features.
  * Ensures controlled distribution of experimental features.
  * Enables **tiered access** based on verification levels.

  \
  **Beta Testing Programs**

  * Verifies that testers are genuine users, not automated accounts.
  * Ensures the testing group consists of high-quality participants.
  * Enhances the value of feedback by keeping testing environments secure.

* **Securing token events** – Validating token claims, whitelist entries, and fair distribution.

  \
  **Token Generation Events (TGE)**

  * Validates the legitimacy of participants before allowing access.
  * Prevents multiple registrations to maintain fair distribution.
  * Ensures tokens are allocated to real users.

  **Whitelist Management**

  * Verifies whitelist entries before granting access to sales or events.
  * Prevents duplicate sign-ups or fraudulent registrations.
  * Ensures fairness in presale participation.

  **Token Claim Verification**

  * Authenticates eligibility before allowing claims.
  * Prevents automated claiming or bulk farming of tokens.
  * Enables tiered claiming based on verification levels.

* **Filtering marketing activities** – Ensuring genuine engagement in contests, referrals, and campaigns.

  \
  **Contest Management**

  * Prevents multiple entries from the same person.
  * Ensures fair competition and valid participation.
  * Tracks verified participation to uphold contest integrity.

  \
  **Referral Program Security**

  * Confirms referral sources are legitimate.
  * Prevents self-referrals and exploitative practices.
  * Ensures only genuine users benefit from referral programs.
  * Creates a trusted referral network for organic growth.


---

# 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/key-use-cases-include.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.