2.5.0

We‘ve migrated the DID driver to the latest SDK version, leveraging its built-in DID resolution capabilities.
This comes with upgrades to some other important dependencies, including node and the @polkadot/api packages.

What's Changed

• chore(deps): bump json5 from 1.0.1 to 1.0.2 by @dependabot in #40
• deps: upgrade sdk to v0.35.0 by @rflechtner in #41
• chore: update license by @rflechtner in #46
• deps: use node v20 by @rflechtner in #47

Full Changelog: 2.4.2...2.5.0

2.4.2

Dependencies update and a brand new KILT JSON-LD context

This patch release contains a few dependencies upgrades, and more importantly the new KILT DID JSON-LD context!

What's Changed

• chore(deps): bump minimist from 1.2.5 to 1.2.6 by @dependabot in #32
• chore(deps): bump semver-regex from 3.1.3 to 3.1.4 by @dependabot in #33
• chore(deps): bump node-fetch from 3.1.1 to 3.2.10 by @dependabot in #34
• chore(deps): bump qs from 6.5.2 to 6.5.3 by @dependabot in #36
• chore(deps): bump express from 4.17.1 to 4.17.3 by @dependabot in #37
• chore(deps): bump minimatch from 3.0.4 to 3.1.2 by @dependabot in #38
• feat: add new DID context definition by @ntn-x2 in #39

Full Changelog: 2.4.1...2.4.2

2.4.1

Automatic Handling of Runtime Upgrades

We improved the driver's capability to handle runtime upgrades, allowing it to automatically support new features when available in a new runtime, e.g., web3 names.

Full Changelog: 2.4.0...2.4.1

2.4.0

Support for Web3Names & Docker Optimisations

• This release adds support for the new Web3Name feature soon to land on the KILT spiritnet, adding Web3Names to the Did Document where available. It is backwards-compatible with chains that do not yet offer this feature. Have a look at the driver specs for further information.
• We have also optimised the docker builds to reduce clutter and non-required dependencies.
• Finally, we have added a docker-compose file that simplifies testing the driver on a local environment.

Full Changelog: 2.3.0...2.4.0

2.3.0

Better support for the Accept HTTP header.

• For application/json and application/did+json, the return type is application/did+json and only contains the resolved DID document in JSON form.
• For application/ld+json and application/did+ld+json, the return type is application/did+ld+json and only contains the resolved DID document in JSON-LD form.
• For application/ld+json;profile="https://w3id.org/did-resolution", the return type is application/ld+json;profile="https://w3id.org/did-resolution" and contains the resolved DID document in JSON-LD form plus the document and resolution metadata.

For more information, please refer to the DID Resolution Result and DID Resolution HTTP Bindings specs.

2.2.0

Switch away from Base64 encoding/decoding for light DIDs to using Base58 following the multibase format.

For more info, refer to the KILT DID method specification.

2.1.1

Fix for a bug in the driver happening when a light DID contains details that, when Base64-encoded, contains the / character, resulting in the application truncating the input DID and consequently failing to resolve it.

2.1.0

Minor updates for better handling of the Accept HTTP header content.

KILT Spiritnet

This release updates the DID driver to work with the KILT chain "Spiritnet" on the Kusama blockchain.
Driver version: 2.0.0
Spec version 1.0.0

Some error checks

• check if we receive an error from the prototype services