aegis-verifier
ML-DSA-65 (FIPS 204) post-quantum agent identity verifier for the Aegis platform.
Verifies Merkle Tree Agent Certificates (MTACs) issued by an Aegis Certificate Authority. Built with PyO3 + maturin from a Rust core.
Requirements
- Python 3.11 or later
- No native build dependencies at install time (liboqs is statically bundled)
Installation
pip install aegis-verifier
Python 3.11+ required. On an older interpreter (e.g. stock Ubuntu 22.04's
python3= 3.10), pip reportsERROR: No matching distribution found for aegis-verifier— that error means your Python is below the 3.11 floor (the wheel is abi3-py311), not that the package is missing. Installpython3.11(or newer) and retry, e.g.python3.11 -m pip install aegis-verifier.
Pre-built wheels are available for Linux x86_64 (glibc and musl) and aarch64 (glibc), macOS universal2 (Intel + Apple Silicon), and Windows x86_64.
Basic usage
import aegis_verifier
# All inputs are raw bytes in wire-v1 format (see docs/spec/wire-v1.md).
try:
result = aegis_verifier.verify_inclusion(
leaf_bytes=leaf_bytes, # dcbor-encoded MtacLeaf
proof_bytes=proof_bytes, # wire-v1 encoded InclusionProof
sth_bytes=sth_bytes, # wire-v1 STH envelope (the bytes ML-DSA signed)
signature=signature, # 3309-byte ML-DSA-65 signature
ca_public_key=ca_public_key, # 1952-byte ML-DSA-65 public key
)
print(f"Verified: leaf_index={result.leaf_index}, "
f"tree_size={result.tree_size}, "
f"timestamp_ms={result.timestamp_ms}")
except aegis_verifier.AegisInvalidProofError as e:
print(f"Proof or signature invalid: {e}")
except aegis_verifier.AegisStaleSthError as e:
print(f"STH is stale: {e}")
except aegis_verifier.AegisVerificationError as e:
print(f"Verification error: {e}")
Exception hierarchy
Exception
AegisVerificationError # base class for all Aegis failures
AegisInvalidProofError # signature invalid, proof mismatch, or leaf hash fail
AegisStaleSthError # STH older than caller-supplied max_age
verify_inclusion RAISES on all failure paths. It never returns a
verified=False sentinel — a successful return always means verification passed.
Wire format
leaf_bytes: dcbor canonical encoding ofMtacLeaf(RFC 8949 §4.2.1 CDER profile)proof_bytes: CBORarray(3)of[tree_size: uint, leaf_index: uint, path: array<bstr(32)>]sth_bytes: CBORarray(2)of[tstr("AEGIS-STH-v1"), bstr(body)]where body isarray(5)of[log_id: bstr(32), tree_size: uint, timestamp: uint, root_hash: bstr(32), extensions: array]signature: 3309-byte raw ML-DSA-65 signature (FIPS 204, Algorithm 3)ca_public_key: 1952-byte raw ML-DSA-65 public key (FIPS 204)
See docs/spec/wire-v1.md in the source repository for the full normative spec.
Cryptographic details
- Algorithm: ML-DSA-65 (FIPS 204 final), also known as CRYSTALS-Dilithium level 3
- Tree: RFC 9162-inspired binary Merkle hash tree with SHA-256 leaf and node hashing
- Domain separation: dual-layer per AD-1.6-02 — envelope context string
"AEGIS-STH-v1"in wire bytes (auditor-visible) PLUS FIPS 204 §5.2 ctx parameterb"AEGIS-STH-v1"(cryptographically bound, not in wire bytes) - Native library: liboqs 0.13.0 (Open Quantum Safe, via the oqs 0.11.0 Rust crate), statically bundled
License
Metadata
Release files for aegis-verifier 0.1.4
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 | Actions |
|---|---|---|---|---|
| aegis_verifier-0.1.4.tar.gz | 201.0 kB | With provenance | Details for aegis_verifier-0.1.4.tar.gz |
Built distributions (wheels)
Total release size: 2.6 MB
Release files / aegis_verifier-0.1.4.tar.gz
| Download URL | aegis_verifier-0.1.4.tar.gz |
|---|---|
| Size | 201.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cef4dc992addf8ee919a37810b6f34d11559abe264399454b5342e76101f070f
|
|
BLAKE2b-256 checksum How to use checksums |
779f8791a0beea35634251f5ee724c792fffa3aa0bbdbc785ef675245d90c0ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / aegis_verifier-0.1.4-cp311-abi3-win_amd64.whl
| Download URL | aegis_verifier-0.1.4-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 261.6 kB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
ec4210d4779b6a9113f0aa94554844313fc7781102a3c7527cc2edfae5556e96
|
|
BLAKE2b-256 checksum How to use checksums |
4856d54277ecdd54966f167a96f2095e5efa0a28f267bf1481dbc53f3a609e60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / aegis_verifier-0.1.4-cp311-abi3-musllinux_1_2_x86_64.whl
| Download URL | aegis_verifier-0.1.4-cp311-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 641.9 kB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
57af2e6cd6f8a10b2a4e1a454e99b9a127183a383c933cecef8047653724518e
|
|
BLAKE2b-256 checksum How to use checksums |
1858db8317a620471a95d986442c0d1dacf89efcd25128958bdd84494693a8d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / aegis_verifier-0.1.4-cp311-abi3-manylinux_2_28_x86_64.whl
| Download URL | aegis_verifier-0.1.4-cp311-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 443.5 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
503f7d405981ee8da090af6ba56fe8c46c2bd70955c4f640bad668e8f6471898
|
|
BLAKE2b-256 checksum How to use checksums |
f9360158dfb6bb9c7292ac01f16e46d577ffb7708d18924fd20ca1f9ca346117
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / aegis_verifier-0.1.4-cp311-abi3-manylinux_2_28_aarch64.whl
| Download URL | aegis_verifier-0.1.4-cp311-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 352.7 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
44bb3cc2f6814caedeb4f42579c9bb9d4f9d93767aa6e34d726c8c5e621f993d
|
|
BLAKE2b-256 checksum How to use checksums |
13441e5741a5d888b2439688163eccb7c423139624fb6698fa2195c2b71bf0a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / aegis_verifier-0.1.4-cp311-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl
| Download URL | aegis_verifier-0.1.4-cp311-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl |
|---|---|
| Size | 741.5 kB |
| Tags | CPython 3.11 abi3 macOS 10.12+ universal2 (ARM64, x86-64) macOS 10.12+ x86-64 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3602b3b9935b6bc3bf952b6942f1fe08f3c2edd243fa48c365b47865bb2e2db2
|
|
BLAKE2b-256 checksum How to use checksums |
0700dff9b3f61d79549fe0383a436e69842afb51ece7417d49cd47dd6234b832
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logSecurity for aegis-verifier 0.1.4
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.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for aegis_verifier-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logA 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.