FlareStart
HomeNewsHow ToSources
FlareStart

Where developers start their day. All the tech news & tutorials that matter, in one place.

Quick Links

  • Home
  • News
  • Tutorials
  • Sources
  • Privacy Policy

Connect

© 2026 FlareStart. All rights reserved.

Back to articles
How We Made 'One CPU, One Vote' Actually Work (After 17 Years of Broken Promises)
How-ToSystems

How We Made 'One CPU, One Vote' Actually Work (After 17 Years of Broken Promises)

via Dev.toAutoJanitor1mo ago

Satoshi's Most Violated Design Principle "Proof-of-work is essentially one-CPU-one-vote." -- Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System (2008), Section 4 This is the most broken promise in cryptocurrency history. The economics of SHA-256 hashing destroyed it within 18 months: Year Dominant Hardware Advantage vs CPU 2009 CPU (as designed) 1x 2010 GPU mining begins ~100x 2013 First ASIC miners ~10,000x 2024 Bitmain S21 Pro ~1,000,000x A single modern ASIC casts the equivalent of one million CPU votes . That's not "one CPU, one vote." That's plutocracy measured in silicon. In our introduction to Proof of Antiquity , we explained the philosophy: vintage hardware matters, digital preservation deserves economic incentive, and consensus should be fair. This article is the deep technical dive into the mechanism that makes it work -- RIP-200, the consensus protocol that actually enforces 1 CPU = 1 Vote. Every ASIC-Resistance Attempt Failed Before diving into our approach,

Continue reading on Dev.to

Opens in a new tab

Read Full Article
22 views

Related Articles

How-To

Learn Something Old Every Day, Part XVIII: How Does FPU Detection Work?

Lobsters • 2d ago

“Learn to Code” Is Dead… Learn to Think Instead
How-To

“Learn to Code” Is Dead… Learn to Think Instead

Medium Programming • 3d ago

How-To

How One File Makes Claude Code Actually Follow Your Instructions

Medium Programming • 3d ago

LeetCode Solution: 121. Best Time to Buy and Sell Stock
How-To

LeetCode Solution: 121. Best Time to Buy and Sell Stock

Dev.to Tutorial • 3d ago

The Feature Took 2 Hours to Build — and 2 Weeks to Fix
How-To

The Feature Took 2 Hours to Build — and 2 Weeks to Fix

Medium Programming • 3d ago

Discover More Articles