anoncreds-spec
anoncreds-spec copied to clipboard
The specification for AnonCreds verifiable credential exchange.
When transforming a DIF Presentation Definition/Submission into an AnonCreds Proof Request we need to provide a `nonce`. When proving a W3C AnonCreds VP we can take the `challenge` field from...
In the AnonCreds RS implementation for W3C AnonCreds credentials we've opted to include the credential definition id as the `verificationMethod` property in the proof. I think this makes sense, as...
I've been re-reading the DIF PE specification to create test vectors for AnonCreds W3C credentials and exchange messages. I now noticed in the spec the following sections: This requires that...
The spec defines "holder" as: "an entity that is in possession of a [credential](https://hyperledger.github.io/anoncreds-spec/#term:credential). In many use cases, the holder is also the identity [subject](https://hyperledger.github.io/anoncreds-spec/#term:subject)." Since the term "entity" isn't...
We are getting close to finishing the specification. The work from @aritroCoder has gotten the "hard to do" things out of the way, now to get the text ready. Here...
We've been digging into this issue for the last couple of weeks. I've created this document[1] that has lots of details/rationale about the approach, with only a few questions. I...
This deploys the context for anoncreds credentials on the spec site, allowing it to be accessed using https://hyperledger.github.io/anoncreds-w3c-context
In this section: https://hyperledger.github.io/anoncreds-spec/#constructing-the-credential-request The JSON uses "prover_did", but the text around references "entropy".
I think we could refine the language around nonces. In 8.1 it states that `**The nonce must be present in the subsequent [Credential Request] from the [holder].**` Which reads to...
Something I've seen in a lot of the W3C repos are test vectors for defined models. This can help greatly when implementing a spec, where it is not always very...