Skip to content
DAMREV
Start a Structuring Review

Named engine · Identity, compliance and security layer

Sentinel

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

What does Sentinel do?

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.

  • Point-of-transfer checkEvery transfer is tested against the asset's rules as it happens.
  • Identity-aware rulesEligibility comes from Veritas credentials rather than a separate check.
  • On-chain enforcementRules sit in contract logic, so a failing transfer does not settle.

How it works

How does Sentinel work, step by step?

Three steps, each with one job.

  1. Step one

    Reads eligibility

    When a transfer is attempted, Sentinel reads the relevant credentials from Veritas.

  2. Step two

    Applies the rule set

    The transfer rules configured for the asset are applied and enforced on-chain.

  3. Step three

    Returns a decision

    A transfer that satisfies the rules proceeds, and one that does not is blocked.

Where it fits

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

Sentinel sits in the identity, compliance, and security layer. It depends on a single engine, and five engines call it.

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

Which standards and networks does Sentinel work with?

  • StellarStellar gives the issuer of an asset authorisation flags and clawback natively1. These ledger-level controls are what on-chain transfer rules can rest on.
  • SorobanSentinel's rule logic runs as Soroban smart contracts, which came to Stellar mainnet with Protocol 20 in February 20242.
  • W3C Verifiable Credentials, through VeritasThe eligibility Sentinel reads arrives as credentials from Veritas, aligned with the World Wide Web Consortium (W3C) Verifiable Credentials 2.0 standard3.

Controls

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

Sentinel enforces

Sentinel enforces the transfer rules configured for each asset, on-chain, at the moment of every transfer, and blocks any transfer that fails them.

Sentinel never

  • Assesses or attests smart contracts, which is the role of a smart contract assessor
  • Performs identity checks itself
  • Asserts a licence or regulatory registration

Common questions

What do people ask about Sentinel?

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

What does Sentinel enforce?

The transfer rules configured for an asset, checked against Veritas eligibility at the point of each transfer.

Is this a licensed compliance service?

Sentinel is a software function that applies configured rules. It claims no regulatory registration.

When does Sentinel run?

At the transfer decision. Forge, Agora, Registry, Flux, and Quorum call it whenever a transfer is attempted.

How does Sentinel relate to the smart contract assessor?

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.

What happens when a transfer fails the rules?

It is blocked and does not settle. Only transfers that satisfy the rule set proceed.

References

  1. 1.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
  2. 2.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
  3. 3.World Wide Web Consortium, "Verifiable Credentials 2.0 is a W3C standard". https://www.w3.org/press-releases/2025/verifiable-credentials-2-0/

Last updated:

Ready to build on programmable infrastructure?

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