# consensus algorithm Published articles for consensus algorithm. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Understanding and scaling Raft DevFeed: [Understanding and scaling Raft]() Original publisher: [Read original article]() Published: 2025-04-04T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Raft](), [consensus algorithm](), [distributed-systems](), [scaling](), [CockroachDB](), [Databases]() Tags: [cockroachdb](), [consensus-algorithm](), [databases](), [distributed-systems](), [raft](), [replication](), [scaling]() ### AI overview This tutorial explains the Raft consensus algorithm, including leader election, log replication, safety guarantees, and the network cost of consensus. It also introduces the Multi-Raft pattern for scaling distributed databases by splitting data into ranges with independent Raft groups. ### Source excerpt . [Understanding and Scaling Raft](understanding-and-scaling-raft-cover... ## Ultimate Go: Advanced Engineering Episode 7 DevFeed: [Ultimate Go: Advanced Engineering Episode 7]() Original publisher: [Read original article]() Published: 2022-12-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Databases](), [Data structures](), [Algorithms]() Tags: [2](), [audits](), [batch](), [batch-insert](), [bulk-upload](), [caching](), [consensus](), [consensus-algorithm](), [data-structures](), [databases](), [distributed](), [efficiency](), [engineering](), [go-blockchain](), [memory-pool](), [poa](), [pos](), [pow](), [proof-of-authority]() ### AI overview This video walkthrough explains how a proof-of-authority consensus mechanism affects a dependency manager's database throughput. It introduces a synchronized memory pool for queued records, reduces duplicate insertion work across nodes, and explains how batches of records become blockchain blocks and can be audited. ### Source excerpt Introduction In episode 6, Bill gives an overview of what consensus algorithms are and how these algorithms ensure distributed databases are in sync. Moving forward Bill will adopt the proof of authority (PoA) algorithm as a means to determine which node has the ability to write the next record. To jog your memory, PoA is a consensus mechanism where identity is used as a stake. By implementing this algorithm, Bill will add transparency to his dependency manager as he is no longer the only user with the ability to add new records. The dependency manager now meets the teams' requirements for transparency, however, it will have low throughput since only one record can be shared and inserted at a time. ## Ultimate Go Episode 6: Blockchain Consensus Algorithms DevFeed: [Ultimate Go Episode 6: Blockchain Consensus Algorithms]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Algorithms](), [Security](), [data]() Tags: [algorithms](), [blockchain](), [consensus](), [consensus-algorithm](), [distributed](), [go-blockchain](), [golang-blockchain](), [poa](), [pos](), [pow](), [proof-of-authority](), [proof-of-work](), [security]() ### AI overview This video explains why proof of work can be inefficient as a blockchain grows, focusing on duplicated computation and energy consumption. It introduces proof of stake and proof of authority as alternative consensus algorithms and discusses their role in maintaining valid data in a distributed database. ### Source excerpt Introduction In the last video, Bill left off talking about proof of work (PoW) algorithms. In a distributed and decentralized environment, PoW used to be the gold standard for a node to participate equitably in a Blockchain. However, with PoW as the number of nodes on the Blockchain increases, the amount of energy waste increases. This is because each node is performing the same computationally heavy calculation and only one node's energy usage is leveraged to write the next block. ## Ultimate Go: Advanced Engineering Episode 5 DevFeed: [Ultimate Go: Advanced Engineering Episode 5]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Databases](), [Replication]() Tags: [atomic](), [consensus](), [consensus-algorithm](), [cryptographically-auditable](), [database](), [distributed](), [engineering](), [go-blockchain](), [golang-blockchain](), [poa](), [pos](), [pow](), [proof-of-authority](), [proof-of-work]() ### AI overview This video explains how to use blockchain concepts to design a distributed, auditable, synchronized, and scalable database for a dependency manager. It focuses on atomic writes, consensus, and a proof-of-work algorithm, while also discussing the inefficiency of proof of work and the emergence of proof of stake and proof of authority. ### Source excerpt Introduction In case you missed episode 4, Bill attempted to integrate current database sharing solutions to solve the "database ownership" problem his dependency manager faces. He tried providing copies of the database, implementing a load balancer and replication. While performing these experiments, Bill identified the qualities his dependency manager's database needs to have for users to trust it. He closed episode 4 by stating that his dependency manager needs a database that is distributed, cryptographically auditable, synchronized and scalable. By implementing this Bill hoped to provide greater transparency for his dependency manager. ## Ethereum consensus-layer series rebranded as Finalized; node upgrades required for Berlin DevFeed: [Ethereum consensus-layer series rebranded as Finalized; node upgrades required for Berlin]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2021-03-11T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Protocol (disambiguation)](), [Software]() Tags: [consensus-algorithm](), [ethereum](), [fork](), [pow](), [proof-of-work](), [protocol](), [research-development](), [upgrade](), [upgrades]() ### AI overview The article announces that the blog series formerly associated with "eth2" will be rebranded as "Finalized: the Ethereum consensus-layer." It also explains that the Berlin mainnet upgrade requires Ethereum PoW node operators and beacon-chain stakers to update their software by the stated deadlines. ### Source excerpt tl;dr Finalized: rebranding the blog Upgrade your nodes!... ## eth2 quick update no. 3 DevFeed: [eth2 quick update no. 3]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2019-11-08T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Protocol (disambiguation)](), [Formal verification]() Tags: [analysis](), [attacks](), [audit](), [consensus](), [consensus-algorithm](), [fork](), [formal-verification](), [implementation](), [research-development](), [update](), [verification]() ### AI overview The third eth2 quick update describes strengthened Phase 0 fork-choice defenses following analysis of decoy-flip-flop and bouncing attacks. It also announces challenges.ethereum.org and a Herumi grant for a fast BLS implementation. ### Source excerpt Welcome to the third installment of eth2 quick update. tldr; Harden fork choice defences in response to audits Introducing challenges.ethereum.org Herumi grant for a super-fast BLS implementation...