WEBVTT Kind: captions Language: en 00:00:13.360 --> 00:00:16.070 align:start position:0% all<00:00:13.519> right<00:00:13.839> thanks<00:00:14.160> so<00:00:14.320> much<00:00:14.679> Teresa<00:00:15.679> um<00:00:15.799> for 00:00:16.070 --> 00:00:16.080 align:start position:0% all right thanks so much Teresa um for 00:00:16.080 --> 00:00:18.670 align:start position:0% all right thanks so much Teresa um for introducing<00:00:16.640> us<00:00:17.080> and<00:00:17.720> welcome<00:00:18.039> to<00:00:18.199> the<00:00:18.400> panel 00:00:18.670 --> 00:00:18.680 align:start position:0% introducing us and welcome to the panel 00:00:18.680 --> 00:00:22.070 align:start position:0% introducing us and welcome to the panel on<00:00:18.960> consumer<00:00:19.480> apps<00:00:20.240> um<00:00:20.480> built<00:00:20.840> with<00:00:21.160> CK<00:00:21.640> MPC 00:00:22.070 --> 00:00:22.080 align:start position:0% on consumer apps um built with CK MPC 00:00:22.080 --> 00:00:25.470 align:start position:0% on consumer apps um built with CK MPC and<00:00:22.439> FHA<00:00:23.439> I'm<00:00:23.640> also<00:00:24.000> super<00:00:24.320> excited<00:00:25.199> about 00:00:25.470 --> 00:00:25.480 align:start position:0% and FHA I'm also super excited about 00:00:25.480 --> 00:00:29.589 align:start position:0% and FHA I'm also super excited about this<00:00:25.680> panel<00:00:26.240> here<00:00:27.199> um<00:00:27.599> how<00:00:27.800> I'm<00:00:28.160> thinking<00:00:29.160> of 00:00:29.589 --> 00:00:29.599 align:start position:0% this panel here um how I'm thinking of 00:00:29.599 --> 00:00:32.709 align:start position:0% this panel here um how I'm thinking of these<00:00:30.240> projects<00:00:30.800> is<00:00:31.439> we<00:00:31.599> have<00:00:31.800> two<00:00:32.079> of<00:00:32.279> them 00:00:32.709 --> 00:00:32.719 align:start position:0% these projects is we have two of them 00:00:32.719 --> 00:00:35.430 align:start position:0% these projects is we have two of them that<00:00:33.200> actually<00:00:33.559> buil<00:00:34.079> Primitives<00:00:34.719> so<00:00:35.000> ZK 00:00:35.430 --> 00:00:35.440 align:start position:0% that actually buil Primitives so ZK 00:00:35.440 --> 00:00:38.549 align:start position:0% that actually buil Primitives so ZK email<00:00:35.840> and<00:00:36.160> tesso<00:00:37.160> they're<00:00:37.399> building<00:00:37.960> sort<00:00:38.200> of 00:00:38.549 --> 00:00:38.559 align:start position:0% email and tesso they're building sort of 00:00:38.559 --> 00:00:41.270 align:start position:0% email and tesso they're building sort of libraries<00:00:39.239> and<00:00:39.520> tools<00:00:40.520> and<00:00:40.640> then<00:00:40.800> we<00:00:40.920> have<00:00:41.079> two 00:00:41.270 --> 00:00:41.280 align:start position:0% libraries and tools and then we have two 00:00:41.280 --> 00:00:44.110 align:start position:0% libraries and tools and then we have two of<00:00:41.399> them<00:00:41.600> who<00:00:41.760> built<00:00:42.039> on<00:00:42.320> top<00:00:42.520> of<00:00:42.719> them<00:00:43.079> so<00:00:44.000> we 00:00:44.110 --> 00:00:44.120 align:start position:0% of them who built on top of them so we 00:00:44.120 --> 00:00:47.630 align:start position:0% of them who built on top of them so we have<00:00:44.280> ZK<00:00:44.640> PDP<00:00:45.200> that<00:00:45.559> built<00:00:45.879> on<00:00:46.120> Z<00:00:46.440> Emil<00:00:47.440> and 00:00:47.630 --> 00:00:47.640 align:start position:0% have ZK PDP that built on Z Emil and 00:00:47.640 --> 00:00:52.470 align:start position:0% have ZK PDP that built on Z Emil and then<00:00:48.320> cursive<00:00:49.120> which<00:00:49.520> uses<00:00:50.520> teso<00:00:51.360> as<00:00:51.520> well<00:00:51.719> as 00:00:52.470 --> 00:00:52.480 align:start position:0% then cursive which uses teso as well as 00:00:52.480 --> 00:00:55.029 align:start position:0% then cursive which uses teso as well as mpf<00:00:53.480> so<00:00:53.840> this<00:00:54.000> is<00:00:54.160> a<00:00:54.399> really<00:00:54.719> good 00:00:55.029 --> 00:00:55.039 align:start position:0% mpf so this is a really good 00:00:55.039 --> 00:00:56.790 align:start position:0% mpf so this is a really good representation<00:00:55.800> across<00:00:56.120> the<00:00:56.280> stack<00:00:56.640> and 00:00:56.790 --> 00:00:56.800 align:start position:0% representation across the stack and 00:00:56.800 --> 00:00:59.590 align:start position:0% representation across the stack and we'll<00:00:57.039> have<00:00:57.600> I<00:00:57.719> have<00:00:57.920> lots<00:00:58.120> of<00:00:58.440> questions<00:00:59.440> for 00:00:59.590 --> 00:00:59.600 align:start position:0% we'll have I have lots of questions for 00:00:59.600 --> 00:01:02.590 align:start position:0% we'll have I have lots of questions for you<00:00:59.760> guys<00:01:00.359> um<00:01:01.000> so<00:01:01.320> I<00:01:01.399> want<00:01:01.559> to<00:01:01.920> first<00:01:02.280> start 00:01:02.590 --> 00:01:02.600 align:start position:0% you guys um so I want to first start 00:01:02.600 --> 00:01:08.070 align:start position:0% you guys um so I want to first start with<00:01:02.760> an<00:01:03.199> intro<00:01:04.199> can<00:01:04.360> we<00:01:04.640> get<00:01:05.519> um<00:01:05.799> ZK<00:01:06.280> email<00:01:07.159> ZK 00:01:08.070 --> 00:01:08.080 align:start position:0% with an intro can we get um ZK email ZK 00:01:08.080 --> 00:01:13.030 align:start position:0% with an intro can we get um ZK email ZK PTP<00:01:09.080> too<00:01:09.840> and<00:01:10.080> cursive<00:01:10.680> in<00:01:10.920> that<00:01:11.080> order<00:01:12.040> yeah 00:01:13.030 --> 00:01:13.040 align:start position:0% PTP too and cursive in that order yeah 00:01:13.040 --> 00:01:15.749 align:start position:0% PTP too and cursive in that order yeah sweet<00:01:13.600> um<00:01:14.000> yeah<00:01:14.159> I'm<00:01:14.280> aush<00:01:14.880> I<00:01:15.000> work<00:01:15.280> a<00:01:15.400> bunch<00:01:15.600> on 00:01:15.749 --> 00:01:15.759 align:start position:0% sweet um yeah I'm aush I work a bunch on 00:01:15.759 --> 00:01:18.350 align:start position:0% sweet um yeah I'm aush I work a bunch on ZK<00:01:16.119> email<00:01:16.880> the<00:01:17.000> idea<00:01:17.240> is<00:01:17.360> you<00:01:17.520> make<00:01:17.759> proofs<00:01:18.159> of 00:01:18.350 --> 00:01:18.360 align:start position:0% ZK email the idea is you make proofs of 00:01:18.360 --> 00:01:20.310 align:start position:0% ZK email the idea is you make proofs of emails<00:01:18.759> in<00:01:18.880> your<00:01:19.040> inbox<00:01:19.600> or<00:01:19.799> emails<00:01:20.119> you've 00:01:20.310 --> 00:01:20.320 align:start position:0% emails in your inbox or emails you've 00:01:20.320 --> 00:01:23.510 align:start position:0% emails in your inbox or emails you've sent<00:01:21.159> and<00:01:21.280> these<00:01:21.400> can<00:01:21.560> get<00:01:21.680> proved<00:01:21.960> on<00:01:22.520> chain 00:01:23.510 --> 00:01:23.520 align:start position:0% sent and these can get proved on chain 00:01:23.520 --> 00:01:26.469 align:start position:0% sent and these can get proved on chain um<00:01:24.320> we've<00:01:25.119> thought<00:01:25.320> a<00:01:25.439> lot<00:01:25.640> about<00:01:25.960> what<00:01:26.079> are 00:01:26.469 --> 00:01:26.479 align:start position:0% um we've thought a lot about what are 00:01:26.479 --> 00:01:28.870 align:start position:0% um we've thought a lot about what are both<00:01:27.479> the<00:01:27.799> interesting<00:01:28.159> apps<00:01:28.360> you<00:01:28.439> can<00:01:28.600> build 00:01:28.870 --> 00:01:28.880 align:start position:0% both the interesting apps you can build 00:01:28.880 --> 00:01:30.190 align:start position:0% both the interesting apps you can build and<00:01:29.040> what<00:01:29.119> is<00:01:29.240> the<00:01:29.360> best<00:01:29.520> kind<00:01:29.600> of<00:01:29.720> Def<00:01:29.960> toing 00:01:30.190 --> 00:01:30.200 align:start position:0% and what is the best kind of Def toing 00:01:30.200 --> 00:01:32.190 align:start position:0% and what is the best kind of Def toing to<00:01:30.320> do<00:01:30.520> that<00:01:31.079> um<00:01:31.200> and<00:01:31.320> on<00:01:31.439> the<00:01:31.560> side<00:01:31.759> I<00:01:31.880> also 00:01:32.190 --> 00:01:32.200 align:start position:0% to do that um and on the side I also 00:01:32.200 --> 00:01:34.469 align:start position:0% to do that um and on the side I also like<00:01:32.360> thinking<00:01:32.600> about<00:01:32.840> mpcf<00:01:33.759> and<00:01:34.079> things<00:01:34.320> like 00:01:34.469 --> 00:01:34.479 align:start position:0% like thinking about mpcf and things like 00:01:34.479 --> 00:01:38.190 align:start position:0% like thinking about mpcf and things like that<00:01:34.640> so<00:01:35.119> happy<00:01:35.320> to<00:01:35.479> also<00:01:35.720> jump<00:01:35.960> in<00:01:36.640> there<00:01:37.640> cool 00:01:38.190 --> 00:01:38.200 align:start position:0% that so happy to also jump in there cool 00:01:38.200 --> 00:01:40.910 align:start position:0% that so happy to also jump in there cool uh<00:01:38.320> I'm<00:01:38.439> Richard<00:01:38.920> I<00:01:39.040> work<00:01:39.159> on<00:01:39.320> ZK<00:01:39.680> P2P<00:01:40.680> uh<00:01:40.799> we 00:01:40.910 --> 00:01:40.920 align:start position:0% uh I'm Richard I work on ZK P2P uh we 00:01:40.920 --> 00:01:43.710 align:start position:0% uh I'm Richard I work on ZK P2P uh we build<00:01:41.399> P2P<00:01:41.920> marketplaces<00:01:42.759> that<00:01:42.920> connect<00:01:43.439> web 00:01:43.710 --> 00:01:43.720 align:start position:0% build P2P marketplaces that connect web 00:01:43.720 --> 00:01:47.630 align:start position:0% build P2P marketplaces that connect web 2<00:01:44.520> assets<00:01:45.280> and<00:01:45.759> uh<00:01:46.439> like<00:01:46.640> digital<00:01:47.040> Goods<00:01:47.439> with 00:01:47.630 --> 00:01:47.640 align:start position:0% 2 assets and uh like digital Goods with 00:01:47.640 --> 00:01:50.990 align:start position:0% 2 assets and uh like digital Goods with web<00:01:47.880> 3<00:01:48.799> uh<00:01:49.119> like<00:01:49.320> smart<00:01:49.719> contracts<00:01:50.719> uh<00:01:50.840> in 00:01:50.990 --> 00:01:51.000 align:start position:0% web 3 uh like smart contracts uh in 00:01:51.000 --> 00:01:53.910 align:start position:0% web 3 uh like smart contracts uh in particular<00:01:51.560> we<00:01:51.799> have<00:01:52.159> like<00:01:52.280> a<00:01:52.399> P2P<00:01:53.240> like<00:01:53.399> onoff 00:01:53.910 --> 00:01:53.920 align:start position:0% particular we have like a P2P like onoff 00:01:53.920 --> 00:01:57.069 align:start position:0% particular we have like a P2P like onoff ramp<00:01:54.840> uh<00:01:55.079> so<00:01:55.320> basically<00:01:55.680> you<00:01:55.799> can<00:01:56.640> uh<00:01:56.759> send 00:01:57.069 --> 00:01:57.079 align:start position:0% ramp uh so basically you can uh send 00:01:57.079 --> 00:01:59.469 align:start position:0% ramp uh so basically you can uh send money<00:01:57.399> from<00:01:57.600> VMO<00:01:58.039> and<00:01:58.200> use<00:01:58.439> that<00:01:58.680> to<00:01:59.159> trade 00:01:59.469 --> 00:01:59.479 align:start position:0% money from VMO and use that to trade 00:01:59.479 --> 00:02:02.190 align:start position:0% money from VMO and use that to trade directly<00:01:59.960> for<00:02:00.119> usdc<00:02:00.799> on<00:02:01.039> chain<00:02:01.799> and<00:02:01.960> that's 00:02:02.190 --> 00:02:02.200 align:start position:0% directly for usdc on chain and that's 00:02:02.200 --> 00:02:05.990 align:start position:0% directly for usdc on chain and that's powered<00:02:02.520> by<00:02:02.680> ZK<00:02:03.159> email<00:02:04.159> um<00:02:04.719> as<00:02:04.920> the<00:02:05.159> source<00:02:05.680> of 00:02:05.990 --> 00:02:06.000 align:start position:0% powered by ZK email um as the source of 00:02:06.000 --> 00:02:07.550 align:start position:0% powered by ZK email um as the source of proving<00:02:06.560> that<00:02:06.680> you've<00:02:06.840> sent<00:02:07.079> that<00:02:07.240> VMO 00:02:07.550 --> 00:02:07.560 align:start position:0% proving that you've sent that VMO 00:02:07.560 --> 00:02:09.589 align:start position:0% proving that you've sent that VMO payment<00:02:08.440> and<00:02:08.599> among<00:02:08.920> other<00:02:09.119> things<00:02:09.360> we've 00:02:09.589 --> 00:02:09.599 align:start position:0% payment and among other things we've 00:02:09.599 --> 00:02:12.150 align:start position:0% payment and among other things we've also<00:02:09.840> launched<00:02:10.440> a<00:02:10.679> couple<00:02:11.039> I<00:02:11.200> guess<00:02:11.879> different 00:02:12.150 --> 00:02:12.160 align:start position:0% also launched a couple I guess different 00:02:12.160 --> 00:02:14.350 align:start position:0% also launched a couple I guess different marketplaces<00:02:12.879> for<00:02:13.200> trading<00:02:13.560> tickets<00:02:14.239> and 00:02:14.350 --> 00:02:14.360 align:start position:0% marketplaces for trading tickets and 00:02:14.360 --> 00:02:17.390 align:start position:0% marketplaces for trading tickets and trading<00:02:14.640> domains<00:02:15.000> on<00:02:15.120> the<00:02:15.239> secondary 00:02:17.390 --> 00:02:17.400 align:start position:0% trading domains on the secondary 00:02:17.400 --> 00:02:20.309 align:start position:0% trading domains on the secondary marketpl<00:02:18.400> uh<00:02:18.560> hello<00:02:18.920> my<00:02:19.080> name<00:02:19.319> is<00:02:19.599> Ash<00:02:20.080> I'm 00:02:20.309 --> 00:02:20.319 align:start position:0% marketpl uh hello my name is Ash I'm 00:02:20.319 --> 00:02:24.190 align:start position:0% marketpl uh hello my name is Ash I'm from<00:02:20.879> T<00:02:21.879> we<00:02:22.080> build<00:02:22.760> uh<00:02:22.879> tooling<00:02:23.400> and<00:02:23.640> networks 00:02:24.190 --> 00:02:24.200 align:start position:0% from T we build uh tooling and networks 00:02:24.200 --> 00:02:26.869 align:start position:0% from T we build uh tooling and networks to<00:02:24.519> build<00:02:24.800> and<00:02:25.000> deploy<00:02:25.440> MPC<00:02:26.000> based 00:02:26.869 --> 00:02:26.879 align:start position:0% to build and deploy MPC based 00:02:26.879 --> 00:02:29.509 align:start position:0% to build and deploy MPC based applications<00:02:27.879> um<00:02:28.160> in<00:02:28.319> particular<00:02:28.840> coars 00:02:29.509 --> 00:02:29.519 align:start position:0% applications um in particular coars 00:02:29.519 --> 00:02:31.869 align:start position:0% applications um in particular coars which<00:02:29.640> is<00:02:30.000> what<00:02:30.480> uh<00:02:30.879> cursive<00:02:31.280> are<00:02:31.440> using<00:02:31.760> and 00:02:31.869 --> 00:02:31.879 align:start position:0% which is what uh cursive are using and 00:02:31.879 --> 00:02:33.229 align:start position:0% which is what uh cursive are using and you<00:02:32.000> heard<00:02:32.200> a<00:02:32.280> lot<00:02:32.440> about<00:02:32.680> this<00:02:32.800> week<00:02:33.040> it<00:02:33.120> was 00:02:33.229 --> 00:02:33.239 align:start position:0% you heard a lot about this week it was 00:02:33.239 --> 00:02:34.589 align:start position:0% you heard a lot about this week it was the<00:02:33.360> first<00:02:33.599> week<00:02:33.760> that<00:02:33.879> it's<00:02:34.080> live<00:02:34.280> so<00:02:34.400> we're 00:02:34.589 --> 00:02:34.599 align:start position:0% the first week that it's live so we're 00:02:34.599 --> 00:02:37.070 align:start position:0% the first week that it's live so we're very<00:02:34.920> excited<00:02:35.920> and<00:02:36.120> my<00:02:36.239> role<00:02:36.480> there<00:02:36.680> I<00:02:36.800> care<00:02:36.959> a 00:02:37.070 --> 00:02:37.080 align:start position:0% very excited and my role there I care a 00:02:37.080 --> 00:02:40.750 align:start position:0% very excited and my role there I care a lot<00:02:37.239> about<00:02:37.680> privacy<00:02:38.680> and<00:02:38.920> so<00:02:39.360> I<00:02:39.519> think<00:02:39.760> about 00:02:40.750 --> 00:02:40.760 align:start position:0% lot about privacy and so I think about 00:02:40.760 --> 00:02:43.350 align:start position:0% lot about privacy and so I think about how<00:02:41.760> using<00:02:42.120> these<00:02:42.280> tools<00:02:42.599> in<00:02:42.720> the<00:02:42.800> real<00:02:43.000> world 00:02:43.350 --> 00:02:43.360 align:start position:0% how using these tools in the real world 00:02:43.360 --> 00:02:44.790 align:start position:0% how using these tools in the real world actually<00:02:43.640> affects<00:02:43.959> the<00:02:44.120> lives<00:02:44.319> of<00:02:44.480> the<00:02:44.599> people 00:02:44.790 --> 00:02:44.800 align:start position:0% actually affects the lives of the people 00:02:44.800 --> 00:02:48.190 align:start position:0% actually affects the lives of the people using<00:02:45.560> them<00:02:46.560> cool<00:02:47.000> uh<00:02:47.120> my<00:02:47.239> name<00:02:47.360> is<00:02:47.519> Andrew<00:02:48.080> I 00:02:48.190 --> 00:02:48.200 align:start position:0% using them cool uh my name is Andrew I 00:02:48.200 --> 00:02:51.390 align:start position:0% using them cool uh my name is Andrew I work<00:02:48.400> at<00:02:48.560> cursive<00:02:49.400> and<00:02:49.640> cursive<00:02:50.080> is<00:02:50.400> exploring 00:02:51.390 --> 00:02:51.400 align:start position:0% work at cursive and cursive is exploring 00:02:51.400 --> 00:02:53.350 align:start position:0% work at cursive and cursive is exploring different<00:02:51.760> ways<00:02:52.159> for<00:02:52.560> cryptography<00:02:53.200> to 00:02:53.350 --> 00:02:53.360 align:start position:0% different ways for cryptography to 00:02:53.360 --> 00:02:56.030 align:start position:0% different ways for cryptography to enable<00:02:53.680> new<00:02:53.959> forms<00:02:54.280> of<00:02:54.480> human<00:02:54.720> connection<00:02:55.640> so 00:02:56.030 --> 00:02:56.040 align:start position:0% enable new forms of human connection so 00:02:56.040 --> 00:02:57.750 align:start position:0% enable new forms of human connection so specific<00:02:56.519> C<00:02:56.879> uh<00:02:57.000> certain<00:02:57.280> things<00:02:57.480> that<00:02:57.599> we're 00:02:57.750 --> 00:02:57.760 align:start position:0% specific C uh certain things that we're 00:02:57.760 --> 00:03:00.390 align:start position:0% specific C uh certain things that we're exploring<00:02:58.120> are<00:02:58.440> like<00:02:58.599> multiparty<00:02:59.159> FHA 00:03:00.390 --> 00:03:00.400 align:start position:0% exploring are like multiparty FHA 00:03:00.400 --> 00:03:04.270 align:start position:0% exploring are like multiparty FHA uh<00:03:00.560> looking<00:03:01.120> at<00:03:01.440> karks<00:03:02.360> uh<00:03:02.480> with<00:03:02.720> t<00:03:03.720> and<00:03:03.920> also 00:03:04.270 --> 00:03:04.280 align:start position:0% uh looking at karks uh with t and also 00:03:04.280 --> 00:03:06.229 align:start position:0% uh looking at karks uh with t and also like<00:03:04.440> new<00:03:04.760> MPC<00:03:05.319> Primitives<00:03:05.840> that<00:03:05.920> we're<00:03:06.120> like 00:03:06.229 --> 00:03:06.239 align:start position:0% like new MPC Primitives that we're like 00:03:06.239 --> 00:03:10.149 align:start position:0% like new MPC Primitives that we're like super<00:03:06.519> excited<00:03:06.840> about<00:03:07.040> as<00:03:07.560> well<00:03:08.560> very<00:03:08.840> cool<00:03:09.840> um 00:03:10.149 --> 00:03:10.159 align:start position:0% super excited about as well very cool um 00:03:10.159 --> 00:03:12.509 align:start position:0% super excited about as well very cool um I<00:03:10.239> want<00:03:10.400> to<00:03:10.599> start<00:03:10.920> us<00:03:11.159> off<00:03:11.360> with<00:03:11.599> a<00:03:11.840> high<00:03:12.120> level 00:03:12.509 --> 00:03:12.519 align:start position:0% I want to start us off with a high level 00:03:12.519 --> 00:03:14.830 align:start position:0% I want to start us off with a high level question<00:03:13.519> because<00:03:13.959> you<00:03:14.159> guys<00:03:14.319> are<00:03:14.480> building 00:03:14.830 --> 00:03:14.840 align:start position:0% question because you guys are building 00:03:14.840 --> 00:03:18.589 align:start position:0% question because you guys are building in<00:03:14.959> a<00:03:15.200> paradigm<00:03:15.799> that<00:03:16.200> is<00:03:16.480> very<00:03:17.080> new<00:03:18.080> um<00:03:18.200> and<00:03:18.360> a 00:03:18.589 --> 00:03:18.599 align:start position:0% in a paradigm that is very new um and a 00:03:18.599 --> 00:03:20.550 align:start position:0% in a paradigm that is very new um and a different<00:03:18.920> from<00:03:19.319> most<00:03:19.640> consumer<00:03:20.159> apps<00:03:20.440> that 00:03:20.550 --> 00:03:20.560 align:start position:0% different from most consumer apps that 00:03:20.560 --> 00:03:24.350 align:start position:0% different from most consumer apps that we're<00:03:20.720> used<00:03:21.000> to<00:03:22.000> and<00:03:22.400> I'm<00:03:22.640> wondering<00:03:23.640> um<00:03:24.120> what 00:03:24.350 --> 00:03:24.360 align:start position:0% we're used to and I'm wondering um what 00:03:24.360 --> 00:03:27.070 align:start position:0% we're used to and I'm wondering um what are<00:03:24.640> some<00:03:25.200> application<00:03:25.879> design<00:03:26.360> patterns 00:03:27.070 --> 00:03:27.080 align:start position:0% are some application design patterns 00:03:27.080 --> 00:03:29.949 align:start position:0% are some application design patterns that<00:03:28.000> um<00:03:28.159> are<00:03:28.439> unlocked<00:03:29.400> by<00:03:29.560> the 00:03:29.949 --> 00:03:29.959 align:start position:0% that um are unlocked by the 00:03:29.959 --> 00:03:32.470 align:start position:0% that um are unlocked by the cryptographic<00:03:30.680> Primitives<00:03:31.560> and<00:03:31.760> I<00:03:31.920> want<00:03:32.040> to 00:03:32.470 --> 00:03:32.480 align:start position:0% cryptographic Primitives and I want to 00:03:32.480 --> 00:03:36.229 align:start position:0% cryptographic Primitives and I want to address<00:03:32.959> this<00:03:33.280> sort<00:03:33.519> of<00:03:33.799> like<00:03:34.680> in<00:03:35.280> in<00:03:35.560> like 00:03:36.229 --> 00:03:36.239 align:start position:0% address this sort of like in in like 00:03:36.239 --> 00:03:40.190 align:start position:0% address this sort of like in in like ascending<00:03:36.920> order<00:03:37.439> so<00:03:38.239> in<00:03:38.439> my<00:03:38.680> mind<00:03:39.200> like<00:03:39.400> ZK<00:03:39.959> is 00:03:40.190 --> 00:03:40.200 align:start position:0% ascending order so in my mind like ZK is 00:03:40.200 --> 00:03:44.550 align:start position:0% ascending order so in my mind like ZK is the<00:03:41.200> like<00:03:41.640> most<00:03:42.040> basic<00:03:42.840> primitive<00:03:43.840> followed 00:03:44.550 --> 00:03:44.560 align:start position:0% the like most basic primitive followed 00:03:44.560 --> 00:03:50.030 align:start position:0% the like most basic primitive followed by<00:03:45.560> MPC<00:03:46.360> Co<00:03:46.680> narts<00:03:47.280> followed<00:03:47.760> by<00:03:48.319> MP<00:03:48.720> FH<00:03:49.599> so 00:03:50.030 --> 00:03:50.040 align:start position:0% by MPC Co narts followed by MP FH so 00:03:50.040 --> 00:03:52.589 align:start position:0% by MPC Co narts followed by MP FH so let's<00:03:50.280> go<00:03:50.439> in<00:03:50.720> that<00:03:50.920> order<00:03:51.640> like<00:03:52.239> what<00:03:52.360> are 00:03:52.589 --> 00:03:52.599 align:start position:0% let's go in that order like what are 00:03:52.599 --> 00:03:55.670 align:start position:0% let's go in that order like what are some<00:03:53.200> design<00:03:53.799> patterns<00:03:54.799> um<00:03:55.239> that<00:03:55.360> are 00:03:55.670 --> 00:03:55.680 align:start position:0% some design patterns um that are 00:03:55.680 --> 00:03:59.830 align:start position:0% some design patterns um that are unlocked<00:03:56.200> for<00:03:56.439> you<00:03:57.159> and<00:03:57.599> give<00:03:57.799> us<00:03:58.200> examples<00:03:59.079> um 00:03:59.830 --> 00:03:59.840 align:start position:0% unlocked for you and give us examples um 00:03:59.840 --> 00:04:02.069 align:start position:0% unlocked for you and give us examples um from<00:04:00.120> some<00:04:00.319> of<00:04:00.439> your<00:04:00.680> favorite 00:04:02.069 --> 00:04:02.079 align:start position:0% from some of your favorite 00:04:02.079 --> 00:04:05.949 align:start position:0% from some of your favorite apps<00:04:03.079> let's<00:04:03.280> start<00:04:03.480> with<00:04:03.640> ZK<00:04:04.040> email<00:04:04.760> yeah<00:04:05.519> yeah 00:04:05.949 --> 00:04:05.959 align:start position:0% apps let's start with ZK email yeah yeah 00:04:05.959 --> 00:04:09.429 align:start position:0% apps let's start with ZK email yeah yeah I<00:04:06.400> guess<00:04:07.400> we've<00:04:07.760> seen<00:04:08.120> two<00:04:08.560> main<00:04:08.840> ways<00:04:09.159> people 00:04:09.429 --> 00:04:09.439 align:start position:0% I guess we've seen two main ways people 00:04:09.439 --> 00:04:11.630 align:start position:0% I guess we've seen two main ways people design<00:04:09.840> applications<00:04:10.560> that<00:04:10.720> I<00:04:10.840> think<00:04:11.400> are 00:04:11.630 --> 00:04:11.640 align:start position:0% design applications that I think are 00:04:11.640 --> 00:04:12.869 align:start position:0% design applications that I think are different<00:04:11.959> than<00:04:12.120> everything<00:04:12.360> we've<00:04:12.519> seen 00:04:12.869 --> 00:04:12.879 align:start position:0% different than everything we've seen 00:04:12.879 --> 00:04:16.509 align:start position:0% different than everything we've seen before<00:04:13.879> one<00:04:14.200> is<00:04:15.040> around<00:04:15.400> proof<00:04:15.640> ofed<00:04:16.120> emails 00:04:16.509 --> 00:04:16.519 align:start position:0% before one is around proof ofed emails 00:04:16.519 --> 00:04:17.870 align:start position:0% before one is around proof ofed emails so<00:04:16.680> that's<00:04:16.840> kind<00:04:16.959> of<00:04:17.079> the<00:04:17.239> stuff<00:04:17.440> that<00:04:17.600> Richard 00:04:17.870 --> 00:04:17.880 align:start position:0% so that's kind of the stuff that Richard 00:04:17.880 --> 00:04:20.349 align:start position:0% so that's kind of the stuff that Richard and<00:04:18.000> zbp<00:04:18.560> can<00:04:18.680> contribute<00:04:19.079> to<00:04:19.799> but<00:04:19.959> it's<00:04:20.120> very 00:04:20.349 --> 00:04:20.359 align:start position:0% and zbp can contribute to but it's very 00:04:20.359 --> 00:04:22.510 align:start position:0% and zbp can contribute to but it's very interesting<00:04:20.959> now<00:04:21.400> that<00:04:21.720> it's<00:04:21.919> very<00:04:22.160> easy<00:04:22.360> to 00:04:22.510 --> 00:04:22.520 align:start position:0% interesting now that it's very easy to 00:04:22.520 --> 00:04:25.430 align:start position:0% interesting now that it's very easy to make<00:04:22.720> these<00:04:23.199> proofs<00:04:24.199> um<00:04:24.680> people<00:04:24.880> are<00:04:25.199> kind<00:04:25.320> of 00:04:25.430 --> 00:04:25.440 align:start position:0% make these proofs um people are kind of 00:04:25.440 --> 00:04:27.749 align:start position:0% make these proofs um people are kind of starting<00:04:25.720> to<00:04:25.880> compose<00:04:26.320> them<00:04:26.840> so<00:04:27.040> one<00:04:27.280> example 00:04:27.749 --> 00:04:27.759 align:start position:0% starting to compose them so one example 00:04:27.759 --> 00:04:29.230 align:start position:0% starting to compose them so one example is<00:04:27.919> you<00:04:28.000> can<00:04:28.160> prove<00:04:28.400> you're<00:04:28.560> part<00:04:28.720> of<00:04:28.800> a<00:04:28.880> slack 00:04:29.230 --> 00:04:29.240 align:start position:0% is you can prove you're part of a slack 00:04:29.240 --> 00:04:31.590 align:start position:0% is you can prove you're part of a slack workspace<00:04:30.080> by<00:04:30.560> using<00:04:30.880> any<00:04:31.080> slack 00:04:31.590 --> 00:04:31.600 align:start position:0% workspace by using any slack 00:04:31.600 --> 00:04:33.510 align:start position:0% workspace by using any slack confirmation<00:04:32.080> or<00:04:32.280> invitation<00:04:32.720> email<00:04:33.400> and 00:04:33.510 --> 00:04:33.520 align:start position:0% confirmation or invitation email and 00:04:33.520 --> 00:04:35.390 align:start position:0% confirmation or invitation email and then<00:04:33.759> also<00:04:34.080> prove<00:04:34.360> you<00:04:34.520> for<00:04:34.680> instance<00:04:35.120> took<00:04:35.280> a 00:04:35.390 --> 00:04:35.400 align:start position:0% then also prove you for instance took a 00:04:35.400 --> 00:04:37.670 align:start position:0% then also prove you for instance took a flight<00:04:35.680> on<00:04:35.880> United<00:04:36.600> and<00:04:36.680> you<00:04:36.800> ended<00:04:37.120> up<00:04:37.479> at 00:04:37.670 --> 00:04:37.680 align:start position:0% flight on United and you ended up at 00:04:37.680 --> 00:04:39.670 align:start position:0% flight on United and you ended up at Thailand<00:04:38.479> and<00:04:38.639> now<00:04:38.800> you<00:04:38.919> can<00:04:39.080> automatically 00:04:39.670 --> 00:04:39.680 align:start position:0% Thailand and now you can automatically 00:04:39.680 --> 00:04:41.469 align:start position:0% Thailand and now you can automatically build<00:04:39.880> a<00:04:40.039> system<00:04:40.680> where<00:04:40.919> everybody<00:04:41.280> in<00:04:41.400> your 00:04:41.469 --> 00:04:41.479 align:start position:0% build a system where everybody in your 00:04:41.479 --> 00:04:43.070 align:start position:0% build a system where everybody in your slack<00:04:41.840> worksspace<00:04:42.160> automatically<00:04:42.919> gets 00:04:43.070 --> 00:04:43.080 align:start position:0% slack worksspace automatically gets 00:04:43.080 --> 00:04:45.110 align:start position:0% slack worksspace automatically gets reimbursed<00:04:43.560> for<00:04:43.680> their<00:04:43.800> flight<00:04:44.039> to<00:04:44.160> Thailand 00:04:45.110 --> 00:04:45.120 align:start position:0% reimbursed for their flight to Thailand 00:04:45.120 --> 00:04:46.189 align:start position:0% reimbursed for their flight to Thailand and<00:04:45.240> it's<00:04:45.360> kind<00:04:45.440> of<00:04:45.560> interesting<00:04:46.039> because 00:04:46.189 --> 00:04:46.199 align:start position:0% and it's kind of interesting because 00:04:46.199 --> 00:04:47.270 align:start position:0% and it's kind of interesting because you're<00:04:46.320> not<00:04:46.440> just<00:04:46.560> using<00:04:46.759> one<00:04:46.919> proof<00:04:47.120> you're 00:04:47.270 --> 00:04:47.280 align:start position:0% you're not just using one proof you're 00:04:47.280 --> 00:04:49.110 align:start position:0% you're not just using one proof you're combining<00:04:47.639> all<00:04:47.759> sorts<00:04:47.960> of<00:04:48.120> different<00:04:48.360> proofs 00:04:49.110 --> 00:04:49.120 align:start position:0% combining all sorts of different proofs 00:04:49.120 --> 00:04:50.790 align:start position:0% combining all sorts of different proofs and<00:04:49.280> just<00:04:49.479> because<00:04:49.720> it's<00:04:49.880> very<00:04:50.080> easy<00:04:50.320> to<00:04:50.520> build 00:04:50.790 --> 00:04:50.800 align:start position:0% and just because it's very easy to build 00:04:50.800 --> 00:04:52.830 align:start position:0% and just because it's very easy to build each<00:04:50.960> sort<00:04:51.160> of<00:04:51.280> proof<00:04:51.560> you<00:04:51.639> can<00:04:51.840> build<00:04:52.639> these 00:04:52.830 --> 00:04:52.840 align:start position:0% each sort of proof you can build these 00:04:52.840 --> 00:04:54.350 align:start position:0% each sort of proof you can build these new<00:04:53.039> applications<00:04:53.520> that<00:04:53.759> take<00:04:53.960> multiple 00:04:54.350 --> 00:04:54.360 align:start position:0% new applications that take multiple 00:04:54.360 --> 00:04:56.310 align:start position:0% new applications that take multiple facets<00:04:54.639> of<00:04:54.720> your<00:04:54.840> identity<00:04:55.240> into<00:04:55.479> account<00:04:56.240> and 00:04:56.310 --> 00:04:56.320 align:start position:0% facets of your identity into account and 00:04:56.320 --> 00:04:57.790 align:start position:0% facets of your identity into account and so<00:04:56.479> that's<00:04:56.680> one<00:04:56.840> that<00:04:56.960> I've<00:04:57.160> been<00:04:57.560> really 00:04:57.790 --> 00:04:57.800 align:start position:0% so that's one that I've been really 00:04:57.800 --> 00:05:00.710 align:start position:0% so that's one that I've been really excited<00:04:58.400> by<00:04:59.000> by<00:04:59.160> seeing 00:05:00.710 --> 00:05:00.720 align:start position:0% excited by by seeing 00:05:00.720 --> 00:05:04.189 align:start position:0% excited by by seeing um<00:05:01.720> we've<00:05:01.919> also<00:05:02.440> seen<00:05:03.440> um<00:05:03.680> on<00:05:03.800> the<00:05:03.919> side<00:05:04.080> of 00:05:04.189 --> 00:05:04.199 align:start position:0% um we've also seen um on the side of 00:05:04.199 --> 00:05:07.430 align:start position:0% um we've also seen um on the side of using<00:05:04.440> emails<00:05:04.759> to<00:05:04.880> send<00:05:05.479> transactions<00:05:06.479> people 00:05:07.430 --> 00:05:07.440 align:start position:0% using emails to send transactions people 00:05:07.440 --> 00:05:10.350 align:start position:0% using emails to send transactions people kind<00:05:07.639> of<00:05:07.880> hot<00:05:08.160> swapping<00:05:08.680> almost<00:05:09.120> emails<00:05:10.120> and 00:05:10.350 --> 00:05:10.360 align:start position:0% kind of hot swapping almost emails and 00:05:10.360 --> 00:05:11.990 align:start position:0% kind of hot swapping almost emails and ethereum<00:05:10.800> accounts<00:05:11.120> in<00:05:11.199> their<00:05:11.400> application 00:05:11.990 --> 00:05:12.000 align:start position:0% ethereum accounts in their application 00:05:12.000 --> 00:05:14.510 align:start position:0% ethereum accounts in their application so<00:05:12.199> for<00:05:12.360> instance<00:05:12.960> multi<00:05:13.560> signers<00:05:14.160> can<00:05:14.360> just 00:05:14.510 --> 00:05:14.520 align:start position:0% so for instance multi signers can just 00:05:14.520 --> 00:05:17.029 align:start position:0% so for instance multi signers can just be<00:05:14.880> an<00:05:15.039> email<00:05:15.400> instead<00:05:15.720> of<00:05:16.240> an<00:05:16.639> ethereum 00:05:17.029 --> 00:05:17.039 align:start position:0% be an email instead of an ethereum 00:05:17.039 --> 00:05:18.110 align:start position:0% be an email instead of an ethereum address<00:05:17.320> and<00:05:17.400> it's<00:05:17.560> kind<00:05:17.680> of<00:05:17.800> interesting 00:05:18.110 --> 00:05:18.120 align:start position:0% address and it's kind of interesting 00:05:18.120 --> 00:05:20.070 align:start position:0% address and it's kind of interesting seeing<00:05:18.560> okay<00:05:19.039> once<00:05:19.280> that's<00:05:19.479> really<00:05:19.639> easy<00:05:19.880> to 00:05:20.070 --> 00:05:20.080 align:start position:0% seeing okay once that's really easy to 00:05:20.080 --> 00:05:21.670 align:start position:0% seeing okay once that's really easy to do<00:05:20.639> then<00:05:20.800> people<00:05:21.039> start<00:05:21.240> being<00:05:21.400> able<00:05:21.560> to 00:05:21.670 --> 00:05:21.680 align:start position:0% do then people start being able to 00:05:21.680 --> 00:05:23.110 align:start position:0% do then people start being able to expand<00:05:22.000> their<00:05:22.160> apps<00:05:22.400> to<00:05:22.520> all<00:05:22.639> sorts<00:05:22.840> of<00:05:22.960> new 00:05:23.110 --> 00:05:23.120 align:start position:0% expand their apps to all sorts of new 00:05:23.120 --> 00:05:26.189 align:start position:0% expand their apps to all sorts of new kinds<00:05:23.280> of<00:05:23.400> users<00:05:23.880> so<00:05:24.759> um<00:05:25.199> I<00:05:25.319> think<00:05:25.800> those<00:05:26.000> are 00:05:26.189 --> 00:05:26.199 align:start position:0% kinds of users so um I think those are 00:05:26.199 --> 00:05:28.230 align:start position:0% kinds of users so um I think those are the<00:05:26.319> two<00:05:26.600> and<00:05:26.880> I<00:05:26.960> think<00:05:27.080> we've<00:05:27.280> seen<00:05:27.919> over<00:05:28.120> the 00:05:28.230 --> 00:05:28.240 align:start position:0% the two and I think we've seen over the 00:05:28.240 --> 00:05:30.830 align:start position:0% the two and I think we've seen over the last<00:05:28.440> few<00:05:28.639> years<00:05:29.039> the<00:05:29.199> design<00:05:29.960> evolve<00:05:30.360> more 00:05:30.830 --> 00:05:30.840 align:start position:0% last few years the design evolve more 00:05:30.840 --> 00:05:33.790 align:start position:0% last few years the design evolve more into<00:05:31.840> uh<00:05:32.440> this<00:05:32.639> being<00:05:32.919> almost<00:05:33.160> TurnKey<00:05:33.639> for 00:05:33.790 --> 00:05:33.800 align:start position:0% into uh this being almost TurnKey for 00:05:33.800 --> 00:05:35.590 align:start position:0% into uh this being almost TurnKey for developers<00:05:34.280> instead<00:05:34.520> of<00:05:34.720> like<00:05:34.840> ZK<00:05:35.160> PP<00:05:35.520> which 00:05:35.590 --> 00:05:35.600 align:start position:0% developers instead of like ZK PP which 00:05:35.600 --> 00:05:36.909 align:start position:0% developers instead of like ZK PP which had<00:05:35.720> to<00:05:35.800> slog<00:05:36.120> through<00:05:36.280> like<00:05:36.400> months<00:05:36.639> of<00:05:36.759> The 00:05:36.909 --> 00:05:36.919 align:start position:0% had to slog through like months of The 00:05:36.919 --> 00:05:39.110 align:start position:0% had to slog through like months of The Primitives<00:05:37.400> of<00:05:37.840> getting<00:05:38.080> it<00:05:38.199> up<00:05:38.360> to<00:05:38.520> speed<00:05:38.919> but 00:05:39.110 --> 00:05:39.120 align:start position:0% Primitives of getting it up to speed but 00:05:39.120 --> 00:05:40.830 align:start position:0% Primitives of getting it up to speed but we<00:05:39.240> learned<00:05:39.479> a<00:05:39.560> ton<00:05:39.800> from<00:05:39.960> that<00:05:40.560> yeah<00:05:40.680> I'm 00:05:40.830 --> 00:05:40.840 align:start position:0% we learned a ton from that yeah I'm 00:05:40.840 --> 00:05:43.590 align:start position:0% we learned a ton from that yeah I'm curious<00:05:41.639> what<00:05:41.759> your<00:05:41.919> takes<00:05:42.160> are<00:05:42.440> though<00:05:43.400> yeah 00:05:43.590 --> 00:05:43.600 align:start position:0% curious what your takes are though yeah 00:05:43.600 --> 00:05:45.749 align:start position:0% curious what your takes are though yeah I<00:05:43.720> think<00:05:44.039> for<00:05:44.240> us<00:05:44.440> at<00:05:44.639> ZK<00:05:44.960> PDP<00:05:45.479> we're 00:05:45.749 --> 00:05:45.759 align:start position:0% I think for us at ZK PDP we're 00:05:45.759 --> 00:05:48.110 align:start position:0% I think for us at ZK PDP we're particularly<00:05:46.400> focused<00:05:46.840> and<00:05:47.039> excited<00:05:47.440> about 00:05:48.110 --> 00:05:48.120 align:start position:0% particularly focused and excited about 00:05:48.120 --> 00:05:51.629 align:start position:0% particularly focused and excited about the<00:05:48.560> idea<00:05:49.240> of<00:05:49.440> bringing<00:05:50.080> web2<00:05:50.600> data<00:05:51.080> and<00:05:51.240> using 00:05:51.629 --> 00:05:51.639 align:start position:0% the idea of bringing web2 data and using 00:05:51.639 --> 00:05:54.550 align:start position:0% the idea of bringing web2 data and using that<00:05:52.080> like<00:05:52.280> all<00:05:52.479> across<00:05:53.479> um<00:05:53.960> blockchains 00:05:54.550 --> 00:05:54.560 align:start position:0% that like all across um blockchains 00:05:54.560 --> 00:05:56.749 align:start position:0% that like all across um blockchains especially<00:05:55.440> I<00:05:55.520> think<00:05:55.840> if<00:05:55.919> you<00:05:56.039> think<00:05:56.280> about 00:05:56.749 --> 00:05:56.759 align:start position:0% especially I think if you think about 00:05:56.759 --> 00:06:00.590 align:start position:0% especially I think if you think about like<00:05:57.759> web<00:05:58.000> 2<00:05:58.840> um<00:05:59.400> all<00:05:59.720> the<00:05:59.840> data<00:06:00.120> currently 00:06:00.590 --> 00:06:00.600 align:start position:0% like web 2 um all the data currently 00:06:00.600 --> 00:06:02.469 align:start position:0% like web 2 um all the data currently exists<00:06:01.000> in<00:06:01.160> these<00:06:01.360> like<00:06:01.520> centralized<00:06:02.120> data 00:06:02.469 --> 00:06:02.479 align:start position:0% exists in these like centralized data 00:06:02.479 --> 00:06:05.629 align:start position:0% exists in these like centralized data silos<00:06:03.479> like<00:06:03.880> it's<00:06:04.639> you<00:06:04.840> you<00:06:05.000> basically<00:06:05.400> can't 00:06:05.629 --> 00:06:05.639 align:start position:0% silos like it's you you basically can't 00:06:05.639 --> 00:06:07.710 align:start position:0% silos like it's you you basically can't export<00:06:06.039> them<00:06:06.199> to<00:06:06.360> use<00:06:06.639> anywhere<00:06:06.960> else<00:06:07.599> think 00:06:07.710 --> 00:06:07.720 align:start position:0% export them to use anywhere else think 00:06:07.720 --> 00:06:09.790 align:start position:0% export them to use anywhere else think of<00:06:07.960> like<00:06:08.440> your<00:06:08.680> Facebook<00:06:09.080> follow<00:06:09.479> or<00:06:09.639> your 00:06:09.790 --> 00:06:09.800 align:start position:0% of like your Facebook follow or your 00:06:09.800 --> 00:06:11.270 align:start position:0% of like your Facebook follow or your Facebook<00:06:10.160> friends<00:06:10.479> you<00:06:10.599> can't<00:06:10.800> just<00:06:11.000> take 00:06:11.270 --> 00:06:11.280 align:start position:0% Facebook friends you can't just take 00:06:11.280 --> 00:06:13.870 align:start position:0% Facebook friends you can't just take that<00:06:11.800> and<00:06:11.960> use<00:06:12.199> it<00:06:12.919> um<00:06:13.160> on<00:06:13.319> Twitter<00:06:13.680> for 00:06:13.870 --> 00:06:13.880 align:start position:0% that and use it um on Twitter for 00:06:13.880 --> 00:06:17.070 align:start position:0% that and use it um on Twitter for example<00:06:14.880> right<00:06:15.319> and<00:06:16.039> some<00:06:16.199> of<00:06:16.360> these<00:06:16.560> like<00:06:16.680> ZK 00:06:17.070 --> 00:06:17.080 align:start position:0% example right and some of these like ZK 00:06:17.080 --> 00:06:19.390 align:start position:0% example right and some of these like ZK Primitives<00:06:17.720> allow<00:06:18.000> you<00:06:18.400> and<00:06:18.560> I<00:06:18.680> guess<00:06:18.880> also 00:06:19.390 --> 00:06:19.400 align:start position:0% Primitives allow you and I guess also 00:06:19.400 --> 00:06:22.670 align:start position:0% Primitives allow you and I guess also like<00:06:19.680> NPC<00:06:20.360> with<00:06:20.520> like<00:06:20.639> TLS<00:06:21.039> notary<00:06:22.000> um<00:06:22.440> allow 00:06:22.670 --> 00:06:22.680 align:start position:0% like NPC with like TLS notary um allow 00:06:22.680 --> 00:06:25.830 align:start position:0% like NPC with like TLS notary um allow you<00:06:22.800> to<00:06:23.319> kind<00:06:23.400> of<00:06:23.599> permissionless<00:06:24.479> export<00:06:25.479> uh 00:06:25.830 --> 00:06:25.840 align:start position:0% you to kind of permissionless export uh 00:06:25.840 --> 00:06:28.510 align:start position:0% you to kind of permissionless export uh these<00:06:26.080> web2<00:06:26.880> like<00:06:27.560> data<00:06:27.919> from<00:06:28.120> these<00:06:28.360> like 00:06:28.510 --> 00:06:28.520 align:start position:0% these web2 like data from these like 00:06:28.520 --> 00:06:31.350 align:start position:0% these web2 like data from these like silos<00:06:29.080> and<00:06:29.199> use<00:06:29.360> that<00:06:29.639> anywhere<00:06:30.319> uh<00:06:30.440> you<00:06:30.599> want 00:06:31.350 --> 00:06:31.360 align:start position:0% silos and use that anywhere uh you want 00:06:31.360 --> 00:06:32.950 align:start position:0% silos and use that anywhere uh you want and<00:06:31.520> we're<00:06:31.759> particularly<00:06:32.319> excited<00:06:32.639> about 00:06:32.950 --> 00:06:32.960 align:start position:0% and we're particularly excited about 00:06:32.960 --> 00:06:35.790 align:start position:0% and we're particularly excited about like<00:06:33.080> putting<00:06:33.400> these<00:06:33.560> on<00:06:33.800> chain<00:06:34.759> uh<00:06:35.039> because 00:06:35.790 --> 00:06:35.800 align:start position:0% like putting these on chain uh because 00:06:35.800 --> 00:06:38.870 align:start position:0% like putting these on chain uh because of<00:06:36.000> this<00:06:36.240> like<00:06:36.840> Global<00:06:37.440> like<00:06:38.440> incredibly 00:06:38.870 --> 00:06:38.880 align:start position:0% of this like Global like incredibly 00:06:38.880 --> 00:06:40.749 align:start position:0% of this like Global like incredibly neutral<00:06:39.240> settlement<00:06:39.680> layer<00:06:40.080> that<00:06:40.160> you<00:06:40.280> can<00:06:40.400> do 00:06:40.749 --> 00:06:40.759 align:start position:0% neutral settlement layer that you can do 00:06:40.759 --> 00:06:42.629 align:start position:0% neutral settlement layer that you can do like<00:06:41.000> really<00:06:41.240> cool<00:06:41.560> stuff<00:06:41.880> and<00:06:42.080> composable 00:06:42.629 --> 00:06:42.639 align:start position:0% like really cool stuff and composable 00:06:42.639 --> 00:06:46.309 align:start position:0% like really cool stuff and composable stuff 00:06:46.309 --> 00:06:46.319 align:start position:0% 00:06:46.319 --> 00:06:48.990 align:start position:0% with<00:06:47.319> who<00:06:47.560> go<00:06:47.720> who<00:06:47.840> goes<00:06:48.039> with<00:06:48.199> coars<00:06:48.759> you<00:06:48.880> are 00:06:48.990 --> 00:06:49.000 align:start position:0% with who go who goes with coars you are 00:06:49.000 --> 00:06:52.670 align:start position:0% with who go who goes with coars you are using<00:06:49.360> them<00:06:49.560> I<00:06:49.680> can<00:06:49.800> go<00:06:49.960> General<00:06:50.360> Pur<00:06:51.319> see<00:06:52.319> well 00:06:52.670 --> 00:06:52.680 align:start position:0% using them I can go General Pur see well 00:06:52.680 --> 00:06:55.909 align:start position:0% using them I can go General Pur see well you<00:06:52.800> built<00:06:53.039> them<00:06:54.039> I<00:06:54.120> think<00:06:54.560> I<00:06:54.639> mean<00:06:54.919> with<00:06:55.319> coars 00:06:55.909 --> 00:06:55.919 align:start position:0% you built them I think I mean with coars 00:06:55.919 --> 00:06:59.070 align:start position:0% you built them I think I mean with coars and<00:06:56.319> NPC<00:06:57.319> for<00:06:57.560> coars<00:06:58.160> I<00:06:58.280> think<00:06:58.440> one<00:06:58.560> of<00:06:58.759> the 00:06:59.070 --> 00:06:59.080 align:start position:0% and NPC for coars I think one of the 00:06:59.080 --> 00:07:01.230 align:start position:0% and NPC for coars I think one of the nicest<00:06:59.759> examples<00:07:00.199> is<00:07:00.560> actually<00:07:00.800> what<00:07:00.919> you<00:07:01.039> are 00:07:01.230 --> 00:07:01.240 align:start position:0% nicest examples is actually what you are 00:07:01.240 --> 00:07:03.309 align:start position:0% nicest examples is actually what you are doing<00:07:01.599> and<00:07:01.759> this<00:07:01.919> is<00:07:02.240> essentially<00:07:02.680> doing 00:07:03.309 --> 00:07:03.319 align:start position:0% doing and this is essentially doing 00:07:03.319 --> 00:07:05.749 align:start position:0% doing and this is essentially doing private<00:07:03.680> proof<00:07:04.080> delegation<00:07:05.080> so<00:07:05.280> with<00:07:05.440> zero 00:07:05.749 --> 00:07:05.759 align:start position:0% private proof delegation so with zero 00:07:05.759 --> 00:07:07.430 align:start position:0% private proof delegation so with zero knowledge<00:07:06.080> proofs<00:07:06.479> if<00:07:06.599> you<00:07:06.720> want<00:07:06.879> to<00:07:07.080> generate 00:07:07.430 --> 00:07:07.440 align:start position:0% knowledge proofs if you want to generate 00:07:07.440 --> 00:07:10.469 align:start position:0% knowledge proofs if you want to generate a<00:07:07.599> proof<00:07:07.960> where<00:07:08.840> um<00:07:09.400> like<00:07:09.639> the<00:07:09.800> witness<00:07:10.199> gets 00:07:10.469 --> 00:07:10.479 align:start position:0% a proof where um like the witness gets 00:07:10.479 --> 00:07:11.950 align:start position:0% a proof where um like the witness gets particularly<00:07:11.000> big<00:07:11.280> and<00:07:11.360> you're<00:07:11.479> doing<00:07:11.759> it 00:07:11.950 --> 00:07:11.960 align:start position:0% particularly big and you're doing it 00:07:11.960 --> 00:07:14.710 align:start position:0% particularly big and you're doing it client<00:07:12.479> side<00:07:12.759> and<00:07:13.199> maybe<00:07:13.720> it's<00:07:14.039> your<00:07:14.240> phone<00:07:14.520> is 00:07:14.710 --> 00:07:14.720 align:start position:0% client side and maybe it's your phone is 00:07:14.720 --> 00:07:16.990 align:start position:0% client side and maybe it's your phone is not<00:07:15.280> uh<00:07:15.400> powerful<00:07:15.919> enough<00:07:16.199> or<00:07:16.360> you<00:07:16.440> don't<00:07:16.680> have 00:07:16.990 --> 00:07:17.000 align:start position:0% not uh powerful enough or you don't have 00:07:17.000 --> 00:07:18.990 align:start position:0% not uh powerful enough or you don't have enough<00:07:17.360> time<00:07:17.560> to<00:07:17.680> do<00:07:17.800> it<00:07:17.919> on<00:07:18.120> your<00:07:18.240> phone<00:07:18.879> you 00:07:18.990 --> 00:07:19.000 align:start position:0% enough time to do it on your phone you 00:07:19.000 --> 00:07:21.070 align:start position:0% enough time to do it on your phone you might<00:07:19.160> want<00:07:19.280> to<00:07:19.400> Outsource<00:07:19.919> it<00:07:20.680> and<00:07:20.759> so<00:07:20.960> you 00:07:21.070 --> 00:07:21.080 align:start position:0% might want to Outsource it and so you 00:07:21.080 --> 00:07:22.790 align:start position:0% might want to Outsource it and so you see<00:07:21.319> all<00:07:21.479> these<00:07:21.639> proof<00:07:21.879> markets<00:07:22.280> popping<00:07:22.599> up 00:07:22.790 --> 00:07:22.800 align:start position:0% see all these proof markets popping up 00:07:22.800 --> 00:07:24.510 align:start position:0% see all these proof markets popping up that<00:07:22.960> offer<00:07:23.240> services<00:07:23.840> that<00:07:24.039> you<00:07:24.160> know<00:07:24.360> can 00:07:24.510 --> 00:07:24.520 align:start position:0% that offer services that you know can 00:07:24.520 --> 00:07:26.950 align:start position:0% that offer services that you know can generate<00:07:24.840> your<00:07:25.039> proofs<00:07:25.400> for<00:07:25.639> you<00:07:26.560> but<00:07:26.720> if<00:07:26.800> you 00:07:26.950 --> 00:07:26.960 align:start position:0% generate your proofs for you but if you 00:07:26.960 --> 00:07:28.869 align:start position:0% generate your proofs for you but if you have<00:07:27.120> any<00:07:27.400> notion<00:07:27.720> of<00:07:27.919> privacy<00:07:28.360> at<00:07:28.479> all<00:07:28.639> or<00:07:28.759> if 00:07:28.869 --> 00:07:28.879 align:start position:0% have any notion of privacy at all or if 00:07:28.879 --> 00:07:30.629 align:start position:0% have any notion of privacy at all or if you<00:07:29.000> care<00:07:29.240> about<00:07:29.520> about<00:07:29.759> the<00:07:29.960> witness<00:07:30.319> data 00:07:30.629 --> 00:07:30.639 align:start position:0% you care about about the witness data 00:07:30.639 --> 00:07:32.110 align:start position:0% you care about about the witness data and<00:07:30.759> not<00:07:30.919> leaking<00:07:31.280> this<00:07:31.400> in<00:07:31.560> the<00:07:31.680> clear<00:07:31.919> to 00:07:32.110 --> 00:07:32.120 align:start position:0% and not leaking this in the clear to 00:07:32.120 --> 00:07:33.790 align:start position:0% and not leaking this in the clear to everybody<00:07:32.960> then<00:07:33.080> you<00:07:33.199> might<00:07:33.360> want<00:07:33.479> to<00:07:33.560> do<00:07:33.720> this 00:07:33.790 --> 00:07:33.800 align:start position:0% everybody then you might want to do this 00:07:33.800 --> 00:07:35.909 align:start position:0% everybody then you might want to do this in<00:07:33.919> a<00:07:34.039> privacy<00:07:34.440> preserving<00:07:34.919> way<00:07:35.520> and<00:07:35.639> I<00:07:35.720> think 00:07:35.909 --> 00:07:35.919 align:start position:0% in a privacy preserving way and I think 00:07:35.919 --> 00:07:38.990 align:start position:0% in a privacy preserving way and I think this<00:07:36.000> is<00:07:36.160> where<00:07:36.400> coars<00:07:37.199> enter<00:07:37.720> their<00:07:37.919> story<00:07:38.360> so 00:07:38.990 --> 00:07:39.000 align:start position:0% this is where coars enter their story so 00:07:39.000 --> 00:07:40.950 align:start position:0% this is where coars enter their story so doing<00:07:39.639> yeah<00:07:39.960> private<00:07:40.319> Pro<00:07:40.560> like<00:07:40.720> proof 00:07:40.950 --> 00:07:40.960 align:start position:0% doing yeah private Pro like proof 00:07:40.960 --> 00:07:43.189 align:start position:0% doing yeah private Pro like proof delegation<00:07:41.599> but<00:07:41.759> maintaining<00:07:42.280> privacy<00:07:42.879> in<00:07:43.039> an 00:07:43.189 --> 00:07:43.199 align:start position:0% delegation but maintaining privacy in an 00:07:43.199 --> 00:07:47.629 align:start position:0% delegation but maintaining privacy in an mpca<00:07:44.199> I<00:07:44.319> think<00:07:44.479> is<00:07:44.680> the<00:07:45.199> one<00:07:45.639> real<00:07:46.319> sort<00:07:46.639> of 00:07:47.629 --> 00:07:47.639 align:start position:0% mpca I think is the one real sort of 00:07:47.639 --> 00:07:51.309 align:start position:0% mpca I think is the one real sort of awesome<00:07:48.039> use<00:07:48.400> case<00:07:48.759> that<00:07:49.479> uh<00:07:50.360> coars<00:07:51.000> offer 00:07:51.309 --> 00:07:51.319 align:start position:0% awesome use case that uh coars offer 00:07:51.319 --> 00:07:53.029 align:start position:0% awesome use case that uh coars offer that<00:07:51.440> wouldn't<00:07:51.680> be<00:07:52.000> possible<00:07:52.360> otherwise<00:07:52.840> so 00:07:53.029 --> 00:07:53.039 align:start position:0% that wouldn't be possible otherwise so 00:07:53.039 --> 00:07:54.950 align:start position:0% that wouldn't be possible otherwise so like<00:07:53.159> in<00:07:53.280> New<00:07:53.599> is<00:07:53.759> now<00:07:54.159> you<00:07:54.280> don't<00:07:54.479> do<00:07:54.720> proof 00:07:54.950 --> 00:07:54.960 align:start position:0% like in New is now you don't do proof 00:07:54.960 --> 00:07:56.830 align:start position:0% like in New is now you don't do proof generation<00:07:55.319> on<00:07:55.479> the<00:07:55.879> phone<00:07:56.159> you<00:07:56.319> Outsource<00:07:56.759> it 00:07:56.830 --> 00:07:56.840 align:start position:0% generation on the phone you Outsource it 00:07:56.840 --> 00:08:00.149 align:start position:0% generation on the phone you Outsource it to<00:07:56.960> the<00:07:57.360> network<00:07:58.360> and<00:07:58.479> then<00:07:58.599> I<00:07:58.720> think<00:07:58.879> for 00:08:00.149 --> 00:08:00.159 align:start position:0% to the network and then I think for 00:08:00.159 --> 00:08:04.510 align:start position:0% to the network and then I think for general<00:08:00.599> purpose<00:08:01.280> MPC<00:08:02.479> um<00:08:03.479> I<00:08:03.599> think<00:08:03.919> the<00:08:04.080> thing 00:08:04.510 --> 00:08:04.520 align:start position:0% general purpose MPC um I think the thing 00:08:04.520 --> 00:08:06.830 align:start position:0% general purpose MPC um I think the thing for<00:08:04.680> me<00:08:04.879> this<00:08:05.000> is<00:08:05.199> the<00:08:05.560> most<00:08:05.960> exciting<00:08:06.479> part 00:08:06.830 --> 00:08:06.840 align:start position:0% for me this is the most exciting part 00:08:06.840 --> 00:08:09.149 align:start position:0% for me this is the most exciting part because<00:08:07.479> there<00:08:07.800> you<00:08:08.000> start<00:08:08.280> to<00:08:08.479> now<00:08:08.720> be<00:08:08.879> able 00:08:09.149 --> 00:08:09.159 align:start position:0% because there you start to now be able 00:08:09.159 --> 00:08:12.309 align:start position:0% because there you start to now be able to<00:08:09.680> collaborate<00:08:10.639> on<00:08:10.960> private<00:08:11.400> data<00:08:11.879> across 00:08:12.309 --> 00:08:12.319 align:start position:0% to collaborate on private data across 00:08:12.319 --> 00:08:15.070 align:start position:0% to collaborate on private data across multiple<00:08:12.840> users<00:08:13.759> so<00:08:13.960> I<00:08:14.039> think<00:08:14.159> ZK<00:08:14.599> is<00:08:14.759> great<00:08:14.960> in 00:08:15.070 --> 00:08:15.080 align:start position:0% multiple users so I think ZK is great in 00:08:15.080 --> 00:08:17.270 align:start position:0% multiple users so I think ZK is great in the<00:08:15.199> sense<00:08:15.479> that<00:08:15.599> it<00:08:15.720> gives<00:08:15.919> you<00:08:16.199> like<00:08:16.440> this<00:08:17.120> um 00:08:17.270 --> 00:08:17.280 align:start position:0% the sense that it gives you like this um 00:08:17.280 --> 00:08:19.710 align:start position:0% the sense that it gives you like this um sort<00:08:17.479> of<00:08:17.639> control<00:08:18.000> over<00:08:18.199> your<00:08:18.440> data<00:08:19.319> but<00:08:19.479> in<00:08:19.599> a 00:08:19.710 --> 00:08:19.720 align:start position:0% sort of control over your data but in a 00:08:19.720 --> 00:08:21.309 align:start position:0% sort of control over your data but in a way<00:08:19.879> it<00:08:20.000> restricts<00:08:20.440> you<00:08:20.800> because<00:08:21.000> it's<00:08:21.120> like 00:08:21.309 --> 00:08:21.319 align:start position:0% way it restricts you because it's like 00:08:21.319 --> 00:08:23.350 align:start position:0% way it restricts you because it's like okay<00:08:21.479> I<00:08:21.599> have<00:08:21.720> control<00:08:22.039> over<00:08:22.240> my<00:08:22.400> data<00:08:22.720> but<00:08:22.879> now 00:08:23.350 --> 00:08:23.360 align:start position:0% okay I have control over my data but now 00:08:23.360 --> 00:08:25.350 align:start position:0% okay I have control over my data but now it's<00:08:23.599> stuck<00:08:24.080> and<00:08:24.440> uh<00:08:24.560> I<00:08:24.680> can't<00:08:24.840> share<00:08:25.080> it<00:08:25.240> with 00:08:25.350 --> 00:08:25.360 align:start position:0% it's stuck and uh I can't share it with 00:08:25.360 --> 00:08:26.909 align:start position:0% it's stuck and uh I can't share it with you<00:08:25.520> and<00:08:25.840> sometimes<00:08:26.039> I<00:08:26.199> want<00:08:26.440> this<00:08:26.599> sort<00:08:26.759> of 00:08:26.909 --> 00:08:26.919 align:start position:0% you and sometimes I want this sort of 00:08:26.919 --> 00:08:28.510 align:start position:0% you and sometimes I want this sort of flexibility<00:08:27.639> I<00:08:27.720> don't<00:08:27.879> want<00:08:28.000> this<00:08:28.159> all<00:08:28.319> or 00:08:28.510 --> 00:08:28.520 align:start position:0% flexibility I don't want this all or 00:08:28.520 --> 00:08:30.589 align:start position:0% flexibility I don't want this all or nothing<00:08:29.520> and<00:08:29.639> so<00:08:29.960> if<00:08:30.080> I<00:08:30.240> have<00:08:30.440> this 00:08:30.589 --> 00:08:30.599 align:start position:0% nothing and so if I have this 00:08:30.599 --> 00:08:32.230 align:start position:0% nothing and so if I have this flexibility<00:08:31.240> to<00:08:31.360> say<00:08:31.599> okay<00:08:31.759> I<00:08:31.840> can<00:08:31.919> share<00:08:32.120> it 00:08:32.230 --> 00:08:32.240 align:start position:0% flexibility to say okay I can share it 00:08:32.240 --> 00:08:34.190 align:start position:0% flexibility to say okay I can share it with<00:08:32.360> you<00:08:32.519> and<00:08:32.640> you<00:08:32.800> and<00:08:32.959> you<00:08:33.560> or<00:08:33.719> I<00:08:33.800> can<00:08:33.919> share 00:08:34.190 --> 00:08:34.200 align:start position:0% with you and you and you or I can share 00:08:34.200 --> 00:08:35.589 align:start position:0% with you and you and you or I can share something<00:08:34.640> about<00:08:34.800> it<00:08:34.959> with<00:08:35.080> you<00:08:35.200> and<00:08:35.320> you<00:08:35.440> and 00:08:35.589 --> 00:08:35.599 align:start position:0% something about it with you and you and 00:08:35.599 --> 00:08:37.870 align:start position:0% something about it with you and you and you<00:08:35.719> and<00:08:35.839> we<00:08:35.959> can<00:08:36.120> compute<00:08:36.479> over<00:08:36.640> it<00:08:36.959> together 00:08:37.870 --> 00:08:37.880 align:start position:0% you and we can compute over it together 00:08:37.880 --> 00:08:40.029 align:start position:0% you and we can compute over it together um<00:08:38.159> then<00:08:38.360> this<00:08:38.479> is<00:08:38.719> great<00:08:39.039> so<00:08:39.279> for<00:08:39.440> me<00:08:39.680> this<00:08:39.800> is 00:08:40.029 --> 00:08:40.039 align:start position:0% um then this is great so for me this is 00:08:40.039 --> 00:08:44.070 align:start position:0% um then this is great so for me this is like<00:08:40.919> the<00:08:41.599> real<00:08:42.560> kind<00:08:42.680> of<00:08:43.159> new<00:08:43.519> thing<00:08:43.839> that's 00:08:44.070 --> 00:08:44.080 align:start position:0% like the real kind of new thing that's 00:08:44.080 --> 00:08:46.710 align:start position:0% like the real kind of new thing that's opened<00:08:44.440> up<00:08:44.720> by<00:08:44.920> using<00:08:45.240> APC<00:08:45.800> in<00:08:45.920> a<00:08:46.160> in<00:08:46.240> a<00:08:46.360> ZK 00:08:46.710 --> 00:08:46.720 align:start position:0% opened up by using APC in a in a ZK 00:08:46.720 --> 00:08:49.190 align:start position:0% opened up by using APC in a in a ZK world<00:08:47.080> let's<00:08:47.320> see<00:08:48.320> yeah<00:08:48.440> so<00:08:48.640> I<00:08:48.760> personally 00:08:49.190 --> 00:08:49.200 align:start position:0% world let's see yeah so I personally 00:08:49.200 --> 00:08:52.710 align:start position:0% world let's see yeah so I personally feel<00:08:49.480> like<00:08:49.760> ZK<00:08:50.279> by<00:08:50.440> itself<00:08:50.800> is<00:08:51.320> quite<00:08:51.560> lame<00:08:52.080> for 00:08:52.710 --> 00:08:52.720 align:start position:0% feel like ZK by itself is quite lame for 00:08:52.720 --> 00:08:54.910 align:start position:0% feel like ZK by itself is quite lame for the<00:08:52.880> use<00:08:53.200> cases<00:08:53.600> that<00:08:53.760> we're<00:08:54.040> thinking<00:08:54.360> about 00:08:54.910 --> 00:08:54.920 align:start position:0% the use cases that we're thinking about 00:08:54.920 --> 00:08:57.150 align:start position:0% the use cases that we're thinking about which<00:08:55.080> is<00:08:55.519> social<00:08:55.959> applications<00:08:56.800> like<00:08:56.920> I<00:08:57.000> feel 00:08:57.150 --> 00:08:57.160 align:start position:0% which is social applications like I feel 00:08:57.160 --> 00:08:58.310 align:start position:0% which is social applications like I feel like<00:08:57.279> social<00:08:57.600> is<00:08:57.760> inherently<00:08:58.200> like 00:08:58.310 --> 00:08:58.320 align:start position:0% like social is inherently like 00:08:58.320 --> 00:09:00.310 align:start position:0% like social is inherently like multiplayer<00:08:58.959> you<00:08:59.040> want<00:08:59.160> to<00:08:59.600> get<00:08:59.839> like<00:09:00.040> a<00:09:00.160> bunch 00:09:00.310 --> 00:09:00.320 align:start position:0% multiplayer you want to get like a bunch 00:09:00.320 --> 00:09:02.230 align:start position:0% multiplayer you want to get like a bunch of<00:09:00.440> people<00:09:00.720> involved<00:09:01.360> and<00:09:01.760> the<00:09:01.880> coolest 00:09:02.230 --> 00:09:02.240 align:start position:0% of people involved and the coolest 00:09:02.240 --> 00:09:03.790 align:start position:0% of people involved and the coolest applications<00:09:02.760> there<00:09:03.000> involve<00:09:03.440> multiple 00:09:03.790 --> 00:09:03.800 align:start position:0% applications there involve multiple 00:09:03.800 --> 00:09:06.150 align:start position:0% applications there involve multiple people's<00:09:04.240> private<00:09:04.720> information<00:09:05.720> and<00:09:05.920> for 00:09:06.150 --> 00:09:06.160 align:start position:0% people's private information and for 00:09:06.160 --> 00:09:08.829 align:start position:0% people's private information and for that<00:09:06.320> MPC<00:09:06.800> is<00:09:06.880> a<00:09:07.000> perfect<00:09:07.600> fit<00:09:08.160> so<00:09:08.360> I<00:09:08.440> would<00:09:08.640> say 00:09:08.829 --> 00:09:08.839 align:start position:0% that MPC is a perfect fit so I would say 00:09:08.839 --> 00:09:11.310 align:start position:0% that MPC is a perfect fit so I would say for<00:09:09.079> coars<00:09:09.680> the<00:09:09.800> thing<00:09:09.959> that's<00:09:10.160> more<00:09:10.360> exciting 00:09:11.310 --> 00:09:11.320 align:start position:0% for coars the thing that's more exciting 00:09:11.320 --> 00:09:13.230 align:start position:0% for coars the thing that's more exciting um<00:09:11.440> to<00:09:11.600> me<00:09:11.839> personally<00:09:12.399> is<00:09:12.600> the<00:09:12.760> idea<00:09:13.040> that<00:09:13.160> you 00:09:13.230 --> 00:09:13.240 align:start position:0% um to me personally is the idea that you 00:09:13.240 --> 00:09:15.470 align:start position:0% um to me personally is the idea that you can<00:09:13.480> actually<00:09:14.000> generate<00:09:14.399> proofs<00:09:14.839> about<00:09:15.320> a 00:09:15.470 --> 00:09:15.480 align:start position:0% can actually generate proofs about a 00:09:15.480 --> 00:09:17.110 align:start position:0% can actually generate proofs about a group's<00:09:15.800> data<00:09:16.200> so<00:09:16.360> it's<00:09:16.560> like<00:09:16.720> the<00:09:16.800> other<00:09:17.000> side 00:09:17.110 --> 00:09:17.120 align:start position:0% group's data so it's like the other side 00:09:17.120 --> 00:09:19.069 align:start position:0% group's data so it's like the other side of<00:09:17.200> the<00:09:17.320> coin<00:09:18.000> and<00:09:18.120> I<00:09:18.240> think<00:09:18.399> in<00:09:18.519> general<00:09:18.920> like 00:09:19.069 --> 00:09:19.079 align:start position:0% of the coin and I think in general like 00:09:19.079 --> 00:09:22.990 align:start position:0% of the coin and I think in general like MPC<00:09:19.640> FHA<00:09:20.200> all<00:09:20.320> of<00:09:20.480> these<00:09:20.839> things<00:09:21.839> uh<00:09:22.640> cool 00:09:22.990 --> 00:09:23.000 align:start position:0% MPC FHA all of these things uh cool 00:09:23.000 --> 00:09:25.630 align:start position:0% MPC FHA all of these things uh cool applications<00:09:23.519> or<00:09:23.760> design<00:09:24.120> patterns<00:09:24.560> or<00:09:24.880> like 00:09:25.630 --> 00:09:25.640 align:start position:0% applications or design patterns or like 00:09:25.640 --> 00:09:26.670 align:start position:0% applications or design patterns or like uh<00:09:25.800> one<00:09:25.959> thing<00:09:26.120> that<00:09:26.200> we're<00:09:26.360> trying<00:09:26.560> to 00:09:26.670 --> 00:09:26.680 align:start position:0% uh one thing that we're trying to 00:09:26.680 --> 00:09:28.829 align:start position:0% uh one thing that we're trying to explore<00:09:27.079> is<00:09:27.399> asking<00:09:27.839> questions<00:09:28.519> to<00:09:28.680> your 00:09:28.829 --> 00:09:28.839 align:start position:0% explore is asking questions to your 00:09:28.839 --> 00:09:30.790 align:start position:0% explore is asking questions to your social<00:09:29.120> graph<00:09:29.720> asking<00:09:30.040> private<00:09:30.360> questions 00:09:30.790 --> 00:09:30.800 align:start position:0% social graph asking private questions 00:09:30.800 --> 00:09:33.389 align:start position:0% social graph asking private questions specifically<00:09:31.800> so<00:09:32.360> one<00:09:32.519> setup<00:09:32.880> here<00:09:33.040> is<00:09:33.160> that 00:09:33.389 --> 00:09:33.399 align:start position:0% specifically so one setup here is that 00:09:33.399 --> 00:09:35.230 align:start position:0% specifically so one setup here is that like<00:09:33.800> Richard<00:09:34.279> could<00:09:34.560> like<00:09:34.720> have<00:09:34.880> his<00:09:35.079> like 00:09:35.230 --> 00:09:35.240 align:start position:0% like Richard could like have his like 00:09:35.240 --> 00:09:37.269 align:start position:0% like Richard could like have his like private<00:09:35.560> data<00:09:36.240> uploaded<00:09:36.760> in<00:09:36.959> some<00:09:37.120> like 00:09:37.269 --> 00:09:37.279 align:start position:0% private data uploaded in some like 00:09:37.279 --> 00:09:39.150 align:start position:0% private data uploaded in some like encrypted<00:09:37.720> form<00:09:37.920> or<00:09:38.079> whatnot<00:09:38.680> and<00:09:38.760> I<00:09:38.880> can<00:09:39.000> just 00:09:39.150 --> 00:09:39.160 align:start position:0% encrypted form or whatnot and I can just 00:09:39.160 --> 00:09:40.910 align:start position:0% encrypted form or whatnot and I can just like<00:09:39.360> ask<00:09:39.600> certain<00:09:39.920> queries<00:09:40.320> or<00:09:40.480> I<00:09:40.560> can<00:09:40.680> ask 00:09:40.910 --> 00:09:40.920 align:start position:0% like ask certain queries or I can ask 00:09:40.920 --> 00:09:43.910 align:start position:0% like ask certain queries or I can ask questions<00:09:41.720> like<00:09:42.200> hey<00:09:42.480> like<00:09:42.959> who<00:09:43.240> here<00:09:43.560> wants 00:09:43.910 --> 00:09:43.920 align:start position:0% questions like hey like who here wants 00:09:43.920 --> 00:09:46.110 align:start position:0% questions like hey like who here wants to<00:09:44.519> join<00:09:44.760> the<00:09:44.839> hackathon<00:09:45.279> with<00:09:45.440> me<00:09:45.720> like<00:09:45.920> does 00:09:46.110 --> 00:09:46.120 align:start position:0% to join the hackathon with me like does 00:09:46.120 --> 00:09:47.630 align:start position:0% to join the hackathon with me like does anyone<00:09:46.360> in<00:09:46.480> my<00:09:46.640> social<00:09:46.920> graph<00:09:47.200> meet<00:09:47.440> these 00:09:47.630 --> 00:09:47.640 align:start position:0% anyone in my social graph meet these 00:09:47.640 --> 00:09:49.350 align:start position:0% anyone in my social graph meet these criteria<00:09:48.079> and<00:09:48.240> wants<00:09:48.440> to<00:09:48.720> like<00:09:48.839> be<00:09:49.079> part<00:09:49.200> of 00:09:49.350 --> 00:09:49.360 align:start position:0% criteria and wants to like be part of 00:09:49.360 --> 00:09:51.750 align:start position:0% criteria and wants to like be part of this<00:09:49.519> group<00:09:50.320> um<00:09:50.600> and<00:09:50.839> these<00:09:51.000> queries<00:09:51.560> would 00:09:51.750 --> 00:09:51.760 align:start position:0% this group um and these queries would 00:09:51.760 --> 00:09:54.630 align:start position:0% this group um and these queries would only<00:09:51.959> be<00:09:52.120> decrypted<00:09:52.760> if<00:09:52.880> they're<00:09:53.360> actually<00:09:54.360> uh 00:09:54.630 --> 00:09:54.640 align:start position:0% only be decrypted if they're actually uh 00:09:54.640 --> 00:09:56.269 align:start position:0% only be decrypted if they're actually uh satisfying<00:09:55.160> that<00:09:55.320> criteria<00:09:55.800> so<00:09:55.920> I<00:09:56.000> think<00:09:56.160> like 00:09:56.269 --> 00:09:56.279 align:start position:0% satisfying that criteria so I think like 00:09:56.279 --> 00:09:58.990 align:start position:0% satisfying that criteria so I think like the<00:09:56.360> MPC<00:09:56.920> FHA<00:09:57.399> angle<00:09:57.920> feels<00:09:58.600> a<00:09:58.680> little<00:09:58.839> more 00:09:58.990 --> 00:09:59.000 align:start position:0% the MPC FHA angle feels a little more 00:09:59.000 --> 00:10:01.030 align:start position:0% the MPC FHA angle feels a little more exciting<00:09:59.680> for 00:10:01.030 --> 00:10:01.040 align:start position:0% exciting for 00:10:01.040 --> 00:10:06.269 align:start position:0% exciting for that<00:10:02.279> absolutely<00:10:03.279> I<00:10:03.399> wanted<00:10:03.760> to<00:10:04.079> also<00:10:04.839> so<00:10:05.519> this 00:10:06.269 --> 00:10:06.279 align:start position:0% that absolutely I wanted to also so this 00:10:06.279 --> 00:10:09.550 align:start position:0% that absolutely I wanted to also so this interesting<00:10:07.279> theme<00:10:07.600> sort<00:10:07.839> of<00:10:08.040> came<00:10:08.240> up<00:10:08.600> about 00:10:09.550 --> 00:10:09.560 align:start position:0% interesting theme sort of came up about 00:10:09.560 --> 00:10:12.670 align:start position:0% interesting theme sort of came up about making<00:10:10.040> connections<00:10:11.040> so<00:10:11.560> from<00:10:11.800> web<00:10:12.040> 2<00:10:12.240> to<00:10:12.399> web 00:10:12.670 --> 00:10:12.680 align:start position:0% making connections so from web 2 to web 00:10:12.680 --> 00:10:16.509 align:start position:0% making connections so from web 2 to web 3<00:10:13.519> um<00:10:14.079> from<00:10:14.560> one<00:10:14.959> note<00:10:15.360> to<00:10:15.600> another<00:10:16.240> in<00:10:16.360> your 00:10:16.509 --> 00:10:16.519 align:start position:0% 3 um from one note to another in your 00:10:16.519 --> 00:10:17.550 align:start position:0% 3 um from one note to another in your social 00:10:17.550 --> 00:10:17.560 align:start position:0% social 00:10:17.560 --> 00:10:20.630 align:start position:0% social gr<00:10:18.560> and<00:10:19.200> it's<00:10:19.519> also<00:10:19.920> kind<00:10:20.079> of<00:10:20.279> making 00:10:20.630 --> 00:10:20.640 align:start position:0% gr and it's also kind of making 00:10:20.640 --> 00:10:22.550 align:start position:0% gr and it's also kind of making connections<00:10:21.279> between<00:10:21.640> The<00:10:21.839> Primitives<00:10:22.360> like 00:10:22.550 --> 00:10:22.560 align:start position:0% connections between The Primitives like 00:10:22.560 --> 00:10:25.790 align:start position:0% connections between The Primitives like coars<00:10:23.160> is<00:10:23.360> a<00:10:23.519> good<00:10:23.760> example<00:10:24.320> mpf<00:10:25.320> is<00:10:25.440> a<00:10:25.600> good 00:10:25.790 --> 00:10:25.800 align:start position:0% coars is a good example mpf is a good 00:10:25.800 --> 00:10:29.150 align:start position:0% coars is a good example mpf is a good example<00:10:26.720> so<00:10:27.640> one<00:10:27.920> question<00:10:28.279> that's<00:10:28.600> always<00:10:29.000> at 00:10:29.150 --> 00:10:29.160 align:start position:0% example so one question that's always at 00:10:29.160 --> 00:10:32.110 align:start position:0% example so one question that's always at the<00:10:29.360> the<00:10:29.480> top<00:10:29.640> of<00:10:29.800> my<00:10:30.040> mind<00:10:30.560> is<00:10:30.959> security<00:10:31.880> and 00:10:32.110 --> 00:10:32.120 align:start position:0% the the top of my mind is security and 00:10:32.120 --> 00:10:34.310 align:start position:0% the the top of my mind is security and how<00:10:32.519> security<00:10:33.040> assumptions 00:10:34.310 --> 00:10:34.320 align:start position:0% how security assumptions 00:10:34.320 --> 00:10:38.990 align:start position:0% how security assumptions compose<00:10:35.320> both<00:10:35.760> across<00:10:36.519> Primitives<00:10:37.519> so<00:10:38.519> what 00:10:38.990 --> 00:10:39.000 align:start position:0% compose both across Primitives so what 00:10:39.000 --> 00:10:41.470 align:start position:0% compose both across Primitives so what are<00:10:39.320> so<00:10:39.560> you<00:10:39.720> are<00:10:40.040> introducing<00:10:40.800> new 00:10:41.470 --> 00:10:41.480 align:start position:0% are so you are introducing new 00:10:41.480 --> 00:10:44.030 align:start position:0% are so you are introducing new cryptographic<00:10:42.160> assumptions<00:10:43.120> how<00:10:43.240> do<00:10:43.519> these 00:10:44.030 --> 00:10:44.040 align:start position:0% cryptographic assumptions how do these 00:10:44.040 --> 00:10:48.310 align:start position:0% cryptographic assumptions how do these compose<00:10:45.040> um<00:10:45.720> and<00:10:46.120> also<00:10:46.480> across<00:10:47.320> applications 00:10:48.310 --> 00:10:48.320 align:start position:0% compose um and also across applications 00:10:48.320 --> 00:10:50.310 align:start position:0% compose um and also across applications and<00:10:48.480> in<00:10:48.720> that<00:10:48.959> case<00:10:49.240> it's<00:10:49.399> more<00:10:49.680> about<00:10:49.959> threat 00:10:50.310 --> 00:10:50.320 align:start position:0% and in that case it's more about threat 00:10:50.320 --> 00:10:52.790 align:start position:0% and in that case it's more about threat modeling<00:10:50.959> so<00:10:51.360> for<00:10:51.560> example<00:10:52.480> if<00:10:52.600> you're 00:10:52.790 --> 00:10:52.800 align:start position:0% modeling so for example if you're 00:10:52.800 --> 00:10:57.150 align:start position:0% modeling so for example if you're relying<00:10:53.320> on<00:10:53.680> say<00:10:54.399> the<00:10:54.800> Vanos<00:10:55.440> email<00:10:55.880> format<00:10:56.880> um 00:10:57.150 --> 00:10:57.160 align:start position:0% relying on say the Vanos email format um 00:10:57.160 --> 00:11:01.310 align:start position:0% relying on say the Vanos email format um and<00:10:57.320> they<00:10:57.440> Chang<00:10:57.800> it<00:10:58.399> let's<00:10:58.639> say<00:10:59.440> um<00:11:00.360> or<00:11:01.120> yeah 00:11:01.310 --> 00:11:01.320 align:start position:0% and they Chang it let's say um or yeah 00:11:01.320 --> 00:11:04.949 align:start position:0% and they Chang it let's say um or yeah you're<00:11:02.079> um<00:11:02.600> relying<00:11:03.079> on<00:11:03.519> like<00:11:04.040> uh<00:11:04.240> some<00:11:04.480> dkim 00:11:04.949 --> 00:11:04.959 align:start position:0% you're um relying on like uh some dkim 00:11:04.959 --> 00:11:07.269 align:start position:0% you're um relying on like uh some dkim servers<00:11:05.360> some<00:11:05.600> registry<00:11:06.440> like<00:11:06.680> how<00:11:06.800> did<00:11:07.040> the 00:11:07.269 --> 00:11:07.279 align:start position:0% servers some registry like how did the 00:11:07.279 --> 00:11:11.509 align:start position:0% servers some registry like how did the threat<00:11:07.560> models<00:11:08.560> um<00:11:09.079> compose<00:11:10.079> um<00:11:10.399> so<00:11:10.880> I'm<00:11:11.040> still 00:11:11.509 --> 00:11:11.519 align:start position:0% threat models um compose um so I'm still 00:11:11.519 --> 00:11:14.670 align:start position:0% threat models um compose um so I'm still curious<00:11:12.079> as<00:11:12.560> designers<00:11:13.560> how<00:11:13.880> you<00:11:14.160> reason 00:11:14.670 --> 00:11:14.680 align:start position:0% curious as designers how you reason 00:11:14.680 --> 00:11:18.550 align:start position:0% curious as designers how you reason about<00:11:15.000> that<00:11:15.800> first<00:11:16.000> of<00:11:16.160> all<00:11:16.760> and<00:11:17.040> also<00:11:17.639> how<00:11:18.279> you 00:11:18.550 --> 00:11:18.560 align:start position:0% about that first of all and also how you 00:11:18.560 --> 00:11:21.069 align:start position:0% about that first of all and also how you communicate<00:11:19.160> it<00:11:19.440> to<00:11:19.680> your<00:11:19.920> users<00:11:20.600> how<00:11:20.800> you 00:11:21.069 --> 00:11:21.079 align:start position:0% communicate it to your users how you 00:11:21.079 --> 00:11:25.389 align:start position:0% communicate it to your users how you educate<00:11:21.600> your<00:11:21.760> users<00:11:22.279> about 00:11:25.389 --> 00:11:25.399 align:start position:0% 00:11:25.399 --> 00:11:29.350 align:start position:0% it<00:11:26.399> all<00:11:26.519> right<00:11:26.720> I'll<00:11:26.880> go<00:11:27.040> first<00:11:27.560> um<00:11:28.360> so<00:11:28.959> I<00:11:29.079> think 00:11:29.350 --> 00:11:29.360 align:start position:0% it all right I'll go first um so I think 00:11:29.360 --> 00:11:33.750 align:start position:0% it all right I'll go first um so I think think<00:11:30.040> because<00:11:30.920> ZK<00:11:31.360> PDP<00:11:32.360> uh<00:11:32.600> is<00:11:32.760> building<00:11:33.480> like 00:11:33.750 --> 00:11:33.760 align:start position:0% think because ZK PDP uh is building like 00:11:33.760 --> 00:11:36.670 align:start position:0% think because ZK PDP uh is building like a<00:11:33.959> financial<00:11:34.920> application<00:11:35.440> if<00:11:35.519> you<00:11:35.639> will<00:11:36.440> uh 00:11:36.670 --> 00:11:36.680 align:start position:0% a financial application if you will uh 00:11:36.680 --> 00:11:39.870 align:start position:0% a financial application if you will uh we're<00:11:36.800> dealing<00:11:37.120> with<00:11:37.399> like<00:11:38.240> movement<00:11:38.959> of<00:11:39.760> I 00:11:39.870 --> 00:11:39.880 align:start position:0% we're dealing with like movement of I 00:11:39.880 --> 00:11:41.949 align:start position:0% we're dealing with like movement of I guess<00:11:40.120> stable<00:11:40.519> coins<00:11:40.839> on<00:11:41.040> chain<00:11:41.519> so<00:11:41.720> there<00:11:41.800> is 00:11:41.949 --> 00:11:41.959 align:start position:0% guess stable coins on chain so there is 00:11:41.959 --> 00:11:45.910 align:start position:0% guess stable coins on chain so there is real<00:11:42.200> value<00:11:42.480> tied<00:11:42.720> to<00:11:42.880> it<00:11:43.720> uh<00:11:43.959> we<00:11:44.320> do<00:11:45.000> like 00:11:45.910 --> 00:11:45.920 align:start position:0% real value tied to it uh we do like 00:11:45.920 --> 00:11:48.269 align:start position:0% real value tied to it uh we do like treat<00:11:46.320> security<00:11:46.800> pretty<00:11:47.040> seriously<00:11:48.000> U<00:11:48.120> both 00:11:48.269 --> 00:11:48.279 align:start position:0% treat security pretty seriously U both 00:11:48.279 --> 00:11:49.829 align:start position:0% treat security pretty seriously U both on<00:11:48.360> the<00:11:48.480> cryptographic<00:11:49.120> side<00:11:49.320> and<00:11:49.600> on<00:11:49.720> the 00:11:49.829 --> 00:11:49.839 align:start position:0% on the cryptographic side and on the 00:11:49.839 --> 00:11:53.870 align:start position:0% on the cryptographic side and on the application<00:11:50.399> side<00:11:51.360> um<00:11:51.600> I<00:11:51.720> think<00:11:52.320> on<00:11:52.639> the<00:11:53.639> I<00:11:53.800> I 00:11:53.870 --> 00:11:53.880 align:start position:0% application side um I think on the I I 00:11:53.880 --> 00:11:56.829 align:start position:0% application side um I think on the I I guess<00:11:54.079> overall<00:11:54.839> we<00:11:55.079> see<00:11:55.680> like<00:11:55.920> security<00:11:56.680> as 00:11:56.829 --> 00:11:56.839 align:start position:0% guess overall we see like security as 00:11:56.839 --> 00:11:58.750 align:start position:0% guess overall we see like security as kind<00:11:56.959> of<00:11:57.160> like<00:11:57.440> how<00:11:57.639> comfortable<00:11:58.160> are<00:11:58.360> we<00:11:58.639> like 00:11:58.750 --> 00:11:58.760 align:start position:0% kind of like how comfortable are we like 00:11:58.760 --> 00:12:01.230 align:start position:0% kind of like how comfortable are we like securing<00:11:59.480> like<00:11:59.760> this<00:11:59.920> dollar<00:12:00.240> amount<00:12:00.880> over 00:12:01.230 --> 00:12:01.240 align:start position:0% securing like this dollar amount over 00:12:01.240 --> 00:12:04.710 align:start position:0% securing like this dollar amount over this<00:12:01.839> amount<00:12:02.079> of<00:12:02.240> hours<00:12:03.120> for<00:12:03.360> example<00:12:04.360> uh<00:12:04.519> and 00:12:04.710 --> 00:12:04.720 align:start position:0% this amount of hours for example uh and 00:12:04.720 --> 00:12:08.190 align:start position:0% this amount of hours for example uh and I<00:12:04.839> guess<00:12:05.399> like<00:12:06.399> different<00:12:07.040> Primitives<00:12:08.040> uh 00:12:08.190 --> 00:12:08.200 align:start position:0% I guess like different Primitives uh 00:12:08.200 --> 00:12:11.470 align:start position:0% I guess like different Primitives uh that<00:12:08.320> we<00:12:08.839> use<00:12:09.839> uh<00:12:10.240> I<00:12:10.360> think<00:12:10.800> fall<00:12:11.120> under 00:12:11.470 --> 00:12:11.480 align:start position:0% that we use uh I think fall under 00:12:11.480 --> 00:12:13.590 align:start position:0% that we use uh I think fall under different<00:12:11.920> parts<00:12:12.120> of<00:12:12.320> that<00:12:12.480> Spectrum<00:12:13.320> uh<00:12:13.440> for 00:12:13.590 --> 00:12:13.600 align:start position:0% different parts of that Spectrum uh for 00:12:13.600 --> 00:12:17.310 align:start position:0% different parts of that Spectrum uh for example<00:12:14.199> like<00:12:14.480> email<00:12:15.279> may<00:12:15.480> not<00:12:15.760> be<00:12:16.320> I<00:12:16.480> guess 00:12:17.310 --> 00:12:17.320 align:start position:0% example like email may not be I guess 00:12:17.320 --> 00:12:23.110 align:start position:0% example like email may not be I guess the<00:12:17.560> most<00:12:18.199> I<00:12:18.560> guess<00:12:19.560> um<00:12:20.959> like<00:12:21.959> yeah<00:12:22.199> like<00:12:22.760> gated 00:12:23.110 --> 00:12:23.120 align:start position:0% the most I guess um like yeah like gated 00:12:23.120 --> 00:12:25.629 align:start position:0% the most I guess um like yeah like gated and<00:12:23.360> secured<00:12:24.120> uh<00:12:24.199> for<00:12:24.399> example<00:12:25.040> whereas<00:12:25.440> like 00:12:25.629 --> 00:12:25.639 align:start position:0% and secured uh for example whereas like 00:12:25.639 --> 00:12:27.829 align:start position:0% and secured uh for example whereas like behind<00:12:26.120> like<00:12:26.199> a<00:12:26.440> gated<00:12:26.880> like<00:12:27.040> private<00:12:27.360> API 00:12:27.829 --> 00:12:27.839 align:start position:0% behind like a gated like private API 00:12:27.839 --> 00:12:32.269 align:start position:0% behind like a gated like private API with<00:12:27.959> 2fa<00:12:29.399> and<00:12:29.600> everything<00:12:30.800> um<00:12:31.800> uh<00:12:32.000> yeah<00:12:32.160> the 00:12:32.269 --> 00:12:32.279 align:start position:0% with 2fa and everything um uh yeah the 00:12:32.279 --> 00:12:34.949 align:start position:0% with 2fa and everything um uh yeah the data<00:12:32.560> might<00:12:32.720> be<00:12:32.880> more<00:12:33.160> secure<00:12:33.760> so<00:12:34.079> I<00:12:34.160> think<00:12:34.680> we 00:12:34.949 --> 00:12:34.959 align:start position:0% data might be more secure so I think we 00:12:34.959 --> 00:12:38.790 align:start position:0% data might be more secure so I think we do<00:12:35.360> account<00:12:35.600> for<00:12:35.800> all<00:12:35.920> of<00:12:36.120> that<00:12:36.760> in<00:12:37.000> like<00:12:37.800> how 00:12:38.790 --> 00:12:38.800 align:start position:0% do account for all of that in like how 00:12:38.800 --> 00:12:41.189 align:start position:0% do account for all of that in like how much<00:12:39.199> we<00:12:39.440> allow<00:12:39.959> like<00:12:40.240> the<00:12:40.360> max<00:12:40.680> transaction 00:12:41.189 --> 00:12:41.199 align:start position:0% much we allow like the max transaction 00:12:41.199 --> 00:12:43.230 align:start position:0% much we allow like the max transaction limit<00:12:41.720> uh<00:12:41.839> to<00:12:42.000> be<00:12:42.360> in<00:12:42.480> some<00:12:42.639> of<00:12:42.800> these 00:12:43.230 --> 00:12:43.240 align:start position:0% limit uh to be in some of these 00:12:43.240 --> 00:12:46.030 align:start position:0% limit uh to be in some of these protocols<00:12:44.240> and<00:12:44.399> I<00:12:44.519> think<00:12:45.240> yeah<00:12:45.440> I<00:12:45.519> think<00:12:45.680> we're 00:12:46.030 --> 00:12:46.040 align:start position:0% protocols and I think yeah I think we're 00:12:46.040 --> 00:12:47.949 align:start position:0% protocols and I think yeah I think we're constantly<00:12:46.440> monitoring<00:12:47.040> and<00:12:47.199> seeing<00:12:47.760> as 00:12:47.949 --> 00:12:47.959 align:start position:0% constantly monitoring and seeing as 00:12:47.959 --> 00:12:50.189 align:start position:0% constantly monitoring and seeing as these<00:12:48.120> Technologies<00:12:48.720> mature<00:12:49.480> uh<00:12:49.920> we<00:12:50.000> feel 00:12:50.189 --> 00:12:50.199 align:start position:0% these Technologies mature uh we feel 00:12:50.199 --> 00:12:52.430 align:start position:0% these Technologies mature uh we feel more<00:12:50.440> confident<00:12:51.399> uh<00:12:51.560> confident<00:12:52.079> on<00:12:52.279> it 00:12:52.430 --> 00:12:52.440 align:start position:0% more confident uh confident on it 00:12:52.440 --> 00:12:54.829 align:start position:0% more confident uh confident on it securing<00:12:53.040> uh<00:12:53.199> higher<00:12:53.399> dollar 00:12:54.829 --> 00:12:54.839 align:start position:0% securing uh higher dollar 00:12:54.839 --> 00:12:57.750 align:start position:0% securing uh higher dollar amounts<00:12:55.839> yeah<00:12:56.000> I<00:12:56.079> can<00:12:56.320> also<00:12:57.120> address<00:12:57.440> trust 00:12:57.750 --> 00:12:57.760 align:start position:0% amounts yeah I can also address trust 00:12:57.760 --> 00:13:00.030 align:start position:0% amounts yeah I can also address trust assumptions<00:12:58.120> on<00:12:58.240> the<00:12:58.320> ZK<00:12:58.639> email<00:12:58.920> side 00:13:00.030 --> 00:13:00.040 align:start position:0% assumptions on the ZK email side 00:13:00.040 --> 00:13:02.990 align:start position:0% assumptions on the ZK email side I<00:13:00.240> guess<00:13:01.079> we<00:13:01.360> think<00:13:01.680> about<00:13:02.000> this<00:13:02.279> in<00:13:02.440> two<00:13:02.639> ways 00:13:02.990 --> 00:13:03.000 align:start position:0% I guess we think about this in two ways 00:13:03.000 --> 00:13:05.629 align:start position:0% I guess we think about this in two ways one<00:13:03.160> is<00:13:03.360> around<00:13:04.079> when<00:13:04.360> things<00:13:04.760> update<00:13:05.360> so<00:13:05.560> you 00:13:05.629 --> 00:13:05.639 align:start position:0% one is around when things update so you 00:13:05.639 --> 00:13:06.990 align:start position:0% one is around when things update so you say<00:13:05.800> your<00:13:05.920> email<00:13:06.199> template<00:13:06.519> updates<00:13:06.800> or<00:13:06.920> the 00:13:06.990 --> 00:13:07.000 align:start position:0% say your email template updates or the 00:13:07.000 --> 00:13:09.829 align:start position:0% say your email template updates or the de<00:13:07.279> registry<00:13:07.680> updates<00:13:08.639> it's<00:13:09.079> one<00:13:09.399> very<00:13:09.600> easy 00:13:09.829 --> 00:13:09.839 align:start position:0% de registry updates it's one very easy 00:13:09.839 --> 00:13:11.550 align:start position:0% de registry updates it's one very easy to<00:13:10.000> change<00:13:10.360> that<00:13:10.600> so<00:13:10.760> we<00:13:10.880> have<00:13:11.000> a<00:13:11.120> very<00:13:11.320> simple 00:13:11.550 --> 00:13:11.560 align:start position:0% to change that so we have a very simple 00:13:11.560 --> 00:13:13.590 align:start position:0% to change that so we have a very simple Builder<00:13:11.920> where<00:13:12.040> you<00:13:12.160> put<00:13:12.320> in<00:13:12.480> the<00:13:12.639> new<00:13:13.199> format 00:13:13.590 --> 00:13:13.600 align:start position:0% Builder where you put in the new format 00:13:13.600 --> 00:13:14.550 align:start position:0% Builder where you put in the new format or<00:13:13.720> the<00:13:13.800> new<00:13:13.959> pars<00:13:14.199> thing<00:13:14.360> and<00:13:14.440> it 00:13:14.550 --> 00:13:14.560 align:start position:0% or the new pars thing and it 00:13:14.560 --> 00:13:16.389 align:start position:0% or the new pars thing and it automatically<00:13:15.000> handles<00:13:15.360> everything<00:13:15.600> for<00:13:15.839> you 00:13:16.389 --> 00:13:16.399 align:start position:0% automatically handles everything for you 00:13:16.399 --> 00:13:18.430 align:start position:0% automatically handles everything for you and<00:13:16.480> so<00:13:16.720> one<00:13:16.880> thing<00:13:17.040> is<00:13:17.320> okay<00:13:17.760> when<00:13:17.959> a<00:13:18.079> template 00:13:18.430 --> 00:13:18.440 align:start position:0% and so one thing is okay when a template 00:13:18.440 --> 00:13:20.670 align:start position:0% and so one thing is okay when a template changes<00:13:19.120> the<00:13:19.480> developer's<00:13:19.959> ability<00:13:20.240> to<00:13:20.399> react 00:13:20.670 --> 00:13:20.680 align:start position:0% changes the developer's ability to react 00:13:20.680 --> 00:13:22.710 align:start position:0% changes the developer's ability to react should<00:13:20.839> be<00:13:21.000> extremely<00:13:21.519> fast<00:13:22.240> and<00:13:22.360> then<00:13:22.519> number 00:13:22.710 --> 00:13:22.720 align:start position:0% should be extremely fast and then number 00:13:22.720 --> 00:13:25.949 align:start position:0% should be extremely fast and then number two<00:13:23.760> is<00:13:24.760> we<00:13:24.920> kind<00:13:25.040> of<00:13:25.160> want<00:13:25.279> to<00:13:25.399> make<00:13:25.519> sure<00:13:25.760> the 00:13:25.949 --> 00:13:25.959 align:start position:0% two is we kind of want to make sure the 00:13:25.959 --> 00:13:29.430 align:start position:0% two is we kind of want to make sure the system<00:13:26.199> is<00:13:26.399> robust<00:13:26.839> to<00:13:27.120> any<00:13:27.880> weird<00:13:28.360> kinds<00:13:28.760> of 00:13:29.430 --> 00:13:29.440 align:start position:0% system is robust to any weird kinds of 00:13:29.440 --> 00:13:31.509 align:start position:0% system is robust to any weird kinds of like<00:13:29.639> bugs<00:13:29.959> or<00:13:30.120> malicious<00:13:30.480> DM<00:13:30.880> key<00:13:31.079> updates 00:13:31.509 --> 00:13:31.519 align:start position:0% like bugs or malicious DM key updates 00:13:31.519 --> 00:13:33.030 align:start position:0% like bugs or malicious DM key updates and<00:13:31.639> so<00:13:31.800> one<00:13:32.000> way<00:13:32.120> we<00:13:32.279> think<00:13:32.440> about<00:13:32.720> this<00:13:32.920> for 00:13:33.030 --> 00:13:33.040 align:start position:0% and so one way we think about this for 00:13:33.040 --> 00:13:34.550 align:start position:0% and so one way we think about this for instance<00:13:33.639> with<00:13:33.800> email<00:13:34.040> based<00:13:34.320> account 00:13:34.550 --> 00:13:34.560 align:start position:0% instance with email based account 00:13:34.560 --> 00:13:36.790 align:start position:0% instance with email based account recovery<00:13:35.160> where<00:13:35.279> it<00:13:35.480> really<00:13:35.760> matters<00:13:36.560> like 00:13:36.790 --> 00:13:36.800 align:start position:0% recovery where it really matters like 00:13:36.800 --> 00:13:38.430 align:start position:0% recovery where it really matters like the<00:13:36.920> entire<00:13:37.279> security<00:13:37.639> of<00:13:37.720> your<00:13:37.920> account 00:13:38.430 --> 00:13:38.440 align:start position:0% the entire security of your account 00:13:38.440 --> 00:13:41.030 align:start position:0% the entire security of your account hinges<00:13:38.839> on<00:13:39.320> you<00:13:39.480> know<00:13:40.399> it<00:13:40.560> really<00:13:40.720> shouldn't 00:13:41.030 --> 00:13:41.040 align:start position:0% hinges on you know it really shouldn't 00:13:41.040 --> 00:13:43.750 align:start position:0% hinges on you know it really shouldn't hinge<00:13:41.519> on<00:13:42.519> will<00:13:42.720> this<00:13:42.880> recovery<00:13:43.240> module<00:13:43.600> get 00:13:43.750 --> 00:13:43.760 align:start position:0% hinge on will this recovery module get 00:13:43.760 --> 00:13:45.550 align:start position:0% hinge on will this recovery module get hacked<00:13:44.399> and<00:13:44.480> so<00:13:44.680> one<00:13:44.839> thing<00:13:44.959> we<00:13:45.120> think<00:13:45.279> about 00:13:45.550 --> 00:13:45.560 align:start position:0% hacked and so one thing we think about 00:13:45.560 --> 00:13:47.790 align:start position:0% hacked and so one thing we think about is<00:13:45.680> like<00:13:45.880> very<00:13:46.160> intentional<00:13:46.839> time<00:13:47.079> locks<00:13:47.600> and 00:13:47.790 --> 00:13:47.800 align:start position:0% is like very intentional time locks and 00:13:47.800 --> 00:13:50.749 align:start position:0% is like very intentional time locks and kill<00:13:48.000> switches<00:13:48.480> so<00:13:48.639> for<00:13:48.920> instance<00:13:49.920> uh<00:13:50.639> like 00:13:50.749 --> 00:13:50.759 align:start position:0% kill switches so for instance uh like 00:13:50.759 --> 00:13:53.590 align:start position:0% kill switches so for instance uh like many<00:13:50.959> of<00:13:51.079> these<00:13:51.279> accounts<00:13:51.720> will<00:13:52.079> have<00:13:52.959> uh<00:13:53.360> once 00:13:53.590 --> 00:13:53.600 align:start position:0% many of these accounts will have uh once 00:13:53.600 --> 00:13:55.189 align:start position:0% many of these accounts will have uh once all<00:13:53.759> the<00:13:53.920> emails<00:13:54.240> say<00:13:54.480> hey<00:13:54.600> I<00:13:54.639> should<00:13:54.839> recover 00:13:55.189 --> 00:13:55.199 align:start position:0% all the emails say hey I should recover 00:13:55.199 --> 00:13:57.269 align:start position:0% all the emails say hey I should recover this<00:13:55.320> account<00:13:55.519> to<00:13:55.680> this<00:13:55.839> new<00:13:56.040> address<00:13:56.720> a<00:13:56.880> onewe 00:13:57.269 --> 00:13:57.279 align:start position:0% this account to this new address a onewe 00:13:57.279 --> 00:13:59.110 align:start position:0% this account to this new address a onewe time<00:13:57.480> lock<00:13:57.680> starts<00:13:58.040> that's<00:13:58.240> non-negotiable 00:13:59.110 --> 00:13:59.120 align:start position:0% time lock starts that's non-negotiable 00:13:59.120 --> 00:14:02.110 align:start position:0% time lock starts that's non-negotiable on<00:13:59.320> chain<00:13:59.959> and<00:14:00.079> so<00:14:00.399> even<00:14:00.800> if<00:14:01.399> either<00:14:01.759> the<00:14:01.880> email 00:14:02.110 --> 00:14:02.120 align:start position:0% on chain and so even if either the email 00:14:02.120 --> 00:14:04.030 align:start position:0% on chain and so even if either the email server<00:14:02.399> got<00:14:02.560> hacked<00:14:02.839> or<00:14:02.959> the<00:14:03.040> DM<00:14:03.440> key<00:14:03.759> got 00:14:04.030 --> 00:14:04.040 align:start position:0% server got hacked or the DM key got 00:14:04.040 --> 00:14:06.590 align:start position:0% server got hacked or the DM key got somehow<00:14:04.360> maliciously<00:14:04.800> rotated<00:14:05.160> or<00:14:05.320> even<00:14:05.680> like 00:14:06.590 --> 00:14:06.600 align:start position:0% somehow maliciously rotated or even like 00:14:06.600 --> 00:14:08.870 align:start position:0% somehow maliciously rotated or even like uh<00:14:06.839> you<00:14:07.000> know<00:14:07.399> the<00:14:07.519> users<00:14:08.079> Guardians<00:14:08.560> acted 00:14:08.870 --> 00:14:08.880 align:start position:0% uh you know the users Guardians acted 00:14:08.880 --> 00:14:11.350 align:start position:0% uh you know the users Guardians acted against<00:14:09.079> their<00:14:09.199> own<00:14:09.399> will<00:14:10.199> then<00:14:10.759> at<00:14:10.920> least<00:14:11.199> the 00:14:11.350 --> 00:14:11.360 align:start position:0% against their own will then at least the 00:14:11.360 --> 00:14:13.509 align:start position:0% against their own will then at least the account<00:14:11.560> owner<00:14:11.920> has<00:14:12.040> a<00:14:12.160> week<00:14:12.360> to<00:14:12.519> repair<00:14:12.959> that 00:14:13.509 --> 00:14:13.519 align:start position:0% account owner has a week to repair that 00:14:13.519 --> 00:14:15.310 align:start position:0% account owner has a week to repair that and<00:14:13.600> so<00:14:13.800> I<00:14:13.880> think<00:14:14.079> non-negotiable<00:14:14.759> timel<00:14:15.160> has 00:14:15.310 --> 00:14:15.320 align:start position:0% and so I think non-negotiable timel has 00:14:15.320 --> 00:14:17.350 align:start position:0% and so I think non-negotiable timel has also<00:14:15.480> been<00:14:15.639> quite<00:14:15.839> compelling<00:14:16.839> and<00:14:16.959> the<00:14:17.079> final 00:14:17.350 --> 00:14:17.360 align:start position:0% also been quite compelling and the final 00:14:17.360 --> 00:14:19.389 align:start position:0% also been quite compelling and the final thing<00:14:17.519> is<00:14:17.680> giving<00:14:18.000> users<00:14:18.560> the<00:14:18.720> ability<00:14:19.160> to 00:14:19.389 --> 00:14:19.399 align:start position:0% thing is giving users the ability to 00:14:19.399 --> 00:14:22.590 align:start position:0% thing is giving users the ability to exit<00:14:20.320> so<00:14:21.320> for<00:14:21.480> instance<00:14:21.720> for<00:14:21.880> the<00:14:21.959> deim<00:14:22.320> keys 00:14:22.590 --> 00:14:22.600 align:start position:0% exit so for instance for the deim keys 00:14:22.600 --> 00:14:24.350 align:start position:0% exit so for instance for the deim keys if<00:14:22.720> a<00:14:22.800> user<00:14:23.160> doesn't<00:14:23.440> trust<00:14:24.079> hey<00:14:24.240> these 00:14:24.350 --> 00:14:24.360 align:start position:0% if a user doesn't trust hey these 00:14:24.360 --> 00:14:25.749 align:start position:0% if a user doesn't trust hey these oracles<00:14:24.720> they've<00:14:24.880> set<00:14:25.000> for<00:14:25.079> the<00:14:25.160> dkim<00:14:25.519> keys 00:14:25.749 --> 00:14:25.759 align:start position:0% oracles they've set for the dkim keys 00:14:25.759 --> 00:14:27.829 align:start position:0% oracles they've set for the dkim keys are<00:14:25.959> are<00:14:26.120> going<00:14:26.279> to<00:14:26.480> always<00:14:26.720> act<00:14:26.920> correctly 00:14:27.829 --> 00:14:27.839 align:start position:0% are are going to always act correctly 00:14:27.839 --> 00:14:29.749 align:start position:0% are are going to always act correctly we've<00:14:28.120> made<00:14:28.279> it<00:14:28.440> so<00:14:28.600> that<00:14:28.759> us<00:14:29.079> users<00:14:29.320> can<00:14:29.480> say 00:14:29.749 --> 00:14:29.759 align:start position:0% we've made it so that us users can say 00:14:29.759 --> 00:14:32.110 align:start position:0% we've made it so that us users can say look<00:14:30.240> I<00:14:30.560> have<00:14:30.680> to<00:14:30.920> approve<00:14:31.360> all<00:14:31.560> dick<00:14:31.920> key 00:14:32.110 --> 00:14:32.120 align:start position:0% look I have to approve all dick key 00:14:32.120 --> 00:14:34.590 align:start position:0% look I have to approve all dick key rotations<00:14:32.639> that<00:14:32.720> are<00:14:32.920> applied<00:14:33.279> to<00:14:33.519> my<00:14:33.800> account 00:14:34.590 --> 00:14:34.600 align:start position:0% rotations that are applied to my account 00:14:34.600 --> 00:14:37.710 align:start position:0% rotations that are applied to my account and<00:14:34.680> so<00:14:35.000> now<00:14:35.519> we<00:14:35.680> kind<00:14:35.800> of<00:14:35.920> show<00:14:36.560> you<00:14:36.720> know<00:14:37.480> in 00:14:37.710 --> 00:14:37.720 align:start position:0% and so now we kind of show you know in 00:14:37.720 --> 00:14:40.509 align:start position:0% and so now we kind of show you know in the<00:14:38.079> maybe<00:14:38.279> in<00:14:38.360> the<00:14:38.480> ux<00:14:39.040> hey<00:14:39.800> uh<00:14:40.000> confirm<00:14:40.360> your 00:14:40.509 --> 00:14:40.519 align:start position:0% the maybe in the ux hey uh confirm your 00:14:40.519 --> 00:14:42.590 align:start position:0% the maybe in the ux hey uh confirm your guardian<00:14:40.959> emails<00:14:41.560> and<00:14:41.720> the<00:14:41.839> relevant<00:14:42.240> keys 00:14:42.590 --> 00:14:42.600 align:start position:0% guardian emails and the relevant keys 00:14:42.600 --> 00:14:44.590 align:start position:0% guardian emails and the relevant keys and<00:14:42.720> the<00:14:42.800> user<00:14:43.079> just<00:14:43.600> uh<00:14:43.800> kind<00:14:43.920> of<00:14:44.199> does<00:14:44.440> say 00:14:44.590 --> 00:14:44.600 align:start position:0% and the user just uh kind of does say 00:14:44.600 --> 00:14:46.509 align:start position:0% and the user just uh kind of does say some<00:14:44.759> pass<00:14:45.000> key<00:14:45.199> authorization<00:14:46.160> and<00:14:46.279> that'll 00:14:46.509 --> 00:14:46.519 align:start position:0% some pass key authorization and that'll 00:14:46.519 --> 00:14:48.030 align:start position:0% some pass key authorization and that'll automatically<00:14:47.079> check<00:14:47.600> okay<00:14:47.759> I'm<00:14:47.839> going<00:14:47.920> to<00:14:47.959> do 00:14:48.030 --> 00:14:48.040 align:start position:0% automatically check okay I'm going to do 00:14:48.040 --> 00:14:50.269 align:start position:0% automatically check okay I'm going to do the<00:14:48.120> DNS<00:14:48.519> check<00:14:48.920> did<00:14:49.079> the<00:14:49.160> DM<00:14:49.519> Keys<00:14:49.759> match<00:14:50.160> okay 00:14:50.269 --> 00:14:50.279 align:start position:0% the DNS check did the DM Keys match okay 00:14:50.279 --> 00:14:51.590 align:start position:0% the DNS check did the DM Keys match okay I'm<00:14:50.360> going<00:14:50.440> to<00:14:50.560> rotate<00:14:50.800> them<00:14:50.959> on<00:14:51.079> chain<00:14:51.360> for 00:14:51.590 --> 00:14:51.600 align:start position:0% I'm going to rotate them on chain for 00:14:51.600 --> 00:14:53.790 align:start position:0% I'm going to rotate them on chain for this<00:14:51.759> user<00:14:52.079> specifically<00:14:52.560> so<00:14:52.720> allowing<00:14:53.160> users 00:14:53.790 --> 00:14:53.800 align:start position:0% this user specifically so allowing users 00:14:53.800 --> 00:14:55.150 align:start position:0% this user specifically so allowing users to<00:14:53.959> have<00:14:54.120> control<00:14:54.440> over<00:14:54.600> their<00:14:54.720> own<00:14:54.880> Keys 00:14:55.150 --> 00:14:55.160 align:start position:0% to have control over their own Keys 00:14:55.160 --> 00:14:56.949 align:start position:0% to have control over their own Keys within<00:14:55.360> an<00:14:55.480> intuitive<00:14:55.920> manner<00:14:56.600> I<00:14:56.680> think<00:14:56.800> is 00:14:56.949 --> 00:14:56.959 align:start position:0% within an intuitive manner I think is 00:14:56.959 --> 00:14:58.590 align:start position:0% within an intuitive manner I think is also<00:14:57.240> quite<00:14:57.440> important<00:14:57.920> so<00:14:58.279> yeah<00:14:58.399> these<00:14:58.519> are 00:14:58.590 --> 00:14:58.600 align:start position:0% also quite important so yeah these are 00:14:58.600 --> 00:15:02.269 align:start position:0% also quite important so yeah these are the<00:14:58.720> three<00:14:58.839> ways<00:14:59.199> easy<00:14:59.639> updates<00:15:00.920> um<00:15:01.920> having<00:15:02.160> it 00:15:02.269 --> 00:15:02.279 align:start position:0% the three ways easy updates um having it 00:15:02.279 --> 00:15:03.350 align:start position:0% the three ways easy updates um having it so<00:15:02.360> that<00:15:02.440> there's<00:15:02.600> non-negotiable<00:15:03.160> time 00:15:03.350 --> 00:15:03.360 align:start position:0% so that there's non-negotiable time 00:15:03.360 --> 00:15:04.710 align:start position:0% so that there's non-negotiable time lockss<00:15:03.560> and<00:15:03.639> giving<00:15:03.839> users<00:15:04.160> control<00:15:04.519> over 00:15:04.710 --> 00:15:04.720 align:start position:0% lockss and giving users control over 00:15:04.720 --> 00:15:07.350 align:start position:0% lockss and giving users control over their<00:15:04.920> own<00:15:05.519> keys<00:15:05.800> or<00:15:06.000> parts<00:15:06.480> or<00:15:06.639> oracles<00:15:07.279> that 00:15:07.350 --> 00:15:07.360 align:start position:0% their own keys or parts or oracles that 00:15:07.360 --> 00:15:09.069 align:start position:0% their own keys or parts or oracles that they<00:15:07.480> don't<00:15:07.639> have<00:15:07.720> to<00:15:07.839> trust 00:15:09.069 --> 00:15:09.079 align:start position:0% they don't have to trust 00:15:09.079 --> 00:15:13.110 align:start position:0% they don't have to trust it<00:15:10.079> yeah<00:15:10.240> sure<00:15:10.880> uh<00:15:11.160> for<00:15:11.519> MPC<00:15:11.959> and<00:15:12.120> FHA<00:15:12.680> security 00:15:13.110 --> 00:15:13.120 align:start position:0% it yeah sure uh for MPC and FHA security 00:15:13.120 --> 00:15:15.550 align:start position:0% it yeah sure uh for MPC and FHA security is<00:15:13.759> generally<00:15:14.120> a<00:15:14.240> lot<00:15:14.360> more<00:15:14.880> difficult<00:15:15.320> like 00:15:15.550 --> 00:15:15.560 align:start position:0% is generally a lot more difficult like 00:15:15.560 --> 00:15:16.910 align:start position:0% is generally a lot more difficult like there's<00:15:15.800> been<00:15:16.000> so<00:15:16.160> much<00:15:16.320> money<00:15:16.560> being<00:15:16.759> put 00:15:16.910 --> 00:15:16.920 align:start position:0% there's been so much money being put 00:15:16.920 --> 00:15:18.629 align:start position:0% there's been so much money being put into<00:15:17.120> ZK<00:15:17.480> Audits<00:15:17.800> and<00:15:17.920> all<00:15:18.040> these<00:15:18.160> rollups<00:15:18.519> and 00:15:18.629 --> 00:15:18.639 align:start position:0% into ZK Audits and all these rollups and 00:15:18.639 --> 00:15:19.910 align:start position:0% into ZK Audits and all these rollups and everything<00:15:18.920> that<00:15:19.079> like<00:15:19.199> people<00:15:19.480> know<00:15:19.680> how<00:15:19.759> to 00:15:19.910 --> 00:15:19.920 align:start position:0% everything that like people know how to 00:15:19.920 --> 00:15:23.189 align:start position:0% everything that like people know how to audit<00:15:20.440> circuits<00:15:21.279> very<00:15:21.519> well<00:15:22.360> um<00:15:22.519> and<00:15:22.639> for<00:15:22.759> MPC 00:15:23.189 --> 00:15:23.199 align:start position:0% audit circuits very well um and for MPC 00:15:23.199 --> 00:15:25.629 align:start position:0% audit circuits very well um and for MPC fhe<00:15:23.720> this<00:15:23.800> is<00:15:24.040> maybe<00:15:24.600> becoming<00:15:25.079> more<00:15:25.320> of<00:15:25.519> like 00:15:25.629 --> 00:15:25.639 align:start position:0% fhe this is maybe becoming more of like 00:15:25.639 --> 00:15:27.870 align:start position:0% fhe this is maybe becoming more of like a<00:15:25.759> nent<00:15:26.240> thing<00:15:26.839> so<00:15:27.079> we'll<00:15:27.279> see<00:15:27.519> how<00:15:27.680> that 00:15:27.870 --> 00:15:27.880 align:start position:0% a nent thing so we'll see how that 00:15:27.880 --> 00:15:29.670 align:start position:0% a nent thing so we'll see how that progresses<00:15:28.680> I<00:15:28.800> think<00:15:29.120> there<00:15:29.199> are<00:15:29.399> certain 00:15:29.670 --> 00:15:29.680 align:start position:0% progresses I think there are certain 00:15:29.680 --> 00:15:32.389 align:start position:0% progresses I think there are certain things<00:15:29.959> you<00:15:30.160> can<00:15:30.360> do<00:15:30.759> to<00:15:31.000> make<00:15:31.360> MPC<00:15:31.800> FHA<00:15:32.199> more 00:15:32.389 --> 00:15:32.399 align:start position:0% things you can do to make MPC FHA more 00:15:32.399 --> 00:15:35.030 align:start position:0% things you can do to make MPC FHA more secure<00:15:33.319> one<00:15:33.759> way<00:15:33.920> to<00:15:34.040> look<00:15:34.199> at<00:15:34.360> it<00:15:34.600> is<00:15:34.800> there's 00:15:35.030 --> 00:15:35.040 align:start position:0% secure one way to look at it is there's 00:15:35.040 --> 00:15:36.790 align:start position:0% secure one way to look at it is there's this<00:15:35.240> notion<00:15:35.600> of<00:15:35.839> Direct<00:15:36.120> Security<00:15:36.519> versus 00:15:36.790 --> 00:15:36.800 align:start position:0% this notion of Direct Security versus 00:15:36.800 --> 00:15:40.269 align:start position:0% this notion of Direct Security versus delegated<00:15:37.360> Security<00:15:37.759> in<00:15:37.959> NPC<00:15:38.959> so<00:15:39.720> delegated 00:15:40.269 --> 00:15:40.279 align:start position:0% delegated Security in NPC so delegated 00:15:40.279 --> 00:15:42.069 align:start position:0% delegated Security in NPC so delegated security<00:15:40.720> is<00:15:40.880> when<00:15:41.079> you<00:15:41.319> take<00:15:41.519> your<00:15:41.759> private 00:15:42.069 --> 00:15:42.079 align:start position:0% security is when you take your private 00:15:42.079 --> 00:15:43.949 align:start position:0% security is when you take your private data<00:15:42.639> and<00:15:42.720> you<00:15:42.839> split<00:15:43.120> it<00:15:43.240> up<00:15:43.480> and<00:15:43.560> you<00:15:43.680> give<00:15:43.839> it 00:15:43.949 --> 00:15:43.959 align:start position:0% data and you split it up and you give it 00:15:43.959 --> 00:15:45.990 align:start position:0% data and you split it up and you give it to<00:15:44.160> all<00:15:44.279> the<00:15:44.399> NPC<00:15:44.800> parties<00:15:45.319> and<00:15:45.440> they<00:15:45.560> run<00:15:45.800> this 00:15:45.990 --> 00:15:46.000 align:start position:0% to all the NPC parties and they run this 00:15:46.000 --> 00:15:48.110 align:start position:0% to all the NPC parties and they run this computation<00:15:46.880> versus<00:15:47.240> Direct<00:15:47.560> Security<00:15:47.959> is 00:15:48.110 --> 00:15:48.120 align:start position:0% computation versus Direct Security is 00:15:48.120 --> 00:15:49.269 align:start position:0% computation versus Direct Security is you<00:15:48.279> are<00:15:48.480> actually<00:15:48.720> running<00:15:49.079> this 00:15:49.269 --> 00:15:49.279 align:start position:0% you are actually running this 00:15:49.279 --> 00:15:51.150 align:start position:0% you are actually running this computation<00:15:49.800> yourself<00:15:50.480> and<00:15:50.600> you<00:15:50.720> are<00:15:50.920> one<00:15:51.040> of 00:15:51.150 --> 00:15:51.160 align:start position:0% computation yourself and you are one of 00:15:51.160 --> 00:15:53.269 align:start position:0% computation yourself and you are one of the<00:15:51.319> parties<00:15:52.079> when<00:15:52.319> you<00:15:52.639> actually<00:15:53.079> want<00:15:53.199> to 00:15:53.269 --> 00:15:53.279 align:start position:0% the parties when you actually want to 00:15:53.279 --> 00:15:54.990 align:start position:0% the parties when you actually want to run<00:15:53.519> compute<00:15:53.839> over<00:15:54.000> your<00:15:54.120> own<00:15:54.319> data<00:15:54.880> and 00:15:54.990 --> 00:15:55.000 align:start position:0% run compute over your own data and 00:15:55.000 --> 00:15:56.509 align:start position:0% run compute over your own data and that's<00:15:55.160> like<00:15:55.240> a<00:15:55.360> simple<00:15:55.639> way<00:15:55.759> to<00:15:55.920> say<00:15:56.199> oh<00:15:56.360> it's 00:15:56.509 --> 00:15:56.519 align:start position:0% that's like a simple way to say oh it's 00:15:56.519 --> 00:15:57.790 align:start position:0% that's like a simple way to say oh it's your<00:15:56.639> own<00:15:56.839> data<00:15:57.120> you<00:15:57.240> should<00:15:57.399> be<00:15:57.480> a<00:15:57.560> part<00:15:57.680> of 00:15:57.790 --> 00:15:57.800 align:start position:0% your own data you should be a part of 00:15:57.800 --> 00:15:59.150 align:start position:0% your own data you should be a part of the<00:15:57.920> computation<00:15:58.480> and<00:15:58.600> I<00:15:58.680> think<00:15:59.040> that 00:15:59.150 --> 00:15:59.160 align:start position:0% the computation and I think that 00:15:59.160 --> 00:16:01.470 align:start position:0% the computation and I think that simplifies<00:16:00.160> part<00:16:00.319> of<00:16:00.519> the<00:16:00.680> equation<00:16:01.120> or<00:16:01.279> some 00:16:01.470 --> 00:16:01.480 align:start position:0% simplifies part of the equation or some 00:16:01.480 --> 00:16:03.269 align:start position:0% simplifies part of the equation or some of<00:16:01.600> the<00:16:01.720> threat<00:16:02.000> assumptions<00:16:02.800> but<00:16:02.959> I<00:16:03.079> think 00:16:03.269 --> 00:16:03.279 align:start position:0% of the threat assumptions but I think 00:16:03.279 --> 00:16:05.350 align:start position:0% of the threat assumptions but I think for<00:16:03.560> for<00:16:03.720> MPC<00:16:04.160> MPG<00:16:04.519> as<00:16:04.600> a<00:16:04.720> whole<00:16:04.920> like<00:16:05.199> we're 00:16:05.350 --> 00:16:05.360 align:start position:0% for for MPC MPG as a whole like we're 00:16:05.360 --> 00:16:07.509 align:start position:0% for for MPC MPG as a whole like we're still<00:16:05.600> trying<00:16:05.800> to<00:16:05.920> work<00:16:06.120> this 00:16:07.509 --> 00:16:07.519 align:start position:0% still trying to work this 00:16:07.519 --> 00:16:10.309 align:start position:0% still trying to work this out<00:16:08.519> maybe<00:16:08.880> I<00:16:09.000> can<00:16:09.199> add<00:16:09.440> something<00:16:09.720> on<00:16:10.040> like<00:16:10.199> I 00:16:10.309 --> 00:16:10.319 align:start position:0% out maybe I can add something on like I 00:16:10.319 --> 00:16:12.389 align:start position:0% out maybe I can add something on like I think<00:16:10.480> you<00:16:10.800> talked<00:16:11.279> very<00:16:11.519> nicely<00:16:11.880> about<00:16:12.120> the 00:16:12.389 --> 00:16:12.399 align:start position:0% think you talked very nicely about the 00:16:12.399 --> 00:16:14.509 align:start position:0% think you talked very nicely about the composability<00:16:12.839> but<00:16:13.319> maybe<00:16:13.560> I<00:16:13.639> can<00:16:13.759> try<00:16:13.920> to<00:16:14.079> say 00:16:14.509 --> 00:16:14.519 align:start position:0% composability but maybe I can try to say 00:16:14.519 --> 00:16:17.430 align:start position:0% composability but maybe I can try to say how<00:16:14.839> this<00:16:15.160> translates<00:16:15.800> to<00:16:16.079> users<00:16:17.079> and<00:16:17.199> I<00:16:17.279> think 00:16:17.430 --> 00:16:17.440 align:start position:0% how this translates to users and I think 00:16:17.440 --> 00:16:20.269 align:start position:0% how this translates to users and I think to<00:16:17.759> end<00:16:18.120> users<00:16:18.519> in<00:16:18.720> particular<00:16:19.639> like<00:16:19.839> now<00:16:20.160> we 00:16:20.269 --> 00:16:20.279 align:start position:0% to end users in particular like now we 00:16:20.279 --> 00:16:22.110 align:start position:0% to end users in particular like now we start<00:16:20.519> to<00:16:20.680> hear<00:16:20.959> that<00:16:21.160> like<00:16:21.399> oh<00:16:21.639> people<00:16:21.920> do 00:16:22.110 --> 00:16:22.120 align:start position:0% start to hear that like oh people do 00:16:22.120 --> 00:16:24.430 align:start position:0% start to hear that like oh people do start<00:16:22.360> to<00:16:22.519> care<00:16:22.720> about<00:16:23.040> privacy<00:16:23.720> and<00:16:24.040> like 00:16:24.430 --> 00:16:24.440 align:start position:0% start to care about privacy and like 00:16:24.440 --> 00:16:26.590 align:start position:0% start to care about privacy and like okay<00:16:24.720> yeah<00:16:24.920> we<00:16:25.040> do<00:16:25.199> have<00:16:25.360> stuff<00:16:25.560> to<00:16:25.759> hide<00:16:26.360> so 00:16:26.590 --> 00:16:26.600 align:start position:0% okay yeah we do have stuff to hide so 00:16:26.600 --> 00:16:28.629 align:start position:0% okay yeah we do have stuff to hide so people<00:16:26.839> do<00:16:27.160> start<00:16:27.399> to<00:16:27.600> feel<00:16:28.120> something<00:16:28.440> about 00:16:28.629 --> 00:16:28.639 align:start position:0% people do start to feel something about 00:16:28.639 --> 00:16:31.550 align:start position:0% people do start to feel something about privacy<00:16:29.120> y<00:16:29.279> but<00:16:29.399> I<00:16:29.519> think<00:16:30.000> they<00:16:30.480> really<00:16:30.880> don't 00:16:31.550 --> 00:16:31.560 align:start position:0% privacy y but I think they really don't 00:16:31.560 --> 00:16:33.509 align:start position:0% privacy y but I think they really don't understand<00:16:31.959> like<00:16:32.360> the<00:16:32.519> Nuance<00:16:32.959> or<00:16:33.120> even<00:16:33.319> the 00:16:33.509 --> 00:16:33.519 align:start position:0% understand like the Nuance or even the 00:16:33.519 --> 00:16:35.710 align:start position:0% understand like the Nuance or even the language<00:16:33.880> around<00:16:34.160> it<00:16:34.319> so<00:16:34.560> like<00:16:34.720> explaining<00:16:35.240> to 00:16:35.710 --> 00:16:35.720 align:start position:0% language around it so like explaining to 00:16:35.720 --> 00:16:37.670 align:start position:0% language around it so like explaining to end<00:16:36.079> users<00:16:36.480> like<00:16:36.680> consumers<00:16:37.279> that<00:16:37.480> we're 00:16:37.670 --> 00:16:37.680 align:start position:0% end users like consumers that we're 00:16:37.680 --> 00:16:40.030 align:start position:0% end users like consumers that we're talking<00:16:38.000> about<00:16:38.279> now<00:16:39.160> is 00:16:40.030 --> 00:16:40.040 align:start position:0% talking about now is 00:16:40.040 --> 00:16:43.949 align:start position:0% talking about now is just<00:16:41.040> hard<00:16:41.560> and<00:16:41.800> like<00:16:42.279> uh<00:16:42.959> but<00:16:43.160> even<00:16:43.560> like<00:16:43.720> for 00:16:43.949 --> 00:16:43.959 align:start position:0% just hard and like uh but even like for 00:16:43.959 --> 00:16:46.350 align:start position:0% just hard and like uh but even like for us<00:16:44.240> now<00:16:44.680> we<00:16:45.000> start<00:16:45.360> to<00:16:45.600> kind<00:16:45.720> of<00:16:45.839> onboard 00:16:46.350 --> 00:16:46.360 align:start position:0% us now we start to kind of onboard 00:16:46.360 --> 00:16:48.590 align:start position:0% us now we start to kind of onboard developers<00:16:46.920> to<00:16:47.079> use<00:16:47.319> MPC<00:16:47.800> Tooling<00:16:48.199> in<00:16:48.360> the 00:16:48.590 --> 00:16:48.600 align:start position:0% developers to use MPC Tooling in the 00:16:48.600 --> 00:16:52.030 align:start position:0% developers to use MPC Tooling in the network<00:16:49.600> and<00:16:49.720> it's<00:16:49.959> like<00:16:50.360> even<00:16:50.639> to<00:16:51.040> developers 00:16:52.030 --> 00:16:52.040 align:start position:0% network and it's like even to developers 00:16:52.040 --> 00:16:53.870 align:start position:0% network and it's like even to developers it's<00:16:52.319> really<00:16:52.600> hard<00:16:52.880> to<00:16:53.040> explain<00:16:53.440> and<00:16:53.560> I<00:16:53.680> think 00:16:53.870 --> 00:16:53.880 align:start position:0% it's really hard to explain and I think 00:16:53.880 --> 00:16:56.269 align:start position:0% it's really hard to explain and I think a<00:16:54.000> lot<00:16:54.120> of<00:16:54.279> developers<00:16:54.920> even<00:16:55.279> have<00:16:55.600> like<00:16:55.800> a<00:16:56.079> lot 00:16:56.269 --> 00:16:56.279 align:start position:0% a lot of developers even have like a lot 00:16:56.279 --> 00:16:59.470 align:start position:0% a lot of developers even have like a lot of<00:16:57.079> confusion<00:16:58.079> around<00:16:58.360> the<00:16:58.519> security 00:16:59.470 --> 00:16:59.480 align:start position:0% of confusion around the security 00:16:59.480 --> 00:17:02.069 align:start position:0% of confusion around the security assumptions<00:17:00.480> and<00:17:01.000> like<00:17:01.199> it's<00:17:01.720> actually<00:17:02.000> a 00:17:02.069 --> 00:17:02.079 align:start position:0% assumptions and like it's actually a 00:17:02.079 --> 00:17:04.750 align:start position:0% assumptions and like it's actually a little<00:17:02.279> bit<00:17:02.480> worrying<00:17:03.240> and<00:17:03.600> I<00:17:03.880> so<00:17:04.120> like<00:17:04.319> we<00:17:04.559> and 00:17:04.750 --> 00:17:04.760 align:start position:0% little bit worrying and I so like we and 00:17:04.760 --> 00:17:06.789 align:start position:0% little bit worrying and I so like we and as<00:17:04.839> you<00:17:04.959> said<00:17:05.199> like<00:17:05.319> there's<00:17:05.559> no<00:17:06.000> auditing<00:17:06.640> and 00:17:06.789 --> 00:17:06.799 align:start position:0% as you said like there's no auditing and 00:17:06.799 --> 00:17:09.829 align:start position:0% as you said like there's no auditing and like<00:17:06.959> this<00:17:07.199> little<00:17:07.919> sort<00:17:08.120> of<00:17:08.360> support<00:17:09.199> to<00:17:09.400> for 00:17:09.829 --> 00:17:09.839 align:start position:0% like this little sort of support to for 00:17:09.839 --> 00:17:12.470 align:start position:0% like this little sort of support to for security<00:17:10.439> in<00:17:10.600> MPC<00:17:11.079> and<00:17:11.199> FHA<00:17:11.640> and<00:17:11.799> the<00:17:11.959> slight 00:17:12.470 --> 00:17:12.480 align:start position:0% security in MPC and FHA and the slight 00:17:12.480 --> 00:17:15.029 align:start position:0% security in MPC and FHA and the slight slightly<00:17:12.799> more<00:17:12.959> advanced<00:17:13.520> Primitives<00:17:14.520> so<00:17:14.919> at 00:17:15.029 --> 00:17:15.039 align:start position:0% slightly more advanced Primitives so at 00:17:15.039 --> 00:17:18.029 align:start position:0% slightly more advanced Primitives so at least<00:17:15.480> we<00:17:16.480> talk<00:17:16.839> a<00:17:17.000> lot<00:17:17.280> I<00:17:17.319> mean<00:17:17.559> like<00:17:17.760> all<00:17:17.880> of 00:17:18.029 --> 00:17:18.039 align:start position:0% least we talk a lot I mean like all of 00:17:18.039 --> 00:17:21.309 align:start position:0% least we talk a lot I mean like all of us<00:17:18.240> talk<00:17:18.480> a<00:17:19.120> lot<00:17:20.120> um<00:17:20.240> to<00:17:20.439> each<00:17:20.600> other<00:17:21.039> about 00:17:21.309 --> 00:17:21.319 align:start position:0% us talk a lot um to each other about 00:17:21.319 --> 00:17:22.990 align:start position:0% us talk a lot um to each other about like<00:17:21.520> okay<00:17:21.720> are<00:17:21.839> we<00:17:22.000> right<00:17:22.160> in<00:17:22.319> thinking<00:17:22.720> this 00:17:22.990 --> 00:17:23.000 align:start position:0% like okay are we right in thinking this 00:17:23.000 --> 00:17:24.630 align:start position:0% like okay are we right in thinking this and<00:17:23.240> like<00:17:23.520> with<00:17:23.640> you<00:17:23.919> I<00:17:24.000> was<00:17:24.160> talking<00:17:24.439> about 00:17:24.630 --> 00:17:24.640 align:start position:0% and like with you I was talking about 00:17:24.640 --> 00:17:26.150 align:start position:0% and like with you I was talking about private<00:17:24.919> proof<00:17:25.199> delegation<00:17:25.720> and<00:17:25.880> I<00:17:26.000> was 00:17:26.150 --> 00:17:26.160 align:start position:0% private proof delegation and I was 00:17:26.160 --> 00:17:27.870 align:start position:0% private proof delegation and I was saying<00:17:26.439> like<00:17:26.679> Okay<00:17:26.880> just<00:17:27.280> Outsource 00:17:27.870 --> 00:17:27.880 align:start position:0% saying like Okay just Outsource 00:17:27.880 --> 00:17:29.230 align:start position:0% saying like Okay just Outsource everything<00:17:28.240> and<00:17:28.360> you<00:17:28.439> were<00:17:28.600> like<00:17:28.960> okay<00:17:29.080> no 00:17:29.230 --> 00:17:29.240 align:start position:0% everything and you were like okay no 00:17:29.240 --> 00:17:30.830 align:start position:0% everything and you were like okay no we're<00:17:29.440> happy<00:17:29.640> to<00:17:29.760> Outsource<00:17:30.240> some<00:17:30.480> stuff 00:17:30.830 --> 00:17:30.840 align:start position:0% we're happy to Outsource some stuff 00:17:30.840 --> 00:17:32.390 align:start position:0% we're happy to Outsource some stuff maybe<00:17:31.360> but<00:17:31.600> like<00:17:31.799> if<00:17:31.919> there's<00:17:32.160> like<00:17:32.280> a 00:17:32.390 --> 00:17:32.400 align:start position:0% maybe but like if there's like a 00:17:32.400 --> 00:17:33.909 align:start position:0% maybe but like if there's like a whistleblower<00:17:33.039> or<00:17:33.200> something<00:17:33.600> that's<00:17:33.799> you 00:17:33.909 --> 00:17:33.919 align:start position:0% whistleblower or something that's you 00:17:33.919 --> 00:17:37.029 align:start position:0% whistleblower or something that's you know<00:17:34.480> particularly<00:17:35.480> sensitive<00:17:36.120> or<00:17:36.600> you<00:17:36.720> know 00:17:37.029 --> 00:17:37.039 align:start position:0% know particularly sensitive or you know 00:17:37.039 --> 00:17:38.710 align:start position:0% know particularly sensitive or you know then<00:17:37.360> know<00:17:37.799> like<00:17:38.080> everything<00:17:38.320> needs<00:17:38.520> to<00:17:38.640> be 00:17:38.710 --> 00:17:38.720 align:start position:0% then know like everything needs to be 00:17:38.720 --> 00:17:40.990 align:start position:0% then know like everything needs to be done<00:17:39.000> client<00:17:39.400> side<00:17:39.679> so<00:17:40.440> I<00:17:40.520> think<00:17:40.720> having 00:17:40.990 --> 00:17:41.000 align:start position:0% done client side so I think having 00:17:41.000 --> 00:17:43.070 align:start position:0% done client side so I think having conversations<00:17:41.640> amongst<00:17:42.000> each<00:17:42.160> other<00:17:42.559> to<00:17:42.840> like 00:17:43.070 --> 00:17:43.080 align:start position:0% conversations amongst each other to like 00:17:43.080 --> 00:17:45.870 align:start position:0% conversations amongst each other to like raise<00:17:43.480> the<00:17:43.720> general<00:17:44.240> bar<00:17:44.559> of<00:17:44.799> Education<00:17:45.640> like 00:17:45.870 --> 00:17:45.880 align:start position:0% raise the general bar of Education like 00:17:45.880 --> 00:17:47.470 align:start position:0% raise the general bar of Education like e<00:17:46.120> either<00:17:46.360> amongst<00:17:46.720> consumers<00:17:47.200> and<00:17:47.360> the 00:17:47.470 --> 00:17:47.480 align:start position:0% e either amongst consumers and the 00:17:47.480 --> 00:17:49.630 align:start position:0% e either amongst consumers and the developers<00:17:47.960> and<00:17:48.160> like<00:17:48.320> the<00:17:48.440> researchers<00:17:48.960> and 00:17:49.630 --> 00:17:49.640 align:start position:0% developers and like the researchers and 00:17:49.640 --> 00:17:52.350 align:start position:0% developers and like the researchers and everyone<00:17:50.640> um<00:17:51.200> yeah<00:17:51.440> generally<00:17:51.840> just<00:17:52.039> raising 00:17:52.350 --> 00:17:52.360 align:start position:0% everyone um yeah generally just raising 00:17:52.360 --> 00:17:54.070 align:start position:0% everyone um yeah generally just raising the<00:17:52.480> level<00:17:52.679> of<00:17:52.840> Education<00:17:53.240> I<00:17:53.320> think<00:17:53.480> is<00:17:53.640> good 00:17:54.070 --> 00:17:54.080 align:start position:0% the level of Education I think is good 00:17:54.080 --> 00:17:57.230 align:start position:0% the level of Education I think is good and<00:17:54.280> that's<00:17:54.559> what<00:17:54.840> we<00:17:55.080> do<00:17:55.600> and<00:17:55.760> try<00:17:55.960> to<00:17:56.679> yeah 00:17:57.230 --> 00:17:57.240 align:start position:0% and that's what we do and try to yeah 00:17:57.240 --> 00:18:00.270 align:start position:0% and that's what we do and try to yeah inform<00:17:57.679> each<00:17:57.840> other 00:18:00.270 --> 00:18:00.280 align:start position:0% inform each other 00:18:00.280 --> 00:18:03.310 align:start position:0% inform each other I<00:18:00.440> love<00:18:00.760> that<00:18:01.320> I<00:18:01.440> think<00:18:01.880> a<00:18:02.039> lot<00:18:02.240> of<00:18:02.720> since<00:18:03.039> we're 00:18:03.310 --> 00:18:03.320 align:start position:0% I love that I think a lot of since we're 00:18:03.320 --> 00:18:05.430 align:start position:0% I love that I think a lot of since we're building<00:18:03.640> at<00:18:03.799> a<00:18:03.960> very<00:18:04.200> early<00:18:04.559> stage<00:18:05.039> a<00:18:05.120> lot<00:18:05.280> of 00:18:05.430 --> 00:18:05.440 align:start position:0% building at a very early stage a lot of 00:18:05.440 --> 00:18:07.549 align:start position:0% building at a very early stage a lot of it<00:18:05.600> is<00:18:05.799> about<00:18:06.120> talking<00:18:06.440> to<00:18:06.600> each<00:18:06.840> other<00:18:07.320> and 00:18:07.549 --> 00:18:07.559 align:start position:0% it is about talking to each other and 00:18:07.559 --> 00:18:10.470 align:start position:0% it is about talking to each other and communicating<00:18:08.400> well<00:18:09.159> communicating<00:18:10.159> like<00:18:10.320> in 00:18:10.470 --> 00:18:10.480 align:start position:0% communicating well communicating like in 00:18:10.480 --> 00:18:14.230 align:start position:0% communicating well communicating like in an<00:18:10.720> intuitive<00:18:11.400> way<00:18:11.840> to<00:18:12.159> users<00:18:13.159> um<00:18:13.440> so<00:18:13.720> to<00:18:13.960> that 00:18:14.230 --> 00:18:14.240 align:start position:0% an intuitive way to users um so to that 00:18:14.240 --> 00:18:18.750 align:start position:0% an intuitive way to users um so to that and<00:18:15.000> I<00:18:15.280> I<00:18:15.400> want<00:18:15.640> to<00:18:16.640> sort<00:18:16.880> of<00:18:17.039> find<00:18:17.320> out<00:18:17.919> like 00:18:18.750 --> 00:18:18.760 align:start position:0% and I I want to sort of find out like 00:18:18.760 --> 00:18:20.630 align:start position:0% and I I want to sort of find out like some<00:18:19.159> practical<00:18:19.720> insights<00:18:20.280> that<00:18:20.400> you've 00:18:20.630 --> 00:18:20.640 align:start position:0% some practical insights that you've 00:18:20.640 --> 00:18:23.190 align:start position:0% some practical insights that you've gained<00:18:21.080> from<00:18:21.280> your<00:18:21.600> experiences<00:18:22.559> deploying 00:18:23.190 --> 00:18:23.200 align:start position:0% gained from your experiences deploying 00:18:23.200 --> 00:18:26.470 align:start position:0% gained from your experiences deploying these<00:18:23.440> apps<00:18:23.760> in<00:18:23.919> the<00:18:24.120> wild<00:18:24.840> so<00:18:25.440> by<00:18:25.760> practical<00:18:26.400> I 00:18:26.470 --> 00:18:26.480 align:start position:0% these apps in the wild so by practical I 00:18:26.480 --> 00:18:29.110 align:start position:0% these apps in the wild so by practical I mean<00:18:26.919> like<00:18:27.840> insights<00:18:28.320> that<00:18:28.400> you<00:18:28.520> could<00:18:28.880> not 00:18:29.110 --> 00:18:29.120 align:start position:0% mean like insights that you could not 00:18:29.120 --> 00:18:32.390 align:start position:0% mean like insights that you could not have<00:18:29.320> gained<00:18:29.720> from<00:18:30.039> like<00:18:30.640> just<00:18:31.120> writing<00:18:32.120> a 00:18:32.390 --> 00:18:32.400 align:start position:0% have gained from like just writing a 00:18:32.400 --> 00:18:36.750 align:start position:0% have gained from like just writing a white<00:18:32.760> paper<00:18:33.760> um<00:18:34.280> just<00:18:34.679> implementing<00:18:35.320> it<00:18:35.760> on 00:18:36.750 --> 00:18:36.760 align:start position:0% white paper um just implementing it on 00:18:36.760 --> 00:18:40.549 align:start position:0% white paper um just implementing it on in<00:18:36.840> a<00:18:37.039> hackathon<00:18:38.039> for<00:18:38.320> example<00:18:39.320> um<00:18:40.039> ux 00:18:40.549 --> 00:18:40.559 align:start position:0% in a hackathon for example um ux 00:18:40.559 --> 00:18:43.590 align:start position:0% in a hackathon for example um ux features<00:18:41.000> like<00:18:41.120> I<00:18:41.360> use<00:18:42.200> um<00:18:42.480> making<00:18:42.760> it<00:18:42.960> clear 00:18:43.590 --> 00:18:43.600 align:start position:0% features like I use um making it clear 00:18:43.600 --> 00:18:45.750 align:start position:0% features like I use um making it clear to<00:18:43.760> the<00:18:43.880> users<00:18:44.320> that<00:18:44.480> they<00:18:44.600> can<00:18:44.840> control<00:18:45.559> the 00:18:45.750 --> 00:18:45.760 align:start position:0% to the users that they can control the 00:18:45.760 --> 00:18:50.510 align:start position:0% to the users that they can control the set<00:18:45.960> of<00:18:46.120> De<00:18:46.520> key<00:18:46.919> stes<00:18:47.919> um<00:18:48.400> so<00:18:48.799> like<00:18:49.000> ux<00:18:49.600> prompts 00:18:50.510 --> 00:18:50.520 align:start position:0% set of De key stes um so like ux prompts 00:18:50.520 --> 00:18:53.750 align:start position:0% set of De key stes um so like ux prompts how<00:18:50.919> these<00:18:51.280> Q<00:18:51.880> behaviors<00:18:52.640> in<00:18:52.880> users<00:18:53.559> I'm 00:18:53.750 --> 00:18:53.760 align:start position:0% how these Q behaviors in users I'm 00:18:53.760 --> 00:18:57.230 align:start position:0% how these Q behaviors in users I'm interested<00:18:54.120> in<00:18:54.360> that<00:18:55.159> and<00:18:55.760> um<00:18:56.360> I'm<00:18:56.799> also 00:18:57.230 --> 00:18:57.240 align:start position:0% interested in that and um I'm also 00:18:57.240 --> 00:19:02.630 align:start position:0% interested in that and um I'm also interested<00:18:57.760> in<00:18:58.320> s<00:18:58.880> of<00:18:59.280> how<00:18:59.960> we<00:19:00.360> compensate<00:19:01.640> for 00:19:02.630 --> 00:19:02.640 align:start position:0% interested in s of how we compensate for 00:19:02.640 --> 00:19:06.750 align:start position:0% interested in s of how we compensate for the<00:19:02.840> ux<00:19:03.400> hit<00:19:03.880> so<00:19:04.159> a<00:19:04.280> lot<00:19:04.440> of<00:19:04.760> these<00:19:05.400> apps<00:19:06.400> um 00:19:06.750 --> 00:19:06.760 align:start position:0% the ux hit so a lot of these apps um 00:19:06.760 --> 00:19:09.669 align:start position:0% the ux hit so a lot of these apps um they<00:19:06.919> involve<00:19:07.320> heavy<00:19:07.679> computations<00:19:08.679> right<00:19:09.559> uh 00:19:09.669 --> 00:19:09.679 align:start position:0% they involve heavy computations right uh 00:19:09.679 --> 00:19:11.590 align:start position:0% they involve heavy computations right uh for<00:19:09.880> example<00:19:10.200> making<00:19:10.480> a<00:19:10.600> ZK<00:19:11.000> proof<00:19:11.400> for 00:19:11.590 --> 00:19:11.600 align:start position:0% for example making a ZK proof for 00:19:11.600 --> 00:19:13.830 align:start position:0% for example making a ZK proof for example<00:19:11.960> having<00:19:12.159> to<00:19:12.320> be<00:19:12.520> online<00:19:13.320> for<00:19:13.440> a<00:19:13.600> long 00:19:13.830 --> 00:19:13.840 align:start position:0% example having to be online for a long 00:19:13.840 --> 00:19:17.630 align:start position:0% example having to be online for a long time<00:19:14.320> um<00:19:14.400> for<00:19:14.640> the<00:19:14.799> MPC<00:19:15.440> or<00:19:16.120> FH<00:19:17.120> well<00:19:17.320> not<00:19:17.480> for 00:19:17.630 --> 00:19:17.640 align:start position:0% time um for the MPC or FH well not for 00:19:17.640 --> 00:19:21.510 align:start position:0% time um for the MPC or FH well not for FH<00:19:18.480> but<00:19:18.760> yeah<00:19:19.679> um<00:19:20.200> so<00:19:20.559> having<00:19:20.880> to<00:19:21.080> wait<00:19:21.280> for<00:19:21.400> a 00:19:21.510 --> 00:19:21.520 align:start position:0% FH but yeah um so having to wait for a 00:19:21.520 --> 00:19:23.990 align:start position:0% FH but yeah um so having to wait for a long<00:19:21.720> time<00:19:21.919> be<00:19:22.039> online<00:19:22.360> for<00:19:22.480> a<00:19:22.559> long<00:19:22.840> time<00:19:23.360> like 00:19:23.990 --> 00:19:24.000 align:start position:0% long time be online for a long time like 00:19:24.000 --> 00:19:26.789 align:start position:0% long time be online for a long time like these<00:19:24.200> are<00:19:25.000> ux<00:19:25.520> hits<00:19:25.840> that<00:19:26.000> we<00:19:26.159> have<00:19:26.280> to<00:19:26.480> take 00:19:26.789 --> 00:19:26.799 align:start position:0% these are ux hits that we have to take 00:19:26.799 --> 00:19:29.430 align:start position:0% these are ux hits that we have to take how<00:19:27.400> how<00:19:27.559> have<00:19:27.679> you<00:19:27.799> been<00:19:28.000> dealing<00:19:28.320> with<00:19:28.480> this 00:19:29.430 --> 00:19:29.440 align:start position:0% how how have you been dealing with this 00:19:29.440 --> 00:19:32.510 align:start position:0% how how have you been dealing with this so<00:19:29.799> that's<00:19:29.960> on<00:19:30.080> the<00:19:30.240> ux<00:19:30.760> site<00:19:31.480> and<00:19:31.640> then<00:19:32.080> I'm 00:19:32.510 --> 00:19:32.520 align:start position:0% so that's on the ux site and then I'm 00:19:32.520 --> 00:19:35.149 align:start position:0% so that's on the ux site and then I'm also<00:19:32.840> interested<00:19:33.600> like<00:19:33.799> on<00:19:33.960> the<00:19:34.159> infra<00:19:34.760> site 00:19:35.149 --> 00:19:35.159 align:start position:0% also interested like on the infra site 00:19:35.159 --> 00:19:38.029 align:start position:0% also interested like on the infra site like<00:19:35.520> actually<00:19:36.520> what<00:19:37.120> what<00:19:37.200> are<00:19:37.360> the<00:19:37.520> INF 00:19:38.029 --> 00:19:38.039 align:start position:0% like actually what what are the INF 00:19:38.039 --> 00:19:40.190 align:start position:0% like actually what what are the INF requirements<00:19:38.880> like<00:19:39.200> what<00:19:39.520> difficulties<00:19:40.039> have 00:19:40.190 --> 00:19:40.200 align:start position:0% requirements like what difficulties have 00:19:40.200 --> 00:19:46.549 align:start position:0% requirements like what difficulties have you<00:19:40.360> run<00:19:40.960> into<00:19:41.960> um 00:19:46.549 --> 00:19:46.559 align:start position:0% 00:19:46.559 --> 00:19:50.510 align:start position:0% yeah<00:19:47.559> let's<00:19:47.840> go<00:19:48.320> let's<00:19:48.520> do<00:19:48.720> the<00:19:48.960> U<00:19:49.559> stuff<00:19:49.960> first 00:19:50.510 --> 00:19:50.520 align:start position:0% yeah let's go let's do the U stuff first 00:19:50.520 --> 00:19:53.909 align:start position:0% yeah let's go let's do the U stuff first like<00:19:51.400> so<00:19:52.039> like<00:19:52.520> what<00:19:52.919> interesting<00:19:53.480> user 00:19:53.909 --> 00:19:53.919 align:start position:0% like so like what interesting user 00:19:53.919 --> 00:19:56.909 align:start position:0% like so like what interesting user behaviors<00:19:54.559> have<00:19:54.679> you<00:19:54.960> observed<00:19:55.960> um<00:19:56.480> what<00:19:56.679> sort 00:19:56.909 --> 00:19:56.919 align:start position:0% behaviors have you observed um what sort 00:19:56.919 --> 00:20:00.990 align:start position:0% behaviors have you observed um what sort of<00:19:57.120> ux<00:19:57.679> prompts<00:19:58.240> ux<00:19:58.960> patterns<00:19:59.720> have<00:19:59.840> you<00:20:00.039> found 00:20:00.990 --> 00:20:01.000 align:start position:0% of ux prompts ux patterns have you found 00:20:01.000 --> 00:20:05.390 align:start position:0% of ux prompts ux patterns have you found useful<00:20:02.000> and<00:20:02.520> um<00:20:02.960> how<00:20:03.679> do<00:20:03.880> you<00:20:04.320> compensate<00:20:04.960> for 00:20:05.390 --> 00:20:05.400 align:start position:0% useful and um how do you compensate for 00:20:05.400 --> 00:20:08.390 align:start position:0% useful and um how do you compensate for like<00:20:05.559> the<00:20:05.720> ux<00:20:06.280> hit<00:20:06.720> the<00:20:06.880> performance<00:20:07.400> hit<00:20:07.919> in 00:20:08.390 --> 00:20:08.400 align:start position:0% like the ux hit the performance hit in 00:20:08.400 --> 00:20:10.950 align:start position:0% like the ux hit the performance hit in these 00:20:10.950 --> 00:20:10.960 align:start position:0% 00:20:10.960 --> 00:20:17.270 align:start position:0% apps<00:20:11.960> okay<00:20:12.600> um<00:20:13.400> so<00:20:13.880> for<00:20:14.720> ZK<00:20:15.080> P2P<00:20:15.720> we<00:20:15.960> have<00:20:16.720> two 00:20:17.270 --> 00:20:17.280 align:start position:0% apps okay um so for ZK P2P we have two 00:20:17.280 --> 00:20:20.630 align:start position:0% apps okay um so for ZK P2P we have two flows<00:20:17.880> of<00:20:18.080> interacting<00:20:18.960> with<00:20:19.520> these<00:20:20.440> like 00:20:20.630 --> 00:20:20.640 align:start position:0% flows of interacting with these like 00:20:20.640 --> 00:20:23.190 align:start position:0% flows of interacting with these like cryptographic<00:20:21.280> Primitives<00:20:21.960> that<00:20:22.080> we<00:20:22.200> use<00:20:23.039> uh 00:20:23.190 --> 00:20:23.200 align:start position:0% cryptographic Primitives that we use uh 00:20:23.200 --> 00:20:26.110 align:start position:0% cryptographic Primitives that we use uh one<00:20:23.600> the<00:20:23.760> first<00:20:23.960> one<00:20:24.200> is<00:20:24.880> obviously<00:20:25.200> using<00:20:25.480> ZK 00:20:26.110 --> 00:20:26.120 align:start position:0% one the first one is obviously using ZK 00:20:26.120 --> 00:20:29.310 align:start position:0% one the first one is obviously using ZK email<00:20:27.120> um<00:20:28.039> I<00:20:28.120> think<00:20:28.280> the<00:20:28.400> main<00:20:28.679> main<00:20:28.960> thing 00:20:29.310 --> 00:20:29.320 align:start position:0% email um I think the main main thing 00:20:29.320 --> 00:20:31.950 align:start position:0% email um I think the main main thing about<00:20:29.960> using<00:20:30.280> ZK<00:20:30.679> email<00:20:31.080> is<00:20:31.280> trying<00:20:31.520> to<00:20:31.720> get 00:20:31.950 --> 00:20:31.960 align:start position:0% about using ZK email is trying to get 00:20:31.960 --> 00:20:36.110 align:start position:0% about using ZK email is trying to get that<00:20:32.159> email<00:20:32.919> in<00:20:33.039> your<00:20:33.440> inbox<00:20:34.440> um<00:20:34.840> to<00:20:35.840> yeah<00:20:36.000> to 00:20:36.110 --> 00:20:36.120 align:start position:0% that email in your inbox um to yeah to 00:20:36.120 --> 00:20:38.789 align:start position:0% that email in your inbox um to yeah to start<00:20:36.360> the<00:20:36.520> proof<00:20:36.799> generation<00:20:37.440> process<00:20:38.440> and 00:20:38.789 --> 00:20:38.799 align:start position:0% start the proof generation process and 00:20:38.799 --> 00:20:41.750 align:start position:0% start the proof generation process and that's<00:20:39.000> been<00:20:39.960> a<00:20:40.400> difficult<00:20:40.600> thing<00:20:41.120> to<00:20:41.320> resolve 00:20:41.750 --> 00:20:41.760 align:start position:0% that's been a difficult thing to resolve 00:20:41.760 --> 00:20:44.310 align:start position:0% that's been a difficult thing to resolve you<00:20:41.880> could<00:20:42.600> basically<00:20:43.320> the<00:20:43.480> manual<00:20:43.880> way<00:20:44.080> is 00:20:44.310 --> 00:20:44.320 align:start position:0% you could basically the manual way is 00:20:44.320 --> 00:20:47.630 align:start position:0% you could basically the manual way is you<00:20:44.440> have<00:20:44.640> to<00:20:45.440> open<00:20:45.840> like<00:20:45.960> the<00:20:46.120> raw<00:20:46.440> email<00:20:47.440> uh 00:20:47.630 --> 00:20:47.640 align:start position:0% you have to open like the raw email uh 00:20:47.640 --> 00:20:49.870 align:start position:0% you have to open like the raw email uh copy<00:20:47.960> it<00:20:48.400> and<00:20:48.480> then<00:20:48.679> paste<00:20:48.919> it<00:20:49.080> into<00:20:49.280> the<00:20:49.400> UI 00:20:49.870 --> 00:20:49.880 align:start position:0% copy it and then paste it into the UI 00:20:49.880 --> 00:20:51.789 align:start position:0% copy it and then paste it into the UI and<00:20:50.000> then<00:20:50.240> click<00:20:50.400> a<00:20:50.520> button<00:20:50.760> to<00:20:51.159> run<00:20:51.360> the<00:20:51.520> proof 00:20:51.789 --> 00:20:51.799 align:start position:0% and then click a button to run the proof 00:20:51.799 --> 00:20:53.950 align:start position:0% and then click a button to run the proof generation<00:20:52.280> process<00:20:53.080> uh<00:20:53.159> so<00:20:53.320> we<00:20:53.520> basically 00:20:53.950 --> 00:20:53.960 align:start position:0% generation process uh so we basically 00:20:53.960 --> 00:20:57.789 align:start position:0% generation process uh so we basically built<00:20:54.760> uh<00:20:54.960> like<00:20:55.080> a<00:20:55.520> o<00:20:56.159> we<00:20:56.679> like<00:20:57.120> got<00:20:57.280> a<00:20:57.400> Gmail 00:20:57.789 --> 00:20:57.799 align:start position:0% built uh like a o we like got a Gmail 00:20:57.799 --> 00:21:01.470 align:start position:0% built uh like a o we like got a Gmail API<00:20:58.240> oath<00:20:58.679> flow<00:20:59.520> uh<00:20:59.720> that<00:20:59.840> will<00:21:00.080> basically<00:21:01.000> um 00:21:01.470 --> 00:21:01.480 align:start position:0% API oath flow uh that will basically um 00:21:01.480 --> 00:21:03.909 align:start position:0% API oath flow uh that will basically um yeah<00:21:01.640> o<00:21:01.840> off<00:21:02.000> into<00:21:02.200> your<00:21:02.360> inbox<00:21:03.360> uh<00:21:03.520> and<00:21:03.679> read 00:21:03.909 --> 00:21:03.919 align:start position:0% yeah o off into your inbox uh and read 00:21:03.919 --> 00:21:06.789 align:start position:0% yeah o off into your inbox uh and read the<00:21:04.200> email<00:21:05.200> and<00:21:05.600> but<00:21:06.039> uh<00:21:06.159> keeping<00:21:06.440> it 00:21:06.789 --> 00:21:06.799 align:start position:0% the email and but uh keeping it 00:21:06.799 --> 00:21:09.270 align:start position:0% the email and but uh keeping it completely<00:21:07.440> local<00:21:07.840> in<00:21:08.039> client<00:21:08.480> side<00:21:09.000> uh<00:21:09.080> to 00:21:09.270 --> 00:21:09.280 align:start position:0% completely local in client side uh to 00:21:09.280 --> 00:21:11.870 align:start position:0% completely local in client side uh to kick<00:21:09.440> off<00:21:09.600> the<00:21:09.720> proof<00:21:09.960> generation<00:21:10.679> process<00:21:11.679> um 00:21:11.870 --> 00:21:11.880 align:start position:0% kick off the proof generation process um 00:21:11.880 --> 00:21:14.230 align:start position:0% kick off the proof generation process um so<00:21:12.080> that<00:21:12.240> has<00:21:12.520> helped<00:21:12.919> with<00:21:13.080> ux<00:21:13.520> a<00:21:13.640> little<00:21:13.840> bit 00:21:14.230 --> 00:21:14.240 align:start position:0% so that has helped with ux a little bit 00:21:14.240 --> 00:21:16.230 align:start position:0% so that has helped with ux a little bit but<00:21:14.520> it's<00:21:14.960> obviously<00:21:15.360> like<00:21:15.480> a<00:21:15.600> workaround 00:21:16.230 --> 00:21:16.240 align:start position:0% but it's obviously like a workaround 00:21:16.240 --> 00:21:18.350 align:start position:0% but it's obviously like a workaround kind<00:21:16.360> of<00:21:16.559> thing<00:21:17.320> um<00:21:17.480> and<00:21:17.600> trying<00:21:17.840> to<00:21:18.039> smooth 00:21:18.350 --> 00:21:18.360 align:start position:0% kind of thing um and trying to smooth 00:21:18.360 --> 00:21:22.350 align:start position:0% kind of thing um and trying to smooth out<00:21:18.520> ux<00:21:18.960> things<00:21:19.880> and<00:21:20.720> also<00:21:21.520> uh<00:21:21.880> yeah<00:21:22.080> after 00:21:22.350 --> 00:21:22.360 align:start position:0% out ux things and also uh yeah after 00:21:22.360 --> 00:21:24.510 align:start position:0% out ux things and also uh yeah after getting<00:21:22.840> extracting<00:21:23.279> that<00:21:23.440> email<00:21:24.200> the<00:21:24.320> next 00:21:24.510 --> 00:21:24.520 align:start position:0% getting extracting that email the next 00:21:24.520 --> 00:21:26.390 align:start position:0% getting extracting that email the next step<00:21:24.720> is<00:21:24.880> obviously<00:21:25.240> Genera<00:21:25.640> that<00:21:25.799> proof 00:21:26.390 --> 00:21:26.400 align:start position:0% step is obviously Genera that proof 00:21:26.400 --> 00:21:28.310 align:start position:0% step is obviously Genera that proof themo<00:21:26.720> email<00:21:27.000> circuits<00:21:27.400> are<00:21:27.640> like<00:21:27.919> massive 00:21:28.310 --> 00:21:28.320 align:start position:0% themo email circuits are like massive 00:21:28.320 --> 00:21:31.110 align:start position:0% themo email circuits are like massive they<00:21:28.679> like<00:21:29.320> they<00:21:30.159> probably<00:21:30.400> will<00:21:30.600> take<00:21:30.799> like<00:21:30.880> 8 00:21:31.110 --> 00:21:31.120 align:start position:0% they like they probably will take like 8 00:21:31.120 --> 00:21:33.710 align:start position:0% they like they probably will take like 8 minutes<00:21:31.400> to<00:21:31.559> do<00:21:31.760> client<00:21:32.200> side<00:21:32.960> um<00:21:33.120> but<00:21:33.279> like<00:21:33.440> 20 00:21:33.710 --> 00:21:33.720 align:start position:0% minutes to do client side um but like 20 00:21:33.720 --> 00:21:36.669 align:start position:0% minutes to do client side um but like 20 seconds<00:21:34.080> to<00:21:34.240> do<00:21:34.720> on<00:21:34.880> the<00:21:35.039> server<00:21:35.919> um<00:21:36.080> so<00:21:36.320> we 00:21:36.669 --> 00:21:36.679 align:start position:0% seconds to do on the server um so we 00:21:36.679 --> 00:21:38.789 align:start position:0% seconds to do on the server um so we pass<00:21:36.880> it<00:21:37.000> all<00:21:37.200> through<00:21:37.640> the<00:21:37.799> server<00:21:38.400> and<00:21:38.559> so 00:21:38.789 --> 00:21:38.799 align:start position:0% pass it all through the server and so 00:21:38.799 --> 00:21:41.830 align:start position:0% pass it all through the server and so far<00:21:39.640> like<00:21:40.520> I<00:21:40.640> guess<00:21:40.799> all<00:21:40.919> of<00:21:41.039> our<00:21:41.200> users<00:21:41.600> are 00:21:41.830 --> 00:21:41.840 align:start position:0% far like I guess all of our users are 00:21:41.840 --> 00:21:45.269 align:start position:0% far like I guess all of our users are fine<00:21:42.080> with<00:21:42.240> that<00:21:42.880> uh<00:21:43.000> I<00:21:43.120> think<00:21:43.960> um<00:21:44.960> yeah<00:21:45.159> I 00:21:45.269 --> 00:21:45.279 align:start position:0% fine with that uh I think um yeah I 00:21:45.279 --> 00:21:47.190 align:start position:0% fine with that uh I think um yeah I think<00:21:45.480> it<00:21:45.840> it's<00:21:46.279> yeah<00:21:46.440> they're<00:21:46.799> okay<00:21:47.000> with 00:21:47.190 --> 00:21:47.200 align:start position:0% think it it's yeah they're okay with 00:21:47.200 --> 00:21:50.669 align:start position:0% think it it's yeah they're okay with that<00:21:47.400> leaking<00:21:47.799> that<00:21:48.000> level<00:21:48.360> of<00:21:48.559> privacy<00:21:49.480> um<00:21:50.480> uh 00:21:50.669 --> 00:21:50.679 align:start position:0% that leaking that level of privacy um uh 00:21:50.679 --> 00:21:52.669 align:start position:0% that leaking that level of privacy um uh yeah<00:21:51.320> do<00:21:51.440> they<00:21:51.559> know<00:21:51.960> that<00:21:52.120> they're<00:21:52.240> sending 00:21:52.669 --> 00:21:52.679 align:start position:0% yeah do they know that they're sending 00:21:52.679 --> 00:21:55.549 align:start position:0% yeah do they know that they're sending the<00:21:52.880> pl<00:21:53.159> Tex<00:21:53.440> email<00:21:54.200> yeah<00:21:54.440> yeah<00:21:54.640> yeah<00:21:54.919> we<00:21:55.360> uh 00:21:55.549 --> 00:21:55.559 align:start position:0% the pl Tex email yeah yeah yeah we uh 00:21:55.559 --> 00:21:58.909 align:start position:0% the pl Tex email yeah yeah yeah we uh yeah<00:21:55.720> we<00:21:55.840> disclose<00:21:56.559> everything<00:21:57.559> um<00:21:58.200> to<00:21:58.640> to<00:21:58.799> the 00:21:58.909 --> 00:21:58.919 align:start position:0% yeah we disclose everything um to to the 00:21:58.919 --> 00:22:03.029 align:start position:0% yeah we disclose everything um to to the user<00:21:59.720> uh<00:22:00.120> that<00:22:00.480> we<00:22:00.559> are<00:22:00.720> doing<00:22:01.080> that<00:22:02.080> um<00:22:02.880> yeah 00:22:03.029 --> 00:22:03.039 align:start position:0% user uh that we are doing that um yeah 00:22:03.039 --> 00:22:04.630 align:start position:0% user uh that we are doing that um yeah and<00:22:03.159> then<00:22:03.360> I<00:22:03.480> guess<00:22:03.600> the<00:22:03.760> second<00:22:04.000> flow<00:22:04.480> I<00:22:04.559> was 00:22:04.630 --> 00:22:04.640 align:start position:0% and then I guess the second flow I was 00:22:04.640 --> 00:22:06.149 align:start position:0% and then I guess the second flow I was going<00:22:04.760> to<00:22:04.880> talk<00:22:05.000> about<00:22:05.240> is<00:22:05.400> we<00:22:05.559> also<00:22:05.760> use<00:22:06.000> like 00:22:06.149 --> 00:22:06.159 align:start position:0% going to talk about is we also use like 00:22:06.159 --> 00:22:10.390 align:start position:0% going to talk about is we also use like TLS<00:22:06.640> notary<00:22:07.640> uh<00:22:08.200> which<00:22:09.200> uh<00:22:09.799> I<00:22:09.919> guess<00:22:10.039> for<00:22:10.279> that 00:22:10.390 --> 00:22:10.400 align:start position:0% TLS notary uh which uh I guess for that 00:22:10.400 --> 00:22:12.470 align:start position:0% TLS notary uh which uh I guess for that flow<00:22:10.720> you<00:22:10.880> basically<00:22:11.279> need<00:22:11.559> to<00:22:12.039> have<00:22:12.279> the 00:22:12.470 --> 00:22:12.480 align:start position:0% flow you basically need to have the 00:22:12.480 --> 00:22:16.149 align:start position:0% flow you basically need to have the users<00:22:13.080> like<00:22:14.080> like<00:22:14.279> credentials<00:22:14.880> in<00:22:15.039> order<00:22:15.320> to 00:22:16.149 --> 00:22:16.159 align:start position:0% users like like credentials in order to 00:22:16.159 --> 00:22:18.870 align:start position:0% users like like credentials in order to generate<00:22:16.720> that<00:22:17.000> like<00:22:17.159> MPC<00:22:17.640> proof<00:22:18.320> so<00:22:18.600> in<00:22:18.679> order 00:22:18.870 --> 00:22:18.880 align:start position:0% generate that like MPC proof so in order 00:22:18.880 --> 00:22:21.149 align:start position:0% generate that like MPC proof so in order to<00:22:19.159> get<00:22:19.400> that<00:22:19.720> you<00:22:19.960> basically<00:22:20.320> need<00:22:20.480> to 00:22:21.149 --> 00:22:21.159 align:start position:0% to get that you basically need to 00:22:21.159 --> 00:22:23.990 align:start position:0% to get that you basically need to install<00:22:21.720> or<00:22:21.960> create<00:22:22.200> a<00:22:22.480> browser<00:22:22.880> extension<00:22:23.880> uh 00:22:23.990 --> 00:22:24.000 align:start position:0% install or create a browser extension uh 00:22:24.000 --> 00:22:27.190 align:start position:0% install or create a browser extension uh to<00:22:24.320> scrape<00:22:24.919> those<00:22:25.600> like<00:22:26.159> that<00:22:26.400> request<00:22:26.960> and 00:22:27.190 --> 00:22:27.200 align:start position:0% to scrape those like that request and 00:22:27.200 --> 00:22:29.070 align:start position:0% to scrape those like that request and response<00:22:28.159> uh<00:22:28.279> in<00:22:28.520> in<00:22:28.520> order<00:22:28.679> to<00:22:28.799> pass<00:22:28.919> it<00:22:29.000> to 00:22:29.070 --> 00:22:29.080 align:start position:0% response uh in in order to pass it to 00:22:29.080 --> 00:22:31.590 align:start position:0% response uh in in order to pass it to the<00:22:29.200> NPC<00:22:29.640> proof<00:22:30.640> um<00:22:30.840> and<00:22:31.039> of<00:22:31.159> course<00:22:31.360> all<00:22:31.480> of 00:22:31.590 --> 00:22:31.600 align:start position:0% the NPC proof um and of course all of 00:22:31.600 --> 00:22:34.190 align:start position:0% the NPC proof um and of course all of this<00:22:31.720> is<00:22:31.840> done<00:22:32.120> local<00:22:32.520> and<00:22:32.679> client<00:22:33.120> side<00:22:33.880> um 00:22:34.190 --> 00:22:34.200 align:start position:0% this is done local and client side um 00:22:34.200 --> 00:22:37.110 align:start position:0% this is done local and client side um but<00:22:34.960> yeah<00:22:35.360> I<00:22:35.440> think<00:22:35.600> the<00:22:35.720> reason<00:22:36.000> for<00:22:36.200> that<00:22:36.400> is 00:22:37.110 --> 00:22:37.120 align:start position:0% but yeah I think the reason for that is 00:22:37.120 --> 00:22:39.510 align:start position:0% but yeah I think the reason for that is that's<00:22:37.440> kind<00:22:37.559> of<00:22:37.679> non-negotiable<00:22:38.640> like<00:22:38.840> us 00:22:39.510 --> 00:22:39.520 align:start position:0% that's kind of non-negotiable like us 00:22:39.520 --> 00:22:42.310 align:start position:0% that's kind of non-negotiable like us like<00:22:39.760> storing<00:22:40.320> cookies<00:22:40.919> on<00:22:41.039> a<00:22:41.200> server<00:22:42.039> running 00:22:42.310 --> 00:22:42.320 align:start position:0% like storing cookies on a server running 00:22:42.320 --> 00:22:43.870 align:start position:0% like storing cookies on a server running cookies<00:22:42.640> through<00:22:42.799> a<00:22:42.960> server<00:22:43.520> and<00:22:43.679> their 00:22:43.870 --> 00:22:43.880 align:start position:0% cookies through a server and their 00:22:43.880 --> 00:22:46.310 align:start position:0% cookies through a server and their credentials<00:22:44.480> is<00:22:45.159> like<00:22:45.520> a<00:22:45.640> complete<00:22:45.919> noo 00:22:46.310 --> 00:22:46.320 align:start position:0% credentials is like a complete noo 00:22:46.320 --> 00:22:49.110 align:start position:0% credentials is like a complete noo whereas<00:22:46.640> email<00:22:47.000> is<00:22:47.480> a<00:22:47.600> little<00:22:47.799> bit<00:22:47.960> more<00:22:48.279> okay 00:22:49.110 --> 00:22:49.120 align:start position:0% whereas email is a little bit more okay 00:22:49.120 --> 00:22:51.710 align:start position:0% whereas email is a little bit more okay uh<00:22:49.240> in<00:22:49.320> terms<00:22:49.520> of<00:22:49.880> privacy<00:22:50.880> U<00:22:51.000> but<00:22:51.200> yeah<00:22:51.520> that 00:22:51.710 --> 00:22:51.720 align:start position:0% uh in terms of privacy U but yeah that 00:22:51.720 --> 00:22:54.430 align:start position:0% uh in terms of privacy U but yeah that that's<00:22:51.919> also<00:22:52.279> a<00:22:52.760> kind<00:22:52.880> of<00:22:53.039> ux<00:22:53.840> hurdle<00:22:54.200> we<00:22:54.320> had 00:22:54.430 --> 00:22:54.440 align:start position:0% that's also a kind of ux hurdle we had 00:22:54.440 --> 00:22:56.430 align:start position:0% that's also a kind of ux hurdle we had to<00:22:54.559> deal<00:22:54.840> with<00:22:55.279> like<00:22:55.440> trying<00:22:55.640> to<00:22:55.840> get<00:22:56.000> users<00:22:56.320> to 00:22:56.430 --> 00:22:56.440 align:start position:0% to deal with like trying to get users to 00:22:56.440 --> 00:22:58.110 align:start position:0% to deal with like trying to get users to install<00:22:56.720> a<00:22:56.799> browser<00:22:57.159> extension<00:22:57.799> and<00:22:57.919> going 00:22:58.110 --> 00:22:58.120 align:start position:0% install a browser extension and going 00:22:58.120 --> 00:22:59.390 align:start position:0% install a browser extension and going through<00:22:58.240> that 00:22:59.390 --> 00:22:59.400 align:start position:0% through that 00:22:59.400 --> 00:23:02.149 align:start position:0% through that flow<00:23:00.400> yeah<00:23:00.640> maybe<00:23:01.000> one<00:23:01.200> thing<00:23:01.400> ZK<00:23:01.760> email 00:23:02.149 --> 00:23:02.159 align:start position:0% flow yeah maybe one thing ZK email 00:23:02.159 --> 00:23:04.870 align:start position:0% flow yeah maybe one thing ZK email learned<00:23:02.440> a<00:23:02.520> lot<00:23:02.679> from<00:23:02.799> zkp<00:23:03.279> Top<00:23:04.120> is<00:23:04.360> that<00:23:04.760> yeah 00:23:04.870 --> 00:23:04.880 align:start position:0% learned a lot from zkp Top is that yeah 00:23:04.880 --> 00:23:06.669 align:start position:0% learned a lot from zkp Top is that yeah it's<00:23:05.120> always<00:23:05.440> important<00:23:05.840> to<00:23:06.000> have<00:23:06.200> the<00:23:06.480> clear 00:23:06.669 --> 00:23:06.679 align:start position:0% it's always important to have the clear 00:23:06.679 --> 00:23:08.310 align:start position:0% it's always important to have the clear user<00:23:06.960> flow<00:23:07.240> so<00:23:07.440> actually<00:23:07.760> after<00:23:08.000> you<00:23:08.159> guys 00:23:08.310 --> 00:23:08.320 align:start position:0% user flow so actually after you guys 00:23:08.320 --> 00:23:09.789 align:start position:0% user flow so actually after you guys added<00:23:08.600> the<00:23:08.679> Google<00:23:08.919> o<00:23:09.240> flow<00:23:09.400> and<00:23:09.520> realize 00:23:09.789 --> 00:23:09.799 align:start position:0% added the Google o flow and realize 00:23:09.799 --> 00:23:11.310 align:start position:0% added the Google o flow and realize people<00:23:09.960> are<00:23:10.080> actually<00:23:10.279> using<00:23:10.600> this<00:23:10.960> we<00:23:11.080> added 00:23:11.310 --> 00:23:11.320 align:start position:0% people are actually using this we added 00:23:11.320 --> 00:23:13.430 align:start position:0% people are actually using this we added it<00:23:11.360> to<00:23:11.559> all<00:23:11.720> of<00:23:12.159> the<00:23:12.320> existing<00:23:12.600> zkm<00:23:13.080> apps<00:23:13.279> too 00:23:13.430 --> 00:23:13.440 align:start position:0% it to all of the existing zkm apps too 00:23:13.440 --> 00:23:15.350 align:start position:0% it to all of the existing zkm apps too where<00:23:13.520> it's<00:23:13.600> like<00:23:13.760> you<00:23:14.039> can<00:23:15.039> because<00:23:15.240> we 00:23:15.350 --> 00:23:15.360 align:start position:0% where it's like you can because we 00:23:15.360 --> 00:23:17.669 align:start position:0% where it's like you can because we noticed<00:23:15.799> hey<00:23:16.000> like<00:23:16.760> as<00:23:16.880> long<00:23:17.080> as<00:23:17.240> there<00:23:17.360> is<00:23:17.480> a 00:23:17.669 --> 00:23:17.679 align:start position:0% noticed hey like as long as there is a 00:23:17.679 --> 00:23:20.430 align:start position:0% noticed hey like as long as there is a way<00:23:17.840> for<00:23:18.080> users<00:23:18.520> to<00:23:18.679> do<00:23:18.840> the<00:23:19.039> easy<00:23:19.480> path<00:23:20.159> and<00:23:20.320> as 00:23:20.430 --> 00:23:20.440 align:start position:0% way for users to do the easy path and as 00:23:20.440 --> 00:23:22.269 align:start position:0% way for users to do the easy path and as long<00:23:20.600> as<00:23:20.760> we<00:23:21.080> that<00:23:21.200> means<00:23:21.440> we<00:23:21.559> have<00:23:21.679> to<00:23:21.880> offer<00:23:22.120> a 00:23:22.269 --> 00:23:22.279 align:start position:0% long as we that means we have to offer a 00:23:22.279 --> 00:23:24.470 align:start position:0% long as we that means we have to offer a way<00:23:22.679> for<00:23:22.840> the<00:23:22.960> self-hosted<00:23:23.600> or<00:23:23.720> fully<00:23:24.080> private 00:23:24.470 --> 00:23:24.480 align:start position:0% way for the self-hosted or fully private 00:23:24.480 --> 00:23:26.390 align:start position:0% way for the self-hosted or fully private path<00:23:24.760> and<00:23:24.840> so<00:23:25.000> it's<00:23:25.120> kind<00:23:25.240> of<00:23:25.679> as<00:23:25.840> long<00:23:26.000> as<00:23:26.200> that 00:23:26.390 --> 00:23:26.400 align:start position:0% path and so it's kind of as long as that 00:23:26.400 --> 00:23:29.630 align:start position:0% path and so it's kind of as long as that path<00:23:26.679> exists<00:23:27.360> it's<00:23:27.559> kind<00:23:27.720> of<00:23:27.960> fine<00:23:28.520> to<00:23:28.799> have<00:23:29.400> an 00:23:29.630 --> 00:23:29.640 align:start position:0% path exists it's kind of fine to have an 00:23:29.640 --> 00:23:31.990 align:start position:0% path exists it's kind of fine to have an option<00:23:29.960> for<00:23:30.120> easy<00:23:30.400> users<00:23:30.720> who<00:23:30.880> don't<00:23:31.120> care<00:23:31.480> to 00:23:31.990 --> 00:23:32.000 align:start position:0% option for easy users who don't care to 00:23:32.000 --> 00:23:33.750 align:start position:0% option for easy users who don't care to just<00:23:32.200> use<00:23:32.400> the<00:23:32.600> kind<00:23:32.720> of<00:23:32.880> simple<00:23:33.279> sign<00:23:33.480> in<00:23:33.600> with 00:23:33.750 --> 00:23:33.760 align:start position:0% just use the kind of simple sign in with 00:23:33.760 --> 00:23:36.470 align:start position:0% just use the kind of simple sign in with Google<00:23:34.000> select<00:23:34.279> the<00:23:34.400> email<00:23:34.760> move<00:23:34.919> on<00:23:35.279> path<00:23:36.120> um 00:23:36.470 --> 00:23:36.480 align:start position:0% Google select the email move on path um 00:23:36.480 --> 00:23:37.870 align:start position:0% Google select the email move on path um as<00:23:36.600> long<00:23:36.760> as<00:23:36.919> it's<00:23:37.159> possible<00:23:37.400> for<00:23:37.559> the<00:23:37.679> people 00:23:37.870 --> 00:23:37.880 align:start position:0% as long as it's possible for the people 00:23:37.880 --> 00:23:39.310 align:start position:0% as long as it's possible for the people who<00:23:38.039> really<00:23:38.240> care<00:23:38.440> about<00:23:38.679> privacy<00:23:39.039> to<00:23:39.200> get 00:23:39.310 --> 00:23:39.320 align:start position:0% who really care about privacy to get 00:23:39.320 --> 00:23:40.750 align:start position:0% who really care about privacy to get that<00:23:39.480> privacy<00:23:39.799> they<00:23:39.919> want<00:23:40.440> either<00:23:40.640> they 00:23:40.750 --> 00:23:40.760 align:start position:0% that privacy they want either they 00:23:40.760 --> 00:23:42.310 align:start position:0% that privacy they want either they manually<00:23:41.120> upload<00:23:41.400> the<00:23:41.480> email<00:23:41.760> they<00:23:41.880> select<00:23:42.200> do 00:23:42.310 --> 00:23:42.320 align:start position:0% manually upload the email they select do 00:23:42.320 --> 00:23:44.630 align:start position:0% manually upload the email they select do a<00:23:42.440> client<00:23:42.919> side<00:23:43.880> they're<00:23:44.039> willing<00:23:44.279> to<00:23:44.480> take 00:23:44.630 --> 00:23:44.640 align:start position:0% a client side they're willing to take 00:23:44.640 --> 00:23:47.669 align:start position:0% a client side they're willing to take the<00:23:44.720> ux<00:23:45.080> hit<00:23:45.240> in<00:23:45.360> exchange<00:23:45.640> for<00:23:45.919> privacy<00:23:46.919> or<00:23:47.480> we 00:23:47.669 --> 00:23:47.679 align:start position:0% the ux hit in exchange for privacy or we 00:23:47.679 --> 00:23:48.789 align:start position:0% the ux hit in exchange for privacy or we and<00:23:47.799> this<00:23:47.880> is<00:23:47.960> one<00:23:48.080> of<00:23:48.159> the<00:23:48.279> advantages<00:23:48.679> of 00:23:48.789 --> 00:23:48.799 align:start position:0% and this is one of the advantages of 00:23:48.799 --> 00:23:49.950 align:start position:0% and this is one of the advantages of having<00:23:48.960> a<00:23:49.080> totally<00:23:49.400> open<00:23:49.679> source 00:23:49.950 --> 00:23:49.960 align:start position:0% having a totally open source 00:23:49.960 --> 00:23:51.789 align:start position:0% having a totally open source organization<00:23:50.520> is<00:23:50.679> that<00:23:51.080> all<00:23:51.240> of<00:23:51.320> our<00:23:51.440> repos 00:23:51.789 --> 00:23:51.799 align:start position:0% organization is that all of our repos 00:23:51.799 --> 00:23:53.190 align:start position:0% organization is that all of our repos are<00:23:51.960> open<00:23:52.200> like<00:23:52.320> you<00:23:52.480> can<00:23:52.679> go<00:23:52.840> if<00:23:52.919> you<00:23:53.039> don't 00:23:53.190 --> 00:23:53.200 align:start position:0% are open like you can go if you don't 00:23:53.200 --> 00:23:56.070 align:start position:0% are open like you can go if you don't trust<00:23:53.400> ZK<00:23:53.679> pb's<00:23:54.000> front<00:23:54.159> end<00:23:55.000> get<00:23:55.279> the<00:23:55.799> or<00:23:56.000> you 00:23:56.070 --> 00:23:56.080 align:start position:0% trust ZK pb's front end get the or you 00:23:56.080 --> 00:23:58.070 align:start position:0% trust ZK pb's front end get the or you don't<00:23:56.200> trust<00:23:56.400> zk's<00:23:56.919> front<00:23:57.080> end<00:23:57.360> go<00:23:57.760> go<00:23:57.840> to<00:23:57.960> the 00:23:58.070 --> 00:23:58.080 align:start position:0% don't trust zk's front end go go to the 00:23:58.080 --> 00:24:00.149 align:start position:0% don't trust zk's front end go go to the GitHub<00:23:58.440> repo<00:23:58.760> clone<00:23:58.960> it<00:23:59.120> locally<00:23:59.480> run<00:23:59.679> it<00:24:00.080> and 00:24:00.149 --> 00:24:00.159 align:start position:0% GitHub repo clone it locally run it and 00:24:00.159 --> 00:24:01.909 align:start position:0% GitHub repo clone it locally run it and if<00:24:00.279> you<00:24:00.480> really<00:24:00.799> really<00:24:01.039> care<00:24:01.240> about<00:24:01.520> privacy 00:24:01.909 --> 00:24:01.919 align:start position:0% if you really really care about privacy 00:24:01.919 --> 00:24:04.350 align:start position:0% if you really really care about privacy there's<00:24:02.159> always<00:24:02.440> ways<00:24:02.679> to<00:24:03.200> to<00:24:03.360> get<00:24:03.559> around<00:24:04.200> the 00:24:04.350 --> 00:24:04.360 align:start position:0% there's always ways to to get around the 00:24:04.360 --> 00:24:06.950 align:start position:0% there's always ways to to get around the ease<00:24:04.640> of<00:24:04.840> use<00:24:05.799> uh<00:24:06.000> turn<00:24:06.320> keys<00:24:06.559> that<00:24:06.640> we've<00:24:06.799> put 00:24:06.950 --> 00:24:06.960 align:start position:0% ease of use uh turn keys that we've put 00:24:06.960 --> 00:24:08.870 align:start position:0% ease of use uh turn keys that we've put into<00:24:07.120> the<00:24:07.200> UI<00:24:07.679> but<00:24:07.960> for<00:24:08.159> me<00:24:08.320> it's<00:24:08.480> kind<00:24:08.600> of<00:24:08.720> like 00:24:08.870 --> 00:24:08.880 align:start position:0% into the UI but for me it's kind of like 00:24:08.880 --> 00:24:10.710 align:start position:0% into the UI but for me it's kind of like we've<00:24:09.000> learned<00:24:09.360> okay<00:24:09.559> as<00:24:09.679> long<00:24:09.880> as<00:24:10.080> there<00:24:10.200> is 00:24:10.710 --> 00:24:10.720 align:start position:0% we've learned okay as long as there is 00:24:10.720 --> 00:24:12.950 align:start position:0% we've learned okay as long as there is the<00:24:10.880> easiest<00:24:11.360> possible<00:24:11.760> path<00:24:12.039> and<00:24:12.159> a<00:24:12.320> way<00:24:12.520> for 00:24:12.950 --> 00:24:12.960 align:start position:0% the easiest possible path and a way for 00:24:12.960 --> 00:24:14.310 align:start position:0% the easiest possible path and a way for someone<00:24:13.200> who<00:24:13.320> cares<00:24:13.520> about<00:24:13.720> privacy<00:24:14.039> to<00:24:14.159> do 00:24:14.310 --> 00:24:14.320 align:start position:0% someone who cares about privacy to do 00:24:14.320 --> 00:24:16.029 align:start position:0% someone who cares about privacy to do the<00:24:14.520> private<00:24:14.919> path<00:24:15.400> we<00:24:15.520> feel<00:24:15.760> like<00:24:15.880> that's 00:24:16.029 --> 00:24:16.039 align:start position:0% the private path we feel like that's 00:24:16.039 --> 00:24:17.630 align:start position:0% the private path we feel like that's been<00:24:16.240> like<00:24:16.360> a<00:24:16.480> good<00:24:16.640> enough<00:24:17.000> mix<00:24:17.200> of<00:24:17.400> things 00:24:17.630 --> 00:24:17.640 align:start position:0% been like a good enough mix of things 00:24:17.640 --> 00:24:19.190 align:start position:0% been like a good enough mix of things even<00:24:17.799> if<00:24:17.960> people<00:24:18.200> in<00:24:18.360> general<00:24:18.919> don't 00:24:19.190 --> 00:24:19.200 align:start position:0% even if people in general don't 00:24:19.200 --> 00:24:21.350 align:start position:0% even if people in general don't necessarily<00:24:19.640> always<00:24:19.880> do<00:24:20.039> the<00:24:20.200> private<00:24:20.559> path 00:24:21.350 --> 00:24:21.360 align:start position:0% necessarily always do the private path 00:24:21.360 --> 00:24:22.590 align:start position:0% necessarily always do the private path um<00:24:21.480> so<00:24:21.600> that's<00:24:21.720> one<00:24:21.880> ux<00:24:22.200> pattern<00:24:22.440> we've 00:24:22.590 --> 00:24:22.600 align:start position:0% um so that's one ux pattern we've 00:24:22.600 --> 00:24:25.269 align:start position:0% um so that's one ux pattern we've noticed<00:24:22.840> has<00:24:22.960> been<00:24:23.120> really<00:24:23.480> nice 00:24:25.269 --> 00:24:25.279 align:start position:0% noticed has been really nice 00:24:25.279 --> 00:24:29.870 align:start position:0% noticed has been really nice um<00:24:26.640> yeah<00:24:27.640> yeah<00:24:28.159> um<00:24:28.720> bunch<00:24:28.919> of<00:24:29.080> thoughts<00:24:29.360> here<00:24:29.720> I 00:24:29.870 --> 00:24:29.880 align:start position:0% um yeah yeah um bunch of thoughts here I 00:24:29.880 --> 00:24:32.990 align:start position:0% um yeah yeah um bunch of thoughts here I guess<00:24:30.880> first<00:24:31.080> one<00:24:31.279> is<00:24:31.440> about<00:24:31.840> privacy<00:24:32.720> and 00:24:32.990 --> 00:24:33.000 align:start position:0% guess first one is about privacy and 00:24:33.000 --> 00:24:36.190 align:start position:0% guess first one is about privacy and like<00:24:33.559> I<00:24:33.760> I<00:24:33.840> feel<00:24:34.120> like<00:24:34.600> one<00:24:34.760> of<00:24:34.919> the<00:24:35.200> main 00:24:36.190 --> 00:24:36.200 align:start position:0% like I I feel like one of the main 00:24:36.200 --> 00:24:38.549 align:start position:0% like I I feel like one of the main appeals<00:24:36.880> of<00:24:37.039> building<00:24:37.480> consumer<00:24:37.919> apps<00:24:38.360> with 00:24:38.549 --> 00:24:38.559 align:start position:0% appeals of building consumer apps with 00:24:38.559 --> 00:24:40.750 align:start position:0% appeals of building consumer apps with programmable<00:24:39.120> cryptography<00:24:40.000> is<00:24:40.480> is<00:24:40.600> the 00:24:40.750 --> 00:24:40.760 align:start position:0% programmable cryptography is is the 00:24:40.760 --> 00:24:42.510 align:start position:0% programmable cryptography is is the Privacy<00:24:41.159> you<00:24:41.279> get<00:24:41.640> right<00:24:41.880> is<00:24:42.000> the<00:24:42.159> choice<00:24:42.399> and 00:24:42.510 --> 00:24:42.520 align:start position:0% Privacy you get right is the choice and 00:24:42.520 --> 00:24:44.590 align:start position:0% Privacy you get right is the choice and the<00:24:42.679> consent<00:24:43.080> that<00:24:43.240> you<00:24:43.440> have<00:24:43.640> and<00:24:44.120> that<00:24:44.279> is 00:24:44.590 --> 00:24:44.600 align:start position:0% the consent that you have and that is 00:24:44.600 --> 00:24:46.950 align:start position:0% the consent that you have and that is like<00:24:45.520> one<00:24:45.679> of<00:24:45.799> the<00:24:45.919> major<00:24:46.200> reasons<00:24:46.600> why<00:24:46.760> these 00:24:46.950 --> 00:24:46.960 align:start position:0% like one of the major reasons why these 00:24:46.960 --> 00:24:48.950 align:start position:0% like one of the major reasons why these Technologies<00:24:47.440> are<00:24:47.600> so<00:24:47.840> powerful<00:24:48.600> but<00:24:48.720> I<00:24:48.799> feel 00:24:48.950 --> 00:24:48.960 align:start position:0% Technologies are so powerful but I feel 00:24:48.960 --> 00:24:50.190 align:start position:0% Technologies are so powerful but I feel like<00:24:49.080> if<00:24:49.159> you<00:24:49.320> go<00:24:49.480> down<00:24:49.640> the<00:24:49.720> street<00:24:50.000> and<00:24:50.120> you 00:24:50.190 --> 00:24:50.200 align:start position:0% like if you go down the street and you 00:24:50.200 --> 00:24:52.630 align:start position:0% like if you go down the street and you just<00:24:50.360> like<00:24:50.520> talk<00:24:50.720> to<00:24:50.919> people<00:24:51.399> I<00:24:51.520> think<00:24:52.480> what 00:24:52.630 --> 00:24:52.640 align:start position:0% just like talk to people I think what 00:24:52.640 --> 00:24:55.909 align:start position:0% just like talk to people I think what I've<00:24:52.799> noticed<00:24:53.679> is<00:24:54.360> people<00:24:54.679> just<00:24:55.120> don't<00:24:55.360> even 00:24:55.909 --> 00:24:55.919 align:start position:0% I've noticed is people just don't even 00:24:55.919 --> 00:24:58.510 align:start position:0% I've noticed is people just don't even understand<00:24:56.840> privacy<00:24:57.679> from<00:24:57.840> your<00:24:58.000> peers 00:24:58.510 --> 00:24:58.520 align:start position:0% understand privacy from your peers 00:24:58.520 --> 00:25:00.350 align:start position:0% understand privacy from your peers versus<00:24:58.799> privacy<00:24:59.200> from<00:24:59.320> the<00:24:59.440> server<00:25:00.039> like<00:25:00.200> this 00:25:00.350 --> 00:25:00.360 align:start position:0% versus privacy from the server like this 00:25:00.360 --> 00:25:03.149 align:start position:0% versus privacy from the server like this simple<00:25:00.720> concept<00:25:01.320> of<00:25:02.080> like<00:25:02.640> hey<00:25:02.840> they<00:25:02.960> look<00:25:03.080> at 00:25:03.149 --> 00:25:03.159 align:start position:0% simple concept of like hey they look at 00:25:03.159 --> 00:25:05.310 align:start position:0% simple concept of like hey they look at your<00:25:03.360> venmo<00:25:03.919> history<00:25:04.480> and<00:25:04.720> if<00:25:04.799> you<00:25:04.919> look<00:25:05.039> at<00:25:05.159> it 00:25:05.310 --> 00:25:05.320 align:start position:0% your venmo history and if you look at it 00:25:05.320 --> 00:25:07.149 align:start position:0% your venmo history and if you look at it you<00:25:05.399> can<00:25:05.760> have<00:25:06.000> like<00:25:06.440> venmo<00:25:06.799> or<00:25:06.880> whatever 00:25:07.149 --> 00:25:07.159 align:start position:0% you can have like venmo or whatever 00:25:07.159 --> 00:25:08.669 align:start position:0% you can have like venmo or whatever payment<00:25:07.520> app<00:25:07.720> you<00:25:07.840> use<00:25:08.080> like<00:25:08.240> you<00:25:08.320> can<00:25:08.480> have 00:25:08.669 --> 00:25:08.679 align:start position:0% payment app you use like you can have 00:25:08.679 --> 00:25:10.310 align:start position:0% payment app you use like you can have transactions<00:25:09.240> only<00:25:09.520> visible<00:25:09.960> to<00:25:10.159> your 00:25:10.310 --> 00:25:10.320 align:start position:0% transactions only visible to your 00:25:10.320 --> 00:25:12.669 align:start position:0% transactions only visible to your friends<00:25:10.600> only<00:25:10.840> visible<00:25:11.120> to<00:25:11.279> yourself<00:25:12.159> like 00:25:12.669 --> 00:25:12.679 align:start position:0% friends only visible to yourself like 00:25:12.679 --> 00:25:14.350 align:start position:0% friends only visible to yourself like people<00:25:13.000> think<00:25:13.480> when<00:25:13.679> you<00:25:13.919> set<00:25:14.159> your 00:25:14.350 --> 00:25:14.360 align:start position:0% people think when you set your 00:25:14.360 --> 00:25:16.269 align:start position:0% people think when you set your transactions<00:25:14.919> to<00:25:15.080> be<00:25:15.200> only<00:25:15.480> visible<00:25:16.120> to 00:25:16.269 --> 00:25:16.279 align:start position:0% transactions to be only visible to 00:25:16.279 --> 00:25:18.510 align:start position:0% transactions to be only visible to yourself<00:25:16.880> like<00:25:17.000> that<00:25:17.120> is<00:25:17.320> privacy<00:25:18.080> right<00:25:18.440> that 00:25:18.510 --> 00:25:18.520 align:start position:0% yourself like that is privacy right that 00:25:18.520 --> 00:25:20.470 align:start position:0% yourself like that is privacy right that is<00:25:18.760> like<00:25:19.159> just<00:25:19.440> privacy<00:25:19.840> in<00:25:19.960> general<00:25:20.320> that's 00:25:20.470 --> 00:25:20.480 align:start position:0% is like just privacy in general that's 00:25:20.480 --> 00:25:21.750 align:start position:0% is like just privacy in general that's what<00:25:20.600> that<00:25:20.720> means<00:25:21.240> but<00:25:21.360> it's<00:25:21.520> like<00:25:21.640> a 00:25:21.750 --> 00:25:21.760 align:start position:0% what that means but it's like a 00:25:21.760 --> 00:25:23.430 align:start position:0% what that means but it's like a completely<00:25:22.120> different<00:25:22.520> concept<00:25:22.960> when<00:25:23.279> all 00:25:23.430 --> 00:25:23.440 align:start position:0% completely different concept when all 00:25:23.440 --> 00:25:25.590 align:start position:0% completely different concept when all this<00:25:23.600> cryptography<00:25:24.240> offers<00:25:25.080> privacy<00:25:25.440> from 00:25:25.590 --> 00:25:25.600 align:start position:0% this cryptography offers privacy from 00:25:25.600 --> 00:25:26.909 align:start position:0% this cryptography offers privacy from the<00:25:25.679> server<00:25:26.200> which<00:25:26.320> is<00:25:26.480> really<00:25:26.679> what<00:25:26.760> we're 00:25:26.909 --> 00:25:26.919 align:start position:0% the server which is really what we're 00:25:26.919 --> 00:25:28.350 align:start position:0% the server which is really what we're aiming<00:25:27.200> for<00:25:27.520> right<00:25:27.720> like<00:25:27.840> we<00:25:27.919> don't<00:25:28.039> trust 00:25:28.350 --> 00:25:28.360 align:start position:0% aiming for right like we don't trust 00:25:28.360 --> 00:25:29.909 align:start position:0% aiming for right like we don't trust server<00:25:28.600> to<00:25:28.720> get<00:25:28.880> hacked<00:25:29.159> or<00:25:29.279> to<00:25:29.360> be<00:25:29.480> malicious 00:25:29.909 --> 00:25:29.919 align:start position:0% server to get hacked or to be malicious 00:25:29.919 --> 00:25:33.190 align:start position:0% server to get hacked or to be malicious or<00:25:30.039> all<00:25:30.200> this<00:25:30.399> stuff<00:25:31.279> um<00:25:31.760> and<00:25:32.440> I<00:25:32.559> feel<00:25:32.840> like 00:25:33.190 --> 00:25:33.200 align:start position:0% or all this stuff um and I feel like 00:25:33.200 --> 00:25:35.070 align:start position:0% or all this stuff um and I feel like this<00:25:33.760> this<00:25:33.880> is<00:25:34.120> really<00:25:34.360> like<00:25:34.480> a<00:25:34.600> critical 00:25:35.070 --> 00:25:35.080 align:start position:0% this this is really like a critical 00:25:35.080 --> 00:25:36.310 align:start position:0% this this is really like a critical question<00:25:35.360> we<00:25:35.480> need<00:25:35.600> to<00:25:35.720> solve<00:25:35.960> in<00:25:36.120> like 00:25:36.310 --> 00:25:36.320 align:start position:0% question we need to solve in like 00:25:36.320 --> 00:25:37.870 align:start position:0% question we need to solve in like communication<00:25:36.799> and<00:25:37.039> design<00:25:37.360> of<00:25:37.520> how<00:25:37.600> do<00:25:37.720> you 00:25:37.870 --> 00:25:37.880 align:start position:0% communication and design of how do you 00:25:37.880 --> 00:25:40.310 align:start position:0% communication and design of how do you actually<00:25:38.080> convey<00:25:38.440> this<00:25:38.559> to<00:25:38.840> users<00:25:39.840> um<00:25:40.039> so 00:25:40.310 --> 00:25:40.320 align:start position:0% actually convey this to users um so 00:25:40.320 --> 00:25:42.710 align:start position:0% actually convey this to users um so here's<00:25:40.760> here's<00:25:41.000> one<00:25:41.240> idea<00:25:41.679> I<00:25:41.760> can<00:25:42.000> propose 00:25:42.710 --> 00:25:42.720 align:start position:0% here's here's one idea I can propose 00:25:42.720 --> 00:25:45.389 align:start position:0% here's here's one idea I can propose which<00:25:42.880> is<00:25:43.120> like<00:25:43.600> from<00:25:44.000> from<00:25:44.279> Rachel<00:25:45.039> uh<00:25:45.159> at 00:25:45.389 --> 00:25:45.399 align:start position:0% which is like from from Rachel uh at 00:25:45.399 --> 00:25:47.549 align:start position:0% which is like from from Rachel uh at cursive<00:25:45.760> and<00:25:45.880> also<00:25:46.080> Tomo<00:25:46.440> from<00:25:46.559> the<00:25:46.679> EF<00:25:47.240> like 00:25:47.549 --> 00:25:47.559 align:start position:0% cursive and also Tomo from the EF like 00:25:47.559 --> 00:25:49.149 align:start position:0% cursive and also Tomo from the EF like they're<00:25:47.760> both<00:25:48.000> wonderful<00:25:48.399> designers<00:25:49.000> and 00:25:49.149 --> 00:25:49.159 align:start position:0% they're both wonderful designers and 00:25:49.159 --> 00:25:51.149 align:start position:0% they're both wonderful designers and they<00:25:49.279> have<00:25:49.440> this<00:25:49.640> idea<00:25:50.600> uh<00:25:50.720> which<00:25:50.919> they<00:25:51.000> can 00:25:51.149 --> 00:25:51.159 align:start position:0% they have this idea uh which they can 00:25:51.159 --> 00:25:53.110 align:start position:0% they have this idea uh which they can talk<00:25:51.320> more<00:25:51.480> about<00:25:51.679> of<00:25:51.880> like<00:25:52.440> hey<00:25:52.760> we<00:25:52.880> should 00:25:53.110 --> 00:25:53.120 align:start position:0% talk more about of like hey we should 00:25:53.120 --> 00:25:55.830 align:start position:0% talk more about of like hey we should have<00:25:53.320> some<00:25:53.520> sort<00:25:53.720> of<00:25:53.960> like<00:25:54.480> standard<00:25:55.000> UI<00:25:55.399> kit 00:25:55.830 --> 00:25:55.840 align:start position:0% have some sort of like standard UI kit 00:25:55.840 --> 00:25:57.830 align:start position:0% have some sort of like standard UI kit for<00:25:56.080> like<00:25:56.200> communicating<00:25:56.720> to<00:25:56.880> users<00:25:57.360> like 00:25:57.830 --> 00:25:57.840 align:start position:0% for like communicating to users like 00:25:57.840 --> 00:25:59.470 align:start position:0% for like communicating to users like when<00:25:58.000> you<00:25:58.360> see<00:25:58.520> this<00:25:58.640> interface<00:25:59.159> it<00:25:59.240> means 00:25:59.470 --> 00:25:59.480 align:start position:0% when you see this interface it means 00:25:59.480 --> 00:26:01.110 align:start position:0% when you see this interface it means it's<00:25:59.679> actually<00:26:00.000> private<00:26:00.320> from<00:26:00.440> the<00:26:00.559> server 00:26:01.110 --> 00:26:01.120 align:start position:0% it's actually private from the server 00:26:01.120 --> 00:26:02.389 align:start position:0% it's actually private from the server like<00:26:01.279> this<00:26:01.520> looks<00:26:01.760> totally<00:26:02.080> different<00:26:02.279> it 00:26:02.389 --> 00:26:02.399 align:start position:0% like this looks totally different it 00:26:02.399 --> 00:26:04.110 align:start position:0% like this looks totally different it feels<00:26:02.679> totally<00:26:03.000> different<00:26:03.640> uh<00:26:03.760> it<00:26:03.880> is 00:26:04.110 --> 00:26:04.120 align:start position:0% feels totally different uh it is 00:26:04.120 --> 00:26:05.870 align:start position:0% feels totally different uh it is different<00:26:05.000> um<00:26:05.159> and<00:26:05.360> that's<00:26:05.600> actually 00:26:05.870 --> 00:26:05.880 align:start position:0% different um and that's actually 00:26:05.880 --> 00:26:07.549 align:start position:0% different um and that's actually connected<00:26:06.320> to<00:26:06.440> the<00:26:06.600> technology<00:26:07.399> right 00:26:07.549 --> 00:26:07.559 align:start position:0% connected to the technology right 00:26:07.559 --> 00:26:08.950 align:start position:0% connected to the technology right because<00:26:07.799> right<00:26:07.960> now<00:26:08.120> there<00:26:08.279> really<00:26:08.600> is<00:26:08.760> no 00:26:08.950 --> 00:26:08.960 align:start position:0% because right now there really is no 00:26:08.960 --> 00:26:10.310 align:start position:0% because right now there really is no difference<00:26:09.279> and<00:26:09.440> people<00:26:09.600> don't<00:26:10.120> understand 00:26:10.310 --> 00:26:10.320 align:start position:0% difference and people don't understand 00:26:10.320 --> 00:26:12.190 align:start position:0% difference and people don't understand that<00:26:10.760> so<00:26:10.880> I<00:26:11.000> feel<00:26:11.159> like<00:26:11.559> having<00:26:11.840> something 00:26:12.190 --> 00:26:12.200 align:start position:0% that so I feel like having something 00:26:12.200 --> 00:26:13.750 align:start position:0% that so I feel like having something like<00:26:12.399> that<00:26:12.679> where<00:26:12.919> when<00:26:13.039> the<00:26:13.159> user<00:26:13.520> actually 00:26:13.750 --> 00:26:13.760 align:start position:0% like that where when the user actually 00:26:13.760 --> 00:26:16.029 align:start position:0% like that where when the user actually uses<00:26:14.080> the<00:26:14.279> app<00:26:14.840> that<00:26:14.960> would<00:26:15.200> maybe<00:26:15.720> change 00:26:16.029 --> 00:26:16.039 align:start position:0% uses the app that would maybe change 00:26:16.039 --> 00:26:17.830 align:start position:0% uses the app that would maybe change their<00:26:16.240> perception<00:26:16.600> of<00:26:16.760> things<00:26:16.960> a<00:26:17.039> little<00:26:17.240> bit 00:26:17.830 --> 00:26:17.840 align:start position:0% their perception of things a little bit 00:26:17.840 --> 00:26:20.110 align:start position:0% their perception of things a little bit you<00:26:17.960> mean<00:26:18.240> like<00:26:18.360> a<00:26:18.720> incognito<00:26:19.559> mode<00:26:19.919> or 00:26:20.110 --> 00:26:20.120 align:start position:0% you mean like a incognito mode or 00:26:20.120 --> 00:26:21.630 align:start position:0% you mean like a incognito mode or something<00:26:20.720> yeah<00:26:21.000> yeah<00:26:21.120> something<00:26:21.399> like<00:26:21.520> that 00:26:21.630 --> 00:26:21.640 align:start position:0% something yeah yeah something like that 00:26:21.640 --> 00:26:23.909 align:start position:0% something yeah yeah something like that like<00:26:21.799> incognito<00:26:22.440> mode<00:26:22.760> like<00:26:23.360> it<00:26:23.520> feels 00:26:23.909 --> 00:26:23.919 align:start position:0% like incognito mode like it feels 00:26:23.919 --> 00:26:26.070 align:start position:0% like incognito mode like it feels different<00:26:24.279> because<00:26:24.559> it's<00:26:24.720> like<00:26:24.919> dark<00:26:25.640> yeah 00:26:26.070 --> 00:26:26.080 align:start position:0% different because it's like dark yeah 00:26:26.080 --> 00:26:28.590 align:start position:0% different because it's like dark yeah right<00:26:26.360> it's<00:26:26.559> like<00:26:27.000> or<00:26:27.399> the<00:26:27.760> I<00:26:27.880> think<00:26:28.039> of<00:26:28.399> like 00:26:28.590 --> 00:26:28.600 align:start position:0% right it's like or the I think of like 00:26:28.600 --> 00:26:31.549 align:start position:0% right it's like or the I think of like the<00:26:28.799> TLs<00:26:29.440> like<00:26:29.640> green<00:26:29.960> lock<00:26:30.320> icon<00:26:31.080> like<00:26:31.320> at<00:26:31.399> the 00:26:31.549 --> 00:26:31.559 align:start position:0% the TLs like green lock icon like at the 00:26:31.559 --> 00:26:33.430 align:start position:0% the TLs like green lock icon like at the very<00:26:31.799> least<00:26:32.080> having<00:26:32.360> some<00:26:32.600> visual<00:26:33.000> component 00:26:33.430 --> 00:26:33.440 align:start position:0% very least having some visual component 00:26:33.440 --> 00:26:35.990 align:start position:0% very least having some visual component where<00:26:33.559> it's<00:26:33.760> like<00:26:34.000> oh<00:26:34.840> it's<00:26:35.039> not<00:26:35.480> like<00:26:35.679> a 00:26:35.990 --> 00:26:36.000 align:start position:0% where it's like oh it's not like a 00:26:36.000 --> 00:26:39.070 align:start position:0% where it's like oh it's not like a standard<00:26:36.720> or<00:26:37.039> something<00:26:37.640> but<00:26:38.240> it's<00:26:38.520> basically 00:26:39.070 --> 00:26:39.080 align:start position:0% standard or something but it's basically 00:26:39.080 --> 00:26:41.430 align:start position:0% standard or something but it's basically this<00:26:39.600> Norm<00:26:40.039> you<00:26:40.240> assume<00:26:40.720> that<00:26:40.960> if<00:26:41.080> we<00:26:41.279> have 00:26:41.430 --> 00:26:41.440 align:start position:0% this Norm you assume that if we have 00:26:41.440 --> 00:26:43.750 align:start position:0% this Norm you assume that if we have this<00:26:41.640> green<00:26:41.919> lock<00:26:42.240> icon<00:26:42.799> then<00:26:43.279> you<00:26:43.559> your 00:26:43.750 --> 00:26:43.760 align:start position:0% this green lock icon then you your 00:26:43.760 --> 00:26:45.389 align:start position:0% this green lock icon then you your connection<00:26:44.120> is<00:26:44.360> like<00:26:44.480> more<00:26:44.720> secure<00:26:45.039> in<00:26:45.200> some 00:26:45.389 --> 00:26:45.399 align:start position:0% connection is like more secure in some 00:26:45.399 --> 00:26:46.909 align:start position:0% connection is like more secure in some ways<00:26:45.640> and<00:26:45.799> we're<00:26:45.960> just<00:26:46.080> going<00:26:46.200> to<00:26:46.320> all<00:26:46.559> like 00:26:46.909 --> 00:26:46.919 align:start position:0% ways and we're just going to all like 00:26:46.919 --> 00:26:48.350 align:start position:0% ways and we're just going to all like uphold<00:26:47.320> each<00:26:47.440> other<00:26:47.640> to<00:26:47.840> This<00:26:48.039> Promise 00:26:48.350 --> 00:26:48.360 align:start position:0% uphold each other to This Promise 00:26:48.360 --> 00:26:50.029 align:start position:0% uphold each other to This Promise because<00:26:48.600> at<00:26:48.679> the<00:26:48.760> end<00:26:48.880> of<00:26:49.000> the<00:26:49.159> day<00:26:49.399> like<00:26:49.919> this 00:26:50.029 --> 00:26:50.039 align:start position:0% because at the end of the day like this 00:26:50.039 --> 00:26:52.350 align:start position:0% because at the end of the day like this is<00:26:50.240> all<00:26:50.440> up<00:26:50.600> to<00:26:50.840> like<00:26:51.200> people<00:26:51.640> building<00:26:52.039> apps 00:26:52.350 --> 00:26:52.360 align:start position:0% is all up to like people building apps 00:26:52.360 --> 00:26:54.269 align:start position:0% is all up to like people building apps to<00:26:52.600> just<00:26:52.919> agree<00:26:53.240> on<00:26:53.559> and<00:26:53.679> to<00:26:53.840> like<00:26:53.960> call<00:26:54.120> out 00:26:54.269 --> 00:26:54.279 align:start position:0% to just agree on and to like call out 00:26:54.279 --> 00:26:55.950 align:start position:0% to just agree on and to like call out the<00:26:54.399> people<00:26:54.559> who<00:26:54.679> don't<00:26:54.880> follow<00:26:55.240> this<00:26:55.440> and<00:26:55.559> to 00:26:55.950 --> 00:26:55.960 align:start position:0% the people who don't follow this and to 00:26:55.960 --> 00:26:59.350 align:start position:0% the people who don't follow this and to all<00:26:56.159> work<00:26:56.480> together<00:26:56.679> to<00:26:56.840> communicate 00:26:59.350 --> 00:26:59.360 align:start position:0% all work together to communicate 00:26:59.360 --> 00:27:01.070 align:start position:0% all work together to communicate I<00:26:59.440> think<00:26:59.600> that's<00:26:59.760> a<00:26:59.880> super<00:27:00.120> nice<00:27:00.360> point<00:27:00.640> and 00:27:01.070 --> 00:27:01.080 align:start position:0% I think that's a super nice point and 00:27:01.080 --> 00:27:02.990 align:start position:0% I think that's a super nice point and like<00:27:01.279> if<00:27:01.360> you<00:27:01.520> look<00:27:01.679> at<00:27:02.000> cryptographic<00:27:02.640> papers 00:27:02.990 --> 00:27:03.000 align:start position:0% like if you look at cryptographic papers 00:27:03.000 --> 00:27:05.230 align:start position:0% like if you look at cryptographic papers or<00:27:03.200> whatever<00:27:03.559> when<00:27:03.840> they<00:27:04.440> like<00:27:04.640> draw<00:27:05.039> the 00:27:05.230 --> 00:27:05.240 align:start position:0% or whatever when they like draw the 00:27:05.240 --> 00:27:06.870 align:start position:0% or whatever when they like draw the protocols<00:27:05.760> and<00:27:05.880> The<00:27:05.960> Primitives<00:27:06.559> like<00:27:06.720> they 00:27:06.870 --> 00:27:06.880 align:start position:0% protocols and The Primitives like they 00:27:06.880 --> 00:27:09.389 align:start position:0% protocols and The Primitives like they do<00:27:07.120> have<00:27:07.279> a<00:27:07.440> sort<00:27:07.640> of<00:27:08.120> like<00:27:08.279> it's<00:27:08.520> hashed<00:27:08.960> box 00:27:09.389 --> 00:27:09.399 align:start position:0% do have a sort of like it's hashed box 00:27:09.399 --> 00:27:11.190 align:start position:0% do have a sort of like it's hashed box like<00:27:09.559> it's<00:27:10.039> there's<00:27:10.240> lines<00:27:10.559> in<00:27:10.720> the<00:27:10.840> box<00:27:11.080> when 00:27:11.190 --> 00:27:11.200 align:start position:0% like it's there's lines in the box when 00:27:11.200 --> 00:27:12.710 align:start position:0% like it's there's lines in the box when things<00:27:11.360> are<00:27:11.520> secret<00:27:11.840> shared<00:27:12.159> or<00:27:12.240> it's<00:27:12.360> a<00:27:12.440> clear 00:27:12.710 --> 00:27:12.720 align:start position:0% things are secret shared or it's a clear 00:27:12.720 --> 00:27:14.070 align:start position:0% things are secret shared or it's a clear box<00:27:12.919> when<00:27:13.039> it's<00:27:13.159> in<00:27:13.320> plain<00:27:13.559> text<00:27:13.840> or<00:27:13.919> it's 00:27:14.070 --> 00:27:14.080 align:start position:0% box when it's in plain text or it's 00:27:14.080 --> 00:27:16.389 align:start position:0% box when it's in plain text or it's black<00:27:14.640> whatever<00:27:15.039> so<00:27:15.520> it<00:27:15.679> does<00:27:15.919> exist<00:27:16.159> and<00:27:16.320> I 00:27:16.389 --> 00:27:16.399 align:start position:0% black whatever so it does exist and I 00:27:16.399 --> 00:27:18.310 align:start position:0% black whatever so it does exist and I think<00:27:16.600> this<00:27:16.720> is<00:27:17.039> nice<00:27:17.640> but<00:27:17.799> one<00:27:17.919> other<00:27:18.120> point 00:27:18.310 --> 00:27:18.320 align:start position:0% think this is nice but one other point 00:27:18.320 --> 00:27:21.470 align:start position:0% think this is nice but one other point that<00:27:18.480> I<00:27:18.600> was<00:27:18.919> I<00:27:19.000> wanted<00:27:19.279> to<00:27:19.440> mention<00:27:19.799> was<00:27:20.399> a<00:27:20.559> bit 00:27:21.470 --> 00:27:21.480 align:start position:0% that I was I wanted to mention was a bit 00:27:21.480 --> 00:27:24.070 align:start position:0% that I was I wanted to mention was a bit on<00:27:21.880> still<00:27:22.240> on<00:27:22.360> the<00:27:22.520> design<00:27:22.919> side<00:27:23.120> and<00:27:23.320> also 00:27:24.070 --> 00:27:24.080 align:start position:0% on still on the design side and also 00:27:24.080 --> 00:27:26.590 align:start position:0% on still on the design side and also from<00:27:24.279> Rachel<00:27:24.720> I<00:27:24.840> guess<00:27:25.000> or<00:27:25.159> from<00:27:25.399> cursive<00:27:26.399> is 00:27:26.590 --> 00:27:26.600 align:start position:0% from Rachel I guess or from cursive is 00:27:26.600 --> 00:27:29.590 align:start position:0% from Rachel I guess or from cursive is like<00:27:26.799> that<00:27:26.960> you<00:27:27.200> really<00:27:27.679> play<00:27:28.000> with<00:27:28.320> the<00:27:28.600> ideas 00:27:29.590 --> 00:27:29.600 align:start position:0% like that you really play with the ideas 00:27:29.600 --> 00:27:31.909 align:start position:0% like that you really play with the ideas that<00:27:30.240> you<00:27:30.360> know<00:27:30.880> like<00:27:31.080> the<00:27:31.279> concepts<00:27:31.760> that 00:27:31.909 --> 00:27:31.919 align:start position:0% that you know like the concepts that 00:27:31.919 --> 00:27:34.110 align:start position:0% that you know like the concepts that these<00:27:32.159> programmable<00:27:32.919> crypto<00:27:33.399> Primitives 00:27:34.110 --> 00:27:34.120 align:start position:0% these programmable crypto Primitives 00:27:34.120 --> 00:27:36.750 align:start position:0% these programmable crypto Primitives give<00:27:35.039> and<00:27:35.240> you<00:27:35.520> sort<00:27:35.760> of<00:27:36.159> yeah<00:27:36.320> you<00:27:36.440> play<00:27:36.640> with 00:27:36.750 --> 00:27:36.760 align:start position:0% give and you sort of yeah you play with 00:27:36.760 --> 00:27:38.029 align:start position:0% give and you sort of yeah you play with them<00:27:36.880> in<00:27:37.000> your<00:27:37.080> own<00:27:37.240> minds<00:27:37.480> and<00:27:37.640> sort<00:27:37.799> of 00:27:38.029 --> 00:27:38.039 align:start position:0% them in your own minds and sort of 00:27:38.039 --> 00:27:39.470 align:start position:0% them in your own minds and sort of somehow<00:27:38.520> translate<00:27:39.000> this<00:27:39.159> I<00:27:39.240> don't<00:27:39.360> know 00:27:39.470 --> 00:27:39.480 align:start position:0% somehow translate this I don't know 00:27:39.480 --> 00:27:41.389 align:start position:0% somehow translate this I don't know about<00:27:39.720> design<00:27:40.000> or<00:27:40.159> how<00:27:40.279> you<00:27:40.399> do<00:27:40.600> it<00:27:41.120> but<00:27:41.279> like 00:27:41.389 --> 00:27:41.399 align:start position:0% about design or how you do it but like 00:27:41.399 --> 00:27:43.230 align:start position:0% about design or how you do it but like you<00:27:41.559> somehow<00:27:41.919> translate<00:27:42.399> this<00:27:42.519> to<00:27:42.679> the<00:27:42.799> user 00:27:43.230 --> 00:27:43.240 align:start position:0% you somehow translate this to the user 00:27:43.240 --> 00:27:45.630 align:start position:0% you somehow translate this to the user so<00:27:43.480> like<00:27:43.640> downstairs<00:27:44.200> in<00:27:44.360> the<00:27:44.480> museum<00:27:45.320> there's 00:27:45.630 --> 00:27:45.640 align:start position:0% so like downstairs in the museum there's 00:27:45.640 --> 00:27:47.470 align:start position:0% so like downstairs in the museum there's these<00:27:45.799> art<00:27:46.120> pieces<00:27:46.600> where<00:27:46.799> there's<00:27:47.000> the<00:27:47.159> QR 00:27:47.470 --> 00:27:47.480 align:start position:0% these art pieces where there's the QR 00:27:47.480 --> 00:27:50.029 align:start position:0% these art pieces where there's the QR code<00:27:47.760> that<00:27:47.880> you<00:27:48.000> can<00:27:48.360> scan<00:27:49.360> and<00:27:49.519> input<00:27:49.840> an 00:27:50.029 --> 00:27:50.039 align:start position:0% code that you can scan and input an 00:27:50.039 --> 00:27:51.789 align:start position:0% code that you can scan and input an emotion<00:27:50.559> and<00:27:50.760> like<00:27:50.880> it<00:27:51.039> explains<00:27:51.480> like<00:27:51.679> Hey 00:27:51.789 --> 00:27:51.799 align:start position:0% emotion and like it explains like Hey 00:27:51.799 --> 00:27:53.509 align:start position:0% emotion and like it explains like Hey we're<00:27:51.919> going<00:27:52.000> to<00:27:52.159> send<00:27:52.360> a<00:27:52.519> hash<00:27:52.840> of<00:27:53.080> this<00:27:53.279> and 00:27:53.509 --> 00:27:53.519 align:start position:0% we're going to send a hash of this and 00:27:53.519 --> 00:27:55.350 align:start position:0% we're going to send a hash of this and like<00:27:53.799> prove<00:27:54.159> that<00:27:54.279> you<00:27:54.440> know<00:27:54.640> the<00:27:54.799> pre-image 00:27:55.350 --> 00:27:55.360 align:start position:0% like prove that you know the pre-image 00:27:55.360 --> 00:27:57.750 align:start position:0% like prove that you know the pre-image and<00:27:55.519> like<00:27:55.720> this<00:27:55.840> is<00:27:56.000> so<00:27:56.279> cool<00:27:56.760> like<00:27:56.960> even<00:27:57.279> Just 00:27:57.750 --> 00:27:57.760 align:start position:0% and like this is so cool like even Just 00:27:57.760 --> 00:27:59.590 align:start position:0% and like this is so cool like even Just sh<00:27:58.200> showing<00:27:58.600> people<00:27:58.840> the<00:27:59.080> language<00:27:59.480> and 00:27:59.590 --> 00:27:59.600 align:start position:0% sh showing people the language and 00:27:59.600 --> 00:28:02.630 align:start position:0% sh showing people the language and showing<00:28:00.080> people<00:28:00.559> like<00:28:00.919> just<00:28:01.120> mentioning<00:28:01.720> it 00:28:02.630 --> 00:28:02.640 align:start position:0% showing people like just mentioning it 00:28:02.640 --> 00:28:04.269 align:start position:0% showing people like just mentioning it just<00:28:02.799> saying<00:28:03.159> okay<00:28:03.360> this<00:28:03.440> is<00:28:03.600> what's<00:28:03.840> going<00:28:04.039> on 00:28:04.269 --> 00:28:04.279 align:start position:0% just saying okay this is what's going on 00:28:04.279 --> 00:28:06.870 align:start position:0% just saying okay this is what's going on here<00:28:04.559> I<00:28:04.640> think<00:28:04.919> makes<00:28:05.240> people<00:28:05.559> aware<00:28:05.960> and<00:28:06.279> like 00:28:06.870 --> 00:28:06.880 align:start position:0% here I think makes people aware and like 00:28:06.880 --> 00:28:09.669 align:start position:0% here I think makes people aware and like it's<00:28:07.039> like<00:28:07.320> okay<00:28:07.519> cool<00:28:07.760> I'm<00:28:07.880> doing<00:28:08.679> some 00:28:09.669 --> 00:28:09.679 align:start position:0% it's like okay cool I'm doing some 00:28:09.679 --> 00:28:12.509 align:start position:0% it's like okay cool I'm doing some crypto<00:28:10.519> yeah<00:28:10.760> and<00:28:11.120> I<00:28:11.399> so<00:28:11.679> I<00:28:11.799> was<00:28:12.120> just<00:28:12.279> getting 00:28:12.509 --> 00:28:12.519 align:start position:0% crypto yeah and I so I was just getting 00:28:12.519 --> 00:28:14.149 align:start position:0% crypto yeah and I so I was just getting lunch<00:28:12.799> with<00:28:12.960> Gordon<00:28:13.279> who's<00:28:13.519> like<00:28:13.640> the<00:28:13.720> artist 00:28:14.149 --> 00:28:14.159 align:start position:0% lunch with Gordon who's like the artist 00:28:14.159 --> 00:28:17.310 align:start position:0% lunch with Gordon who's like the artist behind<00:28:14.360> that<00:28:14.559> piece<00:28:15.039> like<00:28:15.519> basically<00:28:16.200> like<00:28:17.120> uh 00:28:17.310 --> 00:28:17.320 align:start position:0% behind that piece like basically like uh 00:28:17.320 --> 00:28:19.630 align:start position:0% behind that piece like basically like uh we<00:28:17.440> were<00:28:17.640> talking<00:28:17.960> about<00:28:18.200> ZK<00:28:18.679> cryptography 00:28:19.630 --> 00:28:19.640 align:start position:0% we were talking about ZK cryptography 00:28:19.640 --> 00:28:21.389 align:start position:0% we were talking about ZK cryptography for<00:28:20.039> for<00:28:20.200> a<00:28:20.320> while<00:28:20.519> for<00:28:20.679> a<00:28:20.760> few<00:28:20.919> hours<00:28:21.159> and<00:28:21.320> like 00:28:21.389 --> 00:28:21.399 align:start position:0% for for a while for a few hours and like 00:28:21.399 --> 00:28:22.630 align:start position:0% for for a while for a few hours and like he<00:28:21.519> made<00:28:21.720> this<00:28:21.840> wonderful<00:28:22.159> R<00:28:22.399> piece 00:28:22.630 --> 00:28:22.640 align:start position:0% he made this wonderful R piece 00:28:22.640 --> 00:28:23.750 align:start position:0% he made this wonderful R piece explaining<00:28:23.039> how<00:28:23.159> you<00:28:23.240> can<00:28:23.440> keep<00:28:23.600> your 00:28:23.750 --> 00:28:23.760 align:start position:0% explaining how you can keep your 00:28:23.760 --> 00:28:26.350 align:start position:0% explaining how you can keep your emotions<00:28:24.200> private<00:28:24.600> blah<00:28:24.760> blah<00:28:24.960> blah<00:28:25.640> um<00:28:26.080> but<00:28:26.240> I 00:28:26.350 --> 00:28:26.360 align:start position:0% emotions private blah blah blah um but I 00:28:26.360 --> 00:28:28.590 align:start position:0% emotions private blah blah blah um but I feel<00:28:26.640> like<00:28:27.440> what<00:28:27.919> what<00:28:28.120> what<00:28:28.240> came<00:28:28.360> out<00:28:28.440> of 00:28:28.590 --> 00:28:28.600 align:start position:0% feel like what what what came out of 00:28:28.600 --> 00:28:30.830 align:start position:0% feel like what what what came out of that<00:28:28.760> conversation<00:28:29.519> is<00:28:29.760> that<00:28:30.120> the<00:28:30.399> most 00:28:30.830 --> 00:28:30.840 align:start position:0% that conversation is that the most 00:28:30.840 --> 00:28:32.470 align:start position:0% that conversation is that the most important<00:28:31.320> thing<00:28:31.519> for<00:28:31.840> all<00:28:31.960> of<00:28:32.120> us<00:28:32.240> who<00:28:32.360> are 00:28:32.470 --> 00:28:32.480 align:start position:0% important thing for all of us who are 00:28:32.480 --> 00:28:33.950 align:start position:0% important thing for all of us who are building<00:28:32.840> apps<00:28:33.240> in<00:28:33.440> programmable 00:28:33.950 --> 00:28:33.960 align:start position:0% building apps in programmable 00:28:33.960 --> 00:28:36.389 align:start position:0% building apps in programmable cryptography<00:28:34.919> is<00:28:35.159> communication<00:28:35.919> like<00:28:36.200> we 00:28:36.389 --> 00:28:36.399 align:start position:0% cryptography is communication like we 00:28:36.399 --> 00:28:38.230 align:start position:0% cryptography is communication like we cannot<00:28:36.720> just<00:28:36.840> be<00:28:37.080> technologists<00:28:37.760> like<00:28:38.000> if<00:28:38.120> we 00:28:38.230 --> 00:28:38.240 align:start position:0% cannot just be technologists like if we 00:28:38.240 --> 00:28:39.630 align:start position:0% cannot just be technologists like if we want<00:28:38.360> to<00:28:38.519> actually<00:28:38.720> build<00:28:39.000> apps<00:28:39.240> that<00:28:39.399> people 00:28:39.630 --> 00:28:39.640 align:start position:0% want to actually build apps that people 00:28:39.640 --> 00:28:41.310 align:start position:0% want to actually build apps that people use<00:28:40.000> like<00:28:40.159> we<00:28:40.279> need<00:28:40.440> to<00:28:40.600> communicate<00:28:41.120> and<00:28:41.200> we 00:28:41.310 --> 00:28:41.320 align:start position:0% use like we need to communicate and we 00:28:41.320 --> 00:28:43.389 align:start position:0% use like we need to communicate and we need<00:28:41.440> to<00:28:41.600> talk<00:28:41.720> to<00:28:41.919> people<00:28:42.200> and<00:28:42.440> like<00:28:42.840> explain 00:28:43.389 --> 00:28:43.399 align:start position:0% need to talk to people and like explain 00:28:43.399 --> 00:28:46.149 align:start position:0% need to talk to people and like explain hey<00:28:43.919> this<00:28:44.120> is<00:28:44.519> what<00:28:44.760> privacy<00:28:45.120> means<00:28:45.600> this<00:28:45.760> is 00:28:46.149 --> 00:28:46.159 align:start position:0% hey this is what privacy means this is 00:28:46.159 --> 00:28:48.350 align:start position:0% hey this is what privacy means this is why<00:28:46.519> you<00:28:46.640> should<00:28:46.919> want<00:28:47.159> it<00:28:47.720> this<00:28:47.840> is<00:28:48.080> what 00:28:48.350 --> 00:28:48.360 align:start position:0% why you should want it this is what 00:28:48.360 --> 00:28:50.710 align:start position:0% why you should want it this is what decentralization<00:28:49.159> means<00:28:49.440> or<00:28:49.640> whatever<00:28:50.320> like 00:28:50.710 --> 00:28:50.720 align:start position:0% decentralization means or whatever like 00:28:50.720 --> 00:28:52.870 align:start position:0% decentralization means or whatever like communication<00:28:51.519> is<00:28:51.760> arguably<00:28:52.360> like<00:28:52.519> more<00:28:52.679> than 00:28:52.870 --> 00:28:52.880 align:start position:0% communication is arguably like more than 00:28:52.880 --> 00:28:54.110 align:start position:0% communication is arguably like more than half<00:28:53.039> the<00:28:53.200> job<00:28:53.399> you<00:28:53.519> can't<00:28:53.679> just<00:28:53.799> build<00:28:54.000> the 00:28:54.110 --> 00:28:54.120 align:start position:0% half the job you can't just build the 00:28:54.120 --> 00:28:55.509 align:start position:0% half the job you can't just build the technology<00:28:54.559> build<00:28:54.760> The<00:28:54.840> Primitives<00:28:55.240> and<00:28:55.399> just 00:28:55.509 --> 00:28:55.519 align:start position:0% technology build The Primitives and just 00:28:55.519 --> 00:28:56.669 align:start position:0% technology build The Primitives and just like<00:28:55.640> throw<00:28:55.799> it<00:28:55.919> out<00:28:56.080> there<00:28:56.240> and<00:28:56.440> hope 00:28:56.669 --> 00:28:56.679 align:start position:0% like throw it out there and hope 00:28:56.679 --> 00:28:58.350 align:start position:0% like throw it out there and hope something<00:28:56.919> Good's<00:28:57.159> going<00:28:57.240> to<00:28:57.399> happen<00:28:58.240> but 00:28:58.350 --> 00:28:58.360 align:start position:0% something Good's going to happen but 00:28:58.360 --> 00:29:00.070 align:start position:0% something Good's going to happen but it's<00:28:58.480> not<00:28:58.640> even<00:28:58.840> just<00:28:59.039> regular<00:28:59.440> communication 00:29:00.070 --> 00:29:00.080 align:start position:0% it's not even just regular communication 00:29:00.080 --> 00:29:02.630 align:start position:0% it's not even just regular communication it's<00:29:00.279> like<00:29:00.559> you<00:29:00.760> make<00:29:01.000> it<00:29:01.200> look<00:29:01.640> cool<00:29:02.000> and<00:29:02.240> fun 00:29:02.630 --> 00:29:02.640 align:start position:0% it's like you make it look cool and fun 00:29:02.640 --> 00:29:04.310 align:start position:0% it's like you make it look cool and fun and<00:29:02.799> entertaining<00:29:03.480> and<00:29:03.600> like<00:29:03.760> if<00:29:03.880> I'm<00:29:04.039> using 00:29:04.310 --> 00:29:04.320 align:start position:0% and entertaining and like if I'm using 00:29:04.320 --> 00:29:06.470 align:start position:0% and entertaining and like if I'm using an<00:29:04.559> app<00:29:05.159> I<00:29:05.320> gen<00:29:05.720> okay<00:29:05.840> unless<00:29:06.120> it's<00:29:06.240> like<00:29:06.360> a 00:29:06.470 --> 00:29:06.480 align:start position:0% an app I gen okay unless it's like a 00:29:06.480 --> 00:29:08.389 align:start position:0% an app I gen okay unless it's like a super<00:29:06.760> serious<00:29:07.200> thing<00:29:07.480> that<00:29:07.600> I<00:29:07.720> want<00:29:08.080> actual 00:29:08.389 --> 00:29:08.399 align:start position:0% super serious thing that I want actual 00:29:08.399 --> 00:29:11.509 align:start position:0% super serious thing that I want actual privacy<00:29:08.880> like<00:29:09.000> real<00:29:09.279> real<00:29:09.640> privacy<00:29:10.080> for<00:29:11.080> fine 00:29:11.509 --> 00:29:11.519 align:start position:0% privacy like real real privacy for fine 00:29:11.519 --> 00:29:13.029 align:start position:0% privacy like real real privacy for fine but<00:29:11.640> if<00:29:11.799> I'm<00:29:11.960> just<00:29:12.080> like<00:29:12.240> using<00:29:12.480> an<00:29:12.679> app<00:29:12.880> I'm 00:29:13.029 --> 00:29:13.039 align:start position:0% but if I'm just like using an app I'm 00:29:13.039 --> 00:29:14.470 align:start position:0% but if I'm just like using an app I'm probably<00:29:13.360> doing<00:29:13.640> it<00:29:13.760> for<00:29:13.960> some<00:29:14.159> sort<00:29:14.360> of 00:29:14.470 --> 00:29:14.480 align:start position:0% probably doing it for some sort of 00:29:14.480 --> 00:29:16.110 align:start position:0% probably doing it for some sort of entertainment<00:29:15.039> or<00:29:15.240> like<00:29:15.360> some<00:29:15.519> fun<00:29:15.760> or<00:29:15.919> to 00:29:16.110 --> 00:29:16.120 align:start position:0% entertainment or like some fun or to 00:29:16.120 --> 00:29:17.870 align:start position:0% entertainment or like some fun or to like<00:29:16.240> engage<00:29:16.559> with<00:29:16.720> my<00:29:16.840> friends<00:29:17.200> or<00:29:17.399> whatever 00:29:17.870 --> 00:29:17.880 align:start position:0% like engage with my friends or whatever 00:29:17.880 --> 00:29:20.509 align:start position:0% like engage with my friends or whatever like<00:29:18.640> and<00:29:18.840> then<00:29:19.200> having<00:29:19.440> it<00:29:19.679> like<00:29:19.840> look<00:29:20.200> cool 00:29:20.509 --> 00:29:20.519 align:start position:0% like and then having it like look cool 00:29:20.519 --> 00:29:22.830 align:start position:0% like and then having it like look cool and<00:29:20.720> feel<00:29:21.080> cool<00:29:21.320> and<00:29:21.480> feel<00:29:21.720> like<00:29:21.880> a<00:29:22.080> shiny<00:29:22.440> cool 00:29:22.830 --> 00:29:22.840 align:start position:0% and feel cool and feel like a shiny cool 00:29:22.840 --> 00:29:24.870 align:start position:0% and feel cool and feel like a shiny cool app<00:29:23.640> then<00:29:23.799> it's<00:29:24.039> great<00:29:24.320> and<00:29:24.440> I<00:29:24.519> think<00:29:24.679> this<00:29:24.760> is 00:29:24.870 --> 00:29:24.880 align:start position:0% app then it's great and I think this is 00:29:24.880 --> 00:29:26.909 align:start position:0% app then it's great and I think this is something<00:29:25.120> that<00:29:25.240> you<00:29:25.399> do<00:29:25.640> well<00:29:26.000> like<00:29:26.480> uh<00:29:26.799> it 00:29:26.909 --> 00:29:26.919 align:start position:0% something that you do well like uh it 00:29:26.919 --> 00:29:29.070 align:start position:0% something that you do well like uh it feels<00:29:27.240> cool<00:29:27.440> I<00:29:27.519> want<00:29:27.640> to<00:29:27.720> be<00:29:27.799> part<00:29:27.919> of<00:29:28.279> it<00:29:28.559> so 00:29:29.070 --> 00:29:29.080 align:start position:0% feels cool I want to be part of it so 00:29:29.080 --> 00:29:31.710 align:start position:0% feels cool I want to be part of it so yeah<00:29:29.440> I 00:29:31.710 --> 00:29:31.720 align:start position:0% 00:29:31.720 --> 00:29:34.669 align:start position:0% think<00:29:32.720> yeah<00:29:33.120> like<00:29:33.440> that's<00:29:33.720> what's<00:29:34.039> cool<00:29:34.360> about 00:29:34.669 --> 00:29:34.679 align:start position:0% think yeah like that's what's cool about 00:29:34.679 --> 00:29:37.669 align:start position:0% think yeah like that's what's cool about cursive<00:29:35.240> is<00:29:35.480> like<00:29:35.679> they<00:29:35.799> make<00:29:36.000> it<00:29:36.240> like<00:29:36.559> joyful 00:29:37.669 --> 00:29:37.679 align:start position:0% cursive is like they make it like joyful 00:29:37.679 --> 00:29:42.470 align:start position:0% cursive is like they make it like joyful social<00:29:38.679> um<00:29:39.159> and<00:29:40.000> like<00:29:40.880> uh<00:29:41.159> they<00:29:41.399> sort<00:29:41.679> of<00:29:42.320> it's 00:29:42.470 --> 00:29:42.480 align:start position:0% social um and like uh they sort of it's 00:29:42.480 --> 00:29:46.789 align:start position:0% social um and like uh they sort of it's sort<00:29:42.679> of<00:29:42.840> turning<00:29:43.519> that<00:29:44.480> um<00:29:45.480> privacy<00:29:46.240> as<00:29:46.480> like 00:29:46.789 --> 00:29:46.799 align:start position:0% sort of turning that um privacy as like 00:29:46.799 --> 00:29:49.310 align:start position:0% sort of turning that um privacy as like isolation<00:29:47.399> and<00:29:47.720> darkness<00:29:48.480> kind<00:29:48.600> of<00:29:48.799> metaphor 00:29:49.310 --> 00:29:49.320 align:start position:0% isolation and darkness kind of metaphor 00:29:49.320 --> 00:29:54.070 align:start position:0% isolation and darkness kind of metaphor on<00:29:49.519> its<00:29:49.760> head<00:29:50.960> so<00:29:51.960> um<00:29:52.600> that<00:29:52.679> was<00:29:52.880> really<00:29:53.120> cool<00:29:53.720> I 00:29:54.070 --> 00:29:54.080 align:start position:0% on its head so um that was really cool I 00:29:54.080 --> 00:29:59.029 align:start position:0% on its head so um that was really cool I I<00:29:54.679> think<00:29:55.679> yeah<00:29:56.399> um<00:29:56.840> all<00:29:57.080> these<00:29:57.440> ux<00:29:58.279> insights 00:29:59.029 --> 00:29:59.039 align:start position:0% I think yeah um all these ux insights 00:29:59.039 --> 00:30:02.149 align:start position:0% I think yeah um all these ux insights there's<00:29:59.440> no<00:30:00.080> way<00:30:00.600> to<00:30:01.039> get<00:30:01.320> them<00:30:01.799> without 00:30:02.149 --> 00:30:02.159 align:start position:0% there's no way to get them without 00:30:02.159 --> 00:30:04.870 align:start position:0% there's no way to get them without deploying<00:30:03.000> in<00:30:03.159> the<00:30:03.360> wild<00:30:03.799> without<00:30:04.120> being<00:30:04.360> in 00:30:04.870 --> 00:30:04.880 align:start position:0% deploying in the wild without being in 00:30:04.880 --> 00:30:09.269 align:start position:0% deploying in the wild without being in production<00:30:06.080> um<00:30:07.080> I<00:30:07.640> guess<00:30:08.640> I'm<00:30:08.880> also 00:30:09.269 --> 00:30:09.279 align:start position:0% production um I guess I'm also 00:30:09.279 --> 00:30:13.070 align:start position:0% production um I guess I'm also interested<00:30:09.960> in<00:30:10.640> sort<00:30:10.880> of<00:30:11.039> on<00:30:11.200> the<00:30:11.440> back<00:30:12.080> end 00:30:13.070 --> 00:30:13.080 align:start position:0% interested in sort of on the back end 00:30:13.080 --> 00:30:18.070 align:start position:0% interested in sort of on the back end like<00:30:13.799> um<00:30:14.080> the<00:30:14.200> on<00:30:14.320> the<00:30:14.559> infrastructure<00:30:15.840> side 00:30:18.070 --> 00:30:18.080 align:start position:0% like um the on the infrastructure side 00:30:18.080 --> 00:30:21.750 align:start position:0% like um the on the infrastructure side um<00:30:19.080> so<00:30:19.880> I<00:30:20.080> I<00:30:20.200> guess<00:30:20.360> I<00:30:20.440> have<00:30:20.679> two<00:30:21.360> sort<00:30:21.559> of 00:30:21.750 --> 00:30:21.760 align:start position:0% um so I I guess I have two sort of 00:30:21.760 --> 00:30:23.350 align:start position:0% um so I I guess I have two sort of questions<00:30:22.120> about<00:30:22.320> infrastructure<00:30:23.000> first<00:30:23.159> of 00:30:23.350 --> 00:30:23.360 align:start position:0% questions about infrastructure first of 00:30:23.360 --> 00:30:29.870 align:start position:0% questions about infrastructure first of all<00:30:24.679> um<00:30:25.679> is<00:30:25.840> it<00:30:26.399> expensive<00:30:27.039> to<00:30:27.200> run<00:30:27.480> these<00:30:27.640> apps 00:30:29.870 --> 00:30:29.880 align:start position:0% all um is it expensive to run these apps 00:30:29.880 --> 00:30:33.430 align:start position:0% all um is it expensive to run these apps so<00:30:30.880> it's<00:30:31.000> a<00:30:31.159> leading<00:30:31.679> question<00:30:32.320> cuz<00:30:32.919> I<00:30:33.039> know<00:30:33.240> it 00:30:33.430 --> 00:30:33.440 align:start position:0% so it's a leading question cuz I know it 00:30:33.440 --> 00:30:35.750 align:start position:0% so it's a leading question cuz I know it is<00:30:33.720> I<00:30:33.799> want<00:30:33.919> to<00:30:34.080> know<00:30:34.440> how<00:30:34.679> expensive<00:30:35.360> and<00:30:35.519> then 00:30:35.750 --> 00:30:35.760 align:start position:0% is I want to know how expensive and then 00:30:35.760 --> 00:30:38.750 align:start position:0% is I want to know how expensive and then like<00:30:36.640> basically<00:30:37.440> what<00:30:37.760> improvements<00:30:38.519> do<00:30:38.640> you 00:30:38.750 --> 00:30:38.760 align:start position:0% like basically what improvements do you 00:30:38.760 --> 00:30:40.830 align:start position:0% like basically what improvements do you see<00:30:39.039> in<00:30:39.279> store<00:30:39.919> what<00:30:40.080> improvements<00:30:40.480> are<00:30:40.600> you 00:30:40.830 --> 00:30:40.840 align:start position:0% see in store what improvements are you 00:30:40.840 --> 00:30:41.990 align:start position:0% see in store what improvements are you excited 00:30:41.990 --> 00:30:42.000 align:start position:0% excited 00:30:42.000 --> 00:30:45.310 align:start position:0% excited about<00:30:43.000> my<00:30:43.240> second<00:30:43.679> question<00:30:44.080> is<00:30:44.559> sort<00:30:44.840> of<00:30:45.000> a 00:30:45.310 --> 00:30:45.320 align:start position:0% about my second question is sort of a 00:30:45.320 --> 00:30:49.149 align:start position:0% about my second question is sort of a spicier<00:30:46.000> one<00:30:46.720> and<00:30:46.880> it's<00:30:47.120> about<00:30:47.840> um 00:30:49.149 --> 00:30:49.159 align:start position:0% spicier one and it's about um 00:30:49.159 --> 00:30:51.669 align:start position:0% spicier one and it's about um decentralization<00:30:50.159> so<00:30:50.799> for 00:30:51.669 --> 00:30:51.679 align:start position:0% decentralization so for 00:30:51.679 --> 00:30:55.310 align:start position:0% decentralization so for example<00:30:52.679> for<00:30:52.919> example<00:30:53.519> worldcoin<00:30:54.519> um<00:30:54.960> they're 00:30:55.310 --> 00:30:55.320 align:start position:0% example for example worldcoin um they're 00:30:55.320 --> 00:30:58.029 align:start position:0% example for example worldcoin um they're secret<00:30:55.679> sharing<00:30:56.440> their 00:30:58.029 --> 00:30:58.039 align:start position:0% secret sharing their 00:30:58.039 --> 00:30:59.990 align:start position:0% secret sharing their Iris<00:30:58.519> codes<00:30:59.039> using 00:30:59.990 --> 00:31:00.000 align:start position:0% Iris codes using 00:31:00.000 --> 00:31:04.629 align:start position:0% Iris codes using T<00:31:01.000> um<00:31:01.279> to<00:31:01.600> three<00:31:02.000> servers<00:31:03.000> so<00:31:03.519> to<00:31:03.720> me<00:31:04.120> three<00:31:04.519> is 00:31:04.629 --> 00:31:04.639 align:start position:0% T um to three servers so to me three is 00:31:04.639 --> 00:31:09.070 align:start position:0% T um to three servers so to me three is a<00:31:04.880> small<00:31:05.519> number<00:31:06.519> um<00:31:07.000> how<00:31:07.159> do<00:31:07.440> we<00:31:08.360> yeah<00:31:08.760> I<00:31:08.919> I'm 00:31:09.070 --> 00:31:09.080 align:start position:0% a small number um how do we yeah I I'm 00:31:09.080 --> 00:31:12.149 align:start position:0% a small number um how do we yeah I I'm wondering<00:31:09.679> like<00:31:10.519> another<00:31:10.960> example<00:31:11.360> is<00:31:11.519> TLS 00:31:12.149 --> 00:31:12.159 align:start position:0% wondering like another example is TLS 00:31:12.159 --> 00:31:16.990 align:start position:0% wondering like another example is TLS notary<00:31:13.200> so<00:31:14.200> they<00:31:14.559> rely<00:31:15.200> on<00:31:15.559> a<00:31:15.799> set<00:31:16.279> of<00:31:16.480> trusted 00:31:16.990 --> 00:31:17.000 align:start position:0% notary so they rely on a set of trusted 00:31:17.000 --> 00:31:20.750 align:start position:0% notary so they rely on a set of trusted notaries<00:31:17.840> to<00:31:18.039> be<00:31:18.519> the<00:31:18.720> other<00:31:19.039> party<00:31:19.720> in<00:31:19.840> the 00:31:20.750 --> 00:31:20.760 align:start position:0% notaries to be the other party in the 00:31:20.760 --> 00:31:25.789 align:start position:0% notaries to be the other party in the 2pc<00:31:21.760> um<00:31:22.519> and<00:31:23.320> how<00:31:23.600> big<00:31:23.919> is<00:31:24.159> this<00:31:24.399> set<00:31:24.919> so<00:31:25.600> yeah 00:31:25.789 --> 00:31:25.799 align:start position:0% 2pc um and how big is this set so yeah 00:31:25.799 --> 00:31:27.669 align:start position:0% 2pc um and how big is this set so yeah it's<00:31:26.200> it's<00:31:26.480> kind<00:31:26.639> of<00:31:26.840> an<00:31:27.039> infrastructure 00:31:27.669 --> 00:31:27.679 align:start position:0% it's it's kind of an infrastructure 00:31:27.679 --> 00:31:29.110 align:start position:0% it's it's kind of an infrastructure question<00:31:28.120> but<00:31:28.200> it's<00:31:28.399> also<00:31:28.639> kind<00:31:28.799> of<00:31:28.919> a 00:31:29.110 --> 00:31:29.120 align:start position:0% question but it's also kind of a 00:31:29.120 --> 00:31:31.870 align:start position:0% question but it's also kind of a decentralization<00:31:30.120> question<00:31:30.559> like<00:31:31.159> um 00:31:31.870 --> 00:31:31.880 align:start position:0% decentralization question like um 00:31:31.880 --> 00:31:36.149 align:start position:0% decentralization question like um underlying<00:31:32.880> these<00:31:33.480> Primitives<00:31:34.480> like<00:31:35.240> what 00:31:36.149 --> 00:31:36.159 align:start position:0% underlying these Primitives like what 00:31:36.159 --> 00:31:38.269 align:start position:0% underlying these Primitives like what implementations<00:31:37.159> and<00:31:37.399> what<00:31:37.600> infrastructure 00:31:38.269 --> 00:31:38.279 align:start position:0% implementations and what infrastructure 00:31:38.279 --> 00:31:41.350 align:start position:0% implementations and what infrastructure are<00:31:38.440> we<00:31:38.760> actually<00:31:39.159> using<00:31:40.159> um<00:31:40.799> and<00:31:41.039> yeah<00:31:41.279> what 00:31:41.350 --> 00:31:41.360 align:start position:0% are we actually using um and yeah what 00:31:41.360 --> 00:31:46.310 align:start position:0% are we actually using um and yeah what are<00:31:41.519> your<00:31:41.720> thoughts<00:31:41.960> on<00:31:42.480> how<00:31:42.760> this<00:31:42.919> will 00:31:46.310 --> 00:31:46.320 align:start position:0% 00:31:46.320 --> 00:31:48.870 align:start position:0% develop<00:31:47.320> should<00:31:47.519> I<00:31:47.679> start<00:31:48.159> we<00:31:48.360> laughed<00:31:48.720> when 00:31:48.870 --> 00:31:48.880 align:start position:0% develop should I start we laughed when 00:31:48.880 --> 00:31:50.509 align:start position:0% develop should I start we laughed when you<00:31:49.240> brought<00:31:49.519> this<00:31:49.679> up<00:31:49.880> and<00:31:50.000> I<00:31:50.080> wanted<00:31:50.320> to 00:31:50.509 --> 00:31:50.519 align:start position:0% you brought this up and I wanted to 00:31:50.519 --> 00:31:52.590 align:start position:0% you brought this up and I wanted to explain<00:31:50.880> why<00:31:51.039> we<00:31:51.200> laughed<00:31:52.120> and<00:31:52.240> I<00:31:52.320> don't<00:31:52.440> know 00:31:52.590 --> 00:31:52.600 align:start position:0% explain why we laughed and I don't know 00:31:52.600 --> 00:31:53.950 align:start position:0% explain why we laughed and I don't know if<00:31:52.720> I<00:31:52.799> should<00:31:53.000> say<00:31:53.159> it<00:31:53.320> like<00:31:53.440> in<00:31:53.519> front<00:31:53.720> of<00:31:53.799> a 00:31:53.950 --> 00:31:53.960 align:start position:0% if I should say it like in front of a 00:31:53.960 --> 00:31:55.230 align:start position:0% if I should say it like in front of a room<00:31:54.159> because<00:31:54.360> we<00:31:54.480> haven't<00:31:54.720> discussed<00:31:55.120> this 00:31:55.230 --> 00:31:55.240 align:start position:0% room because we haven't discussed this 00:31:55.240 --> 00:31:57.950 align:start position:0% room because we haven't discussed this at<00:31:55.360> all<00:31:55.519> with<00:31:55.639> the<00:31:55.720> teams<00:31:56.120> but<00:31:56.320> like<00:31:56.880> so<00:31:57.639> like 00:31:57.950 --> 00:31:57.960 align:start position:0% at all with the teams but like so like 00:31:57.960 --> 00:32:01.269 align:start position:0% at all with the teams but like so like this<00:31:58.159> week<00:31:58.720> was<00:31:58.880> the<00:31:59.080> first<00:31:59.760> time<00:32:00.120> we<00:32:00.440> deployed 00:32:01.269 --> 00:32:01.279 align:start position:0% this week was the first time we deployed 00:32:01.279 --> 00:32:03.629 align:start position:0% this week was the first time we deployed let's<00:32:01.480> say<00:32:01.679> Co<00:32:02.039> snarks<00:32:02.559> in<00:32:02.799> like<00:32:03.000> prod<00:32:03.440> like 00:32:03.629 --> 00:32:03.639 align:start position:0% let's say Co snarks in like prod like 00:32:03.639 --> 00:32:06.149 align:start position:0% let's say Co snarks in like prod like properly<00:32:04.200> so<00:32:04.399> like<00:32:04.559> this<00:32:04.720> week<00:32:04.960> is<00:32:05.200> it's<00:32:05.440> like 00:32:06.149 --> 00:32:06.159 align:start position:0% properly so like this week is it's like 00:32:06.159 --> 00:32:08.230 align:start position:0% properly so like this week is it's like fresh<00:32:06.480> out<00:32:06.679> of<00:32:06.799> the<00:32:06.960> oven<00:32:07.399> and<00:32:07.559> it's<00:32:07.799> like 00:32:08.230 --> 00:32:08.240 align:start position:0% fresh out of the oven and it's like 00:32:08.240 --> 00:32:11.430 align:start position:0% fresh out of the oven and it's like messy<00:32:08.840> it's<00:32:09.000> been<00:32:09.600> a<00:32:09.720> bit<00:32:09.960> messy<00:32:10.840> it's<00:32:11.000> all<00:32:11.200> our 00:32:11.430 --> 00:32:11.440 align:start position:0% messy it's been a bit messy it's all our 00:32:11.440 --> 00:32:12.830 align:start position:0% messy it's been a bit messy it's all our fault<00:32:11.720> they<00:32:11.840> didn't<00:32:12.039> do<00:32:12.200> anything<00:32:12.480> wrong<00:32:12.720> it's 00:32:12.830 --> 00:32:12.840 align:start position:0% fault they didn't do anything wrong it's 00:32:12.840 --> 00:32:17.629 align:start position:0% fault they didn't do anything wrong it's not<00:32:13.120> like<00:32:14.120> so<00:32:14.639> like<00:32:15.120> um<00:32:16.120> so<00:32:16.679> so<00:32:17.039> the<00:32:17.200> situation 00:32:17.629 --> 00:32:17.639 align:start position:0% not like so like um so so the situation 00:32:17.639 --> 00:32:20.149 align:start position:0% not like so like um so so the situation is<00:32:17.880> this<00:32:18.120> like<00:32:18.360> we<00:32:18.559> have<00:32:19.559> established<00:32:20.039> a 00:32:20.149 --> 00:32:20.159 align:start position:0% is this like we have established a 00:32:20.159 --> 00:32:23.389 align:start position:0% is this like we have established a network<00:32:20.840> so<00:32:21.399> T<00:32:21.919> is<00:32:22.039> running<00:32:22.399> a<00:32:22.519> bunch<00:32:22.720> of<00:32:22.840> nodes 00:32:23.389 --> 00:32:23.399 align:start position:0% network so T is running a bunch of nodes 00:32:23.399 --> 00:32:25.070 align:start position:0% network so T is running a bunch of nodes cursive<00:32:23.840> are<00:32:23.960> running<00:32:24.240> a<00:32:24.320> bunch<00:32:24.519> of<00:32:24.639> nodes<00:32:24.919> and 00:32:25.070 --> 00:32:25.080 align:start position:0% cursive are running a bunch of nodes and 00:32:25.080 --> 00:32:26.990 align:start position:0% cursive are running a bunch of nodes and psse<00:32:25.480> are<00:32:25.600> running<00:32:25.840> a<00:32:25.960> bunch<00:32:26.159> of<00:32:26.240> nodes<00:32:26.880> and 00:32:26.990 --> 00:32:27.000 align:start position:0% psse are running a bunch of nodes and 00:32:27.000 --> 00:32:29.029 align:start position:0% psse are running a bunch of nodes and they<00:32:27.120> all<00:32:27.240> do<00:32:27.440> computation<00:32:28.120> they<00:32:28.200> do<00:32:28.320> a<00:32:28.399> multi 00:32:29.029 --> 00:32:29.039 align:start position:0% they all do computation they do a multi 00:32:29.039 --> 00:32:30.310 align:start position:0% they all do computation they do a multi party<00:32:29.279> computation<00:32:29.799> between<00:32:30.080> them<00:32:30.200> and 00:32:30.310 --> 00:32:30.320 align:start position:0% party computation between them and 00:32:30.320 --> 00:32:34.909 align:start position:0% party computation between them and produce<00:32:30.600> a<00:32:31.200> coar<00:32:32.200> and<00:32:33.159> so<00:32:34.159> some<00:32:34.360> of<00:32:34.519> the<00:32:34.679> things 00:32:34.909 --> 00:32:34.919 align:start position:0% produce a coar and so some of the things 00:32:34.919 --> 00:32:36.549 align:start position:0% produce a coar and so some of the things you<00:32:35.080> might<00:32:35.240> learn<00:32:35.559> when<00:32:35.679> you<00:32:35.880> go<00:32:36.000> into<00:32:36.240> prod 00:32:36.549 --> 00:32:36.559 align:start position:0% you might learn when you go into prod 00:32:36.559 --> 00:32:38.470 align:start position:0% you might learn when you go into prod that<00:32:36.679> you<00:32:36.760> wouldn't<00:32:37.000> learn<00:32:37.200> in<00:32:37.320> a<00:32:37.480> hackathon 00:32:38.470 --> 00:32:38.480 align:start position:0% that you wouldn't learn in a hackathon 00:32:38.480 --> 00:32:41.710 align:start position:0% that you wouldn't learn in a hackathon like<00:32:39.360> as<00:32:39.480> you<00:32:39.639> said<00:32:39.880> about<00:32:40.399> like<00:32:40.799> auditing<00:32:41.440> and 00:32:41.710 --> 00:32:41.720 align:start position:0% like as you said about like auditing and 00:32:41.720 --> 00:32:44.590 align:start position:0% like as you said about like auditing and security<00:32:42.679> like<00:32:43.000> being<00:32:43.320> immature<00:32:43.880> for<00:32:44.080> MPC<00:32:44.480> and 00:32:44.590 --> 00:32:44.600 align:start position:0% security like being immature for MPC and 00:32:44.600 --> 00:32:47.029 align:start position:0% security like being immature for MPC and F<00:32:44.960> and<00:32:45.039> the<00:32:45.159> more<00:32:45.320> advanced<00:32:45.720> things<00:32:46.600> yeah<00:32:46.799> like 00:32:47.029 --> 00:32:47.039 align:start position:0% F and the more advanced things yeah like 00:32:47.039 --> 00:32:48.990 align:start position:0% F and the more advanced things yeah like infrastructure<00:32:47.679> and<00:32:47.960> support<00:32:48.440> there<00:32:48.760> is 00:32:48.990 --> 00:32:49.000 align:start position:0% infrastructure and support there is 00:32:49.000 --> 00:32:52.269 align:start position:0% infrastructure and support there is super<00:32:49.919> uh<00:32:50.639> not<00:32:50.960> in<00:32:51.200> place<00:32:51.559> yet<00:32:51.880> so<00:32:52.080> like 00:32:52.269 --> 00:32:52.279 align:start position:0% super uh not in place yet so like 00:32:52.279 --> 00:32:54.470 align:start position:0% super uh not in place yet so like yesterday<00:32:52.760> we<00:32:52.919> had<00:32:53.360> um<00:32:53.559> a<00:32:53.639> bit<00:32:53.799> of<00:32:53.880> an<00:32:54.000> incident 00:32:54.470 --> 00:32:54.480 align:start position:0% yesterday we had um a bit of an incident 00:32:54.480 --> 00:32:56.870 align:start position:0% yesterday we had um a bit of an incident where<00:32:55.039> two<00:32:55.320> of<00:32:55.480> the<00:32:55.600> nodes<00:32:56.080> of<00:32:56.399> one<00:32:56.600> of<00:32:56.720> the 00:32:56.870 --> 00:32:56.880 align:start position:0% where two of the nodes of one of the 00:32:56.880 --> 00:32:59.549 align:start position:0% where two of the nodes of one of the parties<00:32:57.360> died<00:32:58.279> and<00:32:58.399> they<00:32:58.559> had<00:32:58.720> one<00:32:58.880> node<00:32:59.240> left 00:32:59.549 --> 00:32:59.559 align:start position:0% parties died and they had one node left 00:32:59.559 --> 00:33:01.470 align:start position:0% parties died and they had one node left and<00:32:59.679> so<00:32:59.840> this<00:33:00.080> there<00:33:00.240> our 00:33:01.470 --> 00:33:01.480 align:start position:0% and so this there our 00:33:01.480 --> 00:33:04.950 align:start position:0% and so this there our party<00:33:02.480> but<00:33:02.760> like<00:33:03.559> okay<00:33:04.000> there<00:33:04.159> was<00:33:04.360> some<00:33:04.519> sleep 00:33:04.950 --> 00:33:04.960 align:start position:0% party but like okay there was some sleep 00:33:04.960 --> 00:33:06.310 align:start position:0% party but like okay there was some sleep involved<00:33:05.440> because<00:33:05.639> they<00:33:05.799> stayed<00:33:06.039> up<00:33:06.159> all 00:33:06.310 --> 00:33:06.320 align:start position:0% involved because they stayed up all 00:33:06.320 --> 00:33:07.710 align:start position:0% involved because they stayed up all night<00:33:06.480> to<00:33:06.600> finish<00:33:06.880> the<00:33:07.039> thing<00:33:07.240> to<00:33:07.440> actually 00:33:07.710 --> 00:33:07.720 align:start position:0% night to finish the thing to actually 00:33:07.720 --> 00:33:09.629 align:start position:0% night to finish the thing to actually get<00:33:07.840> it<00:33:07.960> done<00:33:08.120> for<00:33:08.320> Devcon<00:33:08.840> so<00:33:09.080> it's<00:33:09.279> a<00:33:09.440> it's<00:33:09.519> a 00:33:09.629 --> 00:33:09.639 align:start position:0% get it done for Devcon so it's a it's a 00:33:09.639 --> 00:33:11.909 align:start position:0% get it done for Devcon so it's a it's a good<00:33:09.840> reason<00:33:10.639> but<00:33:10.880> uh<00:33:11.080> yeah<00:33:11.279> like<00:33:11.559> one<00:33:11.799> like 00:33:11.909 --> 00:33:11.919 align:start position:0% good reason but uh yeah like one like 00:33:11.919 --> 00:33:13.389 align:start position:0% good reason but uh yeah like one like just<00:33:12.039> the<00:33:12.159> nodes<00:33:12.519> died<00:33:12.760> and<00:33:12.919> they<00:33:13.039> just<00:33:13.159> needed 00:33:13.389 --> 00:33:13.399 align:start position:0% just the nodes died and they just needed 00:33:13.399 --> 00:33:16.070 align:start position:0% just the nodes died and they just needed to<00:33:13.519> be<00:33:13.600> rebooted<00:33:14.440> and<00:33:14.880> um<00:33:15.279> that's<00:33:15.480> it<00:33:15.919> but 00:33:16.070 --> 00:33:16.080 align:start position:0% to be rebooted and um that's it but 00:33:16.080 --> 00:33:19.110 align:start position:0% to be rebooted and um that's it but there<00:33:16.200> was<00:33:16.399> no<00:33:16.840> like<00:33:17.559> alarm<00:33:18.039> or<00:33:18.240> notifications 00:33:19.110 --> 00:33:19.120 align:start position:0% there was no like alarm or notifications 00:33:19.120 --> 00:33:20.909 align:start position:0% there was no like alarm or notifications or<00:33:19.360> like<00:33:19.519> anything<00:33:19.880> set<00:33:20.120> up<00:33:20.399> you<00:33:20.519> know<00:33:20.760> this 00:33:20.909 --> 00:33:20.919 align:start position:0% or like anything set up you know this 00:33:20.919 --> 00:33:23.269 align:start position:0% or like anything set up you know this kind<00:33:21.039> of<00:33:21.600> like<00:33:22.240> support<00:33:22.679> that<00:33:22.840> just<00:33:23.000> keeps 00:33:23.269 --> 00:33:23.279 align:start position:0% kind of like support that just keeps 00:33:23.279 --> 00:33:25.710 align:start position:0% kind of like support that just keeps things<00:33:23.480> online<00:33:24.000> or<00:33:24.279> like<00:33:24.840> small<00:33:25.279> stupid 00:33:25.710 --> 00:33:25.720 align:start position:0% things online or like small stupid 00:33:25.720 --> 00:33:27.830 align:start position:0% things online or like small stupid things<00:33:26.000> that<00:33:26.120> are<00:33:26.320> like<00:33:26.519> the<00:33:26.799> absolute<00:33:27.440> like 00:33:27.830 --> 00:33:27.840 align:start position:0% things that are like the absolute like 00:33:27.840 --> 00:33:30.149 align:start position:0% things that are like the absolute like complete<00:33:28.399> like<00:33:28.639> essential<00:33:29.279> things<00:33:29.559> in<00:33:29.799> any 00:33:30.149 --> 00:33:30.159 align:start position:0% complete like essential things in any 00:33:30.159 --> 00:33:32.430 align:start position:0% complete like essential things in any sort<00:33:30.360> of<00:33:30.919> advanced<00:33:31.480> Tech<00:33:31.720> not<00:33:31.840> even<00:33:32.039> Advanced 00:33:32.430 --> 00:33:32.440 align:start position:0% sort of advanced Tech not even Advanced 00:33:32.440 --> 00:33:34.509 align:start position:0% sort of advanced Tech not even Advanced but<00:33:32.600> like<00:33:32.840> used<00:33:33.320> Tech<00:33:33.720> like<00:33:33.919> the<00:33:34.120> the<00:33:34.240> most 00:33:34.509 --> 00:33:34.519 align:start position:0% but like used Tech like the the most 00:33:34.519 --> 00:33:36.590 align:start position:0% but like used Tech like the the most basic<00:33:34.840> things<00:33:35.000> are<00:33:35.159> not<00:33:35.399> there<00:33:36.000> and<00:33:36.120> we<00:33:36.279> focus 00:33:36.590 --> 00:33:36.600 align:start position:0% basic things are not there and we focus 00:33:36.600 --> 00:33:38.310 align:start position:0% basic things are not there and we focus on<00:33:36.760> just<00:33:36.919> getting<00:33:37.200> things<00:33:37.440> working<00:33:37.919> but<00:33:38.120> like 00:33:38.310 --> 00:33:38.320 align:start position:0% on just getting things working but like 00:33:38.320 --> 00:33:39.950 align:start position:0% on just getting things working but like yeah<00:33:38.480> this<00:33:38.600> sort<00:33:38.799> of<00:33:39.080> support<00:33:39.480> to<00:33:39.639> keep<00:33:39.799> it 00:33:39.950 --> 00:33:39.960 align:start position:0% yeah this sort of support to keep it 00:33:39.960 --> 00:33:43.110 align:start position:0% yeah this sort of support to keep it going<00:33:40.919> it's<00:33:41.159> just<00:33:41.320> not<00:33:41.600> there<00:33:42.039> but<00:33:42.519> um<00:33:42.880> and<00:33:43.000> in 00:33:43.110 --> 00:33:43.120 align:start position:0% going it's just not there but um and in 00:33:43.120 --> 00:33:45.909 align:start position:0% going it's just not there but um and in terms<00:33:43.360> of<00:33:44.039> cost<00:33:45.039> I<00:33:45.159> also<00:33:45.360> don't<00:33:45.519> know<00:33:45.679> if<00:33:45.840> I 00:33:45.909 --> 00:33:45.919 align:start position:0% terms of cost I also don't know if I 00:33:45.919 --> 00:33:47.950 align:start position:0% terms of cost I also don't know if I should<00:33:46.320> talk<00:33:46.519> about<00:33:46.799> this<00:33:47.000> without<00:33:47.279> knowing 00:33:47.950 --> 00:33:47.960 align:start position:0% should talk about this without knowing 00:33:47.960 --> 00:33:50.350 align:start position:0% should talk about this without knowing exactly<00:33:48.519> but<00:33:48.720> like<00:33:49.320> I<00:33:49.399> think<00:33:49.559> for<00:33:49.760> us<00:33:49.960> setting 00:33:50.350 --> 00:33:50.360 align:start position:0% exactly but like I think for us setting 00:33:50.360 --> 00:33:53.350 align:start position:0% exactly but like I think for us setting this<00:33:50.880> up<00:33:51.880> I<00:33:52.000> think<00:33:52.240> is<00:33:52.320> it<00:33:52.440> for<00:33:52.639> each<00:33:52.880> party<00:33:53.279> I 00:33:53.350 --> 00:33:53.360 align:start position:0% this up I think is it for each party I 00:33:53.360 --> 00:33:56.830 align:start position:0% this up I think is it for each party I think<00:33:53.519> it's<00:33:53.679> about<00:33:53.919> $7<00:33:54.919> per<00:33:55.200> day<00:33:55.559> for<00:33:55.880> like 00:33:56.830 --> 00:33:56.840 align:start position:0% think it's about $7 per day for like 00:33:56.840 --> 00:34:06.509 align:start position:0% think it's about $7 per day for like seriously<00:33:57.480> be<00:33:57.840> Fe<00:33:58.360> machines<00:33:59.679> so<00:34:00.679> yeah<00:34:00.960> not<00:34:01.159> too 00:34:06.509 --> 00:34:06.519 align:start position:0% 00:34:06.519 --> 00:34:09.069 align:start position:0% bad<00:34:07.519> yeah<00:34:07.799> I<00:34:07.880> don't<00:34:08.119> I<00:34:08.200> don't<00:34:08.359> have<00:34:08.520> much<00:34:08.839> on 00:34:09.069 --> 00:34:09.079 align:start position:0% bad yeah I don't I don't have much on 00:34:09.079 --> 00:34:12.669 align:start position:0% bad yeah I don't I don't have much on numbers<00:34:09.440> that<00:34:09.599> I<00:34:09.720> know<00:34:10.200> of<00:34:10.879> uh<00:34:11.040> concretely<00:34:11.760> but 00:34:12.669 --> 00:34:12.679 align:start position:0% numbers that I know of uh concretely but 00:34:12.679 --> 00:34:15.470 align:start position:0% numbers that I know of uh concretely but I<00:34:12.800> think<00:34:13.480> in<00:34:13.760> terms<00:34:14.200> of<00:34:14.440> like<00:34:14.639> what<00:34:14.760> you<00:34:14.960> said 00:34:15.470 --> 00:34:15.480 align:start position:0% I think in terms of like what you said 00:34:15.480 --> 00:34:17.589 align:start position:0% I think in terms of like what you said like<00:34:15.919> this<00:34:16.079> is<00:34:16.399> not<00:34:16.720> something<00:34:17.200> that<00:34:17.320> we<00:34:17.440> would 00:34:17.589 --> 00:34:17.599 align:start position:0% like this is not something that we would 00:34:17.599 --> 00:34:19.430 align:start position:0% like this is not something that we would have<00:34:17.760> learned<00:34:18.200> this<00:34:18.399> quickly<00:34:18.960> if<00:34:19.079> we<00:34:19.200> didn't 00:34:19.430 --> 00:34:19.440 align:start position:0% have learned this quickly if we didn't 00:34:19.440 --> 00:34:22.310 align:start position:0% have learned this quickly if we didn't deploy<00:34:19.800> it<00:34:20.200> right<00:34:20.399> like<00:34:21.119> this<00:34:21.919> uh<00:34:22.079> we<00:34:22.159> were 00:34:22.310 --> 00:34:22.320 align:start position:0% deploy it right like this uh we were 00:34:22.320 --> 00:34:24.510 align:start position:0% deploy it right like this uh we were using<00:34:22.599> coars<00:34:23.159> for<00:34:23.440> like<00:34:23.560> the<00:34:23.639> leaderboard<00:34:24.359> for 00:34:24.510 --> 00:34:24.520 align:start position:0% using coars for like the leaderboard for 00:34:24.520 --> 00:34:26.069 align:start position:0% using coars for like the leaderboard for like<00:34:24.639> handing<00:34:24.879> out<00:34:25.040> merch<00:34:25.359> downstairs<00:34:25.960> like 00:34:26.069 --> 00:34:26.079 align:start position:0% like handing out merch downstairs like 00:34:26.079 --> 00:34:27.950 align:start position:0% like handing out merch downstairs like if<00:34:26.159> you<00:34:26.280> tap<00:34:26.560> like<00:34:26.679> 40<00:34:27.000> people<00:34:27.280> you<00:34:27.399> generate<00:34:27.839> a 00:34:27.950 --> 00:34:27.960 align:start position:0% if you tap like 40 people you generate a 00:34:27.960 --> 00:34:30.109 align:start position:0% if you tap like 40 people you generate a proof<00:34:28.159> of<00:34:28.280> it<00:34:28.639> and<00:34:28.800> like<00:34:28.960> you<00:34:29.040> can<00:34:29.200> get<00:34:29.320> a<00:34:29.440> shirt 00:34:30.109 --> 00:34:30.119 align:start position:0% proof of it and like you can get a shirt 00:34:30.119 --> 00:34:31.550 align:start position:0% proof of it and like you can get a shirt um<00:34:30.280> the<00:34:30.399> shirt<00:34:30.720> that<00:34:30.839> I'm<00:34:30.960> wearing<00:34:31.280> which<00:34:31.359> is 00:34:31.550 --> 00:34:31.560 align:start position:0% um the shirt that I'm wearing which is 00:34:31.560 --> 00:34:35.470 align:start position:0% um the shirt that I'm wearing which is super<00:34:31.879> sick<00:34:32.800> um<00:34:33.480> but<00:34:34.040> like<00:34:34.440> we<00:34:34.639> learned<00:34:35.280> of 00:34:35.470 --> 00:34:35.480 align:start position:0% super sick um but like we learned of 00:34:35.480 --> 00:34:37.510 align:start position:0% super sick um but like we learned of this<00:34:35.720> incident<00:34:36.240> like<00:34:36.440> literally<00:34:36.879> 30<00:34:37.200> seconds 00:34:37.510 --> 00:34:37.520 align:start position:0% this incident like literally 30 seconds 00:34:37.520 --> 00:34:39.389 align:start position:0% this incident like literally 30 seconds in<00:34:37.960> because<00:34:38.240> people's<00:34:38.560> leaderboards<00:34:39.280> like 00:34:39.389 --> 00:34:39.399 align:start position:0% in because people's leaderboards like 00:34:39.399 --> 00:34:40.909 align:start position:0% in because people's leaderboards like weren't<00:34:39.720> updating<00:34:40.320> and<00:34:40.440> they<00:34:40.560> couldn't<00:34:40.760> get 00:34:40.909 --> 00:34:40.919 align:start position:0% weren't updating and they couldn't get 00:34:40.919 --> 00:34:42.950 align:start position:0% weren't updating and they couldn't get their<00:34:41.000> shirts<00:34:42.000> and<00:34:42.119> like<00:34:42.240> they<00:34:42.320> were<00:34:42.480> so<00:34:42.679> mad 00:34:42.950 --> 00:34:42.960 align:start position:0% their shirts and like they were so mad 00:34:42.960 --> 00:34:44.349 align:start position:0% their shirts and like they were so mad they<00:34:43.040> were<00:34:43.200> like<00:34:43.359> oh<00:34:43.520> where's<00:34:43.760> my<00:34:43.879> shirt<00:34:44.240> I 00:34:44.349 --> 00:34:44.359 align:start position:0% they were like oh where's my shirt I 00:34:44.359 --> 00:34:45.829 align:start position:0% they were like oh where's my shirt I want<00:34:44.599> my<00:34:44.720> shirt<00:34:45.000> like<00:34:45.119> my<00:34:45.200> leaderboard<00:34:45.639> isn't 00:34:45.829 --> 00:34:45.839 align:start position:0% want my shirt like my leaderboard isn't 00:34:45.839 --> 00:34:47.669 align:start position:0% want my shirt like my leaderboard isn't updating<00:34:46.480> so<00:34:46.599> I<00:34:46.679> feel<00:34:46.839> like<00:34:47.240> having<00:34:47.520> that 00:34:47.669 --> 00:34:47.679 align:start position:0% updating so I feel like having that 00:34:47.679 --> 00:34:49.550 align:start position:0% updating so I feel like having that feedback<00:34:48.079> loop<00:34:48.440> instantaneously<00:34:49.240> is<00:34:49.359> like 00:34:49.550 --> 00:34:49.560 align:start position:0% feedback loop instantaneously is like 00:34:49.560 --> 00:34:51.069 align:start position:0% feedback loop instantaneously is like super<00:34:49.800> useful<00:34:50.200> and<00:34:50.320> we<00:34:50.440> like<00:34:50.560> we<00:34:50.639> learned<00:34:50.919> this 00:34:51.069 --> 00:34:51.079 align:start position:0% super useful and we like we learned this 00:34:51.079 --> 00:34:52.829 align:start position:0% super useful and we like we learned this lesson<00:34:51.399> and<00:34:51.560> like<00:34:51.720> we<00:34:51.839> fix<00:34:52.040> it<00:34:52.159> overnight<00:34:52.639> and 00:34:52.829 --> 00:34:52.839 align:start position:0% lesson and like we fix it overnight and 00:34:52.839 --> 00:34:55.389 align:start position:0% lesson and like we fix it overnight and like<00:34:53.200> now<00:34:53.320> we<00:34:53.440> learned<00:34:53.720> something<00:34:54.119> new<00:34:55.119> maybe 00:34:55.389 --> 00:34:55.399 align:start position:0% like now we learned something new maybe 00:34:55.399 --> 00:34:57.310 align:start position:0% like now we learned something new maybe I<00:34:55.480> can<00:34:55.639> add<00:34:55.879> one<00:34:56.119> good<00:34:56.320> point<00:34:56.720> and<00:34:56.839> then<00:34:57.040> I'll 00:34:57.310 --> 00:34:57.320 align:start position:0% I can add one good point and then I'll 00:34:57.320 --> 00:34:59.910 align:start position:0% I can add one good point and then I'll be<00:34:57.440> Qui<00:34:57.960> but<00:34:58.320> uh<00:34:58.880> like<00:34:59.240> the<00:34:59.359> good<00:34:59.520> point<00:34:59.760> is 00:34:59.910 --> 00:34:59.920 align:start position:0% be Qui but uh like the good point is 00:34:59.920 --> 00:35:03.270 align:start position:0% be Qui but uh like the good point is that<00:35:00.160> we<00:35:00.320> had<00:35:00.599> many<00:35:01.280> more<00:35:02.280> we<00:35:02.480> generated<00:35:03.000> many 00:35:03.270 --> 00:35:03.280 align:start position:0% that we had many more we generated many 00:35:03.280 --> 00:35:05.390 align:start position:0% that we had many more we generated many many<00:35:03.480> more<00:35:03.720> coars<00:35:04.280> than<00:35:04.440> we<00:35:04.599> expected<00:35:05.079> so<00:35:05.280> like 00:35:05.390 --> 00:35:05.400 align:start position:0% many more coars than we expected so like 00:35:05.400 --> 00:35:07.030 align:start position:0% many more coars than we expected so like the<00:35:05.520> load<00:35:05.880> was<00:35:06.079> much<00:35:06.280> much<00:35:06.480> higher<00:35:06.760> than<00:35:06.880> we 00:35:07.030 --> 00:35:07.040 align:start position:0% the load was much much higher than we 00:35:07.040 --> 00:35:09.510 align:start position:0% the load was much much higher than we expected<00:35:07.839> and<00:35:07.920> the<00:35:08.079> reason<00:35:08.320> it<00:35:08.440> went<00:35:08.680> down<00:35:08.960> was 00:35:09.510 --> 00:35:09.520 align:start position:0% expected and the reason it went down was 00:35:09.520 --> 00:35:11.390 align:start position:0% expected and the reason it went down was like<00:35:10.160> yeah 00:35:11.390 --> 00:35:11.400 align:start position:0% like yeah 00:35:11.400 --> 00:35:14.030 align:start position:0% like yeah like<00:35:12.400> it<00:35:12.520> was<00:35:12.680> not<00:35:12.960> because<00:35:13.160> of<00:35:13.359> let's<00:35:13.520> say<00:35:13.839> so 00:35:14.030 --> 00:35:14.040 align:start position:0% like it was not because of let's say so 00:35:14.040 --> 00:35:17.470 align:start position:0% like it was not because of let's say so much<00:35:14.280> load<00:35:15.280> um<00:35:15.640> but<00:35:15.880> like<00:35:16.359> we<00:35:16.520> are<00:35:16.920> handling 00:35:17.470 --> 00:35:17.480 align:start position:0% much load um but like we are handling 00:35:17.480 --> 00:35:19.270 align:start position:0% much load um but like we are handling much<00:35:17.640> more<00:35:17.920> throughput<00:35:18.440> than<00:35:18.560> we<00:35:18.760> expected<00:35:19.160> we 00:35:19.270 --> 00:35:19.280 align:start position:0% much more throughput than we expected we 00:35:19.280 --> 00:35:20.990 align:start position:0% much more throughput than we expected we could<00:35:19.480> in<00:35:19.680> like<00:35:19.920> pretty<00:35:20.160> good<00:35:20.400> times<00:35:20.760> so 00:35:20.990 --> 00:35:21.000 align:start position:0% could in like pretty good times so 00:35:21.000 --> 00:35:22.390 align:start position:0% could in like pretty good times so that's<00:35:21.200> the<00:35:21.320> good<00:35:21.480> outcome<00:35:21.920> that<00:35:22.040> we<00:35:22.160> wouldn't 00:35:22.390 --> 00:35:22.400 align:start position:0% that's the good outcome that we wouldn't 00:35:22.400 --> 00:35:23.910 align:start position:0% that's the good outcome that we wouldn't have<00:35:22.560> also<00:35:22.839> expected<00:35:23.240> without<00:35:23.480> going<00:35:23.680> into 00:35:23.910 --> 00:35:23.920 align:start position:0% have also expected without going into 00:35:23.920 --> 00:35:26.750 align:start position:0% have also expected without going into prod<00:35:24.520> and<00:35:24.720> like<00:35:25.000> a<00:35:25.119> lot<00:35:25.240> of<00:35:25.359> it<00:35:25.520> is<00:35:25.760> because<00:35:26.079> of 00:35:26.750 --> 00:35:26.760 align:start position:0% prod and like a lot of it is because of 00:35:26.760 --> 00:35:29.109 align:start position:0% prod and like a lot of it is because of the<00:35:27.040> response<00:35:27.839> of<00:35:28.079> people<00:35:28.359> at<00:35:28.480> the<00:35:28.640> conference 00:35:29.109 --> 00:35:29.119 align:start position:0% the response of people at the conference 00:35:29.119 --> 00:35:30.829 align:start position:0% the response of people at the conference actually<00:35:29.440> like<00:35:29.599> people<00:35:29.800> are<00:35:29.960> super<00:35:30.320> curious 00:35:30.829 --> 00:35:30.839 align:start position:0% actually like people are super curious 00:35:30.839 --> 00:35:33.589 align:start position:0% actually like people are super curious and<00:35:31.839> cool<00:35:32.160> to<00:35:32.320> try<00:35:32.520> it<00:35:32.640> out<00:35:32.920> so<00:35:33.400> that's 00:35:33.589 --> 00:35:33.599 align:start position:0% and cool to try it out so that's 00:35:33.599 --> 00:35:34.829 align:start position:0% and cool to try it out so that's something<00:35:33.880> we<00:35:34.000> wouldn't 00:35:34.829 --> 00:35:34.839 align:start position:0% something we wouldn't 00:35:34.839 --> 00:35:37.589 align:start position:0% something we wouldn't learn<00:35:35.839> yeah<00:35:36.040> that's<00:35:36.200> a<00:35:36.440> good<00:35:36.760> problem<00:35:37.240> like 00:35:37.589 --> 00:35:37.599 align:start position:0% learn yeah that's a good problem like 00:35:37.599 --> 00:35:39.950 align:start position:0% learn yeah that's a good problem like higher<00:35:37.960> than<00:35:38.280> expected<00:35:38.760> through<00:35:39.119> pit<00:35:39.760> and 00:35:39.950 --> 00:35:39.960 align:start position:0% higher than expected through pit and 00:35:39.960 --> 00:35:42.390 align:start position:0% higher than expected through pit and that's<00:35:40.119> a<00:35:40.359> good<00:35:40.760> like<00:35:41.040> alert<00:35:41.480> system<00:35:41.960> angry 00:35:42.390 --> 00:35:42.400 align:start position:0% that's a good like alert system angry 00:35:42.400 --> 00:35:44.069 align:start position:0% that's a good like alert system angry users<00:35:42.920> demanding 00:35:44.069 --> 00:35:44.079 align:start position:0% users demanding 00:35:44.079 --> 00:35:46.990 align:start position:0% users demanding shirts<00:35:45.079> those<00:35:45.280> are<00:35:45.599> like<00:35:46.280> the<00:35:46.480> joys<00:35:46.800> of 00:35:46.990 --> 00:35:47.000 align:start position:0% shirts those are like the joys of 00:35:47.000 --> 00:35:49.230 align:start position:0% shirts those are like the joys of deploying<00:35:47.520> in<00:35:47.680> the<00:35:47.880> wild<00:35:48.119> and<00:35:48.320> having<00:35:48.599> real 00:35:49.230 --> 00:35:49.240 align:start position:0% deploying in the wild and having real 00:35:49.240 --> 00:35:53.069 align:start position:0% deploying in the wild and having real users<00:35:50.240> um<00:35:50.560> so<00:35:50.960> I<00:35:51.160> do<00:35:51.680> think<00:35:52.240> I'm<00:35:52.480> supposed<00:35:52.839> to 00:35:53.069 --> 00:35:53.079 align:start position:0% users um so I do think I'm supposed to 00:35:53.079 --> 00:35:56.150 align:start position:0% users um so I do think I'm supposed to open<00:35:53.440> to<00:35:53.760> questions<00:35:54.280> from<00:35:54.480> the<00:35:55.000> audience<00:35:56.000> but 00:35:56.150 --> 00:35:56.160 align:start position:0% open to questions from the audience but 00:35:56.160 --> 00:35:59.510 align:start position:0% open to questions from the audience but I<00:35:56.240> don't<00:35:56.480> see<00:35:56.839> any<00:35:57.160> questions<00:35:57.839> do<00:35:58.359> you<00:35:59.359> you 00:35:59.510 --> 00:35:59.520 align:start position:0% I don't see any questions do you you 00:35:59.520 --> 00:36:02.829 align:start position:0% I don't see any questions do you you don't<00:36:00.079> I<00:36:00.200> think<00:36:00.480> questions<00:36:00.960> after<00:36:01.400> that<00:36:01.839> time 00:36:02.829 --> 00:36:02.839 align:start position:0% don't I think questions after that time 00:36:02.839 --> 00:36:05.349 align:start position:0% don't I think questions after that time oh<00:36:03.319> okay<00:36:03.599> so<00:36:03.839> we<00:36:04.040> have<00:36:04.280> 9<00:36:04.560> minutes<00:36:04.960> left<00:36:05.240> and 00:36:05.349 --> 00:36:05.359 align:start position:0% oh okay so we have 9 minutes left and 00:36:05.359 --> 00:36:06.750 align:start position:0% oh okay so we have 9 minutes left and then<00:36:05.480> we'll<00:36:05.680> open<00:36:05.960> into<00:36:06.119> questions<00:36:06.480> great 00:36:06.750 --> 00:36:06.760 align:start position:0% then we'll open into questions great 00:36:06.760 --> 00:36:10.309 align:start position:0% then we'll open into questions great because<00:36:07.040> I'm<00:36:07.319> really<00:36:07.599> not<00:36:07.839> done<00:36:08.240> here<00:36:09.160> um<00:36:10.079> yeah 00:36:10.309 --> 00:36:10.319 align:start position:0% because I'm really not done here um yeah 00:36:10.319 --> 00:36:11.950 align:start position:0% because I'm really not done here um yeah I<00:36:10.440> think<00:36:10.640> the<00:36:10.839> second<00:36:11.160> part<00:36:11.319> of<00:36:11.440> my<00:36:11.640> question 00:36:11.950 --> 00:36:11.960 align:start position:0% I think the second part of my question 00:36:11.960 --> 00:36:14.870 align:start position:0% I think the second part of my question was<00:36:12.720> like<00:36:13.000> what<00:36:13.119> do<00:36:13.240> you<00:36:13.359> see<00:36:13.960> in<00:36:14.119> the<00:36:14.319> future 00:36:14.870 --> 00:36:14.880 align:start position:0% was like what do you see in the future 00:36:14.880 --> 00:36:16.550 align:start position:0% was like what do you see in the future like<00:36:15.280> future<00:36:15.680> improvements<00:36:16.280> that<00:36:16.359> you're 00:36:16.550 --> 00:36:16.560 align:start position:0% like future improvements that you're 00:36:16.560 --> 00:36:20.030 align:start position:0% like future improvements that you're looking<00:36:16.839> forward<00:36:17.200> to<00:36:17.960> I<00:36:18.359> in<00:36:18.880> particular<00:36:19.880> um 00:36:20.030 --> 00:36:20.040 align:start position:0% looking forward to I in particular um 00:36:20.040 --> 00:36:22.990 align:start position:0% looking forward to I in particular um want<00:36:20.240> to<00:36:20.440> ask<00:36:20.760> about<00:36:21.160> mobile<00:36:21.720> interfaces<00:36:22.680> and 00:36:22.990 --> 00:36:23.000 align:start position:0% want to ask about mobile interfaces and 00:36:23.000 --> 00:36:25.470 align:start position:0% want to ask about mobile interfaces and whether<00:36:23.800> yeah<00:36:24.040> that's<00:36:24.200> a<00:36:24.400> priority<00:36:25.040> for<00:36:25.280> you 00:36:25.470 --> 00:36:25.480 align:start position:0% whether yeah that's a priority for you 00:36:25.480 --> 00:36:29.150 align:start position:0% whether yeah that's a priority for you guys<00:36:26.200> what<00:36:26.440> challenges<00:36:27.280> uh<00:36:27.880> do<00:36:28.040> you<00:36:28.160> see<00:36:28.520> like 00:36:29.150 --> 00:36:29.160 align:start position:0% guys what challenges uh do you see like 00:36:29.160 --> 00:36:31.390 align:start position:0% guys what challenges uh do you see like sort<00:36:29.400> of<00:36:29.640> what<00:36:29.880> blockers<00:36:30.680> do<00:36:30.760> you<00:36:30.960> have<00:36:31.240> right 00:36:31.390 --> 00:36:31.400 align:start position:0% sort of what blockers do you have right 00:36:31.400 --> 00:36:33.790 align:start position:0% sort of what blockers do you have right now<00:36:32.160> um<00:36:32.480> and<00:36:32.680> what<00:36:32.800> challenges<00:36:33.280> do<00:36:33.359> you<00:36:33.480> see<00:36:33.640> in 00:36:33.790 --> 00:36:33.800 align:start position:0% now um and what challenges do you see in 00:36:33.800 --> 00:36:36.589 align:start position:0% now um and what challenges do you see in future<00:36:34.160> or<00:36:34.440> what<00:36:34.560> needs<00:36:34.800> to<00:36:35.040> happen<00:36:35.359> to<00:36:35.680> make 00:36:36.589 --> 00:36:36.599 align:start position:0% future or what needs to happen to make 00:36:36.599 --> 00:36:39.349 align:start position:0% future or what needs to happen to make um<00:36:37.079> like<00:36:37.400> a<00:36:37.599> joyful<00:36:38.079> mobile<00:36:38.599> experience<00:36:39.160> for 00:36:39.349 --> 00:36:39.359 align:start position:0% um like a joyful mobile experience for 00:36:39.359 --> 00:36:41.910 align:start position:0% um like a joyful mobile experience for the 00:36:41.910 --> 00:36:41.920 align:start position:0% 00:36:41.920 --> 00:36:44.309 align:start position:0% users<00:36:42.920> uh<00:36:43.079> maybe<00:36:43.319> one<00:36:43.640> thing<00:36:43.880> we've<00:36:44.079> thought 00:36:44.309 --> 00:36:44.319 align:start position:0% users uh maybe one thing we've thought 00:36:44.319 --> 00:36:45.990 align:start position:0% users uh maybe one thing we've thought about<00:36:44.880> on<00:36:45.040> the<00:36:45.160> infrastructure<00:36:45.640> side<00:36:45.800> and<00:36:45.880> on 00:36:45.990 --> 00:36:46.000 align:start position:0% about on the infrastructure side and on 00:36:46.000 --> 00:36:49.430 align:start position:0% about on the infrastructure side and on the<00:36:46.079> mobile<00:36:46.440> side<00:36:47.240> is<00:36:47.839> um<00:36:48.040> because<00:36:48.440> proofs 00:36:49.430 --> 00:36:49.440 align:start position:0% the mobile side is um because proofs 00:36:49.440 --> 00:36:51.349 align:start position:0% the mobile side is um because proofs cost<00:36:49.640> a<00:36:49.800> couple<00:36:50.040> cents<00:36:50.280> on<00:36:50.400> a<00:36:50.520> server<00:36:50.960> and<00:36:51.200> will 00:36:51.349 --> 00:36:51.359 align:start position:0% cost a couple cents on a server and will 00:36:51.359 --> 00:36:54.069 align:start position:0% cost a couple cents on a server and will cost<00:36:51.560> a<00:36:51.680> couple<00:36:51.880> more<00:36:52.000> sents<00:36:52.280> if<00:36:52.400> you<00:36:52.520> do<00:36:53.079> coars 00:36:54.069 --> 00:36:54.079 align:start position:0% cost a couple more sents if you do coars 00:36:54.079 --> 00:36:57.270 align:start position:0% cost a couple more sents if you do coars um<00:36:54.520> there<00:36:54.760> is<00:36:55.560> quite<00:36:55.720> a<00:36:55.960> pressure<00:36:56.640> to<00:36:57.040> push 00:36:57.270 --> 00:36:57.280 align:start position:0% um there is quite a pressure to push 00:36:57.280 --> 00:36:58.710 align:start position:0% um there is quite a pressure to push things<00:36:57.640> to<00:36:57.800> the<00:36:57.880> client<00:36:58.240> side<00:36:58.480> because<00:36:58.640> then 00:36:58.710 --> 00:36:58.720 align:start position:0% things to the client side because then 00:36:58.720 --> 00:37:00.390 align:start position:0% things to the client side because then it's<00:36:58.880> free<00:36:59.200> the<00:36:59.280> user<00:36:59.520> handles<00:36:59.800> a<00:36:59.920> computation 00:37:00.390 --> 00:37:00.400 align:start position:0% it's free the user handles a computation 00:37:00.400 --> 00:37:02.829 align:start position:0% it's free the user handles a computation for<00:37:00.599> you<00:37:01.359> and<00:37:01.520> so<00:37:01.920> one<00:37:02.119> interesting<00:37:02.480> thing<00:37:02.680> is 00:37:02.829 --> 00:37:02.839 align:start position:0% for you and so one interesting thing is 00:37:02.839 --> 00:37:05.190 align:start position:0% for you and so one interesting thing is that<00:37:03.119> if<00:37:03.440> ZK<00:37:03.880> proofs<00:37:04.319> get<00:37:04.520> really<00:37:04.760> big<00:37:04.960> and<00:37:05.079> if 00:37:05.190 --> 00:37:05.200 align:start position:0% that if ZK proofs get really big and if 00:37:05.200 --> 00:37:07.030 align:start position:0% that if ZK proofs get really big and if people<00:37:05.400> are<00:37:05.599> doing<00:37:06.319> you<00:37:06.440> know<00:37:06.760> not<00:37:06.880> just 00:37:07.030 --> 00:37:07.040 align:start position:0% people are doing you know not just 00:37:07.040 --> 00:37:08.550 align:start position:0% people are doing you know not just hundreds<00:37:07.280> of<00:37:07.400> proofs<00:37:07.599> a<00:37:07.720> day<00:37:07.839> but<00:37:08.040> thousands 00:37:08.550 --> 00:37:08.560 align:start position:0% hundreds of proofs a day but thousands 00:37:08.560 --> 00:37:10.790 align:start position:0% hundreds of proofs a day but thousands or<00:37:08.839> hundreds<00:37:09.160> of<00:37:09.280> thousands<00:37:09.520> of<00:37:09.599> proofs<00:37:09.839> a<00:37:10.000> day 00:37:10.790 --> 00:37:10.800 align:start position:0% or hundreds of thousands of proofs a day 00:37:10.800 --> 00:37:12.829 align:start position:0% or hundreds of thousands of proofs a day then<00:37:11.040> there's<00:37:11.240> a<00:37:11.480> really<00:37:11.800> big<00:37:12.040> pressure 00:37:12.829 --> 00:37:12.839 align:start position:0% then there's a really big pressure 00:37:12.839 --> 00:37:14.790 align:start position:0% then there's a really big pressure economically<00:37:13.680> to<00:37:13.880> create<00:37:14.280> client<00:37:14.640> side 00:37:14.790 --> 00:37:14.800 align:start position:0% economically to create client side 00:37:14.800 --> 00:37:16.390 align:start position:0% economically to create client side proving<00:37:15.640> I<00:37:15.720> think<00:37:15.839> that's<00:37:16.000> quite<00:37:16.160> cool 00:37:16.390 --> 00:37:16.400 align:start position:0% proving I think that's quite cool 00:37:16.400 --> 00:37:17.750 align:start position:0% proving I think that's quite cool because<00:37:16.599> client<00:37:16.920> side<00:37:17.000> proving<00:37:17.359> is<00:37:17.520> kind<00:37:17.640> of 00:37:17.750 --> 00:37:17.760 align:start position:0% because client side proving is kind of 00:37:17.760 --> 00:37:19.950 align:start position:0% because client side proving is kind of the<00:37:17.880> Holy<00:37:18.160> Grail<00:37:18.480> of<00:37:18.640> where<00:37:19.079> ZK<00:37:19.480> privacy<00:37:19.800> comes 00:37:19.950 --> 00:37:19.960 align:start position:0% the Holy Grail of where ZK privacy comes 00:37:19.960 --> 00:37:21.630 align:start position:0% the Holy Grail of where ZK privacy comes in<00:37:20.119> you<00:37:20.280> don't<00:37:20.800> actually<00:37:21.000> leave<00:37:21.240> privacy<00:37:21.520> to 00:37:21.630 --> 00:37:21.640 align:start position:0% in you don't actually leave privacy to 00:37:21.640 --> 00:37:23.990 align:start position:0% in you don't actually leave privacy to anybody<00:37:21.960> else<00:37:22.240> and<00:37:22.359> so<00:37:22.880> I<00:37:23.000> think<00:37:23.200> that's<00:37:23.800> it's 00:37:23.990 --> 00:37:24.000 align:start position:0% anybody else and so I think that's it's 00:37:24.000 --> 00:37:25.309 align:start position:0% anybody else and so I think that's it's actually<00:37:24.240> potentially<00:37:24.599> a<00:37:24.760> good<00:37:24.920> thing<00:37:25.160> that 00:37:25.309 --> 00:37:25.319 align:start position:0% actually potentially a good thing that 00:37:25.319 --> 00:37:27.589 align:start position:0% actually potentially a good thing that it<00:37:25.880> that<00:37:26.200> uh<00:37:26.560> we<00:37:26.640> can<00:37:26.800> incentivize<00:37:27.280> this 00:37:27.589 --> 00:37:27.599 align:start position:0% it that uh we can incentivize this 00:37:27.599 --> 00:37:30.309 align:start position:0% it that uh we can incentivize this research<00:37:28.400> um<00:37:29.280> and<00:37:29.400> so<00:37:29.560> far<00:37:29.720> there's<00:37:29.880> only<00:37:30.160> like 00:37:30.309 --> 00:37:30.319 align:start position:0% research um and so far there's only like 00:37:30.319 --> 00:37:31.390 align:start position:0% research um and so far there's only like you<00:37:30.400> know<00:37:30.640> maybe<00:37:30.920> two<00:37:31.079> or<00:37:31.240> three 00:37:31.390 --> 00:37:31.400 align:start position:0% you know maybe two or three 00:37:31.400 --> 00:37:33.230 align:start position:0% you know maybe two or three organizations<00:37:31.920> I<00:37:32.000> can<00:37:32.160> think<00:37:32.359> of<00:37:32.560> that<00:37:32.680> are 00:37:33.230 --> 00:37:33.240 align:start position:0% organizations I can think of that are 00:37:33.240 --> 00:37:34.870 align:start position:0% organizations I can think of that are really<00:37:33.520> invested<00:37:33.920> in<00:37:34.200> okay<00:37:34.400> really<00:37:34.560> we<00:37:34.680> should 00:37:34.870 --> 00:37:34.880 align:start position:0% really invested in okay really we should 00:37:34.880 --> 00:37:36.630 align:start position:0% really invested in okay really we should get<00:37:35.000> client<00:37:35.319> side<00:37:35.480> proving<00:37:35.760> today 00:37:36.630 --> 00:37:36.640 align:start position:0% get client side proving today 00:37:36.640 --> 00:37:39.870 align:start position:0% get client side proving today because<00:37:37.640> you<00:37:37.839> kind<00:37:38.000> of<00:37:38.240> like<00:37:38.440> you<00:37:39.319> value<00:37:39.720> in 00:37:39.870 --> 00:37:39.880 align:start position:0% because you kind of like you value in 00:37:39.880 --> 00:37:41.750 align:start position:0% because you kind of like you value in crypto<00:37:40.160> often<00:37:40.560> Cru<00:37:40.880> to<00:37:41.000> the<00:37:41.079> points<00:37:41.280> of 00:37:41.750 --> 00:37:41.760 align:start position:0% crypto often Cru to the points of 00:37:41.760 --> 00:37:43.470 align:start position:0% crypto often Cru to the points of centralization<00:37:42.760> and<00:37:42.920> by<00:37:43.040> saying<00:37:43.280> we're<00:37:43.359> going 00:37:43.470 --> 00:37:43.480 align:start position:0% centralization and by saying we're going 00:37:43.480 --> 00:37:44.470 align:start position:0% centralization and by saying we're going to<00:37:43.560> do<00:37:43.680> client<00:37:43.960> side<00:37:44.079> proving<00:37:44.359> you're 00:37:44.470 --> 00:37:44.480 align:start position:0% to do client side proving you're 00:37:44.480 --> 00:37:45.829 align:start position:0% to do client side proving you're removing<00:37:44.839> that<00:37:44.920> point<00:37:45.079> of<00:37:45.200> centralization<00:37:45.720> of 00:37:45.829 --> 00:37:45.839 align:start position:0% removing that point of centralization of 00:37:45.839 --> 00:37:48.550 align:start position:0% removing that point of centralization of we<00:37:45.960> run<00:37:46.119> the<00:37:46.240> pro<00:37:46.560> we<00:37:46.720> make<00:37:46.880> the<00:37:46.960> money<00:37:47.920> um<00:37:48.480> and 00:37:48.550 --> 00:37:48.560 align:start position:0% we run the pro we make the money um and 00:37:48.560 --> 00:37:49.829 align:start position:0% we run the pro we make the money um and so<00:37:48.680> it's<00:37:48.839> not<00:37:49.000> currently<00:37:49.359> economically 00:37:49.829 --> 00:37:49.839 align:start position:0% so it's not currently economically 00:37:49.839 --> 00:37:51.109 align:start position:0% so it's not currently economically advantageous<00:37:50.440> for<00:37:50.640> infrastructure 00:37:51.109 --> 00:37:51.119 align:start position:0% advantageous for infrastructure 00:37:51.119 --> 00:37:53.030 align:start position:0% advantageous for infrastructure providers<00:37:51.560> to<00:37:51.720> do<00:37:51.880> client<00:37:52.200> side<00:37:52.319> proving<00:37:52.920> but 00:37:53.030 --> 00:37:53.040 align:start position:0% providers to do client side proving but 00:37:53.040 --> 00:37:54.670 align:start position:0% providers to do client side proving but when<00:37:53.240> applications<00:37:53.720> are<00:37:53.880> like<00:37:54.040> we<00:37:54.160> don't<00:37:54.560> we 00:37:54.670 --> 00:37:54.680 align:start position:0% when applications are like we don't we 00:37:54.680 --> 00:37:56.390 align:start position:0% when applications are like we don't we don't<00:37:54.800> want<00:37:54.880> to<00:37:55.079> pay<00:37:55.520> you<00:37:55.640> know<00:37:56.000> hundreds<00:37:56.280> of 00:37:56.390 --> 00:37:56.400 align:start position:0% don't want to pay you know hundreds of 00:37:56.400 --> 00:37:58.030 align:start position:0% don't want to pay you know hundreds of dollars<00:37:56.640> a<00:37:56.720> month<00:37:56.920> or<00:37:57.480> or<00:37:57.680> thousands<00:37:57.960> of 00:37:58.030 --> 00:37:58.040 align:start position:0% dollars a month or or thousands of 00:37:58.040 --> 00:37:59.470 align:start position:0% dollars a month or or thousands of dollars<00:37:58.240> a<00:37:58.319> month<00:37:58.520> to<00:37:58.680> you<00:37:59.119> then<00:37:59.240> all<00:37:59.319> of<00:37:59.400> a 00:37:59.470 --> 00:37:59.480 align:start position:0% dollars a month to you then all of a 00:37:59.480 --> 00:38:01.030 align:start position:0% dollars a month to you then all of a sudden<00:37:59.760> applications<00:38:00.160> are<00:38:00.319> now<00:38:00.480> incentivized 00:38:01.030 --> 00:38:01.040 align:start position:0% sudden applications are now incentivized 00:38:01.040 --> 00:38:02.430 align:start position:0% sudden applications are now incentivized to<00:38:01.119> use<00:38:01.400> somebody<00:38:01.680> who<00:38:01.800> is<00:38:01.960> providing<00:38:02.280> that 00:38:02.430 --> 00:38:02.440 align:start position:0% to use somebody who is providing that 00:38:02.440 --> 00:38:05.030 align:start position:0% to use somebody who is providing that client<00:38:02.760> side<00:38:02.920> proving<00:38:03.400> and<00:38:03.520> so<00:38:04.440> um<00:38:04.880> yeah 00:38:05.030 --> 00:38:05.040 align:start position:0% client side proving and so um yeah 00:38:05.040 --> 00:38:06.750 align:start position:0% client side proving and so um yeah that's<00:38:05.200> one<00:38:05.359> thing<00:38:05.880> that<00:38:06.040> I'm<00:38:06.200> excited<00:38:06.520> about 00:38:06.750 --> 00:38:06.760 align:start position:0% that's one thing that I'm excited about 00:38:06.760 --> 00:38:08.150 align:start position:0% that's one thing that I'm excited about in<00:38:06.839> the<00:38:06.960> future<00:38:07.319> infrastructure<00:38:07.839> wise<00:38:08.000> and 00:38:08.150 --> 00:38:08.160 align:start position:0% in the future infrastructure wise and 00:38:08.160 --> 00:38:10.150 align:start position:0% in the future infrastructure wise and also<00:38:08.319> for<00:38:08.480> mobile<00:38:08.800> proving<00:38:09.160> we've<00:38:09.319> seen<00:38:09.920> some 00:38:10.150 --> 00:38:10.160 align:start position:0% also for mobile proving we've seen some 00:38:10.160 --> 00:38:12.750 align:start position:0% also for mobile proving we've seen some teams<00:38:10.560> like<00:38:10.680> mpro<00:38:11.240> like<00:38:11.359> ligron<00:38:12.079> like<00:38:12.520> teams 00:38:12.750 --> 00:38:12.760 align:start position:0% teams like mpro like ligron like teams 00:38:12.760 --> 00:38:15.230 align:start position:0% teams like mpro like ligron like teams in<00:38:12.960> PSC<00:38:13.599> like<00:38:13.800> Noir<00:38:14.359> really<00:38:14.599> be<00:38:14.839> like<00:38:15.000> how<00:38:15.119> can 00:38:15.230 --> 00:38:15.240 align:start position:0% in PSC like Noir really be like how can 00:38:15.240 --> 00:38:18.109 align:start position:0% in PSC like Noir really be like how can we<00:38:15.359> get<00:38:15.480> this<00:38:15.599> client<00:38:15.920> side<00:38:16.040> proving<00:38:16.480> done<00:38:17.480> um 00:38:18.109 --> 00:38:18.119 align:start position:0% we get this client side proving done um 00:38:18.119 --> 00:38:19.349 align:start position:0% we get this client side proving done um and<00:38:18.280> yeah<00:38:18.440> we're<00:38:18.599> we're<00:38:18.720> excited<00:38:19.000> to<00:38:19.079> see<00:38:19.240> more 00:38:19.349 --> 00:38:19.359 align:start position:0% and yeah we're we're excited to see more 00:38:19.359 --> 00:38:20.550 align:start position:0% and yeah we're we're excited to see more of<00:38:19.480> that<00:38:19.640> there's<00:38:19.880> there's<00:38:20.000> a<00:38:20.079> lot<00:38:20.200> of<00:38:20.319> tech 00:38:20.550 --> 00:38:20.560 align:start position:0% of that there's there's a lot of tech 00:38:20.560 --> 00:38:23.109 align:start position:0% of that there's there's a lot of tech that<00:38:20.800> has<00:38:21.079> been<00:38:21.240> underutilize<00:38:21.920> like<00:38:22.079> web<00:38:22.240> GPU 00:38:23.109 --> 00:38:23.119 align:start position:0% that has been underutilize like web GPU 00:38:23.119 --> 00:38:25.349 align:start position:0% that has been underutilize like web GPU simd<00:38:23.599> acceleration<00:38:24.560> things<00:38:24.760> you<00:38:24.880> can<00:38:25.040> get<00:38:25.200> on 00:38:25.349 --> 00:38:25.359 align:start position:0% simd acceleration things you can get on 00:38:25.359 --> 00:38:27.510 align:start position:0% simd acceleration things you can get on mobile<00:38:25.680> devices<00:38:26.400> that<00:38:26.760> you<00:38:26.920> need<00:38:27.119> for<00:38:27.280> these 00:38:27.510 --> 00:38:27.520 align:start position:0% mobile devices that you need for these 00:38:27.520 --> 00:38:28.950 align:start position:0% mobile devices that you need for these email<00:38:27.760> proof<00:38:28.040> because<00:38:28.280> people<00:38:28.599> most<00:38:28.760> of<00:38:28.839> the 00:38:28.950 --> 00:38:28.960 align:start position:0% email proof because people most of the 00:38:28.960 --> 00:38:30.270 align:start position:0% email proof because people most of the time<00:38:29.079> are<00:38:29.160> just<00:38:29.280> going<00:38:29.359> to<00:38:29.440> scan<00:38:29.640> a<00:38:29.760> QR<00:38:30.040> code 00:38:30.270 --> 00:38:30.280 align:start position:0% time are just going to scan a QR code 00:38:30.280 --> 00:38:31.670 align:start position:0% time are just going to scan a QR code sign<00:38:30.440> into<00:38:30.640> their<00:38:30.720> email<00:38:31.000> on<00:38:31.160> mobile<00:38:31.440> and<00:38:31.560> make 00:38:31.670 --> 00:38:31.680 align:start position:0% sign into their email on mobile and make 00:38:31.680 --> 00:38:33.790 align:start position:0% sign into their email on mobile and make a<00:38:31.839> proof<00:38:32.400> and<00:38:32.839> you<00:38:32.960> want<00:38:33.040> to<00:38:33.200> make<00:38:33.319> that<00:38:33.480> flow 00:38:33.790 --> 00:38:33.800 align:start position:0% a proof and you want to make that flow 00:38:33.800 --> 00:38:36.309 align:start position:0% a proof and you want to make that flow as<00:38:34.000> fast<00:38:34.240> as 00:38:36.309 --> 00:38:36.319 align:start position:0% as fast as 00:38:36.319 --> 00:38:39.710 align:start position:0% as fast as possible<00:38:37.319> yeah<00:38:37.760> I<00:38:37.839> think<00:38:38.000> for<00:38:38.240> us<00:38:38.640> uh<00:38:38.760> we<00:38:39.240> Echo 00:38:39.710 --> 00:38:39.720 align:start position:0% possible yeah I think for us uh we Echo 00:38:39.720 --> 00:38:42.470 align:start position:0% possible yeah I think for us uh we Echo a<00:38:39.800> lot<00:38:39.920> of<00:38:40.040> the<00:38:40.200> same<00:38:40.440> things<00:38:41.040> uh<00:38:41.760> you<00:38:41.960> said 00:38:42.470 --> 00:38:42.480 align:start position:0% a lot of the same things uh you said 00:38:42.480 --> 00:38:44.710 align:start position:0% a lot of the same things uh you said about<00:38:42.960> client<00:38:43.280> side<00:38:43.480> proving<00:38:43.720> for<00:38:43.839> our<00:38:43.960> ZK 00:38:44.710 --> 00:38:44.720 align:start position:0% about client side proving for our ZK 00:38:44.720 --> 00:38:48.829 align:start position:0% about client side proving for our ZK stack<00:38:45.720> um<00:38:46.440> I<00:38:46.599> guess<00:38:47.000> for<00:38:47.280> us<00:38:47.920> we<00:38:48.119> also<00:38:48.520> since<00:38:48.720> we 00:38:48.829 --> 00:38:48.839 align:start position:0% stack um I guess for us we also since we 00:38:48.839 --> 00:38:52.270 align:start position:0% stack um I guess for us we also since we also<00:38:49.040> use<00:38:49.280> TLS<00:38:49.640> notary<00:38:50.040> and<00:38:50.160> the<00:38:50.240> MPC<00:38:50.960> side<00:38:51.960> um 00:38:52.270 --> 00:38:52.280 align:start position:0% also use TLS notary and the MPC side um 00:38:52.280 --> 00:38:54.069 align:start position:0% also use TLS notary and the MPC side um we're<00:38:52.800> I<00:38:52.880> guess<00:38:53.040> we're<00:38:53.280> especially<00:38:53.680> also 00:38:54.069 --> 00:38:54.079 align:start position:0% we're I guess we're especially also 00:38:54.079 --> 00:38:56.069 align:start position:0% we're I guess we're especially also really<00:38:54.280> interested<00:38:55.160> in<00:38:55.319> building<00:38:55.839> like<00:38:55.960> a 00:38:56.069 --> 00:38:56.079 align:start position:0% really interested in building like a 00:38:56.079 --> 00:38:59.670 align:start position:0% really interested in building like a mobile<00:38:56.440> based<00:38:56.720> flow<00:38:57.599> uh<00:38:57.720> to<00:38:57.880> enable<00:38:58.599> like<00:38:59.280> yeah 00:38:59.670 --> 00:38:59.680 align:start position:0% mobile based flow uh to enable like yeah 00:38:59.680 --> 00:39:00.910 align:start position:0% mobile based flow uh to enable like yeah enable<00:39:00.040> some<00:39:00.160> of<00:39:00.280> our 00:39:00.910 --> 00:39:00.920 align:start position:0% enable some of our 00:39:00.920 --> 00:39:04.349 align:start position:0% enable some of our marketplaces<00:39:01.920> and<00:39:02.240> the<00:39:02.359> bottleneck<00:39:03.079> there<00:39:03.960> um 00:39:04.349 --> 00:39:04.359 align:start position:0% marketplaces and the bottleneck there um 00:39:04.359 --> 00:39:07.309 align:start position:0% marketplaces and the bottleneck there um is<00:39:05.160> I<00:39:05.280> guess<00:39:05.640> the<00:39:05.960> it's<00:39:06.160> also<00:39:06.440> memory<00:39:07.000> where 00:39:07.309 --> 00:39:07.319 align:start position:0% is I guess the it's also memory where 00:39:07.319 --> 00:39:11.109 align:start position:0% is I guess the it's also memory where like<00:39:07.839> yeah<00:39:08.200> like<00:39:08.760> like<00:39:08.880> mobile<00:39:09.800> has<00:39:10.079> just<00:39:10.920> much 00:39:11.109 --> 00:39:11.119 align:start position:0% like yeah like like mobile has just much 00:39:11.119 --> 00:39:14.870 align:start position:0% like yeah like like mobile has just much lower<00:39:11.440> memory<00:39:12.200> um<00:39:12.960> than<00:39:13.119> on<00:39:13.480> I<00:39:13.599> guess<00:39:13.880> browser 00:39:14.870 --> 00:39:14.880 align:start position:0% lower memory um than on I guess browser 00:39:14.880 --> 00:39:17.790 align:start position:0% lower memory um than on I guess browser uh<00:39:15.640> but<00:39:16.079> yeah<00:39:16.359> also<00:39:16.720> like<00:39:16.920> bandwidth<00:39:17.640> and 00:39:17.790 --> 00:39:17.800 align:start position:0% uh but yeah also like bandwidth and 00:39:17.800 --> 00:39:20.710 align:start position:0% uh but yeah also like bandwidth and internet<00:39:18.200> connection<00:39:18.640> matters<00:39:18.920> a<00:39:19.079> lot<00:39:19.280> in<00:39:19.720> NPC 00:39:20.710 --> 00:39:20.720 align:start position:0% internet connection matters a lot in NPC 00:39:20.720 --> 00:39:23.230 align:start position:0% internet connection matters a lot in NPC um<00:39:20.960> and<00:39:21.160> when<00:39:21.280> you're<00:39:21.520> on<00:39:21.920> your<00:39:22.160> phone<00:39:23.119> um 00:39:23.230 --> 00:39:23.240 align:start position:0% um and when you're on your phone um 00:39:23.240 --> 00:39:27.069 align:start position:0% um and when you're on your phone um you're<00:39:23.480> typically<00:39:24.319> like<00:39:24.680> out<00:39:25.680> um<00:39:25.960> so<00:39:26.839> uh<00:39:26.960> you 00:39:27.069 --> 00:39:27.079 align:start position:0% you're typically like out um so uh you 00:39:27.079 --> 00:39:29.990 align:start position:0% you're typically like out um so uh you may<00:39:27.440> not<00:39:27.680> have<00:39:27.960> access<00:39:28.440> to<00:39:29.079> like<00:39:29.560> highspeed 00:39:29.990 --> 00:39:30.000 align:start position:0% may not have access to like highspeed 00:39:30.000 --> 00:39:32.349 align:start position:0% may not have access to like highspeed internet<00:39:30.400> for<00:39:30.599> example<00:39:31.079> to<00:39:31.880> like<00:39:32.000> finish 00:39:32.349 --> 00:39:32.359 align:start position:0% internet for example to like finish 00:39:32.359 --> 00:39:34.430 align:start position:0% internet for example to like finish generating<00:39:32.800> these<00:39:32.960> NPC<00:39:33.400> proofs<00:39:34.000> and<00:39:34.160> as<00:39:34.240> a 00:39:34.430 --> 00:39:34.440 align:start position:0% generating these NPC proofs and as a 00:39:34.440 --> 00:39:35.750 align:start position:0% generating these NPC proofs and as a result<00:39:34.720> like<00:39:34.800> the<00:39:34.880> connection<00:39:35.200> drops<00:39:35.680> and 00:39:35.750 --> 00:39:35.760 align:start position:0% result like the connection drops and 00:39:35.760 --> 00:39:37.990 align:start position:0% result like the connection drops and which<00:39:35.880> is<00:39:36.000> a<00:39:36.119> terrible<00:39:36.480> user<00:39:36.880> experience<00:39:37.880> uh 00:39:37.990 --> 00:39:38.000 align:start position:0% which is a terrible user experience uh 00:39:38.000 --> 00:39:40.109 align:start position:0% which is a terrible user experience uh for<00:39:38.160> some<00:39:38.359> people<00:39:39.079> but<00:39:39.280> I<00:39:39.359> think<00:39:39.560> there<00:39:39.680> are 00:39:40.109 --> 00:39:40.119 align:start position:0% for some people but I think there are 00:39:40.119 --> 00:39:43.150 align:start position:0% for some people but I think there are quite<00:39:40.319> a<00:39:40.480> lot<00:39:40.599> of<00:39:40.960> like<00:39:41.440> improvements<00:39:42.440> like 00:39:43.150 --> 00:39:43.160 align:start position:0% quite a lot of like improvements like 00:39:43.160 --> 00:39:45.550 align:start position:0% quite a lot of like improvements like coming<00:39:43.560> soon<00:39:44.119> on<00:39:44.240> the<00:39:44.359> NPC<00:39:44.760> front<00:39:45.000> on<00:39:45.079> the<00:39:45.200> TLs 00:39:45.550 --> 00:39:45.560 align:start position:0% coming soon on the NPC front on the TLs 00:39:45.560 --> 00:39:48.710 align:start position:0% coming soon on the NPC front on the TLs notary<00:39:45.920> front<00:39:46.599> which<00:39:47.599> uh<00:39:47.800> yeah<00:39:48.280> cuts<00:39:48.599> the 00:39:48.710 --> 00:39:48.720 align:start position:0% notary front which uh yeah cuts the 00:39:48.720 --> 00:39:51.230 align:start position:0% notary front which uh yeah cuts the bandwidth<00:39:49.200> requirement<00:39:49.760> by<00:39:50.000> like<00:39:51.000> I<00:39:51.079> don't 00:39:51.230 --> 00:39:51.240 align:start position:0% bandwidth requirement by like I don't 00:39:51.240 --> 00:39:55.670 align:start position:0% bandwidth requirement by like I don't know<00:39:51.599> like<00:39:52.079> like<00:39:52.200> a<00:39:52.359> huge<00:39:53.200> like<00:39:53.680> Factor<00:39:54.680> um<00:39:55.200> and 00:39:55.670 --> 00:39:55.680 align:start position:0% know like like a huge like Factor um and 00:39:55.680 --> 00:39:57.630 align:start position:0% know like like a huge like Factor um and yeah<00:39:55.839> we're<00:39:56.119> pretty<00:39:56.359> excited<00:39:56.640> to<00:39:56.800> adopt<00:39:57.079> that 00:39:57.630 --> 00:39:57.640 align:start position:0% yeah we're pretty excited to adopt that 00:39:57.640 --> 00:40:01.109 align:start position:0% yeah we're pretty excited to adopt that and<00:39:58.160> yeah<00:39:58.720> support<00:39:59.079> mobile<00:39:59.920> um<00:40:00.240> as<00:40:00.359> a<00:40:00.480> Next 00:40:01.109 --> 00:40:01.119 align:start position:0% and yeah support mobile um as a Next 00:40:01.119 --> 00:40:03.589 align:start position:0% and yeah support mobile um as a Next Step<00:40:02.119> yeah<00:40:02.240> I<00:40:02.319> think<00:40:02.520> like<00:40:02.880> mobile<00:40:03.200> is<00:40:03.359> super 00:40:03.589 --> 00:40:03.599 align:start position:0% Step yeah I think like mobile is super 00:40:03.599 --> 00:40:05.710 align:start position:0% Step yeah I think like mobile is super interesting<00:40:03.920> to<00:40:04.079> us<00:40:04.319> just<00:40:04.480> because<00:40:04.920> it<00:40:05.560> has 00:40:05.710 --> 00:40:05.720 align:start position:0% interesting to us just because it has 00:40:05.720 --> 00:40:08.710 align:start position:0% interesting to us just because it has such<00:40:05.880> a<00:40:06.119> wide<00:40:06.359> toolkit<00:40:06.880> for<00:40:07.280> social<00:40:07.680> apps<00:40:08.240> like 00:40:08.710 --> 00:40:08.720 align:start position:0% such a wide toolkit for social apps like 00:40:08.720 --> 00:40:10.910 align:start position:0% such a wide toolkit for social apps like things<00:40:09.000> like<00:40:09.560> Bluetooth<00:40:10.079> NFC<00:40:10.560> like<00:40:10.720> web 00:40:10.910 --> 00:40:10.920 align:start position:0% things like Bluetooth NFC like web 00:40:10.920 --> 00:40:12.870 align:start position:0% things like Bluetooth NFC like web Bluetooth<00:40:11.440> web<00:40:11.680> web<00:40:11.880> NFC<00:40:12.400> like<00:40:12.560> they<00:40:12.720> just 00:40:12.870 --> 00:40:12.880 align:start position:0% Bluetooth web web NFC like they just 00:40:12.880 --> 00:40:14.910 align:start position:0% Bluetooth web web NFC like they just suck<00:40:13.280> I<00:40:13.359> don't<00:40:13.520> know<00:40:13.680> they<00:40:13.760> just<00:40:13.880> don't<00:40:14.079> work 00:40:14.910 --> 00:40:14.920 align:start position:0% suck I don't know they just don't work 00:40:14.920 --> 00:40:16.349 align:start position:0% suck I don't know they just don't work um<00:40:15.040> or<00:40:15.200> like<00:40:15.359> not<00:40:15.520> supported<00:40:15.920> by<00:40:16.040> a<00:40:16.119> lot<00:40:16.240> of 00:40:16.349 --> 00:40:16.359 align:start position:0% um or like not supported by a lot of 00:40:16.359 --> 00:40:17.910 align:start position:0% um or like not supported by a lot of browsers<00:40:16.839> I<00:40:16.920> think<00:40:17.079> apple<00:40:17.359> has<00:40:17.480> a<00:40:17.599> lot<00:40:17.720> of 00:40:17.910 --> 00:40:17.920 align:start position:0% browsers I think apple has a lot of 00:40:17.920 --> 00:40:19.790 align:start position:0% browsers I think apple has a lot of security<00:40:18.359> restrictions<00:40:18.920> on<00:40:19.160> on<00:40:19.319> some<00:40:19.520> things 00:40:19.790 --> 00:40:19.800 align:start position:0% security restrictions on on some things 00:40:19.800 --> 00:40:22.510 align:start position:0% security restrictions on on some things there<00:40:20.560> um<00:40:20.720> and<00:40:20.839> it<00:40:20.960> just<00:40:21.079> sort<00:40:21.280> of<00:40:21.880> widens<00:40:22.359> the 00:40:22.510 --> 00:40:22.520 align:start position:0% there um and it just sort of widens the 00:40:22.520 --> 00:40:25.550 align:start position:0% there um and it just sort of widens the toolkit<00:40:23.440> of<00:40:23.640> things<00:40:23.960> that<00:40:24.079> you<00:40:24.200> can<00:40:24.599> build<00:40:25.440> uh 00:40:25.550 --> 00:40:25.560 align:start position:0% toolkit of things that you can build uh 00:40:25.560 --> 00:40:28.109 align:start position:0% toolkit of things that you can build uh in<00:40:25.680> the<00:40:25.839> social<00:40:26.240> context<00:40:27.160> um<00:40:27.400> um<00:40:27.560> so<00:40:27.760> I<00:40:27.839> think 00:40:28.109 --> 00:40:28.119 align:start position:0% in the social context um um so I think 00:40:28.119 --> 00:40:31.190 align:start position:0% in the social context um um so I think like<00:40:28.839> mobile<00:40:29.280> to<00:40:29.440> me<00:40:29.760> is<00:40:29.920> super<00:40:30.200> important<00:40:30.880> and 00:40:31.190 --> 00:40:31.200 align:start position:0% like mobile to me is super important and 00:40:31.200 --> 00:40:33.589 align:start position:0% like mobile to me is super important and it<00:40:31.359> also<00:40:31.599> is<00:40:31.800> just<00:40:31.960> like<00:40:32.079> a<00:40:32.280> much<00:40:32.440> more<00:40:33.040> buttery 00:40:33.589 --> 00:40:33.599 align:start position:0% it also is just like a much more buttery 00:40:33.599 --> 00:40:35.710 align:start position:0% it also is just like a much more buttery experience<00:40:34.160> than<00:40:34.359> a<00:40:34.599> than<00:40:34.720> a<00:40:34.839> web<00:40:35.040> app<00:40:35.480> but 00:40:35.710 --> 00:40:35.720 align:start position:0% experience than a than a web app but 00:40:35.720 --> 00:40:36.710 align:start position:0% experience than a than a web app but then<00:40:35.800> you<00:40:35.920> have<00:40:36.040> the<00:40:36.119> question<00:40:36.319> of<00:40:36.480> like<00:40:36.640> how 00:40:36.710 --> 00:40:36.720 align:start position:0% then you have the question of like how 00:40:36.720 --> 00:40:37.910 align:start position:0% then you have the question of like how do<00:40:36.800> you<00:40:36.880> get<00:40:37.000> people<00:40:37.119> to<00:40:37.240> download<00:40:37.520> a<00:40:37.599> mobile 00:40:37.910 --> 00:40:37.920 align:start position:0% do you get people to download a mobile 00:40:37.920 --> 00:40:40.790 align:start position:0% do you get people to download a mobile app<00:40:38.560> I<00:40:38.640> don't<00:40:38.800> know<00:40:39.760> yeah<00:40:40.200> there's<00:40:40.560> there's 00:40:40.790 --> 00:40:40.800 align:start position:0% app I don't know yeah there's there's 00:40:40.800 --> 00:40:43.510 align:start position:0% app I don't know yeah there's there's these<00:40:40.960> things<00:40:41.200> called<00:40:41.480> app<00:40:41.720> clips<00:40:42.400> now<00:40:43.400> you 00:40:43.510 --> 00:40:43.520 align:start position:0% these things called app clips now you 00:40:43.520 --> 00:40:45.309 align:start position:0% these things called app clips now you don't<00:40:43.680> need<00:40:43.839> to<00:40:44.200> download<00:40:44.480> a<00:40:44.640> mobile<00:40:44.880> app<00:40:45.240> tell 00:40:45.309 --> 00:40:45.319 align:start position:0% don't need to download a mobile app tell 00:40:45.319 --> 00:40:46.910 align:start position:0% don't need to download a mobile app tell me<00:40:45.440> about<00:40:45.640> app 00:40:46.910 --> 00:40:46.920 align:start position:0% me about app 00:40:46.920 --> 00:40:49.510 align:start position:0% me about app Clips<00:40:47.920> yeah<00:40:48.160> it's<00:40:48.640> um<00:40:49.000> yeah<00:40:49.119> so<00:40:49.319> there's 00:40:49.510 --> 00:40:49.520 align:start position:0% Clips yeah it's um yeah so there's 00:40:49.520 --> 00:40:51.589 align:start position:0% Clips yeah it's um yeah so there's basically<00:40:49.880> these<00:40:50.079> app<00:40:50.359> clips<00:40:50.960> and<00:40:51.280> instant 00:40:51.589 --> 00:40:51.599 align:start position:0% basically these app clips and instant 00:40:51.599 --> 00:40:55.190 align:start position:0% basically these app clips and instant apps<00:40:51.839> on<00:40:51.960> the<00:40:52.079> Android<00:40:52.440> store<00:40:52.920> where<00:40:53.880> uh<00:40:54.640> like 00:40:55.190 --> 00:40:55.200 align:start position:0% apps on the Android store where uh like 00:40:55.200 --> 00:40:58.430 align:start position:0% apps on the Android store where uh like Google<00:40:55.520> or<00:40:55.839> um<00:40:56.079> Google<00:40:56.520> and<00:40:56.839> Apple<00:40:57.400> offer<00:40:58.119> ways 00:40:58.430 --> 00:40:58.440 align:start position:0% Google or um Google and Apple offer ways 00:40:58.440 --> 00:41:01.990 align:start position:0% Google or um Google and Apple offer ways for<00:40:58.680> you<00:40:58.880> to<00:40:59.520> like<00:41:00.079> try<00:41:00.400> out<00:41:00.960> the<00:41:01.200> app<00:41:01.640> without 00:41:01.990 --> 00:41:02.000 align:start position:0% for you to like try out the app without 00:41:02.000 --> 00:41:03.710 align:start position:0% for you to like try out the app without actually<00:41:02.359> downloading<00:41:03.240> going<00:41:03.440> through<00:41:03.599> the 00:41:03.710 --> 00:41:03.720 align:start position:0% actually downloading going through the 00:41:03.720 --> 00:41:05.670 align:start position:0% actually downloading going through the App<00:41:03.920> Store<00:41:04.319> so<00:41:04.480> you<00:41:04.640> basically<00:41:04.960> scan<00:41:05.200> a<00:41:05.359> QR 00:41:05.670 --> 00:41:05.680 align:start position:0% App Store so you basically scan a QR 00:41:05.680 --> 00:41:08.510 align:start position:0% App Store so you basically scan a QR code<00:41:06.119> it<00:41:06.240> loads<00:41:06.640> some<00:41:06.920> like<00:41:07.119> temporary<00:41:08.119> like 00:41:08.510 --> 00:41:08.520 align:start position:0% code it loads some like temporary like 00:41:08.520 --> 00:41:10.790 align:start position:0% code it loads some like temporary like uh<00:41:08.760> like<00:41:08.880> a<00:41:09.040> binary<00:41:09.640> on<00:41:09.760> your<00:41:10.000> phone<00:41:10.560> and<00:41:10.640> you 00:41:10.790 --> 00:41:10.800 align:start position:0% uh like a binary on your phone and you 00:41:10.800 --> 00:41:12.430 align:start position:0% uh like a binary on your phone and you get<00:41:10.920> to<00:41:11.079> interact<00:41:11.560> with<00:41:11.880> some<00:41:12.079> limited 00:41:12.430 --> 00:41:12.440 align:start position:0% get to interact with some limited 00:41:12.440 --> 00:41:14.270 align:start position:0% get to interact with some limited features<00:41:13.040> of<00:41:13.160> the<00:41:13.359> application<00:41:14.000> without 00:41:14.270 --> 00:41:14.280 align:start position:0% features of the application without 00:41:14.280 --> 00:41:18.870 align:start position:0% features of the application without needing<00:41:14.599> to<00:41:15.440> go<00:41:15.560> through<00:41:15.720> the<00:41:15.839> App 00:41:18.870 --> 00:41:18.880 align:start position:0% 00:41:18.880 --> 00:41:21.829 align:start position:0% Store<00:41:19.880> maybe<00:41:20.520> like<00:41:20.760> one<00:41:21.079> point<00:41:21.480> that<00:41:21.599> kind<00:41:21.720> of 00:41:21.829 --> 00:41:21.839 align:start position:0% Store maybe like one point that kind of 00:41:21.839 --> 00:41:24.270 align:start position:0% Store maybe like one point that kind of touches<00:41:22.119> on<00:41:22.319> another<00:41:22.760> question<00:41:23.040> you<00:41:23.280> wanted 00:41:24.270 --> 00:41:24.280 align:start position:0% touches on another question you wanted 00:41:24.280 --> 00:41:26.670 align:start position:0% touches on another question you wanted is<00:41:24.920> um<00:41:25.680> like<00:41:25.839> something<00:41:26.079> that<00:41:26.200> I'm<00:41:26.359> excited 00:41:26.670 --> 00:41:26.680 align:start position:0% is um like something that I'm excited 00:41:26.680 --> 00:41:27.790 align:start position:0% is um like something that I'm excited about<00:41:26.880> is<00:41:27.000> something<00:41:27.319> something<00:41:27.560> that<00:41:27.720> I 00:41:27.790 --> 00:41:27.800 align:start position:0% about is something something that I 00:41:27.800 --> 00:41:29.829 align:start position:0% about is something something that I think<00:41:28.000> both<00:41:28.119> of<00:41:28.240> you<00:41:28.480> mentioned<00:41:28.920> a<00:41:29.040> little<00:41:29.240> bit 00:41:29.829 --> 00:41:29.839 align:start position:0% think both of you mentioned a little bit 00:41:29.839 --> 00:41:31.950 align:start position:0% think both of you mentioned a little bit is<00:41:30.079> about<00:41:30.319> the<00:41:30.440> different<00:41:30.680> models<00:41:31.000> of<00:41:31.160> NPC<00:41:31.680> so 00:41:31.950 --> 00:41:31.960 align:start position:0% is about the different models of NPC so 00:41:31.960 --> 00:41:33.829 align:start position:0% is about the different models of NPC so like<00:41:32.119> the<00:41:32.240> one<00:41:32.480> where<00:41:32.760> the<00:41:32.880> user<00:41:33.319> is<00:41:33.560> actually 00:41:33.829 --> 00:41:33.839 align:start position:0% like the one where the user is actually 00:41:33.839 --> 00:41:37.309 align:start position:0% like the one where the user is actually part<00:41:34.000> of<00:41:34.119> the<00:41:34.280> computation<00:41:35.040> or<00:41:35.720> when<00:41:36.480> uh<00:41:37.200> yeah 00:41:37.309 --> 00:41:37.319 align:start position:0% part of the computation or when uh yeah 00:41:37.319 --> 00:41:39.870 align:start position:0% part of the computation or when uh yeah it's<00:41:37.440> a<00:41:37.640> different<00:41:38.560> like<00:41:38.960> you<00:41:39.119> delegate<00:41:39.560> fully 00:41:39.870 --> 00:41:39.880 align:start position:0% it's a different like you delegate fully 00:41:39.880 --> 00:41:42.710 align:start position:0% it's a different like you delegate fully everything<00:41:40.160> to<00:41:40.319> the<00:41:40.560> network<00:41:41.560> um<00:41:42.160> and<00:41:42.280> so<00:41:42.560> like 00:41:42.710 --> 00:41:42.720 align:start position:0% everything to the network um and so like 00:41:42.720 --> 00:41:45.390 align:start position:0% everything to the network um and so like in<00:41:42.960> some<00:41:43.440> cases<00:41:43.880> it<00:41:44.119> can<00:41:44.359> be<00:41:44.680> that<00:41:45.000> you<00:41:45.119> know<00:41:45.280> as 00:41:45.390 --> 00:41:45.400 align:start position:0% in some cases it can be that you know as 00:41:45.400 --> 00:41:47.910 align:start position:0% in some cases it can be that you know as long<00:41:45.599> as<00:41:45.760> one<00:41:46.040> per<00:41:46.359> party<00:41:46.760> is<00:41:46.960> honest<00:41:47.560> that<00:41:47.839> you 00:41:47.910 --> 00:41:47.920 align:start position:0% long as one per party is honest that you 00:41:47.920 --> 00:41:49.990 align:start position:0% long as one per party is honest that you know<00:41:48.079> the<00:41:48.200> whole<00:41:48.400> thing<00:41:48.599> can<00:41:48.960> remain<00:41:49.160> secure 00:41:49.990 --> 00:41:50.000 align:start position:0% know the whole thing can remain secure 00:41:50.000 --> 00:41:52.030 align:start position:0% know the whole thing can remain secure and<00:41:50.079> so<00:41:50.319> if<00:41:50.480> I'm<00:41:50.800> involved<00:41:51.280> in<00:41:51.400> this<00:41:51.560> protocol 00:41:52.030 --> 00:41:52.040 align:start position:0% and so if I'm involved in this protocol 00:41:52.040 --> 00:41:54.030 align:start position:0% and so if I'm involved in this protocol and<00:41:52.160> I<00:41:52.240> know<00:41:52.599> for<00:41:52.760> sure<00:41:53.000> that<00:41:53.160> I'm<00:41:53.319> honest<00:41:53.800> then 00:41:54.030 --> 00:41:54.040 align:start position:0% and I know for sure that I'm honest then 00:41:54.040 --> 00:41:56.030 align:start position:0% and I know for sure that I'm honest then I<00:41:54.160> can<00:41:54.440> say<00:41:54.720> that<00:41:54.920> this<00:41:55.040> is<00:41:55.160> a<00:41:55.319> good<00:41:55.720> like<00:41:55.880> that 00:41:56.030 --> 00:41:56.040 align:start position:0% I can say that this is a good like that 00:41:56.040 --> 00:41:57.390 align:start position:0% I can say that this is a good like that this<00:41:56.240> protocol<00:41:56.599> is<00:41:56.720> secure<00:41:56.960> and<00:41:57.079> this<00:41:57.280> no 00:41:57.390 --> 00:41:57.400 align:start position:0% this protocol is secure and this no 00:41:57.400 --> 00:41:59.710 align:start position:0% this protocol is secure and this no collusion<00:41:57.839> happening<00:41:58.760> we're<00:41:59.040> like<00:41:59.319> quite<00:41:59.640> I 00:41:59.710 --> 00:41:59.720 align:start position:0% collusion happening we're like quite I 00:41:59.720 --> 00:42:02.230 align:start position:0% collusion happening we're like quite I think<00:42:00.400> not<00:42:00.800> there<00:42:01.079> yet<00:42:01.319> at<00:42:01.440> all<00:42:01.599> for<00:42:01.839> that<00:42:02.040> but 00:42:02.230 --> 00:42:02.240 align:start position:0% think not there yet at all for that but 00:42:02.240 --> 00:42:03.950 align:start position:0% think not there yet at all for that but like<00:42:02.480> I<00:42:02.560> would<00:42:02.720> love<00:42:02.960> to<00:42:03.079> see<00:42:03.400> this<00:42:03.599> happening 00:42:03.950 --> 00:42:03.960 align:start position:0% like I would love to see this happening 00:42:03.960 --> 00:42:06.349 align:start position:0% like I would love to see this happening this<00:42:04.040> would<00:42:04.200> be<00:42:04.319> super<00:42:04.599> cool<00:42:05.359> oh<00:42:05.680> absolutely 00:42:06.349 --> 00:42:06.359 align:start position:0% this would be super cool oh absolutely 00:42:06.359 --> 00:42:08.829 align:start position:0% this would be super cool oh absolutely that's<00:42:06.680> like<00:42:07.480> um<00:42:07.880> one<00:42:08.040> of<00:42:08.160> the<00:42:08.359> interesting 00:42:08.829 --> 00:42:08.839 align:start position:0% that's like um one of the interesting 00:42:08.839 --> 00:42:11.750 align:start position:0% that's like um one of the interesting thing<00:42:09.040> about<00:42:09.319> coars<00:42:10.040> as<00:42:10.200> well<00:42:10.880> is<00:42:11.200> because<00:42:11.480> of 00:42:11.750 --> 00:42:11.760 align:start position:0% thing about coars as well is because of 00:42:11.760 --> 00:42:14.150 align:start position:0% thing about coars as well is because of the<00:42:12.359> security<00:42:12.839> guarantee<00:42:13.359> from<00:42:13.520> the<00:42:13.680> snark 00:42:14.150 --> 00:42:14.160 align:start position:0% the security guarantee from the snark 00:42:14.160 --> 00:42:16.349 align:start position:0% the security guarantee from the snark site<00:42:14.440> you<00:42:14.560> can<00:42:14.880> relax<00:42:15.520> requirements<00:42:16.079> on<00:42:16.240> the 00:42:16.349 --> 00:42:16.359 align:start position:0% site you can relax requirements on the 00:42:16.359 --> 00:42:19.430 align:start position:0% site you can relax requirements on the MPC<00:42:16.960> site<00:42:17.520> and<00:42:17.640> so<00:42:18.040> yeah<00:42:18.319> all<00:42:18.839> all<00:42:19.040> these<00:42:19.240> sort 00:42:19.430 --> 00:42:19.440 align:start position:0% MPC site and so yeah all all these sort 00:42:19.440 --> 00:42:20.309 align:start position:0% MPC site and so yeah all all these sort of 00:42:20.309 --> 00:42:20.319 align:start position:0% of 00:42:20.319 --> 00:42:24.109 align:start position:0% of interesting<00:42:21.319> like<00:42:21.920> paradigms<00:42:22.920> emerge<00:42:23.920> um 00:42:24.109 --> 00:42:24.119 align:start position:0% interesting like paradigms emerge um 00:42:24.119 --> 00:42:26.190 align:start position:0% interesting like paradigms emerge um when<00:42:24.280> you're<00:42:24.880> like<00:42:25.240> confronted<00:42:25.800> with<00:42:26.000> these 00:42:26.190 --> 00:42:26.200 align:start position:0% when you're like confronted with these 00:42:26.200 --> 00:42:29.870 align:start position:0% when you're like confronted with these use<00:42:26.640> cases<00:42:27.440> um<00:42:27.800> where<00:42:28.359> and<00:42:28.599> they<00:42:28.880> they<00:42:29.040> can 00:42:29.870 --> 00:42:29.880 align:start position:0% use cases um where and they they can 00:42:29.880 --> 00:42:31.630 align:start position:0% use cases um where and they they can like<00:42:30.079> these<00:42:30.280> huse<00:42:30.599> cases<00:42:30.880> become<00:42:31.200> interesting 00:42:31.630 --> 00:42:31.640 align:start position:0% like these huse cases become interesting 00:42:31.640 --> 00:42:34.430 align:start position:0% like these huse cases become interesting in<00:42:31.920> applications<00:42:32.599> like<00:42:32.880> maybe<00:42:33.559> in<00:42:33.800> Academia 00:42:34.430 --> 00:42:34.440 align:start position:0% in applications like maybe in Academia 00:42:34.440 --> 00:42:36.670 align:start position:0% in applications like maybe in Academia they<00:42:34.559> were<00:42:34.760> not<00:42:35.040> interesting<00:42:35.680> theoretically 00:42:36.670 --> 00:42:36.680 align:start position:0% they were not interesting theoretically 00:42:36.680 --> 00:42:39.150 align:start position:0% they were not interesting theoretically but<00:42:36.960> yeah<00:42:37.359> like<00:42:37.599> in<00:42:37.880> practice<00:42:38.359> you<00:42:38.520> realize 00:42:39.150 --> 00:42:39.160 align:start position:0% but yeah like in practice you realize 00:42:39.160 --> 00:42:42.270 align:start position:0% but yeah like in practice you realize okay<00:42:39.559> like<00:42:40.000> this<00:42:40.160> is<00:42:40.640> like<00:42:40.880> an<00:42:41.119> opportunity<00:42:42.119> um 00:42:42.270 --> 00:42:42.280 align:start position:0% okay like this is like an opportunity um 00:42:42.280 --> 00:42:44.990 align:start position:0% okay like this is like an opportunity um to<00:42:42.680> like<00:42:42.880> get<00:42:43.160> some<00:42:43.400> performance<00:42:43.880> gains<00:42:44.839> yeah 00:42:44.990 --> 00:42:45.000 align:start position:0% to like get some performance gains yeah 00:42:45.000 --> 00:42:47.589 align:start position:0% to like get some performance gains yeah so<00:42:45.160> that's<00:42:45.319> a<00:42:45.480> really<00:42:45.720> cool<00:42:46.160> point<00:42:47.160> I<00:42:47.319> guess 00:42:47.589 --> 00:42:47.599 align:start position:0% so that's a really cool point I guess 00:42:47.599 --> 00:42:51.069 align:start position:0% so that's a really cool point I guess with<00:42:47.960> my<00:42:48.280> remaining<00:42:48.680> two<00:42:49.000> and<00:42:49.200> a<00:42:49.359> half<00:42:50.079> minutes 00:42:51.069 --> 00:42:51.079 align:start position:0% with my remaining two and a half minutes 00:42:51.079 --> 00:42:54.430 align:start position:0% with my remaining two and a half minutes um<00:42:51.880> I<00:42:52.000> want<00:42:52.200> to<00:42:53.160> I<00:42:53.240> want<00:42:53.359> to<00:42:53.599> find<00:42:53.800> out<00:42:54.200> what 00:42:54.430 --> 00:42:54.440 align:start position:0% um I want to I want to find out what 00:42:54.440 --> 00:42:59.270 align:start position:0% um I want to I want to find out what you're<00:42:54.839> excited<00:42:55.400> about<00:42:56.040> so<00:42:57.240> yeah<00:42:58.040> what<00:42:59.040> what 00:42:59.270 --> 00:42:59.280 align:start position:0% you're excited about so yeah what what 00:42:59.280 --> 00:43:00.990 align:start position:0% you're excited about so yeah what what applications<00:42:59.839> have<00:42:59.960> you<00:43:00.079> seen<00:43:00.440> that<00:43:00.559> are<00:43:00.760> like 00:43:00.990 --> 00:43:01.000 align:start position:0% applications have you seen that are like 00:43:01.000 --> 00:43:03.990 align:start position:0% applications have you seen that are like wow<00:43:01.400> far<00:43:01.720> out<00:43:02.000> there<00:43:02.359> or<00:43:02.839> what<00:43:03.079> applications 00:43:03.990 --> 00:43:04.000 align:start position:0% wow far out there or what applications 00:43:04.000 --> 00:43:06.230 align:start position:0% wow far out there or what applications can<00:43:04.160> you<00:43:04.440> imagine<00:43:05.319> um<00:43:05.520> what 00:43:06.230 --> 00:43:06.240 align:start position:0% can you imagine um what 00:43:06.240 --> 00:43:09.589 align:start position:0% can you imagine um what applications<00:43:07.240> um<00:43:07.960> would<00:43:08.160> be<00:43:08.400> like<00:43:08.760> holy<00:43:09.160> grail 00:43:09.589 --> 00:43:09.599 align:start position:0% applications um would be like holy grail 00:43:09.599 --> 00:43:14.230 align:start position:0% applications um would be like holy grail for<00:43:09.839> you<00:43:10.720> um<00:43:11.520> and<00:43:11.760> this<00:43:11.960> can<00:43:12.280> involve<00:43:13.040> like<00:43:14.040> uh 00:43:14.230 --> 00:43:14.240 align:start position:0% for you um and this can involve like uh 00:43:14.240 --> 00:43:15.589 align:start position:0% for you um and this can involve like uh this<00:43:14.359> can<00:43:14.480> be<00:43:14.680> extensions<00:43:15.119> of<00:43:15.319> what<00:43:15.400> you're 00:43:15.589 --> 00:43:15.599 align:start position:0% this can be extensions of what you're 00:43:15.599 --> 00:43:18.470 align:start position:0% this can be extensions of what you're working<00:43:15.880> on<00:43:16.160> now<00:43:16.760> or<00:43:16.920> it<00:43:17.040> can<00:43:17.319> even<00:43:17.680> involve 00:43:18.470 --> 00:43:18.480 align:start position:0% working on now or it can even involve 00:43:18.480 --> 00:43:21.349 align:start position:0% working on now or it can even involve like<00:43:19.280> um<00:43:19.440> far<00:43:19.720> out<00:43:20.000> Primitives<00:43:20.599> that<00:43:21.160> you're 00:43:21.349 --> 00:43:21.359 align:start position:0% like um far out Primitives that you're 00:43:21.359 --> 00:43:23.589 align:start position:0% like um far out Primitives that you're looking<00:43:21.640> at<00:43:21.920> like<00:43:22.119> witness<00:43:22.559> encryption<00:43:23.119> or 00:43:23.589 --> 00:43:23.599 align:start position:0% looking at like witness encryption or 00:43:23.599 --> 00:43:26.910 align:start position:0% looking at like witness encryption or something<00:43:24.599> um<00:43:25.440> yeah<00:43:25.640> I'd<00:43:25.800> like<00:43:25.960> to<00:43:26.160> hear<00:43:26.760> um 00:43:26.910 --> 00:43:26.920 align:start position:0% something um yeah I'd like to hear um 00:43:26.920 --> 00:43:28.750 align:start position:0% something um yeah I'd like to hear um what<00:43:27.119> what<00:43:27.280> in<00:43:27.440> store<00:43:27.680> for<00:43:27.920> the<00:43:28.160> next<00:43:28.480> few 00:43:28.750 --> 00:43:28.760 align:start position:0% what what in store for the next few 00:43:28.760 --> 00:43:32.790 align:start position:0% what what in store for the next few months<00:43:29.200> and 00:43:32.790 --> 00:43:32.800 align:start position:0% 00:43:32.800 --> 00:43:35.630 align:start position:0% years<00:43:33.800> I<00:43:34.079> personally<00:43:34.599> really<00:43:34.800> want<00:43:34.960> to<00:43:35.160> see 00:43:35.630 --> 00:43:35.640 align:start position:0% years I personally really want to see 00:43:35.640 --> 00:43:37.829 align:start position:0% years I personally really want to see more<00:43:36.240> digital<00:43:36.599> signatures<00:43:37.119> and<00:43:37.280> more<00:43:37.480> ZK 00:43:37.829 --> 00:43:37.839 align:start position:0% more digital signatures and more ZK 00:43:37.839 --> 00:43:39.829 align:start position:0% more digital signatures and more ZK poofs<00:43:38.119> of<00:43:38.280> those<00:43:38.440> signatures<00:43:39.319> I<00:43:39.400> mean<00:43:39.520> emails 00:43:39.829 --> 00:43:39.839 align:start position:0% poofs of those signatures I mean emails 00:43:39.839 --> 00:43:41.750 align:start position:0% poofs of those signatures I mean emails is<00:43:40.000> just<00:43:40.119> one<00:43:40.319> example<00:43:40.720> but<00:43:40.839> if<00:43:40.920> you<00:43:41.040> can<00:43:41.280> get 00:43:41.750 --> 00:43:41.760 align:start position:0% is just one example but if you can get 00:43:41.760 --> 00:43:43.589 align:start position:0% is just one example but if you can get for<00:43:41.920> instance<00:43:42.240> designed<00:43:42.680> website<00:43:43.079> standards 00:43:43.589 --> 00:43:43.599 align:start position:0% for instance designed website standards 00:43:43.599 --> 00:43:45.910 align:start position:0% for instance designed website standards to<00:43:43.760> be<00:43:43.960> more<00:43:44.359> adopted<00:43:44.880> you<00:43:44.960> can<00:43:45.200> get<00:43:45.680> any 00:43:45.910 --> 00:43:45.920 align:start position:0% to be more adopted you can get any 00:43:45.920 --> 00:43:47.589 align:start position:0% to be more adopted you can get any website<00:43:46.240> frontend<00:43:46.680> now<00:43:46.839> approved<00:43:47.119> on<00:43:47.280> chain 00:43:47.589 --> 00:43:47.599 align:start position:0% website frontend now approved on chain 00:43:47.599 --> 00:43:48.710 align:start position:0% website frontend now approved on chain and<00:43:47.760> you<00:43:47.839> can<00:43:47.960> already<00:43:48.160> do<00:43:48.280> this<00:43:48.400> with<00:43:48.559> some 00:43:48.710 --> 00:43:48.720 align:start position:0% and you can already do this with some 00:43:48.720 --> 00:43:51.270 align:start position:0% and you can already do this with some things<00:43:48.960> like<00:43:49.359> Forbes<00:43:49.800> in<00:43:49.920> Italy<00:43:50.880> um<00:43:51.079> but<00:43:51.200> it 00:43:51.270 --> 00:43:51.280 align:start position:0% things like Forbes in Italy um but it 00:43:51.280 --> 00:43:53.510 align:start position:0% things like Forbes in Italy um but it would<00:43:51.440> be<00:43:51.599> great<00:43:51.800> if<00:43:52.000> more<00:43:52.160> websites<00:43:52.599> did<00:43:52.839> this 00:43:53.510 --> 00:43:53.520 align:start position:0% would be great if more websites did this 00:43:53.520 --> 00:43:56.630 align:start position:0% would be great if more websites did this I'm<00:43:53.680> also<00:43:53.920> excited<00:43:54.480> about<00:43:55.480> um<00:43:56.119> pufs<00:43:56.559> like 00:43:56.630 --> 00:43:56.640 align:start position:0% I'm also excited about um pufs like 00:43:56.640 --> 00:43:58.630 align:start position:0% I'm also excited about um pufs like physical<00:43:57.160> clonable<00:43:57.559> functions<00:43:58.119> being<00:43:58.480> the 00:43:58.630 --> 00:43:58.640 align:start position:0% physical clonable functions being the 00:43:58.640 --> 00:44:01.589 align:start position:0% physical clonable functions being the route<00:43:59.200> for<00:43:59.440> new<00:43:59.720> open<00:43:59.960> source<00:44:00.200> tees<00:44:00.960> I<00:44:01.079> think 00:44:01.589 --> 00:44:01.599 align:start position:0% route for new open source tees I think 00:44:01.599 --> 00:44:04.510 align:start position:0% route for new open source tees I think uh<00:44:02.559> like<00:44:02.960> uh<00:44:03.280> open<00:44:03.520> source<00:44:03.720> tees<00:44:04.119> is<00:44:04.240> kind<00:44:04.319> of<00:44:04.400> a 00:44:04.510 --> 00:44:04.520 align:start position:0% uh like uh open source tees is kind of a 00:44:04.520 --> 00:44:06.670 align:start position:0% uh like uh open source tees is kind of a holy<00:44:04.760> grail<00:44:05.079> and<00:44:05.280> gives<00:44:05.520> us<00:44:05.720> the<00:44:05.880> ability<00:44:06.359> to 00:44:06.670 --> 00:44:06.680 align:start position:0% holy grail and gives us the ability to 00:44:06.680 --> 00:44:08.349 align:start position:0% holy grail and gives us the ability to to<00:44:06.800> do<00:44:06.880> a<00:44:06.960> lot<00:44:07.040> of<00:44:07.119> this<00:44:07.280> private<00:44:07.520> computation 00:44:08.349 --> 00:44:08.359 align:start position:0% to do a lot of this private computation 00:44:08.359 --> 00:44:10.230 align:start position:0% to do a lot of this private computation without<00:44:08.640> having<00:44:08.800> to<00:44:08.920> rely<00:44:09.200> in<00:44:09.680> uh<00:44:10.000> you<00:44:10.119> know 00:44:10.230 --> 00:44:10.240 align:start position:0% without having to rely in uh you know 00:44:10.240 --> 00:44:13.309 align:start position:0% without having to rely in uh you know Intel<00:44:10.520> getting<00:44:10.720> hacked<00:44:10.960> every<00:44:11.119> two<00:44:11.319> years<00:44:12.319> um 00:44:13.309 --> 00:44:13.319 align:start position:0% Intel getting hacked every two years um 00:44:13.319 --> 00:44:14.589 align:start position:0% Intel getting hacked every two years um what<00:44:13.440> else<00:44:13.800> I'm<00:44:13.960> excited<00:44:14.240> about<00:44:14.319> witness 00:44:14.589 --> 00:44:14.599 align:start position:0% what else I'm excited about witness 00:44:14.599 --> 00:44:16.470 align:start position:0% what else I'm excited about witness encryption<00:44:15.119> I<00:44:15.240> think<00:44:15.440> more<00:44:15.680> research<00:44:16.079> around 00:44:16.470 --> 00:44:16.480 align:start position:0% encryption I think more research around 00:44:16.480 --> 00:44:17.910 align:start position:0% encryption I think more research around new<00:44:16.720> kinds<00:44:16.920> of<00:44:17.079> privacy<00:44:17.359> modes<00:44:17.640> and<00:44:17.760> maybe 00:44:17.910 --> 00:44:17.920 align:start position:0% new kinds of privacy modes and maybe 00:44:17.920 --> 00:44:19.270 align:start position:0% new kinds of privacy modes and maybe I'll<00:44:18.000> even<00:44:18.200> that<00:44:18.319> Andrew<00:44:18.640> talk<00:44:18.839> more<00:44:19.000> about 00:44:19.270 --> 00:44:19.280 align:start position:0% I'll even that Andrew talk more about 00:44:19.280 --> 00:44:23.309 align:start position:0% I'll even that Andrew talk more about that<00:44:20.240> and<00:44:21.440> um<00:44:22.440> yeah<00:44:22.559> I'm<00:44:22.680> also<00:44:22.839> excited<00:44:23.160> about 00:44:23.309 --> 00:44:23.319 align:start position:0% that and um yeah I'm also excited about 00:44:23.319 --> 00:44:25.349 align:start position:0% that and um yeah I'm also excited about more<00:44:23.480> far<00:44:23.680> out<00:44:23.920> things<00:44:24.240> like<00:44:24.680> making<00:44:25.040> certain 00:44:25.349 --> 00:44:25.359 align:start position:0% more far out things like making certain 00:44:25.359 --> 00:44:27.390 align:start position:0% more far out things like making certain versions<00:44:25.640> of<00:44:25.839> IO<00:44:26.119> a<00:44:26.200> little<00:44:26.359> bit<00:44:26.559> faster 00:44:27.390 --> 00:44:27.400 align:start position:0% versions of IO a little bit faster 00:44:27.400 --> 00:44:31.030 align:start position:0% versions of IO a little bit faster making<00:44:28.400> um<00:44:28.760> having<00:44:29.040> NPC<00:44:29.400> FHA<00:44:29.920> be<00:44:30.200> faster 00:44:31.030 --> 00:44:31.040 align:start position:0% making um having NPC FHA be faster 00:44:31.040 --> 00:44:32.790 align:start position:0% making um having NPC FHA be faster things<00:44:31.280> like<00:44:31.520> we've<00:44:31.680> seen<00:44:31.839> like<00:44:32.000> Apple's<00:44:32.359> w- 00:44:32.790 --> 00:44:32.800 align:start position:0% things like we've seen like Apple's w- 00:44:32.800 --> 00:44:35.470 align:start position:0% things like we've seen like Apple's w- they<00:44:32.960> just<00:44:33.079> released<00:44:33.520> like<00:44:33.680> a<00:44:34.000> ML<00:44:34.319> and<00:44:34.480> FHA 00:44:35.470 --> 00:44:35.480 align:start position:0% they just released like a ML and FHA 00:44:35.480 --> 00:44:36.870 align:start position:0% they just released like a ML and FHA kind<00:44:35.640> of<00:44:35.839> application<00:44:36.280> and<00:44:36.400> I<00:44:36.480> think<00:44:36.599> seeing 00:44:36.870 --> 00:44:36.880 align:start position:0% kind of application and I think seeing 00:44:36.880 --> 00:44:38.950 align:start position:0% kind of application and I think seeing more<00:44:37.040> of<00:44:37.280> that<00:44:37.960> um<00:44:38.079> more<00:44:38.240> Enterprises<00:44:38.800> get 00:44:38.950 --> 00:44:38.960 align:start position:0% more of that um more Enterprises get 00:44:38.960 --> 00:44:40.950 align:start position:0% more of that um more Enterprises get into<00:44:39.359> these<00:44:39.559> privacy<00:44:39.920> protocols<00:44:40.359> make<00:44:40.520> them 00:44:40.950 --> 00:44:40.960 align:start position:0% into these privacy protocols make them 00:44:40.960 --> 00:44:44.030 align:start position:0% into these privacy protocols make them faster<00:44:42.079> um 00:44:44.030 --> 00:44:44.040 align:start position:0% faster um 00:44:44.040 --> 00:44:48.390 align:start position:0% faster um yeah<00:44:45.040> so<00:44:45.280> for<00:44:45.440> me<00:44:45.760> I<00:44:46.119> guess<00:44:47.119> um<00:44:47.880> yeah<00:44:48.119> like 00:44:48.390 --> 00:44:48.400 align:start position:0% yeah so for me I guess um yeah like 00:44:48.400 --> 00:44:50.470 align:start position:0% yeah so for me I guess um yeah like making<00:44:48.720> things<00:44:49.000> faster<00:44:49.760> like<00:44:49.880> harder<00:44:50.200> better 00:44:50.470 --> 00:44:50.480 align:start position:0% making things faster like harder better 00:44:50.480 --> 00:44:53.109 align:start position:0% making things faster like harder better faster<00:44:50.880> stronger<00:44:51.280> is<00:44:51.440> always<00:44:51.720> the<00:44:51.880> goal<00:44:52.640> but<00:44:53.040> I 00:44:53.109 --> 00:44:53.119 align:start position:0% faster stronger is always the goal but I 00:44:53.119 --> 00:44:55.190 align:start position:0% faster stronger is always the goal but I think<00:44:53.599> I<00:44:53.680> would<00:44:53.839> love<00:44:54.040> to<00:44:54.160> see<00:44:54.480> more<00:44:54.839> like<00:44:55.079> what 00:44:55.190 --> 00:44:55.200 align:start position:0% think I would love to see more like what 00:44:55.200 --> 00:44:58.150 align:start position:0% think I would love to see more like what you<00:44:55.319> are<00:44:55.520> doing<00:44:55.960> actually<00:44:56.200> and<00:44:56.359> I<00:44:56.480> think<00:44:56.920> um<00:44:57.200> um 00:44:58.150 --> 00:44:58.160 align:start position:0% you are doing actually and I think um um 00:44:58.160 --> 00:45:00.390 align:start position:0% you are doing actually and I think um um there's<00:44:58.400> not<00:44:58.640> so<00:44:58.880> much<00:44:59.160> incentive<00:44:59.960> to 00:45:00.390 --> 00:45:00.400 align:start position:0% there's not so much incentive to 00:45:00.400 --> 00:45:02.710 align:start position:0% there's not so much incentive to actually<00:45:00.880> play<00:45:01.280> with<00:45:01.599> these<00:45:01.839> tools<00:45:02.440> and<00:45:02.559> I 00:45:02.710 --> 00:45:02.720 align:start position:0% actually play with these tools and I 00:45:02.720 --> 00:45:05.030 align:start position:0% actually play with these tools and I think<00:45:03.280> the<00:45:03.520> gain<00:45:04.000> from<00:45:04.319> playing<00:45:04.680> with<00:45:04.839> these 00:45:05.030 --> 00:45:05.040 align:start position:0% think the gain from playing with these 00:45:05.040 --> 00:45:06.630 align:start position:0% think the gain from playing with these tools<00:45:05.319> and<00:45:05.480> like<00:45:05.599> onboarding<00:45:06.119> users<00:45:06.480> and 00:45:06.630 --> 00:45:06.640 align:start position:0% tools and like onboarding users and 00:45:06.640 --> 00:45:09.190 align:start position:0% tools and like onboarding users and educating<00:45:07.119> them<00:45:07.319> is<00:45:07.599> huge<00:45:08.400> but<00:45:08.559> somehow 00:45:09.190 --> 00:45:09.200 align:start position:0% educating them is huge but somehow 00:45:09.200 --> 00:45:12.030 align:start position:0% educating them is huge but somehow people<00:45:09.640> don't<00:45:09.880> do<00:45:10.040> it<00:45:10.240> enough<00:45:10.960> and<00:45:11.079> so<00:45:11.480> like 00:45:12.030 --> 00:45:12.040 align:start position:0% people don't do it enough and so like 00:45:12.040 --> 00:45:14.309 align:start position:0% people don't do it enough and so like there<00:45:12.160> are<00:45:12.359> apps<00:45:12.800> like<00:45:13.040> yours<00:45:13.599> like<00:45:13.839> Tonk 00:45:14.309 --> 00:45:14.319 align:start position:0% there are apps like yours like Tonk 00:45:14.319 --> 00:45:17.030 align:start position:0% there are apps like yours like Tonk they're<00:45:14.559> building<00:45:15.000> these<00:45:15.240> you<00:45:15.359> know<00:45:15.640> like<00:45:16.079> uh 00:45:17.030 --> 00:45:17.040 align:start position:0% they're building these you know like uh 00:45:17.040 --> 00:45:19.750 align:start position:0% they're building these you know like uh Salon<00:45:17.680> basically<00:45:18.119> where<00:45:18.599> EAS<00:45:19.040> Speak<00:45:19.359> Easy 00:45:19.750 --> 00:45:19.760 align:start position:0% Salon basically where EAS Speak Easy 00:45:19.760 --> 00:45:21.670 align:start position:0% Salon basically where EAS Speak Easy yeah<00:45:19.960> exactly<00:45:20.400> where<00:45:20.559> you<00:45:20.680> can<00:45:21.280> meet<00:45:21.480> your 00:45:21.670 --> 00:45:21.680 align:start position:0% yeah exactly where you can meet your 00:45:21.680 --> 00:45:23.109 align:start position:0% yeah exactly where you can meet your friends<00:45:22.040> like<00:45:22.200> and<00:45:22.400> have<00:45:22.559> this<00:45:22.760> private 00:45:23.109 --> 00:45:23.119 align:start position:0% friends like and have this private 00:45:23.119 --> 00:45:25.390 align:start position:0% friends like and have this private environment<00:45:23.760> where<00:45:24.040> you<00:45:24.200> can<00:45:24.680> yeah<00:45:25.000> like<00:45:25.200> come 00:45:25.390 --> 00:45:25.400 align:start position:0% environment where you can yeah like come 00:45:25.400 --> 00:45:27.630 align:start position:0% environment where you can yeah like come in<00:45:25.640> if<00:45:25.760> you<00:45:25.839> can<00:45:26.040> prove<00:45:26.319> some<00:45:26.559> stuff<00:45:26.839> and<00:45:27.160> like 00:45:27.630 --> 00:45:27.640 align:start position:0% in if you can prove some stuff and like 00:45:27.640 --> 00:45:30.109 align:start position:0% in if you can prove some stuff and like yeah<00:45:27.880> this<00:45:28.319> sort<00:45:28.559> of<00:45:28.839> transitive<00:45:29.440> trust<00:45:29.839> idea 00:45:30.109 --> 00:45:30.119 align:start position:0% yeah this sort of transitive trust idea 00:45:30.119 --> 00:45:33.270 align:start position:0% yeah this sort of transitive trust idea like<00:45:30.280> all<00:45:30.440> this<00:45:30.559> kind<00:45:30.680> of<00:45:30.839> cool<00:45:31.119> stuff<00:45:32.040> um<00:45:32.960> like 00:45:33.270 --> 00:45:33.280 align:start position:0% like all this kind of cool stuff um like 00:45:33.280 --> 00:45:34.950 align:start position:0% like all this kind of cool stuff um like this<00:45:33.440> for<00:45:33.599> me<00:45:33.800> would<00:45:33.960> be<00:45:34.160> great<00:45:34.480> I'd<00:45:34.680> love<00:45:34.839> to 00:45:34.950 --> 00:45:34.960 align:start position:0% this for me would be great I'd love to 00:45:34.960 --> 00:45:37.109 align:start position:0% this for me would be great I'd love to see<00:45:35.200> this<00:45:35.520> actually<00:45:36.280> happening<00:45:36.720> more<00:45:36.920> and 00:45:37.109 --> 00:45:37.119 align:start position:0% see this actually happening more and 00:45:37.119 --> 00:45:40.030 align:start position:0% see this actually happening more and more<00:45:38.119> yeah<00:45:38.440> I'm<00:45:38.559> super<00:45:38.839> excited<00:45:39.240> about<00:45:39.640> new 00:45:40.030 --> 00:45:40.040 align:start position:0% more yeah I'm super excited about new 00:45:40.040 --> 00:45:43.990 align:start position:0% more yeah I'm super excited about new applications<00:45:41.000> of<00:45:41.280> MPC<00:45:42.200> so<00:45:42.559> specifically<00:45:43.559> this 00:45:43.990 --> 00:45:44.000 align:start position:0% applications of MPC so specifically this 00:45:44.000 --> 00:45:46.750 align:start position:0% applications of MPC so specifically this concept<00:45:44.599> called<00:45:44.960> digital<00:45:45.480> fairmon<00:45:46.480> and<00:45:46.640> the 00:45:46.750 --> 00:45:46.760 align:start position:0% concept called digital fairmon and the 00:45:46.760 --> 00:45:48.950 align:start position:0% concept called digital fairmon and the idea<00:45:47.040> here<00:45:47.160> is<00:45:47.319> that<00:45:47.559> like<00:45:47.920> real<00:45:48.160> fairmon<00:45:48.720> are 00:45:48.950 --> 00:45:48.960 align:start position:0% idea here is that like real fairmon are 00:45:48.960 --> 00:45:50.589 align:start position:0% idea here is that like real fairmon are these<00:45:49.160> chemical<00:45:49.559> biochemical<00:45:50.160> signals<00:45:50.520> that 00:45:50.589 --> 00:45:50.599 align:start position:0% these chemical biochemical signals that 00:45:50.599 --> 00:45:52.030 align:start position:0% these chemical biochemical signals that you<00:45:50.680> send<00:45:51.000> around<00:45:51.240> to<00:45:51.400> find<00:45:51.599> people<00:45:51.839> you're 00:45:52.030 --> 00:45:52.040 align:start position:0% you send around to find people you're 00:45:52.040 --> 00:45:53.910 align:start position:0% you send around to find people you're compatible<00:45:52.559> with<00:45:53.200> and<00:45:53.440> what<00:45:53.559> if<00:45:53.680> we<00:45:53.760> could 00:45:53.910 --> 00:45:53.920 align:start position:0% compatible with and what if we could 00:45:53.920 --> 00:45:56.230 align:start position:0% compatible with and what if we could build<00:45:54.160> the<00:45:54.319> same<00:45:54.559> thing<00:45:54.960> with<00:45:55.400> MPC<00:45:56.079> but 00:45:56.230 --> 00:45:56.240 align:start position:0% build the same thing with MPC but 00:45:56.240 --> 00:45:58.190 align:start position:0% build the same thing with MPC but related<00:45:56.599> to<00:45:57.040> Digital<00:45:57.440> Data<00:45:57.839> digital 00:45:58.190 --> 00:45:58.200 align:start position:0% related to Digital Data digital 00:45:58.200 --> 00:45:59.990 align:start position:0% related to Digital Data digital information<00:45:59.000> so<00:45:59.160> you<00:45:59.280> have<00:45:59.440> these<00:45:59.599> signals 00:45:59.990 --> 00:46:00.000 align:start position:0% information so you have these signals 00:46:00.000 --> 00:46:02.230 align:start position:0% information so you have these signals that<00:46:00.079> you<00:46:00.200> send<00:46:00.520> around<00:46:01.119> and<00:46:01.760> because 00:46:02.230 --> 00:46:02.240 align:start position:0% that you send around and because 00:46:02.240 --> 00:46:03.910 align:start position:0% that you send around and because everything<00:46:02.559> is<00:46:02.760> private<00:46:03.119> everything<00:46:03.440> is<00:46:03.599> safe 00:46:03.910 --> 00:46:03.920 align:start position:0% everything is private everything is safe 00:46:03.920 --> 00:46:05.349 align:start position:0% everything is private everything is safe just<00:46:04.040> like<00:46:04.160> your<00:46:04.280> normal<00:46:04.520> phermones<00:46:04.920> are<00:46:05.240> you 00:46:05.349 --> 00:46:05.359 align:start position:0% just like your normal phermones are you 00:46:05.359 --> 00:46:06.870 align:start position:0% just like your normal phermones are you just<00:46:05.480> get<00:46:05.599> to<00:46:05.760> see<00:46:06.240> like<00:46:06.440> where<00:46:06.640> your 00:46:06.870 --> 00:46:06.880 align:start position:0% just get to see like where your 00:46:06.880 --> 00:46:08.910 align:start position:0% just get to see like where your compatibility<00:46:07.599> is<00:46:08.160> you<00:46:08.280> get<00:46:08.359> to<00:46:08.480> see<00:46:08.680> who<00:46:08.800> you 00:46:08.910 --> 00:46:08.920 align:start position:0% compatibility is you get to see who you 00:46:08.920 --> 00:46:10.710 align:start position:0% compatibility is you get to see who you match<00:46:09.240> with<00:46:09.440> who<00:46:09.599> you<00:46:09.720> might<00:46:10.119> be<00:46:10.240> in<00:46:10.359> a<00:46:10.480> group 00:46:10.710 --> 00:46:10.720 align:start position:0% match with who you might be in a group 00:46:10.720 --> 00:46:12.109 align:start position:0% match with who you might be in a group with<00:46:10.920> who<00:46:11.040> you<00:46:11.119> might<00:46:11.280> be<00:46:11.359> able<00:46:11.520> to<00:46:11.640> do<00:46:11.839> stuff 00:46:12.109 --> 00:46:12.119 align:start position:0% with who you might be able to do stuff 00:46:12.119 --> 00:46:14.470 align:start position:0% with who you might be able to do stuff with<00:46:12.680> um<00:46:12.839> and<00:46:12.960> it<00:46:13.079> just<00:46:13.240> happens<00:46:13.599> naturally 00:46:14.470 --> 00:46:14.480 align:start position:0% with um and it just happens naturally 00:46:14.480 --> 00:46:16.109 align:start position:0% with um and it just happens naturally and<00:46:14.559> so<00:46:14.760> one<00:46:14.920> way<00:46:15.119> we<00:46:15.200> can<00:46:15.400> actually<00:46:15.640> implement 00:46:16.109 --> 00:46:16.119 align:start position:0% and so one way we can actually implement 00:46:16.119 --> 00:46:18.510 align:start position:0% and so one way we can actually implement this<00:46:16.440> is<00:46:16.760> through<00:46:17.000> a<00:46:17.160> new<00:46:17.440> scheme<00:46:18.119> uh<00:46:18.200> we<00:46:18.359> came 00:46:18.510 --> 00:46:18.520 align:start position:0% this is through a new scheme uh we came 00:46:18.520 --> 00:46:20.990 align:start position:0% this is through a new scheme uh we came up<00:46:18.680> with<00:46:18.839> called<00:46:19.040> Trinity<00:46:19.960> and<00:46:20.119> Trinity<00:46:20.760> is 00:46:20.990 --> 00:46:21.000 align:start position:0% up with called Trinity and Trinity is 00:46:21.000 --> 00:46:22.230 align:start position:0% up with called Trinity and Trinity is called<00:46:21.240> Trinity<00:46:21.760> because<00:46:21.960> it's<00:46:22.079> a 00:46:22.230 --> 00:46:22.240 align:start position:0% called Trinity because it's a 00:46:22.240 --> 00:46:24.190 align:start position:0% called Trinity because it's a combination<00:46:22.800> of<00:46:23.079> three<00:46:23.319> schemes 00:46:24.190 --> 00:46:24.200 align:start position:0% combination of three schemes 00:46:24.200 --> 00:46:26.950 align:start position:0% combination of three schemes specifically<00:46:24.920> kzg<00:46:25.400> witness<00:46:25.760> encryption<00:46:26.760> uh 00:46:26.950 --> 00:46:26.960 align:start position:0% specifically kzg witness encryption uh 00:46:26.960 --> 00:46:29.589 align:start position:0% specifically kzg witness encryption uh garbled<00:46:27.319> circuits<00:46:27.920> and<00:46:28.240> plunk<00:46:29.240> uh<00:46:29.319> so<00:46:29.480> the 00:46:29.589 --> 00:46:29.599 align:start position:0% garbled circuits and plunk uh so the 00:46:29.599 --> 00:46:31.030 align:start position:0% garbled circuits and plunk uh so the rough<00:46:29.800> setup<00:46:30.119> here<00:46:30.280> is<00:46:30.400> that<00:46:30.559> you<00:46:30.720> have<00:46:30.880> your 00:46:31.030 --> 00:46:31.040 align:start position:0% rough setup here is that you have your 00:46:31.040 --> 00:46:33.349 align:start position:0% rough setup here is that you have your own<00:46:31.520> private<00:46:31.880> data<00:46:32.480> and<00:46:32.599> you<00:46:32.720> just<00:46:32.920> upload<00:46:33.240> a 00:46:33.349 --> 00:46:33.359 align:start position:0% own private data and you just upload a 00:46:33.359 --> 00:46:35.870 align:start position:0% own private data and you just upload a kzg<00:46:33.800> commitment<00:46:34.200> of<00:46:34.359> this<00:46:34.960> into<00:46:35.200> the<00:46:35.359> cloud<00:46:35.720> or 00:46:35.870 --> 00:46:35.880 align:start position:0% kzg commitment of this into the cloud or 00:46:35.880 --> 00:46:37.670 align:start position:0% kzg commitment of this into the cloud or wherever<00:46:36.599> and<00:46:36.760> like<00:46:36.920> people<00:46:37.160> can<00:46:37.280> just<00:46:37.440> start 00:46:37.670 --> 00:46:37.680 align:start position:0% wherever and like people can just start 00:46:37.680 --> 00:46:39.390 align:start position:0% wherever and like people can just start asking<00:46:37.960> you<00:46:38.200> questions<00:46:38.640> people<00:46:39.040> can<00:46:39.200> start 00:46:39.390 --> 00:46:39.400 align:start position:0% asking you questions people can start 00:46:39.400 --> 00:46:41.109 align:start position:0% asking you questions people can start making<00:46:39.800> private<00:46:40.119> queries<00:46:40.559> based<00:46:40.800> on<00:46:40.960> this 00:46:41.109 --> 00:46:41.119 align:start position:0% making private queries based on this 00:46:41.119 --> 00:46:44.150 align:start position:0% making private queries based on this data<00:46:41.800> right<00:46:42.079> and<00:46:42.480> essentially<00:46:43.160> like<00:46:43.559> you<00:46:43.800> only 00:46:44.150 --> 00:46:44.160 align:start position:0% data right and essentially like you only 00:46:44.160 --> 00:46:46.589 align:start position:0% data right and essentially like you only need<00:46:44.359> to<00:46:44.559> respond<00:46:44.880> to<00:46:45.040> these<00:46:45.200> queries<00:46:46.200> if<00:46:46.359> you 00:46:46.589 --> 00:46:46.599 align:start position:0% need to respond to these queries if you 00:46:46.599 --> 00:46:48.950 align:start position:0% need to respond to these queries if you actually<00:46:46.920> meet<00:46:47.240> those<00:46:47.480> criteria<00:46:48.319> like<00:46:48.559> these 00:46:48.950 --> 00:46:48.960 align:start position:0% actually meet those criteria like these 00:46:48.960 --> 00:46:50.790 align:start position:0% actually meet those criteria like these these<00:46:49.119> commitments<00:46:49.640> are<00:46:49.920> like<00:46:50.040> fairmon<00:46:50.640> from 00:46:50.790 --> 00:46:50.800 align:start position:0% these commitments are like fairmon from 00:46:50.800 --> 00:46:52.549 align:start position:0% these commitments are like fairmon from your<00:46:51.079> data<00:46:51.599> they're<00:46:51.839> like<00:46:52.040> hiding 00:46:52.549 --> 00:46:52.559 align:start position:0% your data they're like hiding 00:46:52.559 --> 00:46:55.109 align:start position:0% your data they're like hiding commitments<00:46:53.040> to<00:46:53.280> your<00:46:53.520> data<00:46:54.400> um<00:46:54.640> and<00:46:54.800> you<00:46:54.920> can 00:46:55.109 --> 00:46:55.119 align:start position:0% commitments to your data um and you can 00:46:55.119 --> 00:46:56.510 align:start position:0% commitments to your data um and you can just<00:46:55.319> like<00:46:55.520> naturally<00:46:55.920> have<00:46:56.079> other<00:46:56.280> people 00:46:56.510 --> 00:46:56.520 align:start position:0% just like naturally have other people 00:46:56.520 --> 00:46:58.109 align:start position:0% just like naturally have other people around<00:46:56.960> you<00:46:57.079> ask<00:46:57.280> questions<00:46:57.559> and<00:46:57.720> say<00:46:57.960> hey 00:46:58.109 --> 00:46:58.119 align:start position:0% around you ask questions and say hey 00:46:58.119 --> 00:46:59.870 align:start position:0% around you ask questions and say hey like<00:46:58.280> am<00:46:58.359> I<00:46:58.559> compatible<00:46:59.200> with<00:46:59.319> this<00:46:59.520> person 00:46:59.870 --> 00:46:59.880 align:start position:0% like am I compatible with this person 00:46:59.880 --> 00:47:02.030 align:start position:0% like am I compatible with this person like<00:47:00.599> am<00:47:00.680> I<00:47:00.839> able<00:47:01.079> to<00:47:01.240> do<00:47:01.400> something<00:47:01.680> with<00:47:01.839> this 00:47:02.030 --> 00:47:02.040 align:start position:0% like am I able to do something with this 00:47:02.040 --> 00:47:04.030 align:start position:0% like am I able to do something with this person<00:47:02.760> uh<00:47:02.880> and<00:47:03.000> you<00:47:03.079> can<00:47:03.280> just<00:47:03.599> discover<00:47:03.880> that 00:47:04.030 --> 00:47:04.040 align:start position:0% person uh and you can just discover that 00:47:04.040 --> 00:47:06.470 align:start position:0% person uh and you can just discover that and<00:47:04.160> it's<00:47:04.280> only<00:47:04.520> possible<00:47:05.000> because<00:47:05.359> MPC<00:47:06.359> uh 00:47:06.470 --> 00:47:06.480 align:start position:0% and it's only possible because MPC uh 00:47:06.480 --> 00:47:09.109 align:start position:0% and it's only possible because MPC uh enables<00:47:06.960> this<00:47:07.200> privacy<00:47:07.640> and 00:47:09.109 --> 00:47:09.119 align:start position:0% enables this privacy and 00:47:09.119 --> 00:47:11.870 align:start position:0% enables this privacy and safety<00:47:10.119> yeah<00:47:10.440> I<00:47:10.599> I<00:47:10.720> think<00:47:11.119> I'm<00:47:11.280> really<00:47:11.520> excited 00:47:11.870 --> 00:47:11.880 align:start position:0% safety yeah I I think I'm really excited 00:47:11.880 --> 00:47:15.069 align:start position:0% safety yeah I I think I'm really excited about<00:47:12.319> like<00:47:13.280> more<00:47:13.680> practical<00:47:14.319> applications 00:47:15.069 --> 00:47:15.079 align:start position:0% about like more practical applications 00:47:15.079 --> 00:47:18.190 align:start position:0% about like more practical applications that<00:47:15.720> like<00:47:15.880> use<00:47:16.880> these<00:47:17.079> schemes<00:47:17.720> that<00:47:17.800> are 00:47:18.190 --> 00:47:18.200 align:start position:0% that like use these schemes that are 00:47:18.200 --> 00:47:21.750 align:start position:0% that like use these schemes that are like<00:47:19.119> um<00:47:19.280> being<00:47:20.160> like<00:47:20.880> more<00:47:21.000> and<00:47:21.160> more<00:47:21.400> robust 00:47:21.750 --> 00:47:21.760 align:start position:0% like um being like more and more robust 00:47:21.760 --> 00:47:24.190 align:start position:0% like um being like more and more robust and<00:47:21.920> secure<00:47:22.359> over<00:47:22.960> I<00:47:23.040> guess<00:47:23.200> the<00:47:23.359> next<00:47:23.599> year<00:47:24.119> I 00:47:24.190 --> 00:47:24.200 align:start position:0% and secure over I guess the next year I 00:47:24.200 --> 00:47:26.109 align:start position:0% and secure over I guess the next year I think<00:47:24.359> a<00:47:24.440> lot<00:47:24.559> of<00:47:24.760> protocols<00:47:25.559> I<00:47:25.640> think<00:47:25.800> ZK 00:47:26.109 --> 00:47:26.119 align:start position:0% think a lot of protocols I think ZK 00:47:26.119 --> 00:47:28.430 align:start position:0% think a lot of protocols I think ZK email<00:47:26.400> went<00:47:26.520> through<00:47:27.079> it<00:47:27.720> um<00:47:27.920> and<00:47:28.079> a<00:47:28.200> lot<00:47:28.319> of 00:47:28.430 --> 00:47:28.440 align:start position:0% email went through it um and a lot of 00:47:28.440 --> 00:47:30.549 align:start position:0% email went through it um and a lot of these<00:47:28.640> other<00:47:29.160> like<00:47:29.319> protocols<00:47:29.760> such<00:47:29.880> as<00:47:30.000> tlsn 00:47:30.549 --> 00:47:30.559 align:start position:0% these other like protocols such as tlsn 00:47:30.559 --> 00:47:32.950 align:start position:0% these other like protocols such as tlsn will<00:47:30.760> be<00:47:31.240> I<00:47:31.400> guess<00:47:31.599> in<00:47:31.680> the<00:47:31.839> next<00:47:32.040> year<00:47:32.200> or<00:47:32.319> two 00:47:32.950 --> 00:47:32.960 align:start position:0% will be I guess in the next year or two 00:47:32.960 --> 00:47:35.510 align:start position:0% will be I guess in the next year or two and<00:47:33.079> I<00:47:33.200> think<00:47:34.079> uh<00:47:34.280> as<00:47:34.520> these<00:47:34.720> protocols<00:47:35.200> become 00:47:35.510 --> 00:47:35.520 align:start position:0% and I think uh as these protocols become 00:47:35.520 --> 00:47:38.230 align:start position:0% and I think uh as these protocols become faster<00:47:36.200> and<00:47:36.359> easier<00:47:36.680> to<00:47:36.880> use<00:47:37.520> I<00:47:37.640> think<00:47:37.760> we'll 00:47:38.230 --> 00:47:38.240 align:start position:0% faster and easier to use I think we'll 00:47:38.240 --> 00:47:40.589 align:start position:0% faster and easier to use I think we'll see<00:47:38.640> more<00:47:38.920> and<00:47:39.079> more<00:47:39.319> practical<00:47:39.720> applications 00:47:40.589 --> 00:47:40.599 align:start position:0% see more and more practical applications 00:47:40.599 --> 00:47:43.710 align:start position:0% see more and more practical applications like<00:47:40.760> ours<00:47:41.720> um<00:47:42.119> and<00:47:42.680> yeah<00:47:43.040> like<00:47:43.400> stuff<00:47:43.640> that 00:47:43.710 --> 00:47:43.720 align:start position:0% like ours um and yeah like stuff that 00:47:43.720 --> 00:47:46.630 align:start position:0% like ours um and yeah like stuff that you<00:47:43.839> can<00:47:43.960> do<00:47:44.119> with<00:47:44.280> web2<00:47:44.680> data<00:47:45.280> uh<00:47:45.400> come<00:47:45.640> online 00:47:46.630 --> 00:47:46.640 align:start position:0% you can do with web2 data uh come online 00:47:46.640 --> 00:47:48.630 align:start position:0% you can do with web2 data uh come online and<00:47:47.319> yeah<00:47:47.520> I<00:47:47.599> think<00:47:47.800> I'm<00:47:47.920> just<00:47:48.119> really<00:47:48.319> excited 00:47:48.630 --> 00:47:48.640 align:start position:0% and yeah I think I'm just really excited 00:47:48.640 --> 00:47:51.910 align:start position:0% and yeah I think I'm just really excited to<00:47:48.839> see<00:47:49.359> like<00:47:49.839> combination<00:47:50.599> using<00:47:51.160> schemes 00:47:51.910 --> 00:47:51.920 align:start position:0% to see like combination using schemes 00:47:51.920 --> 00:47:53.390 align:start position:0% to see like combination using schemes these<00:47:52.319> these<00:47:52.480> different<00:47:52.720> schemes<00:47:53.240> in 00:47:53.390 --> 00:47:53.400 align:start position:0% these these different schemes in 00:47:53.400 --> 00:47:55.190 align:start position:0% these these different schemes in combination<00:47:53.839> with<00:47:54.000> each<00:47:54.119> other<00:47:54.480> in 00:47:55.190 --> 00:47:55.200 align:start position:0% combination with each other in 00:47:55.200 --> 00:47:58.790 align:start position:0% combination with each other in production<00:47:56.200> yeah<00:47:56.440> very<00:47:56.599> cool<00:47:56.880> cool<00:47:57.760> um<00:47:58.280> so<00:47:58.680> I 00:47:58.790 --> 00:47:58.800 align:start position:0% production yeah very cool cool um so I 00:47:58.800 --> 00:48:01.150 align:start position:0% production yeah very cool cool um so I think<00:47:59.160> now<00:47:59.400> we're<00:47:59.640> supposed<00:47:59.960> to<00:48:00.119> open<00:48:00.480> to 00:48:01.150 --> 00:48:01.160 align:start position:0% think now we're supposed to open to 00:48:01.160 --> 00:48:02.230 align:start position:0% think now we're supposed to open to audience 00:48:02.230 --> 00:48:02.240 align:start position:0% audience 00:48:02.240 --> 00:48:07.829 align:start position:0% audience questions<00:48:03.240> I<00:48:03.400> still<00:48:03.599> don't<00:48:03.839> see 00:48:07.829 --> 00:48:07.839 align:start position:0% 00:48:07.839 --> 00:48:11.390 align:start position:0% them<00:48:08.839> oh<00:48:09.319> there<00:48:09.480> they 00:48:11.390 --> 00:48:11.400 align:start position:0% them oh there they 00:48:11.400 --> 00:48:14.349 align:start position:0% them oh there they are<00:48:12.400> so<00:48:13.000> we'll<00:48:13.400> start<00:48:13.680> with<00:48:13.839> the<00:48:14.000> most 00:48:14.349 --> 00:48:14.359 align:start position:0% are so we'll start with the most 00:48:14.359 --> 00:48:17.710 align:start position:0% are so we'll start with the most uploaded<00:48:15.200> which<00:48:15.520> is<00:48:16.520> um<00:48:16.920> yeah<00:48:17.160> what's<00:48:17.440> the 00:48:17.710 --> 00:48:17.720 align:start position:0% uploaded which is um yeah what's the 00:48:17.720 --> 00:48:20.910 align:start position:0% uploaded which is um yeah what's the path<00:48:18.040> forward<00:48:18.520> for<00:48:18.720> mobile<00:48:19.720> do<00:48:19.880> we<00:48:20.040> need<00:48:20.280> a<00:48:20.440> new 00:48:20.910 --> 00:48:20.920 align:start position:0% path forward for mobile do we need a new 00:48:20.920 --> 00:48:24.309 align:start position:0% path forward for mobile do we need a new browser<00:48:21.920> who<00:48:22.119> will<00:48:22.280> fund 00:48:24.309 --> 00:48:24.319 align:start position:0% browser who will fund 00:48:24.319 --> 00:48:28.109 align:start position:0% browser who will fund it<00:48:25.319> I<00:48:25.480> guess<00:48:25.760> like<00:48:26.040> we<00:48:26.280> already<00:48:26.839> addressed<00:48:27.760> um 00:48:28.109 --> 00:48:28.119 align:start position:0% it I guess like we already addressed um 00:48:28.119 --> 00:48:30.870 align:start position:0% it I guess like we already addressed um sort<00:48:28.359> of<00:48:28.880> Outsourcing<00:48:29.880> heavy<00:48:30.200> computations 00:48:30.870 --> 00:48:30.880 align:start position:0% sort of Outsourcing heavy computations 00:48:30.880 --> 00:48:34.670 align:start position:0% sort of Outsourcing heavy computations from<00:48:31.119> mobile<00:48:31.920> whereas<00:48:32.440> this<00:48:32.720> question<00:48:33.480> is<00:48:34.400> I'm 00:48:34.670 --> 00:48:34.680 align:start position:0% from mobile whereas this question is I'm 00:48:34.680 --> 00:48:37.750 align:start position:0% from mobile whereas this question is I'm I'm<00:48:34.920> interpreting<00:48:35.520> it<00:48:35.720> more<00:48:35.960> of<00:48:36.319> like<00:48:37.119> um<00:48:37.559> sort 00:48:37.750 --> 00:48:37.760 align:start position:0% I'm interpreting it more of like um sort 00:48:37.760 --> 00:48:40.549 align:start position:0% I'm interpreting it more of like um sort of<00:48:38.079> the<00:48:38.680> current<00:48:39.119> standards<00:48:39.640> of<00:48:39.800> mobile<00:48:40.280> like 00:48:40.549 --> 00:48:40.559 align:start position:0% of the current standards of mobile like 00:48:40.559 --> 00:48:42.750 align:start position:0% of the current standards of mobile like you<00:48:40.720> mentioned<00:48:41.160> there's<00:48:41.440> taets<00:48:42.000> now<00:48:42.520> but 00:48:42.750 --> 00:48:42.760 align:start position:0% you mentioned there's taets now but 00:48:42.760 --> 00:48:46.589 align:start position:0% you mentioned there's taets now but there's<00:48:43.400> lots<00:48:43.640> of<00:48:44.359> um<00:48:45.359> sort<00:48:45.640> of<00:48:45.880> restrictions 00:48:46.589 --> 00:48:46.599 align:start position:0% there's lots of um sort of restrictions 00:48:46.599 --> 00:48:50.190 align:start position:0% there's lots of um sort of restrictions on<00:48:46.800> mobile<00:48:47.200> apps<00:48:47.680> that<00:48:47.839> make<00:48:48.000> it<00:48:48.240> hard<00:48:48.520> to<00:48:49.280> say 00:48:50.190 --> 00:48:50.200 align:start position:0% on mobile apps that make it hard to say 00:48:50.200 --> 00:48:53.470 align:start position:0% on mobile apps that make it hard to say directly<00:48:51.119> interface<00:48:51.760> into<00:48:52.200> like<00:48:52.359> TLS<00:48:52.799> notary 00:48:53.470 --> 00:48:53.480 align:start position:0% directly interface into like TLS notary 00:48:53.480 --> 00:48:57.430 align:start position:0% directly interface into like TLS notary let's<00:48:53.720> say<00:48:54.720> um<00:48:55.280> so<00:48:56.280> like 00:48:57.430 --> 00:48:57.440 align:start position:0% let's say um so like 00:48:57.440 --> 00:49:00.069 align:start position:0% let's say um so like how<00:48:57.680> do<00:48:57.880> we<00:48:58.160> deal<00:48:58.720> with<00:48:58.960> these<00:48:59.280> standards<00:48:59.960> that 00:49:00.069 --> 00:49:00.079 align:start position:0% how do we deal with these standards that 00:49:00.079 --> 00:49:03.870 align:start position:0% how do we deal with these standards that are<00:49:00.920> um<00:49:01.920> incompatible<00:49:02.920> with<00:49:03.040> The<00:49:03.240> Primitives 00:49:03.870 --> 00:49:03.880 align:start position:0% are um incompatible with The Primitives 00:49:03.880 --> 00:49:06.789 align:start position:0% are um incompatible with The Primitives we<00:49:04.000> need<00:49:05.000> do<00:49:05.200> we<00:49:05.839> yeah<00:49:06.000> how<00:49:06.119> do<00:49:06.280> we<00:49:06.400> deal<00:49:06.640> with 00:49:06.789 --> 00:49:06.799 align:start position:0% we need do we yeah how do we deal with 00:49:06.799 --> 00:49:08.829 align:start position:0% we need do we yeah how do we deal with them<00:49:07.079> do<00:49:07.240> we<00:49:07.559> like<00:49:07.839> start<00:49:08.160> from<00:49:08.359> scratch<00:49:08.720> with 00:49:08.829 --> 00:49:08.839 align:start position:0% them do we like start from scratch with 00:49:08.839 --> 00:49:13.750 align:start position:0% them do we like start from scratch with a<00:49:09.040> new<00:49:09.359> browser<00:49:10.359> what<00:49:10.520> what<00:49:10.599> do<00:49:10.760> you<00:49:10.960> guys 00:49:13.750 --> 00:49:13.760 align:start position:0% 00:49:13.760 --> 00:49:16.710 align:start position:0% think<00:49:14.760> for<00:49:15.040> mobile<00:49:15.440> specifically<00:49:16.119> like<00:49:16.599> I 00:49:16.710 --> 00:49:16.720 align:start position:0% think for mobile specifically like I 00:49:16.720 --> 00:49:18.430 align:start position:0% think for mobile specifically like I feel<00:49:16.920> like<00:49:17.160> we<00:49:17.319> just<00:49:17.559> need<00:49:17.960> more<00:49:18.200> people 00:49:18.430 --> 00:49:18.440 align:start position:0% feel like we just need more people 00:49:18.440 --> 00:49:19.789 align:start position:0% feel like we just need more people building<00:49:18.799> mobile<00:49:19.079> apps<00:49:19.280> and<00:49:19.480> just 00:49:19.789 --> 00:49:19.799 align:start position:0% building mobile apps and just 00:49:19.799 --> 00:49:22.150 align:start position:0% building mobile apps and just experimenting<00:49:20.799> like<00:49:21.280> that's<00:49:21.480> basically<00:49:21.880> it 00:49:22.150 --> 00:49:22.160 align:start position:0% experimenting like that's basically it 00:49:22.160 --> 00:49:25.270 align:start position:0% experimenting like that's basically it like<00:49:22.640> there's<00:49:23.440> how<00:49:23.559> many<00:49:24.440> apps<00:49:24.760> exist<00:49:25.040> today 00:49:25.270 --> 00:49:25.280 align:start position:0% like there's how many apps exist today 00:49:25.280 --> 00:49:27.670 align:start position:0% like there's how many apps exist today on<00:49:25.400> the<00:49:25.559> App<00:49:25.720> Store<00:49:26.040> that<00:49:26.160> are<00:49:26.400> like<00:49:27.200> uh<00:49:27.359> mobile 00:49:27.670 --> 00:49:27.680 align:start position:0% on the App Store that are like uh mobile 00:49:27.680 --> 00:49:29.670 align:start position:0% on the App Store that are like uh mobile apps<00:49:28.079> with<00:49:28.400> programmable<00:49:28.960> cryptography 00:49:29.670 --> 00:49:29.680 align:start position:0% apps with programmable cryptography 00:49:29.680 --> 00:49:32.589 align:start position:0% apps with programmable cryptography running<00:49:30.000> clients<00:49:30.400> side<00:49:30.920> like<00:49:31.880> I<00:49:32.160> I<00:49:32.240> don't<00:49:32.559> I 00:49:32.589 --> 00:49:32.599 align:start position:0% running clients side like I I don't I 00:49:32.599 --> 00:49:35.789 align:start position:0% running clients side like I I don't I don't<00:49:32.760> know<00:49:33.079> we<00:49:33.240> we<00:49:33.359> don't<00:49:33.559> have<00:49:33.680> one<00:49:34.359> um<00:49:35.280> so<00:49:35.680> I 00:49:35.789 --> 00:49:35.799 align:start position:0% don't know we we don't have one um so I 00:49:35.799 --> 00:49:36.950 align:start position:0% don't know we we don't have one um so I feel<00:49:35.960> like<00:49:36.160> we<00:49:36.280> just<00:49:36.400> need<00:49:36.520> to<00:49:36.640> learn<00:49:36.839> the 00:49:36.950 --> 00:49:36.960 align:start position:0% feel like we just need to learn the 00:49:36.960 --> 00:49:38.430 align:start position:0% feel like we just need to learn the lessons<00:49:37.359> there<00:49:37.640> pretty 00:49:38.430 --> 00:49:38.440 align:start position:0% lessons there pretty 00:49:38.440 --> 00:49:41.710 align:start position:0% lessons there pretty much<00:49:39.440> yeah<00:49:39.559> I<00:49:39.680> agree<00:49:39.920> with<00:49:40.079> that<00:49:40.319> I<00:49:40.440> think<00:49:41.319> we 00:49:41.710 --> 00:49:41.720 align:start position:0% much yeah I agree with that I think we 00:49:41.720 --> 00:49:43.829 align:start position:0% much yeah I agree with that I think we need<00:49:42.720> yeah<00:49:42.880> more<00:49:43.079> Dev<00:49:43.319> tooling<00:49:43.640> more 00:49:43.829 --> 00:49:43.839 align:start position:0% need yeah more Dev tooling more 00:49:43.839 --> 00:49:45.630 align:start position:0% need yeah more Dev tooling more developers<00:49:44.599> uh<00:49:44.720> building<00:49:45.240> these<00:49:45.400> kind<00:49:45.520> of 00:49:45.630 --> 00:49:45.640 align:start position:0% developers uh building these kind of 00:49:45.640 --> 00:49:49.390 align:start position:0% developers uh building these kind of programmable<00:49:46.599> crypto<00:49:47.559> U<00:49:47.680> mobile<00:49:48.079> apps<00:49:49.079> um<00:49:49.280> I 00:49:49.390 --> 00:49:49.400 align:start position:0% programmable crypto U mobile apps um I 00:49:49.400 --> 00:49:51.910 align:start position:0% programmable crypto U mobile apps um I think<00:49:49.640> in<00:49:49.799> particular<00:49:50.520> like<00:49:51.240> there's<00:49:51.680> a<00:49:51.799> lot 00:49:51.910 --> 00:49:51.920 align:start position:0% think in particular like there's a lot 00:49:51.920 --> 00:49:54.950 align:start position:0% think in particular like there's a lot of<00:49:52.119> pain<00:49:52.440> we<00:49:52.640> experienced<00:49:53.359> trying<00:49:53.559> to<00:49:53.720> do<00:49:53.960> this 00:49:54.950 --> 00:49:54.960 align:start position:0% of pain we experienced trying to do this 00:49:54.960 --> 00:49:58.069 align:start position:0% of pain we experienced trying to do this um<00:49:55.319> in<00:49:56.040> like<00:49:56.920> yeah<00:49:57.079> the<00:49:57.280> main<00:49:57.520> requirements 00:49:58.069 --> 00:49:58.079 align:start position:0% um in like yeah the main requirements 00:49:58.079 --> 00:50:00.069 align:start position:0% um in like yeah the main requirements being<00:49:58.319> able<00:49:58.520> to<00:49:58.720> extract<00:49:59.480> like<00:49:59.680> the 00:50:00.069 --> 00:50:00.079 align:start position:0% being able to extract like the 00:50:00.079 --> 00:50:02.470 align:start position:0% being able to extract like the credentials<00:50:01.079> um<00:50:01.280> through<00:50:01.559> like<00:50:01.680> a<00:50:01.799> web<00:50:02.040> view 00:50:02.470 --> 00:50:02.480 align:start position:0% credentials um through like a web view 00:50:02.480 --> 00:50:04.950 align:start position:0% credentials um through like a web view like<00:50:02.680> privately<00:50:03.119> and<00:50:03.240> keep<00:50:03.400> it<00:50:03.559> local<00:50:04.319> and 00:50:04.950 --> 00:50:04.960 align:start position:0% like privately and keep it local and 00:50:04.960 --> 00:50:06.750 align:start position:0% like privately and keep it local and apple<00:50:05.280> just<00:50:05.400> doesn't<00:50:05.720> give<00:50:05.839> you<00:50:06.240> or<00:50:06.440> react 00:50:06.750 --> 00:50:06.760 align:start position:0% apple just doesn't give you or react 00:50:06.760 --> 00:50:08.349 align:start position:0% apple just doesn't give you or react native<00:50:07.119> or<00:50:07.280> any<00:50:07.400> of<00:50:07.520> the<00:50:07.640> mobile<00:50:07.880> Frameworks 00:50:08.349 --> 00:50:08.359 align:start position:0% native or any of the mobile Frameworks 00:50:08.359 --> 00:50:09.750 align:start position:0% native or any of the mobile Frameworks just<00:50:08.520> don't<00:50:09.079> they<00:50:09.200> don't<00:50:09.359> give<00:50:09.480> you<00:50:09.640> that 00:50:09.750 --> 00:50:09.760 align:start position:0% just don't they don't give you that 00:50:09.760 --> 00:50:12.710 align:start position:0% just don't they don't give you that tooling<00:50:10.200> right<00:50:10.359> now<00:50:10.680> so<00:50:10.839> you<00:50:10.920> have<00:50:11.440> to<00:50:12.440> be 00:50:12.710 --> 00:50:12.720 align:start position:0% tooling right now so you have to be 00:50:12.720 --> 00:50:16.069 align:start position:0% tooling right now so you have to be pretty<00:50:13.000> hacky<00:50:13.839> um<00:50:14.720> uh<00:50:15.359> when<00:50:15.480> you're 00:50:16.069 --> 00:50:16.079 align:start position:0% pretty hacky um uh when you're 00:50:16.079 --> 00:50:18.150 align:start position:0% pretty hacky um uh when you're developing<00:50:17.079> I<00:50:17.160> think<00:50:17.280> in<00:50:17.359> the<00:50:17.480> mobile<00:50:17.760> browser 00:50:18.150 --> 00:50:18.160 align:start position:0% developing I think in the mobile browser 00:50:18.160 --> 00:50:20.990 align:start position:0% developing I think in the mobile browser side<00:50:18.400> one<00:50:18.559> thing<00:50:18.760> we<00:50:19.000> really<00:50:19.240> want<00:50:19.839> is<00:50:20.839> uh 00:50:20.990 --> 00:50:21.000 align:start position:0% side one thing we really want is uh 00:50:21.000 --> 00:50:22.430 align:start position:0% side one thing we really want is uh there's<00:50:21.160> this<00:50:21.359> kind<00:50:21.480> of<00:50:21.839> vectorization 00:50:22.430 --> 00:50:22.440 align:start position:0% there's this kind of vectorization 00:50:22.440 --> 00:50:24.470 align:start position:0% there's this kind of vectorization called<00:50:22.640> simd<00:50:23.520> and<00:50:23.680> you<00:50:23.799> can<00:50:23.920> only<00:50:24.200> access 00:50:24.470 --> 00:50:24.480 align:start position:0% called simd and you can only access 00:50:24.480 --> 00:50:26.150 align:start position:0% called simd and you can only access 64-bit<00:50:25.040> registers<00:50:25.440> in<00:50:25.520> Mobile<00:50:25.839> right<00:50:25.960> now<00:50:26.079> but 00:50:26.150 --> 00:50:26.160 align:start position:0% 64-bit registers in Mobile right now but 00:50:26.160 --> 00:50:28.230 align:start position:0% 64-bit registers in Mobile right now but if<00:50:26.240> we<00:50:26.319> could<00:50:26.440> access<00:50:26.680> access<00:50:26.920> to<00:50:27.079> full<00:50:27.400> 256bit 00:50:28.230 --> 00:50:28.240 align:start position:0% if we could access access to full 256bit 00:50:28.240 --> 00:50:29.910 align:start position:0% if we could access access to full 256bit registers<00:50:28.680> you<00:50:28.760> could<00:50:28.839> do<00:50:29.000> ZK<00:50:29.319> proofs<00:50:29.599> a<00:50:29.720> lot 00:50:29.910 --> 00:50:29.920 align:start position:0% registers you could do ZK proofs a lot 00:50:29.920 --> 00:50:32.750 align:start position:0% registers you could do ZK proofs a lot faster<00:50:30.839> um<00:50:30.960> similarly<00:50:31.400> web<00:50:31.559> GPU<00:50:32.160> exists<00:50:32.559> on 00:50:32.750 --> 00:50:32.760 align:start position:0% faster um similarly web GPU exists on 00:50:32.760 --> 00:50:35.309 align:start position:0% faster um similarly web GPU exists on most<00:50:33.040> laptops<00:50:33.680> but<00:50:34.160> doesn't<00:50:34.760> isn't<00:50:35.079> doesn't 00:50:35.309 --> 00:50:35.319 align:start position:0% most laptops but doesn't isn't doesn't 00:50:35.319 --> 00:50:36.710 align:start position:0% most laptops but doesn't isn't doesn't have<00:50:35.440> very<00:50:35.559> good<00:50:35.680> support<00:50:35.920> on<00:50:36.079> mobile<00:50:36.440> so<00:50:36.599> I 00:50:36.710 --> 00:50:36.720 align:start position:0% have very good support on mobile so I 00:50:36.720 --> 00:50:38.349 align:start position:0% have very good support on mobile so I think<00:50:37.079> in<00:50:37.200> the<00:50:37.319> short<00:50:37.520> term<00:50:37.720> if<00:50:37.839> browsers<00:50:38.200> can 00:50:38.349 --> 00:50:38.359 align:start position:0% think in the short term if browsers can 00:50:38.359 --> 00:50:39.910 align:start position:0% think in the short term if browsers can ship<00:50:38.640> those<00:50:38.880> that<00:50:39.000> would<00:50:39.119> be<00:50:39.280> super<00:50:39.559> awesome 00:50:39.910 --> 00:50:39.920 align:start position:0% ship those that would be super awesome 00:50:39.920 --> 00:50:41.710 align:start position:0% ship those that would be super awesome and<00:50:40.079> then<00:50:40.720> uh<00:50:40.839> but<00:50:40.960> I<00:50:41.040> do<00:50:41.200> think<00:50:41.359> the<00:50:41.480> large 00:50:41.710 --> 00:50:41.720 align:start position:0% and then uh but I do think the large 00:50:41.720 --> 00:50:42.950 align:start position:0% and then uh but I do think the large browsers<00:50:42.079> will<00:50:42.240> have<00:50:42.359> that<00:50:42.480> eventually<00:50:42.880> in 00:50:42.950 --> 00:50:42.960 align:start position:0% browsers will have that eventually in 00:50:42.960 --> 00:50:44.190 align:start position:0% browsers will have that eventually in Mobile<00:50:43.240> within<00:50:43.400> the<00:50:43.520> next<00:50:43.720> like<00:50:43.839> year<00:50:43.960> or<00:50:44.040> two 00:50:44.190 --> 00:50:44.200 align:start position:0% Mobile within the next like year or two 00:50:44.200 --> 00:50:45.430 align:start position:0% Mobile within the next like year or two and<00:50:44.280> that'll<00:50:44.480> help<00:50:44.680> accelerate<00:50:45.119> a<00:50:45.200> lot<00:50:45.319> of 00:50:45.430 --> 00:50:45.440 align:start position:0% and that'll help accelerate a lot of 00:50:45.440 --> 00:50:48.190 align:start position:0% and that'll help accelerate a lot of these<00:50:45.599> client<00:50:45.960> side 00:50:48.190 --> 00:50:48.200 align:start position:0% 00:50:48.200 --> 00:50:53.430 align:start position:0% proofs<00:50:49.400> cool<00:50:50.760> um<00:50:51.760> okay<00:50:52.200> what<00:50:52.440> are<00:50:52.680> you<00:50:53.200> going 00:50:53.430 --> 00:50:53.440 align:start position:0% proofs cool um okay what are you going 00:50:53.440 --> 00:50:55.470 align:start position:0% proofs cool um okay what are you going to<00:50:53.640> have<00:50:53.880> privacy<00:50:54.359> by<00:50:54.520> default<00:50:54.880> the<00:50:55.040> heart 00:50:55.470 --> 00:50:55.480 align:start position:0% to have privacy by default the heart 00:50:55.480 --> 00:50:58.549 align:start position:0% to have privacy by default the heart path<00:50:56.160> not<00:50:56.359> just<00:50:56.839> privacy<00:50:57.280> by<00:50:57.559> complicated<00:50:58.160> UI 00:50:58.549 --> 00:50:58.559 align:start position:0% path not just privacy by complicated UI 00:50:58.559 --> 00:51:01.910 align:start position:0% path not just privacy by complicated UI and<00:50:58.839> default<00:50:59.240> no<00:50:59.559> privacy<00:51:00.200> and<00:51:00.400> limited 00:51:01.910 --> 00:51:01.920 align:start position:0% and default no privacy and limited 00:51:01.920 --> 00:51:04.990 align:start position:0% and default no privacy and limited security<00:51:02.920> I<00:51:03.200> don't<00:51:04.200> I<00:51:04.280> don't<00:51:04.480> know<00:51:04.680> how<00:51:04.799> to 00:51:04.990 --> 00:51:05.000 align:start position:0% security I don't I don't know how to 00:51:05.000 --> 00:51:07.470 align:start position:0% security I don't I don't know how to parse<00:51:05.359> this<00:51:05.680> do<00:51:05.880> you<00:51:06.040> guys<00:51:06.240> get<00:51:06.400> the<00:51:06.640> question 00:51:07.470 --> 00:51:07.480 align:start position:0% parse this do you guys get the question 00:51:07.480 --> 00:51:09.670 align:start position:0% parse this do you guys get the question um<00:51:08.000> I<00:51:08.119> guess<00:51:08.319> it's<00:51:08.799> kind<00:51:08.920> of<00:51:09.160> responding<00:51:09.559> to 00:51:09.670 --> 00:51:09.680 align:start position:0% um I guess it's kind of responding to 00:51:09.680 --> 00:51:13.309 align:start position:0% um I guess it's kind of responding to something<00:51:09.960> I<00:51:10.119> used<00:51:10.520> that<00:51:11.000> about<00:51:12.000> yeah<00:51:12.480> like 00:51:13.309 --> 00:51:13.319 align:start position:0% something I used that about yeah like 00:51:13.319 --> 00:51:16.349 align:start position:0% something I used that about yeah like it's<00:51:13.760> okay<00:51:14.160> to<00:51:14.400> present<00:51:14.839> an<00:51:15.079> easy<00:51:15.599> path<00:51:16.160> as 00:51:16.349 --> 00:51:16.359 align:start position:0% it's okay to present an easy path as 00:51:16.359 --> 00:51:19.150 align:start position:0% it's okay to present an easy path as long<00:51:16.760> as<00:51:17.040> we<00:51:17.200> make<00:51:17.559> available<00:51:18.359> the<00:51:18.559> fully 00:51:19.150 --> 00:51:19.160 align:start position:0% long as we make available the fully 00:51:19.160 --> 00:51:21.549 align:start position:0% long as we make available the fully private<00:51:19.839> like<00:51:20.079> hard<00:51:20.480> path<00:51:20.880> of<00:51:21.200> like 00:51:21.549 --> 00:51:21.559 align:start position:0% private like hard path of like 00:51:21.559 --> 00:51:26.670 align:start position:0% private like hard path of like completely<00:51:22.040> self-posted<00:51:23.319> approving<00:51:24.319> um 00:51:26.670 --> 00:51:26.680 align:start position:0% completely self-posted approving um 00:51:26.680 --> 00:51:28.950 align:start position:0% completely self-posted approving um question<00:51:27.040> mark<00:51:28.040> maybe<00:51:28.359> one<00:51:28.520> thing<00:51:28.680> I<00:51:28.760> can 00:51:28.950 --> 00:51:28.960 align:start position:0% question mark maybe one thing I can 00:51:28.960 --> 00:51:30.910 align:start position:0% question mark maybe one thing I can clarify<00:51:29.400> on<00:51:29.520> that<00:51:29.680> is<00:51:29.920> I<00:51:30.160> I<00:51:30.240> think<00:51:30.400> it<00:51:30.599> is 00:51:30.910 --> 00:51:30.920 align:start position:0% clarify on that is I I think it is 00:51:30.920 --> 00:51:33.910 align:start position:0% clarify on that is I I think it is possible<00:51:31.319> to<00:51:31.520> have<00:51:32.240> decent<00:51:32.760> UI<00:51:33.319> for<00:51:33.720> things 00:51:33.910 --> 00:51:33.920 align:start position:0% possible to have decent UI for things 00:51:33.920 --> 00:51:35.630 align:start position:0% possible to have decent UI for things that<00:51:34.040> are<00:51:34.200> private<00:51:34.640> like<00:51:34.760> for<00:51:34.920> instance 00:51:35.630 --> 00:51:35.640 align:start position:0% that are private like for instance 00:51:35.640 --> 00:51:38.069 align:start position:0% that are private like for instance dragging<00:51:36.000> and<00:51:36.200> dropping<00:51:36.760> the<00:51:36.920> email 00:51:38.069 --> 00:51:38.079 align:start position:0% dragging and dropping the email 00:51:38.079 --> 00:51:41.349 align:start position:0% dragging and dropping the email on<00:51:39.079> on<00:51:39.319> like<00:51:39.440> a<00:51:39.599> computer<00:51:40.000> is<00:51:40.200> not<00:51:40.839> that<00:51:41.119> bad 00:51:41.349 --> 00:51:41.359 align:start position:0% on on like a computer is not that bad 00:51:41.359 --> 00:51:42.710 align:start position:0% on on like a computer is not that bad like<00:51:41.440> it's<00:51:41.599> still<00:51:41.760> an<00:51:41.880> option<00:51:42.119> in<00:51:42.240> the<00:51:42.319> UI<00:51:42.640> and 00:51:42.710 --> 00:51:42.720 align:start position:0% like it's still an option in the UI and 00:51:42.720 --> 00:51:43.829 align:start position:0% like it's still an option in the UI and it's<00:51:42.839> definitely<00:51:43.119> harder<00:51:43.359> than<00:51:43.440> sounding 00:51:43.829 --> 00:51:43.839 align:start position:0% it's definitely harder than sounding 00:51:43.839 --> 00:51:45.190 align:start position:0% it's definitely harder than sounding with<00:51:43.960> Google<00:51:44.280> but<00:51:44.440> it's<00:51:44.720> it's<00:51:44.880> not<00:51:45.000> like<00:51:45.119> you 00:51:45.190 --> 00:51:45.200 align:start position:0% with Google but it's it's not like you 00:51:45.200 --> 00:51:46.589 align:start position:0% with Google but it's it's not like you have<00:51:45.280> to<00:51:45.440> download<00:51:45.760> something<00:51:46.000> and<00:51:46.119> get<00:51:46.280> clone 00:51:46.589 --> 00:51:46.599 align:start position:0% have to download something and get clone 00:51:46.599 --> 00:51:48.510 align:start position:0% have to download something and get clone and<00:51:46.720> run<00:51:47.000> locally<00:51:47.400> like<00:51:47.520> you<00:51:47.599> can<00:51:47.799> still<00:51:48.319> give 00:51:48.510 --> 00:51:48.520 align:start position:0% and run locally like you can still give 00:51:48.520 --> 00:51:50.750 align:start position:0% and run locally like you can still give option<00:51:48.720> to<00:51:48.880> do<00:51:49.040> that<00:51:49.280> in<00:51:49.400> the<00:51:49.599> UI<00:51:50.240> and<00:51:50.480> we<00:51:50.640> try 00:51:50.750 --> 00:51:50.760 align:start position:0% option to do that in the UI and we try 00:51:50.760 --> 00:51:53.870 align:start position:0% option to do that in the UI and we try to<00:51:50.880> do<00:51:50.960> that<00:51:51.079> where<00:51:51.240> we<00:51:51.359> can<00:51:51.640> and<00:51:51.760> so<00:51:52.599> I<00:51:53.400> I<00:51:53.480> do 00:51:53.870 --> 00:51:53.880 align:start position:0% to do that where we can and so I I do 00:51:53.880 --> 00:51:57.069 align:start position:0% to do that where we can and so I I do think<00:51:54.880> yeah<00:51:55.480> it's<00:51:55.599> a<00:51:55.720> fair<00:51:56.000> point<00:51:56.319> that<00:51:56.720> foring 00:51:57.069 --> 00:51:57.079 align:start position:0% think yeah it's a fair point that foring 00:51:57.079 --> 00:51:58.430 align:start position:0% think yeah it's a fair point that foring people<00:51:57.240> to<00:51:57.319> self<00:51:57.559> host<00:51:57.799> is<00:51:57.920> maybe<00:51:58.160> not<00:51:58.319> the 00:51:58.430 --> 00:51:58.440 align:start position:0% people to self host is maybe not the 00:51:58.440 --> 00:51:59.789 align:start position:0% people to self host is maybe not the best<00:51:58.559> way<00:51:58.680> to<00:51:58.799> offer<00:51:59.000> privacy<00:51:59.359> but<00:51:59.440> I<00:51:59.520> do<00:51:59.680> think 00:51:59.789 --> 00:51:59.799 align:start position:0% best way to offer privacy but I do think 00:51:59.799 --> 00:52:01.870 align:start position:0% best way to offer privacy but I do think you<00:51:59.920> can<00:52:00.079> have<00:52:00.319> buttons<00:52:00.599> in<00:52:00.720> the<00:52:00.839> UI<00:52:01.200> that<00:52:01.720> hey 00:52:01.870 --> 00:52:01.880 align:start position:0% you can have buttons in the UI that hey 00:52:01.880 --> 00:52:03.150 align:start position:0% you can have buttons in the UI that hey this<00:52:01.960> will<00:52:02.079> take<00:52:02.200> a<00:52:02.280> little<00:52:02.440> bit<00:52:02.599> longer<00:52:03.040> this 00:52:03.150 --> 00:52:03.160 align:start position:0% this will take a little bit longer this 00:52:03.160 --> 00:52:05.589 align:start position:0% this will take a little bit longer this might<00:52:03.359> require<00:52:03.640> an<00:52:03.760> extra<00:52:04.040> action<00:52:04.599> but<00:52:05.359> it'll 00:52:05.589 --> 00:52:05.599 align:start position:0% might require an extra action but it'll 00:52:05.599 --> 00:52:08.190 align:start position:0% might require an extra action but it'll be 00:52:08.190 --> 00:52:08.200 align:start position:0% 00:52:08.200 --> 00:52:11.950 align:start position:0% private<00:52:09.200> how<00:52:09.480> far<00:52:09.839> are<00:52:10.119> we<00:52:10.799> from<00:52:11.040> ZK<00:52:11.520> based 00:52:11.950 --> 00:52:11.960 align:start position:0% private how far are we from ZK based 00:52:11.960 --> 00:52:15.470 align:start position:0% private how far are we from ZK based transitive<00:52:12.640> trust<00:52:13.079> graphs<00:52:14.040> of<00:52:14.559> 10K<00:52:15.200> plus 00:52:15.470 --> 00:52:15.480 align:start position:0% transitive trust graphs of 10K plus 00:52:15.480 --> 00:52:17.510 align:start position:0% transitive trust graphs of 10K plus users<00:52:16.000> in 00:52:17.510 --> 00:52:17.520 align:start position:0% users in 00:52:17.520 --> 00:52:21.549 align:start position:0% users in DBS<00:52:18.520> good 00:52:21.549 --> 00:52:21.559 align:start position:0% 00:52:21.559 --> 00:52:25.069 align:start position:0% question<00:52:22.559> I'm<00:52:22.640> looking<00:52:22.880> at<00:52:23.040> you<00:52:23.839> I<00:52:24.000> would<00:52:24.280> say 00:52:25.069 --> 00:52:25.079 align:start position:0% question I'm looking at you I would say 00:52:25.079 --> 00:52:26.829 align:start position:0% question I'm looking at you I would say uh<00:52:25.240> and<00:52:25.400> I<00:52:25.559> probably<00:52:25.880> shouldn't<00:52:26.200> say<00:52:26.599> but<00:52:26.760> I 00:52:26.829 --> 00:52:26.839 align:start position:0% uh and I probably shouldn't say but I 00:52:26.839 --> 00:52:29.870 align:start position:0% uh and I probably shouldn't say but I would<00:52:27.280> probably<00:52:27.680> say<00:52:27.839> it's<00:52:28.040> closer<00:52:28.720> than<00:52:29.720> we 00:52:29.870 --> 00:52:29.880 align:start position:0% would probably say it's closer than we 00:52:29.880 --> 00:52:31.750 align:start position:0% would probably say it's closer than we think<00:52:30.440> I<00:52:30.480> mean<00:52:30.720> it's<00:52:30.839> a<00:52:31.000> hard<00:52:31.319> problem<00:52:31.640> and 00:52:31.750 --> 00:52:31.760 align:start position:0% think I mean it's a hard problem and 00:52:31.760 --> 00:52:33.190 align:start position:0% think I mean it's a hard problem and especially<00:52:32.119> if<00:52:32.200> you<00:52:32.319> want<00:52:32.440> to<00:52:32.559> do<00:52:32.720> this<00:52:32.839> fully 00:52:33.190 --> 00:52:33.200 align:start position:0% especially if you want to do this fully 00:52:33.200 --> 00:52:34.829 align:start position:0% especially if you want to do this fully privately<00:52:33.720> like<00:52:33.880> suppose<00:52:34.160> you<00:52:34.280> want<00:52:34.480> to<00:52:34.640> do 00:52:34.829 --> 00:52:34.839 align:start position:0% privately like suppose you want to do 00:52:34.839 --> 00:52:37.549 align:start position:0% privately like suppose you want to do like<00:52:34.960> a<00:52:35.079> full<00:52:35.319> trust<00:52:35.720> graph<00:52:36.119> in<00:52:36.359> in<00:52:36.520> MPC<00:52:37.440> you 00:52:37.549 --> 00:52:37.559 align:start position:0% like a full trust graph in in MPC you 00:52:37.559 --> 00:52:39.069 align:start position:0% like a full trust graph in in MPC you need<00:52:37.720> to<00:52:37.839> do<00:52:38.079> like<00:52:38.319> essentially<00:52:38.760> a<00:52:38.880> full 00:52:39.069 --> 00:52:39.079 align:start position:0% need to do like essentially a full 00:52:39.079 --> 00:52:40.750 align:start position:0% need to do like essentially a full search<00:52:39.559> because<00:52:39.880> almost<00:52:40.240> everything<00:52:40.599> is 00:52:40.750 --> 00:52:40.760 align:start position:0% search because almost everything is 00:52:40.760 --> 00:52:43.030 align:start position:0% search because almost everything is connected<00:52:41.680> so<00:52:41.880> it's<00:52:42.040> super<00:52:42.319> inefficient<00:52:42.920> and 00:52:43.030 --> 00:52:43.040 align:start position:0% connected so it's super inefficient and 00:52:43.040 --> 00:52:46.109 align:start position:0% connected so it's super inefficient and it's<00:52:43.319> yeah<00:52:43.480> not<00:52:43.760> not<00:52:43.920> so<00:52:44.119> good<00:52:44.760> now<00:52:45.760> but<00:52:46.000> I 00:52:46.109 --> 00:52:46.119 align:start position:0% it's yeah not not so good now but I 00:52:46.119 --> 00:52:48.990 align:start position:0% it's yeah not not so good now but I would<00:52:46.359> imagine<00:52:47.280> that<00:52:47.559> like<00:52:48.079> I<00:52:48.160> mean<00:52:48.319> the<00:52:48.640> speed 00:52:48.990 --> 00:52:49.000 align:start position:0% would imagine that like I mean the speed 00:52:49.000 --> 00:52:51.390 align:start position:0% would imagine that like I mean the speed at<00:52:49.200> which<00:52:49.559> things<00:52:49.760> are<00:52:50.000> improving<00:52:50.520> now<00:52:51.040> I 00:52:51.390 --> 00:52:51.400 align:start position:0% at which things are improving now I 00:52:51.400 --> 00:52:55.069 align:start position:0% at which things are improving now I would<00:52:51.640> say<00:52:52.640> not<00:52:52.920> too<00:52:53.160> far<00:52:53.720> away<00:52:54.720> yeah<00:52:54.839> I<00:52:54.920> think 00:52:55.069 --> 00:52:55.079 align:start position:0% would say not too far away yeah I think 00:52:55.079 --> 00:52:56.670 align:start position:0% would say not too far away yeah I think technically<00:52:55.480> it's<00:52:55.680> possible<00:52:56.040> for<00:52:56.160> me<00:52:56.520> it's 00:52:56.670 --> 00:52:56.680 align:start position:0% technically it's possible for me it's 00:52:56.680 --> 00:53:00.030 align:start position:0% technically it's possible for me it's like<00:52:57.040> uh<00:52:57.960> like<00:52:58.359> how<00:52:58.480> to<00:52:58.720> design<00:52:59.240> this<00:52:59.880> like 00:53:00.030 --> 00:53:00.040 align:start position:0% like uh like how to design this like 00:53:00.040 --> 00:53:01.470 align:start position:0% like uh like how to design this like protocol<00:53:00.520> Wise<00:53:00.760> It's<00:53:00.880> like<00:53:01.040> how<00:53:01.119> do<00:53:01.200> you<00:53:01.319> do 00:53:01.470 --> 00:53:01.480 align:start position:0% protocol Wise It's like how do you do 00:53:01.480 --> 00:53:02.670 align:start position:0% protocol Wise It's like how do you do this<00:53:01.599> the<00:53:01.760> right<00:53:01.920> way<00:53:02.079> where<00:53:02.240> this<00:53:02.359> is<00:53:02.520> like 00:53:02.670 --> 00:53:02.680 align:start position:0% this the right way where this is like 00:53:02.680 --> 00:53:04.750 align:start position:0% this the right way where this is like fair<00:53:02.920> for<00:53:03.160> people<00:53:03.680> there's<00:53:03.839> a<00:53:04.000> lot<00:53:04.119> of<00:53:04.319> like 00:53:04.750 --> 00:53:04.760 align:start position:0% fair for people there's a lot of like 00:53:04.760 --> 00:53:07.470 align:start position:0% fair for people there's a lot of like tricky<00:53:05.319> I<00:53:05.400> don't<00:53:05.520> know<00:53:05.880> moral<00:53:06.880> uh<00:53:07.040> product 00:53:07.470 --> 00:53:07.480 align:start position:0% tricky I don't know moral uh product 00:53:07.480 --> 00:53:10.670 align:start position:0% tricky I don't know moral uh product questions<00:53:07.920> that<00:53:08.040> are<00:53:09.040> uh<00:53:09.119> to<00:53:09.240> be<00:53:09.440> answered 00:53:10.670 --> 00:53:10.680 align:start position:0% questions that are uh to be answered 00:53:10.680 --> 00:53:12.789 align:start position:0% questions that are uh to be answered here 00:53:12.789 --> 00:53:12.799 align:start position:0% here 00:53:12.799 --> 00:53:16.710 align:start position:0% here MH<00:53:13.799> I<00:53:13.880> was<00:53:14.119> also<00:53:14.440> thinking<00:53:14.839> just<00:53:15.040> now<00:53:15.400> that<00:53:15.960> um 00:53:16.710 --> 00:53:16.720 align:start position:0% MH I was also thinking just now that um 00:53:16.720 --> 00:53:20.230 align:start position:0% MH I was also thinking just now that um fhe<00:53:17.640> is<00:53:17.960> one<00:53:18.359> example<00:53:18.960> where<00:53:19.240> like<00:53:19.480> you<00:53:19.720> cannot 00:53:20.230 --> 00:53:20.240 align:start position:0% fhe is one example where like you cannot 00:53:20.240 --> 00:53:22.150 align:start position:0% fhe is one example where like you cannot offload<00:53:20.839> and<00:53:21.000> don't<00:53:21.200> want<00:53:21.359> to<00:53:21.520> offload<00:53:21.960> to 00:53:22.150 --> 00:53:22.160 align:start position:0% offload and don't want to offload to 00:53:22.160 --> 00:53:24.990 align:start position:0% offload and don't want to offload to client<00:53:22.599> side<00:53:23.240> you<00:53:23.599> fully<00:53:24.079> want<00:53:24.319> the<00:53:24.440> server<00:53:24.760> to 00:53:24.990 --> 00:53:25.000 align:start position:0% client side you fully want the server to 00:53:25.000 --> 00:53:29.069 align:start position:0% client side you fully want the server to absorb<00:53:25.480> the<00:53:25.680> cost<00:53:26.119> so<00:53:26.839> yeah<00:53:27.119> like<00:53:27.839> I<00:53:28.040> guess<00:53:28.720> um 00:53:29.069 --> 00:53:29.079 align:start position:0% absorb the cost so yeah like I guess um 00:53:29.079 --> 00:53:32.069 align:start position:0% absorb the cost so yeah like I guess um and<00:53:29.280> the<00:53:29.559> tradeoffs<00:53:30.400> you<00:53:30.520> know<00:53:31.240> um<00:53:31.599> oh<00:53:31.799> sorry 00:53:32.069 --> 00:53:32.079 align:start position:0% and the tradeoffs you know um oh sorry 00:53:32.079 --> 00:53:35.510 align:start position:0% and the tradeoffs you know um oh sorry for<00:53:32.359> gesturing<00:53:33.359> this<00:53:33.520> is<00:53:33.720> just<00:53:34.000> my<00:53:34.280> my<00:53:34.559> opinion 00:53:35.510 --> 00:53:35.520 align:start position:0% for gesturing this is just my my opinion 00:53:35.520 --> 00:53:40.390 align:start position:0% for gesturing this is just my my opinion um<00:53:36.160> like<00:53:36.440> the<00:53:36.680> tradeoff<00:53:37.280> is<00:53:37.960> um<00:53:39.400> just 00:53:40.390 --> 00:53:40.400 align:start position:0% um like the tradeoff is um just 00:53:40.400 --> 00:53:44.630 align:start position:0% um like the tradeoff is um just individual<00:53:40.960> users<00:53:41.359> doing<00:53:41.760> less<00:53:42.079> work<00:53:43.040> um<00:53:43.839> and 00:53:44.630 --> 00:53:44.640 align:start position:0% individual users doing less work um and 00:53:44.640 --> 00:53:46.430 align:start position:0% individual users doing less work um and that<00:53:44.839> could<00:53:45.079> maybe<00:53:45.359> allow<00:53:45.599> you<00:53:45.720> to<00:53:45.880> scale<00:53:46.280> to 00:53:46.430 --> 00:53:46.440 align:start position:0% that could maybe allow you to scale to 00:53:46.440 --> 00:53:48.390 align:start position:0% that could maybe allow you to scale to 10K<00:53:46.839> plus<00:53:47.079> users<00:53:47.440> but<00:53:47.640> yeah<00:53:47.839> like<00:53:47.960> you<00:53:48.079> said 00:53:48.390 --> 00:53:48.400 align:start position:0% 10K plus users but yeah like you said 00:53:48.400 --> 00:53:52.309 align:start position:0% 10K plus users but yeah like you said there's<00:53:48.559> a<00:53:49.160> it's<00:53:49.280> a<00:53:49.480> big<00:53:49.720> design<00:53:50.400> space<00:53:51.400> um<00:53:52.119> all 00:53:52.309 --> 00:53:52.319 align:start position:0% there's a it's a big design space um all 00:53:52.319 --> 00:53:55.109 align:start position:0% there's a it's a big design space um all right<00:53:53.319> how<00:53:53.680> do<00:53:53.839> you<00:53:54.040> solve<00:53:54.359> the<00:53:54.559> issue<00:53:54.920> of 00:53:55.109 --> 00:53:55.119 align:start position:0% right how do you solve the issue of 00:53:55.119 --> 00:53:57.750 align:start position:0% right how do you solve the issue of querying<00:53:55.799> large<00:53:56.240> dat<00:53:56.480> databases<00:53:57.240> efficiently 00:53:57.750 --> 00:53:57.760 align:start position:0% querying large dat databases efficiently 00:53:57.760 --> 00:54:01.309 align:start position:0% querying large dat databases efficiently in<00:53:58.280> MPC<00:53:59.280> all<00:53:59.520> queries<00:54:00.119> are<00:54:00.440> linear<00:54:00.960> in<00:54:01.119> the 00:54:01.309 --> 00:54:01.319 align:start position:0% in MPC all queries are linear in the 00:54:01.319 --> 00:54:03.630 align:start position:0% in MPC all queries are linear in the database<00:54:01.839> size 00:54:03.630 --> 00:54:03.640 align:start position:0% database size 00:54:03.640 --> 00:54:07.309 align:start position:0% database size no<00:54:04.640> maybe<00:54:04.920> one<00:54:05.160> quick<00:54:05.359> thing<00:54:05.520> is<00:54:05.760> like<00:54:06.240> apple<00:54:06.599> w 00:54:07.309 --> 00:54:07.319 align:start position:0% no maybe one quick thing is like apple w 00:54:07.319 --> 00:54:09.670 align:start position:0% no maybe one quick thing is like apple w like<00:54:07.440> their<00:54:07.599> new<00:54:07.720> F<00:54:08.079> system<00:54:08.319> solves<00:54:08.680> this<00:54:09.000> by 00:54:09.670 --> 00:54:09.680 align:start position:0% like their new F system solves this by 00:54:09.680 --> 00:54:11.630 align:start position:0% like their new F system solves this by one<00:54:10.160> like<00:54:10.319> bucketing<00:54:10.880> so<00:54:11.040> you<00:54:11.160> say<00:54:11.400> look<00:54:11.559> we're 00:54:11.630 --> 00:54:11.640 align:start position:0% one like bucketing so you say look we're 00:54:11.640 --> 00:54:12.870 align:start position:0% one like bucketing so you say look we're going<00:54:11.720> to<00:54:11.799> make<00:54:11.960> square<00:54:12.119> root<00:54:12.319> of<00:54:12.440> n<00:54:12.559> buckets 00:54:12.870 --> 00:54:12.880 align:start position:0% going to make square root of n buckets 00:54:12.880 --> 00:54:13.950 align:start position:0% going to make square root of n buckets and<00:54:12.960> we're<00:54:13.079> going<00:54:13.160> to<00:54:13.280> send<00:54:13.440> it<00:54:13.559> to<00:54:13.680> the<00:54:13.799> right 00:54:13.950 --> 00:54:13.960 align:start position:0% and we're going to send it to the right 00:54:13.960 --> 00:54:15.309 align:start position:0% and we're going to send it to the right bucket<00:54:14.559> then<00:54:14.680> you<00:54:14.760> leak<00:54:14.920> a<00:54:15.000> little<00:54:15.119> bit<00:54:15.240> of 00:54:15.309 --> 00:54:15.319 align:start position:0% bucket then you leak a little bit of 00:54:15.319 --> 00:54:16.430 align:start position:0% bucket then you leak a little bit of information<00:54:15.720> which<00:54:15.799> is<00:54:15.960> which<00:54:16.119> bucket<00:54:16.319> did 00:54:16.430 --> 00:54:16.440 align:start position:0% information which is which bucket did 00:54:16.440 --> 00:54:18.390 align:start position:0% information which is which bucket did the<00:54:16.520> query<00:54:16.799> go<00:54:16.960> to<00:54:17.359> so<00:54:17.520> they<00:54:17.640> send<00:54:18.000> square<00:54:18.200> root 00:54:18.390 --> 00:54:18.400 align:start position:0% the query go to so they send square root 00:54:18.400 --> 00:54:20.670 align:start position:0% the query go to so they send square root of<00:54:18.480> n<00:54:18.640> queries<00:54:19.359> and<00:54:19.440> then<00:54:19.559> it's<00:54:19.720> like<00:54:19.960> well<00:54:20.520> you 00:54:20.670 --> 00:54:20.680 align:start position:0% of n queries and then it's like well you 00:54:20.680 --> 00:54:22.910 align:start position:0% of n queries and then it's like well you know<00:54:21.680> which<00:54:22.000> which<00:54:22.200> query<00:54:22.480> is<00:54:22.599> the<00:54:22.760> right 00:54:22.910 --> 00:54:22.920 align:start position:0% know which which query is the right 00:54:22.920 --> 00:54:24.549 align:start position:0% know which which query is the right query<00:54:23.280> you<00:54:23.400> don't<00:54:23.559> know<00:54:23.680> and<00:54:23.799> the<00:54:23.960> user<00:54:24.240> throws 00:54:24.549 --> 00:54:24.559 align:start position:0% query you don't know and the user throws 00:54:24.559 --> 00:54:26.150 align:start position:0% query you don't know and the user throws away<00:54:25.040> all<00:54:25.240> about<00:54:25.400> one<00:54:25.520> of<00:54:25.599> the<00:54:25.720> queries<00:54:26.040> so<00:54:26.119> I 00:54:26.150 --> 00:54:26.160 align:start position:0% away all about one of the queries so I 00:54:26.160 --> 00:54:27.910 align:start position:0% away all about one of the queries so I thought<00:54:26.400> that<00:54:26.480> was<00:54:26.559> a<00:54:26.640> kind<00:54:26.760> of<00:54:26.880> clever<00:54:27.200> way<00:54:27.400> to 00:54:27.910 --> 00:54:27.920 align:start position:0% thought that was a kind of clever way to 00:54:27.920 --> 00:54:29.109 align:start position:0% thought that was a kind of clever way to you<00:54:28.040> know<00:54:28.160> leak<00:54:28.359> a<00:54:28.440> little<00:54:28.559> bit<00:54:28.680> of<00:54:28.799> privacy 00:54:29.109 --> 00:54:29.119 align:start position:0% you know leak a little bit of privacy 00:54:29.119 --> 00:54:30.870 align:start position:0% you know leak a little bit of privacy but<00:54:29.200> then<00:54:29.319> undo<00:54:29.640> that<00:54:29.760> leakage<00:54:30.599> uh<00:54:30.680> and<00:54:30.799> have 00:54:30.870 --> 00:54:30.880 align:start position:0% but then undo that leakage uh and have 00:54:30.880 --> 00:54:34.670 align:start position:0% but then undo that leakage uh and have it<00:54:31.000> be<00:54:31.119> a<00:54:31.200> bit<00:54:31.400> more 00:54:34.670 --> 00:54:34.680 align:start position:0% 00:54:34.680 --> 00:54:38.710 align:start position:0% efficient<00:54:35.680> oh<00:54:36.319> okay<00:54:36.880> so<00:54:37.559> it's<00:54:37.839> like<00:54:38.079> linear 00:54:38.710 --> 00:54:38.720 align:start position:0% efficient oh okay so it's like linear 00:54:38.720 --> 00:54:41.470 align:start position:0% efficient oh okay so it's like linear over<00:54:39.079> square<00:54:39.440> root<00:54:39.640> and<00:54:40.319> buckets<00:54:41.160> and<00:54:41.240> you<00:54:41.359> can 00:54:41.470 --> 00:54:41.480 align:start position:0% over square root and buckets and you can 00:54:41.480 --> 00:54:42.750 align:start position:0% over square root and buckets and you can keep<00:54:41.680> kind<00:54:41.760> of<00:54:41.880> recursively<00:54:42.400> doing<00:54:42.640> the 00:54:42.750 --> 00:54:42.760 align:start position:0% keep kind of recursively doing the 00:54:42.760 --> 00:54:46.910 align:start position:0% keep kind of recursively doing the square<00:54:42.960> root<00:54:43.160> of<00:54:43.280> n<00:54:44.040> uh<00:54:44.480> I<00:54:45.119> see 00:54:46.910 --> 00:54:46.920 align:start position:0% square root of n uh I see 00:54:46.920 --> 00:54:50.549 align:start position:0% square root of n uh I see yeah<00:54:47.920> how<00:54:48.160> about<00:54:48.640> I<00:54:48.720> know<00:54:48.960> world<00:54:49.640> does<00:54:50.160> have 00:54:50.549 --> 00:54:50.559 align:start position:0% yeah how about I know world does have 00:54:50.559 --> 00:54:54.510 align:start position:0% yeah how about I know world does have this<00:54:51.280> um<00:54:51.960> they<00:54:52.079> do<00:54:52.280> a<00:54:52.520> database<00:54:53.119> search<00:54:53.760> per 00:54:54.510 --> 00:54:54.520 align:start position:0% this um they do a database search per 00:54:54.520 --> 00:54:58.270 align:start position:0% this um they do a database search per new<00:54:55.040> Iris<00:54:55.520> code<00:54:56.599> so<00:54:56.880> yeah<00:54:57.079> we<00:54:57.440> do<00:54:58.040> actually 00:54:58.270 --> 00:54:58.280 align:start position:0% new Iris code so yeah we do actually 00:54:58.280 --> 00:55:00.109 align:start position:0% new Iris code so yeah we do actually search<00:54:58.599> over<00:54:58.839> the<00:54:58.920> full<00:54:59.200> database<00:54:59.640> for<00:54:59.880> this 00:55:00.109 --> 00:55:00.119 align:start position:0% search over the full database for this 00:55:00.119 --> 00:55:02.510 align:start position:0% search over the full database for this and<00:55:00.319> like<00:55:00.520> it<00:55:00.640> is<00:55:01.079> quite<00:55:01.599> optimized<00:55:02.119> and<00:55:02.280> it's 00:55:02.510 --> 00:55:02.520 align:start position:0% and like it is quite optimized and it's 00:55:02.520 --> 00:55:04.710 align:start position:0% and like it is quite optimized and it's quite<00:55:02.720> efficient<00:55:03.480> but<00:55:03.720> like<00:55:03.920> it's<00:55:04.280> yeah 00:55:04.710 --> 00:55:04.720 align:start position:0% quite efficient but like it's yeah 00:55:04.720 --> 00:55:07.549 align:start position:0% quite efficient but like it's yeah heavily<00:55:05.720> specialized<00:55:06.520> optimized<00:55:07.079> protocol 00:55:07.549 --> 00:55:07.559 align:start position:0% heavily specialized optimized protocol 00:55:07.559 --> 00:55:10.150 align:start position:0% heavily specialized optimized protocol so<00:55:07.760> far<00:55:08.680> um<00:55:08.960> but<00:55:09.119> I<00:55:09.200> mean<00:55:09.359> there<00:55:09.480> is<00:55:09.720> work 00:55:10.150 --> 00:55:10.160 align:start position:0% so far um but I mean there is work 00:55:10.160 --> 00:55:13.270 align:start position:0% so far um but I mean there is work definitely<00:55:10.720> on<00:55:11.640> um 00:55:13.270 --> 00:55:13.280 align:start position:0% definitely on um 00:55:13.280 --> 00:55:16.030 align:start position:0% definitely on um like<00:55:14.280> like<00:55:14.440> lookup<00:55:14.839> tables<00:55:15.400> and<00:55:15.680> you<00:55:15.799> know 00:55:16.030 --> 00:55:16.040 align:start position:0% like like lookup tables and you know 00:55:16.040 --> 00:55:17.430 align:start position:0% like like lookup tables and you know like<00:55:16.160> there<00:55:16.280> are<00:55:16.520> ways<00:55:16.839> I<00:55:16.920> mean<00:55:17.079> there<00:55:17.240> people 00:55:17.430 --> 00:55:17.440 align:start position:0% like there are ways I mean there people 00:55:17.440 --> 00:55:19.470 align:start position:0% like there are ways I mean there people are<00:55:17.599> looking<00:55:17.880> into<00:55:18.200> this<00:55:18.680> and<00:55:18.839> coming<00:55:19.119> up<00:55:19.280> with 00:55:19.470 --> 00:55:19.480 align:start position:0% are looking into this and coming up with 00:55:19.480 --> 00:55:22.589 align:start position:0% are looking into this and coming up with like<00:55:19.640> clever<00:55:20.160> tricks<00:55:20.599> like<00:55:20.839> this<00:55:21.720> um<00:55:22.240> but<00:55:22.440> yeah 00:55:22.589 --> 00:55:22.599 align:start position:0% like clever tricks like this um but yeah 00:55:22.599 --> 00:55:24.870 align:start position:0% like clever tricks like this um but yeah so<00:55:22.799> far<00:55:23.200> it's 00:55:24.870 --> 00:55:24.880 align:start position:0% so far it's 00:55:24.880 --> 00:55:27.390 align:start position:0% so far it's uh<00:55:25.880> people<00:55:26.039> are<00:55:26.319> looking<00:55:26.559> into<00:55:26.760> it<00:55:27.000> but<00:55:27.160> it<00:55:27.240> is 00:55:27.390 --> 00:55:27.400 align:start position:0% uh people are looking into it but it is 00:55:27.400 --> 00:55:30.349 align:start position:0% uh people are looking into it but it is still<00:55:27.599> an<00:55:27.760> issue<00:55:28.680> we<00:55:28.760> need<00:55:28.960> more<00:55:29.280> P<00:55:29.760> research 00:55:30.349 --> 00:55:30.359 align:start position:0% still an issue we need more P research 00:55:30.359 --> 00:55:37.549 align:start position:0% still an issue we need more P research PR<00:55:30.680> is<00:55:30.880> really<00:55:31.079> cool<00:55:31.760> private<00:55:32.240> information 00:55:37.549 --> 00:55:37.559 align:start position:0% 00:55:37.559 --> 00:55:41.109 align:start position:0% retrieval<00:55:38.559> isn't<00:55:38.920> P<00:55:39.559> also<00:55:40.119> like<00:55:40.400> linear<00:55:40.880> work 00:55:41.109 --> 00:55:41.119 align:start position:0% retrieval isn't P also like linear work 00:55:41.119 --> 00:55:43.750 align:start position:0% retrieval isn't P also like linear work on<00:55:41.319> the<00:55:41.480> server<00:55:41.920> site<00:55:42.400> though<00:55:43.039> yeah<00:55:43.280> yeah<00:55:43.480> yeah 00:55:43.750 --> 00:55:43.760 align:start position:0% on the server site though yeah yeah yeah 00:55:43.760 --> 00:55:45.069 align:start position:0% on the server site though yeah yeah yeah right<00:55:43.920> now<00:55:44.119> I<00:55:44.200> think<00:55:44.440> they<00:55:44.599> you<00:55:44.720> just<00:55:44.880> like 00:55:45.069 --> 00:55:45.079 align:start position:0% right now I think they you just like 00:55:45.079 --> 00:55:48.349 align:start position:0% right now I think they you just like encrypt<00:55:45.480> the<00:55:45.640> whole<00:55:46.119> database<00:55:47.000> yeah<00:55:48.000> but<00:55:48.200> not 00:55:48.349 --> 00:55:48.359 align:start position:0% encrypt the whole database yeah but not 00:55:48.359 --> 00:55:53.309 align:start position:0% encrypt the whole database yeah but not for<00:55:48.559> the<00:55:48.720> user<00:55:49.599> yeah<00:55:50.599> um<00:55:51.079> cool<00:55:51.920> so<00:55:52.920> I<00:55:53.039> think<00:55:53.200> we 00:55:53.309 --> 00:55:53.319 align:start position:0% for the user yeah um cool so I think we 00:55:53.319 --> 00:55:56.670 align:start position:0% for the user yeah um cool so I think we are<00:55:53.559> over<00:55:53.920> time<00:55:54.280> now<00:55:55.039> um<00:55:55.680> and<00:55:55.880> I<00:55:56.039> really<00:55:56.440> love 00:55:56.670 --> 00:55:56.680 align:start position:0% are over time now um and I really love 00:55:56.680 --> 00:55:58.349 align:start position:0% are over time now um and I really love this<00:55:56.799> panel<00:55:57.160> thank<00:55:57.319> you<00:55:57.480> so<00:55:57.680> much<00:55:57.920> to<00:55:58.079> the 00:55:58.349 --> 00:55:58.359 align:start position:0% this panel thank you so much to the 00:55:58.359 --> 00:56:01.029 align:start position:0% this panel thank you so much to the panelists<00:55:59.359> thank<00:55:59.520> you<00:55:59.920> thank<00:56:00.079> you<00:56:00.280> also<00:56:00.520> Fork 00:56:01.029 --> 00:56:01.039 align:start position:0% panelists thank you thank you also Fork 00:56:01.039 --> 00:56:02.710 align:start position:0% panelists thank you thank you also Fork you 00:56:02.710 --> 00:56:02.720 align:start position:0% you 00:56:02.720 --> 00:56:06.760 align:start position:0% you guys<00:56:03.720> I<00:56:03.880> actually<00:56:04.280> had<00:56:04.440> to<00:56:04.520> say