Resetter Registration

In the case that a client loses all of her private keys, the client has an option to reset her DID, i.e. revoking all of her key series in that DID, with the approval of her resetters.

To invoke the reset operation, a list of resetters must be first registered with did_register_resetters operation. All resetters must also approve the registration themselves before the reset operation becomes available. In the resetter registration request, the client must specify (i) each resetter's DID address ("did_address") and (ii) each resetter's vote power ("vote_power") and (iii) the acceptable number of combined voting powers ("acceptable_votes") for approving the reset operation.

Note that the client cannot submit a request to reset her DID herself. To reset all key series in a DID, the client must contact each of her resetters individually and ask them to submit a reset request. For the reset operation to be complete, the combined voting powers from all resetters must surpass the threshold.

For a set resetters to become active, all resetters in the set must respond and approve the registration.

post
did_register_resetters

https://test-network.finema.co/did/<did_address>/reset
Request
Response
Request
Body Parameters
operation
required
string
The method's name that is "did_register_resetters".
did_address
required
string
The DID address.
current_key
required
string
The current public key in the series. It is used to verify the request's signature.
next_key_hash
required
string
The SHA-256 hash of the next public key in the series.
resetters
required
string
The list of the resetters. Each element in the list contains a resetter's DID address and voting power.
acceptable_votes
required
string
The voting power threshold in a resetter consensus.
nonce
required
number
The request nonce.
Response
200: OK
The operation name and DID address (<did_address>) will be given as the response.
{
"operation": "did_register_resetters",
"did_address": "did:idin:9cd19d4cbab9ca1d6f4c6a4b9117fb8904f250b47307cf4f484424f44e0c8370"
}
422: Unprocessable Entity
{
"errors": [
{
"status": 422,
"title": "Invalid Attribute",
"detail": "the server cannot process the request",
}
]
}

Example Message and Request

{
"operation": "did_register_resetters",
"did_address": "did:idin:9cd19d4cbab9ca1d6f4c6a4b9117fb8904f250b47307cf4f484424f44e0c8370",
"current_key": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEeR8NhQeHPT7l1yMyvkZMacPpibjH\n7mp5IRyO2J2kuE97h/fzu1c/7DFsO23qUN6/OezYglMEkoVo5Ob1b6k53A==\n-----END PUBLIC KEY-----",
"next_key_hash": "a18b790a92683ad00d3562de385ca9e07d20a729809c782e72412f57dd847105"
"resetters": [
{
"did_address": "asdfasdf",
"vote_power": 3
},
{
"did_address": "asdfasdf",
"vote_power": 3
},
{
"did_address": "asdfasdf",
"vote_power": 3
},
{
"did_address": "asdfasdf",
"vote_power": 3
},
],
"acceptable_votes": 6,
"nonce": 3
}

The above message can then be encoded in Base64 and signed with ECDSA to obtain the following HTTP request

{
"message": "ewogICAgIm9wZXJhdGlvbiI6ICJkaWRfcmVnaXN0ZXJfcmVzZXR0ZXJzIiwKICAgICJkaWRfYWRkcmVzcyI6ICJkaWQ6aWRpbjo5Y2QxOWQ0Y2JhYjljYTFkNmY0YzZhNGI5MTE3ZmI4OTA0ZjI1MGI0NzMwN2NmNGY0ODQ0MjRmNDRlMGM4MzcwIiwKICAgICJjdXJyZW50X2tleSI6ICItLS0tLUJFR0lOIFBVQkxJQyBLRVktLS0tLVxuTUZrd0V3WUhLb1pJemowQ0FRWUlLb1pJemowREFRY0RRZ0FFZVI4TmhRZUhQVDdsMXlNeXZrWk1hY1BwaWJqSFxuN21wNUlSeU8ySjJrdUU5N2gvZnp1MWMvN0RGc08yM3FVTjYvT2V6WWdsTUVrb1ZvNU9iMWI2azUzQT09XG4tLS0tLUVORCBQVUJMSUMgS0VZLS0tLS0iLAogICAgIm5leHRfa2V5X2hhc2giOiAiYTE4Yjc5MGE5MjY4M2FkMDBkMzU2MmRlMzg1Y2E5ZTA3ZDIwYTcyOTgwOWM3ODJlNzI0MTJmNTdkZDg0NzEwNSIKICAgICJub25jZSI6IDEKfQ==",
"signature": "OTI3MzgyNDgzNTQ3NTU5ODMyNTM1NzYwMDc2MTEwNzYwMTUzMjAzMzQ2NzQ5MDU4NzIwMzM4ODUzNjc4OTE2MTI2NzA2NzQyODgyMDcsIDQ1MjE2NzEwMzM3MjI5NjEzOTc3MjYxMzY2MjUwODYxOTA5MzY2MDU1MDg2Mjk0NzEyMDAwMTU3MjU4ODYxNTQ3ODUzNDc3NTY2ODQw"
}