Quantum ID
Status: Planned · Group: Identity & security
A name only a post-quantum key can move.
alice.quantum or alice.pqc is a quantum-safe identity, seeded on a real quantum computer. The name is the handle, and inside it sit a Falcon wallet, a Falcon signing key, an optional multisig and the quantum proof of where it came from. Each ID is a Metaplex NFT.
| Field | Value |
|---|---|
| NFT | Metaplex Core |
| Wallet | Falcon smart account |
| Signature | Falcon-512 |
| Multisig | 2-of-3 post-quantum |
| Seed | Real QPU run |
| Proof | QPU receipt · slot |
| Price | {{QUANTUM_ID_PRICE}} |
| Renewal | {{QUANTUM_ID_RENEWAL}} |
Seeded via real quantum hardware
- Every ID is seeded on a real quantum computer, through IBM Quantum or Amazon Braket.
- QPU bits are mixed with randomness from your own device, so no one else, bb84 included, can compute your key.
- The QPU job is recorded on Solana with a bb84 proof receipt (hashes only), linked from the ID.
Security comes from Falcon-512. The QPU gives each ID its origin and a public, auditable record of it. See Hardware.
Six parts, one name
| Part | What it is |
|---|---|
| The name | alice.quantum or alice.pqc, a child name under roots bb84 holds in the Solana Name Service. Each ID is also a Metaplex Core NFT, so it shows up in wallets and can be traded. |
| bb84 Wallet | SOL and tokens sent to the ID land in a Falcon-512 smart account. One Falcon signature runs any instruction. |
| Signature | The ID holds the owner's Falcon-512 key, registered once on-chain, so any program can check a post-quantum signature from that name. |
| bb84 Multisig | Optional M-of-N post-quantum keys, for example 2-of-3 across phone, laptop and guardian, for teams and DAO treasuries. |
| Quantum proof | The bb84 proof receipt of the real QPU job that seeded the ID, plus the registration slot that proves the key existed before Q-Day. |
| Records | SOL address, post-quantum key commitment, ML-KEM key for encrypted messages, and an avatar drawn from the QPU shots. |
What you can do with an ID
| Action | How |
|---|---|
| Receive SOL and tokens | Send to alice.quantum; it lands in the bb84 Wallet |
| Spend | Sign with your Falcon key; a relayer pays the fee |
| Run a team treasury | dao.quantum with a 2-of-3 post-quantum multisig |
| Get encrypted messages | Others look up your ML-KEM key |
| Prove you're quantum-ready | "Registered before slot X with a PQ key", checkable by any program |
| Sell the name | Transfer the NFT, with a post-quantum signature from the current owner |
The hard part: a quantum-safe NFT
A plain NFT transfer needs only Ed25519, so on Q-Day an attacker could take the name even if the wallet is safe. Quantum IDs gate transfers with a Metaplex Core plugin: a transfer is approved only after a valid post-quantum signature from the current owner.
Before Q-Day, marketplace sales use a hybrid path (Ed25519 and a post-quantum signature). In Q-Day mode only the post-quantum path works.
Honest limits
- Names resolve through the bb84 app and SDK first; other wallets need to add the resolver.
- .quantum and .pqc are roots in the Solana Name Service, not official SNS top-level domains.
- Fees still need an ordinary Ed25519 payer (the relayer), which never controls funds.
Related
Updated about 1 hour ago