> For the complete documentation index, see [llms.txt](https://ours-meme-1.gitbook.io/ours.meme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ours-meme-1.gitbook.io/ours.meme-docs/impel/airdrops.md).

# Airdrops

Within the OURS (`ours.meme`) ecosystem on the open, EVM-compatible Robinhood Chain (Chain ID: 4663), airdrops are neither inflationary tokens minted from thin air nor discretionary handouts distributed through opaque, off-chain point schemes. Instead, OURS anchors its contributor rewards in a dual-track architecture that combines the largest non-dilutable supply allocation (50%) with a sustainable, fee-funded revenue stream.

The platform strictly enforces a 0% team allocation, 0% advisor reserve, and 0% private pre-mine policy. All rewards are emitted programmatically via open, immutable smart contracts triggered by verified on-chain actions and verified cultural output.

### 1. Dual-Track Funding Architecture

Airdrop and reward distributions are funded by two independent pools, each governed by separate accounting to prevent commingling with trading reserves, early fundraising capital, or protocol-owned liquidity:

```
                       OURS Dual-Track Reward Pipeline
                                    │
       ┌────────────────────────────┴────────────────────────────┐
       ▼                                                         ▼
[ Track 1: 50% Behavior & Content Mining Pool ] [ Track 2: Ecosystem Buyback Stream ]
  (Hardcoded in Total Genesis $OURS Supply)     (Funded via 16% Eco & Contributor Leg)
       │                                                         │
Dynamically unlocked via on-chain actions and   Programmatic market-buys of $OURS
verified cultural output; zero caps; claimable  stream into the reward budget (Never burned)
       │                                                         │
       └────────────────────────────┬────────────────────────────┘
                                    ▼
                     [ Isolated Reward Distributor ]
                                    │
                     Non-custodial claim by verified users
```

#### Track 1: Behavior & Content Mining Pool (50% of Total Supply)

* Allocation Size: Fixed at 50% of the total $OURS supply within the immutable platform tokenomics.
* Release Mechanism: Dynamically unlocked based on verified positive on-chain actions and recognized cultural contributions.
* Zero Artificial Caps: No daily limits, no weekly quotas, and no per-wallet constraints.
* Unrestricted Liquidity: Accrues continuously and remains non-custodially claimable at any time via the "My OURS" dashboard without mandatory lockup schedules.
* Dual-Engine Scope: Rewards on-chain trading volume, single-tier referral turnover, bonding curve graduations, as well as tutorials, video guides, viral memes, and deep ecosystem research.

#### Track 2: Flywheel Ecosystem Buyback Stream (from the 16% Allocation)

* Allocation Source: Within the platform's transparent 48/16/16/20 fee flywheel, 16% of the platform's net fee revenue is allocated to Eligible Ecosystem Project Support and Contributor Rewards.
* Non-Burn Yield Realization: Unlike the 48% buyback-and-burn leg that permanently removes tokens from circulation, a dedicated portion of this leg market-buys $OURS across DEX pools and routes it directly into the active reward budget.
* Real Yield Backing: Converts real platform volume into tangible, cash-flow-backed yield for verified builders and active referrers without inflating the total supply.

### 2. Recognized Contribution Vectors

The reward pipeline rejects off-chain clicker tasks, vanity social bots, and sybil manipulation, evaluating contributions strictly across verified on-chain events and verified content output:

| **Contribution Vector**       | **Verification Standard**                                                                                      | **Source Channel / Contract Event**      | **Rule Constraints**                                                                |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------------------------------- |
| Trading Volume Mining         | Settled gross volume across internal Bonding Curves and external Uniswap v4 pools (both buys and sells count). | `TradingGateway`, Curve, Uniswap v4 Hook | Uncapped; wash trading and self-swaps scrubbed.                                     |
| Single-Tier Referral Turnover | Valid volume and graduation milestones driven by directly referred wallets.                                    | `InviteRegistry` attribution logs        | Uncapped; permanent single-tier on-chain binding.                                   |
| Pool Graduation Milestones    | Driving an internal curve to meet target reserve capacity and migrate into Uniswap v4.                         | `LaunchFactory` graduation events        | Accumulates across multiple pools and project roles.                                |
| Independent Content Mining    | Creating guides, video tutorials, viral memes, research reports, and onboarding verified users.                | Content Mining Verification Module       | Rewarded strictly on verified real contribution; bots and fake engagement excluded. |

#### Candidate Epoch Distribution Formulation

$$\text{User Epoch Allocation} = \text{Allocated Epoch Budget} \times \frac{\text{User Valid Contribution Points}}{\text{Total Valid Points Across Eligible Users}}$$

### 3. Anti-Sybil Verification & Integrity Filters

To protect genuine builders and active traders from reward dilution, the protocol applies strict integrity filters:

* Self-Referral & Affiliated Wallet Filtering: The protocol detects and excludes circular self-referrals and reciprocal volume between linked addresses under common operational control.
* Wash-Trade Scrubbing: Zero-slippage self-trades, automated circular cross-swaps, and artificial volume padding are scrubbed from rewarded metrics.
* System Action Exemption: Platform-level interactions—such as protocol-owned liquidity (POL) seeding, automated fee buyback-and-burn transactions, and user reward claims—do not generate contribution points.
* Reorg Reversal Protection: Airdrop points and reward allocations settle exclusively on finalized block heights. In the event of an underlying EVM reorganization, unconfirmed records roll back automatically to maintain ledger precision.

### 4. Non-Custodial Claims & Gas Responsibilities

In full alignment with decentralized, non-custodial smart contract standards, gas fees are borne strictly by the transaction initiator without protocol subsidies:

| **Operation**            | **Executing Actor**         | **Access Rights & Boundary**                                                         | **Gas Fee Payer**         |
| ------------------------ | --------------------------- | ------------------------------------------------------------------------------------ | ------------------------- |
| Publishing Merkle Root   | Platform Multi-Sig / Keeper | Submits verified cryptographic root; cannot alter destinations or redirect balances. | Platform Execution Wallet |
| Claiming Rewards ($OURS) | Eligible Beneficiary        | Submits cryptographic Merkle proof to withdraw tokens directly to private wallet.    | Claiming User (Self-Paid) |

* Non-Custodial "Pull" Architecture: Airdrops and rewards are never broadcast via gas-intensive push transfers; participants claim accrued balances on demand via the My OURS dashboard.
* Zero Gas Subsidies: Contract vaults holding reward tokens cannot execute meta-transactions to cover network gas on behalf of external EOAs. Users must maintain sufficient native Robinhood Chain ETH to cover network gas when claiming rewards.

### 5. Specification Standards & Implementation Status

| **Parameter**                 | **Specification Standard**              | **Implementation Status**                                            |
| ----------------------------- | --------------------------------------- | -------------------------------------------------------------------- |
| Network                       | Robinhood Chain (Chain ID: `4663`)      | Open, EVM-compatible L2 infrastructure.                              |
| Behavior & Content Allocation | 50% of total $OURS supply               | Hardcoded platform standard in genesis tokenomics.                   |
| Protocol Revenue Leg          | 16% Ecosystem Support & Contributor Leg | Funds continuous open-market buybacks for active builders.           |
| Team & Insider Reserve        | Strictly 0%                             | Zero founder tokens, zero advisor shares, zero private allocations.  |
| Distribution Framework        | Dynamic epoch-based settlement          | Settled relative to epoch budgets and verified contribution weights. |
| Production Integration        | Isolated Reward Distributor & Indexer   | Non-custodial claiming integrated into the My OURS terminal.         |

> Launch Tokens. Fund Builders. Reward Culture. Grow the Market Together.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ours-meme-1.gitbook.io/ours.meme-docs/impel/airdrops.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
