v1.2 Specification GA

What is the
VeritasChain Protocol (VCP)?

An open standard for cryptographic auditability across AI-driven & algorithmic trading systems.

Hash₀
Hash₁
Hash₂
...

Cryptographically linked chain of trading events

THE PROBLEM

Why VCP Exists

The algorithmic trading industry faces critical trust gaps — VCP addresses the root causes.

💥

Industry Collapse

2024: an estimated 80–100 prop trading firms shut down (Finance Magnates estimate), leaving many traders with unpaid payouts.

🔒

Black Box Systems

Trading logs are easily falsified. Outside parties cannot verify server-side data independently.

⚖️

Regulatory Pressure

Regulators demand AI transparency: the EU AI Act requires high-risk AI systems to allow automatic recording of events (Art. 12; applies to Annex III systems from 2 December 2027 — algorithmic trading is not listed in Annex III); MiFID II requires record-keeping for algorithmic trading (RTS 6).

😱
Opaque Logs
🔥
Market Chaos
✅
VCP Standard
THE SOLUTION

How VCP Solves These Problems

VCP defines how trading events—from decision to execution—are recorded in a cryptographically verifiable, tamper-evident format.

Tamper-Evident Records

Once recorded, events are append-only. Merkle trees and external anchoring make retroactive falsification of anchored events detectable.

Radical Transparency

Recorded decision points can be inspected. Traders, auditors, and regulators can independently verify the recorded audit trail.

Auditors can validate any subset of events independently using hash-chains & Merkle proofs.

Tamper-Evidence & Integrity

Cryptographic signatures (Ed25519) and Merkle trees make data integrity cryptographically verifiable.

VCP is designed to record the lifecycle of a trading decision—from signal generation to execution completion—in a cryptographically verifiable format.

ARCHITECTURE

How VCP Works — Three-Layer Architecture

Since v1.1, VCP defines a clear three-layer architecture for integrity and security, supporting "Verify, Don't Trust."

LAYER 3

External Verifiability

REQUIRED

Third-party verification without trusting the producer

Digital Signature (Ed25519) Dual Timestamp External Anchor (Blockchain/TSA)
LAYER 2

Collection Integrity

REQUIRED

Make completeness of event batches verifiable (omissions detectable)

Merkle Tree (RFC 6962) Merkle Root Audit Path
LAYER 1

Event Integrity

Individual event completeness

EventHash (REQUIRED) PrevHash (OPTIONAL)

External Anchor

Merkle Roots are anchored to external timestamping services (Blockchain, RFC 3161 TSA) for third-party verifiability.

Merkle Tree

Merkle trees with RFC 6962 domain-separated hashing enable efficient integrity verification of large datasets.

Canonical JSON

RFC 8785 deterministic JSON serialization ensures consistent hashing across all platforms.

UUIDv7

Time-ordered unique identifiers (RFC 9562) support temporal ordering of events; time bounds come from external anchoring.

Ed25519 Signatures

High-performance elliptic curve signatures with future-ready quantum migration path.

Precision Timestamps

PTP/NTP synchronized timestamps with nanosecond precision for HFT clock-synchronization requirements.

Key Insight: VCP is NOT a blockchain—it's a lightweight, high-speed "cryptographic audit layer" that works alongside existing trading systems.

LIFECYCLE

Full Trade Lifecycle Auditability

Each recorded stage of a trade is cryptographically linked.

SIG
ORD
ACK
EXE
CXL (Cancel) REJ (Reject)

SIG (Signal)

AI/Algorithm generates a trading decision

ORD (Order)

Order is submitted to broker/exchange

ACK (Acknowledge)

Broker/exchange confirms receipt

EXE (Execute)

Order is fully filled

Each event includes EventHash, Merkle Proof, and Signature — all linked by TraceID and externally anchored

TARGET AUDIENCE

Who VCP Is For

VCP serves the entire spectrum of algorithmic trading participants.

Proprietary Trading Firms

Produce verifiable evidence of fair dealing and rebuild trader trust

Silver / Gold

Retail/CFD/FX Brokers

Produce evidence relevant to best execution obligations

Gold

Exchanges & Dark Pools

Verifiable evidence for front-running detection and matching transparency

Platinum

DeFi Protocols & Bridges

Off-chain transparency, on-chain security

Gold / Platinum
COMPLIANCE

Regulatory Evidence by Design

VCP is a "cryptographic evidence layer" designed to produce evidence relevant to international financial regulations. Conformance does not by itself constitute legal compliance.

🇪🇺

EU AI Act

High-risk AI systems must technically allow automatic recording of events (Art. 12; Annex III systems from 2 December 2027). Algorithmic trading is not listed in Annex III. The VCP-GOV module records algorithm decisions and human-oversight events.

📊

MiFID II (RTS 6/25)

Algorithmic trading audit trails and clock synchronization requirements. Platinum tier uses PTPv2 for <1µs precision.

🔐

GDPR

VCP-PRIVACY supports crypto-shredding: destroying the encryption keys makes the personal data unreadable while the audit trail stays verifiable — a technique relevant to GDPR Art. 17 erasure requests. Whether it satisfies Art. 17 is a legal assessment for the controller.

🇺🇸

CFTC / SEC

Evidence relevant to market surveillance requirements and CAT Rule 613 consolidated audit trails.

🇯🇵

FSA Japan

Internal control requirements for algorithmic trading systems and risk management documentation.

🌏

APAC Standards

Singapore MAS, Hong Kong SFC, and ASIC guidelines for algorithmic trading transparency.

MODULES

VCP Modules at a Glance

Modular architecture for flexible implementation based on your requirements.

VCP-CORE

Three-layer architecture: Event integrity, Collection integrity (Merkle), External verifiability.

VCP-TRADE

Trading payload schema: orders, executions, positions, slippage data.

VCP-GOV

Algorithm governance, AI decision factors, human oversight records.

VCP-RISK

Risk parameters, position limits, stop-loss rules, margin requirements.

VCP-PRIVACY

Crypto-shredding relevant to GDPR erasure obligations, key management, data encryption.

VCP-RECOVERY

Chain disruption recovery, failure detection, gap identification.

VCP-XREF NEW

Cross-reference & Dual Logging for multi-party verification and dispute resolution.

COMPARISON

Why VCP vs. Traditional Logs?

Feature Traditional Logs VCP
Tamper Evidence ✗ ◎
Independent Verification ✗ ◎
Lifecycle Visibility ✗ ◎
Regulatory Evidence △ ◎
Log Format Proprietary / Inconsistent Open Standard
TIERS

Compliance Tiers

Choose the tier that matches your technical requirements and use case.

Platinum

HFT / Exchange

  • PTPv2 clock sync (<1µs)
  • Binary serialization (SBE)
  • >1M events/second
  • Hardware HSM signatures
  • External Anchor (10 min)

Gold

Institutional

  • NTP clock sync (<1ms)
  • JSON serialization
  • >100K events/second
  • Cloud-native deployment
  • External Anchor (1 hour)

Silver

Prop / Retail

  • Best-effort clock sync
  • JSON serialization
  • >1K events/second
  • MT4/MT5 compatible
  • External Anchor (24 hours)

v1.1 Key Change: External Anchor Required for All Tiers

As of v1.1, External Anchoring is mandatory for all tiers to uphold the "Verify, Don't Trust" principle. Silver tier can use lightweight options like OpenTimestamps or FreeTSA. Hash chains (PrevHash) are now optional—Merkle trees provide equivalent integrity verification.

FAQ

Frequently Asked Questions

Does VCP certification mean regulatory approval?

No. VC-Certified indicates technical conformance with the VCP standard, assessed by a VSO-approved Conformity Assessment Body (CAB)—it does not constitute regulatory approval, legal compliance, or financial soundness certification. VSO is a standards organization, not a financial regulator, and does not issue certifications itself.

Which platforms can implement VCP?

VCP is platform-agnostic. An SDK interface specification (vcp-sdk-spec: TypeScript, Python, MQL5; Release Candidate) and open-source reference implementations are published on GitHub, together with vcp-sdk v0.1.0, a pre-release offline core for VCP v1.2 (Python, TypeScript, MQL5) that is not an implementation of vcp-sdk-spec. No SDK package is published to PyPI or npm. It can be integrated as a sidecar alongside existing trading systems without modifying core logic.

How much development effort is required?

No external implementation exists yet, so VSO has no measured implementation times; the open-source reference implementations show the scope of a Silver-tier integration. Gold and Platinum tiers may require additional infrastructure setup for clock synchronization and high-performance logging.

How do auditors verify VCP data?

Verification depends on the input format, trusted keys and available evidence. The separate VCP RTA legacy-format PoC reports VALID, INVALID and INDETERMINATE; its ordinary CLI does not authenticate batch metadata or verify external anchors. Opt-in supplemental verification uses an unadopted format and cannot turn a later timestamp into proof of the original anchor time. Independent reproduction and full conformance are not established. The Explorer API source is public. Ordinary API routes return mock data; the separate SDK Evidence Demo is available in the public Explorer. The production URLs and SDK-spec workflow illustrated here are not an available production service. Authentication middleware is not implemented in the published API. Selected original CI records and their limits →

What's the difference between tiers?

Platinum is for HFT/exchanges (PTPv2, binary). Gold is for institutional traders (NTP, JSON). Silver is for retail/prop firms (best-effort timing). All tiers provide cryptographic integrity.

Is VCP a blockchain?

No. VCP is a lightweight cryptographic audit layer—not a distributed ledger. It uses Merkle trees and external anchoring for integrity, but doesn't require consensus or mining. The Platinum tier sets performance targets for HFT environments; no measured results have been published.

What is Dual Logging (VCP-XREF)?

VCP-XREF enables independent VCP event streams from multiple parties (e.g., trader + broker) that can be cross-referenced to detect discrepancies. Unless both parties collude, manipulation by one party is detectable by the other.

What is completeness verification?

v1.1 introduces completeness verification (termed "Completeness Guarantees" in the specification)—third parties can cryptographically verify, at anchor (batch) granularity, not only that events were not altered, but that no events were removed from a batch after it was anchored (omission after anchoring and split-view presentation are detectable). This is achieved through mandatory Merkle Tree construction and external anchoring.

Ready to Get Started?

Help build an ecosystem of transparent, verifiable trading systems.