How popular is hashsigs-solidity on GitHub?

QuipNetwork/hashsigs-solidity has 11,209 stars and 34 forks on GitHub, and gained -2 stars in the last 7 days.

What license does hashsigs-solidity use?

QuipNetwork/hashsigs-solidity is released under the AGPL-3.0 license.

QuipNetwork/hashsigs-solidityPublic

Solidity contracts implementing hash based post quantum signatures

AI summary: A Solidity implementation of the Winternitz One-Time Signature Plus scheme providing post-quantum security.

Star on GitHub

Stars: 11.2K; +-2 today
Forks: 34
Watchers: 9
Open issues: 1
Open PRs: 0
Contributors: ~1
Commits: 28
Branches: 30

SolidityAGPL-3.0Created Mar 19, 2025Last push 2d ago+-2 stars this week+-5 this month

Quick answers

What is hashsigs-solidity?: A Solidity implementation of the Winternitz One-Time Signature Plus scheme providing post-quantum security.
What does hashsigs-solidity do?: This project provides a Solidity implementation of the WOTS+ (Winternitz One-Time Signature Plus) scheme, a specialized hash-based cryptographic algorithm. It introduces practical post-quantum signature verification directly into Ethereum smart contracts. By relying solely on secure hash functions rather than the discrete logarithm problem or integer factorization, WOTS+ is theoretically resistant to attacks from quantum computers. The implementation is designed to be efficiently deployed on EVM-compatible blockchains, allowing decentralized applications to verify signatures that are secure against future quantum cryptographic threats.
Who is hashsigs-solidity for?: Blockchain developers, cryptographers, and security researchers building EVM-compatible smart contracts that strictly require post-quantum cryptographic security guarantees.
How do I get started with hashsigs-solidity?: forge test -vv
How popular is hashsigs-solidity on GitHub?: QuipNetwork/hashsigs-solidity has 11,209 stars and 34 forks on GitHub, and gained -2 stars in the last 7 days.
What license does hashsigs-solidity use?: QuipNetwork/hashsigs-solidity is released under the AGPL-3.0 license.

Star history

since Jul 28, 2026

11.2K stars as of Oct 4, 2026. Measured daily since Jul 28, 2026; GitHub no longer exposes earlier star timestamps.

Contribution activity

commits per day, last 52 weeks

4 commits in the last yearLessMore

Signals and awards

derived from tracked data

Widely adopted
11,209 stars

What hashsigs-solidity does

This project provides a Solidity implementation of the WOTS+ (Winternitz One-Time Signature Plus) scheme, a specialized hash-based cryptographic algorithm. It introduces practical post-quantum signature verification directly into Ethereum smart contracts. By relying solely on secure hash functions rather than the discrete logarithm problem or integer factorization, WOTS+ is theoretically resistant to attacks from quantum computers. The implementation is designed to be efficiently deployed on EVM-compatible blockchains, allowing decentralized applications to verify signatures that are secure against future quantum cryptographic threats.

Blockchain developers, cryptographers, and security researchers building EVM-compatible smart contracts that strictly require post-quantum cryptographic security guarantees.

WOTS+ Implementation: Provides a complete, tested Solidity realization of the robust Winternitz One-Time Signature Plus cryptographic scheme.
Post-Quantum Resistance: Utilizes hash-based cryptography, protecting digital signatures against potential Shor's algorithm attacks from quantum computers.
EVM Compatibility: Specifically designed for efficient deployment and execution on Ethereum and other standard EVM-compatible blockchain networks.
Foundry Integration: Uses the modern Foundry toolkit for development, comprehensive testing, and streamlined deployment workflows.
On-Chain Verification: Enables smart contracts to natively and autonomously verify WOTS+ signatures without relying on external off-chain oracles.

Where teams use it

Quantum-Resistant Multisigs

Allows the creation of highly secure multi-signature wallets that remain safe even if standard Elliptic Curve Cryptography is broken by quantum computers.

Long-Term Data Notarization

Provides a verifiable way to sign and anchor critical documents on-chain with a strict guarantee of long-term cryptographic integrity.

Secure Cross-Chain Bridges

Enhances the fundamental security of cross-chain messaging protocols by utilizing advanced post-quantum signature verification.

Future-Proofing Smart Contracts

Enables forward-thinking developers to build decentralized applications that anticipate and mathematically mitigate the emerging threat of quantum computing.

Getting started: forge test -vv

README

main branch

WOTS+ Solidity Implementation

A Solidity implementation of the Winternitz One-Time Signature Plus (WOTS+) scheme.

Development

This project uses Foundry for development and testing.

Prerequisites

Install Foundry:

curl -L https://foundry.paradigm.xyz | bash
foundryup

Testing

Run the Foundry tests:

forge test -vv

The -vv flag increases verbosity to show more test details. Use -vvv for even more detailed output including stack traces.

Building

forge build

License

This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License along with this program. If not, see https://www.gnu.org/licenses/.

View on GitHub

Recent activity

commits and pull requests

Merge branch 'dependabot' into 'main'
rcarback committed e92d0b9 · 1mo ago
ci: build foundry on a base image so jq is available
rcarback committed 9cc84c7 · 1mo ago
ci: install jq for the vm.ffi test vector check
rcarback committed 11bd371 · 1mo ago
ci: add a Foundry build and test pipeline
rcarback committed 1705d55 · 1mo ago
chore: remove unused Hardhat toolchain and npm lockfile
rcarback committed ad137d6 · 1mo ago
Trim randomization elements to ChainLen and add verifyOrRevertClosed
#2 by parsaaba · updated 2mo ago
Merge branch 'structs' into 'main'
rcarback committed e542347 · 18mo ago
The public key segments were just the randomization elements. Include the actual public key segments in the test vectors instead
rcarback committed 9cd60b0 · 18mo ago
Use memory instead of calldata for randomization elements. This is more gas efficient due to the different access pattern. Specifically, for
rcarback committed 74d2b53 · 18mo ago
Switch to using structs
rcarback committed cca6a8a · 18mo ago
Whoops, make sure npm publish includes our contract code
rcarback committed 2cfd044 · 18mo ago

Recent open issues

view all

F3 (low): verifyWithRandomizationElements accepts publicSeed then ignores it
#3 · 1mo ago · by aeonframework · 1 comments

Code frequency

additions and deletions

+57 lines added, -7.8K removed over the last year.

Commits per week

last 52 weeks

4 commits in the last 52 weeks.

When work happens

weekday and hour

Commit volume by weekday and hour (UTC). Larger dots mean more commits.

Date	List	Rank	Stars gained
Feb 12, 2026	daily	#18	+168
Feb 11, 2026	daily	#14	+255