I'm happy to announce we are officially above replacement! Please welcome James, our third boy ❤️🎉

A statement on the comments from Secretary of War Pete Hegseth. anthropic.com/news/statement…

zkVM Standards v0 is here! 🎉 The zkEVM team has published three initial standards to reduce fragmentation across the zkVM ecosystem: • RV64IM+Zicclsm common ISA • C interface for precompiles • C interface for guest IO zkevm.ethereum.foundation/bl…

Tomasz gently frontran us :) but here's our summary for how we plan to implement the L1-zkEVM roadmap: ethereum-magicians.org/t/l1-… Let us know what you think and also feel free to join the discussions on #l1-zkevm & #l1-zkevm-protocol on the ETH R&D discord server!

Just published the first part of a series on how to think through Ethereum gas repricings required for block proving using zkVMs. Any repricing-related work is complex, and we should start walking through it as soon as possible. Link to article 👇 1/5

This marks the transition of Aztec from a deep-research project into a decentralized, community-owned privacy network. It is a key milestone required for Aztec to operate as a public good prior to our network launch early next year. Owned, steered, and sustained by the community that carried ZK from an academic niche into a cornerstone of ethereum. Over the past seven years, the ZK ecosystem collectively built the foundations this token now activates. PLONK, Noir, folding schemes, lookup arguments, private rollups - none of this was the sole achievement of one team. Our work has been shaped and strengthened by researchers, builders and orgs across the space. @zooko, @0xpolygon, @jbaylina, @zcash, @monero, @0xmiden, @aleo_HQ, @1HowardWu, @scroll_zkp, @bobbinth, @efbull, @feministplt, @zksync, @succinctfnd, @world, @succinctJT @recmo,@jensgroth16, @starknet, @elibensasson, @zkdragon, @srinathtv,  @aisconnolly, @taceo_IO, @luhelminger, @zkpassport, @yush_g, @uhhaboeck, @o1labs, @kevaundray, @khovr, @secparam, @drakefjustin, @dankrad - this list is just a fragment of the thousands of people it took to get ZK technology into a place where something like Aztec is possible. $AZTEC will launch through an entirely onchain, community-driven sale with no hidden allocations, no preferential classes, and no off-chain negotiations. The participants, not us, set the clearing price. There are no airdrops, no pre-market backroom rounds. The goal is simple: a fair, transparent, public distribution so that $AZTEC becomes a token owned by the ecosystem, not the company. This launch sits on years of shipped work. Aztec 1.0, the first shielding protocol on Ethereum. Aztec Connect, the first private rollup; PLONK, the first universal SNARK; @NoirLang, a purpose-built language for private smart contracts. This is a huge milestone for us but it is also just one more step in a marathon. Our goal as an institution is not to launch a token, it’s to launch a fully decentralised, Private World Computer. Onwards, together.

0/ Devconnect is coming to Argentina in November. The country has a rich crypto history, so rich that it predates crypto itself. I'm @smpalladino, engineer at @aztecnetwork, based in 🇦🇷 - and here’s my take on what makes this country so unique 🧵

Great post by @ignaciohagopian shining light on some of the efforts being undertaken by the zkEVM team. Out of many things, we spent the last six months iterating on the infrastructure needed to benchmark zkEVMs. We started by working with the Reth team to upstream a stateless implementation so that all zkEVMs being benchmarked use the same EEST tested implementation. Since then we’ve added EthRex with more clients to come, pending an important architectural decision. Unsuprisingly, there’s a lot of engineering work still left to do, not just with benchmarking, but with all of the components needed to ship zkEVMs on L1. The main idea here is to iterate quickly, thinking about the components and the system from first principles, so we form a coherent picture as to how everything fits together. This means we are not just working on ~~Slot~~ Real Time Proving, but also the changes needed to, enable the Consensus Layer to verify proofs, make proving more efficient on the Execution Layer, who creates the proofs, what exactly happens when a proof is being created, etc

I am excited to announce that I will be joining Tempo. This last year has been a turning point for crypto, where we have finally seen the outlines of our vision being materialized. While payments used to be front and center in the early days of crypto, I see a special opportunity to finally achieve this ambitious goal with relentless execution on both the technical and distribution fronts. I believe that the real world moment is now, and I want to make sure we do not miss this window to touch normal people’s lives everywhere in the world. I have dedicated the past several years to architecting and scaling blockchains, and I’m excited to leverage my learnings together with the very strong team being assembled at Tempo. My journey in Ethereum first started when I began working with the EF research team in 2018, and later joining full time in 2019. The project has greatly matured since then and with the soon coming Fusaka upgrade will implement PeerDAS, a significant scaling milestone I am proud to have contributed to. I am very happy to have played a role in leading to more people being able to use Ethereum and I look forward to continuing being able to do that. Over the last year, I have been involved in advancing Ethereum Foundation’s strategy and roadmap and I will remain a research advisor to the three strategic initiatives (Scale L1, Scale Blobs, Improve UX) at the Protocol Cluster at the EF. Ethereum has a strong set of values and technical choices that make it unique in the world. And Tempo will be a great complement, built using similar technology and values, whilst being able to push the boundaries on scale and speed. I believe that this will be of great benefit to Ethereum. Tempo’s open-source technology can easily integrate back into Ethereum, benefiting the entire ecosystem. Ethereum and Tempo are strongly aligned, as they are built with the same permissionless ideals in mind. I am looking forward to staying involved with the community and continuing to push Ethereum forward!

Most software for home cooks sucks and charges you a subscription forever. Saving recipes, swapping ingredients, handling dietary needs, making grocery lists... It's all a mess. So I built a tool called Olea to fix it. It's live today and free to use. ⬇️⬇️

have you tried aztec's testnet yet? play.aztec.network

The U.K. is coming after all encryption. washingtonpost.com/technolog…

New EIP: N/A By: - Kevaundray Wedderburn -Ben Adams -Gajinder Singh -Dustin 🔗 github.com/ethereum/EIPs/pul… This EIP introduces a flag for block builders to set a client-configured maximum number of blobs to include in a block. This aims to help builders with low bandwidth avoid including too many blobs, which could lead to network availability issues.🤖

In December, I had my 20-week full anatomy scan. @jonwu_ held my hand tightly while the technician squeezed jelly over my belly. As she performed the ultrasound, we looked at Baby Love Wu on a big screen. There everything was. A brain. A spine. Kidneys. Fingers. Two little ears. Two tiny kicking feet that, come April, I would be able to squeeze ever so gently. And finally, according to the technician: “A very strong heart.” We listened intently. The sound of our baby’s heartbeat took over the room, and I was overwhelmed with joy. Fast, powerful little thumps. I wanted to listen to it forever. The scan was unlike anything I have ever experienced before. It was a miracle. Over my first two trimesters, I learned that pregnancy can be mysterious, full of surprises, and scary. For the first time in my life, I was no longer in control of my body, hormones, and even emotions. If I wasn’t nauseous, I was beyond tired. I had to learn how to say no to opportunities, how to smile in sponsor meetings despite feeling seasick, and how to navigate confusing medical test results. There were moments I felt anxious, upset, and terrified. Until the 20-week appointment, I had little confirmation our baby’s body was developing correctly. But after seeing our baby at 20 weeks, I internalized something: I was born to do this. Born to create. And to create even in the face of uncertainty. Even after this scan, there is still a lot of uncertainty left on the now life-long journey of motherhood. And while there are a few variables in my control, I ultimately have to trust both the process and that I am doing my best. As I reflect on these past few months, I realized my motherhood journey feels a lot like my founder journey. Dare I say, motherhood is the ultimate founder mode. With SheFi, my first baby, I thought “How hard can it be?” With pregnancy, I had the same thought. The answer: very hard. But very worth it. As a founder, I experience the highs, lows, moments of fear – and an immense amount of trust in myself despite my fears. Would people sign up? Would sponsors support us? How do I grow this business? I have worked diligently, day after day, giving SheFi my all to make it a success. But the uncertainty never goes away. Similar stressful questions pop up during pregnancy. Is my baby healthy? Am I doing all the right things? Is this normal? But all I can do is try my best – and continue to trust. I’m doing that for both SheFi and my pregnancy. I had always wanted to be a mother, and my dream is finally coming true while continuing to build SheFi. Many of you have already met Baby Love Wu while I was 10 weeks pregnant in Singapore, or while I taught Season 12 and felt the first kicks. My pregnancy is the reason I couldn’t go to Bangkok, and it’s why I’ve had to put even more trust in my team. But every worthwhile journey in your life will come with uncertainty. I had no idea, after all those late nights making educational content and sending sponsor emails, that my hard work would grow SheFi to over 7,000 members worldwide. And every woman and non-binary person who joins SheFi is embarking on a transformative, uncertain journey of their own, in an effort to learn new skills and reinvent their futures. Of course the unknown is a little scary. But we can do it scared. And now, SheFi is about to have a little sibling. Baby Love Wu, launching April 2025.

🤖 New EIP: N/A By: - Parithosh Jayanthi -Kevaundray Wedderburn -Josh Rudolf -Dankrad Feist -Justin Traglia -Ignacio Hagopian -George Kadianakis 🔗 github.com/ethereum/EIPs/pul… This EIP provides hardware and bandwidth recommendations for validators and full nodes in the Ethereum network. It aims to establish clear system specifications to ensure meaningful benchmark comparisons, informed decision-making about protocol upgrades, and guidance for node operators. The proposal outlines specific requirements for storage, RAM, CPU, and network bandwidth for different node types, including full nodes, attesters, and block builders. It also suggests prebuilt hardware options and discusses considerations for storage, RAM, and bandwidth to support efficient network participation.

Thanks for the ping :) Let me know what you think of the following: In a world without FOCIL, we could go with the other option in the bandwidth document, where we still stick with 50/50 for local block building, but home stakers will be able to adjust the amount of blobs they include in a block accordingly. The rationale is that as a local block builder, if my bandwidth is 25/25 then this puts an upper bound on the number of blobs I can ever include* and if the blob limit is increased, I should be able to stay at this number. Doing it this way decouples an increase in blobs from the bandwidth restrictions of local block builders, or more generally it allows validators to fine tune the number of blobs they want to include based on their bandwidth/hardware, where the default minimum is set by the recommended bandwidth needed to attest, currently 25/25. If this argument is accepted, then the question shifts to "How does an increase in blob count affect attesters and by proxy full nodes in terms of download bandwidth" * unless the protocol becomes more bandwidth efficient

i know you didn't ask to see these but we finally got all of our wedding photos back and so here some are:

1/ Announcing the Noir 1.0 Pre-Release. Noir, the universal language of zk, is open-source, flexible, and now racing towards stability. We’ve seen a massive surge of interest as devs look for intuitive ways to build zk applications with a great DX. Keep reading to see what’s new 🧵