algovoi-keystone-verifier
Independent, offline, one-call verification of AlgoVoi keystone evidence.
Given a keystone record, a Payment Evidence Frame, an audit chain of frames, or a full bundle of
all three, this re-derives every content-addressed reference from the raw fields and confirms it
matches the carried value. It depends only on the substrate JCS canonicalisation (sha256_jcs),
not on the packages that produced the evidence, so an auditor verifies without trusting the
builder. RFC 8785 JCS + SHA-256 are the whole dependency; it runs on any substrate version (v0/v1).
Install
pip install algovoi-keystone-verifier
Use
from algovoi_keystone_verifier import verify_bundle, verify_keystone, verify_frame, verify_audit_chain
res = verify_bundle({
"keystone": keystone_record, # passport/mandate/policy/decision/execution/trust_query
"frames": [pef_frame, ...], # optional Payment Evidence Frames
"audit_chain": audit_chain, # optional chain of frames, capped
})
res.ok # True iff every re-derivation matched
res.to_dict() # {"ok": ..., "checks": [{"name","ok","detail"}, ...]}
It re-derives decision_ref, execution_ref, trust_query_ref and the chain; the PEF
receipt_hash and frame_id; the audit-chain rows (prev_hash linkage, genesis 64 zeros) and the
trust_query_ref cap; and cross-checks that frames carry the keystone's execution_ref. Tamper any
field and the relevant check fails.
CLI:
cat bundle.json | python -m algovoi_keystone_verifier # exit 0 if every check passes
TypeScript twin: @algovoi/keystone-verifier,
byte-identical re-derivation.
Licensing
Apache-2.0. This open verifier checks the content-addressed references (the unsigned substrate). A commercial tier verifies the cryptographic signatures (hybrid Falcon-1024 + ML-DSA-65) and ingests into the Compliance Command Center.
Pinned edition for adopters, with a free key. Pin algovoi-keystone-verifier==0.1.0, anchor a
keystone_v1 (or pef_keystone_v1) vector hash, and keep the NOTICE; that four check gate earns a
free v0 licence key for algovoi-mandate-auditor (email chopmob@gmail.com with your import-by-hash
evidence and the NOTICE).
Python and TypeScript produce identical re-derivations. Redistribution must retain the NOTICE and
the Apache-2.0 LICENSE.
Metadata
Release files for algovoi-keystone-verifier 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| algovoi_keystone_verifier-0.1.0.tar.gz | 11.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| algovoi_keystone_verifier-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.1 kB
Release files / algovoi_keystone_verifier-0.1.0.tar.gz
| Download URL | algovoi_keystone_verifier-0.1.0.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f1297d19ca385285fc7987dac109058256006c508dc6a9b0264ed5527a9309e
|
|
BLAKE2b-256 checksum How to use checksums |
9c857dcb7db2821e4a11cb808343705612bba2f8d855e5c6512164219c3b9181
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / algovoi_keystone_verifier-0.1.0-py3-none-any.whl
| Download URL | algovoi_keystone_verifier-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60e2f40c41a7b1425933c662d644858b4ec243342a098ea66558c0e79fb82352
|
|
BLAKE2b-256 checksum How to use checksums |
0a66523a4b902e003aa9d507e101026c7ad6f8d761f8d61dc0bb569a8597b402
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for algovoi-keystone-verifier 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.