Reads eligibility
When a transfer is attempted, Sentinel reads the relevant credentials from Veritas.
Named engine · Identity, compliance and security layer
Compliance enforcement at the point of transfer.
Sentinel decides whether a transfer may proceed. When a transfer is attempted it reads eligibility from Veritas, applies the rule set configured for the asset, and enforces those rules on-chain. Forge, Agora, Registry, Flux, and Quorum all call it. Sentinel is the platform's enforcer, and it describes a function rather than a licensed activity.
What it does
Sentinel is the compliance engine. At the point of a transfer it checks eligibility from Veritas and applies the rule set that governs the asset, including on-chain enforcement of transfer rules. It is the control that decides whether a given transfer may proceed, described as a function rather than a licensed activity.
How it works
Three steps, each with one job.
When a transfer is attempted, Sentinel reads the relevant credentials from Veritas.
The transfer rules configured for the asset are applied and enforced on-chain.
A transfer that satisfies the rules proceeds, and one that does not is blocked.
Where it fits
Sentinel sits in the identity, compliance, and security layer. It depends on a single engine, and five engines call it.
Compliance enforcement at transfer.
Depends on (1)
Veritas supplies the inputs to every decision: the reusable credentials that say who a party is and whether they are eligible. Sentinel does not re-run identity checks; it reads the credential.
Forge calls Sentinel before any mint. Agora calls it before a listing transacts, Registry before a change of holder is written, Flux when a swap would be attempted, and Quorum when staking or governance would move $DREV. Cadence and Praxis also route through it, Cadence at each release and Praxis for every agent action.
Sentinel is also the enforcer in the platform's separation of powers. A smart contract assessor, a related party through common ownership, assesses smart contracts and renders a signed attestation; Sentinel acts on that verdict on-chain. No party holds both powers.
Standards and integrations
Controls
Sentinel enforces the transfer rules configured for each asset, on-chain, at the moment of every transfer, and blocks any transfer that fails them.
Common questions
Short answers to the questions people ask most about this topic.
The transfer rules configured for an asset, checked against Veritas eligibility at the point of each transfer.
Sentinel is a software function that applies configured rules. It claims no regulatory registration.
At the transfer decision. Forge, Agora, Registry, Flux, and Quorum call it whenever a transfer is attempted.
A smart contract assessor assesses smart contracts and renders a signed attestation, and Sentinel enforces on-chain. Keeping the two apart means no party holds both powers.
It is blocked and does not settle. Only transfers that satisfy the rule set proceed.
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.