Start here
SDK-Rust is the generic Rust foundation shared by Identus ecosystem products. It is not a wallet application, blockchain SDK, cloud service, or umbrella that automatically owns every SSI protocol.
Ownership rule
Reusable, chain-neutral domain primitives, cryptographic utilities, protocol engines, ports, validation, and conformance evidence belong in SDK-Rust. Method, ledger, runtime, custody, consent, trust, persistence, user experience, deployment, and certification policy remain with their owning downstream.
That distinction allows Midnight Identity, NeoPRISM/Cardano, Lace ID Portal, Oxid, and future products to share foundations without forcing one chain or product model into the others.
Maturity vocabulary
| Term | Meaning here |
|---|---|
| Implemented | Code and tests exist; the public surface may still change. |
| Candidate | A reproducible artifact is available for review; publication status is proven only by its registry receipt. |
Experimental 0.x | SemVer applies with an explicit migration policy and support window. |
| Supported | The documented compiler, targets, features, and support period are an effective promise. |
| Certified | An external assessment or certification exists; tests alone never imply this. |
The first three packages—identus-derive, identus-core, and
identus-crypto—are release-activated 0.1.0-rc.1 packages. The independent
identus-did and identus-did-resolver-http train is candidate-only: its
release-shaped archives are prepared in an isolated temporary workspace, but
its canonical manifests remain version 0.0.0 with publish = false. Every
other workspace package remains 0.0.0, unpublished, and outside either
candidate closure.
Branches
developis the protected integration and documentation source.mainis intentionally reserved and is not populated by site publication.- Releases require a separately approved exact revision and protected process.
For the repository-level contract, see Governance, constraints, and the release policy.