Transfer Ownership of the Customized DID
It's already been mentioned that Publish DID is an effective cochain of Customized DID for primitive DID and non-change controller information (Controller and Multisig). This section is to introduce the instructions for using DID Document cochain after changing the information of controller.
DID Document provides the TransferDID method to complete the transaction of changing the controller information, which needs to use the master key of original controller of the DID to complete the transaction based on the modified document and the Transfer Ticket.
Example
Usage
DID Document provides a method to generate Transfer Ticket, which is initiated by a Controller of DID Document before modification, and Tickets are also signed and encapsulated by the initiator.
owner is the owner of Transfer Ticket, that is, Customized DID; to is the recipient of the Transfer Ticket and must be one of the Controller in the modified DID Document and one of the signers of the modified DID Document. Otherwise, subsequent Transfer DID will fail.
Transfer Ticket also needs to comply with the multi-signature rule of DID Document before modification. When the first Controller signs to generate Transfer Ticket, this method should be used if more than one signature of the Controller is needed. Refer to DIDDocument_SignDIDDocument method for specific usage.
This method is used for the cochain of Customized DID Document after changing the controller information, which can be signed by the Authentication Key of the current document and the Authentication Key of its Controller.
Last updated