Proof of stake vs proof of work a simple guide
Proof of stake vs proof of work a simple guide
Proof of stake vs proof of work a simple guide compares two ways a public chain decides which block comes next. Ethereum’s documentation describes its proof-of-stake design. Satoshi Nakamoto’s Bitcoin paper describes proof of work. Figures, dates, and penalty math stay on those two documents. This article is not investment advice.
The Ethereum proof-of-stake page and the Bitcoin paper are the only sources used below. Nothing here is a reason to buy, sell, or stake.
What proof of stake vs proof of work a simple guide is comparing
On the Ethereum page, proof of stake means a validator puts capital, in ETH, into a contract on Ethereum. The page says that capital can be destroyed if the validator acts dishonestly. The validator checks that new blocks are valid and sometimes creates a block. The page’s examples of dishonest action are proposing more than one block when the validator should send one, and sending conflicting attestations. The deposit size is printed on that page.
The same page says a validator runs an execution client, a consensus client, and a validator client. After the deposit, the validator joins a queue that limits how fast new validators start. Once active, the validator receives blocks, re-executes the transactions to check the proposed state, checks the block signature, and sends a vote the page calls an attestation.
Proof of work, in the Bitcoin paper, is a different job. Nodes collect transactions into a block and expend computation searching for a result that meets a difficulty target. The paper treats the chain with the most of that work as the chain honest nodes extend. Changing a block means redoing that work and the work of the blocks after it. This article does not turn that design into steps for attacking a chain.
How a block gets accepted
The Ethereum page describes a transaction from signature to attestation. A user signs with a private key, usually through a wallet, and offers a tip so a validator will include the transaction. The page says the tip goes to the validator and the base fee is burned. It does not set a price for this article to quote.
An execution client checks that the sender has enough ETH and that the signature matches. If the transaction is valid, the client keeps it with other pending transactions and tells other nodes. The page also notes that some users send a transaction to a block builder instead of broadcasting it. That is a description of the network, not a recommendation to do so.
One validator is the block proposer for the current turn. The page says the choice is pseudo-random. That node builds a block, has the execution client run the transactions, and passes the result to the consensus client with the reward, penalty, and attestation data the page lists. Other nodes re-execute the transactions. Validators that agree send an attestation. Finality, on that page, is a later step between checkpoints. The vote share used for that step is printed on the page.
Under proof of work, the Bitcoin paper does not use a fixed turn. Miners search until someone finds a qualifying result. Other nodes check the result and the transactions, then start work on the next block. The paper’s rule is to extend the chain that represents the most work. Two honest miners can find blocks close together. The next block decides which branch continues, because nodes extend the branch that then has more work.
What the pages say about misbehavior
The Ethereum page says a validator who does not take part misses rewards, and a validator who proposes conflicting blocks or conflicting attestations can lose stake. It names a correlation penalty, an inactivity leak, and a fork-choice rule, LMD-GHOST, that follows the fork with the greatest weight of attestations. The percentages and the timelines are on that page, next to those names.
The page also says a majority of stake could try to favor one fork, and that the design includes ways for honest validators to keep building on another fork. It names other attacks and points at the rules that limit them. Those names are labels for the page’s own section. Proof of stake vs proof of work a simple guide does not include commands, client flags, or hardware.
The Bitcoin paper’s security section says an attacker has to redo the proof of work and outpace the honest chain. Read that section in the paper. This article does not reprint it and does not suggest a pool, a machine, or a fee.
The two jobs, side by side
Ethereum’s page says the network moved from proof of work to proof of stake. It lists energy use, hardware, the number of programs a validator runs, and staking pools. Those points stay in the page’s own list. This article does not rate a pool, a client, or a token.
Set the two jobs next to each other and the comparison is done. In proof of stake, the Ethereum page’s job is a deposit, three clients, an attestation, and sometimes a proposed block. In proof of work, the Bitcoin paper’s job is computation toward a difficulty target, then extending the chain with the most work. A yield, a price, or a countdown is not part of either job as this article states them.
Open the Ethereum page when you want the deposit size, the vote share, or the penalty schedule. Open the Bitcoin paper when you want the proof-of-work argument in the author’s own words. Both pages can change, so the copy on the site is the one to trust.
A wallet balance, a chart, or a headline is not part of either design. If someone asks which chain will be worth more, these two documents do not answer. They describe how a block becomes the next block.
Proof of stake vs proof of work a simple guide ends on that pair of jobs. The photograph is Backlit laptop keyboard keys by ChromeGames923, Wikimedia Commons, licence CC BY-SA 4.0.
