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)
VeritasChain Cloud is a concept for cloud-based logging and certificate issuance for systems that implement VCP; this page presents a browser-based demo
The VCC demo is a browser-based demonstration of VeritasChain Protocol (VCP) concepts, not a conformant or reference implementation. It demonstrates:
| 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 |
VCC Demo illustrates the three-layer integrity architecture defined by VCP v1.1 (signatures are not implemented and the anchor is simulated)
Individual event tamper-evidence
Batch verification with Merkle Trees
Third-party timestamp anchoring
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 │ │ │
│ │ └────────┘ └────────┘ │ │
│ └────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────┘
UI Framework for interactive components
Utility-first CSS framework
Native browser cryptography
Browser-based persistent storage
Certificate Transparency standard
Time-ordered unique identifiers (RFC 9562)
VCC Demo uses industry-standard cryptographic primitives
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('');
};
Domain separation to prevent second-preimage attacks:
| Node Type | Prefix Byte |
|---|---|
| Leaf | 0x00 |
| Internal | 0x01 |
[Root]
│
┌──────────┴──────────┐
│ │
[N01] [N23-4]
│ │
┌────┴────┐ ┌─────┴─────┐
│ │ │ │
[N0] [N1] [N23] [L4]
│ │ │
┌──┴──┐ ┌──┴──┐ ┌──┴──┐
│ │ │ │ │ │
[L0] [L1] [L2] [L3] [L2] [L3]
Where: Lx = merkleHashLeaf(Ex), Nxy = merkleHashNode(Lx, Ly)
Understanding the demo's limitations and the production alternatives
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.
| Aspect | VCC Demo | Production |
|---|---|---|
| Key Storage | None | HSM |
| Signature | SHA-256 | Ed25519 |
| Tamper Evidence | Browser | Blockchain |
| Data Privacy | Local | Server-side |
Native cryptographic operations via crypto.subtle
crypto.getRandomValues() for UUID generation
No cross-site data access enforced by browser
User can clear all data at any time
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.