Platform
Platform
The DAMREV platform is twenty engines arranged in five architecture layers, from settlement at the base to the applications people use. Each engine performs one defined function and reads what it needs from the others. A client can run a whole programme on it, or connect only the engines its own systems lack.
Capabilities
Which part of the platform answers your question?
Eight explainers follow one capability across every engine it touches. Start with how it works for the whole sequence, or go straight to the control that matters to you: who may hold an instrument, how it is issued, how value settles, or where the register is kept.
- How It WorksFollow one programme from the asset and the claim to servicing for life, across five architecture layers and twenty engines that hand off in a stated order.
- Identity & EligibilityA licensed provider verifies each holder once, Veritas issues a reusable credential the holder controls, and Sentinel reads it every time an instrument changes hands.
- Issuance & Transfer ControlForge mints only after Veritas and Sentinel clear eligibility and Beacon's circuit-breaker allows it, Cadence releases on schedule, and Sentinel checks every transfer on-chain.
- Settlement & LiquidityValue settles in the asset each jurisdiction permits, with fiat entering through a licensed provider, swaps routed by Flux without custody, and the user holding the keys throughout.
- The Securities RegisterRegistry keeps the authoritative register of holders for each issued asset, performs the transfer-agent function as software, and handles corporate actions for the instrument's life.
- Roles & ResponsibilitiesEvery function has a named owner: DAMREV Labs builds the software, the issuer sets the rules, a smart contract assessor assesses smart contracts, and Sentinel enforces them on-chain.
- Structured ProbabilitiesHow the platform treats inputs that are not settled facts: readings enter through Beacon, views carry human verification, and a doubtful reading can halt a mint.
- Device SecuritySentry binds signing to the secure hardware of the user's own device, Vault keeps the keys with the user, and DAMREV cannot sign on anyone's behalf.
The five layers
How are the twenty engines organised?
By architecture layer. Settlement moves value; financial infrastructure issues, releases, prices and services the instrument; identity, compliance and security decides who may act; the token economy carries governance and modelling; application and operations presents the platform to the people who use it. Select an engine to see what it does, what it depends on and what uses it.
Application and operations
Token economy
Identity, compliance and security
Financial infrastructure
Settlement
Stellar ledger, with Soroban contract logicFinal at ledger close
- Selected
- Depends on
- Used by
How to choose
Where should you start?
With the question you have to answer. Counsel usually begins with eligibility and transfer rules, an operations team with the register and servicing, and a technology team with the architecture and the hand-offs between engines.
- Your questionWho may hold and receive the instrument?VeritasSentinel
- Your questionHow is the instrument created and released?ForgeCadenceBeacon
- Your questionHow does value move, and who holds it?ConduitFluxAgoraReserve
- Your questionWhere is ownership recorded?RegistryPortal
- Your questionWho signs, and on what device?SentryVault
- Your questionHow does it all fit together?All twenty
The base
What does the platform run on?
On Stellar, a public network that closes a ledger roughly every five seconds with finality at close, and lets any account issue an asset natively with issuer controls such as authorisation flags and clawback1. Soroban runs the contract logic on the same ledger2.
The model is proven there: a US-registered money market fund has used Stellar as its official system of record since 20213.
Position paper
Where does DAMREV stand?
Each position paper takes one question and sets out the evidence and the positions DAMREV holds on it. Each is read through the same steps as a whitepaper.
- Position paperNew
AI Agents & Tokenized Assets
Platform, 16 November 2026Who gives an AI agent authority over a tokenized asset, how an account contract enforces its limits, how its transactions settle, and who bears a loss. - Position paperNew
Agentic AI in Trading Tokenized Instruments
Listing Preparation, 16 November 2026What an AI agent may do when it trades tokenized instruments: limits checked before each order, independent stops, a decision record and market abuse rules. - Position paperNew
Governing AI in Regulated Financial Infrastructure
Compliance, 16 November 2026What the law already requires when a regulated financial firm uses AI, what the EU AI Act and ISO/IEC 42001 add, and the practice the group holds itself to. - Position paperNew
AI in Compliance Monitoring for Tokenized Instruments
Compliance, 16 November 2026Where on-chain rules end and AI monitoring begins in AML, KYC and transaction monitoring for tokenized instruments, and why a named person decides.
Common questions
What else do people ask?
Short answers to the questions people ask most about this topic.
Can we use some engines and not others?
Yes. DAMREV can serve as the whole programme stack, or connect selected engines into an existing architecture, so a counterparty keeps its own permissions, systems and operating boundaries.
Who holds the keys and the assets?
The user holds the keys in Vault, and signing happens on the user's own device through Sentry. DAMREV is non-custodial and holds no customer funds; institutions integrate their own qualified custody.
How do transfers stay compliant?
Sentinel reads eligibility from Veritas at the moment of each transfer and applies the rules the issuer set, on-chain. A transfer that fails the rules does not settle.
Is every engine live today?
Deployment is recorded separately from the roadmap, in capability status, and no page marks an engine live until a verified record exists for it.
Where next
Where should you go next?
The pages below pick up where this one ends. Start with the one closest to where your asset or programme stands today.
- How It WorksThe five stages every programme follows, the five architecture layers, and how twenty engines hand off so each control has a named owner.
- Technical ArchitectureThe engineer's view: five architecture layers on Stellar, Soroban contract logic in Rust, twenty engines, and every named integration and standard.
- Security & ControlsWho holds the keys, how signing is bound to the user's device, who performs identity checks, and why DAMREV holds no client assets.
- ImplementationBringing a designed programme live: encoding rights, eligibility, and transfer controls, gating issuance, and opening the register of holders on Stellar.
References
- 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
- 2.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
- 3.Stellar Development Foundation, Franklin Templeton case study. https://stellar.org/case-studies/franklin-templeton
Last updated:






