Canton DevNet - synthetic data

Check a borrower's covenant without seeing the portfolio.

VTE answers one narrow question about a private position on Canton DevNet, and records the outcome and its references on the ledger. In VTE Match, no figure reaches it.

Run the DevNet check (about 2 min)

or follow every step on the flows page

Three possible answers: condition met, condition not met, insufficient evidence.

Four modes

The four modes in detail
VTE Reveal

What do these holdings add up to?

Exact total and pass or fail

Governance sees: a random split and the total VTE Policy

What is the total made of?

Total, category breakdown and pass or fail

Governance sees: the values VTE Trade Check

Is there enough behind this trade to proceed?

Pass or fail against the required minimum

Governance sees: the values VTE Match

Does the position reach the minimum?

Whether the position clears the minimum

Governance sees: one yes-or-no fact only; the value never reaches the ledger

Four steps

How it works
  1. 01

    Ask

    The relying party sets the threshold, categories, freshness and validity window.

    Relying party
  2. 02

    Consent

    The holder sees what is asked and what the other side will not see, then accepts or declines.

    Holder
  3. 03

    Answer

    The selected mode records its bounded answer; where a mode uses a source, that source attests, while Match uses the issuer party for the binary tier. The default composition checks shared scope and metadata; it does not establish that declared values are true.

    Source and ledger
  4. 04

    Evidence

    The relying party gets a bounded package.

    Relying party

Four situations

Use cases
01

Private credit, warehouse covenant

Does the collateral reach the minimum the covenant requires?

VTE Match 02

Tokenized collateral in DeFi lending

Does the position reach the required minimum?

VTE Match 03

OTC block trade

Is there enough behind this trade to proceed?

VTE Trade Check 04

Holder condition before an issue, transfer or mint

Does the holder’s sum across custodians reach the issuer’s minimum subscription?

VTE Reveal
Why on-ledger

Not a signed letter

Refused

In the Trade Check ceremony, the ledger refuses an answer from a source that was never onboarded or has been revoked, or one whose value disagrees with the subject's committed book.

Shown in recorded DevNet runs (5 October)
Refused

A combined package is refused if its parts disagree on subject, scope, epoch, governance or book. This checks scope and metadata, not that the values agree.

Recorded

After a full case, a reliance decision is recorded on the ledger. By design only the relying party signs it; in this demo a demonstration party submits it.

BoundaryVTE records what was declared and checks scope and metadata coherence. Strict mode can compare selected declared values; this default demo does not. It does not determine that a declared value is true. Every party in this demo is operated by our team, and the demo service keeps the figures entered. What VTE does and does not do

We are looking for a source and a relying party that we do not operate.[email protected]