Verification by the provider
Identity and accredited checks are performed by the identity verification provider, not by DAMREV.
Named engine · Identity, compliance and security layer
Self-sovereign identity and verifiable credentials.
Veritas is the platform's root of trust for identity. A licensed provider performs the know-your-customer (KYC) and accredited checks, and Veritas turns the result into reusable verifiable credentials that the holder stores and controls. Nine engines read identity from those credentials instead of repeating checks. Veritas is aligned with W3C Verifiable Credentials, never certified against it.
What it does
Veritas is the platform's identity engine and root of trust. It integrates a licensed identity provider for checks, then issues reusable verifiable credentials that the holder controls. Other engines read identity from Veritas at the point they need it. It is aligned with the World Wide Web Consortium (W3C) Verifiable Credentials data model.
How it works
Three steps, each with one job.
Identity and accredited checks are performed by the identity verification provider, not by DAMREV.
Veritas issues reusable credentials, aligned with the W3C model, which the holder stores and controls.
Engines that need identity read a credential from Veritas instead of re-running a check.
Where it fits
Veritas sits in the identity, compliance, and security layer and is a root engine: it depends on no other engine, and nine engines read from it.
Identity and verifiable credentials.
Depends on (0)
Used by (9)
Sentinel takes eligibility for every transfer decision, and Sentry ties device signing to a verified party. Stratum takes identity to attach roles and access, and Registry takes it so that each entry on the register of holders belongs to a verified holder.
Portal takes identity and accredited context before showing disclosure, and Agora takes it to gate listings. Conduit reads it on the ramp, Vault can hold the holder's credentials, and Lyceum issues its Academy credentials through Veritas. Forge, Cadence, Quorum, Equilibrium, and Praxis also draw on Veritas in their own work.
Standards and integrations
Controls
Veritas enforces one source of identity: engines read the holder's credential rather than keeping their own copies of personal checks.
Common questions
Short answers on Veritas: who performs the identity checks, who controls the credentials, whether Veritas is standards-certified, why credentials are reused, and which engines rely on it.
The identity verification provider performs them. DAMREV Labs, LLC provides the software that integrates the check and issues the result.
The holder. Veritas issues reusable credentials, aligned with the W3C model, that the holder stores and presents.
Veritas is built to the model of the named standards and aligned with them. It is not certified or compliant.
A check done once can serve every engine, so holders are not asked to repeat it for each transaction.
Nine list it directly: Stratum, Sentinel, Sentry, Portal, Registry, Agora, Conduit, Lyceum, and Vault.
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.