The past month has been full of product updates and improvements. This blog post will introduce new features like support for passkeys, did:web, Ed25519 signatures, wallet pass integrations and a number of exciting experiments happening in the Trinsic Labs.
Passkeys for wallet authentication
We’ve added support for passkeys within our wallet infrastructure. Providers can now expose passkeys as a login option for their customers, rather than using a one-time passcode. Major browsers like Safari and Chrome natively support passkeys and we expect adoption to continue to grow due to the security and user experience benefits.
Right now this feature is in beta and only available on paid plans. If you’d like it enabled for your ecosystem, please get in touch.
did:web + Ed25519 signatures
New wallets created within Trinsic ecosystems now have a did:web identifier rather than using did:key as we used before. This change allows us to support additional signing keys to provide developers a more flexible and interoperable platform. We’ve incorporated Ed25519 signatures, a NIST-compliant curve and when you visit the DID Document for a given identifier you’ll see both key types listed.
If you log into your dashboard, and add a wallet, you’ll be able to see that wallet’s DID. Copy that DID, paste it into your browsers search bar. To view the DID document, remove the “did:web:” prefix, swap out the final “:” for a “/” and add “/did.json” to the end of the string.
Google and Apple wallet
You can now add a verifiable credential to the Apple and Google wallets directly from the Trinsic White-Labelled Wallet. This feature is only available to teams on our Build or Launch tier and can be configured in your Dashboard settings.
Our team has been busy with a set of experimental features and demos that will promote wider adoption of verifiable credentials. We have two recorded videos from the Trinsic Labs this month. We’re eager to gather feedback on these prototypes, so if you want a personalized demo on how you could implement these features in your ecosystem.
AI Agent Demo
When trying to use an AI agent to book a trip to Oregon in May, our CEO realized that there was no good way to share information like login credentials, loyalty numbers, or other private data. The AI agent’s usefulness was limited by its lack of context, so we built a way for an AI agent to interact in a private and secure way with a digital identity wallet.
You can watch Riley’s demo video or visit our page about AI agents to see how an LLM can request certain private information from the user’s digital wallet, the user consents to sharing the information, and the workflow continues.
The goal of CHAPI integration is to enable interoperability by allowing users to choose which wallets to use to hold their credentials and verify them. The end state is that credentials issued by Trinsic could be accepted and held from any CHAPI-compatible wallet, and that any CHAPI compatible wallet could present credentials that could be verified through Trinsic. Check out Josh’s to see the early versions of our CHAPI integration.
The team has been hard at work shipping platform updates to make verifiable credentials easier to access for users, more interoperable for teams, and more ready for mainstream adoption. The future is bright, and if you’d like to work with Trinsic to bring your identity product to market, set up a today.