JSON-LD context URIs for interpreting this payload, including contexts for ZCAP (capabilities), Data Integrity proofs, and JSON-LD patch ops.
A JSON Patch (or JSON-LD Patch) object defining the mutations to apply to the DID Document. Applying this patch to the current DID Document yields the new DID Document (which must remain valid per DID Core spec).
Optional
proofA proof object (Data Integrity proof) that authorizes this update. It is a JSON-LD proof indicating a capability invocation on the DID's root capability, typically signed with the DID's verification key (using Schnorr secp256k1 in did:btc1).
The multihash of the current (source) DID Document, encoded as a multibase base58-btc string. This is a SHA-256 hash of the canonicalized source DID Document, used to ensure the patch is applied to the correct document state.
The multihash of the updated (target) DID Document, encoded as multibase base58-btc. This is the SHA-256 hash of the canonicalized DID Document after applying the patch, used to verify the update result.
The version number of the DID Document after this update. It is equal to the previous document version + 1.
The unsigned payload object containing instructions for how to update a did:btc1 DID Document. Once signed, it becomes a DID Update Invocation
DID BTC1 4.3.1 Construct DID Update Payload.
Found in DID BTC1 Specification Section 9.4.2
Example