# proof of work Published articles for proof of work. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Software Development Is Changing from Programming to Air Traffic Control DevFeed: [How Software Development Is Changing from Programming to Air Traffic Control]() Original publisher: [Read original article]() Author: Kent Beck Published: 2026-07-01T14:25:26Z Content type: opinion Language: en Sources: [Software Design: Tidy First?]() Topics: [systems](), [Software](), [proof of work](), [Programming]() Tags: [audio](), [compute](), [programming](), [proof-of-work](), [software](), [sponsored](), [systems]() ### AI overview Keith Adams and Kent discuss how a changing software-building playbook could affect the economics of technology and the work of programming, including compute, Jevons paradox, and software as "proof of work." ### Source excerpt Keith Adams has spent his career at the systems layer, with nine years at VMware, the founding of Facebook's HHVM team, and a run as chief architect at Slack. ## What Entry-Level Software Engineering Looks Like in the AI Age DevFeed: [What Entry-Level Software Engineering Looks Like in the AI Age]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-05-28T00:00:00Z Content type: article Language: en Sources: [Swizec Teller]() Topics: [Software Engineering](), [Artificial Intelligence](), [proof of work](), [systems]() Tags: [ai](), [engineering](), [interviews](), [proof-of-work](), [software-engineering](), [systems](), [talks]() ### AI overview Clara Shih, Chip Huyen, and Swizec Teller discuss how AI-assisted coding is affecting entry-level software engineering, including interviews, proof-of-work projects, systems thinking, and side projects. ### Source excerpt Clara Shih talks with Chip Huyen and Swizec Teller about what entry-level software engineering looks like in the AI age. ## Enhanced Authorization with Square DevFeed: [Enhanced Authorization with Square]() Original publisher: [Read original article]() Author: Conrado Brenna Published: 2024-12-16T08:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Authorization](), [Security](), [Transactions](), [Protocol (disambiguation)](), [User Experience]() Tags: [3](), [apis](), [authorization](), [features](), [fraud](), [information](), [networks](), [payment](), [pow](), [proof-of-work](), [protocol](), [real-time](), [security](), [tools](), [user-experience](), [validation](), [with]() ### AI overview Square describes three approaches to payment authorization and fraud prevention: 3DS Data Only, Capital One Direct Data Share, and anti-carding protections. The article reports improvements of 220 basis points in decline rates for 3DS Data Only and 50 basis points for Direct Data Share. ### Source excerpt Enhancing Payment Success with Square Advanced Authorization Tools ## 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. ## Mainnet Merge Announcement DevFeed: [Mainnet Merge Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-08-24T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [upgrade](), [proof of work](), [Network](), [hash](), [JSON](), [Remote Procedure Call (RPC)]() Tags: [consensus](), [ethereum](), [execution](), [hash](), [json](), [network](), [node](), [proof-of-work](), [protocol-announcements](), [rpc](), [upgrade]() ### AI overview Ethereum's mainnet transition from proof-of-work to proof-of-stake, known as The Merge, was scheduled in two phases: the Bellatrix upgrade on the Beacon Chain followed by the Paris transition when the execution layer reached the specified Terminal Total Difficulty. ### Source excerpt Ethereum is moving to proof-of-stake! The transition, known as The Merge, must first be activated on the Beacon Chain with the Bellatrix upgrade. After this, the proof-of-work chain will migrate to proof-of-stake upon hitting a specific Total Difficulty value. The Bellatrix upgrade is scheduled for epoch 144896 on the Beacon... ## Goerli/Prater Merge Announcement DevFeed: [Goerli/Prater Merge Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-07-27T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [JSON]() Tags: [announcement](), [ethereum](), [json](), [proof-of-work](), [protocol-announcements](), [rpc](), [update](), [upgrades]() ### AI overview The article announces that Goerli will merge with Prater for Ethereum's final testnet proof-of-stake transition. It describes the Bellatrix and Paris phases, their expected activation conditions, and the continued availability of Goerli validators for individual stakers. ### Source excerpt For the last testnet proof-of-stake transition, Goerli will merge with Prater. The combined Goerli/Prater network will retain the Goerli name post-merge. Bellatrix, the Prater upgrade readying it for The Merge will happen at epoch 112260, expected at 12:24PM UTC on August 4, 2022. After Bellatrix is activated, the Goerli/Prater merge... ## Sepolia Merge Announcement DevFeed: [Sepolia Merge Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-06-30T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [releases]() Tags: [beacon](), [consensus](), [ethereum](), [network](), [proof-of-authority](), [proof-of-work](), [protocol-announcements](), [releases]() ### AI overview Ethereum announces the next phase of the Sepolia testnet's transition from proof-of-work to proof-of-stake as part of The Merge. The transition is triggered by a Terminal Total Difficulty threshold, following the Bellatrix upgrade on the Sepolia Beacon Chain. ### Source excerpt Note: on July 5, 2022, the recommended releases for go-ethereum and Erigon were modified. See "Client Releases" for details. Sepolia will be the second of three public testnets to run through The Merge. The network will transition to proof-of-stake when the total difficulty on the proof-of-work chain exceeds 17,000,000,000,000,000, which... ## Ropsten, Rinkeby & Kiln Deprecation Announcement DevFeed: [Ropsten, Rinkeby & Kiln Deprecation Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-06-21T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [migration](), [Protocol (disambiguation)]() Tags: [announcement](), [deprecated](), [developers](), [ethereum](), [migration](), [proof-of-work](), [protocol-announcements](), [upgrade]() ### AI overview Ethereum is deprecating the Kiln, Ropsten, and Rinkeby testnets as it focuses long-term maintenance on Goerli and Sepolia. The article provides their planned shutdown timelines and encourages users and developers to migrate to Goerli or Sepolia. ### Source excerpt Reminder: the Gray Glacier upgrade is scheduled for block 15,050,000, expected June 29, 2022 The Kiln Merge testnet, launched earlier this year, will be shut down shortly after the Ethereum mainnet's transition to proof-of-stake. Ropsten, Ethereum's longest-lived proof-of-work testnet, has transitionned to proof-of-stake. It will be shut down in Q4... ## Ropsten TTD Announcement DevFeed: [Ropsten TTD Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-06-03T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Terminal](), [configuration](), [Network](), [Command-line interface]() Tags: [announcement](), [cli](), [config](), [configuration](), [consensus](), [network](), [node](), [override](), [proof-of-work](), [protocol-announcements](), [terminal]() ### AI overview The article announces a Terminal Total Difficulty of 50000000000000000 for the Ropsten Merge. It instructs stakers and node operators to override the TTD in both execution and consensus layer clients before June 7, 2022, and estimates the transition for June 8-9, 2022 if hash rates remain stable. ### Source excerpt A Terminal Total Difficulty (TTD) of 50000000000000000 has been selected for the Ropsten Merge. Stakers and node operators must manually override the TTD in both their execution and consensus layer clients before June 7, 2022. Proof-of-Work testnets can have volatile hash rates and the exact timing of The Merge on... ## Blockchain In Go: Part III: Redundant Storage And Consensus DevFeed: [Blockchain In Go: Part III: Redundant Storage And Consensus]() Original publisher: [Read original article]() Published: 2022-04-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Databases](), [Transactions]() Tags: [availability](), [blockchain](), [blockchain-consensus-protocol](), [build-blockchain-from-scratch](), [consensus](), [database](), [digital-wallet](), [ethereum](), [go](), [go-blockchain](), [golang](), [golang-blockchain](), [proof-of-work](), [storage](), [transactions](), [verification]() ### AI overview The third article in a series explains how the Ardan blockchain project handles consensus between computers and uses that process for redundant storage of the blockchain database. It introduces proof of work and proof of stake, discusses safety versus liveness, and notes the consensus approaches used by Bitcoin and Ethereum. ### Source excerpt Introduction In the first two posts, I explained there were four aspects of a blockchain that this series would explore with a backing implementation provided by the Ardan blockchain project. Digital accounts with electronic signatures and verification Transaction distribution and synchronization between computers Redundant storage and consensus by different computers Detection of any fraud to past transactions The first post focused on how the Ardan blockchain provides support for digital accounts, signatures, and verification. The second post focused on transaction distribution and synchronization between different computers. In this third post, I will focus on how the Ardan blockchain handles consensus between different computers which results in the redundant storage of the blockchain database. ## How The Merge Impacts Ethereum's Application Layer DevFeed: [How The Merge Impacts Ethereum's Application Layer]() Original publisher: [Read original article]() Author: Tim Beiko Published: 2021-11-29T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [Tooling](), [Transactions]() Tags: [architecture](), [beacon](), [consensus](), [developers](), [ethereum](), [features](), [merge](), [proof-of-work](), [research-development](), [tooling](), [transactions]() ### AI overview This article explains how Ethereum's transition from proof of work to proof of stake through The Merge affects end users, smart contracts, decentralized applications, and application developers. It describes the Beacon Chain as the new consensus layer, ExecutionPayloads as the post-merge equivalent of blocks, and the minor changes to block fields and transaction infrastructure. ### Source excerpt Ethereum's transition to proof of stake -- The Merge -- is near: devnets are being stood up, specifications are being finalized and community outreach has begun in earnest. The Merge is designed to have minimal impact on how Ethereum operates for end users, smart contracts and dapps. That said, there... ## Ethereum Altair prereleases, beacon chain security RfP, and merge progress DevFeed: [Ethereum Altair prereleases, beacon chain security RfP, and merge progress]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2021-03-24T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [releases](), [Ethereum](), [Testing](), [Security]() Tags: [ethereum](), [pre-release](), [proof-of-work](), [release](), [research-development](), [security](), [testing]() ### AI overview The article reports on two feature-complete Altair prereleases for Ethereum's beacon chain, a security and testing request for proposals, and progress toward the merge of Ethereum's proof-of-work application layer with its proof-of-stake consensus layer. ### Source excerpt tl;dr Altair prereleases: Stargazer and Half of 'em just look like dots Security RfP Merge progress... ## 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!... ## Turning Down a Blockchain Job Offer DevFeed: [Turning Down a Blockchain Job Offer]() Original publisher: [Read original article]() Published: 2018-01-21T23:00:00Z Content type: opinion Language: en Sources: [Dennis Felsing]() Topics: [Blockchain](), [proof of work](), [Programming](), [Hardware]() Tags: [blockchain](), [consensus](), [energy](), [hardware](), [implementation](), [job](), [programming](), [proof-of-work](), [work]() ### AI overview The author explains why they declined a generous, remote job developing a blockchain implementation. Although they found Bitcoin's electronic-cash concept and the programming opportunity appealing, they objected to proof-of-work's hardware and energy costs and to hype and questionable practices surrounding cryptocurrencies and token offerings. ### Source excerpt I have recently received a job offer to work on a blockchain implementation. While the offer was very generous, I had to turn it down. In this post I want to collect the thoughts that went into my decision process leading to this conclusion. Introduction I have not touched blockchain technology much before, other than reading the original Bitcoin paper shortly after it was released and accepting Bitcoin donations for DDNet. But I have always used those donations pretty much immediately, and thus I have no investment in cryptocurrencies either way and am thus impartial to their fate. The Good I consider the Bitcoin idea to be quite interesting as an electronic cash system that doesn't require any trusted intermediary. This is a small and simple idea that combines old cryptographic ideas into something new. The job I got offered had a significantly higher salary attached than my current job. The new job would have been remote, thus enabling me to spend more time with my girlfriend and live in any location I wish. I would have been able to work in a nice programming language, developing a blockchain implementation from the ground up with a small group of colleagues. The Bad Proof of work in the form of mining is currently the most common form of trustless consensus in blockchain systems. It requires immense amounts of computational hardware in the form of ASICs and GPUs as well as energy to supply them. The only function of this is to prevent any one actor to take over more than 50% of the mining market and thus controlling the currency. This is a large price to pay for replacing trust. Looking at it the other way: Trust can be seen as a shortcut that humanity has used for a long time in order not to require expensive proof of work. For most applications this still works fine. Companies are doing initial coin offerings (ICOs), giving out their own cryptotoken to public investors, circumventing a proper IPO process. While companies often claim that their tokens will hav ## The Render Token DevFeed: [The Render Token]() Original publisher: [Read original article]() Author: Brendan Eich Published: 2017-09-25T14:57:39Z Content type: opinion Language: en Sources: [Brendan Eich]() Topics: [render](), [GPU](), [Blockchain](), [watermarking](), [Security](), [Testing](), [Ethereum](), [proof of work]() Tags: [blockchain](), [ethereum](), [gpu](), [proof-of-work](), [render](), [security](), [testing](), [uncategorized](), [watermarking]() ### AI overview Brendan Eich discusses OTOY's RNDR token as a decentralized GPU-cloud rendering system for AR/VR, games, and movies. He describes token-based access to computing resources, blockchain-attested work verification, renderer reputation, hardware-assisted confidentiality, and watermarking for protecting digital models and art. ### Source excerpt I wrote about OTOY over four years ago, in "Today I Saw The Future". Since then, I have been inspired by the commitment of the founders Jules Urbach and Alissa Grainger to the vision that Jules enunciates: "... to render and remix simulated reality as effortlessly as the web did for text and digital media. ... Continue reading "The Render Token" ## Uncle Rate and Transaction Fee Analysis DevFeed: [Uncle Rate and Transaction Fee Analysis]() Original publisher: [Read original article]() Author: Vitalik Buterin Published: 2016-10-31T03:52:04Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Blockchain](), [Ethereum](), [data](), [Transactions](), [Network](), [Bitcoin]() Tags: [analysis](), [bitcoin](), [blockchain](), [data](), [ethereum](), [network](), [proof-of-work](), [research-development](), [transactions]() ### AI overview This article analyzes how Ethereum's uncle rate relates to transaction gas usage and block propagation. It explains the role of stale blocks and uncles, compares propagation data with Bitcoin, and describes using blockchain data to study the relationship. ### Source excerpt One of the important indicators of how much load the Ethereum blockchain can safely handle is how the uncle rate responds to the gas usage of a transaction. In all blockchains of the Satoshian proof-of-work variety, any block that is published has the risk of howbecoming a "stale", ie. not... ## C++ DEV Update - July edition DevFeed: [C++ DEV Update - July edition]() Original publisher: [Read original article]() Author: Christian Reitwiessner Published: 2016-07-08T17:57:33Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [C++](), [Development](), [Blockchain](), [Benchmark](), [Remote Procedure Call (RPC)](), [JIT](), [Ubuntu]() Tags: [apache](), [benchmark](), [benchmarks](), [blockchain](), [c-plus-plus](), [dev](), [go](), [ipc](), [jit](), [native](), [proof-of-work](), [research-development](), [rpc](), [ubuntu](), [update]() ### AI overview An overview of work on the C++ Ethereum client, including proposed Apache 2.0 relicensing, new RPC endpoints for smart-contract testing, improvements to the EVM interpreter, and benchmark results comparing interpreter and JIT performance. ### Source excerpt Since the last C++ DEV Update, a lot of things happened in the engine room which were not really visible to the outside. This post wants to give an overview about what we are currently working on. Apart from the features side, Bob has been working on a proposed... ## On Settlement Finality DevFeed: [On Settlement Finality]() Original publisher: [Read original article]() Author: Vitalik Buterin Published: 2016-05-09T08:07:25Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Blockchain](), [Computer science](), [Mathematics]() Tags: [architectures](), [blockchain](), [computer-science](), [financial](), [proof-of-work](), [research-development]() ### AI overview The article examines settlement finality in public and permissioned blockchains, arguing that finality can be absolute, probabilistic, economically bounded, or absent depending on system design. It introduces a cryptoeconomic analysis involving mathematics, computer science, and game theory. ### Source excerpt Special thanks to Tim Swanson for reviewing, and for further discussions on the arguments in his original paper on settlement finality. Recently one of the major disputes in ongoing debate between public blockchain and permissioned blockchain proponents is the issue of settlement finality. One of the simple properties that... ## From Smart Contracts to Courts with not so Smart Judges DevFeed: [From Smart Contracts to Courts with not so Smart Judges]() Original publisher: [Read original article]() Author: Christian Reitwiessner Published: 2016-02-17T15:42:29Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [systems](), [Protocol (disambiguation)]() Tags: [article](), [ethereum](), [platform](), [proof-of-work](), [research-development](), [smart-contract](), [transactions]() ### AI overview This article presents Ethereum smart contracts as courts with computationally restricted judges assisted by outside actors acting as lawyers. It explains how contracts can obtain and verify external information, and how this model can support complex computations despite gas limits. ### Source excerpt Ethereum is often described as a platform for self-enforcing smart contracts. While this is certainly true, this article argues that, especially when more complex systems are involved, it is rather a court with smart lawyers and a judge that is not so smart, or more formally, a judge with restricted... ## Understanding Serenity, Part 2: Casper DevFeed: [Understanding Serenity, Part 2: Casper]() Original publisher: [Read original article]() Author: Vitalik Buterin Published: 2015-12-28T01:54:30Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Algorithm](), [Protocol (disambiguation)]() Tags: [algorithm](), [consensus](), [ethereum](), [proof-of-work](), [protocol](), [research-development]() ### AI overview This article explains Casper, Ethereum's proof-of-stake algorithm for the Serenity milestone. It presents consensus-by-bet, in which validators receive rewards or penalties based on which blocks they support, and describes how incentives are intended to drive convergence toward a shared state. ### Source excerpt Special thanks to Vlad Zamfir for introducing the idea of by-block consensus and convincing me of its merits, alongside many of the other core ideas of Casper, and to Vlad Zamfir and Greg Meredith for their continued work on the protocol In the last post in this series, we...