You can now issue and request presentation of SD-JWT VCs with nested attributes. This means you don't have to provide all properties top-level anymore, but you can define nested attributes such as user.firstName and address.streetName.

Usage of nested attributes is not supported for Anoncreds credentials and only available through the API for now. You can read more about using nested attributes in the docs.

We have redesigned the invitation page to make it more intuitive and user-friendly. It now includes the branding of the initiator. For example, didcomm invitations will display the branding of the invitation.

We have added support for DIDComm custom messages in the API. With this feature you are able to receive custom messages from agents and send custom messages to agents.

The following APIs and Events have been added:

• DIDComm Custom Messaging API
• DIDComm Custom Message Received Event

We have added support for DIDComm and AnonCreds to the new dashboard and API! In the dashboard you can now create Anoncreds credential and presentation templates, and the new DIDComm APIs allow you to issue, verify, connect and exchange basic messages. All features supported by the Workflow Builder are now available in the API.

The following APIs have been added:

• Anoncreds Credential Templates
• DIDComm Invitations
• DIDComm Connections
• DIDComm Issuance
• DIDComm Verification
• DIDComm Messaging

You can now revoke SD-JWT VCs, allowing you to invalidate a credential after is has been issued. To allow revocation on an SD-JWT VC, you must enable the revocable configuration option (in the dashboard or through the API). You can revoke a credential (or multiple) using the new Batch Revocation endpoint.

Direct issuance of SD-JWT VC

In addition to revocation for SD-JWT VCs, it's now also possible to directly issue an SD-JWT VC without using OpenID4VC as an exchange protocol. You can start issuing SD-JWT VCs directly using the new Issuance API.

You can now use your did:web DID from your profile in for AnonCreds credential templates in the builder. Earlier we released support for using your did:web DID for DIDComm invitations, and with this addition you can now use your did:web for whole the issuance and verification flow of AnonCreds credentials as well.

Read more on using did:web in credential templates in the docs.

You can now use your did:web DID from your profile in DIDComm invitations. This allows external wallets to recognize your DID (as it's a stable cryptographically verifiable identifier), as well as reuse existing connections. External wallets can recognize they already have a connection with your agent, and choose to reuse the existing connection.

Usage of did:web is available in the workflow builder for the didcomm/createConnection, didcomm/createInvitation, didcomm/createCredentialIssuanceInvitation and didcomm/createPresentationRequestInvitation actions, and will soon also be available in the DIDComm API.

Update and archive templates from dashboard

You can now update and archive credential and presentation templates in the dashboard. Templates are not static, and thus you should be able to modify and archive them. We also updated the credential and presentation templates API to archive instead of delete templates. As there's often metadata published to ledgers and credentials issued based on templates, archiving allows for better insights in the history of your project.

When we first introduced multi-project with support for collaborators into Paradym, we enabled the feature for everyone to try it out and see how the multi-project functionality worked in practice.

In the latest update we've limited creating and managing multiple projects, including adding new members to a project, to the Pro and Custom tiers. Any projects that you created will remain active but if you're on the Free tier you won't be able to create new projects, or add collaborators anymore until your account is upgraded. You can always remove members from a project, independant of your current tier.

You can read more on managing projects and collaborators in the documentation.

Due to some issues with the Cheqd testnet we had temporarily enabled writing to the Cheqd mainnet for the Free tier. This has now been reverted, and only accounts on the Pro or Custom tier are able to write to the Cheqd mainnet again. Any DIDs, Schemas and Credential Definitions that have been created on the mainnet during this period can still be used.

Removal of teamId from webhook events

The teamId property has been deprecated for a while with the introduction of projects, and has now been removed from webhook events. You should update your webhook handler to use the projectId property (the value is the same).

We've been working hard on a new dashboard, API and support for OpenID4VC with SD-JWT. You can read more about it in our announcement.

Pricing Changes

We have removed the Showcase tier, and lowered the entry price for the Pro tier to €25. We've also enabled usage based pricing on the Pro tier, allowing Paradym to scale with your needs. See the updated pricing page for more information.

DIDComm DID Exchange protocol updated to 1.1

The https://didcomm.org/didexchange protocol has been updated to version 1.1. DIDComm compliant implementations should handle minor version upgrades without problems, but it may cause some unexpected behaviour if you're not using the Paradym Wallet.