Home / FAQ
Straight answers
Frequently asked questions
Is VAP a blockchain?
No. VAP composes hash-chained events, Ed25519 signatures, Merkle batching, and external anchoring (for example, RFC 3161 time-stamps or transparency logs). A blockchain can serve as one anchor target class among several; none is required.
Does VAP prevent tampering or bad AI behavior?
No. VAP is post-hoc forensic and evidentiary infrastructure. It is tamper-evident, not tamper-proof: alteration and post-anchor omission are made detectable after the fact. It does not prevent, block, or intercept anything at runtime, and it does not make AI decisions correct, fair, or safe.
Is VAP a protocol?
No. VAP is a meta-framework. The Protocol designation belongs to exactly one document in the family: VCP, the VeritasChain Protocol (finance / algorithmic trading, v1.2 RC1).
What does conformance actually guarantee?
Per the normative §1.6 statement, conformance warrants only the integrity, completeness (at anchor granularity), and attributability of the records — never the correctness, fairness, or safety of the underlying decisions, and never legal compliance with any regulation. VAP generates evidence; competent authorities and courts evaluate it.
Can VAP recover records that were never created?
No, and it never will. That is Tier 1 of the missing-data taxonomy: events that never crossed the observation boundary are permanently unrecoverable by design. VAP makes the boundary itself declared and checkable (ScopeManifest), bounds Tier 2 loss, and makes Tier 3 omission third-party detectable (INT-008).
How does VAP relate to existing standards?
It builds on them rather than replacing them: SHA-256, Ed25519 (RFC 8032), RFC 3161 time-stamping, Merkle proofs, WARC/1.1 for web observation, and COSE/SCITT alignment. Five Internet-Drafts are active in the IETF RATS and SCITT areas.
Who maintains VAP, and under what license?
The VeritasChain Standards Organization (VSO), an independent standards body whose secretariat is provided by VeritasChain Co., Ltd. (Tokyo). Specifications are published under CC BY 4.0 and developed openly on GitHub.
What is the project's real adoption status?
As of August 2026: zero external implementations, zero paying customers, and zero Evidence Packs accepted in any proceeding. This disclosure is mandatory in every VSO document, including this website.