What VTE does and does not do

Every statement on this site has a boundary. This page lists them in one place.

Real in this build

The Daml templates run on a Canton participant connected to DevNet. Internal DevNet runs of 5 October covered four situations on our own participant. 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.

Simulated in this build

Every party and every source is operated by our team. The data is synthetic. The only source is a labelled demonstration source, so every package says consistency only. This is not a pilot and no customer has used VTE.

What VTE records

VTE records what was declared and checks coherence of scope and metadata. It detects disagreement in those checks, not falsehood. It does not determine that a declared value is true.

What VTE does not do

It does not settle, lock or set aside anything. It says nothing about solvency or legal title. It is not a legal or compliance opinion.

Who sees what

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 demo service stores the values it is given; there is no cryptographic hiding.

Wallet signatures

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.

Words we use

VTE returns evidence.