VCP v1.0 — Path Toward IETF RFC
VCP v1.0 is designed to be RFC-friendly, but we have not yet submitted an Internet-Draft nor initiated any formal Working Group process at the IETF.
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 v1.0 is designed for compatibility with the following IETF RFCs, ensuring future Internet-Draft conversion 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 ensures future Internet-Draft conversion 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 and gathering feedback from real-world implementations.
Based on vcp-spec, publish a v0.x draft following the IETF Internet-Draft template on GitHub for community review.
draft-vso-vcp-00.txt format
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
With sufficient adoption metrics and community feedback, consider formal Internet-Draft submission to datatracker.ietf.org.
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 ensures compliance alignment from day one
| Internet-Draft | not yet submitted |
| Working Group | not yet formed |
| RFC Compatibility | designed for alignment |
| Target | future submission 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 growing ecosystem of organizations building verifiable algorithmic trading infrastructure.