explaingit

peavey2787/qssm-rs

Analysis updated 2026-05-18

1eCAudience · researcherComplexity · 5/5LicenseSetup · hard

TLDR

A post-quantum, stateless zero-knowledge proving system with local Rust, CLI, and WebAssembly integrations.

Mindmap

mindmap
  root((QSSM))
    What it does
      Zero-knowledge proofs
      Post-quantum lattice math
      Stateless verification
    Tech stack
      Rust crates
      WebAssembly package
      CLI binary
    Use cases
      Local proof and verify flows
      CI pipeline verification
      Cryptography research
    Audience
      Researchers
      Auditors
      Rust developers
    Setup
      Choose Rust CLI or WASM
      Formal EasyCrypt model

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Embed the QSSM Rust crates into an application to generate local zero-knowledge proofs.

USE CASE 2

Use the qssm-cli tool to prove and verify templates as part of a CI pipeline.

USE CASE 3

Integrate the WASM package into a browser or Node.js app that needs local proof verification.

USE CASE 4

Audit the formally verified cryptographic engines before relying on them in production.

What is it built with?

RustWebAssemblyEasyCryptCLI

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires understanding of zero-knowledge cryptography, integration surfaces span Rust, CLI, and WASM.

Business Source License 1.1 restricts commercial production use for a period before converting to an open license.

In plain English

QSSM, short for Quantum-Safe Sovereign Multiset, is a cryptographic system for generating and checking zero-knowledge proofs, meaning it lets someone prove a statement is true without revealing the private data behind it. It is designed to be post-quantum, built on lattice-based mathematics that is expected to resist attacks from quantum computers, and stateless, so a verifier does not need to replay any history or trust a shared ledger to check a proof. The project is built around two proving engines behind one shared interface. Engine A uses a lattice-based method with prover randomness and statistical proofs, while Engine B is a deterministic, hash-based engine with no randomness involved. Both aim for fast local proof generation, with a stated performance target of under 10 milliseconds, and neither requires a network of external provers, GPU farms, or any blockchain. The project's security claims have been checked with a formal verification tool called EasyCrypt, covering 149 theories with no unproven assumptions. QSSM is distributed three ways depending on how you want to use it. There is a set of Rust crates for embedding the proving system directly into a Rust application, a standalone command line tool for proving and verifying files locally, and a WebAssembly package for use in a browser, Node.js, or TypeScript project. The README describes the target users as developers building local proof and verify flows, researchers studying post-quantum proving systems, and auditors reviewing the underlying cryptography. The project explicitly states what it is not: not a virtual machine for zero-knowledge circuits, not a blockchain, not a prover network, and not a layer-2 scaling system. It is licensed under the Business Source License 1.1 and is aimed at technical users comfortable with cryptography rather than general application developers. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Explain how QSSM's two proving engines differ from each other.
Prompt 2
Show me how to install and run qssm-cli to prove and verify a template locally.
Prompt 3
Walk me through integrating the QSSM WASM package into a TypeScript project.
Prompt 4
What does it mean that QSSM's EasyCrypt model has zero admits and zero axioms?
Prompt 5
Help me understand what makes QSSM stateless compared to blockchain-based proving systems.

Frequently asked questions

What is qssm-rs?

A post-quantum, stateless zero-knowledge proving system with local Rust, CLI, and WebAssembly integrations.

What language is qssm-rs written in?

Mainly eC. The stack also includes Rust, WebAssembly, EasyCrypt.

What license does qssm-rs use?

Business Source License 1.1 restricts commercial production use for a period before converting to an open license.

How hard is qssm-rs to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is qssm-rs for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.