# Fundraising Round Rules

OneWorld Launchpad uses a round-based fundraising model.\
Each fundraising round is configured, settled, and advanced independently.

With round-based fundraising, a project can set different prices, allocations, and targets at different stages. Users can evaluate whether to participate in the current round based on project progress and previous-round results.

### What Each Round Must Define

When creating or advancing a fundraising round, the project owner must define:

1. Current-round sale amount
2. Current-round price
3. Current-round original fundraising target
4. Current-round start time
5. Current-round end time
6. Conditions for opening the next round after current-round success

Input order:

1. Current-round sale amount
2. Current-round price

The system can then derive:

Current-round original fundraising target = current-round sale amount x current-round price

If the manually entered fundraising target does not match the sale amount and price, it must be corrected before submission. Otherwise, review may be affected.

### Parameter Definitions

#### Current-Round Sale Amount

The maximum amount of Tokens allocated to users in the current round.\
This amount determines the current-round subscribable allocation and affects the number of Tokens users can claim after success.

#### Current-Round Price

The subscription price per Token in the current round.\
A user's subscription amount is converted into an estimated claimable quantity according to this price.

#### Current-Round Original Fundraising Target

The fundraising amount the project owner wants to complete from newly sold Tokens in the current round.\
If the current round also needs to absorb previous-round exit applications, the total fundraising target may be higher than the original fundraising target.

#### Start Time and End Time

Start time determines when users can subscribe.\
End time determines the latest time at which the round enters settlement judgment.

#### Next-Round Conditions

Next-round conditions explain what the project must satisfy after the current round succeeds before it can continue.\
They usually relate to fund usage, product delivery, community goals, technical milestones, or external launch conditions.

### How Users Should Read a Round

For users, the most important points are:

1. How many Tokens are being sold in this round
2. What price is used in this round
3. When this round starts and ends
4. What status the project enters after this round succeeds

Users should also pay attention to:

1. Whether this round includes previous-round exit absorption
2. Whether the round is close to full allocation
3. Whether refunds are available if the round fails
4. When Tokens can be claimed after round success
5. Whether the project owner plans to apply for the next round and whether a stage proof will be required

### Oversubscription Handling

Oversubscription is handled as follows:

1. Each round has a clear fundraising cap
2. New subscriptions stop after the cap is reached
3. If the final subscription exceeds the remaining allocation, only the fillable portion is accepted and the rest is automatically returned

This keeps:

1. Current-round price clear
2. Current-round allocation clear
3. User expectations stable
4. Project owner fundraising results calculable

### When a Round Is Complete

#### Early Completion

If the total fundraising target is reached before the end time, the round can complete early.\
After early completion, no new subscriptions are accepted and the round enters settlement preparation.

#### Time-Based Settlement

If the round does not fill early, the system determines success or failure after the end time.\
The judgment usually depends on whether actual subscription reaches the success condition.

### What Happens After a Round Succeeds

After the current round succeeds:

1. Users do not receive results automatically
2. The project owner must actively initiate an on-chain fund claim
3. The platform enters settlement and result-claim status
4. Users must initiate on-chain claims after results are claimable
5. The project owner can actively claim funds on-chain
6. If the project owner wants to open the next round, a stage proof must be submitted and approved

Success only means the current-round fundraising target has been met. It does not automatically open the next round or complete final launch.

### What Happens After a Round Fails

After the current round fails:

1. The round no longer continues fundraising
2. Users can claim refunds according to the rules
3. If exit applications are involved, related assets are processed according to settlement rules
4. The project owner cannot directly open the next round
5. The project page keeps the failure result so users can review the reason and follow-up arrangement

### Example

Assume the project owner configures:

1. Current-round sale amount: 100,000 Tokens
2. Current-round price: 0.10 USDT

Then:

Current-round original fundraising target = 100,000 x 0.10 = 10,000 USDT

If the current round also needs to absorb a previous-round exit settlement pool of 2,000 USDT, then:

Current-round total fundraising target = 10,000 + 2,000 = 12,000 USDT

This means current-round new funds must first cover the exit settlement pool before forming net new fundraising for the project owner.


---

# 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.oneworld.xyz/oneworld-launchpad/core-rules/fundraising-round-rules.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.
