aboutsummaryrefslogtreecommitdiff
path: root/progress/Overview.tex
diff options
context:
space:
mode:
authorHolden Rohrer <holden.rohrer@gmail.com>2019-10-21 22:07:19 -0400
committerHolden Rohrer <holden.rohrer@gmail.com>2019-10-21 22:07:19 -0400
commit6fe1fe2b715c227fa12a667681aaac15428d6d0e (patch)
treeab521f4253f9d60c2f8f955c620228230d3dcd10 /progress/Overview.tex
parent763aa3e5f18c7fbd0d4df10a23cfa6537fea81e3 (diff)
parent66e5114c037279a2bdba36497027cc8d8e4418b2 (diff)
Merge branch 'modular'
Diffstat (limited to 'progress/Overview.tex')
-rw-r--r--progress/Overview.tex5
1 files changed, 5 insertions, 0 deletions
diff --git a/progress/Overview.tex b/progress/Overview.tex
new file mode 100644
index 0000000..a6f57c0
--- /dev/null
+++ b/progress/Overview.tex
@@ -0,0 +1,5 @@
+There's a famous problem in computer science called the Two Generals' Problem. It follows two Roman camps on opposite sides of a valley, claimed by enemies. Each can send a scout to the other to decide when to attack---which is necessary because if either attacks alone he is guaranteed to lose---but there is no guarantee the scout will arrive. Clearly, one message cannot guarantee consensus between the two. But neither can thirty---or a billion.
+
+This is global consensus in a distributed system, and is still an unsolved problem so far as such a problem can be ``solved.'' This is because it is intimately intertwined with novel technologies, starting with the internet and routing paths (even though it's about 50 years old), torrent software, the TOR network, server redundancy in commercial applications, and the almighty cryptocurrency. % Are all of them necessary? If so, long sentence.
+
+We want to review existing literature on the topic as well as practical applications of those principles (e.g. Bitcoin's consensus algorithm and its failures),\footnote{$^1$}{\link{https://bitcointalk.org/index.php?topic=702755.0}} so