At Spruce, we’re building a product suite to manage all aspects of the data supply chain. Here’s the latest from our development efforts
DIDKit is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).
- DIDKit and ssi library released under Apache License, Version 2.0. Tagged release version 0.1.0.
- Implemented did:web
- Implemented linked data proof type for Tezos DID method (did:tz).
- Built DIDKit CLI and HTTP server as Docker images.
- Improved DID resolution support.
- Adjusted API to allow for multiple DID methods derived from keypair.
- DID method implementations modularized, making it easier to support more DID methods.
- Updated Rust interfaces to use asynchronous I/O.
- Documentation website launched: https://spruceid.dev/docs/didkit/
- Added more example shell scripts.
- Added a CHAPI wallet implementation example.
- Added a Spring Boot example application with sign-in powered by the previously mentioned CHAPI wallet example implementation using DIDKit.
- Added Makefile targets to build static DIDKit library files for `aarch64-apple-ios` and `x86_64-apple-ios`.
- (Unmerged) Added WASM build support using `wasm-pack`.
- (Unmerged) Added Node.js build support using `neon-bindings`.
Credible is Spruce’s native credential wallet for the consumption, storage, and presentation of Verifiable Credentials on Android and iOS.
- Updated to make use of the official `v0.1.0` release of DIDKit.
- Credible has now been built on iOS for the first time after DIDKit was updated, to build for `aarch64-apple-ios` and `x86_64-apple-ios`.
- The settings were updated to include a personal profile page and pages with various notices (privacy, terms and conditions, licenses, etc).
- There is now a DID sharing option available for users.
As a quick experiment to demonstrate method interoperability, we’ve put together a draft specification for a DID Method for the Dogecoin blockchain. Additionally, we plan on making a light rust implementation that integrates with DIDKit.
Our specification draws heavily from the work on did:btcr due to structural similarities. We managed to further improve upon the did:btcr spec with new privacy-preserving benefits.
Follow us on Twitter
Follow us on LinkedIn