WEBVTT Kind: captions Language: en 00:00:01.120 --> 00:00:03.360 align:start position:0% so<00:00:01.720> I'm<00:00:01.990> Noah<00:00:02.170> Johnson<00:00:02.320> I'm<00:00:02.590> co-founder<00:00:02.860> and 00:00:03.360 --> 00:00:03.370 align:start position:0% so I'm Noah Johnson I'm co-founder and 00:00:03.370 --> 00:00:05.880 align:start position:0% so I'm Noah Johnson I'm co-founder and chief<00:00:03.610> product<00:00:04.150> officer<00:00:04.360> at<00:00:04.930> Oasis<00:00:05.350> labs<00:00:05.560> and 00:00:05.880 --> 00:00:05.890 align:start position:0% chief product officer at Oasis labs and 00:00:05.890 --> 00:00:07.770 align:start position:0% chief product officer at Oasis labs and I'm<00:00:06.100> gonna<00:00:06.190> talk<00:00:06.400> about<00:00:06.670> privacy<00:00:07.540> preserving 00:00:07.770 --> 00:00:07.780 align:start position:0% I'm gonna talk about privacy preserving 00:00:07.780 --> 00:00:10.799 align:start position:0% I'm gonna talk about privacy preserving smart<00:00:08.320> contracts<00:00:08.740> at<00:00:09.370> scale<00:00:09.730> so<00:00:10.300> if<00:00:10.660> you 00:00:10.799 --> 00:00:10.809 align:start position:0% smart contracts at scale so if you 00:00:10.809 --> 00:00:12.810 align:start position:0% smart contracts at scale so if you follow<00:00:11.050> the<00:00:11.230> news<00:00:11.260> it<00:00:12.250> seems<00:00:12.460> like<00:00:12.580> every 00:00:12.810 --> 00:00:12.820 align:start position:0% follow the news it seems like every 00:00:12.820 --> 00:00:14.430 align:start position:0% follow the news it seems like every article<00:00:13.180> in<00:00:13.420> the<00:00:13.510> last<00:00:13.660> three<00:00:13.960> years<00:00:14.019> or<00:00:14.320> so 00:00:14.430 --> 00:00:14.440 align:start position:0% article in the last three years or so 00:00:14.440 --> 00:00:16.589 align:start position:0% article in the last three years or so has<00:00:14.830> written<00:00:15.040> about<00:00:15.160> the<00:00:15.730> huge<00:00:16.029> potential<00:00:16.390> of 00:00:16.589 --> 00:00:16.599 align:start position:0% has written about the huge potential of 00:00:16.599 --> 00:00:18.060 align:start position:0% has written about the huge potential of blockchain<00:00:16.990> how<00:00:17.019> blockchain<00:00:17.500> can<00:00:17.530> change<00:00:17.890> the 00:00:18.060 --> 00:00:18.070 align:start position:0% blockchain how blockchain can change the 00:00:18.070 --> 00:00:20.550 align:start position:0% blockchain how blockchain can change the world<00:00:18.250> how<00:00:18.610> it<00:00:18.820> can<00:00:19.000> enable<00:00:19.570> fundamentally 00:00:20.550 --> 00:00:20.560 align:start position:0% world how it can enable fundamentally 00:00:20.560 --> 00:00:22.950 align:start position:0% world how it can enable fundamentally new<00:00:20.740> applications<00:00:21.430> and<00:00:21.730> unlock<00:00:22.180> value<00:00:22.690> in 00:00:22.950 --> 00:00:22.960 align:start position:0% new applications and unlock value in 00:00:22.960 --> 00:00:25.710 align:start position:0% new applications and unlock value in different<00:00:23.650> verticals<00:00:24.250> like<00:00:24.520> healthcare<00:00:25.150> now 00:00:25.710 --> 00:00:25.720 align:start position:0% different verticals like healthcare now 00:00:25.720 --> 00:00:27.359 align:start position:0% different verticals like healthcare now if<00:00:26.080> you<00:00:26.199> compare<00:00:26.560> this<00:00:26.710> to<00:00:26.980> where<00:00:27.189> we<00:00:27.340> are 00:00:27.359 --> 00:00:27.369 align:start position:0% if you compare this to where we are 00:00:27.369 --> 00:00:29.970 align:start position:0% if you compare this to where we are today<00:00:28.170> it's<00:00:29.170> clear<00:00:29.410> we're<00:00:29.529> not<00:00:29.560> there<00:00:29.949> yet 00:00:29.970 --> 00:00:29.980 align:start position:0% today it's clear we're not there yet 00:00:29.980 --> 00:00:31.710 align:start position:0% today it's clear we're not there yet right<00:00:30.369> what<00:00:30.699> we<00:00:30.789> have<00:00:30.939> today<00:00:31.150> are<00:00:31.300> things<00:00:31.449> like 00:00:31.710 --> 00:00:31.720 align:start position:0% right what we have today are things like 00:00:31.720 --> 00:00:33.960 align:start position:0% right what we have today are things like crypto<00:00:32.289> kitties<00:00:32.559> group<00:00:33.520> do<00:00:33.640> kitties<00:00:33.850> are 00:00:33.960 --> 00:00:33.970 align:start position:0% crypto kitties group do kitties are 00:00:33.970 --> 00:00:36.150 align:start position:0% crypto kitties group do kitties are great<00:00:34.210> but<00:00:34.630> they're<00:00:34.960> not<00:00:35.200> gonna<00:00:35.649> change<00:00:35.920> the 00:00:36.150 --> 00:00:36.160 align:start position:0% great but they're not gonna change the 00:00:36.160 --> 00:00:38.970 align:start position:0% great but they're not gonna change the world<00:00:36.280> and<00:00:36.640> so<00:00:36.880> an<00:00:37.480> oasis<00:00:37.989> what<00:00:38.230> we're<00:00:38.620> focused 00:00:38.970 --> 00:00:38.980 align:start position:0% world and so an oasis what we're focused 00:00:38.980 --> 00:00:40.650 align:start position:0% world and so an oasis what we're focused on<00:00:39.070> is<00:00:39.219> the<00:00:39.250> question<00:00:39.610> of<00:00:39.730> how<00:00:40.180> do<00:00:40.239> we<00:00:40.329> get 00:00:40.650 --> 00:00:40.660 align:start position:0% on is the question of how do we get 00:00:40.660 --> 00:00:42.660 align:start position:0% on is the question of how do we get there<00:00:40.840> how<00:00:41.020> do<00:00:41.079> we<00:00:41.200> build<00:00:41.950> a<00:00:42.190> computing 00:00:42.660 --> 00:00:42.670 align:start position:0% there how do we build a computing 00:00:42.670 --> 00:00:45.810 align:start position:0% there how do we build a computing platform<00:00:42.700> that<00:00:43.770> allows<00:00:44.770> developers<00:00:45.430> to<00:00:45.640> build 00:00:45.810 --> 00:00:45.820 align:start position:0% platform that allows developers to build 00:00:45.820 --> 00:00:47.819 align:start position:0% platform that allows developers to build these<00:00:46.149> sorts<00:00:46.420> of<00:00:46.510> applications<00:00:46.780> to<00:00:47.469> fulfill 00:00:47.819 --> 00:00:47.829 align:start position:0% these sorts of applications to fulfill 00:00:47.829 --> 00:00:50.580 align:start position:0% these sorts of applications to fulfill exactly<00:00:48.610> these<00:00:48.760> promises<00:00:49.360> and<00:00:49.600> so<00:00:50.140> we're 00:00:50.580 --> 00:00:50.590 align:start position:0% exactly these promises and so we're 00:00:50.590 --> 00:00:52.680 align:start position:0% exactly these promises and so we're building<00:00:51.010> a<00:00:51.219> smart<00:00:51.579> contract<00:00:51.730> platform<00:00:52.390> that 00:00:52.680 --> 00:00:52.690 align:start position:0% building a smart contract platform that 00:00:52.690 --> 00:00:54.510 align:start position:0% building a smart contract platform that can<00:00:52.840> support<00:00:53.140> real<00:00:53.440> world<00:00:53.649> applications<00:00:54.309> and 00:00:54.510 --> 00:00:54.520 align:start position:0% can support real world applications and 00:00:54.520 --> 00:00:56.369 align:start position:0% can support real world applications and what<00:00:54.700> makes<00:00:54.910> our<00:00:55.149> platform<00:00:55.629> unique<00:00:55.930> is<00:00:56.140> that 00:00:56.369 --> 00:00:56.379 align:start position:0% what makes our platform unique is that 00:00:56.379 --> 00:00:59.040 align:start position:0% what makes our platform unique is that we're<00:00:57.250> focused<00:00:57.579> on<00:00:57.700> both<00:00:58.000> privacy<00:00:58.780> and 00:00:59.040 --> 00:00:59.050 align:start position:0% we're focused on both privacy and 00:00:59.050 --> 00:01:02.310 align:start position:0% we're focused on both privacy and scalability<00:01:00.010> together<00:01:00.699> now<00:01:01.329> by<00:01:01.539> privacy<00:01:02.289> I 00:01:02.310 --> 00:01:02.320 align:start position:0% scalability together now by privacy I 00:01:02.320 --> 00:01:04.560 align:start position:0% scalability together now by privacy I mean<00:01:02.680> the<00:01:03.129> ability<00:01:03.340> to<00:01:03.579> protect<00:01:03.760> data<00:01:04.210> and 00:01:04.560 --> 00:01:04.570 align:start position:0% mean the ability to protect data and 00:01:04.570 --> 00:01:07.199 align:start position:0% mean the ability to protect data and state<00:01:05.229> of<00:01:05.529> the<00:01:05.889> smart<00:01:06.130> contract<00:01:06.310> as<00:01:06.759> it<00:01:06.969> runs 00:01:07.199 --> 00:01:07.209 align:start position:0% state of the smart contract as it runs 00:01:07.209 --> 00:01:09.539 align:start position:0% state of the smart contract as it runs on<00:01:07.420> a<00:01:07.600> decentralized<00:01:08.350> network<00:01:08.679> and<00:01:08.889> for 00:01:09.539 --> 00:01:09.549 align:start position:0% on a decentralized network and for 00:01:09.549 --> 00:01:11.699 align:start position:0% on a decentralized network and for scalability<00:01:09.969> we<00:01:10.209> mean<00:01:10.359> not<00:01:10.539> just<00:01:10.569> high<00:01:11.200> TPS 00:01:11.699 --> 00:01:11.709 align:start position:0% scalability we mean not just high TPS 00:01:11.709 --> 00:01:13.859 align:start position:0% scalability we mean not just high TPS and<00:01:11.950> low<00:01:12.159> latency<00:01:12.340> which<00:01:12.880> is<00:01:13.060> what<00:01:13.600> most 00:01:13.859 --> 00:01:13.869 align:start position:0% and low latency which is what most 00:01:13.869 --> 00:01:15.989 align:start position:0% and low latency which is what most projects<00:01:14.560> talk<00:01:14.740> about<00:01:15.009> when<00:01:15.579> they<00:01:15.700> discuss 00:01:15.989 --> 00:01:15.999 align:start position:0% projects talk about when they discuss 00:01:15.999 --> 00:01:18.480 align:start position:0% projects talk about when they discuss scalability<00:01:16.599> what<00:01:17.259> we<00:01:17.409> mean<00:01:17.619> specifically<00:01:18.399> is 00:01:18.480 --> 00:01:18.490 align:start position:0% scalability what we mean specifically is 00:01:18.490 --> 00:01:20.309 align:start position:0% scalability what we mean specifically is the<00:01:18.609> ability<00:01:18.759> to<00:01:18.939> scale<00:01:19.329> to<00:01:19.630> fundamentally 00:01:20.309 --> 00:01:20.319 align:start position:0% the ability to scale to fundamentally 00:01:20.319 --> 00:01:22.800 align:start position:0% the ability to scale to fundamentally more<00:01:20.469> complex<00:01:21.130> types<00:01:21.429> of<00:01:21.639> applications<00:01:22.329> so<00:01:22.779> we 00:01:22.800 --> 00:01:22.810 align:start position:0% more complex types of applications so we 00:01:22.810 --> 00:01:24.749 align:start position:0% more complex types of applications so we think<00:01:23.020> these<00:01:23.289> two<00:01:23.619> things<00:01:23.889> are<00:01:24.039> absolutely 00:01:24.749 --> 00:01:24.759 align:start position:0% think these two things are absolutely 00:01:24.759 --> 00:01:27.269 align:start position:0% think these two things are absolutely necessary<00:01:25.359> to<00:01:25.630> support<00:01:26.109> applications<00:01:26.799> of<00:01:27.069> the 00:01:27.269 --> 00:01:27.279 align:start position:0% necessary to support applications of the 00:01:27.279 --> 00:01:29.639 align:start position:0% necessary to support applications of the future<00:01:27.659> so<00:01:28.659> if<00:01:28.719> we<00:01:28.779> take<00:01:28.899> a<00:01:28.959> step<00:01:29.079> back<00:01:29.349> there's 00:01:29.639 --> 00:01:29.649 align:start position:0% future so if we take a step back there's 00:01:29.649 --> 00:01:31.199 align:start position:0% future so if we take a step back there's a<00:01:29.709> reason<00:01:30.249> people<00:01:30.279> are<00:01:30.579> so<00:01:30.700> excited<00:01:30.819> about 00:01:31.199 --> 00:01:31.209 align:start position:0% a reason people are so excited about 00:01:31.209 --> 00:01:33.179 align:start position:0% a reason people are so excited about blockchain<00:01:31.899> in<00:01:32.499> the<00:01:32.619> first<00:01:32.799> place 00:01:33.179 --> 00:01:33.189 align:start position:0% blockchain in the first place 00:01:33.189 --> 00:01:34.559 align:start position:0% blockchain in the first place blockchain<00:01:33.700> has<00:01:33.849> a<00:01:33.880> number<00:01:34.329> of<00:01:34.419> really 00:01:34.559 --> 00:01:34.569 align:start position:0% blockchain has a number of really 00:01:34.569 --> 00:01:36.179 align:start position:0% blockchain has a number of really exciting<00:01:35.020> properties<00:01:35.469> like<00:01:35.740> the<00:01:35.889> fact<00:01:36.099> that 00:01:36.179 --> 00:01:36.189 align:start position:0% exciting properties like the fact that 00:01:36.189 --> 00:01:37.519 align:start position:0% exciting properties like the fact that it's<00:01:36.369> completely<00:01:36.729> open<00:01:36.909> and<00:01:37.209> transparent 00:01:37.519 --> 00:01:37.529 align:start position:0% it's completely open and transparent 00:01:37.529 --> 00:01:40.889 align:start position:0% it's completely open and transparent doesn't<00:01:38.529> rely<00:01:38.799> on<00:01:38.829> any<00:01:39.219> central<00:01:39.939> party<00:01:40.299> and<00:01:40.509> of 00:01:40.889 --> 00:01:40.899 align:start position:0% doesn't rely on any central party and of 00:01:40.899 --> 00:01:42.480 align:start position:0% doesn't rely on any central party and of course<00:01:41.139> through<00:01:41.439> smart<00:01:41.770> contracts<00:01:42.189> we<00:01:42.340> can 00:01:42.480 --> 00:01:42.490 align:start position:0% course through smart contracts we can 00:01:42.490 --> 00:01:45.419 align:start position:0% course through smart contracts we can automatically<00:01:43.090> enforce<00:01:43.959> agreements<00:01:44.829> even 00:01:45.419 --> 00:01:45.429 align:start position:0% automatically enforce agreements even 00:01:45.429 --> 00:01:46.649 align:start position:0% automatically enforce agreements even with<00:01:45.549> people<00:01:45.849> that<00:01:45.999> we<00:01:46.119> don't<00:01:46.239> otherwise 00:01:46.649 --> 00:01:46.659 align:start position:0% with people that we don't otherwise 00:01:46.659 --> 00:01:50.639 align:start position:0% with people that we don't otherwise trust<00:01:47.279> but<00:01:48.899> blockchain<00:01:49.899> by<00:01:50.049> itself<00:01:50.409> actually 00:01:50.639 --> 00:01:50.649 align:start position:0% trust but blockchain by itself actually 00:01:50.649 --> 00:01:52.800 align:start position:0% trust but blockchain by itself actually doesn't<00:01:51.249> provide<00:01:51.579> privacy<00:01:51.999> so<00:01:52.329> blockchain 00:01:52.800 --> 00:01:52.810 align:start position:0% doesn't provide privacy so blockchain 00:01:52.810 --> 00:01:54.899 align:start position:0% doesn't provide privacy so blockchain can<00:01:52.989> provide<00:01:53.200> anonymity<00:01:53.799> in<00:01:54.189> that<00:01:54.399> I<00:01:54.609> can<00:01:54.789> have 00:01:54.899 --> 00:01:54.909 align:start position:0% can provide anonymity in that I can have 00:01:54.909 --> 00:01:56.309 align:start position:0% can provide anonymity in that I can have a<00:01:54.939> wallet<00:01:55.239> that's<00:01:55.599> not<00:01:55.779> linked<00:01:56.109> to<00:01:56.139> my 00:01:56.309 --> 00:01:56.319 align:start position:0% a wallet that's not linked to my 00:01:56.319 --> 00:01:59.190 align:start position:0% a wallet that's not linked to my identity<00:01:56.709> but<00:01:57.279> it<00:01:57.489> doesn't<00:01:58.090> protect<00:01:58.539> the<00:01:58.959> data 00:01:59.190 --> 00:01:59.200 align:start position:0% identity but it doesn't protect the data 00:01:59.200 --> 00:02:00.929 align:start position:0% identity but it doesn't protect the data and<00:01:59.559> the<00:01:59.679> computation<00:02:00.369> that's<00:02:00.549> running<00:02:00.759> on 00:02:00.929 --> 00:02:00.939 align:start position:0% and the computation that's running on 00:02:00.939 --> 00:02:02.459 align:start position:0% and the computation that's running on the<00:02:01.029> network<00:02:01.359> in<00:02:01.539> fact<00:02:01.779> today's<00:02:02.049> blockchain 00:02:02.459 --> 00:02:02.469 align:start position:0% the network in fact today's blockchain 00:02:02.469 --> 00:02:04.529 align:start position:0% the network in fact today's blockchain platforms<00:02:02.919> are<00:02:03.069> designed<00:02:03.700> so<00:02:03.969> that<00:02:03.999> all<00:02:04.149> data 00:02:04.529 --> 00:02:04.539 align:start position:0% platforms are designed so that all data 00:02:04.539 --> 00:02:06.330 align:start position:0% platforms are designed so that all data is<00:02:04.719> public<00:02:05.169> this<00:02:05.380> makes<00:02:05.590> the<00:02:05.709> architecture<00:02:06.309> a 00:02:06.330 --> 00:02:06.340 align:start position:0% is public this makes the architecture a 00:02:06.340 --> 00:02:08.940 align:start position:0% is public this makes the architecture a lot<00:02:06.549> simpler<00:02:06.989> and<00:02:07.989> so<00:02:08.410> this<00:02:08.560> is<00:02:08.679> a<00:02:08.709> huge 00:02:08.940 --> 00:02:08.950 align:start position:0% lot simpler and so this is a huge 00:02:08.950 --> 00:02:10.380 align:start position:0% lot simpler and so this is a huge limitation<00:02:09.549> if<00:02:09.610> you<00:02:09.700> think<00:02:09.849> about<00:02:09.939> all<00:02:10.209> the 00:02:10.380 --> 00:02:10.390 align:start position:0% limitation if you think about all the 00:02:10.390 --> 00:02:12.240 align:start position:0% limitation if you think about all the applications<00:02:11.170> on<00:02:11.439> the<00:02:11.590> internet<00:02:11.920> that<00:02:12.099> could 00:02:12.240 --> 00:02:12.250 align:start position:0% applications on the internet that could 00:02:12.250 --> 00:02:14.640 align:start position:0% applications on the internet that could benefit<00:02:12.760> from<00:02:13.000> these<00:02:13.540> properties 00:02:14.640 --> 00:02:14.650 align:start position:0% benefit from these properties 00:02:14.650 --> 00:02:16.229 align:start position:0% benefit from these properties and<00:02:14.739> then<00:02:14.980> you<00:02:15.069> think<00:02:15.250> about<00:02:15.430> which<00:02:15.909> of<00:02:15.939> those 00:02:16.229 --> 00:02:16.239 align:start position:0% and then you think about which of those 00:02:16.239 --> 00:02:19.319 align:start position:0% and then you think about which of those would<00:02:16.569> still<00:02:16.930> work<00:02:17.170> if<00:02:17.530> you<00:02:18.519> required<00:02:19.090> that 00:02:19.319 --> 00:02:19.329 align:start position:0% would still work if you required that 00:02:19.329 --> 00:02:21.210 align:start position:0% would still work if you required that all<00:02:19.599> of<00:02:19.840> the<00:02:19.930> data<00:02:20.079> was<00:02:20.409> publicly<00:02:20.860> accessible 00:02:21.210 --> 00:02:21.220 align:start position:0% all of the data was publicly accessible 00:02:21.220 --> 00:02:23.369 align:start position:0% all of the data was publicly accessible to<00:02:21.549> everyone<00:02:21.760> in<00:02:21.970> the<00:02:22.060> world<00:02:22.090> right<00:02:22.989> the<00:02:23.170> list 00:02:23.369 --> 00:02:23.379 align:start position:0% to everyone in the world right the list 00:02:23.379 --> 00:02:25.530 align:start position:0% to everyone in the world right the list gets<00:02:23.650> pretty<00:02:24.250> small<00:02:24.579> and<00:02:24.790> so<00:02:24.970> this<00:02:25.239> is<00:02:25.390> I<00:02:25.420> think 00:02:25.530 --> 00:02:25.540 align:start position:0% gets pretty small and so this is I think 00:02:25.540 --> 00:02:27.509 align:start position:0% gets pretty small and so this is I think one<00:02:25.750> of<00:02:25.780> the<00:02:25.930> reasons<00:02:26.230> we<00:02:26.349> haven't<00:02:26.590> seen<00:02:26.920> many 00:02:27.509 --> 00:02:27.519 align:start position:0% one of the reasons we haven't seen many 00:02:27.519 --> 00:02:29.819 align:start position:0% one of the reasons we haven't seen many of<00:02:27.640> these<00:02:27.760> breakthrough<00:02:28.299> applications<00:02:28.959> yet 00:02:29.819 --> 00:02:29.829 align:start position:0% of these breakthrough applications yet 00:02:29.829 --> 00:02:32.670 align:start position:0% of these breakthrough applications yet so<00:02:30.610> what<00:02:31.269> could<00:02:31.420> you<00:02:31.540> do<00:02:31.689> if<00:02:31.930> you<00:02:32.049> were<00:02:32.230> able<00:02:32.530> to 00:02:32.670 --> 00:02:32.680 align:start position:0% so what could you do if you were able to 00:02:32.680 --> 00:02:34.679 align:start position:0% so what could you do if you were able to provide<00:02:32.920> privacy<00:02:33.430> here's<00:02:33.819> a<00:02:33.879> list<00:02:34.209> of<00:02:34.390> some<00:02:34.569> of 00:02:34.679 --> 00:02:34.689 align:start position:0% provide privacy here's a list of some of 00:02:34.689 --> 00:02:36.420 align:start position:0% provide privacy here's a list of some of the<00:02:34.780> applications<00:02:35.319> that<00:02:35.409> people<00:02:35.769> are<00:02:36.069> already 00:02:36.420 --> 00:02:36.430 align:start position:0% the applications that people are already 00:02:36.430 --> 00:02:38.880 align:start position:0% the applications that people are already building<00:02:36.760> or<00:02:37.120> excited<00:02:37.840> to<00:02:37.959> build<00:02:38.109> on 00:02:38.880 --> 00:02:38.890 align:start position:0% building or excited to build on 00:02:38.890 --> 00:02:41.099 align:start position:0% building or excited to build on blockchain<00:02:39.329> things<00:02:40.329> ranging<00:02:40.659> from<00:02:40.810> credit 00:02:41.099 --> 00:02:41.109 align:start position:0% blockchain things ranging from credit 00:02:41.109 --> 00:02:44.220 align:start position:0% blockchain things ranging from credit scoring<00:02:41.379> to<00:02:41.739> private<00:02:42.220> escrow<00:02:42.780> to<00:02:43.780> you<00:02:44.109> know 00:02:44.220 --> 00:02:44.230 align:start position:0% scoring to private escrow to you know 00:02:44.230 --> 00:02:47.339 align:start position:0% scoring to private escrow to you know games<00:02:44.500> and<00:02:44.890> private<00:02:45.340> tokens<00:02:45.670> so<00:02:46.569> what<00:02:47.049> do<00:02:47.139> all 00:02:47.339 --> 00:02:47.349 align:start position:0% games and private tokens so what do all 00:02:47.349 --> 00:02:49.740 align:start position:0% games and private tokens so what do all these<00:02:47.560> things<00:02:47.620> have<00:02:48.220> in<00:02:48.549> common<00:02:48.609> well<00:02:49.450> they 00:02:49.740 --> 00:02:49.750 align:start position:0% these things have in common well they 00:02:49.750 --> 00:02:51.750 align:start position:0% these things have in common well they all<00:02:49.900> need<00:02:50.409> privacy<00:02:50.799> they<00:02:51.040> all<00:02:51.250> need<00:02:51.579> the 00:02:51.750 --> 00:02:51.760 align:start position:0% all need privacy they all need the 00:02:51.760 --> 00:02:54.420 align:start position:0% all need privacy they all need the ability<00:02:52.060> to<00:02:52.329> protect<00:02:52.930> data<00:02:53.349> or<00:02:53.799> protect<00:02:54.220> state 00:02:54.420 --> 00:02:54.430 align:start position:0% ability to protect data or protect state 00:02:54.430 --> 00:02:56.399 align:start position:0% ability to protect data or protect state either<00:02:54.909> because<00:02:55.269> the<00:02:55.389> data<00:02:55.569> is<00:02:55.690> sensitive<00:02:56.170> for 00:02:56.399 --> 00:02:56.409 align:start position:0% either because the data is sensitive for 00:02:56.409 --> 00:02:58.770 align:start position:0% either because the data is sensitive for example<00:02:56.769> it's<00:02:56.950> user<00:02:57.519> data<00:02:57.819> like<00:02:58.389> in<00:02:58.510> the<00:02:58.629> case 00:02:58.770 --> 00:02:58.780 align:start position:0% example it's user data like in the case 00:02:58.780 --> 00:03:00.750 align:start position:0% example it's user data like in the case of<00:02:58.810> healthcare<00:02:59.260> or<00:02:59.530> you<00:03:00.040> just<00:03:00.220> need<00:03:00.459> to<00:03:00.670> be 00:03:00.750 --> 00:03:00.760 align:start position:0% of healthcare or you just need to be 00:03:00.760 --> 00:03:02.789 align:start position:0% of healthcare or you just need to be able<00:03:00.879> to<00:03:01.060> keep<00:03:01.689> certain<00:03:02.019> aspects<00:03:02.530> of<00:03:02.680> the 00:03:02.789 --> 00:03:02.799 align:start position:0% able to keep certain aspects of the 00:03:02.799 --> 00:03:04.830 align:start position:0% able to keep certain aspects of the application<00:03:02.920> secret<00:03:03.760> in<00:03:03.909> order<00:03:04.480> for<00:03:04.659> the 00:03:04.830 --> 00:03:04.840 align:start position:0% application secret in order for the 00:03:04.840 --> 00:03:07.050 align:start position:0% application secret in order for the incentives<00:03:05.409> to<00:03:05.590> work<00:03:05.799> out<00:03:05.980> for<00:03:06.159> example<00:03:06.310> games 00:03:07.050 --> 00:03:07.060 align:start position:0% incentives to work out for example games 00:03:07.060 --> 00:03:08.699 align:start position:0% incentives to work out for example games I<00:03:07.420> need<00:03:07.569> to<00:03:07.689> be<00:03:07.810> able<00:03:07.930> to<00:03:08.049> keep<00:03:08.379> the<00:03:08.560> secret 00:03:08.699 --> 00:03:08.709 align:start position:0% I need to be able to keep the secret 00:03:08.709 --> 00:03:10.860 align:start position:0% I need to be able to keep the secret part<00:03:09.129> of<00:03:09.189> the<00:03:09.280> game<00:03:09.459> secret<00:03:10.030> from<00:03:10.420> the<00:03:10.510> miners 00:03:10.860 --> 00:03:10.870 align:start position:0% part of the game secret from the miners 00:03:10.870 --> 00:03:12.210 align:start position:0% part of the game secret from the miners and<00:03:10.900> the<00:03:11.049> players<00:03:11.290> to<00:03:11.620> make<00:03:11.739> sure<00:03:11.920> that<00:03:12.069> they 00:03:12.210 --> 00:03:12.220 align:start position:0% and the players to make sure that they 00:03:12.220 --> 00:03:14.789 align:start position:0% and the players to make sure that they don't<00:03:12.340> cheat<00:03:12.989> so<00:03:13.989> these<00:03:14.139> are<00:03:14.319> all<00:03:14.439> really 00:03:14.789 --> 00:03:14.799 align:start position:0% don't cheat so these are all really 00:03:14.799 --> 00:03:16.589 align:start position:0% don't cheat so these are all really exciting<00:03:15.220> applications<00:03:15.849> but<00:03:16.030> if<00:03:16.120> you<00:03:16.209> wanted 00:03:16.589 --> 00:03:16.599 align:start position:0% exciting applications but if you wanted 00:03:16.599 --> 00:03:18.119 align:start position:0% exciting applications but if you wanted to<00:03:16.659> run<00:03:16.930> these<00:03:17.049> applications<00:03:17.680> on<00:03:17.829> today's 00:03:18.119 --> 00:03:18.129 align:start position:0% to run these applications on today's 00:03:18.129 --> 00:03:20.729 align:start position:0% to run these applications on today's platforms<00:03:18.760> you<00:03:19.299> wouldn't<00:03:19.569> be<00:03:19.629> able<00:03:19.750> to<00:03:20.079> and<00:03:20.319> to 00:03:20.729 --> 00:03:20.739 align:start position:0% platforms you wouldn't be able to and to 00:03:20.739 --> 00:03:22.470 align:start position:0% platforms you wouldn't be able to and to illustrate<00:03:20.859> that<00:03:21.220> let's<00:03:21.639> take<00:03:22.180> a<00:03:22.209> simple 00:03:22.470 --> 00:03:22.480 align:start position:0% illustrate that let's take a simple 00:03:22.480 --> 00:03:24.629 align:start position:0% illustrate that let's take a simple example<00:03:22.660> of<00:03:23.019> credit<00:03:23.349> scoring<00:03:23.620> so<00:03:24.040> I<00:03:24.069> could<00:03:24.489> go 00:03:24.629 --> 00:03:24.639 align:start position:0% example of credit scoring so I could go 00:03:24.639 --> 00:03:27.150 align:start position:0% example of credit scoring so I could go out<00:03:24.819> and<00:03:24.849> write<00:03:25.480> a<00:03:25.840> smart<00:03:26.319> contract<00:03:26.769> that<00:03:26.949> does 00:03:27.150 --> 00:03:27.160 align:start position:0% out and write a smart contract that does 00:03:27.160 --> 00:03:28.650 align:start position:0% out and write a smart contract that does credit<00:03:27.430> scoring<00:03:27.790> right<00:03:28.090> I<00:03:28.120> could<00:03:28.359> implement 00:03:28.650 --> 00:03:28.660 align:start position:0% credit scoring right I could implement 00:03:28.660 --> 00:03:31.080 align:start position:0% credit scoring right I could implement this<00:03:28.900> in<00:03:29.109> solidity<00:03:29.799> the<00:03:30.250> contract<00:03:30.730> could<00:03:30.849> take 00:03:31.080 --> 00:03:31.090 align:start position:0% this in solidity the contract could take 00:03:31.090 --> 00:03:33.330 align:start position:0% this in solidity the contract could take in<00:03:31.269> some<00:03:31.629> data<00:03:32.290> from<00:03:32.620> various<00:03:33.129> institutions 00:03:33.330 --> 00:03:33.340 align:start position:0% in some data from various institutions 00:03:33.340 --> 00:03:36.390 align:start position:0% in some data from various institutions and<00:03:34.180> output<00:03:34.989> a<00:03:35.019> model<00:03:35.440> for<00:03:35.709> predicting<00:03:36.099> a 00:03:36.390 --> 00:03:36.400 align:start position:0% and output a model for predicting a 00:03:36.400 --> 00:03:39.180 align:start position:0% and output a model for predicting a credit<00:03:36.730> score<00:03:37.169> now<00:03:38.169> if<00:03:38.260> I<00:03:38.349> try<00:03:38.620> to<00:03:38.680> take<00:03:38.980> this 00:03:39.180 --> 00:03:39.190 align:start position:0% credit score now if I try to take this 00:03:39.190 --> 00:03:42.270 align:start position:0% credit score now if I try to take this and<00:03:39.430> run<00:03:40.000> it<00:03:40.060> on<00:03:40.359> today's<00:03:41.019> platforms<00:03:41.620> I'd<00:03:42.069> face 00:03:42.270 --> 00:03:42.280 align:start position:0% and run it on today's platforms I'd face 00:03:42.280 --> 00:03:43.379 align:start position:0% and run it on today's platforms I'd face a<00:03:42.310> number<00:03:42.609> of<00:03:42.669> issues<00:03:42.790> that<00:03:42.970> make<00:03:43.269> this 00:03:43.379 --> 00:03:43.389 align:start position:0% a number of issues that make this 00:03:43.389 --> 00:03:45.809 align:start position:0% a number of issues that make this completely<00:03:43.659> impractical<00:03:44.400> the<00:03:45.400> first<00:03:45.579> issue 00:03:45.809 --> 00:03:45.819 align:start position:0% completely impractical the first issue 00:03:45.819 --> 00:03:48.300 align:start position:0% completely impractical the first issue is<00:03:46.000> that<00:03:46.419> if<00:03:46.900> the<00:03:47.109> output<00:03:47.620> of<00:03:47.650> my<00:03:47.829> smart 00:03:48.300 --> 00:03:48.310 align:start position:0% is that if the output of my smart 00:03:48.310 --> 00:03:50.640 align:start position:0% is that if the output of my smart contract<00:03:48.760> is<00:03:48.909> derived<00:03:49.299> from<00:03:49.510> sensitive<00:03:50.319> input 00:03:50.640 --> 00:03:50.650 align:start position:0% contract is derived from sensitive input 00:03:50.650 --> 00:03:52.649 align:start position:0% contract is derived from sensitive input data<00:03:50.829> then<00:03:51.400> I<00:03:51.430> have<00:03:51.609> to<00:03:51.729> be<00:03:51.819> very<00:03:52.150> careful<00:03:52.569> to 00:03:52.649 --> 00:03:52.659 align:start position:0% data then I have to be very careful to 00:03:52.659 --> 00:03:54.030 align:start position:0% data then I have to be very careful to make<00:03:52.690> sure<00:03:52.840> that<00:03:53.079> the<00:03:53.169> output<00:03:53.319> doesn't<00:03:53.739> leak 00:03:54.030 --> 00:03:54.040 align:start position:0% make sure that the output doesn't leak 00:03:54.040 --> 00:03:56.670 align:start position:0% make sure that the output doesn't leak anything<00:03:54.430> about<00:03:54.909> the<00:03:55.120> inputs<00:03:55.510> this<00:03:56.440> might 00:03:56.670 --> 00:03:56.680 align:start position:0% anything about the inputs this might 00:03:56.680 --> 00:03:58.979 align:start position:0% anything about the inputs this might seem<00:03:56.949> like<00:03:57.310> this<00:03:57.940> is<00:03:58.120> intuitive<00:03:58.479> if<00:03:58.840> you're 00:03:58.979 --> 00:03:58.989 align:start position:0% seem like this is intuitive if you're 00:03:58.989 --> 00:04:00.210 align:start position:0% seem like this is intuitive if you're doing<00:03:59.169> machine<00:03:59.470> learning<00:03:59.530> of<00:03:59.889> course<00:03:59.949> you're 00:04:00.210 --> 00:04:00.220 align:start position:0% doing machine learning of course you're 00:04:00.220 --> 00:04:01.619 align:start position:0% doing machine learning of course you're not<00:04:00.340> leaking<00:04:00.579> information<00:04:00.909> it<00:04:01.269> turns<00:04:01.449> out 00:04:01.619 --> 00:04:01.629 align:start position:0% not leaking information it turns out 00:04:01.629 --> 00:04:03.180 align:start position:0% not leaking information it turns out actually<00:04:01.900> that<00:04:02.109> assumption<00:04:02.530> is<00:04:02.799> completely 00:04:03.180 --> 00:04:03.190 align:start position:0% actually that assumption is completely 00:04:03.190 --> 00:04:05.490 align:start position:0% actually that assumption is completely wrong<00:04:03.370> and<00:04:03.519> you<00:04:04.030> need<00:04:04.209> to<00:04:04.449> employ<00:04:04.930> solutions 00:04:05.490 --> 00:04:05.500 align:start position:0% wrong and you need to employ solutions 00:04:05.500 --> 00:04:07.050 align:start position:0% wrong and you need to employ solutions at<00:04:05.620> the<00:04:05.709> application<00:04:06.280> layer<00:04:06.430> to<00:04:06.909> protect 00:04:07.050 --> 00:04:07.060 align:start position:0% at the application layer to protect 00:04:07.060 --> 00:04:09.300 align:start position:0% at the application layer to protect against<00:04:07.540> information<00:04:08.169> leakage<00:04:08.500> in<00:04:08.709> this<00:04:09.159> way 00:04:09.300 --> 00:04:09.310 align:start position:0% against information leakage in this way 00:04:09.310 --> 00:04:11.789 align:start position:0% against information leakage in this way the<00:04:10.030> other<00:04:10.150> problem<00:04:10.599> of<00:04:10.690> course<00:04:10.750> is<00:04:11.139> that<00:04:11.199> the 00:04:11.789 --> 00:04:11.799 align:start position:0% the other problem of course is that the 00:04:11.799 --> 00:04:13.379 align:start position:0% the other problem of course is that the workers<00:04:12.250> that<00:04:12.280> actually<00:04:12.760> run<00:04:13.030> the 00:04:13.379 --> 00:04:13.389 align:start position:0% workers that actually run the 00:04:13.389 --> 00:04:15.420 align:start position:0% workers that actually run the computation<00:04:13.690> the<00:04:14.260> workers<00:04:14.650> that<00:04:14.799> execute<00:04:15.280> the 00:04:15.420 --> 00:04:15.430 align:start position:0% computation the workers that execute the 00:04:15.430 --> 00:04:17.460 align:start position:0% computation the workers that execute the smart<00:04:15.639> contract<00:04:15.849> will<00:04:16.690> have<00:04:16.870> access<00:04:17.229> to<00:04:17.349> all 00:04:17.460 --> 00:04:17.470 align:start position:0% smart contract will have access to all 00:04:17.470 --> 00:04:19.620 align:start position:0% smart contract will have access to all of<00:04:17.500> this<00:04:17.709> really<00:04:18.010> sensitive<00:04:18.310> data<00:04:18.579> so<00:04:19.150> if<00:04:19.479> I 00:04:19.620 --> 00:04:19.630 align:start position:0% of this really sensitive data so if I 00:04:19.630 --> 00:04:21.509 align:start position:0% of this really sensitive data so if I don't<00:04:19.690> trust<00:04:19.989> those<00:04:20.260> workers<00:04:20.500> if<00:04:20.949> this<00:04:21.340> data 00:04:21.509 --> 00:04:21.519 align:start position:0% don't trust those workers if this data 00:04:21.519 --> 00:04:23.129 align:start position:0% don't trust those workers if this data is<00:04:21.639> really<00:04:21.699> sensitive<00:04:22.210> they<00:04:22.449> could<00:04:22.599> trivially 00:04:23.129 --> 00:04:23.139 align:start position:0% is really sensitive they could trivially 00:04:23.139 --> 00:04:25.680 align:start position:0% is really sensitive they could trivially snoop<00:04:23.800> on<00:04:23.919> the<00:04:24.039> data<00:04:24.250> or<00:04:24.550> leak<00:04:24.849> the<00:04:25.029> data<00:04:25.210> so 00:04:25.680 --> 00:04:25.690 align:start position:0% snoop on the data or leak the data so 00:04:25.690 --> 00:04:27.089 align:start position:0% snoop on the data or leak the data so for<00:04:25.870> that<00:04:25.960> reason<00:04:26.020> I<00:04:26.529> wouldn't<00:04:26.770> be<00:04:26.889> able<00:04:26.979> to 00:04:27.089 --> 00:04:27.099 align:start position:0% for that reason I wouldn't be able to 00:04:27.099 --> 00:04:27.840 align:start position:0% for that reason I wouldn't be able to run<00:04:27.310> this<00:04:27.550> on 00:04:27.840 --> 00:04:27.850 align:start position:0% run this on 00:04:27.850 --> 00:04:29.490 align:start position:0% run this on platform<00:04:28.240> where<00:04:28.420> all<00:04:28.450> the<00:04:28.690> data<00:04:28.900> is<00:04:29.110> public 00:04:29.490 --> 00:04:29.500 align:start position:0% platform where all the data is public 00:04:29.500 --> 00:04:31.110 align:start position:0% platform where all the data is public and<00:04:29.710> then<00:04:30.070> finally<00:04:30.400> of<00:04:30.490> course<00:04:30.520> this<00:04:30.970> is<00:04:31.090> a 00:04:31.110 --> 00:04:31.120 align:start position:0% and then finally of course this is a 00:04:31.120 --> 00:04:32.760 align:start position:0% and then finally of course this is a relatively<00:04:31.600> complex<00:04:32.080> application 00:04:32.760 --> 00:04:32.770 align:start position:0% relatively complex application 00:04:32.770 --> 00:04:34.680 align:start position:0% relatively complex application everyone's<00:04:33.460> familiar<00:04:33.580> with<00:04:34.000> the<00:04:34.090> scalability 00:04:34.680 --> 00:04:34.690 align:start position:0% everyone's familiar with the scalability 00:04:34.690 --> 00:04:37.200 align:start position:0% everyone's familiar with the scalability challenges<00:04:35.290> of<00:04:35.890> today's<00:04:36.160> platforms<00:04:36.760> right 00:04:37.200 --> 00:04:37.210 align:start position:0% challenges of today's platforms right 00:04:37.210 --> 00:04:39.420 align:start position:0% challenges of today's platforms right now<00:04:37.390> if<00:04:37.630> I<00:04:37.750> wanted<00:04:37.990> to<00:04:38.050> do<00:04:38.230> anything<00:04:38.560> even 00:04:39.420 --> 00:04:39.430 align:start position:0% now if I wanted to do anything even 00:04:39.430 --> 00:04:41.490 align:start position:0% now if I wanted to do anything even moderately<00:04:39.880> sophisticated<00:04:40.510> in<00:04:41.170> a<00:04:41.230> smart 00:04:41.490 --> 00:04:41.500 align:start position:0% moderately sophisticated in a smart 00:04:41.500 --> 00:04:43.530 align:start position:0% moderately sophisticated in a smart contract<00:04:41.980> I<00:04:42.190> would<00:04:42.340> face<00:04:42.640> really<00:04:43.030> really<00:04:43.360> poor 00:04:43.530 --> 00:04:43.540 align:start position:0% contract I would face really really poor 00:04:43.540 --> 00:04:46.470 align:start position:0% contract I would face really really poor performance<00:04:44.050> and<00:04:44.200> very<00:04:44.530> high<00:04:44.740> costs<00:04:45.360> so<00:04:46.360> that 00:04:46.470 --> 00:04:46.480 align:start position:0% performance and very high costs so that 00:04:46.480 --> 00:04:48.090 align:start position:0% performance and very high costs so that brings<00:04:46.570> me<00:04:46.720> to<00:04:46.750> our<00:04:46.840> solution<00:04:47.320> so<00:04:47.470> at<00:04:47.710> Oasis 00:04:48.090 --> 00:04:48.100 align:start position:0% brings me to our solution so at Oasis 00:04:48.100 --> 00:04:49.770 align:start position:0% brings me to our solution so at Oasis we're<00:04:48.280> building<00:04:48.670> a<00:04:48.790> new<00:04:48.970> platform<00:04:49.210> that<00:04:49.480> tries 00:04:49.770 --> 00:04:49.780 align:start position:0% we're building a new platform that tries 00:04:49.780 --> 00:04:51.500 align:start position:0% we're building a new platform that tries to<00:04:49.810> address<00:04:50.350> all<00:04:50.590> of<00:04:50.650> these<00:04:51.130> problems 00:04:51.500 --> 00:04:51.510 align:start position:0% to address all of these problems 00:04:51.510 --> 00:04:53.730 align:start position:0% to address all of these problems specifically<00:04:52.510> we<00:04:53.020> have<00:04:53.170> an<00:04:53.380> architecture 00:04:53.730 --> 00:04:53.740 align:start position:0% specifically we have an architecture 00:04:53.740 --> 00:04:55.920 align:start position:0% specifically we have an architecture that<00:04:54.130> protects<00:04:54.670> privacy<00:04:55.060> both<00:04:55.750> at<00:04:55.870> the 00:04:55.920 --> 00:04:55.930 align:start position:0% that protects privacy both at the 00:04:55.930 --> 00:04:57.570 align:start position:0% that protects privacy both at the application<00:04:56.620> layer<00:04:56.830> as<00:04:57.040> well<00:04:57.280> as<00:04:57.460> the 00:04:57.570 --> 00:04:57.580 align:start position:0% application layer as well as the 00:04:57.580 --> 00:05:00.390 align:start position:0% application layer as well as the platform<00:04:57.760> layer<00:04:58.150> and<00:04:58.470> a<00:04:59.470> new<00:04:59.920> approach<00:05:00.130> for 00:05:00.390 --> 00:05:00.400 align:start position:0% platform layer and a new approach for 00:05:00.400 --> 00:05:03.210 align:start position:0% platform layer and a new approach for scaling<00:05:01.360> to<00:05:01.630> more<00:05:02.050> complex<00:05:02.530> application 00:05:03.210 --> 00:05:03.220 align:start position:0% scaling to more complex application 00:05:03.220 --> 00:05:05.040 align:start position:0% scaling to more complex application workloads<00:05:03.580> so<00:05:04.030> I'll<00:05:04.120> talk<00:05:04.270> about<00:05:04.330> each<00:05:04.840> of 00:05:05.040 --> 00:05:05.050 align:start position:0% workloads so I'll talk about each of 00:05:05.050 --> 00:05:06.900 align:start position:0% workloads so I'll talk about each of these<00:05:05.170> layers<00:05:05.530> kind<00:05:06.070> of<00:05:06.190> independently<00:05:06.760> I'll 00:05:06.900 --> 00:05:06.910 align:start position:0% these layers kind of independently I'll 00:05:06.910 --> 00:05:08.670 align:start position:0% these layers kind of independently I'll describe<00:05:07.300> how<00:05:07.720> our<00:05:07.870> solution<00:05:08.260> works<00:05:08.440> and<00:05:08.590> then 00:05:08.670 --> 00:05:08.680 align:start position:0% describe how our solution works and then 00:05:08.680 --> 00:05:12.300 align:start position:0% describe how our solution works and then how<00:05:08.800> you<00:05:08.830> can<00:05:09.040> use<00:05:09.370> them<00:05:09.550> as<00:05:09.730> developers<00:05:11.310> so 00:05:12.300 --> 00:05:12.310 align:start position:0% how you can use them as developers so 00:05:12.310 --> 00:05:14.100 align:start position:0% how you can use them as developers so let's<00:05:12.490> start<00:05:12.670> with<00:05:12.820> the<00:05:13.090> platform<00:05:13.660> layer<00:05:13.810> so 00:05:14.100 --> 00:05:14.110 align:start position:0% let's start with the platform layer so 00:05:14.110 --> 00:05:16.230 align:start position:0% let's start with the platform layer so how<00:05:14.560> do<00:05:14.620> we<00:05:14.710> protect<00:05:15.160> data<00:05:15.370> that<00:05:15.700> is<00:05:15.790> running 00:05:16.230 --> 00:05:16.240 align:start position:0% how do we protect data that is running 00:05:16.240 --> 00:05:18.810 align:start position:0% how do we protect data that is running on<00:05:16.420> a<00:05:16.480> network<00:05:17.080> of<00:05:17.230> nodes<00:05:17.500> whom<00:05:18.280> we<00:05:18.520> may<00:05:18.670> not 00:05:18.810 --> 00:05:18.820 align:start position:0% on a network of nodes whom we may not 00:05:18.820 --> 00:05:21.570 align:start position:0% on a network of nodes whom we may not trust<00:05:19.530> so<00:05:20.530> if<00:05:20.620> you<00:05:20.710> look<00:05:20.860> at<00:05:20.950> the<00:05:21.070> model<00:05:21.400> for 00:05:21.570 --> 00:05:21.580 align:start position:0% trust so if you look at the model for 00:05:21.580 --> 00:05:23.550 align:start position:0% trust so if you look at the model for smart<00:05:22.120> contracts<00:05:22.540> today<00:05:22.690> the<00:05:22.960> model<00:05:23.410> for 00:05:23.550 --> 00:05:23.560 align:start position:0% smart contracts today the model for 00:05:23.560 --> 00:05:25.320 align:start position:0% smart contracts today the model for smart<00:05:23.770> contracts<00:05:24.160> of<00:05:24.280> course<00:05:24.490> is<00:05:24.700> smart 00:05:25.320 --> 00:05:25.330 align:start position:0% smart contracts of course is smart 00:05:25.330 --> 00:05:26.670 align:start position:0% smart contracts of course is smart contract<00:05:25.660> is<00:05:25.750> a<00:05:25.780> piece<00:05:25.960> of<00:05:26.110> code<00:05:26.290> that<00:05:26.320> takes 00:05:26.670 --> 00:05:26.680 align:start position:0% contract is a piece of code that takes 00:05:26.680 --> 00:05:29.250 align:start position:0% contract is a piece of code that takes in<00:05:26.890> some<00:05:27.010> input<00:05:27.300> running<00:05:28.300> the<00:05:28.420> code<00:05:28.600> produces 00:05:29.250 --> 00:05:29.260 align:start position:0% in some input running the code produces 00:05:29.260 --> 00:05:30.930 align:start position:0% in some input running the code produces some<00:05:29.440> state<00:05:29.680> transition<00:05:30.250> that's<00:05:30.520> recorded 00:05:30.930 --> 00:05:30.940 align:start position:0% some state transition that's recorded 00:05:30.940 --> 00:05:33.300 align:start position:0% some state transition that's recorded back<00:05:31.120> to<00:05:31.360> the<00:05:31.540> ledger<00:05:31.720> and<00:05:32.020> on<00:05:32.770> platforms<00:05:33.220> like 00:05:33.300 --> 00:05:33.310 align:start position:0% back to the ledger and on platforms like 00:05:33.310 --> 00:05:34.860 align:start position:0% back to the ledger and on platforms like aetherium<00:05:33.640> of<00:05:33.880> course<00:05:34.060> all<00:05:34.180> the<00:05:34.300> inputs<00:05:34.690> and 00:05:34.860 --> 00:05:34.870 align:start position:0% aetherium of course all the inputs and 00:05:34.870 --> 00:05:37.760 align:start position:0% aetherium of course all the inputs and outputs<00:05:35.200> are<00:05:35.650> public<00:05:36.340> so<00:05:36.910> the<00:05:37.030> concept<00:05:37.540> of 00:05:37.760 --> 00:05:37.770 align:start position:0% outputs are public so the concept of 00:05:37.770 --> 00:05:40.080 align:start position:0% outputs are public so the concept of confidentiality<00:05:38.770> preserving<00:05:39.730> smart 00:05:40.080 --> 00:05:40.090 align:start position:0% confidentiality preserving smart 00:05:40.090 --> 00:05:42.330 align:start position:0% confidentiality preserving smart contract<00:05:40.450> execution<00:05:40.930> is<00:05:41.200> that<00:05:41.710> all<00:05:41.950> of<00:05:42.220> these 00:05:42.330 --> 00:05:42.340 align:start position:0% contract execution is that all of these 00:05:42.340 --> 00:05:44.850 align:start position:0% contract execution is that all of these inputs<00:05:42.940> and<00:05:43.090> outputs<00:05:43.510> are<00:05:43.660> encrypted<00:05:44.350> that<00:05:44.740> is 00:05:44.850 --> 00:05:44.860 align:start position:0% inputs and outputs are encrypted that is 00:05:44.860 --> 00:05:46.920 align:start position:0% inputs and outputs are encrypted that is they<00:05:45.040> remain<00:05:45.340> secret<00:05:45.820> and<00:05:45.970> nobody<00:05:46.270> else<00:05:46.660> in 00:05:46.920 --> 00:05:46.930 align:start position:0% they remain secret and nobody else in 00:05:46.930 --> 00:05:49.200 align:start position:0% they remain secret and nobody else in the<00:05:47.050> world<00:05:47.280> except<00:05:48.280> for<00:05:48.370> the<00:05:48.730> smart<00:05:49.030> contract 00:05:49.200 --> 00:05:49.210 align:start position:0% the world except for the smart contract 00:05:49.210 --> 00:05:51.390 align:start position:0% the world except for the smart contract can<00:05:49.990> actually<00:05:50.290> view<00:05:50.470> their<00:05:50.620> contents<00:05:51.160> and 00:05:51.390 --> 00:05:51.400 align:start position:0% can actually view their contents and 00:05:51.400 --> 00:05:53.820 align:start position:0% can actually view their contents and this<00:05:51.970> isn't<00:05:52.270> just<00:05:52.690> about<00:05:52.930> encrypting<00:05:53.590> the 00:05:53.820 --> 00:05:53.830 align:start position:0% this isn't just about encrypting the 00:05:53.830 --> 00:05:56.250 align:start position:0% this isn't just about encrypting the data<00:05:53.860> the<00:05:54.640> challenge<00:05:55.090> is<00:05:55.270> being<00:05:55.780> able<00:05:55.930> to 00:05:56.250 --> 00:05:56.260 align:start position:0% data the challenge is being able to 00:05:56.260 --> 00:05:58.770 align:start position:0% data the challenge is being able to still<00:05:56.620> run<00:05:57.120> computations<00:05:58.120> on<00:05:58.330> the<00:05:58.570> data 00:05:58.770 --> 00:05:58.780 align:start position:0% still run computations on the data 00:05:58.780 --> 00:06:01.080 align:start position:0% still run computations on the data without<00:05:59.530> allowing<00:06:00.070> others<00:06:00.340> to<00:06:00.580> view<00:06:00.760> the<00:06:00.910> data 00:06:01.080 --> 00:06:01.090 align:start position:0% without allowing others to view the data 00:06:01.090 --> 00:06:03.900 align:start position:0% without allowing others to view the data and<00:06:01.510> to<00:06:02.410> protect<00:06:02.740> data<00:06:02.890> both<00:06:03.160> during<00:06:03.610> storage 00:06:03.900 --> 00:06:03.910 align:start position:0% and to protect data both during storage 00:06:03.910 --> 00:06:05.370 align:start position:0% and to protect data both during storage when<00:06:04.330> the<00:06:04.450> data<00:06:04.630> is<00:06:04.750> when<00:06:04.900> the<00:06:05.020> state<00:06:05.200> for 00:06:05.370 --> 00:06:05.380 align:start position:0% when the data is when the state for 00:06:05.380 --> 00:06:07.320 align:start position:0% when the data is when the state for example<00:06:05.440> stored<00:06:05.920> on<00:06:06.010> the<00:06:06.070> ledger<00:06:06.250> and<00:06:06.580> when 00:06:07.320 --> 00:06:07.330 align:start position:0% example stored on the ledger and when 00:06:07.330 --> 00:06:09.470 align:start position:0% example stored on the ledger and when the<00:06:07.450> data<00:06:07.630> is<00:06:07.720> actually<00:06:07.930> being<00:06:08.140> computed<00:06:08.860> on 00:06:09.470 --> 00:06:09.480 align:start position:0% the data is actually being computed on 00:06:09.480 --> 00:06:11.400 align:start position:0% the data is actually being computed on so<00:06:10.480> it<00:06:10.660> turns<00:06:10.840> out<00:06:10.930> there<00:06:11.080> are<00:06:11.140> a<00:06:11.170> number<00:06:11.290> of 00:06:11.400 --> 00:06:11.410 align:start position:0% so it turns out there are a number of 00:06:11.410 --> 00:06:14.190 align:start position:0% so it turns out there are a number of different<00:06:11.830> technologies<00:06:12.340> for<00:06:13.200> supporting 00:06:14.190 --> 00:06:14.200 align:start position:0% different technologies for supporting 00:06:14.200 --> 00:06:15.930 align:start position:0% different technologies for supporting confidentiality<00:06:14.620> preserving<00:06:15.370> smart 00:06:15.930 --> 00:06:15.940 align:start position:0% confidentiality preserving smart 00:06:15.940 --> 00:06:17.430 align:start position:0% confidentiality preserving smart contracts<00:06:16.330> these<00:06:16.510> range<00:06:16.810> from<00:06:16.960> the<00:06:17.260> use<00:06:17.410> of 00:06:17.430 --> 00:06:17.440 align:start position:0% contracts these range from the use of 00:06:17.440 --> 00:06:19.440 align:start position:0% contracts these range from the use of special<00:06:18.010> hardware<00:06:18.370> to<00:06:18.910> cryptographic 00:06:19.440 --> 00:06:19.450 align:start position:0% special hardware to cryptographic 00:06:19.450 --> 00:06:21.450 align:start position:0% special hardware to cryptographic techniques<00:06:20.200> like<00:06:20.440> secure<00:06:21.220> multi-party 00:06:21.450 --> 00:06:21.460 align:start position:0% techniques like secure multi-party 00:06:21.460 --> 00:06:23.370 align:start position:0% techniques like secure multi-party computation<00:06:22.000> zero<00:06:22.540> knowledge<00:06:22.690> proof<00:06:22.840> s--<00:06:23.110> and 00:06:23.370 --> 00:06:23.380 align:start position:0% computation zero knowledge proof s-- and 00:06:23.380 --> 00:06:25.950 align:start position:0% computation zero knowledge proof s-- and homomorphic<00:06:24.280> encryption<00:06:24.400> so<00:06:25.030> each<00:06:25.690> of<00:06:25.750> this 00:06:25.950 --> 00:06:25.960 align:start position:0% homomorphic encryption so each of this 00:06:25.960 --> 00:06:27.180 align:start position:0% homomorphic encryption so each of this these<00:06:26.290> techniques<00:06:26.710> has<00:06:26.890> different 00:06:27.180 --> 00:06:27.190 align:start position:0% these techniques has different 00:06:27.190 --> 00:06:29.010 align:start position:0% these techniques has different trade-offs<00:06:27.400> in<00:06:27.790> terms<00:06:28.030> of<00:06:28.330> the<00:06:28.600> performance 00:06:29.010 --> 00:06:29.020 align:start position:0% trade-offs in terms of the performance 00:06:29.020 --> 00:06:31.260 align:start position:0% trade-offs in terms of the performance overhead<00:06:29.260> in<00:06:29.620> terms<00:06:29.860> of<00:06:30.340> the<00:06:30.490> class<00:06:30.940> of 00:06:31.260 --> 00:06:31.270 align:start position:0% overhead in terms of the class of 00:06:31.270 --> 00:06:32.880 align:start position:0% overhead in terms of the class of applications<00:06:31.930> that<00:06:31.990> they<00:06:32.170> can<00:06:32.320> support<00:06:32.620> and 00:06:32.880 --> 00:06:32.890 align:start position:0% applications that they can support and 00:06:32.890 --> 00:06:34.860 align:start position:0% applications that they can support and in<00:06:33.340> terms<00:06:33.520> of<00:06:33.730> the<00:06:33.850> security<00:06:34.090> model<00:06:34.450> that<00:06:34.720> is 00:06:34.860 --> 00:06:34.870 align:start position:0% in terms of the security model that is 00:06:34.870 --> 00:06:37.080 align:start position:0% in terms of the security model that is where<00:06:35.380> are<00:06:35.650> the<00:06:35.860> security<00:06:36.310> guarantees<00:06:36.700> coming 00:06:37.080 --> 00:06:37.090 align:start position:0% where are the security guarantees coming 00:06:37.090 --> 00:06:39.750 align:start position:0% where are the security guarantees coming from<00:06:37.270> so<00:06:37.810> there's<00:06:38.020> no<00:06:38.200> single<00:06:38.740> approach<00:06:39.130> that 00:06:39.750 --> 00:06:39.760 align:start position:0% from so there's no single approach that 00:06:39.760 --> 00:06:41.370 align:start position:0% from so there's no single approach that is<00:06:39.880> strictly<00:06:40.270> better<00:06:40.600> than<00:06:40.870> all<00:06:40.960> the<00:06:41.110> others 00:06:41.370 --> 00:06:41.380 align:start position:0% is strictly better than all the others 00:06:41.380 --> 00:06:41.670 align:start position:0% is strictly better than all the others it 00:06:41.670 --> 00:06:41.680 align:start position:0% it 00:06:41.680 --> 00:06:43.469 align:start position:0% it depends<00:06:42.039> on<00:06:42.130> the<00:06:42.280> application<00:06:42.940> and<00:06:43.120> the<00:06:43.240> use 00:06:43.469 --> 00:06:43.479 align:start position:0% depends on the application and the use 00:06:43.479 --> 00:06:46.409 align:start position:0% depends on the application and the use case<00:06:43.720> and<00:06:43.960> so<00:06:44.380> OSS<00:06:44.949> will<00:06:45.280> support<00:06:45.970> all<00:06:46.240> of 00:06:46.409 --> 00:06:46.419 align:start position:0% case and so OSS will support all of 00:06:46.419 --> 00:06:48.210 align:start position:0% case and so OSS will support all of these<00:06:46.570> techniques<00:06:46.990> and<00:06:47.199> allow<00:06:47.440> the<00:06:47.500> developer 00:06:48.210 --> 00:06:48.220 align:start position:0% these techniques and allow the developer 00:06:48.220 --> 00:06:50.360 align:start position:0% these techniques and allow the developer to<00:06:48.340> decide<00:06:48.639> which<00:06:49.270> one<00:06:49.509> they<00:06:49.539> want<00:06:49.900> to<00:06:49.960> use 00:06:50.360 --> 00:06:50.370 align:start position:0% to decide which one they want to use 00:06:50.370 --> 00:06:52.439 align:start position:0% to decide which one they want to use I'll<00:06:51.370> talk<00:06:51.550> briefly<00:06:51.580> about<00:06:51.880> secure<00:06:52.330> hardware 00:06:52.439 --> 00:06:52.449 align:start position:0% I'll talk briefly about secure hardware 00:06:52.449 --> 00:06:53.790 align:start position:0% I'll talk briefly about secure hardware because<00:06:52.690> it's<00:06:52.930> the<00:06:53.020> one<00:06:53.169> that<00:06:53.350> will<00:06:53.470> support 00:06:53.790 --> 00:06:53.800 align:start position:0% because it's the one that will support 00:06:53.800 --> 00:06:55.320 align:start position:0% because it's the one that will support initially<00:06:54.190> and<00:06:54.430> have<00:06:54.550> done<00:06:54.699> the<00:06:54.850> most<00:06:54.940> work<00:06:55.060> on 00:06:55.320 --> 00:06:55.330 align:start position:0% initially and have done the most work on 00:06:55.330 --> 00:06:57.540 align:start position:0% initially and have done the most work on so<00:06:55.570> far<00:06:55.780> so<00:06:56.320> are<00:06:56.830> people<00:06:57.130> familiar<00:06:57.250> with 00:06:57.540 --> 00:06:57.550 align:start position:0% so far so are people familiar with 00:06:57.550 --> 00:06:59.070 align:start position:0% so far so are people familiar with secure<00:06:57.910> Hardware<00:06:58.240> have<00:06:58.449> you<00:06:58.750> heard<00:06:58.930> of 00:06:59.070 --> 00:06:59.080 align:start position:0% secure Hardware have you heard of 00:06:59.080 --> 00:07:01.860 align:start position:0% secure Hardware have you heard of trusted<00:06:59.740> hardware<00:07:00.009> great<00:07:00.669> so<00:07:00.970> for<00:07:01.479> those<00:07:01.600> who 00:07:01.860 --> 00:07:01.870 align:start position:0% trusted hardware great so for those who 00:07:01.870 --> 00:07:03.719 align:start position:0% trusted hardware great so for those who aren't<00:07:02.169> familiar<00:07:02.259> secure<00:07:03.250> hardware<00:07:03.610> is<00:07:03.699> a 00:07:03.719 --> 00:07:03.729 align:start position:0% aren't familiar secure hardware is a 00:07:03.729 --> 00:07:06.270 align:start position:0% aren't familiar secure hardware is a technology<00:07:04.570> that's<00:07:04.960> built<00:07:05.229> into<00:07:05.500> processors 00:07:06.270 --> 00:07:06.280 align:start position:0% technology that's built into processors 00:07:06.280 --> 00:07:08.640 align:start position:0% technology that's built into processors that<00:07:06.520> allows<00:07:07.090> code<00:07:07.539> to<00:07:07.900> construct<00:07:08.410> what's 00:07:08.640 --> 00:07:08.650 align:start position:0% that allows code to construct what's 00:07:08.650 --> 00:07:11.189 align:start position:0% that allows code to construct what's called<00:07:08.860> the<00:07:08.949> secure<00:07:09.250> Enclave<00:07:09.430> and<00:07:09.850> the<00:07:10.840> secure 00:07:11.189 --> 00:07:11.199 align:start position:0% called the secure Enclave and the secure 00:07:11.199 --> 00:07:13.980 align:start position:0% called the secure Enclave and the secure Enclave<00:07:11.410> can<00:07:12.310> run<00:07:12.550> computations<00:07:13.360> and<00:07:13.600> store 00:07:13.980 --> 00:07:13.990 align:start position:0% Enclave can run computations and store 00:07:13.990 --> 00:07:15.659 align:start position:0% Enclave can run computations and store data<00:07:14.020> in<00:07:14.530> a<00:07:14.650> way<00:07:14.800> where<00:07:15.130> it's<00:07:15.250> completely 00:07:15.659 --> 00:07:15.669 align:start position:0% data in a way where it's completely 00:07:15.669 --> 00:07:17.100 align:start position:0% data in a way where it's completely isolated<00:07:15.820> from<00:07:16.479> the<00:07:16.630> rest<00:07:16.660> of<00:07:16.930> the<00:07:16.990> machine 00:07:17.100 --> 00:07:17.110 align:start position:0% isolated from the rest of the machine 00:07:17.110 --> 00:07:19.920 align:start position:0% isolated from the rest of the machine that<00:07:17.470> is<00:07:17.889> to<00:07:18.099> say<00:07:18.280> no<00:07:18.880> other<00:07:19.090> applications<00:07:19.780> on 00:07:19.920 --> 00:07:19.930 align:start position:0% that is to say no other applications on 00:07:19.930 --> 00:07:21.960 align:start position:0% that is to say no other applications on the<00:07:20.020> machine<00:07:20.320> or<00:07:20.560> the<00:07:20.650> operating<00:07:21.340> system<00:07:21.789> or 00:07:21.960 --> 00:07:21.970 align:start position:0% the machine or the operating system or 00:07:21.970 --> 00:07:24.629 align:start position:0% the machine or the operating system or even<00:07:22.419> the<00:07:22.810> user<00:07:23.110> of<00:07:23.440> the<00:07:23.560> machine<00:07:23.860> is<00:07:24.070> actually 00:07:24.629 --> 00:07:24.639 align:start position:0% even the user of the machine is actually 00:07:24.639 --> 00:07:27.120 align:start position:0% even the user of the machine is actually able<00:07:24.849> to<00:07:25.060> view<00:07:25.449> the<00:07:25.599> data<00:07:25.810> or<00:07:26.110> modify<00:07:26.740> the<00:07:26.800> data 00:07:27.120 --> 00:07:27.130 align:start position:0% able to view the data or modify the data 00:07:27.130 --> 00:07:28.830 align:start position:0% able to view the data or modify the data in<00:07:27.370> the<00:07:27.639> secure<00:07:27.910> Enclave<00:07:28.120> and<00:07:28.509> this<00:07:28.720> is 00:07:28.830 --> 00:07:28.840 align:start position:0% in the secure Enclave and this is 00:07:28.840 --> 00:07:31.020 align:start position:0% in the secure Enclave and this is enforced<00:07:29.229> at<00:07:29.349> the<00:07:29.680> hardware<00:07:30.039> level<00:07:30.250> and<00:07:30.550> so 00:07:31.020 --> 00:07:31.030 align:start position:0% enforced at the hardware level and so 00:07:31.030 --> 00:07:32.850 align:start position:0% enforced at the hardware level and so what<00:07:31.150> this<00:07:31.270> means<00:07:31.330> is<00:07:31.780> secure<00:07:32.470> enclaves 00:07:32.850 --> 00:07:32.860 align:start position:0% what this means is secure enclaves 00:07:32.860 --> 00:07:35.100 align:start position:0% what this means is secure enclaves provide<00:07:33.280> both<00:07:33.520> integrity<00:07:34.150> that<00:07:34.599> is<00:07:34.780> we<00:07:34.960> have 00:07:35.100 --> 00:07:35.110 align:start position:0% provide both integrity that is we have 00:07:35.110 --> 00:07:36.900 align:start position:0% provide both integrity that is we have assurances<00:07:35.560> that<00:07:35.620> the<00:07:35.979> computation<00:07:36.610> result 00:07:36.900 --> 00:07:36.910 align:start position:0% assurances that the computation result 00:07:36.910 --> 00:07:38.450 align:start position:0% assurances that the computation result hasn't<00:07:37.240> been<00:07:37.389> tampered<00:07:37.599> with<00:07:37.780> and 00:07:38.450 --> 00:07:38.460 align:start position:0% hasn't been tampered with and 00:07:38.460 --> 00:07:40.980 align:start position:0% hasn't been tampered with and confidentiality<00:07:39.460> that<00:07:39.970> is<00:07:40.150> we<00:07:40.419> know<00:07:40.599> that<00:07:40.630> no 00:07:40.980 --> 00:07:40.990 align:start position:0% confidentiality that is we know that no 00:07:40.990 --> 00:07:42.749 align:start position:0% confidentiality that is we know that no one<00:07:41.139> can<00:07:41.289> actually<00:07:41.440> view<00:07:41.949> the<00:07:42.070> data<00:07:42.280> as<00:07:42.460> long 00:07:42.749 --> 00:07:42.759 align:start position:0% one can actually view the data as long 00:07:42.759 --> 00:07:44.909 align:start position:0% one can actually view the data as long as<00:07:43.180> we<00:07:43.300> construct<00:07:43.750> this<00:07:43.900> unclaimed<00:07:44.380> carefully 00:07:44.909 --> 00:07:44.919 align:start position:0% as we construct this unclaimed carefully 00:07:44.919 --> 00:07:46.950 align:start position:0% as we construct this unclaimed carefully the<00:07:45.729> other<00:07:45.880> thing<00:07:46.120> that<00:07:46.150> secure<00:07:46.659> Hardware 00:07:46.950 --> 00:07:46.960 align:start position:0% the other thing that secure Hardware 00:07:46.960 --> 00:07:48.779 align:start position:0% the other thing that secure Hardware provides<00:07:47.289> is<00:07:47.560> the<00:07:47.860> ability<00:07:48.099> to<00:07:48.280> generate<00:07:48.580> a 00:07:48.779 --> 00:07:48.789 align:start position:0% provides is the ability to generate a 00:07:48.789 --> 00:07:51.510 align:start position:0% provides is the ability to generate a certificate<00:07:49.120> that<00:07:49.570> can<00:07:49.780> prove<00:07:50.110> to<00:07:50.889> a<00:07:51.159> remote 00:07:51.510 --> 00:07:51.520 align:start position:0% certificate that can prove to a remote 00:07:51.520 --> 00:07:53.339 align:start position:0% certificate that can prove to a remote party<00:07:51.880> that<00:07:52.060> doesn't<00:07:52.270> have<00:07:52.539> physical<00:07:53.020> access 00:07:53.339 --> 00:07:53.349 align:start position:0% party that doesn't have physical access 00:07:53.349 --> 00:07:56.040 align:start position:0% party that doesn't have physical access to<00:07:53.409> the<00:07:53.560> machine<00:07:53.830> that<00:07:54.210> the<00:07:55.210> code<00:07:55.479> is<00:07:55.510> running 00:07:56.040 --> 00:07:56.050 align:start position:0% to the machine that the code is running 00:07:56.050 --> 00:07:57.870 align:start position:0% to the machine that the code is running on<00:07:56.199> correct<00:07:56.710> hardware<00:07:56.889> and<00:07:57.280> that<00:07:57.340> the 00:07:57.870 --> 00:07:57.880 align:start position:0% on correct hardware and that the 00:07:57.880 --> 00:08:02.210 align:start position:0% on correct hardware and that the contents<00:07:58.449> of<00:07:58.539> the<00:07:58.750> Enclave<00:07:59.199> are<00:07:59.560> correct<00:08:00.479> so 00:08:02.210 --> 00:08:02.220 align:start position:0% contents of the Enclave are correct so 00:08:02.220 --> 00:08:04.950 align:start position:0% contents of the Enclave are correct so in<00:08:03.220> our<00:08:03.340> previous<00:08:03.580> work<00:08:04.060> we<00:08:04.419> publish<00:08:04.870> an 00:08:04.950 --> 00:08:04.960 align:start position:0% in our previous work we publish an 00:08:04.960 --> 00:08:06.540 align:start position:0% in our previous work we publish an academic<00:08:05.380> paper<00:08:05.500> that<00:08:05.830> shows<00:08:06.039> how<00:08:06.310> to<00:08:06.340> use 00:08:06.540 --> 00:08:06.550 align:start position:0% academic paper that shows how to use 00:08:06.550 --> 00:08:10.020 align:start position:0% academic paper that shows how to use secure<00:08:07.060> hardware<00:08:07.539> to<00:08:08.260> run<00:08:08.710> smart<00:08:09.610> contracts 00:08:10.020 --> 00:08:10.030 align:start position:0% secure hardware to run smart contracts 00:08:10.030 --> 00:08:11.730 align:start position:0% secure hardware to run smart contracts in<00:08:10.210> an<00:08:10.330> enclave<00:08:10.690> to<00:08:11.020> provide<00:08:11.349> end-to-end 00:08:11.730 --> 00:08:11.740 align:start position:0% in an enclave to provide end-to-end 00:08:11.740 --> 00:08:13.980 align:start position:0% in an enclave to provide end-to-end privacy<00:08:12.400> that<00:08:13.030> papers<00:08:13.360> called<00:08:13.599> akedan 00:08:13.980 --> 00:08:13.990 align:start position:0% privacy that papers called akedan 00:08:13.990 --> 00:08:15.270 align:start position:0% privacy that papers called akedan there's<00:08:14.169> a<00:08:14.199> lot<00:08:14.320> of<00:08:14.409> interesting<00:08:14.740> details<00:08:15.099> to 00:08:15.270 --> 00:08:15.280 align:start position:0% there's a lot of interesting details to 00:08:15.280 --> 00:08:16.860 align:start position:0% there's a lot of interesting details to get<00:08:15.400> this<00:08:15.520> to<00:08:15.699> work<00:08:15.820> I<00:08:16.030> encourage<00:08:16.630> you<00:08:16.750> to 00:08:16.860 --> 00:08:16.870 align:start position:0% get this to work I encourage you to 00:08:16.870 --> 00:08:19.499 align:start position:0% get this to work I encourage you to check<00:08:17.289> out<00:08:17.440> the<00:08:17.530> paper<00:08:17.759> we're<00:08:18.759> also<00:08:19.030> working 00:08:19.499 --> 00:08:19.509 align:start position:0% check out the paper we're also working 00:08:19.509 --> 00:08:22.230 align:start position:0% check out the paper we're also working with<00:08:19.960> the<00:08:20.349> Keystone<00:08:20.800> project<00:08:20.979> on<00:08:21.460> a<00:08:21.880> fully 00:08:22.230 --> 00:08:22.240 align:start position:0% with the Keystone project on a fully 00:08:22.240 --> 00:08:24.839 align:start position:0% with the Keystone project on a fully open<00:08:22.570> source<00:08:23.110> design<00:08:23.470> for<00:08:24.220> secure<00:08:24.669> hardware 00:08:24.839 --> 00:08:24.849 align:start position:0% open source design for secure hardware 00:08:24.849 --> 00:08:26.930 align:start position:0% open source design for secure hardware so<00:08:25.599> this<00:08:25.810> is<00:08:25.930> based<00:08:26.110> on<00:08:26.259> the<00:08:26.409> risk<00:08:26.620> 5 00:08:26.930 --> 00:08:26.940 align:start position:0% so this is based on the risk 5 00:08:26.940 --> 00:08:28.529 align:start position:0% so this is based on the risk 5 microarchitecture<00:08:27.940> and<00:08:27.970> this<00:08:28.300> will<00:08:28.419> be<00:08:28.509> a 00:08:28.529 --> 00:08:28.539 align:start position:0% microarchitecture and this will be a 00:08:28.539 --> 00:08:30.839 align:start position:0% microarchitecture and this will be a design<00:08:28.900> that<00:08:29.110> anyone<00:08:29.470> can<00:08:29.590> audit<00:08:29.860> anyone<00:08:30.669> can 00:08:30.839 --> 00:08:30.849 align:start position:0% design that anyone can audit anyone can 00:08:30.849 --> 00:08:32.310 align:start position:0% design that anyone can audit anyone can verify<00:08:31.060> and<00:08:31.270> any<00:08:31.570> chip<00:08:31.870> maker<00:08:32.079> can 00:08:32.310 --> 00:08:32.320 align:start position:0% verify and any chip maker can 00:08:32.320 --> 00:08:34.290 align:start position:0% verify and any chip maker can manufacture<00:08:32.620> so<00:08:33.370> in<00:08:33.550> the<00:08:33.669> meantime<00:08:33.849> we're 00:08:34.290 --> 00:08:34.300 align:start position:0% manufacture so in the meantime we're 00:08:34.300 --> 00:08:36.120 align:start position:0% manufacture so in the meantime we're using<00:08:34.479> the<00:08:34.870> trusted<00:08:35.169> Hardware<00:08:35.589> technology 00:08:36.120 --> 00:08:36.130 align:start position:0% using the trusted Hardware technology 00:08:36.130 --> 00:08:38.040 align:start position:0% using the trusted Hardware technology that's<00:08:36.310> available<00:08:36.400> today<00:08:36.880> including<00:08:37.810> Intel 00:08:38.040 --> 00:08:38.050 align:start position:0% that's available today including Intel 00:08:38.050 --> 00:08:40.440 align:start position:0% that's available today including Intel SGX<00:08:38.229> but<00:08:38.979> in<00:08:39.099> the<00:08:39.190> future<00:08:39.399> as<00:08:39.550> new 00:08:40.440 --> 00:08:40.450 align:start position:0% SGX but in the future as new 00:08:40.450 --> 00:08:42.449 align:start position:0% SGX but in the future as new technologies<00:08:41.140> become<00:08:41.440> available<00:08:41.469> they'll<00:08:42.310> be 00:08:42.449 --> 00:08:42.459 align:start position:0% technologies become available they'll be 00:08:42.459 --> 00:08:44.550 align:start position:0% technologies become available they'll be exposed<00:08:42.820> to<00:08:43.149> developers<00:08:43.690> through<00:08:43.959> the<00:08:44.169> Oasis 00:08:44.550 --> 00:08:44.560 align:start position:0% exposed to developers through the Oasis 00:08:44.560 --> 00:08:47.280 align:start position:0% exposed to developers through the Oasis platform<00:08:45.300> tomorrow<00:08:46.300> morning<00:08:46.630> at<00:08:46.810> 10:00<00:08:47.200> a.m. 00:08:47.280 --> 00:08:47.290 align:start position:0% platform tomorrow morning at 10:00 a.m. 00:08:47.290 --> 00:08:49.620 align:start position:0% platform tomorrow morning at 10:00 a.m. there's<00:08:47.770> a<00:08:47.829> workshop<00:08:48.310> with<00:08:48.550> with<00:08:49.029> Intel<00:08:49.420> and<00:08:49.600> a 00:08:49.620 --> 00:08:49.630 align:start position:0% there's a workshop with with Intel and a 00:08:49.630 --> 00:08:50.670 align:start position:0% there's a workshop with with Intel and a few<00:08:49.750> other<00:08:49.959> companies<00:08:50.380> that<00:08:50.529> are<00:08:50.650> using 00:08:50.670 --> 00:08:50.680 align:start position:0% few other companies that are using 00:08:50.680 --> 00:08:52.740 align:start position:0% few other companies that are using secure<00:08:51.640> hardware<00:08:51.790> so<00:08:52.120> if<00:08:52.209> you're<00:08:52.329> interested 00:08:52.740 --> 00:08:52.750 align:start position:0% secure hardware so if you're interested 00:08:52.750 --> 00:08:54.510 align:start position:0% secure hardware so if you're interested in<00:08:52.839> this<00:08:52.930> subject<00:08:53.110> I<00:08:53.829> encourage<00:08:54.339> you<00:08:54.400> to<00:08:54.430> check 00:08:54.510 --> 00:08:54.520 align:start position:0% in this subject I encourage you to check 00:08:54.520 --> 00:08:55.940 align:start position:0% in this subject I encourage you to check out<00:08:54.730> that<00:08:54.880> workshop 00:08:55.940 --> 00:08:55.950 align:start position:0% out that workshop 00:08:55.950 --> 00:08:58.350 align:start position:0% out that workshop okay<00:08:56.950> so<00:08:57.010> how<00:08:57.400> do<00:08:57.460> you<00:08:57.610> actually<00:08:57.760> use<00:08:58.000> this 00:08:58.350 --> 00:08:58.360 align:start position:0% okay so how do you actually use this 00:08:58.360 --> 00:09:00.690 align:start position:0% okay so how do you actually use this feature<00:08:58.570> so<00:08:58.900> suppose<00:08:59.890> we<00:08:59.920> want<00:09:00.160> to<00:09:00.430> have<00:09:00.550> an 00:09:00.690 --> 00:09:00.700 align:start position:0% feature so suppose we want to have an 00:09:00.700 --> 00:09:02.760 align:start position:0% feature so suppose we want to have an election<00:09:01.000> through<00:09:01.390> a<00:09:01.420> smart<00:09:01.720> contract<00:09:01.870> so<00:09:02.470> I'm 00:09:02.760 --> 00:09:02.770 align:start position:0% election through a smart contract so I'm 00:09:02.770 --> 00:09:04.800 align:start position:0% election through a smart contract so I'm gonna<00:09:02.950> implement<00:09:03.310> a<00:09:03.520> ballot<00:09:03.880> as<00:09:04.390> a<00:09:04.450> smart 00:09:04.800 --> 00:09:04.810 align:start position:0% gonna implement a ballot as a smart 00:09:04.810 --> 00:09:07.530 align:start position:0% gonna implement a ballot as a smart contract<00:09:04.990> and<00:09:05.790> typically<00:09:06.790> today<00:09:07.060> if<00:09:07.330> you<00:09:07.450> want 00:09:07.530 --> 00:09:07.540 align:start position:0% contract and typically today if you want 00:09:07.540 --> 00:09:09.300 align:start position:0% contract and typically today if you want to<00:09:07.690> interact<00:09:07.960> with<00:09:08.320> a<00:09:08.350> smart<00:09:08.650> contract<00:09:09.100> right 00:09:09.300 --> 00:09:09.310 align:start position:0% to interact with a smart contract right 00:09:09.310 --> 00:09:11.880 align:start position:0% to interact with a smart contract right you<00:09:09.430> would<00:09:09.550> have<00:09:09.670> a<00:09:09.700> DAP<00:09:10.030> that<00:09:10.500> includes<00:09:11.500> a<00:09:11.680> web 00:09:11.880 --> 00:09:11.890 align:start position:0% you would have a DAP that includes a web 00:09:11.890 --> 00:09:14.130 align:start position:0% you would have a DAP that includes a web 3<00:09:12.160> library<00:09:12.790> and<00:09:12.970> the<00:09:13.060> DAP<00:09:13.240> would<00:09:13.510> call<00:09:13.720> into 00:09:14.130 --> 00:09:14.140 align:start position:0% 3 library and the DAP would call into 00:09:14.140 --> 00:09:15.960 align:start position:0% 3 library and the DAP would call into web<00:09:14.620> 3<00:09:14.890> that<00:09:15.100> library<00:09:15.610> would<00:09:15.760> issue 00:09:15.960 --> 00:09:15.970 align:start position:0% web 3 that library would issue 00:09:15.970 --> 00:09:19.500 align:start position:0% web 3 that library would issue transactions<00:09:16.840> to<00:09:17.350> a<00:09:17.380> web<00:09:17.920> 3<00:09:18.250> gateway<00:09:18.790> like<00:09:19.300> in 00:09:19.500 --> 00:09:19.510 align:start position:0% transactions to a web 3 gateway like in 00:09:19.510 --> 00:09:21.420 align:start position:0% transactions to a web 3 gateway like in Fuhrer<00:09:19.780> and<00:09:20.050> those<00:09:20.380> transactions<00:09:21.040> would<00:09:21.250> be 00:09:21.420 --> 00:09:21.430 align:start position:0% Fuhrer and those transactions would be 00:09:21.430 --> 00:09:23.160 align:start position:0% Fuhrer and those transactions would be relayed<00:09:22.180> to<00:09:22.210> the<00:09:22.480> workers<00:09:22.810> that<00:09:22.840> would 00:09:23.160 --> 00:09:23.170 align:start position:0% relayed to the workers that would 00:09:23.170 --> 00:09:24.840 align:start position:0% relayed to the workers that would execute<00:09:23.740> the<00:09:23.860> transactions<00:09:24.430> and<00:09:24.610> of<00:09:24.670> course 00:09:24.840 --> 00:09:24.850 align:start position:0% execute the transactions and of course 00:09:24.850 --> 00:09:26.670 align:start position:0% execute the transactions and of course in<00:09:24.970> this<00:09:25.090> model<00:09:25.420> all<00:09:25.660> of<00:09:25.870> the<00:09:26.170> transaction 00:09:26.670 --> 00:09:26.680 align:start position:0% in this model all of the transaction 00:09:26.680 --> 00:09:29.820 align:start position:0% in this model all of the transaction data<00:09:26.860> and<00:09:27.160> the<00:09:27.550> state<00:09:27.760> are<00:09:27.970> public<00:09:28.390> now<00:09:28.900> this 00:09:29.820 --> 00:09:29.830 align:start position:0% data and the state are public now this 00:09:29.830 --> 00:09:31.890 align:start position:0% data and the state are public now this is<00:09:29.980> a<00:09:30.010> great<00:09:30.250> design<00:09:30.400> but<00:09:30.970> it's<00:09:31.420> designed 00:09:31.890 --> 00:09:31.900 align:start position:0% is a great design but it's designed 00:09:31.900 --> 00:09:33.870 align:start position:0% is a great design but it's designed specifically<00:09:32.620> under<00:09:32.980> the<00:09:33.100> model<00:09:33.430> where<00:09:33.640> all 00:09:33.870 --> 00:09:33.880 align:start position:0% specifically under the model where all 00:09:33.880 --> 00:09:36.960 align:start position:0% specifically under the model where all of<00:09:34.120> this<00:09:34.240> transaction<00:09:34.600> data<00:09:34.990> is<00:09:35.200> public<00:09:35.740> so<00:09:36.370> if 00:09:36.960 --> 00:09:36.970 align:start position:0% of this transaction data is public so if 00:09:36.970 --> 00:09:39.840 align:start position:0% of this transaction data is public so if we<00:09:37.660> want<00:09:37.930> to<00:09:38.290> support<00:09:38.890> the<00:09:39.040> ability<00:09:39.400> to<00:09:39.430> keep 00:09:39.840 --> 00:09:39.850 align:start position:0% we want to support the ability to keep 00:09:39.850 --> 00:09:42.630 align:start position:0% we want to support the ability to keep state<00:09:40.510> and<00:09:40.780> data<00:09:41.110> secret<00:09:41.650> we<00:09:42.130> need<00:09:42.310> to<00:09:42.490> make 00:09:42.630 --> 00:09:42.640 align:start position:0% state and data secret we need to make 00:09:42.640 --> 00:09:45.060 align:start position:0% state and data secret we need to make extensions<00:09:43.330> to<00:09:43.690> this<00:09:43.900> web<00:09:44.140> 3<00:09:44.410> interface<00:09:44.650> and 00:09:45.060 --> 00:09:45.070 align:start position:0% extensions to this web 3 interface and 00:09:45.070 --> 00:09:47.310 align:start position:0% extensions to this web 3 interface and that's<00:09:45.520> exactly<00:09:45.880> what<00:09:46.240> we've<00:09:46.360> done<00:09:46.540> so<00:09:46.870> we 00:09:47.310 --> 00:09:47.320 align:start position:0% that's exactly what we've done so we 00:09:47.320 --> 00:09:48.870 align:start position:0% that's exactly what we've done so we have<00:09:47.470> an<00:09:47.590> extension<00:09:47.920> to<00:09:48.130> web<00:09:48.280> 3<00:09:48.580> called 00:09:48.870 --> 00:09:48.880 align:start position:0% have an extension to web 3 called 00:09:48.880 --> 00:09:51.450 align:start position:0% have an extension to web 3 called confidential<00:09:49.600> web<00:09:49.900> 3<00:09:50.230> and<00:09:50.440> what<00:09:50.800> this<00:09:50.950> does<00:09:51.160> is 00:09:51.450 --> 00:09:51.460 align:start position:0% confidential web 3 and what this does is 00:09:51.460 --> 00:09:54.960 align:start position:0% confidential web 3 and what this does is allow<00:09:51.790> callers<00:09:52.740> locally<00:09:53.740> to<00:09:54.340> construct<00:09:54.850> a 00:09:54.960 --> 00:09:54.970 align:start position:0% allow callers locally to construct a 00:09:54.970 --> 00:09:57.390 align:start position:0% allow callers locally to construct a secure<00:09:55.360> channel<00:09:55.840> to<00:09:56.020> the<00:09:56.140> contract<00:09:56.620> and<00:09:56.830> then 00:09:57.390 --> 00:09:57.400 align:start position:0% secure channel to the contract and then 00:09:57.400 --> 00:09:59.280 align:start position:0% secure channel to the contract and then send<00:09:57.790> transactions<00:09:58.510> to<00:09:58.600> the<00:09:58.720> contract<00:09:59.170> in 00:09:59.280 --> 00:09:59.290 align:start position:0% send transactions to the contract in 00:09:59.290 --> 00:10:01.140 align:start position:0% send transactions to the contract in such<00:09:59.470> a<00:09:59.500> way<00:09:59.740> where<00:09:59.980> the<00:10:00.430> contents<00:10:00.970> of<00:10:01.060> the 00:10:01.140 --> 00:10:01.150 align:start position:0% such a way where the contents of the 00:10:01.150 --> 00:10:03.360 align:start position:0% such a way where the contents of the transaction<00:10:01.720> are<00:10:01.810> encrypted<00:10:02.230> so<00:10:02.410> only<00:10:02.950> the 00:10:03.360 --> 00:10:03.370 align:start position:0% transaction are encrypted so only the 00:10:03.370 --> 00:10:05.010 align:start position:0% transaction are encrypted so only the smart<00:10:03.640> contract<00:10:03.790> can<00:10:04.210> actually<00:10:04.480> decrypt<00:10:04.810> them 00:10:05.010 --> 00:10:05.020 align:start position:0% smart contract can actually decrypt them 00:10:05.020 --> 00:10:07.020 align:start position:0% smart contract can actually decrypt them and<00:10:05.230> view<00:10:05.440> them<00:10:05.620> so<00:10:06.160> essentially<00:10:06.610> we<00:10:06.760> have<00:10:06.790> an 00:10:07.020 --> 00:10:07.030 align:start position:0% and view them so essentially we have an 00:10:07.030 --> 00:10:08.850 align:start position:0% and view them so essentially we have an end-to-end<00:10:07.330> encrypted<00:10:07.840> channel<00:10:08.290> to<00:10:08.710> the 00:10:08.850 --> 00:10:08.860 align:start position:0% end-to-end encrypted channel to the 00:10:08.860 --> 00:10:11.040 align:start position:0% end-to-end encrypted channel to the smart<00:10:09.100> contracts<00:10:09.580> so<00:10:09.730> no<00:10:10.000> other<00:10:10.270> machines<00:10:10.750> on 00:10:11.040 --> 00:10:11.050 align:start position:0% smart contracts so no other machines on 00:10:11.050 --> 00:10:14.040 align:start position:0% smart contracts so no other machines on the<00:10:11.230> network<00:10:11.340> not<00:10:12.340> the<00:10:12.670> Gateway<00:10:13.180> not<00:10:13.750> the<00:10:13.900> web 00:10:14.040 --> 00:10:14.050 align:start position:0% the network not the Gateway not the web 00:10:14.050 --> 00:10:16.680 align:start position:0% the network not the Gateway not the web 3<00:10:14.290> provider<00:10:14.650> not<00:10:15.370> even<00:10:15.700> the<00:10:15.790> workers<00:10:16.000> are 00:10:16.680 --> 00:10:16.690 align:start position:0% 3 provider not even the workers are 00:10:16.690 --> 00:10:18.570 align:start position:0% 3 provider not even the workers are actually<00:10:17.110> able<00:10:17.230> to<00:10:17.410> see<00:10:17.710> the<00:10:17.920> contents<00:10:18.430> and 00:10:18.570 --> 00:10:18.580 align:start position:0% actually able to see the contents and 00:10:18.580 --> 00:10:20.340 align:start position:0% actually able to see the contents and the<00:10:18.790> payloads<00:10:19.210> of<00:10:19.360> these<00:10:19.480> transactions<00:10:20.140> and 00:10:20.340 --> 00:10:20.350 align:start position:0% the payloads of these transactions and 00:10:20.350 --> 00:10:22.110 align:start position:0% the payloads of these transactions and of<00:10:20.740> course<00:10:20.920> the<00:10:21.070> smart<00:10:21.310> contract<00:10:21.460> state<00:10:21.940> is 00:10:22.110 --> 00:10:22.120 align:start position:0% of course the smart contract state is 00:10:22.120 --> 00:10:23.700 align:start position:0% of course the smart contract state is encrypted<00:10:22.690> with<00:10:22.840> a<00:10:22.960> different<00:10:23.320> key<00:10:23.470> that's 00:10:23.700 --> 00:10:23.710 align:start position:0% encrypted with a different key that's 00:10:23.710 --> 00:10:25.830 align:start position:0% encrypted with a different key that's known<00:10:23.860> only<00:10:24.130> to<00:10:24.400> the<00:10:24.760> smart<00:10:24.970> contract<00:10:25.120> so<00:10:25.810> that 00:10:25.830 --> 00:10:25.840 align:start position:0% known only to the smart contract so that 00:10:25.840 --> 00:10:28.050 align:start position:0% known only to the smart contract so that users<00:10:26.410> can't<00:10:26.770> decrypt<00:10:27.040> the<00:10:27.250> state<00:10:27.490> but<00:10:27.940> they 00:10:28.050 --> 00:10:28.060 align:start position:0% users can't decrypt the state but they 00:10:28.060 --> 00:10:29.550 align:start position:0% users can't decrypt the state but they can<00:10:28.210> decrypt<00:10:28.480> for<00:10:28.690> example<00:10:28.990> the<00:10:29.050> responses 00:10:29.550 --> 00:10:29.560 align:start position:0% can decrypt for example the responses 00:10:29.560 --> 00:10:31.980 align:start position:0% can decrypt for example the responses from<00:10:29.710> the<00:10:29.920> smart<00:10:30.130> contract<00:10:30.280> so<00:10:31.000> the<00:10:31.630> the 00:10:31.980 --> 00:10:31.990 align:start position:0% from the smart contract so the the 00:10:31.990 --> 00:10:33.600 align:start position:0% from the smart contract so the the library<00:10:32.200> that<00:10:32.620> we're<00:10:32.740> releasing<00:10:33.040> is<00:10:33.400> going<00:10:33.550> to 00:10:33.600 --> 00:10:33.610 align:start position:0% library that we're releasing is going to 00:10:33.610 --> 00:10:35.130 align:start position:0% library that we're releasing is going to be<00:10:33.700> available<00:10:33.910> as<00:10:34.240> a<00:10:34.300> JavaScript<00:10:34.630> library 00:10:35.130 --> 00:10:35.140 align:start position:0% be available as a JavaScript library 00:10:35.140 --> 00:10:36.630 align:start position:0% be available as a JavaScript library that<00:10:35.170> you<00:10:35.410> can<00:10:35.440> integrate<00:10:35.800> in<00:10:36.130> your<00:10:36.160> DAPs 00:10:36.630 --> 00:10:36.640 align:start position:0% that you can integrate in your DAPs 00:10:36.640 --> 00:10:38.880 align:start position:0% that you can integrate in your DAPs and<00:10:37.480> the<00:10:37.720> library<00:10:38.140> handles<00:10:38.530> all<00:10:38.650> of<00:10:38.770> these 00:10:38.880 --> 00:10:38.890 align:start position:0% and the library handles all of these 00:10:38.890 --> 00:10:40.830 align:start position:0% and the library handles all of these details<00:10:39.250> under<00:10:39.610> the<00:10:39.640> hood<00:10:39.880> establishing<00:10:40.720> this 00:10:40.830 --> 00:10:40.840 align:start position:0% details under the hood establishing this 00:10:40.840 --> 00:10:42.960 align:start position:0% details under the hood establishing this channel<00:10:41.260> and<00:10:41.610> generating<00:10:42.610> secure 00:10:42.960 --> 00:10:42.970 align:start position:0% channel and generating secure 00:10:42.970 --> 00:10:45.420 align:start position:0% channel and generating secure transactions<00:10:43.600> so<00:10:44.020> that<00:10:44.200> the<00:10:44.620> interface<00:10:45.100> for 00:10:45.420 --> 00:10:45.430 align:start position:0% transactions so that the interface for 00:10:45.430 --> 00:10:46.890 align:start position:0% transactions so that the interface for calling<00:10:45.820> in<00:10:45.940> to<00:10:46.090> confidential<00:10:46.660> smart 00:10:46.890 --> 00:10:46.900 align:start position:0% calling in to confidential smart 00:10:46.900 --> 00:10:48.360 align:start position:0% calling in to confidential smart contracts<00:10:47.290> is<00:10:47.380> very<00:10:47.590> similar<00:10:47.980> to<00:10:48.100> what<00:10:48.250> you're 00:10:48.360 --> 00:10:48.370 align:start position:0% contracts is very similar to what you're 00:10:48.370 --> 00:10:51.360 align:start position:0% contracts is very similar to what you're used<00:10:48.430> to<00:10:48.670> today<00:10:48.820> that<00:10:49.210> is<00:10:49.560> your<00:10:50.560> code<00:10:50.890> requires 00:10:51.360 --> 00:10:51.370 align:start position:0% used to today that is your code requires 00:10:51.370 --> 00:10:53.370 align:start position:0% used to today that is your code requires only<00:10:51.640> very<00:10:51.820> minimal<00:10:52.210> changes<00:10:52.660> in<00:10:52.870> order<00:10:53.290> to 00:10:53.370 --> 00:10:53.380 align:start position:0% only very minimal changes in order to 00:10:53.380 --> 00:10:55.740 align:start position:0% only very minimal changes in order to use<00:10:53.650> the<00:10:53.800> confidential<00:10:54.310> version<00:10:54.700> versus<00:10:55.420> the 00:10:55.740 --> 00:10:55.750 align:start position:0% use the confidential version versus the 00:10:55.750 --> 00:11:00.000 align:start position:0% use the confidential version versus the existing<00:10:56.140> version<00:10:57.480> so<00:10:58.480> I<00:10:58.780> just<00:10:59.230> described<00:10:59.650> how 00:11:00.000 --> 00:11:00.010 align:start position:0% existing version so I just described how 00:11:00.010 --> 00:11:02.640 align:start position:0% existing version so I just described how os's<00:11:00.910> can<00:11:01.240> protect<00:11:01.570> data<00:11:01.780> at<00:11:02.080> the<00:11:02.230> platform 00:11:02.640 --> 00:11:02.650 align:start position:0% os's can protect data at the platform 00:11:02.650 --> 00:11:05.430 align:start position:0% os's can protect data at the platform layer<00:11:02.830> from<00:11:03.220> nodes<00:11:03.940> and<00:11:04.240> workers<00:11:04.780> on<00:11:05.020> the 00:11:05.430 --> 00:11:05.440 align:start position:0% layer from nodes and workers on the 00:11:05.440 --> 00:11:06.569 align:start position:0% layer from nodes and workers on the network 00:11:06.569 --> 00:11:06.579 align:start position:0% network 00:11:06.579 --> 00:11:08.340 align:start position:0% network this<00:11:06.699> is<00:11:06.910> essential<00:11:07.779> of<00:11:07.869> course<00:11:08.079> for 00:11:08.340 --> 00:11:08.350 align:start position:0% this is essential of course for 00:11:08.350 --> 00:11:10.889 align:start position:0% this is essential of course for protecting<00:11:08.769> privacy<00:11:09.129> and<00:11:09.899> supporting 00:11:10.889 --> 00:11:10.899 align:start position:0% protecting privacy and supporting 00:11:10.899 --> 00:11:12.809 align:start position:0% protecting privacy and supporting applications<00:11:11.079> that<00:11:11.799> need<00:11:11.980> to<00:11:12.129> protect<00:11:12.459> data 00:11:12.809 --> 00:11:12.819 align:start position:0% applications that need to protect data 00:11:12.819 --> 00:11:15.239 align:start position:0% applications that need to protect data but<00:11:13.509> it's<00:11:13.749> actually<00:11:14.110> not<00:11:14.139> enough<00:11:14.769> for<00:11:15.009> certain 00:11:15.239 --> 00:11:15.249 align:start position:0% but it's actually not enough for certain 00:11:15.249 --> 00:11:18.689 align:start position:0% but it's actually not enough for certain applications<00:11:15.929> and<00:11:16.929> in<00:11:17.559> certain<00:11:18.160> cases<00:11:18.399> you 00:11:18.689 --> 00:11:18.699 align:start position:0% applications and in certain cases you 00:11:18.699 --> 00:11:19.889 align:start position:0% applications and in certain cases you actually<00:11:18.730> need<00:11:19.119> to<00:11:19.209> do<00:11:19.329> something<00:11:19.660> at<00:11:19.779> the 00:11:19.889 --> 00:11:19.899 align:start position:0% actually need to do something at the 00:11:19.899 --> 00:11:23.220 align:start position:0% actually need to do something at the application<00:11:20.589> level<00:11:20.769> as<00:11:21.069> well<00:11:21.309> and<00:11:21.610> so<00:11:22.420> to 00:11:23.220 --> 00:11:23.230 align:start position:0% application level as well and so to 00:11:23.230 --> 00:11:25.949 align:start position:0% application level as well and so to motivate<00:11:23.619> this<00:11:23.769> let's<00:11:24.360> ignore<00:11:25.360> blockchain 00:11:25.949 --> 00:11:25.959 align:start position:0% motivate this let's ignore blockchain 00:11:25.959 --> 00:11:27.419 align:start position:0% motivate this let's ignore blockchain for<00:11:26.139> a<00:11:26.170> second<00:11:26.529> let's<00:11:26.709> just<00:11:26.920> talk<00:11:27.040> about<00:11:27.069> the 00:11:27.419 --> 00:11:27.429 align:start position:0% for a second let's just talk about the 00:11:27.429 --> 00:11:30.090 align:start position:0% for a second let's just talk about the general<00:11:27.850> problem<00:11:28.389> of<00:11:28.709> there's<00:11:29.709> some<00:11:29.920> data 00:11:30.090 --> 00:11:30.100 align:start position:0% general problem of there's some data 00:11:30.100 --> 00:11:32.220 align:start position:0% general problem of there's some data scientist<00:11:30.759> that<00:11:30.910> wants<00:11:31.239> to<00:11:31.269> do<00:11:32.199> something 00:11:32.220 --> 00:11:32.230 align:start position:0% scientist that wants to do something 00:11:32.230 --> 00:11:33.869 align:start position:0% scientist that wants to do something useful<00:11:32.739> on<00:11:33.100> sensitive<00:11:33.489> data 00:11:33.869 --> 00:11:33.879 align:start position:0% useful on sensitive data 00:11:33.879 --> 00:11:34.979 align:start position:0% useful on sensitive data maybe<00:11:34.089> it's<00:11:34.299> train<00:11:34.569> and<00:11:34.720> machine<00:11:34.959> learning 00:11:34.979 --> 00:11:34.989 align:start position:0% maybe it's train and machine learning 00:11:34.989 --> 00:11:37.379 align:start position:0% maybe it's train and machine learning model<00:11:35.559> so<00:11:35.920> they<00:11:36.069> would<00:11:36.279> write<00:11:36.759> some<00:11:36.970> code<00:11:37.149> that 00:11:37.379 --> 00:11:37.389 align:start position:0% model so they would write some code that 00:11:37.389 --> 00:11:39.449 align:start position:0% model so they would write some code that trains<00:11:37.629> the<00:11:37.779> model<00:11:38.110> that<00:11:38.649> code<00:11:38.949> inputs 00:11:39.449 --> 00:11:39.459 align:start position:0% trains the model that code inputs 00:11:39.459 --> 00:11:41.609 align:start position:0% trains the model that code inputs sensitive<00:11:39.970> training<00:11:40.269> data<00:11:40.480> and<00:11:40.600> and<00:11:41.139> outputs 00:11:41.609 --> 00:11:41.619 align:start position:0% sensitive training data and and outputs 00:11:41.619 --> 00:11:43.979 align:start position:0% sensitive training data and and outputs the<00:11:41.769> model<00:11:42.069> now<00:11:42.999> even<00:11:43.389> if<00:11:43.480> we<00:11:43.600> don't<00:11:43.749> release 00:11:43.979 --> 00:11:43.989 align:start position:0% the model now even if we don't release 00:11:43.989 --> 00:11:46.350 align:start position:0% the model now even if we don't release the<00:11:44.170> model<00:11:44.470> if<00:11:44.619> all<00:11:45.220> we<00:11:45.369> allow<00:11:45.639> is<00:11:45.939> for<00:11:45.970> people 00:11:46.350 --> 00:11:46.360 align:start position:0% the model if all we allow is for people 00:11:46.360 --> 00:11:48.119 align:start position:0% the model if all we allow is for people to<00:11:46.480> query<00:11:46.809> the<00:11:46.959> model<00:11:47.259> right<00:11:47.799> that's<00:11:48.040> the 00:11:48.119 --> 00:11:48.129 align:start position:0% to query the model right that's the 00:11:48.129 --> 00:11:49.919 align:start position:0% to query the model right that's the whole<00:11:48.160> point<00:11:48.519> of<00:11:48.730> training<00:11:49.449> a<00:11:49.540> model<00:11:49.779> in<00:11:49.839> the 00:11:49.919 --> 00:11:49.929 align:start position:0% whole point of training a model in the 00:11:49.929 --> 00:11:51.210 align:start position:0% whole point of training a model in the first<00:11:50.110> place<00:11:50.290> is<00:11:50.529> so<00:11:50.589> that<00:11:50.769> I<00:11:50.920> can<00:11:51.100> serve 00:11:51.210 --> 00:11:51.220 align:start position:0% first place is so that I can serve 00:11:51.220 --> 00:11:53.819 align:start position:0% first place is so that I can serve inferences<00:11:51.819> it<00:11:52.480> turns<00:11:52.720> out<00:11:52.899> even<00:11:53.170> through 00:11:53.819 --> 00:11:53.829 align:start position:0% inferences it turns out even through 00:11:53.829 --> 00:11:56.039 align:start position:0% inferences it turns out even through these<00:11:54.040> inferences<00:11:54.549> that<00:11:55.449> are<00:11:55.569> generated<00:11:56.019> by 00:11:56.039 --> 00:11:56.049 align:start position:0% these inferences that are generated by 00:11:56.049 --> 00:11:59.369 align:start position:0% these inferences that are generated by the<00:11:56.170> model<00:11:56.649> it's<00:11:57.220> possible<00:11:57.730> to<00:11:57.910> leak<00:11:58.379> original 00:11:59.369 --> 00:11:59.379 align:start position:0% the model it's possible to leak original 00:11:59.379 --> 00:12:02.400 align:start position:0% the model it's possible to leak original sensitive<00:12:00.160> data<00:12:00.389> from<00:12:01.389> the<00:12:01.899> training<00:12:02.170> data 00:12:02.400 --> 00:12:02.410 align:start position:0% sensitive data from the training data 00:12:02.410 --> 00:12:04.319 align:start position:0% sensitive data from the training data set<00:12:02.679> and<00:12:02.920> there's<00:12:03.549> actually<00:12:03.850> a<00:12:03.879> recent<00:12:04.059> work 00:12:04.319 --> 00:12:04.329 align:start position:0% set and there's actually a recent work 00:12:04.329 --> 00:12:06.780 align:start position:0% set and there's actually a recent work that<00:12:04.509> shows<00:12:04.720> that<00:12:04.989> this<00:12:05.170> happens<00:12:05.559> even<00:12:06.399> if 00:12:06.780 --> 00:12:06.790 align:start position:0% that shows that this happens even if 00:12:06.790 --> 00:12:08.129 align:start position:0% that shows that this happens even if you're<00:12:06.939> not<00:12:07.089> intentionally<00:12:07.689> trying<00:12:07.749> to<00:12:07.959> leak 00:12:08.129 --> 00:12:08.139 align:start position:0% you're not intentionally trying to leak 00:12:08.139 --> 00:12:09.749 align:start position:0% you're not intentionally trying to leak the<00:12:08.259> data<00:12:08.439> even<00:12:08.679> if<00:12:08.920> this<00:12:09.069> is<00:12:09.220> a<00:12:09.249> completely 00:12:09.749 --> 00:12:09.759 align:start position:0% the data even if this is a completely 00:12:09.759 --> 00:12:11.519 align:start position:0% the data even if this is a completely benign<00:12:10.029> example<00:12:10.569> and<00:12:10.720> it's<00:12:11.110> a<00:12:11.230> pretty 00:12:11.519 --> 00:12:11.529 align:start position:0% benign example and it's a pretty 00:12:11.529 --> 00:12:12.720 align:start position:0% benign example and it's a pretty straightforward<00:12:11.860> machine<00:12:12.429> learning 00:12:12.720 --> 00:12:12.730 align:start position:0% straightforward machine learning 00:12:12.730 --> 00:12:14.850 align:start position:0% straightforward machine learning pipeline<00:12:13.119> it's<00:12:13.629> possible<00:12:14.259> for<00:12:14.410> the<00:12:14.499> model<00:12:14.829> to 00:12:14.850 --> 00:12:14.860 align:start position:0% pipeline it's possible for the model to 00:12:14.860 --> 00:12:16.049 align:start position:0% pipeline it's possible for the model to inadvertently<00:12:15.279> leak 00:12:16.049 --> 00:12:16.059 align:start position:0% inadvertently leak 00:12:16.059 --> 00:12:17.699 align:start position:0% inadvertently leak for<00:12:16.299> example<00:12:16.600> credit<00:12:17.049> card<00:12:17.199> numbers<00:12:17.499> and 00:12:17.699 --> 00:12:17.709 align:start position:0% for example credit card numbers and 00:12:17.709 --> 00:12:19.109 align:start position:0% for example credit card numbers and Social<00:12:17.980> Security<00:12:18.069> numbers<00:12:18.339> this<00:12:18.730> was<00:12:18.910> shown 00:12:19.109 --> 00:12:19.119 align:start position:0% Social Security numbers this was shown 00:12:19.119 --> 00:12:22.019 align:start position:0% Social Security numbers this was shown in<00:12:19.360> this<00:12:19.540> paper<00:12:19.749> and<00:12:20.019> so<00:12:20.559> clearly<00:12:20.919> if<00:12:21.279> we<00:12:21.549> want 00:12:22.019 --> 00:12:22.029 align:start position:0% in this paper and so clearly if we want 00:12:22.029 --> 00:12:24.210 align:start position:0% in this paper and so clearly if we want to<00:12:22.269> move<00:12:22.869> this<00:12:23.049> to<00:12:23.199> blockchain<00:12:23.649> and<00:12:23.799> we<00:12:24.040> want 00:12:24.210 --> 00:12:24.220 align:start position:0% to move this to blockchain and we want 00:12:24.220 --> 00:12:25.979 align:start position:0% to move this to blockchain and we want to<00:12:24.309> provide<00:12:24.519> end-to-end<00:12:24.910> privacy<00:12:25.569> guarantees 00:12:25.979 --> 00:12:25.989 align:start position:0% to provide end-to-end privacy guarantees 00:12:25.989 --> 00:12:28.289 align:start position:0% to provide end-to-end privacy guarantees we<00:12:26.589> need<00:12:26.799> to<00:12:26.949> protect<00:12:27.309> against<00:12:27.730> these<00:12:27.910> sorts 00:12:28.289 --> 00:12:28.299 align:start position:0% we need to protect against these sorts 00:12:28.299 --> 00:12:31.859 align:start position:0% we need to protect against these sorts of<00:12:28.509> issues<00:12:29.379> as<00:12:29.589> well<00:12:29.889> and<00:12:30.449> this<00:12:31.449> is<00:12:31.509> actually<00:12:31.839> a 00:12:31.859 --> 00:12:31.869 align:start position:0% of issues as well and this is actually a 00:12:31.869 --> 00:12:33.780 align:start position:0% of issues as well and this is actually a real-world<00:12:32.139> problem<00:12:32.709> that<00:12:32.949> companies<00:12:33.519> in 00:12:33.780 --> 00:12:33.790 align:start position:0% real-world problem that companies in 00:12:33.790 --> 00:12:35.879 align:start position:0% real-world problem that companies in industry<00:12:34.360> face<00:12:34.540> so<00:12:34.929> in<00:12:35.139> our<00:12:35.169> previous<00:12:35.379> work<00:12:35.739> we 00:12:35.879 --> 00:12:35.889 align:start position:0% industry face so in our previous work we 00:12:35.889 --> 00:12:37.379 align:start position:0% industry face so in our previous work we collaborated<00:12:36.459> with<00:12:36.579> uber<00:12:36.970> to<00:12:37.059> help<00:12:37.239> them 00:12:37.379 --> 00:12:37.389 align:start position:0% collaborated with uber to help them 00:12:37.389 --> 00:12:39.090 align:start position:0% collaborated with uber to help them solve<00:12:37.569> a<00:12:37.720> very<00:12:37.839> similar<00:12:38.259> problem<00:12:38.470> their 00:12:39.090 --> 00:12:39.100 align:start position:0% solve a very similar problem their 00:12:39.100 --> 00:12:41.309 align:start position:0% solve a very similar problem their setting<00:12:39.489> was<00:12:39.669> of<00:12:40.089> course<00:12:40.329> they<00:12:40.449> collect<00:12:40.809> you 00:12:41.309 --> 00:12:41.319 align:start position:0% setting was of course they collect you 00:12:41.319 --> 00:12:43.109 align:start position:0% setting was of course they collect you know<00:12:41.439> customer<00:12:41.860> data<00:12:42.040> about<00:12:42.369> rides<00:12:42.699> and 00:12:43.109 --> 00:12:43.119 align:start position:0% know customer data about rides and 00:12:43.119 --> 00:12:45.179 align:start position:0% know customer data about rides and destinations<00:12:43.689> and<00:12:43.839> so<00:12:43.959> forth<00:12:44.199> and<00:12:44.410> the<00:12:44.980> data 00:12:45.179 --> 00:12:45.189 align:start position:0% destinations and so forth and the data 00:12:45.189 --> 00:12:46.650 align:start position:0% destinations and so forth and the data is<00:12:45.309> extremely<00:12:45.730> valuable<00:12:45.850> so<00:12:46.299> they<00:12:46.419> want<00:12:46.600> to 00:12:46.650 --> 00:12:46.660 align:start position:0% is extremely valuable so they want to 00:12:46.660 --> 00:12:47.939 align:start position:0% is extremely valuable so they want to make<00:12:46.720> it<00:12:46.929> accessible<00:12:47.169> to<00:12:47.559> their<00:12:47.709> data 00:12:47.939 --> 00:12:47.949 align:start position:0% make it accessible to their data 00:12:47.949 --> 00:12:49.979 align:start position:0% make it accessible to their data scientists<00:12:48.610> internally<00:12:49.149> to<00:12:49.569> mine<00:12:49.779> the<00:12:49.959> data 00:12:49.979 --> 00:12:49.989 align:start position:0% scientists internally to mine the data 00:12:49.989 --> 00:12:52.470 align:start position:0% scientists internally to mine the data and<00:12:50.499> and<00:12:50.860> generate<00:12:51.309> business<00:12:51.639> insights<00:12:52.239> on 00:12:52.470 --> 00:12:52.480 align:start position:0% and and generate business insights on 00:12:52.480 --> 00:12:54.210 align:start position:0% and and generate business insights on the<00:12:53.110> other<00:12:53.230> hand<00:12:53.470> because<00:12:53.799> the<00:12:53.949> data<00:12:54.129> is 00:12:54.210 --> 00:12:54.220 align:start position:0% the other hand because the data is 00:12:54.220 --> 00:12:56.069 align:start position:0% the other hand because the data is sensitive<00:12:54.669> they<00:12:55.119> want<00:12:55.299> to<00:12:55.419> make<00:12:55.600> sure<00:12:55.629> that 00:12:56.069 --> 00:12:56.079 align:start position:0% sensitive they want to make sure that 00:12:56.079 --> 00:12:57.359 align:start position:0% sensitive they want to make sure that they're<00:12:56.199> protecting<00:12:56.769> the<00:12:56.889> privacy<00:12:57.339> of 00:12:57.359 --> 00:12:57.369 align:start position:0% they're protecting the privacy of 00:12:57.369 --> 00:13:00.509 align:start position:0% they're protecting the privacy of individuals<00:12:58.119> and<00:12:58.360> so<00:12:59.049> the<00:12:59.559> the<00:12:59.829> big<00:13:00.009> challenge 00:13:00.509 --> 00:13:00.519 align:start position:0% individuals and so the the big challenge 00:13:00.519 --> 00:13:03.449 align:start position:0% individuals and so the the big challenge here<00:13:00.579> is<00:13:00.939> how<00:13:01.119> do<00:13:01.480> you<00:13:01.899> allow<00:13:02.499> kind<00:13:03.100> of<00:13:03.189> safe 00:13:03.449 --> 00:13:03.459 align:start position:0% here is how do you allow kind of safe 00:13:03.459 --> 00:13:05.220 align:start position:0% here is how do you allow kind of safe analytics<00:13:04.119> things<00:13:04.540> that<00:13:04.749> don't<00:13:04.959> violate 00:13:05.220 --> 00:13:05.230 align:start position:0% analytics things that don't violate 00:13:05.230 --> 00:13:05.939 align:start position:0% analytics things that don't violate privacy 00:13:05.939 --> 00:13:05.949 align:start position:0% privacy 00:13:05.949 --> 00:13:09.090 align:start position:0% privacy well<00:13:06.929> disallowing<00:13:07.929> things<00:13:08.230> that<00:13:08.529> do<00:13:08.769> violate 00:13:09.090 --> 00:13:09.100 align:start position:0% well disallowing things that do violate 00:13:09.100 --> 00:13:11.039 align:start position:0% well disallowing things that do violate privacy<00:13:09.309> so<00:13:09.669> a<00:13:09.699> good<00:13:09.970> example<00:13:10.299> to<00:13:10.480> contrast 00:13:11.039 --> 00:13:11.049 align:start position:0% privacy so a good example to contrast 00:13:11.049 --> 00:13:13.019 align:start position:0% privacy so a good example to contrast this<00:13:11.290> is<00:13:11.499> you<00:13:12.040> know<00:13:12.129> something<00:13:12.369> safe<00:13:12.730> is 00:13:13.019 --> 00:13:13.029 align:start position:0% this is you know something safe is 00:13:13.029 --> 00:13:15.359 align:start position:0% this is you know something safe is asking<00:13:13.959> a<00:13:14.049> statistical<00:13:14.679> query<00:13:14.889> like<00:13:15.069> how<00:13:15.189> many 00:13:15.359 --> 00:13:15.369 align:start position:0% asking a statistical query like how many 00:13:15.369 --> 00:13:17.189 align:start position:0% asking a statistical query like how many people<00:13:15.699> visited<00:13:16.149> New<00:13:16.269> York<00:13:16.509> last<00:13:16.720> year<00:13:16.899> right 00:13:17.189 --> 00:13:17.199 align:start position:0% people visited New York last year right 00:13:17.199 --> 00:13:18.900 align:start position:0% people visited New York last year right clearly<00:13:17.529> that's<00:13:18.100> not<00:13:18.369> going<00:13:18.519> to<00:13:18.610> violate 00:13:18.900 --> 00:13:18.910 align:start position:0% clearly that's not going to violate 00:13:18.910 --> 00:13:19.900 align:start position:0% clearly that's not going to violate anyone's<00:13:19.480> privacy 00:13:19.900 --> 00:13:19.910 align:start position:0% anyone's privacy 00:13:19.910 --> 00:13:22.360 align:start position:0% anyone's privacy nobody<00:13:20.270> in<00:13:20.450> this<00:13:20.600> data<00:13:20.870> would<00:13:21.140> object<00:13:21.260> if<00:13:21.740> this 00:13:22.360 --> 00:13:22.370 align:start position:0% nobody in this data would object if this 00:13:22.370 --> 00:13:24.340 align:start position:0% nobody in this data would object if this result<00:13:22.820> was<00:13:23.090> returned<00:13:23.420> to<00:13:23.540> the<00:13:23.750> analyst<00:13:24.170> on 00:13:24.340 --> 00:13:24.350 align:start position:0% result was returned to the analyst on 00:13:24.350 --> 00:13:26.560 align:start position:0% result was returned to the analyst on the<00:13:24.710> other<00:13:24.920> hand<00:13:25.160> if<00:13:25.340> the<00:13:25.430> analyst<00:13:25.910> asked<00:13:26.300> this 00:13:26.560 --> 00:13:26.570 align:start position:0% the other hand if the analyst asked this 00:13:26.570 --> 00:13:28.840 align:start position:0% the other hand if the analyst asked this sort<00:13:26.810> of<00:13:26.870> question<00:13:27.020> how<00:13:27.380> many<00:13:27.440> times<00:13:27.620> did<00:13:28.250> Joe 00:13:28.840 --> 00:13:28.850 align:start position:0% sort of question how many times did Joe 00:13:28.850 --> 00:13:30.910 align:start position:0% sort of question how many times did Joe go<00:13:29.180> to<00:13:29.210> Whole<00:13:29.480> Foods<00:13:29.510> last<00:13:29.930> week<00:13:30.110> that's<00:13:30.800> a 00:13:30.910 --> 00:13:30.920 align:start position:0% go to Whole Foods last week that's a 00:13:30.920 --> 00:13:32.980 align:start position:0% go to Whole Foods last week that's a statistical<00:13:31.460> question<00:13:31.610> on<00:13:32.060> exactly<00:13:32.720> the<00:13:32.810> same 00:13:32.980 --> 00:13:32.990 align:start position:0% statistical question on exactly the same 00:13:32.990 --> 00:13:35.320 align:start position:0% statistical question on exactly the same data<00:13:33.200> this<00:13:33.890> is<00:13:34.190> a<00:13:34.220> pretty<00:13:34.640> serious<00:13:34.910> privacy 00:13:35.320 --> 00:13:35.330 align:start position:0% data this is a pretty serious privacy 00:13:35.330 --> 00:13:37.990 align:start position:0% data this is a pretty serious privacy violation<00:13:36.020> so<00:13:36.410> how<00:13:36.830> do<00:13:36.890> you<00:13:37.040> automatically 00:13:37.990 --> 00:13:38.000 align:start position:0% violation so how do you automatically 00:13:38.000 --> 00:13:40.630 align:start position:0% violation so how do you automatically guarantee<00:13:38.960> that<00:13:39.320> the<00:13:39.710> system<00:13:40.100> will<00:13:40.370> allow 00:13:40.630 --> 00:13:40.640 align:start position:0% guarantee that the system will allow 00:13:40.640 --> 00:13:43.000 align:start position:0% guarantee that the system will allow things<00:13:40.850> like<00:13:41.000> this<00:13:41.300> and<00:13:41.540> disallow<00:13:42.290> things 00:13:43.000 --> 00:13:43.010 align:start position:0% things like this and disallow things 00:13:43.010 --> 00:13:45.310 align:start position:0% things like this and disallow things like<00:13:43.280> this<00:13:43.460> this<00:13:44.030> is<00:13:44.210> a<00:13:44.240> very<00:13:44.450> hard<00:13:44.690> problem<00:13:44.930> in 00:13:45.310 --> 00:13:45.320 align:start position:0% like this this is a very hard problem in 00:13:45.320 --> 00:13:47.770 align:start position:0% like this this is a very hard problem in general<00:13:45.740> so<00:13:46.310> one<00:13:47.090> of<00:13:47.120> the<00:13:47.270> techniques<00:13:47.690> that 00:13:47.770 --> 00:13:47.780 align:start position:0% general so one of the techniques that 00:13:47.780 --> 00:13:49.750 align:start position:0% general so one of the techniques that we've<00:13:48.050> used<00:13:48.220> is<00:13:49.220> a<00:13:49.310> technique<00:13:49.700> that's 00:13:49.750 --> 00:13:49.760 align:start position:0% we've used is a technique that's 00:13:49.760 --> 00:13:51.460 align:start position:0% we've used is a technique that's developed<00:13:50.360> out<00:13:50.480> of<00:13:50.600> academia<00:13:50.930> and<00:13:51.320> it's 00:13:51.460 --> 00:13:51.470 align:start position:0% developed out of academia and it's 00:13:51.470 --> 00:13:54.070 align:start position:0% developed out of academia and it's called<00:13:51.680> differential<00:13:52.130> privacy<00:13:52.900> by<00:13:53.900> the<00:13:53.960> way 00:13:54.070 --> 00:13:54.080 align:start position:0% called differential privacy by the way 00:13:54.080 --> 00:13:55.240 align:start position:0% called differential privacy by the way are<00:13:54.170> people<00:13:54.380> familiar<00:13:54.470> with<00:13:54.740> differential 00:13:55.240 --> 00:13:55.250 align:start position:0% are people familiar with differential 00:13:55.250 --> 00:13:57.880 align:start position:0% are people familiar with differential privacy<00:13:55.400> so<00:13:56.300> fewer<00:13:56.720> people<00:13:57.020> great<00:13:57.740> so 00:13:57.880 --> 00:13:57.890 align:start position:0% privacy so fewer people great so 00:13:57.890 --> 00:14:00.490 align:start position:0% privacy so fewer people great so differential<00:13:58.790> privacy<00:13:59.270> is<00:13:59.540> a<00:13:59.570> formal 00:14:00.490 --> 00:14:00.500 align:start position:0% differential privacy is a formal 00:14:00.500 --> 00:14:02.680 align:start position:0% differential privacy is a formal definition<00:14:01.130> of<00:14:01.280> what<00:14:01.430> privacy<00:14:01.760> means<00:14:01.880> it's<00:14:02.630> a 00:14:02.680 --> 00:14:02.690 align:start position:0% definition of what privacy means it's a 00:14:02.690 --> 00:14:04.650 align:start position:0% definition of what privacy means it's a formal<00:14:03.020> mathematical<00:14:03.370> definition<00:14:04.370> and 00:14:04.650 --> 00:14:04.660 align:start position:0% formal mathematical definition and 00:14:04.660 --> 00:14:07.300 align:start position:0% formal mathematical definition and intuitively<00:14:05.660> it<00:14:05.960> says<00:14:06.230> that<00:14:06.470> okay<00:14:07.010> if<00:14:07.100> I<00:14:07.190> have 00:14:07.300 --> 00:14:07.310 align:start position:0% intuitively it says that okay if I have 00:14:07.310 --> 00:14:09.040 align:start position:0% intuitively it says that okay if I have any<00:14:07.460> two<00:14:07.700> databases<00:14:08.000> that<00:14:08.450> have<00:14:08.510> sensitive 00:14:09.040 --> 00:14:09.050 align:start position:0% any two databases that have sensitive 00:14:09.050 --> 00:14:11.650 align:start position:0% any two databases that have sensitive information<00:14:09.140> and<00:14:10.120> one<00:14:11.120> of<00:14:11.240> those<00:14:11.330> databases 00:14:11.650 --> 00:14:11.660 align:start position:0% information and one of those databases 00:14:11.660 --> 00:14:13.720 align:start position:0% information and one of those databases has<00:14:12.080> a<00:14:12.110> user<00:14:12.410> and<00:14:12.710> the<00:14:12.830> other<00:14:12.980> database<00:14:13.280> is 00:14:13.720 --> 00:14:13.730 align:start position:0% has a user and the other database is 00:14:13.730 --> 00:14:16.060 align:start position:0% has a user and the other database is identical<00:14:14.510> to<00:14:14.720> the<00:14:15.050> first<00:14:15.200> one<00:14:15.470> except<00:14:15.950> it 00:14:16.060 --> 00:14:16.070 align:start position:0% identical to the first one except it 00:14:16.070 --> 00:14:18.040 align:start position:0% identical to the first one except it doesn't<00:14:16.430> have<00:14:16.550> that<00:14:16.730> user<00:14:16.910> right<00:14:17.450> so<00:14:17.660> database 00:14:18.040 --> 00:14:18.050 align:start position:0% doesn't have that user right so database 00:14:18.050 --> 00:14:20.470 align:start position:0% doesn't have that user right so database one<00:14:18.260> has<00:14:18.500> Jo<00:14:18.800> database<00:14:19.490> two<00:14:19.670> has<00:14:19.820> every<00:14:20.240> record 00:14:20.470 --> 00:14:20.480 align:start position:0% one has Jo database two has every record 00:14:20.480 --> 00:14:23.590 align:start position:0% one has Jo database two has every record in<00:14:20.840> database<00:14:21.290> one<00:14:21.470> except<00:14:22.070> Jo<00:14:22.600> differential 00:14:23.590 --> 00:14:23.600 align:start position:0% in database one except Jo differential 00:14:23.600 --> 00:14:26.320 align:start position:0% in database one except Jo differential privacy<00:14:23.780> the<00:14:24.290> definition<00:14:25.010> says<00:14:25.310> that<00:14:25.670> if<00:14:25.940> I 00:14:26.320 --> 00:14:26.330 align:start position:0% privacy the definition says that if I 00:14:26.330 --> 00:14:28.450 align:start position:0% privacy the definition says that if I take<00:14:26.510> any<00:14:26.570> query<00:14:27.110> or<00:14:27.530> I<00:14:27.650> train<00:14:27.980> any<00:14:28.130> machine 00:14:28.450 --> 00:14:28.460 align:start position:0% take any query or I train any machine 00:14:28.460 --> 00:14:31.330 align:start position:0% take any query or I train any machine learning<00:14:28.730> model<00:14:29.030> or<00:14:29.180> I<00:14:29.210> do<00:14:29.330> anything<00:14:29.780> on<00:14:30.340> both 00:14:31.330 --> 00:14:31.340 align:start position:0% learning model or I do anything on both 00:14:31.340 --> 00:14:33.730 align:start position:0% learning model or I do anything on both of<00:14:31.520> these<00:14:31.610> data<00:14:31.910> sets<00:14:32.120> independently<00:14:32.990> then 00:14:33.730 --> 00:14:33.740 align:start position:0% of these data sets independently then 00:14:33.740 --> 00:14:36.370 align:start position:0% of these data sets independently then the<00:14:34.340> answers<00:14:34.970> the<00:14:35.420> results<00:14:35.990> of<00:14:36.140> those 00:14:36.370 --> 00:14:36.380 align:start position:0% the answers the results of those 00:14:36.380 --> 00:14:38.320 align:start position:0% the answers the results of those computations<00:14:37.190> have<00:14:37.340> to<00:14:37.460> be<00:14:37.550> essentially<00:14:38.210> the 00:14:38.320 --> 00:14:38.330 align:start position:0% computations have to be essentially the 00:14:38.330 --> 00:14:40.210 align:start position:0% computations have to be essentially the same<00:14:38.540> whether<00:14:39.230> it's<00:14:39.440> run<00:14:39.620> on<00:14:39.740> this<00:14:39.920> database 00:14:40.210 --> 00:14:40.220 align:start position:0% same whether it's run on this database 00:14:40.220 --> 00:14:42.730 align:start position:0% same whether it's run on this database or<00:14:40.610> this<00:14:40.790> database<00:14:41.060> so<00:14:41.780> what<00:14:41.990> this<00:14:42.080> means<00:14:42.140> is 00:14:42.730 --> 00:14:42.740 align:start position:0% or this database so what this means is 00:14:42.740 --> 00:14:45.490 align:start position:0% or this database so what this means is that<00:14:42.830> from<00:14:43.610> the<00:14:43.880> result<00:14:44.240> there's<00:14:44.870> no<00:14:45.200> way<00:14:45.440> to 00:14:45.490 --> 00:14:45.500 align:start position:0% that from the result there's no way to 00:14:45.500 --> 00:14:47.500 align:start position:0% that from the result there's no way to tell<00:14:45.800> whether<00:14:46.160> Jo<00:14:46.490> was<00:14:46.670> actually<00:14:46.970> in<00:14:47.180> the 00:14:47.500 --> 00:14:47.510 align:start position:0% tell whether Jo was actually in the 00:14:47.510 --> 00:14:49.030 align:start position:0% tell whether Jo was actually in the database<00:14:47.900> because<00:14:48.290> the<00:14:48.560> result<00:14:48.860> would<00:14:49.010> look 00:14:49.030 --> 00:14:49.040 align:start position:0% database because the result would look 00:14:49.040 --> 00:14:51.610 align:start position:0% database because the result would look identical<00:14:49.340> even<00:14:50.150> if<00:14:50.450> he<00:14:50.570> wasn't<00:14:50.750> and<00:14:51.050> so<00:14:51.530> what 00:14:51.610 --> 00:14:51.620 align:start position:0% identical even if he wasn't and so what 00:14:51.620 --> 00:14:53.350 align:start position:0% identical even if he wasn't and so what this<00:14:51.740> means<00:14:51.980> is<00:14:52.220> given<00:14:52.760> that<00:14:52.850> I<00:14:52.940> can't<00:14:53.210> even 00:14:53.350 --> 00:14:53.360 align:start position:0% this means is given that I can't even 00:14:53.360 --> 00:14:55.090 align:start position:0% this means is given that I can't even tell<00:14:53.510> whether<00:14:53.900> a<00:14:54.020> user's<00:14:54.410> in<00:14:54.530> the<00:14:54.620> database<00:14:54.980> I 00:14:55.090 --> 00:14:55.100 align:start position:0% tell whether a user's in the database I 00:14:55.100 --> 00:14:56.860 align:start position:0% tell whether a user's in the database I certainly<00:14:55.370> can't<00:14:55.730> learn<00:14:56.060> their<00:14:56.450> sensitive 00:14:56.860 --> 00:14:56.870 align:start position:0% certainly can't learn their sensitive 00:14:56.870 --> 00:14:59.410 align:start position:0% certainly can't learn their sensitive information<00:14:57.140> and<00:14:57.650> so<00:14:58.220> it<00:14:58.700> means<00:14:58.880> the<00:14:59.060> outcome 00:14:59.410 --> 00:14:59.420 align:start position:0% information and so it means the outcome 00:14:59.420 --> 00:15:00.910 align:start position:0% information and so it means the outcome is<00:14:59.540> the<00:14:59.570> same<00:14:59.810> with<00:15:00.020> or<00:15:00.140> without<00:15:00.230> Jo's<00:15:00.620> data 00:15:00.910 --> 00:15:00.920 align:start position:0% is the same with or without Jo's data 00:15:00.920 --> 00:15:02.860 align:start position:0% is the same with or without Jo's data and<00:15:01.160> the<00:15:01.580> property<00:15:02.030> says<00:15:02.210> that<00:15:02.240> this<00:15:02.480> has<00:15:02.690> to 00:15:02.860 --> 00:15:02.870 align:start position:0% and the property says that this has to 00:15:02.870 --> 00:15:05.740 align:start position:0% and the property says that this has to hold<00:15:03.080> for<00:15:03.500> every<00:15:03.800> user<00:15:04.610> and<00:15:04.760> every<00:15:05.480> database 00:15:05.740 --> 00:15:05.750 align:start position:0% hold for every user and every database 00:15:05.750 --> 00:15:07.810 align:start position:0% hold for every user and every database and<00:15:06.140> so<00:15:07.010> the<00:15:07.130> nice<00:15:07.280> thing<00:15:07.310> about<00:15:07.520> this 00:15:07.810 --> 00:15:07.820 align:start position:0% and so the nice thing about this 00:15:07.820 --> 00:15:10.030 align:start position:0% and so the nice thing about this definition<00:15:08.270> is<00:15:08.600> it<00:15:08.810> provides<00:15:09.320> very<00:15:09.650> strong 00:15:10.030 --> 00:15:10.040 align:start position:0% definition is it provides very strong 00:15:10.040 --> 00:15:12.130 align:start position:0% definition is it provides very strong guarantees<00:15:10.550> for<00:15:10.760> individuals<00:15:11.390> while<00:15:11.870> still 00:15:12.130 --> 00:15:12.140 align:start position:0% guarantees for individuals while still 00:15:12.140 --> 00:15:13.960 align:start position:0% guarantees for individuals while still allowing<00:15:12.470> those<00:15:12.980> sorts<00:15:13.220> of<00:15:13.280> general-purpose 00:15:13.960 --> 00:15:13.970 align:start position:0% allowing those sorts of general-purpose 00:15:13.970 --> 00:15:15.880 align:start position:0% allowing those sorts of general-purpose analytics<00:15:14.630> and<00:15:14.810> machine<00:15:15.080> learning<00:15:15.110> which<00:15:15.860> is 00:15:15.880 --> 00:15:15.890 align:start position:0% analytics and machine learning which is 00:15:15.890 --> 00:15:17.500 align:start position:0% analytics and machine learning which is the<00:15:16.100> very<00:15:16.250> reason<00:15:16.460> often<00:15:16.790> times<00:15:17.120> we<00:15:17.240> want<00:15:17.420> to 00:15:17.500 --> 00:15:17.510 align:start position:0% the very reason often times we want to 00:15:17.510 --> 00:15:20.260 align:start position:0% the very reason often times we want to analyze<00:15:17.780> data<00:15:18.410> so<00:15:18.950> if<00:15:19.130> a<00:15:19.250> user<00:15:19.430> knows<00:15:19.850> that<00:15:20.120> the 00:15:20.260 --> 00:15:20.270 align:start position:0% analyze data so if a user knows that the 00:15:20.270 --> 00:15:22.630 align:start position:0% analyze data so if a user knows that the system<00:15:20.630> enforces<00:15:21.080> this<00:15:21.380> property<00:15:21.890> they<00:15:22.430> don't 00:15:22.630 --> 00:15:22.640 align:start position:0% system enforces this property they don't 00:15:22.640 --> 00:15:24.400 align:start position:0% system enforces this property they don't need<00:15:22.970> to<00:15:23.330> worry<00:15:23.570> about<00:15:23.690> what<00:15:23.960> the<00:15:23.990> query<00:15:24.320> is 00:15:24.400 --> 00:15:24.410 align:start position:0% need to worry about what the query is 00:15:24.410 --> 00:15:26.020 align:start position:0% need to worry about what the query is doing<00:15:24.680> they<00:15:24.770> don't<00:15:24.890> need<00:15:25.190> to<00:15:25.370> inspect<00:15:25.880> the 00:15:26.020 --> 00:15:26.030 align:start position:0% doing they don't need to inspect the 00:15:26.030 --> 00:15:28.780 align:start position:0% doing they don't need to inspect the query<00:15:26.300> they<00:15:26.840> have<00:15:27.110> assurances<00:15:27.680> that<00:15:27.790> whatever 00:15:28.780 --> 00:15:28.790 align:start position:0% query they have assurances that whatever 00:15:28.790 --> 00:15:30.940 align:start position:0% query they have assurances that whatever is<00:15:29.000> returned<00:15:29.390> there's<00:15:29.960> no<00:15:30.290> way<00:15:30.530> for<00:15:30.560> the 00:15:30.940 --> 00:15:30.950 align:start position:0% is returned there's no way for the 00:15:30.950 --> 00:15:33.010 align:start position:0% is returned there's no way for the person<00:15:31.130> that<00:15:31.370> sees<00:15:31.790> that<00:15:32.000> result<00:15:32.360> to<00:15:32.840> know 00:15:33.010 --> 00:15:33.020 align:start position:0% person that sees that result to know 00:15:33.020 --> 00:15:33.430 align:start position:0% person that sees that result to know whether 00:15:33.430 --> 00:15:33.440 align:start position:0% whether 00:15:33.440 --> 00:15:34.750 align:start position:0% whether in<00:15:33.500> the<00:15:33.560> database<00:15:33.890> so<00:15:34.100> there's<00:15:34.250> no<00:15:34.400> reason<00:15:34.730> for 00:15:34.750 --> 00:15:34.760 align:start position:0% in the database so there's no reason for 00:15:34.760 --> 00:15:37.480 align:start position:0% in the database so there's no reason for them<00:15:34.940> to<00:15:35.000> object<00:15:35.600> on<00:15:35.810> privacy<00:15:36.560> grounds<00:15:37.040> to 00:15:37.480 --> 00:15:37.490 align:start position:0% them to object on privacy grounds to 00:15:37.490 --> 00:15:39.340 align:start position:0% them to object on privacy grounds to being<00:15:37.730> in<00:15:37.940> the<00:15:38.030> database<00:15:38.390> in<00:15:38.600> the<00:15:38.780> first<00:15:38.990> place 00:15:39.340 --> 00:15:39.350 align:start position:0% being in the database in the first place 00:15:39.350 --> 00:15:42.220 align:start position:0% being in the database in the first place so<00:15:39.560> this<00:15:39.650> is<00:15:39.740> a<00:15:39.770> very<00:15:40.070> very<00:15:40.340> nice<00:15:40.520> property<00:15:41.230> our 00:15:42.220 --> 00:15:42.230 align:start position:0% so this is a very very nice property our 00:15:42.230 --> 00:15:44.920 align:start position:0% so this is a very very nice property our work<00:15:42.740> actually<00:15:43.310> was<00:15:43.610> focused<00:15:44.210> on<00:15:44.330> how<00:15:44.510> to<00:15:44.540> take 00:15:44.920 --> 00:15:44.930 align:start position:0% work actually was focused on how to take 00:15:44.930 --> 00:15:46.540 align:start position:0% work actually was focused on how to take this<00:15:45.110> property<00:15:45.560> and<00:15:45.740> build<00:15:45.950> real-world 00:15:46.540 --> 00:15:46.550 align:start position:0% this property and build real-world 00:15:46.550 --> 00:15:48.730 align:start position:0% this property and build real-world systems<00:15:46.850> to<00:15:47.510> automatically<00:15:48.230> enforce 00:15:48.730 --> 00:15:48.740 align:start position:0% systems to automatically enforce 00:15:48.740 --> 00:15:50.770 align:start position:0% systems to automatically enforce differential<00:15:49.640> privacy<00:15:49.820> and<00:15:50.240> other<00:15:50.330> types<00:15:50.630> of 00:15:50.770 --> 00:15:50.780 align:start position:0% differential privacy and other types of 00:15:50.780 --> 00:15:53.260 align:start position:0% differential privacy and other types of security<00:15:50.960> policies<00:15:51.620> for<00:15:52.100> real<00:15:52.580> world<00:15:52.820> queries 00:15:53.260 --> 00:15:53.270 align:start position:0% security policies for real world queries 00:15:53.270 --> 00:15:55.330 align:start position:0% security policies for real world queries and<00:15:53.510> in<00:15:53.690> a<00:15:53.750> real-world<00:15:53.990> setting<00:15:54.350> like<00:15:54.950> ubers 00:15:55.330 --> 00:15:55.340 align:start position:0% and in a real-world setting like ubers 00:15:55.340 --> 00:15:58.240 align:start position:0% and in a real-world setting like ubers and<00:15:56.150> in<00:15:56.300> particular<00:15:56.450> allow<00:15:57.380> it<00:15:57.590> to<00:15:57.710> be<00:15:57.800> used<00:15:58.070> by 00:15:58.240 --> 00:15:58.250 align:start position:0% and in particular allow it to be used by 00:15:58.250 --> 00:16:00.250 align:start position:0% and in particular allow it to be used by non<00:15:58.490> experts<00:15:58.970> so<00:15:59.120> hide<00:15:59.300> all<00:15:59.600> the<00:15:59.780> complex 00:16:00.250 --> 00:16:00.260 align:start position:0% non experts so hide all the complex 00:16:00.260 --> 00:16:01.750 align:start position:0% non experts so hide all the complex details<00:16:00.620> of<00:16:00.800> how<00:16:00.890> to<00:16:00.950> actually<00:16:01.160> get<00:16:01.460> this<00:16:01.580> to 00:16:01.750 --> 00:16:01.760 align:start position:0% details of how to actually get this to 00:16:01.760 --> 00:16:04.180 align:start position:0% details of how to actually get this to work<00:16:01.910> so<00:16:02.150> that<00:16:02.630> analysts<00:16:03.560> and<00:16:03.710> developers 00:16:04.180 --> 00:16:04.190 align:start position:0% work so that analysts and developers 00:16:04.190 --> 00:16:06.190 align:start position:0% work so that analysts and developers have<00:16:04.820> a<00:16:04.880> very<00:16:05.120> simple<00:16:05.450> interface<00:16:05.660> they<00:16:06.020> don't 00:16:06.190 --> 00:16:06.200 align:start position:0% have a very simple interface they don't 00:16:06.200 --> 00:16:07.750 align:start position:0% have a very simple interface they don't need<00:16:06.320> to<00:16:06.470> make<00:16:06.590> major<00:16:06.890> changes<00:16:07.040> to<00:16:07.520> the<00:16:07.670> way 00:16:07.750 --> 00:16:07.760 align:start position:0% need to make major changes to the way 00:16:07.760 --> 00:16:09.730 align:start position:0% need to make major changes to the way they<00:16:08.030> write<00:16:08.180> their<00:16:08.330> code<00:16:08.510> and<00:16:08.780> the<00:16:09.350> system 00:16:09.730 --> 00:16:09.740 align:start position:0% they write their code and the system 00:16:09.740 --> 00:16:11.530 align:start position:0% they write their code and the system automatically<00:16:10.400> enforces<00:16:11.030> differential 00:16:11.530 --> 00:16:11.540 align:start position:0% automatically enforces differential 00:16:11.540 --> 00:16:13.720 align:start position:0% automatically enforces differential privacy<00:16:11.900> and<00:16:12.080> can<00:16:12.230> prove<00:16:12.500> that<00:16:13.130> it<00:16:13.280> enforced<00:16:13.640> a 00:16:13.720 --> 00:16:13.730 align:start position:0% privacy and can prove that it enforced a 00:16:13.730 --> 00:16:15.580 align:start position:0% privacy and can prove that it enforced a differential<00:16:14.180> privacy<00:16:14.630> so<00:16:15.230> we<00:16:15.320> have<00:16:15.410> a<00:16:15.470> number 00:16:15.580 --> 00:16:15.590 align:start position:0% differential privacy so we have a number 00:16:15.590 --> 00:16:17.200 align:start position:0% differential privacy so we have a number of<00:16:15.740> papers<00:16:15.920> that<00:16:16.220> talk<00:16:16.340> about<00:16:16.400> this<00:16:16.790> work<00:16:17.030> and 00:16:17.200 --> 00:16:17.210 align:start position:0% of papers that talk about this work and 00:16:17.210 --> 00:16:19.990 align:start position:0% of papers that talk about this work and the<00:16:18.110> the<00:16:18.500> system<00:16:18.710> that<00:16:19.040> we<00:16:19.130> built<00:16:19.160> based<00:16:19.820> on 00:16:19.990 --> 00:16:20.000 align:start position:0% the the system that we built based on 00:16:20.000 --> 00:16:22.420 align:start position:0% the the system that we built based on this<00:16:20.120> research<00:16:20.330> is<00:16:20.690> actually<00:16:21.380> now<00:16:21.890> already 00:16:22.420 --> 00:16:22.430 align:start position:0% this research is actually now already 00:16:22.430 --> 00:16:24.190 align:start position:0% this research is actually now already deployed<00:16:22.760> internally<00:16:23.420> at<00:16:23.510> uber<00:16:23.780> so<00:16:23.960> all 00:16:24.190 --> 00:16:24.200 align:start position:0% deployed internally at uber so all 00:16:24.200 --> 00:16:26.410 align:start position:0% deployed internally at uber so all queries<00:16:24.620> that<00:16:24.950> are<00:16:25.040> submitted<00:16:25.460> internally<00:16:26.270> by 00:16:26.410 --> 00:16:26.420 align:start position:0% queries that are submitted internally by 00:16:26.420 --> 00:16:28.300 align:start position:0% queries that are submitted internally by uber<00:16:26.750> analysts<00:16:27.230> are<00:16:27.320> routed<00:16:28.040> through<00:16:28.160> the 00:16:28.300 --> 00:16:28.310 align:start position:0% uber analysts are routed through the 00:16:28.310 --> 00:16:30.220 align:start position:0% uber analysts are routed through the system<00:16:28.730> to<00:16:29.210> enforce<00:16:29.570> properties<00:16:30.050> like 00:16:30.220 --> 00:16:30.230 align:start position:0% system to enforce properties like 00:16:30.230 --> 00:16:32.290 align:start position:0% system to enforce properties like differential<00:16:30.710> privacy<00:16:30.890> and<00:16:31.370> other<00:16:31.790> policies 00:16:32.290 --> 00:16:32.300 align:start position:0% differential privacy and other policies 00:16:32.300 --> 00:16:34.840 align:start position:0% differential privacy and other policies around<00:16:32.570> compliance<00:16:33.350> with<00:16:33.500> gdpr<00:16:33.860> and<00:16:34.730> there 00:16:34.840 --> 00:16:34.850 align:start position:0% around compliance with gdpr and there 00:16:34.850 --> 00:16:37.240 align:start position:0% around compliance with gdpr and there are<00:16:34.910> other<00:16:35.060> pilots<00:16:35.480> underway<00:16:36.040> the<00:16:37.040> tool 00:16:37.240 --> 00:16:37.250 align:start position:0% are other pilots underway the tool 00:16:37.250 --> 00:16:39.760 align:start position:0% are other pilots underway the tool itself<00:16:37.520> is<00:16:37.730> a<00:16:37.760> veil<00:16:38.330> above<00:16:38.540> open-source<00:16:38.990> we 00:16:39.760 --> 00:16:39.770 align:start position:0% itself is a veil above open-source we 00:16:39.770 --> 00:16:42.400 align:start position:0% itself is a veil above open-source we want<00:16:40.100> to<00:16:40.400> put<00:16:41.270> this<00:16:41.390> in<00:16:41.540> the<00:16:41.600> hands<00:16:41.960> of<00:16:42.050> smart 00:16:42.400 --> 00:16:42.410 align:start position:0% want to put this in the hands of smart 00:16:42.410 --> 00:16:44.290 align:start position:0% want to put this in the hands of smart contract<00:16:42.830> developers<00:16:43.340> so<00:16:43.760> this<00:16:44.030> has<00:16:44.150> already 00:16:44.290 --> 00:16:44.300 align:start position:0% contract developers so this has already 00:16:44.300 --> 00:16:46.330 align:start position:0% contract developers so this has already been<00:16:44.510> battle<00:16:44.840> tested<00:16:44.870> and<00:16:45.380> enterprise<00:16:45.770> we 00:16:46.330 --> 00:16:46.340 align:start position:0% been battle tested and enterprise we 00:16:46.340 --> 00:16:48.430 align:start position:0% been battle tested and enterprise we want<00:16:46.580> smart<00:16:47.090> contract<00:16:47.540> developers<00:16:47.930> to<00:16:48.080> also 00:16:48.430 --> 00:16:48.440 align:start position:0% want smart contract developers to also 00:16:48.440 --> 00:16:50.200 align:start position:0% want smart contract developers to also benefit<00:16:48.830> from<00:16:48.860> this<00:16:49.100> technology<00:16:49.280> so<00:16:49.880> that<00:16:50.030> any 00:16:50.200 --> 00:16:50.210 align:start position:0% benefit from this technology so that any 00:16:50.210 --> 00:16:52.810 align:start position:0% benefit from this technology so that any developer<00:16:50.870> can<00:16:51.320> use<00:16:51.350> it<00:16:51.740> even<00:16:52.280> if<00:16:52.400> they're<00:16:52.670> not 00:16:52.810 --> 00:16:52.820 align:start position:0% developer can use it even if they're not 00:16:52.820 --> 00:16:54.610 align:start position:0% developer can use it even if they're not privacy<00:16:53.330> experts<00:16:53.690> so<00:16:54.110> we're<00:16:54.290> gonna<00:16:54.380> release 00:16:54.610 --> 00:16:54.620 align:start position:0% privacy experts so we're gonna release 00:16:54.620 --> 00:16:56.830 align:start position:0% privacy experts so we're gonna release what<00:16:54.950> we<00:16:55.040> call<00:16:55.220> the<00:16:55.340> Oasis<00:16:55.760> privacy<00:16:56.180> SDK<00:16:56.600> that 00:16:56.830 --> 00:16:56.840 align:start position:0% what we call the Oasis privacy SDK that 00:16:56.840 --> 00:16:59.050 align:start position:0% what we call the Oasis privacy SDK that allows<00:16:57.470> a<00:16:57.500> developer<00:16:57.890> to<00:16:58.460> write<00:16:58.700> a<00:16:58.730> smart 00:16:59.050 --> 00:16:59.060 align:start position:0% allows a developer to write a smart 00:16:59.060 --> 00:17:01.030 align:start position:0% allows a developer to write a smart contract<00:16:59.570> that<00:16:59.900> includes<00:17:00.380> some<00:17:00.830> of<00:17:00.920> these 00:17:01.030 --> 00:17:01.040 align:start position:0% contract that includes some of these 00:17:01.040 --> 00:17:03.010 align:start position:0% contract that includes some of these libraries<00:17:01.280> and<00:17:01.730> that<00:17:02.120> means<00:17:02.390> that<00:17:02.630> the<00:17:02.750> smart 00:17:03.010 --> 00:17:03.020 align:start position:0% libraries and that means that the smart 00:17:03.020 --> 00:17:05.260 align:start position:0% libraries and that means that the smart contract<00:17:03.200> for<00:17:03.950> example<00:17:04.010> if<00:17:04.520> it's<00:17:04.699> training<00:17:05.209> a 00:17:05.260 --> 00:17:05.270 align:start position:0% contract for example if it's training a 00:17:05.270 --> 00:17:07.420 align:start position:0% contract for example if it's training a machine<00:17:05.540> learning<00:17:05.660> model<00:17:06.189> even<00:17:07.189> if<00:17:07.310> it's 00:17:07.420 --> 00:17:07.430 align:start position:0% machine learning model even if it's 00:17:07.430 --> 00:17:09.220 align:start position:0% machine learning model even if it's training<00:17:07.670> on<00:17:07.910> sensitive<00:17:08.209> data<00:17:08.480> there<00:17:09.050> are 00:17:09.220 --> 00:17:09.230 align:start position:0% training on sensitive data there are 00:17:09.230 --> 00:17:11.170 align:start position:0% training on sensitive data there are provable<00:17:09.740> guarantees<00:17:10.280> that<00:17:10.310> the<00:17:10.699> output 00:17:11.170 --> 00:17:11.180 align:start position:0% provable guarantees that the output 00:17:11.180 --> 00:17:12.460 align:start position:0% provable guarantees that the output actually<00:17:11.510> doesn't<00:17:11.990> leak<00:17:12.140> any<00:17:12.380> information 00:17:12.460 --> 00:17:12.470 align:start position:0% actually doesn't leak any information 00:17:12.470 --> 00:17:15.819 align:start position:0% actually doesn't leak any information about<00:17:13.189> inputs<00:17:13.760> and<00:17:14.660> so<00:17:14.900> essentially<00:17:15.589> what 00:17:15.819 --> 00:17:15.829 align:start position:0% about inputs and so essentially what 00:17:15.829 --> 00:17:18.010 align:start position:0% about inputs and so essentially what this<00:17:15.860> means<00:17:15.980> is<00:17:16.430> that<00:17:16.569> developers<00:17:17.569> can 00:17:18.010 --> 00:17:18.020 align:start position:0% this means is that developers can 00:17:18.020 --> 00:17:19.750 align:start position:0% this means is that developers can demonstrate<00:17:18.319> to<00:17:18.709> users<00:17:19.160> because<00:17:19.459> smart 00:17:19.750 --> 00:17:19.760 align:start position:0% demonstrate to users because smart 00:17:19.760 --> 00:17:21.610 align:start position:0% demonstrate to users because smart contract<00:17:20.180> code<00:17:20.300> is<00:17:20.569> auditable<00:17:21.079> they<00:17:21.470> can 00:17:21.610 --> 00:17:21.620 align:start position:0% contract code is auditable they can 00:17:21.620 --> 00:17:23.949 align:start position:0% contract code is auditable they can actually<00:17:21.890> prove<00:17:22.130> to<00:17:22.400> users<00:17:22.850> that<00:17:23.270> they're<00:17:23.810> not 00:17:23.949 --> 00:17:23.959 align:start position:0% actually prove to users that they're not 00:17:23.959 --> 00:17:26.590 align:start position:0% actually prove to users that they're not violating<00:17:24.530> privacy<00:17:24.680> the<00:17:25.610> user<00:17:25.910> can<00:17:26.360> verify 00:17:26.590 --> 00:17:26.600 align:start position:0% violating privacy the user can verify 00:17:26.600 --> 00:17:28.270 align:start position:0% violating privacy the user can verify that<00:17:26.839> their<00:17:27.319> privacy<00:17:27.620> is<00:17:27.770> not<00:17:27.890> being<00:17:28.100> violated 00:17:28.270 --> 00:17:28.280 align:start position:0% that their privacy is not being violated 00:17:28.280 --> 00:17:30.730 align:start position:0% that their privacy is not being violated this<00:17:28.730> is<00:17:28.910> really<00:17:29.570> an<00:17:29.630> unprecedented<00:17:30.020> property 00:17:30.730 --> 00:17:30.740 align:start position:0% this is really an unprecedented property 00:17:30.740 --> 00:17:32.140 align:start position:0% this is really an unprecedented property this<00:17:30.860> is<00:17:30.980> something<00:17:31.250> that<00:17:31.340> you<00:17:31.430> don't<00:17:31.610> have<00:17:31.850> in 00:17:32.140 --> 00:17:32.150 align:start position:0% this is something that you don't have in 00:17:32.150 --> 00:17:33.730 align:start position:0% this is something that you don't have in traditional<00:17:32.540> cloud<00:17:32.750> applications<00:17:33.380> the<00:17:33.530> fact 00:17:33.730 --> 00:17:33.740 align:start position:0% traditional cloud applications the fact 00:17:33.740 --> 00:17:35.470 align:start position:0% traditional cloud applications the fact that<00:17:33.830> the<00:17:34.280> user<00:17:34.520> doesn't<00:17:34.820> need<00:17:35.030> to<00:17:35.180> take<00:17:35.330> the 00:17:35.470 --> 00:17:35.480 align:start position:0% that the user doesn't need to take the 00:17:35.480 --> 00:17:37.810 align:start position:0% that the user doesn't need to take the developer's<00:17:35.930> word<00:17:36.140> for<00:17:36.410> it<00:17:36.530> they<00:17:37.070> can<00:17:37.430> prove 00:17:37.810 --> 00:17:37.820 align:start position:0% developer's word for it they can prove 00:17:37.820 --> 00:17:39.850 align:start position:0% developer's word for it they can prove to<00:17:38.030> themselves<00:17:38.210> that<00:17:38.690> their<00:17:39.290> privacy<00:17:39.650> is<00:17:39.830> not 00:17:39.850 --> 00:17:39.860 align:start position:0% to themselves that their privacy is not 00:17:39.860 --> 00:17:41.650 align:start position:0% to themselves that their privacy is not being<00:17:40.220> leaked<00:17:40.460> and<00:17:40.640> we<00:17:40.730> don't<00:17:40.880> need<00:17:41.000> terms<00:17:41.480> of 00:17:41.650 --> 00:17:41.660 align:start position:0% being leaked and we don't need terms of 00:17:41.660 --> 00:17:43.450 align:start position:0% being leaked and we don't need terms of service<00:17:42.050> we<00:17:42.200> don't<00:17:42.380> need<00:17:42.470> privacy<00:17:42.950> policies 00:17:43.450 --> 00:17:43.460 align:start position:0% service we don't need privacy policies 00:17:43.460 --> 00:17:46.870 align:start position:0% service we don't need privacy policies everything<00:17:44.270> just<00:17:44.510> happens<00:17:44.870> automatically<00:17:45.550> so 00:17:46.870 --> 00:17:46.880 align:start position:0% everything just happens automatically so 00:17:46.880 --> 00:17:48.040 align:start position:0% everything just happens automatically so example<00:17:47.180> if<00:17:47.240> you<00:17:47.330> wanted<00:17:47.510> to<00:17:47.600> build<00:17:47.720> a<00:17:47.870> data 00:17:48.040 --> 00:17:48.050 align:start position:0% example if you wanted to build a data 00:17:48.050 --> 00:17:50.020 align:start position:0% example if you wanted to build a data market<00:17:48.440> you<00:17:48.950> would<00:17:49.100> be<00:17:49.190> able<00:17:49.280> to<00:17:49.370> use<00:17:49.550> this<00:17:49.700> SDK 00:17:50.020 --> 00:17:50.030 align:start position:0% market you would be able to use this SDK 00:17:50.030 --> 00:17:52.870 align:start position:0% market you would be able to use this SDK build<00:17:50.930> a<00:17:51.020> machine<00:17:51.320> learning<00:17:51.680> pipeline<00:17:52.610> and 00:17:52.870 --> 00:17:52.880 align:start position:0% build a machine learning pipeline and 00:17:52.880 --> 00:17:55.090 align:start position:0% build a machine learning pipeline and have<00:17:53.630> users<00:17:54.080> that<00:17:54.110> interact<00:17:54.710> with<00:17:54.920> that<00:17:55.040> data 00:17:55.090 --> 00:17:55.100 align:start position:0% have users that interact with that data 00:17:55.100 --> 00:17:58.330 align:start position:0% have users that interact with that data market<00:17:55.700> know<00:17:56.420> that<00:17:56.900> there's<00:17:57.350> no<00:17:57.560> way<00:17:57.740> even<00:17:58.190> if 00:17:58.330 --> 00:17:58.340 align:start position:0% market know that there's no way even if 00:17:58.340 --> 00:18:00.120 align:start position:0% market know that there's no way even if you<00:17:58.430> wanted<00:17:58.730> to<00:17:58.790> to<00:17:59.330> violate<00:17:59.720> their<00:17:59.870> privacy 00:18:00.120 --> 00:18:00.130 align:start position:0% you wanted to to violate their privacy 00:18:00.130 --> 00:18:03.040 align:start position:0% you wanted to to violate their privacy so<00:18:01.130> in<00:18:01.460> the<00:18:01.580> future<00:18:01.790> as<00:18:02.090> privacy<00:18:02.540> becomes<00:18:02.870> more 00:18:03.040 --> 00:18:03.050 align:start position:0% so in the future as privacy becomes more 00:18:03.050 --> 00:18:04.840 align:start position:0% so in the future as privacy becomes more and<00:18:03.170> more<00:18:03.290> important<00:18:03.650> for<00:18:03.680> users<00:18:03.920> features 00:18:04.840 --> 00:18:04.850 align:start position:0% and more important for users features 00:18:04.850 --> 00:18:06.130 align:start position:0% and more important for users features like<00:18:05.060> this<00:18:05.240> I<00:18:05.420> think<00:18:05.480> will<00:18:05.720> be<00:18:05.810> a<00:18:05.840> huge 00:18:06.130 --> 00:18:06.140 align:start position:0% like this I think will be a huge 00:18:06.140 --> 00:18:07.870 align:start position:0% like this I think will be a huge competitive<00:18:06.680> advantage<00:18:06.770> for<00:18:07.280> applications 00:18:07.870 --> 00:18:07.880 align:start position:0% competitive advantage for applications 00:18:07.880 --> 00:18:09.670 align:start position:0% competitive advantage for applications that<00:18:07.970> are<00:18:08.060> moving<00:18:08.420> to<00:18:08.510> blockchain<00:18:08.990> versus 00:18:09.670 --> 00:18:09.680 align:start position:0% that are moving to blockchain versus 00:18:09.680 --> 00:18:12.430 align:start position:0% that are moving to blockchain versus traditional<00:18:09.830> cloud<00:18:10.250> applications<00:18:11.110> okay<00:18:12.110> so 00:18:12.430 --> 00:18:12.440 align:start position:0% traditional cloud applications okay so 00:18:12.440 --> 00:18:13.570 align:start position:0% traditional cloud applications okay so that's<00:18:12.620> a<00:18:12.710> glimpse<00:18:13.010> of<00:18:13.130> some<00:18:13.400> of<00:18:13.430> the 00:18:13.570 --> 00:18:13.580 align:start position:0% that's a glimpse of some of the 00:18:13.580 --> 00:18:15.130 align:start position:0% that's a glimpse of some of the solutions<00:18:14.060> at<00:18:14.240> the<00:18:14.390> application<00:18:14.960> layer 00:18:15.130 --> 00:18:15.140 align:start position:0% solutions at the application layer 00:18:15.140 --> 00:18:17.100 align:start position:0% solutions at the application layer finally<00:18:15.860> I<00:18:15.890> want<00:18:16.190> to<00:18:16.250> talk<00:18:16.340> briefly<00:18:16.490> about 00:18:17.100 --> 00:18:17.110 align:start position:0% finally I want to talk briefly about 00:18:17.110 --> 00:18:20.440 align:start position:0% finally I want to talk briefly about scalability<00:18:18.110> and<00:18:18.920> in<00:18:18.980> particular<00:18:19.100> how<00:18:19.520> we<00:18:19.580> can 00:18:20.440 --> 00:18:20.450 align:start position:0% scalability and in particular how we can 00:18:20.450 --> 00:18:22.690 align:start position:0% scalability and in particular how we can scale<00:18:20.570> to<00:18:20.750> more<00:18:21.170> complex<00:18:21.650> types<00:18:21.950> of<00:18:22.160> workloads 00:18:22.690 --> 00:18:22.700 align:start position:0% scale to more complex types of workloads 00:18:22.700 --> 00:18:24.820 align:start position:0% scale to more complex types of workloads so<00:18:22.910> scalability<00:18:23.750> is<00:18:23.810> a<00:18:23.840> complex<00:18:24.200> subject<00:18:24.440> I 00:18:24.820 --> 00:18:24.830 align:start position:0% so scalability is a complex subject I 00:18:24.830 --> 00:18:26.350 align:start position:0% so scalability is a complex subject I won't<00:18:25.040> go<00:18:25.250> into<00:18:25.430> full<00:18:25.640> depth<00:18:25.880> in<00:18:26.030> this<00:18:26.120> but 00:18:26.350 --> 00:18:26.360 align:start position:0% won't go into full depth in this but 00:18:26.360 --> 00:18:28.090 align:start position:0% won't go into full depth in this but I'll<00:18:26.660> kind<00:18:26.930> of<00:18:26.960> sketch<00:18:27.230> out<00:18:27.470> at<00:18:27.830> least<00:18:27.980> the 00:18:28.090 --> 00:18:28.100 align:start position:0% I'll kind of sketch out at least the 00:18:28.100 --> 00:18:33.030 align:start position:0% I'll kind of sketch out at least the intuition<00:18:28.640> of<00:18:29.110> some<00:18:30.110> of<00:18:30.230> our<00:18:30.370> architecture<00:18:31.690> so 00:18:33.030 --> 00:18:33.040 align:start position:0% intuition of some of our architecture so 00:18:33.040 --> 00:18:35.170 align:start position:0% intuition of some of our architecture so if<00:18:34.040> we<00:18:34.160> look<00:18:34.310> at<00:18:34.400> why<00:18:34.490> scalability<00:18:35.120> is 00:18:35.170 --> 00:18:35.180 align:start position:0% if we look at why scalability is 00:18:35.180 --> 00:18:37.990 align:start position:0% if we look at why scalability is important<00:18:35.600> as<00:18:36.130> these<00:18:37.130> smart<00:18:37.640> contract 00:18:37.990 --> 00:18:38.000 align:start position:0% important as these smart contract 00:18:38.000 --> 00:18:40.120 align:start position:0% important as these smart contract platforms<00:18:38.540> continue<00:18:39.320> to<00:18:39.410> evolve<00:18:39.620> people<00:18:40.040> are 00:18:40.120 --> 00:18:40.130 align:start position:0% platforms continue to evolve people are 00:18:40.130 --> 00:18:41.500 align:start position:0% platforms continue to evolve people are building<00:18:40.280> more<00:18:40.700> and<00:18:40.850> more<00:18:41.030> complex 00:18:41.500 --> 00:18:41.510 align:start position:0% building more and more complex 00:18:41.510 --> 00:18:44.980 align:start position:0% building more and more complex applications<00:18:42.350> and<00:18:42.650> as<00:18:43.460> the<00:18:44.240> applications<00:18:44.810> get 00:18:44.980 --> 00:18:44.990 align:start position:0% applications and as the applications get 00:18:44.990 --> 00:18:47.080 align:start position:0% applications and as the applications get more<00:18:45.170> complex<00:18:45.730> congestion<00:18:46.730> on<00:18:46.850> these 00:18:47.080 --> 00:18:47.090 align:start position:0% more complex congestion on these 00:18:47.090 --> 00:18:49.060 align:start position:0% more complex congestion on these networks<00:18:47.660> increases<00:18:48.440> so<00:18:48.680> I'm<00:18:48.950> sure 00:18:49.060 --> 00:18:49.070 align:start position:0% networks increases so I'm sure 00:18:49.070 --> 00:18:50.410 align:start position:0% networks increases so I'm sure everyone's<00:18:49.370> familiar<00:18:49.460> with<00:18:49.700> crypto<00:18:50.120> kitties 00:18:50.410 --> 00:18:50.420 align:start position:0% everyone's familiar with crypto kitties 00:18:50.420 --> 00:18:53.470 align:start position:0% everyone's familiar with crypto kitties when<00:18:50.930> it<00:18:51.050> became<00:18:51.260> popular<00:18:51.740> last<00:18:51.980> year<00:18:52.210> it<00:18:53.210> you 00:18:53.470 --> 00:18:53.480 align:start position:0% when it became popular last year it you 00:18:53.480 --> 00:18:55.030 align:start position:0% when it became popular last year it you know<00:18:53.570> it<00:18:53.690> slowed<00:18:53.990> down<00:18:54.140> the<00:18:54.290> entire<00:18:54.500> aetherium 00:18:55.030 --> 00:18:55.040 align:start position:0% know it slowed down the entire aetherium 00:18:55.040 --> 00:18:56.860 align:start position:0% know it slowed down the entire aetherium network<00:18:55.370> and<00:18:55.550> it<00:18:55.640> caused<00:18:55.850> transaction<00:18:56.720> fees 00:18:56.860 --> 00:18:56.870 align:start position:0% network and it caused transaction fees 00:18:56.870 --> 00:18:59.170 align:start position:0% network and it caused transaction fees to<00:18:57.080> go<00:18:57.230> through<00:18:57.770> the<00:18:57.860> roof<00:18:57.980> so<00:18:58.430> if<00:18:58.670> we<00:18:58.940> kind<00:18:59.120> of 00:18:59.170 --> 00:18:59.180 align:start position:0% to go through the roof so if we kind of 00:18:59.180 --> 00:19:01.210 align:start position:0% to go through the roof so if we kind of extrapolate<00:18:59.540> to<00:18:59.870> the<00:18:59.960> future<00:19:00.290> where<00:19:00.590> what<00:19:01.100> we 00:19:01.210 --> 00:19:01.220 align:start position:0% extrapolate to the future where what we 00:19:01.220 --> 00:19:02.860 align:start position:0% extrapolate to the future where what we want<00:19:01.400> to<00:19:01.490> build<00:19:01.610> is<00:19:01.970> not<00:19:02.120> just<00:19:02.480> the<00:19:02.690> next 00:19:02.860 --> 00:19:02.870 align:start position:0% want to build is not just the next 00:19:02.870 --> 00:19:03.640 align:start position:0% want to build is not just the next crypto<00:19:03.200> kitties 00:19:03.640 --> 00:19:03.650 align:start position:0% crypto kitties 00:19:03.650 --> 00:19:06.700 align:start position:0% crypto kitties but<00:19:03.980> rather<00:19:04.190> a<00:19:04.550> new<00:19:05.060> paradigm<00:19:06.020> for<00:19:06.410> data 00:19:06.700 --> 00:19:06.710 align:start position:0% but rather a new paradigm for data 00:19:06.710 --> 00:19:08.590 align:start position:0% but rather a new paradigm for data sharing<00:19:06.830> and<00:19:07.370> doing<00:19:07.760> machine<00:19:08.060> learning<00:19:08.120> on 00:19:08.590 --> 00:19:08.600 align:start position:0% sharing and doing machine learning on 00:19:08.600 --> 00:19:11.260 align:start position:0% sharing and doing machine learning on sensitive<00:19:09.590> data<00:19:09.770> these<00:19:10.520> applications<00:19:11.150> are 00:19:11.260 --> 00:19:11.270 align:start position:0% sensitive data these applications are 00:19:11.270 --> 00:19:13.360 align:start position:0% sensitive data these applications are significantly<00:19:11.960> more<00:19:12.200> complex<00:19:12.620> than<00:19:12.980> anything 00:19:13.360 --> 00:19:13.370 align:start position:0% significantly more complex than anything 00:19:13.370 --> 00:19:15.670 align:start position:0% significantly more complex than anything that<00:19:13.850> is<00:19:14.030> being<00:19:14.300> deployed<00:19:14.690> today<00:19:15.020> and<00:19:15.260> that 00:19:15.670 --> 00:19:15.680 align:start position:0% that is being deployed today and that 00:19:15.680 --> 00:19:17.380 align:start position:0% that is being deployed today and that means<00:19:15.890> we<00:19:16.070> need<00:19:16.190> a<00:19:16.250> new<00:19:16.430> architecture<00:19:17.120> that<00:19:17.300> it 00:19:17.380 --> 00:19:17.390 align:start position:0% means we need a new architecture that it 00:19:17.390 --> 00:19:18.670 align:start position:0% means we need a new architecture that it can<00:19:17.510> accommodate<00:19:17.840> these<00:19:18.260> sorts<00:19:18.590> of 00:19:18.670 --> 00:19:18.680 align:start position:0% can accommodate these sorts of 00:19:18.680 --> 00:19:21.280 align:start position:0% can accommodate these sorts of applications<00:19:19.510> now<00:19:20.510> I<00:19:20.540> want<00:19:20.810> to<00:19:20.870> emphasize 00:19:21.280 --> 00:19:21.290 align:start position:0% applications now I want to emphasize 00:19:21.290 --> 00:19:24.010 align:start position:0% applications now I want to emphasize that<00:19:21.940> skill<00:19:22.940> build<00:19:23.120> is<00:19:23.210> more<00:19:23.420> than<00:19:23.600> just<00:19:23.870> high 00:19:24.010 --> 00:19:24.020 align:start position:0% that skill build is more than just high 00:19:24.020 --> 00:19:26.590 align:start position:0% that skill build is more than just high TPS<00:19:24.500> so<00:19:24.770> when<00:19:25.190> when<00:19:25.520> most<00:19:25.790> platforms<00:19:26.330> talk 00:19:26.590 --> 00:19:26.600 align:start position:0% TPS so when when most platforms talk 00:19:26.600 --> 00:19:28.120 align:start position:0% TPS so when when most platforms talk about<00:19:26.870> scalability<00:19:27.230> usually<00:19:27.830> what<00:19:27.980> they're 00:19:28.120 --> 00:19:28.130 align:start position:0% about scalability usually what they're 00:19:28.130 --> 00:19:30.160 align:start position:0% about scalability usually what they're referring<00:19:28.460> to<00:19:28.730> is<00:19:29.150> the<00:19:29.840> number<00:19:30.080> of 00:19:30.160 --> 00:19:30.170 align:start position:0% referring to is the number of 00:19:30.170 --> 00:19:31.720 align:start position:0% referring to is the number of transactions<00:19:30.740> that<00:19:30.860> they<00:19:30.980> can<00:19:31.130> process<00:19:31.340> in 00:19:31.720 --> 00:19:31.730 align:start position:0% transactions that they can process in 00:19:31.730 --> 00:19:33.790 align:start position:0% transactions that they can process in any<00:19:32.180> given<00:19:32.510> time<00:19:32.660> period<00:19:32.720> and<00:19:33.110> this<00:19:33.470> is<00:19:33.650> an 00:19:33.790 --> 00:19:33.800 align:start position:0% any given time period and this is an 00:19:33.800 --> 00:19:35.320 align:start position:0% any given time period and this is an important<00:19:34.220> metric<00:19:34.400> but<00:19:34.760> it<00:19:34.910> actually<00:19:35.180> doesn't 00:19:35.320 --> 00:19:35.330 align:start position:0% important metric but it actually doesn't 00:19:35.330 --> 00:19:38.730 align:start position:0% important metric but it actually doesn't capture<00:19:35.780> the<00:19:36.080> full<00:19:36.770> story<00:19:37.300> there<00:19:38.300> are<00:19:38.330> a 00:19:38.730 --> 00:19:38.740 align:start position:0% capture the full story there are a 00:19:38.740 --> 00:19:41.320 align:start position:0% capture the full story there are a number<00:19:39.740> of<00:19:39.890> variables<00:19:40.370> that<00:19:40.460> determine<00:19:40.790> you 00:19:41.320 --> 00:19:41.330 align:start position:0% number of variables that determine you 00:19:41.330 --> 00:19:43.360 align:start position:0% number of variables that determine you know<00:19:41.390> how<00:19:41.540> well<00:19:41.750> a<00:19:41.780> platform<00:19:42.290> performs<00:19:42.740> in 00:19:43.360 --> 00:19:43.370 align:start position:0% know how well a platform performs in 00:19:43.370 --> 00:19:45.010 align:start position:0% know how well a platform performs in practice<00:19:43.880> and<00:19:44.060> one<00:19:44.270> of<00:19:44.360> the<00:19:44.420> most<00:19:44.510> important 00:19:45.010 --> 00:19:45.020 align:start position:0% practice and one of the most important 00:19:45.020 --> 00:19:46.810 align:start position:0% practice and one of the most important of<00:19:45.110> them<00:19:45.260> is<00:19:45.290> what<00:19:46.010> is<00:19:46.100> the<00:19:46.190> workload<00:19:46.580> look 00:19:46.810 --> 00:19:46.820 align:start position:0% of them is what is the workload look 00:19:46.820 --> 00:19:48.730 align:start position:0% of them is what is the workload look like<00:19:46.970> how<00:19:47.150> complex<00:19:47.780> are<00:19:48.020> the<00:19:48.140> computations 00:19:48.730 --> 00:19:48.740 align:start position:0% like how complex are the computations 00:19:48.740 --> 00:19:50.050 align:start position:0% like how complex are the computations there's<00:19:48.920> a<00:19:49.010> huge<00:19:49.190> difference<00:19:49.550> between<00:19:49.700> a 00:19:50.050 --> 00:19:50.060 align:start position:0% there's a huge difference between a 00:19:50.060 --> 00:19:52.030 align:start position:0% there's a huge difference between a platform<00:19:50.780> that<00:19:50.900> can<00:19:51.020> process<00:19:51.260> you<00:19:51.920> know 00:19:52.030 --> 00:19:52.040 align:start position:0% platform that can process you know 00:19:52.040 --> 00:19:54.400 align:start position:0% platform that can process you know thousands<00:19:52.550> of<00:19:52.700> very<00:19:53.420> simple<00:19:53.840> transactions 00:19:54.400 --> 00:19:54.410 align:start position:0% thousands of very simple transactions 00:19:54.410 --> 00:19:56.710 align:start position:0% thousands of very simple transactions like<00:19:54.530> payments<00:19:55.010> but<00:19:55.460> completely<00:19:55.940> fails<00:19:56.270> to 00:19:56.710 --> 00:19:56.720 align:start position:0% like payments but completely fails to 00:19:56.720 --> 00:19:59.350 align:start position:0% like payments but completely fails to process<00:19:57.260> anything<00:19:57.500> that's<00:19:58.250> even<00:19:59.030> moderately 00:19:59.350 --> 00:19:59.360 align:start position:0% process anything that's even moderately 00:19:59.360 --> 00:20:01.090 align:start position:0% process anything that's even moderately more<00:19:59.570> complex<00:19:59.960> than<00:20:00.080> the 00:20:01.090 --> 00:20:01.100 align:start position:0% more complex than the 00:20:01.100 --> 00:20:02.770 align:start position:0% more complex than the and<00:20:01.250> so<00:20:01.370> we<00:20:01.550> architected<00:20:01.850> in<00:20:02.270> our<00:20:02.390> system<00:20:02.720> our 00:20:02.770 --> 00:20:02.780 align:start position:0% and so we architected in our system our 00:20:02.780 --> 00:20:04.240 align:start position:0% and so we architected in our system our system<00:20:03.200> specifically<00:20:03.710> to<00:20:03.980> provide 00:20:04.240 --> 00:20:04.250 align:start position:0% system specifically to provide 00:20:04.250 --> 00:20:06.850 align:start position:0% system specifically to provide scalability<00:20:05.000> for<00:20:05.030> complex<00:20:05.990> applications<00:20:06.620> and 00:20:06.850 --> 00:20:06.860 align:start position:0% scalability for complex applications and 00:20:06.860 --> 00:20:09.070 align:start position:0% scalability for complex applications and those<00:20:07.070> that<00:20:07.340> have<00:20:07.550> dependence<00:20:08.540> on<00:20:08.750> other 00:20:09.070 --> 00:20:09.080 align:start position:0% those that have dependence on other 00:20:09.080 --> 00:20:11.350 align:start position:0% those that have dependence on other smart<00:20:09.410> contracts<00:20:09.860> and<00:20:10.700> so<00:20:10.820> this<00:20:10.970> is<00:20:11.090> actually 00:20:11.350 --> 00:20:11.360 align:start position:0% smart contracts and so this is actually 00:20:11.360 --> 00:20:14.050 align:start position:0% smart contracts and so this is actually an<00:20:11.480> architectural<00:20:12.050> solution<00:20:12.500> and<00:20:13.400> to<00:20:13.760> sketch 00:20:14.050 --> 00:20:14.060 align:start position:0% an architectural solution and to sketch 00:20:14.060 --> 00:20:16.210 align:start position:0% an architectural solution and to sketch why<00:20:14.390> this<00:20:14.450> is<00:20:14.870> necessary<00:20:15.020> if<00:20:15.740> you<00:20:15.830> look<00:20:16.040> at<00:20:16.130> the 00:20:16.210 --> 00:20:16.220 align:start position:0% why this is necessary if you look at the 00:20:16.220 --> 00:20:18.580 align:start position:0% why this is necessary if you look at the design<00:20:16.520> for<00:20:16.910> most<00:20:17.420> existing<00:20:17.720> platforms 00:20:18.580 --> 00:20:18.590 align:start position:0% design for most existing platforms 00:20:18.590 --> 00:20:21.460 align:start position:0% design for most existing platforms the<00:20:18.920> reason<00:20:19.370> these<00:20:19.730> platforms<00:20:20.330> don't<00:20:21.110> work 00:20:21.460 --> 00:20:21.470 align:start position:0% the reason these platforms don't work 00:20:21.470 --> 00:20:24.670 align:start position:0% the reason these platforms don't work well<00:20:21.740> for<00:20:22.450> complex<00:20:23.450> transactions<00:20:24.170> is<00:20:24.350> the 00:20:24.670 --> 00:20:24.680 align:start position:0% well for complex transactions is the 00:20:24.680 --> 00:20:27.820 align:start position:0% well for complex transactions is the fact<00:20:24.890> that<00:20:25.570> every<00:20:26.570> node<00:20:26.840> actually<00:20:27.170> runs<00:20:27.620> the 00:20:27.820 --> 00:20:27.830 align:start position:0% fact that every node actually runs the 00:20:27.830 --> 00:20:29.620 align:start position:0% fact that every node actually runs the same<00:20:28.010> computation<00:20:28.910> so<00:20:29.090> that<00:20:29.210> means<00:20:29.390> there's 00:20:29.620 --> 00:20:29.630 align:start position:0% same computation so that means there's 00:20:29.630 --> 00:20:32.020 align:start position:0% same computation so that means there's an<00:20:29.840> enormous<00:20:30.080> amount<00:20:30.440> of<00:20:30.560> redundant<00:20:31.010> work<00:20:31.160> and 00:20:32.020 --> 00:20:32.030 align:start position:0% an enormous amount of redundant work and 00:20:32.030 --> 00:20:34.660 align:start position:0% an enormous amount of redundant work and there's<00:20:32.270> no<00:20:32.420> parallelism<00:20:33.190> also<00:20:34.190> the<00:20:34.430> fact 00:20:34.660 --> 00:20:34.670 align:start position:0% there's no parallelism also the fact 00:20:34.670 --> 00:20:37.450 align:start position:0% there's no parallelism also the fact that<00:20:34.820> every<00:20:35.270> node<00:20:35.510> has<00:20:35.540> to<00:20:36.110> do<00:20:36.260> both<00:20:36.470> execution 00:20:37.450 --> 00:20:37.460 align:start position:0% that every node has to do both execution 00:20:37.460 --> 00:20:39.880 align:start position:0% that every node has to do both execution that<00:20:37.940> is<00:20:38.090> to<00:20:38.270> run<00:20:38.480> the<00:20:38.630> code<00:20:38.840> as<00:20:39.020> well<00:20:39.620> as 00:20:39.880 --> 00:20:39.890 align:start position:0% that is to run the code as well as 00:20:39.890 --> 00:20:43.060 align:start position:0% that is to run the code as well as validating<00:20:40.730> transactions<00:20:41.510> and<00:20:42.070> maintaining 00:20:43.060 --> 00:20:43.070 align:start position:0% validating transactions and maintaining 00:20:43.070 --> 00:20:45.490 align:start position:0% validating transactions and maintaining the<00:20:43.160> ledger<00:20:43.370> this<00:20:44.000> means<00:20:44.330> that<00:20:44.690> if<00:20:44.930> there's<00:20:45.440> a 00:20:45.490 --> 00:20:45.500 align:start position:0% the ledger this means that if there's a 00:20:45.500 --> 00:20:47.860 align:start position:0% the ledger this means that if there's a slow<00:20:45.860> transaction<00:20:46.640> like<00:20:46.970> a<00:20:47.240> crypto<00:20:47.540> kiddies 00:20:47.860 --> 00:20:47.870 align:start position:0% slow transaction like a crypto kiddies 00:20:47.870 --> 00:20:50.650 align:start position:0% slow transaction like a crypto kiddies breeding<00:20:48.410> transaction<00:20:48.950> that<00:20:49.820> has<00:20:50.090> to<00:20:50.210> run<00:20:50.420> and 00:20:50.650 --> 00:20:50.660 align:start position:0% breeding transaction that has to run and 00:20:50.660 --> 00:20:52.720 align:start position:0% breeding transaction that has to run and it<00:20:50.750> will<00:20:50.840> prevent<00:20:51.290> even<00:20:51.830> faster<00:20:52.190> transactions 00:20:52.720 --> 00:20:52.730 align:start position:0% it will prevent even faster transactions 00:20:52.730 --> 00:20:54.340 align:start position:0% it will prevent even faster transactions that<00:20:52.880> could<00:20:53.090> have<00:20:53.240> confirmed<00:20:53.570> immediately<00:20:54.140> if 00:20:54.340 --> 00:20:54.350 align:start position:0% that could have confirmed immediately if 00:20:54.350 --> 00:20:56.110 align:start position:0% that could have confirmed immediately if the<00:20:54.740> machine<00:20:55.010> was<00:20:55.040> able<00:20:55.460> to<00:20:55.580> validate<00:20:55.760> it 00:20:56.110 --> 00:20:56.120 align:start position:0% the machine was able to validate it 00:20:56.120 --> 00:20:58.780 align:start position:0% the machine was able to validate it those<00:20:56.630> have<00:20:56.930> to<00:20:56.960> wait<00:20:57.260> for<00:20:57.680> the<00:20:58.130> computation 00:20:58.780 --> 00:20:58.790 align:start position:0% those have to wait for the computation 00:20:58.790 --> 00:21:01.390 align:start position:0% those have to wait for the computation of<00:20:58.940> the<00:20:59.060> slower<00:20:59.300> transaction<00:20:59.990> to<00:21:00.380> finish<00:21:00.680> so 00:21:01.390 --> 00:21:01.400 align:start position:0% of the slower transaction to finish so 00:21:01.400 --> 00:21:04.150 align:start position:0% of the slower transaction to finish so this<00:21:02.210> means<00:21:02.480> fundamentally<00:21:03.350> that<00:21:03.650> slow 00:21:04.150 --> 00:21:04.160 align:start position:0% this means fundamentally that slow 00:21:04.160 --> 00:21:06.280 align:start position:0% this means fundamentally that slow transactions<00:21:04.790> will<00:21:04.970> cause<00:21:05.210> congestion<00:21:05.870> for 00:21:06.280 --> 00:21:06.290 align:start position:0% transactions will cause congestion for 00:21:06.290 --> 00:21:07.720 align:start position:0% transactions will cause congestion for faster<00:21:06.620> transactions<00:21:07.190> and<00:21:07.340> this<00:21:07.430> is<00:21:07.550> true 00:21:07.720 --> 00:21:07.730 align:start position:0% faster transactions and this is true 00:21:07.730 --> 00:21:10.450 align:start position:0% faster transactions and this is true even<00:21:07.880> for<00:21:08.300> typical<00:21:09.170> scaling<00:21:09.890> solutions<00:21:10.310> like 00:21:10.450 --> 00:21:10.460 align:start position:0% even for typical scaling solutions like 00:21:10.460 --> 00:21:12.220 align:start position:0% even for typical scaling solutions like sharding<00:21:10.910> a<00:21:11.030> simple<00:21:11.390> shorting<00:21:11.750> solution 00:21:12.220 --> 00:21:12.230 align:start position:0% sharding a simple shorting solution 00:21:12.230 --> 00:21:15.100 align:start position:0% sharding a simple shorting solution simply<00:21:12.940> partitions<00:21:13.940> the<00:21:14.300> network<00:21:14.660> into 00:21:15.100 --> 00:21:15.110 align:start position:0% simply partitions the network into 00:21:15.110 --> 00:21:17.140 align:start position:0% simply partitions the network into multiple<00:21:15.620> groups<00:21:15.830> of<00:21:16.340> nodes<00:21:16.580> that<00:21:16.820> all<00:21:16.970> have 00:21:17.140 --> 00:21:17.150 align:start position:0% multiple groups of nodes that all have 00:21:17.150 --> 00:21:19.450 align:start position:0% multiple groups of nodes that all have the<00:21:17.300> same<00:21:17.480> property<00:21:17.930> so<00:21:18.170> even<00:21:18.920> with<00:21:19.070> simple 00:21:19.450 --> 00:21:19.460 align:start position:0% the same property so even with simple 00:21:19.460 --> 00:21:21.700 align:start position:0% the same property so even with simple shorting<00:21:20.000> you<00:21:20.420> still<00:21:20.750> have<00:21:20.960> this<00:21:21.170> congestion 00:21:21.700 --> 00:21:21.710 align:start position:0% shorting you still have this congestion 00:21:21.710 --> 00:21:23.650 align:start position:0% shorting you still have this congestion issue<00:21:21.860> for<00:21:22.430> transactions<00:21:23.090> you<00:21:23.390> know<00:21:23.480> within 00:21:23.650 --> 00:21:23.660 align:start position:0% issue for transactions you know within 00:21:23.660 --> 00:21:25.090 align:start position:0% issue for transactions you know within the<00:21:23.780> same<00:21:23.990> shard<00:21:24.260> so<00:21:24.800> we<00:21:24.920> need<00:21:25.070> a 00:21:25.090 --> 00:21:25.100 align:start position:0% the same shard so we need a 00:21:25.100 --> 00:21:27.220 align:start position:0% the same shard so we need a fundamentally<00:21:25.700> new<00:21:25.730> approach<00:21:26.330> one<00:21:26.870> of<00:21:27.050> the 00:21:27.220 --> 00:21:27.230 align:start position:0% fundamentally new approach one of the 00:21:27.230 --> 00:21:29.680 align:start position:0% fundamentally new approach one of the main<00:21:27.830> intuitions<00:21:28.490> behind<00:21:28.910> our<00:21:29.060> architecture 00:21:29.680 --> 00:21:29.690 align:start position:0% main intuitions behind our architecture 00:21:29.690 --> 00:21:32.530 align:start position:0% main intuitions behind our architecture is<00:21:29.810> to<00:21:30.020> separate<00:21:30.500> out<00:21:30.710> the<00:21:31.220> computation<00:21:31.880> that 00:21:32.530 --> 00:21:32.540 align:start position:0% is to separate out the computation that 00:21:32.540 --> 00:21:33.940 align:start position:0% is to separate out the computation that is<00:21:32.660> you<00:21:32.900> know<00:21:32.990> the<00:21:33.110> machines<00:21:33.410> that<00:21:33.650> actually 00:21:33.940 --> 00:21:33.950 align:start position:0% is you know the machines that actually 00:21:33.950 --> 00:21:36.700 align:start position:0% is you know the machines that actually run<00:21:34.430> the<00:21:34.610> code<00:21:34.820> separate<00:21:35.750> that<00:21:35.930> from<00:21:35.990> the 00:21:36.700 --> 00:21:36.710 align:start position:0% run the code separate that from the 00:21:36.710 --> 00:21:38.650 align:start position:0% run the code separate that from the machines<00:21:37.040> that<00:21:37.280> validate<00:21:37.730> transactions<00:21:38.420> and 00:21:38.650 --> 00:21:38.660 align:start position:0% machines that validate transactions and 00:21:38.660 --> 00:21:42.400 align:start position:0% machines that validate transactions and manage<00:21:39.530> the<00:21:39.680> ledger<00:21:39.860> and<00:21:40.160> so<00:21:40.750> one<00:21:41.750> of<00:21:41.780> the<00:21:41.990> you 00:21:42.400 --> 00:21:42.410 align:start position:0% manage the ledger and so one of the you 00:21:42.410 --> 00:21:43.600 align:start position:0% manage the ledger and so one of the you know<00:21:42.500> one<00:21:42.740> of<00:21:42.770> the<00:21:42.890> challenges<00:21:42.920> of<00:21:43.310> course<00:21:43.430> is 00:21:43.600 --> 00:21:43.610 align:start position:0% know one of the challenges of course is 00:21:43.610 --> 00:21:45.370 align:start position:0% know one of the challenges of course is how<00:21:44.000> do<00:21:44.060> you<00:21:44.180> do<00:21:44.270> this<00:21:44.390> in<00:21:44.540> a<00:21:44.600> scalable<00:21:45.050> way<00:21:45.080> how 00:21:45.370 --> 00:21:45.380 align:start position:0% how do you do this in a scalable way how 00:21:45.380 --> 00:21:47.740 align:start position:0% how do you do this in a scalable way how do<00:21:45.440> you<00:21:45.500> allow<00:21:45.920> these<00:21:46.310> nodes<00:21:46.640> to<00:21:46.940> verify<00:21:47.720> that 00:21:47.740 --> 00:21:47.750 align:start position:0% do you allow these nodes to verify that 00:21:47.750 --> 00:21:49.540 align:start position:0% do you allow these nodes to verify that their<00:21:48.080> transaction<00:21:48.710> is<00:21:48.800> correct<00:21:49.100> even<00:21:49.460> if 00:21:49.540 --> 00:21:49.550 align:start position:0% their transaction is correct even if 00:21:49.550 --> 00:21:51.190 align:start position:0% their transaction is correct even if they<00:21:49.670> can't<00:21:49.940> see<00:21:50.030> the<00:21:50.450> transaction<00:21:50.960> data 00:21:51.190 --> 00:21:51.200 align:start position:0% they can't see the transaction data 00:21:51.200 --> 00:21:53.800 align:start position:0% they can't see the transaction data right<00:21:51.830> earlier<00:21:52.340> I<00:21:52.430> showed<00:21:52.610> the<00:21:53.150> concept<00:21:53.720> of 00:21:53.800 --> 00:21:53.810 align:start position:0% right earlier I showed the concept of 00:21:53.810 --> 00:21:55.240 align:start position:0% right earlier I showed the concept of confidentiality<00:21:54.260> preserving<00:21:54.980> smart 00:21:55.240 --> 00:21:55.250 align:start position:0% confidentiality preserving smart 00:21:55.250 --> 00:21:57.280 align:start position:0% confidentiality preserving smart contracts<00:21:55.670> is<00:21:55.790> that<00:21:55.940> all<00:21:56.240> of<00:21:56.600> the<00:21:56.690> outputs<00:21:57.080> are 00:21:57.280 --> 00:21:57.290 align:start position:0% contracts is that all of the outputs are 00:21:57.290 --> 00:22:00.040 align:start position:0% contracts is that all of the outputs are secret<00:21:57.740> so<00:21:58.160> these<00:21:58.850> nodes<00:21:59.120> have<00:21:59.420> to<00:21:59.540> be<00:21:59.630> able<00:21:59.750> to 00:22:00.040 --> 00:22:00.050 align:start position:0% secret so these nodes have to be able to 00:22:00.050 --> 00:22:02.260 align:start position:0% secret so these nodes have to be able to verify<00:22:00.710> that<00:22:00.950> the<00:22:01.370> transaction<00:22:01.880> result<00:22:02.150> is 00:22:02.260 --> 00:22:02.270 align:start position:0% verify that the transaction result is 00:22:02.270 --> 00:22:03.850 align:start position:0% verify that the transaction result is correct<00:22:02.390> even<00:22:02.750> if<00:22:02.870> the<00:22:03.020> data<00:22:03.200> is<00:22:03.290> encrypted<00:22:03.410> so 00:22:03.850 --> 00:22:03.860 align:start position:0% correct even if the data is encrypted so 00:22:03.860 --> 00:22:05.170 align:start position:0% correct even if the data is encrypted so there's<00:22:04.040> a<00:22:04.070> lot<00:22:04.160> of<00:22:04.250> details<00:22:04.580> like<00:22:04.760> that<00:22:04.940> that 00:22:05.170 --> 00:22:05.180 align:start position:0% there's a lot of details like that that 00:22:05.180 --> 00:22:07.060 align:start position:0% there's a lot of details like that that need<00:22:05.210> to<00:22:05.450> be<00:22:05.540> worked<00:22:05.720> out<00:22:05.840> but<00:22:06.110> fundamentally 00:22:07.060 --> 00:22:07.070 align:start position:0% need to be worked out but fundamentally 00:22:07.070 --> 00:22:08.620 align:start position:0% need to be worked out but fundamentally the<00:22:07.250> advantage<00:22:07.700> of<00:22:07.790> this<00:22:07.910> architecture<00:22:08.540> is 00:22:08.620 --> 00:22:08.630 align:start position:0% the advantage of this architecture is 00:22:08.630 --> 00:22:10.930 align:start position:0% the advantage of this architecture is that<00:22:08.660> these<00:22:09.230> layers<00:22:09.500> can<00:22:09.800> be<00:22:09.860> scaled<00:22:10.730> and 00:22:10.930 --> 00:22:10.940 align:start position:0% that these layers can be scaled and 00:22:10.940 --> 00:22:12.880 align:start position:0% that these layers can be scaled and optimized<00:22:11.390> completely<00:22:12.110> independently<00:22:12.590> so<00:22:12.800> if 00:22:12.880 --> 00:22:12.890 align:start position:0% optimized completely independently so if 00:22:12.890 --> 00:22:14.140 align:start position:0% optimized completely independently so if there's<00:22:13.040> a<00:22:13.100> bottleneck<00:22:13.610> because 00:22:14.140 --> 00:22:14.150 align:start position:0% there's a bottleneck because 00:22:14.150 --> 00:22:16.270 align:start position:0% there's a bottleneck because compute<00:22:14.570> for<00:22:15.050> example<00:22:15.380> because<00:22:15.680> there's<00:22:16.190> a 00:22:16.270 --> 00:22:16.280 align:start position:0% compute for example because there's a 00:22:16.280 --> 00:22:18.070 align:start position:0% compute for example because there's a burst<00:22:16.580> of<00:22:16.700> transactions<00:22:17.330> that<00:22:17.540> require<00:22:17.840> more 00:22:18.070 --> 00:22:18.080 align:start position:0% burst of transactions that require more 00:22:18.080 --> 00:22:19.900 align:start position:0% burst of transactions that require more computing<00:22:18.500> power<00:22:18.560> then<00:22:19.160> it's<00:22:19.280> very<00:22:19.430> easy<00:22:19.550> to 00:22:19.900 --> 00:22:19.910 align:start position:0% computing power then it's very easy to 00:22:19.910 --> 00:22:22.360 align:start position:0% computing power then it's very easy to scale<00:22:20.330> up<00:22:20.570> just<00:22:21.170> the<00:22:21.320> computing<00:22:21.770> side<00:22:21.980> of<00:22:22.250> the 00:22:22.360 --> 00:22:22.370 align:start position:0% scale up just the computing side of the 00:22:22.370 --> 00:22:24.130 align:start position:0% scale up just the computing side of the network<00:22:22.700> and<00:22:22.850> conversely<00:22:23.750> if<00:22:23.930> there's 00:22:24.130 --> 00:22:24.140 align:start position:0% network and conversely if there's 00:22:24.140 --> 00:22:25.990 align:start position:0% network and conversely if there's congestion<00:22:24.680> during<00:22:25.130> consensus<00:22:25.760> because 00:22:25.990 --> 00:22:26.000 align:start position:0% congestion during consensus because 00:22:26.000 --> 00:22:27.130 align:start position:0% congestion during consensus because there<00:22:26.150> are<00:22:26.240> too<00:22:26.330> many<00:22:26.420> transactions<00:22:27.050> that 00:22:27.130 --> 00:22:27.140 align:start position:0% there are too many transactions that 00:22:27.140 --> 00:22:29.110 align:start position:0% there are too many transactions that need<00:22:27.350> to<00:22:27.470> be<00:22:27.590> confirmed<00:22:28.070> in<00:22:28.340> any<00:22:28.700> given<00:22:28.970> time 00:22:29.110 --> 00:22:29.120 align:start position:0% need to be confirmed in any given time 00:22:29.120 --> 00:22:31.210 align:start position:0% need to be confirmed in any given time period<00:22:29.450> you<00:22:29.780> can<00:22:29.930> add<00:22:30.110> more<00:22:30.440> workers<00:22:30.830> easily 00:22:31.210 --> 00:22:31.220 align:start position:0% period you can add more workers easily 00:22:31.220 --> 00:22:33.580 align:start position:0% period you can add more workers easily to<00:22:31.460> the<00:22:31.670> consensus<00:22:32.420> pool<00:22:32.630> and<00:22:32.840> so<00:22:33.230> you<00:22:33.290> have<00:22:33.560> a 00:22:33.580 --> 00:22:33.590 align:start position:0% to the consensus pool and so you have a 00:22:33.590 --> 00:22:36.220 align:start position:0% to the consensus pool and so you have a lot<00:22:33.800> of<00:22:33.950> flexibility<00:22:34.520> for<00:22:34.910> for<00:22:35.870> you<00:22:36.200> know 00:22:36.220 --> 00:22:36.230 align:start position:0% lot of flexibility for for you know 00:22:36.230 --> 00:22:37.870 align:start position:0% lot of flexibility for for you know performance<00:22:37.100> optimizations<00:22:37.700> and 00:22:37.870 --> 00:22:37.880 align:start position:0% performance optimizations and 00:22:37.880 --> 00:22:39.790 align:start position:0% performance optimizations and scalability<00:22:38.270> and<00:22:39.110> so<00:22:39.200> this<00:22:39.380> is<00:22:39.530> most 00:22:39.790 --> 00:22:39.800 align:start position:0% scalability and so this is most 00:22:39.800 --> 00:22:42.010 align:start position:0% scalability and so this is most beneficial<00:22:40.070> for<00:22:40.730> really<00:22:41.450> any<00:22:41.690> kind<00:22:41.900> of 00:22:42.010 --> 00:22:42.020 align:start position:0% beneficial for really any kind of 00:22:42.020 --> 00:22:43.450 align:start position:0% beneficial for really any kind of complex<00:22:42.410> application<00:22:42.980> like<00:22:43.160> machine 00:22:43.450 --> 00:22:43.460 align:start position:0% complex application like machine 00:22:43.460 --> 00:22:46.180 align:start position:0% complex application like machine learning<00:22:43.490> and<00:22:44.480> and<00:22:44.720> and<00:22:45.040> applications<00:22:46.040> with 00:22:46.180 --> 00:22:46.190 align:start position:0% learning and and and applications with 00:22:46.190 --> 00:22:47.800 align:start position:0% learning and and and applications with mass<00:22:46.340> adoption<00:22:46.850> that<00:22:46.970> required<00:22:47.300> this<00:22:47.480> sort<00:22:47.690> of 00:22:47.800 --> 00:22:47.810 align:start position:0% mass adoption that required this sort of 00:22:47.810 --> 00:22:49.720 align:start position:0% mass adoption that required this sort of flexible<00:22:48.680> scaling<00:22:49.160> that<00:22:49.280> you<00:22:49.370> don't<00:22:49.550> have 00:22:49.720 --> 00:22:49.730 align:start position:0% flexible scaling that you don't have 00:22:49.730 --> 00:22:52.020 align:start position:0% flexible scaling that you don't have with<00:22:50.030> these<00:22:50.240> bundled<00:22:50.990> architectures<00:22:51.590> today 00:22:52.020 --> 00:22:52.030 align:start position:0% with these bundled architectures today 00:22:52.030 --> 00:22:54.100 align:start position:0% with these bundled architectures today and<00:22:53.030> we'll<00:22:53.150> publish<00:22:53.300> a<00:22:53.450> paper<00:22:53.660> soon<00:22:53.930> that 00:22:54.100 --> 00:22:54.110 align:start position:0% and we'll publish a paper soon that 00:22:54.110 --> 00:22:55.870 align:start position:0% and we'll publish a paper soon that describes<00:22:54.470> this<00:22:54.980> architecture<00:22:55.550> in<00:22:55.700> more 00:22:55.870 --> 00:22:55.880 align:start position:0% describes this architecture in more 00:22:55.880 --> 00:22:56.370 align:start position:0% describes this architecture in more detail 00:22:56.370 --> 00:22:56.380 align:start position:0% detail 00:22:56.380 --> 00:22:58.540 align:start position:0% detail ok<00:22:57.380> so<00:22:57.440> let's<00:22:57.740> put<00:22:57.890> this<00:22:57.980> all<00:22:58.130> together<00:22:58.310> and 00:22:58.540 --> 00:22:58.550 align:start position:0% ok so let's put this all together and 00:22:58.550 --> 00:23:01.150 align:start position:0% ok so let's put this all together and show<00:22:58.790> how<00:22:59.420> all<00:22:59.720> these<00:22:59.960> features<00:23:00.160> work 00:23:01.150 --> 00:23:01.160 align:start position:0% show how all these features work 00:23:01.160 --> 00:23:02.920 align:start position:0% show how all these features work together<00:23:01.340> to<00:23:01.820> solve<00:23:02.180> real-world<00:23:02.780> problems 00:23:02.920 --> 00:23:02.930 align:start position:0% together to solve real-world problems 00:23:02.930 --> 00:23:04.990 align:start position:0% together to solve real-world problems and<00:23:03.440> hopefully<00:23:03.500> get<00:23:04.280> you<00:23:04.400> excited<00:23:04.610> about<00:23:04.820> the 00:23:04.990 --> 00:23:05.000 align:start position:0% and hopefully get you excited about the 00:23:05.000 --> 00:23:06.400 align:start position:0% and hopefully get you excited about the sorts<00:23:05.210> of<00:23:05.270> applications<00:23:05.450> that<00:23:05.930> you<00:23:06.020> can<00:23:06.230> build 00:23:06.400 --> 00:23:06.410 align:start position:0% sorts of applications that you can build 00:23:06.410 --> 00:23:07.960 align:start position:0% sorts of applications that you can build on<00:23:06.650> this<00:23:06.770> platform<00:23:07.010> so<00:23:07.610> I'll<00:23:07.760> talk<00:23:07.910> briefly 00:23:07.960 --> 00:23:07.970 align:start position:0% on this platform so I'll talk briefly 00:23:07.970 --> 00:23:10.090 align:start position:0% on this platform so I'll talk briefly about<00:23:08.390> an<00:23:08.600> application<00:23:08.990> that's<00:23:09.380> currently 00:23:10.090 --> 00:23:10.100 align:start position:0% about an application that's currently 00:23:10.100 --> 00:23:12.040 align:start position:0% about an application that's currently being<00:23:10.280> developed<00:23:10.430> on<00:23:10.880> oasis<00:23:11.510> which<00:23:11.720> is<00:23:11.840> called 00:23:12.040 --> 00:23:12.050 align:start position:0% being developed on oasis which is called 00:23:12.050 --> 00:23:13.960 align:start position:0% being developed on oasis which is called kora<00:23:12.350> there's<00:23:13.250> a<00:23:13.340> collaboration<00:23:13.790> between 00:23:13.960 --> 00:23:13.970 align:start position:0% kora there's a collaboration between 00:23:13.970 --> 00:23:16.990 align:start position:0% kora there's a collaboration between Berkeley<00:23:14.570> ETH<00:23:15.020> Zurich<00:23:15.410> and<00:23:15.590> Stanford<00:23:16.280> and<00:23:16.460> so 00:23:16.990 --> 00:23:17.000 align:start position:0% Berkeley ETH Zurich and Stanford and so 00:23:17.000 --> 00:23:18.910 align:start position:0% Berkeley ETH Zurich and Stanford and so cara<00:23:17.450> is<00:23:17.540> designed<00:23:18.050> to<00:23:18.320> solve<00:23:18.470> this<00:23:18.740> problem 00:23:18.910 --> 00:23:18.920 align:start position:0% cara is designed to solve this problem 00:23:18.920 --> 00:23:21.910 align:start position:0% cara is designed to solve this problem of<00:23:19.340> data<00:23:20.330> silos<00:23:20.780> around<00:23:21.140> medical<00:23:21.530> data<00:23:21.710> so 00:23:21.910 --> 00:23:21.920 align:start position:0% of data silos around medical data so 00:23:21.920 --> 00:23:23.770 align:start position:0% of data silos around medical data so medical<00:23:22.340> data<00:23:22.520> is<00:23:22.610> very<00:23:22.760> sensitive<00:23:23.150> but<00:23:23.660> it's 00:23:23.770 --> 00:23:23.780 align:start position:0% medical data is very sensitive but it's 00:23:23.780 --> 00:23:25.690 align:start position:0% medical data is very sensitive but it's also<00:23:23.930> very<00:23:24.050> valuable<00:23:24.590> if<00:23:24.860> researchers<00:23:25.220> had 00:23:25.690 --> 00:23:25.700 align:start position:0% also very valuable if researchers had 00:23:25.700 --> 00:23:27.700 align:start position:0% also very valuable if researchers had better<00:23:26.030> access<00:23:26.510> to<00:23:26.540> medical<00:23:26.960> data<00:23:27.170> they<00:23:27.650> could 00:23:27.700 --> 00:23:27.710 align:start position:0% better access to medical data they could 00:23:27.710 --> 00:23:29.920 align:start position:0% better access to medical data they could develop<00:23:28.010> better<00:23:28.310> systems<00:23:28.850> for<00:23:29.150> personalized 00:23:29.920 --> 00:23:29.930 align:start position:0% develop better systems for personalized 00:23:29.930 --> 00:23:31.660 align:start position:0% develop better systems for personalized health<00:23:30.170> and<00:23:30.530> predicting<00:23:31.070> you<00:23:31.310> know<00:23:31.430> health 00:23:31.660 --> 00:23:31.670 align:start position:0% health and predicting you know health 00:23:31.670 --> 00:23:34.330 align:start position:0% health and predicting you know health conditions<00:23:32.180> and<00:23:32.360> so<00:23:32.450> forth<00:23:32.690> so<00:23:33.340> Cara 00:23:34.330 --> 00:23:34.340 align:start position:0% conditions and so forth so Cara 00:23:34.340 --> 00:23:37.030 align:start position:0% conditions and so forth so Cara implements<00:23:35.300> a<00:23:35.480> data<00:23:35.840> market<00:23:36.320> specifically 00:23:37.030 --> 00:23:37.040 align:start position:0% implements a data market specifically 00:23:37.040 --> 00:23:38.350 align:start position:0% implements a data market specifically around<00:23:37.250> medical<00:23:37.490> data<00:23:37.880> so<00:23:38.090> the<00:23:38.180> way<00:23:38.270> it<00:23:38.330> works 00:23:38.350 --> 00:23:38.360 align:start position:0% around medical data so the way it works 00:23:38.360 --> 00:23:41.260 align:start position:0% around medical data so the way it works is<00:23:38.720> the<00:23:39.260> user<00:23:39.530> inputs<00:23:40.250> their<00:23:40.460> data<00:23:40.670> into<00:23:41.000> a 00:23:41.260 --> 00:23:41.270 align:start position:0% is the user inputs their data into a 00:23:41.270 --> 00:23:44.050 align:start position:0% is the user inputs their data into a smart<00:23:41.570> contract<00:23:41.990> and<00:23:42.560> a<00:23:43.370> researcher<00:23:43.880> that 00:23:44.050 --> 00:23:44.060 align:start position:0% smart contract and a researcher that 00:23:44.060 --> 00:23:46.600 align:start position:0% smart contract and a researcher that wants<00:23:44.390> to<00:23:44.450> train<00:23:44.810> a<00:23:44.840> model<00:23:45.110> on<00:23:45.470> that<00:23:45.680> data<00:23:45.920> can 00:23:46.600 --> 00:23:46.610 align:start position:0% wants to train a model on that data can 00:23:46.610 --> 00:23:48.370 align:start position:0% wants to train a model on that data can submit<00:23:47.060> the<00:23:47.210> model<00:23:47.630> to<00:23:47.810> the<00:23:47.840> smart<00:23:48.200> contract 00:23:48.370 --> 00:23:48.380 align:start position:0% submit the model to the smart contract 00:23:48.380 --> 00:23:51.370 align:start position:0% submit the model to the smart contract and<00:23:48.890> pay<00:23:49.340> a<00:23:49.370> token<00:23:49.850> or<00:23:50.030> you<00:23:50.600> know<00:23:50.690> pay<00:23:50.900> in<00:23:51.170> terms 00:23:51.370 --> 00:23:51.380 align:start position:0% and pay a token or you know pay in terms 00:23:51.380 --> 00:23:53.020 align:start position:0% and pay a token or you know pay in terms of<00:23:51.560> tokens<00:23:51.920> in<00:23:52.010> order<00:23:52.580> to<00:23:52.700> run<00:23:52.850> that 00:23:53.020 --> 00:23:53.030 align:start position:0% of tokens in order to run that 00:23:53.030 --> 00:23:55.570 align:start position:0% of tokens in order to run that computation<00:23:53.630> the<00:23:54.230> entire<00:23:54.530> computation<00:23:54.950> runs 00:23:55.570 --> 00:23:55.580 align:start position:0% computation the entire computation runs 00:23:55.580 --> 00:23:57.970 align:start position:0% computation the entire computation runs directly<00:23:56.210> in<00:23:56.360> the<00:23:56.480> smart<00:23:56.720> contract<00:23:57.140> and<00:23:57.350> the 00:23:57.970 --> 00:23:57.980 align:start position:0% directly in the smart contract and the 00:23:57.980 --> 00:24:00.100 align:start position:0% directly in the smart contract and the users<00:23:58.400> receive<00:23:59.000> compensation<00:23:59.420> for<00:23:59.930> their 00:24:00.100 --> 00:24:00.110 align:start position:0% users receive compensation for their 00:24:00.110 --> 00:24:02.650 align:start position:0% users receive compensation for their data<00:24:00.290> and<00:24:00.590> the<00:24:01.130> researchers<00:24:01.700> receive<00:24:02.390> the 00:24:02.650 --> 00:24:02.660 align:start position:0% data and the researchers receive the 00:24:02.660 --> 00:24:05.320 align:start position:0% data and the researchers receive the train<00:24:02.900> model<00:24:03.320> so<00:24:03.770> this<00:24:03.920> is<00:24:04.070> ideal<00:24:04.280> because<00:24:04.880> on 00:24:05.320 --> 00:24:05.330 align:start position:0% train model so this is ideal because on 00:24:05.330 --> 00:24:08.050 align:start position:0% train model so this is ideal because on the<00:24:05.660> one<00:24:05.780> hand<00:24:06.020> users<00:24:06.710> write<00:24:07.310> because<00:24:07.550> this<00:24:07.910> is 00:24:08.050 --> 00:24:08.060 align:start position:0% the one hand users write because this is 00:24:08.060 --> 00:24:09.430 align:start position:0% the one hand users write because this is implemented<00:24:08.480> as<00:24:08.570> a<00:24:08.630> smart<00:24:08.870> contract<00:24:09.020> they 00:24:09.430 --> 00:24:09.440 align:start position:0% implemented as a smart contract they 00:24:09.440 --> 00:24:10.840 align:start position:0% implemented as a smart contract they don't<00:24:09.590> need<00:24:09.710> to<00:24:09.860> trust<00:24:10.100> researchers<00:24:10.700> they 00:24:10.840 --> 00:24:10.850 align:start position:0% don't need to trust researchers they 00:24:10.850 --> 00:24:12.700 align:start position:0% don't need to trust researchers they don't<00:24:11.030> need<00:24:11.150> to<00:24:11.330> vet<00:24:11.930> the<00:24:12.110> researchers<00:24:12.620> they 00:24:12.700 --> 00:24:12.710 align:start position:0% don't need to vet the researchers they 00:24:12.710 --> 00:24:14.500 align:start position:0% don't need to vet the researchers they don't<00:24:12.860> need<00:24:12.980> to<00:24:13.100> worry<00:24:13.310> about<00:24:13.400> exactly<00:24:14.210> what 00:24:14.500 --> 00:24:14.510 align:start position:0% don't need to worry about exactly what 00:24:14.510 --> 00:24:15.970 align:start position:0% don't need to worry about exactly what the<00:24:14.540> researchers<00:24:14.990> are<00:24:15.110> doing<00:24:15.230> they<00:24:15.800> have 00:24:15.970 --> 00:24:15.980 align:start position:0% the researchers are doing they have 00:24:15.980 --> 00:24:17.680 align:start position:0% the researchers are doing they have assurances<00:24:16.490> that<00:24:16.550> their<00:24:16.850> data<00:24:17.030> will<00:24:17.210> only<00:24:17.420> be 00:24:17.680 --> 00:24:17.690 align:start position:0% assurances that their data will only be 00:24:17.690 --> 00:24:19.360 align:start position:0% assurances that their data will only be used<00:24:17.930> for<00:24:18.230> this<00:24:18.410> specific<00:24:18.920> purpose<00:24:19.070> of 00:24:19.360 --> 00:24:19.370 align:start position:0% used for this specific purpose of 00:24:19.370 --> 00:24:21.010 align:start position:0% used for this specific purpose of training<00:24:19.550> a<00:24:19.760> model<00:24:20.060> and<00:24:20.210> because<00:24:20.720> they<00:24:20.870> can 00:24:21.010 --> 00:24:21.020 align:start position:0% training a model and because they can 00:24:21.020 --> 00:24:23.320 align:start position:0% training a model and because they can verify<00:24:21.230> actually<00:24:21.920> that<00:24:22.130> the<00:24:22.550> model<00:24:22.910> enforces 00:24:23.320 --> 00:24:23.330 align:start position:0% verify actually that the model enforces 00:24:23.330 --> 00:24:25.360 align:start position:0% verify actually that the model enforces differential<00:24:23.810> privacy<00:24:24.200> they<00:24:24.710> know<00:24:24.980> that 00:24:25.360 --> 00:24:25.370 align:start position:0% differential privacy they know that 00:24:25.370 --> 00:24:26.860 align:start position:0% differential privacy they know that while<00:24:25.790> their<00:24:25.970> data<00:24:26.150> is<00:24:26.270> going<00:24:26.360> to<00:24:26.450> be<00:24:26.540> used<00:24:26.780> for 00:24:26.860 --> 00:24:26.870 align:start position:0% while their data is going to be used for 00:24:26.870 --> 00:24:27.740 align:start position:0% while their data is going to be used for this<00:24:27.080> analytics 00:24:27.740 --> 00:24:27.750 align:start position:0% this analytics 00:24:27.750 --> 00:24:29.690 align:start position:0% this analytics the<00:24:28.230> output<00:24:28.770> actually<00:24:28.980> won't<00:24:29.400> reveal 00:24:29.690 --> 00:24:29.700 align:start position:0% the output actually won't reveal 00:24:29.700 --> 00:24:31.610 align:start position:0% the output actually won't reveal anything<00:24:30.030> about<00:24:30.270> them<00:24:30.600> individually<00:24:30.809> so<00:24:31.380> it's 00:24:31.610 --> 00:24:31.620 align:start position:0% anything about them individually so it's 00:24:31.620 --> 00:24:33.830 align:start position:0% anything about them individually so it's completely<00:24:32.070> safe<00:24:32.280> for<00:24:32.490> them<00:24:32.720> researchers<00:24:33.720> on 00:24:33.830 --> 00:24:33.840 align:start position:0% completely safe for them researchers on 00:24:33.840 --> 00:24:36.230 align:start position:0% completely safe for them researchers on the<00:24:33.929> other<00:24:34.080> hand<00:24:34.380> now<00:24:34.919> have<00:24:35.250> access<00:24:35.429> to<00:24:35.669> richer 00:24:36.230 --> 00:24:36.240 align:start position:0% the other hand now have access to richer 00:24:36.240 --> 00:24:38.000 align:start position:0% the other hand now have access to richer and<00:24:36.450> broader<00:24:36.750> data<00:24:37.289> sets<00:24:37.559> than<00:24:37.770> they<00:24:37.860> had 00:24:38.000 --> 00:24:38.010 align:start position:0% and broader data sets than they had 00:24:38.010 --> 00:24:40.039 align:start position:0% and broader data sets than they had access<00:24:38.159> to<00:24:38.340> before<00:24:38.789> because<00:24:39.390> users<00:24:39.750> are<00:24:39.780> more 00:24:40.039 --> 00:24:40.049 align:start position:0% access to before because users are more 00:24:40.049 --> 00:24:41.899 align:start position:0% access to before because users are more willing<00:24:40.200> to<00:24:40.470> contribute<00:24:40.890> their<00:24:41.010> data<00:24:41.220> and<00:24:41.400> the 00:24:41.899 --> 00:24:41.909 align:start position:0% willing to contribute their data and the 00:24:41.909 --> 00:24:43.909 align:start position:0% willing to contribute their data and the fact<00:24:42.120> that<00:24:42.270> the<00:24:42.630> whole<00:24:42.780> thing<00:24:43.049> runs<00:24:43.289> on<00:24:43.470> Oasis 00:24:43.909 --> 00:24:43.919 align:start position:0% fact that the whole thing runs on Oasis 00:24:43.919 --> 00:24:45.710 align:start position:0% fact that the whole thing runs on Oasis means<00:24:44.159> that<00:24:44.370> even<00:24:44.940> the<00:24:45.030> workers<00:24:45.210> that<00:24:45.600> are 00:24:45.710 --> 00:24:45.720 align:start position:0% means that even the workers that are 00:24:45.720 --> 00:24:47.750 align:start position:0% means that even the workers that are running<00:24:46.080> the<00:24:46.440> machine<00:24:46.710> learning<00:24:46.890> actually 00:24:47.750 --> 00:24:47.760 align:start position:0% running the machine learning actually 00:24:47.760 --> 00:24:49.610 align:start position:0% running the machine learning actually can't<00:24:48.150> see<00:24:48.299> the<00:24:48.450> data<00:24:48.630> so<00:24:49.080> we<00:24:49.169> have<00:24:49.200> end-to-end 00:24:49.610 --> 00:24:49.620 align:start position:0% can't see the data so we have end-to-end 00:24:49.620 --> 00:24:52.220 align:start position:0% can't see the data so we have end-to-end privacy<00:24:50.490> guarantees<00:24:50.940> for<00:24:51.419> users<00:24:51.840> and<00:24:51.990> their 00:24:52.220 --> 00:24:52.230 align:start position:0% privacy guarantees for users and their 00:24:52.230 --> 00:24:53.990 align:start position:0% privacy guarantees for users and their data<00:24:52.409> and<00:24:52.650> of<00:24:53.130> course<00:24:53.340> you<00:24:53.610> know<00:24:53.730> you<00:24:53.789> need 00:24:53.990 --> 00:24:54.000 align:start position:0% data and of course you know you need 00:24:54.000 --> 00:24:56.060 align:start position:0% data and of course you know you need scalability<00:24:54.750> you<00:24:55.110> need<00:24:55.289> scalability<00:24:55.919> to 00:24:56.060 --> 00:24:56.070 align:start position:0% scalability you need scalability to 00:24:56.070 --> 00:24:58.220 align:start position:0% scalability you need scalability to these<00:24:56.220> complex<00:24:56.700> types<00:24:57.120> of<00:24:57.299> computations<00:24:58.080> in 00:24:58.220 --> 00:24:58.230 align:start position:0% these complex types of computations in 00:24:58.230 --> 00:24:59.539 align:start position:0% these complex types of computations in order<00:24:58.440> to<00:24:58.530> be<00:24:58.620> able<00:24:58.710> to<00:24:58.830> run<00:24:59.039> all<00:24:59.250> of<00:24:59.280> this 00:24:59.539 --> 00:24:59.549 align:start position:0% order to be able to run all of this 00:24:59.549 --> 00:25:03.700 align:start position:0% order to be able to run all of this directly<00:24:59.970> on<00:25:00.059> chain<00:25:01.309> great 00:25:03.700 --> 00:25:03.710 align:start position:0% directly on chain great 00:25:03.710 --> 00:25:06.230 align:start position:0% directly on chain great so<00:25:04.710> hopefully<00:25:05.100> this<00:25:05.580> gets<00:25:05.760> you<00:25:05.940> thinking 00:25:06.230 --> 00:25:06.240 align:start position:0% so hopefully this gets you thinking 00:25:06.240 --> 00:25:07.789 align:start position:0% so hopefully this gets you thinking about<00:25:06.330> the<00:25:06.570> sorts<00:25:06.780> of<00:25:06.840> things<00:25:06.900> that<00:25:07.289> you<00:25:07.650> can 00:25:07.789 --> 00:25:07.799 align:start position:0% about the sorts of things that you can 00:25:07.799 --> 00:25:09.380 align:start position:0% about the sorts of things that you can do<00:25:07.919> remember<00:25:08.220> earlier<00:25:08.580> the<00:25:08.760> slide<00:25:08.970> I<00:25:09.000> talked 00:25:09.380 --> 00:25:09.390 align:start position:0% do remember earlier the slide I talked 00:25:09.390 --> 00:25:11.960 align:start position:0% do remember earlier the slide I talked about<00:25:09.480> unleashing<00:25:10.200> the<00:25:10.500> value<00:25:10.770> of<00:25:10.970> medical 00:25:11.960 --> 00:25:11.970 align:start position:0% about unleashing the value of medical 00:25:11.970 --> 00:25:14.060 align:start position:0% about unleashing the value of medical data<00:25:12.330> you<00:25:12.840> know<00:25:12.929> this<00:25:13.080> is<00:25:13.230> exactly<00:25:13.830> an<00:25:13.980> example 00:25:14.060 --> 00:25:14.070 align:start position:0% data you know this is exactly an example 00:25:14.070 --> 00:25:16.460 align:start position:0% data you know this is exactly an example where<00:25:14.610> blockchain<00:25:15.510> can<00:25:15.539> can<00:25:16.110> solve<00:25:16.320> new 00:25:16.460 --> 00:25:16.470 align:start position:0% where blockchain can can solve new 00:25:16.470 --> 00:25:18.529 align:start position:0% where blockchain can can solve new problems<00:25:16.500> and<00:25:17.070> and<00:25:17.280> bring<00:25:17.610> value<00:25:18.030> to<00:25:18.059> places 00:25:18.529 --> 00:25:18.539 align:start position:0% problems and and bring value to places 00:25:18.539 --> 00:25:20.990 align:start position:0% problems and and bring value to places where<00:25:18.659> right<00:25:19.650> now<00:25:19.679> the<00:25:19.860> value<00:25:20.280> is<00:25:20.580> locked<00:25:20.820> up 00:25:20.990 --> 00:25:21.000 align:start position:0% where right now the value is locked up 00:25:21.000 --> 00:25:24.640 align:start position:0% where right now the value is locked up specifically<00:25:21.960> because<00:25:22.289> of<00:25:22.470> privacy<00:25:22.890> concerns 00:25:24.640 --> 00:25:24.650 align:start position:0% specifically because of privacy concerns 00:25:24.650 --> 00:25:27.380 align:start position:0% specifically because of privacy concerns so<00:25:25.650> we<00:25:25.890> want<00:25:26.190> to<00:25:26.280> support<00:25:26.580> and<00:25:26.880> empower 00:25:27.380 --> 00:25:27.390 align:start position:0% so we want to support and empower 00:25:27.390 --> 00:25:30.169 align:start position:0% so we want to support and empower developers<00:25:27.780> building<00:25:28.440> on<00:25:28.559> Oasis<00:25:29.010> to<00:25:29.850> develop 00:25:30.169 --> 00:25:30.179 align:start position:0% developers building on Oasis to develop 00:25:30.179 --> 00:25:31.580 align:start position:0% developers building on Oasis to develop these<00:25:30.330> sorts<00:25:30.570> of<00:25:30.630> exciting<00:25:30.870> applications 00:25:31.580 --> 00:25:31.590 align:start position:0% these sorts of exciting applications 00:25:31.590 --> 00:25:33.020 align:start position:0% these sorts of exciting applications we're<00:25:31.799> releasing<00:25:32.070> a<00:25:32.309> number<00:25:32.490> of<00:25:32.549> tools<00:25:32.760> and 00:25:33.020 --> 00:25:33.030 align:start position:0% we're releasing a number of tools and 00:25:33.030 --> 00:25:35.899 align:start position:0% we're releasing a number of tools and libraries<00:25:33.840> that<00:25:34.260> support<00:25:34.320> you<00:25:35.039> know<00:25:35.159> diverse 00:25:35.899 --> 00:25:35.909 align:start position:0% libraries that support you know diverse 00:25:35.909 --> 00:25:37.669 align:start position:0% libraries that support you know diverse applications<00:25:36.570> ranging<00:25:36.929> from<00:25:37.140> machine 00:25:37.669 --> 00:25:37.679 align:start position:0% applications ranging from machine 00:25:37.679 --> 00:25:40.850 align:start position:0% applications ranging from machine learning<00:25:37.710> to<00:25:38.309> data<00:25:38.610> markets<00:25:39.120> to<00:25:39.360> games<00:25:39.860> and 00:25:40.850 --> 00:25:40.860 align:start position:0% learning to data markets to games and 00:25:40.860 --> 00:25:42.680 align:start position:0% learning to data markets to games and even<00:25:41.070> standard<00:25:41.669> kind<00:25:42.000> of<00:25:42.030> aetherium<00:25:42.450> style 00:25:42.680 --> 00:25:42.690 align:start position:0% even standard kind of aetherium style 00:25:42.690 --> 00:25:44.600 align:start position:0% even standard kind of aetherium style smart<00:25:43.049> contracts<00:25:43.470> we<00:25:43.890> also<00:25:44.039> have<00:25:44.250> a<00:25:44.280> startup 00:25:44.600 --> 00:25:44.610 align:start position:0% smart contracts we also have a startup 00:25:44.610 --> 00:25:46.549 align:start position:0% smart contracts we also have a startup hub<00:25:44.820> which<00:25:45.630> I'll<00:25:45.750> discuss<00:25:45.990> briefly<00:25:46.200> to 00:25:46.549 --> 00:25:46.559 align:start position:0% hub which I'll discuss briefly to 00:25:46.559 --> 00:25:48.649 align:start position:0% hub which I'll discuss briefly to provide<00:25:46.860> more<00:25:47.640> direct<00:25:47.940> support<00:25:48.179> to<00:25:48.270> teams 00:25:48.649 --> 00:25:48.659 align:start position:0% provide more direct support to teams 00:25:48.659 --> 00:25:51.020 align:start position:0% provide more direct support to teams that<00:25:48.929> need<00:25:49.380> it<00:25:49.559> and<00:25:49.679> we<00:25:50.490> want<00:25:50.640> to<00:25:50.730> build<00:25:50.820> a 00:25:51.020 --> 00:25:51.030 align:start position:0% that need it and we want to build a 00:25:51.030 --> 00:25:53.330 align:start position:0% that need it and we want to build a strong<00:25:51.299> community<00:25:51.960> together<00:25:52.320> so<00:25:53.190> we 00:25:53.330 --> 00:25:53.340 align:start position:0% strong community together so we 00:25:53.340 --> 00:25:54.680 align:start position:0% strong community together so we announced<00:25:53.520> a<00:25:53.730> few<00:25:53.850> weeks<00:25:53.909> ago<00:25:54.210> this<00:25:54.360> startup 00:25:54.680 --> 00:25:54.690 align:start position:0% announced a few weeks ago this startup 00:25:54.690 --> 00:25:57.049 align:start position:0% announced a few weeks ago this startup hub<00:25:54.929> you<00:25:55.860> can<00:25:55.980> apply<00:25:56.220> at<00:25:56.370> the<00:25:56.490> URL<00:25:56.760> at<00:25:56.909> the 00:25:57.049 --> 00:25:57.059 align:start position:0% hub you can apply at the URL at the 00:25:57.059 --> 00:25:58.940 align:start position:0% hub you can apply at the URL at the bottom<00:25:57.120> this<00:25:57.870> will<00:25:58.080> give<00:25:58.260> teams<00:25:58.590> that<00:25:58.830> are 00:25:58.940 --> 00:25:58.950 align:start position:0% bottom this will give teams that are 00:25:58.950 --> 00:26:01.130 align:start position:0% bottom this will give teams that are working<00:25:58.980> on<00:25:59.460> really<00:26:00.059> complex<00:26:00.450> applications 00:26:01.130 --> 00:26:01.140 align:start position:0% working on really complex applications 00:26:01.140 --> 00:26:02.510 align:start position:0% working on really complex applications and<00:26:01.320> want<00:26:01.470> a<00:26:01.620> little<00:26:01.740> more<00:26:01.980> support<00:26:02.400> and 00:26:02.510 --> 00:26:02.520 align:start position:0% and want a little more support and 00:26:02.520 --> 00:26:04.610 align:start position:0% and want a little more support and mentorship<00:26:03.210> directly<00:26:03.780> from<00:26:03.929> the<00:26:04.080> Oasis<00:26:04.440> team 00:26:04.610 --> 00:26:04.620 align:start position:0% mentorship directly from the Oasis team 00:26:04.620 --> 00:26:06.830 align:start position:0% mentorship directly from the Oasis team this<00:26:04.770> will<00:26:04.950> give<00:26:05.100> direct<00:26:05.820> access<00:26:06.210> to<00:26:06.360> Oasis 00:26:06.830 --> 00:26:06.840 align:start position:0% this will give direct access to Oasis 00:26:06.840 --> 00:26:11.180 align:start position:0% this will give direct access to Oasis engineers<00:26:07.289> and<00:26:08.220> and<00:26:08.929> access<00:26:09.929> to<00:26:09.960> our<00:26:10.289> our<00:26:10.890> list 00:26:11.180 --> 00:26:11.190 align:start position:0% engineers and and access to our our list 00:26:11.190 --> 00:26:15.200 align:start position:0% engineers and and access to our our list of<00:26:11.400> top<00:26:12.150> investors<00:26:13.080> as<00:26:13.289> well<00:26:13.820> so<00:26:14.820> if<00:26:15.059> you're 00:26:15.200 --> 00:26:15.210 align:start position:0% of top investors as well so if you're 00:26:15.210 --> 00:26:17.080 align:start position:0% of top investors as well so if you're working<00:26:15.390> on<00:26:15.630> an<00:26:15.809> exciting<00:26:16.230> application 00:26:17.080 --> 00:26:17.090 align:start position:0% working on an exciting application 00:26:17.090 --> 00:26:19.310 align:start position:0% working on an exciting application please<00:26:18.090> apply<00:26:18.360> here<00:26:18.600> we'd<00:26:18.840> love<00:26:18.990> to<00:26:19.020> have<00:26:19.200> you 00:26:19.310 --> 00:26:19.320 align:start position:0% please apply here we'd love to have you 00:26:19.320 --> 00:26:21.740 align:start position:0% please apply here we'd love to have you in<00:26:19.409> the<00:26:19.470> program<00:26:19.590> and<00:26:20.150> then<00:26:21.150> finally<00:26:21.510> so<00:26:21.659> we 00:26:21.740 --> 00:26:21.750 align:start position:0% in the program and then finally so we 00:26:21.750 --> 00:26:23.539 align:start position:0% in the program and then finally so we launched<00:26:22.020> our<00:26:22.080> private<00:26:22.590> test<00:26:22.799> net<00:26:22.980> a<00:26:23.130> few 00:26:23.539 --> 00:26:23.549 align:start position:0% launched our private test net a few 00:26:23.549 --> 00:26:24.110 align:start position:0% launched our private test net a few months<00:26:23.730> ago 00:26:24.110 --> 00:26:24.120 align:start position:0% months ago 00:26:24.120 --> 00:26:25.850 align:start position:0% months ago we've<00:26:24.510> gotten<00:26:24.750> a<00:26:24.809> ton<00:26:24.960> of<00:26:25.020> excitement<00:26:25.590> there's 00:26:25.850 --> 00:26:25.860 align:start position:0% we've gotten a ton of excitement there's 00:26:25.860 --> 00:26:27.260 align:start position:0% we've gotten a ton of excitement there's a<00:26:25.919> lot<00:26:26.039> of<00:26:26.159> developers<00:26:26.610> already<00:26:26.760> building<00:26:27.120> on 00:26:27.260 --> 00:26:27.270 align:start position:0% a lot of developers already building on 00:26:27.270 --> 00:26:28.909 align:start position:0% a lot of developers already building on it<00:26:27.419> based<00:26:27.960> on<00:26:28.140> the<00:26:28.289> feedback<00:26:28.590> from<00:26:28.620> these 00:26:28.909 --> 00:26:28.919 align:start position:0% it based on the feedback from these 00:26:28.919 --> 00:26:31.190 align:start position:0% it based on the feedback from these developers<00:26:29.520> and<00:26:30.390> our<00:26:30.539> experience<00:26:30.929> operating 00:26:31.190 --> 00:26:31.200 align:start position:0% developers and our experience operating 00:26:31.200 --> 00:26:32.870 align:start position:0% developers and our experience operating the<00:26:31.409> test<00:26:31.620> net<00:26:31.770> we're<00:26:32.220> really<00:26:32.370> excited<00:26:32.760> to 00:26:32.870 --> 00:26:32.880 align:start position:0% the test net we're really excited to 00:26:32.880 --> 00:26:35.000 align:start position:0% the test net we're really excited to announce<00:26:32.909> the<00:26:33.210> next<00:26:33.419> milestone<00:26:33.799> here<00:26:34.799> today 00:26:35.000 --> 00:26:35.010 align:start position:0% announce the next milestone here today 00:26:35.010 --> 00:26:37.070 align:start position:0% announce the next milestone here today and<00:26:35.190> we're<00:26:35.370> calling<00:26:35.669> it<00:26:35.820> a<00:26:35.970> dev<00:26:36.450> net<00:26:36.690> because 00:26:37.070 --> 00:26:37.080 align:start position:0% and we're calling it a dev net because 00:26:37.080 --> 00:26:39.680 align:start position:0% and we're calling it a dev net because the<00:26:37.320> main<00:26:37.860> goal<00:26:38.130> is<00:26:38.399> to<00:26:38.429> allow<00:26:38.820> developers<00:26:39.179> to 00:26:39.680 --> 00:26:39.690 align:start position:0% the main goal is to allow developers to 00:26:39.690 --> 00:26:41.480 align:start position:0% the main goal is to allow developers to start<00:26:39.750> building<00:26:40.350> these<00:26:40.500> sorts<00:26:40.770> of<00:26:40.860> privacy 00:26:41.480 --> 00:26:41.490 align:start position:0% start building these sorts of privacy 00:26:41.490 --> 00:26:43.730 align:start position:0% start building these sorts of privacy preserving<00:26:41.850> applications<00:26:42.510> so<00:26:42.990> what<00:26:43.380> it<00:26:43.559> will 00:26:43.730 --> 00:26:43.740 align:start position:0% preserving applications so what it will 00:26:43.740 --> 00:26:46.220 align:start position:0% preserving applications so what it will include<00:26:44.010> is<00:26:44.520> the<00:26:45.090> confidentiality<00:26:45.510> libraries 00:26:46.220 --> 00:26:46.230 align:start position:0% include is the confidentiality libraries 00:26:46.230 --> 00:26:47.510 align:start position:0% include is the confidentiality libraries that<00:26:46.350> I<00:26:46.410> described<00:26:46.800> earlier<00:26:46.920> these 00:26:47.510 --> 00:26:47.520 align:start position:0% that I described earlier these 00:26:47.520 --> 00:26:49.940 align:start position:0% that I described earlier these extensions<00:26:48.150> to<00:26:48.300> web<00:26:48.450> 3<00:26:48.750> for<00:26:49.110> providing<00:26:49.440> you 00:26:49.940 --> 00:26:49.950 align:start position:0% extensions to web 3 for providing you 00:26:49.950 --> 00:26:52.010 align:start position:0% extensions to web 3 for providing you know<00:26:50.070> new<00:26:50.220> ap<00:26:50.520> is<00:26:50.640> to<00:26:50.940> protect<00:26:51.270> data<00:26:51.450> during 00:26:52.010 --> 00:26:52.020 align:start position:0% know new ap is to protect data during 00:26:52.020 --> 00:26:54.350 align:start position:0% know new ap is to protect data during computation<00:26:52.679> provide<00:26:53.460> a<00:26:53.490> contract<00:26:53.970> kit<00:26:54.179> to 00:26:54.350 --> 00:26:54.360 align:start position:0% computation provide a contract kit to 00:26:54.360 --> 00:26:56.540 align:start position:0% computation provide a contract kit to allow<00:26:54.510> you<00:26:54.570> to<00:26:54.929> develop<00:26:55.080> and<00:26:55.530> debug<00:26:55.950> contracts 00:26:56.540 --> 00:26:56.550 align:start position:0% allow you to develop and debug contracts 00:26:56.550 --> 00:27:00.410 align:start position:0% allow you to develop and debug contracts locally<00:26:57.000> we<00:26:57.600> support<00:26:58.050> EVM<00:26:58.590> as<00:26:58.860> well<00:26:59.220> as<00:26:59.490> web 00:27:00.410 --> 00:27:00.420 align:start position:0% locally we support EVM as well as web 00:27:00.420 --> 00:27:02.180 align:start position:0% locally we support EVM as well as web assembly<00:27:00.840> so<00:27:01.230> that<00:27:01.260> means<00:27:01.590> you<00:27:01.860> can<00:27:02.010> develop 00:27:02.180 --> 00:27:02.190 align:start position:0% assembly so that means you can develop 00:27:02.190 --> 00:27:05.090 align:start position:0% assembly so that means you can develop smart<00:27:02.550> contracts<00:27:02.940> in<00:27:03.120> in<00:27:03.570> rust<00:27:03.830> and<00:27:04.830> we<00:27:04.950> have<00:27:05.070> a 00:27:05.090 --> 00:27:05.100 align:start position:0% smart contracts in in rust and we have a 00:27:05.100 --> 00:27:07.370 align:start position:0% smart contracts in in rust and we have a set<00:27:05.250> of<00:27:05.340> tools<00:27:05.520> for<00:27:05.820> doing<00:27:05.910> that<00:27:06.380> we're 00:27:07.370 --> 00:27:07.380 align:start position:0% set of tools for doing that we're 00:27:07.380 --> 00:27:08.840 align:start position:0% set of tools for doing that we're backwards<00:27:07.559> compatible<00:27:08.130> with<00:27:08.250> aetherium<00:27:08.700> if 00:27:08.840 --> 00:27:08.850 align:start position:0% backwards compatible with aetherium if 00:27:08.850 --> 00:27:10.610 align:start position:0% backwards compatible with aetherium if you<00:27:09.179> have<00:27:09.300> an<00:27:09.420> existing<00:27:09.630> smart<00:27:10.050> contract<00:27:10.470> and 00:27:10.610 --> 00:27:10.620 align:start position:0% you have an existing smart contract and 00:27:10.620 --> 00:27:12.380 align:start position:0% you have an existing smart contract and you<00:27:10.679> want<00:27:10.860> to<00:27:10.950> port<00:27:11.160> it<00:27:11.250> over<00:27:11.340> to<00:27:11.580> Oasis<00:27:11.970> you 00:27:12.380 --> 00:27:12.390 align:start position:0% you want to port it over to Oasis you 00:27:12.390 --> 00:27:13.940 align:start position:0% you want to port it over to Oasis you can<00:27:12.540> do<00:27:12.660> so<00:27:12.840> without<00:27:12.960> any<00:27:13.260> changes<00:27:13.740> to<00:27:13.860> the 00:27:13.940 --> 00:27:13.950 align:start position:0% can do so without any changes to the 00:27:13.950 --> 00:27:15.680 align:start position:0% can do so without any changes to the smart<00:27:14.160> contract<00:27:14.309> and<00:27:14.820> your<00:27:15.450> app<00:27:15.540> immediately 00:27:15.680 --> 00:27:15.690 align:start position:0% smart contract and your app immediately 00:27:15.690 --> 00:27:17.810 align:start position:0% smart contract and your app immediately benefits<00:27:16.440> from<00:27:16.740> you<00:27:17.130> know<00:27:17.220> the<00:27:17.309> scalability 00:27:17.810 --> 00:27:17.820 align:start position:0% benefits from you know the scalability 00:27:17.820 --> 00:27:19.970 align:start position:0% benefits from you know the scalability and<00:27:17.910> privacy<00:27:18.300> properties<00:27:18.720> provided<00:27:19.530> by<00:27:19.590> Oasis 00:27:19.970 --> 00:27:19.980 align:start position:0% and privacy properties provided by Oasis 00:27:19.980 --> 00:27:22.460 align:start position:0% and privacy properties provided by Oasis we<00:27:20.880> have<00:27:21.000> a<00:27:21.030> set<00:27:21.210> of<00:27:21.330> resources<00:27:21.600> and<00:27:21.960> tutorials 00:27:22.460 --> 00:27:22.470 align:start position:0% we have a set of resources and tutorials 00:27:22.470 --> 00:27:24.799 align:start position:0% we have a set of resources and tutorials including<00:27:23.309> best<00:27:23.940> practices<00:27:24.480> for<00:27:24.690> writing 00:27:24.799 --> 00:27:24.809 align:start position:0% including best practices for writing 00:27:24.809 --> 00:27:27.410 align:start position:0% including best practices for writing private<00:27:25.620> smart<00:27:25.860> contracts<00:27:26.309> how<00:27:26.700> to<00:27:26.760> build<00:27:27.030> you 00:27:27.410 --> 00:27:27.420 align:start position:0% private smart contracts how to build you 00:27:27.420 --> 00:27:30.650 align:start position:0% private smart contracts how to build you know<00:27:27.480> secret<00:27:27.840> voting<00:27:28.530> apps<00:27:28.800> for<00:27:29.010> example<00:27:29.660> how 00:27:30.650 --> 00:27:30.660 align:start position:0% know secret voting apps for example how 00:27:30.660 --> 00:27:32.570 align:start position:0% know secret voting apps for example how to<00:27:30.720> build<00:27:30.960> a<00:27:31.200> game<00:27:31.470> in<00:27:31.770> order<00:27:31.890> to<00:27:32.070> protect<00:27:32.280> the 00:27:32.570 --> 00:27:32.580 align:start position:0% to build a game in order to protect the 00:27:32.580 --> 00:27:34.310 align:start position:0% to build a game in order to protect the state<00:27:32.790> of<00:27:32.970> the<00:27:33.090> game<00:27:33.270> and<00:27:33.540> a<00:27:33.900> number<00:27:34.110> of<00:27:34.200> other 00:27:34.310 --> 00:27:34.320 align:start position:0% state of the game and a number of other 00:27:34.320 --> 00:27:35.840 align:start position:0% state of the game and a number of other tutorials<00:27:34.800> so<00:27:34.950> that<00:27:35.070> will<00:27:35.190> be<00:27:35.280> available<00:27:35.670> at 00:27:35.840 --> 00:27:35.850 align:start position:0% tutorials so that will be available at 00:27:35.850 --> 00:27:38.180 align:start position:0% tutorials so that will be available at launch<00:27:36.030> and<00:27:36.900> then<00:27:37.020> finally<00:27:37.470> just<00:27:37.500> better 00:27:38.180 --> 00:27:38.190 align:start position:0% launch and then finally just better 00:27:38.190 --> 00:27:40.160 align:start position:0% launch and then finally just better reliability<00:27:38.490> and<00:27:39.150> performance<00:27:39.540> and<00:27:40.050> we'll 00:27:40.160 --> 00:27:40.170 align:start position:0% reliability and performance and we'll 00:27:40.170 --> 00:27:41.690 align:start position:0% reliability and performance and we'll continue<00:27:40.350> to<00:27:40.590> improve<00:27:40.920> the<00:27:40.980> performance<00:27:41.250> as 00:27:41.690 --> 00:27:41.700 align:start position:0% continue to improve the performance as 00:27:41.700 --> 00:27:43.669 align:start position:0% continue to improve the performance as we<00:27:42.059> implement<00:27:42.330> more<00:27:42.720> of<00:27:42.929> our<00:27:43.080> scalability 00:27:43.669 --> 00:27:43.679 align:start position:0% we implement more of our scalability 00:27:43.679 --> 00:27:46.760 align:start position:0% we implement more of our scalability architecture<00:27:44.600> into<00:27:45.600> the<00:27:45.720> test<00:27:45.900> net<00:27:46.050> so<00:27:46.470> we're 00:27:46.760 --> 00:27:46.770 align:start position:0% architecture into the test net so we're 00:27:46.770 --> 00:27:50.150 align:start position:0% architecture into the test net so we're really<00:27:46.920> excited<00:27:47.010> about<00:27:47.429> this<00:27:48.860> this<00:27:49.860> will<00:27:50.070> be 00:27:50.150 --> 00:27:50.160 align:start position:0% really excited about this this will be 00:27:50.160 --> 00:27:53.180 align:start position:0% really excited about this this will be available<00:27:50.700> very<00:27:51.000> very<00:27:51.300> soon<00:27:51.620> so<00:27:52.620> if<00:27:52.980> you're 00:27:53.180 --> 00:27:53.190 align:start position:0% available very very soon so if you're 00:27:53.190 --> 00:27:55.730 align:start position:0% available very very soon so if you're interested<00:27:53.700> I<00:27:53.910> encourage<00:27:53.940> you<00:27:54.450> to<00:27:54.480> go<00:27:54.780> to<00:27:54.840> OSS 00:27:55.730 --> 00:27:55.740 align:start position:0% interested I encourage you to go to OSS 00:27:55.740 --> 00:27:58.010 align:start position:0% interested I encourage you to go to OSS labs<00:27:55.920> calm<00:27:56.340> we<00:27:57.240> there's<00:27:57.660> still<00:27:57.870> be<00:27:57.960> an 00:27:58.010 --> 00:27:58.020 align:start position:0% labs calm we there's still be an 00:27:58.020 --> 00:27:59.210 align:start position:0% labs calm we there's still be an application<00:27:58.500> process<00:27:58.890> but<00:27:59.070> we've 00:27:59.210 --> 00:27:59.220 align:start position:0% application process but we've 00:27:59.220 --> 00:28:00.770 align:start position:0% application process but we've streamlined<00:27:59.490> the<00:27:59.820> process<00:27:59.850> you<00:28:00.450> should<00:28:00.480> hear 00:28:00.770 --> 00:28:00.780 align:start position:0% streamlined the process you should hear 00:28:00.780 --> 00:28:02.299 align:start position:0% streamlined the process you should hear back<00:28:00.809> from<00:28:00.960> us<00:28:01.290> probably<00:28:01.679> within<00:28:01.830> 24<00:28:02.280> hours 00:28:02.299 --> 00:28:02.309 align:start position:0% back from us probably within 24 hours 00:28:02.309 --> 00:28:04.610 align:start position:0% back from us probably within 24 hours and<00:28:02.760> you<00:28:03.090> can<00:28:03.240> immediately<00:28:03.510> start<00:28:03.809> building 00:28:04.610 --> 00:28:04.620 align:start position:0% and you can immediately start building 00:28:04.620 --> 00:28:05.930 align:start position:0% and you can immediately start building your<00:28:04.710> applications<00:28:05.280> so<00:28:05.400> that<00:28:05.610> they'll<00:28:05.790> be 00:28:05.930 --> 00:28:05.940 align:start position:0% your applications so that they'll be 00:28:05.940 --> 00:28:08.270 align:start position:0% your applications so that they'll be ready<00:28:06.480> to<00:28:06.570> go<00:28:06.780> by<00:28:07.020> the<00:28:07.050> time<00:28:07.350> we<00:28:07.980> launch<00:28:08.160> our 00:28:08.270 --> 00:28:08.280 align:start position:0% ready to go by the time we launch our 00:28:08.280 --> 00:28:11.180 align:start position:0% ready to go by the time we launch our main<00:28:08.460> net<00:28:09.050> so<00:28:10.050> if<00:28:10.470> you<00:28:10.740> want<00:28:10.890> to<00:28:10.950> build<00:28:11.040> an 00:28:11.180 --> 00:28:11.190 align:start position:0% main net so if you want to build an 00:28:11.190 --> 00:28:12.620 align:start position:0% main net so if you want to build an application<00:28:11.309> you<00:28:11.760> can<00:28:11.850> go<00:28:11.910> here<00:28:12.300> if<00:28:12.480> you're 00:28:12.620 --> 00:28:12.630 align:start position:0% application you can go here if you're 00:28:12.630 --> 00:28:14.630 align:start position:0% application you can go here if you're excited<00:28:12.870> about<00:28:13.110> this<00:28:13.350> project<00:28:13.620> or<00:28:13.980> about 00:28:14.630 --> 00:28:14.640 align:start position:0% excited about this project or about 00:28:14.640 --> 00:28:17.000 align:start position:0% excited about this project or about confidentiality<00:28:15.450> and<00:28:15.840> secure<00:28:16.410> hardware<00:28:16.559> and 00:28:17.000 --> 00:28:17.010 align:start position:0% confidentiality and secure hardware and 00:28:17.010 --> 00:28:19.490 align:start position:0% confidentiality and secure hardware and machine<00:28:17.610> learning<00:28:17.640> in<00:28:18.150> general<00:28:18.540> we'd<00:28:19.320> love<00:28:19.470> to 00:28:19.490 --> 00:28:19.500 align:start position:0% machine learning in general we'd love to 00:28:19.500 --> 00:28:21.020 align:start position:0% machine learning in general we'd love to work<00:28:19.590> with<00:28:19.740> you<00:28:19.890> either<00:28:20.250> as<00:28:20.520> researchers 00:28:21.020 --> 00:28:21.030 align:start position:0% work with you either as researchers 00:28:21.030 --> 00:28:23.570 align:start position:0% work with you either as researchers collaborators<00:28:21.809> as<00:28:22.740> well<00:28:22.950> as<00:28:23.010> team<00:28:23.130> members<00:28:23.250> so 00:28:23.570 --> 00:28:23.580 align:start position:0% collaborators as well as team members so 00:28:23.580 --> 00:28:25.910 align:start position:0% collaborators as well as team members so we're<00:28:23.820> hiring<00:28:24.000> you<00:28:24.210> can<00:28:24.390> go<00:28:24.480> to<00:28:24.570> this<00:28:24.660> URL<00:28:24.920> to 00:28:25.910 --> 00:28:25.920 align:start position:0% we're hiring you can go to this URL to 00:28:25.920 --> 00:28:29.120 align:start position:0% we're hiring you can go to this URL to see<00:28:25.950> the<00:28:26.130> job<00:28:26.309> openings<00:28:26.960> so<00:28:27.960> that's<00:28:28.140> it<00:28:28.290> if<00:28:29.070> you 00:28:29.120 --> 00:28:29.130 align:start position:0% see the job openings so that's it if you 00:28:29.130 --> 00:28:30.350 align:start position:0% see the job openings so that's it if you want<00:28:29.309> to<00:28:29.340> find<00:28:29.460> out<00:28:29.610> more<00:28:29.760> go<00:28:29.820> to<00:28:29.970> always<00:28:30.210> this 00:28:30.350 --> 00:28:30.360 align:start position:0% want to find out more go to always this 00:28:30.360 --> 00:28:32.390 align:start position:0% want to find out more go to always this lab<00:28:30.510> calm<00:28:30.900> and<00:28:31.230> follow<00:28:31.500> us<00:28:31.800> on<00:28:31.950> Twitter<00:28:32.190> at 00:28:32.390 --> 00:28:32.400 align:start position:0% lab calm and follow us on Twitter at 00:28:32.400 --> 00:28:38.990 align:start position:0% lab calm and follow us on Twitter at Oasis<00:28:32.880> labs<00:28:33.230> thank<00:28:34.230> you 00:28:38.990 --> 00:28:39.000 align:start position:0% 00:28:39.000 --> 00:28:45.240 align:start position:0% we<00:28:40.000> have<00:28:40.120> time<00:28:40.360> for<00:28:40.390> one<00:28:40.600> question<00:28:43.919> yes<00:28:44.919> I<00:28:44.950> I 00:28:45.240 --> 00:28:45.250 align:start position:0% we have time for one question yes I I 00:28:45.250 --> 00:28:46.770 align:start position:0% we have time for one question yes I I just<00:28:45.640> wondered<00:28:46.030> with<00:28:46.510> your 00:28:46.770 --> 00:28:46.780 align:start position:0% just wondered with your 00:28:46.780 --> 00:28:50.100 align:start position:0% just wondered with your privacy-preserving<00:28:47.710> smart<00:28:48.610> contracts<00:28:49.150> if 00:28:50.100 --> 00:28:50.110 align:start position:0% privacy-preserving smart contracts if 00:28:50.110 --> 00:28:52.230 align:start position:0% privacy-preserving smart contracts if the<00:28:50.380> inputs<00:28:50.799> and<00:28:50.980> outputs<00:28:51.100> are<00:28:51.580> encrypted<00:28:52.120> and 00:28:52.230 --> 00:28:52.240 align:start position:0% the inputs and outputs are encrypted and 00:28:52.240 --> 00:28:54.840 align:start position:0% the inputs and outputs are encrypted and I<00:28:52.330> can't<00:28:52.780> see<00:28:52.960> it<00:28:53.049> run<00:28:53.320> how<00:28:53.830> does<00:28:54.040> consensus 00:28:54.840 --> 00:28:54.850 align:start position:0% I can't see it run how does consensus 00:28:54.850 --> 00:28:57.810 align:start position:0% I can't see it run how does consensus work<00:28:55.090> on<00:28:55.480> a<00:28:55.540> blockchain<00:28:55.980> right<00:28:56.980> so<00:28:57.190> we'll 00:28:57.810 --> 00:28:57.820 align:start position:0% work on a blockchain right so we'll 00:28:57.820 --> 00:28:59.669 align:start position:0% work on a blockchain right so we'll describe<00:28:58.179> that<00:28:58.360> in<00:28:58.600> the<00:28:59.140> paper<00:28:59.350> that<00:28:59.440> we'll 00:28:59.669 --> 00:28:59.679 align:start position:0% describe that in the paper that we'll 00:28:59.679 --> 00:29:01.039 align:start position:0% describe that in the paper that we'll publish<00:28:59.799> about<00:29:00.070> this<00:29:00.370> new<00:29:00.490> architecture 00:29:01.039 --> 00:29:01.049 align:start position:0% publish about this new architecture 00:29:01.049 --> 00:29:04.470 align:start position:0% publish about this new architecture conceptually<00:29:02.049> the<00:29:03.040> nodes<00:29:03.340> that<00:29:03.760> validate 00:29:04.470 --> 00:29:04.480 align:start position:0% conceptually the nodes that validate 00:29:04.480 --> 00:29:06.840 align:start position:0% conceptually the nodes that validate transactions<00:29:05.140> the<00:29:05.320> transactions<00:29:05.980> still<00:29:06.610> run 00:29:06.840 --> 00:29:06.850 align:start position:0% transactions the transactions still run 00:29:06.850 --> 00:29:09.360 align:start position:0% transactions the transactions still run on<00:29:07.090> multiple<00:29:07.419> workers<00:29:07.900> the<00:29:08.650> encrypted 00:29:09.360 --> 00:29:09.370 align:start position:0% on multiple workers the encrypted 00:29:09.370 --> 00:29:11.280 align:start position:0% on multiple workers the encrypted results<00:29:09.880> are<00:29:10.000> sent<00:29:10.299> back<00:29:10.540> and<00:29:10.840> you<00:29:11.080> can<00:29:11.260> have 00:29:11.280 --> 00:29:11.290 align:start position:0% results are sent back and you can have 00:29:11.290 --> 00:29:13.710 align:start position:0% results are sent back and you can have the<00:29:11.530> same<00:29:11.740> sort<00:29:12.070> of<00:29:12.190> validation<00:29:13.120> process<00:29:13.540> that 00:29:13.710 --> 00:29:13.720 align:start position:0% the same sort of validation process that 00:29:13.720 --> 00:29:15.030 align:start position:0% the same sort of validation process that you<00:29:13.870> would<00:29:13.990> have<00:29:14.080> in<00:29:14.260> other<00:29:14.350> systems<00:29:14.620> where 00:29:15.030 --> 00:29:15.040 align:start position:0% you would have in other systems where 00:29:15.040 --> 00:29:17.010 align:start position:0% you would have in other systems where you<00:29:15.760> compare<00:29:16.179> the<00:29:16.330> results<00:29:16.690> from<00:29:16.809> multiple 00:29:17.010 --> 00:29:17.020 align:start position:0% you compare the results from multiple 00:29:17.020 --> 00:29:19.500 align:start position:0% you compare the results from multiple independent<00:29:17.860> workers<00:29:18.190> and<00:29:18.460> if<00:29:19.030> there's<00:29:19.240> any 00:29:19.500 --> 00:29:19.510 align:start position:0% independent workers and if there's any 00:29:19.510 --> 00:29:21.780 align:start position:0% independent workers and if there's any discrepancy<00:29:20.500> in<00:29:20.590> those<00:29:20.740> results<00:29:20.919> then<00:29:21.669> you 00:29:21.780 --> 00:29:21.790 align:start position:0% discrepancy in those results then you 00:29:21.790 --> 00:29:23.669 align:start position:0% discrepancy in those results then you know<00:29:22.000> that<00:29:22.299> one<00:29:22.480> of<00:29:22.510> the<00:29:22.630> workers<00:29:22.840> actually 00:29:23.669 --> 00:29:23.679 align:start position:0% know that one of the workers actually 00:29:23.679 --> 00:29:25.350 align:start position:0% know that one of the workers actually produced<00:29:24.040> the<00:29:24.190> wrong<00:29:24.460> result<00:29:24.820> and<00:29:25.000> there's 00:29:25.350 --> 00:29:25.360 align:start position:0% produced the wrong result and there's 00:29:25.360 --> 00:29:26.880 align:start position:0% produced the wrong result and there's ways<00:29:25.510> of<00:29:25.630> resolving<00:29:26.049> that<00:29:26.200> and<00:29:26.470> punishing 00:29:26.880 --> 00:29:26.890 align:start position:0% ways of resolving that and punishing 00:29:26.890 --> 00:29:28.830 align:start position:0% ways of resolving that and punishing those<00:29:27.010> workers<00:29:27.370> so<00:29:27.790> intuitively<00:29:28.480> that's<00:29:28.660> how 00:29:28.830 --> 00:29:28.840 align:start position:0% those workers so intuitively that's how 00:29:28.840 --> 00:29:30.659 align:start position:0% those workers so intuitively that's how it<00:29:28.929> works<00:29:29.080> there's<00:29:29.290> a<00:29:29.320> lot<00:29:29.440> more<00:29:29.559> details<00:29:29.980> and 00:29:30.659 --> 00:29:30.669 align:start position:0% it works there's a lot more details and 00:29:30.669 --> 00:29:31.860 align:start position:0% it works there's a lot more details and those<00:29:30.790> will<00:29:30.940> all<00:29:31.000> be<00:29:31.120> in<00:29:31.240> the<00:29:31.270> paper<00:29:31.480> good 00:29:31.860 --> 00:29:31.870 align:start position:0% those will all be in the paper good 00:29:31.870 --> 00:29:33.840 align:start position:0% those will all be in the paper good question<00:29:32.169> I<00:29:32.350> think<00:29:33.220> we're<00:29:33.400> out<00:29:33.429> of<00:29:33.520> time<00:29:33.580> I'm 00:29:33.840 --> 00:29:33.850 align:start position:0% question I think we're out of time I'm 00:29:33.850 --> 00:29:34.890 align:start position:0% question I think we're out of time I'm gonna<00:29:34.000> hang<00:29:34.210> out<00:29:34.270> here<00:29:34.330> for<00:29:34.510> a<00:29:34.630> little<00:29:34.690> while 00:29:34.890 --> 00:29:34.900 align:start position:0% gonna hang out here for a little while 00:29:34.900 --> 00:29:36.240 align:start position:0% gonna hang out here for a little while if<00:29:34.990> you<00:29:35.049> have<00:29:35.110> other<00:29:35.320> questions<00:29:35.380> yeah<00:29:36.070> this 00:29:36.240 --> 00:29:36.250 align:start position:0% if you have other questions yeah this 00:29:36.250 --> 00:29:37.620 align:start position:0% if you have other questions yeah this room<00:29:36.460> is<00:29:36.549> empty<00:29:36.760> so<00:29:37.059> if<00:29:37.179> you<00:29:37.299> guys<00:29:37.419> have 00:29:37.620 --> 00:29:37.630 align:start position:0% room is empty so if you guys have 00:29:37.630 --> 00:29:38.909 align:start position:0% room is empty so if you guys have questions<00:29:37.809> for<00:29:38.049> them<00:29:38.260> you<00:29:38.350> can<00:29:38.470> just<00:29:38.530> come<00:29:38.770> up 00:29:38.909 --> 00:29:38.919 align:start position:0% questions for them you can just come up 00:29:38.919 --> 00:29:48.870 align:start position:0% questions for them you can just come up and<00:29:39.100> talk<00:29:39.190> in<00:29:39.520> person<00:29:39.730> thank<00:29:40.510> you<00:29:40.630> guys 00:29:48.870 --> 00:29:48.880 align:start position:0% 00:29:48.880 --> 00:29:50.940 align:start position:0% you