# Airdrop

**TL;DR**

* **100 ONI Early-Engagement Airdrop** - complete all steps in **October 2025** (details below).
* **2,000 ONI Bug Bounty Airdrop** - to the single winner who reports the **most severe valid bug first**.
* **Deadline:** **October 31, 2025, 23:59 CEST**
* **Payouts:** **Early November 2025**
* Platform: [**app.onino.io**](http://app.onino.io)

***

### 100 ONI Early-Engagement Airdrop

**Reward**

* **100 ONI** per eligible participant (one reward per person).

**How to qualify (all steps required in October 2025)**

1. **Sign up** at [**app.onino.io**](http://app.onino.io).
2. For **all three “Coming Soon” projects**:
   * Select **Interested** and state **how much** you would invest **(indicative)**; **or**
   * Select **Not interested** and provide a short **reason**.
3. Complete **KYC**.
4. Add a **valid ONINO Mainnet wallet address** to your profile (this is where we send the ONI).

**Timing**

* Eligibility window closes **October 31, 2025 at 23:59 CEST**.
* Distribution in **early November 2025**.

**Notes**

* Indicative interest signals are **non-binding** and for allocation planning only.
* **One reward per natural person**; duplicate accounts or attempts to circumvent limits will be disqualified.
* Standard anti-fraud checks apply.

***

### 2,000 ONI Bug Bounty Airdrop

**Goal**

Help us harden the platform during the “Coming Soon” phase.

**Reward**

* **2,000 ONI** to the **single** winner who submits the **most severe valid bug first** (as determined by ONINO’s review).

**Scope (examples, non-exhaustive)**

* **High severity (what we’re looking for)**
  * Security/privacy exposure (e.g., unauthorized access, data leakage)
  * Authentication/authorization bypass
  * Loss or corruption of user data
  * Critical transaction logic errors (e.g., incorrect balances, irreversible state corruption)
  * KYC/identity flow bypass or integrity failure
* **Medium/Low (eligible but unlikely to win)**
  * Blocks core flows without security impact, serious state errors, or repeatable crashes

**Out of scope**

* Typos, cosmetic/visual issues, minor layout quirks
* Issues caused by non-standard browser extensions or dev tools
* Duplicates (earliest valid report counts)
* Third-party service outages outside our control

**How to report**

* Use **“Report a bug”** inside [**app.onino.io**](http://app.onino.io). Include:
  * Clear **steps to reproduce**
  * **Expected vs. actual** behavior
  * **Screenshots / screen recordings**
  * **Browser & OS** details, plus any relevant headers/network info (if safe to share)

**Selection & tie-breakers**

* We evaluate **impact**, **exploitability**, **user reach**, and **clarity of report**.
* If multiple reports describe the **same** bug, the **earliest valid submission** wins.
* If distinct bugs tie on severity, the one with **greater impact** wins.

**Responsible disclosure**

* Please **do not publicly disclose** details before we confirm and mitigate.
* Only test with your own accounts and data; do not compromise others’ privacy or funds.


---

# Agent Instructions: 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:

```
GET https://docs.onino.io/for-users/the-onino-tokenization-platform/airdrop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.