affinidi-tdk

The unified entry point for the Affinidi Trust Development Kit. Depend on this single crate and enable feature flags to pull in only the libraries you need.

Disclaimer: This project is provided "as is" without warranties or guarantees. Users assume all risks associated with its deployment and use.

Installation

[dependencies]
affinidi-tdk = "0.8"

Feature Flags

Every published capability crate is reachable through a facade feature. Group features (e.g. credentials, protocols) enable a whole layer; the individual features let you pull in just one crate. The * re-export column is the module name the crate is re-exported as (e.g. affinidi_tdk::vc).

Use the facade or direct sub-crate deps, not both. Mixing affinidi-tdk with a direct dependency on a crate it re-exports can resolve two copies of that crate. Foundation crates (affinidi-crypto, affinidi-tdk-common) are pinned at major.minor (caret), so any compatible patch resolves to a single version within the facade's tree.

Disable defaults with default-features = false in your Cargo.toml or --no-default-features on the command line, then enable only what you need:

[dependencies]
affinidi-tdk = { version = "0.8", default-features = false, features = ["credentials", "protocols"] }

Re-exported Crates

This crate re-exports the following libraries:

• affinidi-did-resolver-cache-sdk — DID resolution and caching
• affinidi-did-common — DID Document types
• affinidi-messaging-didcomm — DIDComm protocol
• affinidi-messaging-sdk — Messaging SDK (feature: messaging)
• affinidi-meeting-place — Meeting Place SDK (feature: meeting-place)
• affinidi-data-integrity — Data Integrity proofs (feature: data-integrity)
• affinidi-did-authentication — DID authentication
• affinidi-tdk-common — Shared utilities
• affinidi-secrets-resolver — Secret management
• affinidi-crypto — Cryptographic primitives

Examples

Runnable examples live in examples/ and import only through affinidi_tdk::* — they are the canonical onboarding pattern (never depend on a sub-crate directly):

• did_auth — authenticate a DID against a service endpoint.
• resolve_did — resolve a DID and print its document.

cargo run -p affinidi-tdk --example resolve_did -- did:key:z6Mk…

Contributing: new capability crate ⇒ new facade feature

When a new published capability crate is added to the workspace, it must be made reachable through this facade in the same change:

1. Add it as an optional = true dependency (path + major.minor version).
2. Add a dep:-gated feature for it (and fold it into the relevant group feature — credentials / protocols / did-methods).
3. Re-export it under a #[cfg(feature = "…")] in src/lib.rs.
4. Add a row to the Feature Flags table above.
5. Extend the facade feature-matrix CI job.

Related Crates

• affinidi-messaging — Full messaging framework
• affinidi-did-resolver — DID resolution

License

Apache-2.0