If you use Codex and Claude on the same codebase, how do you share context between them?

best read of the day

‼️ BREAKING: The private keys of 8 certificates from Indian certificate authority eMudhra were compromised, Mozilla says. Firefox blocked them within 3 hours. Each key should be a 116-digit number, but one was just 4. Anyone can guess them and forge HTTPS certs for any website.

they didn’t hack ledger. they didn’t exploit the code. they BOUGHT the company selling you the device. $86 million gone a company called CryptoBilis was an authorized ledger reseller in southeast asia. trusted. legit. sold ledgers for years a random chinese company quietly bought CryptoBilis from its malaysian owner made the original owner sign a confidentiality agreement. he couldn’t tell anyone the company was sold same brand name. same website. same “authorized reseller” badge. but different people behind it now the new owners started opening every ledger device before shipping soldered a tiny spy chip onto the board inside. repackaged it. sealed the box. shipped it the device looked normal. felt normal. worked normal but the spy chip was silently capturing your private keys the moment you set it up your seed phrase was sent to the attacker before you even finished writing it down hundreds of wallets across ethereum tron and bitcoin. all drained the guy who lost $5.3 million said “i did everything right. no leverage. no memecoins. i stored my funds on a hardware wallet like we’re all told to” he was right. he did everything right except his device had a parasite inside it that he couldn’t see ledger has now told CryptoBilis to stop all sales. told recent buyers NOT to set up their devices mark karpelès posted photos of the implant. normal board on top. spy chip below the most dangerous attack in crypto this year wasn’t a line of code it was a business acquisition

We’ve been predicting big new cryptanalysis advances. Seems like that might be starting. We don’t need just post-quantum cryptography, we also need post-AI cryptography, post-bugs cryptography, and more. Post-Everything Cryptography. 😊

Don’t reuse addresses as a best practice. There’s no need to panic because an Ethereum researcher is saying silly things. Remember, it’s an Ethereum researcher.

Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.