is your key already out?

an address is just a hash. the real public key stays hidden until the wallet sends something. after that anyone can rebuild it from the signature, and it sits there for good. paste an address and we’ll pull it out.

robinhood chain—
ethereum—
base—

read-only. we call public nodes, nothing gets signed.

public key · 64 byteswaiting for an address

the starting point for anyone with a big qubit machine

key lab

the replacements are already standard (NIST FIPS 203 and 204). run them here, in this tab. nothing leaves it.

ML-KEM-768

FIPS 203 · share a secret

ML-DSA-65

FIPS 204 · sign & verify

message

and verify again

vault beta

lock any file to a post-quantum key. ML-KEM-768 wraps a fresh AES-256 key per file. it all happens in this tab, the file never gets uploaded. not audited yet, so keep a normal backup too.

1 · your vault key

none yet

one key opens every file locked to it. share the public half with anyone who wants to send you something.

load key file

2 · lock a file

→ .hush

drop a file or tap to pick lock to (public half, leave empty for your own key)

3 · open a .hush

needs your key

drop a .hush file

how a key leaks

you receive

only the address is public. it’s 20 bytes cut from the key’s keccak hash, and hashes don’t run backwards.
you send once

the signature plus the tx is enough to rebuild the full key. the scanner above does exactly that.
someone builds the machine

give shor’s algorithm a machine with enough qubits and the public key gives up the private one. that machine isn’t built yet.

dates that matter

1994Shor’s factoring paper comes out.paper
Aug 2024NIST finalises ML-KEM, ML-DSA and SLH-DSA.nist
Nov 2024NIST draft plan: deprecate today’s public-key crypto by 2030, disallow by 2035.ir 8547
May 2025Gidney’s estimate for breaking RSA-2048 drops below one million (error-prone) qubits, about a week of running.paper

$HUSH

not out yet. when it is, holding some opens the heavier stuff: watchlists that ping you when a wallet first sends, batch scans, saved reports.

the scanner and the key lab stay free either way, no wallet needed.

status: not launched
chain: rh chain (id 4663)
contract: goes up on this page the day it launches. if you see one earlier, it isn’t ours.
off limits: we don’t want your 12 words, your keys, or any approval “to log in”. whoever asks isn’t us.

faq

is my wallet in danger right now?

no. nothing that exists today can pull this off. the point is knowing which wallets are open before something can.

how do you get my public key?

we find one tx the address sent, rebuild what it signed, and recover the key from the signature. then we hash it and check it gives back your address.

what should i do if it says exposed?

nothing urgent. for long-term coins, a fresh wallet that only receives keeps its key hidden.

do you store addresses?

no. the page talks straight to public nodes and explorers from your browser. we don’t run a server for it.

why does it say “couldn’t pull the tx”?

to show the key we need one tx the wallet sent, and only explorers keep that list. some of them block calls now and then. if it’s your wallet, a free signature shows the same key.