← Opportunities

Post-quantum owners for Safe: hash-based signers (Winterlock)

Funder
Safe Foundation · Safe Grants / Security Track payout history not checked
Type / status
other · open
Amount
—
Deadline
unknown
Ecosystems
ethereumarbitrumoptimismbasestarknetzksync
Categories
securityinfradev toolingresearch
Tech stack
solidityrustcairostarkwotssphincs+
Apply
https://forum.safe.global/t/post-quantum-owners-for-safe-hash-based-signers-winterlock/7165
Source
https://forum.safe.global/t/post-quantum-owners-for-safe-hash-based-signers-winterlock/7165
Fit
46% · weak fit · The team's expertise in ZK, Rust, and cryptography aligns with the post-quantum and security focus, and their work on hash-based signers is a credible adjacent fit for Safe's security track, though they operate primarily in the Aleo ecosystem rather than Ethereum.
Trust
60% · model self-report 75% · first seen 2026-11-17 · v1
Verified
2026-11-17 · by extraction

Winterlock proposes replacing ECDSA owner keys in Safe smart accounts with hash-based signers (WOTS for daily signing, SPHINCS+ for recovery) that can be adopted in place without moving funds. The project seeks design feedback, a foundation open call or grant track for post-quantum owner support, help with Safe app integration, and audit funding through the security track. Milestones include spec and reference contracts, audited owner contract and migration tool on testnet, batched verification beta, and hardware wallet signing app.

Eligibility: Teams or individuals capable of building EIP-1271 hash-based owner contracts, migration tooling, STARK-based batched verification, and hardware wallet integration for Safe smart accounts.

Pipeline

Override status:

Funder track record · does Safe DAO actually pay grants?

payout history not checked · last check failed: web search unavailable: 4 of 6 searches failed

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

Trust breakdown (1/2 checkable facts verified)

SignalWeightResultNote
apply link0.0750%link not in source
funder0.075100%named in source
source quality0.1560%forum post
model confidence0.175%model self-report

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.570%model rated 70%
ecosystem overlap0.250%ethereum, arbitrum, optimism, base, starknet, zksync vs aleo
category overlap0.1550%security, infra, dev_tooling, research vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.133%solidity, rust, cairo, stark, wots, sphincs+ vs rust, leo, zk

Sources (1)

RoleDocumentFromFetched
primaryPost-quantum owners for Safe: hash-based signers (Winterlock)Safe forum2026-11-17

History (1)

vChangedFields
12026-11-17created

Extracted text

**TL;DR**  
Every Safe is ultimately controlled by ECDSA owner keys. Winterlock replaces them with hash-based owners — WOTS for daily signing, SPHINCS+ for recovery — that an existing Safe can adopt in place, without moving funds. Feedback welcome. We’d also ask the foundation to consider an open call for post-quantum owner support.

**Why now**  
This week Vitalik argued that AI-accelerated math could weaken elliptic-curve and lattice cryptography sooner than expected, and recommended hash-based constructions wherever possible. Ethereum’s post-quantum roadmap targets core L1 upgrades for 2029. Wallet migration will take longer.

For Safe specifically:

*   A Safe has no key of its own, but its owners are almost always ECDSA.
*   Every executed transaction publishes owner signatures, so each signer’s public key is recoverable. If ECDSA weakens, those keys are the first targets.
*   Owners can be swapped in place, without moving funds — avoiding the migration mistakes Vitalik says have cost him more than hacks.

**What we propose**

1.  **Hash-based owner.** An EIP-1271 contract that verifies WOTS signatures against a Merkle tree of one-time keys. Each key is valid for one Safe nonce only. A stateless SPHINCS+ key is the backup and recovery path.
2.  **Migration.** Tooling to add a Winterlock owner, raise the threshold, and retire the ECDSA owners, after checking modules, guards, and fallback handlers so no ECDSA path to the funds remains.
3.  **Shared verification cost.** A WOTS signature is about 2 KB and takes hundreds of hashes to check, far more gas than ECDSA. An off-chain prover can collect many signatures and post one STARK proof that they are all valid, splitting the on-chain cost across the batch. STARKs are hash-based, so the stack stays free of elliptic curves and lattices. Anyone can skip the batch and verify directly at full price. Batching is optional and cannot block a transaction.
4.  **Signing app.** Existing hardware wallets first; dedicated hardware only if demand justifies it.

Once owners are hash-based, publishing signatures on-chain no longer exposes a reusable key.

**Open questions**

*   Long term, does Safe prefer an EIP-1271 owner, a module, or a guard?
*   Some flows sign more than once per nonce (rejections, off-chain messages, permits). We plan separate key slots so no one-time key is reused. Better ideas welcome.
*   Would Safe{Wallet} flag owners whose public keys are already exposed?
*   Which chains first? Verification gas is easier to absorb on L2s.
*   Any DAOs or treasuries interested as design partners?

**What we’re asking for**

*   Design feedback.
*   A foundation open call or grant track for post-quantum owner support.
*   Help with Safe app integration, and audit funding through the security track.

**Rough milestones**

1.  Spec, reference contracts, test suite
2.  Audited owner contract and migration tool on testnet
3.  Batched verification beta, with direct verification as fallback
4.  Hardware wallet signing app

**About us**  
Johann & Max, Berlin  
winterlock.eth.limo