-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathwhat-is-pepper.htm
More file actions
117 lines (106 loc) · 5.27 KB
/
what-is-pepper.htm
File metadata and controls
117 lines (106 loc) · 5.27 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta name="keywords" content="verifiable,verified,verified computation,verifiable compuation,outsourced computation,third-party computing,PCP,probabilistically-checkable proofs,arguments,interactive proofs,IPs" />
<link href="https://fonts.googleapis.com/css?family=Roboto" rel="stylesheet">
<link rel="stylesheet" type="text/css" href="bootstrap/css/bootstrap.css" />
<link rel="stylesheet" type="text/css" href="index.css" />
<title>Pepper: toward practical verifiable computation</title>
</head>
<body>
<div id="wrap">
<div class="container">
<!--fixed navbar on top of the page-->
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="container">
<div class="navbar-header">
<a class="navbar-brand" href="index.htm">
<span>Pepper: toward practical verifiable computation</span>
</a>
</div>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="sidebar col-xs-3">
<div class="container">
<ul id="nav-tab" class="nav sidenav affix">
<li class="">
<a class="tab-toggle" href="index.htm">Home</a>
</li>
<li>
<a class="collapse-toggle" href="what-is-pepper-collapsed.htm">About <span class="up-caret"></span></a>
<ul id="about-collapse" class="in">
<li class="active"><a class="tab-toggle" href="what-is-pepper.htm">What is Pepper?</a></li>
<li class=""><a class="tab-toggle" href="our-approach.htm">Approach and research</a></li>
<li class=""><a class="tab-toggle" href="summary-results.htm">Summary of results</a></li>
<li class=""><a class="tab-toggle" href="summary-systems.htm">Built systems</a></li>
<li class=""><a class="tab-toggle" href="summary-perf.htm">Performance</a></li>
</ul>
</li >
<li class=""><a class="tab-toggle" href="publications.htm">Publications</a></li>
<li class=""><a class="tab-toggle" href="talks.htm">Presentations</a></li>
<li class=""><a class="tab-toggle" href="tutorials.htm">Tutorials and exercises</a></li>
<li class=""><a class="tab-toggle" href="people.htm">People</a></li>
<li class=""><a class="tab-toggle" href="related.htm">Related projects</a></li>
<li class=""><a class="tab-toggle" href="source.htm">Source code</a></li>
<li class=""><a class="tab-toggle" href="funding.htm">Funding and support</a></li>
<li class=""><a class="tab-toggle" href="contact.htm">Contact</a></li>
</ul>
</div>
</div>
<!--content for each tab -->
<div class="tab-content col-xs-9">
<div class="my-tab-pane active" id="what-is-pepper">
<div class="content">
<div class="descriptive">
<h3>Overview: what is Pepper?</h3>
<p>Pepper is an academic research project whose goal is to make
verified computation
practical. By verified computation (which is sometimes also called
“verifiable computation”), we mean a system that implements
the following picture:
</p>
<div class="image-container">
<img id="overview" class="image-center" src="overview.png" alt="Overview of Pepper" />
</div>
<p>One motivation is <i>cloud computing</i> (more
generally, <i>third-party computing</i>).
These environments bring:
</p>
<ul>
<li>Issues of <i>scale</i>: with hundreds of
thousands or millions of machines, correct and
unfailing execution in all cases seems
unlikely.</li>
<li>Issues of <i>trust</i>: the computation “provider” and the “consumer” are
different entities.</li>
</ul>
<!--<p>Thus, we don't want to make any assumptions
about the performing computer, but we still want to
give a guarantee to the delegating computer that the
computation was done correctly.</p>-->
<p>Goal: A system that is</p>
<ol>
<li><b>Comprehensive</b> -- the
system makes no assumptions about the behavior and capabilities of the performing computer other than cryptographic hardness.</li>
<li><b>General-purpose</b> -- not
specialized to a particular family of functions.</li>
<li><b>Practical</b> -- can be used for real problems.</li>
</ol>
<p>Prior work does not meet all three of these properties.</p>
<p>We approach this problem using deep results in cryptography and
complexity theory. <a href="our-approach.htm">Here</a> is a high-level
description of the foundations of our approach.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="bootstrap/js/bootstrap.js" ></script>
</body>
</html>