WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.230 align:start position:0% [Music] 00:00:09.230 --> 00:00:09.240 align:start position:0% [Music] 00:00:09.240 --> 00:00:13.509 align:start position:0% [Music] thank<00:00:09.400> you<00:00:09.960> for<00:00:10.360> the<00:00:11.000> introduction<00:00:12.400> um<00:00:13.400> that 00:00:13.509 --> 00:00:13.519 align:start position:0% thank you for the introduction um that 00:00:13.519 --> 00:00:16.189 align:start position:0% thank you for the introduction um that was<00:00:13.880> quite<00:00:14.639> I<00:00:14.759> think<00:00:14.960> it's<00:00:15.639> uh<00:00:15.799> I<00:00:16.000> should<00:00:16.119> have 00:00:16.189 --> 00:00:16.199 align:start position:0% was quite I think it's uh I should have 00:00:16.199 --> 00:00:17.910 align:start position:0% was quite I think it's uh I should have wrote<00:00:16.440> to<00:00:16.560> someone<00:00:16.840> earlier<00:00:17.240> to<00:00:17.400> ask<00:00:17.640> if<00:00:17.800> I 00:00:17.910 --> 00:00:17.920 align:start position:0% wrote to someone earlier to ask if I 00:00:17.920 --> 00:00:19.990 align:start position:0% wrote to someone earlier to ask if I don't<00:00:18.199> go<00:00:18.439> after<00:00:18.760> Amir<00:00:19.320> because<00:00:19.640> like<00:00:19.840> it's 00:00:19.990 --> 00:00:20.000 align:start position:0% don't go after Amir because like it's 00:00:20.000 --> 00:00:21.550 align:start position:0% don't go after Amir because like it's really<00:00:20.240> hard<00:00:20.400> to<00:00:20.560> follow<00:00:20.880> somebody<00:00:21.160> who's<00:00:21.400> so 00:00:21.550 --> 00:00:21.560 align:start position:0% really hard to follow somebody who's so 00:00:21.560 --> 00:00:23.710 align:start position:0% really hard to follow somebody who's so full<00:00:21.760> of<00:00:21.920> energy<00:00:22.680> and<00:00:22.800> so<00:00:23.000> full<00:00:23.199> of<00:00:23.359> like<00:00:23.519> good 00:00:23.710 --> 00:00:23.720 align:start position:0% full of energy and so full of like good 00:00:23.720 --> 00:00:25.710 align:start position:0% full of energy and so full of like good ideas<00:00:24.199> and<00:00:24.519> yeah<00:00:24.720> principles<00:00:25.199> that<00:00:25.359> we<00:00:25.480> should 00:00:25.710 --> 00:00:25.720 align:start position:0% ideas and yeah principles that we should 00:00:25.720 --> 00:00:26.990 align:start position:0% ideas and yeah principles that we should follow<00:00:26.039> more<00:00:26.199> and 00:00:26.990 --> 00:00:27.000 align:start position:0% follow more and 00:00:27.000 --> 00:00:30.310 align:start position:0% follow more and more<00:00:28.000> um<00:00:28.279> so<00:00:28.560> yeah<00:00:28.720> I<00:00:28.800> will<00:00:28.960> talk<00:00:29.160> to<00:00:29.320> you<00:00:29.560> about 00:00:30.310 --> 00:00:30.320 align:start position:0% more um so yeah I will talk to you about 00:00:30.320 --> 00:00:33.030 align:start position:0% more um so yeah I will talk to you about MPC<00:00:31.160> basically<00:00:31.840> um<00:00:32.000> some<00:00:32.320> some<00:00:32.480> of<00:00:32.599> the<00:00:32.719> tools 00:00:33.030 --> 00:00:33.040 align:start position:0% MPC basically um some some of the tools 00:00:33.040 --> 00:00:34.910 align:start position:0% MPC basically um some some of the tools that<00:00:33.200> can<00:00:33.360> provide<00:00:33.719> some<00:00:33.840> of<00:00:34.000> the<00:00:34.239> Privacy 00:00:34.910 --> 00:00:34.920 align:start position:0% that can provide some of the Privacy 00:00:34.920 --> 00:00:36.910 align:start position:0% that can provide some of the Privacy expectations<00:00:35.600> that<00:00:35.760> the<00:00:35.879> cipher<00:00:36.239> Punk<00:00:36.480> values 00:00:36.910 --> 00:00:36.920 align:start position:0% expectations that the cipher Punk values 00:00:36.920 --> 00:00:39.990 align:start position:0% expectations that the cipher Punk values might<00:00:37.320> actually<00:00:37.600> benefit<00:00:38.320> from<00:00:39.320> um<00:00:39.680> I'll<00:00:39.879> give 00:00:39.990 --> 00:00:40.000 align:start position:0% might actually benefit from um I'll give 00:00:40.000 --> 00:00:41.990 align:start position:0% might actually benefit from um I'll give you<00:00:40.120> an<00:00:40.280> educational<00:00:40.760> tour<00:00:41.000> of<00:00:41.120> MPC<00:00:41.640> so<00:00:41.840> from 00:00:41.990 --> 00:00:42.000 align:start position:0% you an educational tour of MPC so from 00:00:42.000 --> 00:00:44.709 align:start position:0% you an educational tour of MPC so from auctions<00:00:42.399> to<00:00:42.559> ZK<00:00:43.079> my<00:00:43.280> a 00:00:44.709 --> 00:00:44.719 align:start position:0% auctions to ZK my a 00:00:44.719 --> 00:00:50.110 align:start position:0% auctions to ZK my a toz 00:00:50.110 --> 00:00:50.120 align:start position:0% 00:00:50.120 --> 00:00:54.830 align:start position:0% uh<00:00:51.120> I<00:00:51.199> don't<00:00:51.480> know<00:00:51.640> if<00:00:51.800> it 00:00:54.830 --> 00:00:54.840 align:start position:0% 00:00:54.840 --> 00:00:58.270 align:start position:0% works<00:00:55.840> is<00:00:56.000> there<00:00:56.160> a<00:00:56.359> way 00:00:58.270 --> 00:00:58.280 align:start position:0% works is there a way 00:00:58.280 --> 00:01:00.910 align:start position:0% works is there a way sorry<00:00:59.280> is<00:00:59.399> there<00:00:59.680> some 00:01:00.910 --> 00:01:00.920 align:start position:0% sorry is there some 00:01:00.920 --> 00:01:05.030 align:start position:0% sorry is there some um<00:01:01.920> special 00:01:05.030 --> 00:01:05.040 align:start position:0% 00:01:05.040 --> 00:01:09.830 align:start position:0% trick 00:01:09.830 --> 00:01:09.840 align:start position:0% 00:01:09.840 --> 00:01:21.870 align:start position:0% this 00:01:21.870 --> 00:01:21.880 align:start position:0% 00:01:21.880 --> 00:01:45.990 align:start position:0% yeah<00:01:22.880> okay 00:01:45.990 --> 00:01:46.000 align:start position:0% 00:01:46.000 --> 00:01:48.910 align:start position:0% hello<00:01:47.000> so<00:01:47.360> I<00:01:47.479> go<00:01:47.680> back<00:01:47.840> to<00:01:48.040> the<00:01:48.200> start<00:01:48.600> so<00:01:48.759> yeah 00:01:48.910 --> 00:01:48.920 align:start position:0% hello so I go back to the start so yeah 00:01:48.920 --> 00:01:50.670 align:start position:0% hello so I go back to the start so yeah I<00:01:49.000> want<00:01:49.159> to<00:01:49.280> give<00:01:49.399> you<00:01:49.560> a<00:01:49.799> bit<00:01:49.920> of<00:01:50.000> an<00:01:50.119> overview 00:01:50.670 --> 00:01:50.680 align:start position:0% I want to give you a bit of an overview 00:01:50.680 --> 00:01:54.789 align:start position:0% I want to give you a bit of an overview of<00:01:51.360> uh<00:01:52.000> NPC<00:01:52.680> from<00:01:52.960> A<00:01:53.119> to<00:01:53.320> Z<00:01:53.680> which<00:01:54.360> uh<00:01:54.560> if<00:01:54.680> you 00:01:54.789 --> 00:01:54.799 align:start position:0% of uh NPC from A to Z which uh if you 00:01:54.799 --> 00:01:56.749 align:start position:0% of uh NPC from A to Z which uh if you know<00:01:55.000> about<00:01:55.200> NPC<00:01:55.640> use<00:01:55.960> cases<00:01:56.399> it's<00:01:56.560> from 00:01:56.749 --> 00:01:56.759 align:start position:0% know about NPC use cases it's from 00:01:56.759 --> 00:01:59.270 align:start position:0% know about NPC use cases it's from auctions<00:01:57.200> to<00:01:57.479> zero<00:01:57.880> knowledge<00:01:58.880> and<00:01:58.960> so<00:01:59.159> one 00:01:59.270 --> 00:01:59.280 align:start position:0% auctions to zero knowledge and so one 00:01:59.280 --> 00:02:01.630 align:start position:0% auctions to zero knowledge and so one thing<00:01:59.399> I<00:01:59.520> wanted<00:02:00.039> start<00:02:00.360> by<00:02:00.640> and<00:02:00.799> maybe<00:02:01.320> uh 00:02:01.630 --> 00:02:01.640 align:start position:0% thing I wanted start by and maybe uh 00:02:01.640 --> 00:02:03.789 align:start position:0% thing I wanted start by and maybe uh this<00:02:01.799> room<00:02:02.159> kind<00:02:02.280> of<00:02:02.439> appreciates<00:02:03.000> this<00:02:03.600> is 00:02:03.789 --> 00:02:03.799 align:start position:0% this room kind of appreciates this is 00:02:03.799 --> 00:02:06.469 align:start position:0% this room kind of appreciates this is that<00:02:04.079> cryptographers<00:02:04.880> are<00:02:05.159> not<00:02:05.680> Cipher<00:02:06.119> punks 00:02:06.469 --> 00:02:06.479 align:start position:0% that cryptographers are not Cipher punks 00:02:06.479 --> 00:02:08.309 align:start position:0% that cryptographers are not Cipher punks and<00:02:06.600> I<00:02:06.719> think<00:02:06.960> I<00:02:07.119> come<00:02:07.520> from<00:02:07.680> a<00:02:07.880> background<00:02:08.200> of 00:02:08.309 --> 00:02:08.319 align:start position:0% and I think I come from a background of 00:02:08.319 --> 00:02:09.910 align:start position:0% and I think I come from a background of cryptography<00:02:08.920> and<00:02:09.039> there<00:02:09.160> is<00:02:09.280> a<00:02:09.399> tendency<00:02:09.800> in 00:02:09.910 --> 00:02:09.920 align:start position:0% cryptography and there is a tendency in 00:02:09.920 --> 00:02:11.910 align:start position:0% cryptography and there is a tendency in the<00:02:10.039> cryptography<00:02:10.599> Community<00:02:11.160> to<00:02:11.319> think<00:02:11.599> that 00:02:11.910 --> 00:02:11.920 align:start position:0% the cryptography Community to think that 00:02:11.920 --> 00:02:15.190 align:start position:0% the cryptography Community to think that because<00:02:12.360> we<00:02:12.520> build<00:02:12.959> the<00:02:13.080> tools<00:02:13.879> that<00:02:14.760> can<00:02:15.080> you 00:02:15.190 --> 00:02:15.200 align:start position:0% because we build the tools that can you 00:02:15.200 --> 00:02:17.110 align:start position:0% because we build the tools that can you know<00:02:15.400> help<00:02:15.640> us<00:02:15.920> exercise<00:02:16.440> the<00:02:16.560> freedoms<00:02:16.959> and 00:02:17.110 --> 00:02:17.120 align:start position:0% know help us exercise the freedoms and 00:02:17.120 --> 00:02:19.750 align:start position:0% know help us exercise the freedoms and the<00:02:17.239> cipher<00:02:17.560> Punk<00:02:17.840> values<00:02:18.160> that<00:02:18.319> we<00:02:18.480> want<00:02:19.480> um 00:02:19.750 --> 00:02:19.760 align:start position:0% the cipher Punk values that we want um 00:02:19.760 --> 00:02:21.509 align:start position:0% the cipher Punk values that we want um we<00:02:19.920> do<00:02:20.120> feel<00:02:20.440> like<00:02:20.599> we<00:02:20.760> are<00:02:21.000> some<00:02:21.160> sort<00:02:21.360> of 00:02:21.509 --> 00:02:21.519 align:start position:0% we do feel like we are some sort of 00:02:21.519 --> 00:02:23.949 align:start position:0% we do feel like we are some sort of rebels<00:02:22.239> but<00:02:22.560> after<00:02:22.879> quite<00:02:23.080> some<00:02:23.280> time<00:02:23.480> now<00:02:23.800> I 00:02:23.949 --> 00:02:23.959 align:start position:0% rebels but after quite some time now I 00:02:23.959 --> 00:02:25.630 align:start position:0% rebels but after quite some time now I kind<00:02:24.080> of<00:02:24.200> realize<00:02:24.800> that's<00:02:24.959> not<00:02:25.200> actually<00:02:25.480> the 00:02:25.630 --> 00:02:25.640 align:start position:0% kind of realize that's not actually the 00:02:25.640 --> 00:02:27.589 align:start position:0% kind of realize that's not actually the case<00:02:26.080> mostly<00:02:26.560> what<00:02:26.760> people<00:02:27.280> like<00:02:27.400> what<00:02:27.480> the 00:02:27.589 --> 00:02:27.599 align:start position:0% case mostly what people like what the 00:02:27.599 --> 00:02:29.990 align:start position:0% case mostly what people like what the cryptographers<00:02:28.319> actually<00:02:28.599> like<00:02:28.800> to<00:02:28.959> do<00:02:29.599> is 00:02:29.990 --> 00:02:30.000 align:start position:0% cryptographers actually like to do is 00:02:30.000 --> 00:02:31.949 align:start position:0% cryptographers actually like to do is push<00:02:30.239> symbols<00:02:30.680> around<00:02:31.040> to<00:02:31.239> try<00:02:31.400> and<00:02:31.560> make<00:02:31.720> some 00:02:31.949 --> 00:02:31.959 align:start position:0% push symbols around to try and make some 00:02:31.959 --> 00:02:35.589 align:start position:0% push symbols around to try and make some proofs<00:02:32.239> of<00:02:32.480> security<00:02:33.400> and<00:02:33.560> feel<00:02:34.120> uh<00:02:34.440> smart<00:02:35.440> and 00:02:35.589 --> 00:02:35.599 align:start position:0% proofs of security and feel uh smart and 00:02:35.599 --> 00:02:39.030 align:start position:0% proofs of security and feel uh smart and so<00:02:36.040> this<00:02:36.200> is<00:02:36.680> uh<00:02:37.080> this<00:02:37.239> is<00:02:38.200> great<00:02:38.760> and<00:02:38.879> it's 00:02:39.030 --> 00:02:39.040 align:start position:0% so this is uh this is great and it's 00:02:39.040 --> 00:02:40.589 align:start position:0% so this is uh this is great and it's really<00:02:39.319> cool<00:02:39.599> that<00:02:39.720> we<00:02:39.879> have<00:02:40.120> a<00:02:40.280> secure 00:02:40.589 --> 00:02:40.599 align:start position:0% really cool that we have a secure 00:02:40.599 --> 00:02:42.229 align:start position:0% really cool that we have a secure protocols<00:02:41.120> but<00:02:41.239> it<00:02:41.360> does<00:02:41.519> not<00:02:41.760> make<00:02:41.959> them 00:02:42.229 --> 00:02:42.239 align:start position:0% protocols but it does not make them 00:02:42.239 --> 00:02:44.750 align:start position:0% protocols but it does not make them Cipher<00:02:42.680> punks<00:02:42.959> and<00:02:43.080> it<00:02:43.239> does<00:02:43.440> not<00:02:44.000> result<00:02:44.519> in 00:02:44.750 --> 00:02:44.760 align:start position:0% Cipher punks and it does not result in 00:02:44.760 --> 00:02:46.110 align:start position:0% Cipher punks and it does not result in the<00:02:44.879> sort<00:02:45.040> of<00:02:45.159> Freedom<00:02:45.480> tools<00:02:45.879> that<00:02:46.040> the 00:02:46.110 --> 00:02:46.120 align:start position:0% the sort of Freedom tools that the 00:02:46.120 --> 00:02:48.589 align:start position:0% the sort of Freedom tools that the cipher<00:02:46.480> Punk<00:02:46.720> values<00:02:47.280> maybe<00:02:47.599> need<00:02:47.920> and<00:02:48.080> the<00:02:48.319> T 00:02:48.589 --> 00:02:48.599 align:start position:0% cipher Punk values maybe need and the T 00:02:48.599 --> 00:02:50.070 align:start position:0% cipher Punk values maybe need and the T types<00:02:48.879> of<00:02:49.040> things<00:02:49.200> that<00:02:49.360> Amir<00:02:49.640> was<00:02:49.800> talking 00:02:50.070 --> 00:02:50.080 align:start position:0% types of things that Amir was talking 00:02:50.080 --> 00:02:51.670 align:start position:0% types of things that Amir was talking about<00:02:50.360> just 00:02:51.670 --> 00:02:51.680 align:start position:0% about just 00:02:51.680 --> 00:02:54.550 align:start position:0% about just now<00:02:52.680> um<00:02:53.159> so<00:02:53.400> yeah<00:02:53.680> cryptographers<00:02:54.280> are<00:02:54.400> not 00:02:54.550 --> 00:02:54.560 align:start position:0% now um so yeah cryptographers are not 00:02:54.560 --> 00:02:56.070 align:start position:0% now um so yeah cryptographers are not Cipher<00:02:54.879> punks<00:02:55.200> and<00:02:55.319> this<00:02:55.400> is<00:02:55.560> why<00:02:55.720> I<00:02:55.840> kind<00:02:55.959> of 00:02:56.070 --> 00:02:56.080 align:start position:0% Cipher punks and this is why I kind of 00:02:56.080 --> 00:02:58.949 align:start position:0% Cipher punks and this is why I kind of put<00:02:56.239> it<00:02:56.360> in<00:02:56.560> this<00:02:56.879> in<00:02:57.239> this<00:02:58.239> um<00:02:58.640> in<00:02:58.800> this 00:02:58.949 --> 00:02:58.959 align:start position:0% put it in this in this um in this 00:02:58.959 --> 00:03:00.309 align:start position:0% put it in this in this um in this session<00:02:59.239> in<00:02:59.319> the<00:02:59.440> cipher<00:02:59.680> Punk<00:03:00.000> session 00:03:00.309 --> 00:03:00.319 align:start position:0% session in the cipher Punk session 00:03:00.319 --> 00:03:04.309 align:start position:0% session in the cipher Punk session rather<00:03:00.560> than<00:03:00.840> the<00:03:01.640> uh<00:03:02.640> applied<00:03:03.000> crypto<00:03:03.319> truck 00:03:04.309 --> 00:03:04.319 align:start position:0% rather than the uh applied crypto truck 00:03:04.319 --> 00:03:07.070 align:start position:0% rather than the uh applied crypto truck and<00:03:04.440> so<00:03:04.680> I<00:03:04.760> think<00:03:04.920> in<00:03:05.120> building<00:03:06.080> uh<00:03:06.480> kind<00:03:06.599> of 00:03:07.070 --> 00:03:07.080 align:start position:0% and so I think in building uh kind of 00:03:07.080 --> 00:03:08.869 align:start position:0% and so I think in building uh kind of Freedom<00:03:07.480> tools<00:03:08.000> or<00:03:08.200> you<00:03:08.319> know<00:03:08.480> privacy 00:03:08.869 --> 00:03:08.879 align:start position:0% Freedom tools or you know privacy 00:03:08.879 --> 00:03:10.470 align:start position:0% Freedom tools or you know privacy preserving<00:03:09.319> tools<00:03:09.680> it's<00:03:09.840> important<00:03:10.200> to<00:03:10.360> kind 00:03:10.470 --> 00:03:10.480 align:start position:0% preserving tools it's important to kind 00:03:10.480 --> 00:03:13.030 align:start position:0% preserving tools it's important to kind of<00:03:11.080> understand<00:03:11.360> some<00:03:11.519> of<00:03:11.640> the<00:03:12.040> cryptography 00:03:13.030 --> 00:03:13.040 align:start position:0% of understand some of the cryptography 00:03:13.040 --> 00:03:14.350 align:start position:0% of understand some of the cryptography and<00:03:13.159> so<00:03:13.360> yeah<00:03:13.519> this<00:03:13.599> is<00:03:13.720> why<00:03:13.840> I<00:03:13.920> want<00:03:14.080> to<00:03:14.200> give 00:03:14.350 --> 00:03:14.360 align:start position:0% and so yeah this is why I want to give 00:03:14.360 --> 00:03:17.509 align:start position:0% and so yeah this is why I want to give you<00:03:14.560> some<00:03:14.920> view<00:03:15.200> of<00:03:15.519> MPC<00:03:16.519> so<00:03:16.840> what<00:03:16.959> has<00:03:17.120> MPC 00:03:17.509 --> 00:03:17.519 align:start position:0% you some view of MPC so what has MPC 00:03:17.519 --> 00:03:20.110 align:start position:0% you some view of MPC so what has MPC been<00:03:17.680> used<00:03:17.920> for<00:03:18.040> and<00:03:18.200> first<00:03:18.360> of<00:03:18.920> all<00:03:19.920> does 00:03:20.110 --> 00:03:20.120 align:start position:0% been used for and first of all does 00:03:20.120 --> 00:03:22.869 align:start position:0% been used for and first of all does everybody<00:03:20.440> know<00:03:20.599> what<00:03:20.720> I<00:03:20.799> mean<00:03:21.000> when<00:03:21.080> I<00:03:21.200> say 00:03:22.869 --> 00:03:22.879 align:start position:0% everybody know what I mean when I say 00:03:22.879 --> 00:03:27.509 align:start position:0% everybody know what I mean when I say MPC<00:03:23.879> okay<00:03:24.360> one<00:03:24.920> two<00:03:25.920> three<00:03:26.239> people<00:03:26.879> so<00:03:27.040> NPC 00:03:27.509 --> 00:03:27.519 align:start position:0% MPC okay one two three people so NPC 00:03:27.519 --> 00:03:30.509 align:start position:0% MPC okay one two three people so NPC stands<00:03:27.760> for<00:03:28.040> multi-party<00:03:28.640> computation<00:03:29.959> um<00:03:30.400> is 00:03:30.509 --> 00:03:30.519 align:start position:0% stands for multi-party computation um is 00:03:30.519 --> 00:03:32.350 align:start position:0% stands for multi-party computation um is there<00:03:30.720> anybody<00:03:31.159> like<00:03:31.319> who<00:03:31.519> has<00:03:31.760> absolutely<00:03:32.200> no 00:03:32.350 --> 00:03:32.360 align:start position:0% there anybody like who has absolutely no 00:03:32.360 --> 00:03:35.149 align:start position:0% there anybody like who has absolutely no clue<00:03:32.599> at<00:03:32.680> all<00:03:32.879> what<00:03:33.000> multiparty<00:03:33.599> computation 00:03:35.149 --> 00:03:35.159 align:start position:0% clue at all what multiparty computation 00:03:35.159 --> 00:03:37.470 align:start position:0% clue at all what multiparty computation is<00:03:36.159> okay<00:03:36.400> one<00:03:36.599> person<00:03:36.879> at<00:03:37.000> the<00:03:37.120> very<00:03:37.319> back 00:03:37.470 --> 00:03:37.480 align:start position:0% is okay one person at the very back 00:03:37.480 --> 00:03:40.990 align:start position:0% is okay one person at the very back you're<00:03:37.879> too<00:03:38.080> far<00:03:38.319> back<00:03:38.480> to<00:03:38.920> uh<00:03:39.760> no<00:03:40.040> but<00:03:40.680> anyway 00:03:40.990 --> 00:03:41.000 align:start position:0% you're too far back to uh no but anyway 00:03:41.000 --> 00:03:44.030 align:start position:0% you're too far back to uh no but anyway MPC<00:03:41.720> is<00:03:41.959> used<00:03:42.360> for<00:03:42.760> computing<00:03:43.239> on<00:03:43.519> encrypted 00:03:44.030 --> 00:03:44.040 align:start position:0% MPC is used for computing on encrypted 00:03:44.040 --> 00:03:46.789 align:start position:0% MPC is used for computing on encrypted data<00:03:44.560> so<00:03:45.120> it<00:03:45.280> started<00:03:45.760> in<00:03:45.840> the<00:03:45.920> 80s<00:03:46.360> with<00:03:46.560> coin 00:03:46.789 --> 00:03:46.799 align:start position:0% data so it started in the 80s with coin 00:03:46.799 --> 00:03:49.630 align:start position:0% data so it started in the 80s with coin flipping<00:03:47.439> mental<00:03:47.840> poker<00:03:48.560> comparing<00:03:49.040> integers 00:03:49.630 --> 00:03:49.640 align:start position:0% flipping mental poker comparing integers 00:03:49.640 --> 00:03:51.830 align:start position:0% flipping mental poker comparing integers small<00:03:50.000> things<00:03:50.760> and<00:03:50.879> essentially<00:03:51.360> what<00:03:51.480> it<00:03:51.640> is 00:03:51.830 --> 00:03:51.840 align:start position:0% small things and essentially what it is 00:03:51.840 --> 00:03:54.869 align:start position:0% small things and essentially what it is is<00:03:52.040> that<00:03:52.239> you<00:03:52.360> know<00:03:52.519> a<00:03:52.640> user<00:03:53.360> Alice<00:03:54.360> has<00:03:54.599> some 00:03:54.869 --> 00:03:54.879 align:start position:0% is that you know a user Alice has some 00:03:54.879 --> 00:03:57.229 align:start position:0% is that you know a user Alice has some data<00:03:55.319> in<00:03:55.439> her<00:03:55.720> local<00:03:56.200> device<00:03:56.560> or<00:03:56.760> in<00:03:57.000> her 00:03:57.229 --> 00:03:57.239 align:start position:0% data in her local device or in her 00:03:57.239 --> 00:03:59.270 align:start position:0% data in her local device or in her machine<00:03:57.640> and<00:03:57.840> whatever<00:03:58.159> machine<00:03:58.959> she<00:03:59.120> can 00:03:59.270 --> 00:03:59.280 align:start position:0% machine and whatever machine she can 00:03:59.280 --> 00:04:01.470 align:start position:0% machine and whatever machine she can Secret<00:03:59.799> share<00:04:00.040> it<00:04:00.280> to<00:04:00.439> a<00:04:00.599> network<00:04:01.159> and<00:04:01.319> this 00:04:01.470 --> 00:04:01.480 align:start position:0% Secret share it to a network and this 00:04:01.480 --> 00:04:03.229 align:start position:0% Secret share it to a network and this network<00:04:02.040> communicates<00:04:02.680> nodes<00:04:02.959> in<00:04:03.120> this 00:04:03.229 --> 00:04:03.239 align:start position:0% network communicates nodes in this 00:04:03.239 --> 00:04:05.750 align:start position:0% network communicates nodes in this network<00:04:03.599> communicate<00:04:04.439> to<00:04:04.599> do<00:04:05.040> computation<00:04:05.599> on 00:04:05.750 --> 00:04:05.760 align:start position:0% network communicate to do computation on 00:04:05.760 --> 00:04:07.750 align:start position:0% network communicate to do computation on her<00:04:05.959> encrypted<00:04:06.400> shares<00:04:07.040> and<00:04:07.159> they<00:04:07.280> produce<00:04:07.560> a 00:04:07.750 --> 00:04:07.760 align:start position:0% her encrypted shares and they produce a 00:04:07.760 --> 00:04:09.509 align:start position:0% her encrypted shares and they produce a result<00:04:08.200> this<00:04:08.319> is<00:04:08.439> it 00:04:09.509 --> 00:04:09.519 align:start position:0% result this is it 00:04:09.519 --> 00:04:12.710 align:start position:0% result this is it essentially<00:04:10.519> and<00:04:10.640> so<00:04:11.319> the<00:04:11.480> first<00:04:11.840> large<00:04:12.319> scale 00:04:12.710 --> 00:04:12.720 align:start position:0% essentially and so the first large scale 00:04:12.720 --> 00:04:14.309 align:start position:0% essentially and so the first large scale kind<00:04:12.840> of<00:04:13.040> practical<00:04:13.519> example<00:04:13.879> of<00:04:14.040> this<00:04:14.200> was 00:04:14.309 --> 00:04:14.319 align:start position:0% kind of practical example of this was 00:04:14.319 --> 00:04:16.550 align:start position:0% kind of practical example of this was the<00:04:14.439> sugar<00:04:14.720> beat<00:04:15.000> auction<00:04:15.439> which<00:04:15.560> was<00:04:15.760> run<00:04:16.000> in 00:04:16.550 --> 00:04:16.560 align:start position:0% the sugar beat auction which was run in 00:04:16.560 --> 00:04:18.949 align:start position:0% the sugar beat auction which was run in 2008<00:04:17.560> and<00:04:17.720> this<00:04:17.840> was<00:04:18.079> a<00:04:18.199> double<00:04:18.479> auction<00:04:18.799> to 00:04:18.949 --> 00:04:18.959 align:start position:0% 2008 and this was a double auction to 00:04:18.959 --> 00:04:20.870 align:start position:0% 2008 and this was a double auction to determine<00:04:19.479> the<00:04:19.639> market<00:04:20.040> price<00:04:20.320> of<00:04:20.560> sugar 00:04:20.870 --> 00:04:20.880 align:start position:0% determine the market price of sugar 00:04:20.880 --> 00:04:23.550 align:start position:0% determine the market price of sugar beads<00:04:21.880> um<00:04:22.000> it<00:04:22.120> was<00:04:22.199> an<00:04:22.360> NPC<00:04:22.759> you<00:04:22.880> run<00:04:23.160> between 00:04:23.550 --> 00:04:23.560 align:start position:0% beads um it was an NPC you run between 00:04:23.560 --> 00:04:26.189 align:start position:0% beads um it was an NPC you run between farmers<00:04:24.440> and<00:04:24.840> a<00:04:24.960> sugar<00:04:25.320> processor<00:04:26.000> and 00:04:26.189 --> 00:04:26.199 align:start position:0% farmers and a sugar processor and 00:04:26.199 --> 00:04:28.749 align:start position:0% farmers and a sugar processor and researchers<00:04:26.840> in<00:04:27.080> Denmark<00:04:28.080> um<00:04:28.240> it<00:04:28.320> was<00:04:28.479> super 00:04:28.749 --> 00:04:28.759 align:start position:0% researchers in Denmark um it was super 00:04:28.759 --> 00:04:30.430 align:start position:0% researchers in Denmark um it was super nice<00:04:29.039> because<00:04:29.280> everybody<00:04:29.840> agreed<00:04:30.160> that<00:04:30.320> this 00:04:30.430 --> 00:04:30.440 align:start position:0% nice because everybody agreed that this 00:04:30.440 --> 00:04:32.510 align:start position:0% nice because everybody agreed that this was<00:04:30.639> kind<00:04:30.759> of<00:04:30.919> needed<00:04:31.400> and<00:04:31.560> useful<00:04:32.280> um<00:04:32.440> the 00:04:32.510 --> 00:04:32.520 align:start position:0% was kind of needed and useful um the 00:04:32.520 --> 00:04:34.270 align:start position:0% was kind of needed and useful um the farmers<00:04:33.000> didn't<00:04:33.320> have<00:04:33.440> to<00:04:33.600> reveal<00:04:34.000> how<00:04:34.120> much 00:04:34.270 --> 00:04:34.280 align:start position:0% farmers didn't have to reveal how much 00:04:34.280 --> 00:04:36.430 align:start position:0% farmers didn't have to reveal how much they<00:04:34.400> were<00:04:34.560> willing<00:04:34.800> to<00:04:35.000> pay<00:04:35.639> the<00:04:35.759> sugar<00:04:36.160> Pro 00:04:36.430 --> 00:04:36.440 align:start position:0% they were willing to pay the sugar Pro 00:04:36.440 --> 00:04:37.830 align:start position:0% they were willing to pay the sugar Pro processors<00:04:37.000> couldn't<00:04:37.320> you<00:04:37.400> know<00:04:37.680> take 00:04:37.830 --> 00:04:37.840 align:start position:0% processors couldn't you know take 00:04:37.840 --> 00:04:39.749 align:start position:0% processors couldn't you know take advantage<00:04:38.199> of<00:04:38.360> farmers<00:04:39.080> and<00:04:39.240> everybody<00:04:39.639> kind 00:04:39.749 --> 00:04:39.759 align:start position:0% advantage of farmers and everybody kind 00:04:39.759 --> 00:04:41.870 align:start position:0% advantage of farmers and everybody kind of<00:04:39.880> won<00:04:40.160> so<00:04:40.320> this<00:04:40.440> was<00:04:40.560> a<00:04:40.720> super<00:04:40.960> nice<00:04:41.520> um 00:04:41.870 --> 00:04:41.880 align:start position:0% of won so this was a super nice um 00:04:41.880 --> 00:04:43.670 align:start position:0% of won so this was a super nice um example<00:04:42.360> of<00:04:42.560> an<00:04:42.720> auction<00:04:43.039> that<00:04:43.120> was<00:04:43.240> run<00:04:43.479> in 00:04:43.670 --> 00:04:43.680 align:start position:0% example of an auction that was run in 00:04:43.680 --> 00:04:45.950 align:start position:0% example of an auction that was run in NPC<00:04:44.680> something<00:04:45.039> that<00:04:45.440> um<00:04:45.680> could<00:04:45.800> have 00:04:45.950 --> 00:04:45.960 align:start position:0% NPC something that um could have 00:04:45.960 --> 00:04:47.629 align:start position:0% NPC something that um could have benefited<00:04:46.400> from<00:04:46.560> something<00:04:46.880> like<00:04:47.039> this<00:04:47.360> is 00:04:47.629 --> 00:04:47.639 align:start position:0% benefited from something like this is 00:04:47.639 --> 00:04:49.550 align:start position:0% benefited from something like this is let's<00:04:47.800> say<00:04:47.960> the<00:04:48.120> Constitution<00:04:48.800> da<00:04:49.080> who<00:04:49.240> lost 00:04:49.550 --> 00:04:49.560 align:start position:0% let's say the Constitution da who lost 00:04:49.560 --> 00:04:51.070 align:start position:0% let's say the Constitution da who lost an<00:04:49.759> auction<00:04:50.160> because<00:04:50.440> they<00:04:50.560> revealed<00:04:50.960> how 00:04:51.070 --> 00:04:51.080 align:start position:0% an auction because they revealed how 00:04:51.080 --> 00:04:52.790 align:start position:0% an auction because they revealed how much<00:04:51.240> they<00:04:51.320> were<00:04:51.479> willing<00:04:51.720> to<00:04:51.880> pay<00:04:52.199> and<00:04:52.680> you 00:04:52.790 --> 00:04:52.800 align:start position:0% much they were willing to pay and you 00:04:52.800 --> 00:04:56.189 align:start position:0% much they were willing to pay and you know<00:04:53.800> uh<00:04:54.800> uh<00:04:54.960> their<00:04:55.160> competitors<00:04:55.720> could<00:04:55.880> see 00:04:56.189 --> 00:04:56.199 align:start position:0% know uh uh their competitors could see 00:04:56.199 --> 00:04:58.469 align:start position:0% know uh uh their competitors could see how<00:04:56.320> much<00:04:56.520> there<00:04:56.680> was<00:04:56.880> in<00:04:57.000> a<00:04:57.120> public<00:04:57.400> wallet 00:04:58.469 --> 00:04:58.479 align:start position:0% how much there was in a public wallet 00:04:58.479 --> 00:05:00.990 align:start position:0% how much there was in a public wallet before<00:04:59.479> and<00:04:59.800> um<00:04:59.960> another<00:05:00.240> one<00:05:00.360> was<00:05:00.520> the<00:05:00.639> Boston 00:05:00.990 --> 00:05:01.000 align:start position:0% before and um another one was the Boston 00:05:01.000 --> 00:05:03.270 align:start position:0% before and um another one was the Boston wage<00:05:01.280> study<00:05:01.680> so<00:05:01.880> identifying<00:05:02.479> salary<00:05:02.960> gaps 00:05:03.270 --> 00:05:03.280 align:start position:0% wage study so identifying salary gaps 00:05:03.280 --> 00:05:06.510 align:start position:0% wage study so identifying salary gaps across<00:05:03.639> gender<00:05:04.320> and<00:05:05.280> um<00:05:05.639> ethnicity<00:05:06.240> so<00:05:06.400> this 00:05:06.510 --> 00:05:06.520 align:start position:0% across gender and um ethnicity so this 00:05:06.520 --> 00:05:09.430 align:start position:0% across gender and um ethnicity so this was<00:05:06.680> done<00:05:06.840> in<00:05:06.960> Boston<00:05:07.759> they<00:05:07.880> did<00:05:08.479> uh<00:05:08.759> NPC<00:05:09.199> saw 00:05:09.430 --> 00:05:09.440 align:start position:0% was done in Boston they did uh NPC saw 00:05:09.440 --> 00:05:11.870 align:start position:0% was done in Boston they did uh NPC saw like<00:05:09.560> a<00:05:10.000> private<00:05:10.400> computation<00:05:11.039> across<00:05:11.759> uh 00:05:11.870 --> 00:05:11.880 align:start position:0% like a private computation across uh 00:05:11.880 --> 00:05:14.830 align:start position:0% like a private computation across uh census<00:05:12.479> data<00:05:13.199> to<00:05:13.560> try<00:05:13.759> and<00:05:14.080> analyze<00:05:14.600> whether 00:05:14.830 --> 00:05:14.840 align:start position:0% census data to try and analyze whether 00:05:14.840 --> 00:05:17.430 align:start position:0% census data to try and analyze whether there<00:05:14.960> was<00:05:15.080> a<00:05:15.240> disparity<00:05:15.919> between<00:05:16.560> gender<00:05:17.320> uh 00:05:17.430 --> 00:05:17.440 align:start position:0% there was a disparity between gender uh 00:05:17.440 --> 00:05:19.710 align:start position:0% there was a disparity between gender uh wages<00:05:17.840> across<00:05:18.160> genders<00:05:19.120> naturally<00:05:19.600> they 00:05:19.710 --> 00:05:19.720 align:start position:0% wages across genders naturally they 00:05:19.720 --> 00:05:22.749 align:start position:0% wages across genders naturally they found<00:05:20.000> that<00:05:20.160> there<00:05:20.319> was<00:05:21.199> um<00:05:22.199> and<00:05:22.319> they<00:05:22.440> found<00:05:22.680> I 00:05:22.749 --> 00:05:22.759 align:start position:0% found that there was um and they found I 00:05:22.759 --> 00:05:24.710 align:start position:0% found that there was um and they found I think<00:05:22.880> it<00:05:22.960> was<00:05:23.120> 30%<00:05:23.960> maybe<00:05:24.160> it's<00:05:24.280> too<00:05:24.440> small 00:05:24.710 --> 00:05:24.720 align:start position:0% think it was 30% maybe it's too small 00:05:24.720 --> 00:05:27.469 align:start position:0% think it was 30% maybe it's too small here<00:05:24.919> oh<00:05:25.120> yeah<00:05:25.520> it<00:05:25.639> was<00:05:25.800> 30%<00:05:26.360> I<00:05:26.440> think<00:05:26.560> in<00:05:26.680> 2016 00:05:27.469 --> 00:05:27.479 align:start position:0% here oh yeah it was 30% I think in 2016 00:05:27.479 --> 00:05:29.710 align:start position:0% here oh yeah it was 30% I think in 2016 when<00:05:27.600> they<00:05:27.720> first<00:05:27.919> did<00:05:28.120> this<00:05:28.280> study<00:05:29.280> um<00:05:29.440> and 00:05:29.710 --> 00:05:29.720 align:start position:0% when they first did this study um and 00:05:29.720 --> 00:05:32.510 align:start position:0% when they first did this study um and they<00:05:29.840> did<00:05:29.960> it<00:05:30.120> again<00:05:30.520> last<00:05:30.880> year<00:05:31.360> no<00:05:31.600> 2023<00:05:32.319> yeah 00:05:32.510 --> 00:05:32.520 align:start position:0% they did it again last year no 2023 yeah 00:05:32.520 --> 00:05:35.749 align:start position:0% they did it again last year no 2023 yeah last<00:05:32.720> year<00:05:33.240> and<00:05:33.400> it<00:05:33.639> had<00:05:33.960> decreased<00:05:34.479> to<00:05:34.720> 21%<00:05:35.520> so 00:05:35.749 --> 00:05:35.759 align:start position:0% last year and it had decreased to 21% so 00:05:35.759 --> 00:05:38.029 align:start position:0% last year and it had decreased to 21% so by<00:05:35.919> doing<00:05:36.280> this<00:05:36.440> kind<00:05:36.560> of<00:05:36.720> study<00:05:37.360> um<00:05:37.759> at<00:05:37.880> least 00:05:38.029 --> 00:05:38.039 align:start position:0% by doing this kind of study um at least 00:05:38.039 --> 00:05:40.390 align:start position:0% by doing this kind of study um at least you<00:05:38.319> become<00:05:38.600> aware<00:05:39.080> of<00:05:39.280> some<00:05:39.639> problems<00:05:40.280> and 00:05:40.390 --> 00:05:40.400 align:start position:0% you become aware of some problems and 00:05:40.400 --> 00:05:41.830 align:start position:0% you become aware of some problems and then<00:05:40.520> maybe<00:05:40.759> you<00:05:40.840> can<00:05:41.039> actually<00:05:41.199> start<00:05:41.680> try 00:05:41.830 --> 00:05:41.840 align:start position:0% then maybe you can actually start try 00:05:41.840 --> 00:05:43.990 align:start position:0% then maybe you can actually start try and<00:05:41.960> solve<00:05:42.240> them<00:05:42.759> um<00:05:42.960> which<00:05:43.080> is<00:05:43.520> quite<00:05:43.800> nice 00:05:43.990 --> 00:05:44.000 align:start position:0% and solve them um which is quite nice 00:05:44.000 --> 00:05:45.469 align:start position:0% and solve them um which is quite nice for 00:05:45.469 --> 00:05:45.479 align:start position:0% for 00:05:45.479 --> 00:05:48.350 align:start position:0% for society<00:05:46.479> um<00:05:46.639> there<00:05:46.759> was<00:05:46.960> also<00:05:47.280> an<00:05:47.520> Estonian 00:05:48.350 --> 00:05:48.360 align:start position:0% society um there was also an Estonian 00:05:48.360 --> 00:05:50.070 align:start position:0% society um there was also an Estonian student<00:05:48.759> graduation<00:05:49.400> so<00:05:49.639> I<00:05:49.720> don't<00:05:49.840> know<00:05:50.000> if 00:05:50.070 --> 00:05:50.080 align:start position:0% student graduation so I don't know if 00:05:50.080 --> 00:05:51.790 align:start position:0% student graduation so I don't know if you<00:05:50.240> notice<00:05:50.600> we<00:05:50.720> are<00:05:50.840> also<00:05:51.039> doing<00:05:51.280> a<00:05:51.360> bit<00:05:51.520> of<00:05:51.600> a 00:05:51.790 --> 00:05:51.800 align:start position:0% you notice we are also doing a bit of a 00:05:51.800 --> 00:05:54.189 align:start position:0% you notice we are also doing a bit of a tour<00:05:52.800> uh<00:05:52.919> of<00:05:53.120> different<00:05:53.400> countries<00:05:53.880> here<00:05:54.039> and 00:05:54.189 --> 00:05:54.199 align:start position:0% tour uh of different countries here and 00:05:54.199 --> 00:05:55.710 align:start position:0% tour uh of different countries here and these<00:05:54.400> countries<00:05:54.759> are<00:05:55.000> where<00:05:55.280> a<00:05:55.360> lot<00:05:55.520> of<00:05:55.600> the 00:05:55.710 --> 00:05:55.720 align:start position:0% these countries are where a lot of the 00:05:55.720 --> 00:05:58.390 align:start position:0% these countries are where a lot of the main<00:05:55.960> NPC<00:05:56.440> researchers<00:05:57.000> are<00:05:57.280> actually<00:05:57.560> from 00:05:58.390 --> 00:05:58.400 align:start position:0% main NPC researchers are actually from 00:05:58.400 --> 00:06:00.150 align:start position:0% main NPC researchers are actually from and<00:05:58.520> so<00:05:58.720> it's<00:05:58.880> kind<00:05:59.000> of<00:05:59.160> interesting<00:05:59.759> also 00:06:00.150 --> 00:06:00.160 align:start position:0% and so it's kind of interesting also 00:06:00.160 --> 00:06:03.189 align:start position:0% and so it's kind of interesting also geographical<00:06:00.759> tour<00:06:01.039> of<00:06:01.479> MPC<00:06:02.479> but<00:06:02.680> this<00:06:03.039> uh 00:06:03.189 --> 00:06:03.199 align:start position:0% geographical tour of MPC but this uh 00:06:03.199 --> 00:06:08.189 align:start position:0% geographical tour of MPC but this uh study<00:06:03.639> was<00:06:04.520> uh<00:06:05.520> to<00:06:05.800> try<00:06:06.000> and<00:06:06.199> determine<00:06:06.960> if<00:06:07.520> um 00:06:08.189 --> 00:06:08.199 align:start position:0% study was uh to try and determine if um 00:06:08.199 --> 00:06:11.309 align:start position:0% study was uh to try and determine if um the<00:06:08.360> Dropout<00:06:09.000> rates<00:06:09.440> in<00:06:09.800> it<00:06:10.280> studies<00:06:10.720> were<00:06:11.039> due 00:06:11.309 --> 00:06:11.319 align:start position:0% the Dropout rates in it studies were due 00:06:11.319 --> 00:06:13.909 align:start position:0% the Dropout rates in it studies were due to<00:06:12.039> people<00:06:12.319> working<00:06:12.680> at<00:06:12.800> the<00:06:12.919> weekends<00:06:13.720> uh<00:06:13.840> if 00:06:13.909 --> 00:06:13.919 align:start position:0% to people working at the weekends uh if 00:06:13.919 --> 00:06:15.430 align:start position:0% to people working at the weekends uh if their<00:06:14.160> part-time<00:06:14.560> jobs<00:06:14.800> were<00:06:14.960> interfering 00:06:15.430 --> 00:06:15.440 align:start position:0% their part-time jobs were interfering 00:06:15.440 --> 00:06:16.870 align:start position:0% their part-time jobs were interfering with<00:06:15.599> their<00:06:15.720> studies<00:06:16.039> and<00:06:16.199> causing<00:06:16.479> them<00:06:16.639> to 00:06:16.870 --> 00:06:16.880 align:start position:0% with their studies and causing them to 00:06:16.880 --> 00:06:18.830 align:start position:0% with their studies and causing them to drop<00:06:17.160> out<00:06:17.919> and<00:06:18.080> this<00:06:18.160> was<00:06:18.360> particularly 00:06:18.830 --> 00:06:18.840 align:start position:0% drop out and this was particularly 00:06:18.840 --> 00:06:21.430 align:start position:0% drop out and this was particularly important<00:06:19.199> in<00:06:19.360> Estonia<00:06:19.880> because<00:06:20.160> they<00:06:20.440> became 00:06:21.430 --> 00:06:21.440 align:start position:0% important in Estonia because they became 00:06:21.440 --> 00:06:24.070 align:start position:0% important in Estonia because they became um<00:06:21.639> much<00:06:21.800> more<00:06:22.400> technologically<00:06:23.400> relevant 00:06:24.070 --> 00:06:24.080 align:start position:0% um much more technologically relevant 00:06:24.080 --> 00:06:26.029 align:start position:0% um much more technologically relevant country<00:06:24.520> and<00:06:24.680> they<00:06:24.759> needed<00:06:25.039> a<00:06:25.240> highly<00:06:25.560> skilled 00:06:26.029 --> 00:06:26.039 align:start position:0% country and they needed a highly skilled 00:06:26.039 --> 00:06:28.110 align:start position:0% country and they needed a highly skilled it<00:06:26.360> Force<00:06:26.720> but<00:06:26.880> they<00:06:27.039> had<00:06:27.240> high<00:06:27.440> Dropout<00:06:27.880> rates 00:06:28.110 --> 00:06:28.120 align:start position:0% it Force but they had high Dropout rates 00:06:28.120 --> 00:06:30.309 align:start position:0% it Force but they had high Dropout rates so<00:06:28.240> they<00:06:28.360> were<00:06:28.520> really<00:06:28.720> trying<00:06:29.000> to<00:06:29.639> increase 00:06:30.309 --> 00:06:30.319 align:start position:0% so they were really trying to increase 00:06:30.319 --> 00:06:34.189 align:start position:0% so they were really trying to increase like<00:06:30.800> uh<00:06:31.360> the<00:06:31.880> education<00:06:32.479> of<00:06:32.759> it<00:06:33.199> Workforce 00:06:34.189 --> 00:06:34.199 align:start position:0% like uh the education of it Workforce 00:06:34.199 --> 00:06:35.710 align:start position:0% like uh the education of it Workforce they<00:06:34.400> actually<00:06:34.599> found<00:06:34.880> that<00:06:35.000> there<00:06:35.120> was<00:06:35.319> no 00:06:35.710 --> 00:06:35.720 align:start position:0% they actually found that there was no 00:06:35.720 --> 00:06:37.870 align:start position:0% they actually found that there was no correlation<00:06:36.360> between<00:06:36.680> these<00:06:36.840> two<00:06:37.039> things<00:06:37.680> but 00:06:37.870 --> 00:06:37.880 align:start position:0% correlation between these two things but 00:06:37.880 --> 00:06:39.430 align:start position:0% correlation between these two things but the<00:06:38.199> which<00:06:38.319> was<00:06:38.440> a<00:06:38.520> bit<00:06:38.680> sad<00:06:38.880> for<00:06:39.039> the<00:06:39.160> study 00:06:39.430 --> 00:06:39.440 align:start position:0% the which was a bit sad for the study 00:06:39.440 --> 00:06:41.390 align:start position:0% the which was a bit sad for the study but<00:06:39.599> like<00:06:39.800> at<00:06:39.919> least<00:06:40.319> um<00:06:40.599> we<00:06:40.759> got<00:06:40.960> a<00:06:41.120> nice 00:06:41.390 --> 00:06:41.400 align:start position:0% but like at least um we got a nice 00:06:41.400 --> 00:06:43.469 align:start position:0% but like at least um we got a nice example<00:06:41.720> of<00:06:41.880> MPC<00:06:42.360> out<00:06:42.520> of<00:06:42.680> this<00:06:42.840> so<00:06:42.960> it<00:06:43.080> was<00:06:43.199> run 00:06:43.469 --> 00:06:43.479 align:start position:0% example of MPC out of this so it was run 00:06:43.479 --> 00:06:46.589 align:start position:0% example of MPC out of this so it was run between<00:06:43.720> the<00:06:43.800> Ministry<00:06:44.160> of<00:06:44.400> Finance<00:06:45.400> and<00:06:45.880> the 00:06:46.589 --> 00:06:46.599 align:start position:0% between the Ministry of Finance and the 00:06:46.599 --> 00:06:48.510 align:start position:0% between the Ministry of Finance and the uh 00:06:48.510 --> 00:06:48.520 align:start position:0% uh 00:06:48.520 --> 00:06:52.749 align:start position:0% uh University<00:06:49.520> so<00:06:50.440> uh<00:06:50.759> another<00:06:51.160> one<00:06:51.599> was<00:06:52.280> then 00:06:52.749 --> 00:06:52.759 align:start position:0% University so uh another one was then 00:06:52.759 --> 00:06:54.749 align:start position:0% University so uh another one was then then<00:06:52.919> things<00:06:53.080> start<00:06:53.280> to<00:06:53.400> turn<00:06:53.560> a<00:06:53.680> bit<00:06:53.840> weird 00:06:54.749 --> 00:06:54.759 align:start position:0% then things start to turn a bit weird 00:06:54.759 --> 00:06:56.309 align:start position:0% then things start to turn a bit weird and<00:06:55.000> all<00:06:55.120> of<00:06:55.280> these<00:06:55.440> things<00:06:55.680> kind<00:06:55.759> of<00:06:55.919> had<00:06:56.120> like 00:06:56.309 --> 00:06:56.319 align:start position:0% and all of these things kind of had like 00:06:56.319 --> 00:06:59.790 align:start position:0% and all of these things kind of had like nice<00:06:56.960> societal<00:06:57.960> uh<00:06:58.319> implications<00:06:59.319> um<00:06:59.639> but 00:06:59.790 --> 00:06:59.800 align:start position:0% nice societal uh implications um but 00:06:59.800 --> 00:07:03.390 align:start position:0% nice societal uh implications um but then<00:07:00.039> you<00:07:00.160> know<00:07:00.680> uh<00:07:00.919> the<00:07:01.319> tooling<00:07:02.319> and<00:07:02.520> the<00:07:02.680> MPC 00:07:03.390 --> 00:07:03.400 align:start position:0% then you know uh the tooling and the MPC 00:07:03.400 --> 00:07:05.270 align:start position:0% then you know uh the tooling and the MPC protocols<00:07:03.919> became<00:07:04.199> a<00:07:04.280> bit<00:07:04.440> more<00:07:04.639> efficient 00:07:05.270 --> 00:07:05.280 align:start position:0% protocols became a bit more efficient 00:07:05.280 --> 00:07:06.710 align:start position:0% protocols became a bit more efficient and<00:07:05.400> they<00:07:05.520> started<00:07:05.800> being<00:07:05.960> picked<00:07:06.199> up<00:07:06.360> by<00:07:06.479> big 00:07:06.710 --> 00:07:06.720 align:start position:0% and they started being picked up by big 00:07:06.720 --> 00:07:09.869 align:start position:0% and they started being picked up by big Tech<00:07:07.720> and<00:07:07.840> the<00:07:08.000> Google<00:07:08.479> so<00:07:08.759> Google<00:07:09.400> had<00:07:09.599> this 00:07:09.869 --> 00:07:09.879 align:start position:0% Tech and the Google so Google had this 00:07:09.879 --> 00:07:12.270 align:start position:0% Tech and the Google so Google had this experiment<00:07:10.319> with<00:07:10.960> MasterCard<00:07:11.960> I<00:07:12.039> can't 00:07:12.270 --> 00:07:12.280 align:start position:0% experiment with MasterCard I can't 00:07:12.280 --> 00:07:16.029 align:start position:0% experiment with MasterCard I can't remember<00:07:12.560> what<00:07:12.720> year<00:07:13.160> 2017<00:07:14.120> is<00:07:14.720> 18<00:07:15.160> maybe 00:07:16.029 --> 00:07:16.039 align:start position:0% remember what year 2017 is 18 maybe 00:07:16.039 --> 00:07:18.150 align:start position:0% remember what year 2017 is 18 maybe where<00:07:16.440> they<00:07:16.599> wanted<00:07:16.960> to<00:07:17.280> achieve<00:07:17.680> the<00:07:17.800> Holy 00:07:18.150 --> 00:07:18.160 align:start position:0% where they wanted to achieve the Holy 00:07:18.160 --> 00:07:20.589 align:start position:0% where they wanted to achieve the Holy Grail<00:07:18.720> of<00:07:19.120> advertising<00:07:19.919> so<00:07:20.160> this<00:07:20.280> was<00:07:20.440> the 00:07:20.589 --> 00:07:20.599 align:start position:0% Grail of advertising so this was the 00:07:20.599 --> 00:07:22.550 align:start position:0% Grail of advertising so this was the headline<00:07:21.000> at<00:07:21.120> the<00:07:21.280> time<00:07:21.879> and<00:07:21.960> so<00:07:22.120> Google<00:07:22.479> as 00:07:22.550 --> 00:07:22.560 align:start position:0% headline at the time and so Google as 00:07:22.560 --> 00:07:24.670 align:start position:0% headline at the time and so Google as you<00:07:22.680> know<00:07:22.919> has<00:07:23.160> like<00:07:23.280> a<00:07:23.560> very<00:07:23.759> predatory<00:07:24.400> ad 00:07:24.670 --> 00:07:24.680 align:start position:0% you know has like a very predatory ad 00:07:24.680 --> 00:07:26.589 align:start position:0% you know has like a very predatory ad model<00:07:25.039> where<00:07:25.199> they<00:07:25.319> try<00:07:25.520> to<00:07:25.919> um<00:07:26.039> mine<00:07:26.400> things 00:07:26.589 --> 00:07:26.599 align:start position:0% model where they try to um mine things 00:07:26.599 --> 00:07:28.869 align:start position:0% model where they try to um mine things from<00:07:26.800> your<00:07:27.120> information<00:07:28.120> and<00:07:28.199> the<00:07:28.319> Holy<00:07:28.560> Grail 00:07:28.869 --> 00:07:28.879 align:start position:0% from your information and the Holy Grail 00:07:28.879 --> 00:07:31.430 align:start position:0% from your information and the Holy Grail of<00:07:29.039> this<00:07:29.199> ad<00:07:29.599> model<00:07:29.879> is<00:07:30.080> essentially<00:07:30.479> linking 00:07:31.430 --> 00:07:31.440 align:start position:0% of this ad model is essentially linking 00:07:31.440 --> 00:07:33.629 align:start position:0% of this ad model is essentially linking um<00:07:31.560> your<00:07:31.720> online<00:07:32.199> activity<00:07:32.759> with<00:07:32.960> your 00:07:33.629 --> 00:07:33.639 align:start position:0% um your online activity with your 00:07:33.639 --> 00:07:35.830 align:start position:0% um your online activity with your payments<00:07:34.639> Google<00:07:34.960> doesn't<00:07:35.360> have<00:07:35.560> all<00:07:35.680> the 00:07:35.830 --> 00:07:35.840 align:start position:0% payments Google doesn't have all the 00:07:35.840 --> 00:07:38.749 align:start position:0% payments Google doesn't have all the payment<00:07:36.240> information<00:07:37.080> but<00:07:37.280> MasterCard<00:07:37.919> does 00:07:38.749 --> 00:07:38.759 align:start position:0% payment information but MasterCard does 00:07:38.759 --> 00:07:40.950 align:start position:0% payment information but MasterCard does they<00:07:38.919> can't<00:07:39.360> compute<00:07:40.280> together<00:07:40.599> like 00:07:40.950 --> 00:07:40.960 align:start position:0% they can't compute together like 00:07:40.960 --> 00:07:42.589 align:start position:0% they can't compute together like MasterCard<00:07:41.599> would<00:07:41.800> never<00:07:42.000> be<00:07:42.160> willing<00:07:42.440> to 00:07:42.589 --> 00:07:42.599 align:start position:0% MasterCard would never be willing to 00:07:42.599 --> 00:07:44.830 align:start position:0% MasterCard would never be willing to share<00:07:43.560> uh<00:07:43.759> people's<00:07:44.159> information<00:07:44.639> with 00:07:44.830 --> 00:07:44.840 align:start position:0% share uh people's information with 00:07:44.840 --> 00:07:47.909 align:start position:0% share uh people's information with Google<00:07:45.479> just<00:07:45.639> in<00:07:45.759> the<00:07:45.919> clear<00:07:46.759> um<00:07:47.159> because<00:07:47.560> it's 00:07:47.909 --> 00:07:47.919 align:start position:0% Google just in the clear um because it's 00:07:47.919 --> 00:07:49.510 align:start position:0% Google just in the clear um because it's first<00:07:48.120> of<00:07:48.240> all<00:07:48.440> illegal<00:07:48.840> due<00:07:49.000> to<00:07:49.159> whatever 00:07:49.510 --> 00:07:49.520 align:start position:0% first of all illegal due to whatever 00:07:49.520 --> 00:07:51.510 align:start position:0% first of all illegal due to whatever privacy<00:07:49.919> regulations<00:07:50.919> and<00:07:51.120> consumer 00:07:51.510 --> 00:07:51.520 align:start position:0% privacy regulations and consumer 00:07:51.520 --> 00:07:53.790 align:start position:0% privacy regulations and consumer protection<00:07:52.000> reg<00:07:52.319> regulations<00:07:53.319> but<00:07:53.520> Google 00:07:53.790 --> 00:07:53.800 align:start position:0% protection reg regulations but Google 00:07:53.800 --> 00:07:55.589 align:start position:0% protection reg regulations but Google also<00:07:54.039> would<00:07:54.199> not<00:07:54.360> be<00:07:54.479> willing<00:07:54.720> to<00:07:54.840> share<00:07:55.440> um 00:07:55.589 --> 00:07:55.599 align:start position:0% also would not be willing to share um 00:07:55.599 --> 00:07:56.950 align:start position:0% also would not be willing to share um their<00:07:55.759> information<00:07:56.159> with<00:07:56.280> MasterCard<00:07:56.840> so 00:07:56.950 --> 00:07:56.960 align:start position:0% their information with MasterCard so 00:07:56.960 --> 00:07:58.390 align:start position:0% their information with MasterCard so they<00:07:57.080> had<00:07:57.240> some<00:07:57.360> sort<00:07:57.520> of<00:07:57.639> blocker<00:07:58.120> where<00:07:58.280> they 00:07:58.390 --> 00:07:58.400 align:start position:0% they had some sort of blocker where they 00:07:58.400 --> 00:08:00.350 align:start position:0% they had some sort of blocker where they wanted<00:07:58.720> to<00:07:59.159> get<00:07:59.560> around<00:07:59.759> and<00:07:59.879> they<00:07:59.960> were<00:08:00.159> like 00:08:00.350 --> 00:08:00.360 align:start position:0% wanted to get around and they were like 00:08:00.360 --> 00:08:01.950 align:start position:0% wanted to get around and they were like okay<00:08:00.520> we<00:08:00.639> want<00:08:00.759> to<00:08:00.960> compute<00:08:01.360> on<00:08:01.479> each<00:08:01.599> other's 00:08:01.950 --> 00:08:01.960 align:start position:0% okay we want to compute on each other's 00:08:01.960 --> 00:08:03.749 align:start position:0% okay we want to compute on each other's data<00:08:02.280> but<00:08:02.440> how<00:08:02.560> can<00:08:02.680> we<00:08:02.800> do<00:08:02.960> this<00:08:03.080> in<00:08:03.199> a<00:08:03.360> legal 00:08:03.749 --> 00:08:03.759 align:start position:0% data but how can we do this in a legal 00:08:03.759 --> 00:08:07.189 align:start position:0% data but how can we do this in a legal way<00:08:04.759> um<00:08:05.039> so<00:08:05.240> they<00:08:05.400> did<00:08:06.000> um<00:08:06.120> an<00:08:06.240> NPC<00:08:06.800> between 00:08:07.189 --> 00:08:07.199 align:start position:0% way um so they did um an NPC between 00:08:07.199 --> 00:08:09.710 align:start position:0% way um so they did um an NPC between some<00:08:07.599> Google<00:08:08.080> and<00:08:08.479> MasterCard<00:08:09.039> to<00:08:09.159> do<00:08:09.400> some 00:08:09.710 --> 00:08:09.720 align:start position:0% some Google and MasterCard to do some 00:08:09.720 --> 00:08:11.830 align:start position:0% some Google and MasterCard to do some aggregate<00:08:10.280> statistics<00:08:10.840> so<00:08:11.120> saying<00:08:11.479> I<00:08:11.599> show 00:08:11.830 --> 00:08:11.840 align:start position:0% aggregate statistics so saying I show 00:08:11.840 --> 00:08:15.110 align:start position:0% aggregate statistics so saying I show you<00:08:12.479> an<00:08:12.680> advertisement<00:08:13.319> for<00:08:13.840> um<00:08:14.120> some<00:08:14.759> privacy 00:08:15.110 --> 00:08:15.120 align:start position:0% you an advertisement for um some privacy 00:08:15.120 --> 00:08:17.830 align:start position:0% you an advertisement for um some privacy bracelets<00:08:15.720> on<00:08:16.440> your<00:08:17.159> uh 00:08:17.830 --> 00:08:17.840 align:start position:0% bracelets on your uh 00:08:17.840 --> 00:08:20.790 align:start position:0% bracelets on your uh browser<00:08:18.840> um<00:08:19.599> did<00:08:19.759> you<00:08:20.080> actually<00:08:20.360> go<00:08:20.520> to<00:08:20.680> the 00:08:20.790 --> 00:08:20.800 align:start position:0% browser um did you actually go to the 00:08:20.800 --> 00:08:23.270 align:start position:0% browser um did you actually go to the store<00:08:21.080> and<00:08:21.240> buy<00:08:21.879> privacy<00:08:22.280> bracelets<00:08:22.960> or<00:08:23.159> how 00:08:23.270 --> 00:08:23.280 align:start position:0% store and buy privacy bracelets or how 00:08:23.280 --> 00:08:24.869 align:start position:0% store and buy privacy bracelets or how many<00:08:23.639> people<00:08:23.879> went<00:08:24.080> to<00:08:24.199> the<00:08:24.319> store<00:08:24.520> to<00:08:24.639> buy 00:08:24.869 --> 00:08:24.879 align:start position:0% many people went to the store to buy 00:08:24.879 --> 00:08:27.270 align:start position:0% many people went to the store to buy privacy<00:08:25.199> bracelets<00:08:25.680> after<00:08:25.919> they<00:08:26.000> saw<00:08:26.240> this<00:08:26.400> ad 00:08:27.270 --> 00:08:27.280 align:start position:0% privacy bracelets after they saw this ad 00:08:27.280 --> 00:08:29.550 align:start position:0% privacy bracelets after they saw this ad so<00:08:27.440> this<00:08:27.560> was<00:08:27.720> the<00:08:27.840> kind<00:08:27.960> of<00:08:28.120> thing<00:08:29.120> and<00:08:29.199> then 00:08:29.550 --> 00:08:29.560 align:start position:0% so this was the kind of thing and then 00:08:29.560 --> 00:08:31.589 align:start position:0% so this was the kind of thing and then another<00:08:29.800> one<00:08:30.120> um<00:08:30.319> worldcoin<00:08:30.919> Iris<00:08:31.240> scanning 00:08:31.589 --> 00:08:31.599 align:start position:0% another one um worldcoin Iris scanning 00:08:31.599 --> 00:08:33.149 align:start position:0% another one um worldcoin Iris scanning so<00:08:31.720> this<00:08:31.840> is<00:08:31.960> maybe<00:08:32.279> something<00:08:32.560> that<00:08:32.719> you've 00:08:33.149 --> 00:08:33.159 align:start position:0% so this is maybe something that you've 00:08:33.159 --> 00:08:34.389 align:start position:0% so this is maybe something that you've actually<00:08:33.399> now<00:08:33.560> it's<00:08:33.719> called<00:08:33.880> world<00:08:34.200> I<00:08:34.279> should 00:08:34.389 --> 00:08:34.399 align:start position:0% actually now it's called world I should 00:08:34.399 --> 00:08:36.709 align:start position:0% actually now it's called world I should have<00:08:34.560> updated<00:08:35.000> this<00:08:35.719> but<00:08:36.039> um<00:08:36.279> this<00:08:36.360> is<00:08:36.560> where 00:08:36.709 --> 00:08:36.719 align:start position:0% have updated this but um this is where 00:08:36.719 --> 00:08:40.070 align:start position:0% have updated this but um this is where an<00:08:36.919> orb<00:08:37.479> scans<00:08:37.719> your<00:08:38.159> eye<00:08:39.159> and<00:08:39.399> tries<00:08:39.680> to<00:08:39.839> do 00:08:40.070 --> 00:08:40.080 align:start position:0% an orb scans your eye and tries to do 00:08:40.080 --> 00:08:41.589 align:start position:0% an orb scans your eye and tries to do some<00:08:40.279> uniqueness<00:08:40.839> checks<00:08:41.120> so<00:08:41.240> that<00:08:41.399> people 00:08:41.589 --> 00:08:41.599 align:start position:0% some uniqueness checks so that people 00:08:41.599 --> 00:08:44.509 align:start position:0% some uniqueness checks so that people cannot<00:08:41.919> register<00:08:42.320> more<00:08:42.519> than<00:08:42.760> once<00:08:43.760> um<00:08:44.320> they 00:08:44.509 --> 00:08:44.519 align:start position:0% cannot register more than once um they 00:08:44.519 --> 00:08:46.350 align:start position:0% cannot register more than once um they got<00:08:44.680> a<00:08:44.839> knock<00:08:45.040> on<00:08:45.160> the<00:08:45.279> door<00:08:45.560> from<00:08:46.120> some 00:08:46.350 --> 00:08:46.360 align:start position:0% got a knock on the door from some 00:08:46.360 --> 00:08:47.990 align:start position:0% got a knock on the door from some regulator<00:08:46.920> saying<00:08:47.240> you<00:08:47.360> know<00:08:47.519> how<00:08:47.680> are<00:08:47.800> you 00:08:47.990 --> 00:08:48.000 align:start position:0% regulator saying you know how are you 00:08:48.000 --> 00:08:49.670 align:start position:0% regulator saying you know how are you processing<00:08:48.519> this<00:08:48.720> data<00:08:49.080> where<00:08:49.240> is<00:08:49.360> it<00:08:49.519> all 00:08:49.670 --> 00:08:49.680 align:start position:0% processing this data where is it all 00:08:49.680 --> 00:08:52.509 align:start position:0% processing this data where is it all stored<00:08:50.600> and<00:08:50.680> so<00:08:50.920> then<00:08:51.160> they<00:08:51.320> decided<00:08:51.680> to<00:08:52.279> um<00:08:52.360> do 00:08:52.509 --> 00:08:52.519 align:start position:0% stored and so then they decided to um do 00:08:52.519 --> 00:08:54.310 align:start position:0% stored and so then they decided to um do some<00:08:52.680> multiparty<00:08:53.279> to<00:08:53.480> split<00:08:53.760> this<00:08:53.959> data<00:08:54.240> and 00:08:54.310 --> 00:08:54.320 align:start position:0% some multiparty to split this data and 00:08:54.320 --> 00:08:56.870 align:start position:0% some multiparty to split this data and do<00:08:54.480> some<00:08:54.640> multiparty<00:08:55.160> computation<00:08:55.680> over<00:08:55.880> it 00:08:56.870 --> 00:08:56.880 align:start position:0% do some multiparty computation over it 00:08:56.880 --> 00:08:58.949 align:start position:0% do some multiparty computation over it and<00:08:57.000> so<00:08:57.600> these<00:08:57.880> last<00:08:58.040> two<00:08:58.279> cases<00:08:58.720> kind<00:08:58.839> of 00:08:58.949 --> 00:08:58.959 align:start position:0% and so these last two cases kind of 00:08:58.959 --> 00:09:01.150 align:start position:0% and so these last two cases kind of start<00:08:59.160> moving<00:08:59.440> moving<00:08:59.680> towards<00:09:00.120> the 00:09:01.150 --> 00:09:01.160 align:start position:0% start moving moving towards the 00:09:01.160 --> 00:09:03.150 align:start position:0% start moving moving towards the dystopian<00:09:02.160> maybe<00:09:02.360> I<00:09:02.440> shouldn't<00:09:02.680> say<00:09:02.839> this<00:09:03.000> but 00:09:03.150 --> 00:09:03.160 align:start position:0% dystopian maybe I shouldn't say this but 00:09:03.160 --> 00:09:05.990 align:start position:0% dystopian maybe I shouldn't say this but like<00:09:03.920> Realm<00:09:04.600> where<00:09:05.200> you<00:09:05.320> know<00:09:05.560> people<00:09:05.760> are 00:09:05.990 --> 00:09:06.000 align:start position:0% like Realm where you know people are 00:09:06.000 --> 00:09:09.829 align:start position:0% like Realm where you know people are kind<00:09:06.120> of<00:09:06.240> doing<00:09:06.600> MPC<00:09:07.079> to<00:09:07.399> sort<00:09:07.519> of<00:09:08.200> sidestep<00:09:09.200> uh 00:09:09.829 --> 00:09:09.839 align:start position:0% kind of doing MPC to sort of sidestep uh 00:09:09.839 --> 00:09:12.069 align:start position:0% kind of doing MPC to sort of sidestep uh regulation<00:09:10.839> and<00:09:10.959> so<00:09:11.640> I<00:09:11.760> think<00:09:11.920> the 00:09:12.069 --> 00:09:12.079 align:start position:0% regulation and so I think the 00:09:12.079 --> 00:09:14.350 align:start position:0% regulation and so I think the cryptographer<00:09:12.800> point<00:09:13.000> of<00:09:13.200> view<00:09:13.880> is<00:09:14.000> a<00:09:14.160> bit 00:09:14.350 --> 00:09:14.360 align:start position:0% cryptographer point of view is a bit 00:09:14.360 --> 00:09:16.389 align:start position:0% cryptographer point of view is a bit like<00:09:14.720> you<00:09:14.880> know<00:09:15.240> okay<00:09:15.480> there<00:09:15.560> are<00:09:15.800> problems<00:09:16.120> in 00:09:16.389 --> 00:09:16.399 align:start position:0% like you know okay there are problems in 00:09:16.399 --> 00:09:19.110 align:start position:0% like you know okay there are problems in society<00:09:17.240> and<00:09:17.399> we<00:09:17.519> have<00:09:17.760> privacy<00:09:18.240> issues<00:09:18.920> like 00:09:19.110 --> 00:09:19.120 align:start position:0% society and we have privacy issues like 00:09:19.120 --> 00:09:20.550 align:start position:0% society and we have privacy issues like just<00:09:19.240> throw<00:09:19.440> NPC<00:09:19.839> at<00:09:19.959> it<00:09:20.079> like<00:09:20.240> just<00:09:20.360> throw 00:09:20.550 --> 00:09:20.560 align:start position:0% just throw NPC at it like just throw 00:09:20.560 --> 00:09:23.430 align:start position:0% just throw NPC at it like just throw some<00:09:20.720> crypto<00:09:21.040> tools<00:09:21.360> at<00:09:21.519> it<00:09:22.519> and<00:09:23.000> that's<00:09:23.160> all 00:09:23.430 --> 00:09:23.440 align:start position:0% some crypto tools at it and that's all 00:09:23.440 --> 00:09:26.430 align:start position:0% some crypto tools at it and that's all fine<00:09:23.760> like<00:09:23.920> your<00:09:24.160> problem<00:09:24.399> is<00:09:24.920> solved<00:09:25.920> um<00:09:26.320> but 00:09:26.430 --> 00:09:26.440 align:start position:0% fine like your problem is solved um but 00:09:26.440 --> 00:09:28.030 align:start position:0% fine like your problem is solved um but I<00:09:26.560> don't<00:09:26.720> think<00:09:26.920> this<00:09:27.040> is<00:09:27.279> necessarily<00:09:27.920> the 00:09:28.030 --> 00:09:28.040 align:start position:0% I don't think this is necessarily the 00:09:28.040 --> 00:09:29.430 align:start position:0% I don't think this is necessarily the case<00:09:28.360> because<00:09:28.640> like<00:09:28.760> with<00:09:28.880> the<00:09:28.959> Google 00:09:29.430 --> 00:09:29.440 align:start position:0% case because like with the Google 00:09:29.440 --> 00:09:32.190 align:start position:0% case because like with the Google MasterCard<00:09:30.440> uh<00:09:30.600> example<00:09:31.480> there<00:09:31.680> was<00:09:31.880> really 00:09:32.190 --> 00:09:32.200 align:start position:0% MasterCard uh example there was really 00:09:32.200 --> 00:09:34.910 align:start position:0% MasterCard uh example there was really kind<00:09:32.360> of<00:09:32.680> a<00:09:32.800> lot<00:09:33.000> of<00:09:33.920> not<00:09:34.120> uproar<00:09:34.600> but<00:09:34.720> like 00:09:34.910 --> 00:09:34.920 align:start position:0% kind of a lot of not uproar but like 00:09:34.920 --> 00:09:36.310 align:start position:0% kind of a lot of not uproar but like discussion<00:09:35.399> at<00:09:35.519> the<00:09:35.680> time<00:09:35.880> about<00:09:36.079> whether 00:09:36.310 --> 00:09:36.320 align:start position:0% discussion at the time about whether 00:09:36.320 --> 00:09:38.670 align:start position:0% discussion at the time about whether this<00:09:36.440> is<00:09:36.640> actually<00:09:36.920> good<00:09:37.079> or<00:09:37.240> not<00:09:37.680> like<00:09:38.279> um<00:09:38.600> is 00:09:38.670 --> 00:09:38.680 align:start position:0% this is actually good or not like um is 00:09:38.680 --> 00:09:40.750 align:start position:0% this is actually good or not like um is it<00:09:38.880> good<00:09:39.120> that<00:09:39.320> now<00:09:39.720> Google<00:09:40.000> and<00:09:40.200> MasterCard 00:09:40.750 --> 00:09:40.760 align:start position:0% it good that now Google and MasterCard 00:09:40.760 --> 00:09:43.110 align:start position:0% it good that now Google and MasterCard can<00:09:40.920> collaborate<00:09:41.399> on<00:09:41.519> our<00:09:41.720> data<00:09:42.040> okay<00:09:42.200> sure<00:09:43.000> I 00:09:43.110 --> 00:09:43.120 align:start position:0% can collaborate on our data okay sure I 00:09:43.120 --> 00:09:45.310 align:start position:0% can collaborate on our data okay sure I can't<00:09:43.320> be<00:09:43.480> singled<00:09:43.959> out<00:09:44.160> it's<00:09:44.320> not<00:09:44.560> my<00:09:44.800> data 00:09:45.310 --> 00:09:45.320 align:start position:0% can't be singled out it's not my data 00:09:45.320 --> 00:09:48.430 align:start position:0% can't be singled out it's not my data necessarily<00:09:46.320> but<00:09:46.560> like<00:09:47.240> um<00:09:47.680> as<00:09:47.800> a<00:09:47.959> group<00:09:48.279> we 00:09:48.430 --> 00:09:48.440 align:start position:0% necessarily but like um as a group we 00:09:48.440 --> 00:09:50.590 align:start position:0% necessarily but like um as a group we all<00:09:48.680> kind<00:09:48.839> of<00:09:49.320> suffer<00:09:49.800> because<00:09:50.079> Google<00:09:50.440> has 00:09:50.590 --> 00:09:50.600 align:start position:0% all kind of suffer because Google has 00:09:50.600 --> 00:09:53.150 align:start position:0% all kind of suffer because Google has more<00:09:50.880> power<00:09:51.720> and<00:09:51.839> so<00:09:52.240> this<00:09:52.399> is<00:09:52.560> a<00:09:52.720> bit 00:09:53.150 --> 00:09:53.160 align:start position:0% more power and so this is a bit 00:09:53.160 --> 00:09:56.190 align:start position:0% more power and so this is a bit questionable<00:09:54.120> um<00:09:54.440> so<00:09:54.839> it's<00:09:55.040> not<00:09:55.360> really<00:09:55.959> like 00:09:56.190 --> 00:09:56.200 align:start position:0% questionable um so it's not really like 00:09:56.200 --> 00:09:57.990 align:start position:0% questionable um so it's not really like just<00:09:56.399> throwing<00:09:56.800> MPC<00:09:57.320> or<00:09:57.519> just<00:09:57.640> throwing 00:09:57.990 --> 00:09:58.000 align:start position:0% just throwing MPC or just throwing 00:09:58.000 --> 00:09:59.710 align:start position:0% just throwing MPC or just throwing cryptographic<00:09:58.560> tools<00:09:58.800> at<00:09:58.920> a<00:09:59.040> problem<00:09:59.440> doesn't 00:09:59.710 --> 00:09:59.720 align:start position:0% cryptographic tools at a problem doesn't 00:09:59.720 --> 00:10:01.790 align:start position:0% cryptographic tools at a problem doesn't necessarily<00:10:00.279> solve<00:10:00.680> the<00:10:00.839> Privacy<00:10:01.279> issue<00:10:01.600> that 00:10:01.790 --> 00:10:01.800 align:start position:0% necessarily solve the Privacy issue that 00:10:01.800 --> 00:10:05.350 align:start position:0% necessarily solve the Privacy issue that kind<00:10:01.920> of<00:10:02.040> underlies<00:10:02.600> the<00:10:02.720> whole<00:10:03.440> thing<00:10:04.440> and<00:10:04.600> so 00:10:05.350 --> 00:10:05.360 align:start position:0% kind of underlies the whole thing and so 00:10:05.360 --> 00:10:07.550 align:start position:0% kind of underlies the whole thing and so the<00:10:05.560> question<00:10:05.959> then<00:10:06.200> I<00:10:06.240> mean<00:10:06.480> like<00:10:06.839> I 00:10:07.550 --> 00:10:07.560 align:start position:0% the question then I mean like I 00:10:07.560 --> 00:10:10.430 align:start position:0% the question then I mean like I think<00:10:08.560> is<00:10:08.640> it<00:10:09.000> possible<00:10:09.399> to<00:10:09.560> solve<00:10:09.880> these<00:10:10.320> you 00:10:10.430 --> 00:10:10.440 align:start position:0% think is it possible to solve these you 00:10:10.440 --> 00:10:12.389 align:start position:0% think is it possible to solve these you know<00:10:10.640> like<00:10:11.040> how<00:10:11.200> do<00:10:11.320> you<00:10:11.480> start<00:10:11.760> to<00:10:12.160> think 00:10:12.389 --> 00:10:12.399 align:start position:0% know like how do you start to think 00:10:12.399 --> 00:10:14.829 align:start position:0% know like how do you start to think about<00:10:12.800> solving<00:10:13.399> privacy<00:10:13.839> issues<00:10:14.200> or<00:10:14.480> like<00:10:14.720> you 00:10:14.829 --> 00:10:14.839 align:start position:0% about solving privacy issues or like you 00:10:14.839 --> 00:10:18.230 align:start position:0% about solving privacy issues or like you know<00:10:15.760> um<00:10:16.760> adhering<00:10:17.200> to<00:10:17.399> these<00:10:17.600> Cipher<00:10:17.959> Punk 00:10:18.230 --> 00:10:18.240 align:start position:0% know um adhering to these Cipher Punk 00:10:18.240 --> 00:10:20.590 align:start position:0% know um adhering to these Cipher Punk values<00:10:18.600> with<00:10:18.760> cryptographic<00:10:19.440> tools<00:10:20.440> and 00:10:20.590 --> 00:10:20.600 align:start position:0% values with cryptographic tools and 00:10:20.600 --> 00:10:22.910 align:start position:0% values with cryptographic tools and there<00:10:20.760> are<00:10:21.040> some<00:10:21.480> super<00:10:21.800> nice<00:10:22.120> examples<00:10:22.720> which 00:10:22.910 --> 00:10:22.920 align:start position:0% there are some super nice examples which 00:10:22.920 --> 00:10:25.470 align:start position:0% there are some super nice examples which maybe<00:10:23.360> you<00:10:23.560> have<00:10:23.800> actually<00:10:24.040> seen<00:10:24.920> at<00:10:25.120> this 00:10:25.470 --> 00:10:25.480 align:start position:0% maybe you have actually seen at this 00:10:25.480 --> 00:10:27.990 align:start position:0% maybe you have actually seen at this venue<00:10:26.079> so<00:10:26.320> one<00:10:26.440> of<00:10:26.560> them<00:10:26.680> is<00:10:26.800> from<00:10:27.040> cursive<00:10:27.720> who 00:10:27.990 --> 00:10:28.000 align:start position:0% venue so one of them is from cursive who 00:10:28.000 --> 00:10:29.750 align:start position:0% venue so one of them is from cursive who are<00:10:28.600> um<00:10:28.760> a<00:10:28.880> small<00:10:29.079> team<00:10:29.320> team<00:10:29.519> who<00:10:29.640> are 00:10:29.750 --> 00:10:29.760 align:start position:0% are um a small team team who are 00:10:29.760 --> 00:10:32.190 align:start position:0% are um a small team team who are building<00:10:30.760> privacy<00:10:31.160> preserving 00:10:32.190 --> 00:10:32.200 align:start position:0% building privacy preserving 00:10:32.200 --> 00:10:34.509 align:start position:0% building privacy preserving applications<00:10:33.200> and<00:10:33.399> they<00:10:33.560> are<00:10:33.760> doing<00:10:34.360> uh 00:10:34.509 --> 00:10:34.519 align:start position:0% applications and they are doing uh 00:10:34.519 --> 00:10:36.470 align:start position:0% applications and they are doing uh private<00:10:34.839> proof<00:10:35.120> delegation<00:10:35.760> so<00:10:36.000> this<00:10:36.160> means 00:10:36.470 --> 00:10:36.480 align:start position:0% private proof delegation so this means 00:10:36.480 --> 00:10:38.949 align:start position:0% private proof delegation so this means that<00:10:37.120> um<00:10:37.399> actually<00:10:37.680> you<00:10:38.079> have<00:10:38.320> these<00:10:38.519> badges 00:10:38.949 --> 00:10:38.959 align:start position:0% that um actually you have these badges 00:10:38.959 --> 00:10:41.870 align:start position:0% that um actually you have these badges or<00:10:39.120> some<00:10:39.320> stickers<00:10:39.760> or<00:10:39.959> some<00:10:40.480> uh<00:10:41.240> uh<00:10:41.360> coar 00:10:41.870 --> 00:10:41.880 align:start position:0% or some stickers or some uh uh coar 00:10:41.880 --> 00:10:43.870 align:start position:0% or some stickers or some uh uh coar bracelets<00:10:42.279> or<00:10:42.440> whatever<00:10:42.760> they're<00:10:43.040> downstairs 00:10:43.870 --> 00:10:43.880 align:start position:0% bracelets or whatever they're downstairs 00:10:43.880 --> 00:10:46.590 align:start position:0% bracelets or whatever they're downstairs in<00:10:44.360> uh<00:10:44.880> in<00:10:45.000> the<00:10:45.120> main<00:10:45.440> hall<00:10:45.880> just<00:10:46.120> after<00:10:46.440> the 00:10:46.590 --> 00:10:46.600 align:start position:0% in uh in the main hall just after the 00:10:46.600 --> 00:10:49.030 align:start position:0% in uh in the main hall just after the registration<00:10:47.240> you<00:10:47.360> can<00:10:47.560> go<00:10:48.440> and<00:10:48.600> essentially 00:10:49.030 --> 00:10:49.040 align:start position:0% registration you can go and essentially 00:10:49.040 --> 00:10:52.470 align:start position:0% registration you can go and essentially it's<00:10:49.160> a<00:10:49.800> a<00:10:50.639> a<00:10:50.920> chip<00:10:51.480> that<00:10:51.639> you<00:10:51.800> can<00:10:52.040> tap<00:10:52.360> with 00:10:52.470 --> 00:10:52.480 align:start position:0% it's a a a chip that you can tap with 00:10:52.480 --> 00:10:55.069 align:start position:0% it's a a a chip that you can tap with your<00:10:52.720> phone<00:10:53.720> you<00:10:53.839> can<00:10:53.959> enter<00:10:54.240> your<00:10:54.399> socials 00:10:55.069 --> 00:10:55.079 align:start position:0% your phone you can enter your socials 00:10:55.079 --> 00:10:56.509 align:start position:0% your phone you can enter your socials and<00:10:55.200> then<00:10:55.360> when<00:10:55.480> you<00:10:55.639> tap<00:10:55.920> other<00:10:56.160> people's 00:10:56.509 --> 00:10:56.519 align:start position:0% and then when you tap other people's 00:10:56.519 --> 00:10:58.870 align:start position:0% and then when you tap other people's chips<00:10:57.160> you<00:10:57.279> can<00:10:57.480> do<00:10:57.639> a<00:10:57.800> private<00:10:58.120> intersection 00:10:58.870 --> 00:10:58.880 align:start position:0% chips you can do a private intersection 00:10:58.880 --> 00:11:00.350 align:start position:0% chips you can do a private intersection of<00:10:59.000> your 00:11:00.350 --> 00:11:00.360 align:start position:0% of your 00:11:00.360 --> 00:11:02.389 align:start position:0% of your uh<00:11:00.560> common<00:11:01.079> connections<00:11:01.560> so<00:11:01.839> the<00:11:02.000> common 00:11:02.389 --> 00:11:02.399 align:start position:0% uh common connections so the common 00:11:02.399 --> 00:11:05.190 align:start position:0% uh common connections so the common people<00:11:02.639> that<00:11:02.800> you've<00:11:03.040> met<00:11:03.320> and<00:11:04.040> tapped<00:11:05.040> and 00:11:05.190 --> 00:11:05.200 align:start position:0% people that you've met and tapped and 00:11:05.200 --> 00:11:07.750 align:start position:0% people that you've met and tapped and then<00:11:05.320> you<00:11:05.519> generate<00:11:05.880> approve<00:11:06.480> on<00:11:06.880> this<00:11:07.600> uh 00:11:07.750 --> 00:11:07.760 align:start position:0% then you generate approve on this uh 00:11:07.760 --> 00:11:10.389 align:start position:0% then you generate approve on this uh private<00:11:08.160> intersection<00:11:09.160> to<00:11:09.680> prove<00:11:10.040> how<00:11:10.160> many 00:11:10.389 --> 00:11:10.399 align:start position:0% private intersection to prove how many 00:11:10.399 --> 00:11:11.750 align:start position:0% private intersection to prove how many connections<00:11:10.880> you<00:11:11.000> have<00:11:11.120> in<00:11:11.279> common<00:11:11.560> and<00:11:11.639> then 00:11:11.750 --> 00:11:11.760 align:start position:0% connections you have in common and then 00:11:11.760 --> 00:11:12.990 align:start position:0% connections you have in common and then you<00:11:11.839> can<00:11:11.959> write<00:11:12.160> up<00:11:12.240> the<00:11:12.320> leader<00:11:12.600> board<00:11:12.800> rise 00:11:12.990 --> 00:11:13.000 align:start position:0% you can write up the leader board rise 00:11:13.000 --> 00:11:15.269 align:start position:0% you can write up the leader board rise up<00:11:13.120> the<00:11:13.200> leaderboard<00:11:13.600> and<00:11:13.720> get<00:11:13.800> some<00:11:14.040> merch<00:11:15.040> um 00:11:15.269 --> 00:11:15.279 align:start position:0% up the leaderboard and get some merch um 00:11:15.279 --> 00:11:17.750 align:start position:0% up the leaderboard and get some merch um crypto<00:11:15.639> conference<00:11:16.160> style<00:11:17.160> and<00:11:17.519> but<00:11:17.639> the 00:11:17.750 --> 00:11:17.760 align:start position:0% crypto conference style and but the 00:11:17.760 --> 00:11:19.910 align:start position:0% crypto conference style and but the reason<00:11:18.000> that<00:11:18.120> this<00:11:18.240> is<00:11:18.399> interesting<00:11:19.279> uh<00:11:19.480> is 00:11:19.910 --> 00:11:19.920 align:start position:0% reason that this is interesting uh is 00:11:19.920 --> 00:11:23.150 align:start position:0% reason that this is interesting uh is because<00:11:20.480> you<00:11:20.639> know<00:11:21.160> as<00:11:21.920> uh<00:11:22.600> Things<00:11:22.800> become<00:11:23.040> a 00:11:23.150 --> 00:11:23.160 align:start position:0% because you know as uh Things become a 00:11:23.160 --> 00:11:25.269 align:start position:0% because you know as uh Things become a bit<00:11:23.320> more<00:11:23.480> complicated<00:11:23.880> the<00:11:24.000> proofs<00:11:24.320> get<00:11:24.560> big 00:11:25.269 --> 00:11:25.279 align:start position:0% bit more complicated the proofs get big 00:11:25.279 --> 00:11:28.910 align:start position:0% bit more complicated the proofs get big and<00:11:25.440> actually<00:11:25.680> your<00:11:25.839> phone<00:11:26.600> gets<00:11:26.880> slow<00:11:27.560> and<00:11:28.240> um 00:11:28.910 --> 00:11:28.920 align:start position:0% and actually your phone gets slow and um 00:11:28.920 --> 00:11:30.190 align:start position:0% and actually your phone gets slow and um you<00:11:29.040> know<00:11:29.440> these<00:11:29.560> things<00:11:29.760> need<00:11:29.959> some 00:11:30.190 --> 00:11:30.200 align:start position:0% you know these things need some 00:11:30.200 --> 00:11:31.949 align:start position:0% you know these things need some libraries<00:11:30.680> for<00:11:30.920> verification<00:11:31.519> and<00:11:31.680> proof 00:11:31.949 --> 00:11:31.959 align:start position:0% libraries for verification and proof 00:11:31.959 --> 00:11:34.590 align:start position:0% libraries for verification and proof generation<00:11:32.360> and<00:11:32.519> all<00:11:32.680> sorts<00:11:32.880> of<00:11:33.040> stuff<00:11:33.920> so 00:11:34.590 --> 00:11:34.600 align:start position:0% generation and all sorts of stuff so 00:11:34.600 --> 00:11:35.949 align:start position:0% generation and all sorts of stuff so sometimes<00:11:34.800> it<00:11:34.920> becomes<00:11:35.160> a<00:11:35.279> bit<00:11:35.440> restrictive 00:11:35.949 --> 00:11:35.959 align:start position:0% sometimes it becomes a bit restrictive 00:11:35.959 --> 00:11:37.790 align:start position:0% sometimes it becomes a bit restrictive to<00:11:36.160> actually<00:11:36.399> do<00:11:36.639> proof<00:11:36.920> generation<00:11:37.480> on<00:11:37.639> your 00:11:37.790 --> 00:11:37.800 align:start position:0% to actually do proof generation on your 00:11:37.800 --> 00:11:40.030 align:start position:0% to actually do proof generation on your phone<00:11:38.279> so<00:11:38.600> then<00:11:39.000> an<00:11:39.160> answer<00:11:39.480> might<00:11:39.639> be<00:11:39.839> well 00:11:40.030 --> 00:11:40.040 align:start position:0% phone so then an answer might be well 00:11:40.040 --> 00:11:41.710 align:start position:0% phone so then an answer might be well why<00:11:40.160> don't<00:11:40.399> we<00:11:40.600> actually<00:11:40.839> start<00:11:41.120> delegating 00:11:41.710 --> 00:11:41.720 align:start position:0% why don't we actually start delegating 00:11:41.720 --> 00:11:44.269 align:start position:0% why don't we actually start delegating proofs<00:11:42.600> and<00:11:42.720> you<00:11:42.839> see<00:11:43.120> this<00:11:43.279> a<00:11:43.519> lot<00:11:43.760> lot<00:11:44.000> with<00:11:44.200> I 00:11:44.269 --> 00:11:44.279 align:start position:0% proofs and you see this a lot lot with I 00:11:44.279 --> 00:11:46.550 align:start position:0% proofs and you see this a lot lot with I think<00:11:44.839> um<00:11:45.399> the<00:11:45.480> development<00:11:46.000> of<00:11:46.279> proof 00:11:46.550 --> 00:11:46.560 align:start position:0% think um the development of proof 00:11:46.560 --> 00:11:48.230 align:start position:0% think um the development of proof markets<00:11:47.000> so<00:11:47.200> like<00:11:47.320> all<00:11:47.480> these<00:11:47.639> proof<00:11:47.880> Markets 00:11:48.230 --> 00:11:48.240 align:start position:0% markets so like all these proof Markets 00:11:48.240 --> 00:11:50.350 align:start position:0% markets so like all these proof Markets started<00:11:48.560> popping<00:11:48.839> up<00:11:49.040> over<00:11:49.240> the<00:11:49.399> last<00:11:49.639> years 00:11:50.350 --> 00:11:50.360 align:start position:0% started popping up over the last years 00:11:50.360 --> 00:11:52.310 align:start position:0% started popping up over the last years to<00:11:50.519> say<00:11:50.760> like<00:11:50.920> ah<00:11:51.160> hey<00:11:51.320> we<00:11:51.440> can<00:11:51.839> you<00:11:51.959> know<00:11:52.160> have 00:11:52.310 --> 00:11:52.320 align:start position:0% to say like ah hey we can you know have 00:11:52.320 --> 00:11:54.509 align:start position:0% to say like ah hey we can you know have some<00:11:52.880> pure<00:11:53.320> beefy<00:11:53.760> machines<00:11:54.240> that<00:11:54.360> will 00:11:54.509 --> 00:11:54.519 align:start position:0% some pure beefy machines that will 00:11:54.519 --> 00:11:57.110 align:start position:0% some pure beefy machines that will generate<00:11:54.920> your<00:11:55.240> proofs<00:11:55.639> really<00:11:55.880> fast<00:11:56.120> for<00:11:56.279> you 00:11:57.110 --> 00:11:57.120 align:start position:0% generate your proofs really fast for you 00:11:57.120 --> 00:11:58.710 align:start position:0% generate your proofs really fast for you which<00:11:57.240> is<00:11:57.480> great<00:11:57.800> but<00:11:58.000> like<00:11:58.120> if<00:11:58.200> you<00:11:58.360> have<00:11:58.519> any 00:11:58.710 --> 00:11:58.720 align:start position:0% which is great but like if you have any 00:11:58.720 --> 00:12:00.509 align:start position:0% which is great but like if you have any sort<00:11:58.880> of<00:11:59.240> sense<00:11:59.399> of<00:11:59.560> privacy<00:12:00.000> at<00:12:00.120> all<00:12:00.279> this<00:12:00.399> is 00:12:00.509 --> 00:12:00.519 align:start position:0% sort of sense of privacy at all this is 00:12:00.519 --> 00:12:01.870 align:start position:0% sort of sense of privacy at all this is terrible<00:12:00.920> now<00:12:01.120> because<00:12:01.360> now<00:12:01.519> you're<00:12:01.720> just 00:12:01.870 --> 00:12:01.880 align:start position:0% terrible now because now you're just 00:12:01.880 --> 00:12:04.069 align:start position:0% terrible now because now you're just Outsourcing<00:12:02.519> all<00:12:02.720> your<00:12:03.000> private<00:12:03.320> data<00:12:03.680> to 00:12:04.069 --> 00:12:04.079 align:start position:0% Outsourcing all your private data to 00:12:04.079 --> 00:12:05.750 align:start position:0% Outsourcing all your private data to This<00:12:04.279> Server<00:12:04.680> who<00:12:04.800> will<00:12:04.959> generate<00:12:05.320> proofs<00:12:05.600> for 00:12:05.750 --> 00:12:05.760 align:start position:0% This Server who will generate proofs for 00:12:05.760 --> 00:12:08.190 align:start position:0% This Server who will generate proofs for you<00:12:05.920> very<00:12:06.120> quickly<00:12:07.040> but<00:12:07.399> um<00:12:07.639> yeah<00:12:07.800> you<00:12:07.959> don't 00:12:08.190 --> 00:12:08.200 align:start position:0% you very quickly but um yeah you don't 00:12:08.200 --> 00:12:11.310 align:start position:0% you very quickly but um yeah you don't get<00:12:08.360> any<00:12:08.600> privacy<00:12:09.560> here<00:12:10.560> uh<00:12:10.680> you<00:12:10.839> Outsource 00:12:11.310 --> 00:12:11.320 align:start position:0% get any privacy here uh you Outsource 00:12:11.320 --> 00:12:13.310 align:start position:0% get any privacy here uh you Outsource your<00:12:11.440> proof<00:12:11.720> generation<00:12:12.200> but<00:12:12.440> you<00:12:12.560> do<00:12:12.680> it<00:12:12.760> in<00:12:12.880> a 00:12:13.310 --> 00:12:13.320 align:start position:0% your proof generation but you do it in a 00:12:13.320 --> 00:12:16.150 align:start position:0% your proof generation but you do it in a secret<00:12:14.160> uh<00:12:14.240> shared<00:12:14.720> way<00:12:15.279> like<00:12:15.399> in<00:12:15.519> this<00:12:15.680> MPC 00:12:16.150 --> 00:12:16.160 align:start position:0% secret uh shared way like in this MPC 00:12:16.160 --> 00:12:18.230 align:start position:0% secret uh shared way like in this MPC way<00:12:16.959> um<00:12:17.079> and<00:12:17.199> you<00:12:17.320> generate<00:12:17.680> the<00:12:17.800> proof<00:12:18.040> over 00:12:18.230 --> 00:12:18.240 align:start position:0% way um and you generate the proof over 00:12:18.240 --> 00:12:20.870 align:start position:0% way um and you generate the proof over those<00:12:18.399> secret<00:12:18.720> shairs<00:12:19.600> and<00:12:19.760> so<00:12:20.399> um<00:12:20.600> this<00:12:20.720> is 00:12:20.870 --> 00:12:20.880 align:start position:0% those secret shairs and so um this is 00:12:20.880 --> 00:12:23.790 align:start position:0% those secret shairs and so um this is being<00:12:21.120> done<00:12:21.760> now<00:12:22.199> downstairs<00:12:23.199> not<00:12:23.320> downstairs 00:12:23.790 --> 00:12:23.800 align:start position:0% being done now downstairs not downstairs 00:12:23.800 --> 00:12:26.870 align:start position:0% being done now downstairs not downstairs but<00:12:23.959> like<00:12:24.079> in<00:12:24.199> the<00:12:24.639> internet<00:12:25.639> you<00:12:25.760> can<00:12:25.880> see<00:12:26.040> it 00:12:26.870 --> 00:12:26.880 align:start position:0% but like in the internet you can see it 00:12:26.880 --> 00:12:28.949 align:start position:0% but like in the internet you can see it downstairs<00:12:27.880> um<00:12:28.000> so<00:12:28.199> yeah<00:12:28.360> this<00:12:28.519> just<00:12:28.680> happened 00:12:28.949 --> 00:12:28.959 align:start position:0% downstairs um so yeah this just happened 00:12:28.959 --> 00:12:30.949 align:start position:0% downstairs um so yeah this just happened yest<00:12:29.279> today<00:12:29.600> and<00:12:29.720> when<00:12:29.839> I<00:12:29.959> say<00:12:30.279> actually<00:12:30.880> you 00:12:30.949 --> 00:12:30.959 align:start position:0% yest today and when I say actually you 00:12:30.959 --> 00:12:32.509 align:start position:0% yest today and when I say actually you can<00:12:31.120> Outsource<00:12:31.600> this<00:12:31.720> to<00:12:31.839> a<00:12:31.959> network<00:12:32.360> this 00:12:32.509 --> 00:12:32.519 align:start position:0% can Outsource this to a network this 00:12:32.519 --> 00:12:34.509 align:start position:0% can Outsource this to a network this network<00:12:32.920> is<00:12:33.040> not<00:12:33.279> this<00:12:33.560> uh<00:12:33.680> mystical<00:12:34.120> being<00:12:34.399> in 00:12:34.509 --> 00:12:34.519 align:start position:0% network is not this uh mystical being in 00:12:34.519 --> 00:12:36.310 align:start position:0% network is not this uh mystical being in the<00:12:34.680> sky<00:12:34.959> as<00:12:35.079> it<00:12:35.240> has<00:12:35.360> been<00:12:35.519> for<00:12:35.720> the<00:12:35.839> past<00:12:36.040> 20 00:12:36.310 --> 00:12:36.320 align:start position:0% the sky as it has been for the past 20 00:12:36.320 --> 00:12:38.550 align:start position:0% the sky as it has been for the past 20 years<00:12:36.880> now<00:12:37.040> it<00:12:37.199> is<00:12:37.360> actually<00:12:37.639> live<00:12:38.199> um<00:12:38.360> so 00:12:38.550 --> 00:12:38.560 align:start position:0% years now it is actually live um so 00:12:38.560 --> 00:12:40.590 align:start position:0% years now it is actually live um so there's<00:12:38.800> one<00:12:39.440> Network<00:12:39.839> that<00:12:39.920> has<00:12:40.040> run<00:12:40.279> between 00:12:40.590 --> 00:12:40.600 align:start position:0% there's one Network that has run between 00:12:40.600 --> 00:12:43.110 align:start position:0% there's one Network that has run between us<00:12:40.839> T<00:12:41.639> the<00:12:41.760> cursive<00:12:42.240> guys<00:12:42.440> who<00:12:42.600> built<00:12:42.880> this 00:12:43.110 --> 00:12:43.120 align:start position:0% us T the cursive guys who built this 00:12:43.120 --> 00:12:45.230 align:start position:0% us T the cursive guys who built this nice<00:12:43.480> uh<00:12:43.600> cryptographic<00:12:44.199> connections<00:12:44.680> app 00:12:45.230 --> 00:12:45.240 align:start position:0% nice uh cryptographic connections app 00:12:45.240 --> 00:12:47.949 align:start position:0% nice uh cryptographic connections app and<00:12:45.399> the<00:12:45.519> psse<00:12:46.199> group<00:12:47.199> so<00:12:47.399> each<00:12:47.560> of<00:12:47.680> us<00:12:47.800> are 00:12:47.949 --> 00:12:47.959 align:start position:0% and the psse group so each of us are 00:12:47.959 --> 00:12:49.949 align:start position:0% and the psse group so each of us are running<00:12:48.440> um<00:12:48.600> a<00:12:48.680> bunch<00:12:48.880> of<00:12:49.000> notes<00:12:49.320> that<00:12:49.440> are 00:12:49.949 --> 00:12:49.959 align:start position:0% running um a bunch of notes that are 00:12:49.959 --> 00:12:52.949 align:start position:0% running um a bunch of notes that are generating<00:12:50.600> these<00:12:51.240> uh<00:12:51.760> proofs<00:12:52.160> on<00:12:52.440> these<00:12:52.839> uh 00:12:52.949 --> 00:12:52.959 align:start position:0% generating these uh proofs on these uh 00:12:52.959 --> 00:12:55.629 align:start position:0% generating these uh proofs on these uh secret<00:12:53.519> chairs<00:12:54.519> so<00:12:54.880> yeah<00:12:55.040> go<00:12:55.199> down<00:12:55.320> and<00:12:55.440> see 00:12:55.629 --> 00:12:55.639 align:start position:0% secret chairs so yeah go down and see 00:12:55.639 --> 00:12:57.910 align:start position:0% secret chairs so yeah go down and see them<00:12:55.800> if<00:12:55.880> you<00:12:56.000> want<00:12:56.120> to<00:12:56.440> actually<00:12:56.760> feel<00:12:57.279> ly<00:12:57.800> in 00:12:57.910 --> 00:12:57.920 align:start position:0% them if you want to actually feel ly in 00:12:57.920 --> 00:13:00.350 align:start position:0% them if you want to actually feel ly in your<00:12:58.040> hands<00:12:58.560> there's<00:12:58.760> also<00:12:59.360> actually<00:12:59.639> an<00:12:59.800> MPC 00:13:00.350 --> 00:13:00.360 align:start position:0% your hands there's also actually an MPC 00:13:00.360 --> 00:13:02.829 align:start position:0% your hands there's also actually an MPC exhibition<00:13:00.880> that<00:13:01.000> you<00:13:01.120> can<00:13:01.240> learn<00:13:01.519> more<00:13:02.399> um<00:13:02.680> of 00:13:02.829 --> 00:13:02.839 align:start position:0% exhibition that you can learn more um of 00:13:02.839 --> 00:13:03.470 align:start position:0% exhibition that you can learn more um of the 00:13:03.470 --> 00:13:03.480 align:start position:0% the 00:13:03.480 --> 00:13:05.870 align:start position:0% the history<00:13:04.480> so<00:13:04.760> yeah<00:13:05.320> actually<00:13:05.600> what<00:13:05.720> they're 00:13:05.870 --> 00:13:05.880 align:start position:0% history so yeah actually what they're 00:13:05.880 --> 00:13:07.790 align:start position:0% history so yeah actually what they're doing<00:13:06.240> is<00:13:06.480> collaborative<00:13:06.959> snarks<00:13:07.399> generating 00:13:07.790 --> 00:13:07.800 align:start position:0% doing is collaborative snarks generating 00:13:07.800 --> 00:13:09.230 align:start position:0% doing is collaborative snarks generating collaborative<00:13:08.240> snarks<00:13:08.680> which<00:13:08.800> is<00:13:09.040> just 00:13:09.230 --> 00:13:09.240 align:start position:0% collaborative snarks which is just 00:13:09.240 --> 00:13:10.870 align:start position:0% collaborative snarks which is just generating<00:13:09.639> zero<00:13:09.959> knowledge<00:13:10.279> proofs<00:13:10.600> in<00:13:10.720> an 00:13:10.870 --> 00:13:10.880 align:start position:0% generating zero knowledge proofs in an 00:13:10.880 --> 00:13:14.150 align:start position:0% generating zero knowledge proofs in an MPC<00:13:11.320> Network<00:13:12.320> currently<00:13:13.240> they<00:13:13.360> are<00:13:13.560> using<00:13:13.880> our 00:13:14.150 --> 00:13:14.160 align:start position:0% MPC Network currently they are using our 00:13:14.160 --> 00:13:16.470 align:start position:0% MPC Network currently they are using our tooling<00:13:14.560> actually<00:13:14.800> to<00:13:14.920> do<00:13:15.160> this<00:13:15.480> which<00:13:15.680> is<00:13:16.240> um 00:13:16.470 --> 00:13:16.480 align:start position:0% tooling actually to do this which is um 00:13:16.480 --> 00:13:18.230 align:start position:0% tooling actually to do this which is um available<00:13:16.920> for<00:13:17.199> circom<00:13:17.720> so<00:13:17.839> if<00:13:17.920> you're<00:13:18.040> used 00:13:18.230 --> 00:13:18.240 align:start position:0% available for circom so if you're used 00:13:18.240 --> 00:13:20.350 align:start position:0% available for circom so if you're used to<00:13:18.360> building<00:13:18.639> circom<00:13:19.160> circuits<00:13:19.639> or<00:13:19.839> noira 00:13:20.350 --> 00:13:20.360 align:start position:0% to building circom circuits or noira 00:13:20.360 --> 00:13:22.230 align:start position:0% to building circom circuits or noira circuits<00:13:20.839> which<00:13:20.959> is<00:13:21.360> up<00:13:21.560> and<00:13:21.760> coming<00:13:22.040> and 00:13:22.230 --> 00:13:22.240 align:start position:0% circuits which is up and coming and 00:13:22.240 --> 00:13:23.790 align:start position:0% circuits which is up and coming and getting<00:13:22.480> lots<00:13:22.680> of<00:13:22.800> hype<00:13:23.160> this<00:13:23.279> week<00:13:23.480> in 00:13:23.790 --> 00:13:23.800 align:start position:0% getting lots of hype this week in 00:13:23.800 --> 00:13:25.790 align:start position:0% getting lots of hype this week in particular<00:13:24.800> and<00:13:25.079> now<00:13:25.240> you<00:13:25.360> can<00:13:25.480> use<00:13:25.639> our 00:13:25.790 --> 00:13:25.800 align:start position:0% particular and now you can use our 00:13:25.800 --> 00:13:27.910 align:start position:0% particular and now you can use our tooling<00:13:26.160> to<00:13:26.320> do<00:13:27.000> the<00:13:27.120> same<00:13:27.360> thing<00:13:27.519> but<00:13:27.639> in<00:13:27.760> an 00:13:27.910 --> 00:13:27.920 align:start position:0% tooling to do the same thing but in an 00:13:27.920 --> 00:13:30.269 align:start position:0% tooling to do the same thing but in an MPC<00:13:28.320> environment 00:13:30.269 --> 00:13:30.279 align:start position:0% MPC environment 00:13:30.279 --> 00:13:32.629 align:start position:0% MPC environment um<00:13:30.560> so<00:13:31.040> yeah<00:13:31.240> that's<00:13:31.440> snarks<00:13:32.000> and<00:13:32.079> so<00:13:32.279> yeah<00:13:32.440> all 00:13:32.629 --> 00:13:32.639 align:start position:0% um so yeah that's snarks and so yeah all 00:13:32.639 --> 00:13:34.230 align:start position:0% um so yeah that's snarks and so yeah all the<00:13:33.000> stuff<00:13:33.240> that<00:13:33.360> you<00:13:33.519> will<00:13:33.680> generate<00:13:34.079> here 00:13:34.230 --> 00:13:34.240 align:start position:0% the stuff that you will generate here 00:13:34.240 --> 00:13:38.990 align:start position:0% the stuff that you will generate here are<00:13:34.480> clabber<00:13:34.839> of<00:13:35.199> snarks<00:13:36.199> and<00:13:36.320> so<00:13:37.480> uh<00:13:38.480> how<00:13:38.800> is 00:13:38.990 --> 00:13:39.000 align:start position:0% are clabber of snarks and so uh how is 00:13:39.000 --> 00:13:40.829 align:start position:0% are clabber of snarks and so uh how is all<00:13:39.120> of<00:13:39.279> this<00:13:39.480> stuff<00:13:39.760> actually<00:13:40.000> leading<00:13:40.399> to 00:13:40.829 --> 00:13:40.839 align:start position:0% all of this stuff actually leading to 00:13:40.839 --> 00:13:42.829 align:start position:0% all of this stuff actually leading to these<00:13:41.040> kind<00:13:41.160> of<00:13:41.360> new<00:13:41.800> nice<00:13:42.279> things<00:13:42.560> that<00:13:42.680> are 00:13:42.829 --> 00:13:42.839 align:start position:0% these kind of new nice things that are 00:13:42.839 --> 00:13:44.750 align:start position:0% these kind of new nice things that are not<00:13:43.079> just<00:13:43.279> getting<00:13:43.560> us<00:13:43.720> around<00:13:44.120> regulation 00:13:44.750 --> 00:13:44.760 align:start position:0% not just getting us around regulation 00:13:44.760 --> 00:13:47.550 align:start position:0% not just getting us around regulation but<00:13:44.959> like<00:13:45.480> this<00:13:45.760> actually<00:13:46.160> cool<00:13:46.920> solving 00:13:47.550 --> 00:13:47.560 align:start position:0% but like this actually cool solving 00:13:47.560 --> 00:13:49.990 align:start position:0% but like this actually cool solving privacy<00:13:48.079> problems<00:13:48.519> kind<00:13:48.639> of<00:13:48.800> tech<00:13:49.760> and<00:13:49.880> I 00:13:49.990 --> 00:13:50.000 align:start position:0% privacy problems kind of tech and I 00:13:50.000 --> 00:13:51.389 align:start position:0% privacy problems kind of tech and I think<00:13:50.160> the<00:13:50.360> most<00:13:50.639> interesting<00:13:51.079> thing<00:13:51.240> that 00:13:51.389 --> 00:13:51.399 align:start position:0% think the most interesting thing that 00:13:51.399 --> 00:13:53.230 align:start position:0% think the most interesting thing that MPC<00:13:51.880> is<00:13:52.000> kind<00:13:52.120> of<00:13:52.240> enabling<00:13:52.720> now<00:13:52.920> in<00:13:53.120> this 00:13:53.230 --> 00:13:53.240 align:start position:0% MPC is kind of enabling now in this 00:13:53.240 --> 00:13:55.030 align:start position:0% MPC is kind of enabling now in this blockchain<00:13:53.680> world<00:13:53.959> is<00:13:54.120> this<00:13:54.360> private<00:13:54.680> shared 00:13:55.030 --> 00:13:55.040 align:start position:0% blockchain world is this private shared 00:13:55.040 --> 00:13:57.310 align:start position:0% blockchain world is this private shared state<00:13:55.360> so<00:13:55.519> you<00:13:55.639> have<00:13:55.880> these<00:13:56.639> um<00:13:56.880> private 00:13:57.310 --> 00:13:57.320 align:start position:0% state so you have these um private 00:13:57.320 --> 00:14:00.550 align:start position:0% state so you have these um private blockchains<00:13:57.920> or<00:13:58.079> l1s<00:13:58.639> or<00:13:58.759> l<00:13:59.480> like<00:13:59.880> Alo<00:14:00.399> and 00:14:00.550 --> 00:14:00.560 align:start position:0% blockchains or l1s or l like Alo and 00:14:00.560 --> 00:14:03.110 align:start position:0% blockchains or l1s or l like Alo and Aztec<00:14:01.079> who<00:14:01.600> now<00:14:01.839> have<00:14:02.000> zero<00:14:02.360> knowledge<00:14:02.720> smart 00:14:03.110 --> 00:14:03.120 align:start position:0% Aztec who now have zero knowledge smart 00:14:03.120 --> 00:14:04.629 align:start position:0% Aztec who now have zero knowledge smart contracts<00:14:03.519> and<00:14:03.680> they<00:14:03.839> have<00:14:04.079> like<00:14:04.279> private 00:14:04.629 --> 00:14:04.639 align:start position:0% contracts and they have like private 00:14:04.639 --> 00:14:07.069 align:start position:0% contracts and they have like private State<00:14:05.000> and<00:14:05.320> sometimes<00:14:05.600> public<00:14:05.920> State<00:14:06.279> and<00:14:06.759> you 00:14:07.069 --> 00:14:07.079 align:start position:0% State and sometimes public State and you 00:14:07.079 --> 00:14:08.870 align:start position:0% State and sometimes public State and you generate<00:14:07.519> proofs<00:14:07.880> on<00:14:08.040> your<00:14:08.240> private<00:14:08.560> State 00:14:08.870 --> 00:14:08.880 align:start position:0% generate proofs on your private State 00:14:08.880 --> 00:14:10.430 align:start position:0% generate proofs on your private State and<00:14:09.040> you<00:14:09.160> can<00:14:09.399> do<00:14:09.680> stuff<00:14:09.880> with<00:14:10.040> the<00:14:10.160> public 00:14:10.430 --> 00:14:10.440 align:start position:0% and you can do stuff with the public 00:14:10.440 --> 00:14:13.870 align:start position:0% and you can do stuff with the public State<00:14:10.720> and<00:14:11.040> interact<00:14:12.040> and<00:14:12.199> this<00:14:12.320> is<00:14:12.519> nice<00:14:12.920> but 00:14:13.870 --> 00:14:13.880 align:start position:0% State and interact and this is nice but 00:14:13.880 --> 00:14:15.550 align:start position:0% State and interact and this is nice but in<00:14:14.000> a<00:14:14.160> sense<00:14:14.399> it's<00:14:14.519> a<00:14:14.639> little<00:14:14.800> bit<00:14:15.079> limited 00:14:15.550 --> 00:14:15.560 align:start position:0% in a sense it's a little bit limited 00:14:15.560 --> 00:14:17.069 align:start position:0% in a sense it's a little bit limited because<00:14:15.880> the<00:14:16.000> zero<00:14:16.279> knowledge<00:14:16.560> proof<00:14:16.839> is<00:14:16.959> just 00:14:17.069 --> 00:14:17.079 align:start position:0% because the zero knowledge proof is just 00:14:17.079 --> 00:14:18.949 align:start position:0% because the zero knowledge proof is just a<00:14:17.240> statement<00:14:17.639> about<00:14:17.839> a<00:14:18.040> fact<00:14:18.399> and<00:14:18.600> like<00:14:18.759> it's 00:14:18.949 --> 00:14:18.959 align:start position:0% a statement about a fact and like it's 00:14:18.959 --> 00:14:20.470 align:start position:0% a statement about a fact and like it's very<00:14:19.360> difficult<00:14:19.480> to<00:14:19.680> actually<00:14:19.920> do 00:14:20.470 --> 00:14:20.480 align:start position:0% very difficult to actually do 00:14:20.480 --> 00:14:23.870 align:start position:0% very difficult to actually do computation<00:14:21.480> with<00:14:21.759> that<00:14:22.440> and<00:14:22.560> so<00:14:23.000> um<00:14:23.519> if<00:14:23.680> you 00:14:23.870 --> 00:14:23.880 align:start position:0% computation with that and so um if you 00:14:23.880 --> 00:14:26.629 align:start position:0% computation with that and so um if you can<00:14:24.560> instead<00:14:25.120> have<00:14:25.360> a<00:14:25.480> sort<00:14:25.639> of<00:14:25.759> MPC<00:14:26.240> Network 00:14:26.629 --> 00:14:26.639 align:start position:0% can instead have a sort of MPC Network 00:14:26.639 --> 00:14:29.430 align:start position:0% can instead have a sort of MPC Network where<00:14:26.800> you<00:14:26.920> can<00:14:27.480> maintain<00:14:27.920> your<00:14:28.120> privacy<00:14:29.199> you 00:14:29.430 --> 00:14:29.440 align:start position:0% where you can maintain your privacy you 00:14:29.440 --> 00:14:32.110 align:start position:0% where you can maintain your privacy you can<00:14:29.680> actually<00:14:29.959> do<00:14:30.680> more<00:14:31.480> Leo<00:14:31.880> you<00:14:31.959> can 00:14:32.110 --> 00:14:32.120 align:start position:0% can actually do more Leo you can 00:14:32.120 --> 00:14:33.749 align:start position:0% can actually do more Leo you can actually<00:14:32.279> do<00:14:32.519> computation<00:14:33.079> on<00:14:33.279> all<00:14:33.440> of<00:14:33.560> your 00:14:33.749 --> 00:14:33.759 align:start position:0% actually do computation on all of your 00:14:33.759 --> 00:14:37.189 align:start position:0% actually do computation on all of your private<00:14:34.079> State<00:14:34.959> instead<00:14:35.279> of<00:14:35.519> just<00:14:36.079> um<00:14:36.959> having 00:14:37.189 --> 00:14:37.199 align:start position:0% private State instead of just um having 00:14:37.199 --> 00:14:39.350 align:start position:0% private State instead of just um having zero<00:14:37.480> knowledge<00:14:37.720> proofs<00:14:37.959> in<00:14:38.120> public<00:14:38.399> State 00:14:39.350 --> 00:14:39.360 align:start position:0% zero knowledge proofs in public State 00:14:39.360 --> 00:14:41.230 align:start position:0% zero knowledge proofs in public State and<00:14:39.480> so<00:14:39.920> um<00:14:40.079> you<00:14:40.199> remember<00:14:40.519> this<00:14:40.680> picture<00:14:40.959> from 00:14:41.230 --> 00:14:41.240 align:start position:0% and so um you remember this picture from 00:14:41.240 --> 00:14:43.509 align:start position:0% and so um you remember this picture from before<00:14:41.680> we<00:14:41.800> had<00:14:42.040> like<00:14:42.199> one<00:14:42.480> party<00:14:43.160> secret 00:14:43.509 --> 00:14:43.519 align:start position:0% before we had like one party secret 00:14:43.519 --> 00:14:46.670 align:start position:0% before we had like one party secret sharing<00:14:43.920> their<00:14:44.120> data<00:14:44.480> to<00:14:44.759> nodes<00:14:45.120> in<00:14:45.240> a<00:14:45.680> network 00:14:46.670 --> 00:14:46.680 align:start position:0% sharing their data to nodes in a network 00:14:46.680 --> 00:14:49.030 align:start position:0% sharing their data to nodes in a network now<00:14:46.880> I<00:14:46.959> think<00:14:47.120> the<00:14:47.240> interesting<00:14:47.880> part<00:14:48.880> with 00:14:49.030 --> 00:14:49.040 align:start position:0% now I think the interesting part with 00:14:49.040 --> 00:14:50.870 align:start position:0% now I think the interesting part with private<00:14:49.320> shared<00:14:49.720> state<00:14:49.959> is<00:14:50.079> when<00:14:50.240> you<00:14:50.480> sort<00:14:50.680> of 00:14:50.870 --> 00:14:50.880 align:start position:0% private shared state is when you sort of 00:14:50.880 --> 00:14:53.590 align:start position:0% private shared state is when you sort of introduce<00:14:51.639> other<00:14:52.560> uh<00:14:52.759> players<00:14:53.160> or<00:14:53.360> other 00:14:53.590 --> 00:14:53.600 align:start position:0% introduce other uh players or other 00:14:53.600 --> 00:14:56.949 align:start position:0% introduce other uh players or other entities<00:14:54.519> so<00:14:54.880> now<00:14:55.399> you<00:14:55.560> can<00:14:55.800> take<00:14:56.360> um<00:14:56.519> secret 00:14:56.949 --> 00:14:56.959 align:start position:0% entities so now you can take um secret 00:14:56.959 --> 00:15:00.110 align:start position:0% entities so now you can take um secret like<00:14:57.680> multiple<00:14:58.199> people<00:14:58.759> can<00:14:59.440> uh<00:14:59.560> share<00:14:59.880> their 00:15:00.110 --> 00:15:00.120 align:start position:0% like multiple people can uh share their 00:15:00.120 --> 00:15:02.069 align:start position:0% like multiple people can uh share their data<00:15:00.480> to<00:15:00.639> a<00:15:00.800> network<00:15:01.320> in<00:15:01.440> a<00:15:01.680> privacy 00:15:02.069 --> 00:15:02.079 align:start position:0% data to a network in a privacy 00:15:02.079 --> 00:15:04.590 align:start position:0% data to a network in a privacy preserving<00:15:02.560> way<00:15:03.000> and<00:15:03.120> the<00:15:03.240> network<00:15:03.600> can<00:15:03.759> do<00:15:04.399> uh 00:15:04.590 --> 00:15:04.600 align:start position:0% preserving way and the network can do uh 00:15:04.600 --> 00:15:06.749 align:start position:0% preserving way and the network can do uh computation<00:15:05.120> over<00:15:05.440> that<00:15:06.000> and<00:15:06.120> I<00:15:06.240> think<00:15:06.639> this 00:15:06.749 --> 00:15:06.759 align:start position:0% computation over that and I think this 00:15:06.759 --> 00:15:08.350 align:start position:0% computation over that and I think this is<00:15:06.959> super<00:15:07.199> nice<00:15:07.519> because<00:15:07.720> we<00:15:07.839> don't<00:15:08.040> have<00:15:08.160> to 00:15:08.350 --> 00:15:08.360 align:start position:0% is super nice because we don't have to 00:15:08.360 --> 00:15:10.350 align:start position:0% is super nice because we don't have to start<00:15:08.680> revealing<00:15:09.320> things<00:15:09.560> to<00:15:09.759> anybody<00:15:10.240> we 00:15:10.350 --> 00:15:10.360 align:start position:0% start revealing things to anybody we 00:15:10.360 --> 00:15:12.430 align:start position:0% start revealing things to anybody we don't<00:15:10.600> have<00:15:10.720> to<00:15:11.199> we<00:15:11.360> have<00:15:11.560> like<00:15:11.720> all<00:15:12.040> full 00:15:12.430 --> 00:15:12.440 align:start position:0% don't have to we have like all full 00:15:12.440 --> 00:15:15.030 align:start position:0% don't have to we have like all full general<00:15:12.880> purpose<00:15:13.360> computation<00:15:14.360> and<00:15:14.480> not<00:15:14.720> just 00:15:15.030 --> 00:15:15.040 align:start position:0% general purpose computation and not just 00:15:15.040 --> 00:15:16.509 align:start position:0% general purpose computation and not just kind<00:15:15.160> of<00:15:15.320> workarounds<00:15:15.839> with<00:15:16.040> Z<00:15:16.279> knowledge 00:15:16.509 --> 00:15:16.519 align:start position:0% kind of workarounds with Z knowledge 00:15:16.519 --> 00:15:19.389 align:start position:0% kind of workarounds with Z knowledge proofs<00:15:17.199> so<00:15:17.519> for<00:15:17.680> me<00:15:17.920> this<00:15:18.040> is<00:15:18.320> like<00:15:18.959> the<00:15:19.160> most 00:15:19.389 --> 00:15:19.399 align:start position:0% proofs so for me this is like the most 00:15:19.399 --> 00:15:21.310 align:start position:0% proofs so for me this is like the most exciting<00:15:19.800> thing<00:15:19.959> that<00:15:20.079> is<00:15:20.279> happening<00:15:20.720> in<00:15:21.160> the 00:15:21.310 --> 00:15:21.320 align:start position:0% exciting thing that is happening in the 00:15:21.320 --> 00:15:22.749 align:start position:0% exciting thing that is happening in the crypto<00:15:21.639> world<00:15:21.839> at<00:15:21.959> the 00:15:22.749 --> 00:15:22.759 align:start position:0% crypto world at the 00:15:22.759 --> 00:15:25.670 align:start position:0% crypto world at the moment<00:15:23.759> so<00:15:24.440> I<00:15:24.519> think<00:15:24.720> with<00:15:24.920> that<00:15:25.399> like<00:15:25.519> the 00:15:25.670 --> 00:15:25.680 align:start position:0% moment so I think with that like the 00:15:25.680 --> 00:15:28.389 align:start position:0% moment so I think with that like the Privacy<00:15:26.199> conversations<00:15:26.920> becoming<00:15:27.639> super 00:15:28.389 --> 00:15:28.399 align:start position:0% Privacy conversations becoming super 00:15:28.399 --> 00:15:32.030 align:start position:0% Privacy conversations becoming super nicely<00:15:29.120> nuanced<00:15:29.759> it's<00:15:30.000> not<00:15:30.279> like<00:15:31.279> full<00:15:31.800> like 00:15:32.030 --> 00:15:32.040 align:start position:0% nicely nuanced it's not like full like 00:15:32.040 --> 00:15:34.550 align:start position:0% nicely nuanced it's not like full like privacy<00:15:32.519> is<00:15:32.680> not<00:15:32.959> secrecy<00:15:33.680> necessarily<00:15:34.360> it's 00:15:34.550 --> 00:15:34.560 align:start position:0% privacy is not secrecy necessarily it's 00:15:34.560 --> 00:15:36.710 align:start position:0% privacy is not secrecy necessarily it's like<00:15:34.800> you're<00:15:35.040> not<00:15:35.360> like<00:15:35.560> completely<00:15:36.399> black 00:15:36.710 --> 00:15:36.720 align:start position:0% like you're not like completely black 00:15:36.720 --> 00:15:38.430 align:start position:0% like you're not like completely black boxed<00:15:37.079> and<00:15:37.240> tied<00:15:37.560> off<00:15:37.720> from<00:15:37.920> everything<00:15:38.240> and 00:15:38.430 --> 00:15:38.440 align:start position:0% boxed and tied off from everything and 00:15:38.440 --> 00:15:40.030 align:start position:0% boxed and tied off from everything and nobody<00:15:38.759> can<00:15:38.880> see<00:15:39.079> my<00:15:39.279> data<00:15:39.519> and<00:15:39.639> no<00:15:39.759> one<00:15:39.920> can 00:15:40.030 --> 00:15:40.040 align:start position:0% nobody can see my data and no one can 00:15:40.040 --> 00:15:41.829 align:start position:0% nobody can see my data and no one can touch<00:15:40.240> it<00:15:40.440> and<00:15:40.600> I<00:15:40.759> can't<00:15:40.959> even<00:15:41.160> use<00:15:41.360> it<00:15:41.560> and 00:15:41.829 --> 00:15:41.839 align:start position:0% touch it and I can't even use it and 00:15:41.839 --> 00:15:44.430 align:start position:0% touch it and I can't even use it and like<00:15:42.480> you<00:15:42.639> shouldn't<00:15:42.920> learn<00:15:43.240> anything<00:15:43.560> about 00:15:44.430 --> 00:15:44.440 align:start position:0% like you shouldn't learn anything about 00:15:44.440 --> 00:15:47.189 align:start position:0% like you shouldn't learn anything about me<00:15:45.440> and<00:15:45.560> it's<00:15:45.720> not<00:15:45.959> like<00:15:46.199> fully<00:15:46.560> open<00:15:46.959> like 00:15:47.189 --> 00:15:47.199 align:start position:0% me and it's not like fully open like 00:15:47.199 --> 00:15:48.710 align:start position:0% me and it's not like fully open like everything<00:15:47.480> on<00:15:47.639> ethereum<00:15:48.120> if<00:15:48.199> I<00:15:48.319> interact 00:15:48.710 --> 00:15:48.720 align:start position:0% everything on ethereum if I interact 00:15:48.720 --> 00:15:50.389 align:start position:0% everything on ethereum if I interact with<00:15:48.839> the<00:15:48.959> chain<00:15:49.279> like<00:15:49.519> everything<00:15:49.839> is<00:15:50.079> public 00:15:50.389 --> 00:15:50.399 align:start position:0% with the chain like everything is public 00:15:50.399 --> 00:15:52.870 align:start position:0% with the chain like everything is public and<00:15:50.560> everything<00:15:50.839> is<00:15:51.040> recorded<00:15:51.680> forever<00:15:52.680> um 00:15:52.870 --> 00:15:52.880 align:start position:0% and everything is recorded forever um 00:15:52.880 --> 00:15:54.949 align:start position:0% and everything is recorded forever um now<00:15:53.160> we're<00:15:53.399> kind<00:15:53.519> of<00:15:53.680> finding<00:15:54.079> this<00:15:54.360> like 00:15:54.949 --> 00:15:54.959 align:start position:0% now we're kind of finding this like 00:15:54.959 --> 00:15:57.110 align:start position:0% now we're kind of finding this like somewhere<00:15:55.360> in<00:15:55.519> between<00:15:56.040> this<00:15:56.240> All<00:15:56.480> or<00:15:56.720> Nothing 00:15:57.110 --> 00:15:57.120 align:start position:0% somewhere in between this All or Nothing 00:15:57.120 --> 00:15:59.030 align:start position:0% somewhere in between this All or Nothing approach<00:15:57.519> and<00:15:57.639> for<00:15:57.759> me<00:15:57.920> this<00:15:58.040> is<00:15:58.199> super<00:15:58.480> nice 00:15:59.030 --> 00:15:59.040 align:start position:0% approach and for me this is super nice 00:15:59.040 --> 00:16:01.430 align:start position:0% approach and for me this is super nice because<00:15:59.800> in<00:16:00.000> my<00:16:00.199> life<00:16:00.480> in<00:16:00.600> my<00:16:00.720> day-to-day<00:16:01.240> life 00:16:01.430 --> 00:16:01.440 align:start position:0% because in my life in my day-to-day life 00:16:01.440 --> 00:16:03.470 align:start position:0% because in my life in my day-to-day life I<00:16:01.560> come<00:16:01.959> here<00:16:02.199> I<00:16:02.319> stand<00:16:02.680> in<00:16:02.800> front<00:16:03.040> of<00:16:03.160> you<00:16:03.399> I 00:16:03.470 --> 00:16:03.480 align:start position:0% I come here I stand in front of you I 00:16:03.480 --> 00:16:06.710 align:start position:0% I come here I stand in front of you I want<00:16:03.680> to<00:16:03.839> be<00:16:04.000> seen<00:16:04.480> at<00:16:04.680> times<00:16:05.639> but<00:16:05.759> I<00:16:05.920> also<00:16:06.600> at 00:16:06.710 --> 00:16:06.720 align:start position:0% want to be seen at times but I also at 00:16:06.720 --> 00:16:08.189 align:start position:0% want to be seen at times but I also at times<00:16:07.120> don't<00:16:07.279> want<00:16:07.440> to<00:16:07.519> be<00:16:07.639> seen<00:16:07.880> and<00:16:08.000> I<00:16:08.079> want 00:16:08.189 --> 00:16:08.199 align:start position:0% times don't want to be seen and I want 00:16:08.199 --> 00:16:09.749 align:start position:0% times don't want to be seen and I want to<00:16:08.360> choose<00:16:08.720> like<00:16:08.880> I<00:16:08.959> want<00:16:09.120> to<00:16:09.240> have<00:16:09.399> the<00:16:09.519> option 00:16:09.749 --> 00:16:09.759 align:start position:0% to choose like I want to have the option 00:16:09.759 --> 00:16:12.590 align:start position:0% to choose like I want to have the option to<00:16:09.959> come<00:16:10.199> and<00:16:10.480> like<00:16:10.839> um<00:16:11.199> see<00:16:11.519> people<00:16:12.399> and<00:16:12.519> I 00:16:12.590 --> 00:16:12.600 align:start position:0% to come and like um see people and I 00:16:12.600 --> 00:16:14.590 align:start position:0% to come and like um see people and I want<00:16:12.720> to<00:16:12.839> share<00:16:13.240> myself<00:16:13.600> and<00:16:13.800> my<00:16:14.040> thoughts 00:16:14.590 --> 00:16:14.600 align:start position:0% want to share myself and my thoughts 00:16:14.600 --> 00:16:16.069 align:start position:0% want to share myself and my thoughts sometimes<00:16:15.040> but<00:16:15.120> I<00:16:15.240> also<00:16:15.399> want<00:16:15.560> the<00:16:15.680> option<00:16:15.880> to 00:16:16.069 --> 00:16:16.079 align:start position:0% sometimes but I also want the option to 00:16:16.079 --> 00:16:19.230 align:start position:0% sometimes but I also want the option to not<00:16:16.440> so<00:16:16.720> having<00:16:17.000> this<00:16:17.199> sort<00:16:17.440> of<00:16:18.319> um<00:16:18.680> and<00:16:18.800> I<00:16:19.000> also 00:16:19.230 --> 00:16:19.240 align:start position:0% not so having this sort of um and I also 00:16:19.240 --> 00:16:21.430 align:start position:0% not so having this sort of um and I also want<00:16:19.399> to<00:16:19.759> sometimes<00:16:20.040> avoid<00:16:20.440> some<00:16:20.880> people<00:16:21.279> and 00:16:21.430 --> 00:16:21.440 align:start position:0% want to sometimes avoid some people and 00:16:21.440 --> 00:16:23.030 align:start position:0% want to sometimes avoid some people and talk<00:16:21.639> to<00:16:21.800> some<00:16:22.000> other<00:16:22.240> people<00:16:22.480> and<00:16:22.639> whatever 00:16:23.030 --> 00:16:23.040 align:start position:0% talk to some other people and whatever 00:16:23.040 --> 00:16:25.350 align:start position:0% talk to some other people and whatever like<00:16:23.199> so<00:16:23.399> having<00:16:23.720> this<00:16:24.360> um<00:16:24.519> nuanced<00:16:25.000> view<00:16:25.240> is 00:16:25.350 --> 00:16:25.360 align:start position:0% like so having this um nuanced view is 00:16:25.360 --> 00:16:29.829 align:start position:0% like so having this um nuanced view is super<00:16:25.680> nice<00:16:26.680> and<00:16:26.800> so<00:16:27.480> if<00:16:27.800> you<00:16:28.000> are<00:16:28.399> sort<00:16:28.680> of<00:16:29.160> MPC 00:16:29.829 --> 00:16:29.839 align:start position:0% super nice and so if you are sort of MPC 00:16:29.839 --> 00:16:31.910 align:start position:0% super nice and so if you are sort of MPC inclined<00:16:30.639> but<00:16:30.839> not<00:16:31.279> necessarily<00:16:31.759> A 00:16:31.910 --> 00:16:31.920 align:start position:0% inclined but not necessarily A 00:16:31.920 --> 00:16:33.629 align:start position:0% inclined but not necessarily A cryptographer<00:16:32.560> how<00:16:32.720> can<00:16:32.880> you<00:16:33.000> start<00:16:33.319> thinking 00:16:33.629 --> 00:16:33.639 align:start position:0% cryptographer how can you start thinking 00:16:33.639 --> 00:16:35.870 align:start position:0% cryptographer how can you start thinking about<00:16:33.959> these<00:16:34.720> and<00:16:34.839> I<00:16:34.959> think<00:16:35.480> one<00:16:35.639> of<00:16:35.759> the 00:16:35.870 --> 00:16:35.880 align:start position:0% about these and I think one of the 00:16:35.880 --> 00:16:37.629 align:start position:0% about these and I think one of the things<00:16:36.079> that<00:16:36.199> we're<00:16:36.319> seeing<00:16:36.639> is<00:16:36.759> like<00:16:37.199> okay 00:16:37.629 --> 00:16:37.639 align:start position:0% things that we're seeing is like okay 00:16:37.639 --> 00:16:39.470 align:start position:0% things that we're seeing is like okay you<00:16:37.759> know<00:16:38.040> I<00:16:38.199> get<00:16:38.440> excited<00:16:38.800> and<00:16:38.920> I'm<00:16:39.040> like<00:16:39.240> oh 00:16:39.470 --> 00:16:39.480 align:start position:0% you know I get excited and I'm like oh 00:16:39.480 --> 00:16:41.030 align:start position:0% you know I get excited and I'm like oh look<00:16:39.680> it's<00:16:39.880> like<00:16:40.120> it's<00:16:40.319> live<00:16:40.680> you<00:16:40.800> can 00:16:41.030 --> 00:16:41.040 align:start position:0% look it's like it's live you can 00:16:41.040 --> 00:16:43.509 align:start position:0% look it's like it's live you can actually<00:16:41.319> use<00:16:41.560> it<00:16:41.759> now<00:16:41.959> it's<00:16:42.240> great<00:16:43.240> um 00:16:43.509 --> 00:16:43.519 align:start position:0% actually use it now it's great um 00:16:43.519 --> 00:16:45.470 align:start position:0% actually use it now it's great um everybody<00:16:43.959> should<00:16:44.279> do<00:16:44.560> this<00:16:44.920> like<00:16:45.120> and<00:16:45.279> some 00:16:45.470 --> 00:16:45.480 align:start position:0% everybody should do this like and some 00:16:45.480 --> 00:16:47.389 align:start position:0% everybody should do this like and some people<00:16:45.680> are<00:16:45.800> like<00:16:46.040> wait<00:16:46.279> no<00:16:46.759> though<00:16:47.120> like 00:16:47.389 --> 00:16:47.399 align:start position:0% people are like wait no though like 00:16:47.399 --> 00:16:49.350 align:start position:0% people are like wait no though like because<00:16:48.120> I<00:16:48.199> mean<00:16:48.319> like<00:16:48.560> Amir<00:16:49.040> like<00:16:49.160> he's 00:16:49.350 --> 00:16:49.360 align:start position:0% because I mean like Amir like he's 00:16:49.360 --> 00:16:51.350 align:start position:0% because I mean like Amir like he's talking<00:16:49.639> about<00:16:50.000> super<00:16:50.399> serious<00:16:50.839> things<00:16:51.120> where 00:16:51.350 --> 00:16:51.360 align:start position:0% talking about super serious things where 00:16:51.360 --> 00:16:53.389 align:start position:0% talking about super serious things where people<00:16:51.560> are<00:16:51.800> like<00:16:52.040> dying<00:16:52.600> and<00:16:52.880> whatever<00:16:53.240> and 00:16:53.389 --> 00:16:53.399 align:start position:0% people are like dying and whatever and 00:16:53.399 --> 00:16:54.150 align:start position:0% people are like dying and whatever and it's 00:16:54.150 --> 00:16:54.160 align:start position:0% it's 00:16:54.160 --> 00:16:57.470 align:start position:0% it's like<00:16:55.160> okay<00:16:55.360> yeah<00:16:55.560> maybe<00:16:56.160> like<00:16:56.639> my<00:16:56.800> little<00:16:57.040> MPC 00:16:57.470 --> 00:16:57.480 align:start position:0% like okay yeah maybe like my little MPC 00:16:57.480 --> 00:16:59.430 align:start position:0% like okay yeah maybe like my little MPC Protocols<00:16:57.920> are<00:16:58.079> not<00:16:58.279> for<00:16:58.480> that<00:16:58.639> case<00:16:59.120> and<00:16:59.279> like 00:16:59.430 --> 00:16:59.440 align:start position:0% Protocols are not for that case and like 00:16:59.440 --> 00:17:00.910 align:start position:0% Protocols are not for that case and like the<00:16:59.600> question<00:16:59.920> then<00:17:00.079> is<00:17:00.240> like<00:17:00.480> okay<00:17:00.639> who<00:17:00.759> are 00:17:00.910 --> 00:17:00.920 align:start position:0% the question then is like okay who are 00:17:00.920 --> 00:17:02.710 align:start position:0% the question then is like okay who are your<00:17:01.120> adversaries<00:17:01.720> and<00:17:01.880> how<00:17:02.040> much<00:17:02.279> power<00:17:02.560> do 00:17:02.710 --> 00:17:02.720 align:start position:0% your adversaries and how much power do 00:17:02.720 --> 00:17:04.870 align:start position:0% your adversaries and how much power do they<00:17:02.920> have<00:17:03.759> and<00:17:03.880> so<00:17:04.120> like<00:17:04.280> I<00:17:04.400> said<00:17:04.559> to<00:17:04.679> you 00:17:04.870 --> 00:17:04.880 align:start position:0% they have and so like I said to you 00:17:04.880 --> 00:17:06.470 align:start position:0% they have and so like I said to you before<00:17:05.120> that<00:17:05.240> we<00:17:05.319> are<00:17:05.480> running<00:17:05.760> these<00:17:05.919> coars 00:17:06.470 --> 00:17:06.480 align:start position:0% before that we are running these coars 00:17:06.480 --> 00:17:08.270 align:start position:0% before that we are running these coars on<00:17:06.600> the<00:17:06.720> network<00:17:07.400> which<00:17:07.520> is<00:17:07.720> established 00:17:08.270 --> 00:17:08.280 align:start position:0% on the network which is established 00:17:08.280 --> 00:17:13.590 align:start position:0% on the network which is established between<00:17:09.520> oo<00:17:10.520> um<00:17:11.079> PSD<00:17:11.720> and<00:17:11.880> T<00:17:12.360> and<00:17:12.679> uh<00:17:12.839> cursive 00:17:13.590 --> 00:17:13.600 align:start position:0% between oo um PSD and T and uh cursive 00:17:13.600 --> 00:17:15.549 align:start position:0% between oo um PSD and T and uh cursive so<00:17:13.799> in<00:17:13.919> a<00:17:14.079> sense<00:17:14.439> you're<00:17:14.640> Outsourcing<00:17:15.360> your 00:17:15.549 --> 00:17:15.559 align:start position:0% so in a sense you're Outsourcing your 00:17:15.559 --> 00:17:17.270 align:start position:0% so in a sense you're Outsourcing your work<00:17:15.839> to<00:17:16.039> us<00:17:16.240> and<00:17:16.319> you're<00:17:16.439> Outsourcing<00:17:17.079> your 00:17:17.270 --> 00:17:17.280 align:start position:0% work to us and you're Outsourcing your 00:17:17.280 --> 00:17:19.630 align:start position:0% work to us and you're Outsourcing your data<00:17:17.600> to<00:17:17.799> us<00:17:18.240> so<00:17:18.400> in<00:17:18.480> a<00:17:18.640> sense<00:17:18.799> you<00:17:18.959> trust<00:17:19.319> us 00:17:19.630 --> 00:17:19.640 align:start position:0% data to us so in a sense you trust us 00:17:19.640 --> 00:17:21.470 align:start position:0% data to us so in a sense you trust us you<00:17:19.760> trust<00:17:20.079> us<00:17:20.280> not<00:17:20.439> to<00:17:20.640> collude<00:17:21.120> because<00:17:21.319> if 00:17:21.470 --> 00:17:21.480 align:start position:0% you trust us not to collude because if 00:17:21.480 --> 00:17:23.829 align:start position:0% you trust us not to collude because if we<00:17:21.640> all<00:17:21.880> come<00:17:22.240> together<00:17:22.880> we<00:17:23.039> can<00:17:23.280> reconstruct 00:17:23.829 --> 00:17:23.839 align:start position:0% we all come together we can reconstruct 00:17:23.839 --> 00:17:26.710 align:start position:0% we all come together we can reconstruct your<00:17:24.000> secrets<00:17:24.959> and<00:17:25.079> so<00:17:26.039> one<00:17:26.280> question<00:17:26.600> that 00:17:26.710 --> 00:17:26.720 align:start position:0% your secrets and so one question that 00:17:26.720 --> 00:17:28.029 align:start position:0% your secrets and so one question that you<00:17:26.880> might<00:17:27.120> ask<00:17:27.360> if<00:17:27.439> you're<00:17:27.600> starting<00:17:27.880> to 00:17:28.029 --> 00:17:28.039 align:start position:0% you might ask if you're starting to 00:17:28.039 --> 00:17:29.510 align:start position:0% you might ask if you're starting to think<00:17:28.240> about<00:17:28.439> these<00:17:28.600> things<00:17:28.960> is<00:17:29.120> like<00:17:29.320> how 00:17:29.510 --> 00:17:29.520 align:start position:0% think about these things is like how 00:17:29.520 --> 00:17:31.350 align:start position:0% think about these things is like how many<00:17:29.880> people<00:17:30.160> need<00:17:30.360> to<00:17:30.600> actually<00:17:30.880> collude<00:17:31.280> is 00:17:31.350 --> 00:17:31.360 align:start position:0% many people need to actually collude is 00:17:31.360 --> 00:17:33.230 align:start position:0% many people need to actually collude is it<00:17:31.520> like<00:17:31.720> all<00:17:31.880> of<00:17:32.080> them<00:17:32.400> is<00:17:32.520> it<00:17:32.679> just<00:17:32.919> one<00:17:33.080> of 00:17:33.230 --> 00:17:33.240 align:start position:0% it like all of them is it just one of 00:17:33.240 --> 00:17:35.150 align:start position:0% it like all of them is it just one of them<00:17:33.799> as<00:17:33.919> long<00:17:34.080> as<00:17:34.200> one<00:17:34.320> of<00:17:34.440> them<00:17:34.600> is<00:17:34.720> honest<00:17:35.080> is 00:17:35.150 --> 00:17:35.160 align:start position:0% them as long as one of them is honest is 00:17:35.160 --> 00:17:36.909 align:start position:0% them as long as one of them is honest is it<00:17:35.440> okay<00:17:36.039> and<00:17:36.160> so<00:17:36.280> there<00:17:36.400> are<00:17:36.559> different 00:17:36.909 --> 00:17:36.919 align:start position:0% it okay and so there are different 00:17:36.919 --> 00:17:38.669 align:start position:0% it okay and so there are different models<00:17:37.320> and<00:17:37.520> different<00:17:37.840> tradeoffs<00:17:38.400> that<00:17:38.559> you 00:17:38.669 --> 00:17:38.679 align:start position:0% models and different tradeoffs that you 00:17:38.679 --> 00:17:40.029 align:start position:0% models and different tradeoffs that you can<00:17:38.840> make<00:17:39.080> and<00:17:39.240> different<00:17:39.520> levels<00:17:39.799> of 00:17:40.029 --> 00:17:40.039 align:start position:0% can make and different levels of 00:17:40.039 --> 00:17:42.909 align:start position:0% can make and different levels of efficiency<00:17:40.840> and<00:17:41.120> things<00:17:41.320> like<00:17:41.559> that<00:17:42.400> so 00:17:42.909 --> 00:17:42.919 align:start position:0% efficiency and things like that so 00:17:42.919 --> 00:17:44.549 align:start position:0% efficiency and things like that so another<00:17:43.280> one<00:17:43.440> is<00:17:43.640> then<00:17:43.880> yeah<00:17:44.080> like<00:17:44.280> different 00:17:44.549 --> 00:17:44.559 align:start position:0% another one is then yeah like different 00:17:44.559 --> 00:17:47.470 align:start position:0% another one is then yeah like different Notions<00:17:45.000> of<00:17:45.520> security<00:17:45.919> so<00:17:46.160> like<00:17:46.440> okay<00:17:46.760> if<00:17:47.320> if 00:17:47.470 --> 00:17:47.480 align:start position:0% Notions of security so like okay if if 00:17:47.480 --> 00:17:49.549 align:start position:0% Notions of security so like okay if if somebody<00:17:47.880> can<00:17:48.080> tamper<00:17:48.520> with<00:17:48.679> your<00:17:48.880> system<00:17:49.360> how 00:17:49.549 --> 00:17:49.559 align:start position:0% somebody can tamper with your system how 00:17:49.559 --> 00:17:52.150 align:start position:0% somebody can tamper with your system how much<00:17:49.840> can<00:17:50.039> they<00:17:50.200> do<00:17:51.000> and<00:17:51.120> so<00:17:51.480> I<00:17:51.559> think<00:17:51.720> the<00:17:51.880> most 00:17:52.150 --> 00:17:52.160 align:start position:0% much can they do and so I think the most 00:17:52.160 --> 00:17:53.789 align:start position:0% much can they do and so I think the most common<00:17:52.480> model<00:17:52.880> of<00:17:53.000> things<00:17:53.200> that<00:17:53.320> are<00:17:53.440> running 00:17:53.789 --> 00:17:53.799 align:start position:0% common model of things that are running 00:17:53.799 --> 00:17:57.190 align:start position:0% common model of things that are running now<00:17:54.080> is<00:17:54.320> this<00:17:54.520> semi<00:17:54.840> honest<00:17:55.200> security<00:17:55.679> so<00:17:56.200> like 00:17:57.190 --> 00:17:57.200 align:start position:0% now is this semi honest security so like 00:17:57.200 --> 00:17:59.350 align:start position:0% now is this semi honest security so like parties<00:17:57.720> can<00:17:58.000> become<00:17:58.360> corrupt 00:17:59.350 --> 00:17:59.360 align:start position:0% parties can become corrupt 00:17:59.360 --> 00:18:00.830 align:start position:0% parties can become corrupt but<00:17:59.520> they<00:17:59.640> will<00:17:59.799> follow<00:18:00.120> the<00:18:00.280> protocol<00:18:00.679> as 00:18:00.830 --> 00:18:00.840 align:start position:0% but they will follow the protocol as 00:18:00.840 --> 00:18:02.549 align:start position:0% but they will follow the protocol as normal<00:18:01.240> so<00:18:01.400> maybe<00:18:01.640> there's<00:18:01.840> some<00:18:02.039> information 00:18:02.549 --> 00:18:02.559 align:start position:0% normal so maybe there's some information 00:18:02.559 --> 00:18:05.029 align:start position:0% normal so maybe there's some information leakage<00:18:03.039> maybe<00:18:03.280> you<00:18:03.559> like<00:18:04.080> learn<00:18:04.440> some<00:18:04.679> stuff 00:18:05.029 --> 00:18:05.039 align:start position:0% leakage maybe you like learn some stuff 00:18:05.039 --> 00:18:08.310 align:start position:0% leakage maybe you like learn some stuff by<00:18:05.600> uh<00:18:05.799> observing<00:18:06.240> the<00:18:06.360> network<00:18:07.320> but<00:18:08.159> they 00:18:08.310 --> 00:18:08.320 align:start position:0% by uh observing the network but they 00:18:08.320 --> 00:18:10.510 align:start position:0% by uh observing the network but they still<00:18:08.559> follow<00:18:08.880> the<00:18:09.280> protocol<00:18:10.280> and<00:18:10.360> then 00:18:10.510 --> 00:18:10.520 align:start position:0% still follow the protocol and then 00:18:10.520 --> 00:18:12.350 align:start position:0% still follow the protocol and then there's<00:18:10.760> kind<00:18:10.880> of<00:18:11.120> the<00:18:11.240> worst<00:18:11.600> case<00:18:11.799> situation 00:18:12.350 --> 00:18:12.360 align:start position:0% there's kind of the worst case situation 00:18:12.360 --> 00:18:14.950 align:start position:0% there's kind of the worst case situation where<00:18:12.559> you<00:18:12.799> kind<00:18:12.960> of<00:18:13.919> try<00:18:14.159> to<00:18:14.320> protect<00:18:14.679> against 00:18:14.950 --> 00:18:14.960 align:start position:0% where you kind of try to protect against 00:18:14.960 --> 00:18:16.870 align:start position:0% where you kind of try to protect against militia<00:18:15.440> security<00:18:15.880> and<00:18:16.120> protecting<00:18:16.559> against 00:18:16.870 --> 00:18:16.880 align:start position:0% militia security and protecting against 00:18:16.880 --> 00:18:19.029 align:start position:0% militia security and protecting against this<00:18:17.080> means<00:18:17.440> that<00:18:17.760> or<00:18:18.000> like<00:18:18.240> adversaries<00:18:18.880> that 00:18:19.029 --> 00:18:19.039 align:start position:0% this means that or like adversaries that 00:18:19.039 --> 00:18:21.310 align:start position:0% this means that or like adversaries that can<00:18:19.200> break<00:18:19.720> Security<00:18:20.200> in<00:18:20.360> this<00:18:20.640> sense<00:18:20.960> means 00:18:21.310 --> 00:18:21.320 align:start position:0% can break Security in this sense means 00:18:21.320 --> 00:18:23.270 align:start position:0% can break Security in this sense means that<00:18:21.480> they<00:18:21.600> can<00:18:21.840> control<00:18:22.280> and<00:18:22.440> manipulate<00:18:23.039> and 00:18:23.270 --> 00:18:23.280 align:start position:0% that they can control and manipulate and 00:18:23.280 --> 00:18:25.430 align:start position:0% that they can control and manipulate and arbitrarily<00:18:24.240> inject<00:18:24.679> messages<00:18:25.159> like<00:18:25.320> they 00:18:25.430 --> 00:18:25.440 align:start position:0% arbitrarily inject messages like they 00:18:25.440 --> 00:18:27.510 align:start position:0% arbitrarily inject messages like they can<00:18:25.640> just<00:18:25.799> completely<00:18:26.240> destroy<00:18:26.600> your<00:18:26.799> system 00:18:27.510 --> 00:18:27.520 align:start position:0% can just completely destroy your system 00:18:27.520 --> 00:18:29.750 align:start position:0% can just completely destroy your system so<00:18:27.760> like<00:18:27.960> if<00:18:28.080> you<00:18:28.760> are<00:18:28.880> running<00:18:29.120> an<00:18:29.280> election 00:18:29.750 --> 00:18:29.760 align:start position:0% so like if you are running an election 00:18:29.760 --> 00:18:31.390 align:start position:0% so like if you are running an election let's<00:18:29.919> say<00:18:30.080> in<00:18:30.159> an<00:18:30.320> NPC<00:18:30.840> and<00:18:30.960> you<00:18:31.080> have<00:18:31.200> a 00:18:31.390 --> 00:18:31.400 align:start position:0% let's say in an NPC and you have a 00:18:31.400 --> 00:18:34.990 align:start position:0% let's say in an NPC and you have a malicious<00:18:32.400> uh<00:18:33.039> like<00:18:33.240> if<00:18:33.600> you<00:18:34.600> um<00:18:34.799> have<00:18:34.919> a 00:18:34.990 --> 00:18:35.000 align:start position:0% malicious uh like if you um have a 00:18:35.000 --> 00:18:36.870 align:start position:0% malicious uh like if you um have a malicious<00:18:35.440> adversary<00:18:35.960> they<00:18:36.120> could<00:18:36.360> you<00:18:36.480> know 00:18:36.870 --> 00:18:36.880 align:start position:0% malicious adversary they could you know 00:18:36.880 --> 00:18:38.870 align:start position:0% malicious adversary they could you know just<00:18:37.039> change<00:18:37.360> the<00:18:37.520> results<00:18:37.840> of<00:18:37.960> your<00:18:38.159> election 00:18:38.870 --> 00:18:38.880 align:start position:0% just change the results of your election 00:18:38.880 --> 00:18:41.390 align:start position:0% just change the results of your election like<00:18:39.200> you<00:18:39.280> know<00:18:39.559> you<00:18:39.760> have<00:18:39.960> nothing<00:18:40.799> so<00:18:41.080> if<00:18:41.200> you 00:18:41.390 --> 00:18:41.400 align:start position:0% like you know you have nothing so if you 00:18:41.400 --> 00:18:42.710 align:start position:0% like you know you have nothing so if you want<00:18:41.600> to<00:18:41.799> protect<00:18:42.120> in<00:18:42.280> this<00:18:42.440> kind<00:18:42.559> of 00:18:42.710 --> 00:18:42.720 align:start position:0% want to protect in this kind of 00:18:42.720 --> 00:18:44.950 align:start position:0% want to protect in this kind of situation<00:18:43.600> it's<00:18:43.760> super<00:18:44.080> hard<00:18:44.440> and<00:18:44.559> you're<00:18:44.760> not 00:18:44.950 --> 00:18:44.960 align:start position:0% situation it's super hard and you're not 00:18:44.960 --> 00:18:47.710 align:start position:0% situation it's super hard and you're not going<00:18:45.159> to<00:18:45.360> have<00:18:45.679> much<00:18:46.000> efficiency<00:18:46.880> that's<00:18:47.080> for 00:18:47.710 --> 00:18:47.720 align:start position:0% going to have much efficiency that's for 00:18:47.720 --> 00:18:50.710 align:start position:0% going to have much efficiency that's for sure<00:18:48.720> um<00:18:49.000> so<00:18:49.240> yeah<00:18:49.440> what<00:18:49.559> about<00:18:49.880> efficiency<00:18:50.600> I 00:18:50.710 --> 00:18:50.720 align:start position:0% sure um so yeah what about efficiency I 00:18:50.720 --> 00:18:52.549 align:start position:0% sure um so yeah what about efficiency I think<00:18:51.360> um<00:18:51.600> I<00:18:51.720> mentioned<00:18:52.000> a<00:18:52.120> few<00:18:52.280> things<00:18:52.440> the 00:18:52.549 --> 00:18:52.559 align:start position:0% think um I mentioned a few things the 00:18:52.559 --> 00:18:54.669 align:start position:0% think um I mentioned a few things the worldcoin<00:18:53.159> example<00:18:53.600> the<00:18:53.720> cursive<00:18:54.200> example<00:18:54.600> I 00:18:54.669 --> 00:18:54.679 align:start position:0% worldcoin example the cursive example I 00:18:54.679 --> 00:18:56.070 align:start position:0% worldcoin example the cursive example I think<00:18:54.840> these<00:18:54.960> are<00:18:55.120> two<00:18:55.320> nice<00:18:55.600> examples<00:18:55.960> of 00:18:56.070 --> 00:18:56.080 align:start position:0% think these are two nice examples of 00:18:56.080 --> 00:18:57.669 align:start position:0% think these are two nice examples of things<00:18:56.240> that<00:18:56.360> are<00:18:56.480> running<00:18:56.880> in<00:18:57.120> production 00:18:57.669 --> 00:18:57.679 align:start position:0% things that are running in production 00:18:57.679 --> 00:18:59.830 align:start position:0% things that are running in production which<00:18:57.840> I<00:18:57.919> think<00:18:58.159> are<00:18:58.360> the<00:18:58.480> kind<00:18:58.880> of<00:18:59.080> things<00:18:59.520> I 00:18:59.830 --> 00:18:59.840 align:start position:0% which I think are the kind of things I 00:18:59.840 --> 00:19:01.710 align:start position:0% which I think are the kind of things I would<00:19:00.080> hope<00:19:00.720> the<00:19:00.880> sort<00:19:01.039> of<00:19:01.120> Cipher<00:19:01.480> punk 00:19:01.710 --> 00:19:01.720 align:start position:0% would hope the sort of Cipher punk 00:19:01.720 --> 00:19:03.149 align:start position:0% would hope the sort of Cipher punk people<00:19:01.960> would<00:19:02.159> care<00:19:02.400> about<00:19:02.640> more<00:19:02.840> than<00:19:03.000> the 00:19:03.149 --> 00:19:03.159 align:start position:0% people would care about more than the 00:19:03.159 --> 00:19:04.789 align:start position:0% people would care about more than the theoretical<00:19:03.720> people<00:19:03.919> who<00:19:04.080> care<00:19:04.280> about<00:19:04.480> the 00:19:04.789 --> 00:19:04.799 align:start position:0% theoretical people who care about the 00:19:04.799 --> 00:19:07.830 align:start position:0% theoretical people who care about the math<00:19:05.799> um<00:19:06.760> and<00:19:06.880> so<00:19:07.159> in<00:19:07.280> saying<00:19:07.520> that<00:19:07.720> the 00:19:07.830 --> 00:19:07.840 align:start position:0% math um and so in saying that the 00:19:07.840 --> 00:19:09.870 align:start position:0% math um and so in saying that the difference<00:19:08.200> between<00:19:08.679> specialized<00:19:09.280> protocols 00:19:09.870 --> 00:19:09.880 align:start position:0% difference between specialized protocols 00:19:09.880 --> 00:19:11.909 align:start position:0% difference between specialized protocols and<00:19:10.280> like<00:19:10.480> general<00:19:10.960> purpose 00:19:11.909 --> 00:19:11.919 align:start position:0% and like general purpose 00:19:11.919 --> 00:19:14.350 align:start position:0% and like general purpose computation<00:19:12.919> um<00:19:13.320> is<00:19:13.559> quite<00:19:13.760> different<00:19:14.120> so 00:19:14.350 --> 00:19:14.360 align:start position:0% computation um is quite different so 00:19:14.360 --> 00:19:15.830 align:start position:0% computation um is quite different so like<00:19:14.480> you<00:19:14.600> can<00:19:14.799> do<00:19:15.000> like<00:19:15.200> highly<00:19:15.520> highly 00:19:15.830 --> 00:19:15.840 align:start position:0% like you can do like highly highly 00:19:15.840 --> 00:19:18.870 align:start position:0% like you can do like highly highly optimized<00:19:16.559> stuff<00:19:17.559> um<00:19:17.919> as<00:19:18.240> in<00:19:18.360> the<00:19:18.520> case<00:19:18.720> of 00:19:18.870 --> 00:19:18.880 align:start position:0% optimized stuff um as in the case of 00:19:18.880 --> 00:19:20.669 align:start position:0% optimized stuff um as in the case of worldcoin<00:19:19.520> and<00:19:19.679> they<00:19:19.760> are<00:19:19.919> doing<00:19:20.320> un 00:19:20.669 --> 00:19:20.679 align:start position:0% worldcoin and they are doing un 00:19:20.679 --> 00:19:22.750 align:start position:0% worldcoin and they are doing un uniqueness<00:19:21.120> checks<00:19:21.400> you<00:19:21.520> do<00:19:21.760> about<00:19:22.120> 40 00:19:22.750 --> 00:19:22.760 align:start position:0% uniqueness checks you do about 40 00:19:22.760 --> 00:19:25.830 align:start position:0% uniqueness checks you do about 40 billion<00:19:23.159> checks<00:19:23.720> per<00:19:24.320> second<00:19:25.240> and<00:19:25.440> okay<00:19:25.679> that 00:19:25.830 --> 00:19:25.840 align:start position:0% billion checks per second and okay that 00:19:25.840 --> 00:19:28.310 align:start position:0% billion checks per second and okay that translates<00:19:26.400> to<00:19:26.679> okay<00:19:26.840> you<00:19:27.000> have<00:19:27.280> two<00:19:27.640> eyes<00:19:28.120> and 00:19:28.310 --> 00:19:28.320 align:start position:0% translates to okay you have two eyes and 00:19:28.320 --> 00:19:29.870 align:start position:0% translates to okay you have two eyes and you<00:19:28.400> know<00:19:28.720> you<00:19:28.840> have<00:19:28.960> many<00:19:29.159> readings<00:19:29.559> and<00:19:29.720> your 00:19:29.870 --> 00:19:29.880 align:start position:0% you know you have many readings and your 00:19:29.880 --> 00:19:34.430 align:start position:0% you know you have many readings and your iris<00:19:30.240> is<00:19:30.440> pretty<00:19:30.799> like<00:19:31.240> uh<00:19:31.480> data<00:19:32.039> Rich<00:19:33.280> um<00:19:34.280> yeah 00:19:34.430 --> 00:19:34.440 align:start position:0% iris is pretty like uh data Rich um yeah 00:19:34.440 --> 00:19:36.669 align:start position:0% iris is pretty like uh data Rich um yeah it's<00:19:34.640> data<00:19:34.919> Rich<00:19:35.080> so<00:19:35.240> it's<00:19:35.360> a<00:19:35.440> lot<00:19:36.240> um<00:19:36.360> and<00:19:36.480> this 00:19:36.669 --> 00:19:36.679 align:start position:0% it's data Rich so it's a lot um and this 00:19:36.679 --> 00:19:39.310 align:start position:0% it's data Rich so it's a lot um and this translates<00:19:37.080> to<00:19:37.240> I<00:19:37.320> think<00:19:37.520> about 00:19:39.310 --> 00:19:39.320 align:start position:0% translates to I think about 00:19:39.320 --> 00:19:43.549 align:start position:0% translates to I think about 15<00:19:40.320> people<00:19:41.120> uniqueness<00:19:41.679> checks<00:19:42.159> per<00:19:42.559> second 00:19:43.549 --> 00:19:43.559 align:start position:0% 15 people uniqueness checks per second 00:19:43.559 --> 00:19:45.430 align:start position:0% 15 people uniqueness checks per second and<00:19:43.679> so<00:19:43.840> these<00:19:44.200> curse<00:19:44.480> of<00:19:44.679> coars<00:19:45.200> that<00:19:45.320> we're 00:19:45.430 --> 00:19:45.440 align:start position:0% and so these curse of coars that we're 00:19:45.440 --> 00:19:47.750 align:start position:0% and so these curse of coars that we're generating<00:19:46.000> downstairs<00:19:47.000> not<00:19:47.200> downstairs<00:19:47.640> but 00:19:47.750 --> 00:19:47.760 align:start position:0% generating downstairs not downstairs but 00:19:47.760 --> 00:19:50.310 align:start position:0% generating downstairs not downstairs but in<00:19:47.880> the<00:19:47.960> network<00:19:48.840> um<00:19:49.120> are<00:19:49.320> about<00:19:49.520> 12<00:19:49.919> seconds 00:19:50.310 --> 00:19:50.320 align:start position:0% in the network um are about 12 seconds 00:19:50.320 --> 00:19:53.230 align:start position:0% in the network um are about 12 seconds each<00:19:50.679> but<00:19:50.919> 11.9<00:19:51.919> like<00:19:52.240> like<00:19:52.600> the<00:19:52.919> vast 00:19:53.230 --> 00:19:53.240 align:start position:0% each but 11.9 like like the vast 00:19:53.240 --> 00:19:54.669 align:start position:0% each but 11.9 like like the vast majority<00:19:53.679> of<00:19:53.840> that<00:19:54.080> is<00:19:54.200> the<00:19:54.320> witness 00:19:54.669 --> 00:19:54.679 align:start position:0% majority of that is the witness 00:19:54.679 --> 00:19:57.149 align:start position:0% majority of that is the witness extension<00:19:55.080> so<00:19:55.240> this<00:19:55.360> is<00:19:55.520> like<00:19:55.679> the<00:19:55.840> actual<00:19:56.559> NPC 00:19:57.149 --> 00:19:57.159 align:start position:0% extension so this is like the actual NPC 00:19:57.159 --> 00:19:58.669 align:start position:0% extension so this is like the actual NPC part<00:19:57.480> rather<00:19:57.720> than<00:19:57.880> just<00:19:58.000> the<00:19:58.159> proof 00:19:58.669 --> 00:19:58.679 align:start position:0% part rather than just the proof 00:19:58.679 --> 00:20:00.430 align:start position:0% part rather than just the proof generation<00:19:59.080> part<00:19:59.280> so<00:19:59.440> proof<00:19:59.720> generation<00:20:00.240> is 00:20:00.430 --> 00:20:00.440 align:start position:0% generation part so proof generation is 00:20:00.440 --> 00:20:04.029 align:start position:0% generation part so proof generation is very<00:20:00.679> fast<00:20:01.400> but<00:20:01.559> witness<00:20:01.960> extension<00:20:02.840> is<00:20:03.840> not 00:20:04.029 --> 00:20:04.039 align:start position:0% very fast but witness extension is not 00:20:04.039 --> 00:20:07.029 align:start position:0% very fast but witness extension is not too<00:20:04.280> bad<00:20:04.960> so<00:20:05.159> this<00:20:05.240> is<00:20:05.400> where<00:20:05.520> it's<00:20:05.720> at<00:20:05.960> now<00:20:06.880> and 00:20:07.029 --> 00:20:07.039 align:start position:0% too bad so this is where it's at now and 00:20:07.039 --> 00:20:09.390 align:start position:0% too bad so this is where it's at now and so<00:20:07.679> uh<00:20:07.799> that's<00:20:07.960> it<00:20:08.080> for<00:20:08.280> me<00:20:08.640> if<00:20:08.720> you<00:20:08.919> have<00:20:09.120> any 00:20:09.390 --> 00:20:09.400 align:start position:0% so uh that's it for me if you have any 00:20:09.400 --> 00:20:11.470 align:start position:0% so uh that's it for me if you have any questions<00:20:09.799> I<00:20:09.880> will<00:20:10.039> be<00:20:10.159> glad<00:20:10.400> to<00:20:10.640> take<00:20:10.960> them 00:20:11.470 --> 00:20:11.480 align:start position:0% questions I will be glad to take them 00:20:11.480 --> 00:20:15.430 align:start position:0% questions I will be glad to take them thanks<00:20:11.760> very 00:20:15.430 --> 00:20:15.440 align:start position:0% 00:20:15.440 --> 00:20:17.230 align:start position:0% much<00:20:16.440> thanks<00:20:16.640> so<00:20:16.799> much<00:20:16.919> for<00:20:17.039> your 00:20:17.230 --> 00:20:17.240 align:start position:0% much thanks so much for your 00:20:17.240 --> 00:20:19.430 align:start position:0% much thanks so much for your presentation<00:20:17.760> Ash<00:20:18.400> um<00:20:18.799> we've<00:20:18.960> got<00:20:19.120> a<00:20:19.240> couple 00:20:19.430 --> 00:20:19.440 align:start position:0% presentation Ash um we've got a couple 00:20:19.440 --> 00:20:22.710 align:start position:0% presentation Ash um we've got a couple of<00:20:19.640> questions<00:20:20.520> uh<00:20:20.760> here<00:20:20.880> on<00:20:21.039> the<00:20:21.400> docket<00:20:22.400> um 00:20:22.710 --> 00:20:22.720 align:start position:0% of questions uh here on the docket um 00:20:22.720 --> 00:20:24.470 align:start position:0% of questions uh here on the docket um but<00:20:22.919> before<00:20:23.120> we<00:20:23.360> ask<00:20:23.679> those<00:20:23.919> questions<00:20:24.400> I 00:20:24.470 --> 00:20:24.480 align:start position:0% but before we ask those questions I 00:20:24.480 --> 00:20:26.510 align:start position:0% but before we ask those questions I meant<00:20:24.679> to<00:20:24.919> actually<00:20:25.360> mention<00:20:25.720> one<00:20:25.919> fun<00:20:26.240> fact 00:20:26.510 --> 00:20:26.520 align:start position:0% meant to actually mention one fun fact 00:20:26.520 --> 00:20:29.070 align:start position:0% meant to actually mention one fun fact about<00:20:26.840> Ash<00:20:27.120> here<00:20:27.520> is<00:20:27.840> that<00:20:28.200> uh<00:20:28.679> she<00:20:28.880> actually 00:20:29.070 --> 00:20:29.080 align:start position:0% about Ash here is that uh she actually 00:20:29.080 --> 00:20:30.990 align:start position:0% about Ash here is that uh she actually was<00:20:29.240> an<00:20:29.400> MC<00:20:29.760> just<00:20:29.919> yesterday<00:20:30.440> so<00:20:30.600> she<00:20:30.760> knows 00:20:30.990 --> 00:20:31.000 align:start position:0% was an MC just yesterday so she knows 00:20:31.000 --> 00:20:32.789 align:start position:0% was an MC just yesterday so she knows how<00:20:31.120> it<00:20:31.240> feels<00:20:31.919> I<00:20:32.000> know<00:20:32.320> I<00:20:32.400> know<00:20:32.520> how<00:20:32.640> you're 00:20:32.789 --> 00:20:32.799 align:start position:0% how it feels I know I know how you're 00:20:32.799 --> 00:20:34.789 align:start position:0% how it feels I know I know how you're feeling<00:20:33.200> right<00:20:33.360> now<00:20:33.640> after<00:20:33.919> like<00:20:34.120> 5<00:20:34.360> hours<00:20:34.679> I 00:20:34.789 --> 00:20:34.799 align:start position:0% feeling right now after like 5 hours I 00:20:34.799 --> 00:20:36.750 align:start position:0% feeling right now after like 5 hours I was<00:20:34.919> like<00:20:35.080> I<00:20:35.159> don't<00:20:35.320> remember<00:20:35.679> anyone's<00:20:36.200> name 00:20:36.750 --> 00:20:36.760 align:start position:0% was like I don't remember anyone's name 00:20:36.760 --> 00:20:38.750 align:start position:0% was like I don't remember anyone's name I<00:20:36.840> don't<00:20:37.039> know<00:20:37.480> what<00:20:37.640> even<00:20:37.919> this<00:20:38.159> topic<00:20:38.600> where 00:20:38.750 --> 00:20:38.760 align:start position:0% I don't know what even this topic where 00:20:38.760 --> 00:20:41.310 align:start position:0% I don't know what even this topic where are<00:20:39.000> we<00:20:40.000> this<00:20:40.120> was<00:20:40.280> a<00:20:40.440> great<00:20:40.640> one<00:20:40.880> though<00:20:41.120> even 00:20:41.310 --> 00:20:41.320 align:start position:0% are we this was a great one though even 00:20:41.320 --> 00:20:43.230 align:start position:0% are we this was a great one though even though<00:20:41.440> it<00:20:41.480> was<00:20:41.640> technical<00:20:42.600> um<00:20:42.760> but<00:20:42.880> the<00:20:43.000> first 00:20:43.230 --> 00:20:43.240 align:start position:0% though it was technical um but the first 00:20:43.240 --> 00:20:47.149 align:start position:0% though it was technical um but the first question<00:20:43.600> here<00:20:43.840> is<00:20:44.360> when<00:20:44.840> kir<00:20:45.760> kir<00:20:46.320> is<00:20:46.600> now 00:20:47.149 --> 00:20:47.159 align:start position:0% question here is when kir kir is now 00:20:47.159 --> 00:20:50.710 align:start position:0% question here is when kir kir is now there<00:20:47.600> like<00:20:47.840> now<00:20:48.240> now<00:20:48.440> you<00:20:48.520> can<00:20:48.679> use<00:20:48.880> it<00:20:49.200> so<00:20:49.919> um 00:20:50.710 --> 00:20:50.720 align:start position:0% there like now now you can use it so um 00:20:50.720 --> 00:20:52.789 align:start position:0% there like now now you can use it so um yeah<00:20:50.880> if<00:20:50.960> you<00:20:51.080> go<00:20:51.200> to<00:20:51.360> the<00:20:51.480> TSO<00:20:51.960> GitHub<00:20:52.400> you<00:20:52.480> can 00:20:52.789 --> 00:20:52.799 align:start position:0% yeah if you go to the TSO GitHub you can 00:20:52.799 --> 00:20:56.470 align:start position:0% yeah if you go to the TSO GitHub you can go<00:20:53.039> and<00:20:53.440> find<00:20:54.080> uh<00:20:54.240> kir<00:20:54.840> and<00:20:55.000> play<00:20:55.240> with<00:20:55.480> that 00:20:56.470 --> 00:20:56.480 align:start position:0% go and find uh kir and play with that 00:20:56.480 --> 00:20:58.230 align:start position:0% go and find uh kir and play with that awesome<00:20:57.080> and<00:20:57.240> then<00:20:57.520> what's<00:20:57.720> the<00:20:57.880> difference 00:20:58.230 --> 00:20:58.240 align:start position:0% awesome and then what's the difference 00:20:58.240 --> 00:21:02.590 align:start position:0% awesome and then what's the difference between<00:20:58.799> ZK<00:20:59.360> with<00:20:59.559> MPC<00:21:00.280> versus<00:21:01.080> FHA 00:21:02.590 --> 00:21:02.600 align:start position:0% between ZK with MPC versus FHA 00:21:02.600 --> 00:21:04.110 align:start position:0% between ZK with MPC versus FHA computation 00:21:04.110 --> 00:21:04.120 align:start position:0% computation 00:21:04.120 --> 00:21:07.430 align:start position:0% computation well<00:21:05.120> um<00:21:05.760> I<00:21:05.919> did<00:21:06.240> I<00:21:06.400> I<00:21:06.600> resisted<00:21:07.039> saying<00:21:07.240> things 00:21:07.430 --> 00:21:07.440 align:start position:0% well um I did I I resisted saying things 00:21:07.440 --> 00:21:10.710 align:start position:0% well um I did I I resisted saying things about<00:21:07.600> FH<00:21:08.200> so<00:21:08.919> is<00:21:09.360> great<00:21:09.880> and<00:21:10.120> like<00:21:10.320> is<00:21:10.440> a 00:21:10.710 --> 00:21:10.720 align:start position:0% about FH so is great and like is a 00:21:10.720 --> 00:21:12.870 align:start position:0% about FH so is great and like is a super<00:21:11.080> ultimate<00:21:11.520> goal<00:21:11.720> for<00:21:11.960> privacy<00:21:12.520> because 00:21:12.870 --> 00:21:12.880 align:start position:0% super ultimate goal for privacy because 00:21:12.880 --> 00:21:14.909 align:start position:0% super ultimate goal for privacy because even<00:21:13.159> if<00:21:13.720> like<00:21:13.880> there<00:21:14.039> is<00:21:14.240> collusion<00:21:14.679> in<00:21:14.799> the 00:21:14.909 --> 00:21:14.919 align:start position:0% even if like there is collusion in the 00:21:14.919 --> 00:21:17.070 align:start position:0% even if like there is collusion in the network<00:21:15.400> stuff<00:21:15.720> is<00:21:15.919> still<00:21:16.240> encrypted<00:21:16.760> and<00:21:16.919> you 00:21:17.070 --> 00:21:17.080 align:start position:0% network stuff is still encrypted and you 00:21:17.080 --> 00:21:20.070 align:start position:0% network stuff is still encrypted and you cannot<00:21:17.799> like<00:21:18.159> uh<00:21:18.320> it's<00:21:18.679> like<00:21:19.400> a<00:21:19.559> better<00:21:19.840> level 00:21:20.070 --> 00:21:20.080 align:start position:0% cannot like uh it's like a better level 00:21:20.080 --> 00:21:22.310 align:start position:0% cannot like uh it's like a better level of<00:21:20.240> privacy<00:21:20.679> but<00:21:20.799> it's<00:21:21.000> hyper<00:21:21.400> inefficient 00:21:22.310 --> 00:21:22.320 align:start position:0% of privacy but it's hyper inefficient 00:21:22.320 --> 00:21:25.029 align:start position:0% of privacy but it's hyper inefficient well<00:21:22.960> like<00:21:23.120> it's<00:21:23.880> uh<00:21:24.039> it's<00:21:24.200> super<00:21:24.520> inefficient 00:21:25.029 --> 00:21:25.039 align:start position:0% well like it's uh it's super inefficient 00:21:25.039 --> 00:21:26.390 align:start position:0% well like it's uh it's super inefficient so<00:21:25.200> I<00:21:25.320> think 00:21:26.390 --> 00:21:26.400 align:start position:0% so I think 00:21:26.400 --> 00:21:29.350 align:start position:0% so I think um<00:21:27.400> we<00:21:27.520> saw<00:21:27.760> at<00:21:27.919> CK<00:21:28.240> Summit<00:21:28.679> recently<00:21:29.159> if<00:21:29.240> you 00:21:29.350 --> 00:21:29.360 align:start position:0% um we saw at CK Summit recently if you 00:21:29.360 --> 00:21:31.070 align:start position:0% um we saw at CK Summit recently if you wanted<00:21:29.640> to<00:21:29.799> generate<00:21:30.200> Zer<00:21:30.480> knowledge<00:21:30.799> proofs 00:21:31.070 --> 00:21:31.080 align:start position:0% wanted to generate Zer knowledge proofs 00:21:31.080 --> 00:21:33.470 align:start position:0% wanted to generate Zer knowledge proofs in<00:21:31.200> an<00:21:31.919> environment<00:21:32.559> it 00:21:33.470 --> 00:21:33.480 align:start position:0% in an environment it 00:21:33.480 --> 00:21:37.230 align:start position:0% in an environment it was<00:21:34.760> like<00:21:35.760> like<00:21:36.000> order<00:21:36.279> of<00:21:36.559> minutes<00:21:36.960> rather 00:21:37.230 --> 00:21:37.240 align:start position:0% was like like order of minutes rather 00:21:37.240 --> 00:21:40.430 align:start position:0% was like like order of minutes rather than<00:21:38.080> you<00:21:38.200> know<00:21:38.360> tens<00:21:38.760> per<00:21:39.000> second<00:21:39.440> so<00:21:40.080> it's<00:21:40.240> uh 00:21:40.430 --> 00:21:40.440 align:start position:0% than you know tens per second so it's uh 00:21:40.440 --> 00:21:43.190 align:start position:0% than you know tens per second so it's uh just<00:21:40.600> low<00:21:41.039> and<00:21:41.320> I<00:21:41.400> think<00:21:41.600> FHA<00:21:42.159> is<00:21:42.600> often 00:21:43.190 --> 00:21:43.200 align:start position:0% just low and I think FHA is often 00:21:43.200 --> 00:21:46.149 align:start position:0% just low and I think FHA is often considered<00:21:44.200> a<00:21:44.559> specific<00:21:44.919> example<00:21:45.240> of<00:21:45.360> MPC<00:21:45.799> MPC 00:21:46.149 --> 00:21:46.159 align:start position:0% considered a specific example of MPC MPC 00:21:46.159 --> 00:21:48.070 align:start position:0% considered a specific example of MPC MPC is<00:21:46.320> super<00:21:46.720> General<00:21:47.120> so<00:21:47.480> everything<00:21:47.760> can<00:21:47.919> be 00:21:48.070 --> 00:21:48.080 align:start position:0% is super General so everything can be 00:21:48.080 --> 00:21:51.870 align:start position:0% is super General so everything can be cast<00:21:48.400> essentially<00:21:48.799> as<00:21:49.000> MPC<00:21:50.000> but<00:21:50.240> uh<00:21:50.400> yeah<00:21:50.880> FG 00:21:51.870 --> 00:21:51.880 align:start position:0% cast essentially as MPC but uh yeah FG 00:21:51.880 --> 00:21:54.830 align:start position:0% cast essentially as MPC but uh yeah FG is<00:21:52.039> just<00:21:52.480> slower<00:21:53.480> thanks<00:21:53.880> and<00:21:54.320> uh<00:21:54.440> the<00:21:54.600> next 00:21:54.830 --> 00:21:54.840 align:start position:0% is just slower thanks and uh the next 00:21:54.840 --> 00:21:57.909 align:start position:0% is just slower thanks and uh the next question<00:21:55.120> is<00:21:55.279> about<00:21:55.520> NPC<00:21:56.480> wallets<00:21:57.480> is<00:21:57.600> it<00:21:57.760> the 00:21:57.909 --> 00:21:57.919 align:start position:0% question is about NPC wallets is it the 00:21:57.919 --> 00:22:00.070 align:start position:0% question is about NPC wallets is it the future<00:21:58.240> and<00:21:58.600> what<00:21:58.679> are<00:21:58.799> your<00:21:59.120> thoughts<00:21:59.480> on<00:21:59.679> NPC 00:22:00.070 --> 00:22:00.080 align:start position:0% future and what are your thoughts on NPC 00:22:00.080 --> 00:22:01.990 align:start position:0% future and what are your thoughts on NPC wallets<00:22:00.440> generally<00:22:01.159> I<00:22:01.279> also<00:22:01.480> didn't<00:22:01.720> mention 00:22:01.990 --> 00:22:02.000 align:start position:0% wallets generally I also didn't mention 00:22:02.000 --> 00:22:04.070 align:start position:0% wallets generally I also didn't mention NPC<00:22:02.440> wallets<00:22:02.760> and<00:22:02.880> I<00:22:03.000> was<00:22:03.159> going<00:22:03.360> to<00:22:03.760> make<00:22:03.919> a 00:22:04.070 --> 00:22:04.080 align:start position:0% NPC wallets and I was going to make a 00:22:04.080 --> 00:22:06.190 align:start position:0% NPC wallets and I was going to make a comment<00:22:04.440> about<00:22:04.720> that<00:22:04.880> so<00:22:05.039> for<00:22:05.159> me<00:22:05.480> I<00:22:05.640> mean<00:22:06.080> when 00:22:06.190 --> 00:22:06.200 align:start position:0% comment about that so for me I mean when 00:22:06.200 --> 00:22:08.470 align:start position:0% comment about that so for me I mean when I<00:22:06.320> mean<00:22:06.600> MPC<00:22:07.080> I<00:22:07.159> mean<00:22:07.440> like<00:22:07.640> general<00:22:08.080> purpose 00:22:08.470 --> 00:22:08.480 align:start position:0% I mean MPC I mean like general purpose 00:22:08.480 --> 00:22:10.990 align:start position:0% I mean MPC I mean like general purpose MPC<00:22:09.159> like<00:22:09.320> general<00:22:09.640> purpose<00:22:10.000> computation<00:22:10.880> for 00:22:10.990 --> 00:22:11.000 align:start position:0% MPC like general purpose computation for 00:22:11.000 --> 00:22:14.070 align:start position:0% MPC like general purpose computation for me<00:22:11.159> MPC<00:22:11.640> wallets<00:22:12.039> are<00:22:12.279> kind<00:22:12.400> of<00:22:13.080> threshold 00:22:14.070 --> 00:22:14.080 align:start position:0% me MPC wallets are kind of threshold 00:22:14.080 --> 00:22:15.909 align:start position:0% me MPC wallets are kind of threshold signatures<00:22:14.640> and<00:22:14.760> things<00:22:14.919> like<00:22:15.120> this<00:22:15.279> so<00:22:15.799> it's 00:22:15.909 --> 00:22:15.919 align:start position:0% signatures and things like this so it's 00:22:15.919 --> 00:22:17.710 align:start position:0% signatures and things like this so it's a<00:22:16.039> little<00:22:16.240> bit<00:22:16.360> of<00:22:16.480> a<00:22:16.679> special<00:22:17.080> case<00:22:17.320> and<00:22:17.559> like 00:22:17.710 --> 00:22:17.720 align:start position:0% a little bit of a special case and like 00:22:17.720 --> 00:22:20.909 align:start position:0% a little bit of a special case and like a<00:22:17.919> kind<00:22:18.039> of<00:22:18.159> a<00:22:18.360> sub<00:22:19.360> um<00:22:19.840> sub<00:22:20.240> computation<00:22:20.720> it's 00:22:20.909 --> 00:22:20.919 align:start position:0% a kind of a sub um sub computation it's 00:22:20.919 --> 00:22:22.310 align:start position:0% a kind of a sub um sub computation it's just<00:22:21.080> one<00:22:21.320> type<00:22:21.559> it's<00:22:21.720> just<00:22:21.880> generating 00:22:22.310 --> 00:22:22.320 align:start position:0% just one type it's just generating 00:22:22.320 --> 00:22:24.029 align:start position:0% just one type it's just generating signatures<00:22:22.880> essentially<00:22:23.360> so<00:22:23.480> it's<00:22:23.640> kind<00:22:23.760> of<00:22:23.880> a 00:22:24.029 --> 00:22:24.039 align:start position:0% signatures essentially so it's kind of a 00:22:24.039 --> 00:22:27.590 align:start position:0% signatures essentially so it's kind of a small<00:22:24.400> part<00:22:24.600> of<00:22:24.960> NPC<00:22:25.960> um<00:22:26.440> super<00:22:26.840> efficient<00:22:27.360> I 00:22:27.590 --> 00:22:27.600 align:start position:0% small part of NPC um super efficient I 00:22:27.600 --> 00:22:30.590 align:start position:0% small part of NPC um super efficient I quite<00:22:27.840> like<00:22:28.120> them<00:22:29.000> personally<00:22:29.880> we<00:22:30.000> don't<00:22:30.200> work 00:22:30.590 --> 00:22:30.600 align:start position:0% quite like them personally we don't work 00:22:30.600 --> 00:22:33.470 align:start position:0% quite like them personally we don't work on<00:22:30.760> any<00:22:30.919> of<00:22:31.080> that<00:22:31.240> stuff<00:22:31.559> but<00:22:31.919> um<00:22:32.360> I<00:22:32.559> I<00:22:32.679> like<00:22:32.840> it 00:22:33.470 --> 00:22:33.480 align:start position:0% on any of that stuff but um I I like it 00:22:33.480 --> 00:22:36.950 align:start position:0% on any of that stuff but um I I like it yeah<00:22:33.679> they're<00:22:34.080> cool<00:22:35.080> cool<00:22:35.760> um<00:22:36.200> and<00:22:36.760> there<00:22:36.880> are 00:22:36.950 --> 00:22:36.960 align:start position:0% yeah they're cool cool um and there are 00:22:36.960 --> 00:22:38.350 align:start position:0% yeah they're cool cool um and there are a<00:22:37.080> couple<00:22:37.320> of<00:22:37.520> questions<00:22:37.880> that<00:22:38.000> are<00:22:38.120> more 00:22:38.350 --> 00:22:38.360 align:start position:0% a couple of questions that are more 00:22:38.360 --> 00:22:40.669 align:start position:0% a couple of questions that are more about<00:22:38.679> the<00:22:39.200> yeah<00:22:39.400> your<00:22:39.600> opinion<00:22:39.960> on<00:22:40.240> things 00:22:40.669 --> 00:22:40.679 align:start position:0% about the yeah your opinion on things 00:22:40.679 --> 00:22:44.590 align:start position:0% about the yeah your opinion on things but<00:22:41.080> first<00:22:41.360> one<00:22:41.640> is<00:22:42.200> how<00:22:42.360> do<00:22:42.679> co-<00:22:43.000> snarks<00:22:43.679> work 00:22:44.590 --> 00:22:44.600 align:start position:0% but first one is how do co- snarks work 00:22:44.600 --> 00:22:47.230 align:start position:0% but first one is how do co- snarks work how<00:22:44.679> to<00:22:44.880> co<00:22:45.440> very<00:22:45.600> briefly<00:22:46.240> in<00:22:46.440> like<00:22:46.720> 20 00:22:47.230 --> 00:22:47.240 align:start position:0% how to co very briefly in like 20 00:22:47.240 --> 00:22:49.789 align:start position:0% how to co very briefly in like 20 seconds<00:22:48.240> if<00:22:48.360> you<00:22:48.520> know<00:22:48.720> how<00:22:48.919> ZK<00:22:49.400> works<00:22:49.679> you 00:22:49.789 --> 00:22:49.799 align:start position:0% seconds if you know how ZK works you 00:22:49.799 --> 00:22:51.710 align:start position:0% seconds if you know how ZK works you take<00:22:49.960> the<00:22:50.080> ZK<00:22:50.559> and<00:22:50.679> you<00:22:50.799> split<00:22:51.080> it<00:22:51.240> over<00:22:51.600> uh 00:22:51.710 --> 00:22:51.720 align:start position:0% take the ZK and you split it over uh 00:22:51.720 --> 00:22:55.190 align:start position:0% take the ZK and you split it over uh three<00:22:52.000> people<00:22:52.520> like<00:22:53.240> essentially<00:22:54.240> like<00:22:55.080> what 00:22:55.190 --> 00:22:55.200 align:start position:0% three people like essentially like what 00:22:55.200 --> 00:22:56.590 align:start position:0% three people like essentially like what is<00:22:55.320> needed<00:22:55.600> to<00:22:55.720> compute<00:22:55.960> is<00:22:56.080> zero<00:22:56.320> knowledge 00:22:56.590 --> 00:22:56.600 align:start position:0% is needed to compute is zero knowledge 00:22:56.600 --> 00:22:58.149 align:start position:0% is needed to compute is zero knowledge proof<00:22:56.840> is<00:22:56.960> essentially<00:22:57.320> linear<00:22:57.799> so<00:22:57.919> you<00:22:58.039> just 00:22:58.149 --> 00:22:58.159 align:start position:0% proof is essentially linear so you just 00:22:58.159 --> 00:22:59.669 align:start position:0% proof is essentially linear so you just do<00:22:58.279> it<00:22:58.520> three<00:22:58.720> times<00:22:58.919> and<00:22:59.039> you<00:22:59.200> communicate 00:22:59.669 --> 00:22:59.679 align:start position:0% do it three times and you communicate 00:22:59.679 --> 00:23:01.870 align:start position:0% do it three times and you communicate and<00:22:59.799> you<00:22:59.880> get<00:23:00.000> one<00:23:00.200> proof<00:23:00.640> in<00:23:00.799> in<00:23:00.880> a 00:23:01.870 --> 00:23:01.880 align:start position:0% and you get one proof in in a 00:23:01.880 --> 00:23:04.789 align:start position:0% and you get one proof in in a nutshell<00:23:02.880> okay<00:23:03.440> and<00:23:03.679> what<00:23:03.799> do<00:23:03.919> you<00:23:04.080> think<00:23:04.279> of 00:23:04.789 --> 00:23:04.799 align:start position:0% nutshell okay and what do you think of 00:23:04.799 --> 00:23:07.669 align:start position:0% nutshell okay and what do you think of te<00:23:05.600> or 00:23:07.669 --> 00:23:07.679 align:start position:0% te or 00:23:07.679 --> 00:23:10.590 align:start position:0% te or T<00:23:08.679> and<00:23:08.880> what<00:23:09.000> is<00:23:09.200> tea<00:23:09.640> did<00:23:09.840> this<00:23:10.080> question<00:23:10.440> come 00:23:10.590 --> 00:23:10.600 align:start position:0% T and what is tea did this question come 00:23:10.600 --> 00:23:12.110 align:start position:0% T and what is tea did this question come from<00:23:10.799> someone<00:23:11.039> who<00:23:11.200> knows<00:23:11.480> me<00:23:11.640> or<00:23:11.760> someone<00:23:11.960> who 00:23:12.110 --> 00:23:12.120 align:start position:0% from someone who knows me or someone who 00:23:12.120 --> 00:23:14.110 align:start position:0% from someone who knows me or someone who doesn't<00:23:12.480> know<00:23:12.640> me<00:23:12.880> that<00:23:13.480> that<00:23:13.600> makes<00:23:13.799> all<00:23:13.960> the 00:23:14.110 --> 00:23:14.120 align:start position:0% doesn't know me that that makes all the 00:23:14.120 --> 00:23:16.430 align:start position:0% doesn't know me that that makes all the difference<00:23:14.760> so<00:23:14.960> te<00:23:15.320> is<00:23:15.400> a<00:23:15.559> trusted<00:23:15.919> execution 00:23:16.430 --> 00:23:16.440 align:start position:0% difference so te is a trusted execution 00:23:16.440 --> 00:23:18.110 align:start position:0% difference so te is a trusted execution environment<00:23:16.919> and<00:23:17.080> it's<00:23:17.279> like<00:23:17.400> a<00:23:17.600> super<00:23:17.919> Hot 00:23:18.110 --> 00:23:18.120 align:start position:0% environment and it's like a super Hot 00:23:18.120 --> 00:23:21.870 align:start position:0% environment and it's like a super Hot Topic<00:23:18.400> at<00:23:18.520> the<00:23:18.640> moment<00:23:19.600> um<00:23:20.400> I<00:23:21.039> think<00:23:21.400> they're 00:23:21.870 --> 00:23:21.880 align:start position:0% Topic at the moment um I think they're 00:23:21.880 --> 00:23:24.390 align:start position:0% Topic at the moment um I think they're wonderful<00:23:22.679> and<00:23:23.159> um<00:23:23.480> no<00:23:23.640> so<00:23:23.840> the<00:23:23.960> thing<00:23:24.120> is<00:23:24.240> with 00:23:24.390 --> 00:23:24.400 align:start position:0% wonderful and um no so the thing is with 00:23:24.400 --> 00:23:26.350 align:start position:0% wonderful and um no so the thing is with tees<00:23:24.960> they're<00:23:25.240> great<00:23:25.559> and<00:23:25.720> it's<00:23:25.880> a<00:23:26.120> it's<00:23:26.240> a 00:23:26.350 --> 00:23:26.360 align:start position:0% tees they're great and it's a it's a 00:23:26.360 --> 00:23:28.710 align:start position:0% tees they're great and it's a it's a Super<00:23:26.600> Hot<00:23:26.799> Topic<00:23:27.080> at<00:23:27.200> the<00:23:27.440> moment<00:23:28.520> they're 00:23:28.710 --> 00:23:28.720 align:start position:0% Super Hot Topic at the moment they're 00:23:28.720 --> 00:23:31.350 align:start position:0% Super Hot Topic at the moment they're quite<00:23:29.240> easily<00:23:29.880> breakable<00:23:30.480> so<00:23:30.760> I<00:23:30.880> have 00:23:31.350 --> 00:23:31.360 align:start position:0% quite easily breakable so I have 00:23:31.360 --> 00:23:32.669 align:start position:0% quite easily breakable so I have sometimes<00:23:31.559> been<00:23:31.760> critical<00:23:32.120> of<00:23:32.279> them<00:23:32.400> in<00:23:32.520> the 00:23:32.669 --> 00:23:32.679 align:start position:0% sometimes been critical of them in the 00:23:32.679 --> 00:23:34.390 align:start position:0% sometimes been critical of them in the past<00:23:32.960> which<00:23:33.039> is<00:23:33.240> why<00:23:33.440> sometime<00:23:33.919> I'm<00:23:34.080> wondering 00:23:34.390 --> 00:23:34.400 align:start position:0% past which is why sometime I'm wondering 00:23:34.400 --> 00:23:36.870 align:start position:0% past which is why sometime I'm wondering if<00:23:34.520> this<00:23:34.600> is<00:23:34.720> someone<00:23:34.960> who<00:23:35.080> knows<00:23:35.279> me<00:23:36.080> but<00:23:36.360> uh<00:23:36.799> I 00:23:36.870 --> 00:23:36.880 align:start position:0% if this is someone who knows me but uh I 00:23:36.880 --> 00:23:39.669 align:start position:0% if this is someone who knows me but uh I think<00:23:37.039> it's<00:23:37.240> good<00:23:37.559> like<00:23:37.679> so<00:23:37.919> with<00:23:38.240> the<00:23:38.679> coars 00:23:39.669 --> 00:23:39.679 align:start position:0% think it's good like so with the coars 00:23:39.679 --> 00:23:42.029 align:start position:0% think it's good like so with the coars we<00:23:39.880> talked<00:23:40.240> about<00:23:40.799> um<00:23:40.960> the<00:23:41.080> collusion<00:23:41.600> problem 00:23:42.029 --> 00:23:42.039 align:start position:0% we talked about um the collusion problem 00:23:42.039 --> 00:23:44.669 align:start position:0% we talked about um the collusion problem and<00:23:42.360> you<00:23:42.480> know<00:23:43.039> I<00:23:43.159> said<00:23:43.480> that<00:23:43.840> in<00:23:44.039> this<00:23:44.200> network 00:23:44.669 --> 00:23:44.679 align:start position:0% and you know I said that in this network 00:23:44.679 --> 00:23:46.269 align:start position:0% and you know I said that in this network let's<00:23:44.840> say<00:23:44.960> that<00:23:45.080> we<00:23:45.159> are<00:23:45.279> running<00:23:45.600> now<00:23:46.080> you 00:23:46.269 --> 00:23:46.279 align:start position:0% let's say that we are running now you 00:23:46.279 --> 00:23:48.470 align:start position:0% let's say that we are running now you trust<00:23:46.640> the<00:23:46.760> three<00:23:46.919> of<00:23:47.039> us<00:23:47.240> not<00:23:47.400> to<00:23:47.840> uh<00:23:48.000> collude 00:23:48.470 --> 00:23:48.480 align:start position:0% trust the three of us not to uh collude 00:23:48.480 --> 00:23:50.789 align:start position:0% trust the three of us not to uh collude and<00:23:48.600> so<00:23:49.000> tees<00:23:49.440> are<00:23:49.640> one<00:23:49.919> defense<00:23:50.279> against<00:23:50.559> this 00:23:50.789 --> 00:23:50.799 align:start position:0% and so tees are one defense against this 00:23:50.799 --> 00:23:53.510 align:start position:0% and so tees are one defense against this if<00:23:50.919> you<00:23:51.120> sort<00:23:51.360> of<00:23:51.520> run<00:23:51.720> the<00:23:51.840> MPC<00:23:52.480> in<00:23:52.640> a<00:23:52.760> te 00:23:53.510 --> 00:23:53.520 align:start position:0% if you sort of run the MPC in a te 00:23:53.520 --> 00:23:54.870 align:start position:0% if you sort of run the MPC in a te across<00:23:54.039> you<00:23:54.159> know<00:23:54.279> the<00:23:54.400> nodes<00:23:54.679> and<00:23:54.799> the 00:23:54.870 --> 00:23:54.880 align:start position:0% across you know the nodes and the 00:23:54.880 --> 00:23:57.310 align:start position:0% across you know the nodes and the network<00:23:55.720> um<00:23:55.919> it's<00:23:56.080> one<00:23:56.320> nice<00:23:56.600> defense<00:23:57.120> and 00:23:57.310 --> 00:23:57.320 align:start position:0% network um it's one nice defense and 00:23:57.320 --> 00:23:59.470 align:start position:0% network um it's one nice defense and also<00:23:57.919> like 00:23:59.470 --> 00:23:59.480 align:start position:0% also like 00:23:59.480 --> 00:24:01.510 align:start position:0% also like I<00:23:59.720> as<00:23:59.799> I<00:23:59.919> said<00:24:00.080> te<00:24:00.600> can<00:24:00.919> sometimes<00:24:01.120> be<00:24:01.279> a<00:24:01.360> bit 00:24:01.510 --> 00:24:01.520 align:start position:0% I as I said te can sometimes be a bit 00:24:01.520 --> 00:24:03.750 align:start position:0% I as I said te can sometimes be a bit weak<00:24:02.200> um<00:24:02.360> if<00:24:02.480> you<00:24:02.600> use<00:24:02.880> three<00:24:03.080> of<00:24:03.240> them<00:24:03.520> from 00:24:03.750 --> 00:24:03.760 align:start position:0% weak um if you use three of them from 00:24:03.760 --> 00:24:05.950 align:start position:0% weak um if you use three of them from different<00:24:04.520> uh<00:24:04.840> providers<00:24:05.320> then<00:24:05.520> like<00:24:05.679> spread 00:24:05.950 --> 00:24:05.960 align:start position:0% different uh providers then like spread 00:24:05.960 --> 00:24:07.470 align:start position:0% different uh providers then like spread them<00:24:06.080> around<00:24:06.240> the<00:24:06.360> world<00:24:06.720> it's<00:24:06.880> also<00:24:07.159> a<00:24:07.279> lot 00:24:07.470 --> 00:24:07.480 align:start position:0% them around the world it's also a lot 00:24:07.480 --> 00:24:09.470 align:start position:0% them around the world it's also a lot better<00:24:07.760> so<00:24:08.200> ultimately<00:24:08.799> I<00:24:08.880> think<00:24:09.200> um<00:24:09.360> yeah 00:24:09.470 --> 00:24:09.480 align:start position:0% better so ultimately I think um yeah 00:24:09.480 --> 00:24:11.590 align:start position:0% better so ultimately I think um yeah we're<00:24:09.600> going<00:24:09.720> to<00:24:09.840> see<00:24:10.120> that<00:24:10.720> happening<00:24:11.240> very 00:24:11.590 --> 00:24:11.600 align:start position:0% we're going to see that happening very 00:24:11.600 --> 00:24:14.950 align:start position:0% we're going to see that happening very soon<00:24:12.600> cool<00:24:12.960> thank<00:24:13.159> you<00:24:13.559> and<00:24:13.960> um<00:24:14.640> I<00:24:14.720> think<00:24:14.840> we 00:24:14.950 --> 00:24:14.960 align:start position:0% soon cool thank you and um I think we 00:24:14.960 --> 00:24:16.830 align:start position:0% soon cool thank you and um I think we have<00:24:15.080> time<00:24:15.200> for<00:24:15.400> one<00:24:15.640> last<00:24:15.880> question<00:24:16.520> how<00:24:16.640> does 00:24:16.830 --> 00:24:16.840 align:start position:0% have time for one last question how does 00:24:16.840 --> 00:24:19.630 align:start position:0% have time for one last question how does the<00:24:16.960> MPC<00:24:17.440> Network<00:24:17.960> receive<00:24:18.559> private<00:24:18.919> data<00:24:19.520> is 00:24:19.630 --> 00:24:19.640 align:start position:0% the MPC Network receive private data is 00:24:19.640 --> 00:24:21.870 align:start position:0% the MPC Network receive private data is it<00:24:19.760> in<00:24:19.880> the<00:24:20.000> encrypted<00:24:20.600> format<00:24:21.080> for<00:24:21.279> snark 00:24:21.870 --> 00:24:21.880 align:start position:0% it in the encrypted format for snark 00:24:21.880 --> 00:24:24.310 align:start position:0% it in the encrypted format for snark generation 00:24:24.310 --> 00:24:24.320 align:start position:0% generation 00:24:24.320 --> 00:24:27.909 align:start position:0% generation yes<00:24:25.320> simple<00:24:25.799> um<00:24:26.039> I<00:24:26.120> mean<00:24:26.880> it's<00:24:27.080> encrypted<00:24:27.720> like 00:24:27.909 --> 00:24:27.919 align:start position:0% yes simple um I mean it's encrypted like 00:24:27.919 --> 00:24:30.269 align:start position:0% yes simple um I mean it's encrypted like across<00:24:28.159> the<00:24:28.440> internet<00:24:29.039> but<00:24:29.559> overall<00:24:30.080> like 00:24:30.269 --> 00:24:30.279 align:start position:0% across the internet but overall like 00:24:30.279 --> 00:24:32.669 align:start position:0% across the internet but overall like before<00:24:30.559> that<00:24:30.760> even<00:24:31.159> from<00:24:31.559> your<00:24:31.760> phone<00:24:32.360> it's 00:24:32.669 --> 00:24:32.679 align:start position:0% before that even from your phone it's 00:24:32.679 --> 00:24:35.350 align:start position:0% before that even from your phone it's sent<00:24:33.679> it's<00:24:33.880> split<00:24:34.279> into<00:24:34.480> secret<00:24:34.799> shares<00:24:35.240> which 00:24:35.350 --> 00:24:35.360 align:start position:0% sent it's split into secret shares which 00:24:35.360 --> 00:24:37.870 align:start position:0% sent it's split into secret shares which is<00:24:35.559> seen<00:24:35.960> as<00:24:36.480> can<00:24:36.600> be<00:24:36.760> cast<00:24:37.039> as<00:24:37.159> a<00:24:37.240> form<00:24:37.559> of 00:24:37.870 --> 00:24:37.880 align:start position:0% is seen as can be cast as a form of 00:24:37.880 --> 00:24:39.590 align:start position:0% is seen as can be cast as a form of encryption<00:24:38.399> so<00:24:38.679> essentially<00:24:39.039> you<00:24:39.159> encrypt<00:24:39.520> it 00:24:39.590 --> 00:24:39.600 align:start position:0% encryption so essentially you encrypt it 00:24:39.600 --> 00:24:41.870 align:start position:0% encryption so essentially you encrypt it on<00:24:39.720> your<00:24:39.880> phone<00:24:40.399> or<00:24:40.559> your<00:24:40.720> local<00:24:41.080> device<00:24:41.760> and 00:24:41.870 --> 00:24:41.880 align:start position:0% on your phone or your local device and 00:24:41.880 --> 00:24:44.350 align:start position:0% on your phone or your local device and then<00:24:42.000> you<00:24:42.080> send<00:24:42.279> it<00:24:42.399> to<00:24:42.520> the<00:24:42.880> servers<00:24:43.880> cool 00:24:44.350 --> 00:24:44.360 align:start position:0% then you send it to the servers cool 00:24:44.360 --> 00:24:45.830 align:start position:0% then you send it to the servers cool okay<00:24:44.640> I<00:24:44.679> think<00:24:44.840> we<00:24:44.960> got<00:24:45.159> one<00:24:45.360> time<00:24:45.480> for<00:24:45.720> one 00:24:45.830 --> 00:24:45.840 align:start position:0% okay I think we got one time for one 00:24:45.840 --> 00:24:49.830 align:start position:0% okay I think we got one time for one more<00:24:46.120> can<00:24:46.240> we<00:24:46.399> remove<00:24:46.840> initial<00:24:47.200> trust<00:24:47.520> set<00:24:47.760> of 00:24:49.830 --> 00:24:49.840 align:start position:0% more can we remove initial trust set of 00:24:49.840 --> 00:24:53.950 align:start position:0% more can we remove initial trust set of MPC<00:24:50.840> what's<00:24:51.039> the<00:24:51.200> initial<00:24:51.559> trust<00:24:51.919> set<00:24:52.679> I 00:24:53.950 --> 00:24:53.960 align:start position:0% MPC what's the initial trust set I 00:24:53.960 --> 00:24:58.430 align:start position:0% MPC what's the initial trust set I wonder<00:24:54.960> um<00:24:55.880> so<00:24:56.200> like<00:24:56.480> if<00:24:56.720> you<00:24:56.960> talk<00:24:57.279> about<00:24:58.039> like 00:24:58.430 --> 00:24:58.440 align:start position:0% wonder um so like if you talk about like 00:24:58.440 --> 00:25:00.630 align:start position:0% wonder um so like if you talk about like the<00:24:58.559> collusion<00:24:59.120> issue<00:24:59.919> um<00:25:00.279> I<00:25:00.360> think<00:25:00.520> that's 00:25:00.630 --> 00:25:00.640 align:start position:0% the collusion issue um I think that's 00:25:00.640 --> 00:25:02.470 align:start position:0% the collusion issue um I think that's what<00:25:00.760> they're<00:25:00.880> implying<00:25:01.279> is<00:25:01.440> the<00:25:01.600> collusion 00:25:02.470 --> 00:25:02.480 align:start position:0% what they're implying is the collusion 00:25:02.480 --> 00:25:04.510 align:start position:0% what they're implying is the collusion can<00:25:02.600> you<00:25:02.720> remove<00:25:03.039> it<00:25:03.360> I<00:25:03.399> mean<00:25:03.720> everybody's<00:25:04.360> not 00:25:04.510 --> 00:25:04.520 align:start position:0% can you remove it I mean everybody's not 00:25:04.520 --> 00:25:05.789 align:start position:0% can you remove it I mean everybody's not everybody's<00:25:04.919> working<00:25:05.200> on<00:25:05.320> it<00:25:05.440> but<00:25:05.559> like<00:25:05.720> this 00:25:05.789 --> 00:25:05.799 align:start position:0% everybody's working on it but like this 00:25:05.799 --> 00:25:07.870 align:start position:0% everybody's working on it but like this is<00:25:05.960> the<00:25:06.080> big<00:25:06.240> problem<00:25:06.480> in<00:25:06.640> NPC<00:25:07.080> at<00:25:07.159> the<00:25:07.279> moment 00:25:07.870 --> 00:25:07.880 align:start position:0% is the big problem in NPC at the moment 00:25:07.880 --> 00:25:11.070 align:start position:0% is the big problem in NPC at the moment um<00:25:08.559> can<00:25:08.679> you<00:25:08.840> remove 00:25:11.070 --> 00:25:11.080 align:start position:0% um can you remove 00:25:11.080 --> 00:25:15.549 align:start position:0% um can you remove it<00:25:12.080> never<00:25:12.399> fully<00:25:12.840> I'd<00:25:13.039> say<00:25:13.880> um<00:25:14.240> but<00:25:15.080> uh<00:25:15.279> yeah<00:25:15.440> we 00:25:15.549 --> 00:25:15.559 align:start position:0% it never fully I'd say um but uh yeah we 00:25:15.559 --> 00:25:17.110 align:start position:0% it never fully I'd say um but uh yeah we try<00:25:15.840> I<00:25:15.880> mean<00:25:16.080> one<00:25:16.440> there<00:25:16.559> are<00:25:16.799> different 00:25:17.110 --> 00:25:17.120 align:start position:0% try I mean one there are different 00:25:17.120 --> 00:25:19.510 align:start position:0% try I mean one there are different options<00:25:17.679> like<00:25:17.880> running<00:25:18.240> things<00:25:18.399> in<00:25:18.559> tees<00:25:19.440> you 00:25:19.510 --> 00:25:19.520 align:start position:0% options like running things in tees you 00:25:19.520 --> 00:25:20.990 align:start position:0% options like running things in tees you can<00:25:19.679> start<00:25:19.960> thinking<00:25:20.240> about<00:25:20.520> economic 00:25:20.990 --> 00:25:21.000 align:start position:0% can start thinking about economic 00:25:21.000 --> 00:25:23.269 align:start position:0% can start thinking about economic incentives<00:25:21.480> for<00:25:21.679> people<00:25:21.919> not<00:25:22.039> to<00:25:22.200> collude<00:25:23.120> um 00:25:23.269 --> 00:25:23.279 align:start position:0% incentives for people not to collude um 00:25:23.279 --> 00:25:25.830 align:start position:0% incentives for people not to collude um but<00:25:23.480> yeah<00:25:23.679> this<00:25:23.840> is<00:25:24.000> a<00:25:24.279> is<00:25:24.399> a<00:25:24.640> problem<00:25:25.600> cool 00:25:25.830 --> 00:25:25.840 align:start position:0% but yeah this is a is a problem cool 00:25:25.840 --> 00:25:27.950 align:start position:0% but yeah this is a is a problem cool well<00:25:26.039> thank<00:25:26.200> you<00:25:26.399> so<00:25:26.640> much<00:25:26.880> Ash<00:25:27.200> and<00:25:27.559> uh<00:25:27.760> thank 00:25:27.950 --> 00:25:27.960 align:start position:0% well thank you so much Ash and uh thank 00:25:27.960 --> 00:25:30.789 align:start position:0% well thank you so much Ash and uh thank you<00:25:28.399> you're<00:25:28.600> a<00:25:28.679> better<00:25:28.919> MC<00:25:29.320> than<00:25:29.480> me<00:25:30.480> you<00:25:30.559> did<00:25:30.720> a 00:25:30.789 --> 00:25:30.799 align:start position:0% you you're a better MC than me you did a 00:25:30.799 --> 00:25:32.990 align:start position:0% you you're a better MC than me you did a very<00:25:31.000> good<00:25:31.159> job<00:25:31.760> thank<00:25:31.919> you<00:25:32.520> but<00:25:32.640> you<00:25:32.720> can<00:25:32.840> find 00:25:32.990 --> 00:25:33.000 align:start position:0% very good job thank you but you can find 00:25:33.000 --> 00:25:35.159 align:start position:0% very good job thank you but you can find out