How it works
VTE uses one mechanism across four situations and four modes. It answers one narrow question about a private position on Canton DevNet and records the outcome with its references. In this demo's VTE Match ledger flow, the raw value is not recorded.
Quick check: the main mode plus an optional second check, about 2 min. Full case: all four modes, 3 to 4 min. You can also choose which modes to run.
Who takes part
1. Relying party
Writes the request and its terms, and decides whether to rely on the answer.
2. Subject
Sees exactly what is asked, enters its own figures, and accepts or declines.
3. Source
Provides the declared figures with its own key in the modes that use a source. In VTE Match the issuer party confirms the tier.
In this demo our team operates every party, including the only source and governance.
Where it runs
Canton ledger
The Daml templates record the outcome. The default composition checks shared scope and metadata; it does not establish that declared values are true. In this demo's VTE Match ledger flow, the raw value is not recorded.
Who else can read
Governance
The governance parties of the ledger. What they can read depends on the mode: the values in VTE Policy and VTE Trade Check, a random split and the total in VTE Reveal, no value in VTE Match.
The flow of a request
Pick a step to see who acts and what is signed.
Step 1 of 4
Ask
Request with terms. Required figures, freshness and validity.
- Who acts
- Relying party
- What is signed or recorded
- The request lives in the memory of the demo service. It is not a contract on the ledger.
Step 2 of 4
Consent
Consent by the subject. The subject sees exactly what is asked, enters its own figures, and accepts or declines.
- Who acts
- Subject
- What is signed or recorded
- The demo uses team-operated parties and synthetic data. The available evidence does not establish a full four-mode run with two real Loop wallets. Ledger commands are sent by demonstration parties, not by the wallet.
Step 3 of 4
Answer
The selected ceremony runs on the ledger. The default composition checks shared scope and metadata, not cross-mode values.
- Who acts
- The service
- What is signed or recorded
- The ledger steps are signed by the service’s demonstration parties.
Step 4 of 4
Evidence
Bounded package to the relying party. Decision, confidence level, freshness, validity and ledger references, plus only what the mode returns (see the table below). No whole-book disclosure in this package.
- Who acts
- Relying party
- What is signed or recorded
- The service delivers the package.
The four modes in detail
| Mode and question | The asking party sees | Governance sees the values |
|---|---|---|
| VTE RevealWhat do these holdings add up to? | Exact total and met or not met | A random split and the total |
| VTE PolicyDoes the mix by category reach the required amount? | Total, category breakdown and met or not met | Yes |
| VTE Trade CheckIs there enough behind this trade to proceed? | Only the VTE Trade Check answer (its fact and evidence statement) is intended to be readable by the counterparty on the configured ledger today. Supporting contracts can have separate visibility under the configured party topology. The service package carries no value or digest. | Yes |
| VTE MatchDoes the position reach the minimum? | Band and lower bound, not the underlying value in this package. | No |
In this demo's VTE Match ledger flow, the raw value is not recorded; the ledger records one yes-or-no fact and the demo service names the band. For VTE Reveal the requesting party receives only the total; in this demo, governance sees only a random split of the total and the total. The service's governance parties can see the values in VTE Policy and VTE Trade Check. The ledger record the counterparty is intended to read carries the floor, the window and a salted digest of the value, not the underlying value in this package. The demo service stores the values it receives; there is no cryptographic hiding.
Three possible answers
Every answer carries one of three labels. Condition met: the declared figures meet the condition. Condition not met: they do not. Insufficient evidence: the ledger recorded no evidence statement for this part, so there is no determination either way. Each answer also carries a validity window. The labels describe the declared figures and the recorded check. They do not say whether a figure is true. In the internal DevNet runs, every condition was met.
Composing the modes
The four modes can run on one case and be composed into a single cross-checked package. The cross-check is coherence between the declared statements: same subject, scope, epoch, governance and book. It is not a check that the data is true.
What the ledger adds
Each refusal is shown with the participant’s own error.
Disagreement
In the Trade Check ceremony, the ledger refuses a submission when the subject and the source disagree.
Source never onboarded
In the Trade Check ceremony, it refuses when the source was never onboarded.
Source revoked
In the Trade Check ceremony, it refuses when the source has been revoked.
Replay
In the Trade Check ceremony, it refuses when a command already committed is replayed (within the participant’s deduplication window).
After the answer
Revalidation receipt
A revalidation receipt, with a validity window applied by the service.
Reliance decision
Reliance is a separate action with its own button and endpoint, outside the four-mode case. The service records it on the ledger on behalf of a demonstration party operated by the team. The client wallet does not sign this decision.