VSO / Research resources

VSO · Public research resources

VCP SDK: source, installation and verification limits

An offline core for Python, TypeScript and MQL5. Check distribution status, the installation snapshot and unsupported claims before evaluating it.

Public-source review: · Informative, non-normative

Published development source

vcp-sdk is unreleased development source; package metadata remains 0.1.0. It is not published to PyPI or npm. It is separate from the cloud/Explorer clients described by VCP SDK Specification.

It is a first-party implementation by VeritasChain Co., Ltd., not an external implementation, certified product or independent validation. See VCP SDK: current source and pinned installation.

Install a pinned source revision

The README pins installation to 8eadded87e4f4e46d011835b2ba9a874b91c916d. The current main documentation reviewed on 14 November and that installation snapshot are distinct; later main changes are not automatically included.

The historical v0.1.0 tag lacks subsequent fixes. Record the full commit rather than “0.1.0” alone. Python requires 3.10+; TypeScript requires Node 20+ or a browser bundler. Follow the installation section in VCP SDK: current source and pinned installation.

Read three-valued results

  • VALID: a performed check matched.
  • INVALID: a checked mismatch or malformed input.
  • INDETERMINATE: required trust, external proof or support is missing. Not a pass.

Aggregation prioritizes INVALID, then INDETERMINATE, then VALID. Without supplied and verified external anchoring, the full batch remains INDETERMINATE.

Capabilities and boundaries

The core covers canonical hashes, Merkle proofs and Python/TypeScript Ed25519 operations. MQL5 has a smaller feature set; do not assume identical signing and verification support.

Exact-integer handling, RFC trees and root-only signature coverage are documented in SDK implementation choices and verification limits. These implementation choices are not adopted VSO requirements.

The SDK does not contact services, establish real-world key ownership, prove all actions were captured, guarantee decision safety or validate the full JSON Schema. The SDK Explorer evidence demo is also a synthetic example, not a production audit.

Sources and reviewed revisions

This page summarizes public materials at pinned commits. Creating it is not a new research test run. Historical test records and fixed distributions remain unchanged.