Generator/Setup guides/Kraken

Kraken setup key, and the code it expects

Kraken is the common exception: it issues SHA-512 secrets, so a generator locked to SHA-1 produces codes Kraken will always reject.

Service kraken.comAlgorithm SHA-512Step 30sDigits 6
or drop an image here

Advanced
Digits
Period
Algorithm
Waiting for a keypaste one above to start27

——————

Where Kraken hides the key

  1. Security → Two-Factor Authentication → Sign-in → Set up.
  2. Kraken shows the QR and the Base32 key together.
  3. Paste the key above, then open Advanced and switch the algorithm to SHA-512.
  4. Enter the six digits to confirm.

Why your codes fail elsewhereMost authenticator apps assume SHA-1 and ignore the algorithm field in the otpauth URI. Kraken’s SHA-512 secrets are the single most common cause of “my app gives the wrong code” reports in this niche.

Parameters Kraken issues

AlgorithmSHA-512. Set this under Advanced before the codes will match.
Period30 seconds
Digits6
URI formatotpauth://totp/Kraken:you@kraken.com?secret=…&issuer=Kraken. Paste the whole URI above and the label fills itself in.

If the key is gone

  1. Saved key. Re-add it with SHA-512 selected.
  2. Account recovery. Kraken requires a support ticket with identity documents and will disable trading while it runs.

Questions

Why does my authenticator give the wrong code for Kraken?
Kraken issues SHA-512 secrets. An app that hard-codes SHA-1 computes a different HMAC from the same key, so every code is wrong. Switch the algorithm to SHA-512.

Related

TroubleshootingWhy your 2FA code is rejectedSetup guideGitHub setup keySetup guideDiscord setup key