Registry
Claim your coins before a quantum computer can
The quantum threat to Bitcoin and Ethereum is that a private key can one day be worked out from a public key. On that day a thief and the true owner can both sign for the same coins, and nothing on-chain says which one is the owner. This registry settles that argument in advance. While only you control the key, you sign a short statement naming a post-quantum key of your own. We verify the signature, record the statement, and stamp it into Bitcoin. Nothing moves. What you get is a dated, unforgeable claim made before anyone else could make one.
Commitments
0
Addresses
0
Bitcoin
0
Ethereum
0
Register a commitment
Three steps, about two minutes, no transaction and no fee. Works with any wallet that can sign a message.
We read your address before you sign anything, because there are two kinds. An address that has sent a transaction has already published its public key, and it gets an ordinary commitment that anyone can verify today. An address that has only ever received still hides its key behind a hash, and a signature would give that key away. That one gets a sealed commitment: only a fingerprint of your signature is recorded and dated, and the key stays hidden until you choose to open it.
Open a sealed commitment
If you sealed a commitment earlier, this is where the signature from your claim file goes. We check that it matches the seal and that it proves control of the address. From then on anyone can verify the commitment, and it keeps the date it was sealed.
Look up an address
Anyone can check whether an address has a commitment on record, and re-verify the signature and the Bitcoin timestamp themselves.
What the signature proves. A Bitcoin signed message or an Ethereum personal_sign signature can only be made with the private key of the address. We recover the public key from the signature and derive the address from it; if they match, the statement was made by whoever controls the coins. Only the public half of your post-quantum key is ever sent to us.
What the timestamp proves. Each record is hashed and submitted to OpenTimestamps, which commits it into a Bitcoin block. Once confirmed, the proof shows the claim existed before that block, and any Bitcoin node can check it with no trust in us. The record cannot be backdated after the fact, which is the whole point.
What it does not do. It does not move your coins, protect them, or change how the chain works. It is evidence. When a chain adopts a post-quantum migration path, or when a dispute reaches a custodian, an exchange or a court, the holder with the earliest verified commitment has the stronger claim. Pair it with Canary to know the moment your key is exposed, and see Exposure to check whether it already is.
In plain words, three things a commitment is not.
- It is not ownership of the coins. It records that on a given date, the person who controlled this address chose this quantum-safe key. If you later send the coins to someone else, that transfer is yours and it stands. The buyer becomes the owner and can file their own commitment for their own address.
- It cannot bring coins back. Nothing here can reverse a transaction. Bitcoin and Ethereum have no undo, and the registry does not add one.
- It settles one argument only. If one day two people can both sign for the same address because a quantum computer recovered the key, the record shows which of them was here first. The lookup above shows what the address holds today, so a record for an address that was emptied long ago is read for what it is.
Formats. Bitcoin: legacy, SegWit and wrapped SegWit addresses with the standard signed-message scheme. Taproot needs BIP-322 and is next. Ethereum: any externally owned account with EIP-191. Post-quantum key: ML-DSA-65 (FIPS 204). Everything is readable at /api/registry?address=…, and the statement format is part of the Proof of Quantum Solvency specification.