Trust Anchor Documentation

The Digital Evidence Standard for the Post-Truth Era.

Version 1.0

Model: Evidence-First

Works with DATA_ANCHOR

Overview

The Trust Anchor is a standard that transforms any "digital event" (an image, video, text, declaration, or AI result) into verifiable evidence. This evidence is dated, localized via Timeverse coordinates (SWT + Tile, without GPS), signed, and durably anchored.

As synthetic media and AI-generated content become indistinguishable from organic data, the Trust Anchor provides the technical foundation for provable existence and provenance. It bridges the gap between raw data and verifiable truth by encapsulating the entire context of an event into a reproducible, audit-grade artifact.

Core Concept

Trust Anchor = Digital Evidence Standard

Signed evidence (off-chain)+Anchored hash (on-chain)+Offline verification+BFT finality

1) What is a Trust Anchor?

A Trust Anchor is used to certify content and disclosures across critical domains:

Anti‑deepfake: Source provenance and authenticity.
IP Priority Proof: Evidence of existence & creation timeline.
Moral Rights: Signed declarations for AI training or style imitation.

AI Disclosure: AI Act-style labeling and transparency evidence.
Source Verification: Combating misinformation at the root.

The Key Insight

Evidence is stored off-chain in a signed Layer‑0 audit ledger, while Clockchain anchors only a hash commitment. This ensures privacy and scalability without sacrificing truth.

2) Why Evidence-First?

This model keeps Clockchain scalable and privacy-preserving:

Scalability

Stores 32-byte hash commitments, not heavy media bytes.

Privacy

Rich evidence remains off-chain. No raw content or GPS on-chain.

Verifiability

Proofs are independently verifiable offline via the audit hash.

Interoperability

Anchor any format (PDF, Video, QARP) via a standard hash.

3) End-to-End Flow

Create Trust Evidence (Off-chain)

Generate a rich evidence object (Content Attestation, IP Proof). MUST be int-only signable JSON.

Issue a TSAE Receipt (Audit Proof)

Signed receipt proving evidence was produced under a specific policy context (ticks, cycle, SWT).

Build an Anchor Envelope (ORCH)

ORCH signs an envelope binding the audit hash, TSAE hash, and trust projection fields.

Optional Witness (T‑WATCH)

A physical T-WATCH device signs a witness envelope binding to the same anchor hash.

Anchor on Clockchain

Submit a DATA_ANCHOR transaction. Clockchain finalizes it with BFT votes (8/12 threshold).

4) What gets anchored (and what does not)

Anchored on Clockchain

• data_hash (Hash of the ORCH anchor envelope)

• Inclusion in a FINAL block (BFT votes)

• Minimal trust labels (Kind + Subject Hash)

Stored Off-chain

• Raw content bytes (image, video, text)

• Detailed evidence payloads

• Full policy and audit logs

5) Data Model Overview

5.1 Trust Evidence Object (Off-chain)

Schema: TV-TRUST-EVIDENCE-2026-01. All fields MUST be integers/strings.

Example: Content Attestation

{
  "schema":"TV-TRUST-EVIDENCE-2026-01",
  "trust_kind":"CONTENT_ATTESTATION",
  "content_hash":"sha256:<64hex>",
  "perceptual_hash":"sha256:<64hex>",
  "content_type":"image/jpeg",
  "content_size_u32":123456,
  "author_did":"did:timeverse:author-001",
  "creation_method":"HUMAN_RECORDED",
  "ai_disclosure": null
}

Example: TSAE Receipt (Audit Proof)

TV-TSAE-2025-12

{
  "tsae_schema":"TV-TSAE-2025-12",
  "scope":"tsae.now.trust",
  "day_index":1240,
  "phi_action_ticks":59318,
  "swt_zone":6,
  "tile_id":266,
  "trust_kind":"CONTENT_ATTESTATION",
  "trust_subject_hash":"sha256:<64hex>"
}

6) Optional: T‑WATCH Witness

The T-WATCH adds a physical dimension to the Trust Anchor. An independent hardware witness signs that it has observed the anchoring event, ensuring maximum non-repudiation.

Witness Message Example

{
  "schema":"TV-TWATCH-WITNESS-2026-01",
  "witness_kind":"OBSERVED_ANCHOR",
  "observed_data_hash":"sha256:<64hex>",
  "device_id":"T-WATCH-7421",
  "device_state":{
    "battery_mv_u16":3920,
    "light_lux_u16":120,
    "sensor_ok":1
  }
}

Binding rule (MUST): observed_data_hash == data_hash

7) Offline Verification Checklist

Recompute data_hash == sha256(canonical(anchor_envelope)).
Verify ORCH signature with pinned ORCH key (from /api/v1/keys).
If witness exists: verify T-WATCH signature and check observed_data_hash == data_hash.
Verify FINALity: bft_votes >= bft_threshold.

8) Important Disclaimer

Legal Notice

Trust Anchors produce verifiable evidence artifacts. They do not automatically guarantee legal compliance in all jurisdictions. Compliance depends on specific local laws and your organization's internal policies.

9) Explorer UX

Explorers (like binutecoin.com) display Trust Anchors by Kind, Subject Hash, and Finality status.

Recommended Filters:• By Trust Kind (IP, AI Disclosure)
• By Subject Hash (Content Hash)
• By Tile ID / SWT Zone

Trust Anchor = Signed Evidence (off-chain) + Anchored Hash (on-chain) + BFT finality.