Skip to content
DAMREV
Start a Structuring Review

Named engine · Identity, compliance and security layer

Sentry

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

What does Sentry do?

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.

  • Hardware-bound keysSigning relies on the secure enclave or StrongBox inside the user's phone.
  • User approvalNothing is signed until the user approves on their own device.
  • One signer, many enginesThe same device-bound signature serves issuance, swaps, sales, ramps, and votes.

How it works

How does Sentry work, step by step?

Three steps, each with one job.

  1. Step one

    Binds to the device

    Signing is tied to the device's secure enclave or StrongBox hardware.

  2. Step two

    Authorises on-device

    The user approves on their device, and the signature is produced there.

  3. Step three

    Pairs with Vault

    Keys stay with Vault, so signing never leaves the user's control.

Where it fits

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

Sentry sits in the identity, compliance, and security layer. Two engines supply it, and five call on it for signatures.

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

Which standards and networks does Sentry work with?

  • Secure enclave and StrongBoxThese are the hardware-backed key stores on mobile devices: the secure enclave on Apple devices and StrongBox on Android. Keys held there are designed not to leave the hardware.
  • StellarSignatures from Sentry authorise transactions on Stellar, where a ledger closes roughly every five seconds and finality comes at close1. Once signed and closed, a transaction stands.

Controls

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

Sentry enforces

Sentry enforces user authorisation: no engine obtains a signature unless the user approves it on their own device's secure hardware.

Sentry never

  • Holds or exports keys
  • Signs in place of the user
  • Performs identity checks, which stay with the licensed provider

Common questions

What do people ask about Sentry?

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

Where are transactions signed?

On the user's device. Sentry binds signing to secure hardware, so authorisation happens locally.

Does DAMREV hold my keys?

The user holds the keys and authorises each transaction on their own device. Sentry is non-custodial.

Which engines use Sentry?

Any engine that needs a user signature, including Forge, Flux, Agora, Conduit, and Quorum.

What hardware does Sentry use?

The device's secure enclave or StrongBox, the hardware-backed key storage built into current phones.

Can an agent sign for me?

Praxis routes agent actions through Sentry, so a signature still needs the user's approval on their device.

What happens if a user loses 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.

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.