Touchstone

USTB · Sequence 1 · X Layer testnet

UNVERIFIABLE

Five of eight controls were satisfied. Three could not be evaluated, so the asset is reported as unverified — and that report is on chain, permanently.

  1. holdings-as-of-date-present: satisfied
  2. ustb-aum-published: unevaluable
  3. ustb-nav-date-freshness: satisfied
  4. ustb-nav-per-share-published: unevaluable
  5. ustb-one-day-yield-present: satisfied
  6. ustb-outstanding-shares-published: unevaluable
  7. ustb-seven-day-yield-present: satisfied
  8. ustb-thirty-day-yield-present: satisfied

5 satisfied · 3 unevaluable

2026-08-17T16:48:32.075003Z · block 38526525

What Touchstone does

Touchstone compiles a fund issuer's own disclosures into machine-checkable controls. Each control cites a byte-exact span of the issuer's document. A deterministic engine evaluates the controls against freshly retrieved evidence, signs the result with Ed25519, and publishes it to a registry on X Layer testnet. A consumer contract, AssetGate, is written to gate on that state — on the report's status, freshness, publisher lineage and pinned control-set root — but it is not deployed, so nothing is reading the registry in production today.

Compile

A model reads the issuer's published documents and proposes controls. Each candidate cites the exact bytes it was drawn from. Deterministic gates screen every candidate; a human approves the set. Declined candidates are recorded, with reasons.

Evaluate

An engine retrieves fresh evidence and evaluates each control. It never guesses. When the evidence cannot support an answer, the control is reported unevaluable — and that is a result, not an omission.

Publish

The report is signed with Ed25519 and published to a registry contract on X Layer testnet. Anyone can download the signed bundle and verify the signature, the roots, and every control hash offline.

Abstention is a decision

On its first live run, Touchstone evaluated the eight approved controls for Superstate's USTB. Five were satisfied. For three, no qualifying earlier capture existed, so their values were not evaluated. The engine did not fill the gap with an assumption. It published the asset as UNVERIFIABLE — signed, sequenced, permanent.

Anyone can build a thing that says CONFIRMED. This one tells you when it doesn't know.

One report

The registry holds one published report: USTB, epoch ustb-2026-08-17, sequence 1. This site renders it in full and links the bundle it was signed from. Nothing else is claimed.