Optional
capabilityThe root capability being invoked. In did:btc1, this is typically
urn:zcap:root:<urlencoded-did>
(see Section 9.4.1).
Optional
capabilityThe action performed under the capability—set to "Write" in the spec for DID document updates.
Optional
challengeOptional
created(Optional) Some cryptosuites or proofs may include a timestamp, domain, or challenge. Although not explicitly required in the doc's steps, they often appear in Data Integrity proofs and may be included as needed.
The cryptographic suite used, e.g. "schnorr-secp256k1-jcs-2025".
Optional
domainThe purpose of the proof, which the spec sets to "capabilityInvocation".
The cryptographic signature value. The exact property name may be defined
by the cryptosuite (for instance, proofValue
for a raw signature) and
contains the actual signature bytes in an encoded form.
The proof type—per the spec’s example, "DataIntegrityProof".
DID URL of the key invoking the capability, i.e. the DID Document's verificationMethod.id used to sign this update.
Proof is the Data Integrity proof (ZCAP-LD style) added to a did:btc1 DID Update Payload.
Verifiable Credential Data Integrity 2.1 Proofs.
DID BTC1 4.3.2 Invoke DID Update Payload.