Technical verification

Kardix technical test vectors

Test vectors help developers and users verify that identical fictional inputs reproduce identical outputs across compatible implementations.

Written by Savvas Katsikas · Published 2026-06-12 · Reviewed for Kardix KDX2
Never use these fictional examples as real credentials. They are public verification inputs.

Verification input

Phrase: example testing phrase only
PIN: 2468
Label: example-service
Version: KDX2

How to verify behavior

  1. Enter the fictional values above.
  2. Record the generated username and password.
  3. Clear the form and repeat the process.
  4. Confirm that the outputs match exactly.
  5. Change only the label and verify that the output changes.

Why published test vectors matter

They make deterministic claims falsifiable. A compatible implementation should reproduce the same outputs when normalization, Argon2id parameters, output encoding, and version rules match.

Review the published source snapshot and security design for implementation details.

Try the generator locally

Generate login details from a private phrase, optional PIN, and account label. Kardix does not save the inputs or generated credentials.

Open the Kardix generator →

About the author

Savvas Katsikas created Kardix and writes about practical password security, local-first tools, and deterministic generation trade-offs.

Read the author profile →