Holds keys with the user
Vault is non-custodial, and the keys belong to the user rather than DAMREV.
Named engine · Application and operations layer
A wallet where the user holds the keys.
Vault is the wallet where users keep tokenized assets and, if they choose, their Veritas credentials, under keys only they hold. It pairs with Sentry so every transaction is signed on the user's device, and with Conduit so funds can arrive from a licensed on-ramp. Flux, Conduit, and Quorum rely on it. DAMREV never holds the keys.
What it does
Vault is the non-custodial wallet engine: the user holds the keys. It holds assets and may hold Veritas credentials, pairing with Sentry for device-bound signing and Conduit for ramps. It is non-custodial throughout. The recovery model is an open build item, so the page describes no recovery service that would imply custody.
How it works
Three steps, each with one job.
Vault is non-custodial, and the keys belong to the user rather than DAMREV.
Tokenized assets sit in Vault, alongside the holder's Veritas credentials where chosen.
Sentry signs for Vault, and Conduit connects it to on-ramps.
Where it fits
Vault sits in the application and operations layer as the holder's own store of assets. It depends on two engines, and three depend on it.
A wallet where the user holds the keys.
Depends on (2)
Veritas supplies the credentials a holder may choose to keep in the wallet. Sentry supplies device-bound signing, so the keys in Vault are used only with the user's approval on their own device.
Flux is designed to rely on Vault for custody: a swap from USDC to $DREV would leave the keys where they are. Conduit delivers the settlement asset into Vault from the licensed on-ramp. Quorum is designed to rely on Vault when a holder stakes $DREV, so staking would never move keys away from the user.
Standards and integrations
Controls
Vault enforces user control: nothing leaves the wallet without the user's signature through Sentry.
Common questions
Short answers to the questions people ask most about this topic.
The user does. Vault is non-custodial, so the keys to the user's assets stay with the user throughout.
The recovery model is an open build item. Vault describes no recovery service, because one could imply custody.
Tokenized assets and, optionally, the holder's Veritas credentials, with signing via Sentry.
Through Conduit. A user brings fiat in through the licensed provider, and Conduit delivers the settlement asset to Vault.
Yes, by design. If a holder stakes $DREV through Quorum once $DREV exists, the keys would stay in Vault and the user would sign through Sentry.
Yes. Stellar gives issuers authorisation flags and clawback1, so an asset carries its issuer's controls into the wallet.
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.