ssi
ssi copied to clipboard
spruceid
Core library for decentralized identity.
Currently, when verifying a VC or VP, the issuer/holder id is usually resolved twice: once to verify that the proof's verification method has the appropriate verification relationship with the issuer...
Support more libraries for cryptographic operations, using features, e.g.: - [HACL*](https://github.com/project-everest/hacl-star) - libsodium - openssl (we are already using it for SSL) Also: #54 OS-provided crypto libraries/APIs
[`vc::get_verification_method`](https://github.com/spruceid/ssi/blob/4217a62f6bf2e5fddb1af44052dd0eb7a00ffca1/src/vc.rs#L875) currently returns an Option. It could instead return a Result, to pass through any error from the DID Resolution step. This would be a breaking change for the API....
Re: https://github.com/spruceid/didkit/issues/16, https://github.com/spruceid/didkit/issues/16#issuecomment-748346141 Performance: an OS may provide access to cryptographic hardware that is faster than using our own crypto dependencies on the CPU. Security and interop: an OS may...
Related to https://github.com/spruceid/didkit/issues/16, https://github.com/spruceid/didkit/issues/16#issuecomment-748346141 Allow issuing/signing where we don't have direct access to the private key, e.g. because it is in a hardware authentication device. Support some key management system...
We need to register the tz1/tz2/tz3 verification methods so we could refer to them satisfying LD-Proofs? E.g., `Ed25519PublicKeyBLAKE2BDigestSize20Base58Encoded2020`. > It looks to me like the way to register a proof...
As mentioned in https://github.com/spruceid/ssi/pull/147: > Test with local proxy server and web server
Proof type | Verification method type | Used with -|-|- `Ed25519BLAKE2BDigestSize20Base58CheckEncodedSignature2021`|`Ed25519PublicKeyBLAKE2BDigestSize20Base58CheckEncoded2021` | `did:tz:tz1` `P256BLAKE2BDigestSize20Base58CheckEncodedSignature2021` | `P256PublicKeyBLAKE2BDigestSize20Base58CheckEncoded2021` | `did:tz:tz3` `Eip712Signature2021` | `Eip712Method2021` | `did:ethr` (experimental) `SolanaSignature2021` | `SolanaMethod2021` | `did:sol` (experimental)...
This should avoid any confusion regarding the format of the key and whether it should have a prefix (e.g. `edpk`) or not. Original comment: https://github.com/spruceid/ssi/pull/121#issuecomment-799707086
These verification method types and proof types should probably be renamed, since they no longer depend specifically on `BLAKE2B`, etc.: Proof type | Verification method type -|- `Ed25519BLAKE2BDigestSize20Base58CheckEncodedSignature2021`|`Ed25519PublicKeyBLAKE2BDigestSize20Base58CheckEncoded2021` `P256BLAKE2BDigestSize20Base58CheckEncodedSignature2021` |...