# Joint Pools

### **Purpose**

Join Pools (Layer 3) are designed to **amplify referral performance through coordinated collaboration**, without changing how referrals are tracked or how rewards are paid.

Joint Pools allow contributors to **work together under a shared structure** to reach higher referral tiers faster, while **each participant continues to earn rewards individually** through their own referral activity.

> Joint Pools do not create new referral links, do not pool rewards on-chain, and do not override individual ownership of referrals.
>
> They function purely as a **tier amplifier**.

***

### **How Joint Pools Work**

At a high level:

1. A **Joint Pool is created by a qualified Mentor** and approved by the Arkada team.
2. Contributors **join the pool voluntarily** using their existing referral setup.
3. Each contributor continues to:
   * use their **own referral link**,
   * onboard users independently,
   * earn rewards **directly to their wallet**.
4. The **combined performance of the pool** is used to determine a **pool-level tier**.
5. Each pool member temporarily benefits from the **highest eligible tier** achieved by:
   * their **personal performance**, or
   * the **pool’s aggregated performance**.

> Rewards are still calculated per user, paid instantly on-chain, and remain fully transparent in the profile page (Performance Hub).

***

### **What Joint Pools Do (and Do Not Do)**

#### **Joint Pools DO**

* Amplify referral tiers through collaboration
* Reward coordination and collective execution
* Help smaller or newer contributors access higher tiers faster
* Enable mentors to structure cohorts and learning groups
* Stack **on top of Layer 1 and Layer 2**, within system caps

#### **Joint Pools DO NOT**

* Create shared wallets or pooled balances
* Replace individual referral tracking
* Delay or batch payouts
* Bypass system caps or safeguards
* Override Arkada’s right to review or revoke participation

***

### **Tier Amplification Logic**

Joint Pools are treated **conceptually like a contributor** when it comes to tier evaluation.

* Pool performance is measured using the **same quest-driven value logic** as individual referrals.
* If the pool qualifies for a higher tier than a member’s personal tier:
  * the **higher tier applies** for that member while they are in the pool.
* If a member’s personal tier is higher:
  * their **personal tier takes precedence**.

> Tier amplification is dynamic, adjusts automatically, and reflects current performance — no snapshots.

***

### **Entry, Lock Period & Membership Rules**

* **Joining a pool is permissionless**, subject to pool rules and Arkada approval.
* Once a user **joins a pool**, they are **locked in for 1 month**.
* During the lock period:
  * The user **cannot exit** the pool.
  * Referral activity continues normally.
* After the lock period:
  * Exits are allowed.
  * Tier amplification adjusts accordingly.

This design:

* prevents pool hopping,
* limits abuse,
* keeps the system simple and predictable.

***

### **Rewards & Payouts**

* **All rewards are paid instantly on-chain**, at the moment a quest completion generates value.
* Rewards are sent **directly to each contributor’s wallet**.
* Joint Pools **do not delay, aggregate, or redistribute payouts**.

> Pools influence which tier applies, not how or when funds move.

***

### **Contribution Performance**

Pool performance is based on **contribution performance**, meaning:

* Quest completions generated by all pool members
* Normalized value derived from those completions
* Fully visible and traceable in each user’s **Performance Hub**

Higher contribution → higher tier → higher referral share.

***

### **Governance & Safeguards**

* Joint Pools are **mentor-defined and Arkada-approved**
* Arkada reserves the right to:
  * review pool structures,
  * remove abusive participants,
  * dissolve pools if necessary,
  * adjust tier eligibility where anomalies are detected
* All actions prioritize **fairness, sustainability, and abuse prevention**

***

### **Key Takeaways**

* Joint Pools **amplify tiers**, not rewards ownership
* One referral link per user — always
* Rewards are **individual, instant, and on-chain**
* Pool membership is **locked for 1 month**
* Collaboration increases earning potential
* System caps and safeguards always apply

> Joint Pools reward coordination and execution, not shortcuts.


---

# 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://docs.arkada.gg/referral-system/joint-pools.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.