11.2K ·GitHub
What is this?
A TypeScript implementation of hash-based signatures, specifically WOTS+ (Winternitz One-Time Signature Plus), a post-quantum signature primitive.
A TypeScript implementation of hash-based signatures, specifically WOTS+ (Winternitz One-Time Signature Plus), a post-quantum signature primitive.Is this a complete signature scheme or just one building block?It's a single primitive (WOTS+), typically used as a building block inside larger hash-based schemes like SPHINCS+, rather than a full multi-use signature protocol on its own.
It's a single primitive (WOTS+), typically used as a building block inside larger hash-based schemes like SPHINCS+, rather than a full multi-use signature protocol on its own.How do I add it to a project?Clone the repository and run npm install to pull in dependencies like @noble/hashes, then use the tsup-based build (npm run build) or run tests with Vitest.
Clone the repository and run npm install to pull in dependencies like @noble/hashes, then use the tsup-based build (npm run build) or run tests with Vitest.What do I need to use it?It relies on the @noble/hashes package for the underlying hash functions and is built/tested with TypeScript and Vitest, which enforces strict coverage thresholds.
It relies on the @noble/hashes package for the underlying hash functions and is built/tested with TypeScript and Vitest, which enforces strict coverage thresholds.Can I reuse the same key pair to sign multiple messages?No — WOTS+ is a one-time signature scheme, so each key pair is only secure for signing a single message, as the name itself indicates.
No — WOTS+ is a one-time signature scheme, so each key pair is only secure for signing a single message, as the name itself indicates.What is WOTS+ typically used for?WOTS+ is a hash-based one-time signature primitive that serves as the core building block for larger multi-signature, post-quantum schemes such as SPHINCS+.
WOTS+ is a hash-based one-time signature primitive that serves as the core building block for larger multi-signature, post-quantum schemes such as SPHINCS+.Why use hash-based signatures instead of RSA or ECDSA?Hash-based signatures only depend on the security of the underlying hash function, which is believed to remain safe even against quantum computers, unlike RSA or ECDSA.
Hash-based signatures only depend on the security of the underlying hash function, which is believed to remain safe even against quantum computers, unlike RSA or ECDSA.What test coverage does the project enforce?The project requires at least 80% coverage for functions, branches, and statements, verified through Vitest's coverage reports.
The project requires at least 80% coverage for functions, branches, and statements, verified through Vitest's coverage reports.Which cryptographic library does it build on?It uses the @noble/hashes package for the actual hash function implementations that power the WOTS+ signature scheme.
It uses the @noble/hashes package for the actual hash function implementations that power the WOTS+ signature scheme.What are similar projects?cpp-sdk, ethereum-sdk, crypto-js, hashsigs-solidity, hashsigs-rs, javascript-obfuscator, reticle, hashsigs-py
cpp-sdk, ethereum-sdk, crypto-js, hashsigs-solidity, hashsigs-rs, javascript-obfuscator, reticle, hashsigs-pyWhich topics is it in?post-quantum, hashing, cryptography, npm-package, javascript-library, agpl, testing, sdk, security, npm, nodejs, library
post-quantum, hashing, cryptography, npm-package, javascript-library, agpl, testing, sdk, security, npm, nodejs, library