The Parachain team has another round of testing completed on the bi-directional token bridge for Litentry Parachain. The plan is to go live with the functionality this month. However, due to the last event of the token bridge being exploited, we will monitor the bridge intensively and do extensive testing with our partners before releasing the bi-directional bridge to the public. Twitter and Discord identity verification functionality is now in a testing phase. The team put extra thought, effort, and functionality, 3rd party timeouts, and system problems into how we can handle multiple async Identity Management Pallet requests. This functionality is being merged this week. The shielding key problem has been resolved. This was a significant blocker. However, we can allow our UI to communicate securely with our Parachain and TEE Enclave.
Work in progress: Ongoing research for creating a local and secure module for storing the user’s shielding key. The shielding key is used to encrypt and decrypt the communication messages between the Parachain and the user. Ongoing work for Polkadot updates and the Graph team
We have started converting the Identity Linking feature planning into actions and deploying Identity Hub to production for the staging phase. Staging environments are important and are made to test codes, builds, and updates to ensure quality under a production-like environment before application deployment. Everything in a staging environment should be as close a copy to the production environment as possible to ensure the Identity Management Pallet and VC communicate correctly. The products documentation for IDH Quest & Task Participation is ready for review, including the following features:
- Quest Participation (IDHCS)
- Quest Display (IDHCS)
- VC Generation + Sharing (IDHLS)
- Make VC Request To IDHLS
- Initiate VC Generation Extrinsic To Parachain (IDHLS)
- Receive VCs From Parachain (IDHLS)
- Share VCs (IDHLS)
- VC Generation Event Queue (IDHLS)
- VC Verification (IDHCS)
- Tracker (IDHCS)
The new MCP UI has been deployed, and it will be merging into the upcoming IDH.
Litentry is a Decentralized Identity Aggregator that enables linking user identities across multiple networks. Featuring a DID indexing protocol, and a Substrate-built distributed DID validation blockchain, Litentry provides a decentralized, interoperable identity aggregation service that mitigates the difficulty of resolving agnostic DID mechanisms. Litentry provides a secure vehicle through which users manage their identities and dApps obtain real-time DID data of an identity owner across different blockchains.
Stay in touch with us through
Following us on Twitter
Technical discussion on Github
More information on our Website