Refining Transmute ID for Logistics
February brought rapid ideation and development for the Transmute team. We are continuing to build the bridge between centralized and decentralized systems by focusing on high-value applications of hybrid identities and verifiable credentials to business workflows.
We completed dozens of new customer discovery interviews this month, mapping our core feature set to established enterprise workflows and pain points. The crux of these interviews continues to center around improved tracking and easier communication for logistics companies (Shippers, Brokers, 3PL, Carriers, and Drivers).
Below is an example workflow, adapted to demonstrate driver credential attestation with Transmute ID (communication between a subject/holder and issuer). We are currently refining corresponding interfaces and integrations to support user-managed storage, secure messaging, SMS notifications, and administrative control of workflow configurations.
Through these discovery sessions, we’ve also confirmed that our data model and base features map easily into many other verticals, including telecommunications. For instance, Transmute ID can help a telcomm company quickly confirm a business identity, making the process of setting up a company phone line faster, safer, and more transparent.
Technical Update
Our engineering team is using these workflows to solidify a secure and flexible data model and essential UI elements.
Transmute ID
Transmute has continued to fine-tune our Supply Chain Workflow instance of Transmute ID, working in parallel to add support for PII disclosure, public ledger DID standards like ethr-did [most notably used by the team at UPort], as well as refining the experience around credential creation, attestation and workflow authorization. Additionally, we’ve been refactoring our backend to be even more generic to ensure we can leverage the same API and data model we’re using to help supply chain companies to address similar challenges in other industry verticals.
Regarding our commitment to our customers to support vendor optionality, we built a functional proof-of-concept integration with Oracle Blockchain Platform, extending our support from Ethereum to include HyperLedger.
We’ve also began testing and development for OpenFaaS, to scale Transmute ID while remaining free of vendor lock in and as portable as possible for our customers. Shoutout to Alex from OpenFaaS; he has been super helpful here, and we’re excited to leverage OpenFaaS on Kubernetes to achieve enterprise scale with Transmute ID.
Github DID
We released a few updates to our testing and development tool, Github DID. These included a Slack authenticated encryption PoC, and a web app demo for authenticated encryption and signing and verifying with OpenPGPSignature2019 Linked Data Signature Suite, which we are developing as a proposal for the W3C. We have a few more documentation updates to make, but are getting ready to move Github DID to the DIF; stay tuned for more on that later.
Sidetree Ethereum
We made some major contributions to Sidetree Ethereum, including rewriting it in TypeScript to be more like its Bitcoin sibling, an effort currently spearheaded by Microsoft — a fellow DIF member. We also completed the architectural work needed to prepare a branded DID Method built on Sidetree to be supported by Transmute. You can read more about the progress of Sidetree here.
We are completing the technical and implementation foundation for our pilot participants in the logistics space. If you would like to receive information about our upcoming pilot please email us at info@transmute.industries.
