Our recommendation for Fusaka: https://t.co/cdYt8muRsd TLDR: - Smaller, faster forks to keep up w/ momentum - Target a small Fusaka fork by end of Q3, only PeerDAS - If slips, shift to H1 2026 & expand scope - Bigger fork would include ePBS & FOCIL for scalability & CR

Episode 4 of Core Notes from Core Devs is out now! Catch the Ethereum core developers at @offchainlabs discuss the latest happenings in @Ethereum development. This week we talk with @manunalepa and @jameshe_eth about their learnings from challenging times as core devs and advice for their past selves! Hosted by @ohyeahdavid. Time stamps: 0:49 One thing every Ethereum user should know 2:03 Takeaway from Holesky challenges 3:22 Moments of joy and frustration for core devs 6:20 Advice for a younger core dev

Prysm release v5.3.1 is here! Testnet operators are strongly encouraged to update to this release. There are many fixes and improvements from the Holesky upgrade incident. Mainnet operators are recommended to update to this release at their regular cadence. This release is packed with critical fixes for Electra and some important fixes for mainnet, too. Notable features in this release: - Ensuring that deleting a block from the database clears its entry in the slot->root db index. This issue was causing some operators to have a bricked database, requiring a full resync. - Updated go to go1.24.0. - Added a feature flag to sync from an arbitrary beacon block root at startup. - Updated default gas limit from 30M to 36M. Override this with -suggested-gas-limit= in the validator client. Check out GitHub for more details or join the conversation on Discord. Discord:https://t.co/ZBzSG03RZp Github:https://t.co/Uc2PYfDAit

Episode 3 of Core Notes from Core Devs is now out! Catch the Ethereum core developers at @offchainlabs discuss the latest happenings in @ethereum development. This week we talk with @terencechain and @jameshe_eth about the final preparations for the Pectra upgrade and how you could win $2M USD! Hosted by @ohyeahdavid 0:33 One thing every Ethereum user should know 1:35 Significant and exciting changes in the next Prysm release 2:36 Breaking down blob scalability and mempool bottlenecks 4:04 The importance of the 30-day buffer between testnet and mainnet upgrades 4:45 $2M Pectra bug bounty program 6:14 Chaotic times as a core dev

Prysm release v5.3.0 is here! Updating to this release is required for Holesky and Sepolia operators and it is recommended for mainnet users This release includes support for Pectra activation in the Holesky and Sepolia testnets! It also contains many fixes for Electra that have been found in rigorous testing through devnets in the last few months. Two notable features in this release: 1. There is a new file layout structure for storing blobs. Rather than storing all blob root directories in one parent directory, blob root directories are organized in subdirectories by epoch. This should vastly decrease the blob cache warmup time when Prysm is starting. 2. A feature which allows for the beacon database to remain a constant size once it reaches enough history to cover the weak subjectivity period Check out GitHub for more details or join the conversation on Discord. https://t.co/8vvZKS1zGa

Episode 2 of Core Notes from Core Devs is out now! 👀 Catch the Ethereum core developers at @offchainlabs discuss the latest happenings in @Ethereum development. This week we talk with @terencechain, @manunalepa, @jameshe_eth, and @preston_vanloon about scaling & accelerating Ethereum and how we think Ethereum governance can evolve. Hosted by @ohyeahdavid. Time stamps: 0:31 What's one thing from the past two weeks of developments that you wish every Ethereum user understood better? 1:39 What are some challenges to think about when implementing PeerDAS? 3:08 What are your thoughts on scaling Ethereum throughput in general? 4:53 What's one thing you would implement to improve Ethereum governance? 5:55 What do you think about the calls to accelerate Ethereum? 6:35 What's your favorite Ethereum conference or meeting?

The unsung heroes of Ethereum are the people behind testing and DevOps (like @ethPandaOps and @elbuenmayini ). People are drawn to shiny things—new research, the next big idea—but often take the backbone of Ethereum for granted. Prysm encountered consensus edge cases in both Mekong and Devnet5 that could have caused a fork on mainnet if left unnoticed. These tricky edge cases are typically caught only through tireless effort of those dedicated to breaking things. Next time you see someone from Ethereum DevOps or testing team, don’t forget to say thank you—and maybe buy them a beer

Introducing our new video series: Core Notes from Core Devs! Catch the Ethereum core developers at @offchainlabs discuss the latest happenings in Ethereum development. This week we talk about the Pectra upgrade including upcoming preparations for devs and changes in store for users. Time stamps: 0:09 What's one thing from the past two weeks of developments that you wish every Ethereum user understood better? 1:00 What does the Prysm team think about block builder specifications and does this differ from other teams? 2:07 What does the team think is the best approach to upgrading testnets? 3:52 Looking at the timeline discussions from the call, which changes in the coming months excite you the most? 6:23 We want your feedback!

Prysm client validators can now process blocks with 36M gas limits (up from 30M). This technical improvement enables greater network throughput while maintaining our commitment to decentralized, community-driven infrastructure. Building a better Ethereum.

Prysm Release 5.2.0 has arrived! Note that this is mandatory for all validator clients using mev-boost with a gas limit increase and highly recommended for all other clients, especially for users running v5.1.1 or v5.1.2. Some notable fixes and features in this release: 1. QUIC is enabled by default. This is a UDP based networking protocol with default port 13000. 2. This release has some improvements for raising the gas limit, but there are known issues with the proposer settings file provided gas limit not being respected for mev-boost outsourced blocks. 3. Signaling an increase for the gas limit now works perfectly for local block production. 4. Prysm can reuse blobs from the EL via engine_getBlobsV1 to potentially save bandwidth Check out GitHub for more details or join the conversation on Discord. https://t.co/Q65VCMCTSb

- Setting the gas limit is possible with the `--suggested-gas-limit` validator flag, not the proposer settings flag - Update to Prysm v5.1.3 (ETA: upcoming week) to avoid proposing a local block instead of an MEV-Boost block Summary: https://t.co/UAhK4oaC4o

The team @OffchainLabs continues to listen to users to bring the best experience w/ @arbitrum while @prylabs core devs are listening to users to continue steering mainnet forward We don’t run from competition, we stare it in the face, salute it, and get back to building

Over the past 90 minutes, we’ve seen 40 invalid blocks from the mev-boost pipeline. The root cause is still unknown, but all relayer and builder teams have been alerted. Client teams are engaged and providing support in every way they can. If anyone has insights or details about the issue, please share!

I wrote up some preliminary results on Prysm and Geth using the "get-blobs" optimization: https://t.co/9b9BBfUSFT Summary: - Good hit rate on retrieving blobs from the EL mempool - Good reduction in block import time - Observed fewer p2p msgs over the wire - Reduced download bandwidth, but upload increased. Results still inconclusive due to network asymmetric as few nodes are running. See report for more details.

Prysm Release v5.1.2 is here with improvements and new features! 1. The feature flag --enable-experimental-state has been flipped to "opt out" via --disable-experimental-state, bringing significant memory usage improvements at runtime. 2. Updates to libp2p’s gossipsub for better bandwidth stability and support for IDONTWANT control messages 3. The gRPC gateway has been deprecated. For JSON data, please switch to the standardized beacon-APIs 4. This is our first release utilizing pull request authors' entries directly from our https://t.co/HIMZiOS1PV 5. This also contains a hotfix for a bug in the implementation of the beacon api streaming events endpoint of 5.1.1. It's recommended to update to v5.1.2 at your convenience. Check out GitHub for more details or join the conversation on Discord. https://t.co/etoS69nLdt

New Prysm Release! V5.1.0 includes: 1. Tons of bug fixes/internal improvements, 100 changes related to bug fixes 2. Electra changes to participate in current devnets 3. Deprecation notice: GRPC Gateway and the HTTP versions of gateway APIs will be removed in the next release 4. Remote signer public key persistence with new flag --validators-external-signer-key-file: before restarts would wipe out remote signing keys that were added or removed via API 5. Experimental support for multiple beacon nodes using the REST API 6. Newly added Beacon-API endpoints Updating this release is recommended at your convenience. https://t.co/BabdXTanv0