Spruce Developer Update #8
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:
Work-in-Progress: Creator Authenticity
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.
Formally Verifying the Tezos DID Method
The Tezos DID method is a DID method that optimizes for privacy, enables formal verification, and scales to billions of identifiers by using “off-chain updates,” which allow private networks to extend and update on-chain data. A lot of our current work is focused on advancing did-tezos as the first formally verified DID Method.
We’ve continued work on improving the DID method’s core smart contract for on-chain updates. A first version of the formal proof has also been written, and a CI pipeline has been established.
DIDKit Updates
DIDKit is a cross-platform toolkit for working with W3C Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs).
- Added a Python package.
- Added a Django example app.
- Added a Flask example app.
- Added a JavaServer Pages (JSP) example app.
- Added a Svelte example CHAPI wallet.
- We’ve enabled DID Methods to use HTTP(S) on WASM and Android.
- Conducted a test with the VC HTTP API v0.0.2 test suite. Test report.
- Worked on support for Relative DID URLs.
- Improved DID URL dereferencing to support more DID documents.
- Support publicKeyBase58 for Ed25519.
- Implement did:onion.
- (WIP) Implement did:pkh — a DID method for deterministic handling of public key hashes by curve.
- Released ssi v0.2.0.
- Published to crates.io: ssi, ssi-contexts, did-web, did-method-key, did-tz, did-sol, did-pkh, did-ethr, did-onion.
- General bug fixes.
Credible Updates
Credible is a credential wallet for the verification, storage, and presentation of Verifiable Credentials using Decentralized Identifiers. In addition to our native mobile editions, we’ve since written a browser extension version of Credible along with an SDK to enhance any web application with decentralized identity.
If you would like to discuss how we would deploy the architecture described above for a specific use case, please take 30 seconds to leave us a message, and we will respond within 24 hours.
Follow us on Twitter
Follow us on LinkedIn
