Skip to main content

poc-evidence-vectors

Conformance vectors and an independent twin verifier for the evidence artifacts of the Proof-of-Control standard (LFDT-ProofOfControl, v1.0 draft).

For implementers of a Proof-of-Control verifier or evidence producer, and for the working group that wants a requirement to name a test.

pip install poc-evidence-vectors==0.1.0
python -m poc_evidence_vectors.run_vectors
poc-evidence-vectors 0.1.0: 171 passed, 0 failed, corpus_sha256=6e22b2503f1767125800d6bb9e1f96bd21c99dcfaffbd0f83362a739e8898111

To test your own verifier, pass --verifier "your-command". It receives one case as JSON on stdin and prints {"result": "accept"} or {"result": "reject", "code": "..."}. A rejection counts only when its code is one of the reasons the case names, because rejecting for the wrong reason is not a pass. The runner is standard library only.

Conformant means passing this corpus at a pinned version. The corpus_sha256 on the last line is what to pin beside the version number.

What is in it

171 cases, built from the specification at commit 93d0e282fc177d5df741de4cdd6a0d0dacf1955a. Each case names the requirement ids it tests, and each negative case differs from an accepted base by one mutation.

Kind Cases What it tests
token 87 claim-set structure, tagged digests, canonical form, duplicate keys, signatures, MODIFY binding
inclusion 37 RFC 6962 inclusion proofs at nine tree sizes, and the ways a proof can lie
consistency 23 append-only proofs, forked and reordered histories
chain 15 hash-chain replay: alteration, deletion, reordering, truncation, a re-signed rewrite caught by an anchor
canonical 9 RFC 8785 digests for strings, key order, numbers

The case classes are positive, negative, adversarial, robustness, finding, platform-fact, interop, ambiguity and observation. The last four are places where the specification text is silent or the reference code differs from it, and each says so in its note.

The twin

poc_evidence_vectors/twin.py shares no code with the specification's reference implementation. Its Merkle checks use the recursive definition in RFC 6962, its canonical form is written from RFC 8785, and its Ed25519 verification is RFC 8032 in plain integers. A case is only trusted when the twin and the corpus agree.

Status

Version 0.1.0. The builder, which needs the cryptography library, and the reference-validator comparison live beside the corpus and are not shipped in the wheel.

Doc Where
Case schema each file under corpus/<kind>/
Pinned manifest CORPUS-MANIFEST.json

Metadata

Release files for poc-evidence-vectors 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for poc-evidence-vectors 0.1.0
File Size Uploaded Provenance Actions
poc_evidence_vectors-0.1.0.tar.gz 52.8 kB Without provenance Details for poc_evidence_vectors-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for poc-evidence-vectors 0.1.0
File Interpreter ABI Platform Actions
poc_evidence_vectors-0.1.0-py3-none-any.whl Python 3 none any Details for poc_evidence_vectors-0.1.0-py3-none-any.whl

Total release size: 268.3 kB

Release files / poc_evidence_vectors-0.1.0.tar.gz

Download URL poc_evidence_vectors-0.1.0.tar.gz
Size 52.8 kB
Tags Source
SHA-256 checksum
How to use checksums
8040c5eb7e39f9aa6b8e2d7ddf1ed150746aa77309955e9ff3581404b1028fa7
BLAKE2b-256 checksum
How to use checksums
ae3c31578467f59cd6e0d2cb1f7adf554bb17abb9c0a4e54ac091416d7f339c6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / poc_evidence_vectors-0.1.0-py3-none-any.whl

Download URL poc_evidence_vectors-0.1.0-py3-none-any.whl
Size 215.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3d8828e1eea6eb195900cd48ddf844a72fbcb2b6742e6c0a42add4c2bc083e86
BLAKE2b-256 checksum
How to use checksums
e1c6e15c49de2af677c1f6d05dc57350071e53fdc6ac7d67c6bf8427ae784ad3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for poc-evidence-vectors 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page