Case studies, framework page, no customer exists
The unlinkability implementation described here is unaudited.
This page is a framework, what a real case study will say once one exists, not a set of real deployments, and no company, named or anonymized, stands in for one.
What a real case study will contain
When a design partner signs, a case study here will follow one shape, every time:
- Problem. The buyer's actual re-verification cost before Solidus, sourced from their own funnel or vendor spend, not estimated.
- Integration. How the credential was wired in, hosted capture or direct API, timeline, what changed on the buyer's side.
- Outcome. A measured, sourced verification reuse figure, never rounded, never undocumented.
That's the template, illustrative only: no invented company, no composite customer, no placeholder metric dressed up as a result. It extends credential portability, the Lexicon defines the term; this page doesn't.
Where the real proof lives today
Three things on this site are real, sourced, and checkable now, a better use of your time than a hypothetical:
- The unlinkability demo: a command that runs on a clean machine in
- Reuse economics and pricing, the modeled cost math, shown inline, never a billed number.
did:solidus's registration in the W3C DID Method Registry, and Solidus's DIF Associate Membership, independently checkable, real receipts, not case studies.
See also Solidus vs. Sumsub, a sourced comparison against a named incumbent, not a hypothetical customer.
What changes when a partner signs
The day a design-partner LOI is signed, this page gets rewritten with a real case study and a real proof artifact, at minimum a code or terminal screenshot, the same standard the demo above holds itself to. Not a logo added to an empty template.