Is this address's public key already on chain?
Paste Bitcoin or Ethereum addresses, one per line. Each one is classified here, in your browser, by the same code that the command-line quantum exposure report runs in its offline mode: by the type of the address alone. The page sends nothing anywhere.
What the labels mean
- exposed (on-chain evidence): the public key, or the script that holds the keys, is part of the output itself. A P2PK output carries the key; a P2TR output carries its output key (the tweaked public key); a bare multisig output carries every key in it. Anyone who reads the chain reads the key from the first such output.
- no on-chain evidence of exposure: the address commits only to a hash (P2PKH, P2WPKH, P2SH, P2WSH), or it is an Ethereum address, which is the last 20 bytes of the keccak-256 hash of the key. Nothing read in this mode shows the key. It says nothing about spends, which this mode does not read, about a key shown off chain, or about the future.
- unmeasured, with a reason: the line could not be classified (a wrong checksum, an unknown prefix, an OP_RETURN script). It is not a label.
Every result lists what the label rests on and what was not seen, in the words of the report, so that a reader knows how far it goes.
Why the public key matters
Bitcoin and Ethereum accounts are controlled by secp256k1 keys. A quantum computer able to run Shor's algorithm at a large enough scale would compute a private key from its public key. A key that is already readable from chain data could then be attacked at any time; a key that sits behind a hash is readable only once it is used. When such a computer will exist is not known, and this page makes no claim about it.
What this check does not see
- Spends. The first spend from a hash-type address shows its key (or its script) in the spending transaction, and the first transaction an Ethereum account signs shows its key through the signature. This page reads no chain, so an address that has already been used still reads "no on-chain evidence of exposure" here. To see spends, run the report in mode 2 against a node or an index you operate (below).
- Keys shown off chain: a shared extended public key, a signed message, a token permit, a transaction that was broadcast and never confirmed.
- Other chains that use the same key: a fork of the same history, a test network, an EVM chain where the same address is the same account.
The same judge, with the chain, on your own machine
git clone https://git.aere.network/aere-network/aere-quantum.git cd aere-quantum/exposure-report npm install --ignore-scripts --no-audit --no-fund node raport.mjs --mod 1 --adrese addresses.txt --iesire out/ # exactly what this page does node raport.mjs --mod 2 --adrese addresses.txt --esplora http://127.0.0.1:3000 --iesire out/
Mode 2 asks one target you name (your Electrum server, Esplora index, Bitcoin Core node or Ethereum JSON-RPC endpoint) and writes a dated report: a JSON, a Markdown for people and a signed envelope that binds the JSON. The modes, the evidence each verdict names and the limits are described in the report's README.
Nothing leaves this page
Once this page has loaded, a check makes no request: not to Aere Network, not to anyone. The addresses you paste stay in this tab. To see it yourself, open the network panel of your browser's developer tools before you press the button.
What runs here
One script, not minified: exposure.js. It is built from app.mjs (this page), from four modules of the published report copied byte for byte (clasifica.mjs, bitcoin.mjs, ethereum.mjs, limbaj.mjs), and from the open-source @noble/curves, @noble/hashes and buffer libraries, by build.mjs, which can rebuild the file and compare it byte for byte. What the browser lacks is supplied beside them: SHA-256 from @noble/hashes in place of Node's crypto module.