TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The Byzantine Generals Problem (1982) [pdf]

110 点作者 typedweb超过 10 年前

4 条评论

mjb超过 10 年前
If you&#x27;re interested, here&#x27;s some other interesting reading in this area:<p>* Castro and Liskov, &quot;Practical Byzantine Fault Tolerance&quot;, <a href="http://www.pmg.lcs.mit.edu/papers/osdi99.pdf" rel="nofollow">http:&#x2F;&#x2F;www.pmg.lcs.mit.edu&#x2F;papers&#x2F;osdi99.pdf</a> As the title says, this paper describes a practical consensus algorithm that tolerates Byzantine failures. In some ways it is provably optimal.<p>* Lamport, &quot;Leaderless Byzantine Paxos&quot;, <a href="http://research.microsoft.com/en-us/um/people/lamport/pubs/disc-leaderless-web.pdf" rel="nofollow">http:&#x2F;&#x2F;research.microsoft.com&#x2F;en-us&#x2F;um&#x2F;people&#x2F;lamport&#x2F;pubs&#x2F;d...</a> Interesting follow-on from Castro and Liskov, removing the role of the leader.<p>* Driscoll, &quot;Murphy was an Optimist&quot;, <a href="http://www.rvs.uni-bielefeld.de/publications/DriscollMurphyv19.pdf" rel="nofollow">http:&#x2F;&#x2F;www.rvs.uni-bielefeld.de&#x2F;publications&#x2F;DriscollMurphyv...</a> These things really happen in practice.<p>* van Renesse et al, &quot;Byzantine Chain Replication&quot;, <a href="http://www.cs.cornell.edu/home/rvr/newpapers/opodis2012.pdf" rel="nofollow">http:&#x2F;&#x2F;www.cs.cornell.edu&#x2F;home&#x2F;rvr&#x2F;newpapers&#x2F;opodis2012.pdf</a> Very fast replication in a model that allows Byzantine failures.
评论 #8697879 未加载
kanzure超过 10 年前
Here is the explanation that Satoshi Nakamoto was using (and you should totally read most things written by Lamport):<p><a href="http://web.archive.org/web/20090309175840/http://www.bitcoin.org/byzantine.html" rel="nofollow">http:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20090309175840&#x2F;http:&#x2F;&#x2F;www.bitcoin...</a><p>A number of Byzantine Generals each have a computer and want to attack the King&#x27;s wi-fi by brute forcing the password, which they&#x27;ve learned is a certain number of characters in length. Once they stimulate the network to generate a packet, they must crack the password within a limited time to break in and erase the logs, lest they be discovered. They only have enough CPU power to crack it fast enough if a majority of them attack at the same time.<p>They don&#x27;t particularly care when the attack will be, just that they agree. It has been decided that anyone who feels like it will announce an attack time, which we&#x27;ll call the &quot;plan&quot;, and whatever plan is heard first will be the official plan. The problem is that the network is not instantaneous, and if two generals announce different plans at close to the same time, some may hear one first and others hear the other first.<p>They use a proof-of-work chain to solve the problem. Once each general receives whatever plan he hears first, he sets his computer to solve a difficult hash-based proof-of-work problem that includes the plan in its hash. The proof-of-work is difficult enough that with all of them working at once, it&#x27;s expected to take 10 minutes before one of them finds a solution and broadcasts it to the network. Once received, everyone adjusts the hash in their proof-of-work computation to include the first solution, so that when they find the next proof-of-work, it chains after the first one. If anyone was working on a different plan, they switch to this one, because its proof-of-work chain is now longer.<p>After about two hours, the plan should be hashed by a chain of 12 proofs-of-work. Every general, just by verifying the difficulty of the proof-of-work chain, can estimate how much parallel CPU power per hour was expended on it and see that it must have required the majority of the computers to produce in the allotted time. At the least, most of them had to have seen the plan, since the proof-of-work is proof that they worked on it. If the CPU power exhibited by the proof-of-work is sufficient to crack the password, they can safely attack at the agreed time.
评论 #8697596 未加载
评论 #8698561 未加载
AceJohnny2超过 10 年前
This is a classic paper from 1982, which contributed in setting Leslie Lamport as a top distributed computing researcher.<p>What did the poster want to indicate?
评论 #8697292 未加载
评论 #8697487 未加载
tormeh超过 10 年前
<a href="http://research.microsoft.com/en-us/people/mickens/thesaddestmoment.pdf" rel="nofollow">http:&#x2F;&#x2F;research.microsoft.com&#x2F;en-us&#x2F;people&#x2F;mickens&#x2F;thesaddes...</a><p>One of the funniest things I&#x27;ve read about tech.
评论 #8697625 未加载
评论 #8698241 未加载
评论 #8698128 未加载