VCP — Path Toward IETF RFC
VCP is designed to be RFC-friendly. VSO has five active individual Internet-Drafts (draft-kamimura-vap-framework-01, draft-kamimura-scitt-vcp-03, draft-kamimura-rats-behavioral-evidence-02, draft-kamimura-scitt-refusal-events-03, draft-vso-cpp-core-03); 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.
Being transparent about our standardization status is consistent with VCP's core philosophy: cryptographic truth, not marketing claims. We believe in earning credibility through technical merit and operational track record, not premature announcements.
VCP is designed for compatibility with the following IETF RFCs, supporting Internet-Draft development and interoperability with other RFC-based systems.
Deterministic JSON serialization ensuring identical byte sequences for cryptographic hashing across all implementations.
Merkle Tree audit design following CT patterns for efficient inclusion proofs and tamper detection.
Time-ordered, sortable, globally unique identifiers with embedded timestamps for event IDs.
Edwards-curve digital signatures providing high security, excellent performance, and compact signatures. Future PQC support planned.
ISO 8601 compatible date/time format for consistent timestamp representation across systems.
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.
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.
Building deployment experience. Current status: zero external implementations; zero Evidence Packs accepted in any proceeding. VeritasChain Co., Ltd. (the operating base of VSO) holds ten paid service contracts with European organizations in regulatory technology, financial trading, and audit and assurance (client names withheld pending individual consent).
Based on vcp-spec, a draft following the IETF Internet-Draft template has been published as an individual Internet-Draft for community review.
draft-kamimura-scitt-vcp-03 (individual submission)
Dialogue with relevant IETF Working Groups and potential BoF (Birds of a Feather) session participation.
OPSAWG, SEC Area, RTG Area, ART Area
BoF session → New WG formation if no suitable existing WG
Individual Internet-Drafts have been submitted to datatracker.ietf.org; five are currently active. Individual submission confers no IETF standing.
If adopted by a Working Group: iterative revisions, running code evidence, IETF Last Call, IESG review, and eventual RFC publication.
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 the content of future Internet-Drafts and RFCs.
This is an opportunity not just to follow a standard, but to participate in its design — a key differentiator of the VCP ecosystem.
Your implementation feedback directly shapes specification improvements
Certified adopters gain voice in standardization discussions
Regulatory input informs regulatory alignment from day one
| 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 |
If VCP is standardized, the following registries may be requested:
OrderSubmitted, OrderFilled, OrderCanceled, etc.
SHA-256, SHA-384, SHA-512, SHA3-256, etc.
Ed25519, ECDSA-P256, RSA-2048, Dilithium2, Falcon-512
Registry details will be finalized during the I-D process.
The best way to influence future standards is to implement and deploy VCP now. Join the effort to build verifiable algorithmic trading infrastructure.