Since before Trinsic even began, we were major contributors to various open source decentralized identity projects, the primary one being Hyperledger Aries. In fact, I became a main contributor to the Aries Framework .NET, a mature self-sovereign identity (SSI) agent codebase for the .NET Core runtime, and our CPO Michael Boyd is an original contributor to the first open source Python agent, which helped launch the Aries project. As a company, Trinsic is still contributing to these efforts, and we’re excited to announce our next major contribution.
We are excited to announce that we have contributed an out-of-the-box cloud agent controller for Aries Framework .NET accessible via an OpenAPI. Before this contribution, the Aries Framework .NET, although a feature-rich codebase, required configuration to assemble a useful agent service. This contribution brings Aries Framework .NET into parity with other Aries codebases which expose an API for developers to interact with. Now, building Aries-based cloud agents will be easier than ever.
Interoperable decentralized identity
Hyperledger Aries provides libraries, frameworks, and protocols for developers to implement verifiable credentials that are interoperable across any ecosystem or method that supports DID communications (DIDComm). Standardization of DIDComm is done at the Decentralized Identity Foundation and is used by decentralized identity ecosystems across the board.
Dozens of organizations, especially enterprises, use the Aries Framework .NET for various SSI projects across different business domains, especially mobile wallets. The foremost user of the framework is Trinsic—our entire product stack is based on Aries Framework .NET.
The addition of the OpenAPI
With the addition of the OpenAPI, consumers of Aries Framework .NET in a cloud environment no longer need to spend time building their own controllers or APIs to access the functionality therein. Instead, they can use the OpenAPI included in the repo to speed up the development process significantly.
The ASP.NET core sample project has been updated to show how easy it is to add the OpenAPI endpoints to your .NET project. By just adding a few lines of code into your
Startup.cs file, your project will support the primary SSI use cases of issuing credentials, verifying credentials, making connections, etc.
The Trinsic platform
We’re passionate about building an amazing developer experience—it’s why Trinsic is the fastest-growing decentralized identity company in the world, with hundreds of developers trusting the platform. While the open source Aries Framework APIs must expose a great deal of complexity in order to be runnable on all platforms, accommodate all use cases, and remain unbiased with regard to implementation details, the Trinsic APIs cut out all the complexity to create the best developer experience possible.
As a cloud-native managed service, we’ve taken special care to ensure stability, security, and scalability. And best of all, it’s free to get started—just pay by usage once you start to scale.
Trinsic supports three APIs you can integrate free and provides robust documentation and support for each.
- Provider API: Our newest and most powerful API enables developers to programmatically provision issuer and verifier cloud agents. Learn more about the provider API in the recent launch announcement.
- Credentials API: Our original API enables developers to have a turnkey way to issue, verify, and manage verifiable credentials on any Hyperledger Indy network. Check out our documentation or one of our reference applications to get started.
- Wallet API: An API for creating and managing cloud wallets on behalf of credential holders. It’s the backend of our Mobile SDK, which you can read more about in our recent post about building your own SSI wallets. Get started with the API by checking out the documentation.