Challenge request
When an APP request the PKSA to sign a challenge, it will receive the following message:
challenge_req
{
cmd: "challenge_req"
account: string
data: string
uuid: string
expire: number
token: the authentication token - DEPRECATED since protocol v1
}account: the Hive account namedata: the Base64 representation of an encryptedchallenge_req_dataobjectuuid{string} the transaction request identifierexpire{Number} UNIX time when the request will expiretoken: the authentication token - Deprecated since protocol v1
The PKSA must decrypt the challenge_req_data object using the encryption key previously shared with the APP (auth_key)
The structure of the challenge_req_data is:
challenge_req_data
{
key_type: string,
challenge: string,
decrypt: boolean = false // protocol >= 1
nonce: number
}key_type: the key type required to sign the transactions. It can be one ofposting|active|memo.challenge: a string to be signeddecrypt: (optional - default value is false) indicates if the passed
challengemust be encrypted (decrypt=false) or decrypted (decrypt=true) before being returned by the PKSAnonce: UNIX time of the request
Last updated