Elysia Tools

Browse tools, examples, visual explainers, and topic guides from one clear workspace.

Top Categories

Hubs

Language
ZHESPTRUFRDEEN

Elysia Tools

Navigation

Cryptography

PQC & ZK Signature Verifier Auditor

· Last updated:2026-10-04

Audit ML-DSA / SLH-DSA / FN-DSA / BBS+ / PLONK / Halo2 parameter compatibility, proof sizes and trusted-setup requirements, with a live pure-TS ML-DSA (FIPS 204) demo

Details

What this tool helps you do

Audit the post-quantum signature and zero-knowledge verifier landscape — and run a real ML-DSA keygen/sign/verify in your browser-side pipeline, in pure TypeScript.

What it checks:

  • Standards matrix: ML-DSA (FIPS 204 final — note: not 203, which is ML-KEM), SLH-DSA (FIPS 205, 12 parameter sets), FN-DSA (FIPS 206 draft, Falcon), BBS signatures (CFRG draft, BLS12-381), and the ZK verifier families Groth16 / PLONK / Halo2 — with exact public-key, secret-key and signature sizes, NIST security categories, and COSE/JOSE algorithm IDs from RFC 9964 (-48/-49/-50).
  • Trusted-setup audit: which systems need a per-circuit ceremony (Groth16), a universal updatable Powers-of-Tau SRS (PLONK/KZG), or nothing at all (Halo2's transparent IPA over Pasta curves; every lattice/hash PQC scheme).
  • CNSA 2.0 timeline: 2027 new-acquisition gate, 2030 software/firmware-signing deadline (LMS/XMSS encouraged now), 2033 browsers/servers/OS, 2035 NSM-10 endpoint.
  • Live ML-DSA demo: generates a deterministic keypair, signs your message and verifies it — plus a tamper-detection check — using the repository's pure-TS FIPS-204-final port, which was verified byte-exact against locally compiled PQClean reference binaries (pk/sk/sig identical for ML-DSA-44/65/87, rejection-loop trace matched iteration-for-iteration).
  • Blob identifier: paste a hex or base64 public key / signature and the auditor matches its byte length against every parameter set (e.g. 1312 → ML-DSA-44 public key; 3309 → ML-DSA-65 signature; 49856 → SLH-DSA-256f signature).

Good to know: the FIPS numbering in older blog posts is frequently shifted by one — this tool pins the verified mapping (ML-DSA = 204, SLH-DSA = 205, FN-DSA = 206 draft; ML-KEM = 203). BBS proofs are not fixed-size: per draft-12 the deserialization floor is 3 G1 points + 4 scalars = 272 bytes, growing 32 bytes per additional scalar.

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Samples

Examples that match this tool

Related

Continue with connected tools and hubs

Written by the Elysia Tools team

Tool usage guide

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Category
Cryptography
Input types
select, text, textarea
Output type
html
Sample coverage
4
API ready
Yes

Overview

The PQC & ZK Signature Verifier Auditor inspects post-quantum signature schemes and zero-knowledge verifier specifications, allowing you to audit exact key and proof sizes, trusted-setup constraints, RFC 9964 algorithm identifiers, and CNSA 2.0 migration milestones while running pure TypeScript ML-DSA (FIPS 204) operations directly in your browser.

When to use

  • Evaluating key sizes, signature overhead, and trusted-setup trade-offs across NIST PQC standards (ML-DSA, SLH-DSA, FN-DSA) and ZK verifiers (Groth16, PLONK, Halo2).
  • Testing client-side ML-DSA-44, ML-DSA-65, or ML-DSA-87 signing, verification, and tamper detection with deterministic keypairs.
  • Identifying unknown post-quantum cryptographic public keys or signature blobs from raw hex or base64 strings by exact byte length matching.

How it works

  1. 1Select your operational mode: matrix audit, live ML-DSA sign and verify demo, or raw blob identification.
  2. 2Filter your scope across all cryptographic schemes, NIST PQC digital signatures, or zero-knowledge verifier families.
  3. 3Configure parameter sets such as ML-DSA-65, enter custom payload messages to sign, or paste encoded key and signature blobs for length parsing.
  4. 4Generate audit matrices, run deterministic FIPS 204 signature cycles with tamper verification, or review matched algorithm parameters alongside RFC 9964 IDs and CNSA 2.0 timelines.

Use cases

  • Security engineers planning CNSA 2.0 compliance timelines for firmware signing, protocol upgrades, and post-quantum certificate deployment.
  • Protocol designers benchmarking payload overhead and proof size footprints between BBS signatures, lattice signatures, and zero-knowledge verification schemes.
  • Developers debugging raw cryptographic blobs during protocol migrations by parsing unknown public keys or signatures against standardized byte sizes.

Examples

1. Audit Standards Matrix and CNSA 2.0 Timeline

Security Architect

Background

An architect is planning the migration of an enterprise authentication protocol to post-quantum signature schemes.

Problem

They need to compare public-key sizes, signature lengths, COSE algorithm IDs, and CNSA 2.0 compliance deadlines across ML-DSA, SLH-DSA, and ZK verifiers.

How to use

Set Mode to 'Audit matrix (standards, sizes, COSE, CNSA 2.0)' and select 'All schemes' under Scope.

Mode: audit, Scope: all

Outcome

Displays a complete matrix covering exact byte sizes, RFC 9964 IDs, trusted-setup requirements, and CNSA 2.0 adoption gates.

2. Deterministic ML-DSA-65 Signature and Tamper Test

Cryptographic Engineer

Background

A developer needs to verify client-side message signing behavior using FIPS 204 parameter sets.

Problem

They need to validate that a custom release manifest can be signed and verified deterministically with instant detection of tampered payload bytes.

How to use

Select 'Live ML-DSA demo' mode, choose 'ML-DSA-65' for parameter set, and input the target payload message.

FAQ

What is the difference between FIPS 203, FIPS 204, and FIPS 205?

FIPS 203 standardizes ML-KEM for key encapsulation, FIPS 204 standardizes ML-DSA for lattice-based digital signatures, and FIPS 205 standardizes SLH-DSA for stateless hash-based digital signatures.

Which zero-knowledge proof systems require a trusted setup?

Groth16 requires a circuit-specific ceremony, PLONK requires a universal updatable Powers-of-Tau structured reference string, and Halo2 requires no trusted setup by using inner product arguments.

What algorithm identifiers does RFC 9964 define for ML-DSA in COSE?

RFC 9964 assigns COSE algorithm identifiers -48 for ML-DSA-44, -49 for ML-DSA-65, and -50 for ML-DSA-87.

How does the blob identification mode identify keys and signatures?

It decodes hex or base64 inputs, calculates total byte length, and maps that length to exact parameter specifications across ML-DSA, SLH-DSA, FN-DSA, and BBS signatures.

Are ML-DSA signatures and keys run completely client-side in the live demo?

Yes, key generation, message signing, and signature verification execute entirely client-side using a pure TypeScript implementation matching FIPS 204.

Home
Tools3215
Samples593
Visualizations472
Viewers103
Hubs239
Tags333
Images, Audio & Video657

Image, audio, and video processing, conversion, and optimization tools

Math, Date & Finance647

Calculators, numerics, date logic, statistics, and finance tools

Design & Color298

Color, layout, graphics, visual styling, and design helper tools

Text & Writing209

Writing, cleanup, formatting, extraction, and text analysis tools

Developer & Web194

Developer utilities, networking, web debugging, and automation helpers

Conversion & Encoding175

Format, file, archive, unit, and encoding conversion tools

Lead Generation Quiz Launch and Contact Handoff
Memorial Drafts: Family Review and Print Handoff
Private Habit Records: Backup, Restore and Sharing Review
Article to X and LinkedIn Drafts: Fact Review and Handoff
Markdown Interactive Deck Review and Offline Handoff

© 2026 Elysia Tools. All rights reserved.

DocsPricingAboutTerms of ServicePrivacy PolicyCookiesContact
Java

Android Image Processing Java Samples

Android Java image processing examples including reading/saving images, scaling, and format conversion

Kotlin

Android Image Processing Kotlin Samples

Android Kotlin image processing examples including reading/saving images, scaling, and format conversion

Python

Web Image Processing Python Samples

Web Python image processing examples using PIL/Pillow including reading, saving, resizing, and format conversion

Rust

Web Image Processing Rust Samples

Web Rust image processing examples including image read/save, scaling, and format conversion

Cryptography

Hash Algorithm Comparator

Hash the same input with MD5, SHA-1, SHA-256, SHA-512, BLAKE2b, and BLAKE3 at the same time and compare them side by side: output length, hex/Base64 digest, security status (broken / modern), and a relative speed benchmark. Great for teaching, choosing a hashing algorithm, or sanity-checking checksums.

Security

Digital Signature Generator

Sign a message with a private key or verify a signature with a public key — supports RSA-PSS (SHA-256), ECDSA (P-256), and Ed25519. Pure client-side crypto (Node crypto.createSign/createVerify), no network. Paste a PEM key to sign or to verify a base64 signature. This tool signs/verifies; it does not generate key pairs.

Security

PKCE Code Verifier & Challenge Generator

Generate, validate and verify OAuth2 / OIDC PKCE (RFC 7636) code_verifier and S256 code_challenge pairs. Three modes: (1) generate a fresh verifier + challenge from cryptographically secure random bytes at 256/384/512/768-bit entropy, (2) audit a verifier you already have against the RFC — length (43–128), charset [A-Za-z0-9-._~] and ≥256-bit entropy, and (3) verify a verifier/challenge pair by recomputing BASE64URL(SHA256(verifier)). Optionally build the full authorization-request URL and token-exchange body. Complements the generic nonce-generator (which only emits a verifier+challenge pair) with RFC-compliance auditing and pair verification.

Format Conversion

Web Push RFC 8030 Request + VAPID + RFC 8291 Payload Encryption Encoder

Encode a complete Web Push send: RFC 8291 aes128gcm payload encryption, RFC 8292 VAPID ES256 JWT, RFC 8030 headers, APNs/FCM cross-walk and decrypt round-trip verification.

Mode: mldsa-demo, ML-DSA Parameter Set: ML-DSA-65, Message: release-manifest-v2.4.0

Outcome

Generates public and secret keys, computes the ML-DSA-65 signature, confirms positive verification, and proves tamper rejection.

3. Identify Unlabeled Post-Quantum Public Key Blob

Security Analyst

Background

An analyst extracts an unlabelled 1312-byte public key string in base64 format from an intercept log.

Problem

The protocol documentation does not state the algorithm family or parameter level used.

How to use

Switch Mode to 'Identify pasted key / signature' and paste the base64 string into the blob input field.

Mode: identify, Key or Signature Blob: <base64 string>

Outcome

Identifies the blob as an ML-DSA-44 public key based on its exact 1312-byte length and outputs its NIST security category.