emilia-verify (Python)
Zero-infrastructure verification of EMILIA Protocol trust receipts — pure Python,
one dependency (cryptography). A faithful port of @emilia-protocol/verify:
recursive canonical JSON + Ed25519 (SPKI-DER public key) + sorted-pair Merkle anchors.
The guarantee: a receipt signed on the Node side verifies here, and vice versa —
proven by a cross-language test (tests/test_verify.py verifies a JS-signed fixture).
No EP account, no API key. Just math.
Install
pip install emilia-verify # once published
# or, from the repo: pip install packages/python-verify
Use
from emilia_verify import verify_receipt
result = verify_receipt(receipt_doc, signer_public_key_base64url)
if result.valid:
print("authorized by", receipt_doc["payload"]["claim"]["approver"])
else:
print("rejected:", result.checks, result.error)
verify_receipt(doc, public_key_base64url) -> VerifyResult(valid, checks, error) checks
the version, the Ed25519 signature over the canonical payload, and (when present) the
Merkle anchor. It never raises on bad input — a malformed receipt returns valid=False.
Also exported: verify_merkle_anchor(leaf_hash, proof, expected_root) and
canonicalize(value) (the exact canonical-JSON used for signing).
Why this exists
A trust receipt is only as useful as the number of places that can check it. Shipping a verifier in the Python agent ecosystem (LangChain, CrewAI, AutoGen, LlamaIndex) means a receipt minted anywhere can be verified offline, in the language your agent already speaks.
Publishing (maintainers)
Direct local upload is intentionally unsupported. Create the version-matching
python-verify-v<version> tag from merged main, then manually dispatch
publish-python-verify.yml with the exact typed confirmation and approve the
protected registry-publishing-approval job. The workflow builds twice,
attests the exact wheel and source distribution, publishes through PyPI OIDC,
and byte-compares both registry artifacts.
Apache-2.0.
1 maintainer
Release files for emilia-verify 2.8.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 | |
|---|---|---|---|
| emilia_verify-2.8.0.tar.gz | 84.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| emilia_verify-2.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 146.5 kB
Release files / emilia_verify-2.8.0.tar.gz
| Download URL | emilia_verify-2.8.0.tar.gz |
|---|---|
| Size | 84.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b6bd932bda25ab43e9c9b5841934acc38457f24999ea0c29847aab0f8964ea9
|
|
BLAKE2b-256 checksum How to use checksums |
5604362009f66a212b0cfd4a361c485de80d8407ce882dee1f09d4904d3a24ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency logRelease files / emilia_verify-2.8.0-py3-none-any.whl
| Download URL | emilia_verify-2.8.0-py3-none-any.whl |
|---|---|
| Size | 61.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
83cb225925c6e7756764fc5bb1c416231e458efda2ee4e662c195f8c1fb4ff6a
|
|
BLAKE2b-256 checksum How to use checksums |
a86e6b8d28cb8529ca8522604c795234680fc08fe0e8abcb6e98c1fc695aee50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency log
