Use case
Verified business identity
Evidence of who controls a company, collected once and presented later. The documents stay off the public chain.
A marketplace, a lender, or a payments firm repeats the same ownership checks. The business wants to reuse evidence without republishing it.
When shared machinery earns a place
A credential the holder can present to many verifiers, with revocation, is a real design. A public commitment to a status list can be part of it.
When it does not
Putting the registry extract, the passport, or the beneficial-ownership file on a public chain is the wrong design. One firm checking its own customers can stay on a conventional case tool.
Conventional-first
Case management, evidence vault, retention schedule, access log.
No reuse by other firms. Simpler duty of care.
Hybrid
Issuer, encrypted vault, verifiable credential, status list, policy engine. Chain only for a status commitment if it earns its place.
Issuer key management becomes critical. Liability for a wrong credential does not vanish.
On-chain-native
Do not build this option for the files. A public registry of personal or corporate documents is a data breach with extra steps.
Rejected by this constructor as a default.
Patterns
Components
- Spruce SSIGreen — compatible use if you keep the notices
- walt.id IdentityGreen — compatible use if you keep the notices
- Kubo (IPFS)Amber — conditions, and a legal review before you copy it in
Questions a person still has to answer
- Who is allowed to issue?
- What is the retention period?
- How does a subject correct a claim?
- Which fields are inside the credential, and which stay as a private link?