> For the complete documentation index, see [llms.txt](https://polydash.gitbook.io/polydash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polydash.gitbook.io/polydash-docs/polypad/commitment-window.md).

# Commitment window

A commitment window is an optional period before trading opens. Wallets commit ETH to a launch and can withdraw all of it until the window ends. It gives a launch a fair opening, because no one trades against the curve while the window is open.

## Options

| Item               | Value                                                     |
| ------------------ | --------------------------------------------------------- |
| Website presets    | 24 hours, 3 days, 7 days                                  |
| Factory limit      | Any delay up to 30 days (`launchDelay`, in seconds)       |
| Minimum commitment | 0.0001 ETH (100000000000000 wei), per the agent API       |
| Zero delay         | Skips the window. The curve opens in the same transaction |

## How it works

{% stepper %}
{% step %}

### Commit

During the window, a wallet calls `commit` with ETH. A wallet can `uncommit` and take the full amount back at any time while the window is open.
{% endstep %}

{% step %}

### Start the launch

When `launchTime` is reached, anyone can start the launch. The creator's dev buy runs before commitments are filled.
{% endstep %}

{% step %}

### Process commitments

Commitments are bought in batches of up to 200 at curve prices. Later batches are permissionless. Processed commitments pay the normal platform and creator fee. They do not pay an anti-sniper surcharge and have no wallet cap.
{% endstep %}

{% step %}

### Trading opens

When the last commitment is processed, the launch moves to normal curve trading.
{% endstep %}
{% endstepper %}

## Commitments are not trapped

A commitment that is still unprocessed can be pulled back by its owner, including after graduation. If a commitment is processed after graduation, it is refunded through a pull-based `claimRefund`.

## Commit vault

An optional `PolydashCommitVault` pools several wallets into one commitment. After settlement, each depositor claims the same average-price share of tokens plus any refund. The vault has no owner, no fee, no pause, and no sweep. Its funds move only through depositor actions and the permissionless `settle`.

Current commit vault: [`0xF013bF17D511E2f65D0dA4Bd320948646F567Ae4`](https://robinhoodchain.blockscout.com/address/0xF013bF17D511E2f65D0dA4Bd320948646F567Ae4)

## Risks

A commitment is ETH that you place into a contract. Commit only what you can afford to lose, and check that the launch address matches the token you expect. The contracts are **Not audited.**


---

# 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://polydash.gitbook.io/polydash-docs/polypad/commitment-window.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.
