We've added two new endpoints for updating projects, providing more idiomatic semantics aligned with HTTP conventions:

• PUT /v1/projects/{projectId} fully replaces a project's settings. Fields that are not provided are reset to their defaults.
• PATCH /v1/projects/{projectId} only updates the fields included in the request, leaving any other settings untouched.

The existing POST /v1/projects/{projectId} endpoint is now deprecated. It will continue to work, but we recommend migrating to PUT for full replacement or PATCH for partial updates.

You can now import X.509 certificates in your Trusted Entities signed with the following key types:

• EC: P-256, P-384, P-521 and secp256k1
• OKP: Ed25519, X25519
• RSA

We've added two new webhook events, that can serve as an additional way to handle certain alerts that would otherwise be sent by e-mail in an automated fashion:

• certificate.renewal.required for when a certificate is due for renewal.
• trustedEntity.etsiLote.update.failed for when an ETSI LoTE update has failed.

We've added activity analytics to the overview page, giving you better insight into how your project is performing.

• View the total number of transactions across your project
• Monitor the success rate of those transactions
• Get a clear visual breakdown of transaction activity over time

These analytics help you quickly understand usage patterns, monitor performance, and identify potential issues at a glance.

Fixed an issue where removing a CSR would remove the associated signing key, even if the CSR already reached the imported status. It now only removes associated signing key if the CSR has not reached the imported status yet.

With this release, we are adding experimental support for ETSI Lists of Trusted Entities (LoTEs).

A LoTE is a digitally signed list of trusted entities, published as part of the European Digital Identity (EUDI) trust framework. Instead of manually adding individual X.509 certificates for each trusted entity, you can point to a LoTE URL and Paradym will automatically fetch the list, verify its signature, and extract the certificates it contains. Read more about how this feature works on our documentation.

This feature is based on standards that are still in development and is therefore experimental. It is subject to change, so please use it with caution.

Fixed an issue where you could link Trusted Issuers from a different project to a Presentation Template using the API.

There have been no cross-project usages.

OpenID4VC Verification sessions now have a new requestRetrieved state, allowing you to react to the user having retrieved the verification request.

This can be useful if you want to hide the deeplink or QR after is has been clicked/scanned, to prevent the user from scanning it multiple times.

The new state value can be subscribed to through webhooks using the new openid4vc.verification.requestRetrieved event. You can read more in the webhooks documentation. If you want to use the new event but only subscribe to specific events for your webhooks, you should update the webhook to also listen to the new request retrieved event.

You can now import X.509 certificates where the hash algorithm uses a different length than the key size. This means you can import an X.509 certificate with a P-256 that is signed using ECDSA with SHA-384 or SHA-512 hashing algorithms. ECDSA certificates signed by Paradym will still always use ECDSA with SHA-256 when using the P-256 key type.

With this release, we are expanding the OpenID4VC Issuance capabilities when using an Attribute Provider. The Attribute Provider can now defer the issuance of a credential, in case it is not ready yet. For more information, please check the Attribute Providers documentation.