@techreport{kamimura-scitt-vcp-03,
    number =    {draft-kamimura-scitt-vcp-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kamimura-scitt-vcp/03/},
    author =    {TOKACHI KAMIMURA},
    title =     {{A SCITT Profile for Verifiable Audit Trails in Algorithmic Trading: The VeritasChain Protocol (VCP)}},
    pagetotal = 26,
    year =      2026,
    month =     jul,
    day =       21,
    abstract =  {This document defines a profile of the SCITT (Supply Chain Integrity, Transparency, and Trust) architecture for creating tamper-evident audit trails of AI-driven algorithmic trading decisions and executions. The VeritasChain Protocol (VCP) applies the SCITT framework to address the specific requirements of financial markets, including high-precision timestamps, regulatory compliance considerations (EU AI Act, MiFID II), and privacy-preserving mechanisms (crypto-shredding) compatible with GDPR. This profile specifies how VCP events are encoded as SCITT Signed Statements, registered with Transparency Services, and verified using COSE Receipts. It further defines SCITT conformance profiles for interoperability and an ERASURE event type that records crypto- shredding operations as immutable audit events. About This Document This note is to be removed before publishing as an RFC. The latest version of this document, along with implementation resources and test vectors, can be found at https://github.com/veritaschain/vcp-spec. Discussion of this document takes place on the SCITT Working Group mailing list (scitt@ietf.org). Changes from -02: * Updated to align with VCP Specification v1.2 * Added SCITT Alignment Object and conformance profiles (Section 4.4) * Added ERASURE event type recording crypto-shredding operations (Section 6.3) * Corrected the post-quantum SignAlgo registry value from DILITHIUM3 to DILITHIUM2 (ML-DSA, FIPS 204) * PolicyID examples migrated to the Issuer Domain + Local ID naming convention defined in VCP v1.2},
}