Skip to content
DAMREV
Start a Structuring Review

Named engine · Application and operations layer

Vault

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

What does Vault do?

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.

  • Keys stay with the userOnly the user can move what Vault holds.
  • Assets and credentials togetherTokenized assets and Veritas credentials can sit in one wallet.
  • Ramp-connectedThe settlement asset from Conduit's licensed on-ramp arrives directly in Vault.

How it works

How does Vault work, step by step?

Three steps, each with one job.

  1. Step one

    Holds keys with the user

    Vault is non-custodial, and the keys belong to the user rather than DAMREV.

  2. Step two

    Holds assets and credentials

    Tokenized assets sit in Vault, alongside the holder's Veritas credentials where chosen.

  3. Step three

    Pairs for signing and ramps

    Sentry signs for Vault, and Conduit connects it to on-ramps.

Where it fits

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

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.

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

Which standards and networks does Vault work with?

  • StellarAssets in Vault are Stellar assets, and Stellar lets their issuers set authorisation flags and use clawback1. An asset keeps its issuer's rules even while it sits in a wallet the user controls.
  • Non-custodial modelThe user, not DAMREV, holds the keys. Recovery is an open build item, and no recovery service is described while it remains open.

Controls

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

Vault enforces

Vault enforces user control: nothing leaves the wallet without the user's signature through Sentry.

Vault never

  • Gives DAMREV the keys
  • Offers a recovery service that would imply custody
  • Moves assets on anyone else's instruction

Common questions

What do people ask about Vault?

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

Who holds the keys?

The user does. Vault is non-custodial, so the keys to the user's assets stay with the user throughout.

Does Vault offer recovery?

The recovery model is an open build item. Vault describes no recovery service, because one could imply custody.

What does Vault hold?

Tokenized assets and, optionally, the holder's Veritas credentials, with signing via Sentry.

How do funds reach Vault?

Through Conduit. A user brings fiat in through the licensed provider, and Conduit delivers the settlement asset to Vault.

Would Vault work with staking?

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.

Can an issuer's rules still apply to an asset in Vault?

Yes. Stellar gives issuers authorisation flags and clawback1, so an asset carries its issuer's controls into the wallet.

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

Last updated:

Ready to build on programmable infrastructure?

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