O que é Proof of Work (PoW)
Proof of Work é um mecanismo de consenso que exige que os participantes da rede (mineiros) resolvam quebra-cabeças computacionalmente intensivos para validar transações e adicionar novos blocos à blockchain.
Proof of Work (PoW) foi introduzido pela primeira vez no whitepaper do Bitcoin de 2008 por Satoshi Nakamoto, embora o conceito tenha se originado do Hashcash (1997). Ele resolve o problema do gasto duplo sem exigir um terceiro confiável.
Como o PoW Funciona:
1. Os mineiros coletam transações pendentes em um bloco
2. Eles repetidamente fazem o hash do cabeçalho do bloco com diferentes valores de nonce
3. O objetivo: encontrar um hash abaixo da dificuldade alvo (começa com zeros suficientes)
4. O primeiro mineiro a encontrar um hash válido transmite o bloco
5. Outros nós verificam e aceitam o bloco
6. O mineiro vencedor recebe moedas recém-criadas + taxas de transação
Modelo de Segurança:
- Para atacar a rede, você precisaria de >50% do poder total de mineração (ataque de 51%)
- Quanto mais mineiros participam, mais segura é a rede
- Os incentivos econômicos alinham os mineiros com um comportamento honesto
Ajuste de Dificuldade:
O Bitcoin ajusta a dificuldade a cada 2016 blocos (~2 semanas) para manter tempos de bloco de ~10 minutos, independentemente do poder total de mineração.
Críticas:
- Alto consumo de energia (~150 TWh/ano para Bitcoin)
- Centralização do poder de mineração em regiões com eletricidade barata
- Corrida armamentista de hardware (domínio ASIC)
Apesar das críticas, o PoW continua sendo o mecanismo de consenso mais testado e seguro.
graph LR
Center["O que é Proof of Work (PoW)"]:::main
Pre_logic["logic"]:::pre --> Center
click Pre_logic "/terms/logic"
Rel_consensus_mechanism["consensus-mechanism"]:::related -.-> Center
click Rel_consensus_mechanism "/terms/consensus-mechanism"
Rel_proof_verification["proof-verification"]:::related -.-> Center
click Rel_proof_verification "/terms/proof-verification"
Rel_proof_of_stake["proof-of-stake"]:::related -.-> Center
click Rel_proof_of_stake "/terms/proof-of-stake"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧠 Teste de conhecimento
🧒 Explique como se eu tivesse 5 anos
It's like a giant, difficult Sudoku puzzle that miners race to solve. The first one to solve it gets to add the next page of transactions to the shared digital ledger and gets a reward, but everyone else can easily check their answer.
🤓 Expert Deep Dive
The security of Proof-of-Work is rooted in the computational difficulty and the probabilistic nature of block discovery. The [hash function](/pt/terms/hash-function) used (typically SHA-256 for Bitcoin) provides pre-image resistance, second pre-image resistance, and collision resistance, ensuring that finding a valid nonce is computationally infeasible without performing the hashing work. The difficulty target is dynamically adjusted (e.g., every 2016 blocks in Bitcoin) to maintain a consistent block generation time, regardless of fluctuations in the network's total hash rate.
From a game-theoretic perspective, the Nash equilibrium incentivizes miners to act honestly. The cost of acquiring and operating the necessary hashing hardware to mount a 51% attack is substantial. The expected reward for honest mining (block reward + fees) is generally greater than the expected cost of mining, assuming a rational actor. However, the concentration of mining power in large pools presents a centralization vector.
Potential vulnerabilities include selfish mining strategies, where miners strategically withhold discovered blocks to gain an advantage, and the aforementioned 51% attack. The energy consumption is a significant environmental and economic externality. Alternative PoW variants exist, such as Proof-of-Capacity or Proof-of-Burn, which aim to reduce energy usage while maintaining security properties, though they often introduce different trade-offs regarding hardware requirements or attack vectors.