Schedules releases
Cadence holds the vesting and release schedule configured for an asset issued through Forge.
Named engine · Financial infrastructure layer
Programmable release and vesting.
Cadence releases issued tokens on the schedule their rules set. It holds vesting, lockup, and distribution schedules for an asset, checks eligibility through Veritas and Sentinel at every release, and records each movement through Registry, with Reserve and Equilibrium seeing the result. Cadence describes timing only, so no release is framed as a return or a schedule of value.
What it does
Cadence is the release and vesting engine. It takes tokens that Forge has issued and releases them over time under the vesting, lockup, and distribution rules set for the asset, with Veritas and Sentinel gating each release. Cadence describes timing and release as a function, with no return or schedule-of-value language.
How it works
Three steps, each with one job.
Cadence holds the vesting and release schedule configured for an asset issued through Forge.
Before tokens move, Veritas confirms the recipient's identity and Sentinel confirms the release is permitted.
Each release is recorded through Registry and reflected in Reserve and Equilibrium.
Where it fits
Cadence sits in the financial infrastructure layer, between issuance and servicing. It depends on Forge and passes its results to three engines.
Programmable release and vesting.
Depends on (1)
Forge supplies what Cadence releases: tokens issued after Veritas and Sentinel have cleared eligibility, under the issuer authority of the relevant dedicated entity. Cadence then applies time to that issuance, deciding when each portion moves and to whom.
Registry takes each release into the register of holders, so ownership reflects what has vested. Reserve takes scheduled movements into the treasury picture, since it relies on Cadence for flows that happen over time. Equilibrium takes release timing into its model, because when tokens are released is part of how a token economy is modelled.
Standards and integrations
Controls
Cadence enforces the schedule and the gate together: a release happens only when its schedule allows, under the asset's rules, and only after Veritas and Sentinel clear the recipient.
Common questions
Short answers to the questions people ask most about this topic.
Cadence schedules and releases issued tokens, applying vesting and lockups, with Veritas and Sentinel gating each release.
Cadence describes timing and release only. It uses no return, yield, or schedule-of-value language.
Forge. Cadence releases what Forge has issued, then records each release through Registry.
Veritas and Sentinel do. Veritas supplies the recipient's credential and Sentinel applies the asset's transfer rules before tokens move.
In Registry's register of holders, with the movement also reflected in Reserve and Equilibrium.
Yes. Cadence holds the schedule configured for each asset, so vesting and lockups follow that asset's own rules.
Where next
The pages below pick up where this one ends. Start with the one closest to where your asset or programme stands today.
Last updated:
Insights

Since 17 September 2026 a tokenized securities venue may run automated liquidity pools in tokenized listed stock without registering as an exchange, on conditions.

The GENIUS Act binds payment stablecoin issuers from 18 January 2027, not the firms that hold or settle in stablecoins. Service providers follow in 2028.

The CLARITY Act stalled on a 49 to 50 vote, so tokenized securities stay with the Securities and Exchange Commission, as before.

Guernsey's guidance of 24 July 2026 lets a fund or issuer record and transfer its investments as tokens, under the regimes already applying to it.
Tell us what you want to tokenize.
We will show you how DAMREV can run it.