Corrections log
VSO corrects its public statements by adding dated records rather than silently rewriting them. This page lists corrections to the specifications, repository READMEs and this website, newest first. Each entry links to its change record. Dated announcements and blog posts are kept as records of what was published at the time; where they are affected, they carry a note.
VeraSnap is VeritasChain Co., Ltd.'s app, not VSO's
The 13 April 2026 announcement called VeraSnap “our production cryptographic evidence capture app”. VeraSnap is an app of VeritasChain Co., Ltd., the company that operates VSO, not a VSO specification, and its availability in app stores is not a claim of conformance to VAP or CPP. A dated note was added under the announcement (English and Chinese); the announcement text is kept as published.
Records: vcp-site #111
Commercial contract figure withdrawn
The previously published figure of ten paid service contracts with European organisations, held by VeritasChain Co., Ltd., has not been substantiated through reconciliation with primary records. It was withdrawn from the VAP, VCP, CAP and CPP repositories and this site pending that review. This is not a finding that there were no contracts, and no replacement figure is asserted.
Records: Dated correction and counting criteria vap-spec #15 vap-spec #20 vcp-site #100 vcp-spec #5 cap-spec #2 cpp-spec #1
Regulator-submission figures under review
The homepage figure of 67 regulatory authorities in 50 jurisdictions is no longer presented as a current count. The list included entries that are not regulatory authorities, a placeholder, a duplicate and an authority that no longer exists. Earlier dated announcements with regulator counts are kept, with a note that the totals remain under review.
Records: vcp-site #102 vcp-site #104
VCP alignment with VAP v1.2 under review
VAP §10.4 no longer records VCP v1.1 and v1.2 as fully conformant to VAP v1.2. The VCP v1.2 Merkle construction and audit-path examples conflict with the specification's own RFC 6962 requirement, and the root-only AnchorRecord signature does not authenticate the attached count, endpoint or policy metadata. Two integrity-layer drafts are published as unadopted discussion documents; they are not an issued erratum.
Records: vap-spec #18 vap-spec #19 vcp-spec #5 vcp-spec #3 vcp-spec #4
VCP status and cross-party wording recorded as known issues
The VCP v1.2 known-issues lists now record that §1.1 calls VCP "a global standard specification" and says it "establishes truth", and that §5.6 (VCP-XREF) uses guarantee and dispute-prevention language. The specification text is unchanged; these are errata candidates.
Records: vcp-spec #7
Company-specific proposal pages removed
Pages addressed to named companies were removed from this site. Some described exclusive positions under the VC-Certified scheme and interpretation of the standard by an assessment body; they were not descriptions of the scheme. A test now fails if such wording returns.
Records: vcp-site #105
"Approved", not "accredited", Conformity Assessment Bodies
Under ISO/IEC 17000:2020, accreditation is a third-party attestation related to a conformity assessment body. VSO's designation of a CAB under the VC-Certified scheme is an approval, and the site now says so. The only listed CAB provides VSO's operating base and is not independent of the scheme owner.
Records: vcp-site #106
Mission wording aligned with VAP §1.6
The company and exchange pages no longer say that VCP establishes "mathematically verifiable truth" or "cryptographically verifiable truth". They now describe third-party verification of whether a record was altered or omitted after anchoring; a verifiable record does not establish that a decision was correct.
Records: vcp-site #104
Unverified SDK installation instructions removed
Installation commands for package names that VSO has not published (npm @veritaschain/sdk and PyPI veritaschain, which returned 404) were removed from the organisation profile.
Records: Organisation profile change
CAB independence errata (E-2026-10-21)
The VAP specification and README no longer say that independent Conformity Assessment Bodies currently perform assessment. The requirement that a CAB be independent of the scheme owner is unchanged.
Records: VAP v1.2 ERRATA
Site-wide review of outdated and incorrect statements
Version and status information, regulatory references and statements beyond what the specifications provide were corrected across the English, Japanese and Chinese pages. Blog posts and two white papers were kept as dated records with correction notes.
Records: Site changes
VAP v1.2.0 Draft 3 post-publication folds and site corrections
Regulatory references (L-1 to L-3) and capability language (H-3 to H-5) in VAP v1.2.0 Draft 3 were corrected, with dispositions in Appendix D; matching corrections were made on this site.
Records: Appendix D Site changes
"Non-profit" removed from descriptions of VSO
VSO's operating base is provided by VeritasChain Co., Ltd., a Japanese kabushiki kaisha. Descriptions of VSO as a non-profit were replaced with a description of neutrality by published mechanisms.
Records: Site change