Skip to content

v1.4.0
Compare
Choose a tag to compare
@tmarkovski tmarkovski released this 18 Mar 17:51
· 773 commits to main since this release
v1.4.0
95ac9c2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

This release introduces our Ecosystems feature that allows you to create a custom ecosystem and onboard participants. Each wallet created is now scoped to a specific ecosystem. By default, the global trinsic ecosystem will still be used when creating a wallet if a custom ecosystem isn't specified.

Ecosystems are identified by a unique name that is passed during the process of registering for an ecosystem. These names are globally unique and will be bound to the email of the person that registers the ecosystem. For testing purposes, you can also create anonymous ecosystems without specifying an email or name, at which point we'll randomly generate a name for your ecosystem.

To create new ecosystem use the ProviderService.CreateEcosystem endpoint.

To create a wallet or sign in to one within an existing ecosystem, pass the ecosystem name or id to the AccountService.SignIn endpoint.

Breaking Changes

  • Most endpoints will now use a single request/response object, instead of language specific types. This mostly affects the endpoints in the credential service.
  • The endpoints CreateEcosystem and SignIn now return a auth_token (string) which can be saved and passed back to the user via the service options
  • You can now use the CLI to generate an API token for use with your server, and pass that token in your configuration. The CLI stores its data in ~/.trinsic/config.toml file. Please remove any previous configurations of the CLI, as they will not work with the new version.
  • The ServiceOptions used to configure services now accept AuthToken field
  • The endpoint to CreateProof in CredentialService doesn't require passing a RevealDocumentJson. If empty, one will be automatically generated from the input proof. Additionally, this endpoint now supports passing either a ProofDocumentJson or ItemId to use for proof creation. This allows users to create proofs without first storing the proof in the wallet.

API Versioning Clarification

This is still a "rolling beta" release model. As such, the first production version will be v2.0.0. While semantic versioning does not allow for breaking API changes in minor versions after 1.0.0, Trinsic currently has an existing system in production that we consider as v1. This development is therefore considered "v2". This is why our target first production release for Ecosystems will be version 2.0. Until v2.0 is released, please assume that this is a 0.X.Y release, and breaking changes can (and sometimes will) be published. Trinsic will clearly communicate these breaking changes in advance and work to mitigate any impact.

SDK Contributions

Full Changelog: trinsic-id/sdk@v1.3.0...v1.4.0

Contributors

tmarkovski, sethjback, and 6 other contributors
Assets 16
Loading