This release is a pre-release and may not be stable for production use.
tba-protocol-zcap
ZCAP-LD v0.4.0 delegation and HTTP invocation signing and verification for the TBA Ed25519 development profile.
Use ZcapRoot to configure a trusted local root and sign_delegation
to grant a controller restricted actions at a target. A signed delegation
embeds its immediate delegated parent and references older ancestors by ID.
Use sign_http_invocation to present a root by ID or a leaf delegation as
gzip-compressed, base64url-encoded JSON.
Configure ZcapVerifier with a trusted local root lookup, an Ed25519 key
lookup, a revocation check, and a TBA replay reservation provider. The key
lookup takes the controller, verification method ID, and required proof
purpose. Return a key only if the method is authorized for that controller
and purpose. The revocation check takes the root and delegated capability IDs.
Supply the operation's trusted root, method, target, and action to
verify_invocation, then dispatch using the verified request.
Delegation proofs use eddsa-jcs-2022. The verifier hashes the canonical
proof options and the canonical unsigned document separately, then checks
the Ed25519 signature over their concatenated hashes. The two fixed
JSON-LD contexts are checked locally. This suite uses JSON canonicalization
and needs no remote context fetching or RDF canonicalization.
The HTTP profile uses one RFC 9421 signature named zcap. It signs the
method, full target URI, Capability-Invocation field, SHA-256 Content-Digest,
and Content-Type when present. The application supplies the externally
effective URL and unmodified body. Preserve repeated headers so the verifier
can reject duplicates. Each signature includes a creation time, an expiry,
and a nonce. Use shared atomic replay storage for a multi-worker deployment.
The profile accepts one controller per capability, explicit action restrictions on delegations, simple HTTPS paths without query strings, and up to eight delegated capabilities. It uses this exact Capability-Invocation field syntax for root and delegated invocations, respectively.
zcap id="<root-id>",action="read"
zcap capability=<base64url-gzip-json>,action="read"
This is a bounded profile. It does not implement JSON invocation proofs, arbitrary JSON-LD contexts or caveats, query attenuation, or a revocation endpoint.
- ZCAP-LD v0.4.0
- W3C EdDSA Data Integrity suites
- RFC 9421 HTTP Message Signatures
- RFC 9530 Digest Fields
Quick start
Build the package from the repository root.
uv build --wheel pkgs/50-protocols/tba-protocol-zcap
Verification
Check that the build produces a wheel with the package version declared in pyproject.toml.
Metadata
Release files for tba-protocol-zcap 0.4.0.dev2
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 |
|---|---|---|---|---|
| tba_protocol_zcap-0.4.0.dev2.tar.gz | 10.8 kB | Without provenance | Details for tba_protocol_zcap-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_protocol_zcap-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_protocol_zcap-0.4.0.dev2-py3-none-any.whl |
Total release size: 23.1 kB
Release files / tba_protocol_zcap-0.4.0.dev2.tar.gz
| Download URL | tba_protocol_zcap-0.4.0.dev2.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb520839901bd0078a7697c66b94fef6cd99e47a14fba03ff12ccf34ea7b73de
|
|
BLAKE2b-256 checksum How to use checksums |
a32ddcee8168720f15f9e76eec4d27dcf52d8ef6aecaba8dad16a932cbf5fd72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tba_protocol_zcap-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_protocol_zcap-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f8ff3992c66941973b339f8ddf4daa758a0cababa8c77ee56e498eb51fcae41
|
|
BLAKE2b-256 checksum How to use checksums |
5744009abbcb260d59711cdbbdc2a75c4c8dcf8b700a60afa72658e96bbed001
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tba-protocol-zcap 0.4.0.dev2
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.