DIDKit header

What is DIDKit?#

DIDKit provides Verifiable Credential and Decentralized Identifier functionality across different platforms. It's written primarily in Rust due to Rust's expressive type system, memory safety, simple dependency web, and suitability across different platforms including embedded systems.

DIDKit supports the following high level use cases, with more to be added shortly:

What does DIDKit include?#

DIDKit ships with a command line tool and HTTP service. The HTTP service aims to comply with HTTP-VC-API.

Through cross-compilation and linking through C ABIs, DIDKit also supports other platforms through SDKs for:

Although support across different platforms is in its early stages, we will continue to add new platforms and improve interface ergonomics over time. For platforms that do not currently have SDK support, the HTTP API and command line tools are readily integrated.


In this quickstart, we will build and run the command line tool along with the HTTP server.


  • GNU/Linux or MacOS, not yet tested on Windows.
  • Rust nightly (rustup default nightly)

Building didkit (we are working on crate packaging):

$ git clone https://github.com/spruceid/ssi --recurse-submodules
$ git clone https://github.com/spruceid/didkit
$ cd didkit/
$ cargo build

Using didkit CLI (Github documentation)
Read more about CLI Commands here

$ ./target/debug/didkit -h
$ ./target/debug/didkit generate-ed25519-key > key.jwk

Using didkit HTTP server (Github documentation)
Read more about HTTP Commands here

$ ./target/debug/didkit-http -k key.jwk
Listening on

Please see the installation instructions for more detailed steps or how to use containerized builds. The CLI and HTTP related pages in the examples section will demonstrate how to issue and verify Verifiable Credentials and Verifiable Presentations.


The core featureset of DIDKit is expanding steadily over time and in the open, so feel free to engage with the repository directly on github. Currently, DIDKit currently supports the following features:

  • Key generation and handling.
  • Issuance and presentation of W3C Verifiable Credentials in JSON-LD, signed by a local and/or passed key.
  • Verification of W3C Verifiable Credentials in JSON-LD.

DID Methods supported so far:

  • did-key
  • did-web
  • did-tezos
  • did-ethr (implicit only)
  • did-sol

Proof types verifiable so far:

  • RSASignature2018
  • Ed25519VerificationKeys
  • EcdsaSecp256k1Signature2019
  • EcdsaSecp256r1Signature2019
  • EcdsaSecp256k1RecoverySignature2020
  • Eip712Signature2021
  • SolanaSignature2021
  • JsonWebSignature2020


The following tools and features are high priority for subsequent releases:

  1. Exposing interfaces for JWT-based Verifiable Credential workflows
  2. JSON-LD context editor
  3. Registration of several new LD signature suites and support for new cryptography
  4. Further DID method support: did-btcr, did-onion
  5. BBS+ signatures
  6. DIDComm support
  7. Aries interoperability profile support