> For the complete documentation index, see [llms.txt](https://polymarks.gitbook.io/polymarks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polymarks.gitbook.io/polymarks-docs/token-and-revenue-sharing/revenue-sharing.md).

# Revenue Distribution

## Overview

PolyMarks will distribute a portion of Polymarket referral earnings to $POLYMARKS token holders.

## How We Earn Revenue

PolyMarks generates revenue through Polymarket's referral program:

1. User clicks "Trade on Polymarket" button on PolyMarks
2. User creates account or places trade on Polymarket
3. Polymarket pays PolyMarks a referral fee
4. PolyMarks distributes portion to qualifying token holders

## Eligibility Requirements

### Minimum Holding Requirement

**Hold 20,000,000+ $POLYMARKS tokens**

That's it. No tiers. No complexity. Just hold the minimum and qualify for revenue sharing.

### Snapshot Schedule

* Monthly snapshots on the **1st of each month**
* Must hold **20,000,000+ $POLYMARKS** at time of snapshot
* No lock-up period required
* No staking required

## Distribution Mechanism

### Monthly Payouts

1. **Revenue Collection:** All referral earnings for the month
2. **Revenue Pool:** Portion allocated to qualifying token holders
3. **Snapshot:** Check wallets holding 20M+ tokens
4. **Distribution:** Split equally among all qualifying wallets
5. **Payout:** Automatic airdrop

### Payment Currency

* **USDC** (Polygon network)
* Low gas fees
* Instant receipt

## Example Calculation

**Scenario:**

* Monthly referral revenue: $100,000
* Token holder allocation: 30% → $30,000
* Qualifying wallets: 150 wallets (all holding 20M+ tokens)

**Your Share:**

```
Revenue pool = $30,000
Qualifying wallets = 150
Your payout = $30,000 / 150 = $200 USDC
```

**Simple Math:**

* More revenue = Higher payouts
* More qualifying holders = Split among more wallets
* All qualifying holders get equal share (no tiers)

## Transparency

### Public Revenue Dashboard

* Real-time referral earnings tracker
* Monthly revenue reports
* Distribution history
* Qualifying wallet count

### On-Chain Verification

* Revenue wallet address (public)
* Distribution transactions (public)
* Snapshot data (public)
* Audit trail (immutable)

## Important Notes

⚠️ **Disclaimer:**

* Revenue sharing is subject to Polymarket's referral terms
* Amounts may vary based on platform activity
* No guaranteed minimum payout
* Subject to applicable laws and regulations

🔒 **Security:**

* Smart contract audited before launch
* Multi-sig wallet for revenue
* No access to user funds
* Transparent treasury

💎 **Fair Distribution:**

* No whales get unfair advantage
* 20M minimum = accessible to community
* Equal share for all qualifying holders
* No complex tier calculations

***

**Questions?** Join the discussion on Twitter [@polymarksBSC](https://x.com/polymarksBSC)


---

# 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, and the optional `goal` query parameter:

```
GET https://polymarks.gitbook.io/polymarks-docs/token-and-revenue-sharing/revenue-sharing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.