Skip to content
DAMREV
Start a Structuring Review

How it works across the platform

How It Works

Every DAMREV programme runs the same five stages, from the asset and the claim to servicing for life, on a platform built in five architecture layers on the Stellar network. Twenty engines each perform one defined function and hand off to one another in a stated order, so every control has a named owner and a place on the record.

The problem

Why is the platform built as engines rather than one product?

Because institutions already have systems, permissions and counterparties that work. A single product adopted whole forces them to replace those in order to gain what they lack, and it hides which component performs which control.

  • One function per engineEach engine performs one defined function, so every control traces to the engine that performs it.
  • Stated dependenciesEach engine names the engines it depends on and the engines that consume it.
  • Adopt what you needA client takes the whole stack, or connects selected engines into its own architecture.

Tokenization changes how an instrument is recorded and moved. It does not change what the instrument is: three divisions of the Securities and Exchange Commission (SEC) stated in January 2026 that the format in which a security is issued does not affect the application of the federal securities laws1.

When a regulator or an auditor asks which component checked eligibility, which one minted, and which one kept the register, the answer on DAMREV is a named engine with a stated function.

The sequence

What sequence does every programme follow?

The same five stages, in the same order, for every asset class. The deal is made before anything is encoded, the instrument is encoded before anything is issued, and servicing runs for the life of the instrument.

  1. The asset and the claim

    What is financed, and what the investor holds a claim on, established before any technology is introduced.

    • Counsel
    • General partner
  2. The structure

    The vehicle, the ranking and the control framework, settled with counsel and the appointed regulated parties.

    • Counsel
    • Administrator
    • Custodian
  3. The instrument

    Rights, eligibility, transfer controls and servicing logic, encoded once and enforced from then on.

    • Sentinel
    • Assessor
  4. Issuance and the register

    Minting under the issuer's authority, and a register of holders kept from the first issue.

    • Veritas
    • Sentinel
    • Forge
    • Registry
    • Licensed provider
  5. Servicing for life

    Distributions, corporate actions and reporting, for as long as the instrument exists.

    • Cadence
    • Sentinel
    • Registry
    • Portal
The order matters because each stage consumes the output of the one before it. Every decision, input, encoded rule and approval stays on the programme record. The worked example is an illustrative feeder fund, not a client.

The layers and the hand-offs

What are the five layers, and how do the engines hand off?

Settlement at the base and application and operations at the top. Each engine belongs to exactly one layer and reads what it needs from another engine rather than sourcing it again. Select an engine to see what it depends on and what consumes it.

  1. Application and operations

  2. Token economy

  3. Identity, compliance and security

  4. Financial infrastructure

  5. Settlement

Stellar ledger, with Soroban contract logicFinal at ledger close

  • Selected
  • Depends on
  • Consumed by
  • FirstIdentityEvery other control needs to know who is acting. Veritas depends on no other engine.
  • SecondComplianceSentinel applies the asset's rules to that identity.
  • ThirdIssuanceForge mints only once both have cleared, and reads Beacon's circuit-breaker signal first.
  • ThenServicingRelease, servicing and reporting follow from what was issued.

The base

What does the platform settle on, and why Stellar?

Stellar closes a ledger roughly every five seconds with finality at close, and any account can issue an asset natively, with authorisation flags and clawback available to the issuer2. For a regulated instrument, final settlement and issuer-level controls are the properties that count.

  • Settlement networkStellarPublic since 31 July 2014, running the Stellar Consensus Protocol, with finality at ledger close2.
  • Contract logicSorobanLive on Stellar mainnet since February 2024 with Protocol 20, on the same ledger3. Transfer rules are enforced here, in Rust.
  • Settlement assetChosen per jurisdictionFrom what local rules permit. The group issues none of them.
  • External dataOracle networkDesigned to bring external price and reserve data on-chain, through Beacon.
The reference case on Stellar

Franklin Templeton's Franklin OnChain U.S. Government Money Fund launched on Stellar in April 2021, the first money market fund registered in the United States to use a public blockchain as the official system of record for transactions and share ownership4. DAMREV cites it as evidence of what the network can carry, not as a relationship.

A transfer

What happens when an instrument changes hands?

It passes through the engines in a fixed order. If the asset's rules are satisfied, the transfer settles on Stellar; if not, it is blocked before settlement. Nothing in the path depends on DAMREV holding the asset or the key.

Run the transfer. Sentry, then Veritas, then Sentinel, then Stellar, then Registry. Choose a holder and run the transfer.
  • Run the transfer
  • Sentry: The holder authorises on their own device, with keys held in Vault.
  • Veritas: Supplies the credential that shows eligibility.
  • Sentinel: Applies the asset's transfer rules on-chain.
  • Stellar: Settles the transfer, final at ledger close.
  • Registry: Maintains the register of holders.
Run the transfer. Sentry, then Veritas, then Sentinel, then Stellar, then Registry. Choose a holder and run the transfer.

Choose a holder and run the transfer.

The platform is non-custodial: the user holds the keys in Vault, and signing happens on the user's device. Because a Stellar ledger is final at close2, the control has to act before settlement rather than after it, which is why Sentinel's check sits in the contract logic of the transfer itself.

Integration

Can a client connect only some of the engines?

Yes. DAMREV can serve as the whole programme stack, or connect selected engines into an existing architecture. Where a programme already has a licensed identity provider, a qualified custodian or an appointed transfer agent, that party keeps its role.

  • White-label clientTakes the platform under its own brand, themed through Atelier, with functional configuration carried by Stratum.
  • API clientDrives the platform by integration through an application programming interface (API).
  • Platform userUses DAMREV's own platform, with personal settings within role and tenant limits.
  • TenantHolds an isolated space for one client's data and configuration, kept apart from every other tenant.

Illustration: a programme adds issuance and the register. Forge and Registry join, and bring Veritas and Sentinel because they depend on them. Each engine that joins brings the engines it depends on, and nothing else.

  • Keeps its identity provider
  • Keeps its qualified custodian
  • Keeps its transfer agent
  • Keeps its administrator
  • Veritas (in the programme)
  • Sentinel (in the programme)
  • Sentry
  • Forge (in the programme)
  • Cadence
  • Registry (in the programme)
  • Beacon
  • Agora
  • Flux
  • Anchor
  • Reserve
  • Conduit
  • Equilibrium
  • Quorum
  • Stratum
  • Portal
  • Vault
  • Praxis
  • Atelier
  • Lyceum

Responsibility

Who keeps the regulated functions?

The parties appointed to hold them, with permissions held entity by entity.

The assessor assesses

A related party through common ownership, it assesses each smart contract and renders a signed attestation.

No party holds both powers

Sentinel enforces

Acts on that verdict on-chain, in the contract logic of every transfer.

What the platform company does not do

DAMREV does not issue securities, act as general partner, manage funds or give investment advice. It is not a party to any transaction, holds no client assets, effects no trades and introduces no parties to one another.

Common questions

What else do people ask?

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

Which network does DAMREV settle on?

Stellar, with Soroban running the contract logic on the same ledger3. Settlement runs in the asset each jurisdiction permits, such as USDC, EURC, a licensed local stablecoin, tokenized deposits, or fiat through a bank. The group issues none of them.

Must a client use all twenty engines?

No. DAMREV can serve as the whole programme stack or connect selected engines into an existing architecture. The dependencies each engine states show which engines travel together: Forge, for example, depends on Veritas and Sentinel.

Is every engine deployed today?

Deployment is recorded engine by engine in capability status records, kept apart from the roadmap. Those records are being prepared, so this page describes how the platform is designed to work and marks no capability as live.

Does DAMREV hold client assets or keys?

The platform is non-custodial. The user holds the keys in Vault and signs on their own device through Sentry. DAMREV holds no client assets, and institutions integrate their own qualified custody.

Why are engines grouped by layer here and by family elsewhere?

Layers describe how the platform is built, which is what engineers, auditors and counsel need. Families group the same twenty engines by what a buyer is trying to do. The engines and their functions are the same in both views.

How do the programme sequence and the layers relate?

The sequence is the order in which a programme is built and run. The layers are where each function sits in the platform. Every stage of the sequence draws on engines from several layers.

How can a reviewer see what was agreed?

Through the programme record. Every decision, input, encoded rule and approval stays attached to it, so the operating instrument can be traced back to the terms that authorised it.

Where next

The pages below pick up where this one ends. Start with the one closest to where your asset or programme stands today.

References

  1. 1.US Securities and Exchange Commission, Statement on Tokenized Securities, 28 January 2026. https://www.sec.gov/newsroom/speeches-statements/corp-fin-statement-tokenized-securities-012826-statement-tokenized-securities
  2. 2.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
  3. 3.Stellar Development Foundation, "Protocol 20 and smart contracts are live on Mainnet". https://stellar.org/blog/developers/protocol-20-and-smart-contracts-are-live-on-mainnet
  4. 4.Stellar Development Foundation, Franklin Templeton case study. https://stellar.org/case-studies/franklin-templeton

Last updated:

Ready to build on programmable infrastructure?

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