How VeraSnap Opens the Door to a "Verifiable World"

Executive Summary

In early 2026, the VeritasChain Standards Organization (VSO) released "VeraSnap," an iOS application that represents the first commercial implementation of the Capture Provenance Profile (CPP) built on the VAP (Verifiable AI Provenance) framework.

This article provides a detailed technical and strategic analysis of how VeraSnap—a CPP implementation designed for media capture—contributes to the adoption of the VeritasChain Protocol (VCP), which was designed for financial trading audit trails. Despite appearing unrelated, these technologies share fundamental design philosophies, cryptographic foundations, and ecosystem effects that create deep interconnections between "camera applications" and "financial audit protocols."

---

1. Why Does a "Camera App" Contribute to "Financial Protocol" Adoption?

1.1 Framing the Question

VeraSnap is an iOS application designed as "a camera that cannot lie." It attaches cryptographic signatures to captured photos, proves timestamps via RFC 3161, and detects deletions through Completeness Invariants. Meanwhile, VCP (VeritasChain Protocol) is an audit trail protocol for recording decision-making and execution processes in financial trading, designed for compliance with MiFID II, EU AI Act, and GDPR.

On the surface, these two technologies belong to different domains. However, VeraSnap's release and adoption accelerate VCP adoption through several structural factors.

---

2. VAP/VSO Hierarchy — The Relationship Between CPP and VCP

2.1 Overview of the Three-Layer Architecture

Understanding the relationship between VeraSnap and VCP requires grasping the hierarchical structure of the VAP (Verifiable AI Provenance) framework established by the VeritasChain Standards Organization (VSO).

VCP is a profile for the financial domain, while CPP is a profile for media capture—both share VAP's common infrastructure. This shared foundation is the technical basis for VeraSnap's contribution to VCP adoption.

2.2 Shared Cryptographic Foundation

VCP and CPP share the following cryptographic primitives completely:

Purpose	Algorithm	Specification
Event Hash	SHA-256	REQUIRED
Digital Signature	Ed25519 (VCP) / ES256 (CPP)	REQUIRED
Merkle Tree	SHA-256 (RFC 6962)	REQUIRED
Completeness Assurance	XOR of SHA-256 (Completeness Invariant)	REQUIRED
JSON Canonicalization	RFC 8785 (JCS)	REQUIRED
External Anchoring	RFC 3161 TSA	REQUIRED (Silver+)
Post-Quantum Cryptography	ML-DSA-65	RESERVED

---

3. Social Implementation of "Verify, Don't Trust" Philosophy

3.1 Limitations of the C2PA Model and the Self-Attestation Problem

Existing media authenticity solutions, particularly C2PA (Coalition for Content Provenance and Authenticity), face the following structural challenges:

C2PA Model:
Creator signs → "Trust me" → NO INDEPENDENT CHECK

CPP Model:
Creator signs → TSA countersigns → INDEPENDENT THIRD-PARTY

C2PA uses a model where "creators sign their own content," lacking an independent third-party verification mechanism. This is a fatal flaw in the financial audit context—"trading systems proving their own legitimacy" is unacceptable to regulators.

3.2 Mandatory RFC 3161 TSA

Both CPP and VCP require external anchoring via RFC 3161 Time-Stamping Authority (TSA) for Silver conformance level and above. VeraSnap performs batch processing at 30-minute intervals, sending Merkle roots to external TSAs.

As VeraSnap users routinely take photos and obtain RFC 3161 timestamps, the concept of "time certification by external third parties" becomes widely understood. This reduces the explanation cost when financial institutions introduce VCP to management and compliance departments.

3.3 Deletion Detection via Completeness Invariant

The Completeness Invariant, standardized in VAP v1.2, is a "deletion detection" mechanism implemented by both CPP and VCP.

def verify_completeness(events, seal):
    ci = seal.completeness_invariant
    if len(events) != ci.expected_count:
        return VIOLATION
    computed = bytes(32)
    for e in events:
        computed = xor(computed, sha256(e))
    if computed != ci.hash_sum:
        return VIOLATION
    return VALID

The mathematical definition:

CI = {
  expected_count: n,
  hash_sum: H(E₁) ⊕ H(E₂) ⊕ ... ⊕ H(Eₙ),
  first_timestamp: T₁,
  last_timestamp: Tₙ
}

In VeraSnap, when users attempt to delete photos, they choose between "delete media only" or "invalidate proof"—the latter records a Tombstone event. This generalizes the concept that "the act of deletion itself is recorded."

---

4. Developer Ecosystem Sharing and Expansion

4.1 Shared SDKs and Reference Implementations

Technical assets developed during VeraSnap creation can be repurposed for VCP implementations:

Component	VeraSnap Implementation	VCP Reusability
RFC 3161 Client	AnchorService.swift	Directly reusable
Merkle Tree Builder	MerkleTreeService.swift	Directly reusable
JSON Canonicalization (RFC 8785)	Canonicalizer.swift	Directly reusable
Completeness Invariant	ChainIntegrityService.swift	Directly reusable
UUIDv7 Generation	UUIDv7.swift	Directly reusable
Ed25519/ES256 Signatures	CryptoService.swift	Reusable with algorithm substitution

As VeraSnap is distributed on the App Store and improved through real user feedback, the quality of these shared components increases. When financial institutions implement VCP, they can use these "battle-tested" components as reference implementations.

4.2 Open Source Community Formation

VeraSnap's technical specifications are publicly available, enabling third-party verification tools and alternative implementations. This openness contrasts with vendor-controlled trust list models like C2PA, allowing financial institutions to avoid vendor lock-in risks.

The TSA candidate list published by VSO includes diverse options:

TSA	URL	Features
rfc3161.ai.moda	https://rfc3161.ai.moda	Automatic failover to multiple TSAs
DigiCert	http://timestamp.digicert.com	Adobe AATL certified
Sectigo	https://timestamp.sectigo.com	eIDAS compliance option
FreeTSA	https://freetsa.org/tsr	Experimental/validation

---

5. Value as Demonstrated Case Studies for Regulatory Authorities

5.1 EU AI Act Article 12 Compliance

EU AI Act Article 12 mandates automatic logging capabilities for high-risk AI systems. VAP/VCP is designed to directly address these requirements.

Article 12 Clause	Requirement	VCP Implementation
12(1)	Automatic recording capability	Event-driven logging
12(2)(a)	Period of use recording	Timestamp, SessionID
12(2)(b)	Reference database used	ModelContext.ModelID
12(2)(c)	Input data identification	PromptHash, InputHash
12(2)(d)	Human oversight	HumanOverride field
12(3)	Technical measures	Hash chain, signatures
12(4)	Retention period	Silver: 2 years

As VeraSnap is distributed as a consumer application on the App Store, it creates opportunities for regulators to recognize VAP-based technology as "systems operating in the real world." This serves as a "precedent" when financial institutions explain VCP to regulatory authorities.

5.2 GDPR and Privacy by Design

Both CPP and VCP adopt "Privacy by Design" as a design principle. VeraSnap implements:

Privacy Feature	Implementation
Location Data	Default OFF, hashing option
Identity	Anonymous/Pseudonymous/Identified modes
Crypto-Shredding	GDPR-compliant deletion
Biometric Data	Not stored even in ACE mode

"We prove authentication was attempted. We store ZERO biometric data."

---

6. Open Protocol Strategy as a C2PA Alternative

6.1 Structural Issues with C2PA

C2PA is a consortium led by major companies including Adobe, Microsoft, Intel, and BBC, developing specifications for recording media provenance information. However, C2PA has the following structural issues:

Challenge	C2PA	CPP/VCP
Self-Attestation	Creators sign their own claims	Mandatory third-party timestamps (RFC 3161)
Metadata Stripping	95%+ stripped on social media	Verification URL + pHash recovery
No Deletion Detection	Missing events undetectable	Completeness Invariant
Exclusion Lists	Some changes bypass signatures	NO exclusion lists (all fields signed)
Trust Lists	Vendor-controlled	Open TSA ecosystem
UI Misconception	"Verified" display	"Provenance Available" display

6.2 Clarifying "Provenance ≠ Truth"

CPP establishes strict UI design guidelines:

Use	Avoid
"Provenance Available"	"Verified"
"Capture Recorded"	"Authenticated"
Information icon (ℹ️)	Checkmark (✓)

"This shows capture data. It does NOT verify content truthfulness."

By adhering to these UI guidelines and clearly communicating to users that "provenance proof is not truth proof," VeraSnap helps spread the same understanding in financial auditing. VCP records "trading system decision processes," not "whether those decisions were correct." This distinction is crucial for regulatory compliance.

---

7. Unified Conformance Levels

7.1 Bronze/Silver/Gold Three-Tier Structure

The conformance levels standardized in VAP v1.2 are common to both CPP and VCP:

Level	TSA	Completeness	Retention	Typical Use
Bronze	Optional	REQUIRED	6 months	Personal use, PoC
Silver	Daily	REQUIRED	2 years	Commercial, quasi-regulatory
Gold	Per-capture/trade	REQUIRED	5+ years	Regulatory mandatory, legal evidence

VeraSnap implements Silver level at initial release, with plans to transition to Gold level (ACE mandatory, per-capture TSA) in the future. This phased approach serves as a reference roadmap for financial institutions adopting VCP.

---

8. Shared Verification Service Infrastructure

8.1 VeritasChain Verification Service

VeraSnap adopts a verification URL architecture:

https://verify.veritaschain.org/cpp/{verification_code}
SLA: 99.95% availability, 50+ year retention

This infrastructure is potentially extensible as a VCP verification service in the future. When financial institutions adopt VCP, they may not need to "build verification services from scratch" but can use VSO-provided infrastructure.

8.2 Verification Pack Standard Format

CPP and VCP adopt a common Evidence Pack format:

{
  "verification_pack_version": "1.0",
  "verification_code": "CPP-2026-ABC123XYZ",
  "verification_url": "https://verify.veritaschain.org/cpp/CPP-2026-ABC123XYZ",
  "capture_event": { ... },
  "seal_event": { ... },
  "merkle_proof": {
    "leaf_hash": "sha256:...",
    "audit_path": ["sha256:...", "sha256:..."],
    "directions": ["L", "R"]
  },
  "completeness_invariant": { ... },
  "external_anchor": { ... },
  "recovery": {
    "phash_algorithm": "pHash-DCT",
    "phash_value": "d4c3b2a1..."
  }
}

This format standardization enables Proofs generated by VeraSnap and VCP to be verified using the same toolchain. If audit firms or forensic companies develop "VAP-compatible verification tools," they can support both CPP and VCP.

---

9. Cross-Reference of Use Cases

9.1 VeraSnap Use Case — Real Estate Fraud Prevention

This use case directly corresponds to VCP functions such as "counterparty identity verification," "contract authenticity," and "chronological consistency" in financial transactions. As VeraSnap use cases accumulate in real estate transactions, financial institutions can concretely envision VCP's utility.

9.2 Cross-Profile Interoperability

VAP v1.2 enables cross-references between different profiles:

{
  "cross_reference": {
    "source_profile": "CPP",
    "source_event_id": "019467a1-0001-7000-0000-000000000001",
    "target_profile": "VCP",
    "target_event_id": "01945f2a-8b3c-7f93-9f3a-1234567890ab",
    "relationship": "TRIGGERED_BY"
  }
}

For example, when an algorithmic trading decision (VCP event) was based on analysis of specific news images (images recorded via CPP), both can be linked. This cross-reference functionality addresses regulatory requirements for "input data provenance proof" in AI trading.

---

10. Market Education Effects

10.1 Proliferation of "Verifiability" Concepts

By making VeraSnap available to general consumers on the App Store, concepts like "cryptographic verification," "timestamp proof," and "hash chains" become socially permeated. This reduces "internal education costs" when financial institutions adopt VCP.

When executives experience that "their own photos become verifiable" using VeraSnap, they can intuitively understand VCP's value of "making trading system decisions verifiable."

10.2 Media Coverage and Awareness

VeraSnap has an accessible concept—"a camera that cannot lie"—and can be associated with topical issues like fake news countermeasures and AI-generated image detection. If media coverage increases VAP framework awareness, interest in VCP will also indirectly grow.

---

11. Risks and Challenges

11.1 VeraSnap Adoption Failure Risk

If VeraSnap fails to gain traction on the App Store, its contribution to VCP will be limited. Primary failure risks include:

Risk	Impact	Mitigation
UX Complexity	User attrition	Progressive feature disclosure, default optimization
TSA Availability	Functional failure	Failover to multiple TSAs
App Store Review	Release delays	Strict Apple guideline compliance
Competition (C2PA cameras)	Market share loss	Maintain C2PA compatibility, emphasize differentiation

11.2 Cognitive Distance Between Domains

Cognitive distance still exists between "camera apps" and "financial auditing." If financial institution decision-makers perceive VeraSnap as "a consumer app unrelated to us," the VCP interest-generation effect will be limited.

Addressing this requires proactive marketing communication by VSO, joint presentations at industry conferences, and PoC support for financial institutions.

---

12. Conclusion — Entry Point to a "Verifiable World"

VeraSnap's release is not merely "another camera app." It is the first entry point to a "verifiable world" based on the VAP (Verifiable AI Provenance) framework.

---

---