Binds to the device
Signing is tied to the device's secure enclave or StrongBox hardware.
Named engine · Identity, compliance and security layer
Device-bound signing the user controls.
Sentry puts the final say on every transaction in the user's hand. It binds signing to the secure hardware inside the user's mobile device, so a signature can only be produced there, and it pairs with Vault for keys and Veritas for identity. Forge, Flux, Agora, Conduit, and Quorum rely on it. DAMREV never holds the keys.
What it does
Sentry is a mobile, device-bound transaction signer. It binds signing to the device's secure hardware, so a transaction is authorised on the user's own device. It pairs with Vault for keys and reads identity from Veritas. It is non-custodial: the user authorises, and DAMREV does not hold the keys.
How it works
Three steps, each with one job.
Signing is tied to the device's secure enclave or StrongBox hardware.
Keys stay with Vault, so signing never leaves the user's control.
Where it fits
Sentry sits in the identity, compliance, and security layer. Two engines supply it, and five call on it for signatures.
Device-bound signing the user controls.
Depends on (2)
Veritas supplies identity, so the signer on the device is tied to a verified party. Vault supplies the keys: the non-custodial wallet holds them with the user, and Sentry is how those keys are put to use.
Forge calls Sentry where issuance needs a user's authorisation. Flux uses it to sign a swap, Agora a sale, Conduit a ramp transaction, and Quorum a stake or a vote. Praxis routes agent actions through it too, so an agent cannot sign in the user's place.
Standards and integrations
Controls
Sentry enforces user authorisation: no engine obtains a signature unless the user approves it on their own device's secure hardware.
Common questions
Short answers to the questions people ask most about this topic.
On the user's device. Sentry binds signing to secure hardware, so authorisation happens locally.
The user holds the keys and authorises each transaction on their own device. Sentry is non-custodial.
Any engine that needs a user signature, including Forge, Flux, Agora, Conduit, and Quorum.
The device's secure enclave or StrongBox, the hardware-backed key storage built into current phones.
Praxis routes agent actions through Sentry, so a signature still needs the user's approval on their device.
Keys belong with Vault, whose recovery model is an open build item. No recovery service is described while that item remains open, because one could imply custody.
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.