did_resetter_approve
operation. The server will take the consensus of all resetters and decide whether to approve or reject the request.did_register_resetters
and did_revoke_resetters
operations that are initiated by the DID owner, the did_resetter_approve
is initiated by a DID resetter.did_register_resetters
approves a resetter registration for a DID. A set of resetters will become active after all resetters in the set approve the registration.did_revoke_resetters
approves a resetter revocation for a DID. A set of resetters will be revoked, i.e. become deactivated, if the combined voting powers of all resetters surpass "acceptable_votes"
.did_reset
approves a DID reset, i.e. resetting all key series in the DID. The reset will take place if the combined voting powers of all resetters surpass "acceptable_votes"
.did_resetter_approve
, a resetter must specify the attribute "consensus"
that contains (i) the consensus type, (ii) DID address of the target client and (iii) the DID address of the resetter who makes this HTTP request, which are seperated by |
as follows:"acceptable_votes"
.did:idin:03e450465cd3bd268163dde7223bfb99efe03e3cbf279f6b1772050e09e09fbf
and the target DID address is did:idin:9cd19d4cbab9ca1d6f4c6a4b9117fb8904f250b47307cf4f484424f44e0c8370
, then the field "consensus" must have the following form:consensus_name
could be either (i) did_register_resetters
, (ii) did_revoke_resetters
or (iii) did_reset
.