tip 🐦‍⬛🐦‍⬛🐦‍⬛

The government does not want you to know about this community discord.gg/RBufxFFRmT

Just recently talked about this at the workplace, excited to read this writeup thanks

@Pu5chk1n Get well soon Budd!!

The next release of "The Dev Files" is going to be a little delayed. I need to focus on some mediacal issues this week and dont have access to my laptop.

@0x002timmy Peak opus right here

“[Industry] is cooked. Claude just came out with this new feature. I just one-shotted this.” The “one”-shot:

🚨 Breaking, Rāyān Vinklapor, Head of Media in Iran, was eliminated. #Iran #Israel #usa #airstrikes

@TheMoneyApe disable ecrecover

ETHEREUM IS GOING QUANTUM SAFE 🚨 VITALIK UNVEILS A 4-YEAR ROADMAP TO MAKE ETH FULLY QUANTUM RESISTANT BY 2029. 4 KEY VULNERABILITIES IDENTIFIED. 7 NETWORK FORKS PLANNED. THE BUILDING BLOCKS ALREADY EXIST. ETHEREUM GETTING READY FOR A BIG RALLY. 🚀

@joni_vrbt Mistral

USA has ChatGPT USA has Grok USA has Claude USA has Gemini USA has Llama USA has Copilot China has DeepSeek China has Qwen China has Ernie China has GLM China has Kimi China has MiniMax Europe has?

@VitalikButerin but anything using ecrecover onchain is doomed did I get that right lmao

Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8141 ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-st… firefly.social/post/farcaster…

@BobbysBong1 Wow that looks beautiful Sorry for your forced house arrest though 😂

the wind has me pinned in haha

Very cool write up. Learnt a lot. Not your keys not your coins!

The new American dream: a life in Europe.

alleged

good night

@geekbarchemist @YourAnonTV Ah ok nvm ure a web3 gaming shill Yeah had my attemtion Glhf with ur vibe coded rugpull

🚨⚡️BREAKING: UN panel says Jeffrey Epstein files suggest existence of a "global criminal enterprise" committing crimes against humanity

@geekbarchemist @YourAnonTV huh I had a pink cigarette once it was strawberry flavor from China and very disgusting

@MagellanQuest Off to Poland to get gas then head back home

I’m European. That means I can cross borders like they’re city limits. Schengen isn’t a treaty. It’s a superpower: 29 countries, ~450M people, one seamless space. 🇪🇺🛂✨ Where was your first ‘Schengen moment’?”

ramadan mubarak

@Diana_European They're a data Kraken it goes against our values and the GDPR

Or go to the hell. Fuck Peter Thiel! 🤡🐖🐀

Web3 gaming is not an if, it’s a when. As in, “when will I get my money back?”

@yo_Frizz these fuckers worth tens of millions $$$ vs one big electro magnet for $100

After seeing this, we need EMP grenades

@SumitM_X inodes

As a developer , Have you ever thought that WHY a BIG file gets deleted instantly, but copying it takes time.