VSO-SPEC-VCC-DEMO-001 | Version 1.0.0

VCC — VeritasChain Cloud

VCP Logging Concept and Browser Demo

Status clarification — 1 November 2026: This page describes a concept and a browser demo. It is not a hosted service, certification or conformance result. Experimental extensions remain unadopted; independent third-party reproduction has not been established.

VCC is a concept for a cloud-based VCP logging and certificate issuance service. This page presents a browser-based demonstration; a hosted service has not been released.

It provides cryptographically verifiable audit trails modelled on VCP v1.1 (the demo is not a conformant implementation).

Try the interactive demo to experience VCP in action.

"Verify, Don't Trust"

Maintained by VeritasChain Standards Organization (VSO)

What is VCC?

VeritasChain Cloud is a concept for cloud-based logging and certificate issuance for systems that implement VCP; this page presents a browser-based demo

Core Purpose

The VCC demo is a browser-based demonstration of VeritasChain Protocol (VCP) concepts, not a conformant or reference implementation. It demonstrates:

  • Client-side VCP v1.1 event creation and management
  • Merkle tree with RFC 6962-style hashing (published builder examples have known inconsistencies; see the notice above)
  • Certificate generation and verification
  • IndexedDB-based persistent storage

Target Audience

  • Developers evaluating VCP integration
  • Auditors understanding VCP data structures
  • Prop trading firms exploring transparency solutions
  • RegTech researchers studying compliance

Demo vs Production

Aspect VCC Demo VCC Production
Deployment Static hosting Cloud infrastructure
Storage Browser IndexedDB PostgreSQL / TimescaleDB
External Anchor Simulated OpenTimestamps / Blockchain
Multi-tenancy Single user Multi-tenant with API keys
Cryptographic Signing SHA-256 hash Ed25519 with HSM

VCP v1.1 Concepts Demonstrated

VCC Demo illustrates the three-layer integrity architecture defined by VCP v1.1 (signatures are not implemented and the anchor is simulated)

1

Event Integrity

Individual event tamper-evidence

  • EventHash (SHA-256)
  • PrevHash (optional)
2

Collection Integrity

Batch verification with Merkle Trees

  • Merkle Tree (RFC 6962)
  • MerkleRoot generation
  • Audit Path generation
3

External Verifiability

Third-party timestamp anchoring

  • External Anchor (simulated)
  • Digital Signature (not implemented — SHA-256 hash only)

Supported Event Types

1 SIG — Signal Generated 2 ORD — Order Submitted 3 ACK — Order Acknowledged 6 REJ — Order Rejected 4 EXE — Execution 7 CXL — Cancellation 9 CLS — Position Closed

Architecture Overview

VCC Demo runs entirely in the browser with zero server dependencies

┌─────────────────────────────────────────────────────────────────────┐
│                        Browser Environment                          │
├─────────────────────────────────────────────────────────────────────┤
│                                                                     │
│  ┌─────────────────────────────────────────────────────────────┐   │
│  │                    React Application                         │   │
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐  │   │
│  │  │  Dashboard  │  │   Events    │  │      Verify         │  │   │
│  │  │    Tab      │  │    Tab      │  │       Tab           │  │   │
│  │  └──────┬──────┘  └──────┬──────┘  └──────────┬──────────┘  │   │
│  │         │                │                     │             │   │
│  │         └────────────────┼─────────────────────┘             │   │
│  │                          ▼                                   │   │
│  │              ┌───────────────────────┐                       │   │
│  │              │     VCCService        │                       │   │
│  │              │  (Business Logic)     │                       │   │
│  │              └───────────┬───────────┘                       │   │
│  │                          │                                   │   │
│  │         ┌────────────────┼────────────────┐                  │   │
│  │         ▼                ▼                ▼                  │   │
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐          │   │
│  │  │   Crypto    │  │   Merkle    │  │    UUID     │          │   │
│  │  │   Module    │  │   Module    │  │   Module    │          │   │
│  │  └─────────────┘  └─────────────┘  └─────────────┘          │   │
│  │                                                              │   │
│  └──────────────────────────────┬───────────────────────────────┘   │
│                                 │                                   │
│                                 ▼                                   │
│                    ┌────────────────────────┐                       │
│                    │      IndexedDB         │                       │
│                    │  ┌────────┐ ┌────────┐ │                       │
│                    │  │ events │ │anchors │ │                       │
│                    │  └────────┘ └────────┘ │                       │
│                    └────────────────────────┘                       │
│                                                                     │
└─────────────────────────────────────────────────────────────────────┘

React 18.x

UI Framework for interactive components

Tailwind CSS 3.x

Utility-first CSS framework

Web Crypto API

Native browser cryptography

IndexedDB

Browser-based persistent storage

RFC 6962 Merkle Tree

Certificate Transparency standard

UUID v7

Time-ordered unique identifiers (RFC 9562)

Cryptographic Implementation

VCC Demo uses industry-standard cryptographic primitives

SHA-256 Hashing

Using Web Crypto API for native performance:

const sha256 = async (data) => {
  const encoder = new TextEncoder();
  const dataBuffer = encoder.encode(
    typeof data === 'string'
      ? data
      : JSON.stringify(data)
  );
  const hashBuffer = await crypto.subtle
    .digest('SHA-256', dataBuffer);
  return Array.from(
    new Uint8Array(hashBuffer)
  )
    .map(b => b.toString(16)
      .padStart(2, '0'))
    .join('');
};

RFC 6962 Merkle Tree

Domain separation to prevent second-preimage attacks:

Node Type Prefix Byte
Leaf 0x00
Internal 0x01

Merkle Tree Structure Example (5 Events)

                    [Root]
                      │
           ┌──────────┴──────────┐
           │                     │
        [N01]                 [N23-4]
           │                     │
      ┌────┴────┐          ┌─────┴─────┐
      │         │          │           │
   [N0]      [N1]       [N23]        [L4]
      │         │          │
   ┌──┴──┐   ┌──┴──┐   ┌──┴──┐
   │     │   │     │   │     │
 [L0]  [L1] [L2] [L3] [L2]  [L3]

Where: Lx = merkleHashLeaf(Ex), Nxy = merkleHashNode(Lx, Ly)

Security Considerations

Understanding the demo's limitations and the production alternatives

Important Notice

VCC Demo is a demonstration tool. The "anchor" is simulated within the browser and provides no external verifiability. Production systems must use real external timestamp authorities (OpenTimestamps, RFC 3161), blockchain anchoring for tamper-evidence, and HSM-backed digital signatures.

Client-Side Limitations

Aspect VCC Demo Production
Key Storage None HSM
Signature SHA-256 Ed25519
Tamper Evidence Browser Blockchain
Data Privacy Local Server-side

Security Features

  • Web Crypto API

    Native cryptographic operations via crypto.subtle

  • Secure Random

    crypto.getRandomValues() for UUID generation

  • Same-Origin Policy

    No cross-site data access enforced by browser

  • User Control

    User can clear all data at any time

Experience VCP in Action

Try the VCC Demo to understand how VCP v1.1 provides cryptographic audit trails for algorithmic trading.

Certification Status: This demo is NOT VC-Certified and does not constitute VSO endorsement. See the current certification status and limitations. This page does not establish a certification decision.