> For the complete documentation index, see [llms.txt](https://openledger.gitbook.io/openledger/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openledger.gitbook.io/openledger/epoch-2.md). # Epoch 2 ## 1. Epoch 2 & Datanets ### 1.1 Whitelisted User Access * Only whitelisted users can access and participate in datanets. * Users must apply for whitelisting through the OpenLedger platform. * Once approved, users gain access to exclusive datanets and tasks.

### 1.2 Available Datanets * The platform provides various datanets categorized by different project needs. * Users can browse available datanets on the homepage. * Each datanet may have unique eligibility requirements and specific participation criteria.

### 1.3 Selecting a Datanet * Users can choose which datanet they want to contribute to based on their interests and expertise. * Each datanet will have a description outlining its objectives and required skill sets.

### 1.4 Preassessment Requirement * Users must complete a preassessment before participating in any datanet.

* The preassessment consists of multiple-choice, scenario-based, or practical questions. * Successful completion of the preassessment unlocks access to tasks within the datanet. ### 1.5 Datanet Tasks * After successfully passing the assessment, users can access the task page. * Tasks may include data validation, categorization, analysis, or other project-specific activities. * Users must complete tasks within the assigned timeframes to receive testnet points.

### 1.6 Failed Assessments & Cooldown * If a user fails a datanet assessment, they must wait 2-3 days before retaking it. * During the waiting period, users can review relevant study materials to improve their understanding. * Repeated failures may require users to contact support for further assistance.

## 2. Leaderboards & Rewards ### 2.1 Leaderboard * A specific leaderboard tracks performance within each datanet. * Users earn points based on accuracy, speed, and participation. * Top performers may receive additional rewards or incentives. * The leaderboard updates dynamically, encouraging user engagement.

### 2.2 Reward System #### **Task Reward Categories** * Points are assigned based on the category of questions. * Higher difficulty levels yield more points. | **Category** | **Reward Points** | | ------------ | ----------------- | | Hard | 30 | | Medium | 15 | | Easy | 10 | #### **Answer Result Reward Percentage** * The points earned depend on answer accuracy. * The validation process determines the final awarded points. | | | | ----------------------- | ------------------- | | **Accuracy Percentage** | **Reward Points** | | 70% and above | Full points | | 50% and above | 75% of total points | | 30% and above | 50% of total points | | Below 30% | 0 points | #### **Validation Process** * All completed tasks will undergo a validation process before points are awarded. * Reviewers will assess the answers to ensure quality and correctness. * Users will receive points only after successful validation. #### **XP System** | **Action** | **XP Earned** | | --------------------------------------------- | ------------- | | First question answered in any datanet | 1 XP | | 80% of questions answered across all datanets | 1 XP | ## 3. Epoch History * The Epoch History tab allows users to track their overall points earned during a specific epoch.

* Users can review their contributions, performance, and ranking over time. * This feature helps users assess their progress across different datanets. ## 4. Disclaimer * The details, requirements, and reward structure mentioned in this document are subject to change at any time. * OpenLedger reserves the right to modify, update, or remove any features, guidelines, or rewards without prior notice. * Users should refer to the latest updates on the platform to stay informed about any changes. --- # 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://openledger.gitbook.io/openledger/epoch-2.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.