# Schedules and Releases

### Unlock vs Vesting

* **Unlock schedule**: time-based milestones that make tokens eligible to claim.
* **Vesting**: deliver eligible tokens via a **CliqueLock** linear stream.

You can use unlock-only, vesting-only, or unlock that feeds vesting.

### Signer-controlled `released`

An off-chain service tracks per-handler `released` (cumulative).\
A signer (EIP‑712) attests `{ root, handler, released, onBehalfOf?, deadline }`.\
The contract enforces: `amount ≤ released - previouslyClaimed`.

#### Dynamic vs fixed recipient

* **Fixed**: Merkle leaf binds recipient: `handler == keccak256(onBehalfOf)`.
* **Dynamic**: Signer includes `onBehalfOf` in signature; Merkle doesn’t hard-bind.

### Map roots to configurations

For each Merkle `root`, set `configurationId[root]` to the configuration you created in Step 1.\
Roots may reuse or override fees and windows.

**Next:** **Step 3 —** [Onboarding CSV](/token-distribution/quickstart/onboarding-csv.md)

**Prev:** **Step 1 —** [Setup](/token-distribution/quickstart/setup.md)


---

# 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.clique.tech/token-distribution/quickstart/schedules-and-releases.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.