Release 4: Barnard’s Star
This release we focused on expanding the identity system we rely on to support our platform. This application — we call it Transmute ID — will also function as an freestanding identity product. It is a combination of decentralized identifiers built on open standards, a user dashboard and cloud wallet to facilitate usability, a decentralized “identity hub” to support access permissions, and API compatibility with centralized identity providers. Enterprise organizations can also seamlessly track activity and demonstrate compliance with user requests through an immutable audit log.
Transmute ID is still under development, but we have taken the foundational elements of our previous identity work and begun to rework them into an application which supports rapid development and can integrate with our platform as we start to support user interfaces for our platform components.
We have also continued to invest significant time and energy into in-depth product and user research to better understand the specific pain points enterprises currently face around identity and access management. Our team spent time interviewing privacy professionals at the International Association of Privacy Professionals Privacy Security Risk conference, including many CPOs dealing with regulations like GDPR and the new California Consumer Privacy Act. We also spoke with DApp developers and vendors at the HoshoCon Blockchain Security conference. We are continuing to narrow in on early adopters of blockchain identity solutions.
A deeper dive into progress this month…
Decentralized Identity
We’ve implemented the cryptographic primitives for working with decentralized identities, and are preparing to begin work on new initiatives which we have researched and architected over the last month.
Transmute Cloud Wallet
We are building a cloud wallet geared towards helping users transition from centralized to decentralized identity with particular support for the decentralized identity standard and identity hubs. This cloud wallet will hold private keys on a users behalf. In the future, users will have the option to hold their own private keys if they would like to do so.
Decentralized Identity Hub
It’s important to separate cryptographic interfaces form business logic and PII. We’re working to design libraries and services to support permissioned access to user data while supporting the decentralized identity standards. More on our take on identity hubs coming soon.
Overall the past month has been filled with intensive research, design and architecture, as well as some UI work (demos coming soon!) and library work to support decentralized identity.
