# consensus Published articles for consensus. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Lowering Slot Time and Validator Economics DevFeed: [Lowering Slot Time and Validator Economics]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-19T10:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Latency](), [Protocol (disambiguation)]() Tags: [blockchain](), [blockchain-technology](), [consensus](), [crypto-news](), [cryptocurrency](), [defi](), [infrastructure](), [latency](), [nfts](), [performance](), [podcasts](), [protocol](), [reports](), [solana](), [solana-ecosystem](), [upgrades](), [web3]() ### AI overview Solana plans to reduce slot times from 400 ms to 200 ms. The article examines possible effects on latency, arbitrage, sandwich MEV, validator rewards and costs, voting frequency, and consensus performance, while noting that some impacts require empirical mainnet monitoring. ### Source excerpt Solana will reduce its slot times from 400ms to 200ms. This change will make the protocol more competitive in terms of latency. Here we explore some possible implication on validators economic. ## Google Cloud: PostgreSQL community contribution updates DevFeed: [Google Cloud: PostgreSQL community contribution updates]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-07-10T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [PostgreSQL](), [Google Cloud Platform (GCP)](), [Google](), [Open Source](), [Replication]() Tags: [architecture](), [collaboration](), [community-contribution](), [conference](), [consensus](), [contribution](), [google](), [google-cloud](), [open-source](), [postgresql](), [replication](), [technical](), [updates]() ### AI overview Google Cloud recaps its participation in 2026 PostgreSQL community events, including discussions of logical replication, global index architecture, DDL replication, and AI-assisted development workflows. ### Source excerpt by Dilip Kumar, Cloud SQL for PostgreSQL & Matt Cornillon, Sales EMEA Google Cloud is deeply committed to the long-term success of the PostgreSQL ecosystem. Our involvement goes beyond providing PostgreSQL managed services; it's also about active participation in the open source communities through technical contributions, leadership in conference committees, and sharing architectural insights that benefit all users. Following is a recap of recent events Google Cloud participated in. PGConf.dev 2026 Serving as a vital developer-centric hub, PGConf.dev provides a unique opportunity for collaboration with the full assembly of senior PostgreSQL committers. This gathering is essential for aligning technical efforts and shaping the future project roadmap. Key Highlights Participation focused on strategic coordination with PostgreSQL committers regarding logical replication development, and a consultation on global index architecture. High community interest confirms the Global Index feature solves a vital architectural requirement for enterprises. Established community consensus to pursue a deparsing-based architectural approach for DDL replication. Google Cloud Sessions Dilip Kumar, a PostgreSQL contributor from Google Cloud, presenting "Experimenting with a Global Index in PostgreSQL" at pgconf.dev 2026 in Vancouver. He is speaking at a podium next to a presentation slide detailing the Global Index storage architecture and PartitionIdentifier management. Session Title Session Type Speakers/Led by Experimenting with a Global Index in PostgreSQL: Design, Implementation, and Challenges Technical Talk Dilip Kumar Unconference: Global Indexes Unconference Session Dilip Kumar Unconference: Logical Replication: Warts and Missing Pieces Unconference Session Hannu Krosing PGConf India 2026 Key Highlights The three-day conference was divided into a training day followed by two days of sessions. More than 580 participants attended the conference over three days. The conference se ## Scalable Leader Leases for Distributed SQL Databases: CockroachDB at SIGMOD 2026 DevFeed: [Scalable Leader Leases for Distributed SQL Databases: CockroachDB at SIGMOD 2026]() Original publisher: [Read original article]() Author: Rebecca Taft Published: 2026-05-26T00:00:00Z Content type: release Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [distributed-systems](), [Databases](), [Cockroach Labs](), [SQL](), [Raft](), [systems](), [health checks]() Tags: [2026](), [cockroach-labs](), [cockroachdb](), [consensus](), [distributed](), [paper](), [sql]() ### AI overview Cockroach Labs announces a SIGMOD 2026 paper on scalable leader leases for multi-consensus groups in CockroachDB. The paper addresses lease-management overhead in distributed SQL databases, where coordinating leases across very large numbers of replicated data ranges can consume CPU and slow recovery from failures. ### Source excerpt We are pleased to announce that Cockroach Labs has a new paper appearing at SIGMOD 2026: Scalable Leader Leases For Multi Consensus Groups in CockroachDB. ## Dropbox's Former Most Senior Eng: Building Great Systems and Advice for the AI Era | James Cowling DevFeed: [Dropbox's Former Most Senior Eng: Building Great Systems and Advice for the AI Era | James Cowling]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-05-25T10:00:57Z Content type: opinion Language: en Sources: [The Developing Dev]() Topics: [systems](), [distributed-systems](), [Concurrency](), [Transactions](), [Computer science](), [Replication](), [Protocol (disambiguation)]() Tags: [concurrency](), [consensus](), [distributed](), [distributed-system](), [distributed-transaction](), [protocol](), [replication](), [systems](), [technical](), [transactions]() ### AI overview A podcast interview with James Cowling, CTO of Convex and former senior engineer at Dropbox, about designing abstractions and large-scale transactional systems. Cowling discusses Granola, distributed transaction coordination, concurrency, Byzantine fault tolerance, and career advice in the context of AI. ### Source excerpt Transcript & Audio ## Building High Availability PostgreSQL Clusters with Patroni and Other Integrated Approaches DevFeed: [Building High Availability PostgreSQL Clusters with Patroni and Other Integrated Approaches]() Original publisher: [Read original article]() Author: Agus Syafaat Published: 2026-05-21T07:20:00Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [postgresql clusters](), [PostgreSQL](), [Availability](), [Replication](), [Resilience](), [Automation](), [configuration](), [Open Source]() Tags: [automation](), [availability](), [configuration](), [consensus](), [database](), [distributed](), [failover](), [ha](), [high-availability](), [open-source](), [patroni](), [postgresql](), [postgresql-clusters](), [recovery-repair](), [replication]() ### AI overview This article explains how to build highly available PostgreSQL clusters with Patroni and related tools. It describes Patroni's use of replication, distributed consensus, a distributed configuration store, leader election, health checks, and YAML configuration to support automated failover. It also discusses operational challenges and the possible use of ClusterControl in the workflow. ### Source excerpt In modern application stacks, downtime is a direct threat to business continuity, customer trust, and revenue. Regardless of whether it is an e-commerce platform, a fintech application, or a critical internal system, the expectation is 24/7 availability, underscoring the critical importance of High Availability (HA) and automated failover mechanisms within PostgreSQL clusters. HA ensures that [...] The post Building High Availability PostgreSQL Clusters with Patroni and Other Integrated Approaches appeared first on Severalnines. ## Instrumenting AI: Multi-master replication and the split brain problem DevFeed: [Instrumenting AI: Multi-master replication and the split brain problem]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-05-17T00:00:00Z Content type: article Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [distributed-systems](), [Databases](), [AI Infrastructure](), [Raft](), [Availability](), [Network]() Tags: [ai](), [ai-infrastructure](), [conflict-resolution](), [consensus](), [database](), [distributed-systems](), [network](), [partitions](), [paxos](), [raft](), [split-brain]() ### AI overview The article explains how multi-master replication can produce split-brain behavior during network partitions. Both masters may accept conflicting writes, and reconciliation after the partition can discard valid data through last-write-wins rules. It presents Raft and Paxos quorum requirements as a way to prevent a second active brain. ### Source excerpt In multi-master replication every node accepts writes, so when the network partitions both masters stay active and accept conflicting writes into isolated silos. On heal, automated conflict resolution usually falls back to last-write-wins, which blindly discards valid data. Raft and Paxos prevent this by requiring an odd node count and a strict majority: an isolated leader cannot reach quorum, so it steps down instead of forming a second brain. ## Docker vs Kubernetes DevFeed: [Docker vs Kubernetes]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-05-11T12:32:56Z Content type: comparison Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [Docker](), [Kubernetes](), [Docker Compose](), [Containers](), [Orchestration]() Tags: [ci](), [compose](), [consensus](), [containers](), [docker](), [git](), [go](), [kafka](), [kubernetes](), [orchestration](), [redis]() ### AI overview This comparison explains that Docker packages and runs software, while Kubernetes manages applications at scale. It describes Docker's components, Compose, and Swarm, and outlines where Docker works well and where Kubernetes is more suitable. ### Source excerpt (4 min read) | The real difference that actually matters, how to decide, where teams go wrong, and more... ## Modernizing the Facebook Groups Search to Unlock the Power of Community Knowledge DevFeed: [Modernizing the Facebook Groups Search to Unlock the Power of Community Knowledge]() Original publisher: [Read original article]() Author: Shubhojeet Sarkar; Shengbo Guo; Guohao Zhang; Woon Jo; Laura Vig Published: 2026-04-21T16:00:19Z Content type: article Language: en Sources: [Meta ML Applications]() Topics: [Meta](), [systems]() Tags: [architecture](), [automated](), [consensus](), [discovery](), [engineering](), [facebook](), [improvements](), [meta](), [ml-applications](), [model](), [retrieval](), [search](), [validation]() ### AI overview Meta describes a modernization of Facebook Groups Search using hybrid retrieval and automated model-based evaluation. The article explains how the changes address discovery, content consumption, and validation challenges in community search, while reporting improvements in engagement and relevance without increased error rates. ### Source excerpt We've fundamentally transformed Facebook Groups Search to help people more reliably discover, sort through, and validate community content that's most relevant to them. We've adopted a new hybrid retrieval architecture and implemented automated model-based evaluation to address the major friction points people experience when searching community content. Under this new framework, we've made tangible improvements [...] Read More... The post Modernizing the Facebook Groups Search to Unlock the Power of Community Knowledge appeared first on Engineering at Meta. ## Checkpoint #9: Apr 2026 DevFeed: [Checkpoint #9: Apr 2026]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2026-04-10T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Protocol (disambiguation)]() Tags: [2026](), [compatibility](), [complexity](), [consensus](), [ethereum](), [feature](), [implementation](), [protocol](), [research-development](), [scheduled](), [state](), [update](), [upgrade]() ### AI overview This checkpoint summarizes Ethereum core development. Glamsterdam implementation is progressing, but ePBS, gas repricing, and Block-level Access Lists remain technically complex. Hegotá has selected FOCIL as a major feature and plans work on Account Abstraction as a minor feature, while developers prepare additional devnets. ### Source excerpt Ethereum's All Core Developer calls can be a lot to keep up with, so this "Checkpoint" series aims for periodic high-level updates, depending on what's happening in core development. See the previous update here. !image... ## How Split Brain Happens in Distributed Databases and How It Gets Fixed DevFeed: [How Split Brain Happens in Distributed Databases and How It Gets Fixed]() Original publisher: [Read original article]() Published: 2026-03-31T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Databases](), [Network](), [Replication](), [CAP theorem]() Tags: [consensus](), [databases](), [distributed](), [failed](), [false-positives](), [partition](), [replication](), [split-brain]() ### AI overview This tutorial explains how split brain occurs in distributed databases when a network partition causes multiple nodes to become primary and accept conflicting writes. It discusses why timeout-based failure detection can create false positives and introduces the distributed consensus complexity motivated by this failure mode. ### Source excerpt . [How Split Brain Happens in Distributed Databases and How It Gets Fixed](split-brain-in-distributed-databases-cover... ## Active-Active MySQL Group Replication Best Practices DevFeed: [Active-Active MySQL Group Replication Best Practices]() Original publisher: [Read original article]() Author: Paul Namuag Published: 2026-03-11T12:54:52Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [MySQL](), [Replication](), [Scalability](), [Availability](), [Transactions]() Tags: [availability](), [best-practices](), [consensus](), [consistency](), [deployment-scaling](), [high-availability](), [mgr](), [mysql](), [mysql-group-replication](), [replication](), [scalability](), [transactions]() ### AI overview This article explains active-active MySQL Group Replication, where multiple primary members accept concurrent writes that are synchronously replicated and coordinated through consensus and write-set certification. It discusses scalability limits, transaction conflicts, rollback surges, and operational considerations for production deployments. ### Source excerpt In MySQL Group Replication (MGR) or Group Replication, an active-active configuration allows multiple group members to accept concurrent write transactions. These writes are coordinated through a consensus-based group communication system (GCS) and validated via write-set certification to preserve global transactional consistency as defined by the Group Replication protocol. active-active mode is designed for write scalability. [...] The post Active-Active MySQL Group Replication Best Practices appeared first on Severalnines. ## Ethereum Foundation Begins Staking Approximately 70,000 ETH From Its Treasury DevFeed: [Ethereum Foundation Begins Staking Approximately 70,000 ETH From Its Treasury]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2026-02-24T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Resilience](), [Open Source](), [cloud-infrastructure]() Tags: [beacon](), [consensus](), [distributed](), [ethereum](), [hardware](), [infrastructure](), [open-source](), [operational](), [organizational](), [policy](), [resilience](), [software](), [yield]() ### AI overview The Ethereum Foundation has begun staking approximately 70,000 ETH from its treasury, directing rewards back to the treasury. It uses the open-source Dirk and Vouch software, minority client pairings, hosted infrastructure, and self-managed hardware to support validator resilience and client diversity. ### Source excerpt The Ethereum Foundation has begun staking a portion of its treasury, in line with its Treasury Policy announced last year. Approximately 70,000 ETH is being staked with rewards directed back to the EF treasury.... ## The Future of Ethereum's State DevFeed: [The Future of Ethereum's State]() Original publisher: [Read original article]() Author: Wei Han Ng; Carlos Pérez; the Stateless Consensus team Published: 2025-12-16T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [data](), [Database]() Tags: [consensus](), [database](), [ethereum](), [infrastructure](), [network](), [research-development](), [smart-contract](), [state](), [stateless]() ### AI overview A proposal from Ethereum's Stateless Consensus team examines the growing size of Ethereum's state, which includes accounts, contract storage, and bytecode. It explains how state growth increases storage, database, RPC, and syncing demands, potentially making the network more expensive and harder to decentralize. ### Source excerpt Disclaimer: The following blog is a proposal from the Stateless Consensus team. Content may not imply consensus views, and the EF is a broad organization that includes a healthy diversity of opinion across Protocol and beyond that together strengthen Ethereum. Special thanks to Ladislaus von Daniels and Marius van der... ## An Engineer's Guide to Influence (Part One) DevFeed: [An Engineer's Guide to Influence (Part One)]() Original publisher: [Read original article]() Author: Sidwyn Koh Published: 2025-09-06T13:06:40Z Content type: tutorial Language: en Sources: [Path to Staff]() Topics: [Framework](), [Meta]() Tags: [collaboration](), [consensus](), [framework](), [guide](), [how-to](), [influence](), [metric](), [objectives](), [service](), [teams]() ### AI overview This guide explains how engineers can influence decisions without formal authority. Part One covers understanding stakeholders' goals, building private consensus, and using the Minto Pyramid to present a case. ### Source excerpt How to turn your ideas into reality - even without authority ## HoliPaxos: Towards More Predictable Performance in State Machine Replication DevFeed: [HoliPaxos: Towards More Predictable Performance in State Machine Replication]() Original publisher: [Read original article]() Author: Aleksey Charapko Published: 2025-08-12T20:42:29Z Content type: article Language: en Sources: [Aleksey Charapko]() Topics: [Replication](), [Protocol (disambiguation)](), [Algorithms](), [Algorithms, Complexity]() Tags: [consensus](), [management](), [network](), [other-thoughts](), [paper-review-and-summary](), [partitions](), [paxos](), [performance](), [protocol](), [replication]() ### AI overview The article introduces HoliPaxos, a paper proposing orthogonal optimizations to the classical MultiPaxos state machine replication protocol. The changes target more stable performance during slow-node conditions, network partitions, and log management while preserving MultiPaxos behavior in the common case. ### Source excerpt I will be presenting our new paper, "HoliPaxos: Towards More Predictable Performance in State Machine Replication," at the VLDB'25. Feel free to ping me if you are there and want to chat! This paper explores several orthogonal optimizations to the classical MultiPaxos state machine replication protocol to improve its performance stability in the presence of [...] ## How Do Committees Fail To Invent? DevFeed: [How Do Committees Fail To Invent?]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-08-11T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [Development](), [Web platform](), [W3C]() Tags: [bias](), [browsers](), [consensus](), [development](), [engineering](), [standards](), [web-platform](), [webdev]() ### AI overview The article applies Conway's Law to standards development organizations, arguing that a "fifth column" problem can arise when delegates conceal their intentions through objections or silence. It examines how open membership, veto-heavy rules, and poor information can obstruct progress in standards working groups and affect developers' perceptions of standards. ### Source excerpt Mel Conway's seminal paper "How Do Committees Invent?" (PDF) is commonly paraphrased as Conway's Law: Organizations which design systems are (broadly) constrained to produce designs which are copies of the communication structures of these organizations. This is deep organisational insight that engineering leaders ignore at their peril, and everyone who delivers code for a living benefits from a (re)read of "The Mythical Man-Month", available at fine retailers everywhere. Conway's Law is generally invoked to describe organisations working to solve well-defined problems, in which everyone is working towards a solution. But what if there are defectors? And what if they can prevent forward progress without paying any price? This problem is rarely analysed for the simple reason that such an organisation would be deranged. But what if that happened regularly? I was reminded of the possibility while chatting with a colleague joining a new (to them) Working Group at the W3C. The most cursed expressions of Conway's Law regularly occur in Standards Development Organisations (SDOs); specifically, when delegates refuse to communicate their true intentions, either through spurious objection or tactical silence. This special case is the fifth column problem. Contents How Does This Happen? Mayfly Half-Lives The Web Platform's Power Structure But Why? Problem Misstatements Closed For Business Survivorship Bias and The Problem of Big, Old Rooms Marketing Gridlock As Thoughtfulness When Is A "Consensus" Not Consensus? Defences Against Fifth Columns Expressed in Conwayist terms, the fifth column problem describes the way organisations mirror the miscommunication patterns of their participants when they fail to deliver designs of any sort. This pathology presents when the goal of the majority is antithetical to a small minority with a veto. Reticence of certain SDO participants to consider important problems is endemic, in part, due to open membership. Unlike corporate environments wh ## Checkpoint #4: Berlinterop DevFeed: [Checkpoint #4: Berlinterop]() Original publisher: [Read original article]() Author: Nixo Rokish Published: 2025-06-19T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Network](), [Testing]() Tags: [blockchain](), [consensus](), [development](), [ethereum](), [github](), [hardening](), [network](), [research-development](), [stress](), [testing](), [upgrade]() ### AI overview Ethereum's Checkpoint #4 reports on Berlinterop, an interop hacking week where core developers and researchers worked on Fusaka implementation, devnet progress, gas-limit increases, and longer-term research directions. The article also describes stress testing and plans to consult the public governance process before finalizing changes. ### Source excerpt Ethereum's weekly All Core Developer calls are a lot to keep up with, so this "Checkpoint" series aims for high-level updates depending on what's happening in core development. See the previous update here. This is a special edition of the series! Kicking off Berlin Blockchain Week, ethereum core... ## 【分布式系统实战】Raft 实现拆解：etcd 的共识算法到底长什么样 DevFeed: [【分布式系统实战】Raft 实现拆解：etcd 的共识算法到底长什么样]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2025-01-24T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Raft](), [Go Language](), [Replication](), [bug]() Tags: [bug](), [consensus](), [distributed](), [distributed-systems](), [etcd](), [go](), [leader-election](), [log-replication](), [pipeline](), [raft](), [replication]() ### AI overview This article examines how etcd's Go Raft library extends the Raft paper with engineering mechanisms and edge-case handling. It discusses PreVote and leader transfer, pipelined replication with Probe, Replicate, and snapshot states, Ready-based I/O separation, and configuration-change safety concerns. ### Source excerpt Raft 论文 18 页，etcd raft 库 ~15000 行 Go。中间的差距不是代码量，是论文没提的工程 edge case：PreVote、流水线复制、ReadIndex、joint consensus。 ## Comparing CockroachDB and PostgreSQL DevFeed: [Comparing CockroachDB and PostgreSQL]() Original publisher: [Read original article]() Author: Cassie McAllister Published: 2025-01-06T00:00:00Z Content type: comparison Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [PostgreSQL](), [Databases](), [cloud-infrastructure](), [Open Source]() Tags: [cloud-infrastructure](), [cockroachdb](), [comparison](), [consensus](), [databases](), [distributed](), [postgresql](), [sharding](), [sql]() ### AI overview This comparison examines architectural differences between PostgreSQL and CockroachDB. It explains PostgreSQL's vertical scaling and manual sharding approach, then describes CockroachDB's distributed SQL architecture, horizontal scaling, distributed consensus, and triplicated data storage. ### Source excerpt Before we begin a comparison blog post about PostgreSQL, we must first acknowledge that it is one of the most reliable and widely used databases in the history of software. The world owes a debt of gratitude to the open source community that has built and supported this important project for the last 35 years. In this post, we unpack some of the architectural differences between PostgreSQL and CockroachDB. We'll point out where the limitations of single server, single instance architecture might pose challenges for modern cloud infrastructure, and how a distributed foundation can be a better solution for your apps and services. ## 4844 Data Challenge: Insights and Winners DevFeed: [4844 Data Challenge: Insights and Winners]() Original publisher: [Read original article]() Author: Rodrigo Vasquez Published: 2024-09-13T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [Scalability](), [Transactions](), [datasets](), [Security]() Tags: [announce](), [consensus](), [dataset](), [ethereum](), [network](), [research-development](), [scalability](), [transactions]() ### AI overview The article announces the winners of a data collection round examining the empirical impacts of Ethereum's EIP-4844 upgrade. The selected projects study consensus security, rollup economics, blob transactions, blob adoption, block propagation, Layer 2 posting patterns, and network stability. ### Source excerpt In March 2024, the Ethereum network underwent a significant upgrade with the implementation of EIP-4844, an essential part of the Dencun hardfork, aimed at bolstering Ethereum's role as a data availability layer. This upgrade introduced "blobs" of data, dramatically enhancing the scalability of Layer 2 solutions by increasing data availability... ## Ethereum Protocol Fellowship: Third Cohort Recap DevFeed: [Ethereum Protocol Fellowship: Third Cohort Recap]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2023-05-10T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Protocol (disambiguation)](), [Development](), [Learning](), [Security](), [Testing]() Tags: [community](), [consensus](), [developers](), [development](), [ethereum](), [protocol](), [recap](), [research](), [research-development](), [security](), [testing]() ### AI overview The Ethereum Protocol Fellowship completed its third four-month cohort in February 2023 and is preparing for a fourth cohort. The article explains how EPF helps developers enter Ethereum core development through independent projects, feedback from core developers, and participation in a community spanning research, clients, testing, consensus, and protocol security. ### Source excerpt TL;DR: The EPF concluded its third cohort and is preparing for the fourth cohort. Applications will be open soon. Sign up here to get notified when they open. The Ethereum Protocol Fellowship recently completed its third successful cohort in February 2023. Its completion marked 4 months of immersive learning,... ## From Zero to Kubernetes Subproject Lead DevFeed: [From Zero to Kubernetes Subproject Lead]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2023-03-29T00:00:00Z Content type: opinion Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Open Source](), [Learning](), [Security]() Tags: [beginner](), [community](), [consensus](), [growth](), [how-to](), [kubernetes](), [learning](), [open-source]() ### AI overview A personal account of becoming a Kubernetes subproject lead through participation in SIG Security. The author describes finding an area of interest, joining community meetings, volunteering for opportunities, asking for help, and continuing to learn while building consensus. ### Source excerpt Getting started in any open-source community can be daunting, especially if it's a big one like Kubernetes. I wrote this post to share my experience and encourage others to join up. All it takes is some curiosity and a willingness to show up! Here's how my journey unfolded at a high level: What am I interested in? Is there a SIG (Special Interest Group) or a WG (Working Group) that is dedicated to that topic, or something similar? Sign up for their mailing list and start hopping on meetings. When (never if!) there are opportunities to help out and it aligns with your skills and desired growth areas, raise your hand. Ask for lots of help and don't be shy about not knowing everything (or anything!) Keep plugging along, even if progress isn't as fast as you would like it to be. Starting up First things first. What are you interested in learning more about? There are so many wonderful SIGs and working groups in the Kubernetes community: there's something for everyone. And continuing to show up and participate will be so much easier if you think what you are doing is interesting. Likewise, continued participation is what keeps the community thriving, so that interest will drive you to have more of an impact. Also: it's ok to show up knowing nothing! I remember showing up knowing very little about Kubernetes or how the community itself worked. And while I know more about how the community functions today, I am still learning all the time about it and the project. Fortunately, the community is full of friendly people who want to help you learn. Learning as you go is expected and celebrated. When you raise your hand to do something, even if you know nothing, people will cheer and help you along the way. This method was my exact story. It was my first or second meeting with SIG Security , and Pushkar Joglekar mentioned that he needed a lead for a subproject he was creating after having done a security assessment of Cluster API . Everyone was so friendly in the meeting that I ## Mainnet Shapella Announcement DevFeed: [Mainnet Shapella Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2023-03-28T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [releases](), [Network](), [API]() Tags: [announcement](), [api](), [beacon](), [consensus](), [ethereum](), [protocol-announcements](), [python](), [release](), [specifications](), [upgrade]() ### AI overview Ethereum's Shapella network upgrade was scheduled for mainnet activation on April 12, 2023. The upgrade combined Shanghai execution-layer changes, Capella consensus-layer changes, and Engine API changes, enabling full and partial validator withdrawals. ### Source excerpt Withdrawals are coming! The Shapella network upgrade will activate on the Ethereum network at epoch 194048, scheduled for 22:27:35 UTC on Apr. 12, 2023 Stakers & node operators should read this post as well as the Withdrawals FAQ From now until April 5th, the Ethereum Bug Bounty rewards have been... ## EF-Supported Teams: Research & Development Roundup DevFeed: [EF-Supported Teams: Research & Development Roundup]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2022-12-29T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Protocol (disambiguation)](), [DevOps](), [Security](), [Testing]() Tags: [consensus](), [core](), [development](), [devops](), [ethereum](), [organizational](), [research](), [research-development](), [security](), [testing](), [upgrades]() ### AI overview The Ethereum Foundation's 2022 roundup reviews accomplishments by EF-supported teams during and after The Merge, including the transition of Ethereum mainnet consensus to Proof-of-Stake. It also outlines ongoing work in consensus research, MEV, beacon-chain security, withdrawals, EIP-4844 proto-danksharding, client interoperability, and related research. ### Source excerpt Friends, As the year of the Merge ends, we wanted to share updates from many of the Ethereum gardeners and EF-supported teams that achieved long sought accomplishments, both big and small, alongside the rest of the ecosystem in 2022. We all have a lot to be thankful for, from... [Next page]()