Is My Neighbor Alice Quantum Safe?
Is My Neighbor Alice quantum safe? It's a question that barely registers in most ALICE community discussions, yet it cuts to the heart of long-term asset security for every holder. My Neighbor Alice is a blockchain-based multiplayer builder game whose ALICE token and in-game NFT assets inherit whatever cryptographic assumptions underpin the chain they live on. This article breaks down exactly which cryptographic schemes protect ALICE holdings today, what happens to those schemes when large-scale quantum computers arrive, and what migration paths, if any, exist for the project and its users.
What Cryptography Underpins My Neighbor Alice Today
My Neighbor Alice launched its token on the Ethereum Virtual Machine (EVM) and later integrated Chromia, a relational blockchain built on top of Ethereum infrastructure. Both environments rely on the same foundational signing algorithm: ECDSA (Elliptic Curve Digital Signature Algorithm) over the secp256k1 curve, which is identical to Bitcoin's curve and the default for virtually every EVM-compatible wallet.
ECDSA: How It Works in Plain Terms
ECDSA security rests on the elliptic curve discrete logarithm problem (ECDLP). When you create a wallet, the protocol generates a private key (a 256-bit random integer) and derives a public key by multiplying a generator point on the curve by that integer. The ECDLP states that going backward, deriving the private key from the public key, is computationally infeasible on classical hardware.
Every transaction you sign with an ALICE-holding wallet publishes your public key to the blockchain. The assumption is that no adversary can invert the ECDLP to steal funds.
NFT Assets and Smart Contract Signatures
My Neighbor Alice's land parcels, cosmetic items, and in-game collectibles exist as ERC-721 or ERC-1155 tokens on Ethereum-compatible infrastructure. Ownership transfers are authorised by the same ECDSA signatures. This means quantum risk is not limited to the fungible ALICE token. Every NFT in a player's wallet is equally exposed.
---
The Quantum Threat: What Q-Day Actually Means
"Q-day" refers to the point at which a cryptographically relevant quantum computer (CRQC) can run Shor's Algorithm at sufficient scale to break ECDSA and RSA in polynomial time, compared to the exponential time required by classical machines.
Shor's Algorithm and Elliptic Curves
Peter Shor's 1994 algorithm solves integer factorisation and discrete logarithm problems efficiently on a quantum computer. The ECDLP, the backbone of ECDSA, is a discrete logarithm problem. A quantum computer with roughly 2,330 stable logical qubits (per 2022 estimates from Craig Gidney and Martin Ekerå) could break a 256-bit elliptic curve key.
Current quantum hardware sits in the hundreds of noisy physical qubits. The gap is still significant, but the trajectory of progress, from Google's Willow chip to IBM's roadmap targeting thousands of logical qubits by the late 2020s, means the timeline is compressing.
The "Harvest Now, Decrypt Later" Vector
A subtler threat already active today is HNDL (Harvest Now, Decrypt Later). Nation-state and sophisticated adversaries can record encrypted blockchain data and signed transaction metadata now, then decrypt it retroactively once a CRQC is available. For public blockchains, every historical transaction is already public and permanently recorded. Any wallet that has ever broadcast a signed transaction has exposed its public key. That public key is the input Shor's Algorithm needs.
This means the exposure window for ALICE holders is not "when quantum computers arrive" but rather "right now, with retroactive decryption possible later."
---
Quantifying ALICE's Exposure
| Attack Surface | Cryptographic Scheme | Quantum Vulnerable? | Notes |
|---|---|---|---|
| ALICE token wallet (Ethereum/EVM) | ECDSA secp256k1 | Yes | Broken by Shor's Algorithm on a CRQC |
| Chromia account signatures | ECDSA / EdDSA variants | Yes | EdDSA uses Schnorr-like construction, also ECDLP-based |
| NFT ownership (ERC-721/1155) | ECDSA secp256k1 | Yes | Same as token wallets |
| Smart contract bytecode integrity | Keccak-256 (hash) | Partially | Hash functions resist Shor's; Grover's Algorithm halves effective security but 128-bit security remains with SHA-3 variants |
| HTTPS/TLS for game client | RSA / ECDH | Yes | Broken by Shor's; affects frontend communications |
The table above shows that virtually every layer of My Neighbor Alice's infrastructure that relies on asymmetric cryptography is vulnerable to a sufficiently powered quantum computer.
---
Does My Neighbor Alice Have a Post-Quantum Migration Plan?
As of mid-2025, My Neighbor Alice has not published a formal post-quantum cryptography (PQC) migration roadmap. This is not unusual. The vast majority of gaming-focused blockchain projects have not addressed quantum risk in their public documentation or tokenomics papers.
Why Gaming Projects Deprioritise PQC
Several structural factors explain the gap:
- Time horizon mismatch. Game studios operate on 12-to-36-month product cycles. Q-day is framed as a decade-away problem, making it low priority against immediate concerns like user acquisition and gameplay mechanics.
- Dependency on base-layer chains. ALICE cannot unilaterally upgrade its cryptographic primitives. The Ethereum base layer would need to hard-fork to support PQC signatures natively. Ethereum's own research into quantum resistance, via EIP proposals and Vitalik Buterin's writings on post-quantum account abstraction, is exploratory but not scheduled.
- Wallet compatibility. Even if a project introduced PQC signing at the smart contract level, standard MetaMask and hardware wallets do not yet support NIST PQC signature schemes (CRYSTALS-Dilithium, FALCON, SPHINCS+). Adoption would require a complete wallet ecosystem overhaul.
What a Migration Would Actually Require
For a project like My Neighbor Alice to achieve genuine post-quantum security, the following steps would be necessary:
- Base-layer upgrade or migration. Either Ethereum adopts native PQC signing (unlikely before 2030 on current timelines) or ALICE migrates assets to a PQC-native chain.
- Key re-issuance. Every holder would need to generate a new PQC key pair and prove ownership of their existing ECDSA wallet to claim assets on the new scheme. This is a massive operational lift.
- Wallet support. Users would need wallets capable of generating and storing lattice-based or hash-based key pairs, which are structurally different from ECDSA keys.
- Smart contract redeployment. All ERC-721/ERC-1155 contracts governing ALICE NFTs would need to be redeployed with PQC-compatible ownership verification logic.
- Cross-chain bridge security. Any bridging infrastructure connecting ALICE assets across chains would need PQC hardening independently.
None of these steps are trivial, and no single project can execute them in isolation.
---
How Lattice-Based Post-Quantum Wallets Differ
The NIST Post-Quantum Cryptography standardisation process, completed in 2024, selected several algorithms for standardisation. The most relevant for blockchain signing are:
CRYSTALS-Dilithium (ML-DSA)
Dilithium is a lattice-based digital signature scheme whose security rests on the hardness of the Module Learning With Errors (MLWE) problem. Unlike ECDSA, MLWE has no known efficient quantum algorithm. Shor's Algorithm cannot solve it; nor can Grover's Algorithm reduce its security to a practical attack level.
Key differences from ECDSA:
- Signature size. Dilithium Level 3 signatures are approximately 3,293 bytes versus 64 bytes for an ECDSA signature. This has meaningful implications for on-chain storage costs and gas fees.
- Key generation. Lattice key pairs are generated from structured random matrices rather than curve point multiplication. The private key is larger but generation is fast.
- Security foundation. Security is reducible to worst-case lattice problems, which have been studied for decades and show no quantum vulnerability.
FALCON (FN-DSA)
FALCON is another lattice-based scheme (NTRU lattices) that produces smaller signatures than Dilithium, closer to 666 bytes at Level 1 security, making it more blockchain-friendly. It is computationally more intensive to generate keys but efficient to verify.
SPHINCS+ (SLH-DSA)
SPHINCS+ is a hash-based signature scheme that relies only on the security of the underlying hash function (SHA-256 or SHAKE). It produces large signatures (around 8 KB to 50 KB depending on parameters) but offers the most conservative security assumptions because hash functions are quantum-resistant to a much greater degree than elliptic curves.
Practical Implications for ALICE Holders
A wallet built on Dilithium or FALCON today can sign transactions that a quantum computer with billions of qubits still cannot forge. For holders with significant ALICE or NFT positions, migrating assets into a PQC-capable wallet before Q-day is the pragmatic risk-reduction step. Projects like BMIC.ai are already building wallets around NIST-standardised lattice-based cryptography, offering holders a concrete migration destination rather than a theoretical future upgrade.
---
What Should ALICE Holders Do Now?
Waiting for Ethereum or My Neighbor Alice to solve this centrally is a passive strategy that transfers all timing risk to third parties. A layered approach is more resilient:
Short-Term Actions
- Minimise public key exposure. Use a fresh address for each major transaction to reduce the window during which your public key is observable on-chain. Standard HD wallet derivation paths make this straightforward.
- Hardware wallet storage. Keep large ALICE and NFT positions in offline cold storage. While hardware wallets do not provide PQC signing, they reduce hot-wallet attack surfaces.
- Monitor Ethereum PQC EIPs. Track Ethereum Improvement Proposals related to account abstraction and post-quantum signatures. EIP-7560 and related proposals are the likely vehicles for Ethereum's eventual PQC transition.
Medium-Term Actions
- Diversify into PQC-native infrastructure. As PQC-capable chains and wallets mature, holders can shift portions of their broader portfolio into environments with quantum-resistant signing baked in from genesis.
- Watch My Neighbor Alice's official channels. If the project publishes a PQC migration plan or announces a chain migration, early action during a snapshot or claim period typically yields the best outcome.
What Not to Do
- Do not assume base-layer upgrades will be automatic. Ethereum's PQC transition, when it comes, will likely require active user participation, not a silent background update.
- Do not conflate hash-function security with full quantum safety. Keccak-256 and SHA-256 are relatively quantum-resistant, but they protect data integrity, not wallet ownership. The signing layer is the critical vulnerability.
---
Summary: The Honest Verdict
My Neighbor Alice is not quantum safe. Its token, NFT assets, and underlying wallet infrastructure all depend on ECDSA over secp256k1, a scheme that Shor's Algorithm can break on a sufficiently powerful quantum computer. The project has no published PQC migration roadmap, and its dependency on the Ethereum base layer means any fundamental fix requires industry-wide coordination that is years away at minimum.
The risk is not immediate. Current quantum hardware cannot threaten ECDSA today. But the HNDL threat is active now, timelines are shortening, and the migration complexity is high enough that early preparation, rather than reactive scrambling, is the strategically sound position for serious holders.
Frequently Asked Questions
Is My Neighbor Alice quantum safe?
No. My Neighbor Alice relies on ECDSA over the secp256k1 elliptic curve for all token and NFT wallet signatures. ECDSA is broken by Shor's Algorithm on a cryptographically relevant quantum computer (CRQC). The project has no published post-quantum cryptography migration roadmap as of mid-2025.
What is Q-day and why does it matter for ALICE holders?
Q-day is the point at which a large-scale quantum computer can run Shor's Algorithm to derive private keys from public keys, defeating ECDSA and RSA. For ALICE holders, it would mean an attacker could forge wallet signatures and drain token or NFT holdings. Current estimates put a cryptographically relevant machine at roughly 2,330 stable logical qubits, a threshold that does not yet exist but that improving hardware roadmaps are targeting within the next decade.
What is the 'Harvest Now, Decrypt Later' threat to blockchain assets?
Harvest Now, Decrypt Later (HNDL) means an adversary records public blockchain data today, including signed transactions that expose public keys, and stores it for retroactive decryption once quantum hardware matures. Because blockchains are permanent public ledgers, every historical signed transaction is already harvestable. This makes the exposure window start now, not at Q-day.
Could Ethereum upgrade to make ALICE quantum safe automatically?
Not automatically. Ethereum is researching post-quantum account abstraction and signature schemes (CRYSTALS-Dilithium, FALCON), but any transition would require a hard fork, wallet ecosystem updates, and active user participation to re-key accounts. An Ethereum PQC transition is not scheduled and is unlikely before the late 2020s at the earliest.
What cryptographic algorithms are quantum resistant for blockchain use?
The NIST PQC standardisation process (finalised 2024) selected CRYSTALS-Dilithium (ML-DSA), FALCON (FN-DSA), and SPHINCS+ (SLH-DSA) as quantum-resistant signature schemes. All three are immune to Shor's Algorithm. Dilithium and FALCON are lattice-based; SPHINCS+ is hash-based. Signature sizes are larger than ECDSA, which has gas-cost implications on EVM chains.
What can ALICE holders do right now to reduce quantum risk?
In the short term: use fresh addresses to limit public key exposure, keep large positions in cold storage, and monitor Ethereum PQC improvement proposals. In the medium term: consider moving portions of holdings into wallets and infrastructure built on NIST-standardised post-quantum cryptography. Waiting for the project or Ethereum to act centrally is a passive strategy that transfers all timing risk to third parties.