WEBVTT Kind: captions Language: en 00:00:14.610 --> 00:00:17.070 align:start position:0% hi<00:00:15.610> everyone<00:00:15.970> good<00:00:16.119> morning<00:00:16.299> thanks<00:00:16.929> for 00:00:17.070 --> 00:00:17.080 align:start position:0% hi everyone good morning thanks for 00:00:17.080 --> 00:00:20.970 align:start position:0% hi everyone good morning thanks for coming<00:00:17.710> at<00:00:17.829> this<00:00:17.859> early<00:00:18.699> hour<00:00:18.929> hopefully<00:00:19.980> no 00:00:20.970 --> 00:00:20.980 align:start position:0% coming at this early hour hopefully no 00:00:20.980 --> 00:00:22.559 align:start position:0% coming at this early hour hopefully no one's<00:00:21.189> too<00:00:21.369> hungover 00:00:22.559 --> 00:00:22.569 align:start position:0% one's too hungover 00:00:22.569 --> 00:00:25.620 align:start position:0% one's too hungover so<00:00:23.349> I'm<00:00:24.189> gonna<00:00:24.399> talk<00:00:24.669> about<00:00:24.699> enigma<00:00:25.449> and 00:00:25.620 --> 00:00:25.630 align:start position:0% so I'm gonna talk about enigma and 00:00:25.630 --> 00:00:28.139 align:start position:0% so I'm gonna talk about enigma and specifically<00:00:26.529> our<00:00:26.880> decentralized<00:00:27.880> data 00:00:28.139 --> 00:00:28.149 align:start position:0% specifically our decentralized data 00:00:28.149 --> 00:00:39.540 align:start position:0% specifically our decentralized data marketplace<00:00:28.720> protocol<00:00:38.220> all<00:00:39.220> right 00:00:39.540 --> 00:00:39.550 align:start position:0% marketplace protocol all right 00:00:39.550 --> 00:00:41.430 align:start position:0% marketplace protocol all right hey<00:00:39.760> everyone<00:00:40.030> again<00:00:40.240> good<00:00:40.420> morning<00:00:40.690> I'm 00:00:41.430 --> 00:00:41.440 align:start position:0% hey everyone again good morning I'm 00:00:41.440 --> 00:00:43.320 align:start position:0% hey everyone again good morning I'm gonna<00:00:41.710> talk<00:00:41.950> to<00:00:41.980> you<00:00:42.130> about<00:00:42.220> enigma<00:00:42.820> enigma' 00:00:43.320 --> 00:00:43.330 align:start position:0% gonna talk to you about enigma enigma' 00:00:43.330 --> 00:00:45.090 align:start position:0% gonna talk to you about enigma enigma' is<00:00:43.570> building<00:00:43.990> a<00:00:44.170> decentralized<00:00:44.920> data 00:00:45.090 --> 00:00:45.100 align:start position:0% is building a decentralized data 00:00:45.100 --> 00:00:47.820 align:start position:0% is building a decentralized data marketplace<00:00:45.670> that<00:00:46.600> is<00:00:46.750> part<00:00:47.050> on<00:00:47.290> chain<00:00:47.620> on 00:00:47.820 --> 00:00:47.830 align:start position:0% marketplace that is part on chain on 00:00:47.830 --> 00:00:50.520 align:start position:0% marketplace that is part on chain on ethereum<00:00:48.100> in<00:00:48.520> part<00:00:48.790> off<00:00:48.970> chain<00:00:49.270> so<00:00:50.230> the 00:00:50.520 --> 00:00:50.530 align:start position:0% ethereum in part off chain so the 00:00:50.530 --> 00:00:52.800 align:start position:0% ethereum in part off chain so the background<00:00:50.740> to<00:00:51.130> enigma<00:00:51.520> starts<00:00:51.910> at<00:00:52.060> MIT<00:00:52.450> in 00:00:52.800 --> 00:00:52.810 align:start position:0% background to enigma starts at MIT in 00:00:52.810 --> 00:00:57.330 align:start position:0% background to enigma starts at MIT in 2015<00:00:53.910> we<00:00:54.910> launched<00:00:55.450> a<00:00:55.600> enigma<00:00:56.140> project<00:00:56.560> from 00:00:57.330 --> 00:00:57.340 align:start position:0% 2015 we launched a enigma project from 00:00:57.340 --> 00:01:00.110 align:start position:0% 2015 we launched a enigma project from there<00:00:57.579> where<00:00:58.510> we<00:00:58.600> basically<00:00:59.100> conceptualize 00:01:00.110 --> 00:01:00.120 align:start position:0% there where we basically conceptualize 00:01:00.120 --> 00:01:02.910 align:start position:0% there where we basically conceptualize at<00:01:01.120> the<00:01:01.270> centralized<00:01:01.750> computation<00:01:02.410> platform 00:01:02.910 --> 00:01:02.920 align:start position:0% at the centralized computation platform 00:01:02.920 --> 00:01:05.209 align:start position:0% at the centralized computation platform that<00:01:03.489> can<00:01:03.640> guarantee<00:01:03.880> both<00:01:04.449> privacy<00:01:04.930> and 00:01:05.209 --> 00:01:05.219 align:start position:0% that can guarantee both privacy and 00:01:05.219 --> 00:01:07.679 align:start position:0% that can guarantee both privacy and correctness<00:01:06.219> and<00:01:06.579> with<00:01:06.789> better<00:01:06.999> scale<00:01:07.420> than 00:01:07.679 --> 00:01:07.689 align:start position:0% correctness and with better scale than 00:01:07.689 --> 00:01:10.620 align:start position:0% correctness and with better scale than just<00:01:07.990> blocks<00:01:08.289> and<00:01:08.560> themself<00:01:09.399> allow<00:01:09.640> how<00:01:10.420> many 00:01:10.620 --> 00:01:10.630 align:start position:0% just blocks and themself allow how many 00:01:10.630 --> 00:01:12.149 align:start position:0% just blocks and themself allow how many of<00:01:10.780> you<00:01:10.899> here<00:01:11.140> have<00:01:11.200> like<00:01:11.530> seen<00:01:11.799> that<00:01:11.979> white 00:01:12.149 --> 00:01:12.159 align:start position:0% of you here have like seen that white 00:01:12.159 --> 00:01:14.010 align:start position:0% of you here have like seen that white paper<00:01:12.399> like<00:01:12.789> our<00:01:12.999> familiar<00:01:13.450> with<00:01:13.600> the<00:01:13.689> enigma 00:01:14.010 --> 00:01:14.020 align:start position:0% paper like our familiar with the enigma 00:01:14.020 --> 00:01:16.050 align:start position:0% paper like our familiar with the enigma project<00:01:14.409> from<00:01:14.530> that<00:01:14.710> sense<00:01:14.950> all<00:01:15.759> right<00:01:15.850> not 00:01:16.050 --> 00:01:16.060 align:start position:0% project from that sense all right not 00:01:16.060 --> 00:01:19.499 align:start position:0% project from that sense all right not not<00:01:16.420> bad<00:01:16.689> not<00:01:16.899> bad<00:01:17.880> so<00:01:18.880> cool<00:01:19.090> yeah<00:01:19.240> it's<00:01:19.359> been 00:01:19.499 --> 00:01:19.509 align:start position:0% not bad not bad so cool yeah it's been 00:01:19.509 --> 00:01:21.090 align:start position:0% not bad not bad so cool yeah it's been sighted<00:01:19.960> quite<00:01:20.200> a<00:01:20.229> lot<00:01:20.469> I<00:01:20.499> think<00:01:20.679> it's<00:01:20.889> one<00:01:21.009> of 00:01:21.090 --> 00:01:21.100 align:start position:0% sighted quite a lot I think it's one of 00:01:21.100 --> 00:01:22.649 align:start position:0% sighted quite a lot I think it's one of the<00:01:21.189> more<00:01:21.310> sighted<00:01:21.759> white<00:01:22.060> papers<00:01:22.450> in<00:01:22.569> the 00:01:22.649 --> 00:01:22.659 align:start position:0% the more sighted white papers in the 00:01:22.659 --> 00:01:25.950 align:start position:0% the more sighted white papers in the space<00:01:22.920> download<00:01:23.920> it<00:01:24.039> quite<00:01:24.249> frequently<00:01:24.450> so<00:01:25.450> I 00:01:25.950 --> 00:01:25.960 align:start position:0% space download it quite frequently so I 00:01:25.960 --> 00:01:27.419 align:start position:0% space download it quite frequently so I guess<00:01:26.409> there's<00:01:26.619> a<00:01:26.649> lot<00:01:26.799> of<00:01:26.889> people<00:01:27.009> who<00:01:27.189> share 00:01:27.419 --> 00:01:27.429 align:start position:0% guess there's a lot of people who share 00:01:27.429 --> 00:01:35.819 align:start position:0% guess there's a lot of people who share our<00:01:27.460> vision<00:01:29.429> and<00:01:31.829> yeah<00:01:34.289> anyone<00:01:35.289> can<00:01:35.350> help<00:01:35.709> me 00:01:35.819 --> 00:01:35.829 align:start position:0% our vision and yeah anyone can help me 00:01:35.829 --> 00:01:41.170 align:start position:0% our vision and yeah anyone can help me with<00:01:36.069> the<00:01:36.249> slide 00:01:41.170 --> 00:01:41.180 align:start position:0% 00:01:41.180 --> 00:01:50.860 align:start position:0% I<00:01:41.920> should<00:01:42.920> go<00:01:43.040> closer<00:01:46.330> nice<00:01:47.330> coupe<00:01:48.190> so<00:01:49.870> some 00:01:50.860 --> 00:01:50.870 align:start position:0% I should go closer nice coupe so some 00:01:50.870 --> 00:01:53.350 align:start position:0% I should go closer nice coupe so some apart<00:01:51.140> of<00:01:51.290> motivation<00:01:51.830> so<00:01:52.160> our<00:01:52.610> motivations 00:01:53.350 --> 00:01:53.360 align:start position:0% apart of motivation so our motivations 00:01:53.360 --> 00:01:55.390 align:start position:0% apart of motivation so our motivations you<00:01:53.540> know<00:01:53.780> data<00:01:54.020> is<00:01:54.200> everywhere<00:01:54.530> it's<00:01:55.160> the 00:01:55.390 --> 00:01:55.400 align:start position:0% you know data is everywhere it's the 00:01:55.400 --> 00:01:57.310 align:start position:0% you know data is everywhere it's the most<00:01:55.580> valuable<00:01:56.150> asset<00:01:56.660> right<00:01:56.840> now<00:01:57.050> in<00:01:57.230> the 00:01:57.310 --> 00:01:57.320 align:start position:0% most valuable asset right now in the 00:01:57.320 --> 00:01:58.360 align:start position:0% most valuable asset right now in the 21st<00:01:57.710> century 00:01:58.360 --> 00:01:58.370 align:start position:0% 21st century 00:01:58.370 --> 00:02:00.520 align:start position:0% 21st century but<00:01:58.850> right<00:01:59.000> now<00:01:59.210> the<00:01:59.270> situation<00:01:59.540> is<00:02:00.080> that<00:02:00.110> only 00:02:00.520 --> 00:02:00.530 align:start position:0% but right now the situation is that only 00:02:00.530 --> 00:02:02.500 align:start position:0% but right now the situation is that only a<00:02:00.680> handful<00:02:01.130> of<00:02:01.190> companies<00:02:01.460> can<00:02:02.270> really 00:02:02.500 --> 00:02:02.510 align:start position:0% a handful of companies can really 00:02:02.510 --> 00:02:04.420 align:start position:0% a handful of companies can really capitalize<00:02:02.750> on<00:02:03.140> that<00:02:03.320> you<00:02:03.920> know<00:02:04.040> they're<00:02:04.190> hard 00:02:04.420 --> 00:02:04.430 align:start position:0% capitalize on that you know they're hard 00:02:04.430 --> 00:02:06.160 align:start position:0% capitalize on that you know they're hard you<00:02:04.520> need<00:02:04.640> the<00:02:04.820> monetize<00:02:05.300> you<00:02:05.390> need<00:02:05.570> but 00:02:06.160 --> 00:02:06.170 align:start position:0% you need the monetize you need but 00:02:06.170 --> 00:02:07.570 align:start position:0% you need the monetize you need but that's<00:02:06.410> not<00:02:06.620> something<00:02:07.040> that<00:02:07.070> the<00:02:07.310> open 00:02:07.570 --> 00:02:07.580 align:start position:0% that's not something that the open 00:02:07.580 --> 00:02:09.999 align:start position:0% that's not something that the open public<00:02:07.760> can<00:02:08.330> take<00:02:08.540> part<00:02:08.780> in<00:02:08.960> and<00:02:09.200> that<00:02:09.740> is<00:02:09.860> what 00:02:09.999 --> 00:02:10.009 align:start position:0% public can take part in and that is what 00:02:10.009 --> 00:02:13.780 align:start position:0% public can take part in and that is what we<00:02:10.190> are<00:02:10.310> said<00:02:10.580> to<00:02:10.729> protocol<00:02:12.400> I'm<00:02:13.400> gonna<00:02:13.640> give 00:02:13.780 --> 00:02:13.790 align:start position:0% we are said to protocol I'm gonna give 00:02:13.790 --> 00:02:16.180 align:start position:0% we are said to protocol I'm gonna give you<00:02:13.880> a<00:02:13.940> quick<00:02:14.209> outline<00:02:14.450> of<00:02:14.690> my<00:02:14.990> talk<00:02:15.020> I'm<00:02:15.860> gonna 00:02:16.180 --> 00:02:16.190 align:start position:0% you a quick outline of my talk I'm gonna 00:02:16.190 --> 00:02:18.670 align:start position:0% you a quick outline of my talk I'm gonna first<00:02:16.520> of<00:02:16.700> all<00:02:16.820> speak<00:02:17.300> about<00:02:17.600> you<00:02:17.870> know<00:02:17.990> what 00:02:18.670 --> 00:02:18.680 align:start position:0% first of all speak about you know what 00:02:18.680 --> 00:02:20.170 align:start position:0% first of all speak about you know what is<00:02:18.830> the<00:02:18.890> data<00:02:19.070> marketplace<00:02:19.640> at<00:02:19.910> a<00:02:19.940> high<00:02:20.150> level 00:02:20.170 --> 00:02:20.180 align:start position:0% is the data marketplace at a high level 00:02:20.180 --> 00:02:22.660 align:start position:0% is the data marketplace at a high level how<00:02:21.050> does<00:02:21.290> the<00:02:21.440> arm<00:02:21.650> chain<00:02:21.980> works<00:02:22.250> with<00:02:22.459> the<00:02:22.520> of 00:02:22.660 --> 00:02:22.670 align:start position:0% how does the arm chain works with the of 00:02:22.670 --> 00:02:25.000 align:start position:0% how does the arm chain works with the of chain<00:02:22.970> for<00:02:23.510> the<00:02:23.690> stakeholders<00:02:24.410> and<00:02:24.680> how<00:02:24.860> we're 00:02:25.000 --> 00:02:25.010 align:start position:0% chain for the stakeholders and how we're 00:02:25.010 --> 00:02:28.210 align:start position:0% chain for the stakeholders and how we're thinking<00:02:25.040> about<00:02:25.459> designing<00:02:25.940> this<00:02:26.240> I<00:02:27.110> will<00:02:27.920> at 00:02:28.210 --> 00:02:28.220 align:start position:0% thinking about designing this I will at 00:02:28.220 --> 00:02:30.970 align:start position:0% thinking about designing this I will at that<00:02:28.580> point<00:02:28.910> I<00:02:29.240> will<00:02:29.510> not<00:02:29.900> focus<00:02:30.170> on<00:02:30.530> you<00:02:30.860> know 00:02:30.970 --> 00:02:30.980 align:start position:0% that point I will not focus on you know 00:02:30.980 --> 00:02:32.680 align:start position:0% that point I will not focus on you know how<00:02:31.160> the<00:02:31.220> network<00:02:31.520> stores<00:02:32.030> data<00:02:32.330> how 00:02:32.680 --> 00:02:32.690 align:start position:0% how the network stores data how 00:02:32.690 --> 00:02:35.440 align:start position:0% how the network stores data how computation<00:02:33.410> is<00:02:33.530> done<00:02:34.000> that<00:02:35.000> would<00:02:35.180> be<00:02:35.300> the 00:02:35.440 --> 00:02:35.450 align:start position:0% computation is done that would be the 00:02:35.450 --> 00:02:37.420 align:start position:0% computation is done that would be the second<00:02:35.810> part<00:02:36.020> of<00:02:36.080> the<00:02:36.200> talk<00:02:36.380> when<00:02:36.650> we<00:02:36.830> like<00:02:37.220> go 00:02:37.420 --> 00:02:37.430 align:start position:0% second part of the talk when we like go 00:02:37.430 --> 00:02:39.640 align:start position:0% second part of the talk when we like go deeply<00:02:37.850> into<00:02:37.940> that<00:02:38.330> again<00:02:39.080> given<00:02:39.440> time 00:02:39.640 --> 00:02:39.650 align:start position:0% deeply into that again given time 00:02:39.650 --> 00:02:41.020 align:start position:0% deeply into that again given time constraints<00:02:39.800> this<00:02:40.400> is<00:02:40.490> going<00:02:40.670> to<00:02:40.760> be<00:02:40.820> pretty 00:02:41.020 --> 00:02:41.030 align:start position:0% constraints this is going to be pretty 00:02:41.030 --> 00:02:44.230 align:start position:0% constraints this is going to be pretty high<00:02:41.240> level<00:02:41.890> and<00:02:42.890> finally<00:02:43.850> I'm<00:02:43.910> going<00:02:44.030> to<00:02:44.120> give 00:02:44.230 --> 00:02:44.240 align:start position:0% high level and finally I'm going to give 00:02:44.240 --> 00:02:46.030 align:start position:0% high level and finally I'm going to give you<00:02:44.330> a<00:02:44.390> taste<00:02:44.660> of<00:02:44.810> catalyst<00:02:45.320> calories<00:02:45.860> is<00:02:45.950> an 00:02:46.030 --> 00:02:46.040 align:start position:0% you a taste of catalyst calories is an 00:02:46.040 --> 00:02:47.650 align:start position:0% you a taste of catalyst calories is an application<00:02:46.489> that<00:02:46.730> we're<00:02:46.910> developing<00:02:47.120> that 00:02:47.650 --> 00:02:47.660 align:start position:0% application that we're developing that 00:02:47.660 --> 00:02:50.350 align:start position:0% application that we're developing that is<00:02:48.560> going<00:02:48.950> to<00:02:49.040> be<00:02:49.130> the<00:02:49.250> first<00:02:49.430> one<00:02:49.730> to<00:02:49.850> live<00:02:50.090> on 00:02:50.350 --> 00:02:50.360 align:start position:0% is going to be the first one to live on 00:02:50.360 --> 00:02:54.729 align:start position:0% is going to be the first one to live on the<00:02:50.570> data<00:02:50.750> marketplace<00:02:52.900> all<00:02:53.900> right<00:02:53.989> so<00:02:54.230> at<00:02:54.560> the 00:02:54.729 --> 00:02:54.739 align:start position:0% the data marketplace all right so at the 00:02:54.739 --> 00:02:56.890 align:start position:0% the data marketplace all right so at the high<00:02:54.890> level<00:02:55.310> you<00:02:55.850> know<00:02:56.000> the<00:02:56.239> enigma<00:02:56.750> data 00:02:56.890 --> 00:02:56.900 align:start position:0% high level you know the enigma data 00:02:56.900 --> 00:02:58.570 align:start position:0% high level you know the enigma data marketplace<00:02:57.410> it<00:02:57.680> has<00:02:57.920> three<00:02:58.550> main 00:02:58.570 --> 00:02:58.580 align:start position:0% marketplace it has three main 00:02:58.580 --> 00:03:01.509 align:start position:0% marketplace it has three main stakeholders<00:02:59.440> which<00:03:00.440> are<00:03:00.650> pretty<00:03:00.890> pretty 00:03:01.509 --> 00:03:01.519 align:start position:0% stakeholders which are pretty pretty 00:03:01.519 --> 00:03:03.820 align:start position:0% stakeholders which are pretty pretty obvious<00:03:02.150> and<00:03:02.330> trivial<00:03:02.660> you<00:03:03.200> have<00:03:03.380> data 00:03:03.820 --> 00:03:03.830 align:start position:0% obvious and trivial you have data 00:03:03.830 --> 00:03:06.250 align:start position:0% obvious and trivial you have data providers<00:03:04.430> those<00:03:05.360> who<00:03:05.540> want<00:03:05.690> to<00:03:05.750> sell<00:03:06.050> data 00:03:06.250 --> 00:03:06.260 align:start position:0% providers those who want to sell data 00:03:06.260 --> 00:03:08.740 align:start position:0% providers those who want to sell data data<00:03:06.830> consumers<00:03:07.310> those<00:03:08.060> who<00:03:08.209> want<00:03:08.360> to<00:03:08.450> consume 00:03:08.740 --> 00:03:08.750 align:start position:0% data consumers those who want to consume 00:03:08.750 --> 00:03:10.840 align:start position:0% data consumers those who want to consume data<00:03:08.989> and<00:03:09.440> on<00:03:10.040> the<00:03:10.190> off<00:03:10.340> chain<00:03:10.640> you<00:03:10.820> have 00:03:10.840 --> 00:03:10.850 align:start position:0% data and on the off chain you have 00:03:10.850 --> 00:03:13.840 align:start position:0% data and on the off chain you have worker<00:03:11.660> nodes<00:03:11.930> which<00:03:12.500> are<00:03:12.680> basically<00:03:13.190> you 00:03:13.840 --> 00:03:13.850 align:start position:0% worker nodes which are basically you 00:03:13.850 --> 00:03:16.000 align:start position:0% worker nodes which are basically you know<00:03:13.970> just<00:03:14.000> nodes<00:03:14.540> who<00:03:15.050> don't<00:03:15.350> have<00:03:15.530> any<00:03:15.709> stake 00:03:16.000 --> 00:03:16.010 align:start position:0% know just nodes who don't have any stake 00:03:16.010 --> 00:03:18.340 align:start position:0% know just nodes who don't have any stake in<00:03:16.220> the<00:03:16.340> data<00:03:16.550> buying<00:03:16.910> or<00:03:17.060> selling<00:03:17.140> but<00:03:18.140> there 00:03:18.340 --> 00:03:18.350 align:start position:0% in the data buying or selling but there 00:03:18.350 --> 00:03:19.449 align:start position:0% in the data buying or selling but there are<00:03:18.440> the<00:03:18.530> ones<00:03:18.739> who<00:03:18.860> are<00:03:18.890> actually<00:03:19.190> storing 00:03:19.449 --> 00:03:19.459 align:start position:0% are the ones who are actually storing 00:03:19.459 --> 00:03:22.090 align:start position:0% are the ones who are actually storing the<00:03:19.580> data<00:03:19.610> doing<00:03:20.390> computation<00:03:21.260> answering 00:03:22.090 --> 00:03:22.100 align:start position:0% the data doing computation answering 00:03:22.100 --> 00:03:24.580 align:start position:0% the data doing computation answering queries<00:03:22.370> and<00:03:22.760> so<00:03:23.030> forth<00:03:23.330> so<00:03:23.930> my<00:03:24.080> focus<00:03:24.350> right 00:03:24.580 --> 00:03:24.590 align:start position:0% queries and so forth so my focus right 00:03:24.590 --> 00:03:27.250 align:start position:0% queries and so forth so my focus right now<00:03:24.769> is<00:03:24.799> going<00:03:25.040> to<00:03:25.100> be<00:03:25.220> mostly<00:03:25.670> on<00:03:25.970> the<00:03:26.299> on<00:03:26.660> the 00:03:27.250 --> 00:03:27.260 align:start position:0% now is going to be mostly on the on the 00:03:27.260 --> 00:03:28.900 align:start position:0% now is going to be mostly on the on the kind<00:03:27.680> of<00:03:27.739> the<00:03:27.830> contracts<00:03:28.250> between<00:03:28.430> the<00:03:28.760> data 00:03:28.900 --> 00:03:28.910 align:start position:0% kind of the contracts between the data 00:03:28.910 --> 00:03:33.460 align:start position:0% kind of the contracts between the data providers<00:03:29.480> and<00:03:29.660> data<00:03:29.840> consumers<00:03:30.260> first<00:03:32.470> so 00:03:33.460 --> 00:03:33.470 align:start position:0% providers and data consumers first so 00:03:33.470 --> 00:03:35.140 align:start position:0% providers and data consumers first so starting<00:03:33.860> with<00:03:33.950> the<00:03:34.040> data<00:03:34.220> provider<00:03:34.610> a<00:03:34.910> data 00:03:35.140 --> 00:03:35.150 align:start position:0% starting with the data provider a data 00:03:35.150 --> 00:03:37.030 align:start position:0% starting with the data provider a data provider<00:03:35.480> comes<00:03:35.840> has<00:03:36.200> the<00:03:36.350> data<00:03:36.590> said<00:03:36.860> that 00:03:37.030 --> 00:03:37.040 align:start position:0% provider comes has the data said that 00:03:37.040 --> 00:03:40.840 align:start position:0% provider comes has the data said that they<00:03:37.130> want<00:03:37.400> to<00:03:37.610> sell<00:03:38.560> what<00:03:39.560> they<00:03:39.590> do<00:03:39.769> is<00:03:40.100> first 00:03:40.840 --> 00:03:40.850 align:start position:0% they want to sell what they do is first 00:03:40.850 --> 00:03:43.270 align:start position:0% they want to sell what they do is first of<00:03:41.000> all<00:03:41.150> they<00:03:41.570> provide<00:03:41.959> enough<00:03:42.530> context<00:03:43.130> to 00:03:43.270 --> 00:03:43.280 align:start position:0% of all they provide enough context to 00:03:43.280 --> 00:03:46.210 align:start position:0% of all they provide enough context to the<00:03:43.549> oft<00:03:43.760> a<00:03:44.060> network<00:03:44.510> they<00:03:45.170> basically<00:03:45.860> need<00:03:46.070> to 00:03:46.210 --> 00:03:46.220 align:start position:0% the oft a network they basically need to 00:03:46.220 --> 00:03:48.490 align:start position:0% the oft a network they basically need to register<00:03:46.400> the<00:03:46.850> data<00:03:47.060> set<00:03:47.330> now<00:03:48.019> that<00:03:48.260> could<00:03:48.440> be 00:03:48.490 --> 00:03:48.500 align:start position:0% register the data set now that could be 00:03:48.500 --> 00:03:50.500 align:start position:0% register the data set now that could be in<00:03:48.709> one<00:03:48.890> of<00:03:48.950> two<00:03:49.190> ways<00:03:49.220> either<00:03:49.639> they<00:03:50.030> come<00:03:50.269> they 00:03:50.500 --> 00:03:50.510 align:start position:0% in one of two ways either they come they 00:03:50.510 --> 00:03:52.539 align:start position:0% in one of two ways either they come they upload<00:03:51.019> the<00:03:51.320> data<00:03:51.530> to<00:03:51.739> the<00:03:51.829> network<00:03:52.190> and<00:03:52.370> I 00:03:52.539 --> 00:03:52.549 align:start position:0% upload the data to the network and I 00:03:52.549 --> 00:03:53.980 align:start position:0% upload the data to the network and I will<00:03:52.730> show<00:03:52.910> later<00:03:53.090> on<00:03:53.389> how<00:03:53.600> that's 00:03:53.980 --> 00:03:53.990 align:start position:0% will show later on how that's 00:03:53.990 --> 00:03:56.650 align:start position:0% will show later on how that's done<00:03:54.110> securely<00:03:54.650> or<00:03:55.160> they<00:03:55.820> can<00:03:56.060> actually<00:03:56.210> store 00:03:56.650 --> 00:03:56.660 align:start position:0% done securely or they can actually store 00:03:56.660 --> 00:03:58.750 align:start position:0% done securely or they can actually store it<00:03:56.810> in<00:03:57.050> some<00:03:57.320> some<00:03:57.800> of<00:03:57.920> their<00:03:58.070> own<00:03:58.220> nodes<00:03:58.520> and 00:03:58.750 --> 00:03:58.760 align:start position:0% it in some some of their own nodes and 00:03:58.760 --> 00:04:00.670 align:start position:0% it in some some of their own nodes and just<00:03:59.270> provide<00:03:59.600> enough<00:03:59.840> context<00:04:00.380> to<00:04:00.500> the 00:04:00.670 --> 00:04:00.680 align:start position:0% just provide enough context to the 00:04:00.680 --> 00:04:02.950 align:start position:0% just provide enough context to the network<00:04:01.040> onward<00:04:01.670> that<00:04:01.820> daily<00:04:02.060> lives<00:04:02.360> the 00:04:02.950 --> 00:04:02.960 align:start position:0% network onward that daily lives the 00:04:02.960 --> 00:04:05.230 align:start position:0% network onward that daily lives the network<00:04:03.290> then<00:04:03.530> computes<00:04:04.190> some<00:04:04.880> kind<00:04:05.150> of 00:04:05.230 --> 00:04:05.240 align:start position:0% network then computes some kind of 00:04:05.240 --> 00:04:08.320 align:start position:0% network then computes some kind of address<00:04:06.070> like<00:04:07.070> a<00:04:07.100> permanent<00:04:07.580> address<00:04:07.700> kind<00:04:08.270> of 00:04:08.320 --> 00:04:08.330 align:start position:0% address like a permanent address kind of 00:04:08.330 --> 00:04:10.930 align:start position:0% address like a permanent address kind of like<00:04:08.420> a<00:04:08.510> DNS<00:04:08.870> that<00:04:09.340> the<00:04:10.340> network<00:04:10.640> can<00:04:10.670> then 00:04:10.930 --> 00:04:10.940 align:start position:0% like a DNS that the network can then 00:04:10.940 --> 00:04:14.950 align:start position:0% like a DNS that the network can then route<00:04:11.320> consumers<00:04:12.320> to<00:04:12.620> that<00:04:12.770> data<00:04:12.980> set<00:04:13.960> the 00:04:14.950 --> 00:04:14.960 align:start position:0% route consumers to that data set the 00:04:14.960 --> 00:04:16.810 align:start position:0% route consumers to that data set the data<00:04:15.380> provider<00:04:15.770> then<00:04:15.980> takes<00:04:16.280> that<00:04:16.430> address 00:04:16.810 --> 00:04:16.820 align:start position:0% data provider then takes that address 00:04:16.820 --> 00:04:18.630 align:start position:0% data provider then takes that address that<00:04:17.030> unique<00:04:17.300> address<00:04:17.600> some<00:04:18.320> meats 00:04:18.630 --> 00:04:18.640 align:start position:0% that unique address some meats 00:04:18.640 --> 00:04:21.910 align:start position:0% that unique address some meats transaction<00:04:19.640> to<00:04:19.760> the<00:04:19.790> blockchain<00:04:20.650> also<00:04:21.650> puts 00:04:21.910 --> 00:04:21.920 align:start position:0% transaction to the blockchain also puts 00:04:21.920 --> 00:04:23.670 align:start position:0% transaction to the blockchain also puts like<00:04:22.130> the<00:04:22.280> price<00:04:22.520> of<00:04:22.550> the<00:04:22.790> data<00:04:23.000> in<00:04:23.210> some<00:04:23.390> other 00:04:23.670 --> 00:04:23.680 align:start position:0% like the price of the data in some other 00:04:23.680 --> 00:04:27.700 align:start position:0% like the price of the data in some other metadata<00:04:24.680> and<00:04:25.190> also<00:04:26.000> stores<00:04:26.330> a<00:04:26.540> deposit<00:04:27.200> which 00:04:27.700 --> 00:04:27.710 align:start position:0% metadata and also stores a deposit which 00:04:27.710 --> 00:04:32.440 align:start position:0% metadata and also stores a deposit which I'll<00:04:27.980> touch<00:04:28.280> a<00:04:28.340> bit<00:04:28.640> later<00:04:28.880> on<00:04:31.150> now<00:04:32.150> that<00:04:32.360> the 00:04:32.440 --> 00:04:32.450 align:start position:0% I'll touch a bit later on now that the 00:04:32.450 --> 00:04:34.360 align:start position:0% I'll touch a bit later on now that the day<00:04:32.630> that<00:04:32.870> that<00:04:32.900> data<00:04:33.380> set<00:04:33.620> is<00:04:33.710> registered<00:04:34.160> on 00:04:34.360 --> 00:04:34.370 align:start position:0% day that that data set is registered on 00:04:34.370 --> 00:04:36.370 align:start position:0% day that that data set is registered on chain<00:04:34.700> there's<00:04:35.330> a<00:04:35.390> reference<00:04:35.900> to<00:04:36.050> it<00:04:36.170> off 00:04:36.370 --> 00:04:36.380 align:start position:0% chain there's a reference to it off 00:04:36.380 --> 00:04:39.250 align:start position:0% chain there's a reference to it off chain<00:04:36.710> a<00:04:37.400> data<00:04:37.910> consumer<00:04:38.450> can<00:04:38.630> actually<00:04:38.990> come 00:04:39.250 --> 00:04:39.260 align:start position:0% chain a data consumer can actually come 00:04:39.260 --> 00:04:41.200 align:start position:0% chain a data consumer can actually come in<00:04:39.470> and<00:04:39.710> send<00:04:40.340> a<00:04:40.400> message<00:04:40.700> to<00:04:40.730> the<00:04:41.000> blockchain 00:04:41.200 --> 00:04:41.210 align:start position:0% in and send a message to the blockchain 00:04:41.210 --> 00:04:44.050 align:start position:0% in and send a message to the blockchain saying<00:04:41.690> hey<00:04:42.170> I<00:04:42.470> want<00:04:42.500> to<00:04:42.860> subscribe<00:04:43.430> to<00:04:43.940> this 00:04:44.050 --> 00:04:44.060 align:start position:0% saying hey I want to subscribe to this 00:04:44.060 --> 00:04:46.420 align:start position:0% saying hey I want to subscribe to this feed<00:04:44.300> of<00:04:44.450> data<00:04:44.660> and<00:04:45.020> obviously<00:04:45.770> they<00:04:46.190> need<00:04:46.340> to 00:04:46.420 --> 00:04:46.430 align:start position:0% feed of data and obviously they need to 00:04:46.430 --> 00:04:48.160 align:start position:0% feed of data and obviously they need to provide<00:04:46.670> payment<00:04:47.180> and<00:04:47.450> they<00:04:47.690> also<00:04:47.870> need<00:04:48.140> to 00:04:48.160 --> 00:04:48.170 align:start position:0% provide payment and they also need to 00:04:48.170 --> 00:04:51.370 align:start position:0% provide payment and they also need to provide<00:04:48.410> a<00:04:49.010> deposit<00:04:49.970> a<00:04:50.120> deposit<00:04:50.690> is<00:04:50.870> there<00:04:51.110> in 00:04:51.370 --> 00:04:51.380 align:start position:0% provide a deposit a deposit is there in 00:04:51.380 --> 00:04:55.090 align:start position:0% provide a deposit a deposit is there in case<00:04:52.150> the<00:04:53.150> consumer<00:04:54.020> defaults<00:04:54.770> in<00:04:54.950> their 00:04:55.090 --> 00:04:55.100 align:start position:0% case the consumer defaults in their 00:04:55.100 --> 00:05:00.760 align:start position:0% case the consumer defaults in their payments<00:04:55.580> in<00:04:55.730> the<00:04:55.850> future<00:04:58.690> so<00:04:59.690> one<00:05:00.230> note<00:05:00.440> about 00:05:00.760 --> 00:05:00.770 align:start position:0% payments in the future so one note about 00:05:00.770 --> 00:05:03.160 align:start position:0% payments in the future so one note about the<00:05:01.070> incentive<00:05:01.640> structure<00:05:02.000> here<00:05:02.330> really<00:05:03.050> what 00:05:03.160 --> 00:05:03.170 align:start position:0% the incentive structure here really what 00:05:03.170 --> 00:05:05.170 align:start position:0% the incentive structure here really what enigma<00:05:03.620> is<00:05:03.710> trying<00:05:03.920> to<00:05:04.070> do<00:05:04.220> is<00:05:04.400> is<00:05:04.670> it's<00:05:04.970> trying 00:05:05.170 --> 00:05:05.180 align:start position:0% enigma is trying to do is is it's trying 00:05:05.180 --> 00:05:08.620 align:start position:0% enigma is trying to do is is it's trying to<00:05:05.510> kind<00:05:05.900> of<00:05:05.960> tokenize<00:05:06.580> or<00:05:07.580> capture<00:05:08.180> in<00:05:08.480> a 00:05:08.620 --> 00:05:08.630 align:start position:0% to kind of tokenize or capture in a 00:05:08.630 --> 00:05:10.660 align:start position:0% to kind of tokenize or capture in a token<00:05:09.050> the<00:05:09.500> value<00:05:09.800> of<00:05:09.890> data<00:05:10.040> we're<00:05:10.340> trying<00:05:10.550> to 00:05:10.660 --> 00:05:10.670 align:start position:0% token the value of data we're trying to 00:05:10.670 --> 00:05:12.340 align:start position:0% token the value of data we're trying to make<00:05:10.820> something<00:05:11.210> that's<00:05:11.360> really<00:05:11.450> implicit 00:05:12.340 --> 00:05:12.350 align:start position:0% make something that's really implicit 00:05:12.350 --> 00:05:15.460 align:start position:0% make something that's really implicit today<00:05:12.740> and<00:05:13.010> kind<00:05:13.520> of<00:05:13.670> I<00:05:13.880> guess<00:05:14.330> stuck<00:05:15.050> behind 00:05:15.460 --> 00:05:15.470 align:start position:0% today and kind of I guess stuck behind 00:05:15.470 --> 00:05:17.110 align:start position:0% today and kind of I guess stuck behind walls<00:05:15.770> we're<00:05:16.310> trying<00:05:16.520> to<00:05:16.670> make<00:05:16.820> that<00:05:17.000> more 00:05:17.110 --> 00:05:17.120 align:start position:0% walls we're trying to make that more 00:05:17.120 --> 00:05:20.290 align:start position:0% walls we're trying to make that more open<00:05:17.630> and<00:05:17.840> very<00:05:18.110> very<00:05:18.440> very<00:05:19.130> explicit<00:05:19.730> so 00:05:20.290 --> 00:05:20.300 align:start position:0% open and very very very explicit so 00:05:20.300 --> 00:05:21.760 align:start position:0% open and very very very explicit so there<00:05:20.510> are<00:05:20.570> two<00:05:20.750> ways<00:05:20.780> in<00:05:20.990> which<00:05:21.410> the 00:05:21.760 --> 00:05:21.770 align:start position:0% there are two ways in which the 00:05:21.770 --> 00:05:24.190 align:start position:0% there are two ways in which the incentives<00:05:22.310> mechanics<00:05:23.180> kind<00:05:23.390> of<00:05:23.480> work<00:05:23.630> the 00:05:24.190 --> 00:05:24.200 align:start position:0% incentives mechanics kind of work the 00:05:24.200 --> 00:05:27.160 align:start position:0% incentives mechanics kind of work the first<00:05:24.470> one<00:05:24.680> is<00:05:24.800> the<00:05:24.920> value<00:05:25.250> of<00:05:25.280> data<00:05:26.170> directly 00:05:27.160 --> 00:05:27.170 align:start position:0% first one is the value of data directly 00:05:27.170 --> 00:05:29.500 align:start position:0% first one is the value of data directly that's<00:05:27.440> an<00:05:27.560> explicit<00:05:28.130> metric<00:05:28.550> so<00:05:29.180> a<00:05:29.210> data 00:05:29.500 --> 00:05:29.510 align:start position:0% that's an explicit metric so a data 00:05:29.510 --> 00:05:31.960 align:start position:0% that's an explicit metric so a data provider<00:05:29.720> basically<00:05:30.380> sets<00:05:30.710> a<00:05:30.860> price<00:05:31.130> to<00:05:31.820> what 00:05:31.960 --> 00:05:31.970 align:start position:0% provider basically sets a price to what 00:05:31.970 --> 00:05:33.730 align:start position:0% provider basically sets a price to what the<00:05:32.090> data<00:05:32.300> it's<00:05:32.510> worse<00:05:32.660> and<00:05:32.930> then<00:05:33.320> the<00:05:33.440> market 00:05:33.730 --> 00:05:33.740 align:start position:0% the data it's worse and then the market 00:05:33.740 --> 00:05:35.530 align:start position:0% the data it's worse and then the market either<00:05:33.920> buys<00:05:34.250> into<00:05:34.520> that<00:05:34.670> or<00:05:35.030> no<00:05:35.180> that's<00:05:35.450> like 00:05:35.530 --> 00:05:35.540 align:start position:0% either buys into that or no that's like 00:05:35.540 --> 00:05:38.080 align:start position:0% either buys into that or no that's like the<00:05:35.690> explicit<00:05:36.170> value<00:05:36.500> of<00:05:36.560> data<00:05:36.740> and<00:05:37.130> they<00:05:37.880> have 00:05:38.080 --> 00:05:38.090 align:start position:0% the explicit value of data and they have 00:05:38.090 --> 00:05:40.270 align:start position:0% the explicit value of data and they have to<00:05:38.240> share<00:05:38.450> their<00:05:38.510> earnings<00:05:39.170> with<00:05:39.860> the<00:05:40.010> nodes 00:05:40.270 --> 00:05:40.280 align:start position:0% to share their earnings with the nodes 00:05:40.280 --> 00:05:42.640 align:start position:0% to share their earnings with the nodes the<00:05:41.180> worker<00:05:41.390> nodes<00:05:41.750> in<00:05:41.930> the<00:05:42.050> network<00:05:42.380> that<00:05:42.500> are 00:05:42.640 --> 00:05:42.650 align:start position:0% the worker nodes in the network that are 00:05:42.650 --> 00:05:44.740 align:start position:0% the worker nodes in the network that are doing<00:05:42.830> computation<00:05:43.670> that<00:05:43.910> are<00:05:44.360> doing<00:05:44.510> the 00:05:44.740 --> 00:05:44.750 align:start position:0% doing computation that are doing the 00:05:44.750 --> 00:05:46.690 align:start position:0% doing computation that are doing the storage<00:05:45.170> and<00:05:45.470> that<00:05:45.950> is<00:05:46.100> really<00:05:46.280> where<00:05:46.670> the 00:05:46.690 --> 00:05:46.700 align:start position:0% storage and that is really where the 00:05:46.700 --> 00:05:49.800 align:start position:0% storage and that is really where the implicit<00:05:47.240> value<00:05:47.810> of<00:05:47.870> data<00:05:48.080> is<00:05:48.500> also<00:05:48.920> reflected 00:05:49.800 --> 00:05:49.810 align:start position:0% implicit value of data is also reflected 00:05:49.810 --> 00:05:52.600 align:start position:0% implicit value of data is also reflected another<00:05:50.810> note<00:05:51.080> about<00:05:51.380> discovery<00:05:51.980> in<00:05:52.100> ranking 00:05:52.600 --> 00:05:52.610 align:start position:0% another note about discovery in ranking 00:05:52.610 --> 00:05:54.940 align:start position:0% another note about discovery in ranking so<00:05:52.910> we<00:05:53.060> expect<00:05:53.510> to<00:05:53.660> have<00:05:53.840> you<00:05:54.320> know<00:05:54.440> eventually 00:05:54.940 --> 00:05:54.950 align:start position:0% so we expect to have you know eventually 00:05:54.950 --> 00:05:56.890 align:start position:0% so we expect to have you know eventually many<00:05:55.460> thousands<00:05:56.060> of<00:05:56.120> data<00:05:56.390> sets<00:05:56.660> in<00:05:56.810> our 00:05:56.890 --> 00:05:56.900 align:start position:0% many thousands of data sets in our 00:05:56.900 --> 00:05:59.440 align:start position:0% many thousands of data sets in our system<00:05:57.320> of<00:05:57.470> all<00:05:58.010> kinds<00:05:58.610> you<00:05:59.060> know<00:05:59.120> we<00:05:59.300> can 00:05:59.440 --> 00:05:59.450 align:start position:0% system of all kinds you know we can 00:05:59.450 --> 00:06:01.300 align:start position:0% system of all kinds you know we can employ<00:05:59.720> some<00:06:00.080> statistical<00:06:00.710> methods<00:06:01.130> we<00:06:01.280> can 00:06:01.300 --> 00:06:01.310 align:start position:0% employ some statistical methods we can 00:06:01.310 --> 00:06:03.640 align:start position:0% employ some statistical methods we can tag<00:06:01.700> data<00:06:01.970> cells<00:06:02.300> but<00:06:02.870> in<00:06:02.990> the<00:06:03.110> end<00:06:03.229> of<00:06:03.320> the<00:06:03.440> day 00:06:03.640 --> 00:06:03.650 align:start position:0% tag data cells but in the end of the day 00:06:03.650 --> 00:06:06.159 align:start position:0% tag data cells but in the end of the day we<00:06:04.640> need<00:06:04.760> to<00:06:04.820> find<00:06:05.090> some<00:06:05.330> mechanism<00:06:05.810> to<00:06:05.900> rank 00:06:06.159 --> 00:06:06.169 align:start position:0% we need to find some mechanism to rank 00:06:06.169 --> 00:06:07.390 align:start position:0% we need to find some mechanism to rank datasets<00:06:06.710> that<00:06:06.830> are<00:06:07.070> kind 00:06:07.390 --> 00:06:07.400 align:start position:0% datasets that are kind 00:06:07.400 --> 00:06:09.700 align:start position:0% datasets that are kind like<00:06:07.520> in<00:06:07.729> the<00:06:07.850> same<00:06:08.030> bucket<00:06:08.270> and<00:06:08.690> the<00:06:09.229> best<00:06:09.470> way 00:06:09.700 --> 00:06:09.710 align:start position:0% like in the same bucket and the best way 00:06:09.710 --> 00:06:12.400 align:start position:0% like in the same bucket and the best way we<00:06:10.009> see<00:06:10.400> to<00:06:10.550> do<00:06:10.699> that<00:06:10.910> is<00:06:11.120> by<00:06:11.690> directly 00:06:12.400 --> 00:06:12.410 align:start position:0% we see to do that is by directly 00:06:12.410 --> 00:06:15.999 align:start position:0% we see to do that is by directly correlating<00:06:13.370> the<00:06:13.970> economic<00:06:14.600> incentive<00:06:15.259> that 00:06:15.999 --> 00:06:16.009 align:start position:0% correlating the economic incentive that 00:06:16.009 --> 00:06:19.150 align:start position:0% correlating the economic incentive that is<00:06:16.310> locked<00:06:16.940> in<00:06:17.449> a<00:06:17.600> data<00:06:17.810> set<00:06:18.139> with<00:06:18.710> its<00:06:18.830> rank 00:06:19.150 --> 00:06:19.160 align:start position:0% is locked in a data set with its rank 00:06:19.160 --> 00:06:23.020 align:start position:0% is locked in a data set with its rank what<00:06:19.850> I<00:06:19.880> mean<00:06:20.150> by<00:06:20.300> that<00:06:20.330> is<00:06:20.810> that<00:06:21.199> simply<00:06:22.130> it's 00:06:23.020 --> 00:06:23.030 align:start position:0% what I mean by that is that simply it's 00:06:23.030 --> 00:06:25.210 align:start position:0% what I mean by that is that simply it's the<00:06:23.990> amount<00:06:24.169> of<00:06:24.289> money<00:06:24.530> that<00:06:24.650> people<00:06:25.039> have 00:06:25.210 --> 00:06:25.220 align:start position:0% the amount of money that people have 00:06:25.220 --> 00:06:26.680 align:start position:0% the amount of money that people have bought<00:06:25.430> into<00:06:25.610> that<00:06:25.880> data<00:06:26.090> set 00:06:26.680 --> 00:06:26.690 align:start position:0% bought into that data set 00:06:26.690 --> 00:06:31.120 align:start position:0% bought into that data set plus<00:06:27.280> some<00:06:28.330> factorization<00:06:29.330> of<00:06:29.509> the<00:06:30.320> deposit 00:06:31.120 --> 00:06:31.130 align:start position:0% plus some factorization of the deposit 00:06:31.130 --> 00:06:33.909 align:start position:0% plus some factorization of the deposit that<00:06:31.729> the<00:06:31.970> data<00:06:32.300> provider<00:06:32.690> has<00:06:33.050> put<00:06:33.410> in<00:06:33.650> so 00:06:33.909 --> 00:06:33.919 align:start position:0% that the data provider has put in so 00:06:33.919 --> 00:06:36.070 align:start position:0% that the data provider has put in so basically<00:06:34.729> the<00:06:35.000> idea<00:06:35.030> with<00:06:35.360> the<00:06:35.419> deposit<00:06:35.720> here 00:06:36.070 --> 00:06:36.080 align:start position:0% basically the idea with the deposit here 00:06:36.080 --> 00:06:37.779 align:start position:0% basically the idea with the deposit here is<00:06:36.169> that<00:06:36.320> data<00:06:36.590> providers<00:06:37.130> need<00:06:37.310> to<00:06:37.340> kind<00:06:37.729> of 00:06:37.779 --> 00:06:37.789 align:start position:0% is that data providers need to kind of 00:06:37.789 --> 00:06:40.090 align:start position:0% is that data providers need to kind of put<00:06:38.570> their<00:06:39.139> money<00:06:39.320> where<00:06:39.470> their<00:06:39.590> mouth<00:06:39.889> is 00:06:40.090 --> 00:06:40.100 align:start position:0% put their money where their mouth is 00:06:40.100 --> 00:06:42.760 align:start position:0% put their money where their mouth is that<00:06:40.910> sets<00:06:41.270> the<00:06:41.449> rank<00:06:41.660> of<00:06:41.960> a<00:06:42.050> data<00:06:42.229> set<00:06:42.530> and 00:06:42.760 --> 00:06:42.770 align:start position:0% that sets the rank of a data set and 00:06:42.770 --> 00:06:47.350 align:start position:0% that sets the rank of a data set and kind<00:06:43.039> of<00:06:43.130> use<00:06:43.250> to<00:06:43.430> break<00:06:43.639> ties<00:06:45.789> now<00:06:46.789> this<00:06:46.970> is<00:06:47.120> a 00:06:47.350 --> 00:06:47.360 align:start position:0% kind of use to break ties now this is a 00:06:47.360 --> 00:06:49.270 align:start position:0% kind of use to break ties now this is a good<00:06:47.660> way<00:06:47.810> to<00:06:47.840> transition<00:06:48.560> to<00:06:48.740> like<00:06:49.070> the 00:06:49.270 --> 00:06:49.280 align:start position:0% good way to transition to like the 00:06:49.280 --> 00:06:52.750 align:start position:0% good way to transition to like the option<00:06:50.180> computation<00:06:50.930> and<00:06:51.229> storage<00:06:51.760> again 00:06:52.750 --> 00:06:52.760 align:start position:0% option computation and storage again 00:06:52.760 --> 00:06:54.969 align:start position:0% option computation and storage again would<00:06:53.090> be<00:06:53.120> pretty<00:06:53.419> high<00:06:53.600> level<00:06:53.930> but<00:06:54.110> I<00:06:54.169> want<00:06:54.919> to 00:06:54.969 --> 00:06:54.979 align:start position:0% would be pretty high level but I want to 00:06:54.979 --> 00:06:57.279 align:start position:0% would be pretty high level but I want to go<00:06:55.100> through<00:06:55.310> some<00:06:55.669> of<00:06:55.699> the<00:06:55.880> main<00:06:56.030> ideas<00:06:56.289> this 00:06:57.279 --> 00:06:57.289 align:start position:0% go through some of the main ideas this 00:06:57.289 --> 00:06:58.480 align:start position:0% go through some of the main ideas this is<00:06:57.440> really<00:06:57.650> where<00:06:57.800> the<00:06:57.830> heavy<00:06:58.130> lifting 00:06:58.480 --> 00:06:58.490 align:start position:0% is really where the heavy lifting 00:06:58.490 --> 00:07:01.060 align:start position:0% is really where the heavy lifting happens<00:06:58.849> off<00:06:59.090> chain<00:06:59.530> and<00:07:00.530> we'll<00:07:00.740> talk<00:07:00.919> about 00:07:01.060 --> 00:07:01.070 align:start position:0% happens off chain and we'll talk about 00:07:01.070 --> 00:07:06.700 align:start position:0% happens off chain and we'll talk about that<00:07:01.340> next<00:07:02.050> so<00:07:04.300> the<00:07:05.300> main<00:07:05.449> idea<00:07:05.750> is<00:07:05.810> and<00:07:06.530> that's 00:07:06.700 --> 00:07:06.710 align:start position:0% that next so the main idea is and that's 00:07:06.710 --> 00:07:08.050 align:start position:0% that next so the main idea is and that's the<00:07:06.800> main<00:07:06.979> idea<00:07:07.009> that<00:07:07.370> we<00:07:07.460> also<00:07:07.580> set<00:07:07.880> in<00:07:08.000> the 00:07:08.050 --> 00:07:08.060 align:start position:0% the main idea that we also set in the 00:07:08.060 --> 00:07:11.170 align:start position:0% the main idea that we also set in the 2015<00:07:08.630> white<00:07:08.780> paper<00:07:09.020> is<00:07:09.349> as<00:07:10.160> follows<00:07:10.550> global 00:07:11.170 --> 00:07:11.180 align:start position:0% 2015 white paper is as follows global 00:07:11.180 --> 00:07:13.240 align:start position:0% 2015 white paper is as follows global consensus<00:07:11.630> is<00:07:11.750> expensive<00:07:12.320> I<00:07:12.560> think<00:07:12.590> all<00:07:13.010> of<00:07:13.039> us 00:07:13.240 --> 00:07:13.250 align:start position:0% consensus is expensive I think all of us 00:07:13.250 --> 00:07:16.450 align:start position:0% consensus is expensive I think all of us here<00:07:13.520> are<00:07:13.760> aware<00:07:14.120> of<00:07:14.210> that<00:07:14.620> it's<00:07:15.620> not<00:07:15.889> scalable 00:07:16.450 --> 00:07:16.460 align:start position:0% here are aware of that it's not scalable 00:07:16.460 --> 00:07:18.490 align:start position:0% here are aware of that it's not scalable it's<00:07:16.760> very<00:07:17.030> very<00:07:17.180> pricey<00:07:17.479> we<00:07:18.139> need<00:07:18.260> to<00:07:18.349> figure 00:07:18.490 --> 00:07:18.500 align:start position:0% it's very very pricey we need to figure 00:07:18.500 --> 00:07:20.740 align:start position:0% it's very very pricey we need to figure out<00:07:18.680> a<00:07:18.710> way<00:07:18.889> to<00:07:19.310> basically<00:07:19.760> segment<00:07:20.660> the 00:07:20.740 --> 00:07:20.750 align:start position:0% out a way to basically segment the 00:07:20.750 --> 00:07:23.230 align:start position:0% out a way to basically segment the network<00:07:21.139> and<00:07:21.410> you<00:07:22.070> know<00:07:22.190> and<00:07:22.849> four<00:07:23.090> different 00:07:23.230 --> 00:07:23.240 align:start position:0% network and you know and four different 00:07:23.240 --> 00:07:26.189 align:start position:0% network and you know and four different computations<00:07:24.050> for<00:07:24.289> different<00:07:24.849> storage 00:07:26.189 --> 00:07:26.199 align:start position:0% computations for different storage 00:07:26.199 --> 00:07:28.600 align:start position:0% computations for different storage different<00:07:27.199> data<00:07:27.380> set<00:07:27.650> data<00:07:28.099> blocks<00:07:28.430> of 00:07:28.600 --> 00:07:28.610 align:start position:0% different data set data blocks of 00:07:28.610 --> 00:07:30.670 align:start position:0% different data set data blocks of restoring<00:07:29.090> we<00:07:29.630> need<00:07:29.810> to<00:07:29.900> make<00:07:30.050> sure<00:07:30.289> that<00:07:30.440> only 00:07:30.670 --> 00:07:30.680 align:start position:0% restoring we need to make sure that only 00:07:30.680 --> 00:07:33.040 align:start position:0% restoring we need to make sure that only some<00:07:31.039> of<00:07:31.159> the<00:07:31.280> network<00:07:31.580> is<00:07:31.760> utilized<00:07:32.330> and<00:07:32.599> we 00:07:33.040 --> 00:07:33.050 align:start position:0% some of the network is utilized and we 00:07:33.050 --> 00:07:34.570 align:start position:0% some of the network is utilized and we need<00:07:33.169> to<00:07:33.260> do<00:07:33.380> it<00:07:33.500> in<00:07:33.590> a<00:07:33.680> way<00:07:33.800> that's<00:07:34.099> secure 00:07:34.570 --> 00:07:34.580 align:start position:0% need to do it in a way that's secure 00:07:34.580 --> 00:07:38.260 align:start position:0% need to do it in a way that's secure enough<00:07:35.270> again<00:07:36.169> it<00:07:36.380> does<00:07:36.590> it's<00:07:36.979> not<00:07:37.250> as<00:07:37.580> you 00:07:38.260 --> 00:07:38.270 align:start position:0% enough again it does it's not as you 00:07:38.270 --> 00:07:40.120 align:start position:0% enough again it does it's not as you know<00:07:38.389> won't<00:07:38.840> be<00:07:39.020> as<00:07:39.139> perfect<00:07:39.620> security<00:07:39.710> is 00:07:40.120 --> 00:07:40.130 align:start position:0% know won't be as perfect security is 00:07:40.130 --> 00:07:42.490 align:start position:0% know won't be as perfect security is like<00:07:40.400> global<00:07:40.909> consensus<00:07:41.419> but<00:07:42.020> good<00:07:42.260> enough 00:07:42.490 --> 00:07:42.500 align:start position:0% like global consensus but good enough 00:07:42.500 --> 00:07:44.800 align:start position:0% like global consensus but good enough for<00:07:42.979> you<00:07:43.460> know<00:07:43.580> decentralized<00:07:44.240> needs<00:07:44.539> and 00:07:44.800 --> 00:07:44.810 align:start position:0% for you know decentralized needs and 00:07:44.810 --> 00:07:48.010 align:start position:0% for you know decentralized needs and scalable<00:07:45.680> enough<00:07:46.330> there<00:07:47.330> are<00:07:47.360> a<00:07:47.510> couple<00:07:47.810> of 00:07:48.010 --> 00:07:48.020 align:start position:0% scalable enough there are a couple of 00:07:48.020 --> 00:07:50.890 align:start position:0% scalable enough there are a couple of good<00:07:48.199> ways<00:07:48.409> to<00:07:48.680> do<00:07:48.830> that<00:07:49.070> you<00:07:49.970> know<00:07:50.570> first<00:07:50.780> of 00:07:50.890 --> 00:07:50.900 align:start position:0% good ways to do that you know first of 00:07:50.900 --> 00:07:53.140 align:start position:0% good ways to do that you know first of all<00:07:51.020> let<00:07:51.139> me<00:07:51.169> let<00:07:51.770> me<00:07:51.800> let<00:07:51.889> me<00:07:52.099> touch<00:07:52.280> on<00:07:52.430> the<00:07:52.610> on 00:07:53.140 --> 00:07:53.150 align:start position:0% all let me let me let me touch on the on 00:07:53.150 --> 00:07:55.000 align:start position:0% all let me let me let me touch on the on the<00:07:53.570> stake<00:07:53.780> on<00:07:53.990> the<00:07:54.110> stake<00:07:54.320> holders<00:07:54.620> here<00:07:54.800> so 00:07:55.000 --> 00:07:55.010 align:start position:0% the stake on the stake holders here so 00:07:55.010 --> 00:07:56.830 align:start position:0% the stake on the stake holders here so you<00:07:55.550> probably<00:07:55.729> know<00:07:56.090> this<00:07:56.240> is<00:07:56.419> shardene 00:07:56.830 --> 00:07:56.840 align:start position:0% you probably know this is shardene 00:07:56.840 --> 00:07:58.750 align:start position:0% you probably know this is shardene that's<00:07:57.080> kind<00:07:57.680> of<00:07:57.710> what<00:07:57.860> has<00:07:57.979> been<00:07:58.190> popularized 00:07:58.750 --> 00:07:58.760 align:start position:0% that's kind of what has been popularized 00:07:58.760 --> 00:08:01.719 align:start position:0% that's kind of what has been popularized in<00:07:59.030> the<00:07:59.120> space<00:07:59.389> I'm<00:08:00.260> gonna<00:08:00.560> use<00:08:00.680> quorums<00:08:01.310> from 00:08:01.719 --> 00:08:01.729 align:start position:0% in the space I'm gonna use quorums from 00:08:01.729 --> 00:08:03.879 align:start position:0% in the space I'm gonna use quorums from these<00:08:02.000> more<00:08:02.539> of<00:08:02.630> an<00:08:02.720> academic<00:08:02.900> term<00:08:03.470> saying 00:08:03.879 --> 00:08:03.889 align:start position:0% these more of an academic term saying 00:08:03.889 --> 00:08:06.790 align:start position:0% these more of an academic term saying that<00:08:04.190> you<00:08:04.789> you<00:08:05.270> have<00:08:05.599> a<00:08:05.630> large<00:08:06.080> network<00:08:06.380> you 00:08:06.790 --> 00:08:06.800 align:start position:0% that you you have a large network you 00:08:06.800 --> 00:08:08.770 align:start position:0% that you you have a large network you select<00:08:07.460> like<00:08:07.669> a<00:08:07.849> committee<00:08:08.270> and<00:08:08.599> that 00:08:08.770 --> 00:08:08.780 align:start position:0% select like a committee and that 00:08:08.780 --> 00:08:11.050 align:start position:0% select like a committee and that committee<00:08:08.810> is<00:08:09.409> really<00:08:09.710> in<00:08:09.889> charge<00:08:09.919> of<00:08:10.520> like 00:08:11.050 --> 00:08:11.060 align:start position:0% committee is really in charge of like 00:08:11.060 --> 00:08:12.969 align:start position:0% committee is really in charge of like some<00:08:11.419> portion<00:08:11.840> of<00:08:11.930> the<00:08:12.050> data<00:08:12.229> some<00:08:12.530> portion<00:08:12.889> of 00:08:12.969 --> 00:08:12.979 align:start position:0% some portion of the data some portion of 00:08:12.979 --> 00:08:15.010 align:start position:0% some portion of the data some portion of the<00:08:13.099> state<00:08:13.370> some<00:08:14.030> portion<00:08:14.479> of<00:08:14.720> the 00:08:15.010 --> 00:08:15.020 align:start position:0% the state some portion of the 00:08:15.020 --> 00:08:18.490 align:start position:0% the state some portion of the computation<00:08:15.740> so<00:08:17.260> what<00:08:18.260> we're<00:08:18.469> doing 00:08:18.490 --> 00:08:18.500 align:start position:0% computation so what we're doing 00:08:18.500 --> 00:08:20.090 align:start position:0% computation so what we're doing basically 00:08:20.090 --> 00:08:20.100 align:start position:0% basically 00:08:20.100 --> 00:08:22.610 align:start position:0% basically you<00:08:20.430> know<00:08:20.550> for<00:08:20.760> every<00:08:21.060> data<00:08:21.420> block<00:08:21.780> every<00:08:22.410> data 00:08:22.610 --> 00:08:22.620 align:start position:0% you know for every data block every data 00:08:22.620 --> 00:08:24.170 align:start position:0% you know for every data block every data segmentation<00:08:23.130> every<00:08:23.520> data<00:08:23.760> said<00:08:24.000> that's 00:08:24.170 --> 00:08:24.180 align:start position:0% segmentation every data said that's 00:08:24.180 --> 00:08:26.660 align:start position:0% segmentation every data said that's coming<00:08:24.510> into<00:08:24.750> the<00:08:24.960> network<00:08:25.140> the<00:08:26.130> option 00:08:26.660 --> 00:08:26.670 align:start position:0% coming into the network the option 00:08:26.670 --> 00:08:28.550 align:start position:0% coming into the network the option network<00:08:26.940> needs<00:08:27.120> to<00:08:27.330> go<00:08:27.480> into<00:08:27.810> a<00:08:27.990> randomized 00:08:28.550 --> 00:08:28.560 align:start position:0% network needs to go into a randomized 00:08:28.560 --> 00:08:30.980 align:start position:0% network needs to go into a randomized protocol<00:08:29.130> where<00:08:29.940> they<00:08:30.090> kind<00:08:30.300> of<00:08:30.390> like<00:08:30.570> flip<00:08:30.870> a 00:08:30.980 --> 00:08:30.990 align:start position:0% protocol where they kind of like flip a 00:08:30.990 --> 00:08:33.560 align:start position:0% protocol where they kind of like flip a coin<00:08:31.200> and<00:08:31.530> use<00:08:32.130> that<00:08:32.340> to<00:08:32.550> randomly<00:08:32.940> select<00:08:33.060> a 00:08:33.560 --> 00:08:33.570 align:start position:0% coin and use that to randomly select a 00:08:33.570 --> 00:08:37.070 align:start position:0% coin and use that to randomly select a subset<00:08:33.840> of<00:08:34.080> the<00:08:34.289> network<00:08:35.390> likely<00:08:36.390> small<00:08:36.810> it's 00:08:37.070 --> 00:08:37.080 align:start position:0% subset of the network likely small it's 00:08:37.080 --> 00:08:38.990 align:start position:0% subset of the network likely small it's big<00:08:37.710> enough<00:08:37.830> that<00:08:37.979> it's<00:08:38.280> secure<00:08:38.580> but<00:08:38.789> small 00:08:38.990 --> 00:08:39.000 align:start position:0% big enough that it's secure but small 00:08:39.000 --> 00:08:42.200 align:start position:0% big enough that it's secure but small enough<00:08:39.240> that<00:08:39.300> it's<00:08:39.539> scalable<00:08:39.900> and<00:08:40.849> to<00:08:41.849> select 00:08:42.200 --> 00:08:42.210 align:start position:0% enough that it's scalable and to select 00:08:42.210 --> 00:08:43.550 align:start position:0% enough that it's scalable and to select that<00:08:42.450> forum<00:08:42.840> there<00:08:43.020> are<00:08:43.080> several<00:08:43.289> techniques 00:08:43.550 --> 00:08:43.560 align:start position:0% that forum there are several techniques 00:08:43.560 --> 00:08:45.980 align:start position:0% that forum there are several techniques most<00:08:44.430> of<00:08:44.640> you<00:08:44.790> them<00:08:45.120> use<00:08:45.330> a<00:08:45.360> threshold 00:08:45.980 --> 00:08:45.990 align:start position:0% most of you them use a threshold 00:08:45.990 --> 00:08:48.650 align:start position:0% most of you them use a threshold cryptography<00:08:46.830> or<00:08:47.070> secret<00:08:48.000> cheering<00:08:48.360> which<00:08:48.540> is 00:08:48.650 --> 00:08:48.660 align:start position:0% cryptography or secret cheering which is 00:08:48.660 --> 00:08:52.250 align:start position:0% cryptography or secret cheering which is very<00:08:48.840> similar<00:08:49.140> you<00:08:50.040> can<00:08:50.460> also<00:08:50.670> use<00:08:51.260> random 00:08:52.250 --> 00:08:52.260 align:start position:0% very similar you can also use random 00:08:52.260 --> 00:08:55.550 align:start position:0% very similar you can also use random beacons<00:08:52.590> on<00:08:52.770> the<00:08:52.890> blockchain<00:08:53.450> which<00:08:54.450> are<00:08:54.870> very 00:08:55.550 --> 00:08:55.560 align:start position:0% beacons on the blockchain which are very 00:08:55.560 --> 00:08:57.710 align:start position:0% beacons on the blockchain which are very fast<00:08:55.920> but<00:08:56.400> they<00:08:56.640> have<00:08:56.880> some<00:08:57.060> trade-offs<00:08:57.510> in 00:08:57.710 --> 00:08:57.720 align:start position:0% fast but they have some trade-offs in 00:08:57.720 --> 00:08:59.440 align:start position:0% fast but they have some trade-offs in terms<00:08:57.930> of<00:08:58.200> the<00:08:58.320> entropy<00:08:58.710> that<00:08:58.800> you<00:08:58.980> can<00:08:59.160> get 00:08:59.440 --> 00:08:59.450 align:start position:0% terms of the entropy that you can get 00:08:59.450 --> 00:09:03.020 align:start position:0% terms of the entropy that you can get but<00:09:00.530> we<00:09:01.530> kind<00:09:01.890> of<00:09:01.950> like<00:09:02.100> this<00:09:02.310> black<00:09:02.580> box<00:09:02.850> you 00:09:03.020 --> 00:09:03.030 align:start position:0% but we kind of like this black box you 00:09:03.030 --> 00:09:05.210 align:start position:0% but we kind of like this black box you can<00:09:03.210> actually<00:09:03.570> for<00:09:03.810> each<00:09:03.840> data<00:09:04.200> you<00:09:05.040> can 00:09:05.210 --> 00:09:05.220 align:start position:0% can actually for each data you can 00:09:05.220 --> 00:09:07.910 align:start position:0% can actually for each data you can select<00:09:05.810> only<00:09:06.810> a<00:09:07.050> handful<00:09:07.500> of<00:09:07.530> nodes<00:09:07.800> that 00:09:07.910 --> 00:09:07.920 align:start position:0% select only a handful of nodes that 00:09:07.920 --> 00:09:09.260 align:start position:0% select only a handful of nodes that would<00:09:08.100> be<00:09:08.220> in<00:09:08.310> charge<00:09:08.550> of<00:09:08.700> that<00:09:08.820> and<00:09:09.090> that's 00:09:09.260 --> 00:09:09.270 align:start position:0% would be in charge of that and that's 00:09:09.270 --> 00:09:10.280 align:start position:0% would be in charge of that and that's where<00:09:09.420> you<00:09:09.480> kind<00:09:09.690> of<00:09:09.750> get<00:09:09.900> like<00:09:10.080> your 00:09:10.280 --> 00:09:10.290 align:start position:0% where you kind of get like your 00:09:10.290 --> 00:09:15.350 align:start position:0% where you kind of get like your scalability<00:09:10.920> properties<00:09:12.230> sorry<00:09:13.760> but<00:09:14.760> that 00:09:15.350 --> 00:09:15.360 align:start position:0% scalability properties sorry but that 00:09:15.360 --> 00:09:17.450 align:start position:0% scalability properties sorry but that raises<00:09:15.660> the<00:09:15.750> questions<00:09:16.140> once<00:09:16.620> we<00:09:16.950> have<00:09:17.160> a 00:09:17.450 --> 00:09:17.460 align:start position:0% raises the questions once we have a 00:09:17.460 --> 00:09:20.900 align:start position:0% raises the questions once we have a quorum<00:09:18.300> for<00:09:18.510> one<00:09:19.350> one<00:09:19.860> data<00:09:20.130> set<00:09:20.430> right<00:09:20.580> and 00:09:20.900 --> 00:09:20.910 align:start position:0% quorum for one one data set right and 00:09:20.910 --> 00:09:23.360 align:start position:0% quorum for one one data set right and that<00:09:21.540> core<00:09:21.780> needs<00:09:22.050> to<00:09:22.200> make<00:09:22.350> we<00:09:22.950> need<00:09:22.980> to<00:09:23.130> make 00:09:23.360 --> 00:09:23.370 align:start position:0% that core needs to make we need to make 00:09:23.370 --> 00:09:25.010 align:start position:0% that core needs to make we need to make sure<00:09:23.400> that<00:09:23.670> that<00:09:23.790> quorum<00:09:24.270> always<00:09:24.630> runs<00:09:24.870> the 00:09:25.010 --> 00:09:25.020 align:start position:0% sure that that quorum always runs the 00:09:25.020 --> 00:09:26.960 align:start position:0% sure that that quorum always runs the computation<00:09:25.620> correctly<00:09:26.160> over<00:09:26.370> that<00:09:26.520> data<00:09:26.640> set 00:09:26.960 --> 00:09:26.970 align:start position:0% computation correctly over that data set 00:09:26.970 --> 00:09:29.240 align:start position:0% computation correctly over that data set and<00:09:27.120> we<00:09:27.600> also<00:09:27.750> need<00:09:27.990> to<00:09:28.080> make<00:09:28.200> sure<00:09:28.260> that<00:09:28.500> that 00:09:29.240 --> 00:09:29.250 align:start position:0% and we also need to make sure that that 00:09:29.250 --> 00:09:31.100 align:start position:0% and we also need to make sure that that chrome<00:09:29.550> itself<00:09:29.880> cannot<00:09:30.270> actually<00:09:30.540> see<00:09:30.870> the 00:09:31.100 --> 00:09:31.110 align:start position:0% chrome itself cannot actually see the 00:09:31.110 --> 00:09:32.840 align:start position:0% chrome itself cannot actually see the underlying<00:09:31.530> data<00:09:31.800> if<00:09:32.130> that<00:09:32.550> data<00:09:32.730> is 00:09:32.840 --> 00:09:32.850 align:start position:0% underlying data if that data is 00:09:32.850 --> 00:09:34.520 align:start position:0% underlying data if that data is sensitive<00:09:33.360> these<00:09:33.960> are<00:09:34.140> the<00:09:34.230> three<00:09:34.410> key 00:09:34.520 --> 00:09:34.530 align:start position:0% sensitive these are the three key 00:09:34.530 --> 00:09:37.070 align:start position:0% sensitive these are the three key questions<00:09:34.680> that<00:09:35.220> we<00:09:35.340> have<00:09:35.550> and<00:09:35.820> I'm<00:09:36.750> going<00:09:37.050> to 00:09:37.070 --> 00:09:37.080 align:start position:0% questions that we have and I'm going to 00:09:37.080 --> 00:09:38.320 align:start position:0% questions that we have and I'm going to talk<00:09:37.260> about<00:09:37.530> that<00:09:37.680> now 00:09:38.320 --> 00:09:38.330 align:start position:0% talk about that now 00:09:38.330 --> 00:09:42.440 align:start position:0% talk about that now so<00:09:39.920> this<00:09:40.920> is<00:09:41.070> not<00:09:41.220> an<00:09:41.340> exhaustive<00:09:41.610> list<00:09:41.880> but 00:09:42.440 --> 00:09:42.450 align:start position:0% so this is not an exhaustive list but 00:09:42.450 --> 00:09:44.900 align:start position:0% so this is not an exhaustive list but this<00:09:42.570> is<00:09:42.630> meant<00:09:43.020> to<00:09:43.110> give<00:09:43.440> you<00:09:43.680> kind<00:09:44.400> of<00:09:44.520> like<00:09:44.580> a 00:09:44.900 --> 00:09:44.910 align:start position:0% this is meant to give you kind of like a 00:09:44.910 --> 00:09:46.820 align:start position:0% this is meant to give you kind of like a quick<00:09:45.300> overview<00:09:45.720> of<00:09:45.930> different<00:09:46.260> techniques 00:09:46.820 --> 00:09:46.830 align:start position:0% quick overview of different techniques 00:09:46.830 --> 00:09:49.850 align:start position:0% quick overview of different techniques in<00:09:46.980> the<00:09:47.100> literature<00:09:47.460> for<00:09:48.210> handling<00:09:48.860> outsource 00:09:49.850 --> 00:09:49.860 align:start position:0% in the literature for handling outsource 00:09:49.860 --> 00:09:53.120 align:start position:0% in the literature for handling outsource correct<00:09:50.490> computation<00:09:51.300> with<00:09:51.780> privacy<00:09:52.260> so<00:09:53.010> let 00:09:53.120 --> 00:09:53.130 align:start position:0% correct computation with privacy so let 00:09:53.130 --> 00:09:56.450 align:start position:0% correct computation with privacy so let me<00:09:53.220> go<00:09:53.340> very<00:09:53.550> quickly<00:09:53.850> over<00:09:54.210> that<00:09:55.310> first<00:09:56.310> we 00:09:56.450 --> 00:09:56.460 align:start position:0% me go very quickly over that first we 00:09:56.460 --> 00:09:58.960 align:start position:0% me go very quickly over that first we have<00:09:56.610> you<00:09:56.790> know<00:09:56.910> blockchain<00:09:57.450> blockchain<00:09:58.080> is 00:09:58.960 --> 00:09:58.970 align:start position:0% have you know blockchain blockchain is 00:09:58.970 --> 00:10:01.970 align:start position:0% have you know blockchain blockchain is you<00:09:59.970> know<00:10:00.060> fully<00:10:00.660> decentralized<00:10:00.870> gives<00:10:01.620> us<00:10:01.740> a 00:10:01.970 --> 00:10:01.980 align:start position:0% you know fully decentralized gives us a 00:10:01.980 --> 00:10:04.160 align:start position:0% you know fully decentralized gives us a very<00:10:02.400> strong<00:10:02.550> integrity<00:10:03.420> and<00:10:03.540> consists<00:10:03.900> in 00:10:04.160 --> 00:10:04.170 align:start position:0% very strong integrity and consists in 00:10:04.170 --> 00:10:06.410 align:start position:0% very strong integrity and consists in consistency<00:10:04.770> but<00:10:05.700> it's<00:10:05.850> really<00:10:06.120> bad<00:10:06.270> at 00:10:06.410 --> 00:10:06.420 align:start position:0% consistency but it's really bad at 00:10:06.420 --> 00:10:08.000 align:start position:0% consistency but it's really bad at keeping<00:10:06.450> secrets<00:10:06.840> like<00:10:07.260> there's<00:10:07.500> zero 00:10:08.000 --> 00:10:08.010 align:start position:0% keeping secrets like there's zero 00:10:08.010 --> 00:10:10.940 align:start position:0% keeping secrets like there's zero privacy<00:10:08.250> in<00:10:08.700> it<00:10:08.850> and<00:10:09.060> it's<00:10:09.690> very<00:10:10.050> and<00:10:10.650> it's<00:10:10.800> not 00:10:10.940 --> 00:10:10.950 align:start position:0% privacy in it and it's very and it's not 00:10:10.950 --> 00:10:13.880 align:start position:0% privacy in it and it's very and it's not scalable<00:10:11.190> at<00:10:11.520> all<00:10:11.870> then<00:10:12.870> we<00:10:13.020> have<00:10:13.170> something<00:10:13.440> I 00:10:13.880 --> 00:10:13.890 align:start position:0% scalable at all then we have something I 00:10:13.890 --> 00:10:16.220 align:start position:0% scalable at all then we have something I like<00:10:14.070> to<00:10:14.220> call<00:10:14.250> partial<00:10:14.670> encryption<00:10:15.330> not<00:10:16.200> a 00:10:16.220 --> 00:10:16.230 align:start position:0% like to call partial encryption not a 00:10:16.230 --> 00:10:18.410 align:start position:0% like to call partial encryption not a scientific<00:10:16.890> term<00:10:17.070> but<00:10:17.790> that's<00:10:18.150> like<00:10:18.300> an 00:10:18.410 --> 00:10:18.420 align:start position:0% scientific term but that's like an 00:10:18.420 --> 00:10:20.450 align:start position:0% scientific term but that's like an umbrella<00:10:18.690> for<00:10:19.140> like<00:10:19.320> order<00:10:20.040> preserving 00:10:20.450 --> 00:10:20.460 align:start position:0% umbrella for like order preserving 00:10:20.460 --> 00:10:23.360 align:start position:0% umbrella for like order preserving encryption<00:10:21.000> deterministic<00:10:21.990> encryption<00:10:22.370> kind 00:10:23.360 --> 00:10:23.370 align:start position:0% encryption deterministic encryption kind 00:10:23.370 --> 00:10:26.000 align:start position:0% encryption deterministic encryption kind of<00:10:23.490> like<00:10:24.020> encryption<00:10:25.020> methods<00:10:25.440> that<00:10:25.620> are<00:10:25.770> not 00:10:26.000 --> 00:10:26.010 align:start position:0% of like encryption methods that are not 00:10:26.010 --> 00:10:29.140 align:start position:0% of like encryption methods that are not perfect<00:10:26.910> but<00:10:27.720> give<00:10:28.050> you<00:10:28.200> some<00:10:28.500> confirm<00:10:28.890> the 00:10:29.140 --> 00:10:29.150 align:start position:0% perfect but give you some confirm the 00:10:29.150 --> 00:10:31.970 align:start position:0% perfect but give you some confirm the confidentiality<00:10:30.150> for<00:10:30.330> the<00:10:30.420> data<00:10:30.600> but<00:10:31.440> zero 00:10:31.970 --> 00:10:31.980 align:start position:0% confidentiality for the data but zero 00:10:31.980 --> 00:10:32.769 align:start position:0% confidentiality for the data but zero and 00:10:32.769 --> 00:10:32.779 align:start position:0% and 00:10:32.779 --> 00:10:35.470 align:start position:0% and and<00:10:33.819> then<00:10:34.819> we<00:10:34.939> really<00:10:35.149> get<00:10:35.300> to<00:10:35.329> the 00:10:35.470 --> 00:10:35.480 align:start position:0% and then we really get to the 00:10:35.480 --> 00:10:36.989 align:start position:0% and then we really get to the interesting<00:10:35.899> stuff<00:10:36.079> of<00:10:36.290> like<00:10:36.439> the<00:10:36.589> really 00:10:36.989 --> 00:10:36.999 align:start position:0% interesting stuff of like the really 00:10:36.999 --> 00:10:40.840 align:start position:0% interesting stuff of like the really heavy<00:10:38.499> heavy<00:10:39.499> machine<00:10:39.860> guns<00:10:40.129> of<00:10:40.429> cryptography 00:10:40.840 --> 00:10:40.850 align:start position:0% heavy heavy machine guns of cryptography 00:10:40.850 --> 00:10:42.809 align:start position:0% heavy heavy machine guns of cryptography we<00:10:41.240> have<00:10:41.420> fully<00:10:41.660> homomorphic<00:10:41.869> encryption 00:10:42.809 --> 00:10:42.819 align:start position:0% we have fully homomorphic encryption 00:10:42.819 --> 00:10:47.109 align:start position:0% we have fully homomorphic encryption which<00:10:43.819> is<00:10:44.499> would<00:10:45.499> be<00:10:45.529> the<00:10:45.769> best<00:10:46.009> if<00:10:46.759> we<00:10:46.970> ever 00:10:47.109 --> 00:10:47.119 align:start position:0% which is would be the best if we ever 00:10:47.119 --> 00:10:49.150 align:start position:0% which is would be the best if we ever figure<00:10:47.360> out<00:10:47.540> a<00:10:47.569> way<00:10:47.809> to<00:10:47.869> do<00:10:48.019> it<00:10:48.050> fast<00:10:48.379> enough<00:10:48.529> we 00:10:49.150 --> 00:10:49.160 align:start position:0% figure out a way to do it fast enough we 00:10:49.160 --> 00:10:51.850 align:start position:0% figure out a way to do it fast enough we right<00:10:49.579> now<00:10:49.610> we<00:10:49.790> we're<00:10:50.389> not<00:10:50.509> sure<00:10:50.660> how<00:10:50.779> to<00:10:50.809> do<00:10:51.050> it 00:10:51.850 --> 00:10:51.860 align:start position:0% right now we we're not sure how to do it 00:10:51.860 --> 00:10:54.579 align:start position:0% right now we we're not sure how to do it there's<00:10:52.429> snarks<00:10:52.970> which<00:10:53.540> are<00:10:53.720> great<00:10:54.079> if<00:10:54.379> you 00:10:54.579 --> 00:10:54.589 align:start position:0% there's snarks which are great if you 00:10:54.589 --> 00:10:56.230 align:start position:0% there's snarks which are great if you want<00:10:54.800> to<00:10:54.920> prove<00:10:55.189> a<00:10:55.339> statement<00:10:55.399> and<00:10:56.089> then 00:10:56.230 --> 00:10:56.240 align:start position:0% want to prove a statement and then 00:10:56.240 --> 00:10:59.079 align:start position:0% want to prove a statement and then verify<00:10:56.660> that<00:10:57.019> many<00:10:57.319> many<00:10:57.529> times<00:10:57.829> but<00:10:58.670> for 00:10:59.079 --> 00:10:59.089 align:start position:0% verify that many many times but for 00:10:59.089 --> 00:11:01.840 align:start position:0% verify that many many times but for other<00:10:59.389> use<00:10:59.660> cases<00:10:59.990> it<00:11:00.439> is<00:11:00.850> unfortunately 00:11:01.840 --> 00:11:01.850 align:start position:0% other use cases it is unfortunately 00:11:01.850 --> 00:11:04.449 align:start position:0% other use cases it is unfortunately limited<00:11:02.300> and<00:11:02.569> you<00:11:02.649> have<00:11:03.649> multi-party 00:11:04.449 --> 00:11:04.459 align:start position:0% limited and you have multi-party 00:11:04.459 --> 00:11:06.460 align:start position:0% limited and you have multi-party computation<00:11:04.730> which<00:11:05.660> we<00:11:05.929> feel<00:11:06.110> is<00:11:06.230> a<00:11:06.259> good 00:11:06.460 --> 00:11:06.470 align:start position:0% computation which we feel is a good 00:11:06.470 --> 00:11:08.650 align:start position:0% computation which we feel is a good trade-off<00:11:06.740> multi-party<00:11:07.339> computation<00:11:07.660> gives 00:11:08.650 --> 00:11:08.660 align:start position:0% trade-off multi-party computation gives 00:11:08.660 --> 00:11:10.720 align:start position:0% trade-off multi-party computation gives you<00:11:08.929> you<00:11:09.139> can<00:11:09.350> basically<00:11:09.529> compute<00:11:10.129> anything 00:11:10.720 --> 00:11:10.730 align:start position:0% you you can basically compute anything 00:11:10.730 --> 00:11:13.389 align:start position:0% you you can basically compute anything with<00:11:11.029> privacy<00:11:11.600> with<00:11:11.899> correctness<00:11:12.410> under<00:11:13.189> some 00:11:13.389 --> 00:11:13.399 align:start position:0% with privacy with correctness under some 00:11:13.399 --> 00:11:15.850 align:start position:0% with privacy with correctness under some assumptions<00:11:13.730> it<00:11:14.209> is<00:11:14.720> more<00:11:14.929> scalable<00:11:15.230> than<00:11:15.559> the 00:11:15.850 --> 00:11:15.860 align:start position:0% assumptions it is more scalable than the 00:11:15.860 --> 00:11:18.009 align:start position:0% assumptions it is more scalable than the other<00:11:15.980> cryptographic<00:11:16.339> solutions<00:11:17.119> because<00:11:17.899> it 00:11:18.009 --> 00:11:18.019 align:start position:0% other cryptographic solutions because it 00:11:18.019 --> 00:11:21.269 align:start position:0% other cryptographic solutions because it really<00:11:18.649> only<00:11:18.740> uses<00:11:19.129> symmetric<00:11:19.850> cryptography 00:11:21.269 --> 00:11:21.279 align:start position:0% really only uses symmetric cryptography 00:11:21.279 --> 00:11:24.160 align:start position:0% really only uses symmetric cryptography but<00:11:22.279> I<00:11:22.490> do<00:11:22.639> want<00:11:22.970> to<00:11:23.059> emphasize<00:11:23.540> that<00:11:23.569> it<00:11:24.019> is 00:11:24.160 --> 00:11:24.170 align:start position:0% but I do want to emphasize that it is 00:11:24.170 --> 00:11:27.280 align:start position:0% but I do want to emphasize that it is still<00:11:24.439> much<00:11:25.069> slower<00:11:25.730> they<00:11:26.600> like<00:11:26.809> hardware 00:11:27.280 --> 00:11:27.290 align:start position:0% still much slower they like hardware 00:11:27.290 --> 00:11:30.730 align:start position:0% still much slower they like hardware based<00:11:27.439> solutions<00:11:28.069> and<00:11:28.689> of<00:11:29.689> course<00:11:30.079> computing 00:11:30.730 --> 00:11:30.740 align:start position:0% based solutions and of course computing 00:11:30.740 --> 00:11:33.549 align:start position:0% based solutions and of course computing over<00:11:30.860> unencrypted<00:11:31.699> data<00:11:31.850> and<00:11:32.259> this<00:11:33.259> is<00:11:33.410> why 00:11:33.549 --> 00:11:33.559 align:start position:0% over unencrypted data and this is why 00:11:33.559 --> 00:11:35.619 align:start position:0% over unencrypted data and this is why actually<00:11:34.069> we're<00:11:34.399> to<00:11:34.579> make<00:11:34.730> mobile<00:11:34.970> focusing 00:11:35.619 --> 00:11:35.629 align:start position:0% actually we're to make mobile focusing 00:11:35.629 --> 00:11:38.590 align:start position:0% actually we're to make mobile focusing it's<00:11:36.379> a<00:11:36.470> bit<00:11:36.619> of<00:11:36.799> a<00:11:36.980> refocusing<00:11:37.579> on<00:11:37.730> both<00:11:38.389> of 00:11:38.590 --> 00:11:38.600 align:start position:0% it's a bit of a refocusing on both of 00:11:38.600 --> 00:11:41.470 align:start position:0% it's a bit of a refocusing on both of these<00:11:38.720> technologies<00:11:39.350> MPC<00:11:40.339> and<00:11:40.610> secure 00:11:41.470 --> 00:11:41.480 align:start position:0% these technologies MPC and secure 00:11:41.480 --> 00:11:43.389 align:start position:0% these technologies MPC and secure hardware<00:11:41.720> so<00:11:42.470> secure<00:11:42.769> hardware<00:11:43.069> is<00:11:43.189> stuff 00:11:43.389 --> 00:11:43.399 align:start position:0% hardware so secure hardware is stuff 00:11:43.399 --> 00:11:45.879 align:start position:0% hardware so secure hardware is stuff like<00:11:43.490> Intel<00:11:43.970> SGX<00:11:44.119> and<00:11:44.660> trusted<00:11:45.290> execution 00:11:45.879 --> 00:11:45.889 align:start position:0% like Intel SGX and trusted execution 00:11:45.889 --> 00:11:48.579 align:start position:0% like Intel SGX and trusted execution environments<00:11:46.549> we<00:11:47.119> feel<00:11:47.360> that<00:11:47.540> MPC<00:11:48.170> is<00:11:48.230> is 00:11:48.579 --> 00:11:48.589 align:start position:0% environments we feel that MPC is is 00:11:48.589 --> 00:11:50.919 align:start position:0% environments we feel that MPC is is great<00:11:49.100> for<00:11:49.910> like<00:11:50.029> applications<00:11:50.809> like 00:11:50.919 --> 00:11:50.929 align:start position:0% great for like applications like 00:11:50.929 --> 00:11:52.539 align:start position:0% great for like applications like identity<00:11:51.619> where<00:11:51.829> you<00:11:51.889> want<00:11:52.069> to<00:11:52.160> have<00:11:52.249> zero 00:11:52.539 --> 00:11:52.549 align:start position:0% identity where you want to have zero 00:11:52.549 --> 00:11:54.910 align:start position:0% identity where you want to have zero trust<00:11:52.850> but<00:11:53.449> if<00:11:53.569> you<00:11:53.689> okay<00:11:54.049> with<00:11:54.199> having<00:11:54.499> some 00:11:54.910 --> 00:11:54.920 align:start position:0% trust but if you okay with having some 00:11:54.920 --> 00:11:56.919 align:start position:0% trust but if you okay with having some minimal<00:11:55.279> trust<00:11:55.579> in<00:11:55.730> the<00:11:55.850> vendor<00:11:56.240> which<00:11:56.779> is 00:11:56.919 --> 00:11:56.929 align:start position:0% minimal trust in the vendor which is 00:11:56.929 --> 00:11:58.929 align:start position:0% minimal trust in the vendor which is what<00:11:57.079> secure<00:11:57.410> Hardware<00:11:57.769> requires<00:11:58.100> you<00:11:58.399> then 00:11:58.929 --> 00:11:58.939 align:start position:0% what secure Hardware requires you then 00:11:58.939 --> 00:12:00.730 align:start position:0% what secure Hardware requires you then you<00:11:59.029> can<00:11:59.179> really<00:11:59.420> get<00:11:59.600> full<00:12:00.290> functionality 00:12:00.730 --> 00:12:00.740 align:start position:0% you can really get full functionality 00:12:00.740 --> 00:12:06.069 align:start position:0% you can really get full functionality great<00:12:01.429> scalability<00:12:02.149> and<00:12:02.509> privacy<00:12:03.850> and<00:12:05.079> with 00:12:06.069 --> 00:12:06.079 align:start position:0% great scalability and privacy and with 00:12:06.079 --> 00:12:08.019 align:start position:0% great scalability and privacy and with that<00:12:06.199> I'm<00:12:06.410> gonna<00:12:06.649> yeah<00:12:07.579> I<00:12:07.610> think<00:12:07.850> I<00:12:07.910> have 00:12:08.019 --> 00:12:08.029 align:start position:0% that I'm gonna yeah I think I have 00:12:08.029 --> 00:12:09.879 align:start position:0% that I'm gonna yeah I think I have enough<00:12:08.240> time<00:12:08.449> I<00:12:08.689> want<00:12:09.170> to<00:12:09.230> walk<00:12:09.350> if<00:12:09.499> you<00:12:09.529> kind 00:12:09.879 --> 00:12:09.889 align:start position:0% enough time I want to walk if you kind 00:12:09.889 --> 00:12:11.859 align:start position:0% enough time I want to walk if you kind of<00:12:09.920> like<00:12:10.040> the<00:12:10.160> basics<00:12:10.549> of<00:12:10.670> MPC<00:12:11.179> right<00:12:11.389> MPC<00:12:11.839> is 00:12:11.859 --> 00:12:11.869 align:start position:0% of like the basics of MPC right MPC is 00:12:11.869 --> 00:12:13.689 align:start position:0% of like the basics of MPC right MPC is an<00:12:12.019> amazing<00:12:12.350> technology<00:12:12.619> it's<00:12:13.369> something 00:12:13.689 --> 00:12:13.699 align:start position:0% an amazing technology it's something 00:12:13.699 --> 00:12:15.039 align:start position:0% an amazing technology it's something we've<00:12:13.819> been<00:12:13.939> working<00:12:14.360> on<00:12:14.449> for<00:12:14.629> a<00:12:14.689> while<00:12:14.809> and 00:12:15.039 --> 00:12:15.049 align:start position:0% we've been working on for a while and 00:12:15.049 --> 00:12:17.350 align:start position:0% we've been working on for a while and that<00:12:15.589> also<00:12:15.799> would<00:12:16.009> help<00:12:16.279> to<00:12:16.579> illustrate<00:12:16.790> kind 00:12:17.350 --> 00:12:17.360 align:start position:0% that also would help to illustrate kind 00:12:17.360 --> 00:12:18.910 align:start position:0% that also would help to illustrate kind of<00:12:17.449> like<00:12:17.600> the<00:12:17.720> strengths<00:12:18.139> and<00:12:18.230> weaknesses<00:12:18.319> of 00:12:18.910 --> 00:12:18.920 align:start position:0% of like the strengths and weaknesses of 00:12:18.920 --> 00:12:19.389 align:start position:0% of like the strengths and weaknesses of it 00:12:19.389 --> 00:12:19.399 align:start position:0% it 00:12:19.399 --> 00:12:23.949 align:start position:0% it so<00:12:20.029> MPC<00:12:20.720> says<00:12:21.649> something<00:12:22.160> like<00:12:22.189> this<00:12:22.959> imagine 00:12:23.949 --> 00:12:23.959 align:start position:0% so MPC says something like this imagine 00:12:23.959 --> 00:12:25.869 align:start position:0% so MPC says something like this imagine there's<00:12:24.379> an<00:12:24.559> ideal<00:12:24.889> world<00:12:25.129> where<00:12:25.579> we<00:12:25.730> have 00:12:25.869 --> 00:12:25.879 align:start position:0% there's an ideal world where we have 00:12:25.879 --> 00:12:27.850 align:start position:0% there's an ideal world where we have like<00:12:26.059> this<00:12:26.269> godlike<00:12:26.809> computer<00:12:27.350> that<00:12:27.559> we<00:12:27.679> can 00:12:27.850 --> 00:12:27.860 align:start position:0% like this godlike computer that we can 00:12:27.860 --> 00:12:30.579 align:start position:0% like this godlike computer that we can trust<00:12:28.329> and<00:12:29.329> we<00:12:29.569> can<00:12:29.720> outsource<00:12:30.170> every 00:12:30.579 --> 00:12:30.589 align:start position:0% trust and we can outsource every 00:12:30.589 --> 00:12:32.980 align:start position:0% trust and we can outsource every computation<00:12:31.309> to<00:12:31.519> it<00:12:31.699> now<00:12:32.299> that<00:12:32.540> trusted 00:12:32.980 --> 00:12:32.990 align:start position:0% computation to it now that trusted 00:12:32.990 --> 00:12:35.799 align:start position:0% computation to it now that trusted machine<00:12:33.350> would<00:12:34.249> never<00:12:34.490> leave<00:12:34.730> the<00:12:34.759> data<00:12:35.059> it 00:12:35.799 --> 00:12:35.809 align:start position:0% machine would never leave the data it 00:12:35.809 --> 00:12:39.489 align:start position:0% machine would never leave the data it no-one<00:12:36.470> can<00:12:36.740> breach<00:12:37.009> it<00:12:37.600> and<00:12:38.600> we<00:12:39.199> can<00:12:39.350> always 00:12:39.489 --> 00:12:39.499 align:start position:0% no-one can breach it and we can always 00:12:39.499 --> 00:12:40.629 align:start position:0% no-one can breach it and we can always trust<00:12:39.829> it<00:12:40.040> to<00:12:40.129> run<00:12:40.249> the<00:12:40.370> computation 00:12:40.629 --> 00:12:40.639 align:start position:0% trust it to run the computation 00:12:40.639 --> 00:12:42.939 align:start position:0% trust it to run the computation correctly<00:12:41.389> but<00:12:42.049> in<00:12:42.139> the<00:12:42.259> real<00:12:42.410> world<00:12:42.679> that's 00:12:42.939 --> 00:12:42.949 align:start position:0% correctly but in the real world that's 00:12:42.949 --> 00:12:43.929 align:start position:0% correctly but in the real world that's not<00:12:43.160> possible 00:12:43.929 --> 00:12:43.939 align:start position:0% not possible 00:12:43.939 --> 00:12:46.040 align:start position:0% not possible so<00:12:44.389> what<00:12:44.540> MPC<00:12:45.049> comes<00:12:45.290> in 00:12:46.040 --> 00:12:46.050 align:start position:0% so what MPC comes in 00:12:46.050 --> 00:12:48.530 align:start position:0% so what MPC comes in let's<00:12:46.500> simulate<00:12:46.980> that<00:12:47.670> trusted<00:12:48.180> machine 00:12:48.530 --> 00:12:48.540 align:start position:0% let's simulate that trusted machine 00:12:48.540 --> 00:12:50.780 align:start position:0% let's simulate that trusted machine let's<00:12:49.290> simulate<00:12:49.530> that<00:12:49.980> with<00:12:50.280> the<00:12:50.400> network 00:12:50.780 --> 00:12:50.790 align:start position:0% let's simulate that with the network 00:12:50.790 --> 00:12:52.130 align:start position:0% let's simulate that with the network kind<00:12:51.300> of<00:12:51.390> like<00:12:51.540> the<00:12:51.720> argument<00:12:52.110> that 00:12:52.130 --> 00:12:52.140 align:start position:0% kind of like the argument that 00:12:52.140 --> 00:12:54.230 align:start position:0% kind of like the argument that blockchain<00:12:52.560> is<00:12:52.680> making<00:12:53.010> by<00:12:53.130> the<00:12:53.160> way<00:12:53.370> let's 00:12:54.230 --> 00:12:54.240 align:start position:0% blockchain is making by the way let's 00:12:54.240 --> 00:12:57.080 align:start position:0% blockchain is making by the way let's simulate<00:12:54.450> that<00:12:54.720> with<00:12:54.900> the<00:12:54.960> network<00:12:55.380> and<00:12:56.090> the 00:12:57.080 --> 00:12:57.090 align:start position:0% simulate that with the network and the 00:12:57.090 --> 00:12:58.850 align:start position:0% simulate that with the network and the statement<00:12:57.510> says<00:12:57.780> and<00:12:58.140> this<00:12:58.200> is<00:12:58.260> a<00:12:58.380> simplified 00:12:58.850 --> 00:12:58.860 align:start position:0% statement says and this is a simplified 00:12:58.860 --> 00:13:01.220 align:start position:0% statement says and this is a simplified statement<00:12:59.370> that<00:13:00.090> you<00:13:00.390> know<00:13:00.480> as<00:13:00.690> long<00:13:00.930> as 00:13:01.220 --> 00:13:01.230 align:start position:0% statement that you know as long as 00:13:01.230 --> 00:13:04.070 align:start position:0% statement that you know as long as there's<00:13:01.470> at<00:13:01.620> this<00:13:01.800> one<00:13:02.310> honest<00:13:03.240> node<00:13:03.480> this<00:13:03.750> one 00:13:04.070 --> 00:13:04.080 align:start position:0% there's at this one honest node this one 00:13:04.080 --> 00:13:06.260 align:start position:0% there's at this one honest node this one no<00:13:04.290> that<00:13:04.500> is<00:13:04.650> not<00:13:04.770> a<00:13:04.830> bad<00:13:05.070> actor<00:13:05.520> you<00:13:06.090> can 00:13:06.260 --> 00:13:06.270 align:start position:0% no that is not a bad actor you can 00:13:06.270 --> 00:13:08.110 align:start position:0% no that is not a bad actor you can actually<00:13:06.480> make<00:13:06.900> sure<00:13:06.930> that<00:13:07.260> the<00:13:07.380> computation 00:13:08.110 --> 00:13:08.120 align:start position:0% actually make sure that the computation 00:13:08.120 --> 00:13:09.950 align:start position:0% actually make sure that the computation is<00:13:09.120> correct 00:13:09.950 --> 00:13:09.960 align:start position:0% is correct 00:13:09.960 --> 00:13:12.920 align:start position:0% is correct every<00:13:10.470> computation<00:13:11.100> and<00:13:11.250> that<00:13:11.820> no<00:13:12.450> node<00:13:12.750> in 00:13:12.920 --> 00:13:12.930 align:start position:0% every computation and that no node in 00:13:12.930 --> 00:13:14.360 align:start position:0% every computation and that no node in the<00:13:13.050> network<00:13:13.080> no<00:13:13.710> one<00:13:13.860> in<00:13:13.950> the<00:13:14.040> network<00:13:14.340> can 00:13:14.360 --> 00:13:14.370 align:start position:0% the network no one in the network can 00:13:14.370 --> 00:13:16.760 align:start position:0% the network no one in the network can actually<00:13:14.940> see<00:13:15.150> the<00:13:15.270> data<00:13:15.480> the<00:13:16.110> raw<00:13:16.260> data<00:13:16.470> and 00:13:16.760 --> 00:13:16.770 align:start position:0% actually see the data the raw data and 00:13:16.770 --> 00:13:18.620 align:start position:0% actually see the data the raw data and that<00:13:17.130> basically<00:13:17.580> means<00:13:17.850> that<00:13:17.940> data<00:13:18.210> remains 00:13:18.620 --> 00:13:18.630 align:start position:0% that basically means that data remains 00:13:18.630 --> 00:13:22.880 align:start position:0% that basically means that data remains encrypted<00:13:19.320> and<00:13:19.500> to<00:13:20.160> end<00:13:21.620> let<00:13:22.620> me<00:13:22.710> walk<00:13:22.860> you 00:13:22.880 --> 00:13:22.890 align:start position:0% encrypted and to end let me walk you 00:13:22.890 --> 00:13:24.620 align:start position:0% encrypted and to end let me walk you through<00:13:23.010> a<00:13:23.190> simple<00:13:23.400> example<00:13:23.550> let's<00:13:24.480> imagine 00:13:24.620 --> 00:13:24.630 align:start position:0% through a simple example let's imagine 00:13:24.630 --> 00:13:27.470 align:start position:0% through a simple example let's imagine we<00:13:25.020> have<00:13:25.200> a<00:13:25.410> network<00:13:25.800> of<00:13:25.890> three<00:13:26.070> nodes<00:13:26.400> a<00:13:26.760> very 00:13:27.470 --> 00:13:27.480 align:start position:0% we have a network of three nodes a very 00:13:27.480 --> 00:13:29.870 align:start position:0% we have a network of three nodes a very small<00:13:27.750> network<00:13:28.170> and<00:13:28.470> let's<00:13:29.250> say<00:13:29.400> we<00:13:29.550> have<00:13:29.730> you 00:13:29.870 --> 00:13:29.880 align:start position:0% small network and let's say we have you 00:13:29.880 --> 00:13:31.550 align:start position:0% small network and let's say we have you know<00:13:29.970> the<00:13:30.120> data<00:13:30.300> provider<00:13:30.720> on<00:13:30.930> one<00:13:31.110> on<00:13:31.320> one 00:13:31.550 --> 00:13:31.560 align:start position:0% know the data provider on one on one 00:13:31.560 --> 00:13:34.040 align:start position:0% know the data provider on one on one hand<00:13:31.830> and<00:13:32.070> then<00:13:32.220> a<00:13:32.250> data<00:13:32.520> consumer<00:13:33.060> I'm 00:13:34.040 --> 00:13:34.050 align:start position:0% hand and then a data consumer I'm 00:13:34.050 --> 00:13:35.690 align:start position:0% hand and then a data consumer I'm ignoring<00:13:34.650> the<00:13:34.830> blocking<00:13:35.280> here<00:13:35.460> I'm<00:13:35.550> just 00:13:35.690 --> 00:13:35.700 align:start position:0% ignoring the blocking here I'm just 00:13:35.700 --> 00:13:37.490 align:start position:0% ignoring the blocking here I'm just talking<00:13:35.970> about<00:13:36.210> the<00:13:36.420> process<00:13:36.840> of<00:13:36.990> the<00:13:37.230> off 00:13:37.490 --> 00:13:37.500 align:start position:0% talking about the process of the off 00:13:37.500 --> 00:13:41.390 align:start position:0% talking about the process of the off chain<00:13:37.800> storage<00:13:38.310> in<00:13:38.430> computation<00:13:39.150> so<00:13:40.400> let's 00:13:41.390 --> 00:13:41.400 align:start position:0% chain storage in computation so let's 00:13:41.400 --> 00:13:44.960 align:start position:0% chain storage in computation so let's say<00:13:41.520> a<00:13:41.550> data<00:13:41.790> provider<00:13:43.340> wants<00:13:44.340> to<00:13:44.460> store<00:13:44.700> some 00:13:44.960 --> 00:13:44.970 align:start position:0% say a data provider wants to store some 00:13:44.970 --> 00:13:48.680 align:start position:0% say a data provider wants to store some number<00:13:45.270> X<00:13:46.130> what<00:13:47.130> it<00:13:47.310> does<00:13:47.610> locally<00:13:48.390> it 00:13:48.680 --> 00:13:48.690 align:start position:0% number X what it does locally it 00:13:48.690 --> 00:13:50.900 align:start position:0% number X what it does locally it basically<00:13:49.590> goes<00:13:49.890> through<00:13:49.920> a<00:13:50.160> protocol<00:13:50.610> called 00:13:50.900 --> 00:13:50.910 align:start position:0% basically goes through a protocol called 00:13:50.910 --> 00:13:53.870 align:start position:0% basically goes through a protocol called secret<00:13:51.330> sharing<00:13:51.570> that<00:13:52.560> protocol<00:13:53.100> essentially 00:13:53.870 --> 00:13:53.880 align:start position:0% secret sharing that protocol essentially 00:13:53.880 --> 00:13:57.710 align:start position:0% secret sharing that protocol essentially splits<00:13:54.330> that<00:13:55.020> data<00:13:55.350> into<00:13:56.340> shares<00:13:56.910> encrypted 00:13:57.710 --> 00:13:57.720 align:start position:0% splits that data into shares encrypted 00:13:57.720 --> 00:14:00.590 align:start position:0% splits that data into shares encrypted shares<00:13:57.990> and<00:13:58.230> sends<00:13:58.920> one<00:13:59.250> share<00:13:59.610> to<00:13:59.880> each<00:14:00.030> node 00:14:00.590 --> 00:14:00.600 align:start position:0% shares and sends one share to each node 00:14:00.600 --> 00:14:04.820 align:start position:0% shares and sends one share to each node okay<00:14:00.960> so<00:14:01.020> node<00:14:01.800> 1<00:14:02.010> has<00:14:02.160> x<00:14:02.370> 1<00:14:02.610> no<00:14:03.150> 2<00:14:03.180> X<00:14:03.510> 2<00:14:03.720> and<00:14:03.930> no<00:14:04.800> 3 00:14:04.820 --> 00:14:04.830 align:start position:0% okay so node 1 has x 1 no 2 X 2 and no 3 00:14:04.830 --> 00:14:07.610 align:start position:0% okay so node 1 has x 1 no 2 X 2 and no 3 X<00:14:05.190> 3<00:14:05.370> these<00:14:06.360> shares<00:14:06.990> are<00:14:07.140> completely 00:14:07.610 --> 00:14:07.620 align:start position:0% X 3 these shares are completely 00:14:07.620 --> 00:14:09.650 align:start position:0% X 3 these shares are completely encrypted<00:14:08.070> no<00:14:08.280> one<00:14:08.490> and<00:14:08.850> the<00:14:09.030> others<00:14:09.300> cannot 00:14:09.650 --> 00:14:09.660 align:start position:0% encrypted no one and the others cannot 00:14:09.660 --> 00:14:12.200 align:start position:0% encrypted no one and the others cannot see<00:14:09.720> anything<00:14:10.320> about<00:14:10.440> the<00:14:10.710> row<00:14:10.830> X<00:14:11.070> then<00:14:11.970> we<00:14:12.120> do 00:14:12.200 --> 00:14:12.210 align:start position:0% see anything about the row X then we do 00:14:12.210 --> 00:14:17.600 align:start position:0% see anything about the row X then we do the<00:14:12.330> same<00:14:12.540> thing<00:14:12.840> with<00:14:13.260> Y<00:14:14.840> and<00:14:16.220> then<00:14:17.220> actually 00:14:17.600 --> 00:14:17.610 align:start position:0% the same thing with Y and then actually 00:14:17.610 --> 00:14:20.060 align:start position:0% the same thing with Y and then actually the<00:14:17.850> data<00:14:18.540> provider<00:14:18.960> can<00:14:19.170> go<00:14:19.320> offline<00:14:19.650> data 00:14:20.060 --> 00:14:20.070 align:start position:0% the data provider can go offline data 00:14:20.070 --> 00:14:22.670 align:start position:0% the data provider can go offline data lives<00:14:20.340> in<00:14:20.490> the<00:14:20.580> network<00:14:21.230> now<00:14:22.230> the<00:14:22.290> consumer 00:14:22.670 --> 00:14:22.680 align:start position:0% lives in the network now the consumer 00:14:22.680 --> 00:14:24.790 align:start position:0% lives in the network now the consumer comes<00:14:23.010> in<00:14:23.220> wants<00:14:23.460> to<00:14:23.520> run<00:14:23.670> some<00:14:23.850> computation 00:14:24.790 --> 00:14:24.800 align:start position:0% comes in wants to run some computation 00:14:24.800 --> 00:14:27.260 align:start position:0% comes in wants to run some computation the<00:14:25.800> state<00:14:26.070> of<00:14:26.250> the<00:14:26.370> network<00:14:26.730> is<00:14:26.910> that<00:14:27.120> they 00:14:27.260 --> 00:14:27.270 align:start position:0% the state of the network is that they 00:14:27.270 --> 00:14:29.180 align:start position:0% the state of the network is that they collectively<00:14:27.900> hold<00:14:28.170> X<00:14:28.470> and<00:14:28.680> y<00:14:28.800> but<00:14:29.040> it's 00:14:29.180 --> 00:14:29.190 align:start position:0% collectively hold X and y but it's 00:14:29.190 --> 00:14:32.870 align:start position:0% collectively hold X and y but it's encrypted<00:14:29.990> as<00:14:30.990> shares<00:14:31.470> in<00:14:31.680> each<00:14:31.770> node<00:14:32.010> now<00:14:32.820> the 00:14:32.870 --> 00:14:32.880 align:start position:0% encrypted as shares in each node now the 00:14:32.880 --> 00:14:34.940 align:start position:0% encrypted as shares in each node now the consumer<00:14:33.480> comes<00:14:33.720> in<00:14:33.990> and<00:14:34.230> wants<00:14:34.410> to<00:14:34.560> compute 00:14:34.940 --> 00:14:34.950 align:start position:0% consumer comes in and wants to compute 00:14:34.950 --> 00:14:39.530 align:start position:0% consumer comes in and wants to compute just<00:14:35.400> X<00:14:35.670> plus<00:14:35.790> y<00:14:37.339> so<00:14:38.339> because<00:14:39.300> of<00:14:39.450> the 00:14:39.530 --> 00:14:39.540 align:start position:0% just X plus y so because of the 00:14:39.540 --> 00:14:41.329 align:start position:0% just X plus y so because of the properties<00:14:39.930> of<00:14:40.020> secret<00:14:40.380> sharing<00:14:40.620> actually 00:14:41.329 --> 00:14:41.339 align:start position:0% properties of secret sharing actually 00:14:41.339 --> 00:14:43.700 align:start position:0% properties of secret sharing actually that's<00:14:41.730> that<00:14:42.060> comes<00:14:42.300> for<00:14:42.510> free<00:14:42.660> we<00:14:43.290> can<00:14:43.440> just 00:14:43.700 --> 00:14:43.710 align:start position:0% that's that comes for free we can just 00:14:43.710 --> 00:14:45.890 align:start position:0% that's that comes for free we can just each<00:14:44.130> node<00:14:44.460> can<00:14:44.640> locally<00:14:45.150> compute<00:14:45.570> their 00:14:45.890 --> 00:14:45.900 align:start position:0% each node can locally compute their 00:14:45.900 --> 00:14:48.290 align:start position:0% each node can locally compute their local<00:14:46.230> shares<00:14:46.500> which<00:14:47.339> give<00:14:47.820> them<00:14:48.089> the 00:14:48.290 --> 00:14:48.300 align:start position:0% local shares which give them the 00:14:48.300 --> 00:14:51.740 align:start position:0% local shares which give them the encrypted<00:14:49.490> summation<00:14:50.490> and<00:14:50.670> then<00:14:51.420> they<00:14:51.570> can 00:14:51.740 --> 00:14:51.750 align:start position:0% encrypted summation and then they can 00:14:51.750 --> 00:14:54.680 align:start position:0% encrypted summation and then they can just<00:14:51.780> send<00:14:52.290> all<00:14:52.640> all<00:14:53.640> of<00:14:53.850> the<00:14:53.970> shares<00:14:54.210> back<00:14:54.330> to 00:14:54.680 --> 00:14:54.690 align:start position:0% just send all all of the shares back to 00:14:54.690 --> 00:14:56.540 align:start position:0% just send all all of the shares back to the<00:14:54.780> consumer<00:14:55.320> and<00:14:55.500> the<00:14:56.100> one<00:14:56.250> thing<00:14:56.460> about 00:14:56.540 --> 00:14:56.550 align:start position:0% the consumer and the one thing about 00:14:56.550 --> 00:14:58.640 align:start position:0% the consumer and the one thing about secret<00:14:57.030> charity<00:14:57.420> is<00:14:57.480> that<00:14:57.720> if<00:14:57.870> you<00:14:58.110> have<00:14:58.380> all 00:14:58.640 --> 00:14:58.650 align:start position:0% secret charity is that if you have all 00:14:58.650 --> 00:14:59.129 align:start position:0% secret charity is that if you have all the<00:14:58.830> share 00:14:59.129 --> 00:14:59.139 align:start position:0% the share 00:14:59.139 --> 00:15:01.410 align:start position:0% the share in<00:14:59.199> one<00:14:59.379> place<00:14:59.649> you<00:15:00.189> can<00:15:00.429> reconstruct<00:15:00.939> you<00:15:01.239> can 00:15:01.410 --> 00:15:01.420 align:start position:0% in one place you can reconstruct you can 00:15:01.420 --> 00:15:03.689 align:start position:0% in one place you can reconstruct you can decrypt<00:15:01.779> the<00:15:01.959> data<00:15:02.170> but<00:15:02.920> the<00:15:03.009> important<00:15:03.459> part 00:15:03.689 --> 00:15:03.699 align:start position:0% decrypt the data but the important part 00:15:03.699 --> 00:15:06.119 align:start position:0% decrypt the data but the important part to<00:15:03.850> realize<00:15:04.239> is<00:15:04.480> that<00:15:05.290> there<00:15:05.949> was<00:15:06.069> a 00:15:06.119 --> 00:15:06.129 align:start position:0% to realize is that there was a 00:15:06.129 --> 00:15:08.220 align:start position:0% to realize is that there was a computation<00:15:06.879> going<00:15:07.089> on<00:15:07.329> in<00:15:07.480> this<00:15:07.569> network<00:15:07.839> and 00:15:08.220 --> 00:15:08.230 align:start position:0% computation going on in this network and 00:15:08.230 --> 00:15:10.049 align:start position:0% computation going on in this network and we<00:15:08.529> can<00:15:08.679> extend<00:15:08.889> that<00:15:09.160> network<00:15:09.519> as<00:15:09.579> much<00:15:09.670> as<00:15:09.910> we 00:15:10.049 --> 00:15:10.059 align:start position:0% we can extend that network as much as we 00:15:10.059 --> 00:15:12.389 align:start position:0% we can extend that network as much as we want<00:15:10.269> but<00:15:11.019> none<00:15:11.799> of<00:15:11.920> the<00:15:12.040> nodes<00:15:12.220> in<00:15:12.369> the 00:15:12.389 --> 00:15:12.399 align:start position:0% want but none of the nodes in the 00:15:12.399 --> 00:15:14.160 align:start position:0% want but none of the nodes in the network<00:15:12.519> has<00:15:13.059> have<00:15:13.329> actually<00:15:13.720> seen<00:15:13.899> the<00:15:14.049> raw 00:15:14.160 --> 00:15:14.170 align:start position:0% network has have actually seen the raw 00:15:14.170 --> 00:15:16.650 align:start position:0% network has have actually seen the raw data<00:15:14.350> they<00:15:14.829> have<00:15:14.980> just<00:15:15.220> operated<00:15:15.879> on<00:15:16.029> fully 00:15:16.650 --> 00:15:16.660 align:start position:0% data they have just operated on fully 00:15:16.660 --> 00:15:19.280 align:start position:0% data they have just operated on fully encrypted<00:15:16.959> data<00:15:17.319> which<00:15:17.559> is<00:15:17.799> pretty<00:15:18.519> amazing 00:15:19.280 --> 00:15:19.290 align:start position:0% encrypted data which is pretty amazing 00:15:19.290 --> 00:15:21.749 align:start position:0% encrypted data which is pretty amazing so<00:15:20.290> let's<00:15:20.499> run<00:15:20.709> another<00:15:20.949> example<00:15:21.579> with 00:15:21.749 --> 00:15:21.759 align:start position:0% so let's run another example with 00:15:21.759 --> 00:15:25.229 align:start position:0% so let's run another example with multiplication<00:15:22.689> I'm<00:15:23.679> gonna<00:15:23.980> go<00:15:24.160> first<00:15:24.669> over 00:15:25.229 --> 00:15:25.239 align:start position:0% multiplication I'm gonna go first over 00:15:25.239 --> 00:15:27.809 align:start position:0% multiplication I'm gonna go first over that<00:15:25.419> it's<00:15:25.779> like<00:15:26.049> more<00:15:26.350> complicated<00:15:27.069> I<00:15:27.279> just 00:15:27.809 --> 00:15:27.819 align:start position:0% that it's like more complicated I just 00:15:27.819 --> 00:15:29.759 align:start position:0% that it's like more complicated I just want<00:15:27.939> to<00:15:27.999> give<00:15:28.149> you<00:15:28.239> the<00:15:28.359> main<00:15:28.540> ideas<00:15:28.929> so 00:15:29.759 --> 00:15:29.769 align:start position:0% want to give you the main ideas so 00:15:29.769 --> 00:15:32.309 align:start position:0% want to give you the main ideas so company<00:15:30.429> I'm<00:15:31.089> sorry<00:15:31.389> multiplication 00:15:32.309 --> 00:15:32.319 align:start position:0% company I'm sorry multiplication 00:15:32.319 --> 00:15:34.739 align:start position:0% company I'm sorry multiplication requires<00:15:33.189> communication<00:15:34.089> between<00:15:34.239> the<00:15:34.509> nodes 00:15:34.739 --> 00:15:34.749 align:start position:0% requires communication between the nodes 00:15:34.749 --> 00:15:39.030 align:start position:0% requires communication between the nodes they<00:15:35.350> can<00:15:35.589> just<00:15:35.829> compute<00:15:36.100> it<00:15:36.279> locally<00:15:37.319> but<00:15:38.319> we 00:15:39.030 --> 00:15:39.040 align:start position:0% they can just compute it locally but we 00:15:39.040 --> 00:15:41.159 align:start position:0% they can just compute it locally but we know<00:15:39.189> that<00:15:39.220> if<00:15:39.910> you<00:15:40.119> get<00:15:40.299> all<00:15:40.540> the<00:15:40.569> shares<00:15:40.959> in 00:15:41.159 --> 00:15:41.169 align:start position:0% know that if you get all the shares in 00:15:41.169 --> 00:15:43.679 align:start position:0% know that if you get all the shares in one<00:15:41.350> place<00:15:41.999> then<00:15:42.999> you<00:15:43.089> can<00:15:43.119> decrypt<00:15:43.509> the<00:15:43.660> data 00:15:43.679 --> 00:15:43.689 align:start position:0% one place then you can decrypt the data 00:15:43.689 --> 00:15:45.449 align:start position:0% one place then you can decrypt the data so<00:15:44.139> we<00:15:44.259> need<00:15:44.379> we<00:15:44.559> need<00:15:44.589> some<00:15:44.859> trick<00:15:45.100> we<00:15:45.220> need<00:15:45.339> to 00:15:45.449 --> 00:15:45.459 align:start position:0% so we need we need some trick we need to 00:15:45.459 --> 00:15:47.789 align:start position:0% so we need we need some trick we need to avoid<00:15:45.699> that<00:15:45.939> so<00:15:46.509> what<00:15:46.629> happens<00:15:46.989> in<00:15:47.079> MPC<00:15:47.379> and 00:15:47.789 --> 00:15:47.799 align:start position:0% avoid that so what happens in MPC and 00:15:47.799 --> 00:15:49.439 align:start position:0% avoid that so what happens in MPC and that<00:15:48.339> happens<00:15:48.699> here<00:15:48.970> but<00:15:49.089> that<00:15:49.209> really 00:15:49.439 --> 00:15:49.449 align:start position:0% that happens here but that really 00:15:49.449 --> 00:15:51.659 align:start position:0% that happens here but that really happens<00:15:49.809> in<00:15:49.989> every<00:15:50.619> like<00:15:51.189> if<00:15:51.339> you're<00:15:51.489> writing 00:15:51.659 --> 00:15:51.669 align:start position:0% happens in every like if you're writing 00:15:51.669 --> 00:15:54.449 align:start position:0% happens in every like if you're writing a<00:15:51.910> VM<00:15:52.269> and<00:15:52.509> you<00:15:53.019> implement<00:15:53.439> in<00:15:53.769> any<00:15:54.009> kind<00:15:54.369> of 00:15:54.449 --> 00:15:54.459 align:start position:0% a VM and you implement in any kind of 00:15:54.459 --> 00:15:56.999 align:start position:0% a VM and you implement in any kind of protocol<00:15:55.029> you're<00:15:55.509> actually<00:15:55.929> going<00:15:56.169> to<00:15:56.319> use 00:15:56.999 --> 00:15:57.009 align:start position:0% protocol you're actually going to use 00:15:57.009 --> 00:15:58.679 align:start position:0% protocol you're actually going to use this<00:15:57.189> the<00:15:57.429> same<00:15:57.639> trick<00:15:57.910> over<00:15:58.029> and<00:15:58.299> over<00:15:58.540> and 00:15:58.679 --> 00:15:58.689 align:start position:0% this the same trick over and over and 00:15:58.689 --> 00:16:00.989 align:start position:0% this the same trick over and over and the<00:15:59.139> trick<00:15:59.350> is<00:15:59.470> simple<00:15:59.649> whenever<00:16:00.639> you<00:16:00.819> need<00:16:00.970> to 00:16:00.989 --> 00:16:00.999 align:start position:0% the trick is simple whenever you need to 00:16:00.999 --> 00:16:02.639 align:start position:0% the trick is simple whenever you need to share<00:16:01.269> some<00:16:01.540> information<00:16:01.779> with<00:16:02.199> other<00:16:02.379> nodes 00:16:02.639 --> 00:16:02.649 align:start position:0% share some information with other nodes 00:16:02.649 --> 00:16:05.039 align:start position:0% share some information with other nodes you're<00:16:03.279> going<00:16:03.489> to<00:16:03.610> re-encrypt<00:16:04.059> it<00:16:04.329> using<00:16:04.779> some 00:16:05.039 --> 00:16:05.049 align:start position:0% you're going to re-encrypt it using some 00:16:05.049 --> 00:16:07.470 align:start position:0% you're going to re-encrypt it using some like<00:16:05.649> a<00:16:05.679> one-time<00:16:06.220> pad<00:16:06.459> and<00:16:06.759> then<00:16:07.360> you're 00:16:07.470 --> 00:16:07.480 align:start position:0% like a one-time pad and then you're 00:16:07.480 --> 00:16:09.150 align:start position:0% like a one-time pad and then you're going<00:16:07.600> to<00:16:07.660> send<00:16:07.839> the<00:16:07.989> information<00:16:08.499> so<00:16:09.009> that's 00:16:09.150 --> 00:16:09.160 align:start position:0% going to send the information so that's 00:16:09.160 --> 00:16:10.949 align:start position:0% going to send the information so that's what<00:16:09.369> the<00:16:09.459> nodes<00:16:09.639> are<00:16:09.790> doing<00:16:09.999> here<00:16:10.360> then 00:16:10.949 --> 00:16:10.959 align:start position:0% what the nodes are doing here then 00:16:10.959 --> 00:16:12.659 align:start position:0% what the nodes are doing here then they're<00:16:11.139> communicating<00:16:11.919> that<00:16:12.040> information 00:16:12.659 --> 00:16:12.669 align:start position:0% they're communicating that information 00:16:12.669 --> 00:16:15.419 align:start position:0% they're communicating that information with<00:16:12.999> each<00:16:13.149> other<00:16:13.389> and<00:16:13.889> then<00:16:14.889> there<00:16:15.069> is<00:16:15.309> some 00:16:15.419 --> 00:16:15.429 align:start position:0% with each other and then there is some 00:16:15.429 --> 00:16:18.119 align:start position:0% with each other and then there is some more<00:16:15.549> local<00:16:15.790> computation<00:16:16.379> that<00:16:17.379> if<00:16:17.619> you<00:16:17.829> kind 00:16:18.119 --> 00:16:18.129 align:start position:0% more local computation that if you kind 00:16:18.129 --> 00:16:19.919 align:start position:0% more local computation that if you kind of<00:16:18.189> plug<00:16:18.429> the<00:16:18.610> algebra<00:16:18.999> in<00:16:19.179> you<00:16:19.749> would 00:16:19.919 --> 00:16:19.929 align:start position:0% of plug the algebra in you would 00:16:19.929 --> 00:16:23.579 align:start position:0% of plug the algebra in you would actually<00:16:20.169> see<00:16:20.709> that<00:16:21.519> the<00:16:22.269> Z's<00:16:22.540> here<00:16:23.019> end<00:16:23.199> up 00:16:23.579 --> 00:16:23.589 align:start position:0% actually see that the Z's here end up 00:16:23.589 --> 00:16:26.729 align:start position:0% actually see that the Z's here end up being<00:16:23.860> exactly<00:16:24.699> the<00:16:25.089> encrypted<00:16:25.869> shares<00:16:26.470> of 00:16:26.729 --> 00:16:26.739 align:start position:0% being exactly the encrypted shares of 00:16:26.739 --> 00:16:30.809 align:start position:0% being exactly the encrypted shares of the<00:16:27.339> product<00:16:27.790> of<00:16:27.970> X<00:16:28.239> Y<00:16:28.540> and<00:16:28.839> then<00:16:29.679> you<00:16:30.309> can<00:16:30.519> send 00:16:30.809 --> 00:16:30.819 align:start position:0% the product of X Y and then you can send 00:16:30.819 --> 00:16:32.819 align:start position:0% the product of X Y and then you can send that<00:16:31.059> back<00:16:31.329> to<00:16:31.389> the<00:16:31.629> consumer<00:16:32.199> and<00:16:32.410> the 00:16:32.819 --> 00:16:32.829 align:start position:0% that back to the consumer and the 00:16:32.829 --> 00:16:35.269 align:start position:0% that back to the consumer and the consumer<00:16:32.860> again<00:16:33.549> having<00:16:33.879> all<00:16:34.059> the<00:16:34.209> shares<00:16:34.480> can 00:16:35.269 --> 00:16:35.279 align:start position:0% consumer again having all the shares can 00:16:35.279 --> 00:16:37.590 align:start position:0% consumer again having all the shares can pull<00:16:36.279> them<00:16:36.429> back<00:16:36.610> in<00:16:36.850> and<00:16:36.999> decrypt<00:16:37.329> the<00:16:37.389> data 00:16:37.590 --> 00:16:37.600 align:start position:0% pull them back in and decrypt the data 00:16:37.600 --> 00:16:39.840 align:start position:0% pull them back in and decrypt the data and<00:16:37.959> the<00:16:38.169> network<00:16:38.529> so<00:16:38.739> nothing<00:16:39.129> which<00:16:39.339> is<00:16:39.369> and 00:16:39.840 --> 00:16:39.850 align:start position:0% and the network so nothing which is and 00:16:39.850 --> 00:16:43.439 align:start position:0% and the network so nothing which is and that's<00:16:40.059> the<00:16:40.179> point<00:16:41.639> now<00:16:42.639> why<00:16:42.999> did<00:16:43.179> I<00:16:43.269> show<00:16:43.419> you 00:16:43.439 --> 00:16:43.449 align:start position:0% that's the point now why did I show you 00:16:43.449 --> 00:16:45.090 align:start position:0% that's the point now why did I show you addition<00:16:43.839> and<00:16:43.959> multiplication<00:16:44.019> other<00:16:44.860> than 00:16:45.090 --> 00:16:45.100 align:start position:0% addition and multiplication other than 00:16:45.100 --> 00:16:47.429 align:start position:0% addition and multiplication other than them<00:16:45.369> being<00:16:45.639> like<00:16:45.850> relatively<00:16:46.389> simple<00:16:46.779> well 00:16:47.429 --> 00:16:47.439 align:start position:0% them being like relatively simple well 00:16:47.439 --> 00:16:49.220 align:start position:0% them being like relatively simple well there's<00:16:47.649> a<00:16:47.709> nice<00:16:47.889> theorem<00:16:48.309> saying<00:16:48.699> in 00:16:49.220 --> 00:16:49.230 align:start position:0% there's a nice theorem saying in 00:16:49.230 --> 00:16:52.019 align:start position:0% there's a nice theorem saying in computation<00:16:50.230> theory<00:16:50.619> saying<00:16:51.369> that<00:16:51.730> you<00:16:51.939> know 00:16:52.019 --> 00:16:52.029 align:start position:0% computation theory saying that you know 00:16:52.029 --> 00:16:53.329 align:start position:0% computation theory saying that you know if<00:16:52.179> you<00:16:52.269> have<00:16:52.449> addition<00:16:53.049> and<00:16:53.110> multiplication 00:16:53.329 --> 00:16:53.339 align:start position:0% if you have addition and multiplication 00:16:53.339 --> 00:16:56.249 align:start position:0% if you have addition and multiplication you<00:16:54.339> can<00:16:54.549> build<00:16:54.789> any<00:16:55.179> theory<00:16:55.600> you<00:16:55.720> can<00:16:55.899> compute 00:16:56.249 --> 00:16:56.259 align:start position:0% you can build any theory you can compute 00:16:56.259 --> 00:16:58.590 align:start position:0% you can build any theory you can compute any<00:16:56.439> circuit<00:16:56.859> essentially<00:16:57.789> you<00:16:57.879> can<00:16:58.089> compute 00:16:58.590 --> 00:16:58.600 align:start position:0% any circuit essentially you can compute 00:16:58.600 --> 00:17:00.929 align:start position:0% any circuit essentially you can compute anything<00:16:59.379> that<00:16:59.529> you<00:16:59.619> want<00:16:59.829> so<00:17:00.579> these<00:17:00.730> are<00:17:00.879> the 00:17:00.929 --> 00:17:00.939 align:start position:0% anything that you want so these are the 00:17:00.939 --> 00:17:03.539 align:start position:0% anything that you want so these are the building<00:17:01.179> blocks<00:17:01.419> that<00:17:01.509> we<00:17:01.689> need<00:17:02.189> there<00:17:03.189> are<00:17:03.309> I 00:17:03.539 --> 00:17:03.549 align:start position:0% building blocks that we need there are I 00:17:03.549 --> 00:17:05.699 align:start position:0% building blocks that we need there are I mean<00:17:04.240> a<00:17:04.269> lot<00:17:04.510> more<00:17:04.539> like<00:17:04.929> more<00:17:05.110> complicated 00:17:05.699 --> 00:17:05.709 align:start position:0% mean a lot more like more complicated 00:17:05.709 --> 00:17:07.879 align:start position:0% mean a lot more like more complicated protocols<00:17:06.130> how<00:17:06.610> do<00:17:06.669> you<00:17:06.819> compare<00:17:07.240> two<00:17:07.389> numbers 00:17:07.879 --> 00:17:07.889 align:start position:0% protocols how do you compare two numbers 00:17:07.889 --> 00:17:10.139 align:start position:0% protocols how do you compare two numbers you<00:17:08.889> know<00:17:09.010> how<00:17:09.159> do<00:17:09.220> you<00:17:09.339> do<00:17:09.519> like<00:17:09.699> floating 00:17:10.139 --> 00:17:10.149 align:start position:0% you know how do you do like floating 00:17:10.149 --> 00:17:13.240 align:start position:0% you know how do you do like floating points<00:17:10.510> and<00:17:10.629> fixed<00:17:10.929> point<00:17:11.110> operations 00:17:13.240 --> 00:17:13.250 align:start position:0% points and fixed point operations 00:17:13.250 --> 00:17:14.710 align:start position:0% points and fixed point operations many<00:17:13.699> of<00:17:13.820> these<00:17:13.940> obviously<00:17:14.420> I'm<00:17:14.480> not<00:17:14.570> gonna 00:17:14.710 --> 00:17:14.720 align:start position:0% many of these obviously I'm not gonna 00:17:14.720 --> 00:17:17.020 align:start position:0% many of these obviously I'm not gonna get<00:17:14.959> to<00:17:15.079> hear<00:17:15.380> that<00:17:15.650> was<00:17:15.860> a<00:17:15.890> lot<00:17:16.220> of<00:17:16.250> my<00:17:16.579> teases 00:17:17.020 --> 00:17:17.030 align:start position:0% get to hear that was a lot of my teases 00:17:17.030 --> 00:17:19.630 align:start position:0% get to hear that was a lot of my teases actually<00:17:17.589> doing<00:17:18.589> in<00:17:18.800> working<00:17:19.459> about 00:17:19.630 --> 00:17:19.640 align:start position:0% actually doing in working about 00:17:19.640 --> 00:17:21.819 align:start position:0% actually doing in working about improving<00:17:20.089> these<00:17:20.360> protocols<00:17:20.690> we<00:17:21.410> got<00:17:21.589> like 00:17:21.819 --> 00:17:21.829 align:start position:0% improving these protocols we got like 00:17:21.829 --> 00:17:25.150 align:start position:0% improving these protocols we got like between<00:17:22.490> 10<00:17:22.850> to<00:17:22.880> 100<00:17:23.449> X<00:17:23.660> speed-up<00:17:24.320> on<00:17:24.500> quite<00:17:25.130> a 00:17:25.150 --> 00:17:25.160 align:start position:0% between 10 to 100 X speed-up on quite a 00:17:25.160 --> 00:17:27.040 align:start position:0% between 10 to 100 X speed-up on quite a few<00:17:25.250> foundational<00:17:25.940> protocols<00:17:26.449> but 00:17:27.040 --> 00:17:27.050 align:start position:0% few foundational protocols but 00:17:27.050 --> 00:17:28.300 align:start position:0% few foundational protocols but unfortunately<00:17:27.589> I<00:17:27.650> won't<00:17:27.949> have<00:17:28.100> time<00:17:28.250> to 00:17:28.300 --> 00:17:28.310 align:start position:0% unfortunately I won't have time to 00:17:28.310 --> 00:17:32.710 align:start position:0% unfortunately I won't have time to discuss<00:17:29.000> that<00:17:29.180> here<00:17:30.010> so<00:17:31.390> that's<00:17:32.390> it<00:17:32.510> on<00:17:32.630> the 00:17:32.710 --> 00:17:32.720 align:start position:0% discuss that here so that's it on the 00:17:32.720 --> 00:17:34.570 align:start position:0% discuss that here so that's it on the hard<00:17:32.930> stuff<00:17:33.020> I<00:17:33.500> want<00:17:33.830> to<00:17:33.890> finish<00:17:34.130> with<00:17:34.430> like 00:17:34.570 --> 00:17:34.580 align:start position:0% hard stuff I want to finish with like 00:17:34.580 --> 00:17:37.570 align:start position:0% hard stuff I want to finish with like something<00:17:35.000> simpler<00:17:35.450> and<00:17:35.600> kind<00:17:35.840> of<00:17:35.930> nice<00:17:36.580> we 00:17:37.570 --> 00:17:37.580 align:start position:0% something simpler and kind of nice we 00:17:37.580 --> 00:17:39.550 align:start position:0% something simpler and kind of nice we feel<00:17:37.910> that<00:17:38.240> in<00:17:38.420> order<00:17:38.510> to<00:17:38.690> bootstrap<00:17:39.260> a<00:17:39.380> data 00:17:39.550 --> 00:17:39.560 align:start position:0% feel that in order to bootstrap a data 00:17:39.560 --> 00:17:42.220 align:start position:0% feel that in order to bootstrap a data marketplace<00:17:40.160> we<00:17:40.940> need<00:17:41.120> to<00:17:41.300> also<00:17:41.420> introduce 00:17:42.220 --> 00:17:42.230 align:start position:0% marketplace we need to also introduce 00:17:42.230 --> 00:17:43.780 align:start position:0% marketplace we need to also introduce some<00:17:42.260> use<00:17:42.530> cases<00:17:42.800> right<00:17:43.190> we<00:17:43.310> need<00:17:43.430> to<00:17:43.520> set<00:17:43.700> the 00:17:43.780 --> 00:17:43.790 align:start position:0% some use cases right we need to set the 00:17:43.790 --> 00:17:45.880 align:start position:0% some use cases right we need to set the demand<00:17:44.150> side<00:17:44.450> we<00:17:44.960> need<00:17:45.080> to<00:17:45.200> boots<00:17:45.410> up<00:17:45.620> it<00:17:45.710> with 00:17:45.880 --> 00:17:45.890 align:start position:0% demand side we need to boots up it with 00:17:45.890 --> 00:17:48.220 align:start position:0% demand side we need to boots up it with some<00:17:46.040> interesting<00:17:46.280> data<00:17:46.640> and<00:17:47.110> given<00:17:48.110> the 00:17:48.220 --> 00:17:48.230 align:start position:0% some interesting data and given the 00:17:48.230 --> 00:17:49.540 align:start position:0% some interesting data and given the space<00:17:48.500> we're<00:17:48.770> in<00:17:48.890> given<00:17:49.250> what<00:17:49.400> we're 00:17:49.540 --> 00:17:49.550 align:start position:0% space we're in given what we're 00:17:49.550 --> 00:17:52.320 align:start position:0% space we're in given what we're interested<00:17:49.790> in<00:17:50.290> given<00:17:51.290> the<00:17:51.410> state<00:17:51.860> of 00:17:52.320 --> 00:17:52.330 align:start position:0% interested in given the state of 00:17:52.330 --> 00:17:54.010 align:start position:0% interested in given the state of everything<00:17:53.330> that's<00:17:53.480> related<00:17:53.810> to<00:17:53.840> like 00:17:54.010 --> 00:17:54.020 align:start position:0% everything that's related to like 00:17:54.020 --> 00:17:56.680 align:start position:0% everything that's related to like blockchain<00:17:54.650> and<00:17:54.830> cryptocurrencies<00:17:55.280> data<00:17:55.790> we 00:17:56.680 --> 00:17:56.690 align:start position:0% blockchain and cryptocurrencies data we 00:17:56.690 --> 00:18:00.850 align:start position:0% blockchain and cryptocurrencies data we felt<00:17:56.960> that<00:17:57.050> building<00:17:58.600> I'm<00:17:59.600> sorry<00:17:59.930> data-driven 00:18:00.850 --> 00:18:00.860 align:start position:0% felt that building I'm sorry data-driven 00:18:00.860 --> 00:18:03.450 align:start position:0% felt that building I'm sorry data-driven investment<00:18:01.760> platform<00:18:02.000> for<00:18:02.930> cryptocurrencies 00:18:03.450 --> 00:18:03.460 align:start position:0% investment platform for cryptocurrencies 00:18:03.460 --> 00:18:06.760 align:start position:0% investment platform for cryptocurrencies where<00:18:04.460> all<00:18:04.700> the<00:18:04.970> data<00:18:05.120> that<00:18:05.930> that<00:18:06.260> comes<00:18:06.590> in 00:18:06.760 --> 00:18:06.770 align:start position:0% where all the data that that comes in 00:18:06.770 --> 00:18:08.640 align:start position:0% where all the data that that comes in and<00:18:06.920> all<00:18:07.010> the<00:18:07.130> data<00:18:07.250> that<00:18:07.370> is<00:18:07.610> like<00:18:07.820> stored<00:18:08.210> and 00:18:08.640 --> 00:18:08.650 align:start position:0% and all the data that is like stored and 00:18:08.650 --> 00:18:11.920 align:start position:0% and all the data that is like stored and is<00:18:09.650> going<00:18:10.250> to<00:18:10.400> be<00:18:10.520> kept<00:18:10.850> on<00:18:11.120> the<00:18:11.450> enigma<00:18:11.750> data 00:18:11.920 --> 00:18:11.930 align:start position:0% is going to be kept on the enigma data 00:18:11.930 --> 00:18:13.690 align:start position:0% is going to be kept on the enigma data marketplace<00:18:12.500> and<00:18:12.740> that<00:18:12.890> kind<00:18:13.130> of<00:18:13.190> sets<00:18:13.460> in 00:18:13.690 --> 00:18:13.700 align:start position:0% marketplace and that kind of sets in 00:18:13.700 --> 00:18:15.700 align:start position:0% marketplace and that kind of sets in boots<00:18:13.910> up<00:18:14.090> the<00:18:14.180> network<00:18:14.510> and<00:18:14.750> also<00:18:15.140> allows<00:18:15.500> us 00:18:15.700 --> 00:18:15.710 align:start position:0% boots up the network and also allows us 00:18:15.710 --> 00:18:18.280 align:start position:0% boots up the network and also allows us to<00:18:15.890> stress<00:18:16.220> this<00:18:16.520> the<00:18:16.820> protocol<00:18:17.480> as<00:18:17.690> we<00:18:18.170> are 00:18:18.280 --> 00:18:18.290 align:start position:0% to stress this the protocol as we are 00:18:18.290 --> 00:18:20.800 align:start position:0% to stress this the protocol as we are building<00:18:18.560> this<00:18:18.740> out<00:18:18.980> now<00:18:19.970> catalyst<00:18:20.510> is<00:18:20.630> still 00:18:20.800 --> 00:18:20.810 align:start position:0% building this out now catalyst is still 00:18:20.810 --> 00:18:22.540 align:start position:0% building this out now catalyst is still centralized<00:18:21.440> because<00:18:21.770> the<00:18:21.890> protocol<00:18:22.400> is<00:18:22.520> not 00:18:22.540 --> 00:18:22.550 align:start position:0% centralized because the protocol is not 00:18:22.550 --> 00:18:25.180 align:start position:0% centralized because the protocol is not yet<00:18:22.940> live<00:18:23.210> but<00:18:23.870> catalyst<00:18:24.350> is<00:18:24.590> live<00:18:24.950> and 00:18:25.180 --> 00:18:25.190 align:start position:0% yet live but catalyst is live and 00:18:25.190 --> 00:18:27.700 align:start position:0% yet live but catalyst is live and operational<00:18:25.820> if<00:18:26.210> you're<00:18:26.480> interested<00:18:26.900> in<00:18:27.080> algo 00:18:27.700 --> 00:18:27.710 align:start position:0% operational if you're interested in algo 00:18:27.710 --> 00:18:30.130 align:start position:0% operational if you're interested in algo trading<00:18:27.740> or<00:18:28.460> just<00:18:29.000> like<00:18:29.210> using<00:18:29.540> crypto<00:18:29.900> data 00:18:30.130 --> 00:18:30.140 align:start position:0% trading or just like using crypto data 00:18:30.140 --> 00:18:32.260 align:start position:0% trading or just like using crypto data for<00:18:30.470> doing<00:18:30.650> some<00:18:30.800> research<00:18:30.980> I<00:18:31.460> really<00:18:32.090> welcome 00:18:32.260 --> 00:18:32.270 align:start position:0% for doing some research I really welcome 00:18:32.270 --> 00:18:35.920 align:start position:0% for doing some research I really welcome you<00:18:32.630> to<00:18:32.840> try<00:18:33.260> it<00:18:33.320> out<00:18:33.500> it's<00:18:33.800> on<00:18:33.920> a<00:18:33.980> website<00:18:34.930> this 00:18:35.920 --> 00:18:35.930 align:start position:0% you to try it out it's on a website this 00:18:35.930 --> 00:18:38.020 align:start position:0% you to try it out it's on a website this is<00:18:36.110> one<00:18:36.320> cool<00:18:36.650> example<00:18:37.190> so<00:18:37.370> someone<00:18:37.760> from<00:18:37.910> our 00:18:38.020 --> 00:18:38.030 align:start position:0% is one cool example so someone from our 00:18:38.030 --> 00:18:41.190 align:start position:0% is one cool example so someone from our community<00:18:38.510> has<00:18:39.140> actually<00:18:39.590> used<00:18:39.620> catalyst<00:18:40.340> to 00:18:41.190 --> 00:18:41.200 align:start position:0% community has actually used catalyst to 00:18:41.200 --> 00:18:44.620 align:start position:0% community has actually used catalyst to build<00:18:42.200> a<00:18:42.350> model<00:18:42.710> of<00:18:43.150> Markovic<00:18:44.150> portfolio 00:18:44.620 --> 00:18:44.630 align:start position:0% build a model of Markovic portfolio 00:18:44.630 --> 00:18:47.380 align:start position:0% build a model of Markovic portfolio optimizations<00:18:45.320> on<00:18:45.560> crypto<00:18:45.950> assets<00:18:46.370> which<00:18:47.090> i 00:18:47.380 --> 00:18:47.390 align:start position:0% optimizations on crypto assets which i 00:18:47.390 --> 00:18:49.480 align:start position:0% optimizations on crypto assets which i think<00:18:47.690> is<00:18:47.930> fascinating<00:18:48.200> where<00:18:49.070> a<00:18:49.100> few<00:18:49.370> other 00:18:49.480 --> 00:18:49.490 align:start position:0% think is fascinating where a few other 00:18:49.490 --> 00:18:51.550 align:start position:0% think is fascinating where a few other examples<00:18:49.670> like<00:18:50.180> that<00:18:50.240> in<00:18:50.600> our<00:18:50.720> blog<00:18:50.930> and<00:18:51.200> I 00:18:51.550 --> 00:18:51.560 align:start position:0% examples like that in our blog and I 00:18:51.560 --> 00:18:53.590 align:start position:0% examples like that in our blog and I welcome<00:18:51.770> all<00:18:52.130> of<00:18:52.250> you<00:18:52.460> to<00:18:52.790> really<00:18:52.940> look<00:18:53.390> into 00:18:53.590 --> 00:18:53.600 align:start position:0% welcome all of you to really look into 00:18:53.600 --> 00:18:58.570 align:start position:0% welcome all of you to really look into that<00:18:54.460> and<00:18:55.630> with<00:18:56.630> that<00:18:56.780> I'd<00:18:56.930> like<00:18:57.050> to<00:18:57.110> finish<00:18:57.580> if 00:18:58.570 --> 00:18:58.580 align:start position:0% that and with that I'd like to finish if 00:18:58.580 --> 00:19:01.420 align:start position:0% that and with that I'd like to finish if you're<00:18:58.880> interested<00:18:59.510> in<00:18:59.780> you<00:19:00.470> know<00:19:00.500> off<00:19:00.830> chain 00:19:01.420 --> 00:19:01.430 align:start position:0% you're interested in you know off chain 00:19:01.430 --> 00:19:03.670 align:start position:0% you're interested in you know off chain computation<00:19:02.270> the<00:19:02.570> future<00:19:02.930> of<00:19:03.080> data<00:19:03.290> data 00:19:03.670 --> 00:19:03.680 align:start position:0% computation the future of data data 00:19:03.680 --> 00:19:06.850 align:start position:0% computation the future of data data marketplace<00:19:04.280> is<00:19:05.110> anything<00:19:06.110> that<00:19:06.350> I<00:19:06.380> discuss 00:19:06.850 --> 00:19:06.860 align:start position:0% marketplace is anything that I discuss 00:19:06.860 --> 00:19:10.030 align:start position:0% marketplace is anything that I discuss right<00:19:07.070> now<00:19:07.210> please<00:19:08.210> come<00:19:08.540> talk<00:19:08.780> to<00:19:08.840> us<00:19:09.050> I'm 00:19:10.030 --> 00:19:10.040 align:start position:0% right now please come talk to us I'm 00:19:10.040 --> 00:19:12.700 align:start position:0% right now please come talk to us I'm here<00:19:10.550> John<00:19:10.910> is<00:19:10.940> John<00:19:11.420> show<00:19:11.600> your<00:19:11.750> hand<00:19:11.960> John<00:19:12.560> is 00:19:12.700 --> 00:19:12.710 align:start position:0% here John is John show your hand John is 00:19:12.710 --> 00:19:15.370 align:start position:0% here John is John show your hand John is also<00:19:12.860> here<00:19:13.160> John<00:19:13.370> is<00:19:13.400> my<00:19:13.580> co-founder<00:19:14.380> please 00:19:15.370 --> 00:19:15.380 align:start position:0% also here John is my co-founder please 00:19:15.380 --> 00:19:17.800 align:start position:0% also here John is my co-founder please come<00:19:15.620> talk<00:19:15.800> to<00:19:15.860> us<00:19:16.040> and<00:19:16.370> if<00:19:17.300> you're<00:19:17.540> excited 00:19:17.800 --> 00:19:17.810 align:start position:0% come talk to us and if you're excited 00:19:17.810 --> 00:19:19.630 align:start position:0% come talk to us and if you're excited about<00:19:18.170> this<00:19:18.350> and<00:19:18.650> like<00:19:18.830> you<00:19:19.070> really<00:19:19.280> want<00:19:19.550> to 00:19:19.630 --> 00:19:19.640 align:start position:0% about this and like you really want to 00:19:19.640 --> 00:19:21.430 align:start position:0% about this and like you really want to be<00:19:19.760> at<00:19:19.850> the<00:19:19.970> forefront<00:19:20.240> of<00:19:20.720> solving<00:19:21.350> like 00:19:21.430 --> 00:19:21.440 align:start position:0% be at the forefront of solving like 00:19:21.440 --> 00:19:23.440 align:start position:0% be at the forefront of solving like really<00:19:21.740> some<00:19:22.370> of<00:19:22.400> the<00:19:22.490> most<00:19:22.610> interesting<00:19:23.120> and 00:19:23.440 --> 00:19:23.450 align:start position:0% really some of the most interesting and 00:19:23.450 --> 00:19:26.020 align:start position:0% really some of the most interesting and hardest<00:19:23.780> problems<00:19:24.170> we're<00:19:24.950> like<00:19:25.160> we're<00:19:25.460> hiring 00:19:26.020 --> 00:19:26.030 align:start position:0% hardest problems we're like we're hiring 00:19:26.030 --> 00:19:28.630 align:start position:0% hardest problems we're like we're hiring so<00:19:26.420> come<00:19:26.960> talk<00:19:27.200> to<00:19:27.230> us<00:19:27.500> about<00:19:27.590> that<00:19:27.830> as<00:19:27.980> well 00:19:28.630 --> 00:19:28.640 align:start position:0% so come talk to us about that as well 00:19:28.640 --> 00:19:32.540 align:start position:0% so come talk to us about that as well we'd<00:19:29.210> love<00:19:29.360> to<00:19:29.420> hear<00:19:29.660> from<00:19:29.780> you<00:19:30.370> thank<00:19:31.370> you 00:19:32.540 --> 00:19:32.550 align:start position:0% we'd love to hear from you thank you 00:19:32.550 --> 00:19:39.340 align:start position:0% we'd love to hear from you thank you [Applause] 00:19:39.340 --> 00:19:39.350 align:start position:0% [Applause] 00:19:39.350 --> 00:19:46.940 align:start position:0% [Applause] [Music]