Skip to content
DAMREV
Start a Structuring Review

Named engine · Financial infrastructure layer

Cadence

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

What does Cadence do?

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.

  • Vesting schedulesLockups and staged releases follow the rules set for the asset, not manual instructions.
  • Checked at every releaseEach tranche moves only after identity and transfer rules clear.
  • Recorded for servicingEvery release lands in the holder register and the treasury view.

How it works

How does Cadence work, step by step?

Three steps, each with one job.

  1. Step one

    Schedules releases

    Cadence holds the vesting and release schedule configured for an asset issued through Forge.

  2. Step two

    Gates each release

    Before tokens move, Veritas confirms the recipient's identity and Sentinel confirms the release is permitted.

  3. Step three

    Reports to servicing

    Each release is recorded through Registry and reflected in Reserve and Equilibrium.

Where it fits

Which engines does Cadence depend on, and which use it?

Cadence sits in the financial infrastructure layer, between issuance and servicing. It depends on Forge and passes its results to three engines.

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

Which standards and networks does Cadence work with?

  • SorobanVesting and lockup rules are written as Soroban contracts, which run natively on the Stellar ledger and have been on mainnet since February 20241. A schedule held in code applies the same way on every release date.
  • StellarReleased tokens settle on Stellar, where ledgers close about every five seconds and each is final at close2, so a release is complete when its ledger closes.

Controls

What does Cadence enforce, and what does it never do?

Cadence enforces

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.

Cadence never

  • Releases outside the configured schedule
  • Releases to an unverified party
  • Describes a release as income, a return, or a promise of value

Common questions

What do people ask about Cadence?

Short answers to the questions people ask most about this topic.

What does Cadence do?

Cadence schedules and releases issued tokens, applying vesting and lockups, with Veritas and Sentinel gating each release.

Does Cadence imply a return?

Cadence describes timing and release only. It uses no return, yield, or schedule-of-value language.

What does Cadence depend on?

Forge. Cadence releases what Forge has issued, then records each release through Registry.

Who checks the recipient at release?

Veritas and Sentinel do. Veritas supplies the recipient's credential and Sentinel applies the asset's transfer rules before tokens move.

Where is a release recorded?

In Registry's register of holders, with the movement also reflected in Reserve and Equilibrium.

Can a schedule differ between assets?

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.

References

  1. 1.Stellar Development Foundation, "Protocol 20 and smart contracts are live on Mainnet". https://stellar.org/blog/developers/protocol-20-and-smart-contracts-are-live-on-mainnet
  2. 2.Chainstack, "What is Stellar". https://chainstack.com/what-is-stellar/ Also: Stellar developer documentation, "Control access to an asset", https://developers.stellar.org/docs/tokens/control-asset-access

Last updated:

Ready to build on programmable infrastructure?

Tell us what you want to tokenize. We will show you how DAMREV can run it.