> For the complete documentation index, see [llms.txt](https://ocelex.gitbook.io/ocelex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ocelex.gitbook.io/ocelex/tokenomics/community-airdrop.md). # Community Airdrop The Ocelex community airdrop is designed to reward early adopters and aligned community members, ensuring long-term ecosystem stability and active participation. This document outlines the eligibility criteria, token distribution process, and the key benefits of participating in the airdrop program. *** ### Airdrop Allocation Overview To promote long-term protocol alignment, 50% of Ocelex’s initial token supply has been allocated for strategic airdrops. This ensures the protocol’s early supporters are rewarded while fostering a committed user base. **Allocation Breakdown:** * 45% – $veLYNX Holders (subject to eligibility criteria, of locks must be >1 year) * 5% – Engaged users from partner communities, including: Thena on BNB, Aerodrome on Base, Velodrome on Optimism and Fenix on Blast. Additionally, 2.5% from the ‘Partner Activations’ token supply will be distributed through Zircuit’s Launchpool. *** ### Eligibility Criteria for $veLYNX Holders To ensure fair and meaningful participation, only $veLYNX holders who meet specific criteria are eligible for the airdrop. **Eligibility Requirements:** 1. Minimum Lock Period: * Holders must have locked $veLYNX for at least one year prior to the snapshot on the 30th of November. 2. Voting Power-Based Rewards: * Airdrop amounts will be proportional to voting power, not simply the number of tokens held. Longer locks result in higher voting power, leading to larger rewards. *** ### Airdrop Distribution Details **Distribution** Timeline: * TGE Date: December 12, 2024, at 11:00 UTC. * Epoch 0: Community airdrop claims begin. * Claim Portal: Eligible wallets will be able to claim tokens through a dedicated portal. **Token Claim Conditions:** * Claim Window: Users will have 30 days to claim their tokens. * Unclaimed Tokens: Any tokens not claimed within the specified timeframe will be returned to the Ocelex treasury. **Airdrop Structure:** * All airdropped tokens will be distributed as max-locked $veOCX positions to encourage long-term ecosystem stability. These tokens will be non-liquid but tradable as NFTs on secondary marketplaces and OTC platforms. *** ### Benefits of Holding $veOCX **Holders of $veOCX will gain:** * **Weekly Rewards:** Receive trading fees, bribes, and liquidity incentives from voted pools. * **Voting Power:** Participate in weekly gauge votes to influence emissions and boost pool APRs. * Governance Participation: Vote on key governance proposals related to the protocol’s development and future upgrades. *** ### Long-Term Ecosystem Impact The airdrop structure ensures Ocelex’s alignment with its most active and committed community members. By incentivizing long-term participation through max-locked tokens, the protocol fosters sustainable growth and deep liquidity. --- # 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://ocelex.gitbook.io/ocelex/tokenomics/community-airdrop.md?ask=&goal= ``` `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.