> 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/feature/community-fundraising.md).

# Community Fundraising

The Community Fundraising page serves as the native capital contribution and equity subscription portal on the OURS platform (`ours.meme`). Built natively on the open, EVM-compatible Robinhood Chain (Chain ID: 4663), it allows early community backers to deposit native ETH and secure a proportional share of the fixed 20% platform token ($OURS) community fundraising pool.

### 1. Core Ecosystem Metrics

The top metrics panel tracks macroeconomic indicators and on-chain protocol baseline data from inception:

* Market Cap: Dynamically calculated upon TGE and pool deployment based on live circulating supply and real-time market price.
* 24h Volume: Aggregates all verified on-chain swap events across the network once trading goes live.
* Holders: Tracks the count of unique wallet addresses holding $OURS following initial token distribution and user claims.
* Total Burned: Accumulates automatically as the on-chain fee flywheel executes programmatic market buybacks and burns of $OURS.

### 2. Platform Tokenomics ($OURS Allocation)

The total supply of $OURS is strictly budgeted into immutable categories via smart contracts to eliminate insider dump risk and guarantee long-term alignment:

Plaintext

```
                      $OURS Token Distribution
  +-------------------------------------------------------------+
  | [■■■■■■■■■■■■■■■■■■■■■■■■■] 50% Behavior & Content Mining   |
  | [■■■■■■■■■■■■■■■] 30% Protocol-Owned Liquidity (POL)        |
  | [■■■■■■■■■■] 20% Community Seed (12-Month Linear Vesting)   |
  | [ ZERO ] 0% Team / VC / Insider Allocation                  |
  +-------------------------------------------------------------+
```

* 50% Behavior & Content Contribution Mining: Released dynamically to real ecosystem builders. Rewards verified swap volume, single-tier referral turnover, pool graduations, and contributions through the independent Content Mining system (tutorials, video production, viral memes, in-depth research, and community onboarding), filtering out bots, wash trading, and vanity noise.
* 30% Protocol-Owned Liquidity (POL): Dedicated to seeding deep DEX trading pairs and establishing permanent liquidity pools paired with 190+ compliant Robinhood Stock and ETF Tokens, custodied and held permanently by the protocol.
* 20% Community Fundraising Allocation: A fixed, non-dilutable pool distributed among fundraising participants strictly proportional to their valid capital contribution.
* 0% Team & Insider Reserve: Zero tokens are allocated to founders, core teams, or advisors. To acquire $OURS, operators must participate alongside the community through real contribution mining or open-market acquisition.

### 3. Fundraising Structure & Valuation Framework

The page provides complete mathematical clarity and full disclosure of capital allocation:

#### Core Financial Parameters

* Subscription Asset: Robinhood Chain Native ETH.
* Target Range: $1,000,000 to $2,000,000 USD equivalent in ETH.
* Dynamic Valuation Formula: Final Platform Valuation = Final Effective Raised Capital × 5.
  * Raising $1.0M ➡️ Implies an initial $5.0M platform valuation.
  * Raising $2.0M ➡️ Implies an initial $10.0M platform valuation.
* User Token Allocation Formula:

$$\text{User Token Allocation } A = 20% \times \text{Total Supply } S \times \frac{\text{User Valid Contribution } c}{\text{Total Round Effective Capital } C} \quad \text{}$$

* Vesting Schedule: Continuous 12-month linear vesting starting from TGE (unlocked per second/block) with 0% initial cliff/instant unlock, eliminating Day-1 speculative dump pressure.

#### On-Chain Enforced Capital Utilization

* 80% Market Liquidity & Architecture: Deployed into market-making, external pool liquidity pairing, and asset stability systems via verifiable on-chain contracts.
* 20% Product Engineering & Operations: Reserved for smart contract security audits, infrastructure maintenance, core protocol engineering, and public multi-sig treasury reserves.

### 4. User Journey & Contract Lifecycle

The interface interacts directly with the fundraising contract state machine:

1. Wallet Connection: Switch your network to Robinhood Chain (Chain ID: 4663) and connect an authorized Web3 wallet.
2. Deposit Formulation: Enter the desired ETH deposit amount. The interface calculates the USD equivalent via live on-chain oracles and computes the real-time estimated share of the 20% pool.
3. Cryptographic Confirmation: Review risk parameters and terms, sign the transaction, and record the valid deposit once confirmed by block receipt.
4. Final Round Settlement: Upon round completion, the contract aggregates total net deposits and permanently locks each participant’s exact token entitlement.
5. Linear Claiming: Starting at TGE, participants can visit this terminal at any time to claim accrued, linearly vested $OURS tokens directly into their wallet.

### 5. Ecosystem Value Alignment & Transparent Fee Flywheel

* "Those Who Build the Market Own It": The fundraising mechanism aligns early capital providers and long-term network participants, replacing opaque seed allocations with transparent, community-owned protocol equity.
* Direct 48/16/16/20 Flywheel Connectivity: A dedicated gateway links users to the live FlywheelVault monitor, providing transparent on-chain auditing of the platform's 30% net fee revenue:
  * 🔥 48% dedicated to $OURS Market Buyback & Burn (continuous supply deflation)
  * 💧 16% dedicated to Liquidity Development (deepening protocol-owned reserves)
  * 🌟 16% dedicated to Eligible Ecosystem Project Support (backing leading memes and ecosystem builders)
  * ⚙️ 20% dedicated to Security, Development, and Operations


---

# 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/feature/community-fundraising.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.
