Quantum Vault

I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography. The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices. (and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation) So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math. The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be? This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-. For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption. And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10. To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety. And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all. Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems. For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size). Concrete TLDR, my own personal views: * Hash-based > lattice-based, in those situations where hash-based is possible at all * For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ... * For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism. * If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**. * For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money" firefly.social/post/x/210783…

It’s so cool—I can’t wait to share our latest progress with everyone; it’s going even more smoothly than I expected!

Our AI found a bug that let anyone mint infinite XRP, with $94B at risk. It had been hiding in one of the most audited codebases in crypto for nearly a decade, and earned us the maximum $250K bounty. Here's how it went unnoticed, and how we found it.

One more thing worth highlighting: we've accounted for the scenario where your private key is compromised and your EOA wallet is drained — leaving you with no gas to act. For exactly this, we designed Gas Delegation Mode. After your authorized admin wallet signs the operation, simply switch to any wallet that holds gas and your vault executes normally. Your Quantum Vault remains yours, no matter what happens to your wallet. The only thing you ever need to protect is your password.

To prove the security of Quantum Vault, we've deployed a live vault on Robinhood, deposited 0.2 ETH, and published the admin credentials below. If you can crack it, the funds are yours to keep. --- Vault Address: 0xC7c0eE115e37BD1626590196776F61D00e71772b Admin Private Key: 0xa3a11f40cdc57971a14e898f11f22e933e78303cb01e7e0c3a40425d683cf60a Admin EOA: 0x3E4af70884e5ac930D0C946B9c1d5f1Dd7ee9027 --- You don't need to fund the admin wallet with gas. If you successfully crack the vault password, the admin wallet signature alone is sufficient — you can use your own wallet as the gas payer.

To prove the security of Quantum Vault, we've deployed a live vault on Robinhood, deposited 0.2 ETH, and published the admin credentials below. If you can crack it, the funds are yours to keep. --- Vault Address: 0xC7c0eE115e37BD1626590196776F61D00e71772b Admin Private Key: 0xa3a11f40cdc57971a14e898f11f22e933e78303cb01e7e0c3a40425d683cf60a Admin EOA: 0x3E4af70884e5ac930D0C946B9c1d5f1Dd7ee9027 --- You don't need to fund the admin wallet with gas. If you successfully crack the vault password, the admin wallet signature alone is sufficient — you can use your own wallet as the gas payer.

Can you lock your tokens and show proof of tech with a video demo!l? 0xe8c1aee9e02b9e6b5f3b82c601d7c168f1fd234b

Can you lock your tokens and show proof of tech with a video demo!l? 0xe8c1aee9e02b9e6b5f3b82c601d7c168f1fd234b

We will deposit these funds into the Robinhood chain and publicly release the wallet's private key.

To prove the security of Quantum Vault, we've deployed a live vault on Ethereum Mainnet, deposited 0.2 ETH, and published the admin credentials below. If you can crack it, the funds are yours to keep. --- Vault Address: 0xf57Da46317c45C88382a0A49cBFdF627BE1f2711 Admin Private Key: 0x3a84ae812fc058b6fb81cf93c5c24f06bc93ca09e7d25d4db2b97d0f29ceac96 Admin EOA: 0x1D8cD22365633eF77C47509C9992314c34CFA777 --- You don't need to fund the admin wallet with gas. If you successfully crack the vault password, the admin wallet signature alone is sufficient — you can use your own wallet as the gas payer.