Roadmap (copied here from google doc)
The SSI concept appears to be one of the most prominent identity technologies. The main goal of SSI is to shift the locus of control over users’ data and authorization function. It gives back the power of profile control to people while preserving a prominent level of privacy and security. Trust triangle, which is the core of the SSI ecosystem, presumes that the User holds privately its own verifiable credentials issued by authorized actors (Issuers). This credentials are accepted and verified by Verifiers which check-up the Issuers signature and decentralized identifier of the User.
Various consortiums and state authorities have paid attention to the SSI development and have already undertaken certain actions to set up a proper agenda and to hold the best positions at the frontier of technology.
Being technology-agnostic the SSI, however, perfectly fits any blockchain ecosystem due to its decentralized and trustless character. Blockchain networks can perform the role of decentralized virtual machine for SSI-based smart contracts or even store the data of certain SSI components.
A Plan for FreeTON Community
Numerous blockchain ecosystems have already entered the SSI adoption race by promoting the development of basic SSI components. We strongly believe that the competitiveness of any blockchain ecosystem depends on the level of its mass adoption. SSI can become a game-changer. In connection with useful Telegram UX the SSI can become a Passport 2.0 with the ecosystem of credential providers and verifiers.
There is no doubt that open ecosystems stand on good standards that are open to the community. Hence, it is a necessity to develop a bunch of open-source projects that will correspond to the main components of SSI.
Therefore, we propose a X-step plan for the FreeTON community. While Step 1 is definite quite, Steps 2 and following might be expanded or slightly changed with moving on the roadmap.
Step 1. Decentralized Identifiers. Specification + DID Storage + DID method implementation + Use case (demo app)
This step sets up the work on the SSI ecosystem. Decentralized identifier is the basic component for each and every user flow. To start interacting with Issuers and Verifiers, the Holder must identify himself by creating an identificator that will reference it. This step must include
- A detailed specification for DID methods, DID Document and the description of DID resolver.
- A prototype of a smart contract that will perform the role of DID storage.
- Demo application showcasing DID creation, resolution, deactivation functionality
- IPFS module for DID Document storing.
- Gas consumption explanation.
This step must be finalized with a web2 prototype that simulates a real SSI use case but employs a DID module for authorization purposes. The use case must be practical and attempt to solve a real problem.
- A prototype of the use case with implemented DID component
- Documentation (how to reproduce locally)
- Source code on GitHub
Terms: 1-2 months
Step 2. DID SDK + API
This step proceeds with the development of DID components. This step must include:
- DID controller for key rotation and its deactivation.
- SDK + Documentation + Tests
- Governance system & Upgradability
Terms: 1-1.5 months
Step 3. DID Resolver and FreeTON ID API
This step includes DID server-side implementation. Additionally, the Universal Resolver must be delivered. The step must include:
- DID universal Resolver. Resolver application packed into Docker container compatible to specification (Decentralized Identifier Resolution (DID Resolution) v0.2) and published to https://resolver.identity.foundation/
- Free TON ID API, web service for dealing with DIDs.
- Universal resolver + Documentation + Tests
- DID management use case web service
Terms: 2-3 months
Further Steps for SSI Development
Step 4. Verifiable Credentials SDK + TON DID Method (with support)
This step implies the development of the extended SDK for TON DID and VC SDK. This components are necessary to involve Issuers and verifiers in the process of credential exchange and start to pilot first MVPs in the FreeTON ecosystem. The SDKs must include:
- VC issuance toolkit (timestamping; reference to Issuer’s DID).
- VC onchain revocation.
- VC verification
- Generation of Verifiable Presentation
Step 5. Verifiable Data registry. Revoke. Schema registry
This step proceeds the involvement of the ecosystem by creating certain registries that are necessary to build trust across the ecosystem.
- Verifiable Data Registry to store metadata and enable trust flow in SSI applications
- Onchain registries for W3C VC Issuers, Revoked Credentials and verifying VCs.
Step 6. Issuer Registry + Reputation System + Crypto economic model
This final step presumes a certain level of the technology maturity. At this stage we might see several MVPs employing SSI technology. However, to create a functional ecosystem it is necessary to implement various governance mechanisms that will create proper incentives for the participants. The step must include:
- The linkage process of Issuers’ DID and Holders’ VCs.
- A prototype of a reputation system for the SSI prototype based on VCs.
- A concept of crypto economic incentivization for the Trust Triangle participants