Tenant zero
DAMREV's own operations sit in the first tenant in Stratum, before any client is onboarded.
Why DAMREV
DAMREV runs its own operations on the platform it offers. Stratum, the operating core, serves as tenant zero, so DAMREV's own roles, access and approvals pass through the same engines and controls a client's would, and each version of the DAMREV Standard is proved on DAMREV's own programmes before any client is asked to adopt it.
The control
The control is simple: DAMREV is bound by the controls it sells. Its own operations occupy the first tenant in Stratum, and faults are found on DAMREV's programmes before they reach a client's.
How it works
A tenant is an isolated space for one client's data and configuration, and DAMREV's own operations occupy the first one.
DAMREV's own operations sit in the first tenant in Stratum, before any client is onboarded.
DAMREV's staff work inside the role and approval model a client's staff use.
Veritas and Sentinel serve DAMREV's operations exactly as they serve a client's.
Reserve manages DAMREV's own treasury, not customer funds, and reports into the other engines.
Each version of the DAMREV Standard runs on DAMREV's own programmes first.
Only then is the version offered to clients, with the evidence that shaped it.
The base network
Because Stellar already carries regulated records and gives the issuer control at the base layer. Franklin Templeton's Franklin OnChain U.S. Government Money Fund launched on Stellar in April 2021, the first US-registered money market fund to use a public blockchain as its official system of record1.
Stellar launched publicly on 31 July 2014 and runs the Stellar Consensus Protocol2. For DAMREV the practical points are finality, issuer control and contract logic on one ledger: Sentinel enforces transfer rules in Soroban contract logic, and Registry records servicing actions on the same chain.
Evidence
The same evidence a client's programme leaves, because the record is the same record. Each item below is kept for DAMREV's own tenant, and each can be discussed with a counterparty in due diligence.
What it shows
It shows that DAMREV is prepared to be bound by the controls it sells, and that faults surface on DAMREV's operations first. It does not by itself show that a given capability is deployed: deployment status is recorded separately from the roadmap, in capability status.
Common questions
Short answers on DAMREV's own use of its platform: whether it uses the same engines as its clients, whether Reserve holds customer funds, why Stellar, and whether every engine is deployed.
Yes. DAMREV's operations sit in tenant zero in Stratum and reach identity, compliance and treasury through the same engines a client uses.
No. Reserve manages DAMREV's own treasury, not customer funds, and it is non-custodial with respect to user funds.
Stellar offers finality when a ledger closes, issuer controls such as authorisation flags and clawback, and Soroban contracts on the same ledger2. A US-registered money market fund already uses it as its official system of record1.
It means DAMREV relies on what it has deployed. Which capabilities are deployed is recorded in capability status, separately from the roadmap.
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.