Creative Blockchain
primer · post-quantum

Five QUIP primitives, demystified.

QUIP — the Quantum Unit Interlock Pathway — is a post-quantum security layer that sits on the chain you already use. Nothing here relies on elliptic-curve maths that a quantum computer could unwind: ownership is proven with hash-based Winternitz one-time signatures (WOTS+), and value moves between QUIPs through an Interlock instead of a bridge.

Two layers matter. The asset layer holds post-quantum vaults and Interlock exchanges. The compute-consensus layer turns mining into useful work: the proof is the answer to a real optimization question. Every idea in this archive leans on one of the five primitives below.

One rule governs all of them: a WOTS+ key signs exactly once. A seed extension yields 256 keys, so any app that signs must show its nonce budget and rotate before it runs out. See it running in the QUIP Vault demo →

The three secrets

Add these in your Lovable project (Settings → Secrets) before pasting any mega-prompt. WOTS+ signing itself needs no secret — it runs client-side with @quip.network/hashsigs:

  • METAMASK_PRIVATE_KEYDeploys the QUIP verifier to your host chain. Fund on Sepolia via the Google Cloud faucet.open ↗
  • SEPOLIA_RPC_URLHost-chain HTTPS RPC endpoint.open ↗
  • ETHERSCAN_API_KEYFor npx hardhat verify after deploy.open ↗
  • docsquip.gitbook.io/docs — protocol reference and SDKs.open ↗
Live Sepolia verifier
0xfC6626C903E5C776b3715b00…7B2B55a4verified on Etherscan ↗

Linked library 0xE2c95D63FCfaf7b0545794aB…fF4aB00D.

post-quantum custody

QUIP vault deposit

336 ideas use this
kernel
a deposit into a QUIP-enabled contract that pairs the user's classical wallet with a post-quantum commitment and returns a vault ID plus the first WOTS+ public key
how it drives the UI
a 'sealed in a QUIP' panel showing the vault ID, the current WOTS+ public key hash, and the remaining nonce budget
EXAMPLE IDEAS
hash-based signing

WOTS+ one-time signature

330 ideas use this
kernel
a Winternitz One-Time Signature (WOTS+) generated with @quip.network/hashsigs, where every action burns the next one-time key and extends an immutable hash-chain of ownership
how it drives the UI
a growing chain of signed entries, each with its nonce, signature digest and a live 'verified' tick
EXAMPLE IDEAS
quantum-safe upgrade

Post-quantum key wrap

330 ideas use this
kernel
a post-quantum seed extension that wraps an existing ECC/ECDSA wallet key, so the classical signature is only accepted after the hash-based commitment unwraps correctly
how it drives the UI
a two-layer key badge — classical address on top, post-quantum commitment underneath — with a 'quantum-safe' state
EXAMPLE IDEAS
bridgeless exchange

Interlock propose · approve · claim

0 ideas use this
kernel
an Interlock exchange between two QUIPs that moves through propose, approve and claim states with a cancellable proposal timeout and a slashable approval timeout — no bridge, oracle or cross-chain message
how it drives the UI
a four-state timeline (proposed → approved → claimed, with the timeout branch) that both parties watch update live
quantum compute

Useful-work compute job

0 ideas use this
kernel
a 'what's the best / fastest / least costly…?' optimization job submitted to the Quip compute-consensus layer, where the proof-of-work is the answer itself and the result is returned with its solver attestation
how it drives the UI
a job card with the posed question, the solver attestation, and the returned optimum rendered back into the app
paid provenance

Pay-to-anchor

200 ideas use this
kernel
a 0.01 USDC payment over x402 on Base Sepolia that buys one on-chain anchor — the server verifies the settlement, then a relayer writes the user's WOTS+ seal into the QUIP verifier on the host chain
how it drives the UI
a numbered payment log running from 402 challenge to settled USDC to the host-chain anchor tx, every hash a clickable explorer link
EXAMPLE IDEAS
signed receipt

Paid provenance certificate

200 ideas use this
kernel
a 0.01 USDC payment over x402 that returns a relayer-signed provenance certificate over the WOTS+ head — a portable document anyone can verify without trusting the issuer
how it drives the UI
a certificate card with the signed fields, the issuing signer, and a 'recover signer' check that runs in the browser
EXAMPLE IDEAS
pay-per-unlock

Metered 402 gate

200 ideas use this
kernel
an HTTP 402 challenge in front of exactly one valuable operation — an export, a render, a full-resolution download — where each unlock is a single USDC payment bound to its settlement tx
how it drives the UI
a locked panel that states its price before you sign, plus an 'unlocks bought / used' counter beside the released payload
EXAMPLE IDEAS
verification market

Pay-per-verify

196 ideas use this
kernel
a paid verification service where a third party — buyer, festival, insurer — pays 0.01 USDC over x402 to have someone else's WOTS+ chain replayed and gets a signed verdict receipt back
how it drives the UI
a verdict panel with pass/fail per nonce, the local browser verification beside the paid one, and a keepable receipt
EXAMPLE IDEAS