Ctrlk

Schedules and Releases

Model unlock/vesting and configure signer-attested release limits.

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

Prev: Step 1 — Setup

Last updated