WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:02.510 align:start position:0% all<00:00:00.329> right<00:00:00.450> hi<00:00:00.659> everyone<00:00:01.020> my<00:00:01.770> name<00:00:01.920> is<00:00:01.949> guy 00:00:02.510 --> 00:00:02.520 align:start position:0% all right hi everyone my name is guy 00:00:02.520 --> 00:00:04.940 align:start position:0% all right hi everyone my name is guy Siskind<00:00:03.090> I'm<00:00:03.360> the<00:00:03.600> CEO<00:00:03.990> and<00:00:04.319> co-founder<00:00:04.529> of 00:00:04.940 --> 00:00:04.950 align:start position:0% Siskind I'm the CEO and co-founder of 00:00:04.950 --> 00:00:08.690 align:start position:0% Siskind I'm the CEO and co-founder of enigma<00:00:06.319> and<00:00:07.319> I<00:00:07.589> want<00:00:07.799> to<00:00:07.859> tell<00:00:08.010> you<00:00:08.099> today<00:00:08.400> how 00:00:08.690 --> 00:00:08.700 align:start position:0% enigma and I want to tell you today how 00:00:08.700 --> 00:00:10.129 align:start position:0% enigma and I want to tell you today how you<00:00:08.730> can<00:00:08.880> build<00:00:09.360> scalable 00:00:10.129 --> 00:00:10.139 align:start position:0% you can build scalable 00:00:10.139 --> 00:00:11.980 align:start position:0% you can build scalable privacy-preserving 00:00:11.980 --> 00:00:11.990 align:start position:0% privacy-preserving 00:00:11.990 --> 00:00:16.730 align:start position:0% privacy-preserving smart<00:00:12.990> contracts<00:00:13.500> on<00:00:13.830> aetherium<00:00:15.650> so<00:00:16.650> the 00:00:16.730 --> 00:00:16.740 align:start position:0% smart contracts on aetherium so the 00:00:16.740 --> 00:00:18.439 align:start position:0% smart contracts on aetherium so the problem<00:00:17.039> with<00:00:17.160> blockchain<00:00:17.640> is<00:00:17.880> that<00:00:18.270> it's 00:00:18.439 --> 00:00:18.449 align:start position:0% problem with blockchain is that it's 00:00:18.449 --> 00:00:20.720 align:start position:0% problem with blockchain is that it's completely<00:00:19.080> public<00:00:19.470> everything<00:00:20.340> you<00:00:20.550> put<00:00:20.670> on 00:00:20.720 --> 00:00:20.730 align:start position:0% completely public everything you put on 00:00:20.730 --> 00:00:22.400 align:start position:0% completely public everything you put on the<00:00:20.880> blockchain<00:00:21.119> is<00:00:21.660> there<00:00:21.869> for<00:00:22.050> everyone<00:00:22.289> to 00:00:22.400 --> 00:00:22.410 align:start position:0% the blockchain is there for everyone to 00:00:22.410 --> 00:00:26.480 align:start position:0% the blockchain is there for everyone to see<00:00:22.529> and<00:00:23.039> also<00:00:23.400> forever<00:00:24.320> that<00:00:25.320> means<00:00:25.680> that<00:00:26.369> you 00:00:26.480 --> 00:00:26.490 align:start position:0% see and also forever that means that you 00:00:26.490 --> 00:00:28.220 align:start position:0% see and also forever that means that you cannot<00:00:26.849> use<00:00:27.180> sensitive<00:00:27.750> data<00:00:27.930> on<00:00:28.080> the 00:00:28.220 --> 00:00:28.230 align:start position:0% cannot use sensitive data on the 00:00:28.230 --> 00:00:30.500 align:start position:0% cannot use sensitive data on the blockchain<00:00:28.500> today<00:00:29.039> and<00:00:29.340> that's<00:00:30.060> a<00:00:30.150> big<00:00:30.330> issue 00:00:30.500 --> 00:00:30.510 align:start position:0% blockchain today and that's a big issue 00:00:30.510 --> 00:00:33.200 align:start position:0% blockchain today and that's a big issue I'm<00:00:31.380> sure<00:00:31.679> you<00:00:31.800> would<00:00:31.949> all<00:00:32.070> agree<00:00:32.219> that<00:00:32.460> any 00:00:33.200 --> 00:00:33.210 align:start position:0% I'm sure you would all agree that any 00:00:33.210 --> 00:00:35.900 align:start position:0% I'm sure you would all agree that any application<00:00:33.660> today<00:00:34.380> whether<00:00:34.680> centralized<00:00:35.370> or 00:00:35.900 --> 00:00:35.910 align:start position:0% application today whether centralized or 00:00:35.910 --> 00:00:38.330 align:start position:0% application today whether centralized or decentralized<00:00:36.140> is<00:00:37.140> going<00:00:37.770> to<00:00:37.920> need<00:00:38.100> to<00:00:38.219> use 00:00:38.330 --> 00:00:38.340 align:start position:0% decentralized is going to need to use 00:00:38.340 --> 00:00:40.700 align:start position:0% decentralized is going to need to use sensitive<00:00:38.850> data<00:00:39.030> in<00:00:39.420> some<00:00:39.750> form<00:00:40.079> or<00:00:40.290> another 00:00:40.700 --> 00:00:40.710 align:start position:0% sensitive data in some form or another 00:00:40.710 --> 00:00:44.810 align:start position:0% sensitive data in some form or another and<00:00:41.989> obviously<00:00:42.989> this<00:00:43.440> greatly<00:00:43.739> limits<00:00:44.309> the 00:00:44.810 --> 00:00:44.820 align:start position:0% and obviously this greatly limits the 00:00:44.820 --> 00:00:46.520 align:start position:0% and obviously this greatly limits the potential<00:00:45.360> applications<00:00:45.960> that<00:00:46.079> we<00:00:46.230> can<00:00:46.379> use 00:00:46.520 --> 00:00:46.530 align:start position:0% potential applications that we can use 00:00:46.530 --> 00:00:50.330 align:start position:0% potential applications that we can use with<00:00:46.890> the<00:00:46.920> technology<00:00:48.860> so<00:00:49.860> if<00:00:49.950> you<00:00:50.039> want<00:00:50.219> to<00:00:50.280> be 00:00:50.330 --> 00:00:50.340 align:start position:0% with the technology so if you want to be 00:00:50.340 --> 00:00:53.029 align:start position:0% with the technology so if you want to be a<00:00:50.370> bit<00:00:50.520> more<00:00:50.670> technical<00:00:51.379> smart<00:00:52.379> contracts 00:00:53.029 --> 00:00:53.039 align:start position:0% a bit more technical smart contracts 00:00:53.039 --> 00:00:54.770 align:start position:0% a bit more technical smart contracts which<00:00:53.250> is<00:00:53.399> the<00:00:53.550> unit<00:00:53.789> of<00:00:53.910> execution<00:00:54.510> that<00:00:54.660> we 00:00:54.770 --> 00:00:54.780 align:start position:0% which is the unit of execution that we 00:00:54.780 --> 00:00:55.850 align:start position:0% which is the unit of execution that we have<00:00:54.930> in<00:00:55.170> blockchains 00:00:55.850 --> 00:00:55.860 align:start position:0% have in blockchains 00:00:55.860 --> 00:00:58.459 align:start position:0% have in blockchains gives<00:00:56.670> us<00:00:56.850> correctness<00:00:57.300> but<00:00:58.020> it<00:00:58.140> does<00:00:58.260> not 00:00:58.459 --> 00:00:58.469 align:start position:0% gives us correctness but it does not 00:00:58.469 --> 00:01:01.729 align:start position:0% gives us correctness but it does not give<00:00:58.739> us<00:00:58.890> privacy<00:00:59.570> correctness<00:01:00.570> means<00:01:01.020> that 00:01:01.729 --> 00:01:01.739 align:start position:0% give us privacy correctness means that 00:01:01.739 --> 00:01:04.910 align:start position:0% give us privacy correctness means that if<00:01:01.920> you're<00:01:02.250> running<00:01:02.460> a<00:01:02.910> computation<00:01:03.769> then<00:01:04.769> you 00:01:04.910 --> 00:01:04.920 align:start position:0% if you're running a computation then you 00:01:04.920 --> 00:01:07.820 align:start position:0% if you're running a computation then you can<00:01:05.129> be<00:01:05.369> then<00:01:06.330> you<00:01:06.450> can<00:01:06.600> be<00:01:06.720> guaranteed<00:01:06.900> that 00:01:07.820 --> 00:01:07.830 align:start position:0% can be then you can be guaranteed that 00:01:07.830 --> 00:01:09.350 align:start position:0% can be then you can be guaranteed that you're<00:01:07.979> gonna<00:01:08.100> get<00:01:08.280> the<00:01:08.400> right<00:01:08.549> result<00:01:08.970> and<00:01:09.210> no 00:01:09.350 --> 00:01:09.360 align:start position:0% you're gonna get the right result and no 00:01:09.360 --> 00:01:11.300 align:start position:0% you're gonna get the right result and no one<00:01:09.479> can<00:01:09.630> temporarily<00:01:09.960> and<00:01:10.439> that's<00:01:11.010> great 00:01:11.300 --> 00:01:11.310 align:start position:0% one can temporarily and that's great 00:01:11.310 --> 00:01:13.340 align:start position:0% one can temporarily and that's great that's<00:01:11.760> why<00:01:12.030> we're<00:01:12.240> really<00:01:12.510> excited<00:01:13.080> about 00:01:13.340 --> 00:01:13.350 align:start position:0% that's why we're really excited about 00:01:13.350 --> 00:01:15.590 align:start position:0% that's why we're really excited about blockchain<00:01:13.860> technology<00:01:14.430> but<00:01:15.270> we<00:01:15.450> need 00:01:15.590 --> 00:01:15.600 align:start position:0% blockchain technology but we need 00:01:15.600 --> 00:01:17.450 align:start position:0% blockchain technology but we need something<00:01:16.020> stronger<00:01:16.259> and<00:01:16.680> a<00:01:17.070> stronger 00:01:17.450 --> 00:01:17.460 align:start position:0% something stronger and a stronger 00:01:17.460 --> 00:01:19.609 align:start position:0% something stronger and a stronger definition<00:01:18.119> is<00:01:18.299> what<00:01:18.780> we<00:01:18.960> call<00:01:19.140> secret 00:01:19.609 --> 00:01:19.619 align:start position:0% definition is what we call secret 00:01:19.619 --> 00:01:22.070 align:start position:0% definition is what we call secret contracts<00:01:20.250> that<00:01:20.700> provide<00:01:21.090> both<00:01:21.330> both 00:01:22.070 --> 00:01:22.080 align:start position:0% contracts that provide both both 00:01:22.080 --> 00:01:24.499 align:start position:0% contracts that provide both both correctness<00:01:22.680> of<00:01:22.890> the<00:01:23.009> execution<00:01:23.640> but<00:01:24.330> also 00:01:24.499 --> 00:01:24.509 align:start position:0% correctness of the execution but also 00:01:24.509 --> 00:01:28.490 align:start position:0% correctness of the execution but also privacy<00:01:25.049> of<00:01:25.259> the<00:01:25.380> data<00:01:26.960> so<00:01:27.960> in<00:01:28.080> Ligue<00:01:28.200> 1<00:01:28.259> is<00:01:28.409> the 00:01:28.490 --> 00:01:28.500 align:start position:0% privacy of the data so in Ligue 1 is the 00:01:28.500 --> 00:01:31.760 align:start position:0% privacy of the data so in Ligue 1 is the first<00:01:28.829> available<00:01:29.460> platform<00:01:30.439> for<00:01:31.439> you<00:01:31.560> to 00:01:31.760 --> 00:01:31.770 align:start position:0% first available platform for you to 00:01:31.770 --> 00:01:34.370 align:start position:0% first available platform for you to build<00:01:32.040> secret<00:01:32.850> contracts<00:01:33.420> and<00:01:33.570> execute<00:01:34.229> them 00:01:34.370 --> 00:01:34.380 align:start position:0% build secret contracts and execute them 00:01:34.380 --> 00:01:36.319 align:start position:0% build secret contracts and execute them it<00:01:34.740> is<00:01:35.460> the<00:01:35.579> first<00:01:35.790> time<00:01:36.030> that<00:01:36.090> you<00:01:36.299> can 00:01:36.319 --> 00:01:36.329 align:start position:0% it is the first time that you can 00:01:36.329 --> 00:01:39.260 align:start position:0% it is the first time that you can actually<00:01:36.750> add<00:01:37.320> and<00:01:38.070> use<00:01:38.400> sensitive 00:01:39.260 --> 00:01:39.270 align:start position:0% actually add and use sensitive 00:01:39.270 --> 00:01:41.960 align:start position:0% actually add and use sensitive information<00:01:39.540> on<00:01:40.290> the<00:01:40.770> blockchain<00:01:41.040> without 00:01:41.960 --> 00:01:41.970 align:start position:0% information on the blockchain without 00:01:41.970 --> 00:01:43.330 align:start position:0% information on the blockchain without compromising<00:01:42.750> central<00:01:43.140> is<00:01:43.229> a 00:01:43.330 --> 00:01:43.340 align:start position:0% compromising central is a 00:01:43.340 --> 00:01:48.080 align:start position:0% compromising central is a decentralization<00:01:46.070> enigma<00:01:47.070> works<00:01:47.340> by<00:01:48.060> using 00:01:48.080 --> 00:01:48.090 align:start position:0% decentralization enigma works by using 00:01:48.090 --> 00:01:50.840 align:start position:0% decentralization enigma works by using privacy<00:01:49.020> enhancing<00:01:49.320> technologies<00:01:49.850> that 00:01:50.840 --> 00:01:50.850 align:start position:0% privacy enhancing technologies that 00:01:50.850 --> 00:01:52.520 align:start position:0% privacy enhancing technologies that allow<00:01:51.149> you<00:01:51.210> to<00:01:51.329> basically<00:01:51.840> compute<00:01:52.320> over 00:01:52.520 --> 00:01:52.530 align:start position:0% allow you to basically compute over 00:01:52.530 --> 00:01:54.950 align:start position:0% allow you to basically compute over encrypted<00:01:53.130> data<00:01:53.340> that's<00:01:54.180> the<00:01:54.390> main<00:01:54.600> secret 00:01:54.950 --> 00:01:54.960 align:start position:0% encrypted data that's the main secret 00:01:54.960 --> 00:01:59.240 align:start position:0% encrypted data that's the main secret sauce<00:01:55.229> the<00:01:55.920> second<00:01:56.430> part<00:01:56.700> for<00:01:57.509> scalability<00:01:58.250> we 00:01:59.240 --> 00:01:59.250 align:start position:0% sauce the second part for scalability we 00:01:59.250 --> 00:02:02.569 align:start position:0% sauce the second part for scalability we take<00:01:59.520> the<00:01:59.670> position<00:02:00.270> that<00:02:00.950> execution<00:02:01.950> should 00:02:02.569 --> 00:02:02.579 align:start position:0% take the position that execution should 00:02:02.579 --> 00:02:05.959 align:start position:0% take the position that execution should be<00:02:02.729> separated<00:02:03.390> from<00:02:04.200> consensus<00:02:04.920> block<00:02:05.700> shares 00:02:05.959 --> 00:02:05.969 align:start position:0% be separated from consensus block shares 00:02:05.969 --> 00:02:08.330 align:start position:0% be separated from consensus block shares are<00:02:06.149> really<00:02:06.420> good<00:02:06.659> at<00:02:06.899> reaching<00:02:07.350> consensus<00:02:08.160> on 00:02:08.330 --> 00:02:08.340 align:start position:0% are really good at reaching consensus on 00:02:08.340 --> 00:02:11.029 align:start position:0% are really good at reaching consensus on small<00:02:09.030> amounts<00:02:09.420> of<00:02:09.509> public<00:02:09.869> data<00:02:10.020> but<00:02:10.890> they're 00:02:11.029 --> 00:02:11.039 align:start position:0% small amounts of public data but they're 00:02:11.039 --> 00:02:13.309 align:start position:0% small amounts of public data but they're not<00:02:11.250> good<00:02:11.610> at<00:02:11.879> keeping<00:02:12.330> privacy<00:02:13.020> and<00:02:13.170> they're 00:02:13.309 --> 00:02:13.319 align:start position:0% not good at keeping privacy and they're 00:02:13.319 --> 00:02:13.580 align:start position:0% not good at keeping privacy and they're not 00:02:13.580 --> 00:02:13.590 align:start position:0% not 00:02:13.590 --> 00:02:17.540 align:start position:0% not good<00:02:13.890> its<00:02:14.220> scalable<00:02:14.910> execution<00:02:16.280> so<00:02:17.280> we<00:02:17.400> have<00:02:17.519> a 00:02:17.540 --> 00:02:17.550 align:start position:0% good its scalable execution so we have a 00:02:17.550 --> 00:02:21.770 align:start position:0% good its scalable execution so we have a long<00:02:17.760> history<00:02:18.209> of<00:02:18.709> of<00:02:19.709> actually<00:02:20.190> doing<00:02:21.000> this<00:02:21.150> a 00:02:21.770 --> 00:02:21.780 align:start position:0% long history of of actually doing this a 00:02:21.780 --> 00:02:23.900 align:start position:0% long history of of actually doing this a few<00:02:21.840> years<00:02:22.319> ago<00:02:22.500> we<00:02:22.860> came<00:02:23.099> up<00:02:23.340> with<00:02:23.489> these<00:02:23.700> two 00:02:23.900 --> 00:02:23.910 align:start position:0% few years ago we came up with these two 00:02:23.910 --> 00:02:25.940 align:start position:0% few years ago we came up with these two ideas<00:02:24.060> and<00:02:24.599> we<00:02:25.050> published<00:02:25.470> these<00:02:25.590> in<00:02:25.800> two 00:02:25.940 --> 00:02:25.950 align:start position:0% ideas and we published these in two 00:02:25.950 --> 00:02:29.089 align:start position:0% ideas and we published these in two papers<00:02:26.870> decentralizing<00:02:27.870> privacy<00:02:28.410> and<00:02:28.709> the 00:02:29.089 --> 00:02:29.099 align:start position:0% papers decentralizing privacy and the 00:02:29.099 --> 00:02:30.890 align:start position:0% papers decentralizing privacy and the original<00:02:29.489> white<00:02:29.700> paper<00:02:30.000> for<00:02:30.239> enigma<00:02:30.690> and 00:02:30.890 --> 00:02:30.900 align:start position:0% original white paper for enigma and 00:02:30.900 --> 00:02:34.850 align:start position:0% original white paper for enigma and these<00:02:31.830> papers<00:02:32.510> currently<00:02:33.510> stand<00:02:33.810> on<00:02:34.019> more 00:02:34.850 --> 00:02:34.860 align:start position:0% these papers currently stand on more 00:02:34.860 --> 00:02:37.430 align:start position:0% these papers currently stand on more than<00:02:34.950> 500<00:02:35.269> citations<00:02:36.269> combined<00:02:36.660> so<00:02:37.290> they 00:02:37.430 --> 00:02:37.440 align:start position:0% than 500 citations combined so they 00:02:37.440 --> 00:02:40.729 align:start position:0% than 500 citations combined so they really<00:02:37.769> become<00:02:38.099> a<00:02:38.730> cornerstone<00:02:39.420> in<00:02:40.110> the<00:02:40.379> space 00:02:40.729 --> 00:02:40.739 align:start position:0% really become a cornerstone in the space 00:02:40.739 --> 00:02:43.580 align:start position:0% really become a cornerstone in the space and<00:02:41.040> really<00:02:41.970> they<00:02:42.360> are<00:02:42.390> they<00:02:42.989> were<00:02:43.049> the<00:02:43.290> first 00:02:43.580 --> 00:02:43.590 align:start position:0% and really they are they were the first 00:02:43.590 --> 00:02:46.400 align:start position:0% and really they are they were the first to<00:02:43.890> crystallize<00:02:44.489> the<00:02:44.700> ideas<00:02:45.150> that<00:02:45.420> if<00:02:46.170> you 00:02:46.400 --> 00:02:46.410 align:start position:0% to crystallize the ideas that if you 00:02:46.410 --> 00:02:47.780 align:start position:0% to crystallize the ideas that if you want<00:02:46.590> to<00:02:46.680> have<00:02:46.829> privacy<00:02:47.250> in<00:02:47.400> the<00:02:47.549> blockchain 00:02:47.780 --> 00:02:47.790 align:start position:0% want to have privacy in the blockchain 00:02:47.790 --> 00:02:49.430 align:start position:0% want to have privacy in the blockchain you're<00:02:48.630> gonna<00:02:48.840> use<00:02:49.019> some<00:02:49.230> additional 00:02:49.430 --> 00:02:49.440 align:start position:0% you're gonna use some additional 00:02:49.440 --> 00:02:51.589 align:start position:0% you're gonna use some additional cryptography<00:02:50.340> you're<00:02:50.880> gonna<00:02:51.090> use<00:02:51.269> something 00:02:51.589 --> 00:02:51.599 align:start position:0% cryptography you're gonna use something 00:02:51.599 --> 00:02:53.180 align:start position:0% cryptography you're gonna use something that<00:02:51.870> allows<00:02:52.140> you<00:02:52.260> to<00:02:52.319> cut<00:02:52.590> two<00:02:52.739> computer 00:02:53.180 --> 00:02:53.190 align:start position:0% that allows you to cut two computer 00:02:53.190 --> 00:02:56.150 align:start position:0% that allows you to cut two computer encrypted<00:02:53.760> data<00:02:53.970> and<00:02:54.360> on<00:02:54.870> top<00:02:55.110> of<00:02:55.290> that<00:02:55.440> if<00:02:55.709> you 00:02:56.150 --> 00:02:56.160 align:start position:0% encrypted data and on top of that if you 00:02:56.160 --> 00:02:57.949 align:start position:0% encrypted data and on top of that if you really<00:02:56.400> want<00:02:56.579> to<00:02:56.670> have<00:02:56.790> scale<00:02:57.120> you<00:02:57.720> got<00:02:57.930> a 00:02:57.949 --> 00:02:57.959 align:start position:0% really want to have scale you got a 00:02:57.959 --> 00:03:01.280 align:start position:0% really want to have scale you got a separate<00:02:58.700> execution<00:02:59.700> from<00:03:00.360> consensus<00:03:01.079> and 00:03:01.280 --> 00:03:01.290 align:start position:0% separate execution from consensus and 00:03:01.290 --> 00:03:03.890 align:start position:0% separate execution from consensus and you<00:03:01.799> know<00:03:01.950> I<00:03:01.980> was<00:03:02.310> here<00:03:02.610> this<00:03:02.790> week<00:03:03.060> and<00:03:03.360> it<00:03:03.780> was 00:03:03.890 --> 00:03:03.900 align:start position:0% you know I was here this week and it was 00:03:03.900 --> 00:03:06.680 align:start position:0% you know I was here this week and it was really<00:03:04.079> inspiring<00:03:04.739> to<00:03:05.129> see<00:03:05.220> that<00:03:05.700> so<00:03:06.540> many 00:03:06.680 --> 00:03:06.690 align:start position:0% really inspiring to see that so many 00:03:06.690 --> 00:03:08.360 align:start position:0% really inspiring to see that so many other<00:03:06.930> projects<00:03:07.470> are<00:03:07.620> actually<00:03:07.920> taking<00:03:08.340> that 00:03:08.360 --> 00:03:08.370 align:start position:0% other projects are actually taking that 00:03:08.370 --> 00:03:10.699 align:start position:0% other projects are actually taking that approach<00:03:08.760> right<00:03:09.090> now<00:03:09.269> so<00:03:09.870> maybe<00:03:10.049> it's<00:03:10.260> taken<00:03:10.620> a 00:03:10.699 --> 00:03:10.709 align:start position:0% approach right now so maybe it's taken a 00:03:10.709 --> 00:03:12.619 align:start position:0% approach right now so maybe it's taken a few<00:03:10.920> years<00:03:11.190> but<00:03:11.730> it<00:03:11.819> seems<00:03:12.030> that<00:03:12.120> the<00:03:12.239> industry 00:03:12.619 --> 00:03:12.629 align:start position:0% few years but it seems that the industry 00:03:12.629 --> 00:03:16.250 align:start position:0% few years but it seems that the industry is<00:03:12.690> finally<00:03:13.790> coalescing<00:03:14.790> into<00:03:15.120> the<00:03:15.569> idea<00:03:15.870> that 00:03:16.250 --> 00:03:16.260 align:start position:0% is finally coalescing into the idea that 00:03:16.260 --> 00:03:18.650 align:start position:0% is finally coalescing into the idea that execution<00:03:17.069> and<00:03:17.489> consent<00:03:18.239> should<00:03:18.510> be 00:03:18.650 --> 00:03:18.660 align:start position:0% execution and consent should be 00:03:18.660 --> 00:03:20.960 align:start position:0% execution and consent should be separated<00:03:19.139> and<00:03:19.470> that<00:03:19.920> privacy<00:03:20.370> for<00:03:20.730> smart 00:03:20.960 --> 00:03:20.970 align:start position:0% separated and that privacy for smart 00:03:20.970 --> 00:03:23.479 align:start position:0% separated and that privacy for smart contracts<00:03:21.600> is<00:03:21.690> really<00:03:22.380> important<00:03:22.920> and<00:03:23.130> we 00:03:23.479 --> 00:03:23.489 align:start position:0% contracts is really important and we 00:03:23.489 --> 00:03:25.400 align:start position:0% contracts is really important and we should<00:03:23.519> not<00:03:23.910> settle<00:03:24.239> just<00:03:24.630> for<00:03:24.780> transactional 00:03:25.400 --> 00:03:25.410 align:start position:0% should not settle just for transactional 00:03:25.410 --> 00:03:29.780 align:start position:0% should not settle just for transactional privacy<00:03:28.099> so<00:03:29.099> I'm<00:03:29.220> mostly<00:03:29.340> going<00:03:29.639> to<00:03:29.730> talk 00:03:29.780 --> 00:03:29.790 align:start position:0% privacy so I'm mostly going to talk 00:03:29.790 --> 00:03:32.300 align:start position:0% privacy so I'm mostly going to talk today<00:03:30.120> about<00:03:30.269> the<00:03:30.810> Enigma<00:03:31.440> discovery<00:03:31.889> Network 00:03:32.300 --> 00:03:32.310 align:start position:0% today about the Enigma discovery Network 00:03:32.310 --> 00:03:34.220 align:start position:0% today about the Enigma discovery Network this<00:03:32.819> is<00:03:32.880> the<00:03:33.090> first<00:03:33.329> network<00:03:33.780> that<00:03:33.989> we're 00:03:34.220 --> 00:03:34.230 align:start position:0% this is the first network that we're 00:03:34.230 --> 00:03:37.460 align:start position:0% this is the first network that we're pushing<00:03:35.160> out<00:03:35.459> right<00:03:35.730> now<00:03:35.989> the<00:03:36.989> network<00:03:37.260> has 00:03:37.460 --> 00:03:37.470 align:start position:0% pushing out right now the network has 00:03:37.470 --> 00:03:38.900 align:start position:0% pushing out right now the network has all<00:03:37.560> the<00:03:37.680> great<00:03:37.829> features<00:03:38.099> I<00:03:38.400> told<00:03:38.609> you<00:03:38.790> it 00:03:38.900 --> 00:03:38.910 align:start position:0% all the great features I told you it 00:03:38.910 --> 00:03:40.370 align:start position:0% all the great features I told you it allows<00:03:39.180> you<00:03:39.359> to<00:03:39.480> execute<00:03:39.810> these<00:03:40.049> secret 00:03:40.370 --> 00:03:40.380 align:start position:0% allows you to execute these secret 00:03:40.380 --> 00:03:42.860 align:start position:0% allows you to execute these secret contracts<00:03:40.980> and<00:03:41.130> it's<00:03:41.280> scale<00:03:41.549> but<00:03:42.299> it<00:03:42.389> also<00:03:42.569> has 00:03:42.860 --> 00:03:42.870 align:start position:0% contracts and it's scale but it also has 00:03:42.870 --> 00:03:44.690 align:start position:0% contracts and it's scale but it also has other<00:03:43.079> important<00:03:43.620> properties<00:03:44.099> its 00:03:44.690 --> 00:03:44.700 align:start position:0% other important properties its 00:03:44.700 --> 00:03:47.360 align:start position:0% other important properties its permissionless<00:03:45.590> completely<00:03:46.590> it's 00:03:47.360 --> 00:03:47.370 align:start position:0% permissionless completely it's 00:03:47.370 --> 00:03:49.819 align:start position:0% permissionless completely it's economically<00:03:48.150> incentivized<00:03:48.900> which<00:03:49.530> means 00:03:49.819 --> 00:03:49.829 align:start position:0% economically incentivized which means 00:03:49.829 --> 00:03:51.440 align:start position:0% economically incentivized which means that<00:03:49.950> we<00:03:50.069> use<00:03:50.220> some<00:03:50.459> form<00:03:50.700> of<00:03:50.790> proof<00:03:51.060> of<00:03:51.209> stake 00:03:51.440 --> 00:03:51.450 align:start position:0% that we use some form of proof of stake 00:03:51.450 --> 00:03:53.900 align:start position:0% that we use some form of proof of stake model<00:03:51.930> and<00:03:52.169> I<00:03:53.130> think<00:03:53.160> what's<00:03:53.519> mostly 00:03:53.900 --> 00:03:53.910 align:start position:0% model and I think what's mostly 00:03:53.910 --> 00:03:55.819 align:start position:0% model and I think what's mostly important<00:03:54.359> for<00:03:54.510> developers<00:03:55.109> here<00:03:55.380> and<00:03:55.650> for 00:03:55.819 --> 00:03:55.829 align:start position:0% important for developers here and for 00:03:55.829 --> 00:03:58.280 align:start position:0% important for developers here and for this<00:03:55.980> talk<00:03:56.310> is<00:03:56.579> that<00:03:57.239> it's<00:03:57.569> compatible<00:03:57.959> with 00:03:58.280 --> 00:03:58.290 align:start position:0% this talk is that it's compatible with 00:03:58.290 --> 00:04:00.860 align:start position:0% this talk is that it's compatible with the<00:03:58.470> fabien<00:03:58.940> we<00:03:59.940> don't<00:04:00.209> want<00:04:00.389> to<00:04:00.480> make<00:04:00.690> you 00:04:00.860 --> 00:04:00.870 align:start position:0% the fabien we don't want to make you 00:04:00.870 --> 00:04:03.020 align:start position:0% the fabien we don't want to make you choose<00:04:01.139> between<00:04:01.500> aetherium<00:04:02.459> and<00:04:02.760> enigma 00:04:03.020 --> 00:04:03.030 align:start position:0% choose between aetherium and enigma 00:04:03.030 --> 00:04:06.050 align:start position:0% choose between aetherium and enigma there's<00:04:03.810> enough<00:04:04.139> of<00:04:04.410> you<00:04:04.799> know<00:04:05.060> copycat 00:04:06.050 --> 00:04:06.060 align:start position:0% there's enough of you know copycat 00:04:06.060 --> 00:04:08.300 align:start position:0% there's enough of you know copycat blockchains<00:04:06.599> in<00:04:06.750> the<00:04:06.870> space<00:04:07.139> what<00:04:07.859> we<00:04:08.040> want<00:04:08.220> to 00:04:08.300 --> 00:04:08.310 align:start position:0% blockchains in the space what we want to 00:04:08.310 --> 00:04:10.129 align:start position:0% blockchains in the space what we want to do<00:04:08.489> is<00:04:08.730> make<00:04:09.180> sure<00:04:09.209> you<00:04:09.450> can<00:04:09.630> build<00:04:09.870> the<00:04:09.959> best 00:04:10.129 --> 00:04:10.139 align:start position:0% do is make sure you can build the best 00:04:10.139 --> 00:04:11.960 align:start position:0% do is make sure you can build the best decentralized<00:04:10.829> applications<00:04:11.459> that<00:04:11.579> you<00:04:11.730> can 00:04:11.960 --> 00:04:11.970 align:start position:0% decentralized applications that you can 00:04:11.970 --> 00:04:14.990 align:start position:0% decentralized applications that you can so<00:04:12.630> we<00:04:12.870> build<00:04:13.139> a<00:04:13.260> very<00:04:13.440> seamless<00:04:13.829> bridge<00:04:14.400> and<00:04:14.880> I 00:04:14.990 --> 00:04:15.000 align:start position:0% so we build a very seamless bridge and I 00:04:15.000 --> 00:04:17.270 align:start position:0% so we build a very seamless bridge and I will<00:04:15.150> talk<00:04:15.299> about<00:04:15.359> it<00:04:15.750> later<00:04:15.989> on<00:04:16.070> about<00:04:17.070> how 00:04:17.270 --> 00:04:17.280 align:start position:0% will talk about it later on about how 00:04:17.280 --> 00:04:20.060 align:start position:0% will talk about it later on about how you<00:04:17.340> can<00:04:17.639> actually<00:04:18.150> combine<00:04:19.070> public 00:04:20.060 --> 00:04:20.070 align:start position:0% you can actually combine public 00:04:20.070 --> 00:04:22.810 align:start position:0% you can actually combine public execution<00:04:20.700> on<00:04:20.910> aetherium<00:04:21.479> with<00:04:22.019> private 00:04:22.810 --> 00:04:22.820 align:start position:0% execution on aetherium with private 00:04:22.820 --> 00:04:26.370 align:start position:0% execution on aetherium with private execution<00:04:23.820> or<00:04:23.969> enigma 00:04:26.370 --> 00:04:26.380 align:start position:0% execution or enigma 00:04:26.380 --> 00:04:32.790 align:start position:0% execution or enigma so<00:04:27.310> the<00:04:27.460> best<00:04:27.640> way<00:04:27.880> to<00:04:30.990> the<00:04:31.990> best<00:04:32.560> way<00:04:32.770> to 00:04:32.790 --> 00:04:32.800 align:start position:0% so the best way to the best way to 00:04:32.800 --> 00:04:34.920 align:start position:0% so the best way to the best way to explain<00:04:33.610> the<00:04:33.790> protocol<00:04:34.180> is<00:04:34.300> fer<00:04:34.450> to<00:04:34.570> discuss 00:04:34.920 --> 00:04:34.930 align:start position:0% explain the protocol is fer to discuss 00:04:34.930 --> 00:04:37.410 align:start position:0% explain the protocol is fer to discuss the<00:04:35.080> stakeholders<00:04:35.710> so<00:04:36.370> as<00:04:36.730> usual<00:04:37.180> we<00:04:37.390> have 00:04:37.410 --> 00:04:37.420 align:start position:0% the stakeholders so as usual we have 00:04:37.420 --> 00:04:39.990 align:start position:0% the stakeholders so as usual we have developers<00:04:38.080> that<00:04:38.320> write<00:04:38.500> code<00:04:38.800> we<00:04:39.400> have<00:04:39.520> users 00:04:39.990 --> 00:04:40.000 align:start position:0% developers that write code we have users 00:04:40.000 --> 00:04:41.610 align:start position:0% developers that write code we have users that<00:04:40.240> then<00:04:40.390> interact<00:04:40.960> with<00:04:41.080> these<00:04:41.260> secret 00:04:41.610 --> 00:04:41.620 align:start position:0% that then interact with these secret 00:04:41.620 --> 00:04:44.760 align:start position:0% that then interact with these secret contracts<00:04:42.220> with<00:04:42.340> that<00:04:42.490> code<00:04:42.790> and<00:04:43.110> we<00:04:44.110> wear 00:04:44.760 --> 00:04:44.770 align:start position:0% contracts with that code and we wear 00:04:44.770 --> 00:04:46.770 align:start position:0% contracts with that code and we wear things<00:04:44.980> kind<00:04:45.310> of<00:04:45.400> change<00:04:45.610> is<00:04:45.820> that<00:04:46.420> we<00:04:46.630> have 00:04:46.770 --> 00:04:46.780 align:start position:0% things kind of change is that we have 00:04:46.780 --> 00:04:49.350 align:start position:0% things kind of change is that we have workers<00:04:47.310> workers<00:04:48.310> are<00:04:48.430> basically<00:04:48.880> the<00:04:49.120> nodes 00:04:49.350 --> 00:04:49.360 align:start position:0% workers workers are basically the nodes 00:04:49.360 --> 00:04:51.210 align:start position:0% workers workers are basically the nodes in<00:04:49.540> our<00:04:49.630> network<00:04:50.020> that<00:04:50.560> are<00:04:50.680> running<00:04:50.920> and 00:04:51.210 --> 00:04:51.220 align:start position:0% in our network that are running and 00:04:51.220 --> 00:04:54.150 align:start position:0% in our network that are running and executing<00:04:51.820> secret<00:04:52.120> contracts<00:04:52.720> we<00:04:53.620> use<00:04:53.830> these 00:04:54.150 --> 00:04:54.160 align:start position:0% executing secret contracts we use these 00:04:54.160 --> 00:04:56.640 align:start position:0% executing secret contracts we use these definition<00:04:54.910> to<00:04:55.360> kind<00:04:55.570> of<00:04:55.660> separate<00:04:56.140> them<00:04:56.350> and 00:04:56.640 --> 00:04:56.650 align:start position:0% definition to kind of separate them and 00:04:56.650 --> 00:04:58.560 align:start position:0% definition to kind of separate them and not<00:04:56.830> to<00:04:56.950> confuse<00:04:57.310> them<00:04:57.640> with<00:04:57.850> the<00:04:58.210> theory<00:04:58.450> of 00:04:58.560 --> 00:04:58.570 align:start position:0% not to confuse them with the theory of 00:04:58.570 --> 00:05:02.150 align:start position:0% not to confuse them with the theory of nodes<00:04:58.840> and<00:04:59.080> miners<00:04:59.470> that<00:04:59.500> reach<00:04:59.920> consensus 00:05:02.150 --> 00:05:02.160 align:start position:0% nodes and miners that reach consensus 00:05:02.160 --> 00:05:06.780 align:start position:0% nodes and miners that reach consensus the<00:05:03.160> basic<00:05:03.520> architecture<00:05:04.170> is<00:05:05.170> as<00:05:05.350> follows<00:05:05.790> as 00:05:06.780 --> 00:05:06.790 align:start position:0% the basic architecture is as follows as 00:05:06.790 --> 00:05:09.360 align:start position:0% the basic architecture is as follows as I<00:05:07.000> said<00:05:07.470> developers<00:05:08.470> deploy<00:05:08.950> secret 00:05:09.360 --> 00:05:09.370 align:start position:0% I said developers deploy secret 00:05:09.370 --> 00:05:10.770 align:start position:0% I said developers deploy secret contracts<00:05:09.820> to<00:05:10.000> the<00:05:10.090> network 00:05:10.770 --> 00:05:10.780 align:start position:0% contracts to the network 00:05:10.780 --> 00:05:14.190 align:start position:0% contracts to the network there's<00:05:11.580> users<00:05:12.580> can<00:05:12.850> then<00:05:13.060> submit<00:05:13.510> tasks 00:05:14.190 --> 00:05:14.200 align:start position:0% there's users can then submit tasks 00:05:14.200 --> 00:05:16.380 align:start position:0% there's users can then submit tasks that's<00:05:14.440> the<00:05:14.740> equivalent<00:05:15.310> of<00:05:15.520> human 00:05:16.380 --> 00:05:16.390 align:start position:0% that's the equivalent of human 00:05:16.390 --> 00:05:19.380 align:start position:0% that's the equivalent of human transactions<00:05:17.130> and<00:05:18.130> that<00:05:18.160> basically<00:05:19.120> then 00:05:19.380 --> 00:05:19.390 align:start position:0% transactions and that basically then 00:05:19.390 --> 00:05:21.630 align:start position:0% transactions and that basically then gets<00:05:19.660> executed<00:05:20.050> on<00:05:20.470> the<00:05:20.500> Enigma<00:05:20.980> network<00:05:21.400> and 00:05:21.630 --> 00:05:21.640 align:start position:0% gets executed on the Enigma network and 00:05:21.640 --> 00:05:25.910 align:start position:0% gets executed on the Enigma network and final<00:05:22.600> consensus<00:05:23.170> is<00:05:23.350> reached<00:05:23.560> on<00:05:23.950> ethereum 00:05:25.910 --> 00:05:25.920 align:start position:0% final consensus is reached on ethereum 00:05:25.920 --> 00:05:29.130 align:start position:0% final consensus is reached on ethereum for<00:05:26.920> developers<00:05:27.490> we<00:05:28.210> support<00:05:28.570> two<00:05:28.750> modes<00:05:28.990> of 00:05:29.130 --> 00:05:29.140 align:start position:0% for developers we support two modes of 00:05:29.140 --> 00:05:31.260 align:start position:0% for developers we support two modes of execution<00:05:29.230> two<00:05:30.070> modes<00:05:30.280> of<00:05:30.400> sorry<00:05:30.820> of<00:05:30.940> writing 00:05:31.260 --> 00:05:31.270 align:start position:0% execution two modes of sorry of writing 00:05:31.270 --> 00:05:33.420 align:start position:0% execution two modes of sorry of writing contracts<00:05:31.750> you<00:05:32.380> can<00:05:32.410> use<00:05:32.680> solidity<00:05:33.130> which 00:05:33.420 --> 00:05:33.430 align:start position:0% contracts you can use solidity which 00:05:33.430 --> 00:05:37.530 align:start position:0% contracts you can use solidity which many<00:05:33.670> of<00:05:33.820> you<00:05:33.940> know<00:05:33.970> or<00:05:34.690> you<00:05:35.110> can<00:05:35.320> use<00:05:35.530> a<00:05:36.540> web 00:05:37.530 --> 00:05:37.540 align:start position:0% many of you know or you can use a web 00:05:37.540 --> 00:05:40.700 align:start position:0% many of you know or you can use a web assembly<00:05:38.080> enabled<00:05:38.500> language<00:05:38.980> primarily<00:05:39.850> rust 00:05:40.700 --> 00:05:40.710 align:start position:0% assembly enabled language primarily rust 00:05:40.710 --> 00:05:43.080 align:start position:0% assembly enabled language primarily rust we're<00:05:41.710> keeping<00:05:42.070> solidity<00:05:42.460> for<00:05:42.730> backwards 00:05:43.080 --> 00:05:43.090 align:start position:0% we're keeping solidity for backwards 00:05:43.090 --> 00:05:46.110 align:start position:0% we're keeping solidity for backwards compatibility<00:05:43.570> but<00:05:44.580> actually<00:05:45.580> Ross<00:05:45.820> and 00:05:46.110 --> 00:05:46.120 align:start position:0% compatibility but actually Ross and 00:05:46.120 --> 00:05:47.820 align:start position:0% compatibility but actually Ross and webassembly<00:05:46.480> have<00:05:46.870> a<00:05:46.900> lot<00:05:47.170> more<00:05:47.200> benefits 00:05:47.820 --> 00:05:47.830 align:start position:0% webassembly have a lot more benefits 00:05:47.830 --> 00:05:49.110 align:start position:0% webassembly have a lot more benefits we're<00:05:48.070> seeing<00:05:48.280> dangerously<00:05:48.730> go<00:05:48.850> in<00:05:48.970> that 00:05:49.110 --> 00:05:49.120 align:start position:0% we're seeing dangerously go in that 00:05:49.120 --> 00:05:52.080 align:start position:0% we're seeing dangerously go in that direction<00:05:49.270> and<00:05:49.960> so<00:05:50.770> if<00:05:51.190> you<00:05:51.400> really<00:05:51.760> want<00:05:51.940> to 00:05:52.080 --> 00:05:52.090 align:start position:0% direction and so if you really want to 00:05:52.090 --> 00:05:54.630 align:start position:0% direction and so if you really want to enjoy<00:05:52.360> all<00:05:52.660> of<00:05:52.690> the<00:05:52.840> benefits<00:05:53.050> and<00:05:53.770> scale<00:05:54.310> that 00:05:54.630 --> 00:05:54.640 align:start position:0% enjoy all of the benefits and scale that 00:05:54.640 --> 00:05:56.220 align:start position:0% enjoy all of the benefits and scale that the<00:05:55.060> system<00:05:55.360> can<00:05:55.540> provide<00:05:55.840> you<00:05:56.050> should 00:05:56.220 --> 00:05:56.230 align:start position:0% the system can provide you should 00:05:56.230 --> 00:06:00.330 align:start position:0% the system can provide you should probably<00:05:56.470> use<00:05:56.710> the<00:05:56.860> web<00:05:57.010> assembly<00:05:57.460> route<00:05:59.340> from 00:06:00.330 --> 00:06:00.340 align:start position:0% probably use the web assembly route from 00:06:00.340 --> 00:06:03.030 align:start position:0% probably use the web assembly route from a<00:06:00.520> user<00:06:00.700> perspective<00:06:01.140> once<00:06:02.140> a<00:06:02.320> secret 00:06:03.030 --> 00:06:03.040 align:start position:0% a user perspective once a secret 00:06:03.040 --> 00:06:05.310 align:start position:0% a user perspective once a secret contract<00:06:03.490> is<00:06:03.640> deployed<00:06:04.000> the<00:06:04.870> user<00:06:05.050> can 00:06:05.310 --> 00:06:05.320 align:start position:0% contract is deployed the user can 00:06:05.320 --> 00:06:06.990 align:start position:0% contract is deployed the user can interact<00:06:05.830> with<00:06:05.890> that<00:06:06.040> secret<00:06:06.340> contract<00:06:06.850> by 00:06:06.990 --> 00:06:07.000 align:start position:0% interact with that secret contract by 00:06:07.000 --> 00:06:09.570 align:start position:0% interact with that secret contract by submitting<00:06:07.390> tasks<00:06:07.990> which<00:06:08.500> are<00:06:08.650> again<00:06:08.950> they're 00:06:09.570 --> 00:06:09.580 align:start position:0% submitting tasks which are again they're 00:06:09.580 --> 00:06:11.730 align:start position:0% submitting tasks which are again they're the<00:06:09.610> equivalent<00:06:09.910> of<00:06:10.420> ephemeral<00:06:10.900> transactions 00:06:11.730 --> 00:06:11.740 align:start position:0% the equivalent of ephemeral transactions 00:06:11.740 --> 00:06:15.930 align:start position:0% the equivalent of ephemeral transactions the<00:06:12.400> main<00:06:12.670> difference<00:06:13.270> is<00:06:13.510> that<00:06:14.010> a<00:06:15.010> task<00:06:15.550> can 00:06:15.930 --> 00:06:15.940 align:start position:0% the main difference is that a task can 00:06:15.940 --> 00:06:18.270 align:start position:0% the main difference is that a task can include<00:06:16.300> encrypted<00:06:16.930> inputs<00:06:17.380> that<00:06:18.010> the<00:06:18.130> user 00:06:18.270 --> 00:06:18.280 align:start position:0% include encrypted inputs that the user 00:06:18.280 --> 00:06:22.110 align:start position:0% include encrypted inputs that the user supplies<00:06:20.340> under<00:06:21.340> the<00:06:21.460> hood<00:06:21.670> what<00:06:21.940> really 00:06:22.110 --> 00:06:22.120 align:start position:0% supplies under the hood what really 00:06:22.120 --> 00:06:25.740 align:start position:0% supplies under the hood what really happens<00:06:22.630> is<00:06:22.900> that<00:06:23.470> the<00:06:23.740> user<00:06:23.950> commits<00:06:24.700> a<00:06:25.270> proof 00:06:25.740 --> 00:06:25.750 align:start position:0% happens is that the user commits a proof 00:06:25.750 --> 00:06:29.640 align:start position:0% happens is that the user commits a proof of<00:06:25.960> the<00:06:26.050> transaction<00:06:26.680> of<00:06:27.220> the<00:06:28.150> task<00:06:28.440> on<00:06:29.440> the 00:06:29.640 --> 00:06:29.650 align:start position:0% of the transaction of the task on the 00:06:29.650 --> 00:06:31.830 align:start position:0% of the transaction of the task on the freemium<00:06:29.890> blockchain<00:06:30.430> that<00:06:31.120> actually<00:06:31.540> helps 00:06:31.830 --> 00:06:31.840 align:start position:0% freemium blockchain that actually helps 00:06:31.840 --> 00:06:34.230 align:start position:0% freemium blockchain that actually helps us<00:06:32.080> reach<00:06:32.410> consensus<00:06:33.130> on<00:06:33.280> the<00:06:33.490> ordering<00:06:34.060> of 00:06:34.230 --> 00:06:34.240 align:start position:0% us reach consensus on the ordering of 00:06:34.240 --> 00:06:36.240 align:start position:0% us reach consensus on the ordering of the<00:06:34.390> task<00:06:34.630> so<00:06:35.200> that<00:06:35.229> the<00:06:35.470> Enigma<00:06:35.770> network<00:06:36.070> does 00:06:36.240 --> 00:06:36.250 align:start position:0% the task so that the Enigma network does 00:06:36.250 --> 00:06:38.520 align:start position:0% the task so that the Enigma network does not<00:06:36.280> need<00:06:36.700> to<00:06:36.820> do<00:06:36.970> this<00:06:37.150> and<00:06:37.450> we<00:06:37.960> reuse<00:06:38.320> the 00:06:38.520 --> 00:06:38.530 align:start position:0% not need to do this and we reuse the 00:06:38.530 --> 00:06:39.780 align:start position:0% not need to do this and we reuse the trick<00:06:38.770> all<00:06:39.010> over<00:06:39.340> all 00:06:39.780 --> 00:06:39.790 align:start position:0% trick all over all 00:06:39.790 --> 00:06:41.130 align:start position:0% trick all over all over<00:06:39.910> the<00:06:40.030> place<00:06:40.240> whenever<00:06:40.780> there's 00:06:41.130 --> 00:06:41.140 align:start position:0% over the place whenever there's 00:06:41.140 --> 00:06:42.630 align:start position:0% over the place whenever there's something<00:06:41.170> small<00:06:41.770> that<00:06:41.890> we<00:06:42.010> need<00:06:42.160> agreement 00:06:42.630 --> 00:06:42.640 align:start position:0% something small that we need agreement 00:06:42.640 --> 00:06:45.120 align:start position:0% something small that we need agreement on<00:06:42.730> and<00:06:43.000> it's<00:06:43.450> not<00:06:43.600> a<00:06:43.630> heavy<00:06:43.840> computation<00:06:44.620> we 00:06:45.120 --> 00:06:45.130 align:start position:0% on and it's not a heavy computation we 00:06:45.130 --> 00:06:47.310 align:start position:0% on and it's not a heavy computation we do<00:06:45.250> dot<00:06:45.430> on<00:06:45.580> ethereum<00:06:45.840> but<00:06:46.840> the<00:06:46.960> actual 00:06:47.310 --> 00:06:47.320 align:start position:0% do dot on ethereum but the actual 00:06:47.320 --> 00:06:50.130 align:start position:0% do dot on ethereum but the actual execution<00:06:47.950> then<00:06:48.160> happens<00:06:48.580> on<00:06:48.850> enigma<00:06:49.450> which 00:06:50.130 --> 00:06:50.140 align:start position:0% execution then happens on enigma which 00:06:50.140 --> 00:06:53.910 align:start position:0% execution then happens on enigma which is<00:06:50.290> a<00:06:50.320> separate<00:06:50.770> network<00:06:52.230> the<00:06:53.230> way<00:06:53.380> that<00:06:53.620> works 00:06:53.910 --> 00:06:53.920 align:start position:0% is a separate network the way that works 00:06:53.920 --> 00:06:57.330 align:start position:0% is a separate network the way that works is<00:06:54.360> we<00:06:55.360> start<00:06:55.750> with<00:06:56.110> it<00:06:56.440> the<00:06:56.590> user<00:06:56.740> starts<00:06:57.070> with 00:06:57.330 --> 00:06:57.340 align:start position:0% is we start with it the user starts with 00:06:57.340 --> 00:06:58.740 align:start position:0% is we start with it the user starts with a<00:06:57.370> task<00:06:57.670> right 00:06:58.740 --> 00:06:58.750 align:start position:0% a task right 00:06:58.750 --> 00:07:00.870 align:start position:0% a task right he<00:06:59.140> sends<00:06:59.440> the<00:06:59.620> task<00:06:59.860> to<00:07:00.010> the<00:07:00.130> Enigma<00:07:00.490> network 00:07:00.870 --> 00:07:00.880 align:start position:0% he sends the task to the Enigma network 00:07:00.880 --> 00:07:03.930 align:start position:0% he sends the task to the Enigma network but<00:07:01.450> which<00:07:01.720> nodes<00:07:02.050> is<00:07:02.380> a<00:07:02.680> task<00:07:03.040> propagated<00:07:03.790> to 00:07:03.930 --> 00:07:03.940 align:start position:0% but which nodes is a task propagated to 00:07:03.940 --> 00:07:06.360 align:start position:0% but which nodes is a task propagated to we're<00:07:04.720> not<00:07:04.840> using<00:07:05.140> the<00:07:05.380> naive<00:07:05.650> approach<00:07:05.770> that 00:07:06.360 --> 00:07:06.370 align:start position:0% we're not using the naive approach that 00:07:06.370 --> 00:07:08.010 align:start position:0% we're not using the naive approach that current<00:07:06.730> blockchain<00:07:07.150> use<00:07:07.330> where<00:07:07.630> everyone 00:07:08.010 --> 00:07:08.020 align:start position:0% current blockchain use where everyone 00:07:08.020 --> 00:07:09.360 align:start position:0% current blockchain use where everyone computes<00:07:08.410> everything<00:07:08.860> that<00:07:09.190> is 00:07:09.360 --> 00:07:09.370 align:start position:0% computes everything that is 00:07:09.370 --> 00:07:12.240 align:start position:0% computes everything that is counterproductive<00:07:10.000> to<00:07:10.330> scalability<00:07:11.250> instead 00:07:12.240 --> 00:07:12.250 align:start position:0% counterproductive to scalability instead 00:07:12.250 --> 00:07:14.820 align:start position:0% counterproductive to scalability instead we<00:07:12.400> have<00:07:12.550> a<00:07:12.580> proof<00:07:12.820> of<00:07:12.940> state<00:07:13.210> model<00:07:13.690> where<00:07:14.590> we 00:07:14.820 --> 00:07:14.830 align:start position:0% we have a proof of state model where we 00:07:14.830 --> 00:07:17.640 align:start position:0% we have a proof of state model where we sample<00:07:15.430> a<00:07:15.520> group<00:07:15.790> a<00:07:16.120> group<00:07:16.900> of<00:07:17.080> workers<00:07:17.290> the 00:07:17.640 --> 00:07:17.650 align:start position:0% sample a group a group of workers the 00:07:17.650 --> 00:07:19.710 align:start position:0% sample a group a group of workers the constant<00:07:18.130> sized<00:07:18.370> group<00:07:18.670> of<00:07:18.790> workers<00:07:19.030> to 00:07:19.710 --> 00:07:19.720 align:start position:0% constant sized group of workers to 00:07:19.720 --> 00:07:22.650 align:start position:0% constant sized group of workers to actually<00:07:20.110> execute<00:07:20.590> that<00:07:20.950> task<00:07:21.220> and<00:07:21.520> those<00:07:22.270> and 00:07:22.650 --> 00:07:22.660 align:start position:0% actually execute that task and those and 00:07:22.660 --> 00:07:25.550 align:start position:0% actually execute that task and those and and<00:07:22.900> those<00:07:23.290> group<00:07:23.560> of<00:07:23.710> workers<00:07:24.100> are<00:07:24.550> always 00:07:25.550 --> 00:07:25.560 align:start position:0% and those group of workers are always 00:07:25.560 --> 00:07:28.110 align:start position:0% and those group of workers are always weighted<00:07:26.560> by<00:07:26.710> stake<00:07:27.070> which<00:07:27.610> means<00:07:27.880> that<00:07:28.000> if 00:07:28.110 --> 00:07:28.120 align:start position:0% weighted by stake which means that if 00:07:28.120 --> 00:07:29.970 align:start position:0% weighted by stake which means that if you<00:07:28.210> stake<00:07:28.480> more<00:07:28.690> tokens<00:07:29.170> you<00:07:29.680> are<00:07:29.800> more 00:07:29.970 --> 00:07:29.980 align:start position:0% you stake more tokens you are more 00:07:29.980 --> 00:07:32.400 align:start position:0% you stake more tokens you are more likely<00:07:30.310> to<00:07:30.430> get<00:07:30.580> selected<00:07:30.760> to<00:07:31.420> two<00:07:32.230> more 00:07:32.400 --> 00:07:32.410 align:start position:0% likely to get selected to two more 00:07:32.410 --> 00:07:34.230 align:start position:0% likely to get selected to two more computations<00:07:33.130> and<00:07:33.520> that<00:07:33.670> really<00:07:34.000> increases 00:07:34.230 --> 00:07:34.240 align:start position:0% computations and that really increases 00:07:34.240 --> 00:07:36.660 align:start position:0% computations and that really increases scale<00:07:34.810> that<00:07:35.320> gives<00:07:35.590> us<00:07:35.710> a<00:07:35.830> form<00:07:36.070> of<00:07:36.190> sharding 00:07:36.660 --> 00:07:36.670 align:start position:0% scale that gives us a form of sharding 00:07:36.670 --> 00:07:39.450 align:start position:0% scale that gives us a form of sharding that<00:07:37.330> is<00:07:37.480> fairly<00:07:38.140> simple<00:07:38.530> to<00:07:38.710> implement<00:07:38.950> and 00:07:39.450 --> 00:07:39.460 align:start position:0% that is fairly simple to implement and 00:07:39.460 --> 00:07:41.400 align:start position:0% that is fairly simple to implement and that<00:07:39.820> we're<00:07:40.300> gonna<00:07:40.480> have<00:07:40.690> up<00:07:40.870> and<00:07:41.020> running<00:07:41.080> in 00:07:41.400 --> 00:07:41.410 align:start position:0% that we're gonna have up and running in 00:07:41.410 --> 00:07:42.210 align:start position:0% that we're gonna have up and running in about<00:07:41.470> two<00:07:41.830> months 00:07:42.210 --> 00:07:42.220 align:start position:0% about two months 00:07:42.220 --> 00:07:46.230 align:start position:0% about two months and<00:07:43.290> then<00:07:44.290> that<00:07:44.530> quorum<00:07:45.460> these<00:07:45.640> Committees<00:07:46.210> of 00:07:46.230 --> 00:07:46.240 align:start position:0% and then that quorum these Committees of 00:07:46.240 --> 00:07:48.120 align:start position:0% and then that quorum these Committees of workers<00:07:46.780> they<00:07:47.320> actually<00:07:47.740> run<00:07:47.920> these 00:07:48.120 --> 00:07:48.130 align:start position:0% workers they actually run these 00:07:48.130 --> 00:07:51.450 align:start position:0% workers they actually run these computations<00:07:48.970> and<00:07:49.680> at<00:07:50.680> the<00:07:50.920> end<00:07:51.040> of<00:07:51.190> an<00:07:51.310> epoch 00:07:51.450 --> 00:07:51.460 align:start position:0% computations and at the end of an epoch 00:07:51.460 --> 00:07:54.630 align:start position:0% computations and at the end of an epoch so<00:07:52.330> for<00:07:53.200> performance<00:07:53.650> reasons<00:07:53.680> it's<00:07:54.220> not<00:07:54.430> just 00:07:54.630 --> 00:07:54.640 align:start position:0% so for performance reasons it's not just 00:07:54.640 --> 00:07:56.190 align:start position:0% so for performance reasons it's not just one<00:07:54.820> computation<00:07:55.180> that<00:07:55.510> is<00:07:55.690> each<00:07:55.840> group<00:07:56.080> is 00:07:56.190 --> 00:07:56.200 align:start position:0% one computation that is each group is 00:07:56.200 --> 00:07:58.080 align:start position:0% one computation that is each group is assigned<00:07:56.230> to<00:07:56.590> it's<00:07:57.160> actually<00:07:57.610> a<00:07:57.640> group<00:07:57.940> of 00:07:58.080 --> 00:07:58.090 align:start position:0% assigned to it's actually a group of 00:07:58.090 --> 00:08:01.080 align:start position:0% assigned to it's actually a group of computations<00:07:58.870> that<00:07:59.320> are<00:07:59.680> bounded<00:08:00.280> by<00:08:00.460> time<00:08:00.760> in 00:08:01.080 --> 00:08:01.090 align:start position:0% computations that are bounded by time in 00:08:01.090 --> 00:08:03.270 align:start position:0% computations that are bounded by time in an<00:08:01.210> epoch<00:08:01.360> and<00:08:01.840> at<00:08:02.170> the<00:08:02.290> end<00:08:02.410> of<00:08:02.560> the<00:08:02.650> epoch<00:08:03.010> the 00:08:03.270 --> 00:08:03.280 align:start position:0% an epoch and at the end of the epoch the 00:08:03.280 --> 00:08:05.880 align:start position:0% an epoch and at the end of the epoch the workers<00:08:04.120> submit<00:08:04.990> the<00:08:05.110> results<00:08:05.530> back<00:08:05.680> to 00:08:05.880 --> 00:08:05.890 align:start position:0% workers submit the results back to 00:08:05.890 --> 00:08:08.340 align:start position:0% workers submit the results back to Ephesian<00:08:06.400> a<00:08:06.610> theorem<00:08:07.300> only<00:08:07.480> does<00:08:07.780> very<00:08:08.020> small 00:08:08.340 --> 00:08:08.350 align:start position:0% Ephesian a theorem only does very small 00:08:08.350 --> 00:08:10.260 align:start position:0% Ephesian a theorem only does very small verification<00:08:09.100> making<00:08:09.490> sure<00:08:09.610> all<00:08:09.790> the<00:08:10.030> state 00:08:10.260 --> 00:08:10.270 align:start position:0% verification making sure all the state 00:08:10.270 --> 00:08:12.540 align:start position:0% verification making sure all the state changes<00:08:10.750> are<00:08:10.870> correct<00:08:11.230> and<00:08:11.530> if<00:08:12.130> that's<00:08:12.370> the 00:08:12.540 --> 00:08:12.550 align:start position:0% changes are correct and if that's the 00:08:12.550 --> 00:08:15.870 align:start position:0% changes are correct and if that's the case<00:08:12.730> the<00:08:13.180> workers<00:08:13.750> get<00:08:14.130> incentivized<00:08:15.130> if<00:08:15.430> not 00:08:15.870 --> 00:08:15.880 align:start position:0% case the workers get incentivized if not 00:08:15.880 --> 00:08:21.660 align:start position:0% case the workers get incentivized if not they<00:08:16.060> get<00:08:16.270> penalized<00:08:16.810> and<00:08:16.990> slashed<00:08:20.550> so<00:08:21.550> I'm 00:08:21.660 --> 00:08:21.670 align:start position:0% they get penalized and slashed so I'm 00:08:21.670 --> 00:08:23.580 align:start position:0% they get penalized and slashed so I'm gonna<00:08:21.850> I'm<00:08:22.120> gonna<00:08:22.300> go<00:08:22.510> a<00:08:22.540> bit<00:08:22.840> deeper<00:08:22.870> about 00:08:23.580 --> 00:08:23.590 align:start position:0% gonna I'm gonna go a bit deeper about 00:08:23.590 --> 00:08:25.770 align:start position:0% gonna I'm gonna go a bit deeper about the<00:08:23.830> what<00:08:24.580> a<00:08:24.610> secret<00:08:25.000> contract<00:08:25.390> execution 00:08:25.770 --> 00:08:25.780 align:start position:0% the what a secret contract execution 00:08:25.780 --> 00:08:27.990 align:start position:0% the what a secret contract execution looks<00:08:26.110> like<00:08:26.320> internally<00:08:26.860> what's<00:08:27.490> important 00:08:27.990 --> 00:08:28.000 align:start position:0% looks like internally what's important 00:08:28.000 --> 00:08:31.290 align:start position:0% looks like internally what's important to<00:08:28.090> understand<00:08:28.630> here<00:08:28.870> is<00:08:29.050> that<00:08:29.800> each<00:08:30.760> secret 00:08:31.290 --> 00:08:31.300 align:start position:0% to understand here is that each secret 00:08:31.300 --> 00:08:33.719 align:start position:0% to understand here is that each secret contract<00:08:31.870> has<00:08:32.229> an<00:08:32.380> encrypted<00:08:32.740> state<00:08:33.130> that's 00:08:33.719 --> 00:08:33.729 align:start position:0% contract has an encrypted state that's 00:08:33.729 --> 00:08:36.060 align:start position:0% contract has an encrypted state that's like<00:08:33.940> a<00:08:33.970> that's<00:08:34.270> like<00:08:34.450> an<00:08:34.570> ethereal<00:08:34.840> State<00:08:35.380> for 00:08:36.060 --> 00:08:36.070 align:start position:0% like a that's like an ethereal State for 00:08:36.070 --> 00:08:38.010 align:start position:0% like a that's like an ethereal State for contracts<00:08:36.550> but<00:08:37.210> the<00:08:37.300> difference<00:08:37.720> is<00:08:37.840> that 00:08:38.010 --> 00:08:38.020 align:start position:0% contracts but the difference is that 00:08:38.020 --> 00:08:40.469 align:start position:0% contracts but the difference is that this<00:08:38.290> is<00:08:38.349> enter<00:08:38.800> and<00:08:38.950> enter<00:08:39.580> an<00:08:40.090> encrypted 00:08:40.469 --> 00:08:40.479 align:start position:0% this is enter and enter an encrypted 00:08:40.479 --> 00:08:44.159 align:start position:0% this is enter and enter an encrypted when<00:08:41.260> a<00:08:41.290> computation<00:08:42.099> comes<00:08:42.400> in<00:08:42.700> then<00:08:43.690> the<00:08:43.870> the 00:08:44.159 --> 00:08:44.169 align:start position:0% when a computation comes in then the the 00:08:44.169 --> 00:08:45.900 align:start position:0% when a computation comes in then the the current<00:08:44.530> encrypted<00:08:45.040> States<00:08:45.280> goes<00:08:45.610> in 00:08:45.900 --> 00:08:45.910 align:start position:0% current encrypted States goes in 00:08:45.910 --> 00:08:48.330 align:start position:0% current encrypted States goes in basically<00:08:46.690> lives<00:08:46.930> in<00:08:47.050> the<00:08:47.140> network<00:08:47.530> and<00:08:47.740> the 00:08:48.330 --> 00:08:48.340 align:start position:0% basically lives in the network and the 00:08:48.340 --> 00:08:50.430 align:start position:0% basically lives in the network and the workers<00:08:48.970> that<00:08:49.000> are<00:08:49.210> running<00:08:49.630> the<00:08:49.840> execution 00:08:50.430 --> 00:08:50.440 align:start position:0% workers that are running the execution 00:08:50.440 --> 00:08:52.530 align:start position:0% workers that are running the execution they<00:08:50.590> can<00:08:50.800> update<00:08:51.010> the<00:08:51.340> state<00:08:51.580> however<00:08:52.330> they 00:08:52.530 --> 00:08:52.540 align:start position:0% they can update the state however they 00:08:52.540 --> 00:08:53.519 align:start position:0% they can update the state however they see<00:08:52.720> feed<00:08:52.960> based<00:08:53.200> on<00:08:53.380> the 00:08:53.519 --> 00:08:53.529 align:start position:0% see feed based on the 00:08:53.529 --> 00:08:55.590 align:start position:0% see feed based on the computation<00:08:54.069> of<00:08:54.160> course<00:08:54.430> and<00:08:54.639> then<00:08:55.209> they<00:08:55.360> can 00:08:55.590 --> 00:08:55.600 align:start position:0% computation of course and then they can 00:08:55.600 --> 00:08:58.199 align:start position:0% computation of course and then they can spit<00:08:55.990> out<00:08:56.019> a<00:08:56.439> new<00:08:57.009> modified<00:08:57.399> updated 00:08:58.199 --> 00:08:58.209 align:start position:0% spit out a new modified updated 00:08:58.209 --> 00:09:01.559 align:start position:0% spit out a new modified updated encrypted<00:08:58.749> state<00:08:59.579> in<00:09:00.579> addition<00:09:00.730> users<00:09:01.389> can 00:09:01.559 --> 00:09:01.569 align:start position:0% encrypted state in addition users can 00:09:01.569 --> 00:09:05.189 align:start position:0% encrypted state in addition users can supply<00:09:01.959> encrypted<00:09:02.680> inputs<00:09:03.660> users<00:09:04.660> can<00:09:04.899> supply 00:09:05.189 --> 00:09:05.199 align:start position:0% supply encrypted inputs users can supply 00:09:05.199 --> 00:09:07.559 align:start position:0% supply encrypted inputs users can supply encrypted<00:09:05.589> inputs<00:09:05.980> and<00:09:06.249> then<00:09:06.790> get<00:09:07.029> encrypted 00:09:07.559 --> 00:09:07.569 align:start position:0% encrypted inputs and then get encrypted 00:09:07.569 --> 00:09:09.540 align:start position:0% encrypted inputs and then get encrypted outputs<00:09:08.050> that<00:09:08.680> are<00:09:08.740> only<00:09:09.009> selectively 00:09:09.540 --> 00:09:09.550 align:start position:0% outputs that are only selectively 00:09:09.550 --> 00:09:12.509 align:start position:0% outputs that are only selectively revealed<00:09:09.970> to<00:09:10.089> them<00:09:11.220> now<00:09:12.220> what's<00:09:12.370> really 00:09:12.509 --> 00:09:12.519 align:start position:0% revealed to them now what's really 00:09:12.519 --> 00:09:14.489 align:start position:0% revealed to them now what's really important<00:09:13.029> in<00:09:13.149> this<00:09:13.300> slide<00:09:13.569> is<00:09:13.870> how<00:09:14.139> we<00:09:14.199> preach 00:09:14.489 --> 00:09:14.499 align:start position:0% important in this slide is how we preach 00:09:14.499 --> 00:09:17.280 align:start position:0% important in this slide is how we preach to<00:09:14.680> a<00:09:14.740> theorem<00:09:15.189> we<00:09:15.879> have<00:09:15.999> a<00:09:16.029> third<00:09:16.420> type<00:09:17.050> of 00:09:17.280 --> 00:09:17.290 align:start position:0% to a theorem we have a third type of 00:09:17.290 --> 00:09:20.150 align:start position:0% to a theorem we have a third type of output<00:09:17.759> which<00:09:18.759> is<00:09:18.790> the<00:09:19.180> etherium<00:09:19.600> callback 00:09:20.150 --> 00:09:20.160 align:start position:0% output which is the etherium callback 00:09:20.160 --> 00:09:23.239 align:start position:0% output which is the etherium callback basically<00:09:21.160> if<00:09:21.399> you're<00:09:21.730> a<00:09:21.759> secret<00:09:22.059> developer 00:09:23.239 --> 00:09:23.249 align:start position:0% basically if you're a secret developer 00:09:23.249 --> 00:09:25.499 align:start position:0% basically if you're a secret developer if<00:09:24.249> you're<00:09:24.490> if<00:09:24.670> you're<00:09:24.699> a<00:09:24.850> secret<00:09:25.149> contract 00:09:25.499 --> 00:09:25.509 align:start position:0% if you're if you're a secret contract 00:09:25.509 --> 00:09:27.900 align:start position:0% if you're if you're a secret contract developer<00:09:25.959> you<00:09:26.589> can<00:09:26.620> enter<00:09:27.069> it<00:09:27.220> a<00:09:27.249> special 00:09:27.900 --> 00:09:27.910 align:start position:0% developer you can enter it a special 00:09:27.910 --> 00:09:30.509 align:start position:0% developer you can enter it a special return<00:09:28.240> statement<00:09:28.870> that<00:09:29.050> returns<00:09:29.589> statement 00:09:30.509 --> 00:09:30.519 align:start position:0% return statement that returns statement 00:09:30.519 --> 00:09:34.079 align:start position:0% return statement that returns statement can<00:09:31.149> can<00:09:31.540> take<00:09:31.809> the<00:09:32.470> output<00:09:33.009> of<00:09:33.220> the<00:09:33.730> secret 00:09:34.079 --> 00:09:34.089 align:start position:0% can can take the output of the secret 00:09:34.089 --> 00:09:36.590 align:start position:0% can can take the output of the secret contract<00:09:34.600> that<00:09:34.749> just<00:09:35.170> executed<00:09:35.769> an<00:09:36.040> enigma 00:09:36.590 --> 00:09:36.600 align:start position:0% contract that just executed an enigma 00:09:36.600 --> 00:09:40.829 align:start position:0% contract that just executed an enigma call<00:09:37.600> another<00:09:38.439> smart<00:09:39.279> contract<00:09:39.910> on<00:09:40.089> etherium 00:09:40.829 --> 00:09:40.839 align:start position:0% call another smart contract on etherium 00:09:40.839 --> 00:09:45.030 align:start position:0% call another smart contract on etherium with<00:09:41.709> the<00:09:42.540> with<00:09:43.540> the<00:09:43.720> output<00:09:44.319> from<00:09:44.439> enigma<00:09:44.889> as 00:09:45.030 --> 00:09:45.040 align:start position:0% with the with the output from enigma as 00:09:45.040 --> 00:09:46.980 align:start position:0% with the with the output from enigma as an<00:09:45.249> input<00:09:45.579> to<00:09:45.670> that<00:09:45.850> to<00:09:46.120> that<00:09:46.149> smart<00:09:46.540> contract 00:09:46.980 --> 00:09:46.990 align:start position:0% an input to that to that smart contract 00:09:46.990 --> 00:09:49.860 align:start position:0% an input to that to that smart contract that<00:09:47.559> completes<00:09:48.189> the<00:09:48.339> full<00:09:48.519> cycle<00:09:48.790> so<00:09:49.629> if<00:09:49.720> to 00:09:49.860 --> 00:09:49.870 align:start position:0% that completes the full cycle so if to 00:09:49.870 --> 00:09:51.960 align:start position:0% that completes the full cycle so if to give<00:09:50.019> you<00:09:50.139> a<00:09:50.170> concrete<00:09:50.350> example<00:09:50.589> if<00:09:51.339> you<00:09:51.850> have 00:09:51.960 --> 00:09:51.970 align:start position:0% give you a concrete example if you have 00:09:51.970 --> 00:09:54.780 align:start position:0% give you a concrete example if you have a<00:09:51.999> voting<00:09:52.569> smart<00:09:53.410> contract<00:09:53.949> we<00:09:54.220> do<00:09:54.399> know<00:09:54.610> how 00:09:54.780 --> 00:09:54.790 align:start position:0% a voting smart contract we do know how 00:09:54.790 --> 00:09:56.519 align:start position:0% a voting smart contract we do know how private<00:09:55.089> voting<00:09:55.600> how<00:09:55.779> hard<00:09:56.050> it<00:09:56.199> is<00:09:56.259> to<00:09:56.439> achieve 00:09:56.519 --> 00:09:56.529 align:start position:0% private voting how hard it is to achieve 00:09:56.529 --> 00:09:59.280 align:start position:0% private voting how hard it is to achieve that<00:09:56.920> in<00:09:57.189> a<00:09:57.550> good<00:09:57.759> way<00:09:57.970> on<00:09:58.120> the<00:09:58.209> theorem<00:09:58.629> so 00:09:59.280 --> 00:09:59.290 align:start position:0% that in a good way on the theorem so 00:09:59.290 --> 00:10:01.559 align:start position:0% that in a good way on the theorem so what<00:09:59.500> you<00:09:59.649> can<00:09:59.860> do<00:10:00.040> you<00:10:00.610> can<00:10:00.819> have<00:10:00.970> the<00:10:01.120> private 00:10:01.559 --> 00:10:01.569 align:start position:0% what you can do you can have the private 00:10:01.569 --> 00:10:04.799 align:start position:0% what you can do you can have the private voting<00:10:01.959> happen<00:10:02.290> on<00:10:02.470> enigma<00:10:03.040> an<00:10:03.699> enigma<00:10:04.420> users 00:10:04.799 --> 00:10:04.809 align:start position:0% voting happen on enigma an enigma users 00:10:04.809 --> 00:10:07.319 align:start position:0% voting happen on enigma an enigma users can<00:10:05.050> supply<00:10:05.439> their<00:10:05.649> encrypted<00:10:06.189> votes<00:10:06.459> the 00:10:07.319 --> 00:10:07.329 align:start position:0% can supply their encrypted votes the 00:10:07.329 --> 00:10:09.869 align:start position:0% can supply their encrypted votes the actual<00:10:07.779> tally<00:10:08.139> function<00:10:08.740> runs<00:10:09.160> on<00:10:09.430> enigma 00:10:09.869 --> 00:10:09.879 align:start position:0% actual tally function runs on enigma 00:10:09.879 --> 00:10:12.600 align:start position:0% actual tally function runs on enigma workers<00:10:10.360> and<00:10:10.600> then<00:10:11.379> at<00:10:11.529> the<00:10:11.649> end<00:10:11.800> of<00:10:11.949> that<00:10:12.100> you 00:10:12.600 --> 00:10:12.610 align:start position:0% workers and then at the end of that you 00:10:12.610 --> 00:10:15.150 align:start position:0% workers and then at the end of that you can<00:10:12.819> commit<00:10:13.209> that<00:10:13.389> result<00:10:13.839> back<00:10:14.379> to<00:10:14.410> smart<00:10:15.040> as 00:10:15.150 --> 00:10:15.160 align:start position:0% can commit that result back to smart as 00:10:15.160 --> 00:10:17.429 align:start position:0% can commit that result back to smart as input<00:10:15.759> to<00:10:15.910> another<00:10:15.939> smart<00:10:16.660> contract<00:10:17.259> in 00:10:17.429 --> 00:10:17.439 align:start position:0% input to another smart contract in 00:10:17.439 --> 00:10:19.920 align:start position:0% input to another smart contract in aetherium<00:10:18.339> that<00:10:18.910> can<00:10:19.089> do<00:10:19.209> whatever<00:10:19.389> business 00:10:19.920 --> 00:10:19.930 align:start position:0% aetherium that can do whatever business 00:10:19.930 --> 00:10:24.559 align:start position:0% aetherium that can do whatever business logic<00:10:20.139> with<00:10:20.529> those<00:10:20.680> results<00:10:21.189> that<00:10:21.250> it<00:10:21.430> wants 00:10:24.559 --> 00:10:24.569 align:start position:0% 00:10:24.569 --> 00:10:28.889 align:start position:0% all<00:10:25.569> right<00:10:26.279> let's<00:10:27.279> switch<00:10:27.759> gears<00:10:27.790> a<00:10:28.059> bit<00:10:28.149> so 00:10:28.889 --> 00:10:28.899 align:start position:0% all right let's switch gears a bit so 00:10:28.899 --> 00:10:31.319 align:start position:0% all right let's switch gears a bit so far<00:10:29.110> I<00:10:29.170> told<00:10:29.470> you<00:10:29.649> a<00:10:29.709> lot<00:10:29.949> about<00:10:29.980> how<00:10:30.879> enigma 00:10:31.319 --> 00:10:31.329 align:start position:0% far I told you a lot about how enigma 00:10:31.329 --> 00:10:33.420 align:start position:0% far I told you a lot about how enigma architecture<00:10:31.839> works<00:10:32.079> and<00:10:32.379> that<00:10:33.129> we<00:10:33.279> have 00:10:33.420 --> 00:10:33.430 align:start position:0% architecture works and that we have 00:10:33.430 --> 00:10:35.999 align:start position:0% architecture works and that we have encrypted<00:10:33.759> computation<00:10:34.569> but<00:10:35.170> I<00:10:35.199> was<00:10:35.709> kind<00:10:35.949> of 00:10:35.999 --> 00:10:36.009 align:start position:0% encrypted computation but I was kind of 00:10:36.009 --> 00:10:36.569 align:start position:0% encrypted computation but I was kind of hand-wavy 00:10:36.569 --> 00:10:36.579 align:start position:0% hand-wavy 00:10:36.579 --> 00:10:38.400 align:start position:0% hand-wavy right<00:10:36.939> let<00:10:37.179> me<00:10:37.209> explain<00:10:37.300> to<00:10:37.809> you<00:10:37.870> how<00:10:38.139> we 00:10:38.400 --> 00:10:38.410 align:start position:0% right let me explain to you how we 00:10:38.410 --> 00:10:40.169 align:start position:0% right let me explain to you how we actually<00:10:38.649> protect<00:10:39.129> privacy<00:10:39.519> in<00:10:39.699> the<00:10:39.819> network 00:10:40.169 --> 00:10:40.179 align:start position:0% actually protect privacy in the network 00:10:40.179 --> 00:10:43.169 align:start position:0% actually protect privacy in the network so<00:10:40.990> for<00:10:41.199> discovery<00:10:41.709> right<00:10:41.980> now<00:10:42.189> we're<00:10:42.939> user 00:10:43.169 --> 00:10:43.179 align:start position:0% so for discovery right now we're user 00:10:43.179 --> 00:10:45.689 align:start position:0% so for discovery right now we're user entrusted<00:10:43.870> execution<00:10:44.410> environments<00:10:45.100> or<00:10:45.309> T's 00:10:45.689 --> 00:10:45.699 align:start position:0% entrusted execution environments or T's 00:10:45.699 --> 00:10:48.419 align:start position:0% entrusted execution environments or T's to<00:10:46.569> actually<00:10:47.019> achieve<00:10:47.649> these<00:10:47.920> privacy 00:10:48.419 --> 00:10:48.429 align:start position:0% to actually achieve these privacy 00:10:48.429 --> 00:10:51.540 align:start position:0% to actually achieve these privacy guarantees<00:10:48.850> these<00:10:49.749> are<00:10:50.079> basically<00:10:50.529> a<00:10:50.949> secure 00:10:51.540 --> 00:10:51.550 align:start position:0% guarantees these are basically a secure 00:10:51.550 --> 00:10:53.970 align:start position:0% guarantees these are basically a secure region<00:10:51.879> in<00:10:51.970> the<00:10:52.089> processor<00:10:52.660> that<00:10:53.410> can<00:10:53.709> hide 00:10:53.970 --> 00:10:53.980 align:start position:0% region in the processor that can hide 00:10:53.980 --> 00:10:56.759 align:start position:0% region in the processor that can hide any<00:10:54.490> data<00:10:54.939> and<00:10:55.540> anything<00:10:55.959> that<00:10:55.990> goes<00:10:56.290> inside 00:10:56.759 --> 00:10:56.769 align:start position:0% any data and anything that goes inside 00:10:56.769 --> 00:10:59.939 align:start position:0% any data and anything that goes inside of<00:10:57.069> a<00:10:57.129> computation<00:10:57.819> from<00:10:58.749> even<00:10:59.110> the<00:10:59.259> host<00:10:59.470> so<00:10:59.920> a 00:10:59.939 --> 00:10:59.949 align:start position:0% of a computation from even the host so a 00:10:59.949 --> 00:11:02.069 align:start position:0% of a computation from even the host so a malicious<00:11:00.399> Souls<00:11:00.610> cannot<00:11:01.389> see<00:11:01.660> what<00:11:01.899> they're 00:11:02.069 --> 00:11:02.079 align:start position:0% malicious Souls cannot see what they're 00:11:02.079 --> 00:11:04.710 align:start position:0% malicious Souls cannot see what they're computing<00:11:02.589> over<00:11:02.879> it<00:11:03.879> gives<00:11:04.179> us<00:11:04.420> great 00:11:04.710 --> 00:11:04.720 align:start position:0% computing over it gives us great 00:11:04.720 --> 00:11:07.260 align:start position:0% computing over it gives us great scalability<00:11:05.559> guarantees<00:11:05.949> it<00:11:06.250> gives<00:11:06.550> us 00:11:07.260 --> 00:11:07.270 align:start position:0% scalability guarantees it gives us 00:11:07.270 --> 00:11:10.740 align:start position:0% scalability guarantees it gives us strong<00:11:07.540> privacy<00:11:08.110> guarantees<00:11:09.630> but<00:11:10.630> we're 00:11:10.740 --> 00:11:10.750 align:start position:0% strong privacy guarantees but we're 00:11:10.750 --> 00:11:12.120 align:start position:0% strong privacy guarantees but we're actually<00:11:10.900> thinking<00:11:11.230> about<00:11:11.590> how<00:11:11.740> we<00:11:11.800> can<00:11:11.980> do 00:11:12.120 --> 00:11:12.130 align:start position:0% actually thinking about how we can do 00:11:12.130 --> 00:11:14.220 align:start position:0% actually thinking about how we can do better<00:11:12.310> there<00:11:13.210> are<00:11:13.240> other<00:11:13.600> privacy 00:11:14.220 --> 00:11:14.230 align:start position:0% better there are other privacy 00:11:14.230 --> 00:11:16.320 align:start position:0% better there are other privacy preserving<00:11:14.610> technologies<00:11:15.610> that<00:11:16.180> are 00:11:16.320 --> 00:11:16.330 align:start position:0% preserving technologies that are 00:11:16.330 --> 00:11:18.060 align:start position:0% preserving technologies that are available<00:11:16.540> today<00:11:16.960> that<00:11:17.320> are<00:11:17.770> purely 00:11:18.060 --> 00:11:18.070 align:start position:0% available today that are purely 00:11:18.070 --> 00:11:20.520 align:start position:0% available today that are purely cryptographic<00:11:18.780> this<00:11:19.780> is<00:11:19.900> actually<00:11:20.290> a<00:11:20.320> good 00:11:20.520 --> 00:11:20.530 align:start position:0% cryptographic this is actually a good 00:11:20.530 --> 00:11:22.590 align:start position:0% cryptographic this is actually a good time<00:11:20.770> to<00:11:20.950> say<00:11:21.160> that<00:11:21.370> when<00:11:21.520> enigma<00:11:21.910> started<00:11:22.330> and 00:11:22.590 --> 00:11:22.600 align:start position:0% time to say that when enigma started and 00:11:22.600 --> 00:11:26.280 align:start position:0% time to say that when enigma started and I<00:11:23.020> was<00:11:23.200> a<00:11:23.230> student<00:11:23.530> at<00:11:23.740> MIT<00:11:24.040> my<00:11:25.000> teasease<00:11:25.600> was 00:11:26.280 --> 00:11:26.290 align:start position:0% I was a student at MIT my teasease was 00:11:26.290 --> 00:11:28.380 align:start position:0% I was a student at MIT my teasease was on<00:11:26.440> how<00:11:26.590> we<00:11:26.650> can<00:11:26.920> achieve<00:11:27.240> privacy<00:11:28.240> preserving 00:11:28.380 --> 00:11:28.390 align:start position:0% on how we can achieve privacy preserving 00:11:28.390 --> 00:11:31.080 align:start position:0% on how we can achieve privacy preserving smart<00:11:28.870> contracts<00:11:29.530> using<00:11:30.010> secure<00:11:30.760> multi-party 00:11:31.080 --> 00:11:31.090 align:start position:0% smart contracts using secure multi-party 00:11:31.090 --> 00:11:34.470 align:start position:0% smart contracts using secure multi-party computation<00:11:31.720> or<00:11:32.410> MPC<00:11:33.280> which<00:11:33.820> is<00:11:34.000> one<00:11:34.210> of<00:11:34.360> these 00:11:34.470 --> 00:11:34.480 align:start position:0% computation or MPC which is one of these 00:11:34.480 --> 00:11:39.120 align:start position:0% computation or MPC which is one of these techniques<00:11:35.220> MPC<00:11:36.220> is<00:11:36.720> a<00:11:37.720> distant<00:11:38.470> cousin<00:11:38.680> to<00:11:39.100> a 00:11:39.120 --> 00:11:39.130 align:start position:0% techniques MPC is a distant cousin to a 00:11:39.130 --> 00:11:41.280 align:start position:0% techniques MPC is a distant cousin to a fully<00:11:39.400> homomorphic<00:11:39.580> encryption<00:11:40.020> they<00:11:41.020> both 00:11:41.280 --> 00:11:41.290 align:start position:0% fully homomorphic encryption they both 00:11:41.290 --> 00:11:43.530 align:start position:0% fully homomorphic encryption they both try<00:11:41.590> to<00:11:41.620> achieve<00:11:41.860> the<00:11:42.430> the<00:11:42.670> goal<00:11:42.880> of<00:11:43.030> computer 00:11:43.530 --> 00:11:43.540 align:start position:0% try to achieve the the goal of computer 00:11:43.540 --> 00:11:46.170 align:start position:0% try to achieve the the goal of computer over<00:11:43.750> encrypted<00:11:44.200> data<00:11:44.410> but<00:11:45.280> because<00:11:45.640> NPCs 00:11:46.170 --> 00:11:46.180 align:start position:0% over encrypted data but because NPCs 00:11:46.180 --> 00:11:48.090 align:start position:0% over encrypted data but because NPCs steal<00:11:46.600> orders<00:11:46.960> of<00:11:47.080> magnitudes<00:11:47.590> more<00:11:47.770> scalable 00:11:48.090 --> 00:11:48.100 align:start position:0% steal orders of magnitudes more scalable 00:11:48.100 --> 00:11:52.710 align:start position:0% steal orders of magnitudes more scalable we<00:11:49.060> are<00:11:49.180> focusing<00:11:49.660> on<00:11:49.780> developing<00:11:50.230> that<00:11:51.720> one 00:11:52.710 --> 00:11:52.720 align:start position:0% we are focusing on developing that one 00:11:52.720 --> 00:11:55.620 align:start position:0% we are focusing on developing that one one<00:11:53.140> final<00:11:53.560> note<00:11:53.800> on<00:11:54.130> zk<00:11:54.640> snarks<00:11:55.090> and<00:11:55.180> Starks 00:11:55.620 --> 00:11:55.630 align:start position:0% one final note on zk snarks and Starks 00:11:55.630 --> 00:11:58.650 align:start position:0% one final note on zk snarks and Starks there's<00:11:55.930> there's<00:11:56.530> a<00:11:56.590> a<00:11:57.190> big<00:11:57.760> misconception 00:11:58.650 --> 00:11:58.660 align:start position:0% there's there's a a big misconception 00:11:58.660 --> 00:12:00.660 align:start position:0% there's there's a a big misconception about<00:11:58.780> these<00:11:59.050> technologies<00:11:59.550> they're<00:12:00.550> an 00:12:00.660 --> 00:12:00.670 align:start position:0% about these technologies they're an 00:12:00.670 --> 00:12:02.690 align:start position:0% about these technologies they're an amazing<00:12:01.120> technology<00:12:01.420> but<00:12:01.870> at<00:12:01.960> the<00:12:02.080> same<00:12:02.350> time 00:12:02.690 --> 00:12:02.700 align:start position:0% amazing technology but at the same time 00:12:02.700 --> 00:12:06.090 align:start position:0% amazing technology but at the same time ZK<00:12:03.700> star<00:12:04.030> snarks<00:12:04.600> and<00:12:04.720> Starks<00:12:05.170> don't<00:12:05.830> actually 00:12:06.090 --> 00:12:06.100 align:start position:0% ZK star snarks and Starks don't actually 00:12:06.100 --> 00:12:08.130 align:start position:0% ZK star snarks and Starks don't actually allow<00:12:06.430> us<00:12:06.610> to<00:12:06.880> compute<00:12:07.210> over<00:12:07.390> encrypted<00:12:07.930> data 00:12:08.130 --> 00:12:08.140 align:start position:0% allow us to compute over encrypted data 00:12:08.140 --> 00:12:11.010 align:start position:0% allow us to compute over encrypted data what<00:12:08.920> they<00:12:09.100> allow<00:12:09.370> us<00:12:09.400> is<00:12:09.850> that<00:12:10.270> if<00:12:10.480> we<00:12:10.660> trust 00:12:11.010 --> 00:12:11.020 align:start position:0% what they allow us is that if we trust 00:12:11.020 --> 00:12:13.740 align:start position:0% what they allow us is that if we trust someone<00:12:11.200> with<00:12:11.830> the<00:12:11.950> data<00:12:12.190> that<00:12:12.610> someone<00:12:13.540> can 00:12:13.740 --> 00:12:13.750 align:start position:0% someone with the data that someone can 00:12:13.750 --> 00:12:15.870 align:start position:0% someone with the data that someone can then<00:12:13.960> prove<00:12:14.380> a<00:12:14.590> computation<00:12:15.280> over<00:12:15.370> that<00:12:15.670> data 00:12:15.870 --> 00:12:15.880 align:start position:0% then prove a computation over that data 00:12:15.880 --> 00:12:18.480 align:start position:0% then prove a computation over that data without<00:12:16.660> actually<00:12:17.260> revealing<00:12:17.680> the<00:12:17.830> data<00:12:18.280> to 00:12:18.480 --> 00:12:18.490 align:start position:0% without actually revealing the data to 00:12:18.490 --> 00:12:20.280 align:start position:0% without actually revealing the data to anyone<00:12:18.760> else<00:12:19.030> but<00:12:19.480> you<00:12:19.600> still<00:12:19.810> gotta<00:12:20.020> trust 00:12:20.280 --> 00:12:20.290 align:start position:0% anyone else but you still gotta trust 00:12:20.290 --> 00:12:22.590 align:start position:0% anyone else but you still gotta trust someone<00:12:20.530> with<00:12:20.710> the<00:12:20.830> data<00:12:21.040> and<00:12:21.430> in<00:12:21.970> the<00:12:22.090> context 00:12:22.590 --> 00:12:22.600 align:start position:0% someone with the data and in the context 00:12:22.600 --> 00:12:24.750 align:start position:0% someone with the data and in the context of<00:12:22.720> smart<00:12:23.020> contract<00:12:23.590> this<00:12:24.130> doesn't<00:12:24.580> work 00:12:24.750 --> 00:12:24.760 align:start position:0% of smart contract this doesn't work 00:12:24.760 --> 00:12:26.400 align:start position:0% of smart contract this doesn't work because<00:12:25.150> in<00:12:25.270> when<00:12:25.630> you<00:12:25.720> execute<00:12:26.050> smart 00:12:26.400 --> 00:12:26.410 align:start position:0% because in when you execute smart 00:12:26.410 --> 00:12:28.470 align:start position:0% because in when you execute smart contract<00:12:26.800> on<00:12:26.890> the<00:12:26.980> blockchain<00:12:27.280> the<00:12:28.060> nodes<00:12:28.300> are 00:12:28.470 --> 00:12:28.480 align:start position:0% contract on the blockchain the nodes are 00:12:28.480 --> 00:12:30.030 align:start position:0% contract on the blockchain the nodes are untrusted<00:12:29.020> you<00:12:29.140> can't<00:12:29.410> trust<00:12:29.650> them<00:12:29.890> to 00:12:30.030 --> 00:12:30.040 align:start position:0% untrusted you can't trust them to 00:12:30.040 --> 00:12:32.820 align:start position:0% untrusted you can't trust them to actually<00:12:30.370> see<00:12:30.550> the<00:12:30.670> data<00:12:30.840> so<00:12:31.840> ZK<00:12:32.200> snarks<00:12:32.650> and 00:12:32.820 --> 00:12:32.830 align:start position:0% actually see the data so ZK snarks and 00:12:32.830 --> 00:12:36.690 align:start position:0% actually see the data so ZK snarks and Starks<00:12:33.220> are<00:12:33.400> with<00:12:34.360> the<00:12:34.450> exception<00:12:35.140> of<00:12:35.700> very 00:12:36.690 --> 00:12:36.700 align:start position:0% Starks are with the exception of very 00:12:36.700 --> 00:12:38.940 align:start position:0% Starks are with the exception of very specific<00:12:37.000> use<00:12:37.600> cases<00:12:37.900> like<00:12:38.170> transactional 00:12:38.940 --> 00:12:38.950 align:start position:0% specific use cases like transactional 00:12:38.950 --> 00:12:41.370 align:start position:0% specific use cases like transactional privacy<00:12:39.460> that<00:12:40.180> are<00:12:40.240> usually<00:12:40.390> explored<00:12:41.140> for 00:12:41.370 --> 00:12:41.380 align:start position:0% privacy that are usually explored for 00:12:41.380 --> 00:12:46.050 align:start position:0% privacy that are usually explored for scalability<00:12:41.860> and<00:12:42.250> not<00:12:42.460> for<00:12:42.700> privacy<00:12:45.060> long 00:12:46.050 --> 00:12:46.060 align:start position:0% scalability and not for privacy long 00:12:46.060 --> 00:12:48.030 align:start position:0% scalability and not for privacy long story<00:12:46.390> short<00:12:46.660> we<00:12:46.870> need<00:12:46.900> something<00:12:47.380> like<00:12:47.410> MPC 00:12:48.030 --> 00:12:48.040 align:start position:0% story short we need something like MPC 00:12:48.040 --> 00:12:49.830 align:start position:0% story short we need something like MPC and<00:12:48.250> I'm<00:12:48.460> going<00:12:48.640> to<00:12:48.700> give<00:12:48.880> you<00:12:49.090> a<00:12:49.300> quick 00:12:49.830 --> 00:12:49.840 align:start position:0% and I'm going to give you a quick 00:12:49.840 --> 00:12:51.930 align:start position:0% and I'm going to give you a quick background<00:12:50.020> about<00:12:50.740> how<00:12:50.860> that<00:12:50.920> works 00:12:51.930 --> 00:12:51.940 align:start position:0% background about how that works 00:12:51.940 --> 00:12:54.810 align:start position:0% background about how that works I'll<00:12:52.360> try<00:12:52.630> to<00:12:52.690> go<00:12:52.990> I<00:12:53.440> can't<00:12:54.280> go<00:12:54.370> into<00:12:54.520> too<00:12:54.700> many 00:12:54.810 --> 00:12:54.820 align:start position:0% I'll try to go I can't go into too many 00:12:54.820 --> 00:12:56.790 align:start position:0% I'll try to go I can't go into too many details<00:12:54.940> but<00:12:55.420> I<00:12:55.480> try<00:12:55.720> to<00:12:55.750> get<00:12:56.080> to<00:12:56.320> give<00:12:56.530> you<00:12:56.560> the 00:12:56.790 --> 00:12:56.800 align:start position:0% details but I try to get to give you the 00:12:56.800 --> 00:12:57.500 align:start position:0% details but I try to get to give you the main<00:12:56.950> idea 00:12:57.500 --> 00:12:57.510 align:start position:0% main idea 00:12:57.510 --> 00:13:01.500 align:start position:0% main idea so<00:12:58.510> MPC<00:12:59.020> works<00:12:59.230> in<00:13:00.010> this<00:13:00.220> paradigm<00:13:00.730> let's 00:13:01.500 --> 00:13:01.510 align:start position:0% so MPC works in this paradigm let's 00:13:01.510 --> 00:13:04.710 align:start position:0% so MPC works in this paradigm let's assume<00:13:01.840> first<00:13:02.230> that<00:13:02.470> we<00:13:03.100> have<00:13:03.130> an<00:13:03.610> ad<00:13:03.910> ideal 00:13:04.710 --> 00:13:04.720 align:start position:0% assume first that we have an ad ideal 00:13:04.720 --> 00:13:08.250 align:start position:0% assume first that we have an ad ideal world<00:13:04.990> in<00:13:05.290> this<00:13:05.980> ideal<00:13:06.430> scenario<00:13:06.760> we<00:13:07.750> have<00:13:07.960> one 00:13:08.250 --> 00:13:08.260 align:start position:0% world in this ideal scenario we have one 00:13:08.260 --> 00:13:11.400 align:start position:0% world in this ideal scenario we have one trusted<00:13:08.770> machine<00:13:09.130> a<00:13:09.370> godlike<00:13:10.030> machine<00:13:10.510> that 00:13:11.400 --> 00:13:11.410 align:start position:0% trusted machine a godlike machine that 00:13:11.410 --> 00:13:14.580 align:start position:0% trusted machine a godlike machine that we<00:13:11.740> can<00:13:11.920> send<00:13:12.220> any<00:13:12.630> computation<00:13:13.630> to<00:13:13.840> and<00:13:14.080> any 00:13:14.580 --> 00:13:14.590 align:start position:0% we can send any computation to and any 00:13:14.590 --> 00:13:16.980 align:start position:0% we can send any computation to and any sensitive<00:13:15.190> data<00:13:15.250> and<00:13:15.820> we<00:13:16.360> can<00:13:16.570> trust<00:13:16.870> that 00:13:16.980 --> 00:13:16.990 align:start position:0% sensitive data and we can trust that 00:13:16.990 --> 00:13:18.870 align:start position:0% sensitive data and we can trust that machine<00:13:17.260> to<00:13:17.680> always<00:13:18.070> produce<00:13:18.340> the<00:13:18.520> right 00:13:18.870 --> 00:13:18.880 align:start position:0% machine to always produce the right 00:13:18.880 --> 00:13:20.190 align:start position:0% machine to always produce the right results<00:13:19.480> and 00:13:20.190 --> 00:13:20.200 align:start position:0% results and 00:13:20.200 --> 00:13:23.160 align:start position:0% results and ever<00:13:20.320> to<00:13:20.590> leak<00:13:20.800> the<00:13:21.400> data<00:13:21.640> to<00:13:21.910> anyone<00:13:22.300> this<00:13:23.110> is 00:13:23.160 --> 00:13:23.170 align:start position:0% ever to leak the data to anyone this is 00:13:23.170 --> 00:13:25.730 align:start position:0% ever to leak the data to anyone this is obviously<00:13:23.650> not<00:13:23.800> possible<00:13:24.340> in<00:13:24.490> the<00:13:24.610> real<00:13:24.640> world 00:13:25.730 --> 00:13:25.740 align:start position:0% obviously not possible in the real world 00:13:25.740 --> 00:13:28.590 align:start position:0% obviously not possible in the real world these<00:13:26.740> process<00:13:27.310> execution<00:13:28.060> environments 00:13:28.590 --> 00:13:28.600 align:start position:0% these process execution environments 00:13:28.600 --> 00:13:30.600 align:start position:0% these process execution environments really<00:13:29.170> get<00:13:29.350> us<00:13:29.560> to<00:13:29.710> the<00:13:29.860> limit<00:13:30.250> of<00:13:30.400> what's 00:13:30.600 --> 00:13:30.610 align:start position:0% really get us to the limit of what's 00:13:30.610 --> 00:13:32.640 align:start position:0% really get us to the limit of what's possible<00:13:30.700> with<00:13:31.300> that<00:13:31.570> but<00:13:32.140> it's<00:13:32.290> still<00:13:32.380> not 00:13:32.640 --> 00:13:32.650 align:start position:0% possible with that but it's still not 00:13:32.650 --> 00:13:34.860 align:start position:0% possible with that but it's still not perfect<00:13:32.950> if<00:13:33.310> we<00:13:33.640> want<00:13:34.030> the<00:13:34.150> perfect<00:13:34.390> solution 00:13:34.860 --> 00:13:34.870 align:start position:0% perfect if we want the perfect solution 00:13:34.870 --> 00:13:39.480 align:start position:0% perfect if we want the perfect solution will<00:13:35.740> need<00:13:35.860> cryptography<00:13:37.050> so<00:13:38.050> NPC<00:13:38.680> comes<00:13:39.280> and 00:13:39.480 --> 00:13:39.490 align:start position:0% will need cryptography so NPC comes and 00:13:39.490 --> 00:13:42.390 align:start position:0% will need cryptography so NPC comes and says<00:13:39.730> you<00:13:40.600> know<00:13:40.780> maybe<00:13:41.470> you<00:13:41.650> can<00:13:41.860> trust<00:13:42.160> one 00:13:42.390 --> 00:13:42.400 align:start position:0% says you know maybe you can trust one 00:13:42.400 --> 00:13:44.700 align:start position:0% says you know maybe you can trust one machine<00:13:42.760> but<00:13:43.000> if<00:13:43.540> you<00:13:43.630> can<00:13:43.810> trust<00:13:44.050> a<00:13:44.230> network 00:13:44.700 --> 00:13:44.710 align:start position:0% machine but if you can trust a network 00:13:44.710 --> 00:13:47.550 align:start position:0% machine but if you can trust a network of<00:13:44.860> computers<00:13:45.490> where<00:13:46.210> all<00:13:46.510> of<00:13:46.660> the<00:13:46.840> net<00:13:47.050> all<00:13:47.320> of 00:13:47.550 --> 00:13:47.560 align:start position:0% of computers where all of the net all of 00:13:47.560 --> 00:13:49.200 align:start position:0% of computers where all of the net all of the<00:13:47.710> nodes<00:13:47.890> in<00:13:48.070> the<00:13:48.100> network's<00:13:48.550> don't<00:13:48.850> have<00:13:49.030> to 00:13:49.200 --> 00:13:49.210 align:start position:0% the nodes in the network's don't have to 00:13:49.210 --> 00:13:51.660 align:start position:0% the nodes in the network's don't have to be<00:13:49.330> trusted<00:13:49.900> but<00:13:50.590> as<00:13:50.740> long<00:13:50.980> as<00:13:51.190> there<00:13:51.370> is<00:13:51.520> at 00:13:51.660 --> 00:13:51.670 align:start position:0% be trusted but as long as there is at 00:13:51.670 --> 00:13:54.210 align:start position:0% be trusted but as long as there is at least<00:13:51.850> one<00:13:52.660> honest<00:13:52.990> node<00:13:53.290> in<00:13:53.530> that<00:13:53.710> network 00:13:54.210 --> 00:13:54.220 align:start position:0% least one honest node in that network 00:13:54.220 --> 00:13:56.910 align:start position:0% least one honest node in that network then<00:13:54.880> you<00:13:54.910> can<00:13:55.210> actually<00:13:55.450> run<00:13:56.020> secure 00:13:56.910 --> 00:13:56.920 align:start position:0% then you can actually run secure 00:13:56.920 --> 00:13:59.310 align:start position:0% then you can actually run secure computation<00:13:57.280> you<00:13:57.730> can<00:13:57.910> actually<00:13:58.150> run<00:13:58.600> any 00:13:59.310 --> 00:13:59.320 align:start position:0% computation you can actually run any 00:13:59.320 --> 00:14:02.400 align:start position:0% computation you can actually run any computation<00:14:00.220> and<00:14:00.460> achieve<00:14:01.210> both<00:14:01.630> privacy<00:14:02.320> of 00:14:02.400 --> 00:14:02.410 align:start position:0% computation and achieve both privacy of 00:14:02.410 --> 00:14:04.440 align:start position:0% computation and achieve both privacy of the<00:14:02.530> data<00:14:02.560> everything<00:14:03.520> remains<00:14:03.850> encrypted 00:14:04.440 --> 00:14:04.450 align:start position:0% the data everything remains encrypted 00:14:04.450 --> 00:14:07.410 align:start position:0% the data everything remains encrypted and<00:14:04.810> you<00:14:05.440> can<00:14:05.650> get<00:14:05.830> the<00:14:05.950> right<00:14:06.100> result<00:14:06.520> it's<00:14:07.150> an 00:14:07.410 --> 00:14:07.420 align:start position:0% and you can get the right result it's an 00:14:07.420 --> 00:14:09.990 align:start position:0% and you can get the right result it's an amazing<00:14:08.110> it<00:14:08.530> seems<00:14:08.770> almost<00:14:09.010> impossible<00:14:09.820> and 00:14:09.990 --> 00:14:10.000 align:start position:0% amazing it seems almost impossible and 00:14:10.000 --> 00:14:12.090 align:start position:0% amazing it seems almost impossible and counterintuitive<00:14:10.510> but<00:14:11.380> we<00:14:11.530> actually<00:14:11.650> know 00:14:12.090 --> 00:14:12.100 align:start position:0% counterintuitive but we actually know 00:14:12.100 --> 00:14:15.960 align:start position:0% counterintuitive but we actually know that<00:14:12.130> from<00:14:13.030> the<00:14:13.210> 80s<00:14:14.430> so<00:14:15.430> let<00:14:15.580> me<00:14:15.700> walk<00:14:15.940> you 00:14:15.960 --> 00:14:15.970 align:start position:0% that from the 80s so let me walk you 00:14:15.970 --> 00:14:17.370 align:start position:0% that from the 80s so let me walk you through<00:14:16.120> a<00:14:16.330> simple<00:14:16.600> example<00:14:16.780> of<00:14:17.170> how<00:14:17.320> that 00:14:17.370 --> 00:14:17.380 align:start position:0% through a simple example of how that 00:14:17.380 --> 00:14:20.130 align:start position:0% through a simple example of how that works<00:14:17.670> let's<00:14:18.670> imagine<00:14:19.030> we<00:14:19.390> have<00:14:19.420> a<00:14:19.570> very<00:14:19.870> small 00:14:20.130 --> 00:14:20.140 align:start position:0% works let's imagine we have a very small 00:14:20.140 --> 00:14:22.320 align:start position:0% works let's imagine we have a very small network<00:14:20.620> of<00:14:20.800> three<00:14:21.070> computers<00:14:21.640> and<00:14:21.880> they're 00:14:22.320 --> 00:14:22.330 align:start position:0% network of three computers and they're 00:14:22.330 --> 00:14:25.430 align:start position:0% network of three computers and they're gonna<00:14:22.450> do<00:14:22.660> MPC<00:14:23.260> to<00:14:23.920> solve<00:14:24.370> the<00:14:24.580> problem<00:14:25.000> of 00:14:25.430 --> 00:14:25.440 align:start position:0% gonna do MPC to solve the problem of 00:14:25.440 --> 00:14:28.530 align:start position:0% gonna do MPC to solve the problem of computing<00:14:26.440> over<00:14:26.590> encrypted<00:14:27.100> data<00:14:27.310> so<00:14:28.300> first 00:14:28.530 --> 00:14:28.540 align:start position:0% computing over encrypted data so first 00:14:28.540 --> 00:14:30.480 align:start position:0% computing over encrypted data so first of<00:14:28.690> all<00:14:28.750> we<00:14:28.930> need<00:14:29.050> to<00:14:29.170> find<00:14:29.410> out<00:14:29.680> how<00:14:30.190> can<00:14:30.250> we 00:14:30.480 --> 00:14:30.490 align:start position:0% of all we need to find out how can we 00:14:30.490 --> 00:14:33.630 align:start position:0% of all we need to find out how can we store<00:14:30.850> data<00:14:31.030> in<00:14:31.300> this<00:14:31.450> network<00:14:32.400> storing<00:14:33.400> works 00:14:33.630 --> 00:14:33.640 align:start position:0% store data in this network storing works 00:14:33.640 --> 00:14:36.000 align:start position:0% store data in this network storing works by<00:14:34.000> a<00:14:34.030> process<00:14:34.510> called<00:14:34.540> secret<00:14:35.200> sharing<00:14:35.440> it's 00:14:36.000 --> 00:14:36.010 align:start position:0% by a process called secret sharing it's 00:14:36.010 --> 00:14:38.190 align:start position:0% by a process called secret sharing it's actually<00:14:36.430> not<00:14:36.610> that<00:14:36.670> complicated<00:14:37.120> but<00:14:37.810> I'm 00:14:38.190 --> 00:14:38.200 align:start position:0% actually not that complicated but I'm 00:14:38.200 --> 00:14:41.280 align:start position:0% actually not that complicated but I'm not<00:14:38.590> gonna<00:14:38.800> explain<00:14:39.160> it<00:14:39.220> here<00:14:39.960> but<00:14:40.960> the<00:14:41.080> main 00:14:41.280 --> 00:14:41.290 align:start position:0% not gonna explain it here but the main 00:14:41.290 --> 00:14:43.470 align:start position:0% not gonna explain it here but the main idea<00:14:41.620> is<00:14:41.890> that<00:14:42.310> you<00:14:42.610> take<00:14:42.790> a<00:14:42.820> piece<00:14:43.090> of<00:14:43.120> data 00:14:43.470 --> 00:14:43.480 align:start position:0% idea is that you take a piece of data 00:14:43.480 --> 00:14:46.200 align:start position:0% idea is that you take a piece of data let's<00:14:43.750> say<00:14:43.930> that<00:14:44.170> data<00:14:44.320> is<00:14:44.560> called<00:14:44.770> X<00:14:45.010> and<00:14:45.340> then 00:14:46.200 --> 00:14:46.210 align:start position:0% let's say that data is called X and then 00:14:46.210 --> 00:14:49.350 align:start position:0% let's say that data is called X and then you<00:14:46.390> split<00:14:46.750> it<00:14:47.080> into<00:14:47.610> different<00:14:48.610> encrypted 00:14:49.350 --> 00:14:49.360 align:start position:0% you split it into different encrypted 00:14:49.360 --> 00:14:52.620 align:start position:0% you split it into different encrypted shares<00:14:49.690> and<00:14:50.020> only<00:14:50.830> send<00:14:51.310> one<00:14:51.460> encrypted<00:14:52.330> share 00:14:52.620 --> 00:14:52.630 align:start position:0% shares and only send one encrypted share 00:14:52.630 --> 00:14:56.340 align:start position:0% shares and only send one encrypted share to<00:14:53.170> each<00:14:53.200> computer<00:14:54.210> so<00:14:55.210> the<00:14:55.720> first<00:14:55.960> node<00:14:56.170> gets 00:14:56.340 --> 00:14:56.350 align:start position:0% to each computer so the first node gets 00:14:56.350 --> 00:14:59.910 align:start position:0% to each computer so the first node gets x1<00:14:56.860> the<00:14:57.310> second<00:14:57.640> X<00:14:57.820> to<00:14:58.000> the<00:14:58.210> third<00:14:58.660> X<00:14:58.810> 3<00:14:59.050> all<00:14:59.530> of 00:14:59.910 --> 00:14:59.920 align:start position:0% x1 the second X to the third X 3 all of 00:14:59.920 --> 00:15:02.460 align:start position:0% x1 the second X to the third X 3 all of these<00:15:00.160> are<00:15:00.490> independently<00:15:01.210> encrypted<00:15:01.750> you 00:15:02.460 --> 00:15:02.470 align:start position:0% these are independently encrypted you 00:15:02.470 --> 00:15:04.560 align:start position:0% these are independently encrypted you can<00:15:02.650> do<00:15:02.770> the<00:15:02.890> same<00:15:03.070> with<00:15:03.310> any<00:15:03.580> any<00:15:04.000> amount<00:15:04.480> of 00:15:04.560 --> 00:15:04.570 align:start position:0% can do the same with any any amount of 00:15:04.570 --> 00:15:07.830 align:start position:0% can do the same with any any amount of data<00:15:04.630> that<00:15:04.930> you<00:15:05.140> want<00:15:05.170> let's<00:15:05.620> say<00:15:05.710> Y<00:15:06.660> and<00:15:07.660> now 00:15:07.830 --> 00:15:07.840 align:start position:0% data that you want let's say Y and now 00:15:07.840 --> 00:15:10.260 align:start position:0% data that you want let's say Y and now let's<00:15:08.140> run<00:15:08.350> a<00:15:08.380> simple<00:15:08.650> computation<00:15:09.370> so<00:15:10.090> let's 00:15:10.260 --> 00:15:10.270 align:start position:0% let's run a simple computation so let's 00:15:10.270 --> 00:15:12.750 align:start position:0% let's run a simple computation so let's say<00:15:10.390> we<00:15:10.540> wanna<00:15:11.080> run<00:15:11.230> addition<00:15:11.740> when<00:15:12.400> it<00:15:12.520> turns 00:15:12.750 --> 00:15:12.760 align:start position:0% say we wanna run addition when it turns 00:15:12.760 --> 00:15:15.270 align:start position:0% say we wanna run addition when it turns out<00:15:13.000> that<00:15:13.150> addition<00:15:13.660> comes<00:15:13.960> for<00:15:14.230> free<00:15:14.410> because 00:15:15.270 --> 00:15:15.280 align:start position:0% out that addition comes for free because 00:15:15.280 --> 00:15:17.820 align:start position:0% out that addition comes for free because of<00:15:15.550> the<00:15:15.730> properties<00:15:16.300> of<00:15:16.390> secret<00:15:16.750> sharing<00:15:17.140> all 00:15:17.820 --> 00:15:17.830 align:start position:0% of the properties of secret sharing all 00:15:17.830 --> 00:15:19.830 align:start position:0% of the properties of secret sharing all you<00:15:18.250> have<00:15:18.430> to<00:15:18.580> do<00:15:18.700> to<00:15:18.850> compute<00:15:19.300> the<00:15:19.450> addition 00:15:19.830 --> 00:15:19.840 align:start position:0% you have to do to compute the addition 00:15:19.840 --> 00:15:23.150 align:start position:0% you have to do to compute the addition of<00:15:19.900> X<00:15:20.140> plus<00:15:20.380> y<00:15:20.590> is<00:15:20.890> as<00:15:21.610> each<00:15:22.120> one<00:15:22.540> of<00:15:22.720> these 00:15:23.150 --> 00:15:23.160 align:start position:0% of X plus y is as each one of these 00:15:23.160 --> 00:15:26.640 align:start position:0% of X plus y is as each one of these computers<00:15:24.160> to<00:15:24.910> just<00:15:25.180> combine<00:15:25.780> the<00:15:26.500> numbers 00:15:26.640 --> 00:15:26.650 align:start position:0% computers to just combine the numbers 00:15:26.650 --> 00:15:29.580 align:start position:0% computers to just combine the numbers together<00:15:27.250> locally<00:15:27.970> and<00:15:28.060> that's<00:15:28.360> it<00:15:28.600> and<00:15:28.930> then 00:15:29.580 --> 00:15:29.590 align:start position:0% together locally and that's it and then 00:15:29.590 --> 00:15:32.280 align:start position:0% together locally and that's it and then when<00:15:29.860> you<00:15:29.920> want<00:15:30.100> to<00:15:30.280> decrypt<00:15:31.030> the<00:15:31.210> result<00:15:31.570> what 00:15:32.280 --> 00:15:32.290 align:start position:0% when you want to decrypt the result what 00:15:32.290 --> 00:15:33.720 align:start position:0% when you want to decrypt the result what you<00:15:32.320> have<00:15:32.650> to<00:15:32.830> do<00:15:33.010> you 00:15:33.720 --> 00:15:33.730 align:start position:0% you have to do you 00:15:33.730 --> 00:15:35.490 align:start position:0% you have to do you have<00:15:33.820> to<00:15:34.000> send<00:15:34.240> all<00:15:34.600> of<00:15:34.660> the<00:15:34.990> shares<00:15:35.260> of<00:15:35.380> the 00:15:35.490 --> 00:15:35.500 align:start position:0% have to send all of the shares of the 00:15:35.500 --> 00:15:38.790 align:start position:0% have to send all of the shares of the data<00:15:35.829> back<00:15:36.760> to<00:15:36.790> someone<00:15:37.449> that<00:15:38.050> someone<00:15:38.560> having 00:15:38.790 --> 00:15:38.800 align:start position:0% data back to someone that someone having 00:15:38.800 --> 00:15:40.769 align:start position:0% data back to someone that someone having all<00:15:39.010> of<00:15:39.040> the<00:15:39.250> shares<00:15:39.490> in<00:15:39.610> one<00:15:39.880> place<00:15:40.180> can 00:15:40.769 --> 00:15:40.779 align:start position:0% all of the shares in one place can 00:15:40.779 --> 00:15:43.800 align:start position:0% all of the shares in one place can decrypt<00:15:41.139> the<00:15:41.320> information<00:15:42.060> but<00:15:43.060> an<00:15:43.269> amazing 00:15:43.800 --> 00:15:43.810 align:start position:0% decrypt the information but an amazing 00:15:43.810 --> 00:15:46.710 align:start position:0% decrypt the information but an amazing thing<00:15:44.019> you<00:15:44.139> happen<00:15:44.470> here<00:15:44.940> these<00:15:45.940> computers 00:15:46.710 --> 00:15:46.720 align:start position:0% thing you happen here these computers 00:15:46.720 --> 00:15:49.079 align:start position:0% thing you happen here these computers have<00:15:46.930> ran<00:15:47.290> a<00:15:47.320> computation<00:15:48.070> they<00:15:48.730> don't<00:15:48.970> know 00:15:49.079 --> 00:15:49.089 align:start position:0% have ran a computation they don't know 00:15:49.089 --> 00:15:51.090 align:start position:0% have ran a computation they don't know the<00:15:49.269> excess<00:15:49.690> they<00:15:50.079> don't<00:15:50.380> know<00:15:50.470> the<00:15:50.649> whys<00:15:50.829> and 00:15:51.090 --> 00:15:51.100 align:start position:0% the excess they don't know the whys and 00:15:51.100 --> 00:15:53.370 align:start position:0% the excess they don't know the whys and they<00:15:51.370> don't<00:15:51.610> know<00:15:51.730> disease<00:15:52.149> all<00:15:52.389> they<00:15:52.839> saw<00:15:53.110> if 00:15:53.370 --> 00:15:53.380 align:start position:0% they don't know disease all they saw if 00:15:53.380 --> 00:15:55.829 align:start position:0% they don't know disease all they saw if you<00:15:53.560> probe<00:15:53.860> into<00:15:54.100> if<00:15:54.550> you<00:15:54.940> zoom<00:15:55.300> into<00:15:55.510> one<00:15:55.630> of 00:15:55.829 --> 00:15:55.839 align:start position:0% you probe into if you zoom into one of 00:15:55.839 --> 00:15:57.780 align:start position:0% you probe into if you zoom into one of these<00:15:55.930> computers<00:15:56.470> all<00:15:56.769> you<00:15:57.070> see<00:15:57.220> is<00:15:57.279> encrypted 00:15:57.780 --> 00:15:57.790 align:start position:0% these computers all you see is encrypted 00:15:57.790 --> 00:16:01.650 align:start position:0% these computers all you see is encrypted data<00:15:58.000> and<00:15:58.420> yet<00:15:59.110> this<00:15:59.740> guy<00:16:00.070> got<00:16:00.670> the<00:16:01.089> decrypted 00:16:01.650 --> 00:16:01.660 align:start position:0% data and yet this guy got the decrypted 00:16:01.660 --> 00:16:05.430 align:start position:0% data and yet this guy got the decrypted result<00:16:03.149> so<00:16:04.149> that's<00:16:04.300> the<00:16:04.389> basic<00:16:04.750> of<00:16:04.870> MPC<00:16:05.290> when 00:16:05.430 --> 00:16:05.440 align:start position:0% result so that's the basic of MPC when 00:16:05.440 --> 00:16:08.129 align:start position:0% result so that's the basic of MPC when it<00:16:05.529> comes<00:16:05.740> to<00:16:05.920> addition<00:16:06.370> multiplication<00:16:07.180> is 00:16:08.129 --> 00:16:08.139 align:start position:0% it comes to addition multiplication is 00:16:08.139 --> 00:16:10.500 align:start position:0% it comes to addition multiplication is more<00:16:08.470> complicated<00:16:08.860> but<00:16:09.399> I<00:16:09.459> do<00:16:09.579> want<00:16:09.910> to<00:16:09.970> go<00:16:10.180> at 00:16:10.500 --> 00:16:10.510 align:start position:0% more complicated but I do want to go at 00:16:10.510 --> 00:16:12.439 align:start position:0% more complicated but I do want to go at this<00:16:10.720> on<00:16:10.839> a<00:16:10.870> high<00:16:11.079> level<00:16:11.350> of<00:16:11.560> how<00:16:11.740> it<00:16:11.889> works 00:16:12.439 --> 00:16:12.449 align:start position:0% this on a high level of how it works 00:16:12.449 --> 00:16:15.870 align:start position:0% this on a high level of how it works so<00:16:13.449> for<00:16:13.630> multiplication<00:16:14.019> it<00:16:14.769> turns<00:16:15.130> out<00:16:15.399> that 00:16:15.870 --> 00:16:15.880 align:start position:0% so for multiplication it turns out that 00:16:15.880 --> 00:16:17.670 align:start position:0% so for multiplication it turns out that we<00:16:16.389> need<00:16:16.540> something<00:16:16.810> else<00:16:17.079> when<00:16:17.560> it's 00:16:17.670 --> 00:16:17.680 align:start position:0% we need something else when it's 00:16:17.680 --> 00:16:20.269 align:start position:0% we need something else when it's something<00:16:17.889> called<00:16:18.420> multiplication<00:16:19.420> triplets 00:16:20.269 --> 00:16:20.279 align:start position:0% something called multiplication triplets 00:16:20.279 --> 00:16:22.439 align:start position:0% something called multiplication triplets multiplication<00:16:21.279> triple<00:16:21.699> triplets 00:16:22.439 --> 00:16:22.449 align:start position:0% multiplication triple triplets 00:16:22.449 --> 00:16:27.060 align:start position:0% multiplication triple triplets that's<00:16:23.050> the<00:16:23.350> ABC<00:16:24.870> they<00:16:25.870> are<00:16:26.139> correlated 00:16:27.060 --> 00:16:27.070 align:start position:0% that's the ABC they are correlated 00:16:27.070 --> 00:16:30.569 align:start position:0% that's the ABC they are correlated randomness<00:16:27.850> so<00:16:28.060> a<00:16:28.510> and<00:16:28.870> B<00:16:29.050> are<00:16:29.320> just<00:16:29.579> random 00:16:30.569 --> 00:16:30.579 align:start position:0% randomness so a and B are just random 00:16:30.579 --> 00:16:32.100 align:start position:0% randomness so a and B are just random numbers<00:16:30.910> that<00:16:30.940> are<00:16:31.240> randomly<00:16:31.540> generated 00:16:32.100 --> 00:16:32.110 align:start position:0% numbers that are randomly generated 00:16:32.110 --> 00:16:34.829 align:start position:0% numbers that are randomly generated independently<00:16:32.670> but<00:16:33.670> C<00:16:33.940> is<00:16:34.089> correlated 00:16:34.829 --> 00:16:34.839 align:start position:0% independently but C is correlated 00:16:34.839 --> 00:16:38.670 align:start position:0% independently but C is correlated because<00:16:34.990> it's<00:16:35.440> the<00:16:35.680> product<00:16:36.040> of<00:16:36.370> a<00:16:36.490> times<00:16:36.519> B<00:16:37.680> ok 00:16:38.670 --> 00:16:38.680 align:start position:0% because it's the product of a times B ok 00:16:38.680 --> 00:16:42.240 align:start position:0% because it's the product of a times B ok and<00:16:38.920> now<00:16:39.490> every<00:16:40.480> node<00:16:40.720> has<00:16:41.019> has<00:16:41.680> these 00:16:42.240 --> 00:16:42.250 align:start position:0% and now every node has has these 00:16:42.250 --> 00:16:45.000 align:start position:0% and now every node has has these triplets<00:16:42.639> these<00:16:43.630> triplets<00:16:43.990> are<00:16:44.290> independent 00:16:45.000 --> 00:16:45.010 align:start position:0% triplets these triplets are independent 00:16:45.010 --> 00:16:46.590 align:start position:0% triplets these triplets are independent of<00:16:45.100> the<00:16:45.220> data<00:16:45.399> so<00:16:45.819> they<00:16:45.940> can<00:16:45.970> actually<00:16:46.329> be 00:16:46.590 --> 00:16:46.600 align:start position:0% of the data so they can actually be 00:16:46.600 --> 00:16:50.150 align:start position:0% of the data so they can actually be computed<00:16:47.500> a<00:16:47.829> priori<00:16:48.699> like<00:16:49.000> you<00:16:49.149> can<00:16:49.329> put<00:16:49.600> a 00:16:50.150 --> 00:16:50.160 align:start position:0% computed a priori like you can put a 00:16:50.160 --> 00:16:53.189 align:start position:0% computed a priori like you can put a supercomputer<00:16:51.160> these<00:16:51.760> computers<00:16:52.389> can<00:16:52.959> work 00:16:53.189 --> 00:16:53.199 align:start position:0% supercomputer these computers can work 00:16:53.199 --> 00:16:55.800 align:start position:0% supercomputer these computers can work overnight<00:16:53.649> and<00:16:54.160> just<00:16:54.190> generate<00:16:55.089> many<00:16:55.510> many 00:16:55.800 --> 00:16:55.810 align:start position:0% overnight and just generate many many 00:16:55.810 --> 00:16:58.920 align:start position:0% overnight and just generate many many many<00:16:56.139> many<00:16:56.470> of<00:16:56.740> these<00:16:57.190> a<00:16:57.459> B<00:16:57.760> and<00:16:57.910> C's<00:16:58.180> the 00:16:58.920 --> 00:16:58.930 align:start position:0% many many of these a B and C's the 00:16:58.930 --> 00:17:00.960 align:start position:0% many many of these a B and C's the reason<00:16:59.319> is<00:16:59.470> that<00:16:59.800> these<00:17:00.279> a<00:17:00.430> B<00:17:00.610> and<00:17:00.730> C's<00:17:00.940> are 00:17:00.960 --> 00:17:00.970 align:start position:0% reason is that these a B and C's are 00:17:00.970 --> 00:17:03.210 align:start position:0% reason is that these a B and C's are then<00:17:01.300> used<00:17:01.540> as<00:17:01.690> a<00:17:01.720> one-time<00:17:02.019> pad<00:17:02.529> and<00:17:02.800> they 00:17:03.210 --> 00:17:03.220 align:start position:0% then used as a one-time pad and they 00:17:03.220 --> 00:17:05.549 align:start position:0% then used as a one-time pad and they cannot<00:17:03.579> be<00:17:03.790> reused<00:17:04.150> so<00:17:04.360> you<00:17:04.419> really<00:17:04.780> need<00:17:04.959> many 00:17:05.549 --> 00:17:05.559 align:start position:0% cannot be reused so you really need many 00:17:05.559 --> 00:17:09.230 align:start position:0% cannot be reused so you really need many of<00:17:05.770> these<00:17:06.030> pre-process<00:17:07.030> for<00:17:07.660> a<00:17:07.689> computation 00:17:09.230 --> 00:17:09.240 align:start position:0% of these pre-process for a computation 00:17:09.240 --> 00:17:11.569 align:start position:0% of these pre-process for a computation so<00:17:10.240> now<00:17:10.360> let's<00:17:10.540> do<00:17:10.660> the<00:17:10.780> actual<00:17:11.079> computation 00:17:11.569 --> 00:17:11.579 align:start position:0% so now let's do the actual computation 00:17:11.579 --> 00:17:14.939 align:start position:0% so now let's do the actual computation we<00:17:12.579> want<00:17:12.760> to<00:17:12.819> compute<00:17:13.120> x<00:17:13.419> times<00:17:13.660> y<00:17:13.949> what 00:17:14.939 --> 00:17:14.949 align:start position:0% we want to compute x times y what 00:17:14.949 --> 00:17:19.010 align:start position:0% we want to compute x times y what happens<00:17:15.400> here<00:17:15.819> is<00:17:16.000> that<00:17:16.360> each<00:17:16.870> node<00:17:17.250> takes<00:17:18.250> a 00:17:19.010 --> 00:17:19.020 align:start position:0% happens here is that each node takes a 00:17:19.020 --> 00:17:22.740 align:start position:0% happens here is that each node takes a one-time<00:17:20.020> pad<00:17:20.350> of<00:17:20.589> their<00:17:21.339> share<00:17:21.730> of<00:17:21.760> x<00:17:22.360> and<00:17:22.600> y 00:17:22.740 --> 00:17:22.750 align:start position:0% one-time pad of their share of x and y 00:17:22.750 --> 00:17:25.919 align:start position:0% one-time pad of their share of x and y the<00:17:23.679> reason<00:17:24.040> they<00:17:24.189> do<00:17:24.250> this<00:17:24.400> is<00:17:24.850> because<00:17:25.480> then 00:17:25.919 --> 00:17:25.929 align:start position:0% the reason they do this is because then 00:17:25.929 --> 00:17:28.199 align:start position:0% the reason they do this is because then they<00:17:26.319> need<00:17:26.589> to<00:17:26.620> share<00:17:27.010> these<00:17:27.280> with<00:17:27.669> each<00:17:27.970> other 00:17:28.199 --> 00:17:28.209 align:start position:0% they need to share these with each other 00:17:28.209 --> 00:17:31.620 align:start position:0% they need to share these with each other which<00:17:28.929> is<00:17:28.990> what<00:17:29.260> happens<00:17:29.679> here<00:17:30.040> and<00:17:30.419> then<00:17:31.419> when 00:17:31.620 --> 00:17:31.630 align:start position:0% which is what happens here and then when 00:17:31.630 --> 00:17:33.740 align:start position:0% which is what happens here and then when they<00:17:31.780> share<00:17:32.049> it<00:17:32.200> with<00:17:32.350> each<00:17:32.380> other<00:17:32.620> they<00:17:33.429> can 00:17:33.740 --> 00:17:33.750 align:start position:0% they share it with each other they can 00:17:33.750 --> 00:17:35.820 align:start position:0% they share it with each other they can because<00:17:34.750> they<00:17:34.870> have<00:17:35.049> each<00:17:35.230> one<00:17:35.470> of<00:17:35.559> them<00:17:35.679> has 00:17:35.820 --> 00:17:35.830 align:start position:0% because they have each one of them has 00:17:35.830 --> 00:17:39.299 align:start position:0% because they have each one of them has all<00:17:36.010> the<00:17:36.130> shares<00:17:36.370> they<00:17:37.150> can<00:17:37.419> decrypt<00:17:37.900> a<00:17:38.559> number 00:17:39.299 --> 00:17:39.309 align:start position:0% all the shares they can decrypt a number 00:17:39.309 --> 00:17:41.700 align:start position:0% all the shares they can decrypt a number called<00:17:39.549> D<00:17:39.730> and<00:17:39.940> a<00:17:40.000> number<00:17:40.150> called<00:17:40.480> e<00:17:40.710> Deenie 00:17:41.700 --> 00:17:41.710 align:start position:0% called D and a number called e Deenie 00:17:41.710 --> 00:17:44.250 align:start position:0% called D and a number called e Deenie are<00:17:41.890> basically<00:17:42.520> a<00:17:42.549> one-time<00:17:43.090> pair<00:17:43.390> of<00:17:43.570> x<00:17:43.809> and<00:17:44.080> y 00:17:44.250 --> 00:17:44.260 align:start position:0% are basically a one-time pair of x and y 00:17:44.260 --> 00:17:47.630 align:start position:0% are basically a one-time pair of x and y why<00:17:45.100> is<00:17:45.159> this<00:17:45.429> important<00:17:46.059> because<00:17:46.690> if<00:17:47.169> we 00:17:47.630 --> 00:17:47.640 align:start position:0% why is this important because if we 00:17:47.640 --> 00:17:50.450 align:start position:0% why is this important because if we not<00:17:47.820> Dundee<00:17:48.240> step<00:17:48.510> then<00:17:49.320> all<00:17:49.680> the<00:17:50.070> nodes<00:17:50.280> would 00:17:50.450 --> 00:17:50.460 align:start position:0% not Dundee step then all the nodes would 00:17:50.460 --> 00:17:52.400 align:start position:0% not Dundee step then all the nodes would have<00:17:50.610> shared<00:17:50.910> their<00:17:51.120> X<00:17:51.330> and<00:17:51.540> Y's<00:17:51.660> together<00:17:52.080> and 00:17:52.400 --> 00:17:52.410 align:start position:0% have shared their X and Y's together and 00:17:52.410 --> 00:17:54.590 align:start position:0% have shared their X and Y's together and by<00:17:53.160> the<00:17:53.220> property<00:17:53.760> of<00:17:53.820> secret<00:17:54.150> chairman<00:17:54.480> if 00:17:54.590 --> 00:17:54.600 align:start position:0% by the property of secret chairman if 00:17:54.600 --> 00:17:56.330 align:start position:0% by the property of secret chairman if you<00:17:54.690> get<00:17:54.870> all<00:17:55.020> the<00:17:55.140> x<00:17:55.350> and<00:17:55.590> y's<00:17:55.710> in<00:17:55.920> one<00:17:56.070> place 00:17:56.330 --> 00:17:56.340 align:start position:0% you get all the x and y's in one place 00:17:56.340 --> 00:17:58.100 align:start position:0% you get all the x and y's in one place you<00:17:56.610> can<00:17:57.060> decrypt<00:17:57.390> the<00:17:57.600> actual<00:17:57.900> information 00:17:58.100 --> 00:17:58.110 align:start position:0% you can decrypt the actual information 00:17:58.110 --> 00:18:02.050 align:start position:0% you can decrypt the actual information so<00:17:59.040> this<00:17:59.250> is<00:17:59.430> a<00:17:59.460> master<00:17:59.940> we<00:18:00.120> cannot<00:18:00.390> avoid<00:18:00.690> this 00:18:02.050 --> 00:18:02.060 align:start position:0% so this is a master we cannot avoid this 00:18:02.060 --> 00:18:08.240 align:start position:0% so this is a master we cannot avoid this but<00:18:03.230> because<00:18:04.730> c<00:18:05.730> equals<00:18:06.420> a<00:18:06.720> times<00:18:06.990> b<00:18:07.290> and<00:18:07.590> if 00:18:08.240 --> 00:18:08.250 align:start position:0% but because c equals a times b and if 00:18:08.250 --> 00:18:11.300 align:start position:0% but because c equals a times b and if you<00:18:08.430> then<00:18:09.120> plug<00:18:09.450> that<00:18:09.480> into<00:18:10.020> this<00:18:10.310> equation 00:18:11.300 --> 00:18:11.310 align:start position:0% you then plug that into this equation 00:18:11.310 --> 00:18:14.300 align:start position:0% you then plug that into this equation just<00:18:11.820> by<00:18:12.510> very<00:18:12.900> simple<00:18:13.290> algebra<00:18:13.740> you're<00:18:14.040> gonna 00:18:14.300 --> 00:18:14.310 align:start position:0% just by very simple algebra you're gonna 00:18:14.310 --> 00:18:16.640 align:start position:0% just by very simple algebra you're gonna have<00:18:14.400> to<00:18:14.520> trust<00:18:14.700> maybe<00:18:15.000> you're<00:18:15.900> getting<00:18:16.080> is 00:18:16.640 --> 00:18:16.650 align:start position:0% have to trust maybe you're getting is 00:18:16.650 --> 00:18:18.950 align:start position:0% have to trust maybe you're getting is gonna<00:18:16.800> cancel<00:18:17.100> out<00:18:17.490> and<00:18:17.760> you're<00:18:18.270> gonna<00:18:18.450> end<00:18:18.690> up 00:18:18.950 --> 00:18:18.960 align:start position:0% gonna cancel out and you're gonna end up 00:18:18.960 --> 00:18:22.940 align:start position:0% gonna cancel out and you're gonna end up with<00:18:19.680> Z<00:18:20.340> equals<00:18:21.000> X<00:18:21.240> x<00:18:21.600> times<00:18:21.780> y<00:18:22.140> or<00:18:22.410> actually 00:18:22.940 --> 00:18:22.950 align:start position:0% with Z equals X x times y or actually 00:18:22.950 --> 00:18:25.790 align:start position:0% with Z equals X x times y or actually each<00:18:23.550> of<00:18:23.970> these<00:18:24.120> Z's<00:18:24.450> is<00:18:24.750> an<00:18:25.020> encrypted<00:18:25.380> share 00:18:25.790 --> 00:18:25.800 align:start position:0% each of these Z's is an encrypted share 00:18:25.800 --> 00:18:29.330 align:start position:0% each of these Z's is an encrypted share of<00:18:26.070> x<00:18:26.490> times<00:18:26.730> y<00:18:26.940> and<00:18:27.240> so<00:18:28.020> at<00:18:28.170> this<00:18:28.320> point<00:18:28.650> you 00:18:29.330 --> 00:18:29.340 align:start position:0% of x times y and so at this point you 00:18:29.340 --> 00:18:31.790 align:start position:0% of x times y and so at this point you can<00:18:29.550> just<00:18:29.850> send<00:18:30.660> those<00:18:30.840> these<00:18:31.110> back<00:18:31.380> as<00:18:31.620> with 00:18:31.790 --> 00:18:31.800 align:start position:0% can just send those these back as with 00:18:31.800 --> 00:18:34.520 align:start position:0% can just send those these back as with the<00:18:31.890> addition<00:18:32.370> and<00:18:32.550> hold<00:18:33.180> and<00:18:33.330> behold<00:18:33.660> we 00:18:34.520 --> 00:18:34.530 align:start position:0% the addition and hold and behold we 00:18:34.530 --> 00:18:36.620 align:start position:0% the addition and hold and behold we computed<00:18:34.980> multiplication<00:18:35.850> over<00:18:36.060> encrypted 00:18:36.620 --> 00:18:36.630 align:start position:0% computed multiplication over encrypted 00:18:36.630 --> 00:18:39.530 align:start position:0% computed multiplication over encrypted data<00:18:37.400> now<00:18:38.400> that<00:18:38.610> might<00:18:38.820> not<00:18:38.850> sound<00:18:39.270> that 00:18:39.530 --> 00:18:39.540 align:start position:0% data now that might not sound that 00:18:39.540 --> 00:18:40.940 align:start position:0% data now that might not sound that exciting<00:18:39.690> I<00:18:40.170> mean<00:18:40.290> addition<00:18:40.800> multiplication 00:18:40.940 --> 00:18:40.950 align:start position:0% exciting I mean addition multiplication 00:18:40.950 --> 00:18:43.850 align:start position:0% exciting I mean addition multiplication fine<00:18:41.730> how<00:18:42.420> do<00:18:42.480> we<00:18:42.750> get<00:18:43.170> general<00:18:43.470> purpose 00:18:43.850 --> 00:18:43.860 align:start position:0% fine how do we get general purpose 00:18:43.860 --> 00:18:46.370 align:start position:0% fine how do we get general purpose computing<00:18:44.340> well<00:18:45.000> it's<00:18:45.120> a<00:18:45.300> very<00:18:45.540> known<00:18:45.840> result 00:18:46.370 --> 00:18:46.380 align:start position:0% computing well it's a very known result 00:18:46.380 --> 00:18:48.890 align:start position:0% computing well it's a very known result that<00:18:46.890> will<00:18:46.980> addition<00:18:47.460> multiplication<00:18:47.900> you 00:18:48.890 --> 00:18:48.900 align:start position:0% that will addition multiplication you 00:18:48.900 --> 00:18:50.930 align:start position:0% that will addition multiplication you can<00:18:48.930> actually<00:18:49.500> compute<00:18:49.890> any<00:18:50.190> function<00:18:50.760> and 00:18:50.930 --> 00:18:50.940 align:start position:0% can actually compute any function and 00:18:50.940 --> 00:18:53.200 align:start position:0% can actually compute any function and that's<00:18:51.600> what<00:18:51.780> we<00:18:51.960> use<00:18:52.140> and<00:18:52.440> that's 00:18:53.200 --> 00:18:53.210 align:start position:0% that's what we use and that's 00:18:53.210 --> 00:18:56.000 align:start position:0% that's what we use and that's technically<00:18:54.210> what<00:18:54.450> I<00:18:54.480> believe<00:18:54.840> other<00:18:55.470> other 00:18:56.000 --> 00:18:56.010 align:start position:0% technically what I believe other other 00:18:56.010 --> 00:18:58.670 align:start position:0% technically what I believe other other other<00:18:56.430> techniques<00:18:56.970> like<00:18:57.210> fhe<00:18:58.140> and<00:18:58.320> Starks 00:18:58.670 --> 00:18:58.680 align:start position:0% other techniques like fhe and Starks 00:18:58.680 --> 00:19:02.480 align:start position:0% other techniques like fhe and Starks years<00:18:58.920> that's<00:18:59.700> really<00:18:59.910> all<00:19:00.120> you<00:19:00.240> need<00:19:01.340> so<00:19:02.340> how 00:19:02.480 --> 00:19:02.490 align:start position:0% years that's really all you need so how 00:19:02.490 --> 00:19:04.190 align:start position:0% years that's really all you need so how does<00:19:02.550> that<00:19:02.820> tie<00:19:03.090> back<00:19:03.120> to<00:19:03.360> enigma<00:19:03.900> and<00:19:04.050> what 00:19:04.190 --> 00:19:04.200 align:start position:0% does that tie back to enigma and what 00:19:04.200 --> 00:19:06.110 align:start position:0% does that tie back to enigma and what are<00:19:04.350> we<00:19:04.380> working<00:19:04.620> right<00:19:04.980> now<00:19:05.160> to<00:19:05.220> develop<00:19:05.490> next 00:19:06.110 --> 00:19:06.120 align:start position:0% are we working right now to develop next 00:19:06.120 --> 00:19:09.110 align:start position:0% are we working right now to develop next beyond<00:19:06.540> trusted<00:19:07.350> execution<00:19:07.560> environments<00:19:08.400> so 00:19:09.110 --> 00:19:09.120 align:start position:0% beyond trusted execution environments so 00:19:09.120 --> 00:19:12.500 align:start position:0% beyond trusted execution environments so the<00:19:09.330> idea<00:19:09.600> is<00:19:10.100> the<00:19:11.100> idea<00:19:11.130> is<00:19:11.610> and<00:19:11.850> there's<00:19:12.360> only 00:19:12.500 --> 00:19:12.510 align:start position:0% the idea is the idea is and there's only 00:19:12.510 --> 00:19:14.300 align:start position:0% the idea is the idea is and there's only a<00:19:12.930> small<00:19:13.230> amount<00:19:13.500> of<00:19:13.590> difference<00:19:13.980> we<00:19:14.100> need<00:19:14.220> to 00:19:14.300 --> 00:19:14.310 align:start position:0% a small amount of difference we need to 00:19:14.310 --> 00:19:16.490 align:start position:0% a small amount of difference we need to make<00:19:14.490> the<00:19:15.270> idea<00:19:15.540> is<00:19:15.690> that<00:19:15.810> when<00:19:15.990> the<00:19:16.080> user<00:19:16.230> now 00:19:16.490 --> 00:19:16.500 align:start position:0% make the idea is that when the user now 00:19:16.500 --> 00:19:19.190 align:start position:0% make the idea is that when the user now submits<00:19:16.950> a<00:19:17.070> task<00:19:17.340> instead<00:19:18.060> of<00:19:18.540> encrypting 00:19:19.190 --> 00:19:19.200 align:start position:0% submits a task instead of encrypting 00:19:19.200 --> 00:19:21.560 align:start position:0% submits a task instead of encrypting those<00:19:19.410> with<00:19:19.860> you<00:19:20.280> know<00:19:20.370> a<00:19:20.550> yes<00:19:20.910> or<00:19:21.180> something 00:19:21.560 --> 00:19:21.570 align:start position:0% those with you know a yes or something 00:19:21.570 --> 00:19:22.940 align:start position:0% those with you know a yes or something and<00:19:21.660> just<00:19:21.720> sending<00:19:22.170> these<00:19:22.290> to<00:19:22.440> the<00:19:22.560> enclave's 00:19:22.940 --> 00:19:22.950 align:start position:0% and just sending these to the enclave's 00:19:22.950 --> 00:19:26.060 align:start position:0% and just sending these to the enclave's what<00:19:23.790> they<00:19:23.970> can<00:19:24.210> do<00:19:24.390> they<00:19:24.660> can<00:19:25.170> do<00:19:25.560> the<00:19:25.680> secret 00:19:26.060 --> 00:19:26.070 align:start position:0% what they can do they can do the secret 00:19:26.070 --> 00:19:27.560 align:start position:0% what they can do they can do the secret chairmen<00:19:26.430> they<00:19:26.550> can<00:19:26.730> split<00:19:27.120> these<00:19:27.510> into 00:19:27.560 --> 00:19:27.570 align:start position:0% chairmen they can split these into 00:19:27.570 --> 00:19:30.920 align:start position:0% chairmen they can split these into shares<00:19:28.140> and<00:19:28.470> share<00:19:29.370> one<00:19:29.790> and<00:19:30.150> and<00:19:30.390> send<00:19:30.660> one 00:19:30.920 --> 00:19:30.930 align:start position:0% shares and share one and and send one 00:19:30.930 --> 00:19:34.250 align:start position:0% shares and share one and and send one share<00:19:31.290> of<00:19:31.440> the<00:19:31.560> input<00:19:31.950> to<00:19:32.640> each<00:19:32.820> node<00:19:33.660> in<00:19:34.050> the 00:19:34.250 --> 00:19:34.260 align:start position:0% share of the input to each node in the 00:19:34.260 --> 00:19:35.810 align:start position:0% share of the input to each node in the group<00:19:34.440> in<00:19:34.590> the<00:19:34.710> worker<00:19:34.950> group<00:19:35.340> that<00:19:35.580> is 00:19:35.810 --> 00:19:35.820 align:start position:0% group in the worker group that is 00:19:35.820 --> 00:19:38.600 align:start position:0% group in the worker group that is randomly<00:19:36.600> assigned<00:19:36.720> and<00:19:37.430> everything<00:19:38.430> else 00:19:38.600 --> 00:19:38.610 align:start position:0% randomly assigned and everything else 00:19:38.610 --> 00:19:41.150 align:start position:0% randomly assigned and everything else kind<00:19:38.970> of<00:19:39.060> happens<00:19:39.450> is<00:19:39.720> the<00:19:39.960> same<00:19:40.170> way<00:19:40.380> the 00:19:41.150 --> 00:19:41.160 align:start position:0% kind of happens is the same way the 00:19:41.160 --> 00:19:44.090 align:start position:0% kind of happens is the same way the worker<00:19:42.030> groups<00:19:42.450> having<00:19:43.260> secret<00:19:43.830> shared 00:19:44.090 --> 00:19:44.100 align:start position:0% worker groups having secret shared 00:19:44.100 --> 00:19:47.180 align:start position:0% worker groups having secret shared version<00:19:44.610> of<00:19:44.790> the<00:19:44.940> data<00:19:45.180> of<00:19:45.570> the<00:19:46.050> inputs<00:19:46.410> they 00:19:47.180 --> 00:19:47.190 align:start position:0% version of the data of the inputs they 00:19:47.190 --> 00:19:50.630 align:start position:0% version of the data of the inputs they can<00:19:47.460> get<00:19:48.680> they<00:19:49.680> can<00:19:49.860> take<00:19:50.040> the<00:19:50.220> webassembly 00:19:50.630 --> 00:19:50.640 align:start position:0% can get they can take the webassembly 00:19:50.640 --> 00:19:54.470 align:start position:0% can get they can take the webassembly code<00:19:51.030> and<00:19:51.300> then<00:19:51.930> just<00:19:52.230> go<00:19:52.380> one<00:19:52.680> by<00:19:52.920> line<00:19:53.480> line 00:19:54.470 --> 00:19:54.480 align:start position:0% code and then just go one by line line 00:19:54.480 --> 00:19:56.470 align:start position:0% code and then just go one by line line by<00:19:54.660> line<00:19:54.690> in<00:19:55.050> the<00:19:55.140> web<00:19:55.290> assembly<00:19:55.710> code<00:19:55.890> and 00:19:56.470 --> 00:19:56.480 align:start position:0% by line in the web assembly code and 00:19:56.480 --> 00:19:59.990 align:start position:0% by line in the web assembly code and interpret<00:19:57.480> that<00:19:57.630> as<00:19:57.930> an<00:19:58.230> MPC<00:19:58.620> protocol<00:19:59.280> so<00:19:59.850> for 00:19:59.990 --> 00:20:00.000 align:start position:0% interpret that as an MPC protocol so for 00:20:00.000 --> 00:20:01.730 align:start position:0% interpret that as an MPC protocol so for example<00:20:00.420> if<00:20:00.510> you<00:20:00.630> have<00:20:00.810> an<00:20:00.930> instructor 00:20:01.730 --> 00:20:01.740 align:start position:0% example if you have an instructor 00:20:01.740 --> 00:20:04.460 align:start position:0% example if you have an instructor if<00:20:01.920> you<00:20:02.790> if<00:20:03.150> you<00:20:03.360> have<00:20:03.510> an<00:20:03.630> instruction<00:20:04.260> that 00:20:04.460 --> 00:20:04.470 align:start position:0% if you if you have an instruction that 00:20:04.470 --> 00:20:07.700 align:start position:0% if you if you have an instruction that says<00:20:05.840> if<00:20:06.840> you<00:20:06.960> have<00:20:07.050> any<00:20:07.200> service<00:20:07.440> that<00:20:07.470> says 00:20:07.700 --> 00:20:07.710 align:start position:0% says if you have any service that says 00:20:07.710 --> 00:20:09.560 align:start position:0% says if you have any service that says that's<00:20:07.950> multiply<00:20:08.370> two<00:20:08.430> numbers<00:20:08.700> when<00:20:09.420> it's 00:20:09.560 --> 00:20:09.570 align:start position:0% that's multiply two numbers when it's 00:20:09.570 --> 00:20:11.900 align:start position:0% that's multiply two numbers when it's actually<00:20:09.750> being<00:20:10.200> interpreted<00:20:11.010> as<00:20:11.520> what<00:20:11.880> I 00:20:11.900 --> 00:20:11.910 align:start position:0% actually being interpreted as what I 00:20:11.910 --> 00:20:14.080 align:start position:0% actually being interpreted as what I showed<00:20:12.210> you<00:20:12.390> two<00:20:12.540> minutes<00:20:12.690> ago 00:20:14.080 --> 00:20:14.090 align:start position:0% showed you two minutes ago 00:20:14.090 --> 00:20:17.420 align:start position:0% showed you two minutes ago now<00:20:15.090> I'm<00:20:15.360> running<00:20:15.870> out<00:20:16.110> of<00:20:16.140> time<00:20:16.380> a<00:20:16.440> bit<00:20:16.680> so<00:20:17.100> I 00:20:17.420 --> 00:20:17.430 align:start position:0% now I'm running out of time a bit so I 00:20:17.430 --> 00:20:20.720 align:start position:0% now I'm running out of time a bit so I what<00:20:18.270> I<00:20:18.300> do<00:20:18.450> want<00:20:18.810> to<00:20:18.870> focus<00:20:19.050> on<00:20:19.470> is<00:20:19.710> first<00:20:20.550> of 00:20:20.720 --> 00:20:20.730 align:start position:0% what I do want to focus on is first of 00:20:20.730 --> 00:20:22.850 align:start position:0% what I do want to focus on is first of all<00:20:20.850> that<00:20:21.120> this<00:20:21.300> is<00:20:21.510> life<00:20:21.690> today<00:20:22.080> we<00:20:22.680> have<00:20:22.830> very 00:20:22.850 --> 00:20:22.860 align:start position:0% all that this is life today we have very 00:20:22.860 --> 00:20:25.010 align:start position:0% all that this is life today we have very serious<00:20:23.280> projects<00:20:24.120> building<00:20:24.450> on<00:20:24.660> us<00:20:24.780> and 00:20:25.010 --> 00:20:25.020 align:start position:0% serious projects building on us and 00:20:25.020 --> 00:20:27.160 align:start position:0% serious projects building on us and there's<00:20:25.560> a<00:20:25.860> whole<00:20:26.430> host<00:20:26.670> of<00:20:26.850> applications 00:20:27.160 --> 00:20:27.170 align:start position:0% there's a whole host of applications 00:20:27.170 --> 00:20:29.690 align:start position:0% there's a whole host of applications what<00:20:28.170> this<00:20:28.320> is<00:20:28.440> relevant<00:20:28.950> we<00:20:29.310> talking 00:20:29.690 --> 00:20:29.700 align:start position:0% what this is relevant we talking 00:20:29.700 --> 00:20:33.470 align:start position:0% what this is relevant we talking governance<00:20:30.270> auction<00:20:31.640> secret<00:20:32.640> icos 00:20:33.470 --> 00:20:33.480 align:start position:0% governance auction secret icos 00:20:33.480 --> 00:20:36.290 align:start position:0% governance auction secret icos and<00:20:33.600> privacy-preserving<00:20:34.580> Dex's<00:20:35.610> and<00:20:35.820> many 00:20:36.290 --> 00:20:36.300 align:start position:0% and privacy-preserving Dex's and many 00:20:36.300 --> 00:20:38.720 align:start position:0% and privacy-preserving Dex's and many many<00:20:36.540> other<00:20:36.720> use<00:20:36.960> case<00:20:37.230> and<00:20:37.470> at<00:20:38.040> this<00:20:38.220> point<00:20:38.520> I 00:20:38.720 --> 00:20:38.730 align:start position:0% many other use case and at this point I 00:20:38.730 --> 00:20:41.690 align:start position:0% many other use case and at this point I want<00:20:38.910> to<00:20:39.000> invite<00:20:39.240> Stan<00:20:40.010> from<00:20:41.010> our<00:20:41.190> team<00:20:41.430> to 00:20:41.690 --> 00:20:41.700 align:start position:0% want to invite Stan from our team to 00:20:41.700 --> 00:20:43.580 align:start position:0% want to invite Stan from our team to actually<00:20:42.090> show<00:20:42.270> you<00:20:42.330> a<00:20:42.510> live<00:20:42.900> demo<00:20:43.320> for 00:20:43.580 --> 00:20:43.590 align:start position:0% actually show you a live demo for 00:20:43.590 --> 00:20:52.900 align:start position:0% actually show you a live demo for privacy-preserving<00:20:44.040> voting<00:20:47.330> thank<00:20:48.330> you<00:20:48.510> hi 00:20:52.900 --> 00:20:52.910 align:start position:0% 00:20:52.910 --> 00:20:55.730 align:start position:0% I'm<00:20:53.910> a<00:20:54.000> software<00:20:54.300> developer<00:20:54.390> at<00:20:54.990> enigma<00:20:55.620> and 00:20:55.730 --> 00:20:55.740 align:start position:0% I'm a software developer at enigma and 00:20:55.740 --> 00:20:57.380 align:start position:0% I'm a software developer at enigma and part<00:20:55.950> of<00:20:56.070> the<00:20:56.190> protocol<00:20:56.610> team<00:20:56.850> today<00:20:57.180> I<00:20:57.210> will 00:20:57.380 --> 00:20:57.390 align:start position:0% part of the protocol team today I will 00:20:57.390 --> 00:21:00.110 align:start position:0% part of the protocol team today I will demonstrate<00:20:57.540> a<00:20:57.900> demo<00:20:58.320> that<00:20:59.160> is<00:20:59.580> built<00:20:59.880> on<00:20:59.970> top 00:21:00.110 --> 00:21:00.120 align:start position:0% demonstrate a demo that is built on top 00:21:00.120 --> 00:21:02.060 align:start position:0% demonstrate a demo that is built on top of<00:21:00.270> our<00:21:00.360> application<00:21:00.990> but<00:21:01.020> before<00:21:01.710> I<00:21:01.740> want<00:21:01.980> to 00:21:02.060 --> 00:21:02.070 align:start position:0% of our application but before I want to 00:21:02.070 --> 00:21:03.440 align:start position:0% of our application but before I want to make<00:21:02.190> a<00:21:02.220> claim<00:21:02.580> and<00:21:02.760> kind<00:21:02.970> of<00:21:03.090> walk<00:21:03.270> you 00:21:03.440 --> 00:21:03.450 align:start position:0% make a claim and kind of walk you 00:21:03.450 --> 00:21:06.320 align:start position:0% make a claim and kind of walk you through<00:21:03.720> this<00:21:03.900> so<00:21:04.560> unchain<00:21:05.430> governance<00:21:06.000> what 00:21:06.320 --> 00:21:06.330 align:start position:0% through this so unchain governance what 00:21:06.330 --> 00:21:09.140 align:start position:0% through this so unchain governance what is<00:21:06.480> this<00:21:06.740> so<00:21:07.740> it's<00:21:08.010> kind<00:21:08.250> of<00:21:08.340> at<00:21:08.520> risk<00:21:08.820> if<00:21:09.060> you 00:21:09.140 --> 00:21:09.150 align:start position:0% is this so it's kind of at risk if you 00:21:09.150 --> 00:21:10.460 align:start position:0% is this so it's kind of at risk if you think<00:21:09.330> about<00:21:09.450> it<00:21:09.720> we're<00:21:09.960> trying<00:21:10.200> to<00:21:10.350> build 00:21:10.460 --> 00:21:10.470 align:start position:0% think about it we're trying to build 00:21:10.470 --> 00:21:11.870 align:start position:0% think about it we're trying to build this<00:21:10.680> decentralized<00:21:11.160> world<00:21:11.640> this 00:21:11.870 --> 00:21:11.880 align:start position:0% this decentralized world this 00:21:11.880 --> 00:21:14.240 align:start position:0% this decentralized world this decentralized<00:21:12.360> applications<00:21:12.750> but<00:21:13.560> the<00:21:14.010> more 00:21:14.240 --> 00:21:14.250 align:start position:0% decentralized applications but the more 00:21:14.250 --> 00:21:15.950 align:start position:0% decentralized applications but the more we<00:21:14.400> grow<00:21:14.580> the<00:21:14.880> more<00:21:15.000> decisions<00:21:15.570> we<00:21:15.780> need<00:21:15.810> to 00:21:15.950 --> 00:21:15.960 align:start position:0% we grow the more decisions we need to 00:21:15.960 --> 00:21:17.930 align:start position:0% we grow the more decisions we need to make<00:21:16.080> in<00:21:16.350> a<00:21:16.440> decentralized<00:21:16.890> environment<00:21:17.730> and 00:21:17.930 --> 00:21:17.940 align:start position:0% make in a decentralized environment and 00:21:17.940 --> 00:21:20.870 align:start position:0% make in a decentralized environment and this<00:21:18.660> means<00:21:18.870> voting<00:21:19.200> so<00:21:20.130> if<00:21:20.280> we<00:21:20.400> look<00:21:20.550> today 00:21:20.870 --> 00:21:20.880 align:start position:0% this means voting so if we look today 00:21:20.880 --> 00:21:23.240 align:start position:0% this means voting so if we look today the<00:21:21.120> common<00:21:21.510> use<00:21:21.690> case<00:21:21.900> is<00:21:22.050> for<00:21:22.290> voting<00:21:22.470> RTC 00:21:23.240 --> 00:21:23.250 align:start position:0% the common use case is for voting RTC 00:21:23.250 --> 00:21:25.400 align:start position:0% the common use case is for voting RTC ours<00:21:23.400> which<00:21:23.910> is<00:21:23.940> token<00:21:24.450> curated<00:21:24.840> registries 00:21:25.400 --> 00:21:25.410 align:start position:0% ours which is token curated registries 00:21:25.410 --> 00:21:27.680 align:start position:0% ours which is token curated registries and<00:21:25.650> dowse<00:21:26.190> by<00:21:26.820> the<00:21:26.880> way<00:21:27.030> raise<00:21:27.240> your<00:21:27.360> hand<00:21:27.570> if 00:21:27.680 --> 00:21:27.690 align:start position:0% and dowse by the way raise your hand if 00:21:27.690 --> 00:21:31.160 align:start position:0% and dowse by the way raise your hand if you<00:21:27.780> know<00:21:27.900> what<00:21:28.050> the<00:21:28.140> TCR<00:21:28.560> is<00:21:29.030> all<00:21:30.030> right<00:21:30.600> this 00:21:31.160 --> 00:21:31.170 align:start position:0% you know what the TCR is all right this 00:21:31.170 --> 00:21:34.520 align:start position:0% you know what the TCR is all right this ye<00:21:31.380> are<00:21:31.500> are<00:21:31.770> basically<00:21:32.490> a<00:21:32.730> list<00:21:33.150> a<00:21:33.570> list<00:21:34.230> of 00:21:34.520 --> 00:21:34.530 align:start position:0% ye are are basically a list a list of 00:21:34.530 --> 00:21:37.220 align:start position:0% ye are are basically a list a list of some<00:21:35.040> vendors<00:21:35.430> and<00:21:35.640> reviews<00:21:36.060> you<00:21:36.870> can<00:21:36.900> think 00:21:37.220 --> 00:21:37.230 align:start position:0% some vendors and reviews you can think 00:21:37.230 --> 00:21:39.440 align:start position:0% some vendors and reviews you can think of<00:21:37.380> a<00:21:37.470> decentralized<00:21:37.800> al<00:21:38.250> put<00:21:38.580> tokens<00:21:39.000> so<00:21:39.330> we 00:21:39.440 --> 00:21:39.450 align:start position:0% of a decentralized al put tokens so we 00:21:39.450 --> 00:21:42.590 align:start position:0% of a decentralized al put tokens so we have<00:21:39.600> TCR<00:21:40.050> and<00:21:40.350> we<00:21:40.560> have<00:21:40.770> dows<00:21:41.490> that<00:21:41.970> maybe<00:21:42.300> we 00:21:42.590 --> 00:21:42.600 align:start position:0% have TCR and we have dows that maybe we 00:21:42.600 --> 00:21:44.750 align:start position:0% have TCR and we have dows that maybe we want<00:21:42.780> to<00:21:42.930> vote<00:21:43.710> on<00:21:43.770> a<00:21:44.040> change<00:21:44.460> of<00:21:44.610> leadership 00:21:44.750 --> 00:21:44.760 align:start position:0% want to vote on a change of leadership 00:21:44.760 --> 00:21:47.210 align:start position:0% want to vote on a change of leadership or<00:21:45.270> maybe<00:21:45.480> we<00:21:45.690> want<00:21:45.840> to<00:21:45.990> fork<00:21:46.290> the<00:21:46.590> network<00:21:46.980> so 00:21:47.210 --> 00:21:47.220 align:start position:0% or maybe we want to fork the network so 00:21:47.220 --> 00:21:51.080 align:start position:0% or maybe we want to fork the network so all<00:21:47.460> of<00:21:47.580> those<00:21:47.790> require<00:21:48.630> voting<00:21:49.370> now<00:21:50.370> usually 00:21:51.080 --> 00:21:51.090 align:start position:0% all of those require voting now usually 00:21:51.090 --> 00:21:52.730 align:start position:0% all of those require voting now usually the<00:21:51.210> scheme<00:21:51.420> is<00:21:51.540> done<00:21:51.750> with<00:21:52.200> something<00:21:52.590> that 00:21:52.730 --> 00:21:52.740 align:start position:0% the scheme is done with something that 00:21:52.740 --> 00:21:54.920 align:start position:0% the scheme is done with something that is<00:21:52.860> called<00:21:53.100> commit<00:21:53.700> and<00:21:53.850> reveal<00:21:54.180> it<00:21:54.420> has<00:21:54.690> two 00:21:54.920 --> 00:21:54.930 align:start position:0% is called commit and reveal it has two 00:21:54.930 --> 00:21:57.230 align:start position:0% is called commit and reveal it has two steps<00:21:55.200> the<00:21:55.500> first<00:21:55.650> step<00:21:55.800> would<00:21:56.100> be<00:21:56.160> you<00:21:56.520> hash 00:21:57.230 --> 00:21:57.240 align:start position:0% steps the first step would be you hash 00:21:57.240 --> 00:21:59.750 align:start position:0% steps the first step would be you hash some<00:21:57.630> vote<00:21:58.140> you<00:21:58.410> commit<00:21:58.770> this<00:21:58.950> on<00:21:59.220> chain<00:21:59.550> and 00:21:59.750 --> 00:21:59.760 align:start position:0% some vote you commit this on chain and 00:21:59.760 --> 00:22:01.670 align:start position:0% some vote you commit this on chain and then<00:22:00.300> you<00:22:00.420> have<00:22:00.570> this<00:22:00.720> period<00:22:01.080> of<00:22:01.230> time<00:22:01.470> where 00:22:01.670 --> 00:22:01.680 align:start position:0% then you have this period of time where 00:22:01.680 --> 00:22:04.100 align:start position:0% then you have this period of time where you<00:22:01.770> have<00:22:01.950> to<00:22:01.980> reveal<00:22:02.730> the<00:22:03.330> real<00:22:03.480> value<00:22:03.930> on 00:22:04.100 --> 00:22:04.110 align:start position:0% you have to reveal the real value on 00:22:04.110 --> 00:22:05.480 align:start position:0% you have to reveal the real value on chain<00:22:04.410> and<00:22:04.620> validate<00:22:05.130> this 00:22:05.480 --> 00:22:05.490 align:start position:0% chain and validate this 00:22:05.490 --> 00:22:08.510 align:start position:0% chain and validate this now<00:22:06.000> there's<00:22:06.540> two<00:22:06.780> well<00:22:07.680> it's<00:22:07.890> kind<00:22:08.160> of<00:22:08.280> sucks 00:22:08.510 --> 00:22:08.520 align:start position:0% now there's two well it's kind of sucks 00:22:08.520 --> 00:22:10.610 align:start position:0% now there's two well it's kind of sucks from<00:22:08.850> a<00:22:08.970> user<00:22:09.120> perspective<00:22:09.330> because<00:22:09.930> it 00:22:10.610 --> 00:22:10.620 align:start position:0% from a user perspective because it 00:22:10.620 --> 00:22:13.910 align:start position:0% from a user perspective because it requires<00:22:11.100> you<00:22:11.310> to<00:22:11.340> remember<00:22:12.150> to<00:22:12.720> reveal<00:22:13.710> your 00:22:13.910 --> 00:22:13.920 align:start position:0% requires you to remember to reveal your 00:22:13.920 --> 00:22:14.930 align:start position:0% requires you to remember to reveal your vote<00:22:14.190> in 00:22:14.930 --> 00:22:14.940 align:start position:0% vote in 00:22:14.940 --> 00:22:17.769 align:start position:0% vote in limited<00:22:15.570> period<00:22:16.259> of<00:22:16.349> time<00:22:16.409> so<00:22:17.159> if<00:22:17.309> you<00:22:17.460> know 00:22:17.769 --> 00:22:17.779 align:start position:0% limited period of time so if you know 00:22:17.779 --> 00:22:20.749 align:start position:0% limited period of time so if you know civil<00:22:18.779> project<00:22:19.320> for<00:22:19.470> example<00:22:19.950> they<00:22:20.489> sent 00:22:20.749 --> 00:22:20.759 align:start position:0% civil project for example they sent 00:22:20.759 --> 00:22:23.359 align:start position:0% civil project for example they sent Google<00:22:21.179> calendar<00:22:21.710> reminders<00:22:22.710> to<00:22:23.009> tell<00:22:23.220> you 00:22:23.359 --> 00:22:23.369 align:start position:0% Google calendar reminders to tell you 00:22:23.369 --> 00:22:25.339 align:start position:0% Google calendar reminders to tell you hey<00:22:23.549> don't<00:22:23.849> forget<00:22:24.119> to<00:22:24.239> vote<00:22:24.479> otherwise<00:22:24.899> it's 00:22:25.339 --> 00:22:25.349 align:start position:0% hey don't forget to vote otherwise it's 00:22:25.349 --> 00:22:28.009 align:start position:0% hey don't forget to vote otherwise it's lost<00:22:25.789> and<00:22:26.789> also<00:22:27.119> it<00:22:27.239> doesn't<00:22:27.389> prevent<00:22:27.720> vote 00:22:28.009 --> 00:22:28.019 align:start position:0% lost and also it doesn't prevent vote 00:22:28.019 --> 00:22:29.989 align:start position:0% lost and also it doesn't prevent vote bribing<00:22:28.499> because<00:22:28.889> you<00:22:29.009> can<00:22:29.159> always<00:22:29.340> see<00:22:29.729> who 00:22:29.989 --> 00:22:29.999 align:start position:0% bribing because you can always see who 00:22:29.999 --> 00:22:33.739 align:start position:0% bribing because you can always see who voted<00:22:30.299> for<00:22:30.509> what<00:22:30.950> so<00:22:31.950> with<00:22:32.759> the<00:22:32.940> demo<00:22:33.570> I'm 00:22:33.739 --> 00:22:33.749 align:start position:0% voted for what so with the demo I'm 00:22:33.749 --> 00:22:35.839 align:start position:0% voted for what so with the demo I'm demonstrating<00:22:33.960> now<00:22:34.409> it's<00:22:35.070> kind<00:22:35.340> of<00:22:35.460> solved 00:22:35.839 --> 00:22:35.849 align:start position:0% demonstrating now it's kind of solved 00:22:35.849 --> 00:22:38.479 align:start position:0% demonstrating now it's kind of solved right<00:22:36.029> so<00:22:36.330> basically<00:22:36.899> the<00:22:37.200> the<00:22:37.830> schemes<00:22:38.159> today 00:22:38.479 --> 00:22:38.489 align:start position:0% right so basically the the schemes today 00:22:38.489 --> 00:22:41.299 align:start position:0% right so basically the the schemes today are<00:22:39.349> launching<00:22:40.349> voting<00:22:40.769> is<00:22:40.889> subject<00:22:41.249> to 00:22:41.299 --> 00:22:41.309 align:start position:0% are launching voting is subject to 00:22:41.309 --> 00:22:43.249 align:start position:0% are launching voting is subject to automated<00:22:42.090> bribery<00:22:42.450> attacks<00:22:42.809> you<00:22:42.960> can<00:22:43.080> have 00:22:43.249 --> 00:22:43.259 align:start position:0% automated bribery attacks you can have 00:22:43.259 --> 00:22:45.889 align:start position:0% automated bribery attacks you can have different<00:22:43.919> attacks<00:22:44.249> and<00:22:44.580> this<00:22:45.479> is<00:22:45.629> a<00:22:45.659> problem 00:22:45.889 --> 00:22:45.899 align:start position:0% different attacks and this is a problem 00:22:45.899 --> 00:22:49.009 align:start position:0% different attacks and this is a problem so<00:22:46.739> now<00:22:46.889> I'll<00:22:46.979> show<00:22:47.129> you<00:22:47.190> have<00:22:47.340> a<00:22:47.669> demo<00:22:48.239> and<00:22:48.419> if 00:22:49.009 --> 00:22:49.019 align:start position:0% so now I'll show you have a demo and if 00:22:49.019 --> 00:22:50.269 align:start position:0% so now I'll show you have a demo and if you<00:22:49.229> want<00:22:49.379> to<00:22:49.499> build<00:22:49.590> something<00:22:49.889> like<00:22:50.129> this 00:22:50.269 --> 00:22:50.279 align:start position:0% you want to build something like this 00:22:50.279 --> 00:22:51.859 align:start position:0% you want to build something like this all<00:22:50.489> you<00:22:50.549> need<00:22:50.700> to<00:22:50.820> know<00:22:50.940> is<00:22:51.090> solidity<00:22:51.570> and 00:22:51.859 --> 00:22:51.869 align:start position:0% all you need to know is solidity and 00:22:51.869 --> 00:22:53.799 align:start position:0% all you need to know is solidity and JavaScript<00:22:52.649> to<00:22:52.710> interact<00:22:53.099> with<00:22:53.249> our<00:22:53.279> network 00:22:53.799 --> 00:22:53.809 align:start position:0% JavaScript to interact with our network 00:22:53.809 --> 00:22:57.049 align:start position:0% JavaScript to interact with our network so<00:22:54.809> this<00:22:55.409> is<00:22:55.559> a<00:22:55.590> voting<00:22:55.859> application<00:22:56.639> based<00:22:56.909> on 00:22:57.049 --> 00:22:57.059 align:start position:0% so this is a voting application based on 00:22:57.059 --> 00:23:00.680 align:start position:0% so this is a voting application based on top<00:22:57.239> of<00:22:57.389> the<00:22:57.539> enigma<00:22:57.869> protocol<00:22:58.519> and<00:22:59.539> this<00:23:00.539> is 00:23:00.680 --> 00:23:00.690 align:start position:0% top of the enigma protocol and this is 00:23:00.690 --> 00:23:05.149 align:start position:0% top of the enigma protocol and this is just<00:23:01.349> in<00:23:01.499> the<00:23:01.529> browser<00:23:01.799> so<00:23:03.979> maybe<00:23:04.979> the 00:23:05.149 --> 00:23:05.159 align:start position:0% just in the browser so maybe the 00:23:05.159 --> 00:23:10.129 align:start position:0% just in the browser so maybe the internet<00:23:05.429> would<00:23:05.669> work<00:23:08.119> okay<00:23:09.119> so<00:23:09.299> basically<00:23:09.809> we 00:23:10.129 --> 00:23:10.139 align:start position:0% internet would work okay so basically we 00:23:10.139 --> 00:23:12.619 align:start position:0% internet would work okay so basically we have<00:23:10.320> here<00:23:10.710> accounts<00:23:11.639> et<00:23:11.849> really<00:23:12.269> counts<00:23:12.570> at 00:23:12.619 --> 00:23:12.629 align:start position:0% have here accounts et really counts at 00:23:12.629 --> 00:23:14.629 align:start position:0% have here accounts et really counts at our<00:23:12.779> disposal<00:23:13.379> and<00:23:13.559> they're<00:23:14.129> connected<00:23:14.519> to<00:23:14.609> a 00:23:14.629 --> 00:23:14.639 align:start position:0% our disposal and they're connected to a 00:23:14.639 --> 00:23:16.039 align:start position:0% our disposal and they're connected to a test<00:23:14.940> net<00:23:15.149> and<00:23:15.389> we'll<00:23:15.479> access<00:23:15.869> them 00:23:16.039 --> 00:23:16.049 align:start position:0% test net and we'll access them 00:23:16.049 --> 00:23:18.019 align:start position:0% test net and we'll access them programmatically<00:23:16.679> we<00:23:17.249> have<00:23:17.399> tokens<00:23:17.789> we're 00:23:18.019 --> 00:23:18.029 align:start position:0% programmatically we have tokens we're 00:23:18.029 --> 00:23:20.389 align:start position:0% programmatically we have tokens we're using<00:23:18.210> for<00:23:18.570> vote<00:23:18.809> and<00:23:19.200> you<00:23:19.710> buy<00:23:20.009> those<00:23:20.159> tokens 00:23:20.389 --> 00:23:20.399 align:start position:0% using for vote and you buy those tokens 00:23:20.399 --> 00:23:23.119 align:start position:0% using for vote and you buy those tokens and<00:23:20.700> you<00:23:20.789> use<00:23:20.970> them<00:23:21.149> to<00:23:21.869> vote<00:23:22.080> at<00:23:23.070> some 00:23:23.119 --> 00:23:23.129 align:start position:0% and you use them to vote at some 00:23:23.129 --> 00:23:26.330 align:start position:0% and you use them to vote at some exchange<00:23:23.729> rate<00:23:23.970> then<00:23:24.599> we<00:23:24.720> have<00:23:24.960> stake<00:23:25.769> tokens 00:23:26.330 --> 00:23:26.340 align:start position:0% exchange rate then we have stake tokens 00:23:26.340 --> 00:23:28.700 align:start position:0% exchange rate then we have stake tokens I<00:23:26.429> know<00:23:26.489> it's<00:23:26.759> blurred<00:23:27.029> those<00:23:27.809> take<00:23:28.049> tokens<00:23:28.470> is 00:23:28.700 --> 00:23:28.710 align:start position:0% I know it's blurred those take tokens is 00:23:28.710 --> 00:23:32.570 align:start position:0% I know it's blurred those take tokens is for<00:23:29.580> for<00:23:30.179> you<00:23:30.299> to<00:23:30.479> do<00:23:30.629> weighted<00:23:31.229> voting<00:23:31.519> so<00:23:32.519> you 00:23:32.570 --> 00:23:32.580 align:start position:0% for for you to do weighted voting so you 00:23:32.580 --> 00:23:34.609 align:start position:0% for for you to do weighted voting so you kind<00:23:33.029> of<00:23:33.119> you<00:23:33.419> can<00:23:33.599> stake<00:23:33.840> five<00:23:34.049> tokens<00:23:34.259> and 00:23:34.609 --> 00:23:34.619 align:start position:0% kind of you can stake five tokens and 00:23:34.619 --> 00:23:36.289 align:start position:0% kind of you can stake five tokens and wait<00:23:34.830> with<00:23:35.099> and<00:23:35.369> vote<00:23:35.789> with<00:23:36.029> the<00:23:36.119> weight<00:23:36.269> of 00:23:36.289 --> 00:23:36.299 align:start position:0% wait with and vote with the weight of 00:23:36.299 --> 00:23:39.619 align:start position:0% wait with and vote with the weight of five<00:23:37.340> after<00:23:38.340> we<00:23:38.489> do<00:23:38.639> this<00:23:38.849> we<00:23:39.149> need<00:23:39.179> to<00:23:39.419> buy 00:23:39.619 --> 00:23:39.629 align:start position:0% five after we do this we need to buy 00:23:39.629 --> 00:23:42.229 align:start position:0% five after we do this we need to buy tokens<00:23:40.080> so<00:23:40.200> we<00:23:40.289> will<00:23:40.440> buy<00:23:40.559> ten<00:23:40.830> tokens<00:23:41.099> and<00:23:41.669> we 00:23:42.229 --> 00:23:42.239 align:start position:0% tokens so we will buy ten tokens and we 00:23:42.239 --> 00:23:44.690 align:start position:0% tokens so we will buy ten tokens and we will<00:23:42.389> take<00:23:42.690> five<00:23:43.019> of<00:23:43.049> them<00:23:43.440> into<00:23:44.099> the<00:23:44.220> contract 00:23:44.690 --> 00:23:44.700 align:start position:0% will take five of them into the contract 00:23:44.700 --> 00:23:47.089 align:start position:0% will take five of them into the contract and<00:23:45.029> now<00:23:45.239> we<00:23:45.299> need<00:23:45.509> to<00:23:45.599> create<00:23:45.720> a<00:23:45.869> poll<00:23:46.169> so<00:23:46.979> we 00:23:47.089 --> 00:23:47.099 align:start position:0% and now we need to create a poll so we 00:23:47.099 --> 00:23:48.469 align:start position:0% and now we need to create a poll so we need<00:23:47.249> to<00:23:47.340> insert<00:23:47.609> some<00:23:47.879> bits<00:23:48.090> of<00:23:48.179> information 00:23:48.469 --> 00:23:48.479 align:start position:0% need to insert some bits of information 00:23:48.479 --> 00:23:51.169 align:start position:0% need to insert some bits of information first<00:23:49.169> of<00:23:49.320> all<00:23:49.409> we<00:23:49.529> have<00:23:49.649> quorum<00:23:50.159> so<00:23:50.549> we<00:23:51.059> will 00:23:51.169 --> 00:23:51.179 align:start position:0% first of all we have quorum so we will 00:23:51.179 --> 00:23:53.570 align:start position:0% first of all we have quorum so we will choose<00:23:51.330> a<00:23:51.389> quorum<00:23:51.840> of<00:23:52.049> yes<00:23:52.590> votes<00:23:52.919> divided<00:23:53.460> by 00:23:53.570 --> 00:23:53.580 align:start position:0% choose a quorum of yes votes divided by 00:23:53.580 --> 00:23:55.369 align:start position:0% choose a quorum of yes votes divided by the<00:23:53.639> number<00:23:53.820> of<00:23:54.029> total<00:23:54.330> votes<00:23:54.779> should<00:23:55.200> be 00:23:55.369 --> 00:23:55.379 align:start position:0% the number of total votes should be 00:23:55.379 --> 00:23:58.549 align:start position:0% the number of total votes should be bigger<00:23:55.559> than<00:23:55.769> 50%<00:23:56.519> and<00:23:57.200> it's<00:23:58.200> a<00:23:58.259> simple 00:23:58.549 --> 00:23:58.559 align:start position:0% bigger than 50% and it's a simple 00:23:58.559 --> 00:24:01.249 align:start position:0% bigger than 50% and it's a simple majority<00:23:58.679> so<00:23:59.129> if<00:23:59.249> we<00:23:59.399> have<00:23:59.580> more<00:23:59.940> than<00:24:00.149> 50<00:24:00.389> the 00:24:01.249 --> 00:24:01.259 align:start position:0% majority so if we have more than 50 the 00:24:01.259 --> 00:24:03.799 align:start position:0% majority so if we have more than 50 the poll<00:24:01.440> has<00:24:01.619> passed<00:24:01.859> then<00:24:02.639> we<00:24:02.789> need<00:24:02.970> to<00:24:03.090> ask<00:24:03.570> a 00:24:03.799 --> 00:24:03.809 align:start position:0% poll has passed then we need to ask a 00:24:03.809 --> 00:24:06.440 align:start position:0% poll has passed then we need to ask a question<00:24:04.289> so<00:24:04.619> is<00:24:05.070> privacy<00:24:05.580> important<00:24:06.210> and 00:24:06.440 --> 00:24:06.450 align:start position:0% question so is privacy important and 00:24:06.450 --> 00:24:09.529 align:start position:0% question so is privacy important and voting<00:24:06.899> and<00:24:07.109> very<00:24:07.739> topical<00:24:08.220> and<00:24:08.849> then<00:24:09.269> we<00:24:09.389> need 00:24:09.529 --> 00:24:09.539 align:start position:0% voting and very topical and then we need 00:24:09.539 --> 00:24:11.659 align:start position:0% voting and very topical and then we need to<00:24:09.629> add<00:24:09.749> some<00:24:09.989> period<00:24:10.379> we'll<00:24:10.619> say<00:24:10.859> 60<00:24:11.249> seconds 00:24:11.659 --> 00:24:11.669 align:start position:0% to add some period we'll say 60 seconds 00:24:11.669 --> 00:24:14.930 align:start position:0% to add some period we'll say 60 seconds so<00:24:11.909> we<00:24:11.999> have<00:24:12.119> 60<00:24:12.570> seconds<00:24:12.899> to<00:24:13.049> vote<00:24:13.700> go<00:24:14.700> ahead 00:24:14.930 --> 00:24:14.940 align:start position:0% so we have 60 seconds to vote go ahead 00:24:14.940 --> 00:24:16.999 align:start position:0% so we have 60 seconds to vote go ahead create<00:24:15.239> the<00:24:15.359> poll<00:24:15.599> and<00:24:15.960> then<00:24:16.259> users<00:24:16.590> can<00:24:16.799> start 00:24:16.999 --> 00:24:17.009 align:start position:0% create the poll and then users can start 00:24:17.009 --> 00:24:19.249 align:start position:0% create the poll and then users can start voting<00:24:17.460> so<00:24:17.639> the<00:24:17.759> first<00:24:18.029> user<00:24:18.299> will<00:24:18.629> go<00:24:18.840> in<00:24:19.049> and 00:24:19.249 --> 00:24:19.259 align:start position:0% voting so the first user will go in and 00:24:19.259 --> 00:24:23.119 align:start position:0% voting so the first user will go in and say<00:24:19.919> stake<00:24:20.820> 5<00:24:21.149> and<00:24:21.419> say<00:24:21.570> yes<00:24:21.950> privacy<00:24:22.950> is 00:24:23.119 --> 00:24:23.129 align:start position:0% say stake 5 and say yes privacy is 00:24:23.129 --> 00:24:26.089 align:start position:0% say stake 5 and say yes privacy is important<00:24:23.989> the<00:24:24.989> timer<00:24:25.229> keeps<00:24:25.529> growing<00:24:25.950> and 00:24:26.089 --> 00:24:26.099 align:start position:0% important the timer keeps growing and 00:24:26.099 --> 00:24:28.200 align:start position:0% important the timer keeps growing and most<00:24:26.700> importantly<00:24:27.269> is<00:24:27.389> the<00:24:27.539> result 00:24:28.200 --> 00:24:28.210 align:start position:0% most importantly is the result 00:24:28.210 --> 00:24:30.300 align:start position:0% most importantly is the result you<00:24:28.270> can<00:24:28.420> see<00:24:28.570> in<00:24:28.630> the<00:24:28.690> console<00:24:29.140> it's<00:24:29.770> saved 00:24:30.300 --> 00:24:30.310 align:start position:0% you can see in the console it's saved 00:24:30.310 --> 00:24:33.540 align:start position:0% you can see in the console it's saved encrypted<00:24:31.150> in<00:24:31.600> aetherium<00:24:32.410> so<00:24:32.830> just<00:24:33.430> to 00:24:33.540 --> 00:24:33.550 align:start position:0% encrypted in aetherium so just to 00:24:33.550 --> 00:24:36.660 align:start position:0% encrypted in aetherium so just to reiterate<00:24:33.700> no<00:24:34.300> one<00:24:34.780> no<00:24:35.200> third-party<00:24:35.670> sees 00:24:36.660 --> 00:24:36.670 align:start position:0% reiterate no one no third-party sees 00:24:36.670 --> 00:24:39.260 align:start position:0% reiterate no one no third-party sees this<00:24:36.850> information<00:24:37.540> and<00:24:37.720> who<00:24:38.170> wanted<00:24:38.620> for<00:24:38.860> what 00:24:39.260 --> 00:24:39.270 align:start position:0% this information and who wanted for what 00:24:39.270 --> 00:24:42.300 align:start position:0% this information and who wanted for what so<00:24:40.270> this<00:24:40.390> is<00:24:40.540> an<00:24:40.660> important<00:24:41.080> aspect<00:24:41.230> and<00:24:41.920> then 00:24:42.300 --> 00:24:42.310 align:start position:0% so this is an important aspect and then 00:24:42.310 --> 00:24:43.830 align:start position:0% so this is an important aspect and then we<00:24:42.430> need<00:24:42.580> to<00:24:42.700> vote<00:24:42.850> again<00:24:43.180> right 00:24:43.830 --> 00:24:43.840 align:start position:0% we need to vote again right 00:24:43.840 --> 00:24:47.910 align:start position:0% we need to vote again right so<00:24:45.180> after<00:24:46.180> this<00:24:46.390> happens<00:24:46.720> we'll<00:24:47.440> switch<00:24:47.740> an 00:24:47.910 --> 00:24:47.920 align:start position:0% so after this happens we'll switch an 00:24:47.920 --> 00:24:49.410 align:start position:0% so after this happens we'll switch an account<00:24:48.190> this<00:24:48.430> is<00:24:48.490> all<00:24:48.790> Testament<00:24:49.270> of<00:24:49.390> course 00:24:49.410 --> 00:24:49.420 align:start position:0% account this is all Testament of course 00:24:49.420 --> 00:24:51.390 align:start position:0% account this is all Testament of course but<00:24:49.810> this<00:24:49.960> is<00:24:50.080> why<00:24:50.230> it<00:24:50.290> kind<00:24:50.920> of<00:24:51.070> happens 00:24:51.390 --> 00:24:51.400 align:start position:0% but this is why it kind of happens 00:24:51.400 --> 00:24:53.460 align:start position:0% but this is why it kind of happens behind<00:24:51.580> the<00:24:51.790> scene<00:24:52.060> so<00:24:52.870> we'll<00:24:53.080> take<00:24:53.290> three 00:24:53.460 --> 00:24:53.470 align:start position:0% behind the scene so we'll take three 00:24:53.470 --> 00:24:55.620 align:start position:0% behind the scene so we'll take three tokens<00:24:53.800> and<00:24:54.160> we<00:24:54.280> say<00:24:54.490> nope<00:24:54.760> privacy<00:24:55.510> is<00:24:55.570> not 00:24:55.620 --> 00:24:55.630 align:start position:0% tokens and we say nope privacy is not 00:24:55.630 --> 00:24:58.410 align:start position:0% tokens and we say nope privacy is not important<00:24:56.520> again<00:24:57.520> you<00:24:57.640> can<00:24:57.820> see<00:24:57.970> the<00:24:58.090> result 00:24:58.410 --> 00:24:58.420 align:start position:0% important again you can see the result 00:24:58.420 --> 00:25:00.390 align:start position:0% important again you can see the result is<00:24:58.540> completely<00:24:59.110> encrypted<00:24:59.380> and<00:24:59.800> this<00:25:00.220> is<00:25:00.310> how 00:25:00.390 --> 00:25:00.400 align:start position:0% is completely encrypted and this is how 00:25:00.400 --> 00:25:04.500 align:start position:0% is completely encrypted and this is how we<00:25:00.460> start<00:25:00.820> on<00:25:00.940> chain<00:25:01.210> um<00:25:01.810> so<00:25:02.140> again<00:25:03.180> at<00:25:04.180> the<00:25:04.390> end 00:25:04.500 --> 00:25:04.510 align:start position:0% we start on chain um so again at the end 00:25:04.510 --> 00:25:06.690 align:start position:0% we start on chain um so again at the end of<00:25:04.660> this<00:25:04.780> timer<00:25:05.140> a<00:25:05.500> very<00:25:05.950> important<00:25:06.490> function 00:25:06.690 --> 00:25:06.700 align:start position:0% of this timer a very important function 00:25:06.700 --> 00:25:09.090 align:start position:0% of this timer a very important function will<00:25:07.450> happen<00:25:07.870> on<00:25:08.050> our<00:25:08.320> side<00:25:08.680> this<00:25:08.890> will 00:25:09.090 --> 00:25:09.100 align:start position:0% will happen on our side this will 00:25:09.100 --> 00:25:11.730 align:start position:0% will happen on our side this will trigger<00:25:09.400> a<00:25:09.790> computation<00:25:10.750> the<00:25:11.050> nodes<00:25:11.350> on<00:25:11.590> our 00:25:11.730 --> 00:25:11.740 align:start position:0% trigger a computation the nodes on our 00:25:11.740 --> 00:25:14.280 align:start position:0% trigger a computation the nodes on our network<00:25:12.160> will<00:25:12.460> fetch<00:25:12.910> the<00:25:13.240> state<00:25:13.960> fro 00:25:14.280 --> 00:25:14.290 align:start position:0% network will fetch the state fro 00:25:14.290 --> 00:25:16.940 align:start position:0% network will fetch the state fro material<00:25:14.830> compute<00:25:15.820> over<00:25:16.030> the<00:25:16.360> encrypted<00:25:16.660> data 00:25:16.940 --> 00:25:16.950 align:start position:0% material compute over the encrypted data 00:25:16.950 --> 00:25:19.860 align:start position:0% material compute over the encrypted data tightly<00:25:17.950> the<00:25:18.100> results<00:25:18.670> commit<00:25:19.240> them<00:25:19.420> back<00:25:19.630> on 00:25:19.860 --> 00:25:19.870 align:start position:0% tightly the results commit them back on 00:25:19.870 --> 00:25:22.080 align:start position:0% tightly the results commit them back on chain<00:25:20.170> and<00:25:20.440> modify<00:25:20.980> the<00:25:21.040> contract<00:25:21.460> state<00:25:21.850> on 00:25:22.080 --> 00:25:22.090 align:start position:0% chain and modify the contract state on 00:25:22.090 --> 00:25:25.680 align:start position:0% chain and modify the contract state on etherium<00:25:23.430> yeah<00:25:24.430> we<00:25:24.640> can<00:25:24.790> see<00:25:25.030> that<00:25:25.330> success 00:25:25.680 --> 00:25:25.690 align:start position:0% etherium yeah we can see that success 00:25:25.690 --> 00:25:27.720 align:start position:0% etherium yeah we can see that success for<00:25:26.320> those<00:25:26.470> of<00:25:26.620> you<00:25:26.680> who<00:25:26.830> keep<00:25:27.010> account<00:25:27.280> we<00:25:27.550> had 00:25:27.720 --> 00:25:27.730 align:start position:0% for those of you who keep account we had 00:25:27.730 --> 00:25:30.000 align:start position:0% for those of you who keep account we had five<00:25:28.150> vote<00:25:28.390> saying<00:25:28.720> yes<00:25:28.930> really<00:25:29.470> won't<00:25:29.680> saying 00:25:30.000 --> 00:25:30.010 align:start position:0% five vote saying yes really won't saying 00:25:30.010 --> 00:25:34.260 align:start position:0% five vote saying yes really won't saying no<00:25:30.160> so<00:25:30.370> privacy<00:25:31.180> is<00:25:31.270> important<00:25:31.980> and<00:25:32.980> then<00:25:33.270> on 00:25:34.260 --> 00:25:34.270 align:start position:0% no so privacy is important and then on 00:25:34.270 --> 00:25:36.240 align:start position:0% no so privacy is important and then on the<00:25:34.450> front<00:25:34.540> end<00:25:34.900> we<00:25:35.110> have<00:25:35.290> this<00:25:35.530> event 00:25:36.240 --> 00:25:36.250 align:start position:0% the front end we have this event 00:25:36.250 --> 00:25:39.120 align:start position:0% the front end we have this event listener<00:25:36.730> just<00:25:37.150> simply<00:25:37.840> listens<00:25:38.170> to<00:25:38.380> an<00:25:38.710> event 00:25:39.120 --> 00:25:39.130 align:start position:0% listener just simply listens to an event 00:25:39.130 --> 00:25:40.770 align:start position:0% listener just simply listens to an event on<00:25:39.280> the<00:25:39.400> tearoom<00:25:39.730> account<00:25:40.120> on<00:25:40.390> the<00:25:40.570> aterial 00:25:40.770 --> 00:25:40.780 align:start position:0% on the tearoom account on the aterial 00:25:40.780 --> 00:25:42.990 align:start position:0% on the tearoom account on the aterial network<00:25:41.260> and<00:25:41.470> you<00:25:41.920> know<00:25:42.040> once<00:25:42.430> the<00:25:42.670> poll<00:25:42.880> is 00:25:42.990 --> 00:25:43.000 align:start position:0% network and you know once the poll is 00:25:43.000 --> 00:25:50.240 align:start position:0% network and you know once the poll is ended<00:25:43.360> it<00:25:43.750> can<00:25:44.050> update<00:25:44.230> the<00:25:44.470> UI<00:25:44.670> that's 00:25:50.240 --> 00:25:50.250 align:start position:0% 00:25:50.250 --> 00:25:52.650 align:start position:0% alright<00:25:51.250> so<00:25:51.430> I<00:25:51.460> know<00:25:51.550> we<00:25:51.730> run<00:25:51.850> out<00:25:52.030> of<00:25:52.150> time<00:25:52.240> but 00:25:52.650 --> 00:25:52.660 align:start position:0% alright so I know we run out of time but 00:25:52.660 --> 00:25:56.580 align:start position:0% alright so I know we run out of time but I<00:25:52.720> just<00:25:52.930> want<00:25:53.170> to<00:25:53.290> just<00:25:54.010> want<00:25:54.160> to<00:25:55.110> finalize<00:25:56.110> and 00:25:56.580 --> 00:25:56.590 align:start position:0% I just want to just want to finalize and 00:25:56.590 --> 00:25:59.580 align:start position:0% I just want to just want to finalize and tell<00:25:56.950> you<00:25:57.040> some<00:25:57.220> exciting<00:25:57.340> things<00:25:58.590> secret 00:25:59.580 --> 00:25:59.590 align:start position:0% tell you some exciting things secret 00:25:59.590 --> 00:26:02.130 align:start position:0% tell you some exciting things secret voting<00:25:59.950> the<00:26:00.160> demo<00:26:00.340> just<00:26:00.640> saw<00:26:01.240> is<00:26:01.570> not<00:26:01.810> just<00:26:02.050> a 00:26:02.130 --> 00:26:02.140 align:start position:0% voting the demo just saw is not just a 00:26:02.140 --> 00:26:04.530 align:start position:0% voting the demo just saw is not just a demo<00:26:02.470> it's<00:26:02.770> actually<00:26:03.220> being<00:26:03.430> produced<00:26:03.910> by 00:26:04.530 --> 00:26:04.540 align:start position:0% demo it's actually being produced by 00:26:04.540 --> 00:26:07.080 align:start position:0% demo it's actually being produced by very<00:26:04.780> reputable<00:26:05.020> companies<00:26:05.770> in<00:26:05.920> the<00:26:06.010> space<00:26:06.250> we 00:26:07.080 --> 00:26:07.090 align:start position:0% very reputable companies in the space we 00:26:07.090 --> 00:26:09.780 align:start position:0% very reputable companies in the space we have<00:26:07.240> Aragon<00:26:07.780> and<00:26:08.140> ocean<00:26:08.500> protocols<00:26:08.950> actually 00:26:09.780 --> 00:26:09.790 align:start position:0% have Aragon and ocean protocols actually 00:26:09.790 --> 00:26:11.670 align:start position:0% have Aragon and ocean protocols actually building<00:26:10.150> privacy<00:26:10.660> preserving<00:26:10.810> voting<00:26:11.380> on 00:26:11.670 --> 00:26:11.680 align:start position:0% building privacy preserving voting on 00:26:11.680 --> 00:26:13.980 align:start position:0% building privacy preserving voting on ethereal<00:26:12.160> right<00:26:12.310> now<00:26:12.520> you<00:26:13.390> can<00:26:13.570> actually<00:26:13.720> look 00:26:13.980 --> 00:26:13.990 align:start position:0% ethereal right now you can actually look 00:26:13.990 --> 00:26:16.220 align:start position:0% ethereal right now you can actually look at<00:26:14.140> the<00:26:14.200> code<00:26:14.380> if<00:26:14.620> you<00:26:14.740> want<00:26:14.890> it's<00:26:15.160> live 00:26:16.220 --> 00:26:16.230 align:start position:0% at the code if you want it's live 00:26:16.230 --> 00:26:19.500 align:start position:0% at the code if you want it's live another<00:26:17.230> amazing<00:26:17.650> example<00:26:18.160> is<00:26:18.510> machine 00:26:19.500 --> 00:26:19.510 align:start position:0% another amazing example is machine 00:26:19.510 --> 00:26:21.900 align:start position:0% another amazing example is machine learning<00:26:19.540> over<00:26:19.930> encrypted<00:26:20.470> data<00:26:20.680> so<00:26:21.430> eggs<00:26:21.640> in 00:26:21.900 --> 00:26:21.910 align:start position:0% learning over encrypted data so eggs in 00:26:21.910 --> 00:26:23.670 align:start position:0% learning over encrypted data so eggs in chain<00:26:22.150> was<00:26:22.480> working<00:26:22.840> with<00:26:22.960> us<00:26:22.990> has 00:26:23.670 --> 00:26:23.680 align:start position:0% chain was working with us has 00:26:23.680 --> 00:26:26.220 align:start position:0% chain was working with us has implemented<00:26:24.310> a<00:26:24.790> scheme<00:26:25.180> where<00:26:25.810> they<00:26:25.960> can 00:26:26.220 --> 00:26:26.230 align:start position:0% implemented a scheme where they can 00:26:26.230 --> 00:26:28.770 align:start position:0% implemented a scheme where they can classify<00:26:27.100> our<00:26:27.550> credit<00:26:27.880> worthiness<00:26:28.210> that's 00:26:28.770 --> 00:26:28.780 align:start position:0% classify our credit worthiness that's 00:26:28.780 --> 00:26:30.540 align:start position:0% classify our credit worthiness that's what<00:26:28.960> the<00:26:29.050> plain<00:26:29.320> he<00:26:29.350> represents<00:26:30.310> in<00:26:30.400> the 00:26:30.540 --> 00:26:30.550 align:start position:0% what the plain he represents in the 00:26:30.550 --> 00:26:33.540 align:start position:0% what the plain he represents in the diagram<00:26:31.030> and<00:26:31.500> they<00:26:32.500> can<00:26:32.740> keep<00:26:32.980> the<00:26:33.250> actual 00:26:33.540 --> 00:26:33.550 align:start position:0% diagram and they can keep the actual 00:26:33.550 --> 00:26:35.070 align:start position:0% diagram and they can keep the actual weights<00:26:33.910> of<00:26:34.150> the<00:26:34.270> model<00:26:34.600> completely 00:26:35.070 --> 00:26:35.080 align:start position:0% weights of the model completely 00:26:35.080 --> 00:26:37.170 align:start position:0% weights of the model completely encrypted<00:26:35.470> so<00:26:36.190> they<00:26:36.310> can<00:26:36.490> hide<00:26:36.730> the<00:26:36.880> model 00:26:37.170 --> 00:26:37.180 align:start position:0% encrypted so they can hide the model 00:26:37.180 --> 00:26:39.150 align:start position:0% encrypted so they can hide the model from<00:26:37.270> the<00:26:37.420> network<00:26:37.780> and<00:26:37.990> still<00:26:38.470> continue<00:26:39.040> to 00:26:39.150 --> 00:26:39.160 align:start position:0% from the network and still continue to 00:26:39.160 --> 00:26:40.430 align:start position:0% from the network and still continue to train<00:26:39.430> it 00:26:40.430 --> 00:26:40.440 align:start position:0% train it 00:26:40.440 --> 00:26:42.170 align:start position:0% train it and<00:26:40.590> get<00:26:40.830> better<00:26:41.070> predictions<00:26:41.730> on<00:26:41.940> whether 00:26:42.170 --> 00:26:42.180 align:start position:0% and get better predictions on whether 00:26:42.180 --> 00:26:46.840 align:start position:0% and get better predictions on whether people<00:26:42.420> credits<00:26:43.020> is<00:26:43.230> worthless<00:26:43.560> or<00:26:43.950> not 00:26:46.840 --> 00:26:46.850 align:start position:0% 00:26:46.850 --> 00:26:50.090 align:start position:0% enigma<00:26:47.850> is<00:26:48.120> live<00:26:48.600> today<00:26:48.840> you<00:26:49.410> can<00:26:49.590> work<00:26:49.830> on<00:26:49.980> it 00:26:50.090 --> 00:26:50.100 align:start position:0% enigma is live today you can work on it 00:26:50.100 --> 00:26:51.800 align:start position:0% enigma is live today you can work on it you<00:26:50.220> can<00:26:50.370> build<00:26:50.610> on<00:26:50.730> it<00:26:50.850> just<00:26:51.150> go<00:26:51.300> to<00:26:51.330> enigma 00:26:51.800 --> 00:26:51.810 align:start position:0% you can build on it just go to enigma 00:26:51.810 --> 00:26:55.070 align:start position:0% you can build on it just go to enigma dot<00:26:51.990> KO<00:26:52.290> /<00:26:52.350> protocol<00:26:53.190> and<00:26:53.460> start<00:26:54.090> building<00:26:54.330> we 00:26:55.070 --> 00:26:55.080 align:start position:0% dot KO / protocol and start building we 00:26:55.080 --> 00:26:56.960 align:start position:0% dot KO / protocol and start building we have<00:26:55.200> documentation<00:26:55.800> we're<00:26:56.310> open<00:26:56.700> to 00:26:56.960 --> 00:26:56.970 align:start position:0% have documentation we're open to 00:26:56.970 --> 00:26:58.340 align:start position:0% have documentation we're open to feedback<00:26:57.120> the<00:26:57.600> code<00:26:57.810> is<00:26:57.990> open<00:26:58.140> source 00:26:58.340 --> 00:26:58.350 align:start position:0% feedback the code is open source 00:26:58.350 --> 00:27:01.430 align:start position:0% feedback the code is open source everything<00:26:58.950> you<00:26:59.610> need<00:26:59.760> is<00:26:59.880> there<00:27:00.230> but<00:27:01.230> what's 00:27:01.430 --> 00:27:01.440 align:start position:0% everything you need is there but what's 00:27:01.440 --> 00:27:03.350 align:start position:0% everything you need is there but what's even<00:27:01.530> more<00:27:01.710> exciting<00:27:02.220> that<00:27:03.000> I<00:27:03.030> want<00:27:03.270> to 00:27:03.350 --> 00:27:03.360 align:start position:0% even more exciting that I want to 00:27:03.360 --> 00:27:06.440 align:start position:0% even more exciting that I want to announce<00:27:03.570> today<00:27:04.020> is<00:27:04.320> eggs<00:27:05.090> enigma<00:27:06.090> growth 00:27:06.440 --> 00:27:06.450 align:start position:0% announce today is eggs enigma growth 00:27:06.450 --> 00:27:09.290 align:start position:0% announce today is eggs enigma growth grants<00:27:07.140> enigma<00:27:07.950> growth<00:27:08.160> grants<00:27:08.670> is<00:27:08.790> really 00:27:09.290 --> 00:27:09.300 align:start position:0% grants enigma growth grants is really 00:27:09.300 --> 00:27:12.200 align:start position:0% grants enigma growth grants is really the<00:27:09.450> best<00:27:09.720> way<00:27:10.080> for<00:27:10.890> you<00:27:11.040> to<00:27:11.340> become<00:27:11.670> involved 00:27:12.200 --> 00:27:12.210 align:start position:0% the best way for you to become involved 00:27:12.210 --> 00:27:15.290 align:start position:0% the best way for you to become involved is<00:27:12.480> the<00:27:12.630> new<00:27:12.870> emerging<00:27:13.470> ecosystem<00:27:14.300> we're 00:27:15.290 --> 00:27:15.300 align:start position:0% is the new emerging ecosystem we're 00:27:15.300 --> 00:27:16.490 align:start position:0% is the new emerging ecosystem we're going<00:27:15.480> to<00:27:15.570> work<00:27:15.780> together<00:27:15.990> with<00:27:16.380> the<00:27:16.470> people 00:27:16.490 --> 00:27:16.500 align:start position:0% going to work together with the people 00:27:16.500 --> 00:27:18.770 align:start position:0% going to work together with the people who<00:27:16.830> apply<00:27:17.130> to<00:27:17.160> grounds<00:27:17.670> we're<00:27:18.240> going<00:27:18.450> to<00:27:18.570> fund 00:27:18.770 --> 00:27:18.780 align:start position:0% who apply to grounds we're going to fund 00:27:18.780 --> 00:27:19.220 align:start position:0% who apply to grounds we're going to fund these 00:27:19.220 --> 00:27:19.230 align:start position:0% these 00:27:19.230 --> 00:27:21.560 align:start position:0% these we're<00:27:19.530> going<00:27:19.710> to<00:27:19.800> help<00:27:19.980> this<00:27:20.100> evolve<00:27:20.490> and<00:27:20.730> this 00:27:21.560 --> 00:27:21.570 align:start position:0% we're going to help this evolve and this 00:27:21.570 --> 00:27:23.450 align:start position:0% we're going to help this evolve and this includes<00:27:22.020> a<00:27:22.140> lot<00:27:22.350> of<00:27:22.380> the<00:27:22.590> core<00:27:22.980> things<00:27:23.310> that 00:27:23.450 --> 00:27:23.460 align:start position:0% includes a lot of the core things that 00:27:23.460 --> 00:27:27.530 align:start position:0% includes a lot of the core things that we<00:27:23.700> need<00:27:23.850> to<00:27:23.880> make<00:27:24.210> the<00:27:24.870> enigma<00:27:25.800> platform<00:27:26.540> an 00:27:27.530 --> 00:27:27.540 align:start position:0% we need to make the enigma platform an 00:27:27.540 --> 00:27:30.680 align:start position:0% we need to make the enigma platform an independent<00:27:28.350> thriving<00:27:28.830> ecosystem<00:27:29.700> now 00:27:30.680 --> 00:27:30.690 align:start position:0% independent thriving ecosystem now 00:27:30.690 --> 00:27:33.680 align:start position:0% independent thriving ecosystem now enigma<00:27:31.290> is<00:27:31.790> exploding<00:27:32.790> right<00:27:32.820> now<00:27:33.000> it's 00:27:33.680 --> 00:27:33.690 align:start position:0% enigma is exploding right now it's 00:27:33.690 --> 00:27:35.810 align:start position:0% enigma is exploding right now it's growing<00:27:34.080> very<00:27:34.230> fast<00:27:34.590> and<00:27:35.130> there<00:27:35.490> are<00:27:35.520> many 00:27:35.810 --> 00:27:35.820 align:start position:0% growing very fast and there are many 00:27:35.820 --> 00:27:38.170 align:start position:0% growing very fast and there are many ways<00:27:36.060> for<00:27:36.090> you<00:27:36.360> to<00:27:36.480> get<00:27:36.630> involved<00:27:37.110> beyond<00:27:37.830> eggs 00:27:38.170 --> 00:27:38.180 align:start position:0% ways for you to get involved beyond eggs 00:27:38.180 --> 00:27:41.620 align:start position:0% ways for you to get involved beyond eggs whether<00:27:39.180> you're<00:27:39.390> a<00:27:39.450> developer<00:27:39.630> or<00:27:40.380> a<00:27:40.710> user<00:27:41.070> or 00:27:41.620 --> 00:27:41.630 align:start position:0% whether you're a developer or a user or 00:27:41.630 --> 00:27:44.420 align:start position:0% whether you're a developer or a user or you<00:27:42.630> want<00:27:42.810> to<00:27:42.900> just<00:27:43.050> run<00:27:43.260> node<00:27:43.560> and<00:27:43.830> stake<00:27:44.130> and 00:27:44.420 --> 00:27:44.430 align:start position:0% you want to just run node and stake and 00:27:44.430 --> 00:27:46.610 align:start position:0% you want to just run node and stake and earn<00:27:44.580> rewards<00:27:44.610> all<00:27:45.510> of<00:27:45.930> the<00:27:46.020> information<00:27:46.590> that 00:27:46.610 --> 00:27:46.620 align:start position:0% earn rewards all of the information that 00:27:46.620 --> 00:27:50.120 align:start position:0% earn rewards all of the information that you<00:27:46.860> need<00:27:46.890> is<00:27:47.310> packed<00:27:47.910> on<00:27:48.120> this<00:27:48.270> slide<00:27:49.130> thank 00:27:50.120 --> 00:27:50.130 align:start position:0% you need is packed on this slide thank 00:27:50.130 --> 00:28:01.860 align:start position:0% you need is packed on this slide thank you<00:27:50.220> very<00:27:50.370> much 00:28:01.860 --> 00:28:01.870 align:start position:0% 00:28:01.870 --> 00:28:03.930 align:start position:0% you