为何2018年Proof of Work登录未成为全球标准，传统验证码仍广泛使用？

Great question! I’ve dug into proof-of-work (PoW) login systems before, and while they’re a clever take on bot mitigation, there are several practical reasons they hadn’t replaced traditional captchas and reCAPTCHA as the go-to solution by 2018—even as old-school verification methods remained ubiquitous. Let’s break it down:

1. User Experience (UX) Is a Major Dealbreaker #

Unlike reCAPTCHA’s often one-click “I’m not a robot” check, PoW requires the user’s device to perform actual computational work. For anyone on a low-end phone, aging laptop, or slow internet connection, this translates to noticeable wait times—something product teams avoid like the plague. Even small delays can tank login/signup conversion rates, and users have grown accustomed to instant interactions. Asking them to “wait while we verify you” via a background calculation feels clunky compared to a quick click or simple image match.

2. Implementation Complexity Outweighs the Benefits #

Building a robust PoW system isn’t a copy-paste job. You need to:

• Dynamically adjust puzzle difficulty to match device performance (so a flagship phone doesn’t breeze through it while a budget device gets stuck)
• Ensure the algorithm is hard enough to stop bots but easy enough for human users
• Handle edge cases like devices that can’t compute the work efficiently

Compare that to reCAPTCHA: you drop a few lines of code into your form, and Google’s infrastructure handles the rest. Most developers don’t have the time or resources to build and maintain a custom PoW system when a battle-tested, free solution is available.

3. Bots Can Easily Outcompute PoW #

PoW relies on the assumption that bots won’t waste resources solving computational puzzles—but modern botnets have access to massive cloud-based GPU and CPU power. A bot can crunch through PoW challenges far faster than a regular user’s device, rendering the mitigation ineffective. Meanwhile, reCAPTCHA (especially v2 and later) uses behavioral analysis, mouse movement tracking, and machine learning to detect bot patterns that go beyond raw computation—something a basic PoW system can’t replicate.

4. Established Ecosystems Favor the Status Quo #

By 2018, traditional captchas and reCAPTCHA were deeply integrated into every corner of web development:

• CMS platforms like WordPress had one-click plugins for them
• Frameworks like React and Vue had pre-built components
• Developers knew how to implement, debug, and optimize them

PoW systems, on the other hand, were niche. There weren’t many standardized libraries, best practices, or community support to guide developers. Adopting PoW meant stepping outside the comfort zone of tools everyone already knew and trusted.

5. Privacy Benefits Aren’t a Universal Priority #

PoW does have a key advantage: it doesn’t rely on third-party services (like Google’s reCAPTCHA) that track user behavior. But for most mainstream apps and websites, this benefit isn’t enough to justify the UX and implementation costs. Only privacy-focused services (like encrypted messaging apps or decentralized platforms) were likely to prioritize PoW over more convenient, widely accepted solutions.

内容的提问来源于stack exchange，提问作者Viktor Joras