Milestones

List view

• A2 — Portable DID platform

  Deliver generic DID adoption seams, explicit peer DID profiles, portable PRISM CRUD/state reduction, and bounded PRISM VDR/indexer capabilities. Concrete Cardano clients, persistence, services, and node runtime remain downstream. Exit requires method vectors, quality evidence, target receipts, and immutable SDK-TS/NeoPRISM adoption and rollback packets.

  No due date

  •0/6 issues closed
  0% complete6 open0 closed

• M5 — DID SDK consumable release candidate

  Prepare an engineer-reviewable, deterministic, non-publishing 0.1.0-rc.1 candidate for exactly identus-did and identus-did-resolver-http. Decide collision-free multi-train tag identity, preserve the first crypto train, prove API/package/dependency/target/source evidence, and retain chain-neutral boundaries. Publication, crates.io settings, DID methods, chains, UniFFI/WASM package publication, and downstream repository mutation require separate authority.

  No due date

  •6/10 issues closed
  60% complete4 open6 closed

• M3 — Crypto SDK 0.1.0-rc.1 approval

  Engineer-review milestone for the first isolated identus-derive, identus-core, and identus-crypto release candidate. Documentation publication, downstream adoption, compiler/support policy, namespace ownership, exact-SHA slow evidence, and two-person release approval are required. This milestone does not itself authorize crates.io publication.

  No due date

  •8/11 issues closed
  72% complete3 open8 closed