Skip to content
DAMREV
Start a Structuring Review

Named engine · Identity, compliance and security layer

Veritas

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

What does Veritas do?

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.

  • Checked once, reusedA provider check becomes a credential that every engine can read.
  • Holder-controlled credentialsThe holder stores and presents credentials and decides when to share them.
  • Issuers anchored on StellarCredential issuers are anchored on Stellar, so a credential's source can be checked.

How it works

How does Veritas work, step by step?

Three steps, each with one job.

  1. Step one

    Verification by the provider

    Identity and accredited checks are performed by the identity verification provider, not by DAMREV.

  2. Step two

    Issues held credentials

    Veritas issues reusable credentials, aligned with the W3C model, which the holder stores and controls.

  3. Step three

    Serves the platform

    Engines that need identity read a credential from Veritas instead of re-running a check.

Where it fits

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

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.

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

Which standards and networks does Veritas work with?

  • W3C Verifiable Credentials 2.0The World Wide Web Consortium published Verifiable Credentials 2.0 as a Recommendation on 15 May 2025: a standard way to express digital credentials that are cryptographically secure, privacy respecting, and machine-verifiable1. Veritas aligns with it.
  • StellarCredential issuers are anchored on Stellar, a public network running since 31 July 2014 on the Stellar Consensus Protocol2.
  • Aligned frameworksVeritas is also aligned with OpenID for Verifiable Credentials, ISO/IEC 18013-5, and eIDAS 2.0, for credential exchange, mobile identity documents, and European Union electronic identification. It is never certified against them.

Controls

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

Veritas enforces

Veritas enforces one source of identity: engines read the holder's credential rather than keeping their own copies of personal checks.

Veritas never

  • Performs identity or accredited checks itself, which is the licensed provider's work
  • Takes control of a holder's credentials
  • Claims certification against the standards it aligns with

Common questions

What do people ask about Veritas?

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.

Who performs the identity checks?

The identity verification provider performs them. DAMREV Labs, LLC provides the software that integrates the check and issues the result.

Who controls the credentials?

The holder. Veritas issues reusable credentials, aligned with the W3C model, that the holder stores and presents.

Is Veritas standards-certified?

Veritas is built to the model of the named standards and aligned with them. It is not certified or compliant.

Why reuse credentials?

A check done once can serve every engine, so holders are not asked to repeat it for each transaction.

Which engines rely on Veritas?

Nine list it directly: Stratum, Sentinel, Sentry, Portal, Registry, Agora, Conduit, Lyceum, and Vault.

References

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