Skip to content
DAMREV
Start a Structuring Review

Trust centre

Independent Validation

DAMREV's smart contracts are assessed by a party that does not enforce them. A smart contract assessor assesses each contract and renders a signed attestation; Sentinel, DAMREV's compliance engine, acts on that verdict on-chain. The assessor renders the verdict, the enforcer acts on it, and no party holds both powers.

The problem

Why should a firm not validate its own smart contracts?

Because a party that holds both powers can pass its own work, and nothing in the process would show it. Splitting the powers means an attestation must come from one party before another will act, and each is accountable for its own half.

  • What the control isA separate assessmentAn assessment of each smart contract by a separate entity, recorded as a signed attestation, before the contract is relied on.
  • Who performs itTwo parties, two powersA smart contract assessor assesses and attests. Sentinel enforces. The assessor does not enforce, mint, sign or settle, and Sentinel does not assess its own rules.
  • Where it is recordedOn the programme recordThe signed attestation is kept on the programme record with the contract it covers and the decisions that relied on it.
  • What it answersThe same lawThe expectation that a tokenized security is held to the same law as any other1, and the governing rule of the platform: the assessor and the enforcer are never the same party.
  • On StellarEnforced quickly and faithfullyOn Stellar, Soroban smart contracts have run natively on the same ledger as the assets since February 20242, and a ledger closes with finality roughly every five seconds3. An error in a contract is therefore enforced quickly and faithfully.
  • Smart contractsThe check comes firstA smart contract is where a programme's rules stop being words and start being enforced. The check has to come first, and it has to come from someone who did not write the code.

How it works

How does validation run from assessment to enforcement?

In steps, each held by a different party. A smart contract assessor assesses the contract, the assessor signs an attestation, Sentinel enforces the verdict on-chain at each transfer, and the result joins the programme record.

  1. Assess

    The assessor assesses the smart contract that carries the programme's rules.

  2. Attest

    The assessor renders a signed attestation of its assessment.

  3. Enforce

    Sentinel acts on the verdict on-chain, applying the rules at each transfer.

  4. Record

    The attestation and the decisions that relied on it join the programme record.

The related-party relationship

The assessor and DAMREV share common ownership. The separation of powers holds because the assessor only assesses and attests and Sentinel only enforces, not because the two are unrelated. The conflicts page sets out how this and the group's other relationships are handled.

Disclosure

How independent is the smart contract assessor from DAMREV?

The smart contract assessor is a separate entity with its own role, set up as a validator for tokenized finance, with DAMREV as its first client. The two share common ownership, so the relationship is disclosed as related-party, and a reader should weigh each attestation with that disclosure in mind.

Follow one contract. The assessor assesses, then The assessor attests, then Sentinel enforces, then The programme record. Choose a case and follow one contract through the two powers.
  • Follow one contract
  • The assessor assesses: The assessor assesses the smart contract that carries the programme's rules.
  • The assessor attests: The assessor renders a signed attestation of its assessment.
  • Sentinel enforces: Sentinel acts on the verdict on-chain, applying the rules at each transfer.
  • The programme record: The attestation and the decisions that relied on it join the programme record.
Follow one contract. The assessor assesses, then The assessor attests, then Sentinel enforces, then The programme record. Choose a case and follow one contract through the two powers.

Choose a case and follow one contract through the two powers.

Evidence

What is recorded at each point of validation?

Enough for a reader to confirm who assessed what, and what was enforced as a result.

  1. 01

    The smart contract assessed, identified by the programme it serves.
  2. 02

    The signed attestation a smart contract assessor rendered on it.
  3. 03

    The approval, under four eyes or six eyes, to rely on the attested contract.
  4. 04

    The rules Sentinel enforces, and the date from which it enforces them.
  5. 05

    Each transfer decision Sentinel returns, allowed or blocked.

On request

Which validation documents can I ask for?

Name the programme and your role when you ask. Each box opens the contact page for that request.

Common questions

What else do people ask?

Short answers on validation: whether DAMREV validates its own smart contracts, whether a smart contract assessor can change a contract or stop a transfer, why the assessor is disclosed as a related party, and where enforcement actually happens.

Does DAMREV validate its own smart contracts?

A smart contract assessor, a separate entity, assesses them and renders a signed attestation. Sentinel then enforces on-chain. DAMREV's platform enforces; it does not mark its own work.

Can the assessor change a contract or stop a transfer?

The assessor assesses and attests only. It does not enforce, mint, sign or settle. Enforcement is Sentinel's function.

Why disclose the assessor as a related party?

Because the two share common ownership. The disclosure lets a reader weigh the attestation with that relationship in view, and the separation of powers is kept in the functions each party performs.

Where does enforcement actually happen?

On-chain. Sentinel applies the transfer rules in contract logic on Stellar and Soroban at the moment of each transfer, reading eligibility from Veritas.

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