At Spruce, we’re building the most secure and convenient way for developers to share authentic data. Here’s the latest from our open source development efforts:
We are currently working on a project that will enable creator authenticity for digital assets including NFTs. The initial smart contracts are written, as well as a CLI/library to interact with web applications. We plan on alpha testing the application this week.
A DID Method geared for privacy, formal verification, and scaling to billions of identifiers by using off-chain updates.
Spruce and TQ Tezos are jointly releasing the draft specification and initial implementation of Decentralized Identifiers (DIDs) based on the Tezos blockchain. We began our collaboration with TQ Tezos and the wider Tezos ecosystem in August to take full advantage of Tezos’ production-tested proof-of-stake consensus mechanism, ability to perform protocol upgrades, and toolsets for formal methods.
We welcome review of our Tezos DID Method specification, TZIP-019 companion specification, and open-source implementation based on DIDKit. …
Credible v0.1 pushed to GitHub with its core functionality enabled, documentation, and is moving towards stability for white-labeling.
Today, Spruce is open-sourcing under the Apache 2.0 license an early developer release of Credible (GitHub repository here), a native mobile wallet for W3C Verifiable Credentials and Decentralized Identifiers built on DIDKit and Flutter. We were able to package the DIDKit library written in Rust into a Flutter application running on both Android and iOS, using C bindings and Dart’s FFI capabilities. …
DIDKit v0.1 pushed to GitHub with its core features, documentation, and interfaces intact.
DIDKit is a lightweight set of Rust libraries containing a command-line interface and an HTTP interface. Both interfaces expose the core Verifiable Credential-handling capabilities of Spruce’s ssi library. Both ssi and didkit are being open-sourced this week to allow “early access” to the core source code, for review and consideration in advance of a substantial third-party audit.
But what exactly are “VC capabilities,” or for that matter, “DID capabilities”? Why is it so hard to find pluggable libraries that bring them to your project?
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:
The Tezos DID Method specifies how Tezos can be used for DID creation and management, compatible with the issuance, storage, and verification of Verifiable Credentials.
DIDKit is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).
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:
The Tezos DID Method specifies how Tezos can be used for DID creation and management, compatible with the issuance, storage, and verification of Verifiable Credentials.
In order to better work with decentralized identifiers and verifiable credentials, we’re working on DIDKit.
DIDKit is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs). It allows you to resolve and manage DID documents, and also manage the entire lifecycle of Verifiable Credentials including their issuance, presentation, and verification.
Notably, it reuses the same codebase across command-line tooling, RESTful HTTP servers, and platform-specific SDKs to facilitate code-level interoperability and a low total cost of ownership. …
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:
We are currently working on a project called DIDKit: a cross-platform toolkit for using DIDs and VCs with our Rust libraries at the core.
Reimagining Trusted Interactions