This release is a pre-release and may not be stable for production use.
tba-protocol-ucan
UCAN delegation and invocation signing and verification for the TBA Ed25519
development profile. The wire tags are ucan/dlg@1.0.0 and ucan/inv@1.0.0.
This profile supports bare Ed25519 did:key identifiers, canonical DAG-CBOR
with integers in the interoperable 53-bit range, linear proof chains of up to
16 grants, finite expiries, and equality predicates on top-level arguments.
Invocations have a maximum remaining lifetime of five minutes. The profile
rejects unsupported algorithms, fields, and policy operators. It covers a
subset of the UCAN specifications.
Verifying a call
Use sign_delegation and sign_invocation with the issuer's Ed25519 private
key. Index signed delegations with content_id and list their CIDs in
UcanInvocation.prf from root to leaf. Configure UcanVerifier with a
proof lookup, a revocation check, and a TBA replay reservation provider.
Call verify_invocation with the trusted subject, the local executor, and the
expected command. Dispatch the command with the arguments in the returned
invocation. The verifier checks every delegation's policy against those
arguments and atomically reserves the invocation CID before returning.
The caller supplies the mapping from trusted subjects and commands to local resources. A deployment with multiple workers needs a shared replay store with atomic reservations. Revocation storage is supplied by the caller.
Wire codec
DAG-CBOR produces deterministic binary bytes for the signed map. The verifier rejects duplicate keys, noncanonical encodings, and values outside the profile. Varsig is the header inside that map identifying Ed25519 and DAG-CBOR. The signature covers both the header and the versioned payload.
A CID identifies the complete signed envelope. Its binary representation contains CIDv1, the DAG-CBOR codec code, the SHA-256 multihash code and length, and the digest. The text form uses base58btc. In the invocation proof list, each CID is a DAG-CBOR tag 42 link with a leading zero byte followed by the binary CID. The verifier recomputes the CID of every resolved proof before accepting it.
Quick start
Build the package from the repository root.
uv build --wheel pkgs/50-protocols/tba-protocol-ucan
Verification
Check that the build produces a wheel with the package version declared in pyproject.toml.
Metadata
Release files for tba-protocol-ucan 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_ucan-0.4.0.dev2.tar.gz | 7.1 kB | Without provenance | Details for tba_protocol_ucan-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_protocol_ucan-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_protocol_ucan-0.4.0.dev2-py3-none-any.whl |
Total release size: 16.7 kB
Release files / tba_protocol_ucan-0.4.0.dev2.tar.gz
| Download URL | tba_protocol_ucan-0.4.0.dev2.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
841147709fc52e8aedcb206a7a07a67322e7fd11b92dba877f3e927fe0fc6ecc
|
|
BLAKE2b-256 checksum How to use checksums |
c1121a1046c1e7de7f08f317fc5e01801f46282a17dd300ff1583011722d6455
|
| 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_ucan-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_protocol_ucan-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d88068194f0bdade026ae1630c0cd45fc8e2d570863f3267ff48cc310cdbc90a
|
|
BLAKE2b-256 checksum How to use checksums |
68305dd4ba7560d08e21fd9f68f7baec6cd03d25023b2206cdd03f5aa83d4c23
|
| 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-ucan 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.