...
- Most established utilities have test networks that are free to use for testing and use case proofing
- Write about Indicio and Sovrin here.
| Utility | Business Requirements: | Technical Requirements | Legal Requirements | Social Requirements | Governance Requirements | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Does the Utility: | Provide client software (or a Software Development Kit) to issue and consume Verifiable Credentials? | Utilize an Open Source license for its core network functionality and/or SDK? | Have a transparent commercial costs model for DIDs anchored to the Utility? | Support native payment flows for Verifiable Credentials? | Have a financial or economic model for the sustainability of the Utility? | Have examples of its use within a Proof of Concept (PoC)? | Have examples of its use within a production environment? | Support Public DIDs, as defined in the W3C DID core specification? | Support W3C Verifiable Credentials, as defined in the Verifiable Credentials Data Model? | Support AnonCreds V1? | Support the storage of credential schemas on ledger? | Support the storage of DID Documents on ledger? | Support Verifiable Credential revocation? | Provide privacy preserving Verifiable Credential revocation? | Have a publicly accessible DID Core compliant DID method? | Support multiple DID controllers in its DID method? | Support Verification Method Relationships such as Authentication and Assertion in its DID method? | Support the retrieval of historic DID states, such as old/rotated Verification Methods? | Have the capability to support multiple wallets and implementations on top of its core functionality? | Provide clear technical documentation for setting up a node on its core Network? | Support GDPR by design (i.e. no personally identifiable information is written to the Utility? | Have a public crisis and contingency policy, in case the Utility enters a period of downtime? | Have a defined legal organization, responsible for the actions of the network? | Utilize a Decentralized Autonomous Organization (DAO) to underpin its corporate structure? | Intend on acting as a trusted network for the European Blockchain Services Infrastructure (EBSI)? | Publicize educational content on how to create/resolve DIDs on the Utility? | Formally support Trust over IP, as a registered Utility? | Have a core team which actively engages in the SSI community? | Support and/or partner with more than 10 SSI vendors? | Engage in initiatives to offset carbon and/or reduce its environmental footprint? | Support open, public participation in governance decisions? | Have a public, transparent governance framework? | Allow the community to influence the product roadmap? | Have an active strategy to achieve a state of sufficient decentralization or censorship resistance? | Have an enforcement policy for counteracting bad behavior on the Network? | Have a forum for Utility-specific discussion for the users and participants? | A governance voting structure, either based on an elected Board or through a more distributed/decentralized voting structure? | Support the use of democratic voting using a governance token? |
| Sovrin | ||||||||||||||||||||||||||||||||||||||
| Bedrock | ||||||||||||||||||||||||||||||||||||||
| Indicio | ||||||||||||||||||||||||||||||||||||||
| KochiOrgBook | ||||||||||||||||||||||||||||||||||||||
| IDunion | ||||||||||||||||||||||||||||||||||||||
| cheqd | ||||||||||||||||||||||||||||||||||||||
| Kilt | ||||||||||||||||||||||||||||||||||||||