LambdaClass✓

Security fix disclosure: PropAMM contract We fixed a critical bug in the PropAMM contract in main branch; our factories on Ethereum mainnet are not affected by this vulnerability. The vulnerability found was due to the PropAMM contract that had a leftover setup function, reinitializeV2, which anyone could call once on a newly created PropAMM. Calling it could let an exploiter point the PropAMM at a price feed they control and then trade against its vaults at any price they chose, emptying them. More information here: From our conversations with third parties interested in it and from the information we have seen on-chain, there should not be anyone affected. But if anyone has deployed their own factory, or their own PropAMM forking our code, from this repo's code before October 27, 2026, please follow the instructions below: revoke your vaults' approvals to the PropAMM or move the funds out of the vaults create a new PropAMM through our mainnet factory (address in docs/production.md) or from the latest main. Contact us at security@lambdaclass.com if you need help.

Great meeting with @serenita_luca! @SerenitaIO was one of ethrex's early adopters, and we enjoyed hearing more about the team's work on Vero. Excited to keep working together to bring more client diversity to Ethereum with @ethrex_client and @ethlambda_lean.

RT @rj_aligned: Leaving a long answer here but this is a great opportunity to refresh the basics of propAMMs and how they can help new assets such as local currency stablecoins access affordable on chain liquidity. The main difference between an AMM and a propAMM is how prices are set. In a traditional AMM like Uniswap, liquidity comes from multiple LPs, and prices are determined by a formula in the smart contract based on the liquidity available. In a propAMM, a single market maker provides the liquidity and actively updates the prices at which it's willing to buy and sell. This gives the MM more control over pricing and inventory management, while keeping all that liquidity accessible onchain. PropAMMs started on Solana, where they now process around $1B in daily volume, representing ~33% of spot DEX trading. On SOL/USDC, most propAMM trades offered better execution after fees than Binance and other major CEXs, even at their highest-volume trading tiers. On Ethereum, we're now seeing around $100M in daily volume and over $4.3B traded in total, with more propAMMs and liquidity coming soon. One reason this model works well is that MMs can constantly adjust their quotes to market conditions, reducing their exposure to stale prices. That allows them to quote tighter spreads without taking on as much risk. You can see this in the screenshots. For a $10k ETH/USDC trade, most propAMMs are quoting tighter spreads than Binance. FermiSwap, which has some of the deepest liquidity, quotes 1.39 bps vs. 4.51 bps on Binance (VIP9) and 12.10 bps on Uniswap v3. On USDC/USDT, FermiSwap's ask is just 0.10 bps above the reference price for a $1k trade. There's still a lack of depth on Ethereum for really big trades but small/medium size trades are already getting very good quotes, but we need more liquidity to offer the same pricing for larger trades. We think propAMMs make a lot of sense for long-tail assets. A project can work directly with an MM to provide efficient onchain liquidity and customize its pricing logic without needing large amounts of passive LP capital. This is especially useful for stablecoins pegged to local currencies. A single propAMM can quote multiple currencies against USDC and against each other, reusing the same USDC inventory instead of fragmenting liquidity across separate pools for every pair. Since May, we've been working with @alignedlayer, @class_lambda and @titanbuilderxyz on the infrastructure for propAMMs on Ethereum. We've built two things: - A router that provides a single interface to trade across different propAMMs, with additional features to prevent spoofing and support multileg trades. - A propAMM factory that includes both the smart contracts and offchain infrastructure MMs need to launch and run their own propAMMs. At @alignedlayer, we're also running an experimental propAMM called ElZorro together with @polfinance_, where we test new features with real trades and use what we learn to quickly iterate on the propAMM factory. We're now exploring bringing this infrastructure to other EVM chains such as Base and Robinhood. You can read more here: - - - -

@rj_aligned @0xMarcB @0xPolygon how does it work? Base is out main chain, but Solana, Polygon, Arc etc are also welcome

Miden mainnet is live with its first partners. We've been building the Rust and web SDKs and contributing across the stack, including the protocol and node. Practical privacy now has a live network. Access opens up from here.

Miden is now live on partner mainnet

Ghost in the hal kicked off today at @Exactas_UBA: a two-day hardware hackathon organized by ComCom, with 60+ participants building on a dev board from scratch. We're proud to sponsor it, and we gave our talk slot to the Cryptography and Distributed Systems Research Center. Its director, @pablodeymo, walked through the history of cryptography, and where the field stands today, focusing on the role of creativity in building cryptographic solutions. A pleasure to do it on the center's first anniversary.

Ethlambda Community Call

Ethrex Community Call

RT @ethlambda_lean: Back to the usual schedule! Community Call tomorrow, 3:30 PM UTC on X. We’ll do a recap of the last few weeks and what we’re focused on next.

New blog post out: @ethlambda_lean at the Cambridge post-quantum and fast finality workshops. More than 120 researchers and engineers together for a week of post-quantum cryptography, formal verification, fast finality, and hash functions. In this post, we go through what was discussed, where things are headed, and what we’re taking back to ethlambda.

RT @ethrex_client: We loved chibi, so we added partial stateful node support to ethrex. A node for your wallet that keeps only the accounts and storage you use, verifies the values it serves, and follows the chain without executing blocks. Your wallet gets local JSON-RPC, with no RPC provider to trust. In one Sepolia run: 29–34 MB of memory, about 3% of one core, and negligible disk usage beyond the binary. Anchoring took a couple of minutes while waiting for a peer that answered headers. Experimental and Sepolia-only for now, since it needs Glamsterdam’s block access lists. We’ve also added experimental EIP-8440 execution chain proof support, with off (default), observe, and require modes. Require serves state only at blocks covered by a verified proof. Let’s walk through what the node actually does 👇

Partial stateful node is here! Happy to announce chibi: a node that syncs in minutes and lets you transact through your own local RPC. Trust no one because every value is proven. It runs on practically any hardware. Need to send a transaction? Don't need to rely on RPC providers, just spin up chibi and send it right away. Live on Sepolia today and Hoodi next. 👇 demo below

We've been building the Miden client and contributing to the node and protocol alongside @0xMiden for a while now. Counting down to Partner Mainnet on October 26. Excited to see it go live!

Partner Mainnet in 7 days. October 26, 2026.

RT @ethlambda_lean: We spent last week in Cambridge for a workshop on post-quantum cryptography and fast finality. A lot of work is going into making sure Ethereum's move to PQ doesn't come with compromises. We love being part of this effort, and we'll keep pushing it forward.

RT @ethrex_client: ethrex v30.0.0 schedules Glamsterdam on Hoodi. If you run ethrex on Hoodi, this is the release you need to follow the fork. Hoodi activates Glamsterdam at timestamp 1793036568, which is 2026-10-26 17:42:48 UTC. This is the first ethrex release with the fork scheduled on Hoodi, so earlier releases stop following the chain at that point, and it needs to be paired with a consensus client release that ships the Hoodi Gloas config. Mainnet has no Glamsterdam time scheduled. ⚠️ L2: the prover and the SP1 guest move to SP1 6.9.0, and SP1 6 proofs need the SP1 v6.1.0 Groth16 verifier. An existing deployment's SP1 5 verifier rejects them whatever key is registered, so the order matters. Let every committed batch be verified before the upgraded sequencer commits anything, then upgrade the OnChainProposer and replace the verifier in a single Timelock call, upgradeToAndCall(newImplementation, upgradeSP1Verifier(newVerifier)), and register this release's verification key. Full procedure: Aligned mode is unavailable until Aligned ships SP1 6 support, and the OpenVM L2 prover backend is removed. L1 node operators are unaffected. The rest of the release is mostly hardening, on the paths where something outside the node decides how much work it does. JSON-RPC parsing is bounded in memory and the Auth-RPC token is checked before the request body is read. eth_getLogs and log filter polls are bounded in cost, serving eth/72 cells to peers is bounded in CPU, and what a peer's transaction announcements can make the node track is bounded. Maps keyed by contract- or block-chosen values are seeded, and MODEXP gas is charged before its operands are sized. Also in v30.0.0: - RPC: eth_getFilterChanges reports each new log once, and the receipts of blocks still held in memory come back in full. - Sync: snap/2 catch-up charges peers that cannot serve block access lists, and accounts left with no storage slots get the empty storage root. - Performance and zkVM guests: calldata, CALL arguments and CREATE initcode are no longer copied per call, so zkVM guests stop running out of heap. Finality pruning no longer piles up overlapping range deletes, and state-history journaling skips layers that are already final. - L2: the committer generates the prover input for batches another build sealed, so a sequencer that takes over, or batches committed again after a revert, can still be proven. If you run ethrex on Hoodi, upgrade before 26 October. Everyone else, upgrade at your convenience. No resync is needed.

RT @ethrex_client: The Hive tests for Heze devnet 2 are live, and ethrex is the first EL client ready to run them. Our heze-devnet-2 branch is already passing the full suite! The devnet itself hasn’t launched yet. Its planned scope includes: - FOCIL (EIP-7805) - Removal of the deposit and eth1data fields (EIP-8015) - Disallowing new validators with 0x00 withdrawal credentials (EIP-8365) - Quick Slots (EIP-8198)

At the latest ACDT meeting, we decided to rename the devnet branches to better reflect their scope. The FOCIL devnets are now called Heze and will include CL EIPs, while the Frames devnets are now called Bogotá and will include EL EIPs. The combined devnets that follow will be called Hegotá, following the usual naming convention. The launch of bogota-devnet-1 (formerly frames-devnet-1) is just around the corner, with EIPs 8141, 8250, 8272, and 7906 included. The latest execution spec tests release (bogota-devnet@v1.1.0) is already out, and we’re passing all the tests! We’re excited to see this devnet go live!

Last week, we were in Cambridge for a workshop on post-quantum cryptography, fast finality, and formal veritication. We joined +100 people from across the ecosystem, including cryptographers, researchers, and engineers. Ethereum needs to move toward a fully post-quantum future. We don't know when Q-Day will come, and that's exactly why we need to act now. The challenge is making that transition without compromising Ethereum. There's a lot of work ahead, and we're glad to contribute to it. Thanks to @ethereumfndn and @drakefjustin for bringing us together.

Ethrex Community Call

RT @ethrex_client: From our point of view, yesterday's ACDC decision on EIP-8025 was the wrong call for Ethereum's long-term interests. EIP-8025 proposes optional execution proofs, a first step toward the zkEVM roadmap, and the client teams declined to commit to it. Framing the proposal as an "optional feature" may have worked against it. Calling something optional makes it easy to dismiss as low priority. To be clear, it was a proposal, and proposals can be accepted or rejected; nothing obligated anyone to approve it. And it is true that this feature does not inherently require a hard fork. But that is precisely what makes the question of commitment unavoidable: with nothing at the protocol level forcing the work to happen, progress depends entirely on whether people are actually assigned to it. Execution proofs only become real if client developers implement them, if testing teams build the coverage they need, and if DevOps keeps the infrastructure running. Declining to prioritize the proposal means the work simply does not happen. The optionality was meant for operators, those choosing whether to enable execution proofs, not for the people deciding whether the work happens at all. Operators should be able to opt in regardless of which client they run, and a decision taken without all teams present cannot credibly settle a question that depends on all teams delivering. Optional proofs are the foundation of Ethereum's zkEVM roadmap. That roadmap is complex, and it demands extensive integration and testing across teams. Getting there requires a shared, sustained commitment. We need to test under realistic conditions and investigate failures before consensus depends on proofs, and that work should proceed alongside research into mandatory proofs. Every integration bug we uncover now is one we won't be discovering after consensus depends on it. The more groundwork we lay today, the more bandwidth we have later for the challenges specific to mandatory proofs, including the ones we haven't found yet.

hegota scoping ⚡ ACDC #189 - ultra tl;dr DFI: 🪓 7716: Anti-Correlation Attestation Penalties 🪓 8025: Optional Execution Proofs 🪓 8359: Beacon Block Reporting Field 🪓 8371: RowDAS generally liked EIPs, but teams found that they weren't urgent enough to schedule (7716, 8359, 8371) or that they could be tackled without CFI (8025) 5 more EIPs to assess next meeting video and summary:

Meet @Stabileoapp, an open-source structural analysis tool built by @ergodicgroup. It offers tools for both educational and professional use, from learning core structural analysis methods to more advanced engineering workflows. Still in active development, and looking for people to test it and contribute.

Stabileo has two main modes: Basic solves structures with the stiffness method with conceptual explanations, useful for learning. PRO adds finite elements, and we're developing reinforced concrete design and steel connections. You can switch between them at any point.

RT @alignedlayer: Lambda VM (built with @class_lambda and @3miLabs) is on Keccak today, and it isn't a final answer. We're working on making recursion faster, and that has us experimenting with different hashes, algebraic ones included. The longer version, with how each kind works inside, is in the post:

RT @alignedlayer: Lambda VM is an open-source zkVM for RISC-V being built in collaboration with @class_lambda and @3miLabs. to learn more about it, read the article on its principles: