QuantumFinBuild here
QUANTUM EXPOSURE SCANNER

Is your public key
already out there?

A quantum computer attacks the public key, not the address. Most addresses hide the key behind a hash until you spend. Paste an address to see where yours stands.

TRY

Read-only. Paste a public address only. QuantumFin will never ask for your recovery phrase or private key. Lookups go straight from your browser to public explorers (Blockstream, mempool.space, PublicNode). Nothing is stored. Privacy policy

HOW EXPOSURE WORKS

One key. One hash.
One moment that changes it.

Shor’s algorithm on a large enough quantum computer could work back from a public key to its private key. It can’t work back through a hash. So the useful question is whether your public key has been published.

  1. PRIVATE KEYYours aloneSigns every spend
  2. PUBLIC KEYThe quantum targetRevealed when you sign
  3. ADDRESSA hash of the keyWhat you share to get paid
When the public key becomes visible
Address typeLooks likeKey becomes public
Pay-to-public-key (early Bitcoin)block rewards, 2009–2010Always The key is in the output itself
Taprootbc1p…Always The address encodes the key
Legacy & native SegWit1… · bc1q…On first spend Hidden until then
Script hash & multisig3… · bc1q… (long)On first spend The script and its keys appear
Ethereum & EVM accounts0x…On first transaction On every EVM chain at once
Solana accountsbase58, 32–44 charsAlways The address is the key

Keys can also leak off-chain: signed messages, shared extended public keys (xpub) and portfolio trackers all reveal them.

WHY QUANTUMFIN BUILT THIS

Finance runs on signatures.
The future needs proof.

QuantumFin brings zero-knowledge proofs together with quantum-resistant verification, so the check stays strong after Q-Day.