This document is not a W3C Standard nor is it on the W3C Standards Track. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
Comments regarding this document are welcome. Please file issues and PRs directly on Github.
Editors:
- Caspar Roelofs, Founder/Director | Gimly caspar@gimly.io
- Rebal Alhaqash | Tonomy Foundation
- Jack Tanner, Blockchain and SSI Developer | Tonomy Foundation
- Markus Sabadello | Danube Tech markus@danubetech.com
ConditionalProof is a new type of verification method for DID Documents. It can be used to express complex conditions and additional metadata about verification methods. It can be used to combine verification methods to form conjugated conditions such as logical operations (like &&), thresholds, weighted thresholds, relationships, or delegation to external verification methods.
This new type has been created from discussions during the Decentralized Identity Foundation's ID working group sessions. The need for this type has arisen from the creation of the Antelope DID method (formerly "EOSIO DID method") by Gimly. The type is designed to cover several other important use cases requiring similar conditional logic.
Prior work:
- Conditional Proof planning doc - several
ConditionalProoftypes have not yet been added to this draft; see the conversation, and if you think they are important, please submit an issue or PR to add - DID core - multisig and delegated use case
Create a new verification method type that can:
- Express conditional logic required to validate verification methods
- Express additional metadata about verification methods
Support for account and key models of the following protocols:
- Antelope: Accounts And Permissions
- Hyperledger Fabric: Endorsement policies
- Ripple and BigchainDB: Composable cryptographic conditionals
- KERI: KERI Thresholds
- Hyperledger Indy: Indy DID Method
A illustrative object of ConditionalProof type showing the potential properties of the object. Note that a valid object does not require existence of all of these properties.
{
"id": "did:example:123#owner",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"threshold": 0,
"conditionAnd": [],
"conditionOr": [],
"conditionThreshold": [],
"conditionWeightedThreshold": [],
"conditionDelegated": "",
"relationshipParent": [],
"relationshipChild": [],
"relationshipSibling": []
}A verificationMethod which has a ConditionalProof2022 type is a conditional proof. A conditional proof type MUST specify one and only one fulfillment condition (And, Or, Threshold, WeightedThreshold, or Delegated) by having a corresponding object property for that condition. A conditional proof MAY specify one or more relationships (Parent, Child, and/or Sibling) by having a corresponding object property for that relationship.
An And, Or, Threshold, and WeightedThreshold fulfillment condition MUST be either an array of verification methods, or a relative DID URL to a verification method on the same DID Document. These verification methods can be of any type, including Conditional Proof types, creating a recursive structure able to express an infinite range of conditional logic complexity as may be required for the cryptographic material.
The Delegated fulfillment condition MUST be a DID URL string.
The relationships MUST be an array of DID URLs.
The following DID shows a verificationMethod #1 which requires proofs to match the condition of AND( OR( #1-1-1, #1-1-2), #1-2) to be fulfilled. Note different key types are used as well.
{
"@context": [
"https://www.w3.org/ns/did/v1",
"https://example.com/did/conditions-proof/v1"
],
"id": "did:example:123",
"type": "ConditionalProof2022",
"verificationMethod": [
{
"id": "did:example:123#1",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"conditionAnd": [{
"id": "did:example:123#1-1",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"conditionOr": [{
"id": "did:example:123#1-1-1",
"controller": "did:example:123",
"type": "EcdsaSecp256k1VerificationKey2019",
"publicKeyBase58": "5JBxKqYKzzoHrzeqwp6zXk8wZU3Ah94ChWAinSj1fYmyJvJS5rT"
}, {
"id": "did:example:123#1-1-2",
"controller": "did:example:123",
"type": "Ed25519VerificationKey2018",
"publicKeyBase58": "PZ8Tyr4Nx8MHsRAGMpZmZ6TWY63dXWSCzamP7YTHkZc78MJgqWsAy"
}]
}, {
"id": "did:example:123#1-2",
"controller": "did:example:123",
"type": "Ed25519VerificationKey2018",
"publicKeyBase58": "H3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV"
}]
}
]
}This is an example of a verifiable presentation that fulfills the above DID's verificationMethod #1 with two signatures #1-1-1 and #1-2.
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://www.w3.org/2018/credentials/examples/v1"
],
"type": "VerifiablePresentation",
"verifiableCredential": [{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://www.w3.org/2018/credentials/examples/v1"
],
"id": "http://example.edu/credentials/1872",
"type": ["VerifiableCredential", "AlumniCredential"],
"issuer": "https://example.edu/issuers/565049",
"issuanceDate": "2010-01-01T19:73:24Z",
"credentialSubject": {
"id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
"alumniOf": {
"id": "did:example:c276e12ec21ebfeb1f712ebc6f1",
"name": [{
"value": "Example University",
"lang": "en"
}, {
"value": "Exemple d'Université",
"lang": "fr"
}]
}
},
"proof": {
"type": "RsaSignature2018",
"created": "2017-06-18T21:19:10Z",
"proofPurpose": "assertionMethod",
"verificationMethod": "https://example.edu/issuers/keys/1",
"jws": "eyJhbGciOiJSUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..TCYt5X
sITJX1CxPCT8yAV-TVkIEq_PbChOMqsLfRoPsnsgw5WEuts01mq-pQy7UJiN5mgRxD-WUc
X16dUEMGlv50aqzpqh4Qktb3rk-BuQy72IFLOqV0G_zS245-kronKb78cPN25DGlcTwLtj
PAYuNzVBAh4vGHSrQyHUdBBPM"
}
}],
"proof": [{
"type": "JsonWebSignature2020",
"created": "2020-02-15T17:13:18Z",
"verificationMethod": "did:example:123#1",
"proofPurpose": "assertionMethod",
"jws": "eyJiNjQiOmZhbHNlLCJjcml0IjpbImI2NCJdLCJhbGciOiJFZERTQSJ9.Y0KqovWCPAeeFhkJxfQ22pbVl43Z7UI-X-1JX32CA9MkFHkmNprcNj9Da4Q4QOl0cY3obF8cdDRdnKr0IwNrAw"
}, {
"type": "JsonWebSignature2020",
"created": "2020-02-15T17:13:18Z",
"verificationMethod": "did:example:123#1",
"proofPurpose": "assertionMethod",
"jws": "53Fm3mYG9ZJWwRDgyTt9aRDfpsZCGWycS8VChbvdF7PBgHo6MjKCB5k8.
6mV1meQzLKDraHdMzneojsw8eqRYcf7EvXVPC1X2ZRgGHdBHmUhYM4CVt6v4uV4JZ51PWxnB31bM9VvVjaVWu"
}
]
}{
"id": "did:example:123#1",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"conditionAnd": []
}Fulfilled if all of the verificationMethods provided are fulfilled.
Note: this subtype can be expressed through a Threshold subtype by setting the “threshold” property to the the number of verificationMethods.
{
"id": "did:example:123#1",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"conditionOr": []
}Fulfilled if any one of the verificationMethods provided are fulfilled.
Note: this subtype can be expressed through a Threshold subtype by setting the “threshold” property to 1.
{
"id": "did:example:123#4",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"threshold": 3,
"conditionThreshold": [],
}Fulfilled if the number of verificationMethods that are fulfilled are greater than or equal to the “threshold” property.
Note: this subtype can be expressed through a WeightedThreshold subtype by setting all the “weight” properties to 1.
{
"id": "did:example:123#5",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"threshold": 3,
"conditionWeightedThreshold": [{
"condition": {},
"weight": 2
}, {
"condition": {},
"weight": 2
}, {
"condition": {},
"weight": 1
}]
}Fulfilled if the sum of the weights of the verificationMethods that are fulfilled are greater than or equal to the “threshold” property.
{
"id": "did:example:123#10",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"conditionDelegated": ""
}Fulfilled if the verificationMethod found by dereferencing the DID URL "conditionDelegated" is fulfilled. The dereferenced DID document MUST contain a verificationMethod found using the DID URL. The dereferenced DID document MUST NOT contain multiple verificationMethods found using the DID URL.
{
"id": "did:example:123#10",
"controller": "did:example:123",
"type": "ConditionalProof2022",
"relationshipParent": [],
"relationshipChild": [],
"relationshipSibling": [],
}Has no fulfillment requirements.
If one of these properties exist, it MUST be an array of DID URLs.
This verificationMethod type is useful to express information for wallet management and for proofs.
- "relationshipParent" expresses which verificationMethod(s) are a parent to this one.
- "relationshipChild" expresses which verificationMethod(s) are a child to this one.
- "relationshipSibling" expresses which verificationMethod(s) are a sibling to this one.
For Hierarchical Deterministic (HD) Wallets or other types of hierarchial wallets such as Antelope, the relationship between different keys in the wallets is required so that the wallets may correctly update its key hierarchy. For example, a parent key is required to update child keys on an Antelope blockchain.
Such relationship information is useful for wallet management, but can also be used in proofs. For example, an application may require that any approved is for fulfilled if it contains a child key of "did:example:123#1".