SpruceID Developer Update #37
At SpruceID, we’re letting users control their identity and data across the web. Here’s the latest from our development efforts.
In case you missed it, check out our previous update here:
At SpruceID, we’re letting users control their identity and data across the web. Here’s the latest from our development efforts:
SpruceKit
SpruceKit is a collection of libraries that power your application to accept digital credentials from users on their terms, originate trusted information for users, and interact with user data vaults. SpruceKit consists of the following open-source libraries:
- Reference Wallet
- SSX
- Sign-in with Ethereum
- DIDKit
- TreeLDR
- SpruceKit also provides access to Kepler and Rebase
OpenID and Reference Wallet
We are working on implementations of OID4VCI and OID4VP and have recently refactored them to match the latest version of the specifications (oid4vci-rs#10, oid4vp-rs#3)
Work is underway to update our reference wallet (formerly known as Credible Wallet) and refactor it as a collection of our mobile-related technologies which include credentials and keys management but also the OID4VCI protocols.
DIDKit/SSI
DIDKit provides Verifiable Credential and Decentralized Identifier functionality across different platforms. DIDKit's core libraries are written in Rust due to Rust's expressive type system, memory safety, simple dependency web, and suitability across different platforms, including embedded systems, but the comprehensive DIDKit SDK includes many libraries and interfaces for using it almost everywhere.
- Merged an initial implementation of SD-JWT (ssi#529)
- A major refactor of ssi continues to be underway. This refactor will help us to better handle Linked Data and generally improve our implementation of the various Verifiable Credentials and Decentralised IDs specifications (#508). The general API redesign is over, and we are now rewriting all ssi tests and making sure the new implementation does not introduce regressions.
Rebase
- Rebase was refactored to support multiple async runtimes, this allows developers to use Rebase in popular Rust async runtimes like Tokio. Before, it only supported WASM.
- Rebase is being refactored to support witness flows without issuance. All previous issuance work will still be available, but developers will be able to use the witness flows to simply determine if a fact is true and no longer have to issue a credential at the conclusion of the flow. This supports more flexible implementations in apps that call Rebase libraries.
About SpruceID: SpruceID lets users control their data across the web. SpruceID provides an ecosystem of open-source tools for developers that let users collect their data in one place that they control, and show their cards however they want. If you're curious about integrating Spruce's technology into your project, come chat with us in our Discord: