Solana · fixed-term custody
Locks that outlive
the cryptography they’re built on.
QuantumLock holds your SPL tokens or SOL for a term you choose — and seals every lock with a lattice-based ML-DSA-65 signature that anyone can verify in their own browser.
Seal issued
ML-DSA-65 · lattice attestation · 3,309-byte signature
The problem
A lock is a promise about the future.
When you lock liquidity for three years, the question isn’t whether the cryptography holding it is sound today. It is whether it will still be sound on the day it opens. Every other locker on Solana answers that question with ed25519 — a curve whose security assumption has a known expiry condition.
Simulate an adversary
Drag to change how many error-corrected logical qubits they control.
340
logical qubits
Every other lock on Solana
ed25519 · 256-bit curve
Secure against every classical attack we know of — and against quantum machines of this size.
The QuantumLock seal
ML-DSA-65 · module lattice
Shor’s algorithm does not apply to lattice problems. No known quantum algorithm does better than a generic speedup here — which is precisely why NIST standardised it as FIPS 204.
Threshold estimate: ≈2,330 error-corrected logical qubits to break a 256-bit elliptic curve (Roetteler et al., 2017). Machines that size do not exist today — but a five-year lock is a five-year bet that they still won’t.
How it works
Three steps, one signature, no admin key that can rush the clock.
- 01
Deposit
Pick a token, an amount and an unlock date. Your wallet signs one transaction that moves the tokens into the QuantumLock vault. Flat fee, no percentage of your bag.
0.05 SOL per lock
- 02
Seal
The lock record — owner, mint, amount, unlock time, deposit signature — is signed with an ML-DSA-65 lattice key and committed with a SHA3-256 digest. You get a public proof page anyone can check.
Lattice attestation issued
- 03
Unlock
The countdown runs. Nothing can shorten it — the unlock time is inside the signed record. When it hits zero, claim, and the vault returns the full amount to the wallet that owns the lock.
Returned to the original owner
The seal
Cryptography you can check, not a claim you have to trust.
Post-quantum is an easy thing to put on a landing page. So every QuantumLock seal ships with the material needed to verify it independently — the algorithm, the public key, the exact bytes that were signed, and the signature itself.
Lattice attestation
ML-DSA-65 · FIPS 204Every lock record is signed with a module-lattice key: 1,952-byte public key, 3,309-byte signature. The proof page verifies that signature in your browser, against the published key — so a seal cannot be faked by us or by anyone else.
Hash commitment
SHA3-256 · Keccak familyEach lock's parameters are committed to a 256-bit SHA3 digest. Grover's algorithm only halves preimage security, which leaves a 128-bit margin against a quantum search — the reason hash-based commitments are considered quantum-safe as-is.
Lattice-bound release
RoadmapBinding the withdrawal path itself to the lattice key, so releasing a vault never depends on a curve signature. This is the layer we are building next, and it is why the seal format carries a version tag from day one.
Seal format is versioned — QUANTUMLOCK-SEAL-v1
0
Locks sealed
0
Currently locked
0
Released on time
0
Longest term (days)
What people lock
Time is the only guarantee that never needs enforcing.
Liquidity locks
Lock LP tokens and hand your holders a proof page instead of a promise. The seal is verifiable by anyone, without trusting your word or ours.
Team vesting
Put founder and team allocations behind a date that cannot be moved forward, and publish the link in your docs.
Presale cliffs
Hold allocation until a launch date so nothing can be dumped into your own liquidity on day one.
Locking yourself out
The most honest use case: put your own bag behind a term you cannot renegotiate at 3am. Conviction, enforced by a countdown.
Questions
The parts worth asking about.
Who holds my tokens while they are locked?
QuantumLock does. Deposits go to the protocol vault wallet, which is published in the footer and on every proof page — you can watch it on Solscan. The unlock time is fixed inside a signed record at the moment of deposit, and payouts only ever go back to the wallet that created the lock.
Can the unlock date be changed after the fact?
No. The unlock timestamp is one of the nine fields covered by the lattice signature. Changing it by even one second invalidates the seal, and the proof page would show the verification failing to anyone who looked.
What does it cost?
A flat 0.05 SOL per lock, paid in the same transaction as the deposit. No percentage of the locked amount, no fee on the way out.
What can I lock?
Any SPL token in your wallet, plus native SOL. The token picker reads your real balances when you connect.
What actually makes this post-quantum?
The attestation layer. Every lock is signed with ML-DSA-65, the lattice signature scheme NIST standardised as FIPS 204, and committed with SHA3-256 — neither of which Shor’s algorithm applies to. The signature and public key are published so you can verify them yourself rather than take our word for it.
What happens if I lose access to my wallet?
The lock pays out to the owner address recorded at deposit and nowhere else. If you lose the keys to that wallet, nobody can redirect the funds — including us. Lock from a wallet you are certain you will still control on the unlock date.
Set the date. Seal the vault.
One transaction, a countdown nobody can shorten, and a proof page you can hand to anyone who asks.