0.12.0-draftPrivate / internal draftExternal validation pending

Machine-readable verification for tokenized assets.

VOTH — Verifiable Open Token Holdings — defines a deterministic framework for describing what a tokenized product claims to be, what evidence supports those claims, what can currently be verified, and what remains unknown.

See how VOTH reasons

toggle the evidence conditions

Synthetic claim · BACKING

synthetic data

Toggle conditions to see how the verifier reasons. Every combination demonstrates safe behavior — missing, stale, unbound, or self-declared evidence never becomes PASS.

Discovery layer

RESOLVED

Verification verdict

PASS

Independent, fresh, subject-bound evidence supports the claim under the applicable policy → PASS.

Discovery and verification are separate. CONFLICT is a discovery status and is never turned into FAIL or UNKNOWN.

Interactive semantics demo · synthetic data

The model

Three layers, from description to continuous checking.

Claim families

Every claim is a specific, checkable question.

Select a family to see what it represents.

BACKING

Does available admissible evidence support the claimed backing relationship?

Verdicts

PASS, FAIL, and a first-class UNKNOWN.

PASS

Current admissible evidence satisfies the claim under the applicable policy.

FAIL

Admissible evidence materially contradicts the claim.

UNKNOWN

Available evidence is insufficient, stale, unsupported, missing, or otherwise unable to establish the claim.

UNKNOWN is a first-class result.

Missing evidence never becomes PASS.

Self-declared structural truth alone does not become PASS under the current hardened semantics.

Discovery-layer CONFLICT is never flattened into FAIL or UNKNOWN.

Evidence graph

Claims resolve from admissible evidence — or stay UNKNOWN.

Select a node to inspect its trust class, freshness, subject binding, source, and representation scope.

BACKING CLAIMPASS

Custody observation

admissible

Trust class: NATIVE_DETERMINISTIC
Freshness: fresh
Subject binding: bound
Source: on-chain account state
Representation scope: solana representation

Directly read from chain state and bound to the claimed subject.

Synthetic evidence graph · illustrative only

Trust classes

Not a simple best-to-worst ranking.

Admissibility depends on the claim and the applicable policy — a class that is admissible for one claim may be insufficient for another.

NATIVE_DETERMINISTIC

Read directly and deterministically from chain state.

SIGNED_EXTERNAL

A signed statement from an external party.

DOCUMENT_COMMITMENT

A commitment (e.g. hash) to an off-chain document.

ORACLE_DERIVED

Derived from an oracle or external data feed.

SELF_DECLARED

Declared by the subject itself, without independent support.

MULTI_SOURCE

Corroborated across multiple independent sources.

Product passport & representations

One economic product, many representations.

productId: example:solana:tokenized-product-001
productClass: tokenized-index-product
profileVersion: 0.12.0-draft
verificationPolicy: policy:default-hardened
representations: solana: example:solana:mint-XXXX other-chain: example:otherchain:asset-YYYY
claims: IDENTITY, CUSTODY, SUPPLY, BACKING, REDEMPTION, AUTHORITY
evidenceReferences: ev:custody-001 ev:supply-001 ev:issuer-stmt-001
rights: Machine-readable declared/source-backed rights. Not a legal opinion.

Generic synthetic product for demonstration. Not a real product.

Economic product

Solana representationPASS

Other-chain representationUNKNOWN

A representation's verification does not automatically propagate to another representation.

Synthetic chains / product data

Continuous verification

State changes as evidence changes.

Initial admissible evidence

BACKINGPASS

Verdicts re-evaluate as evidence changes or expires. Expiry moves a claim to UNKNOWN — it never silently stays PASS.

API & SDK

Structured, deterministic output.

Private API/SDK — not publicly released

Discovery status and per-claim verification verdicts are returned as separate fields. Illustrative response:

{
  "discoveryStatus": "RESOLVED",
  "verification": {
    "IDENTITY": "PASS",
    "SUPPLY": "PASS",
    "BACKING": "UNKNOWN",
    "REDEMPTION": "UNKNOWN",
    "AUTHORITY": "PASS"
  }
}

Illustrative response · no public API currently exists

Current status

Transparent about what is — and isn’t — done.

This honesty is part of the brand.

VOTH current status
Current normative target	0.12.0-draft
Internal engineering	PASS
Internal adversarial hardening	PASS
External handoff readiness	PASS
Independent external implementation	NOT STARTED
Independent security / spec review	NOT STARTED
VOTH 1.0 RC	NOT CREATED
Publication	PRIVATE

Internal validation evidence

Internal engineering evidence — not external validation.

0 mismatches

Deterministic JS/Python verifier agreement

7 products

Internal product benchmark

370 vectors

Current conformance corpus

7,096

Deterministic tests

28,000

Historical mutation cases

64,000

Historical property cases

5,000

Historical combinatorial cases

5,000

Historical monitoring sequences

These results do not constitute independent external validation or certification.

Limitations

What VOTH does not claim.

External validation has not yet been completed.
Token-2022 is currently unsupported.
The live verification profile is currently Solana-first.
Off-chain-dependent claims may remain UNKNOWN.
The Rights Manifest is not a legal opinion.
No certification.
No investment opinion.
No risk score.
No regulatory classification.
No public production API.
No production monitoring service.
No claimed external adoption.

VOTH remains private while validation is pending.

There is no public integration path yet. The most useful thing you can do today is understand the model.

About VOTHExternal validation pending