Skip to content
DAMREV
Start a Structuring Review

Trust centre

Evidence & Audit

DAMREV keeps every decision, input, encoded rule and approval attached to one programme record, so any event can be traced to the authority that allowed it. An auditor reads one record instead of assembling several parties' files. Access follows the roles held in Stratum, and personal data on the record is handled under the privacy policy.

The problem

Why is reconstructing a programme usually so hard?

Because its history is spread across the issuer, the administrator, the transfer agent and counsel, each keeping its own files. Reconciling them is a project. A single record that holds the decisions beside their effects turns it into a reading.

  • What the control isOne record, for lifeA record that keeps each decision, its inputs, the rules encoded as a result, and the approvals behind them, for the life of the instrument.
  • Who performs itEvery party namedThe platform keeps it for each programme. Assessors, approvers and reviewers are named on it; agents appear under the role they acted in.
  • Where it is recordedBeside the ledgerOn the programme record, with transfers and holdings on the settlement ledger. Stellar closes a ledger roughly every five seconds, with finality at close1.
  • What it answersAuthorised, and by whomThe auditor's question of whether each event was authorised, and by whom, whatever the format of the security2.
  • On the ledgerA chain as the record of ownershipPublic ledgers have already shown that a chain can serve as the official record of ownership. Franklin Templeton's Franklin OnChain U.S. Government Money Fund, launched on Stellar in April 2021, was the first US-registered money market fund to use a public blockchain as the official system of record for transactions and share ownership3.
  • On the programme recordWhat happened, and whyA ledger records what happened. DAMREV's programme record adds why it was allowed to happen.
  • AccessFollows the roles in StratumAccess follows the roles and permissions held in Stratum, the operating core, which feeds them to every engine.
  • Personal dataUnder the privacy policyPersonal data on the record is handled under the privacy policy and kept only as long as the purpose and the law require.
  • The DAMREV StandardDated and readableEvery release of the DAMREV Standard is dated. Superseded versions of the Standard stay readable, and the evidence that changed the method is recorded alongside each version.

How it works

How does an event reach the record?

Each step of a decision is attached to the record, from the inputs to the effect on the ledger. The sequence below follows one decision through.

  1. Inputs captured

    The information a decision will rest on is attached, as it stands at the time.

  2. Assessed

    An assessor drafts the assessment, and is named.

  3. Approved or reviewed

    A separate approver signs, and a reviewer is added where the decision requires one.

  4. Rule encoded

    Any rule that results is encoded, with the date from which it applies.

  5. Enforced and settled

    Sentinel applies the rule at each transfer, and the outcome settles on the ledger.

What this page does not set out

Which parties may read which parts of a programme record is set programme by programme and is not listed here. Ask for the access arrangements of a named programme through the contact page.

Tracing an event

Can any event be traced to the authority that allowed it?

Any event can be traced to the authority that allowed it. An auditor reads one record instead of assembling several parties' files.

Follow one event. Inputs captured, then Assessed, then Approved or reviewed, then Rule encoded, then Enforced and settled. Choose a case and follow one event onto the record.
  • Follow one event
  • Inputs captured: The information a decision will rest on is attached, as it stands at the time.
  • Assessed: An assessor drafts the assessment, and is named.
  • Approved or reviewed: A separate approver signs, and a reviewer is added where the decision requires one.
  • Rule encoded: Any rule that results is encoded, with the date from which it applies.
  • Enforced and settled: Sentinel applies the rule at each transfer, and the outcome settles on the ledger.
Follow one event. Inputs captured, then Assessed, then Approved or reviewed, then Rule encoded, then Enforced and settled. Choose a case and follow one event onto the record.

Choose a case and follow one event onto the record.

Evidence

What does the record hold at each point?

Each kind of entry, what it lets an auditor show, and where it comes from.

  1. 01

    Decisions: what was decided, at which stage, and under which approval path. From the approval paths set by four eyes and six eyes.
  2. 02

    Inputs: what the decision was based on, as it stood at the time. From the assessor, attached when the assessment is drafted.
  3. 03

    Encoded rules: the rule in force, and the date from which it applied. From the instrument, once the rule is approved.
  4. 04

    Approvals: who assessed, who approved and who reviewed. From the roles held in Stratum.
  5. 05

    Attestations: the independent assessment of each smart contract. From a smart contract assessor.
  6. 06

    Transfer decisions: each transfer allowed or blocked, and the eligibility read. From Sentinel, reading from Veritas.
  7. 07

    Standard version: the version of the method that governed the decision. From the dated releases of the DAMREV Standard.

On request

Which audit documents can I ask for?

Name the programme, the period and your role when you ask.

Common questions

What else do people ask?

Short answers on the record: whether an auditor can trace an on-chain event to its approval, how long the record is kept, whether a decision can be read against the method of its time, and how personal data on the record is protected.

Can an auditor trace an on-chain event back to its approval?

Yes. The operating instrument can always be traced back to the terms that authorised it, because each rule is recorded with the decision, inputs and approvals behind it.

How long is the record kept?

For the life of the instrument. DAMREV services the instrument for life, and each servicing event joins the same record.

Can a decision be read against the method that applied at the time?

Yes. The DAMREV Standard is versioned, every release is dated, and superseded versions stay readable, so a past decision is read against the version then in force.

How is personal data on the record protected?

Under the privacy policy: it is processed for stated purposes and legal bases, shared only with named categories of processor and with authorities where the law requires, and kept only as long as needed.

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
  2. 2.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
  3. 3.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.