Standardization Roadmap

VCP v1.2 — Path Toward IETF RFC

Current IETF Status

Target: future WG adoption under consideration
Regulatory outreach archiveHomepage snapshot · 3 November 2026

This is a historical snapshot of VSO’s self-reported homepage listing at commit dfec3b6, dated (UTC). It is preserved with its original qualifications. Moving it here does not newly verify outreach, receipt, technical review or approval. Consult the dated announcements and corrections for context.

REGULATORY OUTREACH — RECORDS UNDER REVIEW

Regulatory outreach: verification in progress

Correction — 24 October 2026: the previously displayed totals of 67 authorities and 50 jurisdictions are withdrawn from current promotional claims pending reconciliation with submission records. This is not a finding of zero submissions.

The map and list include historical outreach records under review. The 26 October 2026 announcements describe 26 individually recorded country contacts: 25 sent emails and one acknowledged form submission. Sending, receipt, technical engagement and approval are distinct evidence states.

Submission, receipt, technical response and approval are distinct evidence states.

Outreach around the world

World map highlighting the 26 countries contacted on 26 October 2026, including Cyprus, Slovenia, Mauritius, Georgia, Austria, Kazakhstan, Rwanda and Sri Lanka

Europe · outreach detail

European outreach detail including Austria, Slovenia and Cyprus; cyan indicates contact records from 26 October 2026
26 countries contacted on 26 October 2026 Historical list · under review

Country and authority names appear below. Colors indicate outreach records, not receipt or approval. Natural Earth

Americas
Europe
APAC + Middle East
Africa
United States
United States
CFTC · SEC
European Union
European Union
CEN-CENELEC
United Kingdom
United Kingdom
UK-Submissions
Singapore
Singapore
MAS
Hong Kong
Hong Kong
SFC
Australia
Australia
ASIC
India
India
RBI · SEBI · IFSCA
Switzerland
Switzerland
FINMA
UAE
UAE
DFSA
South Korea
South Korea
FSC · FSS
Saudi Arabia
Saudi Arabia
CMA · SAMA
Brazil
Brazil
CVM · B3
Liechtenstein
Liechtenstein
TVTG
Canada
Canada
OSC · CSA
New Zealand
New Zealand
FMA
Norway
Norway
Finanstilsynet
Estonia
Estonia
FI
Taiwan
Taiwan
FSC
Mexico
Mexico
CNBV
South Africa
South Africa
FSCA · SARB
Malaysia
Malaysia
SC · BNM
Indonesia
Indonesia
OJK
Thailand
Thailand
SEC Thailand
Qatar
Qatar
QFCRA · QCB
Philippines
Philippines
BSP · SEC
Israel
Israel
ISA · BoI
Chile
Chile
CMF
Vietnam
Vietnam
SSC
Turkey
Turkey
CMB
Egypt
Egypt
FRA
Bahrain
Bahrain
CBB
Kenya
Kenya
CMA
Nigeria
Nigeria
SEC
Bangladesh
Bangladesh
BSEC · BB
Pakistan
Pakistan
SECP
Kuwait
Kuwait
CMA
Jordan
Jordan
JSC
Morocco
Morocco
AMMC
China
China
CSRC
Argentina
Argentina
CNV
Colombia
Colombia
SFC
Peru
Peru
SMV
Oman
Oman
CMA · FSA
Ghana
Ghana
SEC
Luxembourg
Luxembourg
CSSF
Malta
Malta
MFSA · MDIA
Lithuania
Lithuania
BOL · LB
Poland
Poland
KNF
Cayman Islands
Cayman Islands
CIMA
Bermuda
Bermuda
BMA
France
France
AMF
Italy
Italy
CONSOB
Netherlands
Netherlands
AFM
Spain
Spain
CNMV
Ireland
Ireland
Central Bank of Ireland
Sweden
Sweden
FI
Denmark
Denmark
Danish FSA
Portugal
Portugal
CMVM
Czechia
Czechia
CNB
Slovakia
Slovakia
NBS
Belgium
Belgium
NBB
Croatia
Croatia
HANFA
Romania
Romania
ASF
Latvia
Latvia
Latvijas Banka
Hungary
Hungary
MNB
Iceland
Iceland
Central Bank of Iceland
Bulgaria
Bulgaria
FSC
Greece
Greece
Bank of Greece
Cyprus
Cyprus
CySEC
Slovenia
Slovenia
Banka Slovenije
Mauritius
Mauritius
FSC Mauritius
Georgia
Georgia
NBG
Austria
Austria
FMA
Kazakhstan
Kazakhstan
AFSA · AIFC
Rwanda
Rwanda
NBR / BNR
Sri Lanka
Sri Lanka
CBSL

Outreach records are being reconciled before totals are restated

Spanning Americas, Europe, Asia-Pacific, Middle East, and Africa

Section 1

Current Position

VCP is designed to be RFC-friendly. VSO has five active individual Internet-Drafts (draft-kamimura-vap-framework-03, draft-kamimura-scitt-vcp-05, draft-kamimura-rats-behavioral-evidence-02, draft-kamimura-scitt-refusal-events-04, draft-vso-cpp-core-04); none has been adopted by any IETF Working Group, and none has IETF standing.

This page describes our design alignment with existing RFCs and our potential path toward future standardization.

Why This Matters

Being transparent about our standardization status is consistent with VCP's core philosophy: cryptographically verifiable records, not marketing claims. We believe in earning credibility through technical merit and operational track record, not premature announcements.

Section 2

Technical Alignment with Existing RFCs

VCP is designed for compatibility with the following IETF RFCs, supporting Internet-Draft development and interoperability with other RFC-based systems.

RFC 8785

JSON Canonicalization Scheme (JCS)

Deterministic JSON serialization ensuring identical byte sequences for cryptographic hashing across all implementations.

RFC 6962

Certificate Transparency

Merkle Tree audit design following CT patterns for efficient inclusion proofs and tamper detection.

RFC 9562

UUIDv7

Time-ordered, sortable, globally unique identifiers with embedded timestamps for event IDs.

RFC 8032

Ed25519 Signatures

Edwards-curve digital signatures providing high security, excellent performance, and compact signatures. Future PQC support planned.

RFC 3339

Timestamps

ISO 8601 compatible date/time format for consistent timestamp representation across systems.

FIPS 180-4

SHA-256

NIST-approved secure hash algorithm for all hash chain and Merkle Tree operations.

This alignment supports Internet-Draft development and interoperability with other RFC-based systems.

Section 3

Roadmap to IETF RFC

IETF RFC standardization is positioned as a medium-to-long-term option, not a short-term goal. We will mature VCP v1.x through real-world deployment before considering the next steps.

1

Implementation & Operational Track Record

CURRENT PHASE

Building deployment experience. Current status: zero external implementations; zero Evidence Packs accepted in any proceeding. Commercial disclosure update (24 October 2026): the earlier contract figure is withdrawn pending primary-record verification; this does not establish zero contracts. Details

  • Early Adopter Program feedback collection
  • VC-Certified Silver / Gold operational experience
  • VCP Explorer API returns mock data, and the build was failing as of 2026-10-08. The SDK is an interface specification only.
2

Community Draft Publication

COMPLETED

Based on vcp-spec, a draft following the IETF Internet-Draft template has been published as an individual Internet-Draft for community review.

Current: draft-kamimura-scitt-vcp-05 (individual submission)
3

IETF Community Engagement

PLANNED

Dialogue with relevant IETF Working Groups and potential BoF (Birds of a Feather) session participation.

Potential WGs

SCITT, RATS (Security Area)

Alternative Path

BoF session → New WG formation if no suitable existing WG

4

Internet-Draft Submission

INDIVIDUAL SUBMISSION

Individual Internet-Drafts have been submitted to datatracker.ietf.org; five are currently active. Individual submission confers no IETF standing.

5

WG Adoption & RFC Process

GOAL

If adopted by a Working Group: iterative revisions, running code evidence, IETF Last Call, IESG review, and eventual RFC publication.

IETF operates on "rough consensus and running code" — deployment track record is essential.
Section 4

Shape the Future Standard

VCP's standardization process is strongly influenced by feedback from implementers and users.

Companies participating in the Early Adopter Program or achieving VC-Certified status will have substantive influence over future revisions of VSO's individual Internet-Drafts through implementation feedback. No RFC exists, and IETF publication is decided by IETF consensus, not by VSO.

This is an opportunity not just to follow a standard, but to participate in its design — a key differentiator of the VCP ecosystem.

Implementers

Your implementation feedback directly shapes specification improvements

VC-Certified

Certified adopters can contribute implementation feedback to VSO drafts

Regulators

Regulatory input informs regulatory alignment from day one

Summary: Current IETF Status

Internet-Draft individual submission (not WG-adopted)
Working Group not adopted by any WG
RFC Compatibility designed for alignment
Target future WG adoption under consideration

Potential IANA Registries

If VCP is standardized, the following registries may be requested:

VCP Event Type Registry

SIG, ORD, ACK, EXE, CXL, etc.

VCP Hash Algorithm Registry

SHA-256, SHA3-256, BLAKE3, etc.

VCP Signature Algorithm Registry

Ed25519, ECDSA-secp256k1, RSA-2048 (deprecated); experimental: Dilithium2, Falcon-512

Registry details will be finalized during the I-D process.

Get Involved Today

The best way to influence future standards is to implement and deploy VCP now. Join the effort to build verifiable algorithmic trading infrastructure.