> For the complete documentation index, see [llms.txt](https://rh-project.gitbook.io/red-horse-rh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rh-project.gitbook.io/red-horse-rh/ecosystem/2.1-membership-tiers.md).

# 2.1 Membership Tiers

RH membership tiers translate **verifiable commitment** into a simple set of privileges and program weights. A tier is not a badge granted by discretion—it is derived from on-chain locking records under rules that are designed to be easy to understand, easy to audit, and hard to game.

### Design Goals

Membership tiers are designed to:

* **Reward commitment, not noise.** Tiers reflect sustained participation via locking, not short-lived activity spikes.
* **Stay application-agnostic.** Tiers work for community initiatives today and can extend to future integrations, including **P2E-style seasonal campaigns**, without changing the core logic.
* **Minimize manipulation.** Tier qualification is based on observable state (locked amount and lock configuration), evaluated at defined checkpoints.
* **Avoid overpromising.** Tiers can influence access and weighting, but they do not guarantee profits, returns, or fixed rewards.

### How Tiers Are Determined

RH uses a points-based model so that users can qualify either by locking more RH, locking for longer, or a combination of both.

#### Membership Points (MP)

Membership Points are calculated as:

**MP = Locked RH × Duration Multiplier**

Duration multipliers are determined by the lock configuration (final values may be adjusted via governance):

* **7 days:** 1.0×
* **30 days:** 1.5×
* **90 days:** 2.0×
* **180 days:** 2.5×

This structure makes long-term commitment count more, without requiring a single “correct” lock period.

#### Tier Thresholds (Initial Parameters)

Tiers are assigned based on Membership Points (MP). The following thresholds are intended as an initial configuration and may be refined as the ecosystem matures:

| Tier   | Membership Points (MP) Threshold | Typical Profile (Example)                        |
| ------ | -------------------------------- | ------------------------------------------------ |
| Bronze | ≥ 50,000 MP                      | 50,000 RH locked for 7 days                      |
| Silver | ≥ 250,000 MP                     | 170,000 RH locked for 30 days (≈255,000 MP)      |
| Gold   | ≥ 1,000,000 MP                   | 500,000 RH locked for 90 days (≈1,000,000 MP)    |
| Legend | ≥ 5,000,000 MP                   | 2,000,000 RH locked for 180 days (≈5,000,000 MP) |

> Note: These examples illustrate how MP works. Exact tier thresholds and multipliers are protocol parameters and should be published and versioned.

### What Tiers Affect

Membership tiers may influence the following categories, subject to each program’s rules:

* **Eligibility:** Access to certain ecosystem initiatives, early programs, and community campaigns.
* **Weighting:** A tier-based weight may be applied when distributing rewards within a defined program (e.g., higher tiers may receive higher weights).
* **Priority:** Priority access where scarcity exists (e.g., limited slots in a seasonal program).
* **P2E-compatible programs:** If a P2E-style seasonal campaign is introduced, tiers can be used to gate eligibility and apply consistent weighting under verifiable participation criteria.

### When Tier Status Is Evaluated

Tier status is evaluated using **snapshots** taken at predefined times (e.g., at epoch boundaries) to reduce last-minute manipulation. Users keep their tier status for the relevant period according to the rules of each program.

### Anti-Manipulation Principles

To maintain fairness and reduce gaming risk, the tier system may include safeguards such as:

* **Snapshot-based qualification** rather than continuous “live” recalculation.
* **Minimum lock requirements** for program eligibility.
* **Weight caps or diminishing returns** in specific campaigns to reduce extreme concentration (program-dependent).

All active parameters and any safeguards must be disclosed transparently and updated only through the defined governance and operational controls.