This endpoint initiates the authentication process by generating a random challenge
string that must be signed by the user’s private key. The signed challenge should
then be submitted to the /v1/auth/verify endpoint to complete authentication.
The challenge-response authentication mechanism ensures that users prove ownership of their public key.
/v1/auth/verifypublic_key - The user’s public key200 OK with the challenge string and request ID400 Bad Request if the request is malformed or the public key is invalid500 Internal Server Error if the challenge generation failsPublic key for which to generate an authentication challenge
Request body for initiating authentication challenge.
This request starts the authentication flow by requesting a challenge string that must be signed with the user's private key.
The public key of the user requesting authentication. Must be a valid Bitcoin or Spark public key.
"021eec911553028dded1ec644144cd3afee9d9bfe7846af3cf8e6d84f4b3102389"
Challenge generated successfully
Response containing the challenge string to be signed.
The challenge is a hex string composed of an ASCII magic prefix followed by 32 random bytes. The entire byte sequence is what should be signed using the private key corresponding to the provided public key.
The challenge string that must be signed.
Hex string of: "FLASHNET_AUTH_CHALLENGE_V1:" || 32 random bytes.
"464c4153484e45545f415554485f4348414c4c454e47455f56313a19f51e5e9b50314318517a5e2bb19e5beb94d9c5d74b61068ff458c75a649712"
A UTF-8 string version of the challenge suitable for wallets that sign strings.
Format: "FLASHNET_AUTH_CHALLENGE_V1:" + hex(random 32 bytes)
"FLASHNET_AUTH_CHALLENGE_V1:19f51e5e9b50314318517a5e2bb19e5beb94d9c5d74b61068ff458c75a649712"