WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:13.900 align:start position:0% [Applause] 00:00:13.900 --> 00:00:13.910 align:start position:0% 00:00:13.910 --> 00:00:20.560 align:start position:0% laughs 00:00:20.560 --> 00:00:20.570 align:start position:0% 00:00:20.570 --> 00:00:24.890 align:start position:0% because<00:00:21.570> it's<00:00:21.750> upset<00:00:23.509> which<00:00:24.509> might<00:00:24.689> explain 00:00:24.890 --> 00:00:24.900 align:start position:0% because it's upset which might explain 00:00:24.900 --> 00:00:27.259 align:start position:0% because it's upset which might explain all<00:00:25.500> parents<00:00:25.860> work<00:00:26.070> for<00:00:26.310> those<00:00:26.460> people<00:00:26.519> or<00:00:27.029> not 00:00:27.259 --> 00:00:27.269 align:start position:0% all parents work for those people or not 00:00:27.269 --> 00:00:29.269 align:start position:0% all parents work for those people or not tell<00:00:27.810> them<00:00:27.900> well<00:00:28.260> King<00:00:28.470> requires<00:00:28.830> us<00:00:29.070> back 00:00:29.269 --> 00:00:29.279 align:start position:0% tell them well King requires us back 00:00:29.279 --> 00:00:37.520 align:start position:0% tell them well King requires us back there<00:00:31.669> yeah<00:00:32.699> we'll<00:00:33.420> really<00:00:33.720> explain<00:00:36.379> you<00:00:37.379> need 00:00:37.520 --> 00:00:37.530 align:start position:0% there yeah we'll really explain you need 00:00:37.530 --> 00:00:39.170 align:start position:0% there yeah we'll really explain you need this<00:00:37.650> very<00:00:37.830> morning<00:00:38.250> I<00:00:38.430> can<00:00:38.610> just<00:00:38.790> be<00:00:38.970> more 00:00:39.170 --> 00:00:39.180 align:start position:0% this very morning I can just be more 00:00:39.180 --> 00:00:48.440 align:start position:0% this very morning I can just be more loud<00:00:43.219> so<00:00:44.219> first<00:00:46.010> for<00:00:47.010> those<00:00:47.579> who<00:00:47.820> was<00:00:48.149> not 00:00:48.440 --> 00:00:48.450 align:start position:0% loud so first for those who was not 00:00:48.450 --> 00:00:51.290 align:start position:0% loud so first for those who was not unintelligible<00:00:49.079> King<00:00:49.500> we<00:00:49.649> will<00:00:50.340> use<00:00:50.940> it<00:00:51.120> as<00:00:51.210> a 00:00:51.290 --> 00:00:51.300 align:start position:0% unintelligible King we will use it as a 00:00:51.300 --> 00:00:53.560 align:start position:0% unintelligible King we will use it as a short<00:00:51.570> story<00:00:51.690> of<00:00:52.050> how<00:00:52.140> stars<00:00:52.500> party 00:00:53.560 --> 00:00:53.570 align:start position:0% short story of how stars party 00:00:53.570 --> 00:01:02.330 align:start position:0% short story of how stars party what<00:00:54.570> are<00:00:54.629> you<00:00:54.780> saying<00:00:55.199> absolutely<00:01:01.340> alright 00:01:02.330 --> 00:01:02.340 align:start position:0% what are you saying absolutely alright 00:01:02.340 --> 00:01:05.150 align:start position:0% what are you saying absolutely alright she's<00:01:02.820> bright<00:01:03.059> attractive<00:01:03.949> for<00:01:04.949> a<00:01:04.979> liberal 00:01:05.150 --> 00:01:05.160 align:start position:0% she's bright attractive for a liberal 00:01:05.160 --> 00:01:08.779 align:start position:0% she's bright attractive for a liberal for<00:01:05.460> estimating<00:01:05.850> and<00:01:06.180> will<00:01:07.050> instead<00:01:07.830> like 00:01:08.779 --> 00:01:08.789 align:start position:0% for estimating and will instead like 00:01:08.789 --> 00:01:10.910 align:start position:0% for estimating and will instead like instead<00:01:09.060> of<00:01:09.210> showing<00:01:09.390> the<00:01:09.509> codes<00:01:09.899> we<00:01:10.560> wanted 00:01:10.910 --> 00:01:10.920 align:start position:0% instead of showing the codes we wanted 00:01:10.920 --> 00:01:15.139 align:start position:0% instead of showing the codes we wanted to<00:01:11.070> show<00:01:11.340> some<00:01:11.670> publications<00:01:12.119> precise<00:01:14.149> atomic 00:01:15.139 --> 00:01:15.149 align:start position:0% to show some publications precise atomic 00:01:15.149 --> 00:01:17.120 align:start position:0% to show some publications precise atomic State<00:01:15.479> Building<00:01:15.899> this<00:01:16.050> target<00:01:16.470> which<00:01:16.979> is 00:01:17.120 --> 00:01:17.130 align:start position:0% State Building this target which is 00:01:17.130 --> 00:01:19.460 align:start position:0% State Building this target which is unfortunately<00:01:17.910> not<00:01:18.060> the<00:01:18.209> star<00:01:18.450> without<00:01:19.110> the 00:01:19.460 --> 00:01:19.470 align:start position:0% unfortunately not the star without the 00:01:19.470 --> 00:01:23.570 align:start position:0% unfortunately not the star without the humidification<00:01:20.479> and<00:01:21.770> also<00:01:22.770> the<00:01:23.009> negative<00:01:23.130> is 00:01:23.570 --> 00:01:23.580 align:start position:0% humidification and also the negative is 00:01:23.580 --> 00:01:28.279 align:start position:0% humidification and also the negative is here<00:01:23.910> we<00:01:24.750> can<00:01:24.899> quickly<00:01:25.729> discuss<00:01:27.289> education 00:01:28.279 --> 00:01:28.289 align:start position:0% here we can quickly discuss education 00:01:28.289 --> 00:01:30.949 align:start position:0% here we can quickly discuss education for<00:01:28.470> medians<00:01:28.830> when<00:01:29.250> you<00:01:29.520> start<00:01:29.819> start<00:01:30.209> for<00:01:30.569> VDS 00:01:30.949 --> 00:01:30.959 align:start position:0% for medians when you start start for VDS 00:01:30.959 --> 00:01:33.919 align:start position:0% for medians when you start start for VDS venture<00:01:31.289> competition<00:01:31.709> starts<00:01:32.270> but<00:01:33.270> at<00:01:33.690> the 00:01:33.919 --> 00:01:33.929 align:start position:0% venture competition starts but at the 00:01:33.929 --> 00:01:35.140 align:start position:0% venture competition starts but at the end<00:01:33.959> of<00:01:34.110> the<00:01:34.229> presentation 00:01:35.140 --> 00:01:35.150 align:start position:0% end of the presentation 00:01:35.150 --> 00:01:37.960 align:start position:0% end of the presentation which<00:01:35.840> was<00:01:35.990> burning<00:01:36.320> we<00:01:36.440> must<00:01:36.680> humanist<00:01:37.520> which 00:01:37.960 --> 00:01:37.970 align:start position:0% which was burning we must humanist which 00:01:37.970 --> 00:01:39.600 align:start position:0% which was burning we must humanist which you<00:01:38.060> can<00:01:38.210> make<00:01:38.360> out<00:01:38.540> of<00:01:38.660> the<00:01:38.840> fried<00:01:39.170> and 00:01:39.600 --> 00:01:39.610 align:start position:0% you can make out of the fried and 00:01:39.610 --> 00:01:41.590 align:start position:0% you can make out of the fried and potential<00:01:40.610> improvements<00:01:41.090> to<00:01:41.240> it<00:01:41.360> and 00:01:41.590 --> 00:01:41.600 align:start position:0% potential improvements to it and 00:01:41.600 --> 00:01:43.750 align:start position:0% potential improvements to it and difficulties<00:01:42.080> Wiseman<00:01:42.740> but<00:01:43.220> just<00:01:43.520> now<00:01:43.700> you 00:01:43.750 --> 00:01:43.760 align:start position:0% difficulties Wiseman but just now you 00:01:43.760 --> 00:01:45.900 align:start position:0% difficulties Wiseman but just now you will<00:01:44.060> make<00:01:44.180> so<00:01:44.810> the<00:01:44.960> level<00:01:45.230> will<00:01:45.380> be<00:01:45.410> quite 00:01:45.900 --> 00:01:45.910 align:start position:0% will make so the level will be quite 00:01:45.910 --> 00:01:50.230 align:start position:0% will make so the level will be quite enhance<00:01:47.560> so<00:01:48.560> just<00:01:48.890> be<00:01:49.160> prepared<00:01:49.340> for<00:01:49.610> it'll<00:01:50.000> be 00:01:50.230 --> 00:01:50.240 align:start position:0% enhance so just be prepared for it'll be 00:01:50.240 --> 00:01:51.790 align:start position:0% enhance so just be prepared for it'll be worth<00:01:50.480> can<00:01:51.140> something<00:01:51.410> will<00:01:51.560> lead<00:01:51.680> to 00:01:51.790 --> 00:01:51.800 align:start position:0% worth can something will lead to 00:01:51.800 --> 00:01:54.160 align:start position:0% worth can something will lead to presentation<00:01:52.370> mainly<00:01:52.580> what<00:01:53.030> answers<00:01:54.020> the 00:01:54.160 --> 00:01:54.170 align:start position:0% presentation mainly what answers the 00:01:54.170 --> 00:01:56.320 align:start position:0% presentation mainly what answers the question<00:01:54.470> says<00:01:54.650> something<00:01:55.010> happens<00:01:55.310> as<00:01:56.150> a 00:01:56.320 --> 00:01:56.330 align:start position:0% question says something happens as a 00:01:56.330 --> 00:01:58.090 align:start position:0% question says something happens as a format<00:01:56.720> as<00:01:56.930> if<00:01:57.200> you<00:01:57.350> don't<00:01:57.590> understand 00:01:58.090 --> 00:01:58.100 align:start position:0% format as if you don't understand 00:01:58.100 --> 00:01:59.590 align:start position:0% format as if you don't understand something<00:01:58.310> like<00:01:58.490> you<00:01:58.790> really<00:01:59.120> won't<00:01:59.240> ask<00:01:59.480> the 00:01:59.590 --> 00:01:59.600 align:start position:0% something like you really won't ask the 00:01:59.600 --> 00:02:00.880 align:start position:0% something like you really won't ask the question<00:01:59.900> it<00:01:59.960> should<00:01:59.990> price<00:02:00.260> it<00:02:00.290> handed<00:02:00.770> we 00:02:00.880 --> 00:02:00.890 align:start position:0% question it should price it handed we 00:02:00.890 --> 00:02:07.870 align:start position:0% question it should price it handed we should<00:02:01.070> stop<00:02:01.580> and<00:02:01.820> ask<00:02:02.210> your<00:02:02.420> question<00:02:06.880> okay 00:02:07.870 --> 00:02:07.880 align:start position:0% should stop and ask your question okay 00:02:07.880 --> 00:02:11.560 align:start position:0% should stop and ask your question okay thank<00:02:08.630> you<00:02:08.660> for<00:02:08.720> coming<00:02:09.110> as<00:02:09.350> Alex<00:02:09.890> told<00:02:10.570> we 00:02:11.560 --> 00:02:11.570 align:start position:0% thank you for coming as Alex told we 00:02:11.570 --> 00:02:14.520 align:start position:0% thank you for coming as Alex told we won't<00:02:11.750> speak<00:02:12.020> about<00:02:12.290> our<00:02:13.360> implementational 00:02:14.520 --> 00:02:14.530 align:start position:0% won't speak about our implementational 00:02:14.530 --> 00:02:20.610 align:start position:0% won't speak about our implementational stars<00:02:15.530> called<00:02:15.890> order<00:02:17.560> because<00:02:18.560> of<00:02:18.640> recent 00:02:20.610 --> 00:02:20.620 align:start position:0% stars called order because of recent 00:02:20.620 --> 00:02:22.870 align:start position:0% stars called order because of recent appearance<00:02:21.620> of<00:02:21.830> new<00:02:22.010> proof<00:02:22.280> system<00:02:22.490> such<00:02:22.850> as 00:02:22.870 --> 00:02:22.880 align:start position:0% appearance of new proof system such as 00:02:22.880 --> 00:02:25.900 align:start position:0% appearance of new proof system such as born<00:02:23.660> and<00:02:24.020> because<00:02:24.320> of<00:02:25.070> our<00:02:25.280> commitment 00:02:25.900 --> 00:02:25.910 align:start position:0% born and because of our commitment 00:02:25.910 --> 00:02:30.250 align:start position:0% born and because of our commitment skills<00:02:26.480> we<00:02:27.350> decided<00:02:27.920> to<00:02:28.100> give<00:02:28.820> the<00:02:29.570> motivation 00:02:30.250 --> 00:02:30.260 align:start position:0% skills we decided to give the motivation 00:02:30.260 --> 00:02:33.520 align:start position:0% skills we decided to give the motivation of<00:02:30.350> our<00:02:30.560> dog<00:02:30.830> of<00:02:31.100> course<00:02:31.990> it<00:02:32.990> has<00:02:33.230> its<00:02:33.260> roots 00:02:33.520 --> 00:02:33.530 align:start position:0% of our dog of course it has its roots 00:02:33.530 --> 00:02:35.950 align:start position:0% of our dog of course it has its roots its<00:02:33.830> source<00:02:34.100> in<00:02:34.310> starts<00:02:34.670> and<00:02:35.600> we'll<00:02:35.720> start 00:02:35.950 --> 00:02:35.960 align:start position:0% its source in starts and we'll start 00:02:35.960 --> 00:02:39.699 align:start position:0% its source in starts and we'll start from<00:02:37.030> the<00:02:38.030> definition<00:02:38.540> of<00:02:38.630> juggs<00:02:38.900> show<00:02:39.470> how 00:02:39.699 --> 00:02:39.709 align:start position:0% from the definition of juggs show how 00:02:39.709 --> 00:02:41.530 align:start position:0% from the definition of juggs show how they<00:02:39.860> were<00:02:39.920> born<00:02:40.130> and<00:02:40.430> then<00:02:41.000> I<00:02:41.209> will<00:02:41.360> try<00:02:41.480> to 00:02:41.530 --> 00:02:41.540 align:start position:0% they were born and then I will try to 00:02:41.540 --> 00:02:44.080 align:start position:0% they were born and then I will try to show<00:02:41.840> how<00:02:42.110> some<00:02:42.680> components<00:02:43.160> of<00:02:43.370> its<00:02:43.760> charge 00:02:44.080 --> 00:02:44.090 align:start position:0% show how some components of its charge 00:02:44.090 --> 00:02:47.680 align:start position:0% show how some components of its charge when<00:02:44.840> they<00:02:45.020> define<00:02:46.010> this<00:02:46.130> chapter<00:02:46.550> fry<00:02:46.790> can<00:02:47.600> be 00:02:47.680 --> 00:02:47.690 align:start position:0% when they define this chapter fry can be 00:02:47.690 --> 00:02:50.380 align:start position:0% when they define this chapter fry can be combined<00:02:48.080> or<00:02:48.470> even<00:02:48.920> for<00:02:49.459> example<00:02:49.790> blown<00:02:50.060> to 00:02:50.380 --> 00:02:50.390 align:start position:0% combined or even for example blown to 00:02:50.390 --> 00:02:52.750 align:start position:0% combined or even for example blown to achieve<00:02:50.780> for<00:02:51.380> just<00:02:51.680> around<00:02:51.830> times<00:02:52.160> extinction 00:02:52.750 --> 00:02:52.760 align:start position:0% achieve for just around times extinction 00:02:52.760 --> 00:02:55.449 align:start position:0% achieve for just around times extinction snack<00:02:54.070> next<00:02:55.070> one 00:02:55.449 --> 00:02:55.459 align:start position:0% snack next one 00:02:55.459 --> 00:02:57.790 align:start position:0% snack next one hello<00:02:56.239> there<00:02:56.900> are<00:02:57.020> not<00:02:57.140> with<00:02:57.290> the<00:02:57.440> following 00:02:57.790 --> 00:02:57.800 align:start position:0% hello there are not with the following 00:02:57.800 --> 00:03:02.380 align:start position:0% hello there are not with the following reminder<00:02:58.760> stars<00:02:59.480> I<00:03:00.140> will<00:03:00.680> briefly<00:03:01.390> described 00:03:02.380 --> 00:03:02.390 align:start position:0% reminder stars I will briefly described 00:03:02.390 --> 00:03:06.670 align:start position:0% reminder stars I will briefly described all<00:03:02.750> the<00:03:02.900> steps<00:03:03.280> because<00:03:05.680> organization 00:03:06.670 --> 00:03:06.680 align:start position:0% all the steps because organization 00:03:06.680 --> 00:03:09.699 align:start position:0% all the steps because organization called<00:03:06.980> air<00:03:07.430> and<00:03:07.700> a<00:03:07.820> second<00:03:08.239> and<00:03:09.080> justify 00:03:09.699 --> 00:03:09.709 align:start position:0% called air and a second and justify 00:03:09.709 --> 00:03:11.830 align:start position:0% called air and a second and justify itself<00:03:10.010> then<00:03:10.850> I<00:03:10.940> will<00:03:11.060> speak<00:03:11.239> about<00:03:11.300> one 00:03:11.830 --> 00:03:11.840 align:start position:0% itself then I will speak about one 00:03:11.840 --> 00:03:12.790 align:start position:0% itself then I will speak about one second<00:03:12.170> okay 00:03:12.790 --> 00:03:12.800 align:start position:0% second okay 00:03:12.800 --> 00:03:16.840 align:start position:0% second okay Jimmy's<00:03:14.380> gait<00:03:15.380> commitment<00:03:16.010> which<00:03:16.460> I<00:03:16.610> still 00:03:16.840 --> 00:03:16.850 align:start position:0% Jimmy's gait commitment which I still 00:03:16.850 --> 00:03:20.830 align:start position:0% Jimmy's gait commitment which I still mostly<00:03:17.750> use<00:03:17.900> now<00:03:18.140> and<00:03:18.760> how<00:03:19.760> we<00:03:19.820> can<00:03:20.060> build<00:03:20.360> you 00:03:20.830 --> 00:03:20.840 align:start position:0% mostly use now and how we can build you 00:03:20.840 --> 00:03:23.950 align:start position:0% mostly use now and how we can build you commitment<00:03:21.680> scheme<00:03:21.950> from<00:03:22.250> from<00:03:23.030> tried<00:03:23.300> and 00:03:23.950 --> 00:03:23.960 align:start position:0% commitment scheme from from tried and 00:03:23.960 --> 00:03:26.620 align:start position:0% commitment scheme from from tried and then<00:03:24.380> I<00:03:24.440> will<00:03:24.800> try<00:03:25.310> to<00:03:25.370> speak<00:03:25.580> about<00:03:25.700> possible 00:03:26.620 --> 00:03:26.630 align:start position:0% then I will try to speak about possible 00:03:26.630 --> 00:03:30.400 align:start position:0% then I will try to speak about possible applications<00:03:27.200> of<00:03:27.350> commitment<00:03:28.100> scheme<00:03:28.370> to<00:03:29.410> to 00:03:30.400 --> 00:03:30.410 align:start position:0% applications of commitment scheme to to 00:03:30.410 --> 00:03:33.700 align:start position:0% applications of commitment scheme to to make<00:03:30.560> food<00:03:30.800> transparent<00:03:31.310> snacks<00:03:32.350> okay<00:03:33.350> so 00:03:33.700 --> 00:03:33.710 align:start position:0% make food transparent snacks okay so 00:03:33.710 --> 00:03:37.780 align:start position:0% make food transparent snacks okay so let's<00:03:34.100> begin<00:03:34.690> this<00:03:35.690> is<00:03:36.100> the<00:03:37.100> formal 00:03:37.780 --> 00:03:37.790 align:start position:0% let's begin this is the formal 00:03:37.790 --> 00:03:40.420 align:start position:0% let's begin this is the formal definition<00:03:38.270> of<00:03:38.990> algebraic<00:03:39.770> intermediate 00:03:40.420 --> 00:03:40.430 align:start position:0% definition of algebraic intermediate 00:03:40.430 --> 00:03:42.180 align:start position:0% definition of algebraic intermediate representation 00:03:42.180 --> 00:03:42.190 align:start position:0% representation 00:03:42.190 --> 00:03:45.940 align:start position:0% representation it's<00:03:43.190> might<00:03:43.430> look<00:03:43.580> quite<00:03:43.850> weird<00:03:44.750> but<00:03:45.290> I<00:03:45.530> will 00:03:45.940 --> 00:03:45.950 align:start position:0% it's might look quite weird but I will 00:03:45.950 --> 00:03:48.670 align:start position:0% it's might look quite weird but I will just<00:03:46.190> explain<00:03:46.730> what<00:03:47.480> the<00:03:47.570> board<00:03:47.810> what<00:03:48.200> what 00:03:48.670 --> 00:03:48.680 align:start position:0% just explain what the board what what 00:03:48.680 --> 00:03:50.740 align:start position:0% just explain what the board what what does<00:03:48.890> it<00:03:49.010> exactly<00:03:49.130> mean<00:03:49.430> and<00:03:49.880> you<00:03:50.450> will<00:03:50.570> see 00:03:50.740 --> 00:03:50.750 align:start position:0% does it exactly mean and you will see 00:03:50.750 --> 00:03:53.110 align:start position:0% does it exactly mean and you will see that<00:03:51.220> it's<00:03:52.220> pretty<00:03:52.340> simple 00:03:53.110 --> 00:03:53.120 align:start position:0% that it's pretty simple 00:03:53.120 --> 00:03:57.850 align:start position:0% that it's pretty simple okay 00:03:57.850 --> 00:03:57.860 align:start position:0% 00:03:57.860 --> 00:04:06.550 align:start position:0% [Music] 00:04:06.550 --> 00:04:06.560 align:start position:0% 00:04:06.560 --> 00:04:11.900 align:start position:0% okay<00:04:08.570> and<00:04:09.570> is<00:04:10.080> just<00:04:10.410> kind<00:04:10.920> of<00:04:11.100> register 00:04:11.900 --> 00:04:11.910 align:start position:0% okay and is just kind of register 00:04:11.910 --> 00:04:15.170 align:start position:0% okay and is just kind of register machine<00:04:12.060> so<00:04:12.750> you<00:04:13.350> choose<00:04:13.560> your<00:04:13.920> parameters<00:04:14.180> F 00:04:15.170 --> 00:04:15.180 align:start position:0% machine so you choose your parameters F 00:04:15.180 --> 00:04:17.539 align:start position:0% machine so you choose your parameters F which<00:04:15.600> is<00:04:15.720> just<00:04:15.960> a<00:04:16.260> finite<00:04:16.680> field<00:04:16.769> which 00:04:17.539 --> 00:04:17.549 align:start position:0% which is just a finite field which 00:04:17.549 --> 00:04:20.960 align:start position:0% which is just a finite field which should<00:04:17.820> be<00:04:17.970> a<00:04:18.000> residue<00:04:18.450> field<00:04:19.670> some<00:04:20.670> applied 00:04:20.960 --> 00:04:20.970 align:start position:0% should be a residue field some applied 00:04:20.970 --> 00:04:26.390 align:start position:0% should be a residue field some applied fields<00:04:21.269> and<00:04:21.390> other<00:04:21.510> words<00:04:21.750> and<00:04:24.470> W<00:04:25.470> is<00:04:25.800> a<00:04:26.040> number 00:04:26.390 --> 00:04:26.400 align:start position:0% fields and other words and W is a number 00:04:26.400 --> 00:04:34.100 align:start position:0% fields and other words and W is a number of<00:04:26.460> registers<00:04:28.130> so<00:04:29.130> just<00:04:29.490> keeps<00:04:30.090> them<00:04:33.110> and 00:04:34.100 --> 00:04:34.110 align:start position:0% of registers so just keeps them and 00:04:34.110 --> 00:04:38.420 align:start position:0% of registers so just keeps them and they'll<00:04:34.350> tell<00:04:34.560> them<00:04:35.540> empty<00:04:36.560> is<00:04:37.560> just<00:04:37.920> going 00:04:38.420 --> 00:04:38.430 align:start position:0% they'll tell them empty is just going 00:04:38.430 --> 00:04:43.880 align:start position:0% they'll tell them empty is just going trace<00:04:39.240> is<00:04:39.870> the<00:04:40.080> number<00:04:40.590> of<00:04:40.650> steps<00:04:40.980> that<00:04:42.890> your 00:04:43.880 --> 00:04:43.890 align:start position:0% trace is the number of steps that your 00:04:43.890 --> 00:04:48.380 align:start position:0% trace is the number of steps that your program<00:04:44.280> just<00:04:44.520> executes<00:04:46.040> and<00:04:47.040> a<00:04:47.910> cherry<00:04:48.330> stem 00:04:48.380 --> 00:04:48.390 align:start position:0% program just executes and a cherry stem 00:04:48.390 --> 00:04:53.840 align:start position:0% program just executes and a cherry stem we<00:04:48.990> just<00:04:49.260> modify<00:04:51.200> the<00:04:52.200> contents<00:04:52.770> of<00:04:52.950> every 00:04:53.840 --> 00:04:53.850 align:start position:0% we just modify the contents of every 00:04:53.850 --> 00:04:59.170 align:start position:0% we just modify the contents of every registered 00:04:59.170 --> 00:04:59.180 align:start position:0% 00:04:59.180 --> 00:05:03.920 align:start position:0% don't<00:05:00.180> plant<00:05:01.310> the<00:05:02.310> program<00:05:02.789> is<00:05:03.030> encoded<00:05:03.689> as<00:05:03.840> a 00:05:03.920 --> 00:05:03.930 align:start position:0% don't plant the program is encoded as a 00:05:03.930 --> 00:05:12.330 align:start position:0% don't plant the program is encoded as a matrix<00:05:04.169> of<00:05:04.560> size<00:05:05.099> T<00:05:06.020> cross<00:05:07.020> W 00:05:12.330 --> 00:05:12.340 align:start position:0% 00:05:12.340 --> 00:05:15.930 align:start position:0% but<00:05:12.910> the<00:05:13.030> question<00:05:13.390> is<00:05:13.830> how<00:05:14.830> can<00:05:15.220> what's<00:05:15.820> the 00:05:15.930 --> 00:05:15.940 align:start position:0% but the question is how can what's the 00:05:15.940 --> 00:05:18.660 align:start position:0% but the question is how can what's the possible<00:05:16.210> ways<00:05:16.480> to<00:05:16.510> modify<00:05:17.350> the<00:05:17.920> content<00:05:18.370> and 00:05:18.660 --> 00:05:18.670 align:start position:0% possible ways to modify the content and 00:05:18.670 --> 00:05:24.330 align:start position:0% possible ways to modify the content and in<00:05:19.660> fact<00:05:19.930> is<00:05:20.320> how<00:05:20.650> as<00:05:21.400> jack<00:05:21.760> box<00:05:22.890> there<00:05:23.890> is<00:05:24.070> some 00:05:24.330 --> 00:05:24.340 align:start position:0% in fact is how as jack box there is some 00:05:24.340 --> 00:05:28.190 align:start position:0% in fact is how as jack box there is some kind<00:05:24.490> of<00:05:24.700> restrictions<00:05:26.520> on<00:05:27.520> how<00:05:27.730> to<00:05:27.790> modify 00:05:28.190 --> 00:05:28.200 align:start position:0% kind of restrictions on how to modify 00:05:28.200 --> 00:05:35.400 align:start position:0% kind of restrictions on how to modify the<00:05:29.200> values<00:05:30.390> on<00:05:31.390> each<00:05:31.450> step<00:05:33.900> we<00:05:34.900> should<00:05:35.050> apply 00:05:35.400 --> 00:05:35.410 align:start position:0% the values on each step we should apply 00:05:35.410 --> 00:05:39.260 align:start position:0% the values on each step we should apply the<00:05:35.440> same<00:05:36.160> set<00:05:37.120> of<00:05:37.450> polynomial<00:05:38.170> functions 00:05:39.260 --> 00:05:39.270 align:start position:0% the same set of polynomial functions 00:05:39.270 --> 00:05:44.610 align:start position:0% the same set of polynomial functions random<00:05:40.270> called<00:05:41.280> the<00:05:42.280> trace<00:05:42.520> constraints<00:05:43.620> what 00:05:44.610 --> 00:05:44.620 align:start position:0% random called the trace constraints what 00:05:44.620 --> 00:05:49.520 align:start position:0% random called the trace constraints what they<00:05:44.770> call<00:05:44.920> them<00:05:45.070> P<00:05:45.370> 1<00:05:46.080> P<00:05:47.080> 2<00:05:47.110> up<00:05:47.920> to<00:05:48.220> P<00:05:48.490> key<00:05:49.120> and 00:05:49.520 --> 00:05:49.530 align:start position:0% they call them P 1 P 2 up to P key and 00:05:49.530 --> 00:05:55.100 align:start position:0% they call them P 1 P 2 up to P key and they<00:05:50.530> should<00:05:51.160> be<00:05:51.310> applied<00:05:51.610> at<00:05:51.880> every<00:05:52.330> step 00:05:55.100 --> 00:05:55.110 align:start position:0% 00:05:55.110 --> 00:05:59.480 align:start position:0% every<00:05:56.700> such<00:05:57.700> polynomial<00:05:58.210> is<00:05:58.420> a<00:05:58.480> function<00:05:59.050> in 00:05:59.480 --> 00:05:59.490 align:start position:0% every such polynomial is a function in 00:05:59.490 --> 00:06:06.750 align:start position:0% every such polynomial is a function in to<00:06:00.490> W<00:06:01.420> variable<00:06:03.570> the<00:06:04.570> first<00:06:04.900> atomic<00:06:05.860> particles 00:06:06.750 --> 00:06:06.760 align:start position:0% to W variable the first atomic particles 00:06:06.760 --> 00:06:08.940 align:start position:0% to W variable the first atomic particles is<00:06:06.970> just<00:06:07.300> all<00:06:07.810> the<00:06:07.840> state<00:06:08.140> of<00:06:08.290> registers<00:06:08.770> and 00:06:08.940 --> 00:06:08.950 align:start position:0% is just all the state of registers and 00:06:08.950 --> 00:06:11.640 align:start position:0% is just all the state of registers and the<00:06:09.670> next<00:06:09.940> one<00:06:10.150> is<00:06:10.390> the<00:06:11.140> new<00:06:11.290> state<00:06:11.530> of 00:06:11.640 --> 00:06:11.650 align:start position:0% the next one is the new state of 00:06:11.650 --> 00:06:16.380 align:start position:0% the next one is the new state of registers<00:06:13.170> and<00:06:14.250> the<00:06:15.250> most<00:06:15.460> simple<00:06:15.820> example 00:06:16.380 --> 00:06:16.390 align:start position:0% registers and the most simple example 00:06:16.390 --> 00:06:18.570 align:start position:0% registers and the most simple example wedding<00:06:16.750> many<00:06:17.680> of<00:06:17.830> you<00:06:17.950> have<00:06:18.160> shown<00:06:18.310> at<00:06:18.460> my 00:06:18.570 --> 00:06:18.580 align:start position:0% wedding many of you have shown at my 00:06:18.580 --> 00:06:25.560 align:start position:0% wedding many of you have shown at my chance<00:06:19.320> came<00:06:20.320> on<00:06:20.440> as<00:06:20.560> a<00:06:20.590> sequence<00:06:24.420> so<00:06:25.420> the 00:06:25.560 --> 00:06:25.570 align:start position:0% chance came on as a sequence so the 00:06:25.570 --> 00:06:31.260 align:start position:0% chance came on as a sequence so the first<00:06:25.780> register<00:06:26.350> is<00:06:26.470> just<00:06:28.710> 1 00:06:31.260 --> 00:06:31.270 align:start position:0% first register is just 1 00:06:31.270 --> 00:06:39.080 align:start position:0% first register is just 1 -<00:06:31.479> in<00:06:31.840> a<00:06:31.960> second<00:06:32.319> it's<00:06:32.440> 1<00:06:32.680> 2<00:06:33.509> 3<00:06:37.199> and<00:06:38.199> so<00:06:38.380> on<00:06:38.410> so 00:06:39.080 --> 00:06:39.090 align:start position:0% - in a second it's 1 2 3 and so on so 00:06:39.090 --> 00:06:42.689 align:start position:0% - in a second it's 1 2 3 and so on so the<00:06:40.090> UM<00:06:40.449> second<00:06:40.870> register<00:06:41.169> is<00:06:41.530> just<00:06:41.830> the<00:06:42.370> sum 00:06:42.689 --> 00:06:42.699 align:start position:0% the UM second register is just the sum 00:06:42.699 --> 00:06:48.029 align:start position:0% the UM second register is just the sum of<00:06:42.990> the<00:06:43.990> various<00:06:46.199> employees<00:06:47.199> registers<00:06:47.740> and 00:06:48.029 --> 00:06:48.039 align:start position:0% of the various employees registers and 00:06:48.039 --> 00:06:57.360 align:start position:0% of the various employees registers and the<00:06:48.190> function<00:06:48.639> in<00:06:48.819> to<00:06:49.210> the<00:06:49.330> variables<00:06:49.900> is<00:06:56.370> x1 00:06:57.360 --> 00:06:57.370 align:start position:0% the function in to the variables is x1 00:06:57.370 --> 00:07:07.589 align:start position:0% the function in to the variables is x1 plus<00:06:58.319> x2<00:06:59.319> minus<00:07:02.820> is<00:07:03.820> equal<00:07:03.880> to<00:07:04.270> 0<00:07:06.180> what<00:07:07.180> is<00:07:07.300> x1 00:07:07.589 --> 00:07:07.599 align:start position:0% plus x2 minus is equal to 0 what is x1 00:07:07.599 --> 00:07:12.390 align:start position:0% plus x2 minus is equal to 0 what is x1 is<00:07:07.810> y/x<00:07:09.509> I<00:07:10.740> call<00:07:11.740> them<00:07:12.099> all<00:07:12.220> together 00:07:12.390 --> 00:07:12.400 align:start position:0% is y/x I call them all together 00:07:12.400 --> 00:07:14.370 align:start position:0% is y/x I call them all together producers<00:07:13.000> to<00:07:13.389> be<00:07:13.509> next<00:07:13.720> and<00:07:14.020> then<00:07:14.139> you<00:07:14.229> will 00:07:14.370 --> 00:07:14.380 align:start position:0% producers to be next and then you will 00:07:14.380 --> 00:07:16.950 align:start position:0% producers to be next and then you will have<00:07:14.470> letters<00:07:14.680> to<00:07:14.889> be<00:07:15.009> Y<00:07:15.160> so<00:07:15.580> I<00:07:15.639> think<00:07:15.900> this<00:07:16.900> is 00:07:16.950 --> 00:07:16.960 align:start position:0% have letters to be Y so I think this is 00:07:16.960 --> 00:07:23.899 align:start position:0% have letters to be Y so I think this is X<00:07:17.289> and<00:07:17.620> this<00:07:18.280> is<00:07:18.340> y<00:07:18.460> it's<00:07:19.210> one<00:07:19.620> -<00:07:21.570> why<00:07:22.570> -<00:07:22.630> just 00:07:23.899 --> 00:07:23.909 align:start position:0% X and this is y it's one - why - just 00:07:23.909 --> 00:07:27.300 align:start position:0% X and this is y it's one - why - just apply<00:07:24.909> the<00:07:24.970> sum<00:07:25.270> function<00:07:25.449> and<00:07:26.110> the<00:07:26.979> new<00:07:27.159> value 00:07:27.300 --> 00:07:27.310 align:start position:0% apply the sum function and the new value 00:07:27.310 --> 00:07:35.140 align:start position:0% apply the sum function and the new value of<00:07:27.520> y<00:07:29.759> is<00:07:30.759> just<00:07:31.090> the<00:07:31.150> previous<00:07:31.449> value<00:07:31.750> max 00:07:35.140 --> 00:07:35.150 align:start position:0% 00:07:35.150 --> 00:07:37.930 align:start position:0% and<00:07:35.240> the<00:07:35.960> same<00:07:36.200> set<00:07:36.770> of<00:07:36.890> functions<00:07:37.310> is<00:07:37.580> applied 00:07:37.930 --> 00:07:37.940 align:start position:0% and the same set of functions is applied 00:07:37.940 --> 00:07:42.460 align:start position:0% and the same set of functions is applied at<00:07:38.360> every<00:07:38.990> step<00:07:39.200> but<00:07:40.090> sure<00:07:41.090> in<00:07:41.480> real 00:07:42.460 --> 00:07:42.470 align:start position:0% at every step but sure in real 00:07:42.470 --> 00:07:48.960 align:start position:0% at every step but sure in real applications<00:07:42.620> or<00:07:43.520> summer<00:07:43.730> weeks<00:07:44.110> in<00:07:45.110> which 00:07:48.960 --> 00:07:48.970 align:start position:0% 00:07:48.970 --> 00:07:51.580 align:start position:0% the<00:07:49.970> previous<00:07:50.210> well<00:07:50.570> it's<00:07:50.930> the<00:07:51.080> previous<00:07:51.380> well 00:07:51.580 --> 00:07:51.590 align:start position:0% the previous well it's the previous well 00:07:51.590 --> 00:07:53.350 align:start position:0% the previous well it's the previous well and<00:07:51.800> why's<00:07:52.010> the<00:07:52.250> new<00:07:52.370> welcome<00:07:52.610> and<00:07:52.910> the<00:07:53.180> same 00:07:53.350 --> 00:07:53.360 align:start position:0% and why's the new welcome and the same 00:07:53.360 --> 00:07:54.970 align:start position:0% and why's the new welcome and the same set<00:07:53.540> of<00:07:53.660> function<00:07:53.960> applied<00:07:54.230> at<00:07:54.500> every<00:07:54.800> step 00:07:54.970 --> 00:07:54.980 align:start position:0% set of function applied at every step 00:07:54.980 --> 00:07:58.360 align:start position:0% set of function applied at every step and<00:07:55.250> of<00:07:56.000> course<00:07:56.240> just<00:07:56.660> here<00:07:57.530> captures<00:07:58.070> many 00:07:58.360 --> 00:07:58.370 align:start position:0% and of course just here captures many 00:07:58.370 --> 00:08:01.840 align:start position:0% and of course just here captures many functions<00:07:59.000> but<00:07:59.840> in<00:08:00.440> reality<00:08:00.680> you<00:08:01.280> try<00:08:01.490> to<00:08:01.550> call 00:08:01.840 --> 00:08:01.850 align:start position:0% functions but in reality you try to call 00:08:01.850 --> 00:08:07.860 align:start position:0% functions but in reality you try to call some<00:08:04.690> weird<00:08:05.690> to<00:08:05.870> service<00:08:06.710> you<00:08:06.920> will<00:08:07.010> have 00:08:07.860 --> 00:08:07.870 align:start position:0% some weird to service you will have 00:08:07.870 --> 00:08:11.020 align:start position:0% some weird to service you will have phenomenal<00:08:08.870> relations<00:08:09.680> which<00:08:10.280> can<00:08:10.460> be<00:08:10.580> cupid 00:08:11.020 --> 00:08:11.030 align:start position:0% phenomenal relations which can be cupid 00:08:11.030 --> 00:08:14.560 align:start position:0% phenomenal relations which can be cupid or<00:08:11.210> tragically<00:08:11.780> general<00:08:12.740> imagine<00:08:13.480> and<00:08:14.480> you 00:08:14.560 --> 00:08:14.570 align:start position:0% or tragically general imagine and you 00:08:14.570 --> 00:08:17.290 align:start position:0% or tragically general imagine and you can<00:08:14.720> mix<00:08:14.990> the<00:08:15.530> x<00:08:15.740> and<00:08:15.950> y<00:08:16.040> variables<00:08:16.100> as<00:08:17.090> you 00:08:17.290 --> 00:08:17.300 align:start position:0% can mix the x and y variables as you 00:08:17.300 --> 00:08:21.280 align:start position:0% can mix the x and y variables as you wish<00:08:17.510> and<00:08:18.130> the<00:08:19.130> main<00:08:19.340> the<00:08:20.180> main<00:08:20.210> thing<00:08:20.660> here<00:08:21.200> I 00:08:21.280 --> 00:08:21.290 align:start position:0% wish and the main the main thing here I 00:08:21.290 --> 00:08:24.630 align:start position:0% wish and the main the main thing here I want<00:08:21.590> to<00:08:21.740> stress<00:08:22.340> is<00:08:22.640> the<00:08:23.180> difference<00:08:23.750> from 00:08:24.630 --> 00:08:24.640 align:start position:0% want to stress is the difference from 00:08:24.640 --> 00:08:27.550 align:start position:0% want to stress is the difference from around<00:08:25.640> one<00:08:25.850> caste<00:08:26.180> system<00:08:26.600> when<00:08:27.200> they<00:08:27.320> try<00:08:27.500> to 00:08:27.550 --> 00:08:27.560 align:start position:0% around one caste system when they try to 00:08:27.560 --> 00:08:31.600 align:start position:0% around one caste system when they try to encode<00:08:28.280> some<00:08:28.760> gadget<00:08:29.540> in<00:08:30.010> tasty<00:08:31.010> services<00:08:31.400> for 00:08:31.600 --> 00:08:31.610 align:start position:0% encode some gadget in tasty services for 00:08:31.610 --> 00:08:34.330 align:start position:0% encode some gadget in tasty services for example<00:08:31.670> hash<00:08:32.240> function<00:08:32.690> and<00:08:33.380> then<00:08:33.530> when<00:08:34.220> they 00:08:34.330 --> 00:08:34.340 align:start position:0% example hash function and then when they 00:08:34.340 --> 00:08:35.710 align:start position:0% example hash function and then when they try<00:08:34.550> to<00:08:34.580> use<00:08:34.850> it<00:08:35.000> to<00:08:35.180> use<00:08:35.300> service<00:08:35.570> several 00:08:35.710 --> 00:08:35.720 align:start position:0% try to use it to use service several 00:08:35.720 --> 00:08:39.160 align:start position:0% try to use it to use service several times<00:08:36.250> you<00:08:37.250> will<00:08:37.430> need<00:08:37.610> to<00:08:38.030> pay<00:08:38.240> every<00:08:39.140> time 00:08:39.160 --> 00:08:39.170 align:start position:0% times you will need to pay every time 00:08:39.170 --> 00:08:42.040 align:start position:0% times you will need to pay every time you<00:08:40.070> use<00:08:40.310> your<00:08:40.610> hash<00:08:41.030> function<00:08:41.060> so<00:08:41.810> if<00:08:41.930> your 00:08:42.040 --> 00:08:42.050 align:start position:0% you use your hash function so if your 00:08:42.050 --> 00:08:44.440 align:start position:0% you use your hash function so if your stop<00:08:42.230> it<00:08:42.320> contains<00:08:42.800> three<00:08:43.490> instances<00:08:44.060> on<00:08:44.360> the 00:08:44.440 --> 00:08:44.450 align:start position:0% stop it contains three instances on the 00:08:44.450 --> 00:08:46.390 align:start position:0% stop it contains three instances on the same<00:08:44.660> path<00:08:44.900> percentage<00:08:45.560> function<00:08:45.950> then<00:08:46.130> you 00:08:46.390 --> 00:08:46.400 align:start position:0% same path percentage function then you 00:08:46.400 --> 00:08:49.750 align:start position:0% same path percentage function then you will<00:08:46.970> have<00:08:47.150> a<00:08:47.450> triple<00:08:48.200> number<00:08:48.440> of<00:08:48.500> kids<00:08:48.760> and 00:08:49.750 --> 00:08:49.760 align:start position:0% will have a triple number of kids and 00:08:49.760 --> 00:08:53.920 align:start position:0% will have a triple number of kids and the<00:08:49.850> difference<00:08:51.940> in<00:08:52.940> this<00:08:53.060> situation<00:08:53.750> with 00:08:53.920 --> 00:08:53.930 align:start position:0% the difference in this situation with 00:08:53.930 --> 00:08:58.090 align:start position:0% the difference in this situation with just<00:08:54.230> by<00:08:54.470> different<00:08:54.860> was<00:08:55.100> just<00:08:55.610> encode<00:08:57.100> your 00:08:58.090 --> 00:08:58.100 align:start position:0% just by different was just encode your 00:08:58.100 --> 00:09:00.460 align:start position:0% just by different was just encode your guard<00:08:58.340> upon<00:08:58.550> the<00:08:58.670> ones<00:08:58.880> and<00:08:59.300> then<00:09:00.020> you<00:09:00.170> may<00:09:00.320> use 00:09:00.460 --> 00:09:00.470 align:start position:0% guard upon the ones and then you may use 00:09:00.470 --> 00:09:05.100 align:start position:0% guard upon the ones and then you may use of<00:09:00.560> a<00:09:00.620> billion<00:09:01.180> but<00:09:02.180> you<00:09:03.020> need<00:09:03.290> to<00:09:03.680> have<00:09:03.890> some 00:09:05.100 --> 00:09:05.110 align:start position:0% of a billion but you need to have some 00:09:05.110 --> 00:09:10.360 align:start position:0% of a billion but you need to have some bunch<00:09:06.110> of<00:09:07.300> provisions<00:09:08.680> so<00:09:09.680> the<00:09:09.860> sensitive 00:09:10.360 --> 00:09:10.370 align:start position:0% bunch of provisions so the sensitive 00:09:10.370 --> 00:09:13.510 align:start position:0% bunch of provisions so the sensitive trains<00:09:10.640> should<00:09:10.880> be<00:09:11.000> applied<00:09:11.300> at<00:09:12.130> every<00:09:13.130> pair 00:09:13.510 --> 00:09:13.520 align:start position:0% trains should be applied at every pair 00:09:13.520 --> 00:09:17.800 align:start position:0% trains should be applied at every pair of<00:09:13.580> steps<00:09:13.970> or<00:09:14.300> for<00:09:15.050> example<00:09:15.440> each<00:09:15.560> every<00:09:16.810> the 00:09:17.800 --> 00:09:17.810 align:start position:0% of steps or for example each every the 00:09:17.810 --> 00:09:19.420 align:start position:0% of steps or for example each every the decent<00:09:18.200> between<00:09:18.440> the<00:09:18.530> services<00:09:19.190> should<00:09:19.370> be 00:09:19.420 --> 00:09:19.430 align:start position:0% decent between the services should be 00:09:19.430 --> 00:09:22.690 align:start position:0% decent between the services should be able<00:09:19.730> to<00:09:20.000> one<00:09:20.330> or<00:09:20.900> two<00:09:21.230> but<00:09:21.710> this<00:09:22.490> would<00:09:22.670> be 00:09:22.690 --> 00:09:22.700 align:start position:0% able to one or two but this would be 00:09:22.700 --> 00:09:25.990 align:start position:0% able to one or two but this would be some<00:09:23.000> kind<00:09:23.210> of<00:09:23.270> a<00:09:23.390> bejeweled<00:09:23.630> party<00:09:24.850> so<00:09:25.850> guess 00:09:25.990 --> 00:09:26.000 align:start position:0% some kind of a bejeweled party so guess 00:09:26.000 --> 00:09:27.500 align:start position:0% some kind of a bejeweled party so guess how<00:09:26.180> many<00:09:26.360> of<00:09:26.420> you<00:09:26.540> are<00:09:26.570> familiar<00:09:26.780> with 00:09:27.500 --> 00:09:27.510 align:start position:0% how many of you are familiar with 00:09:27.510 --> 00:09:36.670 align:start position:0% how many of you are familiar with miss<00:09:27.750> Frances<00:09:30.830> he<00:09:32.570> was<00:09:33.570> in<00:09:33.690> the<00:09:33.780> campaign 00:09:36.670 --> 00:09:36.680 align:start position:0% 00:09:36.680 --> 00:09:38.950 align:start position:0% doesn't<00:09:37.680> make<00:09:37.920> any<00:09:38.100> sense 00:09:38.950 --> 00:09:38.960 align:start position:0% doesn't make any sense 00:09:38.960 --> 00:09:43.120 align:start position:0% doesn't make any sense yeah<00:09:39.960> and<00:09:40.200> the<00:09:40.350> witness<00:09:40.680> the<00:09:40.890> witness<00:09:41.120> is<00:09:42.120> just 00:09:43.120 --> 00:09:43.130 align:start position:0% yeah and the witness the witness is just 00:09:43.130 --> 00:09:49.190 align:start position:0% yeah and the witness the witness is just the<00:09:44.330> particular<00:09:45.330> instance<00:09:45.750> of<00:09:45.900> matrix<00:09:48.200> the 00:09:49.190 --> 00:09:49.200 align:start position:0% the particular instance of matrix the 00:09:49.200 --> 00:09:54.020 align:start position:0% the particular instance of matrix the bells<00:09:49.440> of<00:09:49.620> the<00:09:49.650> matrix<00:09:50.100> are<00:09:50.430> just<00:09:50.940> I<00:09:52.040> taken<00:09:53.040> saw 00:09:54.020 --> 00:09:54.030 align:start position:0% bells of the matrix are just I taken saw 00:09:54.030 --> 00:09:57.080 align:start position:0% bells of the matrix are just I taken saw that<00:09:54.270> those<00:09:54.930> relations<00:09:55.530> will<00:09:55.740> revolt<00:09:56.160> that's 00:09:57.080 --> 00:09:57.090 align:start position:0% that those relations will revolt that's 00:09:57.090 --> 00:09:59.480 align:start position:0% that those relations will revolt that's it 00:09:59.480 --> 00:09:59.490 align:start position:0% 00:09:59.490 --> 00:10:02.890 align:start position:0% by<00:10:00.060> the<00:10:00.120> way<00:10:00.300> I<00:10:00.330> have<00:10:00.630> only<00:10:00.830> spoken<00:10:01.830> of 00:10:02.890 --> 00:10:02.900 align:start position:0% by the way I have only spoken of 00:10:02.900 --> 00:10:06.110 align:start position:0% by the way I have only spoken of tradesmen<00:10:03.900> strengths<00:10:04.410> another<00:10:05.370> thing<00:10:05.610> is<00:10:05.850> how 00:10:06.110 --> 00:10:06.120 align:start position:0% tradesmen strengths another thing is how 00:10:06.120 --> 00:10:09.620 align:start position:0% tradesmen strengths another thing is how to<00:10:06.540> embed<00:10:06.920> bubble<00:10:07.920> inputs<00:10:08.310> and<00:10:09.090> this<00:10:09.240> is<00:10:09.360> junk 00:10:09.620 --> 00:10:09.630 align:start position:0% to embed bubble inputs and this is junk 00:10:09.630 --> 00:10:12.560 align:start position:0% to embed bubble inputs and this is junk by<00:10:10.010> boundary<00:10:11.010> constraints<00:10:11.610> there<00:10:12.360> are<00:10:12.450> just 00:10:12.560 --> 00:10:12.570 align:start position:0% by boundary constraints there are just 00:10:12.570 --> 00:10:15.380 align:start position:0% by boundary constraints there are just two<00:10:12.810> bowls<00:10:13.050> of<00:10:13.400> coordinates<00:10:14.400> and<00:10:14.670> well<00:10:15.150> the 00:10:15.380 --> 00:10:15.390 align:start position:0% two bowls of coordinates and well the 00:10:15.390 --> 00:10:17.480 align:start position:0% two bowls of coordinates and well the first<00:10:15.600> coordinate<00:10:15.900> is<00:10:16.080> just<00:10:16.380> at<00:10:16.830> the<00:10:16.950> step<00:10:17.220> and 00:10:17.480 --> 00:10:17.490 align:start position:0% first coordinate is just at the step and 00:10:17.490 --> 00:10:20.900 align:start position:0% first coordinate is just at the step and we<00:10:18.270> two<00:10:18.510> to<00:10:18.840> a<00:10:18.870> boil<00:10:19.170> boundary<00:10:19.740> gas<00:10:19.920> trade<00:10:20.130> the 00:10:20.900 --> 00:10:20.910 align:start position:0% we two to a boil boundary gas trade the 00:10:20.910 --> 00:10:22.490 align:start position:0% we two to a boil boundary gas trade the next<00:10:21.180> quadrant<00:10:21.390> is<00:10:21.720> the<00:10:21.750> Nano<00:10:22.080> greatest 00:10:22.490 --> 00:10:22.500 align:start position:0% next quadrant is the Nano greatest 00:10:22.500 --> 00:10:26.330 align:start position:0% next quadrant is the Nano greatest strength<00:10:23.300> and<00:10:24.300> the<00:10:24.990> value<00:10:25.260> by<00:10:25.440> one<00:10:25.710> so<00:10:26.190> the 00:10:26.330 --> 00:10:26.340 align:start position:0% strength and the value by one so the 00:10:26.340 --> 00:10:29.330 align:start position:0% strength and the value by one so the body<00:10:26.520> constraints<00:10:27.090> just<00:10:27.420> says<00:10:27.720> that<00:10:28.340> the 00:10:29.330 --> 00:10:29.340 align:start position:0% body constraints just says that the 00:10:29.340 --> 00:10:32.930 align:start position:0% body constraints just says that the value<00:10:29.730> of<00:10:29.900> these<00:10:30.900> self<00:10:31.170> matrix<00:10:31.650> is<00:10:31.920> ever<00:10:32.340> this 00:10:32.930 --> 00:10:32.940 align:start position:0% value of these self matrix is ever this 00:10:32.940 --> 00:10:40.150 align:start position:0% value of these self matrix is ever this is<00:10:33.000> bicycle<00:10:33.600> I<00:10:35.930> think<00:10:36.930> the<00:10:37.350> next<00:10:37.590> one 00:10:40.150 --> 00:10:40.160 align:start position:0% 00:10:40.160 --> 00:10:44.930 align:start position:0% go<00:10:41.160> back<00:10:41.310> with<00:10:41.490> this<00:10:41.610> guy<00:10:41.790> that's<00:10:42.120> nice<00:10:43.940> this 00:10:44.930 --> 00:10:44.940 align:start position:0% go back with this guy that's nice this 00:10:44.940 --> 00:10:50.180 align:start position:0% go back with this guy that's nice this is<00:10:45.090> an<00:10:45.210> excellent<00:10:46.910> can<00:10:47.910> you<00:10:47.970> go<00:10:48.060> back 00:10:50.180 --> 00:10:50.190 align:start position:0% is an excellent can you go back 00:10:50.190 --> 00:10:55.850 align:start position:0% is an excellent can you go back yeah<00:10:51.089> just<00:10:51.680> simple<00:10:52.680> sentence<00:10:53.009> you<00:10:53.629> in<00:10:54.860> your 00:10:55.850 --> 00:10:55.860 align:start position:0% yeah just simple sentence you in your 00:10:55.860 --> 00:10:57.800 align:start position:0% yeah just simple sentence you in your constraints<00:10:56.629> constraint<00:10:57.629> should<00:10:57.660> be 00:10:57.800 --> 00:10:57.810 align:start position:0% constraints constraint should be 00:10:57.810 --> 00:11:06.220 align:start position:0% constraints constraint should be satisfied<00:10:57.959> and 00:11:06.220 --> 00:11:06.230 align:start position:0% 00:11:06.230 --> 00:11:09.079 align:start position:0% because<00:11:07.230> E<00:11:07.470> is<00:11:07.499> a<00:11:07.679> function<00:11:07.799> every<00:11:08.579> element<00:11:08.879> of 00:11:09.079 --> 00:11:09.089 align:start position:0% because E is a function every element of 00:11:09.089 --> 00:11:10.819 align:start position:0% because E is a function every element of is<00:11:09.359> it<00:11:09.480> is<00:11:09.689> a<00:11:09.720> functioning<00:11:10.290> in<00:11:10.410> two<00:11:10.589> double 00:11:10.819 --> 00:11:10.829 align:start position:0% is it is a functioning in two double 00:11:10.829 --> 00:11:13.549 align:start position:0% is it is a functioning in two double variables<00:11:11.249> and<00:11:11.600> the<00:11:12.600> first<00:11:12.809> half<00:11:13.019> variables 00:11:13.549 --> 00:11:13.559 align:start position:0% variables and the first half variables 00:11:13.559 --> 00:11:17.210 align:start position:0% variables and the first half variables is<00:11:13.769> the<00:11:14.100> previous<00:11:14.899> are<00:11:15.899> all<00:11:16.049> matrix<00:11:16.559> and<00:11:16.859> the 00:11:17.210 --> 00:11:17.220 align:start position:0% is the previous are all matrix and the 00:11:17.220 --> 00:11:19.609 align:start position:0% is the previous are all matrix and the next<00:11:17.459> one<00:11:17.609> is<00:11:17.850> the<00:11:18.089> next<00:11:18.449> row<00:11:18.569> this<00:11:19.199> is<00:11:19.259> what<00:11:19.499> is 00:11:19.609 --> 00:11:19.619 align:start position:0% next one is the next row this is what is 00:11:19.619 --> 00:11:21.639 align:start position:0% next one is the next row this is what is original 00:11:21.639 --> 00:11:21.649 align:start position:0% original 00:11:21.649 --> 00:11:27.679 align:start position:0% original it<00:11:22.649> was<00:11:22.889> like<00:11:23.129> any<00:11:23.429> questions<00:11:25.369> okay<00:11:26.509> the<00:11:27.509> next 00:11:27.679 --> 00:11:27.689 align:start position:0% it was like any questions okay the next 00:11:27.689 --> 00:11:33.679 align:start position:0% it was like any questions okay the next one<00:11:30.439> as<00:11:31.439> well<00:11:31.679> over<00:11:31.799> the<00:11:32.009> best<00:11:32.249> way<00:11:32.549> to<00:11:32.879> encode 00:11:33.679 --> 00:11:33.689 align:start position:0% one as well over the best way to encode 00:11:33.689 --> 00:11:38.019 align:start position:0% one as well over the best way to encode any<00:11:34.259> proof<00:11:34.649> systems<00:11:35.069> is<00:11:35.309> to<00:11:36.089> reduce<00:11:36.359> them<00:11:36.660> to 00:11:38.019 --> 00:11:38.029 align:start position:0% any proof systems is to reduce them to 00:11:38.029 --> 00:11:42.109 align:start position:0% any proof systems is to reduce them to reduce<00:11:39.029> even<00:11:39.899> the<00:11:40.109> witness<00:11:40.439> to<00:11:40.819> animals<00:11:41.819> now 00:11:42.109 --> 00:11:42.119 align:start position:0% reduce even the witness to animals now 00:11:42.119 --> 00:11:45.379 align:start position:0% reduce even the witness to animals now we<00:11:42.179> have<00:11:42.449> just<00:11:43.459> the<00:11:44.459> boundary<00:11:44.759> constrains<00:11:45.299> in 00:11:45.379 --> 00:11:45.389 align:start position:0% we have just the boundary constrains in 00:11:45.389 --> 00:11:46.759 align:start position:0% we have just the boundary constrains in the<00:11:45.480> chest<00:11:45.720> and<00:11:45.959> the<00:11:46.049> trains<00:11:46.319> constraints 00:11:46.759 --> 00:11:46.769 align:start position:0% the chest and the trains constraints 00:11:46.769 --> 00:11:50.389 align:start position:0% the chest and the trains constraints presented<00:11:47.249> in<00:11:47.399> form<00:11:47.669> of<00:11:49.009> polynomials<00:11:50.009> but<00:11:50.189> our 00:11:50.389 --> 00:11:50.399 align:start position:0% presented in form of polynomials but our 00:11:50.399 --> 00:11:53.960 align:start position:0% presented in form of polynomials but our witness<00:11:50.669> is<00:11:50.939> just<00:11:51.239> is<00:11:51.689> just<00:11:51.749> mattress<00:11:52.970> and 00:11:53.960 --> 00:11:53.970 align:start position:0% witness is just is just mattress and 00:11:53.970 --> 00:12:00.099 align:start position:0% witness is just is just mattress and then<00:11:54.209> we<00:11:54.720> need<00:11:54.869> to<00:11:54.989> somehow<00:11:56.209> transform<00:11:57.559> our 00:12:00.099 --> 00:12:00.109 align:start position:0% then we need to somehow transform our 00:12:00.109 --> 00:12:03.789 align:start position:0% then we need to somehow transform our representation<00:12:01.109> into<00:12:01.589> the<00:12:02.339> form<00:12:02.639> which<00:12:02.879> is 00:12:03.789 --> 00:12:03.799 align:start position:0% representation into the form which is 00:12:03.799 --> 00:12:07.249 align:start position:0% representation into the form which is most<00:12:04.799> suitable<00:12:05.129> to<00:12:05.459> oldest<00:12:05.999> just<00:12:06.779> chance 00:12:07.249 --> 00:12:07.259 align:start position:0% most suitable to oldest just chance 00:12:07.259 --> 00:12:12.999 align:start position:0% most suitable to oldest just chance itself<00:12:09.470> and<00:12:10.470> we<00:12:10.589> need<00:12:10.769> the<00:12:11.009> kind<00:12:11.220> of<00:12:11.459> regime 00:12:12.999 --> 00:12:13.009 align:start position:0% itself and we need the kind of regime 00:12:13.009 --> 00:12:17.960 align:start position:0% itself and we need the kind of regime the<00:12:14.009> roti<00:12:14.539> means<00:12:15.539> that<00:12:15.899> we<00:12:16.439> want<00:12:16.589> to<00:12:16.619> blaze<00:12:17.009> the 00:12:17.960 --> 00:12:17.970 align:start position:0% the roti means that we want to blaze the 00:12:17.970 --> 00:12:20.329 align:start position:0% the roti means that we want to blaze the valence<00:12:18.449> of<00:12:18.629> our<00:12:19.109> matrix<00:12:19.439> which<00:12:19.769> is<00:12:19.889> a<00:12:19.919> witness 00:12:20.329 --> 00:12:20.339 align:start position:0% valence of our matrix which is a witness 00:12:20.339 --> 00:12:24.829 align:start position:0% valence of our matrix which is a witness in<00:12:21.119> turn<00:12:21.739> into<00:12:22.739> engine<00:12:23.339> code<00:12:23.489> into<00:12:23.910> integral 00:12:24.829 --> 00:12:24.839 align:start position:0% in turn into engine code into integral 00:12:24.839 --> 00:12:27.279 align:start position:0% in turn into engine code into integral normal<00:12:25.199> again<00:12:26.189> this<00:12:26.429> is<00:12:26.609> just<00:12:26.789> the<00:12:27.029> definition 00:12:27.279 --> 00:12:27.289 align:start position:0% normal again this is just the definition 00:12:27.289 --> 00:12:30.289 align:start position:0% normal again this is just the definition in<00:12:28.289> its<00:12:28.439> books<00:12:28.649> weight<00:12:29.069> and<00:12:29.549> now<00:12:29.759> I<00:12:30.029> will 00:12:30.289 --> 00:12:30.299 align:start position:0% in its books weight and now I will 00:12:30.299 --> 00:12:35.029 align:start position:0% in its books weight and now I will explain<00:12:32.239> what<00:12:33.239> can<00:12:33.449> be<00:12:33.569> done<00:12:33.779> in<00:12:34.619> the<00:12:34.739> see<00:12:34.889> what 00:12:35.029 --> 00:12:35.039 align:start position:0% explain what can be done in the see what 00:12:35.039 --> 00:12:39.949 align:start position:0% explain what can be done in the see what is<00:12:35.279> relative<00:12:36.119> there<00:12:36.209> some<00:12:38.600> some<00:12:39.600> difficulties 00:12:39.949 --> 00:12:39.959 align:start position:0% is relative there some some difficulties 00:12:39.959 --> 00:12:43.309 align:start position:0% is relative there some some difficulties but<00:12:40.799> you<00:12:41.639> know<00:12:41.730> it<00:12:41.879> never<00:12:41.910> nevertheless<00:12:42.600> the 00:12:43.309 --> 00:12:43.319 align:start position:0% but you know it never nevertheless the 00:12:43.319 --> 00:12:47.059 align:start position:0% but you know it never nevertheless the main<00:12:43.529> the<00:12:44.100> main<00:12:44.129> thing<00:12:44.489> is<00:12:44.579> the<00:12:44.699> following<00:12:46.069> we 00:12:47.059 --> 00:12:47.069 align:start position:0% main the main thing is the following we 00:12:47.069 --> 00:12:51.109 align:start position:0% main the main thing is the following we choose<00:12:47.720> two<00:12:48.720> groups<00:12:48.929> I<00:12:49.199> have<00:12:49.649> just<00:12:49.889> our<00:12:50.730> files 00:12:51.109 --> 00:12:51.119 align:start position:0% choose two groups I have just our files 00:12:51.119 --> 00:12:53.300 align:start position:0% choose two groups I have just our files view 00:12:53.300 --> 00:12:53.310 align:start position:0% view 00:12:53.310 --> 00:12:57.850 align:start position:0% view and<00:12:54.199> would<00:12:55.199> take<00:12:55.999> two<00:12:56.999> groups 00:12:57.850 --> 00:12:57.860 align:start position:0% and would take two groups 00:12:57.860 --> 00:13:04.689 align:start position:0% and would take two groups Juwan<00:12:58.889> and<00:12:59.189> the<00:13:00.060> tomb<00:13:00.329> to<00:13:00.689> do<00:13:01.319> inside<00:13:03.620> their 00:13:04.689 --> 00:13:04.699 align:start position:0% Juwan and the tomb to do inside their 00:13:04.699 --> 00:13:07.100 align:start position:0% Juwan and the tomb to do inside their multiplicative<00:13:05.699> sir<00:13:05.970> group<00:13:06.240> must<00:13:06.660> build<00:13:06.839> us<00:13:06.990> a 00:13:07.100 --> 00:13:07.110 align:start position:0% multiplicative sir group must build us a 00:13:07.110 --> 00:13:12.220 align:start position:0% multiplicative sir group must build us a group<00:13:07.290> of<00:13:07.470> our<00:13:07.680> field<00:13:08.009> and<00:13:08.339> the<00:13:09.180> first<00:13:09.449> one 00:13:12.220 --> 00:13:12.230 align:start position:0% 00:13:12.230 --> 00:13:16.389 align:start position:0% should<00:13:13.230> be<00:13:13.290> of<00:13:13.410> size<00:13:13.589> T<00:13:14.689> in<00:13:15.689> the<00:13:15.809> second<00:13:16.139> one 00:13:16.389 --> 00:13:16.399 align:start position:0% should be of size T in the second one 00:13:16.399 --> 00:13:22.460 align:start position:0% should be of size T in the second one should<00:13:17.399> be<00:13:17.550> of<00:13:17.610> size<00:13:18.769> W<00:13:19.769> so<00:13:20.689> in<00:13:21.689> practice<00:13:22.170> we 00:13:22.460 --> 00:13:22.470 align:start position:0% should be of size W so in practice we 00:13:22.470 --> 00:13:27.790 align:start position:0% should be of size W so in practice we want<00:13:23.430> to<00:13:23.819> who<00:13:23.999> want<00:13:24.240> to<00:13:24.569> be<00:13:25.759> the<00:13:26.759> one<00:13:26.970> our<00:13:27.240> field 00:13:27.790 --> 00:13:27.800 align:start position:0% want to who want to be the one our field 00:13:27.800 --> 00:13:32.920 align:start position:0% want to who want to be the one our field to<00:13:28.800> have<00:13:29.009> a<00:13:29.670> lot<00:13:30.420> to<00:13:30.749> a<00:13:30.779> decision<00:13:31.019> so<00:13:31.889> invest 00:13:32.920 --> 00:13:32.930 align:start position:0% to have a lot to a decision so invest 00:13:32.930 --> 00:13:37.850 align:start position:0% to have a lot to a decision so invest its<00:13:33.930> multiplicative<00:13:34.680> group<00:13:36.860> multiplicative 00:13:37.850 --> 00:13:37.860 align:start position:0% its multiplicative group multiplicative 00:13:37.860 --> 00:13:40.540 align:start position:0% its multiplicative group multiplicative group<00:13:38.009> is<00:13:38.279> divided<00:13:38.550> by<00:13:38.790> light<00:13:38.970> power<00:13:39.300> -<00:13:39.600> and 00:13:40.540 --> 00:13:40.550 align:start position:0% group is divided by light power - and 00:13:40.550 --> 00:13:44.960 align:start position:0% group is divided by light power - and our<00:13:41.550> trace<00:13:42.589> length<00:13:43.589> and<00:13:43.949> the<00:13:44.519> number<00:13:44.550> of<00:13:44.850> our 00:13:44.960 --> 00:13:44.970 align:start position:0% our trace length and the number of our 00:13:44.970 --> 00:13:47.809 align:start position:0% our trace length and the number of our editors<00:13:45.180> to<00:13:45.600> be<00:13:45.749> a<00:13:45.779> positive<00:13:46.170> tone<00:13:46.559> so<00:13:46.920> if<00:13:47.670> it 00:13:47.809 --> 00:13:47.819 align:start position:0% editors to be a positive tone so if it 00:13:47.819 --> 00:13:49.280 align:start position:0% editors to be a positive tone so if it is<00:13:47.939> not<00:13:48.089> the<00:13:48.180> case<00:13:48.389> we're<00:13:48.689> going<00:13:48.809> to<00:13:48.870> simply 00:13:49.280 --> 00:13:49.290 align:start position:0% is not the case we're going to simply 00:13:49.290 --> 00:13:57.980 align:start position:0% is not the case we're going to simply exchange<00:13:49.920> more<00:13:50.459> practice<00:13:50.999> with<00:13:51.839> it<00:13:55.100> then<00:13:56.990> and 00:13:57.980 --> 00:13:57.990 align:start position:0% exchange more practice with it then and 00:13:57.990 --> 00:14:01.280 align:start position:0% exchange more practice with it then and when<00:13:58.699> do<00:13:59.699> you<00:13:59.759> want<00:14:00.000> be<00:14:00.509> the<00:14:00.779> junior<00:14:01.019> age<00:14:01.110> of 00:14:01.280 --> 00:14:01.290 align:start position:0% when do you want be the junior age of 00:14:01.290 --> 00:14:08.809 align:start position:0% when do you want be the junior age of the<00:14:01.379> first<00:14:01.589> group<00:14:01.800> and<00:14:07.069> Jesus<00:14:08.069> the<00:14:08.579> first 00:14:08.809 --> 00:14:08.819 align:start position:0% the first group and Jesus the first 00:14:08.819 --> 00:14:13.699 align:start position:0% the first group and Jesus the first group<00:14:09.029> and<00:14:09.379> nu<00:14:10.379> is<00:14:10.709> the<00:14:10.829> generator<00:14:11.339> sexual<00:14:12.709> and 00:14:13.699 --> 00:14:13.709 align:start position:0% group and nu is the generator sexual and 00:14:13.709 --> 00:14:19.220 align:start position:0% group and nu is the generator sexual and we<00:14:14.279> just<00:14:16.069> really<00:14:17.069> rate<00:14:17.250> our<00:14:17.839> seven<00:14:18.839> the<00:14:19.050> size 00:14:19.220 --> 00:14:19.230 align:start position:0% we just really rate our seven the size 00:14:19.230 --> 00:14:23.540 align:start position:0% we just really rate our seven the size of<00:14:19.350> a<00:14:19.439> matrix<00:14:19.649> with<00:14:21.379> elements<00:14:22.399> generated<00:14:23.399> by 00:14:23.540 --> 00:14:23.550 align:start position:0% of a matrix with elements generated by 00:14:23.550 --> 00:14:25.929 align:start position:0% of a matrix with elements generated by these<00:14:23.730> two<00:14:23.879> groups<00:14:24.029> at<00:14:24.779> least<00:14:25.079> self-adjust 00:14:25.929 --> 00:14:25.939 align:start position:0% these two groups at least self-adjust 00:14:25.939 --> 00:14:32.900 align:start position:0% these two groups at least self-adjust Shaban<00:14:27.949> 1<00:14:28.949> raised<00:14:29.189> to<00:14:29.220> to<00:14:29.639> him<00:14:31.339> and<00:14:32.339> so<00:14:32.519> on<00:14:32.550> and 00:14:32.900 --> 00:14:32.910 align:start position:0% Shaban 1 raised to to him and so on and 00:14:32.910 --> 00:14:51.810 align:start position:0% Shaban 1 raised to to him and so on and this<00:14:33.420> will<00:14:33.629> just<00:14:33.809> use<00:14:34.379> the<00:14:34.920> variable 00:14:51.810 --> 00:14:51.820 align:start position:0% 00:14:51.820 --> 00:15:00.720 align:start position:0% so<00:14:52.330> the<00:14:52.510> cell<00:14:53.220> with<00:14:54.220> index<00:14:54.640> I<00:14:56.490> J<00:14:59.190> when<00:15:00.190> I<00:15:00.220> waited 00:15:00.720 --> 00:15:00.730 align:start position:0% so the cell with index I J when I waited 00:15:00.730 --> 00:15:07.950 align:start position:0% so the cell with index I J when I waited with<00:15:00.910> G<00:15:04.260> hi 00:15:07.950 --> 00:15:07.960 align:start position:0% 00:15:07.960 --> 00:15:15.590 align:start position:0% you<00:15:08.880> might<00:15:11.730> know<00:15:12.730> this<00:15:13.170> your<00:15:14.170> hitch<00:15:14.710> the<00:15:14.860> idea 00:15:15.590 --> 00:15:15.600 align:start position:0% you might know this your hitch the idea 00:15:15.600 --> 00:15:18.840 align:start position:0% you might know this your hitch the idea and<00:15:16.600> then<00:15:16.810> then<00:15:17.290> then<00:15:17.680> I<00:15:17.980> will<00:15:18.460> take<00:15:18.640> the 00:15:18.840 --> 00:15:18.850 align:start position:0% and then then then I will take the 00:15:18.850 --> 00:15:29.070 align:start position:0% and then then then I will take the function<00:15:19.240> f<00:15:19.420> on<00:15:20.370> the<00:15:21.370> domain<00:15:25.650> g1<00:15:26.650> plus<00:15:27.040> g2<00:15:28.080> to 00:15:29.070 --> 00:15:29.080 align:start position:0% function f on the domain g1 plus g2 to 00:15:29.080 --> 00:15:33.750 align:start position:0% function f on the domain g1 plus g2 to have<00:15:29.230> this<00:15:29.560> varies<00:15:29.920> in<00:15:30.160> L<00:15:31.890> and<00:15:32.890> the<00:15:33.370> where<00:15:33.580> they 00:15:33.750 --> 00:15:33.760 align:start position:0% have this varies in L and the where they 00:15:33.760 --> 00:15:41.220 align:start position:0% have this varies in L and the where they are<00:15:33.850> on<00:15:34.770> three<00:15:35.770> I<00:15:36.750> minus<00:15:37.750> 1<00:15:38.430> J<00:15:39.430> minus<00:15:39.940> 1<00:15:40.510> would 00:15:41.220 --> 00:15:41.230 align:start position:0% are on three I minus 1 J minus 1 would 00:15:41.230 --> 00:15:49.050 align:start position:0% are on three I minus 1 J minus 1 would be<00:15:41.290> just<00:15:41.590> a<00:15:41.710> well<00:15:44.850> then<00:15:45.850> see<00:15:46.320> how<00:15:47.320> to<00:15:47.380> whom<00:15:48.060> and 00:15:49.050 --> 00:15:49.060 align:start position:0% be just a well then see how to whom and 00:15:49.060 --> 00:15:51.390 align:start position:0% be just a well then see how to whom and this<00:15:49.240> is<00:15:49.360> this<00:15:49.900> will<00:15:50.050> be<00:15:50.140> our<00:15:50.260> witness<00:15:50.680> yeah 00:15:51.390 --> 00:15:51.400 align:start position:0% this is this will be our witness yeah 00:15:51.400 --> 00:15:56.010 align:start position:0% this is this will be our witness yeah just<00:15:51.730> just<00:15:52.180> for<00:15:52.860> this<00:15:53.860> is<00:15:54.010> very<00:15:54.220> for<00:15:54.870> this<00:15:55.870> is<00:15:55.990> a 00:15:56.010 --> 00:15:56.020 align:start position:0% just just for this is very for this is a 00:15:56.020 --> 00:15:57.510 align:start position:0% just just for this is very for this is a very<00:15:56.170> formal<00:15:56.380> definition<00:15:56.980> of<00:15:57.010> presence<00:15:57.460> and 00:15:57.510 --> 00:15:57.520 align:start position:0% very formal definition of presence and 00:15:57.520 --> 00:15:59.040 align:start position:0% very formal definition of presence and once<00:15:57.910> you<00:15:58.030> do<00:15:58.150> some<00:15:58.270> practical<00:15:58.600> application 00:15:59.040 --> 00:15:59.050 align:start position:0% once you do some practical application 00:15:59.050 --> 00:16:00.780 align:start position:0% once you do some practical application of<00:15:59.080> this<00:15:59.260> and<00:15:59.860> just<00:16:00.040> understand<00:16:00.430> how<00:16:00.460> this 00:16:00.780 --> 00:16:00.790 align:start position:0% of this and just understand how this 00:16:00.790 --> 00:16:03.030 align:start position:0% of this and just understand how this works<00:16:00.970> its<00:16:01.570> formal<00:16:01.930> definition<00:16:02.440> it<00:16:02.620> just<00:16:02.830> says 00:16:03.030 --> 00:16:03.040 align:start position:0% works its formal definition it just says 00:16:03.040 --> 00:16:07.050 align:start position:0% works its formal definition it just says take<00:16:03.940> every<00:16:04.300> row<00:16:05.220> contain<00:16:06.220> a<00:16:06.310> simple<00:16:06.550> together 00:16:07.050 --> 00:16:07.060 align:start position:0% take every row contain a simple together 00:16:07.060 --> 00:16:09.920 align:start position:0% take every row contain a simple together and<00:16:07.420> do<00:16:07.960> the<00:16:08.020> interpolation<00:16:08.460> over<00:16:09.460> the 00:16:09.920 --> 00:16:09.930 align:start position:0% and do the interpolation over the 00:16:09.930 --> 00:16:12.960 align:start position:0% and do the interpolation over the multiple<00:16:10.930> kids<00:16:11.110> have<00:16:11.320> group<00:16:11.500> in<00:16:11.740> a<00:16:11.800> prime<00:16:12.730> fell 00:16:12.960 --> 00:16:12.970 align:start position:0% multiple kids have group in a prime fell 00:16:12.970 --> 00:16:17.280 align:start position:0% multiple kids have group in a prime fell it's<00:16:13.660> just<00:16:14.020> very<00:16:14.140> simple<00:16:15.120> well<00:16:16.120> you<00:16:16.750> can<00:16:17.080> see 00:16:17.280 --> 00:16:17.290 align:start position:0% it's just very simple well you can see 00:16:17.290 --> 00:16:19.050 align:start position:0% it's just very simple well you can see you<00:16:17.530> can<00:16:17.680> see<00:16:17.920> the<00:16:18.130> same<00:16:18.340> structure<00:16:18.760> in<00:16:18.790> many 00:16:19.050 --> 00:16:19.060 align:start position:0% you can see the same structure in many 00:16:19.060 --> 00:16:20.730 align:start position:0% you can see the same structure in many systems<00:16:19.780> where<00:16:19.960> you<00:16:19.990> want<00:16:20.290> to<00:16:20.380> encode<00:16:20.590> you 00:16:20.730 --> 00:16:20.740 align:start position:0% systems where you want to encode you 00:16:20.740 --> 00:16:21.370 align:start position:0% systems where you want to encode you witness 00:16:21.370 --> 00:16:21.380 align:start position:0% witness 00:16:21.380 --> 00:16:24.139 align:start position:0% witness so<00:16:22.380> you<00:16:22.440> literally<00:16:23.040> place<00:16:23.459> your<00:16:23.820> witness 00:16:24.139 --> 00:16:24.149 align:start position:0% so you literally place your witness 00:16:24.149 --> 00:16:26.960 align:start position:0% so you literally place your witness values<00:16:24.560> you<00:16:25.560> think<00:16:25.830> is<00:16:26.100> ever<00:16:26.250> existed<00:16:26.730> witness 00:16:26.960 --> 00:16:26.970 align:start position:0% values you think is ever existed witness 00:16:26.970 --> 00:16:29.000 align:start position:0% values you think is ever existed witness political<00:16:27.510> and<00:16:27.839> I<00:16:27.930> want<00:16:28.140> to<00:16:28.200> require<00:16:28.560> all<00:16:28.860> this 00:16:29.000 --> 00:16:29.010 align:start position:0% political and I want to require all this 00:16:29.010 --> 00:16:30.769 align:start position:0% political and I want to require all this as<00:16:29.279> witness<00:16:29.610> bullying<00:16:29.820> develop<00:16:30.270> on<00:16:30.360> certain 00:16:30.769 --> 00:16:30.779 align:start position:0% as witness bullying develop on certain 00:16:30.779 --> 00:16:32.660 align:start position:0% as witness bullying develop on certain points<00:16:30.959> to<00:16:31.680> be<00:16:31.830> pulled<00:16:32.070> to<00:16:32.190> my<00:16:32.310> witness 00:16:32.660 --> 00:16:32.670 align:start position:0% points to be pulled to my witness 00:16:32.670 --> 00:16:35.510 align:start position:0% points to be pulled to my witness volumes<00:16:33.089> here<00:16:33.839> use<00:16:34.170> the<00:16:34.320> same<00:16:34.560> just<00:16:34.980> take<00:16:35.339> your 00:16:35.510 --> 00:16:35.520 align:start position:0% volumes here use the same just take your 00:16:35.520 --> 00:16:37.100 align:start position:0% volumes here use the same just take your video<00:16:35.610> to<00:16:35.970> continue<00:16:36.120> can<00:16:36.600> fit<00:16:36.779> the<00:16:36.839> needs<00:16:37.020> of 00:16:37.100 --> 00:16:37.110 align:start position:0% video to continue can fit the needs of 00:16:37.110 --> 00:16:39.079 align:start position:0% video to continue can fit the needs of all<00:16:37.290> together<00:16:37.440> you<00:16:38.130> get<00:16:38.250> to<00:16:38.430> pull<00:16:38.610> remember 00:16:39.079 --> 00:16:39.089 align:start position:0% all together you get to pull remember 00:16:39.089 --> 00:16:40.850 align:start position:0% all together you get to pull remember you<00:16:39.149> do<00:16:39.360> you<00:16:39.690> get<00:16:39.810> set<00:16:40.080> up<00:16:40.110> Wallace<00:16:40.500> which<00:16:40.709> is 00:16:40.850 --> 00:16:40.860 align:start position:0% you do you get set up Wallace which is 00:16:40.860 --> 00:16:44.780 align:start position:0% you do you get set up Wallace which is size<00:16:41.160> T<00:16:41.459> by<00:16:41.640> W<00:16:42.060> so<00:16:42.779> you<00:16:42.810> just<00:16:43.200> need<00:16:43.350> to<00:16:43.790> salute 00:16:44.780 --> 00:16:44.790 align:start position:0% size T by W so you just need to salute 00:16:44.790 --> 00:16:47.060 align:start position:0% size T by W so you just need to salute which<00:16:45.029> is<00:16:45.180> T<00:16:45.300> by<00:16:45.330> double<00:16:45.720> size<00:16:46.050> and<00:16:46.350> just<00:16:46.620> do<00:16:47.040> a 00:16:47.060 --> 00:16:47.070 align:start position:0% which is T by double size and just do a 00:16:47.070 --> 00:16:48.949 align:start position:0% which is T by double size and just do a simple<00:16:47.310> manipulation<00:16:47.730> which<00:16:48.149> is<00:16:48.270> that<00:16:48.450> just<00:16:48.839> a 00:16:48.949 --> 00:16:48.959 align:start position:0% simple manipulation which is that just a 00:16:48.959 --> 00:16:51.410 align:start position:0% simple manipulation which is that just a fast<00:16:49.709> Fourier<00:16:49.980> transformation<00:16:50.640> it's<00:16:51.149> from 00:16:51.410 --> 00:16:51.420 align:start position:0% fast Fourier transformation it's from 00:16:51.420 --> 00:16:53.900 align:start position:0% fast Fourier transformation it's from some<00:16:51.630> practical<00:16:51.990> perspective<00:16:52.709> and<00:16:53.250> less<00:16:53.790> the 00:16:53.900 --> 00:16:53.910 align:start position:0% some practical perspective and less the 00:16:53.910 --> 00:16:55.639 align:start position:0% some practical perspective and less the formal<00:16:54.209> information<00:16:54.390> even<00:16:55.110> this<00:16:55.230> one<00:16:55.440> doesn't 00:16:55.639 --> 00:16:55.649 align:start position:0% formal information even this one doesn't 00:16:55.649 --> 00:17:00.470 align:start position:0% formal information even this one doesn't shows<00:16:56.300> old<00:16:57.300> essence<00:16:57.830> well<00:16:58.830> this<00:16:59.130> one<00:16:59.279> is<00:16:59.490> too 00:17:00.470 --> 00:17:00.480 align:start position:0% shows old essence well this one is too 00:17:00.480 --> 00:17:02.329 align:start position:0% shows old essence well this one is too complicated<00:17:00.930> explanation<00:17:01.440> or<00:17:01.920> actually<00:17:02.220> how 00:17:02.329 --> 00:17:02.339 align:start position:0% complicated explanation or actually how 00:17:02.339 --> 00:17:02.900 align:start position:0% complicated explanation or actually how it<00:17:02.520> works 00:17:02.900 --> 00:17:02.910 align:start position:0% it works 00:17:02.910 --> 00:17:04.699 align:start position:0% it works the<00:17:03.149> simplest<00:17:03.480> one<00:17:03.690> this<00:17:03.990> is<00:17:04.170> just<00:17:04.470> two 00:17:04.699 --> 00:17:04.709 align:start position:0% the simplest one this is just two 00:17:04.709 --> 00:17:06.949 align:start position:0% the simplest one this is just two interpolation<00:17:05.339> Ginga<00:17:06.030> Adriatic<00:17:06.689> always 00:17:06.949 --> 00:17:06.959 align:start position:0% interpolation Ginga Adriatic always 00:17:06.959 --> 00:17:09.559 align:start position:0% interpolation Ginga Adriatic always points<00:17:07.410> it<00:17:08.100> treats<00:17:08.370> an<00:17:08.520> old<00:17:08.760> visit<00:17:09.089> like<00:17:09.270> while 00:17:09.559 --> 00:17:09.569 align:start position:0% points it treats an old visit like while 00:17:09.569 --> 00:17:11.980 align:start position:0% points it treats an old visit like while used<00:17:09.809> as<00:17:10.050> a<00:17:10.079> point<00:17:10.470> this<00:17:10.800> is<00:17:10.980> a<00:17:11.010> point<00:17:11.100> and 00:17:11.980 --> 00:17:11.990 align:start position:0% used as a point this is a point and 00:17:11.990 --> 00:17:14.179 align:start position:0% used as a point this is a point and while<00:17:12.990> the<00:17:13.170> previous<00:17:13.350> matrix<00:17:13.650> contains 00:17:14.179 --> 00:17:14.189 align:start position:0% while the previous matrix contains 00:17:14.189 --> 00:17:16.790 align:start position:0% while the previous matrix contains evaluated<00:17:14.880> at<00:17:14.970> this<00:17:15.510> point<00:17:15.839> is<00:17:16.439> this<00:17:16.589> view 00:17:16.790 --> 00:17:16.800 align:start position:0% evaluated at this point is this view 00:17:16.800 --> 00:17:18.309 align:start position:0% evaluated at this point is this view requirement<00:17:17.400> for<00:17:17.490> polynomial<00:17:18.030> and<00:17:18.209> you 00:17:18.309 --> 00:17:18.319 align:start position:0% requirement for polynomial and you 00:17:18.319 --> 00:17:21.169 align:start position:0% requirement for polynomial and you strictly<00:17:19.319> defined<00:17:19.620> simple<00:17:19.949> integral<00:17:20.250> of<00:17:20.370> GP<00:17:20.699> t 00:17:21.169 --> 00:17:21.179 align:start position:0% strictly defined simple integral of GP t 00:17:21.179 --> 00:17:23.569 align:start position:0% strictly defined simple integral of GP t by<00:17:21.329> W<00:17:21.689> minus<00:17:21.750> one<00:17:22.199> developed<00:17:22.949> by<00:17:23.040> double<00:17:23.339> point 00:17:23.569 --> 00:17:23.579 align:start position:0% by W minus one developed by double point 00:17:23.579 --> 00:17:26.449 align:start position:0% by W minus one developed by double point success<00:17:24.240> and<00:17:25.010> optimization<00:17:26.010> optimized 00:17:26.449 --> 00:17:26.459 align:start position:0% success and optimization optimized 00:17:26.459 --> 00:17:28.490 align:start position:0% success and optimization optimized applications<00:17:27.089> I<00:17:27.360> don't<00:17:27.929> think<00:17:28.140> you<00:17:28.230> can<00:17:28.380> put 00:17:28.490 --> 00:17:28.500 align:start position:0% applications I don't think you can put 00:17:28.500 --> 00:17:30.020 align:start position:0% applications I don't think you can put an<00:17:28.620> eight<00:17:28.740> all<00:17:28.890> together<00:17:29.040> because<00:17:29.580> this<00:17:29.880> is 00:17:30.020 --> 00:17:30.030 align:start position:0% an eight all together because this is 00:17:30.030 --> 00:17:33.110 align:start position:0% an eight all together because this is going<00:17:30.270> to<00:17:30.390> be<00:17:30.540> a<00:17:30.900> large<00:17:31.410> single<00:17:31.920> fifteen<00:17:32.429> you 00:17:33.110 --> 00:17:33.120 align:start position:0% going to be a large single fifteen you 00:17:33.120 --> 00:17:36.230 align:start position:0% going to be a large single fifteen you can<00:17:33.270> say<00:17:33.510> I<00:17:33.870> will<00:17:34.440> have<00:17:34.470> not<00:17:34.920> one<00:17:35.190> but<00:17:35.460> W 00:17:36.230 --> 00:17:36.240 align:start position:0% can say I will have not one but W 00:17:36.240 --> 00:17:38.780 align:start position:0% can say I will have not one but W witness<00:17:36.929> bullet<00:17:37.200> or<00:17:37.320> else<00:17:37.500> this<00:17:38.010> doesn't 00:17:38.780 --> 00:17:38.790 align:start position:0% witness bullet or else this doesn't 00:17:38.790 --> 00:17:41.840 align:start position:0% witness bullet or else this doesn't change<00:17:38.820> a<00:17:39.120> start<00:17:39.809> and<00:17:40.160> you<00:17:41.160> see<00:17:41.340> my<00:17:41.550> witness 00:17:41.840 --> 00:17:41.850 align:start position:0% change a start and you see my witness 00:17:41.850 --> 00:17:44.330 align:start position:0% change a start and you see my witness polynomial<00:17:42.390> number<00:17:43.080> one<00:17:43.410> it's<00:17:43.890> just<00:17:44.070> for 00:17:44.330 --> 00:17:44.340 align:start position:0% polynomial number one it's just for 00:17:44.340 --> 00:17:47.600 align:start position:0% polynomial number one it's just for register<00:17:44.940> number<00:17:45.179> one<00:17:45.330> so<00:17:46.140> you<00:17:46.230> do<00:17:46.610> larger 00:17:47.600 --> 00:17:47.610 align:start position:0% register number one so you do larger 00:17:47.610 --> 00:17:49.610 align:start position:0% register number one so you do larger number<00:17:48.030> of<00:17:48.059> interpolations<00:17:48.870> but<00:17:49.350> each<00:17:49.590> of 00:17:49.610 --> 00:17:49.620 align:start position:0% number of interpolations but each of 00:17:49.620 --> 00:17:50.540 align:start position:0% number of interpolations but each of those<00:17:49.920> is<00:17:49.980> going 00:17:50.540 --> 00:17:50.550 align:start position:0% those is going 00:17:50.550 --> 00:17:52.550 align:start position:0% those is going my<00:17:50.880> smaller<00:17:51.240> size<00:17:51.540> is<00:17:52.050> this<00:17:52.230> a<00:17:52.260> solid 00:17:52.550 --> 00:17:52.560 align:start position:0% my smaller size is this a solid 00:17:52.560 --> 00:17:53.990 align:start position:0% my smaller size is this a solid immunization<00:17:53.280> which<00:17:53.400> is<00:17:53.520> used<00:17:53.730> everywhere 00:17:53.990 --> 00:17:54.000 align:start position:0% immunization which is used everywhere 00:17:54.000 --> 00:17:57.380 align:start position:0% immunization which is used everywhere which<00:17:54.420> is<00:17:54.510> used<00:17:54.690> by<00:17:54.750> Stanford<00:17:55.230> bias<00:17:55.500> by<00:17:56.390> the 00:17:57.380 --> 00:17:57.390 align:start position:0% which is used by Stanford bias by the 00:17:57.390 --> 00:17:59.210 align:start position:0% which is used by Stanford bias by the Rings<00:17:57.540> guys<00:17:57.840> like<00:17:58.230> this<00:17:58.500> is<00:17:58.680> an<00:17:58.830> efficient<00:17:59.160> way 00:17:59.210 --> 00:17:59.220 align:start position:0% Rings guys like this is an efficient way 00:17:59.220 --> 00:18:01.340 align:start position:0% Rings guys like this is an efficient way to<00:17:59.310> have<00:17:59.640> implemented<00:18:00.060> but<00:18:00.390> here<00:18:00.930> we<00:18:01.050> don't<00:18:01.170> do 00:18:01.340 --> 00:18:01.350 align:start position:0% to have implemented but here we don't do 00:18:01.350 --> 00:18:03.350 align:start position:0% to have implemented but here we don't do too<00:18:01.680> much<00:18:01.860> about<00:18:01.920> optimizations<00:18:02.910> because<00:18:03.270> the 00:18:03.350 --> 00:18:03.360 align:start position:0% too much about optimizations because the 00:18:03.360 --> 00:18:05.930 align:start position:0% too much about optimizations because the right<00:18:03.480> through<00:18:03.660> many<00:18:03.840> of<00:18:03.900> them<00:18:04.080> we<00:18:04.350> really<00:18:04.940> we 00:18:05.930 --> 00:18:05.940 align:start position:0% right through many of them we really we 00:18:05.940 --> 00:18:08.360 align:start position:0% right through many of them we really we just<00:18:05.970> tried<00:18:06.630> to<00:18:06.660> explain<00:18:06.840> them<00:18:07.230> as<00:18:07.890> essence<00:18:08.280> of 00:18:08.360 --> 00:18:08.370 align:start position:0% just tried to explain them as essence of 00:18:08.370 --> 00:18:09.020 align:start position:0% just tried to explain them as essence of the<00:18:08.460> start 00:18:09.020 --> 00:18:09.030 align:start position:0% the start 00:18:09.030 --> 00:18:12.290 align:start position:0% the start you<00:18:09.800> notice<00:18:10.800> the<00:18:10.920> superstar<00:18:11.490> itself<00:18:11.970> is<00:18:12.120> this 00:18:12.290 --> 00:18:12.300 align:start position:0% you notice the superstar itself is this 00:18:12.300 --> 00:18:14.420 align:start position:0% you notice the superstar itself is this common<00:18:12.600> typical<00:18:12.950> sympathises<00:18:13.950> of<00:18:14.250> one 00:18:14.420 --> 00:18:14.430 align:start position:0% common typical sympathises of one 00:18:14.430 --> 00:18:16.280 align:start position:0% common typical sympathises of one eternal<00:18:14.790> and<00:18:15.150> then<00:18:15.420> to<00:18:15.540> have<00:18:15.690> relationships 00:18:16.280 --> 00:18:16.290 align:start position:0% eternal and then to have relationships 00:18:16.290 --> 00:18:17.660 align:start position:0% eternal and then to have relationships about<00:18:16.380> the<00:18:16.680> polynomial<00:18:17.280> incentive 00:18:17.660 --> 00:18:17.670 align:start position:0% about the polynomial incentive 00:18:17.670 --> 00:18:20.450 align:start position:0% about the polynomial incentive relationship<00:18:18.180> model<00:18:18.570> bloggers<00:18:18.900> and<00:18:19.460> concerti 00:18:20.450 --> 00:18:20.460 align:start position:0% relationship model bloggers and concerti 00:18:20.460 --> 00:18:24.520 align:start position:0% relationship model bloggers and concerti will<00:18:20.610> explain<00:18:20.880> the<00:18:21.090> narrative<00:18:21.510> for<00:18:21.690> say<00:18:21.870> the 00:18:24.520 --> 00:18:24.530 align:start position:0% will explain the narrative for say the 00:18:24.530 --> 00:18:29.750 align:start position:0% will explain the narrative for say the last<00:18:25.670> loan<00:18:26.670> equation<00:18:27.210> comes<00:18:27.450> from<00:18:28.340> why<00:18:29.340> to<00:18:29.400> own 00:18:29.750 --> 00:18:29.760 align:start position:0% last loan equation comes from why to own 00:18:29.760 --> 00:18:34.570 align:start position:0% last loan equation comes from why to own just<00:18:30.080> encode<00:18:31.080> this<00:18:31.290> way<00:18:32.270> remember<00:18:33.270> that<00:18:33.450> every 00:18:34.570 --> 00:18:34.580 align:start position:0% just encode this way remember that every 00:18:34.580 --> 00:18:42.550 align:start position:0% just encode this way remember that every trace<00:18:35.580> phenomenal<00:18:40.130> supply<00:18:41.130> to<00:18:41.190> every<00:18:41.670> pair<00:18:41.880> of 00:18:42.550 --> 00:18:42.560 align:start position:0% trace phenomenal supply to every pair of 00:18:42.560 --> 00:18:48.170 align:start position:0% trace phenomenal supply to every pair of of<00:18:43.560> constraints<00:18:45.380> then<00:18:46.380> just<00:18:47.040> what<00:18:48.030> would 00:18:48.170 --> 00:18:48.180 align:start position:0% of constraints then just what would 00:18:48.180 --> 00:18:51.650 align:start position:0% of constraints then just what would happen<00:18:48.570> if<00:18:49.440> rotate<00:18:50.430> we'll<00:18:50.670> take<00:18:50.850> our<00:18:51.000> mask<00:18:51.360> to 00:18:51.650 --> 00:18:51.660 align:start position:0% happen if rotate we'll take our mask to 00:18:51.660 --> 00:18:57.680 align:start position:0% happen if rotate we'll take our mask to be<00:18:51.810> just<00:18:53.180> the<00:18:54.180> consecutive<00:18:54.480> values<00:18:54.840> of<00:18:56.690> the 00:18:57.680 --> 00:18:57.690 align:start position:0% be just the consecutive values of the 00:18:57.690 --> 00:19:00.410 align:start position:0% be just the consecutive values of the group<00:18:57.840> of<00:18:58.410> the<00:18:58.500> second<00:18:58.800> group<00:18:59.150> I'll<00:19:00.150> just 00:19:00.410 --> 00:19:00.420 align:start position:0% group of the second group I'll just 00:19:00.420 --> 00:19:04.030 align:start position:0% group of the second group I'll just write<00:19:01.020> it<00:19:01.200> down 00:19:04.030 --> 00:19:04.040 align:start position:0% 00:19:04.040 --> 00:19:16.890 align:start position:0% and<00:19:06.820> new<00:19:07.900> 1x 00:19:16.890 --> 00:19:16.900 align:start position:0% 00:19:16.900 --> 00:19:19.720 align:start position:0% be 00:19:19.720 --> 00:19:19.730 align:start position:0% be 00:19:19.730 --> 00:19:24.690 align:start position:0% be X 00:19:24.690 --> 00:19:24.700 align:start position:0% 00:19:24.700 --> 00:19:36.370 align:start position:0% yes<00:19:25.080> up<00:19:26.080> to<00:19:26.289> the<00:19:26.379> last<00:19:26.559> one 00:19:36.370 --> 00:19:36.380 align:start position:0% 00:19:36.380 --> 00:19:40.810 align:start position:0% just<00:19:37.990> the<00:19:38.990> previous<00:19:39.500> set<00:19:40.009> of<00:19:40.039> registers<00:19:40.250> and 00:19:40.810 --> 00:19:40.820 align:start position:0% just the previous set of registers and 00:19:40.820 --> 00:19:47.000 align:start position:0% just the previous set of registers and the<00:19:41.330> numinous<00:19:44.889> two<00:19:45.889> 1s 00:19:47.000 --> 00:19:47.010 align:start position:0% the numinous two 1s 00:19:47.010 --> 00:19:54.070 align:start position:0% the numinous two 1s [Music] 00:19:54.070 --> 00:19:54.080 align:start position:0% 00:19:54.080 --> 00:20:03.320 align:start position:0% once<00:19:54.410> we're<00:19:54.830> at<00:19:55.930> X 00:20:03.320 --> 00:20:03.330 align:start position:0% 00:20:03.330 --> 00:20:10.159 align:start position:0% okay<00:20:06.230> so<00:20:07.230> the<00:20:07.409> first<00:20:08.090> form<00:20:09.090> of<00:20:09.210> these<00:20:09.509> album 00:20:10.159 --> 00:20:10.169 align:start position:0% okay so the first form of these album 00:20:10.169 --> 00:20:15.820 align:start position:0% okay so the first form of these album level<00:20:10.470> is<00:20:10.649> into<00:20:11.249> double<00:20:11.519> variables<00:20:12.619> at<00:20:13.619> first 00:20:15.820 --> 00:20:15.830 align:start position:0% level is into double variables at first 00:20:15.830 --> 00:20:20.749 align:start position:0% level is into double variables at first until<00:20:16.830> central<00:20:17.450> where<00:20:18.450> is<00:20:18.659> that<00:20:18.840> we<00:20:19.080> just<00:20:19.759> put 00:20:20.749 --> 00:20:20.759 align:start position:0% until central where is that we just put 00:20:20.759 --> 00:20:23.690 align:start position:0% until central where is that we just put it<00:20:20.909> eponymous<00:20:21.539> air<00:20:22.080> the<00:20:22.799> consecutive<00:20:23.100> pairs 00:20:23.690 --> 00:20:23.700 align:start position:0% it eponymous air the consecutive pairs 00:20:23.700 --> 00:20:28.539 align:start position:0% it eponymous air the consecutive pairs of<00:20:23.940> elements<00:20:24.690> of<00:20:25.049> the<00:20:25.289> second<00:20:25.950> group<00:20:26.070> x<00:20:26.669> x<00:20:27.119> and 00:20:28.539 --> 00:20:28.549 align:start position:0% of elements of the second group x x and 00:20:28.549 --> 00:20:31.539 align:start position:0% of elements of the second group x x and next<00:20:29.549> we<00:20:29.700> just<00:20:29.909> take<00:20:30.360> the<00:20:30.480> same<00:20:30.629> function<00:20:30.840> and 00:20:31.539 --> 00:20:31.549 align:start position:0% next we just take the same function and 00:20:31.549 --> 00:20:34.729 align:start position:0% next we just take the same function and multiply<00:20:32.570> not<00:20:33.570> only<00:20:33.809> the<00:20:33.869> elements<00:20:34.259> of<00:20:34.619> our 00:20:34.729 --> 00:20:34.739 align:start position:0% multiply not only the elements of our 00:20:34.739 --> 00:20:37.039 align:start position:0% multiply not only the elements of our first<00:20:34.980> row<00:20:35.100> but<00:20:35.249> also<00:20:35.460> by<00:20:35.759> the<00:20:36.419> generator<00:20:36.749> of 00:20:37.039 --> 00:20:37.049 align:start position:0% first row but also by the generator of 00:20:37.049 --> 00:20:40.220 align:start position:0% first row but also by the generator of the<00:20:37.320> first<00:20:37.619> row<00:20:37.799> but<00:20:38.549> then<00:20:38.730> what<00:20:39.450> what<00:20:40.049> would 00:20:40.220 --> 00:20:40.230 align:start position:0% the first row but then what what would 00:20:40.230 --> 00:20:47.560 align:start position:0% the first row but then what what would happen<00:20:40.590> if<00:20:40.859> Project<00:20:41.580> X<00:20:43.369> to<00:20:44.369> be<00:20:44.549> just<00:20:46.190> unity 00:20:47.560 --> 00:20:47.570 align:start position:0% happen if Project X to be just unity 00:20:47.570 --> 00:20:54.970 align:start position:0% happen if Project X to be just unity then<00:20:50.059> to<00:20:51.059> be<00:20:51.149> just<00:20:51.389> unity<00:20:52.049> you<00:20:52.320> just<00:20:53.059> filled 00:20:54.970 --> 00:20:54.980 align:start position:0% then to be just unity you just filled 00:20:54.980 --> 00:21:01.940 align:start position:0% then to be just unity you just filled one<00:20:56.659> apparently<00:20:58.639> these<00:20:59.639> fellows<00:21:00.570> will<00:21:01.320> be<00:21:01.499> the 00:21:01.940 --> 00:21:01.950 align:start position:0% one apparently these fellows will be the 00:21:01.950 --> 00:21:04.759 align:start position:0% one apparently these fellows will be the first<00:21:02.190> row<00:21:02.369> of<00:21:02.489> our<00:21:02.609> matrix<00:21:03.379> these<00:21:04.379> will<00:21:04.679> be 00:21:04.759 --> 00:21:04.769 align:start position:0% first row of our matrix these will be 00:21:04.769 --> 00:21:07.460 align:start position:0% first row of our matrix these will be the<00:21:04.799> second<00:21:05.159> row<00:21:05.249> of<00:21:05.340> our<00:21:05.730> matrix<00:21:06.169> so<00:21:07.169> which<00:21:07.350> a 00:21:07.460 --> 00:21:07.470 align:start position:0% the second row of our matrix so which a 00:21:07.470 --> 00:21:10.599 align:start position:0% the second row of our matrix so which a X<00:21:07.710> to<00:21:07.889> the<00:21:08.009> 1<00:21:08.190> then<00:21:08.460> we<00:21:08.609> just<00:21:08.759> quote<00:21:09.350> our 00:21:10.599 --> 00:21:10.609 align:start position:0% X to the 1 then we just quote our 00:21:10.609 --> 00:21:13.940 align:start position:0% X to the 1 then we just quote our constraint<00:21:11.609> on<00:21:12.029> tech<00:21:12.210> transparence<00:21:12.989> it<00:21:13.769> would 00:21:13.940 --> 00:21:13.950 align:start position:0% constraint on tech transparence it would 00:21:13.950 --> 00:21:17.419 align:start position:0% constraint on tech transparence it would take<00:21:14.159> X<00:21:14.519> to<00:21:14.789> be<00:21:15.799> tirant<00:21:16.799> of<00:21:16.919> the<00:21:17.009> first<00:21:17.249> group 00:21:17.419 --> 00:21:17.429 align:start position:0% take X to be tirant of the first group 00:21:17.429 --> 00:21:20.779 align:start position:0% take X to be tirant of the first group dream<00:21:17.879> then<00:21:18.509> we<00:21:18.690> encode<00:21:19.200> the<00:21:19.889> second<00:21:20.220> pair<00:21:20.369> and 00:21:20.779 --> 00:21:20.789 align:start position:0% dream then we encode the second pair and 00:21:20.789 --> 00:21:25.340 align:start position:0% dream then we encode the second pair and then<00:21:21.539> I<00:21:21.980> could<00:21:22.980> take<00:21:23.159> the<00:21:23.879> rest<00:21:24.480> to<00:21:25.049> square 00:21:25.340 --> 00:21:25.350 align:start position:0% then I could take the rest to square 00:21:25.350 --> 00:21:28.639 align:start position:0% then I could take the rest to square them<00:21:26.090> this<00:21:27.090> way<00:21:27.269> would<00:21:27.539> be<00:21:27.570> encoded<00:21:27.869> there 00:21:28.639 --> 00:21:28.649 align:start position:0% them this way would be encoded there 00:21:28.649 --> 00:21:32.149 align:start position:0% them this way would be encoded there third<00:21:28.859> the<00:21:29.399> third<00:21:29.609> pair<00:21:29.850> of<00:21:30.080> rows<00:21:31.080> and<00:21:31.440> so<00:21:31.919> on 00:21:32.149 --> 00:21:32.159 align:start position:0% third the third pair of rows and so on 00:21:32.159 --> 00:21:39.340 align:start position:0% third the third pair of rows and so on so<00:21:33.799> this<00:21:34.799> this<00:21:35.399> equation<00:21:36.169> will<00:21:37.169> hold<00:21:37.499> for<00:21:38.489> all 00:21:39.340 --> 00:21:39.350 align:start position:0% so this this equation will hold for all 00:21:39.350 --> 00:21:43.669 align:start position:0% so this this equation will hold for all elements<00:21:40.350> of<00:21:40.440> hottest<00:21:41.009> group<00:21:42.409> and<00:21:43.409> just 00:21:43.669 --> 00:21:43.679 align:start position:0% elements of hottest group and just 00:21:43.679 --> 00:21:47.580 align:start position:0% elements of hottest group and just written<00:21:44.190> back 00:21:47.580 --> 00:21:47.590 align:start position:0% 00:21:47.590 --> 00:21:51.120 align:start position:0% mas<00:21:47.950> challenging<00:21:48.700> those<00:21:49.240> parameters<00:21:50.130> our 00:21:51.120 --> 00:21:51.130 align:start position:0% mas challenging those parameters our 00:21:51.130 --> 00:21:54.960 align:start position:0% mas challenging those parameters our constraint<00:21:51.669> on<00:21:51.820> normal<00:21:52.120> is<00:21:52.330> the<00:21:52.480> same<00:21:53.760> is<00:21:54.760> the 00:21:54.960 --> 00:21:54.970 align:start position:0% constraint on normal is the same is the 00:21:54.970 --> 00:21:56.909 align:start position:0% constraint on normal is the same is the second<00:21:55.299> level<00:21:55.419> check<00:21:55.690> it<00:21:55.809> from<00:21:55.990> every<00:21:56.650> state 00:21:56.909 --> 00:21:56.919 align:start position:0% second level check it from every state 00:21:56.919 --> 00:21:59.820 align:start position:0% second level check it from every state and<00:21:57.190> with<00:21:57.460> representation<00:21:58.360> and<00:21:58.600> our<00:21:59.409> domain 00:21:59.820 --> 00:21:59.830 align:start position:0% and with representation and our domain 00:21:59.830 --> 00:22:10.850 align:start position:0% and with representation and our domain our<00:22:00.630> domain<00:22:01.630> is<00:22:01.960> just<00:22:03.299> as<00:22:04.299> I<00:22:04.419> said 00:22:10.850 --> 00:22:10.860 align:start position:0% 00:22:10.860 --> 00:22:19.220 align:start position:0% Oh<00:22:10.890> finalmente<00:22:11.640> first<00:22:12.120> group 00:22:19.220 --> 00:22:19.230 align:start position:0% 00:22:19.230 --> 00:22:22.970 align:start position:0% and<00:22:19.769> so<00:22:20.100> our<00:22:20.309> domain<00:22:20.610> remember<00:22:21.059> you<00:22:21.860> will<00:22:22.860> be 00:22:22.970 --> 00:22:22.980 align:start position:0% and so our domain remember you will be 00:22:22.980 --> 00:22:30.789 align:start position:0% and so our domain remember you will be just<00:22:25.039> the<00:22:26.039> project<00:22:26.279> X<00:22:26.700> -<00:22:27.210> -<00:22:27.990> every<00:22:28.289> element<00:22:28.649> and 00:22:30.789 --> 00:22:30.799 align:start position:0% just the project X - - every element and 00:22:30.799 --> 00:22:34.909 align:start position:0% just the project X - - every element and we<00:22:31.799> know<00:22:31.950> that<00:22:32.659> this<00:22:33.659> element<00:22:33.929> for<00:22:34.440> my<00:22:34.559> second 00:22:34.909 --> 00:22:34.919 align:start position:0% we know that this element for my second 00:22:34.919 --> 00:22:37.549 align:start position:0% we know that this element for my second rule<00:22:35.070> so<00:22:35.519> this<00:22:35.850> will<00:22:36.120> be<00:22:36.269> used<00:22:36.510> region<00:22:37.320> is<00:22:37.529> a 00:22:37.549 --> 00:22:37.559 align:start position:0% rule so this will be used region is a 00:22:37.559 --> 00:22:43.399 align:start position:0% rule so this will be used region is a single<00:22:37.919> form<00:22:40.460> its<00:22:41.460> t<00:22:41.789> minus<00:22:42.630> five<00:22:42.840> and<00:22:43.049> this<00:22:43.260> is 00:22:43.399 --> 00:22:43.409 align:start position:0% single form its t minus five and this is 00:22:43.409 --> 00:22:47.360 align:start position:0% single form its t minus five and this is very<00:22:43.559> important<00:22:45.470> this<00:22:46.470> is<00:22:46.529> very<00:22:46.649> bad<00:22:47.010> effects 00:22:47.360 --> 00:22:47.370 align:start position:0% very important this is very bad effects 00:22:47.370 --> 00:22:52.159 align:start position:0% very important this is very bad effects that<00:22:47.549> our<00:22:48.360> group<00:22:48.779> has<00:22:49.399> such<00:22:50.399> that<00:22:50.880> a<00:22:51.169> magical 00:22:52.159 --> 00:22:52.169 align:start position:0% that our group has such that a magical 00:22:52.169 --> 00:22:54.289 align:start position:0% that our group has such that a magical complex<00:22:52.710> representation<00:22:53.399> was<00:22:53.669> being 00:22:54.289 --> 00:22:54.299 align:start position:0% complex representation was being 00:22:54.299 --> 00:22:57.919 align:start position:0% complex representation was being calculated<00:22:55.260> efficiently<00:22:56.130> yeah<00:22:56.639> so<00:22:57.480> exploit 00:22:57.919 --> 00:22:57.929 align:start position:0% calculated efficiently yeah so exploit 00:22:57.929 --> 00:22:59.750 align:start position:0% calculated efficiently yeah so exploit the<00:22:58.139> storage<00:22:58.440> of<00:22:58.529> solution<00:22:59.100> with<00:22:59.580> one 00:22:59.750 --> 00:22:59.760 align:start position:0% the storage of solution with one 00:22:59.760 --> 00:23:02.990 align:start position:0% the storage of solution with one exception<00:22:59.909> here<00:23:00.799> this<00:23:01.799> vulnerable<00:23:02.490> to<00:23:02.610> open 00:23:02.990 --> 00:23:03.000 align:start position:0% exception here this vulnerable to open 00:23:03.000 --> 00:23:06.019 align:start position:0% exception here this vulnerable to open every<00:23:03.529> game<00:23:04.529> except<00:23:05.130> the<00:23:05.220> last<00:23:05.370> one<00:23:05.610> yeah<00:23:05.789> in 00:23:06.019 --> 00:23:06.029 align:start position:0% every game except the last one yeah in 00:23:06.029 --> 00:23:08.509 align:start position:0% every game except the last one yeah in information<00:23:06.720> from<00:23:06.750> here<00:23:07.289> so<00:23:07.740> it<00:23:07.919> should<00:23:07.980> we 00:23:08.509 --> 00:23:08.519 align:start position:0% information from here so it should we 00:23:08.519 --> 00:23:10.940 align:start position:0% information from here so it should we truly<00:23:08.940> Elsa<00:23:09.570> Colin's<00:23:09.960> this<00:23:10.169> one<00:23:10.409> but<00:23:10.710> there<00:23:10.860> is 00:23:10.940 --> 00:23:10.950 align:start position:0% truly Elsa Colin's this one but there is 00:23:10.950 --> 00:23:12.889 align:start position:0% truly Elsa Colin's this one but there is nothing<00:23:11.309> after<00:23:11.460> but<00:23:12.090> we're<00:23:12.269> in<00:23:12.360> a<00:23:12.480> cyclic 00:23:12.889 --> 00:23:12.899 align:start position:0% nothing after but we're in a cyclic 00:23:12.899 --> 00:23:14.779 align:start position:0% nothing after but we're in a cyclic group<00:23:12.929> so<00:23:13.260> who<00:23:13.409> literally<00:23:14.100> it<00:23:14.309> believes<00:23:14.610> the 00:23:14.779 --> 00:23:14.789 align:start position:0% group so who literally it believes the 00:23:14.789 --> 00:23:17.029 align:start position:0% group so who literally it believes the last<00:23:15.000> role<00:23:15.240> was<00:23:15.750> the<00:23:15.779> first<00:23:16.049> one<00:23:16.320> where 00:23:17.029 --> 00:23:17.039 align:start position:0% last role was the first one where 00:23:17.039 --> 00:23:19.009 align:start position:0% last role was the first one where relationship<00:23:17.880> as<00:23:18.029> default<00:23:18.389> we<00:23:18.539> have<00:23:18.600> to<00:23:18.870> pick 00:23:19.009 --> 00:23:19.019 align:start position:0% relationship as default we have to pick 00:23:19.019 --> 00:23:21.230 align:start position:0% relationship as default we have to pick at<00:23:19.169> one<00:23:19.440> week<00:23:19.649> our<00:23:19.950> desert<00:23:20.370> but<00:23:20.940> they're<00:23:21.090> still 00:23:21.230 --> 00:23:21.240 align:start position:0% at one week our desert but they're still 00:23:21.240 --> 00:23:23.360 align:start position:0% at one week our desert but they're still efficiently<00:23:21.750> template<00:23:22.169> or<00:23:22.620> another<00:23:23.190> was 00:23:23.360 --> 00:23:23.370 align:start position:0% efficiently template or another was 00:23:23.370 --> 00:23:26.299 align:start position:0% efficiently template or another was abused<00:23:23.909> during<00:23:24.090> sentient<00:23:24.659> race<00:23:24.840> yeah<00:23:25.740> this 00:23:26.299 --> 00:23:26.309 align:start position:0% abused during sentient race yeah this 00:23:26.309 --> 00:23:28.100 align:start position:0% abused during sentient race yeah this gives<00:23:26.549> you<00:23:26.669> a<00:23:26.730> diminish<00:23:27.120> over<00:23:27.450> it's<00:23:27.630> going<00:23:27.960> to 00:23:28.100 --> 00:23:28.110 align:start position:0% gives you a diminish over it's going to 00:23:28.110 --> 00:23:33.139 align:start position:0% gives you a diminish over it's going to talk<00:23:28.260> about<00:23:28.380> the<00:23:28.559> tail<00:23:28.769> yeah<00:23:29.659> just<00:23:30.659> to<00:23:32.149> just 00:23:33.139 --> 00:23:33.149 align:start position:0% talk about the tail yeah just to just 00:23:33.149 --> 00:23:35.810 align:start position:0% talk about the tail yeah just to just for<00:23:33.539> some<00:23:33.960> well<00:23:34.799> this<00:23:35.130> is<00:23:35.279> three<00:23:35.519> the 00:23:35.810 --> 00:23:35.820 align:start position:0% for some well this is three the 00:23:35.820 --> 00:23:39.320 align:start position:0% for some well this is three the condition<00:23:36.149> of<00:23:36.210> course<00:23:36.470> just<00:23:37.470> for<00:23:38.330> intuitions 00:23:39.320 --> 00:23:39.330 align:start position:0% condition of course just for intuitions 00:23:39.330 --> 00:23:41.210 align:start position:0% condition of course just for intuitions estate<00:23:39.570> Creek<00:23:39.809> was<00:23:40.049> used<00:23:40.289> by<00:23:40.500> Zachary<00:23:41.010> and 00:23:41.210 --> 00:23:41.220 align:start position:0% estate Creek was used by Zachary and 00:23:41.220 --> 00:23:42.799 align:start position:0% estate Creek was used by Zachary and Larry<00:23:41.429> all<00:23:41.549> episode<00:23:42.000> name's<00:23:42.210> Eric<00:23:42.419> want<00:23:42.630> proof 00:23:42.799 --> 00:23:42.809 align:start position:0% Larry all episode name's Eric want proof 00:23:42.809 --> 00:23:44.539 align:start position:0% Larry all episode name's Eric want proof system<00:23:42.990> that<00:23:43.679> you<00:23:43.830> can<00:23:43.980> multiply<00:23:44.309> the 00:23:44.539 --> 00:23:44.549 align:start position:0% system that you can multiply the 00:23:44.549 --> 00:23:45.570 align:start position:0% system that you can multiply the argument<00:23:45.059> of<00:23:45.120> the<00:23:45.240> bull 00:23:45.570 --> 00:23:45.580 align:start position:0% argument of the bull 00:23:45.580 --> 00:23:48.899 align:start position:0% argument of the bull by<00:23:46.149> the<00:23:46.210> generator<00:23:46.869> internets<00:23:47.830> in<00:23:48.399> certain 00:23:48.899 --> 00:23:48.909 align:start position:0% by the generator internets in certain 00:23:48.909 --> 00:23:51.019 align:start position:0% by the generator internets in certain cases<00:23:49.119> and<00:23:49.480> this<00:23:49.929> keeps<00:23:50.110> you<00:23:50.230> bike<00:23:50.440> like<00:23:50.739> at 00:23:51.019 --> 00:23:51.029 align:start position:0% cases and this keeps you bike like at 00:23:51.029 --> 00:23:53.430 align:start position:0% cases and this keeps you bike like at displacement<00:23:52.029> at<00:23:52.360> time<00:23:52.659> displacement<00:23:53.350> or 00:23:53.430 --> 00:23:53.440 align:start position:0% displacement at time displacement or 00:23:53.440 --> 00:23:55.950 align:start position:0% displacement at time displacement or just<00:23:53.649> innovation<00:23:54.399> is<00:23:54.610> places<00:23:54.970> let's<00:23:55.360> go<00:23:55.720> back 00:23:55.950 --> 00:23:55.960 align:start position:0% just innovation is places let's go back 00:23:55.960 --> 00:24:02.519 align:start position:0% just innovation is places let's go back to<00:23:56.110> few<00:23:56.230> panache<00:23:56.499> example<00:23:57.009> with<00:23:57.549> 1<00:23:57.970> 1<00:23:58.529> 1<00:23:59.529> 2<00:23:59.980> 3<00:24:01.529> i 00:24:02.519 --> 00:24:02.529 align:start position:0% to few panache example with 1 1 1 2 3 i 00:24:02.529 --> 00:24:05.669 align:start position:0% to few panache example with 1 1 1 2 3 i will<00:24:02.980> only<00:24:03.279> work<00:24:03.610> in<00:24:03.759> them<00:24:03.909> like<00:24:04.149> on<00:24:04.989> this<00:24:05.379> part 00:24:05.669 --> 00:24:05.679 align:start position:0% will only work in them like on this part 00:24:05.679 --> 00:24:08.820 align:start position:0% will only work in them like on this part of<00:24:06.070> these<00:24:06.249> 2<00:24:06.429> rows<00:24:06.580> just<00:24:06.879> for<00:24:07.059> now<00:24:07.830> by 00:24:08.820 --> 00:24:08.830 align:start position:0% of these 2 rows just for now by 00:24:08.830 --> 00:24:10.139 align:start position:0% of these 2 rows just for now by definition<00:24:09.190> to<00:24:09.639> do<00:24:09.759> with<00:24:09.879> this<00:24:09.970> whole 00:24:10.139 --> 00:24:10.149 align:start position:0% definition to do with this whole 00:24:10.149 --> 00:24:13.729 align:start position:0% definition to do with this whole interval<00:24:10.509> over<00:24:10.840> X<00:24:11.110> and<00:24:11.730> let's<00:24:12.730> say<00:24:12.879> I<00:24:12.999> use<00:24:13.539> it 00:24:13.729 --> 00:24:13.739 align:start position:0% interval over X and let's say I use it 00:24:13.739 --> 00:24:16.289 align:start position:0% interval over X and let's say I use it Omega<00:24:14.739> is<00:24:14.860> the<00:24:14.950> generator<00:24:15.340> or<00:24:15.700> we<00:24:15.820> get<00:24:15.940> a<00:24:15.999> force 00:24:16.289 --> 00:24:16.299 align:start position:0% Omega is the generator or we get a force 00:24:16.299 --> 00:24:17.729 align:start position:0% Omega is the generator or we get a force equal<00:24:16.629> to<00:24:16.659> 1<00:24:16.899> because<00:24:17.110> they<00:24:17.320> have<00:24:17.499> four 00:24:17.729 --> 00:24:17.739 align:start position:0% equal to 1 because they have four 00:24:17.739 --> 00:24:23.009 align:start position:0% equal to 1 because they have four elements<00:24:18.220> here<00:24:19.200> by<00:24:20.200> definition<00:24:21.720> this<00:24:22.720> one 00:24:23.009 --> 00:24:23.019 align:start position:0% elements here by definition this one 00:24:23.019 --> 00:24:37.290 align:start position:0% elements here by definition this one blue<00:24:23.200> pieces<00:24:23.409> so<00:24:26.879> one<00:24:27.879> movie<00:24:28.210> this<00:24:28.269> one 00:24:37.290 --> 00:24:37.300 align:start position:0% 00:24:37.300 --> 00:24:41.490 align:start position:0% it's<00:24:38.430> another<00:24:39.430> one<00:24:39.730> well<00:24:40.350> representative<00:24:41.350> but 00:24:41.490 --> 00:24:41.500 align:start position:0% it's another one well representative but 00:24:41.500 --> 00:24:43.980 align:start position:0% it's another one well representative but carry<00:24:42.250> and<00:24:43.090> this<00:24:43.270> one<00:24:43.420> is<00:24:43.510> too<00:24:43.690> so<00:24:43.930> I<00:24:43.960> just 00:24:43.980 --> 00:24:43.990 align:start position:0% carry and this one is too so I just 00:24:43.990 --> 00:24:45.660 align:start position:0% carry and this one is too so I just didn't<00:24:44.380> read<00:24:44.560> to<00:24:44.650> them<00:24:44.830> one<00:24:45.010> by<00:24:45.160> one<00:24:45.190> by 00:24:45.660 --> 00:24:45.670 align:start position:0% didn't read to them one by one by 00:24:45.670 --> 00:24:48.660 align:start position:0% didn't read to them one by one by community<00:24:46.680> so<00:24:47.680> why<00:24:47.890> it's<00:24:48.040> called<00:24:48.190> rolling 00:24:48.660 --> 00:24:48.670 align:start position:0% community so why it's called rolling 00:24:48.670 --> 00:24:51.230 align:start position:0% community so why it's called rolling against<00:24:49.180> its<00:24:49.480> allows<00:24:49.720> you<00:24:49.840> to<00:24:49.990> navigate<00:24:50.200> in 00:24:51.230 --> 00:24:51.240 align:start position:0% against its allows you to navigate in 00:24:51.240 --> 00:24:54.480 align:start position:0% against its allows you to navigate in space<00:24:52.260> if<00:24:53.260> I<00:24:53.410> never<00:24:53.650> would<00:24:53.860> sell<00:24:54.190> in<00:24:54.310> terms 00:24:54.480 --> 00:24:54.490 align:start position:0% space if I never would sell in terms 00:24:54.490 --> 00:24:56.940 align:start position:0% space if I never would sell in terms they<00:24:54.640> reach<00:24:54.790> a<00:24:54.880> certain<00:24:54.910> time<00:24:55.450> by<00:24:56.380> selections 00:24:56.940 --> 00:24:56.950 align:start position:0% they reach a certain time by selections 00:24:56.950 --> 00:24:59.760 align:start position:0% they reach a certain time by selections of<00:24:57.070> thanks<00:24:57.280> now<00:24:57.480> you<00:24:58.480> will<00:24:58.630> one<00:24:58.810> adds<00:24:59.140> a<00:24:59.620> real 00:24:59.760 --> 00:24:59.770 align:start position:0% of thanks now you will one adds a real 00:24:59.770 --> 00:25:01.830 align:start position:0% of thanks now you will one adds a real application<00:25:00.340> of<00:25:00.430> have<00:25:00.580> separated<00:25:00.940> raided 00:25:01.830 --> 00:25:01.840 align:start position:0% application of have separated raided 00:25:01.840 --> 00:25:03.660 align:start position:0% application of have separated raided witnesses<00:25:02.350> for<00:25:02.500> separate<00:25:02.920> registers<00:25:03.430> who 00:25:03.660 --> 00:25:03.670 align:start position:0% witnesses for separate registers who 00:25:03.670 --> 00:25:05.760 align:start position:0% witnesses for separate registers who love<00:25:03.820> me<00:25:04.000> to<00:25:04.210> the<00:25:04.300> beginning<00:25:04.450> space<00:25:05.020> still 00:25:05.760 --> 00:25:05.770 align:start position:0% love me to the beginning space still 00:25:05.770 --> 00:25:08.520 align:start position:0% love me to the beginning space still need<00:25:05.920> to<00:25:06.070> navigate<00:25:06.400> in<00:25:06.550> time<00:25:06.760> so<00:25:07.480> what<00:25:07.870> this<00:25:08.350> is 00:25:08.520 --> 00:25:08.530 align:start position:0% need to navigate in time so what this is 00:25:08.530 --> 00:25:10.530 align:start position:0% need to navigate in time so what this is the<00:25:08.650> diffusion<00:25:08.800> function<00:25:09.400> of<00:25:09.490> over<00:25:09.640> X<00:25:09.850> what 00:25:10.530 --> 00:25:10.540 align:start position:0% the diffusion function of over X what 00:25:10.540 --> 00:25:13.580 align:start position:0% the diffusion function of over X what happens<00:25:10.690> if<00:25:11.020> I<00:25:11.140> look<00:25:11.350> it's<00:25:11.530> a<00:25:11.590> function<00:25:11.980> of<00:25:12.100> X 00:25:13.580 --> 00:25:13.590 align:start position:0% happens if I look it's a function of X 00:25:13.590 --> 00:25:17.850 align:start position:0% happens if I look it's a function of X multiplied<00:25:14.590> by<00:25:14.620> Omega<00:25:15.250> squared<00:25:16.500> s<00:25:17.500> will 00:25:17.850 --> 00:25:17.860 align:start position:0% multiplied by Omega squared s will 00:25:17.860 --> 00:25:27.460 align:start position:0% multiplied by Omega squared s will actually<00:25:18.790> leave<00:25:19.000> me<00:25:19.270> and<00:25:19.630> say<00:25:22.920> rises 00:25:27.460 --> 00:25:27.470 align:start position:0% 00:25:27.470 --> 00:25:30.129 align:start position:0% oh<00:25:27.499> my<00:25:28.220> goodness<00:25:28.519> nervous<00:25:28.759> oh<00:25:28.879> it's<00:25:29.059> 1:1<00:25:29.720> here 00:25:30.129 --> 00:25:30.139 align:start position:0% oh my goodness nervous oh it's 1:1 here 00:25:30.139 --> 00:25:32.289 align:start position:0% oh my goodness nervous oh it's 1:1 here Omega<00:25:30.590> squared<00:25:30.919> it<00:25:31.460> will<00:25:31.610> give<00:25:31.820> me<00:25:31.940> one<00:25:32.120> this 00:25:32.289 --> 00:25:32.299 align:start position:0% Omega squared it will give me one this 00:25:32.299 --> 00:25:33.480 align:start position:0% Omega squared it will give me one this will<00:25:32.480> give<00:25:32.659> us<00:25:32.749> a<00:25:32.809> song 00:25:33.480 --> 00:25:33.490 align:start position:0% will give us a song 00:25:33.490 --> 00:25:37.899 align:start position:0% will give us a song if<00:25:34.490> I<00:25:34.700> take<00:25:35.200> my<00:25:36.200> modified<00:25:36.799> function<00:25:37.220> at<00:25:37.429> Omega 00:25:37.899 --> 00:25:37.909 align:start position:0% if I take my modified function at Omega 00:25:37.909 --> 00:25:39.220 align:start position:0% if I take my modified function at Omega the<00:25:37.970> first<00:25:38.749> power 00:25:39.220 --> 00:25:39.230 align:start position:0% the first power 00:25:39.230 --> 00:25:43.149 align:start position:0% the first power give<00:25:40.009> me<00:25:40.129> two<00:25:40.340> so<00:25:40.759> I<00:25:40.999> will<00:25:41.269> displace<00:25:41.899> high<00:25:42.440> time 00:25:43.149 --> 00:25:43.159 align:start position:0% give me two so I will displace high time 00:25:43.159 --> 00:25:47.379 align:start position:0% give me two so I will displace high time by<00:25:44.120> one<00:25:44.299> step<00:25:45.129> this<00:25:46.129> way<00:25:46.340> is<00:25:46.399> called<00:25:46.669> the<00:25:47.210> wrong 00:25:47.379 --> 00:25:47.389 align:start position:0% by one step this way is called the wrong 00:25:47.389 --> 00:25:47.769 align:start position:0% by one step this way is called the wrong with<00:25:47.509> him 00:25:47.769 --> 00:25:47.779 align:start position:0% with him 00:25:47.779 --> 00:25:51.310 align:start position:0% with him if<00:25:48.350> any<00:25:48.620> one<00:25:48.740> I<00:25:48.999> choose<00:25:49.999> to<00:25:50.149> live<00:25:50.330> but<00:25:51.080> the 00:25:51.310 --> 00:25:51.320 align:start position:0% if any one I choose to live but the 00:25:51.320 --> 00:25:53.320 align:start position:0% if any one I choose to live but the easiest<00:25:51.769> example<00:25:51.950> to<00:25:52.429> see<00:25:52.580> too<00:25:52.940> many<00:25:53.059> ones 00:25:53.320 --> 00:25:53.330 align:start position:0% easiest example to see too many ones 00:25:53.330 --> 00:25:55.419 align:start position:0% easiest example to see too many ones here<00:25:53.659> I<00:25:53.870> think<00:25:54.289> you<00:25:54.350> do<00:25:54.470> the<00:25:54.649> same<00:25:54.799> for<00:25:54.980> next 00:25:55.419 --> 00:25:55.429 align:start position:0% here I think you do the same for next 00:25:55.429 --> 00:25:57.489 align:start position:0% here I think you do the same for next period<00:25:55.580> for<00:25:55.879> us<00:25:55.970> will<00:25:56.299> be<00:25:56.419> my<00:25:56.539> representative 00:25:57.489 --> 00:25:57.499 align:start position:0% period for us will be my representative 00:25:57.499 --> 00:25:58.869 align:start position:0% period for us will be my representative cause<00:25:57.769> it<00:25:57.889> just<00:25:58.039> allows<00:25:58.460> you<00:25:58.610> to<00:25:58.759> navigate 00:25:58.869 --> 00:25:58.879 align:start position:0% cause it just allows you to navigate 00:25:58.879 --> 00:26:03.190 align:start position:0% cause it just allows you to navigate this<00:25:59.330> is<00:25:59.570> why<00:25:59.779> it's<00:25:59.899> multiple<00:26:01.720> yes<00:26:02.720> and<00:26:02.929> for 00:26:03.190 --> 00:26:03.200 align:start position:0% this is why it's multiple yes and for 00:26:03.200 --> 00:26:05.470 align:start position:0% this is why it's multiple yes and for Z's<00:26:03.440> you<00:26:03.980> just<00:26:04.279> everything<00:26:04.940> you<00:26:04.970> want<00:26:05.210> a 00:26:05.470 --> 00:26:05.480 align:start position:0% Z's you just everything you want a 00:26:05.480 --> 00:26:09.549 align:start position:0% Z's you just everything you want a practical<00:26:06.379> perspective<00:26:08.169> well<00:26:09.169> you<00:26:09.409> can 00:26:09.549 --> 00:26:09.559 align:start position:0% practical perspective well you can 00:26:09.559 --> 00:26:13.869 align:start position:0% practical perspective well you can transform<00:26:11.379> polynomial<00:26:12.379> in<00:26:12.649> this<00:26:12.830> form<00:26:13.129> over<00:26:13.610> X 00:26:13.869 --> 00:26:13.879 align:start position:0% transform polynomial in this form over X 00:26:13.879 --> 00:26:17.409 align:start position:0% transform polynomial in this form over X into<00:26:14.840> polynomial<00:26:15.350> displaced<00:26:15.830> one<00:26:16.100> by<00:26:16.759> very 00:26:17.409 --> 00:26:17.419 align:start position:0% into polynomial displaced one by very 00:26:17.419 --> 00:26:18.519 align:start position:0% into polynomial displaced one by very simple<00:26:17.749> and<00:26:17.869> efficient<00:26:18.259> reliable 00:26:18.519 --> 00:26:18.529 align:start position:0% simple and efficient reliable 00:26:18.529 --> 00:26:20.680 align:start position:0% simple and efficient reliable information<00:26:19.129> which<00:26:19.549> it<00:26:19.730> takes<00:26:20.059> a<00:26:20.269> week<00:26:20.539> you're 00:26:20.680 --> 00:26:20.690 align:start position:0% information which it takes a week you're 00:26:20.690 --> 00:26:23.109 align:start position:0% information which it takes a week you're not<00:26:20.869> gonna<00:26:20.990> multiplication<00:26:21.789> this<00:26:22.789> is<00:26:22.970> all 00:26:23.109 --> 00:26:23.119 align:start position:0% not gonna multiplication this is all 00:26:23.119 --> 00:26:29.619 align:start position:0% not gonna multiplication this is all three<00:26:24.820> okay<00:26:26.980> yeah<00:26:28.009> so<00:26:28.490> this<00:26:28.909> what<00:26:29.210> you<00:26:29.389> would 00:26:29.619 --> 00:26:29.629 align:start position:0% three okay yeah so this what you would 00:26:29.629 --> 00:26:31.389 align:start position:0% three okay yeah so this what you would have<00:26:29.990> in<00:26:30.169> the<00:26:30.200> practical<00:26:30.619> implementation<00:26:30.980> of 00:26:31.389 --> 00:26:31.399 align:start position:0% have in the practical implementation of 00:26:31.399 --> 00:26:33.039 align:start position:0% have in the practical implementation of as<00:26:31.519> optimization<00:26:32.240> you<00:26:32.299> don't<00:26:32.509> need<00:26:32.659> to<00:26:32.779> negate 00:26:33.039 --> 00:26:33.049 align:start position:0% as optimization you don't need to negate 00:26:33.049 --> 00:26:35.710 align:start position:0% as optimization you don't need to negate in<00:26:33.230> space<00:26:33.470> even<00:26:33.769> while<00:26:34.369> in<00:26:34.789> the<00:26:35.059> original 00:26:35.710 --> 00:26:35.720 align:start position:0% in space even while in the original 00:26:35.720 --> 00:26:38.049 align:start position:0% in space even while in the original papers<00:26:36.139> everywhere<00:26:36.590> it<00:26:36.950> say<00:26:37.429> you<00:26:37.580> take<00:26:37.759> only 00:26:38.049 --> 00:26:38.059 align:start position:0% papers everywhere it say you take only 00:26:38.059 --> 00:26:40.539 align:start position:0% papers everywhere it say you take only witness<00:26:38.539> put<00:26:39.230> it<00:26:39.350> all<00:26:39.470> together<00:26:39.649> is<00:26:40.279> one 00:26:40.539 --> 00:26:40.549 align:start position:0% witness put it all together is one 00:26:40.549 --> 00:26:42.700 align:start position:0% witness put it all together is one witness<00:26:40.700> bullet<00:26:41.119> or<00:26:41.210> note<00:26:41.419> in<00:26:42.289> order<00:26:42.529> to 00:26:42.700 --> 00:26:42.710 align:start position:0% witness bullet or note in order to 00:26:42.710 --> 00:26:45.460 align:start position:0% witness bullet or note in order to practice<00:26:43.779> so<00:26:44.779> you<00:26:44.899> only<00:26:45.049> need<00:26:45.139> to<00:26:45.379> the 00:26:45.460 --> 00:26:45.470 align:start position:0% practice so you only need to the 00:26:45.470 --> 00:26:47.529 align:start position:0% practice so you only need to the beginning<00:26:45.860> spacing<00:26:46.249> everything<00:26:47.149> else<00:26:47.299> falls 00:26:47.529 --> 00:26:47.539 align:start position:0% beginning spacing everything else falls 00:26:47.539 --> 00:26:49.690 align:start position:0% beginning spacing everything else falls to<00:26:48.350> be<00:26:48.440> precise<00:26:48.830> it<00:26:49.100> is<00:26:49.129> not<00:26:49.369> from<00:26:49.580> the 00:26:49.690 --> 00:26:49.700 align:start position:0% to be precise it is not from the 00:26:49.700 --> 00:26:50.340 align:start position:0% to be precise it is not from the original 00:26:50.340 --> 00:26:50.350 align:start position:0% original 00:26:50.350 --> 00:26:56.539 align:start position:0% original but<00:26:50.950> by<00:26:51.190> the<00:26:51.250> next<00:26:51.460> one<00:26:52.200> which<00:26:53.200> sports<00:26:53.710> the 00:26:56.539 --> 00:26:56.549 align:start position:0% 00:26:56.549 --> 00:27:06.659 align:start position:0% operation<00:27:04.200> so<00:27:05.200> here<00:27:05.409> they<00:27:05.950> say<00:27:06.250> you<00:27:06.309> for<00:27:06.549> all 00:27:06.659 --> 00:27:06.669 align:start position:0% operation so here they say you for all 00:27:06.669 --> 00:27:14.430 align:start position:0% operation so here they say you for all these<00:27:07.049> in<00:27:08.700> every<00:27:09.700> field<00:27:10.690> it<00:27:10.899> to<00:27:11.019> work<00:27:12.090> oh<00:27:13.440> no 00:27:14.430 --> 00:27:14.440 align:start position:0% these in every field it to work oh no 00:27:14.440 --> 00:27:16.830 align:start position:0% these in every field it to work oh no it's<00:27:14.649> for<00:27:14.860> all<00:27:15.100> X<00:27:15.399> for<00:27:15.730> which<00:27:16.090> the<00:27:16.509> other<00:27:16.659> major 00:27:16.830 --> 00:27:16.840 align:start position:0% it's for all X for which the other major 00:27:16.840 --> 00:27:19.019 align:start position:0% it's for all X for which the other major lunar<00:27:17.200> node<00:27:17.350> is<00:27:17.470> equal<00:27:17.710> to<00:27:17.830> zero<00:27:18.039> so<00:27:18.610> where<00:27:18.909> he 00:27:19.019 --> 00:27:19.029 align:start position:0% lunar node is equal to zero so where he 00:27:19.029 --> 00:27:20.970 align:start position:0% lunar node is equal to zero so where he has<00:27:19.210> money<00:27:19.480> to<00:27:19.570> go<00:27:19.809> in<00:27:19.960> our<00:27:20.080> memory<00:27:20.320> but<00:27:20.679> I<00:27:20.799> mean 00:27:20.970 --> 00:27:20.980 align:start position:0% has money to go in our memory but I mean 00:27:20.980 --> 00:27:26.539 align:start position:0% has money to go in our memory but I mean it's<00:27:21.190> a<00:27:21.309> part<00:27:21.549> of<00:27:21.639> the<00:27:21.759> next<00:27:24.840> so<00:27:25.840> it's<00:27:26.049> not 00:27:26.539 --> 00:27:26.549 align:start position:0% it's a part of the next so it's not 00:27:26.549 --> 00:27:30.480 align:start position:0% it's a part of the next so it's not recycle<00:27:27.549> Li<00:27:27.850> that<00:27:28.090> the<00:27:28.179> stage<00:27:28.480> of<00:27:28.779> not<00:27:29.490> there 00:27:30.480 --> 00:27:30.490 align:start position:0% recycle Li that the stage of not there 00:27:30.490 --> 00:27:33.389 align:start position:0% recycle Li that the stage of not there are<00:27:30.610> some<00:27:30.789> technical<00:27:31.509> tears<00:27:31.870> just<00:27:32.470> second 00:27:33.389 --> 00:27:33.399 align:start position:0% are some technical tears just second 00:27:33.399 --> 00:27:35.999 align:start position:0% are some technical tears just second come<00:27:33.580> out<00:27:33.850> of<00:27:34.090> domain<00:27:34.450> which<00:27:35.289> I<00:27:35.529> don't<00:27:35.769> want<00:27:35.950> to 00:27:35.999 --> 00:27:36.009 align:start position:0% come out of domain which I don't want to 00:27:36.009 --> 00:27:39.729 align:start position:0% come out of domain which I don't want to speak<00:27:36.159> about<00:27:36.220> just<00:27:37.710> sorry 00:27:39.729 --> 00:27:39.739 align:start position:0% speak about just sorry 00:27:39.739 --> 00:27:44.659 align:start position:0% speak about just sorry who<00:27:40.739> from<00:27:41.759> chuckwei<00:27:42.440> but<00:27:43.440> what's<00:27:43.859> going<00:27:44.129> on 00:27:44.659 --> 00:27:44.669 align:start position:0% who from chuckwei but what's going on 00:27:44.669 --> 00:27:47.029 align:start position:0% who from chuckwei but what's going on remember<00:27:45.389> from<00:27:45.570> the<00:27:45.629> previous<00:27:45.989> slide<00:27:46.379> the 00:27:47.029 --> 00:27:47.039 align:start position:0% remember from the previous slide the 00:27:47.039 --> 00:27:52.009 align:start position:0% remember from the previous slide the previous<00:27:47.369> slide<00:27:47.659> but<00:27:49.729> if<00:27:50.729> X<00:27:51.119> is<00:27:51.570> a<00:27:51.629> rotten 00:27:52.009 --> 00:27:52.019 align:start position:0% previous slide but if X is a rotten 00:27:52.019 --> 00:27:56.029 align:start position:0% previous slide but if X is a rotten tomato<00:27:52.609> then<00:27:53.609> should<00:27:53.820> be<00:27:53.850> the<00:27:54.539> root<00:27:54.749> of<00:27:55.049> the 00:27:56.029 --> 00:27:56.039 align:start position:0% tomato then should be the root of the 00:27:56.039 --> 00:28:00.229 align:start position:0% tomato then should be the root of the slide<00:27:56.549> construction<00:27:58.549> and<00:27:59.549> he<00:27:59.729> these<00:27:59.970> large 00:28:00.229 --> 00:28:00.239 align:start position:0% slide construction and he these large 00:28:00.239 --> 00:28:02.869 align:start position:0% slide construction and he these large construction<00:28:00.570> is<00:28:00.840> taken<00:28:01.200> as<00:28:01.350> a<00:28:01.950> numerator<00:28:02.460> and 00:28:02.869 --> 00:28:02.879 align:start position:0% construction is taken as a numerator and 00:28:02.879 --> 00:28:07.669 align:start position:0% construction is taken as a numerator and so<00:28:03.359> on<00:28:03.539> on<00:28:04.320> every<00:28:04.710> such<00:28:04.979> and<00:28:05.369> every<00:28:05.789> X<00:28:06.499> from<00:28:07.499> our 00:28:07.669 --> 00:28:07.679 align:start position:0% so on on every such and every X from our 00:28:07.679 --> 00:28:09.859 align:start position:0% so on on every such and every X from our domain<00:28:08.129> which<00:28:08.759> is<00:28:08.789> just<00:28:09.179> the<00:28:09.419> elements<00:28:09.720> of<00:28:09.779> the 00:28:09.859 --> 00:28:09.869 align:start position:0% domain which is just the elements of the 00:28:09.869 --> 00:28:12.830 align:start position:0% domain which is just the elements of the first<00:28:10.019> group<00:28:10.350> this<00:28:11.220> fraction<00:28:11.759> should<00:28:12.690> be 00:28:12.830 --> 00:28:12.840 align:start position:0% first group this fraction should be 00:28:12.840 --> 00:28:13.820 align:start position:0% first group this fraction should be phenomenal 00:28:13.820 --> 00:28:13.830 align:start position:0% phenomenal 00:28:13.830 --> 00:28:17.479 align:start position:0% phenomenal yeah<00:28:14.220> and<00:28:14.779> we<00:28:15.779> just<00:28:15.809> take<00:28:16.200> random<00:28:16.739> petitions 00:28:17.479 --> 00:28:17.489 align:start position:0% yeah and we just take random petitions 00:28:17.489 --> 00:28:21.229 align:start position:0% yeah and we just take random petitions from<00:28:17.729> the<00:28:17.970> verifier<00:28:18.389> in<00:28:18.840> order<00:28:19.049> to<00:28:20.239> combine 00:28:21.229 --> 00:28:21.239 align:start position:0% from the verifier in order to combine 00:28:21.239 --> 00:28:23.810 align:start position:0% from the verifier in order to combine all<00:28:21.899> those<00:28:22.139> functions<00:28:22.919> into<00:28:23.429> one 00:28:23.810 --> 00:28:23.820 align:start position:0% all those functions into one 00:28:23.820 --> 00:28:31.700 align:start position:0% all those functions into one mr.<00:28:24.269> so<00:28:24.690> that<00:28:24.840> to<00:28:24.960> keep<00:28:25.169> I<00:28:27.619> saw<00:28:30.379> what<00:28:31.379> they<00:28:31.529> mean 00:28:31.700 --> 00:28:31.710 align:start position:0% mr. so that to keep I saw what they mean 00:28:31.710 --> 00:28:32.629 align:start position:0% mr. so that to keep I saw what they mean by<00:28:31.830> fraction 00:28:32.629 --> 00:28:32.639 align:start position:0% by fraction 00:28:32.639 --> 00:28:37.549 align:start position:0% by fraction you<00:28:32.970> actually<00:28:33.179> care<00:28:33.570> just<00:28:34.200> explain<00:28:35.059> less<00:28:36.559> so 00:28:37.549 --> 00:28:37.559 align:start position:0% you actually care just explain less so 00:28:37.559 --> 00:28:40.430 align:start position:0% you actually care just explain less so you<00:28:37.619> season<00:28:38.070> one<00:28:38.669> help<00:28:39.019> cupid<00:28:40.019> internal<00:28:40.349> is 00:28:40.430 --> 00:28:40.440 align:start position:0% you season one help cupid internal is 00:28:40.440 --> 00:28:43.999 align:start position:0% you season one help cupid internal is punishing<00:28:40.889> my<00:28:41.669> personal<00:28:42.059> question<00:28:42.389> yeah<00:28:43.009> but 00:28:43.999 --> 00:28:44.009 align:start position:0% punishing my personal question yeah but 00:28:44.009 --> 00:28:46.700 align:start position:0% punishing my personal question yeah but if<00:28:44.220> you<00:28:44.399> can<00:28:44.580> space<00:28:44.759> full<00:28:45.169> direction<00:28:46.200> I<00:28:46.320> mean 00:28:46.700 --> 00:28:46.710 align:start position:0% if you can space full direction I mean 00:28:46.710 --> 00:28:49.280 align:start position:0% if you can space full direction I mean business<00:28:47.399> practice<00:28:47.729> music 00:28:49.280 --> 00:28:49.290 align:start position:0% business practice music 00:28:49.290 --> 00:28:51.950 align:start position:0% business practice music for<00:28:49.740> a<00:28:49.770> witness<00:28:50.100> since<00:28:50.760> it<00:28:51.240> means<00:28:51.540> that<00:28:51.750> for 00:28:51.950 --> 00:28:51.960 align:start position:0% for a witness since it means that for 00:28:51.960 --> 00:28:54.320 align:start position:0% for a witness since it means that for every<00:28:52.140> X<00:28:52.470> for<00:28:52.800> which<00:28:52.950> light<00:28:53.220> we<00:28:53.610> chose<00:28:54.180> the 00:28:54.320 --> 00:28:54.330 align:start position:0% every X for which light we chose the 00:28:54.330 --> 00:28:57.980 align:start position:0% every X for which light we chose the simple<00:28:54.600> example<00:28:54.960> it<00:28:55.860> is<00:28:56.040> equal<00:28:56.430> to<00:28:56.460> 0<00:28:56.760> and<00:28:56.990> Q 00:28:57.980 --> 00:28:57.990 align:start position:0% simple example it is equal to 0 and Q 00:28:57.990 --> 00:29:00.050 align:start position:0% simple example it is equal to 0 and Q political<00:28:58.440> is<00:28:58.560> equal<00:28:58.800> to<00:28:58.890> 0<00:28:59.070> to<00:28:59.670> be<00:28:59.790> divided 00:29:00.050 --> 00:29:00.060 align:start position:0% political is equal to 0 to be divided 00:29:00.060 --> 00:29:01.970 align:start position:0% political is equal to 0 to be divided one<00:29:00.240> way<00:29:00.390> or<00:29:00.480> another<00:29:00.510> because<00:29:01.380> it<00:29:01.650> captures 00:29:01.970 --> 00:29:01.980 align:start position:0% one way or another because it captures 00:29:01.980 --> 00:29:04.190 align:start position:0% one way or another because it captures people<00:29:02.280> literally<00:29:02.970> at<00:29:03.090> this<00:29:03.240> point<00:29:03.510> admit 00:29:04.190 --> 00:29:04.200 align:start position:0% people literally at this point admit 00:29:04.200 --> 00:29:07.400 align:start position:0% people literally at this point admit that<00:29:04.380> if<00:29:04.590> you<00:29:04.680> do<00:29:04.890> this<00:29:05.130> division<00:29:05.570> and<00:29:06.570> this 00:29:07.400 --> 00:29:07.410 align:start position:0% that if you do this division and this 00:29:07.410 --> 00:29:09.320 align:start position:0% that if you do this division and this construction<00:29:07.920> is<00:29:08.190> not<00:29:08.490> a<00:29:08.700> rational<00:29:08.970> function 00:29:09.320 --> 00:29:09.330 align:start position:0% construction is not a rational function 00:29:09.330 --> 00:29:11.600 align:start position:0% construction is not a rational function but<00:29:10.110> it's<00:29:10.260> a<00:29:10.380> polynomial<00:29:10.770> of<00:29:10.980> degree<00:29:11.190> which 00:29:11.600 --> 00:29:11.610 align:start position:0% but it's a polynomial of degree which 00:29:11.610 --> 00:29:14.230 align:start position:0% but it's a polynomial of degree which you<00:29:11.730> can<00:29:11.910> predict<00:29:12.300> by<00:29:12.540> the<00:29:12.600> tracker<00:29:12.930> system 00:29:14.230 --> 00:29:14.240 align:start position:0% you can predict by the tracker system 00:29:14.240 --> 00:29:17.930 align:start position:0% you can predict by the tracker system just<00:29:15.240> for<00:29:16.230> those<00:29:16.410> technical<00:29:17.400> perspective 00:29:17.930 --> 00:29:17.940 align:start position:0% just for those technical perspective 00:29:17.940 --> 00:29:22.520 align:start position:0% just for those technical perspective Duke<00:29:18.390> wants<00:29:18.930> to<00:29:19.260> have<00:29:19.470> this<00:29:21.080> has<00:29:22.080> raised<00:29:22.380> to 00:29:22.520 --> 00:29:22.530 align:start position:0% Duke wants to have this has raised to 00:29:22.530 --> 00:29:24.770 align:start position:0% Duke wants to have this has raised to the<00:29:22.620> low<00:29:22.740> degree<00:29:22.970> so<00:29:23.970> this<00:29:24.210> will<00:29:24.420> internal 00:29:24.770 --> 00:29:24.780 align:start position:0% the low degree so this will internal 00:29:24.780 --> 00:29:27.440 align:start position:0% the low degree so this will internal which<00:29:25.200> will<00:29:25.560> be<00:29:25.740> part<00:29:25.950> of<00:29:26.070> surprise<00:29:26.490> Fulop 00:29:27.440 --> 00:29:27.450 align:start position:0% which will be part of surprise Fulop 00:29:27.450 --> 00:29:30.380 align:start position:0% which will be part of surprise Fulop drove<00:29:28.080> to<00:29:28.320> very<00:29:28.530> large<00:29:28.710> search<00:29:29.160> County<00:29:29.940> few 00:29:30.380 --> 00:29:30.390 align:start position:0% drove to very large search County few 00:29:30.390 --> 00:29:32.600 align:start position:0% drove to very large search County few constraints<00:29:30.890> like<00:29:31.890> small<00:29:32.370> number<00:29:32.550> of 00:29:32.600 --> 00:29:32.610 align:start position:0% constraints like small number of 00:29:32.610 --> 00:29:35.210 align:start position:0% constraints like small number of constraints<00:29:32.940> large<00:29:33.810> degree<00:29:34.020> you<00:29:34.950> would 00:29:35.210 --> 00:29:35.220 align:start position:0% constraints large degree you would 00:29:35.220 --> 00:29:38.270 align:start position:0% constraints large degree you would rather<00:29:35.730> prefer<00:29:36.060> to<00:29:36.480> break<00:29:36.660> in<00:29:37.620> constraints<00:29:38.160> we 00:29:38.270 --> 00:29:38.280 align:start position:0% rather prefer to break in constraints we 00:29:38.280 --> 00:29:41.150 align:start position:0% rather prefer to break in constraints we should<00:29:38.460> agree<00:29:38.670> to<00:29:38.990> well<00:29:39.990> 3<00:29:40.620> is<00:29:40.650> not<00:29:40.920> good 00:29:41.150 --> 00:29:41.160 align:start position:0% should agree to well 3 is not good 00:29:41.160 --> 00:29:42.620 align:start position:0% should agree to well 3 is not good because<00:29:41.340> you're<00:29:41.700> always<00:29:41.790> part<00:29:42.060> of<00:29:42.210> work<00:29:42.480> is 00:29:42.620 --> 00:29:42.630 align:start position:0% because you're always part of work is 00:29:42.630 --> 00:29:46.340 align:start position:0% because you're always part of work is multiple<00:29:42.990> to<00:29:43.380> so<00:29:43.770> by<00:29:43.980> 2<00:29:44.250> or<00:29:44.400> 4<00:29:44.640> and<00:29:45.330> the<00:29:46.020> large 00:29:46.340 --> 00:29:46.350 align:start position:0% multiple to so by 2 or 4 and the large 00:29:46.350 --> 00:29:51.200 align:start position:0% multiple to so by 2 or 4 and the large from<00:29:47.390> optimization<00:29:48.390> expand<00:29:49.880> here's<00:29:50.880> just<00:29:51.090> a 00:29:51.200 --> 00:29:51.210 align:start position:0% from optimization expand here's just a 00:29:51.210 --> 00:29:54.530 align:start position:0% from optimization expand here's just a question<00:29:51.630> why<00:29:51.780> you<00:29:51.810> can't<00:29:52.440> /<00:29:53.540> desperation 00:29:54.530 --> 00:29:54.540 align:start position:0% question why you can't / desperation 00:29:54.540 --> 00:29:56.340 align:start position:0% question why you can't / desperation when<00:29:54.720> you<00:29:54.870> have<00:29:55.140> polynomial<00:29:55.470> which<00:29:55.950> is 00:29:56.340 --> 00:29:56.350 align:start position:0% when you have polynomial which is 00:29:56.350 --> 00:29:59.370 align:start position:0% when you have polynomial which is that<00:29:57.100> wasn't<00:29:57.370> right<00:29:57.580> but<00:29:58.150> not<00:29:58.360> some<00:29:58.630> function 00:29:59.370 --> 00:29:59.380 align:start position:0% that wasn't right but not some function 00:29:59.380 --> 00:30:01.049 align:start position:0% that wasn't right but not some function because<00:29:59.650> you<00:29:59.830> can<00:30:00.039> define<00:30:00.340> it<00:30:00.490> as<00:30:00.610> a<00:30:00.640> function 00:30:01.049 --> 00:30:01.059 align:start position:0% because you can define it as a function 00:30:01.059 --> 00:30:04.230 align:start position:0% because you can define it as a function but<00:30:01.690> you<00:30:01.840> will<00:30:01.990> then<00:30:02.380> see<00:30:03.100> or<00:30:03.220> but<00:30:03.820> your<00:30:04.000> ass 00:30:04.230 --> 00:30:04.240 align:start position:0% but you will then see or but your ass 00:30:04.240 --> 00:30:11.610 align:start position:0% but you will then see or but your ass will<00:30:04.570> not<00:30:04.720> be<00:30:07.320> able<00:30:08.320> to<00:30:08.380> see<00:30:08.740> it<00:30:08.950> you<00:30:09.120> well<00:30:10.620> your 00:30:11.610 --> 00:30:11.620 align:start position:0% will not be able to see it you well your 00:30:11.620 --> 00:30:13.529 align:start position:0% will not be able to see it you well your mouth<00:30:11.919> piece<00:30:12.370> and<00:30:12.400> put<00:30:12.789> it<00:30:12.820> on<00:30:13.000> constraints 00:30:13.529 --> 00:30:13.539 align:start position:0% mouth piece and put it on constraints 00:30:13.539 --> 00:30:16.529 align:start position:0% mouth piece and put it on constraints check<00:30:14.320> announced<00:30:14.590> now<00:30:14.799> we<00:30:14.860> just<00:30:15.160> go<00:30:15.580> state<00:30:15.850> XY 00:30:16.529 --> 00:30:16.539 align:start position:0% check announced now we just go state XY 00:30:16.539 --> 00:30:19.500 align:start position:0% check announced now we just go state XY as<00:30:16.809> to<00:30:17.410> next<00:30:17.770> steps<00:30:17.980> but<00:30:18.549> you<00:30:18.700> say<00:30:18.910> well<00:30:19.299> I 00:30:19.500 --> 00:30:19.510 align:start position:0% as to next steps but you say well I 00:30:19.510 --> 00:30:23.130 align:start position:0% as to next steps but you say well I replaced<00:30:19.990> my<00:30:20.080> x1<00:30:20.650> by<00:30:21.309> the<00:30:22.090> people<00:30:22.390> which<00:30:23.020> is 00:30:23.130 --> 00:30:23.140 align:start position:0% replaced my x1 by the people which is 00:30:23.140 --> 00:30:25.919 align:start position:0% replaced my x1 by the people which is perfectly<00:30:23.470> possible<00:30:24.179> Q<00:30:25.179> is<00:30:25.330> just<00:30:25.360> to<00:30:25.750> punish 00:30:25.919 --> 00:30:25.929 align:start position:0% perfectly possible Q is just to punish 00:30:25.929 --> 00:30:27.870 align:start position:0% perfectly possible Q is just to punish people<00:30:26.140> in<00:30:26.380> general<00:30:26.500> it<00:30:26.770> just<00:30:26.980> defines<00:30:27.580> you 00:30:27.870 --> 00:30:27.880 align:start position:0% people in general it just defines you 00:30:27.880 --> 00:30:30.570 align:start position:0% people in general it just defines you where<00:30:28.120> it<00:30:28.210> gets<00:30:28.390> very<00:30:28.450> cold<00:30:28.860> just<00:30:29.860> if<00:30:30.250> you<00:30:30.400> want 00:30:30.570 --> 00:30:30.580 align:start position:0% where it gets very cold just if you want 00:30:30.580 --> 00:30:32.549 align:start position:0% where it gets very cold just if you want to<00:30:30.940> fold<00:30:31.120> them<00:30:31.330> there<00:30:31.600> you<00:30:31.720> go<00:30:31.929> since<00:30:32.289> the<00:30:32.380> last 00:30:32.549 --> 00:30:32.559 align:start position:0% to fold them there you go since the last 00:30:32.559 --> 00:30:35.419 align:start position:0% to fold them there you go since the last one<00:30:32.740> is<00:30:32.890> well<00:30:33.070> kept 00:30:35.419 --> 00:30:35.429 align:start position:0% 00:30:35.429 --> 00:30:37.890 align:start position:0% yeah<00:30:36.429> this<00:30:36.610> is<00:30:36.669> a<00:30:36.700> definition<00:30:37.059> y<00:30:37.299> equals<00:30:37.840> I 00:30:37.890 --> 00:30:37.900 align:start position:0% yeah this is a definition y equals I 00:30:37.900 --> 00:30:40.110 align:start position:0% yeah this is a definition y equals I think<00:30:38.200> it's<00:30:38.320> used<00:30:38.530> everywhere<00:30:38.890> even<00:30:39.400> though 00:30:40.110 --> 00:30:40.120 align:start position:0% think it's used everywhere even though 00:30:40.120 --> 00:30:41.760 align:start position:0% think it's used everywhere even though the<00:30:40.240> grocery<00:30:40.600> see<00:30:40.780> brothers<00:30:41.110> good<00:30:41.260> money<00:30:41.530> but 00:30:41.760 --> 00:30:41.770 align:start position:0% the grocery see brothers good money but 00:30:41.770 --> 00:30:43.860 align:start position:0% the grocery see brothers good money but I<00:30:41.830> think<00:30:42.100> might<00:30:42.280> be<00:30:42.400> available<00:30:42.669> and<00:30:43.659> once 00:30:43.860 --> 00:30:43.870 align:start position:0% I think might be available and once 00:30:43.870 --> 00:30:45.690 align:start position:0% I think might be available and once again<00:30:44.080> I<00:30:44.110> want<00:30:44.200> to<00:30:44.289> stress<00:30:44.409> that<00:30:44.620> it<00:30:45.130> does<00:30:45.309> not 00:30:45.690 --> 00:30:45.700 align:start position:0% again I want to stress that it does not 00:30:45.700 --> 00:30:47.640 align:start position:0% again I want to stress that it does not they<00:30:45.880> let<00:30:46.030> protocol<00:30:46.570> and<00:30:46.960> to<00:30:47.200> the<00:30:47.289> region<00:30:47.559> the 00:30:47.640 --> 00:30:47.650 align:start position:0% they let protocol and to the region the 00:30:47.650 --> 00:30:49.710 align:start position:0% they let protocol and to the region the paper<00:30:47.860> but<00:30:48.190> it's<00:30:48.490> nevertheless<00:30:48.940> the<00:30:49.390> main 00:30:49.710 --> 00:30:49.720 align:start position:0% paper but it's nevertheless the main 00:30:49.720 --> 00:30:52.740 align:start position:0% paper but it's nevertheless the main idea<00:30:50.460> install<00:30:51.460> our<00:30:51.669> only<00:30:52.059> produced<00:30:52.539> to<00:30:52.659> the 00:30:52.740 --> 00:30:52.750 align:start position:0% idea install our only produced to the 00:30:52.750 --> 00:30:57.140 align:start position:0% idea install our only produced to the poet<00:30:52.929> went<00:30:53.289> to<00:30:53.380> show<00:30:53.590> that<00:30:53.890> a<00:30:54.100> function<00:30:55.030> g<00:30:55.830> GX 00:30:57.140 --> 00:30:57.150 align:start position:0% poet went to show that a function g GX 00:30:57.150 --> 00:30:59.880 align:start position:0% poet went to show that a function g GX is<00:30:58.150> not<00:30:58.450> a<00:30:58.659> rational<00:30:58.870> function<00:30:59.320> by<00:30:59.679> a 00:30:59.880 --> 00:30:59.890 align:start position:0% is not a rational function by a 00:30:59.890 --> 00:31:05.279 align:start position:0% is not a rational function by a polynomial<00:31:00.130> a<00:31:00.610> polynomial<00:31:00.880> of<00:31:01.179> degree<00:31:04.289> which 00:31:05.279 --> 00:31:05.289 align:start position:0% polynomial a polynomial of degree which 00:31:05.289 --> 00:31:07.020 align:start position:0% polynomial a polynomial of degree which is<00:31:05.320> the<00:31:05.440> same<00:31:05.559> that<00:31:06.010> the<00:31:06.250> order<00:31:06.610> of<00:31:06.760> the<00:31:06.820> first 00:31:07.020 --> 00:31:07.030 align:start position:0% is the same that the order of the first 00:31:07.030 --> 00:31:11.549 align:start position:0% is the same that the order of the first group<00:31:07.210> and<00:31:07.630> when<00:31:08.620> it's<00:31:08.770> a<00:31:08.919> tool<00:31:09.190> to<00:31:09.640> august<00:31:10.559> to 00:31:11.549 --> 00:31:11.559 align:start position:0% group and when it's a tool to august to 00:31:11.559 --> 00:31:17.639 align:start position:0% group and when it's a tool to august to check<00:31:11.740> this<00:31:11.890> efficiently<00:31:12.809> the<00:31:13.809> next<00:31:14.049> one 00:31:17.639 --> 00:31:17.649 align:start position:0% 00:31:17.649 --> 00:31:20.200 align:start position:0% yeah<00:31:18.649> and<00:31:19.009> the<00:31:19.309> problem<00:31:19.580> which<00:31:19.879> we<00:31:19.909> are<00:31:20.090> trying 00:31:20.200 --> 00:31:20.210 align:start position:0% yeah and the problem which we are trying 00:31:20.210 --> 00:31:22.629 align:start position:0% yeah and the problem which we are trying to<00:31:20.509> solve<00:31:20.749> is<00:31:21.080> vaccine<00:31:21.559> suggesting<00:31:22.100> or<00:31:22.399> just 00:31:22.629 --> 00:31:22.639 align:start position:0% to solve is vaccine suggesting or just 00:31:22.639 --> 00:31:26.349 align:start position:0% to solve is vaccine suggesting or just having<00:31:23.119> some<00:31:23.470> access<00:31:24.470> to<00:31:24.499> function<00:31:24.980> f<00:31:25.190> I<00:31:25.549> mean 00:31:26.349 --> 00:31:26.359 align:start position:0% having some access to function f I mean 00:31:26.359 --> 00:31:30.460 align:start position:0% having some access to function f I mean Oracle<00:31:27.049> access<00:31:28.059> that<00:31:29.059> means<00:31:29.899> that<00:31:30.200> you<00:31:30.320> might 00:31:30.460 --> 00:31:30.470 align:start position:0% Oracle access that means that you might 00:31:30.470 --> 00:31:34.810 align:start position:0% Oracle access that means that you might only<00:31:31.840> compare<00:31:32.840> with<00:31:33.080> some<00:31:33.409> values<00:31:33.889> so<00:31:34.309> just<00:31:34.549> to 00:31:34.810 --> 00:31:34.820 align:start position:0% only compare with some values so just to 00:31:34.820 --> 00:31:37.359 align:start position:0% only compare with some values so just to verify<00:31:34.999> as<00:31:35.419> well<00:31:35.960> as<00:31:36.049> from<00:31:36.289> the<00:31:36.379> function<00:31:36.859> and 00:31:37.359 --> 00:31:37.369 align:start position:0% verify as well as from the function and 00:31:37.369 --> 00:31:40.599 align:start position:0% verify as well as from the function and the<00:31:37.489> probe<00:31:37.730> just<00:31:38.230> get<00:31:39.230> stipulation<00:31:40.129> at<00:31:40.340> some 00:31:40.599 --> 00:31:40.609 align:start position:0% the probe just get stipulation at some 00:31:40.609 --> 00:31:45.279 align:start position:0% the probe just get stipulation at some points<00:31:40.989> and<00:31:41.989> we<00:31:42.109> want<00:31:42.379> to<00:31:43.779> and<00:31:44.779> the<00:31:44.869> reply<00:31:45.080> was 00:31:45.279 --> 00:31:45.289 align:start position:0% points and we want to and the reply was 00:31:45.289 --> 00:31:48.310 align:start position:0% points and we want to and the reply was to<00:31:45.470> know<00:31:45.619> that<00:31:45.859> this<00:31:45.980> function<00:31:46.220> is<00:31:46.639> indeed<00:31:47.320> a 00:31:48.310 --> 00:31:48.320 align:start position:0% to know that this function is indeed a 00:31:48.320 --> 00:32:03.970 align:start position:0% to know that this function is indeed a degree<00:32:01.659> let's<00:32:02.659> talk<00:32:02.869> about<00:32:02.989> the<00:32:03.169> fishes<00:32:03.529> so 00:32:03.970 --> 00:32:03.980 align:start position:0% degree let's talk about the fishes so 00:32:03.980 --> 00:32:05.859 align:start position:0% degree let's talk about the fishes so you<00:32:04.070> want<00:32:04.340> to<00:32:04.460> have<00:32:04.669> the<00:32:04.850> twelve<00:32:05.210> you<00:32:05.690> could 00:32:05.859 --> 00:32:05.869 align:start position:0% you want to have the twelve you could 00:32:05.869 --> 00:32:11.710 align:start position:0% you want to have the twelve you could have<00:32:06.169> this<00:32:06.799> way<00:32:07.100> so<00:32:08.409> well<00:32:10.330> you<00:32:11.330> can<00:32:11.480> trigger 00:32:11.710 --> 00:32:11.720 align:start position:0% have this way so well you can trigger 00:32:11.720 --> 00:32:15.070 align:start position:0% have this way so well you can trigger the<00:32:11.869> proofs<00:32:12.169> of<00:32:12.289> G<00:32:12.499> of<00:32:12.590> X<00:32:12.830> is<00:32:13.009> a<00:32:13.929> lot<00:32:14.929> of<00:32:15.019> the 00:32:15.070 --> 00:32:15.080 align:start position:0% the proofs of G of X is a lot of the 00:32:15.080 --> 00:32:16.659 align:start position:0% the proofs of G of X is a lot of the people<00:32:15.259> available<00:32:15.919> for<00:32:16.039> example<00:32:16.369> uses<00:32:16.639> a 00:32:16.659 --> 00:32:16.669 align:start position:0% people available for example uses a 00:32:16.669 --> 00:32:18.430 align:start position:0% people available for example uses a permit<00:32:17.119> because<00:32:17.389> it's<00:32:17.690> actually<00:32:17.840> gives<00:32:18.200> you<00:32:18.289> C 00:32:18.430 --> 00:32:18.440 align:start position:0% permit because it's actually gives you C 00:32:18.440 --> 00:32:24.190 align:start position:0% permit because it's actually gives you C to<00:32:18.799> be<00:32:18.950> found<00:32:19.190> is<00:32:19.399> very<00:32:19.429> alternative<00:32:21.279> to<00:32:23.200> what 00:32:24.190 --> 00:32:24.200 align:start position:0% to be found is very alternative to what 00:32:24.200 --> 00:32:26.379 align:start position:0% to be found is very alternative to what you<00:32:24.350> want<00:32:24.559> to<00:32:24.649> do<00:32:24.799> today<00:32:25.070> is<00:32:25.489> efficiency 00:32:26.379 --> 00:32:26.389 align:start position:0% you want to do today is efficiency 00:32:26.389 --> 00:32:28.280 align:start position:0% you want to do today is efficiency between<00:32:26.779> communication<00:32:27.409> between<00:32:27.619> premiere 00:32:28.280 --> 00:32:28.290 align:start position:0% between communication between premiere 00:32:28.290 --> 00:32:29.409 align:start position:0% between communication between premiere [Music] 00:32:29.409 --> 00:32:29.419 align:start position:0% [Music] 00:32:29.419 --> 00:32:31.839 align:start position:0% [Music] so<00:32:29.719> you<00:32:29.809> don't<00:32:29.959> want<00:32:30.259> an<00:32:30.469> to<00:32:31.459> check<00:32:31.700> this 00:32:31.839 --> 00:32:31.849 align:start position:0% so you don't want an to check this 00:32:31.849 --> 00:32:33.549 align:start position:0% so you don't want an to check this relationship<00:32:32.479> everywhere<00:32:32.929> you<00:32:33.080> need<00:32:33.229> also 00:32:33.549 --> 00:32:33.559 align:start position:0% relationship everywhere you need also 00:32:33.559 --> 00:32:36.009 align:start position:0% relationship everywhere you need also values<00:32:34.070> and<00:32:34.219> do<00:32:34.309> like<00:32:34.849> linear<00:32:35.419> network 00:32:36.009 --> 00:32:36.019 align:start position:0% values and do like linear network 00:32:36.019 --> 00:32:38.469 align:start position:0% values and do like linear network television<00:32:36.529> so<00:32:37.249> you<00:32:37.309> this<00:32:37.759> why<00:32:38.149> it's<00:32:38.299> called 00:32:38.469 --> 00:32:38.479 align:start position:0% television so you this why it's called 00:32:38.479 --> 00:32:40.570 align:start position:0% television so you this why it's called Oracle<00:32:39.109> accent<00:32:39.440> first<00:32:39.889> of<00:32:40.070> all<00:32:40.159> the<00:32:40.249> approver 00:32:40.570 --> 00:32:40.580 align:start position:0% Oracle accent first of all the approver 00:32:40.580 --> 00:32:43.599 align:start position:0% Oracle accent first of all the approver tells<00:32:40.909> I<00:32:41.269> know<00:32:41.330> some<00:32:41.749> set<00:32:41.929> of<00:32:41.989> bogeys<00:32:42.459> and<00:32:43.459> then 00:32:43.599 --> 00:32:43.609 align:start position:0% tells I know some set of bogeys and then 00:32:43.609 --> 00:32:46.560 align:start position:0% tells I know some set of bogeys and then commit<00:32:43.849> to<00:32:43.969> them<00:32:44.119> so<00:32:44.749> we<00:32:44.959> mentioned<00:32:45.320> it's<00:32:45.529> just 00:32:46.560 --> 00:32:46.570 align:start position:0% commit to them so we mentioned it's just 00:32:46.570 --> 00:32:50.889 align:start position:0% commit to them so we mentioned it's just to<00:32:47.570> those<00:32:47.749> numbers<00:32:48.139> which<00:32:49.009> you<00:32:49.719> break<00:32:50.719> the 00:32:50.889 --> 00:32:50.899 align:start position:0% to those numbers which you break the 00:32:50.899 --> 00:32:53.649 align:start position:0% to those numbers which you break the part<00:32:51.169> number<00:32:51.979> by<00:32:52.159> number<00:32:52.339> and<00:32:52.759> give<00:32:53.539> it<00:32:53.629> to 00:32:53.649 --> 00:32:53.659 align:start position:0% part number by number and give it to 00:32:53.659 --> 00:32:58.329 align:start position:0% part number by number and give it to someone<00:32:53.989> you<00:32:54.489> can<00:32:55.489> ask<00:32:55.820> for<00:32:57.009> certain<00:32:58.009> for 00:32:58.329 --> 00:32:58.339 align:start position:0% someone you can ask for certain for 00:32:58.339 --> 00:33:02.919 align:start position:0% someone you can ask for certain for those<00:32:59.179> numbers<00:32:59.419> one<00:33:00.379> by<00:33:00.409> one<00:33:00.739> and<00:33:01.479> the<00:33:02.479> service 00:33:02.919 --> 00:33:02.929 align:start position:0% those numbers one by one and the service 00:33:02.929 --> 00:33:05.199 align:start position:0% those numbers one by one and the service will<00:33:03.049> not<00:33:03.109> be<00:33:03.349> changed<00:33:03.709> in<00:33:04.519> principle<00:33:05.029> you<00:33:05.119> can 00:33:05.199 --> 00:33:05.209 align:start position:0% will not be changed in principle you can 00:33:05.209 --> 00:33:07.779 align:start position:0% will not be changed in principle you can ask<00:33:05.389> frozen<00:33:05.989> but<00:33:06.409> then<00:33:06.769> you<00:33:07.489> do<00:33:07.609> have<00:33:07.639> some 00:33:07.779 --> 00:33:07.789 align:start position:0% ask frozen but then you do have some 00:33:07.789 --> 00:33:10.719 align:start position:0% ask frozen but then you do have some work<00:33:08.059> pitches<00:33:08.450> in<00:33:08.629> norms<00:33:09.259> that<00:33:09.499> you<00:33:10.429> can<00:33:10.579> take 00:33:10.719 --> 00:33:10.729 align:start position:0% work pitches in norms that you can take 00:33:10.729 --> 00:33:13.449 align:start position:0% work pitches in norms that you can take one<00:33:10.969> by<00:33:11.119> one<00:33:11.359> and<00:33:11.709> the<00:33:12.709> small<00:33:12.919> number<00:33:12.950> of 00:33:13.449 --> 00:33:13.459 align:start position:0% one by one and the small number of 00:33:13.459 --> 00:33:15.519 align:start position:0% one by one and the small number of others<00:33:13.849> which<00:33:14.179> will<00:33:14.359> peak<00:33:14.659> from<00:33:14.929> this<00:33:15.109> trusted 00:33:15.519 --> 00:33:15.529 align:start position:0% others which will peak from this trusted 00:33:15.529 --> 00:33:18.069 align:start position:0% others which will peak from this trusted source<00:33:15.739> and<00:33:16.009> in<00:33:16.549> in<00:33:16.999> relatives<00:33:17.599> is<00:33:17.690> trusted 00:33:18.069 --> 00:33:18.079 align:start position:0% source and in in relatives is trusted 00:33:18.079 --> 00:33:21.129 align:start position:0% source and in in relatives is trusted sources<00:33:18.379> and<00:33:18.859> marriages<00:33:19.599> those<00:33:20.599> to<00:33:20.779> the<00:33:20.899> pulse 00:33:21.129 --> 00:33:21.139 align:start position:0% sources and marriages those to the pulse 00:33:21.139 --> 00:33:23.319 align:start position:0% sources and marriages those to the pulse will<00:33:21.440> be<00:33:21.469> not<00:33:21.799> for<00:33:21.950> you<00:33:22.039> to<00:33:22.219> say<00:33:22.249> alone<00:33:22.729> whether 00:33:23.319 --> 00:33:23.329 align:start position:0% will be not for you to say alone whether 00:33:23.329 --> 00:33:26.079 align:start position:0% will be not for you to say alone whether all<00:33:23.839> those<00:33:24.109> those<00:33:24.379> qualities<00:33:24.829> came<00:33:25.789> from 00:33:26.079 --> 00:33:26.089 align:start position:0% all those those qualities came from 00:33:26.089 --> 00:33:28.329 align:start position:0% all those those qualities came from sample<00:33:26.599> in<00:33:26.749> our<00:33:26.869> milk<00:33:27.079> all<00:33:27.739> those<00:33:27.919> as<00:33:28.039> well<00:33:28.219> as 00:33:28.329 --> 00:33:28.339 align:start position:0% sample in our milk all those as well as 00:33:28.339 --> 00:33:30.509 align:start position:0% sample in our milk all those as well as together<00:33:28.489> with<00:33:28.820> some<00:33:29.029> truth<00:33:29.509> which<00:33:29.779> you<00:33:29.929> again 00:33:30.509 --> 00:33:30.519 align:start position:0% together with some truth which you again 00:33:30.519 --> 00:33:33.129 align:start position:0% together with some truth which you again will<00:33:31.519> count<00:33:31.789> as<00:33:31.969> a<00:33:31.999> work<00:33:32.450> from<00:33:32.839> the<00:33:32.989> pool 00:33:33.129 --> 00:33:33.139 align:start position:0% will count as a work from the pool 00:33:33.139 --> 00:33:35.699 align:start position:0% will count as a work from the pool internal<00:33:33.440> which<00:33:33.619> was<00:33:34.190> small<00:33:34.879> degree<00:33:35.179> or 00:33:35.699 --> 00:33:35.709 align:start position:0% internal which was small degree or 00:33:35.709 --> 00:33:40.779 align:start position:0% internal which was small degree or unlikely<00:33:36.709> to<00:33:36.979> be<00:33:37.099> spawning<00:33:39.249> yahoo<00:33:40.249> proceeded 00:33:40.779 --> 00:33:40.789 align:start position:0% unlikely to be spawning yahoo proceeded 00:33:40.789 --> 00:33:44.769 align:start position:0% unlikely to be spawning yahoo proceeded was<00:33:40.940> a<00:33:40.969> form<00:33:41.269> apart<00:33:41.570> from<00:33:43.570> talking<00:33:44.570> of 00:33:44.769 --> 00:33:44.779 align:start position:0% was a form apart from talking of 00:33:44.779 --> 00:33:46.529 align:start position:0% was a form apart from talking of innocence<00:33:45.169> yeah 00:33:46.529 --> 00:33:46.539 align:start position:0% innocence yeah 00:33:46.539 --> 00:33:51.479 align:start position:0% innocence yeah there's<00:33:47.539> no<00:33:47.690> need<00:33:47.899> to<00:33:47.929> equate<00:33:48.320> in<00:33:48.559> other<00:33:48.679> words 00:33:51.479 --> 00:33:51.489 align:start position:0% 00:33:51.489 --> 00:33:54.890 align:start position:0% okay<00:33:53.049> next<00:33:54.049> one 00:33:54.890 --> 00:33:54.900 align:start position:0% okay next one 00:33:54.900 --> 00:33:58.040 align:start position:0% okay next one so<00:33:55.470> that<00:33:55.710> new<00:33:55.950> handsome<00:33:56.670> Austin<00:33:57.180> as<00:33:57.540> Alex<00:33:57.840> told 00:33:58.040 --> 00:33:58.050 align:start position:0% so that new handsome Austin as Alex told 00:33:58.050 --> 00:34:02.120 align:start position:0% so that new handsome Austin as Alex told to<00:33:59.210> query<00:34:00.210> all<00:34:00.630> the<00:34:00.900> vendors<00:34:01.260> follow<00:34:01.650> function 00:34:02.120 --> 00:34:02.130 align:start position:0% to query all the vendors follow function 00:34:02.130 --> 00:34:05.000 align:start position:0% to query all the vendors follow function them<00:34:02.309> ID<00:34:02.480> but<00:34:03.480> to<00:34:03.600> know<00:34:03.720> the<00:34:03.930> domain<00:34:04.230> is<00:34:04.530> real 00:34:05.000 --> 00:34:05.010 align:start position:0% them ID but to know the domain is real 00:34:05.010 --> 00:34:06.890 align:start position:0% them ID but to know the domain is real legit<00:34:05.670> it'll<00:34:05.940> be<00:34:06.059> enormous<00:34:06.300> number<00:34:06.870> of 00:34:06.890 --> 00:34:06.900 align:start position:0% legit it'll be enormous number of 00:34:06.900 --> 00:34:09.590 align:start position:0% legit it'll be enormous number of queries<00:34:07.260> and<00:34:07.740> this<00:34:08.250> is<00:34:08.370> the<00:34:08.460> theme<00:34:08.669> we<00:34:08.940> were 00:34:09.590 --> 00:34:09.600 align:start position:0% queries and this is the theme we were 00:34:09.600 --> 00:34:11.540 align:start position:0% queries and this is the theme we were trying<00:34:09.870> to<00:34:09.899> avoid<00:34:10.169> and<00:34:10.530> the<00:34:10.649> question<00:34:10.950> is<00:34:11.129> that 00:34:11.540 --> 00:34:11.550 align:start position:0% trying to avoid and the question is that 00:34:11.550 --> 00:34:16.220 align:start position:0% trying to avoid and the question is that one<00:34:13.399> candies<00:34:14.399> we<00:34:14.669> achieved<00:34:15.120> with<00:34:15.360> what 00:34:16.220 --> 00:34:16.230 align:start position:0% one candies we achieved with what 00:34:16.230 --> 00:34:18.590 align:start position:0% one candies we achieved with what algorithmic<00:34:17.100> number<00:34:17.399> of<00:34:17.460> queries<00:34:17.700> Reggie<00:34:18.179> is 00:34:18.590 --> 00:34:18.600 align:start position:0% algorithmic number of queries Reggie is 00:34:18.600 --> 00:34:20.930 align:start position:0% algorithmic number of queries Reggie is remember<00:34:19.080> is<00:34:19.260> the<00:34:19.470> degree<00:34:19.919> of<00:34:19.950> power<00:34:20.280> with<00:34:20.850> the 00:34:20.930 --> 00:34:20.940 align:start position:0% remember is the degree of power with the 00:34:20.940 --> 00:34:23.840 align:start position:0% remember is the degree of power with the self<00:34:21.230> the<00:34:22.230> answer<00:34:22.560> is<00:34:22.679> yes<00:34:23.040> this<00:34:23.370> is<00:34:23.580> really 00:34:23.840 --> 00:34:23.850 align:start position:0% self the answer is yes this is really 00:34:23.850 --> 00:34:28.940 align:start position:0% self the answer is yes this is really ingenious<00:34:25.100> protocol<00:34:27.200> the<00:34:28.200> formal<00:34:28.470> definition 00:34:28.940 --> 00:34:28.950 align:start position:0% ingenious protocol the formal definition 00:34:28.950 --> 00:34:32.860 align:start position:0% ingenious protocol the formal definition of<00:34:29.070> so<00:34:29.520> the<00:34:29.669> problem<00:34:29.970> we're<00:34:30.149> trying<00:34:30.179> to<00:34:30.620> solve 00:34:32.860 --> 00:34:32.870 align:start position:0% of so the problem we're trying to solve 00:34:32.870 --> 00:34:37.790 align:start position:0% of so the problem we're trying to solve by<00:34:33.870> working<00:34:34.230> in<00:34:34.700> interactive<00:34:35.960> or<00:34:36.960> growth 00:34:37.790 --> 00:34:37.800 align:start position:0% by working in interactive or growth 00:34:37.800 --> 00:34:41.990 align:start position:0% by working in interactive or growth model<00:34:39.830> anybody<00:34:40.830> is<00:34:40.889> familiar<00:34:41.040> with<00:34:41.429> internal 00:34:41.990 --> 00:34:42.000 align:start position:0% model anybody is familiar with internal 00:34:42.000 --> 00:34:50.270 align:start position:0% model anybody is familiar with internal growth<00:34:42.240> model<00:34:43.580> okay<00:34:45.320> okay<00:34:46.370> explain<00:34:49.280> direct 00:34:50.270 --> 00:34:50.280 align:start position:0% growth model okay okay explain direct 00:34:50.280 --> 00:34:51.440 align:start position:0% growth model okay okay explain direct interactive<00:34:51.030> host 00:34:51.440 --> 00:34:51.450 align:start position:0% interactive host 00:34:51.450 --> 00:34:56.200 align:start position:0% interactive host I<00:34:51.600> think<00:34:51.780> everybody<00:34:52.260> knows<00:34:53.899> this<00:34:54.899> B<00:34:55.230> is<00:34:55.980> a 00:34:56.200 --> 00:34:56.210 align:start position:0% I think everybody knows this B is a 00:34:56.210 --> 00:35:03.800 align:start position:0% I think everybody knows this B is a promoter<00:35:00.410> the<00:35:01.850> the<00:35:02.850> Bruce<00:35:03.090> data<00:35:03.480> the 00:35:03.800 --> 00:35:03.810 align:start position:0% promoter the the Bruce data the 00:35:03.810 --> 00:35:07.490 align:start position:0% promoter the the Bruce data the Provos<00:35:04.080> data<00:35:04.350> is<00:35:05.280> not<00:35:05.670> saying<00:35:06.630> just<00:35:07.140> as<00:35:07.290> a 00:35:07.490 --> 00:35:07.500 align:start position:0% Provos data is not saying just as a 00:35:07.500 --> 00:35:11.060 align:start position:0% Provos data is not saying just as a little<00:35:07.830> piece<00:35:08.100> of<00:35:08.160> information<00:35:08.690> they<00:35:09.690> send<00:35:10.110> in 00:35:11.060 --> 00:35:11.070 align:start position:0% little piece of information they send in 00:35:11.070 --> 00:35:16.250 align:start position:0% little piece of information they send in terms<00:35:11.370> of<00:35:11.700> Oracle's<00:35:12.390> edge<00:35:13.170> tables<00:35:14.030> and<00:35:15.260> the 00:35:16.250 --> 00:35:16.260 align:start position:0% terms of Oracle's edge tables and the 00:35:16.260 --> 00:35:18.650 align:start position:0% terms of Oracle's edge tables and the verifier<00:35:16.710> never<00:35:17.070> fire<00:35:17.430> when<00:35:18.120> he<00:35:18.330> received 00:35:18.650 --> 00:35:18.660 align:start position:0% verifier never fire when he received 00:35:18.660 --> 00:35:21.170 align:start position:0% verifier never fire when he received this<00:35:18.750> table<00:35:19.170> with<00:35:19.320> edge<00:35:19.650> table<00:35:19.980> he<00:35:20.790> can<00:35:20.970> only 00:35:21.170 --> 00:35:21.180 align:start position:0% this table with edge table he can only 00:35:21.180 --> 00:35:25.070 align:start position:0% this table with edge table he can only query<00:35:21.540> a<00:35:21.990> small<00:35:22.530> number<00:35:22.920> of<00:35:23.100> points<00:35:23.810> this<00:35:24.810> is 00:35:25.070 --> 00:35:25.080 align:start position:0% query a small number of points this is 00:35:25.080 --> 00:35:29.330 align:start position:0% query a small number of points this is called<00:35:26.150> easily<00:35:27.150> model<00:35:27.510> and<00:35:28.100> interactive<00:35:29.100> or 00:35:29.330 --> 00:35:29.340 align:start position:0% called easily model and interactive or 00:35:29.340 --> 00:35:32.450 align:start position:0% called easily model and interactive or growth<00:35:29.850> model<00:35:30.270> it<00:35:30.510> just<00:35:30.780> combines<00:35:31.170> those<00:35:32.160> to 00:35:32.450 --> 00:35:32.460 align:start position:0% growth model it just combines those to 00:35:32.460 --> 00:35:35.060 align:start position:0% growth model it just combines those to go<00:35:32.610> those<00:35:33.030> two<00:35:33.210> goals<00:35:33.390> this<00:35:34.350> internet 00:35:35.060 --> 00:35:35.070 align:start position:0% go those two goals this internet 00:35:35.070 --> 00:35:37.850 align:start position:0% go those two goals this internet protocol<00:35:35.670> from<00:35:36.210> which<00:35:36.420> every<00:35:37.320> message<00:35:37.620> from 00:35:37.850 --> 00:35:37.860 align:start position:0% protocol from which every message from 00:35:37.860 --> 00:35:39.920 align:start position:0% protocol from which every message from the<00:35:38.130> prover<00:35:38.520> is<00:35:38.640> a<00:35:38.700> kind<00:35:39.000> of<00:35:39.150> Oracle<00:35:39.600> like 00:35:39.920 --> 00:35:39.930 align:start position:0% the prover is a kind of Oracle like 00:35:39.930 --> 00:35:42.200 align:start position:0% the prover is a kind of Oracle like table<00:35:40.440> from<00:35:40.680> which<00:35:40.830> the<00:35:40.950> provider<00:35:41.130> queries<00:35:41.880> on 00:35:42.200 --> 00:35:42.210 align:start position:0% table from which the provider queries on 00:35:42.210 --> 00:35:45.460 align:start position:0% table from which the provider queries on the<00:35:42.750> small<00:35:43.290> Mart<00:35:43.530> feeds 00:35:45.460 --> 00:35:45.470 align:start position:0% the small Mart feeds 00:35:45.470 --> 00:35:47.740 align:start position:0% the small Mart feeds in<00:35:45.770> response<00:35:46.160> and<00:35:46.580> the<00:35:46.700> next<00:35:47.119> answer<00:35:47.390> from 00:35:47.740 --> 00:35:47.750 align:start position:0% in response and the next answer from 00:35:47.750 --> 00:35:51.120 align:start position:0% in response and the next answer from Chloe<00:35:47.990> is<00:35:48.320> a<00:35:48.349> gated<00:35:48.680> table<00:35:49.010> and<00:35:50.020> Wednesday 00:35:51.120 --> 00:35:51.130 align:start position:0% Chloe is a gated table and Wednesday 00:35:51.130 --> 00:35:53.470 align:start position:0% Chloe is a gated table and Wednesday wouldn't<00:35:52.130> think<00:35:52.250> about<00:35:52.369> interactive<00:35:53.119> Oracle 00:35:53.470 --> 00:35:53.480 align:start position:0% wouldn't think about interactive Oracle 00:35:53.480 --> 00:35:54.520 align:start position:0% wouldn't think about interactive Oracle proof<00:35:53.660> of<00:35:53.780> activity 00:35:54.520 --> 00:35:54.530 align:start position:0% proof of activity 00:35:54.530 --> 00:35:56.260 align:start position:0% proof of activity the<00:35:54.740> first<00:35:55.040> message<00:35:55.220> format<00:35:55.760> for<00:35:56.030> months 00:35:56.260 --> 00:35:56.270 align:start position:0% the first message format for months 00:35:56.270 --> 00:35:59.109 align:start position:0% the first message format for months should<00:35:56.510> be<00:35:56.660> an<00:35:56.720> hour<00:35:57.099> Oracle<00:35:58.099> to<00:35:58.490> the<00:35:58.580> function 00:35:59.109 --> 00:35:59.119 align:start position:0% should be an hour Oracle to the function 00:35:59.119 --> 00:36:02.650 align:start position:0% should be an hour Oracle to the function and<00:36:00.190> we<00:36:01.190> want<00:36:01.490> to<00:36:01.580> prove<00:36:01.790> that<00:36:02.090> it<00:36:02.240> is<00:36:02.390> a 00:36:02.650 --> 00:36:02.660 align:start position:0% and we want to prove that it is a 00:36:02.660 --> 00:36:07.810 align:start position:0% and we want to prove that it is a polynomial<00:36:02.900> of<00:36:03.320> degree<00:36:06.580> Kendall<00:36:07.580> in<00:36:07.640> fact 00:36:07.810 --> 00:36:07.820 align:start position:0% polynomial of degree Kendall in fact 00:36:07.820 --> 00:36:11.800 align:start position:0% polynomial of degree Kendall in fact once<00:36:08.060> every<00:36:08.770> every<00:36:09.770> every<00:36:10.310> other<00:36:10.580> Oracle<00:36:11.119> will 00:36:11.800 --> 00:36:11.810 align:start position:0% once every every every other Oracle will 00:36:11.810 --> 00:36:14.710 align:start position:0% once every every every other Oracle will also<00:36:12.140> publish<00:36:12.290> a<00:36:12.560> function<00:36:13.460> be<00:36:14.210> the<00:36:14.270> case<00:36:14.510> all 00:36:14.710 --> 00:36:14.720 align:start position:0% also publish a function be the case all 00:36:14.720 --> 00:36:22.260 align:start position:0% also publish a function be the case all right 00:36:22.260 --> 00:36:22.270 align:start position:0% 00:36:22.270 --> 00:36:25.630 align:start position:0% so<00:36:23.270> just<00:36:23.540> think<00:36:24.260> of<00:36:24.320> them<00:36:24.500> ideal<00:36:24.800> you<00:36:25.310> have<00:36:25.520> two 00:36:25.630 --> 00:36:25.640 align:start position:0% so just think of them ideal you have two 00:36:25.640 --> 00:36:29.380 align:start position:0% so just think of them ideal you have two functions<00:36:25.820> F<00:36:26.330> and<00:36:26.660> G<00:36:26.950> any<00:36:27.950> functions<00:36:28.550> not 00:36:29.380 --> 00:36:29.390 align:start position:0% functions F and G any functions not 00:36:29.390 --> 00:36:35.790 align:start position:0% functions F and G any functions not animals<00:36:30.280> and<00:36:31.280> they<00:36:31.430> can<00:36:31.609> service 00:36:35.790 --> 00:36:35.800 align:start position:0% 00:36:35.800 --> 00:36:38.870 align:start position:0% and<00:36:36.430> then<00:36:36.580> just<00:36:36.820> count<00:36:37.300> the<00:36:37.990> number<00:36:38.020> of<00:36:38.410> points 00:36:38.870 --> 00:36:38.880 align:start position:0% and then just count the number of points 00:36:38.880 --> 00:36:43.070 align:start position:0% and then just count the number of points in<00:36:39.880> which<00:36:40.750> they<00:36:41.050> are<00:36:41.110> different 00:36:43.070 --> 00:36:43.080 align:start position:0% in which they are different 00:36:43.080 --> 00:36:46.680 align:start position:0% in which they are different an<00:36:44.080> example<00:36:44.470> is<00:36:44.770> two<00:36:45.040> and<00:36:45.280> I<00:36:45.460> just<00:36:45.730> take<00:36:46.420> the 00:36:46.680 --> 00:36:46.690 align:start position:0% an example is two and I just take the 00:36:46.690 --> 00:36:48.660 align:start position:0% an example is two and I just take the relative<00:36:47.320> time<00:36:47.470> distance<00:36:47.830> or<00:36:48.070> divide<00:36:48.550> this 00:36:48.660 --> 00:36:48.670 align:start position:0% relative time distance or divide this 00:36:48.670 --> 00:36:51.480 align:start position:0% relative time distance or divide this number<00:36:48.730> by<00:36:49.030> its<00:36:49.420> estimate<00:36:49.900> so<00:36:50.619> that<00:36:50.770> my<00:36:50.980> metric 00:36:51.480 --> 00:36:51.490 align:start position:0% number by its estimate so that my metric 00:36:51.490 --> 00:36:54.540 align:start position:0% number by its estimate so that my metric will<00:36:51.640> be<00:36:51.820> between<00:36:52.119> zero<00:36:52.720> and<00:36:52.810> one<00:36:53.050> and<00:36:53.830> this<00:36:54.490> is 00:36:54.540 --> 00:36:54.550 align:start position:0% will be between zero and one and this is 00:36:54.550 --> 00:36:56.580 align:start position:0% will be between zero and one and this is just<00:36:54.910> geometric<00:36:55.540> it<00:36:55.690> has<00:36:55.869> all<00:36:56.080> properties<00:36:56.500> of 00:36:56.580 --> 00:36:56.590 align:start position:0% just geometric it has all properties of 00:36:56.590 --> 00:37:04.070 align:start position:0% just geometric it has all properties of matrix<00:36:57.010> symmetry<00:36:58.560> that<00:36:59.560> dragon<00:37:00.010> in<00:37:00.100> water 00:37:04.070 --> 00:37:04.080 align:start position:0% 00:37:04.080 --> 00:37:08.820 align:start position:0% yeah<00:37:05.110> fry<00:37:05.710> fry<00:37:06.330> oxide<00:37:07.330> with<00:37:07.480> them<00:37:07.630> in<00:37:08.440> the<00:37:08.650> next 00:37:08.820 --> 00:37:08.830 align:start position:0% yeah fry fry oxide with them in the next 00:37:08.830 --> 00:37:13.010 align:start position:0% yeah fry fry oxide with them in the next one<00:37:10.200> these<00:37:11.200> are<00:37:11.350> the<00:37:11.410> parameters<00:37:11.560> of<00:37:11.890> Prai<00:37:12.190> and 00:37:13.010 --> 00:37:13.020 align:start position:0% one these are the parameters of Prai and 00:37:13.020 --> 00:37:18.060 align:start position:0% one these are the parameters of Prai and it's<00:37:15.660> exactly<00:37:16.660> takes<00:37:16.900> logarithmic<00:37:17.500> number<00:37:17.710> of 00:37:18.060 --> 00:37:18.070 align:start position:0% it's exactly takes logarithmic number of 00:37:18.070 --> 00:37:20.850 align:start position:0% it's exactly takes logarithmic number of queries<00:37:18.369> but<00:37:19.170> what<00:37:20.170> I<00:37:20.200> want<00:37:20.440> to<00:37:20.470> stress<00:37:20.830> here 00:37:20.850 --> 00:37:20.860 align:start position:0% queries but what I want to stress here 00:37:20.860 --> 00:37:28.400 align:start position:0% queries but what I want to stress here is<00:37:21.660> the<00:37:22.660> sounds<00:37:23.110> service<00:37:27.060> uses<00:37:28.060> some 00:37:28.400 --> 00:37:28.410 align:start position:0% is the sounds service uses some 00:37:28.410 --> 00:37:32.460 align:start position:0% is the sounds service uses some parameter<00:37:29.410> Delta<00:37:30.420> our<00:37:31.420> initial<00:37:31.990> function 00:37:32.460 --> 00:37:32.470 align:start position:0% parameter Delta our initial function 00:37:32.470 --> 00:37:34.350 align:start position:0% parameter Delta our initial function our<00:37:32.650> initial<00:37:33.040> function<00:37:33.250> which<00:37:34.030> will<00:37:34.180> provide 00:37:34.350 --> 00:37:34.360 align:start position:0% our initial function which will provide 00:37:34.360 --> 00:37:39.290 align:start position:0% our initial function which will provide all<00:37:34.630> the<00:37:34.780> Oracle<00:37:35.170> to<00:37:35.260> throw<00:37:35.410> coracle<00:37:35.830> for<00:37:37.770> each 00:37:39.290 --> 00:37:39.300 align:start position:0% all the Oracle to throw coracle for each 00:37:39.300 --> 00:37:42.599 align:start position:0% all the Oracle to throw coracle for each can<00:37:40.300> it<00:37:41.170> may<00:37:41.320> not<00:37:41.560> be<00:37:41.740> a<00:37:41.770> polynomial 00:37:42.599 --> 00:37:42.609 align:start position:0% can it may not be a polynomial 00:37:42.609 --> 00:37:47.150 align:start position:0% can it may not be a polynomial it<00:37:42.670> may<00:37:43.359> be<00:37:43.420> some<00:37:43.690> function<00:37:44.109> some<00:37:44.290> function<00:37:44.890> f 00:37:47.150 --> 00:37:47.160 align:start position:0% it may be some function some function f 00:37:47.160 --> 00:37:51.480 align:start position:0% it may be some function some function f which<00:37:48.160> is<00:37:49.290> which<00:37:50.290> has<00:37:50.320> some<00:37:50.650> distance<00:37:51.070> from 00:37:51.480 --> 00:37:51.490 align:start position:0% which is which has some distance from 00:37:51.490 --> 00:37:56.180 align:start position:0% which is which has some distance from the<00:37:51.850> space<00:37:52.090> of<00:37:52.420> reed-solomon<00:37:52.660> codes<00:37:53.200> and<00:37:55.020> fry 00:37:56.180 --> 00:37:56.190 align:start position:0% the space of reed-solomon codes and fry 00:37:56.190 --> 00:38:01.080 align:start position:0% the space of reed-solomon codes and fry is<00:37:57.190> unable<00:37:57.550> to<00:37:57.840> distinguish<00:37:59.250> precisely<00:38:00.250> the 00:38:01.080 --> 00:38:01.090 align:start position:0% is unable to distinguish precisely the 00:38:01.090 --> 00:38:02.940 align:start position:0% is unable to distinguish precisely the functions<00:38:01.660> which<00:38:01.810> are<00:38:02.050> accessible<00:38:02.380> normals 00:38:02.940 --> 00:38:02.950 align:start position:0% functions which are accessible normals 00:38:02.950 --> 00:38:06.540 align:start position:0% functions which are accessible normals and<00:38:03.190> the<00:38:03.670> functions<00:38:04.650> which<00:38:05.650> which<00:38:06.190> has<00:38:06.369> some 00:38:06.540 --> 00:38:06.550 align:start position:0% and the functions which which has some 00:38:06.550 --> 00:38:07.859 align:start position:0% and the functions which which has some distance<00:38:06.850> from<00:38:06.970> the<00:38:07.090> space<00:38:07.330> over<00:38:07.660> summer 00:38:07.859 --> 00:38:07.869 align:start position:0% distance from the space over summer 00:38:07.869 --> 00:38:11.070 align:start position:0% distance from the space over summer coats<00:38:08.609> just<00:38:09.609> the<00:38:10.119> other<00:38:10.240> night<00:38:10.330> I<00:38:10.660> think<00:38:10.840> here 00:38:11.070 --> 00:38:11.080 align:start position:0% coats just the other night I think here 00:38:11.080 --> 00:38:12.070 align:start position:0% coats just the other night I think here we<00:38:11.109> will<00:38:11.380> do 00:38:12.070 --> 00:38:12.080 align:start position:0% we will do 00:38:12.080 --> 00:38:14.800 align:start position:0% we will do another<00:38:12.380> solid<00:38:12.770> example<00:38:13.310> men<00:38:13.490> okay<00:38:14.090> so<00:38:14.510> friend 00:38:14.800 --> 00:38:14.810 align:start position:0% another solid example men okay so friend 00:38:14.810 --> 00:38:16.720 align:start position:0% another solid example men okay so friend initially<00:38:15.770> problem<00:38:16.190> the<00:38:16.340> kind<00:38:16.490> of<00:38:16.550> bull 00:38:16.720 --> 00:38:16.730 align:start position:0% initially problem the kind of bull 00:38:16.730 --> 00:38:21.010 align:start position:0% initially problem the kind of bull remember<00:38:17.030> was<00:38:17.210> promised<00:38:17.870> let's<00:38:18.290> just<00:38:19.810> say<00:38:20.810> we 00:38:21.010 --> 00:38:21.020 align:start position:0% remember was promised let's just say we 00:38:21.020 --> 00:38:22.210 align:start position:0% remember was promised let's just say we have<00:38:21.230> a<00:38:21.260> full<00:38:21.530> animal<00:38:21.830> it<00:38:21.920> was<00:38:21.980> immoral 00:38:22.210 --> 00:38:22.220 align:start position:0% have a full animal it was immoral 00:38:22.220 --> 00:38:25.480 align:start position:0% have a full animal it was immoral collect<00:38:23.410> we<00:38:24.410> gathered<00:38:24.710> some<00:38:24.740> problems<00:38:25.340> of 00:38:25.480 --> 00:38:25.490 align:start position:0% collect we gathered some problems of 00:38:25.490 --> 00:38:29.860 align:start position:0% collect we gathered some problems of birth<00:38:25.760> so<00:38:26.270> for<00:38:27.730> for<00:38:28.730> a<00:38:28.760> capital<00:38:29.180> it<00:38:29.330> will<00:38:29.720> be<00:38:29.840> a 00:38:29.860 --> 00:38:29.870 align:start position:0% birth so for for a capital it will be a 00:38:29.870 --> 00:38:32.470 align:start position:0% birth so for for a capital it will be a polling<00:38:30.380> of<00:38:30.500> like<00:38:30.710> we<00:38:31.120> happy<00:38:32.120> already<00:38:32.270> knows 00:38:32.470 --> 00:38:32.480 align:start position:0% polling of like we happy already knows 00:38:32.480 --> 00:38:34.030 align:start position:0% polling of like we happy already knows as<00:38:32.690> a<00:38:32.810> suitable<00:38:33.080> I<00:38:33.260> don't<00:38:33.470> know<00:38:33.530> just<00:38:33.770> to<00:38:33.860> show 00:38:34.030 --> 00:38:34.040 align:start position:0% as a suitable I don't know just to show 00:38:34.040 --> 00:38:38.950 align:start position:0% as a suitable I don't know just to show you<00:38:34.100> how<00:38:34.370> to<00:38:34.400> fireworks<00:38:34.880> and<00:38:35.500> we<00:38:36.500> get<00:38:36.830> its<00:38:37.960> so 00:38:38.950 --> 00:38:38.960 align:start position:0% you how to fireworks and we get its so 00:38:38.960 --> 00:38:44.620 align:start position:0% you how to fireworks and we get its so from<00:38:39.740> the<00:38:40.190> main<00:38:42.640> we<00:38:43.640> get<00:38:43.820> a<00:38:43.850> simulation<00:38:44.270> so 00:38:44.620 --> 00:38:44.630 align:start position:0% from the main we get a simulation so 00:38:44.630 --> 00:38:46.630 align:start position:0% from the main we get a simulation so let's<00:38:44.900> meditate<00:38:45.320> with<00:38:45.650> our<00:38:45.830> domain<00:38:46.220> this<00:38:46.340> mole 00:38:46.630 --> 00:38:46.640 align:start position:0% let's meditate with our domain this mole 00:38:46.640 --> 00:38:52.120 align:start position:0% let's meditate with our domain this mole is<00:38:46.880> just<00:38:47.000> four<00:38:47.990> elements<00:38:48.740> are<00:38:48.920> 1<00:38:49.100> 2<00:38:49.850> 3<00:38:49.880> &<00:38:50.510> 4<00:38:50.980> as<00:38:51.980> I 00:38:52.120 --> 00:38:52.130 align:start position:0% is just four elements are 1 2 3 & 4 as I 00:38:52.130 --> 00:39:00.280 align:start position:0% is just four elements are 1 2 3 & 4 as I think<00:38:52.340> of<00:38:52.460> a<00:38:52.520> function<00:38:58.450> for<00:38:59.450> a<00:38:59.510> small<00:38:59.780> inner<00:39:00.050> is 00:39:00.280 --> 00:39:00.290 align:start position:0% think of a function for a small inner is 00:39:00.290 --> 00:39:08.290 align:start position:0% think of a function for a small inner is just<00:39:00.560> some<00:39:01.160> function<00:39:03.460> for<00:39:04.460> is<00:39:04.550> this<00:39:06.820> well<00:39:07.820> 1<00:39:08.150> 2 00:39:08.290 --> 00:39:08.300 align:start position:0% just some function for is this well 1 2 00:39:08.300 --> 00:39:11.830 align:start position:0% just some function for is this well 1 2 3<00:39:08.420> 4<00:39:08.690> wasn't<00:39:09.080> away<00:39:09.260> the<00:39:09.410> stress<00:39:09.680> by<00:39:09.890> looking<00:39:10.840> at 00:39:11.830 --> 00:39:11.840 align:start position:0% 3 4 wasn't away the stress by looking at 00:39:11.840 --> 00:39:14.500 align:start position:0% 3 4 wasn't away the stress by looking at and<00:39:12.200> I'll<00:39:12.680> say<00:39:12.890> I<00:39:12.920> know<00:39:13.130> that<00:39:13.430> degree<00:39:14.210> of<00:39:14.360> this 00:39:14.500 --> 00:39:14.510 align:start position:0% and I'll say I know that degree of this 00:39:14.510 --> 00:39:19.630 align:start position:0% and I'll say I know that degree of this pulling<00:39:14.900> our<00:39:15.020> goal<00:39:17.710> and<00:39:18.710> say<00:39:18.920> is<00:39:18.980> equal<00:39:19.130> to<00:39:19.400> 0 00:39:19.630 --> 00:39:19.640 align:start position:0% pulling our goal and say is equal to 0 00:39:19.640 --> 00:39:24.360 align:start position:0% pulling our goal and say is equal to 0 so<00:39:19.970> I<00:39:20.000> will<00:39:20.300> just<00:39:20.810> have<00:39:21.020> this<00:39:21.200> a<00:39:22.360> lot<00:39:23.360> at<00:39:23.480> once 00:39:24.360 --> 00:39:24.370 align:start position:0% so I will just have this a lot at once 00:39:24.370 --> 00:39:27.070 align:start position:0% so I will just have this a lot at once and<00:39:25.370> it<00:39:25.940> have<00:39:26.060> a<00:39:26.090> look<00:39:26.300> horrible<00:39:26.660> access<00:39:26.930> to 00:39:27.070 --> 00:39:27.080 align:start position:0% and it have a look horrible access to 00:39:27.080 --> 00:39:30.550 align:start position:0% and it have a look horrible access to lives<00:39:27.320> to<00:39:27.590> that<00:39:27.890> taste<00:39:28.130> is<00:39:28.280> a<00:39:28.430> different<00:39:29.560> like 00:39:30.550 --> 00:39:30.560 align:start position:0% lives to that taste is a different like 00:39:30.560 --> 00:39:33.700 align:start position:0% lives to that taste is a different like this<00:39:31.450> so<00:39:32.450> when<00:39:32.690> your<00:39:32.810> opponent<00:39:33.230> multi<00:39:33.500> grew 00:39:33.700 --> 00:39:33.710 align:start position:0% this so when your opponent multi grew 00:39:33.710 --> 00:39:35.590 align:start position:0% this so when your opponent multi grew honest<00:39:34.010> I<00:39:34.250> thank<00:39:34.790> you<00:39:34.880> for<00:39:35.000> your<00:39:35.180> ability<00:39:35.570> to 00:39:35.590 --> 00:39:35.600 align:start position:0% honest I thank you for your ability to 00:39:35.600 --> 00:39:40.200 align:start position:0% honest I thank you for your ability to enjoy<00:39:35.720> teacher 00:39:40.200 --> 00:39:40.210 align:start position:0% 00:39:40.210 --> 00:39:45.460 align:start position:0% those<00:39:41.210> are<00:39:41.390> my<00:39:41.830> invisible<00:39:43.720> Oracle<00:39:44.720> exercises 00:39:45.460 --> 00:39:45.470 align:start position:0% those are my invisible Oracle exercises 00:39:45.470 --> 00:39:47.380 align:start position:0% those are my invisible Oracle exercises I<00:39:45.650> would<00:39:45.950> can<00:39:46.460> assimilate<00:39:46.760> him<00:39:47.000> with<00:39:47.270> some 00:39:47.380 --> 00:39:47.390 align:start position:0% I would can assimilate him with some 00:39:47.390 --> 00:39:50.530 align:start position:0% I would can assimilate him with some people<00:39:47.690> where<00:39:47.870> I<00:39:47.900> can<00:39:48.110> particular<00:39:48.590> volume<00:39:49.540> so 00:39:50.530 --> 00:39:50.540 align:start position:0% people where I can particular volume so 00:39:50.540 --> 00:39:52.000 align:start position:0% people where I can particular volume so what<00:39:50.780> would<00:39:50.930> I<00:39:51.020> do<00:39:51.080> and<00:39:51.380> what<00:39:51.590> I'm<00:39:51.710> willing 00:39:52.000 --> 00:39:52.010 align:start position:0% what would I do and what I'm willing 00:39:52.010 --> 00:39:55.630 align:start position:0% what would I do and what I'm willing again<00:39:52.430> as<00:39:52.670> a<00:39:52.730> result<00:39:53.240> was<00:39:53.450> a<00:39:53.510> primary<00:39:53.750> I<00:39:54.640> can 00:39:55.630 --> 00:39:55.640 align:start position:0% again as a result was a primary I can 00:39:55.640 --> 00:39:57.790 align:start position:0% again as a result was a primary I can treat<00:39:55.850> all<00:39:56.090> the<00:39:56.210> boxes<00:39:56.570> ones<00:39:56.810> because<00:39:57.410> if<00:39:57.680> I 00:39:57.790 --> 00:39:57.800 align:start position:0% treat all the boxes ones because if I 00:39:57.800 --> 00:39:59.590 align:start position:0% treat all the boxes ones because if I would<00:39:58.040> I<00:39:58.280> would<00:39:58.610> just<00:39:58.760> interpolate<00:39:59.210> this 00:39:59.590 --> 00:39:59.600 align:start position:0% would I would just interpolate this 00:39:59.600 --> 00:40:03.010 align:start position:0% would I would just interpolate this locally<00:40:00.350> by<00:40:00.770> myself<00:40:01.340> trusted<00:40:01.970> source<00:40:02.180> and<00:40:02.450> get 00:40:03.010 --> 00:40:03.020 align:start position:0% locally by myself trusted source and get 00:40:03.020 --> 00:40:06.660 align:start position:0% locally by myself trusted source and get the<00:40:03.110> master<00:40:03.440> wizard 00:40:06.660 --> 00:40:06.670 align:start position:0% 00:40:06.670 --> 00:40:09.360 align:start position:0% but<00:40:07.600> it<00:40:07.750> was<00:40:07.870> well<00:40:08.080> as<00:40:08.200> they<00:40:08.380> got<00:40:08.560> or<00:40:08.830> from<00:40:09.100> the 00:40:09.360 --> 00:40:09.370 align:start position:0% but it was well as they got or from the 00:40:09.370 --> 00:40:11.250 align:start position:0% but it was well as they got or from the Greek<00:40:09.760> literally<00:40:10.210> just<00:40:10.420> from<00:40:10.600> some<00:40:10.780> honey 00:40:11.250 --> 00:40:11.260 align:start position:0% Greek literally just from some honey 00:40:11.260 --> 00:40:13.920 align:start position:0% Greek literally just from some honey so<00:40:11.680> if<00:40:11.800> I<00:40:11.920> would<00:40:11.980> get<00:40:12.280> this<00:40:12.550> in<00:40:12.850> full<00:40:13.600> I<00:40:13.630> will 00:40:13.920 --> 00:40:13.930 align:start position:0% so if I would get this in full I will 00:40:13.930 --> 00:40:15.810 align:start position:0% so if I would get this in full I will interpolate<00:40:14.350> this<00:40:14.680> and<00:40:14.920> see<00:40:15.160> well<00:40:15.430> this<00:40:15.640> is 00:40:15.810 --> 00:40:15.820 align:start position:0% interpolate this and see well this is 00:40:15.820 --> 00:40:17.760 align:start position:0% interpolate this and see well this is indeed<00:40:16.000> a<00:40:16.150> bulletin<00:40:16.570> which<00:40:16.780> we<00:40:17.020> 0<00:40:17.260> just 00:40:17.760 --> 00:40:17.770 align:start position:0% indeed a bulletin which we 0 just 00:40:17.770 --> 00:40:20.160 align:start position:0% indeed a bulletin which we 0 just because<00:40:17.980> it<00:40:18.130> for<00:40:19.090> is<00:40:19.150> this<00:40:19.270> one<00:40:19.510> I<00:40:19.750> would<00:40:20.050> do 00:40:20.160 --> 00:40:20.170 align:start position:0% because it for is this one I would do 00:40:20.170 --> 00:40:22.290 align:start position:0% because it for is this one I would do the<00:40:20.320> same<00:40:20.440> work<00:40:20.680> and<00:40:20.920> I<00:40:21.010> will<00:40:21.160> get<00:40:21.310> degree 00:40:22.290 --> 00:40:22.300 align:start position:0% the same work and I will get degree 00:40:22.300 --> 00:40:25.590 align:start position:0% the same work and I will get degree which<00:40:22.480> is<00:40:22.630> more<00:40:23.140> of<00:40:23.290> the<00:40:23.440> cereal<00:40:24.030> but<00:40:25.030> I<00:40:25.150> can<00:40:25.540> I 00:40:25.590 --> 00:40:25.600 align:start position:0% which is more of the cereal but I can I 00:40:25.600 --> 00:40:28.470 align:start position:0% which is more of the cereal but I can I have<00:40:25.840> an<00:40:25.930> excess<00:40:26.170> terrorism<00:40:26.590> -<00:40:27.160> I<00:40:27.520> can<00:40:28.240> cook 00:40:28.470 --> 00:40:28.480 align:start position:0% have an excess terrorism - I can cook 00:40:28.480 --> 00:40:30.840 align:start position:0% have an excess terrorism - I can cook together<00:40:28.750> sweet<00:40:29.200> answer<00:40:29.560> so<00:40:29.980> I<00:40:30.010> can<00:40:30.340> only<00:40:30.580> get 00:40:30.840 --> 00:40:30.850 align:start position:0% together sweet answer so I can only get 00:40:30.850 --> 00:40:33.150 align:start position:0% together sweet answer so I can only get an<00:40:31.120> answer<00:40:31.840> with<00:40:31.990> some<00:40:32.170> probability<00:40:32.440> which<00:40:33.130> is 00:40:33.150 --> 00:40:33.160 align:start position:0% an answer with some probability which is 00:40:33.160 --> 00:40:35.970 align:start position:0% an answer with some probability which is sums<00:40:33.550> and<00:40:33.880> for<00:40:34.390> a<00:40:34.420> delta<00:40:34.750> parameter<00:40:35.260> the<00:40:35.800> other 00:40:35.970 --> 00:40:35.980 align:start position:0% sums and for a delta parameter the other 00:40:35.980 --> 00:40:37.980 align:start position:0% sums and for a delta parameter the other parameters<00:40:36.400> will<00:40:36.670> the<00:40:37.060> Delta<00:40:37.450> pressure<00:40:37.600> will 00:40:37.980 --> 00:40:37.990 align:start position:0% parameters will the Delta pressure will 00:40:37.990 --> 00:40:40.470 align:start position:0% parameters will the Delta pressure will tell<00:40:38.200> me<00:40:38.380> how<00:40:38.860> many<00:40:38.920> points<00:40:39.520> I<00:40:39.730> want<00:40:40.270> to<00:40:40.330> be 00:40:40.470 --> 00:40:40.480 align:start position:0% tell me how many points I want to be 00:40:40.480 --> 00:40:42.410 align:start position:0% tell me how many points I want to be sure<00:40:40.660> that<00:40:40.870> this<00:40:41.020> polynomial<00:40:41.290> doesn't 00:40:42.410 --> 00:40:42.420 align:start position:0% sure that this polynomial doesn't 00:40:42.420 --> 00:40:45.990 align:start position:0% sure that this polynomial doesn't deviate<00:40:43.420> from<00:40:43.870> sample<00:40:44.770> not<00:40:45.280> just<00:40:45.550> from<00:40:45.640> exact 00:40:45.990 --> 00:40:46.000 align:start position:0% deviate from sample not just from exact 00:40:46.000 --> 00:40:51.240 align:start position:0% deviate from sample not just from exact one<00:40:46.210> but<00:40:46.390> from<00:40:46.840> sample<00:40:47.230> interval<00:40:47.530> t0<00:40:50.250> other 00:40:51.240 --> 00:40:51.250 align:start position:0% one but from sample interval t0 other 00:40:51.250 --> 00:40:53.330 align:start position:0% one but from sample interval t0 other others<00:40:51.850> the<00:40:52.000> same<00:40:52.180> work<00:40:52.390> also<00:40:52.540> exists<00:40:52.960> to 00:40:53.330 --> 00:40:53.340 align:start position:0% others the same work also exists to 00:40:53.340 --> 00:40:56.520 align:start position:0% others the same work also exists to emulations<00:40:54.340> or<00:40:54.700> to<00:40:55.030> Oracle<00:40:55.390> safety<00:40:55.750> v8<00:40:56.050> in<00:40:56.320> one 00:40:56.520 --> 00:40:56.530 align:start position:0% emulations or to Oracle safety v8 in one 00:40:56.530 --> 00:41:00.330 align:start position:0% emulations or to Oracle safety v8 in one hand<00:40:56.800> so<00:40:57.580> in<00:40:57.730> this<00:40:57.850> case<00:40:58.090> my<00:40:58.360> Delta<00:40:58.930> u1<00:40:59.500> or<00:41:00.010> so 00:41:00.330 --> 00:41:00.340 align:start position:0% hand so in this case my Delta u1 or so 00:41:00.340 --> 00:41:02.100 align:start position:0% hand so in this case my Delta u1 or so let's<00:41:00.550> say<00:41:00.700> I<00:41:00.970> want<00:41:01.390> to<00:41:01.450> distinguish<00:41:01.840> between 00:41:02.100 --> 00:41:02.110 align:start position:0% let's say I want to distinguish between 00:41:02.110 --> 00:41:04.260 align:start position:0% let's say I want to distinguish between two<00:41:02.350> cases<00:41:02.800> where<00:41:03.460> it's<00:41:03.610> exactly<00:41:04.120> is<00:41:04.180> a 00:41:04.260 --> 00:41:04.270 align:start position:0% two cases where it's exactly is a 00:41:04.270 --> 00:41:06.780 align:start position:0% two cases where it's exactly is a polynomial<00:41:05.260> certain<00:41:05.800> degree<00:41:06.100> after<00:41:06.580> certain 00:41:06.780 --> 00:41:06.790 align:start position:0% polynomial certain degree after certain 00:41:06.790 --> 00:41:11.100 align:start position:0% polynomial certain degree after certain degree<00:41:07.180> or<00:41:07.780> when<00:41:08.350> is<00:41:08.500> one<00:41:09.190> course<00:41:09.610> closed<00:41:10.570> so 00:41:11.100 --> 00:41:11.110 align:start position:0% degree or when is one course closed so 00:41:11.110 --> 00:41:12.510 align:start position:0% degree or when is one course closed so it<00:41:11.200> seemed<00:41:11.410> only<00:41:11.560> different<00:41:12.010> than<00:41:12.100> one<00:41:12.280> point 00:41:12.510 --> 00:41:12.520 align:start position:0% it seemed only different than one point 00:41:12.520 --> 00:41:15.240 align:start position:0% it seemed only different than one point and<00:41:12.730> why<00:41:12.850> is<00:41:12.910> this<00:41:13.120> case<00:41:13.630> but<00:41:14.350> those<00:41:14.500> first<00:41:14.710> so 00:41:15.240 --> 00:41:15.250 align:start position:0% and why is this case but those first so 00:41:15.250 --> 00:41:18.980 align:start position:0% and why is this case but those first so not<00:41:15.430> into<00:41:15.850> points<00:41:16.210> I<00:41:16.390> am<00:41:16.870> okay<00:41:17.140> was<00:41:17.320> one<00:41:17.500> and 00:41:18.980 --> 00:41:18.990 align:start position:0% not into points I am okay was one and 00:41:18.990 --> 00:41:21.480 align:start position:0% not into points I am okay was one and for<00:41:19.990> this<00:41:20.170> so<00:41:20.410> I<00:41:20.440> fixed<00:41:20.770> my<00:41:20.830> promise<00:41:21.190> of<00:41:21.340> the 00:41:21.480 --> 00:41:21.490 align:start position:0% for this so I fixed my promise of the 00:41:21.490 --> 00:41:23.550 align:start position:0% for this so I fixed my promise of the Delta<00:41:22.030> which<00:41:22.360> will<00:41:22.540> tell<00:41:22.750> me<00:41:22.900> how<00:41:23.080> many<00:41:23.140> steps 00:41:23.550 --> 00:41:23.560 align:start position:0% Delta which will tell me how many steps 00:41:23.560 --> 00:41:25.890 align:start position:0% Delta which will tell me how many steps of<00:41:23.710> practically<00:41:24.400> I<00:41:24.430> have<00:41:24.670> to<00:41:24.820> run<00:41:25.000> which<00:41:25.570> ends 00:41:25.890 --> 00:41:25.900 align:start position:0% of practically I have to run which ends 00:41:25.900 --> 00:41:27.030 align:start position:0% of practically I have to run which ends end<00:41:26.050> of<00:41:26.170> the<00:41:26.290> different<00:41:26.620> practical 00:41:27.030 --> 00:41:27.040 align:start position:0% end of the different practical 00:41:27.040 --> 00:41:28.650 align:start position:0% end of the different practical perspective<00:41:27.280> will<00:41:27.700> tell<00:41:27.910> you<00:41:28.030> what<00:41:28.480> is<00:41:28.630> the 00:41:28.650 --> 00:41:28.660 align:start position:0% perspective will tell you what is the 00:41:28.660 --> 00:41:33.150 align:start position:0% perspective will tell you what is the process<00:41:29.110> and<00:41:29.520> then<00:41:30.520> his<00:41:30.640> name<00:41:31.650> but<00:41:32.650> let's<00:41:32.950> say 00:41:33.150 --> 00:41:33.160 align:start position:0% process and then his name but let's say 00:41:33.160 --> 00:41:34.290 align:start position:0% process and then his name but let's say I<00:41:33.190> want<00:41:33.400> to<00:41:33.430> be<00:41:33.580> lessons 00:41:34.290 --> 00:41:34.300 align:start position:0% I want to be lessons 00:41:34.300 --> 00:41:38.070 align:start position:0% I want to be lessons sir<00:41:35.020> McKay<00:41:35.350> was<00:41:35.530> knell<00:41:35.740> to<00:41:35.770> be<00:41:36.040> one<00:41:36.700> cop<00:41:37.420> so<00:41:38.020> I 00:41:38.070 --> 00:41:38.080 align:start position:0% sir McKay was knell to be one cop so I 00:41:38.080 --> 00:41:41.790 align:start position:0% sir McKay was knell to be one cop so I will<00:41:38.560> allows<00:41:39.010> someone<00:41:39.820> to<00:41:40.140> keep<00:41:41.140> evolving<00:41:41.380> is 00:41:41.790 --> 00:41:41.800 align:start position:0% will allows someone to keep evolving is 00:41:41.800 --> 00:41:45.180 align:start position:0% will allows someone to keep evolving is not<00:41:41.980> exactly<00:41:42.430> from<00:41:42.760> the<00:41:42.970> polynomial<00:41:43.690> but<00:41:44.410> from 00:41:45.180 --> 00:41:45.190 align:start position:0% not exactly from the polynomial but from 00:41:45.190 --> 00:41:47.760 align:start position:0% not exactly from the polynomial but from some<00:41:45.430> function<00:41:45.880> we<00:41:46.000> made<00:41:46.270> in<00:41:46.660> two<00:41:47.350> cells<00:41:47.650> here 00:41:47.760 --> 00:41:47.770 align:start position:0% some function we made in two cells here 00:41:47.770 --> 00:41:50.520 align:start position:0% some function we made in two cells here that<00:41:48.520> my<00:41:48.700> delta<00:41:49.090> is<00:41:49.150> larger<00:41:49.570> and<00:41:49.780> the<00:41:50.110> property 00:41:50.520 --> 00:41:50.530 align:start position:0% that my delta is larger and the property 00:41:50.530 --> 00:41:51.380 align:start position:0% that my delta is larger and the property of<00:41:50.620> the<00:41:50.740> primarily 00:41:51.380 --> 00:41:51.390 align:start position:0% of the primarily 00:41:51.390 --> 00:41:53.630 align:start position:0% of the primarily as<00:41:51.480> to<00:41:52.200> certain<00:41:52.380> conditions<00:41:53.010> which<00:41:53.160> we<00:41:53.370> won't 00:41:53.630 --> 00:41:53.640 align:start position:0% as to certain conditions which we won't 00:41:53.640 --> 00:41:56.540 align:start position:0% as to certain conditions which we won't hear<00:41:54.150> it<00:41:55.110> out<00:41:55.500> we'll<00:41:55.770> give<00:41:55.920> you<00:41:56.040> a<00:41:56.070> larger 00:41:56.540 --> 00:41:56.550 align:start position:0% hear it out we'll give you a larger 00:41:56.550 --> 00:41:59.330 align:start position:0% hear it out we'll give you a larger sound<00:41:56.850> so<00:41:57.480> you<00:41:57.540> prove<00:41:57.840> size<00:41:58.140> will<00:41:58.680> potentially 00:41:59.330 --> 00:41:59.340 align:start position:0% sound so you prove size will potentially 00:41:59.340 --> 00:42:02.900 align:start position:0% sound so you prove size will potentially be<00:41:59.520> smaller<00:41:59.820> for<00:42:00.380> and<00:42:01.380> if<00:42:01.560> you<00:42:01.680> want<00:42:01.890> to<00:42:01.980> be<00:42:02.160> if 00:42:02.900 --> 00:42:02.910 align:start position:0% be smaller for and if you want to be if 00:42:02.910 --> 00:42:04.340 align:start position:0% be smaller for and if you want to be if I<00:42:03.060> want<00:42:03.240> to<00:42:03.330> be<00:42:03.420> sure<00:42:03.450> is<00:42:03.750> that<00:42:03.840> this<00:42:03.990> is<00:42:04.170> only 00:42:04.340 --> 00:42:04.350 align:start position:0% I want to be sure is that this is only 00:42:04.350 --> 00:42:06.410 align:start position:0% I want to be sure is that this is only different<00:42:04.740> in<00:42:04.920> one<00:42:05.160> cell<00:42:05.460> with<00:42:06.060> slit<00:42:06.270> a 00:42:06.410 --> 00:42:06.420 align:start position:0% different in one cell with slit a 00:42:06.420 --> 00:42:07.640 align:start position:0% different in one cell with slit a country<00:42:06.810> bits<00:42:06.960> of<00:42:07.080> security 00:42:07.640 --> 00:42:07.650 align:start position:0% country bits of security 00:42:07.650 --> 00:42:09.110 align:start position:0% country bits of security my<00:42:07.800> firm<00:42:07.980> is<00:42:08.010> going<00:42:08.250> to<00:42:08.370> be<00:42:08.520> like<00:42:08.700> here<00:42:08.880> that 00:42:09.110 --> 00:42:09.120 align:start position:0% my firm is going to be like here that 00:42:09.120 --> 00:42:11.030 align:start position:0% my firm is going to be like here that meeting<00:42:09.780> gauge<00:42:09.960> if<00:42:10.140> I<00:42:10.230> want<00:42:10.440> to<00:42:10.530> be<00:42:10.650> sure<00:42:10.680> that 00:42:11.030 --> 00:42:11.040 align:start position:0% meeting gauge if I want to be sure that 00:42:11.040 --> 00:42:12.050 align:start position:0% meeting gauge if I want to be sure that it's<00:42:11.340> different 00:42:12.050 --> 00:42:12.060 align:start position:0% it's different 00:42:12.060 --> 00:42:15.500 align:start position:0% it's different Dante<00:42:12.960> mama<00:42:13.170> at<00:42:13.680> maximum<00:42:14.250> took<00:42:14.400> two<00:42:14.940> cells<00:42:15.240> was 00:42:15.500 --> 00:42:15.510 align:start position:0% Dante mama at maximum took two cells was 00:42:15.510 --> 00:42:16.250 align:start position:0% Dante mama at maximum took two cells was the<00:42:15.630> same<00:42:15.810> everything 00:42:16.250 --> 00:42:16.260 align:start position:0% the same everything 00:42:16.260 --> 00:42:18.830 align:start position:0% the same everything it's<00:42:16.500> a<00:42:16.620> security<00:42:17.480> instead<00:42:18.480> of<00:42:18.600> Delta 00:42:18.830 --> 00:42:18.840 align:start position:0% it's a security instead of Delta 00:42:18.840 --> 00:42:21.170 align:start position:0% it's a security instead of Delta parameter<00:42:19.320> supportive<00:42:19.860> will<00:42:20.100> show<00:42:20.430> why<00:42:20.940> it's 00:42:21.170 --> 00:42:21.180 align:start position:0% parameter supportive will show why it's 00:42:21.180 --> 00:42:24.530 align:start position:0% parameter supportive will show why it's important<00:42:21.600> to<00:42:22.170> letter<00:42:22.470> steps<00:42:22.880> but<00:42:23.880> all<00:42:24.300> the 00:42:24.530 --> 00:42:24.540 align:start position:0% important to letter steps but all the 00:42:24.540 --> 00:42:28.130 align:start position:0% important to letter steps but all the improvements<00:42:24.720> of<00:42:25.050> relative<00:42:25.380> a<00:42:25.530> vertical<00:42:27.140> at 00:42:28.130 --> 00:42:28.140 align:start position:0% improvements of relative a vertical at 00:42:28.140 --> 00:42:30.650 align:start position:0% improvements of relative a vertical at least<00:42:28.350> for<00:42:28.470> now<00:42:28.500> the<00:42:29.490> order<00:42:29.730> to<00:42:29.910> improves<00:42:30.480> the 00:42:30.650 --> 00:42:30.660 align:start position:0% least for now the order to improves the 00:42:30.660 --> 00:42:33.440 align:start position:0% least for now the order to improves the sound<00:42:30.840> so<00:42:31.200> we<00:42:31.230> improve<00:42:31.770> the<00:42:31.950> second<00:42:32.340> term<00:42:32.520> in 00:42:33.440 --> 00:42:33.450 align:start position:0% sound so we improve the second term in 00:42:33.450 --> 00:42:37.190 align:start position:0% sound so we improve the second term in this<00:42:33.780> minimum<00:42:34.170> function<00:42:34.560> and<00:42:34.910> LC<00:42:35.910> say<00:42:36.900> what 00:42:37.190 --> 00:42:37.200 align:start position:0% this minimum function and LC say what 00:42:37.200 --> 00:42:39.770 align:start position:0% this minimum function and LC say what it's<00:42:37.380> like<00:42:37.590> what<00:42:37.980> is<00:42:38.100> your<00:42:38.250> delta<00:42:38.670> up<00:42:39.210> to<00:42:39.540> which 00:42:39.770 --> 00:42:39.780 align:start position:0% it's like what is your delta up to which 00:42:39.780 --> 00:42:42.350 align:start position:0% it's like what is your delta up to which you<00:42:39.960> can<00:42:40.140> even<00:42:40.320> use<00:42:40.530> a<00:42:40.560> prayer<00:42:40.910> but<00:42:41.910> we<00:42:42.180> will 00:42:42.350 --> 00:42:42.360 align:start position:0% you can even use a prayer but we will 00:42:42.360 --> 00:42:44.320 align:start position:0% you can even use a prayer but we will not<00:42:42.510> touch<00:42:42.900> this<00:42:43.140> is<00:42:43.320> too<00:42:43.500> much<00:42:43.650> Delta 00:42:44.320 --> 00:42:44.330 align:start position:0% not touch this is too much Delta 00:42:44.330 --> 00:42:47.300 align:start position:0% not touch this is too much Delta question<00:42:45.330> so<00:42:45.600> how<00:42:46.020> can<00:42:46.080> you<00:42:46.440> tell<00:42:46.800> me<00:42:46.950> how<00:42:47.250> you 00:42:47.300 --> 00:42:47.310 align:start position:0% question so how can you tell me how you 00:42:47.310 --> 00:42:49.790 align:start position:0% question so how can you tell me how you met<00:42:47.640> the<00:42:47.940> number<00:42:48.330> of<00:42:48.450> point<00:42:48.750> that<00:42:48.990> these<00:42:49.290> four 00:42:49.790 --> 00:42:49.800 align:start position:0% met the number of point that these four 00:42:49.800 --> 00:42:50.270 align:start position:0% met the number of point that these four intervals 00:42:50.270 --> 00:42:50.280 align:start position:0% intervals 00:42:50.280 --> 00:42:53.810 align:start position:0% intervals delayed<00:42:50.610> to<00:42:51.150> the<00:42:51.300> beat<00:42:51.510> of<00:42:51.540> security<00:42:52.290> oh<00:42:52.820> well 00:42:53.810 --> 00:42:53.820 align:start position:0% delayed to the beat of security oh well 00:42:53.820 --> 00:42:56.000 align:start position:0% delayed to the beat of security oh well I<00:42:53.850> mean<00:42:54.120> this<00:42:54.270> is<00:42:54.330> the<00:42:54.570> songs<00:42:54.930> error<00:42:55.350> it 00:42:56.000 --> 00:42:56.010 align:start position:0% I mean this is the songs error it 00:42:56.010 --> 00:42:57.560 align:start position:0% I mean this is the songs error it basically<00:42:56.460> tells<00:42:56.730> you<00:42:56.880> what<00:42:57.090> is<00:42:57.210> the<00:42:57.330> chance 00:42:57.560 --> 00:42:57.570 align:start position:0% basically tells you what is the chance 00:42:57.570 --> 00:43:00.940 align:start position:0% basically tells you what is the chance that<00:42:57.630> you<00:42:57.810> were<00:42:57.930> cheated<00:42:58.400> if<00:42:59.400> you<00:42:59.520> want<00:42:59.730> to 00:43:00.940 --> 00:43:00.950 align:start position:0% that you were cheated if you want to 00:43:00.950 --> 00:43:05.240 align:start position:0% that you were cheated if you want to explain<00:43:02.690> to<00:43:03.690> claim<00:43:03.990> all<00:43:04.470> the<00:43:04.530> parameters<00:43:05.010> here 00:43:05.240 --> 00:43:05.250 align:start position:0% explain to claim all the parameters here 00:43:05.250 --> 00:43:08.690 align:start position:0% explain to claim all the parameters here that<00:43:05.820> they're<00:43:06.590> all<00:43:07.590> the<00:43:07.710> deep<00:43:07.920> is<00:43:08.070> important 00:43:08.690 --> 00:43:08.700 align:start position:0% that they're all the deep is important 00:43:08.700 --> 00:43:11.900 align:start position:0% that they're all the deep is important and<00:43:08.940> they<00:43:09.270> think<00:43:09.600> that<00:43:09.710> on<00:43:10.710> the<00:43:10.890> camera<00:43:11.100> is<00:43:11.520> the 00:43:11.900 --> 00:43:11.910 align:start position:0% and they think that on the camera is the 00:43:11.910 --> 00:43:24.790 align:start position:0% and they think that on the camera is the Delta<00:43:12.300> we<00:43:13.050> decide<00:43:13.410> we<00:43:13.740> decide<00:43:14.100> how<00:43:15.090> much 00:43:24.790 --> 00:43:24.800 align:start position:0% 00:43:24.800 --> 00:43:27.470 align:start position:0% according<00:43:25.800> to<00:43:25.830> this<00:43:25.980> prior<00:43:26.250> to<00:43:26.400> Delta<00:43:26.880> Alex 00:43:27.470 --> 00:43:27.480 align:start position:0% according to this prior to Delta Alex 00:43:27.480 --> 00:43:35.030 align:start position:0% according to this prior to Delta Alex told<00:43:28.940> it<00:43:29.940> means<00:43:30.860> how<00:43:31.860> how<00:43:32.790> much<00:43:33.740> year<00:43:34.740> are<00:43:34.890> we 00:43:35.030 --> 00:43:35.040 align:start position:0% told it means how how much year are we 00:43:35.040 --> 00:43:38.470 align:start position:0% told it means how how much year are we can<00:43:35.370> take<00:43:35.580> so<00:43:36.000> this<00:43:36.150> is<00:43:36.300> face<00:43:36.510> of<00:43:36.750> Islamic<00:43:37.200> odds 00:43:38.470 --> 00:43:38.480 align:start position:0% can take so this is face of Islamic odds 00:43:38.480 --> 00:43:42.560 align:start position:0% can take so this is face of Islamic odds and<00:43:39.480> this<00:43:39.630> is<00:43:39.780> just<00:43:40.730> the<00:43:41.730> job<00:43:41.940> to<00:43:42.090> boom<00:43:42.270> in<00:43:42.420> this 00:43:42.560 --> 00:43:42.570 align:start position:0% and this is just the job to boom in this 00:43:42.570 --> 00:43:48.470 align:start position:0% and this is just the job to boom in this base<00:43:43.220> does<00:43:44.220> the<00:43:44.550> circle<00:43:45.510> of<00:43:45.600> radius<00:43:45.720> Delta<00:43:47.480> and 00:43:48.470 --> 00:43:48.480 align:start position:0% base does the circle of radius Delta and 00:43:48.480 --> 00:43:50.570 align:start position:0% base does the circle of radius Delta and this<00:43:48.630> is<00:43:48.780> a<00:43:48.810> function<00:43:49.290> which<00:43:49.800> is<00:43:49.980> just<00:43:50.010> in 00:43:50.570 --> 00:43:50.580 align:start position:0% this is a function which is just in 00:43:50.580 --> 00:43:53.930 align:start position:0% this is a function which is just in those<00:43:51.030> Delta<00:43:51.960> blowing<00:43:52.550> for<00:43:53.550> this<00:43:53.670> function 00:43:53.930 --> 00:43:53.940 align:start position:0% those Delta blowing for this function 00:43:53.940 --> 00:43:58.610 align:start position:0% those Delta blowing for this function with<00:43:54.480> parameter<00:43:55.380> Delta<00:43:55.850> who<00:43:56.850> was<00:43:57.750> right<00:43:58.110> of 00:43:58.610 --> 00:43:58.620 align:start position:0% with parameter Delta who was right of 00:43:58.620 --> 00:44:02.210 align:start position:0% with parameter Delta who was right of course<00:43:58.680> doesn't<00:43:59.370> mean<00:43:59.580> that<00:44:00.860> this<00:44:01.860> function 00:44:02.210 --> 00:44:02.220 align:start position:0% course doesn't mean that this function 00:44:02.220 --> 00:44:06.020 align:start position:0% course doesn't mean that this function toggle<00:44:02.580> I<00:44:03.030> want<00:44:03.810> to<00:44:04.140> stress<00:44:04.350> not<00:44:04.560> yes<00:44:04.830> why<00:44:05.520> not 00:44:06.020 --> 00:44:06.030 align:start position:0% toggle I want to stress not yes why not 00:44:06.030 --> 00:44:10.460 align:start position:0% toggle I want to stress not yes why not why<00:44:06.480> this<00:44:07.140> is<00:44:07.560> not<00:44:07.860> important<00:44:08.580> for<00:44:09.470> forced 00:44:10.460 --> 00:44:10.470 align:start position:0% why this is not important for forced 00:44:10.470 --> 00:44:15.140 align:start position:0% why this is not important for forced jobs<00:44:11.900> as<00:44:12.900> I<00:44:13.050> have<00:44:13.200> said<00:44:13.470> we<00:44:13.710> sure<00:44:14.100> that<00:44:14.150> some 00:44:15.140 --> 00:44:15.150 align:start position:0% jobs as I have said we sure that some 00:44:15.150 --> 00:44:17.030 align:start position:0% jobs as I have said we sure that some functions<00:44:15.660> of<00:44:15.810> we<00:44:15.930> this<00:44:16.050> function<00:44:16.500> is<00:44:16.980> a 00:44:17.030 --> 00:44:17.040 align:start position:0% functions of we this function is a 00:44:17.040 --> 00:44:25.250 align:start position:0% functions of we this function is a corner<00:44:17.460> but<00:44:18.240> if<00:44:20.870> normal<00:44:21.870> notice<00:44:23.840> the<00:44:24.840> prover 00:44:25.250 --> 00:44:25.260 align:start position:0% corner but if normal notice the prover 00:44:25.260 --> 00:44:29.890 align:start position:0% corner but if normal notice the prover is<00:44:25.500> able<00:44:25.980> to<00:44:26.190> honest<00:44:26.610> to<00:44:27.330> pass<00:44:27.510> fry<00:44:27.840> them<00:44:28.740> just 00:44:29.890 --> 00:44:29.900 align:start position:0% is able to honest to pass fry them just 00:44:29.900 --> 00:44:32.660 align:start position:0% is able to honest to pass fry them just this<00:44:30.900> means<00:44:31.140> that<00:44:31.320> he<00:44:31.470> knows<00:44:31.620> some<00:44:32.130> function 00:44:32.660 --> 00:44:32.670 align:start position:0% this means that he knows some function 00:44:32.670 --> 00:44:34.970 align:start position:0% this means that he knows some function which<00:44:32.850> is<00:44:33.000> in<00:44:33.390> this<00:44:33.630> Delta<00:44:34.230> reduce<00:44:34.560> by<00:44:34.920> this 00:44:34.970 --> 00:44:34.980 align:start position:0% which is in this Delta reduce by this 00:44:34.980 --> 00:44:38.450 align:start position:0% which is in this Delta reduce by this multiple<00:44:35.580> normal<00:44:35.940> and<00:44:36.210> the<00:44:37.080> only<00:44:37.460> honest 00:44:38.450 --> 00:44:38.460 align:start position:0% multiple normal and the only honest 00:44:38.460 --> 00:44:41.330 align:start position:0% multiple normal and the only honest witness<00:44:39.090> for<00:44:39.570> drugs<00:44:40.170> is<00:44:40.380> a<00:44:40.470> phone<00:44:40.620> number<00:44:40.650> but 00:44:41.330 --> 00:44:41.340 align:start position:0% witness for drugs is a phone number but 00:44:41.340 --> 00:44:45.860 align:start position:0% witness for drugs is a phone number but that<00:44:41.400> may<00:44:41.730> have<00:44:43.670> decoding<00:44:44.720> algorithms<00:44:45.720> such 00:44:45.860 --> 00:44:45.870 align:start position:0% that may have decoding algorithms such 00:44:45.870 --> 00:44:49.760 align:start position:0% that may have decoding algorithms such as<00:44:45.900> sujin<00:44:46.770> decoding<00:44:47.430> algorithm<00:44:47.880> or<00:44:48.650> bullsh 00:44:49.760 --> 00:44:49.770 align:start position:0% as sujin decoding algorithm or bullsh 00:44:49.770 --> 00:44:52.430 align:start position:0% as sujin decoding algorithm or bullsh velcome<00:44:50.640> algorithm<00:44:51.300> algorithm<00:44:51.810> we<00:44:52.200> just 00:44:52.430 --> 00:44:52.440 align:start position:0% velcome algorithm algorithm we just 00:44:52.440 --> 00:44:55.550 align:start position:0% velcome algorithm algorithm we just gives<00:44:52.830> us<00:44:53.010> the<00:44:53.250> proof<00:44:53.880> of<00:44:54.000> knowledge<00:44:54.560> there 00:44:55.550 --> 00:44:55.560 align:start position:0% gives us the proof of knowledge there 00:44:55.560 --> 00:45:01.190 align:start position:0% gives us the proof of knowledge there just<00:44:56.210> addition<00:44:57.210> to<00:44:57.420> normal<00:44:57.600> and<00:44:59.900> for<00:45:00.900> the<00:45:01.050> main 00:45:01.190 --> 00:45:01.200 align:start position:0% just addition to normal and for the main 00:45:01.200 --> 00:45:04.040 align:start position:0% just addition to normal and for the main say<00:45:01.640> if<00:45:02.640> just<00:45:02.970> prove<00:45:03.210> hakuna<00:45:03.600> was<00:45:03.750> not<00:45:03.900> only 00:45:04.040 --> 00:45:04.050 align:start position:0% say if just prove hakuna was not only 00:45:04.050 --> 00:45:08.810 align:start position:0% say if just prove hakuna was not only local<00:45:04.470> but<00:45:05.780> the<00:45:06.780> function<00:45:07.080> itself<00:45:07.580> if<00:45:08.580> he<00:45:08.760> is 00:45:08.810 --> 00:45:08.820 align:start position:0% local but the function itself if he is 00:45:08.820 --> 00:45:10.990 align:start position:0% local but the function itself if he is able<00:45:08.940> to<00:45:09.150> provide<00:45:09.450> any<00:45:10.020> part<00:45:10.410> which<00:45:10.620> is<00:45:10.740> closed 00:45:10.990 --> 00:45:11.000 align:start position:0% able to provide any part which is closed 00:45:11.000 --> 00:45:15.440 align:start position:0% able to provide any part which is closed then<00:45:12.000> you<00:45:12.660> just<00:45:12.960> use<00:45:13.340> those<00:45:14.450> algorithm 00:45:15.440 --> 00:45:15.450 align:start position:0% then you just use those algorithm 00:45:15.450 --> 00:45:21.200 align:start position:0% then you just use those algorithm decoding<00:45:15.900> and<00:45:16.080> you<00:45:16.680> need<00:45:19.160> therapists<00:45:20.210> people 00:45:21.200 --> 00:45:21.210 align:start position:0% decoding and you need therapists people 00:45:21.210 --> 00:45:23.350 align:start position:0% decoding and you need therapists people number<00:45:21.600> which<00:45:21.840> will<00:45:21.990> satisfy<00:45:22.200> the<00:45:22.560> condition 00:45:23.350 --> 00:45:23.360 align:start position:0% number which will satisfy the condition 00:45:23.360 --> 00:45:27.790 align:start position:0% number which will satisfy the condition but<00:45:23.540> yeah<00:45:24.610> this<00:45:25.610> is<00:45:26.420> the<00:45:26.540> true<00:45:26.780> Yahoo<00:45:27.110> actually 00:45:27.790 --> 00:45:27.800 align:start position:0% but yeah this is the true Yahoo actually 00:45:27.800 --> 00:45:30.250 align:start position:0% but yeah this is the true Yahoo actually says<00:45:28.040> this<00:45:28.190> is<00:45:28.370> a<00:45:28.400> at<00:45:29.330> least<00:45:29.720> D<00:45:29.900> for<00:45:30.110> life 00:45:30.250 --> 00:45:30.260 align:start position:0% says this is a at least D for life 00:45:30.260 --> 00:45:33.280 align:start position:0% says this is a at least D for life practical<00:45:30.830> so<00:45:31.430> yeah<00:45:32.090> here<00:45:32.450> everything<00:45:33.140> will 00:45:33.280 --> 00:45:33.290 align:start position:0% practical so yeah here everything will 00:45:33.290 --> 00:45:35.200 align:start position:0% practical so yeah here everything will take<00:45:33.470> you<00:45:33.560> before<00:45:33.920> was<00:45:34.310> about<00:45:34.340> employer<00:45:35.060> girls 00:45:35.200 --> 00:45:35.210 align:start position:0% take you before was about employer girls 00:45:35.210 --> 00:45:37.360 align:start position:0% take you before was about employer girls I<00:45:35.420> mean<00:45:35.810> we<00:45:35.960> assumes<00:45:36.290> and<00:45:36.530> approvals<00:45:37.040> honest 00:45:37.360 --> 00:45:37.370 align:start position:0% I mean we assumes and approvals honest 00:45:37.370 --> 00:45:39.430 align:start position:0% I mean we assumes and approvals honest we<00:45:38.030> just<00:45:38.060> need<00:45:38.480> coats<00:45:38.630> at<00:45:38.810> regional<00:45:39.110> problem 00:45:39.430 --> 00:45:39.440 align:start position:0% we just need coats at regional problem 00:45:39.440 --> 00:45:41.710 align:start position:0% we just need coats at regional problem the<00:45:39.860> essentially<00:45:40.220> this<00:45:40.430> is<00:45:40.970> a<00:45:41.000> purple<00:45:41.540> easy 00:45:41.710 --> 00:45:41.720 align:start position:0% the essentially this is a purple easy 00:45:41.720 --> 00:45:47.110 align:start position:0% the essentially this is a purple easy food<00:45:41.900> so<00:45:42.560> what<00:45:42.950> we<00:45:43.070> want<00:45:43.250> to<00:45:43.790> say<00:45:44.000> is<00:45:45.940> let's<00:45:46.940> say 00:45:47.110 --> 00:45:47.120 align:start position:0% food so what we want to say is let's say 00:45:47.120 --> 00:45:49.780 align:start position:0% food so what we want to say is let's say the<00:45:47.270> verifier<00:45:47.810> is<00:45:48.050> satisfied<00:45:48.620> with<00:45:49.370> follows 00:45:49.780 --> 00:45:49.790 align:start position:0% the verifier is satisfied with follows 00:45:49.790 --> 00:45:51.790 align:start position:0% the verifier is satisfied with follows the<00:45:49.880> conditions<00:45:50.330> and<00:45:50.540> like<00:45:51.140> all<00:45:51.410> the<00:45:51.590> checks 00:45:51.790 --> 00:45:51.800 align:start position:0% the conditions and like all the checks 00:45:51.800 --> 00:45:54.490 align:start position:0% the conditions and like all the checks will<00:45:51.950> put<00:45:52.220> here<00:45:52.490> it<00:45:53.300> means<00:45:53.540> that<00:45:53.780> certain 00:45:54.490 --> 00:45:54.500 align:start position:0% will put here it means that certain 00:45:54.500 --> 00:45:57.720 align:start position:0% will put here it means that certain values<00:45:55.250> from<00:45:55.760> the<00:45:55.910> Oracle<00:45:56.300> and<00:45:56.510> in<00:45:57.290> principle 00:45:57.720 --> 00:45:57.730 align:start position:0% values from the Oracle and in principle 00:45:57.730 --> 00:46:02.080 align:start position:0% values from the Oracle and in principle criminals<00:45:58.730> or<00:45:58.940> hopefully<00:46:00.130> many<00:46:01.130> resources<00:46:01.970> to 00:46:02.080 --> 00:46:02.090 align:start position:0% criminals or hopefully many resources to 00:46:02.090 --> 00:46:03.790 align:start position:0% criminals or hopefully many resources to pronounce<00:46:02.540> an<00:46:02.690> Oracle<00:46:03.020> hope<00:46:03.260> so<00:46:03.440> he<00:46:03.650> has 00:46:03.790 --> 00:46:03.800 align:start position:0% pronounce an Oracle hope so he has 00:46:03.800 --> 00:46:05.890 align:start position:0% pronounce an Oracle hope so he has access<00:46:04.010> to<00:46:04.160> all<00:46:04.280> the<00:46:04.430> valleys<00:46:04.880> locally<00:46:05.360> he<00:46:05.750> can 00:46:05.890 --> 00:46:05.900 align:start position:0% access to all the valleys locally he can 00:46:05.900 --> 00:46:07.600 align:start position:0% access to all the valleys locally he can do<00:46:06.020> whatever<00:46:06.260> he<00:46:06.380> wants<00:46:06.680> business<00:46:06.920> if<00:46:07.430> he 00:46:07.600 --> 00:46:07.610 align:start position:0% do whatever he wants business if he 00:46:07.610 --> 00:46:09.970 align:start position:0% do whatever he wants business if he satisfies<00:46:08.120> degree<00:46:08.360> mark<00:46:08.690> even<00:46:09.320> if<00:46:09.770> the 00:46:09.970 --> 00:46:09.980 align:start position:0% satisfies degree mark even if the 00:46:09.980 --> 00:46:12.610 align:start position:0% satisfies degree mark even if the vertical<00:46:10.490> was<00:46:10.850> not<00:46:11.090> executive<00:46:11.780> while<00:46:12.260> this<00:46:12.440> is 00:46:12.610 --> 00:46:12.620 align:start position:0% vertical was not executive while this is 00:46:12.620 --> 00:46:15.390 align:start position:0% vertical was not executive while this is a<00:46:12.650> polynomial<00:46:13.280> but<00:46:13.910> they<00:46:14.060> we<00:46:14.180> just<00:46:14.360> closed<00:46:14.570> and 00:46:15.390 --> 00:46:15.400 align:start position:0% a polynomial but they we just closed and 00:46:15.400 --> 00:46:18.550 align:start position:0% a polynomial but they we just closed and there<00:46:16.400> is<00:46:16.520> an<00:46:16.670> algorithm<00:46:16.970> for<00:46:17.420> the<00:46:18.200> proven 00:46:18.550 --> 00:46:18.560 align:start position:0% there is an algorithm for the proven 00:46:18.560 --> 00:46:22.120 align:start position:0% there is an algorithm for the proven himself<00:46:19.150> to<00:46:20.150> take<00:46:20.390> those<00:46:20.600> values<00:46:20.920> decode<00:46:21.920> a 00:46:22.120 --> 00:46:22.130 align:start position:0% himself to take those values decode a 00:46:22.130 --> 00:46:24.040 align:start position:0% himself to take those values decode a polynomial<00:46:22.910> from<00:46:23.060> them<00:46:23.330> and<00:46:23.540> this<00:46:23.810> polynomial 00:46:24.040 --> 00:46:24.050 align:start position:0% polynomial from them and this polynomial 00:46:24.050 --> 00:46:26.530 align:start position:0% polynomial from them and this polynomial will<00:46:24.500> be<00:46:24.650> the<00:46:24.710> true<00:46:25.010> business<00:46:25.160> so<00:46:26.120> the<00:46:26.300> bullet 00:46:26.530 --> 00:46:26.540 align:start position:0% will be the true business so the bullet 00:46:26.540 --> 00:46:30.820 align:start position:0% will be the true business so the bullet even<00:46:27.020> even<00:46:28.750> used<00:46:29.750> to<00:46:29.810> prevent<00:46:30.140> even<00:46:30.500> knows<00:46:30.800> a 00:46:30.820 --> 00:46:30.830 align:start position:0% even even used to prevent even knows a 00:46:30.830 --> 00:46:33.610 align:start position:0% even even used to prevent even knows a business<00:46:31.310> but<00:46:31.940> he<00:46:32.150> Possible's<00:46:32.930> checks<00:46:33.320> with 00:46:33.610 --> 00:46:33.620 align:start position:0% business but he Possible's checks with 00:46:33.620 --> 00:46:35.970 align:start position:0% business but he Possible's checks with also<00:46:33.920> enormous<00:46:34.820> number<00:46:35.180> of<00:46:35.270> bits<00:46:35.420> of<00:46:35.510> security 00:46:35.970 --> 00:46:35.980 align:start position:0% also enormous number of bits of security 00:46:35.980 --> 00:46:39.820 align:start position:0% also enormous number of bits of security he<00:46:36.980> in<00:46:37.190> principle<00:46:37.820> would<00:46:38.270> be<00:46:38.480> able<00:46:38.720> to<00:46:38.990> take 00:46:39.820 --> 00:46:39.830 align:start position:0% he in principle would be able to take 00:46:39.830 --> 00:46:41.530 align:start position:0% he in principle would be able to take all<00:46:40.100> those<00:46:40.220> values<00:46:40.490> and<00:46:40.910> finds<00:46:41.240> it<00:46:41.360> through 00:46:41.530 --> 00:46:41.540 align:start position:0% all those values and finds it through 00:46:41.540 --> 00:46:44.440 align:start position:0% all those values and finds it through weakness<00:46:41.750> easily<00:46:42.320> in<00:46:42.710> a<00:46:42.890> polynomial<00:46:43.160> time<00:46:43.640> so 00:46:44.440 --> 00:46:44.450 align:start position:0% weakness easily in a polynomial time so 00:46:44.450 --> 00:46:45.790 align:start position:0% weakness easily in a polynomial time so in<00:46:44.540> principle<00:46:44.750> this<00:46:45.260> is<00:46:45.410> a<00:46:45.440> proof<00:46:45.680> of 00:46:45.790 --> 00:46:45.800 align:start position:0% in principle this is a proof of 00:46:45.800 --> 00:46:48.760 align:start position:0% in principle this is a proof of knowledge<00:46:46.220> and<00:46:46.810> if<00:46:47.810> permit<00:46:48.260> has<00:46:48.440> satisfied 00:46:48.760 --> 00:46:48.770 align:start position:0% knowledge and if permit has satisfied 00:46:48.770 --> 00:46:51.940 align:start position:0% knowledge and if permit has satisfied the<00:46:49.400> rain<00:46:50.120> fire<00:46:50.360> then<00:46:50.960> he<00:46:51.320> can<00:46:51.500> get<00:46:51.740> the 00:46:51.940 --> 00:46:51.950 align:start position:0% the rain fire then he can get the 00:46:51.950 --> 00:46:53.560 align:start position:0% the rain fire then he can get the knowledge<00:46:52.280> of<00:46:52.430> Toledo's 00:46:53.560 --> 00:46:53.570 align:start position:0% knowledge of Toledo's 00:46:53.570 --> 00:46:57.029 align:start position:0% knowledge of Toledo's this<00:46:53.930> is<00:46:54.080> not<00:46:54.290> raining<00:46:54.860> tweeting 00:46:57.029 --> 00:46:57.039 align:start position:0% this is not raining tweeting 00:46:57.039 --> 00:47:00.940 align:start position:0% this is not raining tweeting to<00:46:58.039> speed<00:46:58.250> up<00:46:58.400> a<00:46:58.760> little<00:46:58.880> bit<00:46:59.710> so<00:47:00.710> there's 00:47:00.940 --> 00:47:00.950 align:start position:0% to speed up a little bit so there's 00:47:00.950 --> 00:47:05.579 align:start position:0% to speed up a little bit so there's limitations<00:47:02.440> but<00:47:03.440> quite<00:47:04.039> common<00:47:04.730> used<00:47:05.029> I 00:47:05.579 --> 00:47:05.589 align:start position:0% limitations but quite common used I 00:47:05.589 --> 00:47:08.529 align:start position:0% limitations but quite common used I think<00:47:06.589> it's<00:47:06.799> most<00:47:07.130> important<00:47:07.970> when<00:47:08.180> concise 00:47:08.529 --> 00:47:08.539 align:start position:0% think it's most important when concise 00:47:08.539 --> 00:47:11.339 align:start position:0% think it's most important when concise system<00:47:08.960> and<00:47:09.529> there<00:47:09.680> are<00:47:09.710> many<00:47:09.980> tools 00:47:11.339 --> 00:47:11.349 align:start position:0% system and there are many tools 00:47:11.349 --> 00:47:14.319 align:start position:0% system and there are many tools libraries<00:47:12.349> to<00:47:12.740> encode<00:47:13.039> programs<00:47:13.549> in<00:47:14.150> the 00:47:14.319 --> 00:47:14.329 align:start position:0% libraries to encode programs in the 00:47:14.329 --> 00:47:16.180 align:start position:0% libraries to encode programs in the Muslim<00:47:14.660> country<00:47:14.960> systems<00:47:15.410> and<00:47:15.740> there<00:47:16.010> are<00:47:16.099> not 00:47:16.180 --> 00:47:16.190 align:start position:0% Muslim country systems and there are not 00:47:16.190 --> 00:47:20.049 align:start position:0% Muslim country systems and there are not so<00:47:16.250> many<00:47:16.490> tools<00:47:16.819> record<00:47:17.510> in<00:47:18.079> stock<00:47:18.680> air<00:47:19.029> so<00:47:20.029> I 00:47:20.049 --> 00:47:20.059 align:start position:0% so many tools record in stock air so I 00:47:20.059 --> 00:47:23.529 align:start position:0% so many tools record in stock air so I think<00:47:20.180> this<00:47:20.480> just<00:47:20.779> penetration<00:47:22.240> as<00:47:23.240> I<00:47:23.390> have 00:47:23.529 --> 00:47:23.539 align:start position:0% think this just penetration as I have 00:47:23.539 --> 00:47:28.470 align:start position:0% think this just penetration as I have told<00:47:24.430> the<00:47:25.430> property<00:47:25.849> of<00:47:25.910> air<00:47:26.180> saw<00:47:26.510> that<00:47:26.750> John 00:47:28.470 --> 00:47:28.480 align:start position:0% told the property of air saw that John 00:47:28.480 --> 00:47:31.059 align:start position:0% told the property of air saw that John is<00:47:29.480> just<00:47:29.539> both<00:47:30.109> well<00:47:30.349> on<00:47:30.500> the<00:47:30.619> poor<00:47:30.859> which 00:47:31.059 --> 00:47:31.069 align:start position:0% is just both well on the poor which 00:47:31.069 --> 00:47:33.670 align:start position:0% is just both well on the poor which mathematicians<00:47:31.430> and<00:47:32.029> the<00:47:32.690> proof<00:47:32.930> sizes<00:47:33.440> large 00:47:33.670 --> 00:47:33.680 align:start position:0% mathematicians and the proof sizes large 00:47:33.680 --> 00:47:35.589 align:start position:0% mathematicians and the proof sizes large special<00:47:34.369> where<00:47:34.490> we<00:47:34.640> can<00:47:34.789> pay<00:47:35.000> each<00:47:35.359> term 00:47:35.589 --> 00:47:35.599 align:start position:0% special where we can pay each term 00:47:35.599 --> 00:47:38.260 align:start position:0% special where we can pay each term stocks<00:47:35.990> where<00:47:36.319> the<00:47:36.920> proof<00:47:37.160> is<00:47:37.400> of<00:47:37.849> constant 00:47:38.260 --> 00:47:38.270 align:start position:0% stocks where the proof is of constant 00:47:38.270 --> 00:47:43.359 align:start position:0% stocks where the proof is of constant size<00:47:38.740> but<00:47:40.690> the<00:47:41.690> final<00:47:42.319> part<00:47:42.529> of<00:47:42.680> juggs<00:47:43.010> is 00:47:43.359 --> 00:47:43.369 align:start position:0% size but the final part of juggs is 00:47:43.369 --> 00:47:47.260 align:start position:0% size but the final part of juggs is really<00:47:44.000> ingenious<00:47:45.099> and<00:47:46.099> maybe<00:47:46.579> we<00:47:46.849> can<00:47:47.000> apply 00:47:47.260 --> 00:47:47.270 align:start position:0% really ingenious and maybe we can apply 00:47:47.270 --> 00:47:56.260 align:start position:0% really ingenious and maybe we can apply some<00:47:47.630> other<00:47:47.829> primitives<00:47:48.910> as<00:47:49.910> mainly<00:47:54.910> what<00:47:55.910> try 00:47:56.260 --> 00:47:56.270 align:start position:0% some other primitives as mainly what try 00:47:56.270 --> 00:47:59.380 align:start position:0% some other primitives as mainly what try shows<00:47:57.170> us<00:47:57.470> that<00:47:57.799> some<00:47:58.069> function<00:47:58.549> is<00:47:59.329> a 00:47:59.380 --> 00:47:59.390 align:start position:0% shows us that some function is a 00:47:59.390 --> 00:48:04.299 align:start position:0% shows us that some function is a polynomial<00:47:59.660> may<00:48:00.319> be<00:48:01.119> able<00:48:02.119> to<00:48:02.329> apply<00:48:03.309> the 00:48:04.299 --> 00:48:04.309 align:start position:0% polynomial may be able to apply the 00:48:04.309 --> 00:48:06.450 align:start position:0% polynomial may be able to apply the strong<00:48:04.579> properties<00:48:04.970> of<00:48:05.089> right<00:48:05.329> or<00:48:05.869> other 00:48:06.450 --> 00:48:06.460 align:start position:0% strong properties of right or other 00:48:06.460 --> 00:48:11.410 align:start position:0% strong properties of right or other related<00:48:07.460> problems<00:48:07.940> and<00:48:09.730> we<00:48:10.730> try<00:48:10.940> to<00:48:10.970> do<00:48:11.180> this 00:48:11.410 --> 00:48:11.420 align:start position:0% related problems and we try to do this 00:48:11.420 --> 00:48:15.430 align:start position:0% related problems and we try to do this with<00:48:11.809> nominal<00:48:12.650> commitment<00:48:14.260> this<00:48:15.260> is<00:48:15.380> a 00:48:15.430 --> 00:48:15.440 align:start position:0% with nominal commitment this is a 00:48:15.440 --> 00:48:19.829 align:start position:0% with nominal commitment this is a definition<00:48:16.279> and<00:48:17.089> just<00:48:17.720> what<00:48:18.500> is<00:48:18.619> going<00:48:18.920> on 00:48:19.829 --> 00:48:19.839 align:start position:0% definition and just what is going on 00:48:19.839 --> 00:48:24.039 align:start position:0% definition and just what is going on Prabhu<00:48:20.839> has<00:48:21.380> phenomenal<00:48:22.329> but<00:48:23.329> he<00:48:23.539> wants<00:48:23.809> to 00:48:24.039 --> 00:48:24.049 align:start position:0% Prabhu has phenomenal but he wants to 00:48:24.049 --> 00:48:27.730 align:start position:0% Prabhu has phenomenal but he wants to know<00:48:24.740> -<00:48:25.460> over<00:48:26.000> this<00:48:26.119> point<00:48:26.329> of<00:48:26.630> us<00:48:26.750> he<00:48:27.710> just 00:48:27.730 --> 00:48:27.740 align:start position:0% know - over this point of us he just 00:48:27.740 --> 00:48:31.660 align:start position:0% know - over this point of us he just always<00:48:28.369> just<00:48:29.980> guesses<00:48:30.980> the<00:48:31.160> commitment<00:48:31.609> to 00:48:31.660 --> 00:48:31.670 align:start position:0% always just guesses the commitment to 00:48:31.670 --> 00:48:34.720 align:start position:0% always just guesses the commitment to the<00:48:31.760> small<00:48:31.970> number<00:48:32.270> so<00:48:32.299> we<00:48:32.839> as<00:48:33.319> verify<00:48:33.920> may<00:48:34.670> be 00:48:34.720 --> 00:48:34.730 align:start position:0% the small number so we as verify may be 00:48:34.730 --> 00:48:36.700 align:start position:0% the small number so we as verify may be sure<00:48:35.059> that<00:48:35.359> played<00:48:35.720> to<00:48:35.750> this<00:48:35.990> donor<00:48:36.319> won't<00:48:36.619> be 00:48:36.700 --> 00:48:36.710 align:start position:0% sure that played to this donor won't be 00:48:36.710 --> 00:48:40.470 align:start position:0% sure that played to this donor won't be changed<00:48:37.450> well<00:48:38.450> verify<00:48:39.039> silicon 00:48:40.470 --> 00:48:40.480 align:start position:0% changed well verify silicon 00:48:40.480 --> 00:48:43.260 align:start position:0% changed well verify silicon he<00:48:40.540> only<00:48:40.750> knows<00:48:41.020> that<00:48:41.290> the<00:48:41.859> brewer<00:48:42.099> has<00:48:42.910> sadly 00:48:43.260 --> 00:48:43.270 align:start position:0% he only knows that the brewer has sadly 00:48:43.270 --> 00:48:45.540 align:start position:0% he only knows that the brewer has sadly known<00:48:43.630> the<00:48:43.810> mind<00:48:44.050> and<00:48:44.500> moreover<00:48:45.310> the 00:48:45.540 --> 00:48:45.550 align:start position:0% known the mind and moreover the 00:48:45.550 --> 00:48:49.260 align:start position:0% known the mind and moreover the polynomial<00:48:46.060> is<00:48:46.180> of<00:48:46.210> degree<00:48:47.250> the<00:48:48.250> degree<00:48:49.119> of 00:48:49.260 --> 00:48:49.270 align:start position:0% polynomial is of degree the degree of 00:48:49.270 --> 00:48:51.240 align:start position:0% polynomial is of degree the degree of autonomy<00:48:49.660> was<00:48:49.750> bounded<00:48:50.290> by<00:48:50.440> some<00:48:50.950> parameter 00:48:51.240 --> 00:48:51.250 align:start position:0% autonomy was bounded by some parameter 00:48:51.250 --> 00:48:58.410 align:start position:0% autonomy was bounded by some parameter chicken<00:48:51.970> is<00:48:52.180> a<00:48:52.210> top<00:48:52.480> phase<00:48:54.150> then<00:48:55.410> the<00:48:57.420> latest 00:48:58.410 --> 00:48:58.420 align:start position:0% chicken is a top phase then the latest 00:48:58.420 --> 00:49:01.230 align:start position:0% chicken is a top phase then the latest Epps<00:48:58.660> protocol<00:48:59.440> with<00:49:00.400> us<00:49:00.550> at<00:49:00.820> the<00:49:00.880> brewer<00:49:01.089> to 00:49:01.230 --> 00:49:01.240 align:start position:0% Epps protocol with us at the brewer to 00:49:01.240 --> 00:49:03.930 align:start position:0% Epps protocol with us at the brewer to open<00:49:02.050> the<00:49:02.470> committee<00:49:02.770> polynomial<00:49:03.339> at<00:49:03.609> some 00:49:03.930 --> 00:49:03.940 align:start position:0% open the committee polynomial at some 00:49:03.940 --> 00:49:09.780 align:start position:0% open the committee polynomial at some point<00:49:04.210> and<00:49:05.070> verify<00:49:06.070> just<00:49:07.800> opens<00:49:08.800> a<00:49:09.099> revelation 00:49:09.780 --> 00:49:09.790 align:start position:0% point and verify just opens a revelation 00:49:09.790 --> 00:49:13.740 align:start position:0% point and verify just opens a revelation of<00:49:10.060> a<00:49:10.210> polynomial<00:49:10.750> and<00:49:11.320> also<00:49:12.270> send<00:49:13.270> us<00:49:13.420> some 00:49:13.740 --> 00:49:13.750 align:start position:0% of a polynomial and also send us some 00:49:13.750 --> 00:49:15.180 align:start position:0% of a polynomial and also send us some proof<00:49:14.530> of<00:49:14.619> correctness 00:49:15.180 --> 00:49:15.190 align:start position:0% proof of correctness 00:49:15.190 --> 00:49:18.329 align:start position:0% proof of correctness so<00:49:15.609> that<00:49:15.820> relate<00:49:16.329> to<00:49:16.359> my<00:49:17.260> chair<00:49:17.619> that<00:49:17.950> this 00:49:18.329 --> 00:49:18.339 align:start position:0% so that relate to my chair that this 00:49:18.339 --> 00:49:22.319 align:start position:0% so that relate to my chair that this openness<00:49:18.910> is<00:49:19.270> these<00:49:19.540> days<00:49:21.060> related<00:49:22.060> to<00:49:22.210> the 00:49:22.319 --> 00:49:22.329 align:start position:0% openness is these days related to the 00:49:22.329 --> 00:49:39.829 align:start position:0% openness is these days related to the conditional<00:49:22.750> normal<00:49:23.050> self<00:49:23.320> so<00:49:23.589> it's<00:49:23.770> possible 00:49:39.829 --> 00:49:39.839 align:start position:0% 00:49:39.839 --> 00:49:42.990 align:start position:0% we<00:49:40.839> was<00:49:41.530> thinking<00:49:41.770> about<00:49:41.829> to<00:49:42.280> commence<00:49:42.670> or 00:49:42.990 --> 00:49:43.000 align:start position:0% we was thinking about to commence or 00:49:43.000 --> 00:49:48.120 align:start position:0% we was thinking about to commence or something<00:49:45.089> I<00:49:46.089> think<00:49:46.690> I<00:49:47.170> don't<00:49:47.560> have<00:49:47.770> much<00:49:47.920> time 00:49:48.120 --> 00:49:48.130 align:start position:0% something I think I don't have much time 00:49:48.130 --> 00:49:50.190 align:start position:0% something I think I don't have much time so<00:49:48.190> he<00:49:48.700> took<00:49:49.119> our<00:49:49.300> kingdom<00:49:49.690> each<00:49:49.810> month<00:49:50.050> which 00:49:50.190 --> 00:49:50.200 align:start position:0% so he took our kingdom each month which 00:49:50.200 --> 00:49:54.410 align:start position:0% so he took our kingdom each month which is<00:49:50.349> just<00:49:51.030> that<00:49:52.030> main<00:49:52.740> protection<00:49:53.740> schemes 00:49:54.410 --> 00:49:54.420 align:start position:0% is just that main protection schemes 00:49:54.420 --> 00:50:01.020 align:start position:0% is just that main protection schemes unity<00:49:55.420> and<00:49:56.760> using<00:49:57.760> no<00:49:57.880> protocols<00:49:59.130> but<00:50:00.130> what 00:50:01.020 --> 00:50:01.030 align:start position:0% unity and using no protocols but what 00:50:01.030 --> 00:50:06.200 align:start position:0% unity and using no protocols but what what's<00:50:01.839> the<00:50:02.020> main<00:50:02.170> point<00:50:02.530> here<00:50:04.349> first<00:50:05.349> of<00:50:05.440> all 00:50:06.200 --> 00:50:06.210 align:start position:0% what's the main point here first of all 00:50:06.210 --> 00:50:09.300 align:start position:0% what's the main point here first of all why<00:50:07.210> isn't<00:50:07.540> some<00:50:07.660> kind<00:50:07.810> of<00:50:07.960> Russian<00:50:08.200> and<00:50:08.650> the 00:50:09.300 --> 00:50:09.310 align:start position:0% why isn't some kind of Russian and the 00:50:09.310 --> 00:50:12.420 align:start position:0% why isn't some kind of Russian and the fractional<00:50:09.730> movies<00:50:10.589> is<00:50:11.589> the<00:50:11.890> main<00:50:12.069> thing<00:50:12.400> that 00:50:12.420 --> 00:50:12.430 align:start position:0% fractional movies is the main thing that 00:50:12.430 --> 00:50:15.660 align:start position:0% fractional movies is the main thing that fries<00:50:13.390> Franco<00:50:14.140> squeeze<00:50:14.440> which<00:50:15.369> shows<00:50:15.640> that 00:50:15.660 --> 00:50:15.670 align:start position:0% fries Franco squeeze which shows that 00:50:15.670 --> 00:50:18.510 align:start position:0% fries Franco squeeze which shows that funding<00:50:16.510> is<00:50:16.990> not<00:50:17.170> really<00:50:17.560> really<00:50:17.920> really<00:50:18.099> ever 00:50:18.510 --> 00:50:18.520 align:start position:0% funding is not really really really ever 00:50:18.520 --> 00:50:22.230 align:start position:0% funding is not really really really ever spoken<00:50:19.000> you<00:50:19.720> cannot<00:50:19.930> just<00:50:20.200> keep<00:50:20.530> this<00:50:20.770> part 00:50:22.230 --> 00:50:22.240 align:start position:0% spoken you cannot just keep this part 00:50:22.240 --> 00:50:24.069 align:start position:0% spoken you cannot just keep this part same<00:50:22.690> thing<00:50:23.109> which<00:50:23.320> is 00:50:24.069 --> 00:50:24.079 align:start position:0% same thing which is 00:50:24.079 --> 00:50:26.229 align:start position:0% same thing which is which<00:50:24.229> wasn't<00:50:24.469> quite<00:50:24.680> right<00:50:25.279> which<00:50:25.910> basically 00:50:26.229 --> 00:50:26.239 align:start position:0% which wasn't quite right which basically 00:50:26.239 --> 00:50:28.150 align:start position:0% which wasn't quite right which basically tells<00:50:26.630> listen<00:50:27.109> same<00:50:27.349> as<00:50:27.589> a<00:50:27.619> bullet<00:50:27.979> on<00:50:28.009> all 00:50:28.150 --> 00:50:28.160 align:start position:0% tells listen same as a bullet on all 00:50:28.160 --> 00:50:31.870 align:start position:0% tells listen same as a bullet on all feet<00:50:28.430> and<00:50:29.529> even<00:50:30.529> the<00:50:30.709> okapi<00:50:30.979> is<00:50:31.459> the<00:50:31.700> true 00:50:31.870 --> 00:50:31.880 align:start position:0% feet and even the okapi is the true 00:50:31.880 --> 00:50:35.099 align:start position:0% feet and even the okapi is the true politics<00:50:32.450> going<00:50:32.599> on<00:50:32.809> at<00:50:32.930> this<00:50:32.989> point<00:50:33.229> and<00:50:33.859> this 00:50:35.099 --> 00:50:35.109 align:start position:0% politics going on at this point and this 00:50:35.109 --> 00:50:37.839 align:start position:0% politics going on at this point and this well<00:50:36.109> if<00:50:36.289> you<00:50:36.380> still<00:50:36.559> practice<00:50:37.099> and<00:50:37.640> you<00:50:37.729> will 00:50:37.839 --> 00:50:37.849 align:start position:0% well if you still practice and you will 00:50:37.849 --> 00:50:40.390 align:start position:0% well if you still practice and you will get<00:50:37.999> to<00:50:38.180> zero<00:50:38.359> waste<00:50:38.539> points<00:50:39.019> because<00:50:39.410> it<00:50:39.680> is 00:50:40.390 --> 00:50:40.400 align:start position:0% get to zero waste points because it is 00:50:40.400 --> 00:50:42.699 align:start position:0% get to zero waste points because it is ilithyia<00:50:40.640> narrator<00:50:41.209> and<00:50:41.989> if<00:50:42.200> it's<00:50:42.349> the<00:50:42.499> booth 00:50:42.699 --> 00:50:42.709 align:start position:0% ilithyia narrator and if it's the booth 00:50:42.709 --> 00:50:45.279 align:start position:0% ilithyia narrator and if it's the booth defenses<00:50:43.519> numerator<00:50:44.209> has<00:50:44.719> a<00:50:44.779> good<00:50:45.049> at<00:50:45.170> this 00:50:45.279 --> 00:50:45.289 align:start position:0% defenses numerator has a good at this 00:50:45.289 --> 00:50:47.049 align:start position:0% defenses numerator has a good at this point<00:50:45.589> that<00:50:45.769> you<00:50:45.890> can<00:50:46.039> divide<00:50:46.279> it<00:50:46.459> and<00:50:46.640> get 00:50:47.049 --> 00:50:47.059 align:start position:0% point that you can divide it and get 00:50:47.059 --> 00:50:48.670 align:start position:0% point that you can divide it and get another<00:50:47.299> collateral<00:50:47.930> which<00:50:48.109> is<00:50:48.259> just<00:50:48.440> making 00:50:48.670 --> 00:50:48.680 align:start position:0% another collateral which is just making 00:50:48.680 --> 00:50:51.489 align:start position:0% another collateral which is just making you<00:50:48.829> less<00:50:49.009> so<00:50:49.819> you<00:50:49.940> can<00:50:50.479> do<00:50:50.599> this<00:50:50.959> is<00:50:51.170> very<00:50:51.410> easy 00:50:51.489 --> 00:50:51.499 align:start position:0% you less so you can do this is very easy 00:50:51.499 --> 00:50:55.739 align:start position:0% you less so you can do this is very easy this<00:50:52.069> is<00:50:52.130> and<00:50:53.289> relation<00:50:54.289> be<00:50:54.380> exploited<00:50:54.890> by 00:50:55.739 --> 00:50:55.749 align:start position:0% this is and relation be exploited by 00:50:55.749 --> 00:50:58.719 align:start position:0% this is and relation be exploited by commitment<00:50:56.749> and<00:50:56.839> else<00:50:57.709> it<00:50:57.920> begins<00:50:58.219> as<00:50:58.430> a<00:50:58.459> set 00:50:58.719 --> 00:50:58.729 align:start position:0% commitment and else it begins as a set 00:50:58.729 --> 00:51:01.509 align:start position:0% commitment and else it begins as a set of<00:50:58.880> space<00:50:59.119> you<00:50:59.299> can<00:50:59.329> implement<00:50:59.749> to<00:51:00.289> how<00:51:00.589> what 00:51:01.509 --> 00:51:01.519 align:start position:0% of space you can implement to how what 00:51:01.519 --> 00:51:04.059 align:start position:0% of space you can implement to how what does<00:51:01.640> it<00:51:01.759> agree<00:51:01.940> is<00:51:02.089> a<00:51:02.119> blonde<00:51:02.359> with<00:51:02.779> me<00:51:02.930> -<00:51:03.170> you 00:51:04.059 --> 00:51:04.069 align:start position:0% does it agree is a blonde with me - you 00:51:04.069 --> 00:51:05.979 align:start position:0% does it agree is a blonde with me - you can<00:51:04.249> be<00:51:04.400> questioners<00:51:04.940> your<00:51:05.420> initial 00:51:05.979 --> 00:51:05.989 align:start position:0% can be questioners your initial 00:51:05.989 --> 00:51:08.559 align:start position:0% can be questioners your initial commitment<00:51:06.319> was<00:51:06.859> actually<00:51:07.459> political<00:51:08.059> after 00:51:08.559 --> 00:51:08.569 align:start position:0% commitment was actually political after 00:51:08.569 --> 00:51:10.509 align:start position:0% commitment was actually political after certain<00:51:08.749> degree<00:51:09.109> and<00:51:09.650> after<00:51:09.799> to<00:51:10.099> you<00:51:10.190> this<00:51:10.339> is 00:51:10.509 --> 00:51:10.519 align:start position:0% certain degree and after to you this is 00:51:10.519 --> 00:51:11.890 align:start position:0% certain degree and after to you this is official<00:51:10.819> you<00:51:10.910> cannot<00:51:11.150> you<00:51:11.390> cannot<00:51:11.630> commit 00:51:11.890 --> 00:51:11.900 align:start position:0% official you cannot you cannot commit 00:51:11.900 --> 00:51:14.499 align:start position:0% official you cannot you cannot commit saturation<00:51:12.380> function<00:51:12.700> unless<00:51:13.700> broken<00:51:14.299> down 00:51:14.499 --> 00:51:14.509 align:start position:0% saturation function unless broken down 00:51:14.509 --> 00:51:17.709 align:start position:0% saturation function unless broken down as<00:51:14.869> if<00:51:15.319> your<00:51:15.589> crypto<00:51:16.239> use<00:51:17.239> this<00:51:17.420> and<00:51:17.660> then 00:51:17.709 --> 00:51:17.719 align:start position:0% as if your crypto use this and then 00:51:17.719 --> 00:51:21.130 align:start position:0% as if your crypto use this and then later<00:51:18.650> and<00:51:19.039> opening<00:51:19.400> space<00:51:19.579> you<00:51:20.119> Elsa<00:51:20.959> not 00:51:21.130 --> 00:51:21.140 align:start position:0% later and opening space you Elsa not 00:51:21.140 --> 00:51:23.319 align:start position:0% later and opening space you Elsa not face<00:51:21.709> the<00:51:21.950> proof<00:51:22.160> and<00:51:22.339> say<00:51:22.549> this<00:51:23.059> my 00:51:23.319 --> 00:51:23.329 align:start position:0% face the proof and say this my 00:51:23.329 --> 00:51:25.870 align:start position:0% face the proof and say this my commitment<00:51:23.900> is<00:51:24.019> my<00:51:24.170> sample<00:51:24.469> uses<00:51:24.979> my<00:51:25.309> proof 00:51:25.870 --> 00:51:25.880 align:start position:0% commitment is my sample uses my proof 00:51:25.880 --> 00:51:27.880 align:start position:0% commitment is my sample uses my proof if<00:51:26.329> everything<00:51:26.839> passes<00:51:27.019> and<00:51:27.319> was<00:51:27.469> a<00:51:27.499> factor<00:51:27.829> of 00:51:27.880 --> 00:51:27.890 align:start position:0% if everything passes and was a factor of 00:51:27.890 --> 00:51:32.109 align:start position:0% if everything passes and was a factor of utility<00:51:28.599> it<00:51:29.599> was<00:51:29.869> to<00:51:30.049> do<00:51:30.229> all<00:51:30.259> of<00:51:30.890> this<00:51:31.119> other 00:51:32.109 --> 00:51:32.119 align:start position:0% utility it was to do all of this other 00:51:32.119 --> 00:51:33.999 align:start position:0% utility it was to do all of this other information<00:51:32.469> committed<00:51:33.469> at<00:51:33.589> this<00:51:33.739> point 00:51:33.999 --> 00:51:34.009 align:start position:0% information committed at this point 00:51:34.009 --> 00:51:39.910 align:start position:0% information committed at this point otherwise<00:51:38.199> yes<00:51:39.199> some<00:51:39.410> of<00:51:39.469> the<00:51:39.559> main<00:51:39.709> thing 00:51:39.910 --> 00:51:39.920 align:start position:0% otherwise yes some of the main thing 00:51:39.920 --> 00:51:42.849 align:start position:0% otherwise yes some of the main thing that<00:51:40.130> this<00:51:40.430> furniture<00:51:40.940> are<00:51:41.150> a<00:51:41.390> is<00:51:41.630> not<00:51:41.869> should 00:51:42.849 --> 00:51:42.859 align:start position:0% that this furniture are a is not should 00:51:42.859 --> 00:51:46.660 align:start position:0% that this furniture are a is not should not<00:51:42.890> be<00:51:43.009> known<00:51:44.319> neither<00:51:45.319> for<00:51:45.739> committee 00:51:46.660 --> 00:51:46.670 align:start position:0% not be known neither for committee 00:51:46.670 --> 00:51:49.359 align:start position:0% not be known neither for committee approval<00:51:47.059> and<00:51:47.239> all<00:51:47.390> for<00:51:47.839> verifying<00:51:48.529> and<00:51:48.859> there 00:51:49.359 --> 00:51:49.369 align:start position:0% approval and all for verifying and there 00:51:49.369 --> 00:51:52.829 align:start position:0% approval and all for verifying and there are<00:51:49.430> many<00:51:49.670> zeros<00:51:50.239> schemes<00:51:50.569> such<00:51:51.259> as<00:51:51.289> long<00:51:51.890> or 00:51:52.829 --> 00:51:52.839 align:start position:0% are many zeros schemes such as long or 00:51:52.839 --> 00:52:01.180 align:start position:0% are many zeros schemes such as long or as<00:51:53.839> a<00:51:54.739> novice<00:51:55.190> taken<00:51:56.109> sewing<00:51:58.959> the<00:51:59.959> only<00:52:00.349> the 00:52:01.180 --> 00:52:01.190 align:start position:0% as a novice taken sewing the only the 00:52:01.190 --> 00:52:06.390 align:start position:0% as a novice taken sewing the only the only<00:52:01.219> one<00:52:01.609> team<00:52:04.569> because<00:52:05.569> the<00:52:05.839> only<00:52:05.989> one 00:52:06.390 --> 00:52:06.400 align:start position:0% only one team because the only one 00:52:06.400 --> 00:52:09.969 align:start position:0% only one team because the only one reason<00:52:07.400> they<00:52:08.209> require<00:52:08.690> the<00:52:09.469> just<00:52:09.680> a<00:52:09.769> setup 00:52:09.969 --> 00:52:09.979 align:start position:0% reason they require the just a setup 00:52:09.979 --> 00:52:10.780 align:start position:0% reason they require the just a setup ceremony 00:52:10.780 --> 00:52:10.790 align:start position:0% ceremony 00:52:10.790 --> 00:52:13.600 align:start position:0% ceremony is<00:52:10.880> it<00:52:11.150> was<00:52:11.330> their<00:52:12.170> ways<00:52:12.470> to<00:52:12.770> keep<00:52:13.100> management 00:52:13.600 --> 00:52:13.610 align:start position:0% is it was their ways to keep management 00:52:13.610 --> 00:52:15.940 align:start position:0% is it was their ways to keep management and<00:52:13.910> so<00:52:14.090> you<00:52:14.420> were<00:52:14.900> able<00:52:15.020> to<00:52:15.200> replace<00:52:15.560> it 00:52:15.940 --> 00:52:15.950 align:start position:0% and so you were able to replace it 00:52:15.950 --> 00:52:17.800 align:start position:0% and so you were able to replace it commitment<00:52:16.430> with<00:52:16.640> something<00:52:17.240> that<00:52:17.480> requires 00:52:17.800 --> 00:52:17.810 align:start position:0% commitment with something that requires 00:52:17.810 --> 00:52:19.690 align:start position:0% commitment with something that requires only<00:52:18.110> as<00:52:18.500> far<00:52:18.650> as<00:52:18.770> the<00:52:18.890> child<00:52:19.070> or<00:52:19.340> against<00:52:19.610> a 00:52:19.690 --> 00:52:19.700 align:start position:0% only as far as the child or against a 00:52:19.700 --> 00:52:22.480 align:start position:0% only as far as the child or against a child<00:52:19.910> then<00:52:20.600> those<00:52:21.350> commitments<00:52:22.100> Keynes 00:52:22.480 --> 00:52:22.490 align:start position:0% child then those commitments Keynes 00:52:22.490 --> 00:52:25.900 align:start position:0% child then those commitments Keynes those<00:52:23.360> zero<00:52:24.170> schemes<00:52:24.560> will<00:52:25.220> be<00:52:25.340> transparent 00:52:25.900 --> 00:52:25.910 align:start position:0% those zero schemes will be transparent 00:52:25.910 --> 00:52:31.260 align:start position:0% those zero schemes will be transparent by<00:52:26.720> my<00:52:27.260> design 00:52:31.260 --> 00:52:31.270 align:start position:0% 00:52:31.270 --> 00:52:38.230 align:start position:0% okay<00:52:32.410> this<00:52:33.410> is<00:52:33.560> just<00:52:35.110> the<00:52:36.110> main<00:52:36.370> the<00:52:37.370> main<00:52:37.400> I 00:52:38.230 --> 00:52:38.240 align:start position:0% okay this is just the main the main I 00:52:38.240 --> 00:52:40.600 align:start position:0% okay this is just the main the main I might<00:52:38.600> want<00:52:38.840> to<00:52:38.870> call<00:52:39.050> the<00:52:39.110> fry<00:52:39.470> based<00:52:39.980> an<00:52:40.460> old 00:52:40.600 --> 00:52:40.610 align:start position:0% might want to call the fry based an old 00:52:40.610 --> 00:52:45.700 align:start position:0% might want to call the fry based an old countries<00:52:40.940> much<00:52:41.120> I<00:52:41.390> just<00:52:42.080> want<00:52:44.440> to<00:52:45.440> explain 00:52:45.700 --> 00:52:45.710 align:start position:0% countries much I just want to explain 00:52:45.710 --> 00:52:48.190 align:start position:0% countries much I just want to explain what<00:52:46.700> is<00:52:46.850> going<00:52:46.880> on<00:52:47.330> first 00:52:48.190 --> 00:52:48.200 align:start position:0% what is going on first 00:52:48.200 --> 00:53:00.630 align:start position:0% what is going on first first<00:52:50.410> the<00:52:51.410> commitment 00:53:00.630 --> 00:53:00.640 align:start position:0% 00:53:00.640 --> 00:53:05.049 align:start position:0% at<00:53:01.640> an<00:53:01.970> interface<00:53:03.039> we<00:53:04.039> want<00:53:04.220> to<00:53:04.309> be<00:53:04.369> sure<00:53:04.579> we<00:53:04.880> as 00:53:05.049 --> 00:53:05.059 align:start position:0% at an interface we want to be sure we as 00:53:05.059 --> 00:53:07.000 align:start position:0% at an interface we want to be sure we as a<00:53:05.150> verified<00:53:05.480> one<00:53:05.599> to<00:53:05.690> be<00:53:05.779> sure<00:53:05.990> that<00:53:06.380> the 00:53:07.000 --> 00:53:07.010 align:start position:0% a verified one to be sure that the 00:53:07.010 --> 00:53:09.130 align:start position:0% a verified one to be sure that the function<00:53:07.220> under<00:53:07.970> commitment<00:53:08.660> is<00:53:08.869> a<00:53:08.930> phone 00:53:09.130 --> 00:53:09.140 align:start position:0% function under commitment is a phone 00:53:09.140 --> 00:53:10.740 align:start position:0% function under commitment is a phone number<00:53:09.289> not<00:53:10.010> soundest 00:53:10.740 --> 00:53:10.750 align:start position:0% number not soundest 00:53:10.750 --> 00:53:14.440 align:start position:0% number not soundest random<00:53:12.549> random<00:53:13.549> set<00:53:13.700> of<00:53:13.730> wireless<00:53:14.000> and<00:53:14.420> the 00:53:14.440 --> 00:53:14.450 align:start position:0% random random set of wireless and the 00:53:14.450 --> 00:53:17.289 align:start position:0% random random set of wireless and the commitment<00:53:15.410> here<00:53:15.619> is<00:53:15.890> again<00:53:16.369> Naruto<00:53:16.700> as<00:53:17.180> in 00:53:17.289 --> 00:53:17.299 align:start position:0% commitment here is again Naruto as in 00:53:17.299 --> 00:53:20.289 align:start position:0% commitment here is again Naruto as in Pride<00:53:17.539> and<00:53:17.869> so<00:53:18.380> we<00:53:18.619> run<00:53:18.950> one<00:53:19.220> it<00:53:19.490> has<00:53:19.640> a<00:53:19.670> fry<00:53:19.970> at 00:53:20.289 --> 00:53:20.299 align:start position:0% Pride and so we run one it has a fry at 00:53:20.299 --> 00:53:25.809 align:start position:0% Pride and so we run one it has a fry at commit<00:53:20.599> phase<00:53:21.069> to<00:53:22.069> be<00:53:22.160> sure<00:53:22.460> that<00:53:24.819> the 00:53:25.809 --> 00:53:25.819 align:start position:0% commit phase to be sure that the 00:53:25.819 --> 00:53:26.920 align:start position:0% commit phase to be sure that the function<00:53:26.000> of<00:53:26.299> the<00:53:26.390> commitment<00:53:26.779> is<00:53:26.900> a 00:53:26.920 --> 00:53:26.930 align:start position:0% function of the commitment is a 00:53:26.930 --> 00:53:30.309 align:start position:0% function of the commitment is a polynomial<00:53:27.200> and<00:53:27.799> then<00:53:28.809> around<00:53:29.809> another 00:53:30.309 --> 00:53:30.319 align:start position:0% polynomial and then around another 00:53:30.319 --> 00:53:34.000 align:start position:0% polynomial and then around another instance<00:53:31.309> of<00:53:31.490> private<00:53:32.299> over<00:53:32.630> face<00:53:32.869> but<00:53:33.529> this 00:53:34.000 --> 00:53:34.010 align:start position:0% instance of private over face but this 00:53:34.010 --> 00:53:36.490 align:start position:0% instance of private over face but this time<00:53:34.250> with<00:53:34.760> respect<00:53:34.940> to<00:53:35.180> the<00:53:35.359> August<00:53:35.779> fraction 00:53:36.490 --> 00:53:36.500 align:start position:0% time with respect to the August fraction 00:53:36.500 --> 00:53:39.069 align:start position:0% time with respect to the August fraction and<00:53:37.099> again<00:53:37.789> we're<00:53:38.119> trying<00:53:38.240> to<00:53:38.450> show<00:53:38.630> that<00:53:38.660> this 00:53:39.069 --> 00:53:39.079 align:start position:0% and again we're trying to show that this 00:53:39.079 --> 00:53:41.549 align:start position:0% and again we're trying to show that this abdominal<00:53:39.680> I<00:53:39.890> think<00:53:40.460> we'll<00:53:40.970> skip<00:53:41.119> the<00:53:41.329> proof 00:53:41.549 --> 00:53:41.559 align:start position:0% abdominal I think we'll skip the proof 00:53:41.559 --> 00:53:44.529 align:start position:0% abdominal I think we'll skip the proof this<00:53:42.559> is<00:53:42.619> the<00:53:42.799> main<00:53:43.039> idea<00:53:43.069> why<00:53:43.609> why<00:53:44.119> oh<00:53:44.150> why 00:53:44.529 --> 00:53:44.539 align:start position:0% this is the main idea why why oh why 00:53:44.539 --> 00:53:48.609 align:start position:0% this is the main idea why why oh why this<00:53:44.930> this<00:53:45.380> book<00:53:45.740> but<00:53:46.430> there's<00:53:46.609> one<00:53:47.619> one 00:53:48.609 --> 00:53:48.619 align:start position:0% this this book but there's one one 00:53:48.619 --> 00:53:52.120 align:start position:0% this this book but there's one one important<00:53:49.519> thing<00:53:49.930> between<00:53:50.930> the<00:53:51.920> gate 00:53:52.120 --> 00:53:52.130 align:start position:0% important thing between the gate 00:53:52.130 --> 00:53:54.009 align:start position:0% important thing between the gate commitment<00:53:52.670> beyond<00:53:53.000> the<00:53:53.119> private<00:53:53.390> and 00:53:54.009 --> 00:53:54.019 align:start position:0% commitment beyond the private and 00:53:54.019 --> 00:53:58.779 align:start position:0% commitment beyond the private and schemes<00:53:54.760> as<00:53:55.760> told<00:53:56.750> some<00:53:57.440> in<00:53:57.559> second<00:53:57.890> fry<00:53:58.490> is 00:53:58.779 --> 00:53:58.789 align:start position:0% schemes as told some in second fry is 00:53:58.789 --> 00:54:01.569 align:start position:0% schemes as told some in second fry is unable<00:53:59.029> to<00:53:59.210> distinguish<00:53:59.750> between<00:54:00.579> Domino's 00:54:01.569 --> 00:54:01.579 align:start position:0% unable to distinguish between Domino's 00:54:01.579 --> 00:54:04.630 align:start position:0% unable to distinguish between Domino's and<00:54:02.769> functions<00:54:03.769> which<00:54:03.890> are<00:54:03.980> close<00:54:04.220> to<00:54:04.460> them 00:54:04.630 --> 00:54:04.640 align:start position:0% and functions which are close to them 00:54:04.640 --> 00:54:12.700 align:start position:0% and functions which are close to them with<00:54:05.509> respect<00:54:05.539> to<00:54:06.049> of<00:54:06.230> having<00:54:06.559> waitress<00:54:08.920> so<00:54:11.710> if 00:54:12.700 --> 00:54:12.710 align:start position:0% with respect to of having waitress so if 00:54:12.710 --> 00:54:16.390 align:start position:0% with respect to of having waitress so if we<00:54:13.329> are<00:54:14.329> not<00:54:14.420> sure<00:54:14.690> that<00:54:14.720> our<00:54:15.230> function<00:54:15.920> can<00:54:16.279> it 00:54:16.390 --> 00:54:16.400 align:start position:0% we are not sure that our function can it 00:54:16.400 --> 00:54:20.319 align:start position:0% we are not sure that our function can it stays<00:54:16.700> is<00:54:17.000> not<00:54:17.210> even<00:54:17.539> a<00:54:17.599> polynomial<00:54:19.329> which 00:54:20.319 --> 00:54:20.329 align:start position:0% stays is not even a polynomial which 00:54:20.329 --> 00:54:27.990 align:start position:0% stays is not even a polynomial which function<00:54:20.869> will<00:54:21.829> open<00:54:22.279> later<00:54:22.599> and<00:54:23.890> the<00:54:24.890> deal<00:54:25.130> is 00:54:27.990 --> 00:54:28.000 align:start position:0% 00:54:28.000 --> 00:54:31.240 align:start position:0% this<00:54:29.000> is<00:54:29.180> our<00:54:29.329> space<00:54:29.690> with<00:54:30.289> some<00:54:30.470> goals<00:54:30.859> or 00:54:31.240 --> 00:54:31.250 align:start position:0% this is our space with some goals or 00:54:31.250 --> 00:54:36.400 align:start position:0% this is our space with some goals or just<00:54:31.690> who<00:54:32.690> do<00:54:32.809> you<00:54:32.900> promise<00:54:33.460> this<00:54:34.460> is<00:54:35.410> our 00:54:36.400 --> 00:54:36.410 align:start position:0% just who do you promise this is our 00:54:36.410 --> 00:54:40.269 align:start position:0% just who do you promise this is our function<00:54:37.369> of<00:54:37.940> which<00:54:38.500> the<00:54:39.500> brewer<00:54:39.710> gives<00:54:40.069> no 00:54:40.269 --> 00:54:40.279 align:start position:0% function of which the brewer gives no 00:54:40.279 --> 00:54:46.180 align:start position:0% function of which the brewer gives no access<00:54:40.759> to<00:54:42.880> this<00:54:43.880> is<00:54:44.059> just<00:54:44.650> just<00:54:45.650> the<00:54:45.799> circle 00:54:46.180 --> 00:54:46.190 align:start position:0% access to this is just just the circle 00:54:46.190 --> 00:54:52.359 align:start position:0% access to this is just just the circle of<00:54:46.460> function<00:54:47.240> f<00:54:47.619> and<00:54:49.630> the<00:54:50.630> Westham<00:54:51.369> intersect 00:54:52.359 --> 00:54:52.369 align:start position:0% of function f and the Westham intersect 00:54:52.369 --> 00:54:56.650 align:start position:0% of function f and the Westham intersect at<00:54:52.579> several<00:54:52.940> numbers<00:54:54.039> the<00:54:55.039> fact<00:54:55.420> this<00:54:56.420> now 00:54:56.650 --> 00:54:56.660 align:start position:0% at several numbers the fact this now 00:54:56.660 --> 00:54:58.980 align:start position:0% at several numbers the fact this now commitment<00:54:57.200> scheme<00:54:57.440> will<00:54:57.920> only<00:54:58.130> show<00:54:58.430> that 00:54:58.980 --> 00:54:58.990 align:start position:0% commitment scheme will only show that 00:54:58.990 --> 00:55:00.670 align:start position:0% commitment scheme will only show that the<00:54:59.990> opening 00:55:00.670 --> 00:55:00.680 align:start position:0% the opening 00:55:00.680 --> 00:55:03.460 align:start position:0% the opening the<00:55:00.799> opening<00:55:01.690> which<00:55:02.690> will<00:55:02.839> be<00:55:02.930> done<00:55:03.140> at 00:55:03.460 --> 00:55:03.470 align:start position:0% the opening which will be done at 00:55:03.470 --> 00:55:08.109 align:start position:0% the opening which will be done at open-face<00:55:05.349> will<00:55:06.349> be<00:55:06.589> the<00:55:07.039> weather<00:55:07.250> of<00:55:07.640> almost 00:55:08.109 --> 00:55:08.119 align:start position:0% open-face will be the weather of almost 00:55:08.119 --> 00:55:11.819 align:start position:0% open-face will be the weather of almost one<00:55:08.510> of<00:55:08.690> these<00:55:08.779> polymers<00:55:09.260> at<00:55:09.500> intersection 00:55:11.819 --> 00:55:11.829 align:start position:0% one of these polymers at intersection 00:55:11.829 --> 00:55:17.410 align:start position:0% one of these polymers at intersection and<00:55:12.829> there<00:55:13.579> is<00:55:13.700> one<00:55:14.529> special<00:55:15.529> case<00:55:15.890> when<00:55:16.670> Delta 00:55:17.410 --> 00:55:17.420 align:start position:0% and there is one special case when Delta 00:55:17.420 --> 00:55:20.980 align:start position:0% and there is one special case when Delta is<00:55:17.660> chosen<00:55:18.230> is<00:55:18.470> chosen<00:55:18.680> to<00:55:18.799> be<00:55:18.920> the<00:55:19.990> Ichiko 00:55:20.980 --> 00:55:20.990 align:start position:0% is chosen is chosen to be the Ichiko 00:55:20.990 --> 00:55:32.590 align:start position:0% is chosen is chosen to be the Ichiko tech<00:55:21.170> writers<00:55:21.799> parameter<00:55:22.460> in<00:55:22.819> this<00:55:23.599> case 00:55:32.590 --> 00:55:32.600 align:start position:0% 00:55:32.600 --> 00:55:34.510 align:start position:0% if<00:55:33.080> there<00:55:33.290> are<00:55:33.380> any<00:55:33.560> intersection<00:55:34.370> between 00:55:34.510 --> 00:55:34.520 align:start position:0% if there are any intersection between 00:55:34.520 --> 00:55:37.330 align:start position:0% if there are any intersection between our<00:55:35.150> function<00:55:35.750> and<00:55:35.960> the<00:55:36.620> space<00:55:36.860> of<00:55:36.980> problem 00:55:37.330 --> 00:55:37.340 align:start position:0% our function and the space of problem 00:55:37.340 --> 00:55:39.250 align:start position:0% our function and the space of problem proponents<00:55:37.850> of<00:55:38.120> our<00:55:38.300> degree<00:55:38.660> the 00:55:39.250 --> 00:55:39.260 align:start position:0% proponents of our degree the 00:55:39.260 --> 00:55:41.110 align:start position:0% proponents of our degree the intersection<00:55:39.770> will<00:55:40.040> contain<00:55:40.340> only<00:55:40.610> one<00:55:40.880> point 00:55:41.110 --> 00:55:41.120 align:start position:0% intersection will contain only one point 00:55:41.120 --> 00:55:46.060 align:start position:0% intersection will contain only one point and<00:55:41.510> this<00:55:42.170> particular<00:55:42.470> case<00:55:43.100> okay<00:55:43.460> just<00:55:45.070> may 00:55:46.060 --> 00:55:46.070 align:start position:0% and this particular case okay just may 00:55:46.070 --> 00:55:48.370 align:start position:0% and this particular case okay just may think<00:55:46.370> that<00:55:46.550> facial<00:55:47.360> commitment<00:55:47.810> at<00:55:47.900> approval 00:55:48.370 --> 00:55:48.380 align:start position:0% think that facial commitment at approval 00:55:48.380 --> 00:55:52.000 align:start position:0% think that facial commitment at approval was<00:55:48.800> not<00:55:48.980> to<00:55:49.190> the<00:55:49.490> function<00:55:50.320> but<00:55:51.320> to<00:55:51.470> that<00:55:51.650> one 00:55:52.000 --> 00:55:52.010 align:start position:0% was not to the function but to that one 00:55:52.010 --> 00:55:57.910 align:start position:0% was not to the function but to that one one<00:55:52.580> point<00:55:52.790> of<00:55:53.150> intersection<00:55:56.380> but<00:55:57.380> when<00:55:57.680> we're 00:55:57.910 --> 00:55:57.920 align:start position:0% one point of intersection but when we're 00:55:57.920 --> 00:56:01.350 align:start position:0% one point of intersection but when we're trying<00:55:58.160> to<00:55:58.280> apply<00:55:58.520> our<00:55:59.500> commitment<00:56:00.500> schemes 00:56:01.350 --> 00:56:01.360 align:start position:0% trying to apply our commitment schemes 00:56:01.360 --> 00:56:06.070 align:start position:0% trying to apply our commitment schemes -<00:56:02.360> it's<00:56:02.750> real<00:56:02.990> protocols<00:56:03.560> such<00:56:03.980> as<00:56:04.750> born<00:56:05.750> for 00:56:06.070 --> 00:56:06.080 align:start position:0% - it's real protocols such as born for 00:56:06.080 --> 00:56:11.140 align:start position:0% - it's real protocols such as born for example<00:56:08.620> we<00:56:09.620> apply<00:56:09.890> them<00:56:10.130> to<00:56:10.250> witness 00:56:11.140 --> 00:56:11.150 align:start position:0% example we apply them to witness 00:56:11.150 --> 00:56:15.790 align:start position:0% example we apply them to witness Panama's<00:56:11.810> inform<00:56:12.770> scheme<00:56:14.140> the<00:56:15.140> verifier<00:56:15.560> us 00:56:15.790 --> 00:56:15.800 align:start position:0% Panama's inform scheme the verifier us 00:56:15.800 --> 00:56:21.130 align:start position:0% Panama's inform scheme the verifier us approval<00:56:16.400> to<00:56:17.260> cope<00:56:18.260> and<00:56:18.350> available<00:56:20.050> with<00:56:21.050> us 00:56:21.130 --> 00:56:21.140 align:start position:0% approval to cope and available with us 00:56:21.140 --> 00:56:25.510 align:start position:0% approval to cope and available with us phenomenal<00:56:21.710> and<00:56:22.240> we<00:56:23.240> may<00:56:23.780> think<00:56:23.840> that<00:56:24.200> any<00:56:25.040> of 00:56:25.510 --> 00:56:25.520 align:start position:0% phenomenal and we may think that any of 00:56:25.520 --> 00:56:29.020 align:start position:0% phenomenal and we may think that any of the<00:56:25.880> possible<00:56:26.060> detection<00:56:27.130> available<00:56:28.130> with 00:56:29.020 --> 00:56:29.030 align:start position:0% the possible detection available with 00:56:29.030 --> 00:56:29.860 align:start position:0% the possible detection available with stone<00:56:29.330> Demasi 00:56:29.860 --> 00:56:29.870 align:start position:0% stone Demasi 00:56:29.870 --> 00:56:32.290 align:start position:0% stone Demasi it<00:56:30.020> doesn't<00:56:30.290> really<00:56:30.410> matter<00:56:30.650> but<00:56:31.150> there<00:56:32.150> is 00:56:32.290 --> 00:56:32.300 align:start position:0% it doesn't really matter but there is 00:56:32.300 --> 00:56:38.520 align:start position:0% it doesn't really matter but there is one<00:56:32.510> one<00:56:33.050> positive<00:56:36.400> the<00:56:37.400> next<00:56:37.610> one 00:56:38.520 --> 00:56:38.530 align:start position:0% one one positive the next one 00:56:38.530 --> 00:56:43.150 align:start position:0% one one positive the next one this<00:56:39.530> group<00:56:39.980> idea<00:56:40.370> was<00:56:40.610> stupid<00:56:40.790> for<00:56:41.060> now<00:56:42.160> this 00:56:43.150 --> 00:56:43.160 align:start position:0% this group idea was stupid for now this 00:56:43.160 --> 00:56:46.840 align:start position:0% this group idea was stupid for now this is<00:56:43.310> the<00:56:43.460> relaxed<00:56:43.790> version<00:56:44.920> was<00:56:45.920> intelligent 00:56:46.840 --> 00:56:46.850 align:start position:0% is the relaxed version was intelligent 00:56:46.850 --> 00:56:49.930 align:start position:0% is the relaxed version was intelligent reduce<00:56:47.120> and<00:56:47.830> her<00:56:48.830> last<00:56:49.010> question<00:56:49.430> where<00:56:49.670> the 00:56:49.930 --> 00:56:49.940 align:start position:0% reduce and her last question where the 00:56:49.940 --> 00:56:51.430 align:start position:0% reduce and her last question where the dissection<00:56:50.270> contained<00:56:50.750> more<00:56:50.930> than<00:56:50.990> one<00:56:51.200> point 00:56:51.430 --> 00:56:51.440 align:start position:0% dissection contained more than one point 00:56:51.440 --> 00:56:54.730 align:start position:0% dissection contained more than one point and<00:56:51.860> he<00:56:51.890> will<00:56:52.640> show<00:56:52.970> that<00:56:53.330> the<00:56:54.050> opening<00:56:54.530> is 00:56:54.730 --> 00:56:54.740 align:start position:0% and he will show that the opening is 00:56:54.740 --> 00:57:00.460 align:start position:0% and he will show that the opening is related<00:56:55.220> to<00:56:55.250> their<00:56:56.470> to<00:56:57.470> the<00:56:57.590> one<00:56:57.830> of<00:56:59.470> inventor 00:57:00.460 --> 00:57:00.470 align:start position:0% related to their to the one of inventor 00:57:00.470 --> 00:57:08.980 align:start position:0% related to their to the one of inventor section<00:57:03.580> and<00:57:05.680> another<00:57:06.680> theme<00:57:07.060> in<00:57:08.060> porn 00:57:08.980 --> 00:57:08.990 align:start position:0% section and another theme in porn 00:57:08.990 --> 00:57:13.000 align:start position:0% section and another theme in porn indicate<00:57:09.950> commitment<00:57:10.930> is<00:57:11.930> not<00:57:11.990> used<00:57:12.590> on<00:57:12.800> the 00:57:13.000 --> 00:57:13.010 align:start position:0% indicate commitment is not used on the 00:57:13.010 --> 00:57:15.970 align:start position:0% indicate commitment is not used on the is<00:57:13.220> not<00:57:13.370> yet<00:57:13.520> only<00:57:13.790> to<00:57:13.910> open<00:57:14.060> the<00:57:14.720> various<00:57:15.350> of 00:57:15.970 --> 00:57:15.980 align:start position:0% is not yet only to open the various of 00:57:15.980 --> 00:57:20.770 align:start position:0% is not yet only to open the various of witness<00:57:16.790> panels<00:57:18.610> their<00:57:19.610> commitment<00:57:20.300> is<00:57:20.480> also 00:57:20.770 --> 00:57:20.780 align:start position:0% witness panels their commitment is also 00:57:20.780 --> 00:57:24.590 align:start position:0% witness panels their commitment is also used<00:57:20.990> for<00:57:21.220> speed-up<00:57:22.450> calculation<00:57:23.450> of<00:57:23.660> custody 00:57:24.590 --> 00:57:24.600 align:start position:0% used for speed-up calculation of custody 00:57:24.600 --> 00:57:27.270 align:start position:0% used for speed-up calculation of custody what<00:57:25.600> I<00:57:25.630> mean<00:57:25.900> about<00:57:25.990> the<00:57:26.230> jacinto<00:57:26.680> jacinto 00:57:27.270 --> 00:57:27.280 align:start position:0% what I mean about the jacinto jacinto 00:57:27.280 --> 00:57:30.390 align:start position:0% what I mean about the jacinto jacinto animal<00:57:28.270> and<00:57:28.660> causes<00:57:29.050> our<00:57:29.230> problem<00:57:29.620> this<00:57:30.220> is<00:57:30.280> a 00:57:30.390 --> 00:57:30.400 align:start position:0% animal and causes our problem this is a 00:57:30.400 --> 00:57:32.130 align:start position:0% animal and causes our problem this is a phenomena<00:57:30.850> that<00:57:30.880> have<00:57:31.090> known<00:57:31.360> for<00:57:31.690> both<00:57:31.870> a 00:57:32.130 --> 00:57:32.140 align:start position:0% phenomena that have known for both a 00:57:32.140 --> 00:57:34.260 align:start position:0% phenomena that have known for both a proven<00:57:32.590> and<00:57:32.680> the<00:57:32.800> verifier<00:57:33.220> but<00:57:33.550> it<00:57:33.760> is<00:57:33.910> a<00:57:33.940> very 00:57:34.260 --> 00:57:34.270 align:start position:0% proven and the verifier but it is a very 00:57:34.270 --> 00:57:39.290 align:start position:0% proven and the verifier but it is a very less<00:57:34.570> degree<00:57:34.960> and<00:57:35.790> then<00:57:37.560> the<00:57:38.560> blue<00:57:38.710> asked 00:57:39.290 --> 00:57:39.300 align:start position:0% less degree and then the blue asked 00:57:39.300 --> 00:57:41.760 align:start position:0% less degree and then the blue asked developers<00:57:40.300> they<00:57:40.570> preferred<00:57:40.930> to<00:57:40.960> send<00:57:41.320> to 00:57:41.760 --> 00:57:41.770 align:start position:0% developers they preferred to send to 00:57:41.770 --> 00:57:43.560 align:start position:0% developers they preferred to send to send<00:57:41.920> the<00:57:42.040> opening<00:57:42.460> of<00:57:42.610> this<00:57:42.760> constraint 00:57:43.560 --> 00:57:43.570 align:start position:0% send the opening of this constraint 00:57:43.570 --> 00:57:44.130 align:start position:0% send the opening of this constraint bernama 00:57:44.130 --> 00:57:44.140 align:start position:0% bernama 00:57:44.140 --> 00:57:48.210 align:start position:0% bernama at<00:57:44.920> some<00:57:45.160> point<00:57:45.430> because<00:57:46.530> hidden<00:57:47.530> you<00:57:48.040> don't 00:57:48.210 --> 00:57:48.220 align:start position:0% at some point because hidden you don't 00:57:48.220 --> 00:57:50.610 align:start position:0% at some point because hidden you don't want<00:57:48.490> to<00:57:48.760> do<00:57:48.940> a<00:57:48.970> huge<00:57:49.510> amount<00:57:49.690> about<00:57:50.260> to<00:57:50.500> be 00:57:50.610 --> 00:57:50.620 align:start position:0% want to do a huge amount about to be 00:57:50.620 --> 00:57:55.770 align:start position:0% want to do a huge amount about to be late<00:57:50.770> my<00:57:51.550> degree<00:57:53.250> and<00:57:54.250> women<00:57:54.910> speak<00:57:55.330> about<00:57:55.510> it 00:57:55.770 --> 00:57:55.780 align:start position:0% late my degree and women speak about it 00:57:55.780 --> 00:57:59.520 align:start position:0% late my degree and women speak about it commitment<00:57:56.350> but<00:57:56.830> know<00:57:57.010> that<00:57:57.960> you<00:57:58.960> can<00:57:58.990> even<00:57:59.350> is 00:57:59.520 --> 00:57:59.530 align:start position:0% commitment but know that you can even is 00:57:59.530 --> 00:58:02.310 align:start position:0% commitment but know that you can even is received<00:58:00.150> then<00:58:01.150> the<00:58:01.300> open<00:58:01.570> of<00:58:01.660> the<00:58:01.750> camel<00:58:01.990> or 00:58:02.310 --> 00:58:02.320 align:start position:0% received then the open of the camel or 00:58:02.320 --> 00:58:05.100 align:start position:0% received then the open of the camel or the<00:58:02.470> commitment<00:58:02.800> is<00:58:03.250> specific<00:58:04.110> specifically 00:58:05.100 --> 00:58:05.110 align:start position:0% the commitment is specific specifically 00:58:05.110 --> 00:58:08.070 align:start position:0% the commitment is specific specifically normal<00:58:05.520> and<00:58:06.520> we<00:58:06.850> just<00:58:07.090> share<00:58:07.300> that<00:58:07.660> the 00:58:08.070 --> 00:58:08.080 align:start position:0% normal and we just share that the 00:58:08.080 --> 00:58:11.220 align:start position:0% normal and we just share that the commitment<00:58:08.710> is<00:58:09.310> just<00:58:09.730> is<00:58:10.420> related<00:58:10.930> to<00:58:10.960> the 00:58:11.220 --> 00:58:11.230 align:start position:0% commitment is just is related to the 00:58:11.230 --> 00:58:16.050 align:start position:0% commitment is just is related to the content<00:58:11.530> or<00:58:11.710> normal<00:58:12.070> but<00:58:12.660> in<00:58:13.660> this<00:58:13.840> case<00:58:15.060> in 00:58:16.050 --> 00:58:16.060 align:start position:0% content or normal but in this case in 00:58:16.060 --> 00:58:22.350 align:start position:0% content or normal but in this case in this<00:58:16.210> case<00:58:17.790> there<00:58:18.790> are<00:58:19.020> several<00:58:21.360> other 00:58:22.350 --> 00:58:22.360 align:start position:0% this case there are several other 00:58:22.360 --> 00:58:26.760 align:start position:0% this case there are several other animals<00:58:23.020> to<00:58:23.470> which<00:58:24.150> no<00:58:25.170> to<00:58:26.170> which<00:58:26.320> the<00:58:26.470> office 00:58:26.760 --> 00:58:26.770 align:start position:0% animals to which no to which the office 00:58:26.770 --> 00:58:29.490 align:start position:0% animals to which no to which the office may<00:58:26.920> provided<00:58:27.600> and<00:58:28.600> when<00:58:29.140> I<00:58:29.170> speak<00:58:29.380> about 00:58:29.490 --> 00:58:29.500 align:start position:0% may provided and when I speak about 00:58:29.500 --> 00:58:33.420 align:start position:0% may provided and when I speak about constrictor<00:58:30.250> enormous<00:58:30.580> this<00:58:30.790> means<00:58:31.150> that<00:58:32.430> the 00:58:33.420 --> 00:58:33.430 align:start position:0% constrictor enormous this means that the 00:58:33.430 --> 00:58:38.190 align:start position:0% constrictor enormous this means that the prover<00:58:33.880> might<00:58:34.390> send<00:58:36.300> the<00:58:37.300> open<00:58:37.570> to<00:58:37.720> Nauticus<00:58:38.110> a 00:58:38.190 --> 00:58:38.200 align:start position:0% prover might send the open to Nauticus a 00:58:38.200 --> 00:58:41.190 align:start position:0% prover might send the open to Nauticus a phenomena<00:58:38.710> which<00:58:38.860> means<00:58:39.390> that<00:58:40.390> he<00:58:40.780> sent<00:58:41.050> the 00:58:41.190 --> 00:58:41.200 align:start position:0% phenomena which means that he sent the 00:58:41.200 --> 00:58:43.470 align:start position:0% phenomena which means that he sent the answer<00:58:41.560> to<00:58:41.740> another<00:58:42.310> constraint<00:58:42.640> system<00:58:43.060> to 00:58:43.470 --> 00:58:43.480 align:start position:0% answer to another constraint system to 00:58:43.480 --> 00:58:46.020 align:start position:0% answer to another constraint system to another<00:58:43.780> problem<00:58:44.370> this<00:58:45.370> is<00:58:45.430> the<00:58:45.670> difference 00:58:46.020 --> 00:58:46.030 align:start position:0% another problem this is the difference 00:58:46.030 --> 00:58:47.760 align:start position:0% another problem this is the difference between<00:58:46.090> with<00:58:46.480> the<00:58:46.540> spa<00:58:46.720> animals<00:58:47.110> and<00:58:47.350> potato 00:58:47.760 --> 00:58:47.770 align:start position:0% between with the spa animals and potato 00:58:47.770 --> 00:58:53.880 align:start position:0% between with the spa animals and potato animals<00:58:48.250> and<00:58:49.740> so<00:58:51.990> the<00:58:52.990> goal<00:58:53.200> is<00:58:53.410> problem 00:58:53.880 --> 00:58:53.890 align:start position:0% animals and so the goal is problem 00:58:53.890 --> 00:58:56.430 align:start position:0% animals and so the goal is problem evolution<00:58:54.820> problem<00:58:55.180> because<00:58:56.050> there<00:58:56.230> was<00:58:56.320> no 00:58:56.430 --> 00:58:56.440 align:start position:0% evolution problem because there was no 00:58:56.440 --> 00:58:58.590 align:start position:0% evolution problem because there was no significant<00:58:57.250> number<00:58:57.580> this<00:58:58.390> is<00:58:58.450> the 00:58:58.590 --> 00:58:58.600 align:start position:0% significant number this is the 00:58:58.600 --> 00:59:00.420 align:start position:0% significant number this is the polynomial<00:58:59.080> which<00:58:59.350> is<00:58:59.470> known<00:58:59.650> for<00:58:59.890> both<00:59:00.100> sides 00:59:00.420 --> 00:59:00.430 align:start position:0% polynomial which is known for both sides 00:59:00.430 --> 00:59:07.830 align:start position:0% polynomial which is known for both sides and<00:59:01.110> for<00:59:02.110> which<00:59:04.890> the<00:59:05.890> verifier<00:59:06.600> wants<00:59:07.600> to<00:59:07.690> get 00:59:07.830 --> 00:59:07.840 align:start position:0% and for which the verifier wants to get 00:59:07.840 --> 00:59:11.010 align:start position:0% and for which the verifier wants to get the<00:59:07.990> opening<00:59:08.380> just<00:59:09.160> to<00:59:09.400> speed<00:59:09.790> up<00:59:10.030> to<00:59:10.390> reduce 00:59:11.010 --> 00:59:11.020 align:start position:0% the opening just to speed up to reduce 00:59:11.020 --> 00:59:14.190 align:start position:0% the opening just to speed up to reduce his<00:59:11.530> complexity<00:59:12.340> and<00:59:12.580> and<00:59:12.820> so<00:59:13.030> on<00:59:13.270> and<00:59:13.480> the 00:59:14.190 --> 00:59:14.200 align:start position:0% his complexity and and so on and the 00:59:14.200 --> 00:59:18.770 align:start position:0% his complexity and and so on and the solution<00:59:14.560> to<00:59:14.620> the<00:59:14.710> problem<00:59:15.010> is<00:59:15.160> the<00:59:15.280> following 00:59:18.770 --> 00:59:18.780 align:start position:0% 00:59:18.780 --> 00:59:22.790 align:start position:0% this<00:59:19.780> is<00:59:19.840> our<00:59:20.080> space<00:59:20.610> again<00:59:21.610> we 00:59:22.790 --> 00:59:22.800 align:start position:0% this is our space again we 00:59:22.800 --> 00:59:25.040 align:start position:0% this is our space again we [Music] 00:59:25.040 --> 00:59:25.050 align:start position:0% [Music] 00:59:25.050 --> 00:59:29.280 align:start position:0% [Music] now<00:59:26.050> we're<00:59:26.500> just<00:59:27.119> the<00:59:28.119> total<00:59:28.630> number<00:59:28.930> to<00:59:29.140> the 00:59:29.280 --> 00:59:29.290 align:start position:0% now we're just the total number to the 00:59:29.290 --> 00:59:31.319 align:start position:0% now we're just the total number to the variable<00:59:29.770> normal<00:59:30.130> so<00:59:30.339> this<00:59:30.579> is<00:59:30.670> inside<00:59:30.820> our 00:59:31.319 --> 00:59:31.329 align:start position:0% variable normal so this is inside our 00:59:31.329 --> 00:59:34.849 align:start position:0% variable normal so this is inside our space<00:59:31.920> little<00:59:32.920> Jake<00:59:33.130> the<00:59:33.310> parameter<00:59:33.730> Delta 00:59:34.849 --> 00:59:34.859 align:start position:0% space little Jake the parameter Delta 00:59:34.859 --> 00:59:38.599 align:start position:0% space little Jake the parameter Delta and<00:59:35.859> there<00:59:36.130> were<00:59:36.390> some<00:59:37.390> other<00:59:37.630> polynomials 00:59:38.599 --> 00:59:38.609 align:start position:0% and there were some other polynomials 00:59:38.609 --> 00:59:42.089 align:start position:0% and there were some other polynomials with<00:59:39.609> these<00:59:39.730> generators<00:59:40.349> but<00:59:41.349> that<00:59:41.560> is<00:59:41.829> East 00:59:42.089 --> 00:59:42.099 align:start position:0% with these generators but that is East 00:59:42.099 --> 00:59:47.099 align:start position:0% with these generators but that is East at<00:59:43.060> Starbase<00:59:44.790> the<00:59:45.790> bundles<00:59:46.329> are<00:59:46.420> small<00:59:46.720> for 00:59:47.099 --> 00:59:47.109 align:start position:0% at Starbase the bundles are small for 00:59:47.109 --> 00:59:49.620 align:start position:0% at Starbase the bundles are small for both<00:59:47.470> of<00:59:47.800> us<00:59:47.950> at<00:59:48.130> the<00:59:48.160> start<00:59:48.339> of<00:59:48.490> protocol<00:59:48.970> and 00:59:49.620 --> 00:59:49.630 align:start position:0% both of us at the start of protocol and 00:59:49.630 --> 00:59:52.380 align:start position:0% both of us at the start of protocol and so<00:59:49.810> all<00:59:50.280> other<00:59:51.280> one<00:59:51.609> of<00:59:51.730> most<00:59:51.880> of<00:59:52.119> the<00:59:52.180> points 00:59:52.380 --> 00:59:52.390 align:start position:0% so all other one of most of the points 00:59:52.390 --> 00:59:55.620 align:start position:0% so all other one of most of the points the<00:59:52.990> circle<00:59:53.410> are<00:59:53.710> known<00:59:54.310> to<00:59:54.820> both<00:59:54.970> sides<00:59:55.329> at 00:59:55.620 --> 00:59:55.630 align:start position:0% the circle are known to both sides at 00:59:55.630 --> 01:00:02.849 align:start position:0% the circle are known to both sides at once<00:59:56.400> so<00:59:57.400> we<00:59:57.430> just<00:59:59.280> change<01:00:00.280> some<01:00:00.940> what<01:00:01.859> you 01:00:02.849 --> 01:00:02.859 align:start position:0% once so we just change some what you 01:00:02.859 --> 01:00:05.430 align:start position:0% once so we just change some what you want<01:00:03.210> with<01:00:04.210> such<01:00:04.390> property<01:00:04.900> that<01:00:05.050> the<01:00:05.200> bearer 01:00:05.430 --> 01:00:05.440 align:start position:0% want with such property that the bearer 01:00:05.440 --> 01:00:08.849 align:start position:0% want with such property that the bearer of<01:00:05.740> our<01:00:06.010> equal<01:00:06.820> number<01:00:07.150> is<01:00:08.020> different<01:00:08.349> from 01:00:08.849 --> 01:00:08.859 align:start position:0% of our equal number is different from 01:00:08.859 --> 01:00:12.270 align:start position:0% of our equal number is different from the<01:00:09.640> relevance<01:00:10.060> of<01:00:10.440> other<01:00:11.440> animals<01:00:11.920> in<01:00:12.130> this 01:00:12.270 --> 01:00:12.280 align:start position:0% the relevance of other animals in this 01:00:12.280 --> 01:00:21.930 align:start position:0% the relevance of other animals in this zone<01:00:17.970> and<01:00:18.970> this<01:00:19.150> will<01:00:19.359> be<01:00:19.540> 0<01:00:20.430> our<01:00:21.430> constraint 01:00:21.930 --> 01:00:21.940 align:start position:0% zone and this will be 0 our constraint 01:00:21.940 --> 01:00:30.510 align:start position:0% zone and this will be 0 our constraint phenomenal<01:00:23.640> and<01:00:24.640> also<01:00:25.390> just<01:00:25.859> 1/2<01:00:28.319> and<01:00:29.319> if<01:00:30.190> I 01:00:30.510 --> 01:00:30.520 align:start position:0% phenomenal and also just 1/2 and if I 01:00:30.520 --> 01:00:36.000 align:start position:0% phenomenal and also just 1/2 and if I want<01:00:30.940> such<01:00:31.270> a<01:00:31.300> poet<01:00:31.569> such<01:00:32.079> a<01:00:32.109> f0<01:00:32.980> of<01:00:33.460> my<01:00:33.670> one<01:00:35.010> if 01:00:36.000 --> 01:00:36.010 align:start position:0% want such a poet such a f0 of my one if 01:00:36.010 --> 01:00:41.120 align:start position:0% want such a poet such a f0 of my one if not<01:00:36.250> equal<01:00:36.490> to<01:00:36.790> Phi<01:00:37.119> Phi<01:00:37.690> 1<01:00:37.900> 4<01:00:38.680> 4<01:00:39.250> very<01:00:40.050> provide 01:00:41.120 --> 01:00:41.130 align:start position:0% not equal to Phi Phi 1 4 4 very provide 01:00:41.130 --> 01:00:44.670 align:start position:0% not equal to Phi Phi 1 4 4 very provide greater<01:00:42.130> we<01:00:42.339> hope<01:00:42.490> that<01:00:42.670> one<01:00:43.290> that<01:00:44.290> make<01:00:44.440> sense 01:00:44.670 --> 01:00:44.680 align:start position:0% greater we hope that one that make sense 01:00:44.680 --> 01:00:47.720 align:start position:0% greater we hope that one that make sense and<01:00:44.950> this<01:00:45.700> is<01:00:45.970> this<01:00:46.329> is<01:00:46.390> the<01:00:46.690> replacement<01:00:46.960> of 01:00:47.720 --> 01:00:47.730 align:start position:0% and this is this is the replacement of 01:00:47.730 --> 01:00:53.150 align:start position:0% and this is this is the replacement of the<01:00:48.730> search<01:00:48.940> of<01:00:49.150> such<01:00:49.359> a<01:00:49.390> rebel<01:00:49.630> said<01:00:50.250> sorry 01:00:53.150 --> 01:00:53.160 align:start position:0% the search of such a rebel said sorry 01:00:53.160 --> 01:00:57.870 align:start position:0% the search of such a rebel said sorry don't<01:00:54.160> resent<01:00:54.670> much<01:00:55.260> this<01:00:56.339> some<01:00:57.339> kind<01:00:57.609> of<01:00:57.670> just 01:00:57.870 --> 01:00:57.880 align:start position:0% don't resent much this some kind of just 01:00:57.880 --> 01:01:06.180 align:start position:0% don't resent much this some kind of just as<01:00:58.119> a<01:00:58.210> child<01:01:00.450> this<01:01:01.450> list<01:01:01.780> very<01:01:02.109> huge<01:01:05.190> decoding 01:01:06.180 --> 01:01:06.190 align:start position:0% as a child this list very huge decoding 01:01:06.190 --> 01:01:09.780 align:start position:0% as a child this list very huge decoding the<01:01:06.579> photos<01:01:07.420> of<01:01:07.569> animals<01:01:07.990> may<01:01:08.619> change<01:01:08.920> my 01:01:09.780 --> 01:01:09.790 align:start position:0% the photos of animals may change my 01:01:09.790 --> 01:01:12.809 align:start position:0% the photos of animals may change my amount<01:01:10.450> of<01:01:10.569> time<01:01:10.839> the<01:01:11.619> socialist<01:01:12.099> point<01:01:12.369> is 01:01:12.809 --> 01:01:12.819 align:start position:0% amount of time the socialist point is 01:01:12.819 --> 01:01:15.630 align:start position:0% amount of time the socialist point is also<01:01:13.089> a<01:01:13.270> Sun<01:01:13.660> God<01:01:13.839> but<01:01:14.829> this<01:01:14.950> is 01:01:15.630 --> 01:01:15.640 align:start position:0% also a Sun God but this is 01:01:15.640 --> 01:01:17.489 align:start position:0% also a Sun God but this is which<01:01:15.819> was<01:01:15.940> the<01:01:16.029> German<01:01:16.329> it<01:01:16.450> was<01:01:16.479> and<01:01:16.959> this<01:01:17.380> is 01:01:17.489 --> 01:01:17.499 align:start position:0% which was the German it was and this is 01:01:17.499 --> 01:01:19.829 align:start position:0% which was the German it was and this is food<01:01:17.680> just<01:01:17.979> as<01:01:18.160> a<01:01:18.190> child<01:01:18.509> and<01:01:19.509> there<01:01:19.599> was<01:01:19.690> no 01:01:19.829 --> 01:01:19.839 align:start position:0% food just as a child and there was no 01:01:19.839 --> 01:01:22.949 align:start position:0% food just as a child and there was no need<01:01:20.140> for<01:01:20.170> some<01:01:20.589> secret<01:01:21.009> parameters<01:01:21.959> as 01:01:22.949 --> 01:01:22.959 align:start position:0% need for some secret parameters as 01:01:22.959 --> 01:01:28.969 align:start position:0% need for some secret parameters as journal<01:01:23.380> in<01:01:23.529> kid<01:01:24.519> commitment<01:01:25.059> and<01:01:26.339> here<01:01:27.339> here 01:01:28.969 --> 01:01:28.979 align:start position:0% journal in kid commitment and here here 01:01:28.979 --> 01:01:33.390 align:start position:0% journal in kid commitment and here here he<01:01:29.979> previous<01:01:30.279> protocols<01:01:30.849> which<01:01:31.059> just<01:01:32.400> opening 01:01:33.390 --> 01:01:33.400 align:start position:0% he previous protocols which just opening 01:01:33.400 --> 01:01:38.989 align:start position:0% he previous protocols which just opening people<01:01:33.969> open<01:01:34.660> schemes<01:01:35.039> we<01:01:36.039> divide<01:01:36.369> by<01:01:37.319> just 01:01:38.989 --> 01:01:38.999 align:start position:0% people open schemes we divide by just 01:01:38.999 --> 01:01:43.650 align:start position:0% people open schemes we divide by just one<01:01:39.999> life<01:01:40.180> function<01:01:40.690> and<01:01:41.849> here<01:01:42.849> I<01:01:43.150> was<01:01:43.479> just 01:01:43.650 --> 01:01:43.660 align:start position:0% one life function and here I was just 01:01:43.660 --> 01:01:46.650 align:start position:0% one life function and here I was just the<01:01:44.349> point<01:01:44.559> which<01:01:44.979> okay<01:01:45.190> so<01:01:45.309> tell<01:01:45.489> face<01:01:45.700> and<01:01:46.150> I 01:01:46.650 --> 01:01:46.660 align:start position:0% the point which okay so tell face and I 01:01:46.660 --> 01:01:52.130 align:start position:0% the point which okay so tell face and I too<01:01:46.809> is<01:01:47.289> just<01:01:47.529> the<01:01:48.160> point<01:01:48.369> which<01:01:50.579> the<01:01:51.579> verifier 01:01:52.130 --> 01:01:52.140 align:start position:0% too is just the point which the verifier 01:01:52.140 --> 01:01:56.910 align:start position:0% too is just the point which the verifier is<01:01:53.140> not<01:01:53.440> open<01:01:53.920> the<01:01:54.400> very<01:01:54.579> edge<01:01:54.849> and<01:01:55.209> you<01:01:56.140> as<01:01:56.349> you 01:01:56.910 --> 01:01:56.920 align:start position:0% is not open the very edge and you as you 01:01:56.920 --> 01:01:59.969 align:start position:0% is not open the very edge and you as you us<01:01:57.609> is<01:01:57.880> a<01:01:57.910> function<01:01:58.390> that<01:01:58.420> just<01:01:59.140> interpolation 01:01:59.969 --> 01:01:59.979 align:start position:0% us is a function that just interpolation 01:01:59.979 --> 01:02:02.370 align:start position:0% us is a function that just interpolation but<01:02:00.849> wanted<01:02:01.239> to<01:02:01.299> publish<01:02:01.539> the<01:02:01.690> function<01:02:02.109> of 01:02:02.370 --> 01:02:02.380 align:start position:0% but wanted to publish the function of 01:02:02.380 --> 01:02:05.420 align:start position:0% but wanted to publish the function of those<01:02:02.559> points<01:02:03.599> with<01:02:04.599> respect<01:02:04.959> to<01:02:05.049> various 01:02:05.420 --> 01:02:05.430 align:start position:0% those points with respect to various 01:02:05.430 --> 01:02:09.839 align:start position:0% those points with respect to various that<01:02:06.430> one<01:02:06.930> NZ<01:02:07.930> to<01:02:08.109> once<01:02:08.920> again<01:02:09.039> the<01:02:09.459> chaplains 01:02:09.839 --> 01:02:09.849 align:start position:0% that one NZ to once again the chaplains 01:02:09.849 --> 01:02:16.559 align:start position:0% that one NZ to once again the chaplains the<01:02:10.719> weather<01:02:10.930> of<01:02:11.410> zero<01:02:11.769> at<01:02:12.809> seven<01:02:13.809> a<01:02:15.569> point 01:02:16.559 --> 01:02:16.569 align:start position:0% the weather of zero at seven a point 01:02:16.569 --> 01:02:19.680 align:start position:0% the weather of zero at seven a point which<01:02:16.809> we<01:02:16.959> try<01:02:17.140> to<01:02:17.200> open<01:02:17.469> and<01:02:18.420> develop<01:02:19.420> prior 01:02:19.680 --> 01:02:19.690 align:start position:0% which we try to open and develop prior 01:02:19.690 --> 01:02:23.099 align:start position:0% which we try to open and develop prior to<01:02:19.869> failure<01:02:19.989> of<01:02:20.259> opening<01:02:20.680> and<01:02:20.949> do<01:02:21.729> it<01:02:22.719> is<01:02:22.869> known 01:02:23.099 --> 01:02:23.109 align:start position:0% to failure of opening and do it is known 01:02:23.109 --> 01:02:25.279 align:start position:0% to failure of opening and do it is known a<01:02:23.140> difference<01:02:23.589> from<01:02:23.849> committee<01:02:24.849> from 01:02:25.279 --> 01:02:25.289 align:start position:0% a difference from committee from 01:02:25.289 --> 01:02:29.609 align:start position:0% a difference from committee from American<01:02:26.289> to<01:02:26.440> scheme<01:02:26.709> any<01:02:27.309> questions 01:02:29.609 --> 01:02:29.619 align:start position:0% American to scheme any questions 01:02:29.619 --> 01:02:32.519 align:start position:0% American to scheme any questions I<01:02:29.650> think<01:02:30.219> here<01:02:30.400> I<01:02:30.430> actually<01:02:31.199> summarized<01:02:32.199> it<01:02:32.410> a 01:02:32.519 --> 01:02:32.529 align:start position:0% I think here I actually summarized it a 01:02:32.529 --> 01:02:33.770 align:start position:0% I think here I actually summarized it a little<01:02:32.739> bit<01:02:32.890> differently 01:02:33.770 --> 01:02:33.780 align:start position:0% little bit differently 01:02:33.780 --> 01:02:36.890 align:start position:0% little bit differently so<01:02:34.520> it<01:02:35.520> also<01:02:35.730> counts<01:02:35.940> as<01:02:36.150> a<01:02:36.270> problem<01:02:36.600> of<01:02:36.750> the 01:02:36.890 --> 01:02:36.900 align:start position:0% so it also counts as a problem of the 01:02:36.900 --> 01:02:39.140 align:start position:0% so it also counts as a problem of the political<01:02:37.290> relationship<01:02:38.000> everyone<01:02:39.000> knows 01:02:39.140 --> 01:02:39.150 align:start position:0% political relationship everyone knows 01:02:39.150 --> 01:02:43.040 align:start position:0% political relationship everyone knows that<01:02:39.180> your<01:02:39.480> article<01:02:41.180> lemma<01:02:42.180> which<01:02:42.540> tells<01:02:42.840> them 01:02:43.040 --> 01:02:43.050 align:start position:0% that your article lemma which tells them 01:02:43.050 --> 01:02:45.470 align:start position:0% that your article lemma which tells them if<01:02:43.560> you<01:02:43.800> want<01:02:44.040> to<01:02:44.190> satisfy<01:02:44.400> relation<01:02:45.090> like<01:02:45.270> if 01:02:45.470 --> 01:02:45.480 align:start position:0% if you want to satisfy relation like if 01:02:45.480 --> 01:02:47.270 align:start position:0% if you want to satisfy relation like if you<01:02:45.630> care<01:02:45.930> for<01:02:45.960> their<01:02:46.410> own<01:02:46.590> a<01:02:46.740> certain<01:02:47.160> degree 01:02:47.270 --> 01:02:47.280 align:start position:0% you care for their own a certain degree 01:02:47.280 --> 01:02:50.060 align:start position:0% you care for their own a certain degree that<01:02:48.180> has<01:02:48.450> a<01:02:48.480> random<01:02:48.930> points<01:02:49.380> and<01:02:49.620> this<01:02:49.860> is<01:02:50.040> a 01:02:50.060 --> 01:02:50.070 align:start position:0% that has a random points and this is a 01:02:50.070 --> 01:02:51.920 align:start position:0% that has a random points and this is a great<01:02:50.430> word<01:02:50.760> as<01:02:50.970> around<01:02:51.240> the<01:02:51.360> point<01:02:51.630> a 01:02:51.920 --> 01:02:51.930 align:start position:0% great word as around the point a 01:02:51.930 --> 01:02:54.920 align:start position:0% great word as around the point a probabilities<01:02:52.740> and<01:02:52.950> people<01:02:53.370> have<01:02:53.670> a<01:02:53.930> people 01:02:54.920 --> 01:02:54.930 align:start position:0% probabilities and people have a people 01:02:54.930 --> 01:02:56.960 align:start position:0% probabilities and people have a people has<01:02:55.140> a<01:02:55.170> root<01:02:55.410> is<01:02:55.800> negligible<01:02:56.460> in<01:02:56.670> a<01:02:56.760> large 01:02:56.960 --> 01:02:56.970 align:start position:0% has a root is negligible in a large 01:02:56.970 --> 01:02:58.730 align:start position:0% has a root is negligible in a large amount<01:02:57.270> you<01:02:57.390> like<01:02:57.720> as<01:02:57.930> a<01:02:57.960> fancy<01:02:58.290> price<01:02:58.530> right 01:02:58.730 --> 01:02:58.740 align:start position:0% amount you like as a fancy price right 01:02:58.740 --> 01:03:01.370 align:start position:0% amount you like as a fancy price right just<01:02:59.550> approve<01:02:59.820> because<01:02:59.970> this<01:03:00.840> particles 01:03:01.370 --> 01:03:01.380 align:start position:0% just approve because this particles 01:03:01.380 --> 01:03:02.720 align:start position:0% just approve because this particles exist<01:03:01.710> yeah 01:03:02.720 --> 01:03:02.730 align:start position:0% exist yeah 01:03:02.730 --> 01:03:07.900 align:start position:0% exist yeah so<01:03:03.180> well<01:03:03.660> in<01:03:03.840> principle<01:03:04.020> if<01:03:04.380> you<01:03:04.470> go<01:03:04.620> back<01:03:04.860> to 01:03:07.900 --> 01:03:07.910 align:start position:0% 01:03:07.910 --> 01:03:13.420 align:start position:0% go<01:03:08.910> all<01:03:09.270> the<01:03:09.300> way<01:03:09.570> back<01:03:09.840> to<01:03:10.230> the<01:03:11.090> start 01:03:13.420 --> 01:03:13.430 align:start position:0% go all the way back to the start 01:03:13.430 --> 01:03:17.000 align:start position:0% go all the way back to the start principle<01:03:14.430> let's<01:03:14.580> say<01:03:14.700> we<01:03:14.850> can<01:03:15.590> heavily<01:03:16.590> this 01:03:17.000 --> 01:03:17.010 align:start position:0% principle let's say we can heavily this 01:03:17.010 --> 01:03:18.590 align:start position:0% principle let's say we can heavily this is<01:03:17.190> deep<01:03:17.370> a<01:03:17.460> life<01:03:17.610> particle<01:03:17.940> which<01:03:18.210> we<01:03:18.330> didn't 01:03:18.590 --> 01:03:18.600 align:start position:0% is deep a life particle which we didn't 01:03:18.600 --> 01:03:20.000 align:start position:0% is deep a life particle which we didn't cover<01:03:18.780> but<01:03:19.020> there<01:03:19.140> is<01:03:19.260> away<01:03:19.440> from<01:03:19.680> beginning 01:03:20.000 --> 01:03:20.010 align:start position:0% cover but there is away from beginning 01:03:20.010 --> 01:03:22.120 align:start position:0% cover but there is away from beginning to<01:03:20.460> sleaze<01:03:20.670> check<01:03:20.910> is<01:03:21.030> around<01:03:21.270> employ<01:03:21.570> and 01:03:22.120 --> 01:03:22.130 align:start position:0% to sleaze check is around employ and 01:03:22.130 --> 01:03:25.670 align:start position:0% to sleaze check is around employ and share<01:03:23.130> you<01:03:23.340> Curia<01:03:24.330> good<01:03:24.690> I<01:03:24.870> mean<01:03:25.140> his<01:03:25.410> around 01:03:25.670 --> 01:03:25.680 align:start position:0% share you Curia good I mean his around 01:03:25.680 --> 01:03:27.770 align:start position:0% share you Curia good I mean his around the<01:03:25.770> points<01:03:26.040> everything<01:03:26.880> here<01:03:27.180> you<01:03:27.210> knows<01:03:27.570> the 01:03:27.770 --> 01:03:27.780 align:start position:0% the points everything here you knows the 01:03:27.780 --> 01:03:30.980 align:start position:0% the points everything here you knows the degrees<01:03:28.110> out<01:03:28.290> front<01:03:29.210> so<01:03:30.210> you<01:03:30.300> can<01:03:30.450> just<01:03:30.630> check 01:03:30.980 --> 01:03:30.990 align:start position:0% degrees out front so you can just check 01:03:30.990 --> 01:03:33.560 align:start position:0% degrees out front so you can just check and<01:03:31.230> guess<01:03:31.410> so<01:03:32.160> you<01:03:32.580> can<01:03:32.730> make<01:03:32.940> the<01:03:33.120> check<01:03:33.330> this 01:03:33.560 --> 01:03:33.570 align:start position:0% and guess so you can make the check this 01:03:33.570 --> 01:03:35.870 align:start position:0% and guess so you can make the check this enormous<01:03:33.990> soundness<01:03:34.500> and<01:03:34.770> to<01:03:35.400> bring<01:03:35.580> a<01:03:35.670> small 01:03:35.870 --> 01:03:35.880 align:start position:0% enormous soundness and to bring a small 01:03:35.880 --> 01:03:37.490 align:start position:0% enormous soundness and to bring a small price<01:03:36.120> if<01:03:36.420> you<01:03:36.510> do<01:03:36.630> it<01:03:36.750> mess<01:03:36.900> around<01:03:37.020> the<01:03:37.260> point 01:03:37.490 --> 01:03:37.500 align:start position:0% price if you do it mess around the point 01:03:37.500 --> 01:03:40.550 align:start position:0% price if you do it mess around the point let's<01:03:37.680> go<01:03:37.770> and<01:03:38.130> you<01:03:38.280> can<01:03:38.460> do<01:03:38.610> this<01:03:39.200> the<01:03:40.200> problem 01:03:40.550 --> 01:03:40.560 align:start position:0% let's go and you can do this the problem 01:03:40.560 --> 01:03:45.740 align:start position:0% let's go and you can do this the problem is<01:03:40.800> as<01:03:41.070> Costa<01:03:41.550> says<01:03:42.170> we<01:03:43.170> worked<01:03:43.440> was<01:03:44.600> in<01:03:45.600> the 01:03:45.740 --> 01:03:45.750 align:start position:0% is as Costa says we worked was in the 01:03:45.750 --> 01:03:48.470 align:start position:0% is as Costa says we worked was in the frying<01:03:46.020> pan<01:03:46.170> dulce<01:03:46.440> parameter<01:03:46.980> Delta<01:03:47.340> and<01:03:47.610> if 01:03:48.470 --> 01:03:48.480 align:start position:0% frying pan dulce parameter Delta and if 01:03:48.480 --> 01:03:50.210 align:start position:0% frying pan dulce parameter Delta and if you<01:03:48.600> help<01:03:48.810> a<01:03:48.930> small<01:03:48.990> you<01:03:49.350> prove<01:03:49.590> sizes<01:03:50.010> large 01:03:50.210 --> 01:03:50.220 align:start position:0% you help a small you prove sizes large 01:03:50.220 --> 01:03:53.270 align:start position:0% you help a small you prove sizes large if<01:03:50.790> you<01:03:50.940> did<01:03:51.150> building<01:03:51.690> is<01:03:51.810> larger<01:03:52.290> for<01:03:52.590> a<01:03:53.040> same 01:03:53.270 --> 01:03:53.280 align:start position:0% if you did building is larger for a same 01:03:53.280 --> 01:03:55.370 align:start position:0% if you did building is larger for a same summer<01:03:53.550> your<01:03:54.150> first<01:03:54.360> size<01:03:54.540> is<01:03:54.690> smaller<01:03:54.960> assume 01:03:55.370 --> 01:03:55.380 align:start position:0% summer your first size is smaller assume 01:03:55.380 --> 01:03:57.350 align:start position:0% summer your first size is smaller assume really<01:03:56.100> want<01:03:56.280> to<01:03:56.400> work<01:03:56.580> with<01:03:56.610> a<01:03:56.790> large<01:03:57.030> Delta 01:03:57.350 --> 01:03:57.360 align:start position:0% really want to work with a large Delta 01:03:57.360 --> 01:04:00.200 align:start position:0% really want to work with a large Delta in<01:03:58.260> starts<01:03:58.680> it's<01:03:58.860> not<01:03:58.890> the<01:03:59.100> problem<01:03:59.460> you<01:03:59.880> take 01:04:00.200 --> 01:04:00.210 align:start position:0% in starts it's not the problem you take 01:04:00.210 --> 01:04:02.630 align:start position:0% in starts it's not the problem you take a<01:04:00.270> large<01:04:00.600> now<01:04:00.930> life<01:04:01.350> you<01:04:01.500> got<01:04:01.650> that<01:04:01.830> right 01:04:02.630 --> 01:04:02.640 align:start position:0% a large now life you got that right 01:04:02.640 --> 01:04:04.880 align:start position:0% a large now life you got that right there<01:04:03.030> was<01:04:03.210> some<01:04:03.390> lubrication<01:04:03.810> exited<01:04:04.470> that's 01:04:04.880 --> 01:04:04.890 align:start position:0% there was some lubrication exited that's 01:04:04.890 --> 01:04:07.640 align:start position:0% there was some lubrication exited that's given<01:04:05.280> you<01:04:06.120> take<01:04:06.300> large<01:04:06.510> Delta<01:04:07.020> so<01:04:07.380> you<01:04:07.470> can 01:04:07.640 --> 01:04:07.650 align:start position:0% given you take large Delta so you can 01:04:07.650 --> 01:04:11.060 align:start position:0% given you take large Delta so you can see<01:04:07.830> you<01:04:08.400> have<01:04:08.430> this<01:04:08.730> intersection<01:04:10.040> to<01:04:11.040> the 01:04:11.060 --> 01:04:11.070 align:start position:0% see you have this intersection to the 01:04:11.070 --> 01:04:14.060 align:start position:0% see you have this intersection to the principal<01:04:11.640> as<01:04:11.880> a<01:04:12.660> random<01:04:13.110> point<01:04:13.320> you<01:04:13.920> can 01:04:14.060 --> 01:04:14.070 align:start position:0% principal as a random point you can 01:04:14.070 --> 01:04:16.490 align:start position:0% principal as a random point you can actually<01:04:14.340> take<01:04:15.270> any<01:04:15.600> of<01:04:15.840> those<01:04:16.050> polynomials 01:04:16.490 --> 01:04:16.500 align:start position:0% actually take any of those polynomials 01:04:16.500 --> 01:04:19.460 align:start position:0% actually take any of those polynomials and<01:04:16.950> pull<01:04:17.430> the<01:04:17.610> volume<01:04:17.760> for<01:04:18.450> this<01:04:18.690> one<01:04:19.290> of 01:04:19.460 --> 01:04:19.470 align:start position:0% and pull the volume for this one of 01:04:19.470 --> 01:04:21.740 align:start position:0% and pull the volume for this one of those<01:04:19.650> as<01:04:19.920> a<01:04:19.980> random<01:04:20.370> point<01:04:20.550> and<01:04:21.270> you<01:04:21.420> can<01:04:21.600> do 01:04:21.740 --> 01:04:21.750 align:start position:0% those as a random point and you can do 01:04:21.750 --> 01:04:24.050 align:start position:0% those as a random point and you can do it<01:04:21.870> for<01:04:22.280> everything<01:04:23.280> becomes<01:04:23.790> with<01:04:23.970> this 01:04:24.050 --> 01:04:24.060 align:start position:0% it for everything becomes with this 01:04:24.060 --> 01:04:26.420 align:start position:0% it for everything becomes with this equation<01:04:24.570> well<01:04:25.020> up<01:04:25.500> to<01:04:25.740> something<01:04:26.100> certain 01:04:26.420 --> 01:04:26.430 align:start position:0% equation well up to something certain 01:04:26.430 --> 01:04:30.470 align:start position:0% equation well up to something certain example<01:04:26.910> and<01:04:27.950> the<01:04:28.950> best<01:04:29.130> is<01:04:29.310> how<01:04:30.030> we<01:04:30.090> can 01:04:30.470 --> 01:04:30.480 align:start position:0% example and the best is how we can 01:04:30.480 --> 01:04:33.410 align:start position:0% example and the best is how we can satisfy<01:04:30.810> this<01:04:31.680> equation<01:04:32.070> at<01:04:32.490> a<01:04:32.670> random<01:04:33.060> point 01:04:33.410 --> 01:04:33.420 align:start position:0% satisfy this equation at a random point 01:04:33.420 --> 01:04:35.910 align:start position:0% satisfy this equation at a random point as<01:04:33.690> well<01:04:34.620> from<01:04:34.890> a<01:04:35.070> polynomial 01:04:35.910 --> 01:04:35.920 align:start position:0% as well from a polynomial 01:04:35.920 --> 01:04:38.819 align:start position:0% as well from a polynomial have<01:04:36.099> this<01:04:36.880> oceans<01:04:37.450> is<01:04:37.779> around<01:04:38.109> the<01:04:38.170> point<01:04:38.410> for 01:04:38.819 --> 01:04:38.829 align:start position:0% have this oceans is around the point for 01:04:38.829 --> 01:04:40.440 align:start position:0% have this oceans is around the point for another<01:04:38.980> one<01:04:39.220> you<01:04:39.309> have<01:04:39.460> this<01:04:39.609> option<01:04:39.849> like 01:04:40.440 --> 01:04:40.450 align:start position:0% another one you have this option like 01:04:40.450 --> 01:04:43.829 align:start position:0% another one you have this option like this<01:04:40.720> setup<01:04:41.230> options<01:04:41.740> and<01:04:42.279> you<01:04:42.730> can<01:04:42.839> pretty 01:04:43.829 --> 01:04:43.839 align:start position:0% this setup options and you can pretty 01:04:43.839 --> 01:04:46.620 align:start position:0% this setup options and you can pretty simply<01:04:44.349> gets<01:04:44.650> some<01:04:45.279> espera<01:04:45.730> persistence<01:04:46.390> like 01:04:46.620 --> 01:04:46.630 align:start position:0% simply gets some espera persistence like 01:04:46.630 --> 01:04:49.789 align:start position:0% simply gets some espera persistence like it<01:04:47.019> will<01:04:47.200> depend<01:04:47.529> on<01:04:47.680> another<01:04:48.059> average<01:04:49.059> size 01:04:49.789 --> 01:04:49.799 align:start position:0% it will depend on another average size 01:04:49.799 --> 01:04:52.289 align:start position:0% it will depend on another average size for<01:04:50.799> each<01:04:51.010> volunteer<01:04:51.250> know<01:04:51.519> like<01:04:51.789> how<01:04:52.240> many 01:04:52.289 --> 01:04:52.299 align:start position:0% for each volunteer know like how many 01:04:52.299 --> 01:04:54.630 align:start position:0% for each volunteer know like how many others<01:04:52.750> you<01:04:52.779> can<01:04:53.019> feed<01:04:53.400> from<01:04:54.400> these 01:04:54.630 --> 01:04:54.640 align:start position:0% others you can feed from these 01:04:54.640 --> 01:04:56.309 align:start position:0% others you can feed from these intersections<01:04:55.329> and<01:04:55.510> the<01:04:55.990> number<01:04:56.230> of 01:04:56.309 --> 01:04:56.319 align:start position:0% intersections and the number of 01:04:56.319 --> 01:04:58.680 align:start position:0% intersections and the number of polynomials<01:04:56.829> /<01:04:57.400> fuel<01:04:57.640> size<01:04:57.880> this<01:04:58.329> is<01:04:58.390> very 01:04:58.680 --> 01:04:58.690 align:start position:0% polynomials / fuel size this is very 01:04:58.690 --> 01:05:00.240 align:start position:0% polynomials / fuel size this is very simple<01:04:59.019> but<01:04:59.109> it's<01:04:59.349> dark<01:04:59.589> it<01:04:59.740> doesn't<01:04:59.769> matter 01:05:00.240 --> 01:05:00.250 align:start position:0% simple but it's dark it doesn't matter 01:05:00.250 --> 01:05:04.620 align:start position:0% simple but it's dark it doesn't matter because<01:05:02.369> even<01:05:03.369> while<01:05:03.579> we<01:05:03.730> pulled<01:05:04.150> all<01:05:04.420> those 01:05:04.620 --> 01:05:04.630 align:start position:0% because even while we pulled all those 01:05:04.630 --> 01:05:06.779 align:start position:0% because even while we pulled all those volumes<01:05:04.960> you<01:05:05.380> actually<01:05:05.890> set<01:05:06.069> this<01:05:06.160> by<01:05:06.369> every 01:05:06.779 --> 01:05:06.789 align:start position:0% volumes you actually set this by every 01:05:06.789 --> 01:05:10.140 align:start position:0% volumes you actually set this by every constraint<01:05:07.150> biggest<01:05:08.140> constraints<01:05:08.799> known<01:05:09.789> is 01:05:10.140 --> 01:05:10.150 align:start position:0% constraint biggest constraints known is 01:05:10.150 --> 01:05:13.079 align:start position:0% constraint biggest constraints known is a<01:05:10.180> very<01:05:10.809> fire<01:05:11.049> as<01:05:11.260> a<01:05:11.289> set<01:05:11.559> up<01:05:11.680> space<01:05:11.890> so<01:05:12.220> in 01:05:13.079 --> 01:05:13.089 align:start position:0% a very fire as a set up space so in 01:05:13.089 --> 01:05:15.690 align:start position:0% a very fire as a set up space so in start<01:05:13.539> a<01:05:13.690> fire<01:05:14.130> literally<01:05:15.130> check<01:05:15.400> having 01:05:15.690 --> 01:05:15.700 align:start position:0% start a fire literally check having 01:05:15.700 --> 01:05:19.650 align:start position:0% start a fire literally check having expanded<01:05:16.000> this<01:05:16.990> is<01:05:17.880> quite<01:05:18.880> hard<01:05:19.119> to<01:05:19.210> mutations 01:05:19.650 --> 01:05:19.660 align:start position:0% expanded this is quite hard to mutations 01:05:19.660 --> 01:05:21.720 align:start position:0% expanded this is quite hard to mutations my<01:05:19.779> kept<01:05:20.049> optimizing<01:05:20.589> constraints<01:05:21.039> capture 01:05:21.720 --> 01:05:21.730 align:start position:0% my kept optimizing constraints capture 01:05:21.730 --> 01:05:26.880 align:start position:0% my kept optimizing constraints capture chasm<01:05:22.089> efficiently<01:05:22.690> computable<01:05:23.079> in<01:05:25.890> narcs 01:05:26.880 --> 01:05:26.890 align:start position:0% chasm efficiently computable in narcs 01:05:26.890 --> 01:05:29.789 align:start position:0% chasm efficiently computable in narcs which<01:05:27.250> don't<01:05:27.670> work<01:05:27.760> was<01:05:28.420> layered<01:05:29.109> circuits 01:05:29.789 --> 01:05:29.799 align:start position:0% which don't work was layered circuits 01:05:29.799 --> 01:05:32.490 align:start position:0% which don't work was layered circuits like<01:05:30.059> Ross<01:05:31.059> 16<01:05:31.599> everything<01:05:32.170> missions<01:05:32.410> of 01:05:32.490 --> 01:05:32.500 align:start position:0% like Ross 16 everything missions of 01:05:32.500 --> 01:05:35.700 align:start position:0% like Ross 16 everything missions of Parowan<01:05:32.920> CS<01:05:34.049> plonk<01:05:35.049> with<01:05:35.289> an<01:05:35.410> us<01:05:35.529> organization 01:05:35.700 --> 01:05:35.710 align:start position:0% Parowan CS plonk with an us organization 01:05:35.710 --> 01:05:38.400 align:start position:0% Parowan CS plonk with an us organization sonic<01:05:36.579> is<01:05:36.670> an<01:05:36.789> us<01:05:36.910> organization<01:05:37.119> your<01:05:38.109> APIs 01:05:38.400 --> 01:05:38.410 align:start position:0% sonic is an us organization your APIs 01:05:38.410 --> 01:05:40.200 align:start position:0% sonic is an us organization your APIs are<01:05:38.529> be<01:05:38.650> three<01:05:38.829> circuits<01:05:39.220> so<01:05:39.789> you<01:05:39.880> have<01:05:40.059> to 01:05:40.200 --> 01:05:40.210 align:start position:0% are be three circuits so you have to 01:05:40.210 --> 01:05:42.180 align:start position:0% are be three circuits so you have to encode<01:05:40.390> your<01:05:40.450> problems<01:05:41.259> a<01:05:41.410> cow<01:05:41.619> becomes<01:05:42.039> if 01:05:42.180 --> 01:05:42.190 align:start position:0% encode your problems a cow becomes if 01:05:42.190 --> 01:05:44.730 align:start position:0% encode your problems a cow becomes if you're<01:05:42.339> a<01:05:42.549> fire<01:05:42.819> otherwise<01:05:43.359> very<01:05:43.750> fire<01:05:44.049> to<01:05:44.619> do 01:05:44.730 --> 01:05:44.740 align:start position:0% you're a fire otherwise very fire to do 01:05:44.740 --> 01:05:46.799 align:start position:0% you're a fire otherwise very fire to do so<01:05:44.799> safely<01:05:45.099> apply<01:05:45.789> because<01:05:46.119> paint<01:05:46.539> which<01:05:46.779> is 01:05:46.799 --> 01:05:46.809 align:start position:0% so safely apply because paint which is 01:05:46.809 --> 01:05:48.930 align:start position:0% so safely apply because paint which is when<01:05:47.079> you're<01:05:47.230> working<01:05:47.380> or<01:05:48.039> adjustable<01:05:48.460> a<01:05:48.640> temp 01:05:48.930 --> 01:05:48.940 align:start position:0% when you're working or adjustable a temp 01:05:48.940 --> 01:05:50.400 align:start position:0% when you're working or adjustable a temp large<01:05:49.180> degree<01:05:49.359> collateral<01:05:49.960> which<01:05:50.109> is<01:05:50.230> still 01:05:50.400 --> 01:05:50.410 align:start position:0% large degree collateral which is still 01:05:50.410 --> 01:05:54.390 align:start position:0% large degree collateral which is still with<01:05:50.529> your<01:05:50.619> work<01:05:50.859> but<01:05:51.690> if<01:05:52.690> we<01:05:52.839> do<01:05:52.960> it<01:05:53.049> namely<01:05:53.500> we 01:05:54.390 --> 01:05:54.400 align:start position:0% with your work but if we do it namely we 01:05:54.400 --> 01:05:57.269 align:start position:0% with your work but if we do it namely we cannot<01:05:54.670> use<01:05:54.940> this<01:05:55.240> just<01:05:55.930> mainly<01:05:56.200> use<01:05:56.589> this<01:05:57.009> kit 01:05:57.269 --> 01:05:57.279 align:start position:0% cannot use this just mainly use this kit 01:05:57.279 --> 01:05:59.490 align:start position:0% cannot use this just mainly use this kit for<01:05:57.670> constraining<01:05:58.480> polynomials<01:05:59.019> because 01:05:59.490 --> 01:05:59.500 align:start position:0% for constraining polynomials because 01:05:59.500 --> 01:06:01.380 align:start position:0% for constraining polynomials because they're<01:05:59.829> different<01:06:00.039> so<01:06:00.400> your<01:06:00.519> content<01:06:00.789> and<01:06:01.150> if 01:06:01.380 --> 01:06:01.390 align:start position:0% they're different so your content and if 01:06:01.390 --> 01:06:04.049 align:start position:0% they're different so your content and if you<01:06:01.509> allow<01:06:01.809> these<01:06:02.019> kids<01:06:02.319> in<01:06:03.009> principle<01:06:03.759> let's 01:06:04.049 --> 01:06:04.059 align:start position:0% you allow these kids in principle let's 01:06:04.059 --> 01:06:06.529 align:start position:0% you allow these kids in principle let's say<01:06:04.210> one<01:06:04.420> of<01:06:04.450> those<01:06:04.630> points 01:06:06.529 --> 01:06:06.539 align:start position:0% say one of those points 01:06:06.539 --> 01:06:09.470 align:start position:0% say one of those points but<01:06:06.930> nothing<01:06:07.260> stops<01:06:07.619> the<01:06:08.519> prober<01:06:08.910> delicious 01:06:09.470 --> 01:06:09.480 align:start position:0% but nothing stops the prober delicious 01:06:09.480 --> 01:06:11.660 align:start position:0% but nothing stops the prober delicious burger<01:06:09.809> from<01:06:10.470> competing<01:06:11.069> all<01:06:11.400> other 01:06:11.660 --> 01:06:11.670 align:start position:0% burger from competing all other 01:06:11.670 --> 01:06:14.089 align:start position:0% burger from competing all other constraint<01:06:12.240> pull<01:06:12.390> animals<01:06:12.779> and<01:06:13.019> make<01:06:13.680> you<01:06:13.890> for 01:06:14.089 --> 01:06:14.099 align:start position:0% constraint pull animals and make you for 01:06:14.099 --> 01:06:17.150 align:start position:0% constraint pull animals and make you for one<01:06:14.309> of<01:06:14.339> those<01:06:14.839> actual<01:06:15.839> witness<01:06:16.319> for<01:06:17.130> a 01:06:17.150 --> 01:06:17.160 align:start position:0% one of those actual witness for a 01:06:17.160 --> 01:06:19.880 align:start position:0% one of those actual witness for a solution<01:06:17.519> is<01:06:18.059> trivial<01:06:18.510> it<01:06:18.720> just<01:06:19.710> settles 01:06:19.880 --> 01:06:19.890 align:start position:0% solution is trivial it just settles 01:06:19.890 --> 01:06:21.650 align:start position:0% solution is trivial it just settles there<01:06:20.130> so<01:06:20.339> you<01:06:20.430> cannot<01:06:20.700> stop<01:06:20.940> this<01:06:21.119> you<01:06:21.480> cannot 01:06:21.650 --> 01:06:21.660 align:start position:0% there so you cannot stop this you cannot 01:06:21.660 --> 01:06:24.799 align:start position:0% there so you cannot stop this you cannot predict<01:06:22.079> it<01:06:22.200> up<01:06:22.319> front<01:06:22.500> so<01:06:23.369> in<01:06:23.700> my<01:06:24.119> commitment 01:06:24.799 --> 01:06:24.809 align:start position:0% predict it up front so in my commitment 01:06:24.809 --> 01:06:27.859 align:start position:0% predict it up front so in my commitment schema<01:06:25.140> can<01:06:25.230> only<01:06:25.410> allow<01:06:25.650> this<01:06:25.890> case<01:06:26.869> because 01:06:27.859 --> 01:06:27.869 align:start position:0% schema can only allow this case because 01:06:27.869 --> 01:06:31.940 align:start position:0% schema can only allow this case because you<01:06:28.289> cannot<01:06:29.150> allow<01:06:30.150> the<01:06:30.210> prover<01:06:30.839> to<01:06:31.049> she<01:06:31.559> was 01:06:31.940 --> 01:06:31.950 align:start position:0% you cannot allow the prover to she was 01:06:31.950 --> 01:06:35.089 align:start position:0% you cannot allow the prover to she was just<01:06:32.579> not<01:06:33.200> peeking<01:06:34.200> from<01:06:34.500> some<01:06:34.859> set<01:06:35.069> of 01:06:35.089 --> 01:06:35.099 align:start position:0% just not peeking from some set of 01:06:35.099 --> 01:06:36.710 align:start position:0% just not peeking from some set of Wally's<01:06:35.519> but<01:06:35.849> actually<01:06:36.119> to<01:06:36.240> begin<01:06:36.390> another 01:06:36.710 --> 01:06:36.720 align:start position:0% Wally's but actually to begin another 01:06:36.720 --> 01:06:39.890 align:start position:0% Wally's but actually to begin another problem<01:06:37.130> so<01:06:38.130> for<01:06:38.279> a<01:06:38.339> commitment<01:06:38.609> scheme<01:06:38.970> may 01:06:39.890 --> 01:06:39.900 align:start position:0% problem so for a commitment scheme may 01:06:39.900 --> 01:06:42.230 align:start position:0% problem so for a commitment scheme may you<01:06:39.960> apply<01:06:40.470> it<01:06:40.529> you<01:06:40.829> would<01:06:41.549> have<01:06:41.579> to<01:06:41.789> limit<01:06:42.119> the 01:06:42.230 --> 01:06:42.240 align:start position:0% you apply it you would have to limit the 01:06:42.240 --> 01:06:44.029 align:start position:0% you apply it you would have to limit the Delta<01:06:42.539> to<01:06:42.690> this<01:06:42.839> case<01:06:43.049> and<01:06:43.289> this<01:06:43.650> Delta<01:06:43.980> is 01:06:44.029 --> 01:06:44.039 align:start position:0% Delta to this case and this Delta is 01:06:44.039 --> 01:06:46.009 align:start position:0% Delta to this case and this Delta is equal<01:06:44.190> to<01:06:44.400> roughly<01:06:45.210> one-half<01:06:45.779> minus 01:06:46.009 --> 01:06:46.019 align:start position:0% equal to roughly one-half minus 01:06:46.019 --> 01:06:50.390 align:start position:0% equal to roughly one-half minus something<01:06:47.390> this<01:06:48.390> is<01:06:48.569> not<01:06:48.720> too<01:06:48.960> large<01:06:49.230> its<01:06:50.220> own 01:06:50.390 --> 01:06:50.400 align:start position:0% something this is not too large its own 01:06:50.400 --> 01:06:53.269 align:start position:0% something this is not too large its own us<01:06:51.109> first<01:06:52.109> some<01:06:52.440> certain<01:06:52.799> sounds<01:06:53.160> your 01:06:53.269 --> 01:06:53.279 align:start position:0% us first some certain sounds your 01:06:53.279 --> 01:06:55.099 align:start position:0% us first some certain sounds your process<01:06:53.579> would<01:06:53.819> be<01:06:53.940> larger<01:06:54.299> than<01:06:54.569> if<01:06:54.990> you 01:06:55.099 --> 01:06:55.109 align:start position:0% process would be larger than if you 01:06:55.109 --> 01:06:57.230 align:start position:0% process would be larger than if you would<01:06:55.260> allow<01:06:55.380> predicate<01:06:55.859> so<01:06:56.519> now<01:06:56.700> we<01:06:56.760> have<01:06:57.089> to 01:06:57.230 --> 01:06:57.240 align:start position:0% would allow predicate so now we have to 01:06:57.240 --> 01:07:01.460 align:start position:0% would allow predicate so now we have to eliminate<01:06:58.430> well<01:06:59.430> now<01:06:59.700> we<01:06:59.760> want<01:07:00.359> to<01:07:00.510> try<01:07:00.750> to<01:07:00.779> to 01:07:01.460 --> 01:07:01.470 align:start position:0% eliminate well now we want to try to to 01:07:01.470 --> 01:07:03.620 align:start position:0% eliminate well now we want to try to to increase<01:07:01.920> the<01:07:02.039> Delta<01:07:02.339> so<01:07:02.910> let's<01:07:03.180> say<01:07:03.390> we<01:07:03.569> need 01:07:03.620 --> 01:07:03.630 align:start position:0% increase the Delta so let's say we need 01:07:03.630 --> 01:07:06.349 align:start position:0% increase the Delta so let's say we need to<01:07:03.809> work<01:07:03.960> with<01:07:03.990> this<01:07:04.319> case<01:07:04.559> we<01:07:05.190> need<01:07:05.339> some<01:07:05.609> kind 01:07:06.349 --> 01:07:06.359 align:start position:0% to work with this case we need some kind 01:07:06.359 --> 01:07:09.049 align:start position:0% to work with this case we need some kind of<01:07:06.450> second<01:07:06.869> chapter<01:07:07.279> in<01:07:08.279> this<01:07:08.490> case<01:07:08.789> which 01:07:09.049 --> 01:07:09.059 align:start position:0% of second chapter in this case which 01:07:09.059 --> 01:07:16.269 align:start position:0% of second chapter in this case which says<01:07:09.269> it<01:07:10.130> go<01:07:11.130> back<01:07:11.309> on<01:07:11.460> distinguishing 01:07:16.269 --> 01:07:16.279 align:start position:0% 01:07:16.279 --> 01:07:19.640 align:start position:0% well<01:07:17.279> in<01:07:17.460> this<01:07:17.579> case<01:07:17.759> we<01:07:18.109> what<01:07:19.109> we<01:07:19.289> have<01:07:19.440> to<01:07:19.559> do 01:07:19.640 --> 01:07:19.650 align:start position:0% well in this case we what we have to do 01:07:19.650 --> 01:07:22.579 align:start position:0% well in this case we what we have to do is<01:07:19.769> we<01:07:20.069> need<01:07:20.250> to<01:07:20.309> second<01:07:21.119> boundary<01:07:21.390> so<01:07:22.259> with 01:07:22.579 --> 01:07:22.589 align:start position:0% is we need to second boundary so with 01:07:22.589 --> 01:07:24.019 align:start position:0% is we need to second boundary so with those<01:07:22.680> our<01:07:22.859> second<01:07:23.190> one<01:07:23.309> there<01:07:23.490> is<01:07:23.579> a<01:07:23.609> set<01:07:23.910> up 01:07:24.019 --> 01:07:24.029 align:start position:0% those our second one there is a set up 01:07:24.029 --> 01:07:26.930 align:start position:0% those our second one there is a set up as<01:07:24.450> satellite<01:07:25.019> in<01:07:26.009> principle<01:07:26.490> since<01:07:26.819> the 01:07:26.930 --> 01:07:26.940 align:start position:0% as satellite in principle since the 01:07:26.940 --> 01:07:28.519 align:start position:0% as satellite in principle since the problem<01:07:27.150> is<01:07:27.299> nobody<01:07:27.480> was<01:07:27.779> prepared<01:07:27.990> the<01:07:28.349> great 01:07:28.519 --> 01:07:28.529 align:start position:0% problem is nobody was prepared the great 01:07:28.529 --> 01:07:31.910 align:start position:0% problem is nobody was prepared the great fire<01:07:29.420> weekend<01:07:30.420> highs<01:07:30.630> reduces<01:07:31.140> three<01:07:31.440> with 01:07:31.910 --> 01:07:31.920 align:start position:0% fire weekend highs reduces three with 01:07:31.920 --> 01:07:34.759 align:start position:0% fire weekend highs reduces three with completing<01:07:32.430> all<01:07:32.789> of<01:07:32.819> those<01:07:33.289> full<01:07:34.289> animals 01:07:34.759 --> 01:07:34.769 align:start position:0% completing all of those full animals 01:07:34.769 --> 01:07:36.950 align:start position:0% completing all of those full animals which<01:07:35.099> are<01:07:35.279> its<01:07:35.519> intersection<01:07:36.089> and<01:07:36.480> like 01:07:36.950 --> 01:07:36.960 align:start position:0% which are its intersection and like 01:07:36.960 --> 01:07:39.230 align:start position:0% which are its intersection and like begins<01:07:37.769> a<01:07:37.859> wall<01:07:38.069> is<01:07:38.400> a<01:07:38.519> wall<01:07:38.549> unit<01:07:38.880> field 01:07:39.230 --> 01:07:39.240 align:start position:0% begins a wall is a wall unit field 01:07:39.240 --> 01:07:40.910 align:start position:0% begins a wall is a wall unit field whereas<01:07:39.750> they're<01:07:39.869> all<01:07:40.079> different<01:07:40.440> so<01:07:40.619> we<01:07:40.740> can 01:07:40.910 --> 01:07:40.920 align:start position:0% whereas they're all different so we can 01:07:40.920 --> 01:07:44.660 align:start position:0% whereas they're all different so we can use<01:07:41.430> this<01:07:42.140> in<01:07:43.140> reality<01:07:43.470> we<01:07:44.069> will<01:07:44.220> not<01:07:44.369> with<01:07:44.519> us 01:07:44.660 --> 01:07:44.670 align:start position:0% use this in reality we will not with us 01:07:44.670 --> 01:07:47.749 align:start position:0% use this in reality we will not with us will<01:07:44.940> pigs<01:07:45.210> around<01:07:45.480> the<01:07:45.539> point<01:07:45.779> this<01:07:46.710> is<01:07:46.769> small 01:07:47.749 --> 01:07:47.759 align:start position:0% will pigs around the point this is small 01:07:47.759 --> 01:07:51.200 align:start position:0% will pigs around the point this is small number<01:07:48.269> compared<01:07:48.930> to<01:07:49.140> the<01:07:49.259> fill<01:07:49.440> itself<01:07:49.819> so<01:07:50.819> so 01:07:51.200 --> 01:07:51.210 align:start position:0% number compared to the fill itself so so 01:07:51.210 --> 01:07:54.859 align:start position:0% number compared to the fill itself so so chances<01:07:51.900> there<01:07:52.140> 80<01:07:52.769> of<01:07:53.039> those<01:07:53.309> two<01:07:53.910> has<01:07:54.809> the 01:07:54.859 --> 01:07:54.869 align:start position:0% chances there 80 of those two has the 01:07:54.869 --> 01:07:57.170 align:start position:0% chances there 80 of those two has the same<01:07:55.230> volume<01:07:55.500> as<01:07:55.950> a<01:07:56.009> random<01:07:56.730> point<01:07:56.849> is<01:07:57.059> still 01:07:57.170 --> 01:07:57.180 align:start position:0% same volume as a random point is still 01:07:57.180 --> 01:07:59.329 align:start position:0% same volume as a random point is still eligible<01:07:57.539> so<01:07:58.440> we<01:07:58.589> can<01:07:58.740> be<01:07:58.859> quite<01:07:59.099> sure<01:07:59.309> that 01:07:59.329 --> 01:07:59.339 align:start position:0% eligible so we can be quite sure that 01:07:59.339 --> 01:08:03.470 align:start position:0% eligible so we can be quite sure that we'd<01:07:59.960> be<01:08:00.960> twelve<01:08:01.319> and<01:08:01.940> proven<01:08:02.940> cannot<01:08:03.269> now 01:08:03.470 --> 01:08:03.480 align:start position:0% we'd be twelve and proven cannot now 01:08:03.480 --> 01:08:06.230 align:start position:0% we'd be twelve and proven cannot now change<01:08:03.990> the<01:08:04.259> problem<01:08:04.619> and<01:08:04.950> after<01:08:05.819> this<01:08:05.880> we're 01:08:06.230 --> 01:08:06.240 align:start position:0% change the problem and after this we're 01:08:06.240 --> 01:08:09.049 align:start position:0% change the problem and after this we're okay<01:08:06.569> possesses<01:08:07.309> help<01:08:08.309> back<01:08:08.519> to<01:08:08.700> this<01:08:08.849> case 01:08:09.049 --> 01:08:09.059 align:start position:0% okay possesses help back to this case 01:08:09.059 --> 01:08:11.269 align:start position:0% okay possesses help back to this case because<01:08:09.599> we<01:08:09.900> knows<01:08:10.079> that<01:08:10.230> problem<01:08:10.589> now<01:08:10.740> so<01:08:11.160> the 01:08:11.269 --> 01:08:11.279 align:start position:0% because we knows that problem now so the 01:08:11.279 --> 01:08:13.249 align:start position:0% because we knows that problem now so the power<01:08:11.460> constraints<01:08:11.789> are<01:08:12.119> fixed<01:08:12.480> as<01:08:12.630> a<01:08:12.839> set<01:08:13.140> up 01:08:13.249 --> 01:08:13.259 align:start position:0% power constraints are fixed as a set up 01:08:13.259 --> 01:08:15.589 align:start position:0% power constraints are fixed as a set up space<01:08:13.529> where<01:08:14.220> a<01:08:14.250> cave<01:08:14.609> is<01:08:14.819> preferred<01:08:15.180> having 01:08:15.589 --> 01:08:15.599 align:start position:0% space where a cave is preferred having 01:08:15.599 --> 01:08:19.459 align:start position:0% space where a cave is preferred having some<01:08:16.100> freedom<01:08:17.100> of<01:08:17.190> choice<01:08:17.630> from<01:08:18.630> set<01:08:19.319> up 01:08:19.459 --> 01:08:19.469 align:start position:0% some freedom of choice from set up 01:08:19.469 --> 01:08:21.890 align:start position:0% some freedom of choice from set up Wallaces<01:08:20.040> around<01:08:20.339> the<01:08:20.400> point<01:08:20.639> but<01:08:21.210> still<01:08:21.389> at 01:08:21.890 --> 01:08:21.900 align:start position:0% Wallaces around the point but still at 01:08:21.900 --> 01:08:23.539 align:start position:0% Wallaces around the point but still at the<01:08:21.989> end<01:08:22.199> of<01:08:22.409> the<01:08:22.529> day<01:08:22.679> he<01:08:22.949> will<01:08:23.069> not<01:08:23.279> be<01:08:23.429> able 01:08:23.539 --> 01:08:23.549 align:start position:0% the end of the day he will not be able 01:08:23.549 --> 01:08:25.249 align:start position:0% the end of the day he will not be able to<01:08:23.670> satisfy<01:08:23.880> sums<01:08:24.480> but<01:08:24.870> we<01:08:24.989> know<01:08:25.139> a 01:08:25.249 --> 01:08:25.259 align:start position:0% to satisfy sums but we know a 01:08:25.259 --> 01:08:27.769 align:start position:0% to satisfy sums but we know a relationship<01:08:25.799> well<01:08:26.370> similar<01:08:26.909> to<01:08:26.940> start<01:08:27.330> the 01:08:27.769 --> 01:08:27.779 align:start position:0% relationship well similar to start the 01:08:27.779 --> 01:08:30.470 align:start position:0% relationship well similar to start the pockets<01:08:28.170> difference<01:08:28.529> is<01:08:28.770> much<01:08:28.920> simpler<01:08:29.480> the 01:08:30.470 --> 01:08:30.480 align:start position:0% pockets difference is much simpler the 01:08:30.480 --> 01:08:32.720 align:start position:0% pockets difference is much simpler the end<01:08:30.750> of<01:08:30.900> the<01:08:30.989> day<01:08:31.139> you<01:08:31.500> still<01:08:31.560> will<01:08:31.980> be<01:08:32.250> limited 01:08:32.720 --> 01:08:32.730 align:start position:0% end of the day you still will be limited 01:08:32.730 --> 01:08:35.329 align:start position:0% end of the day you still will be limited by<01:08:32.880> particular<01:08:33.569> truss<01:08:34.350> analysis 01:08:35.329 --> 01:08:35.339 align:start position:0% by particular truss analysis 01:08:35.339 --> 01:08:39.919 align:start position:0% by particular truss analysis this<01:08:36.060> part<01:08:36.449> is<01:08:36.630> nonlinear<01:08:37.109> problem<01:08:38.690> where<01:08:39.690> she 01:08:39.919 --> 01:08:39.929 align:start position:0% this part is nonlinear problem where she 01:08:39.929 --> 01:08:42.439 align:start position:0% this part is nonlinear problem where she got<01:08:40.080> dissolved<01:08:40.639> we<01:08:41.639> got<01:08:41.969> to<01:08:42.120> know<01:08:42.239> people 01:08:42.439 --> 01:08:42.449 align:start position:0% got dissolved we got to know people 01:08:42.449 --> 01:08:44.840 align:start position:0% got dissolved we got to know people versus<01:08:42.900> soundless<01:08:43.290> aerosol<01:08:43.739> particle<01:08:44.370> which 01:08:44.840 --> 01:08:44.850 align:start position:0% versus soundless aerosol particle which 01:08:44.850 --> 01:08:46.809 align:start position:0% versus soundless aerosol particle which was<01:08:44.880> for<01:08:45.719> which<01:08:45.929> we<01:08:46.080> optimized<01:08:46.469> about 01:08:46.809 --> 01:08:46.819 align:start position:0% was for which we optimized about 01:08:46.819 --> 01:08:49.669 align:start position:0% was for which we optimized about additionally<01:08:47.819> so<01:08:48.330> now<01:08:48.600> we<01:08:48.659> can<01:08:48.929> have<01:08:49.170> a<01:08:49.199> larger 01:08:49.669 --> 01:08:49.679 align:start position:0% additionally so now we can have a larger 01:08:49.679 --> 01:08:50.990 align:start position:0% additionally so now we can have a larger Delta<01:08:50.069> potentially 01:08:50.990 --> 01:08:51.000 align:start position:0% Delta potentially 01:08:51.000 --> 01:08:53.840 align:start position:0% Delta potentially limitless<01:08:51.300> on<01:08:51.660> the<01:08:51.810> right<01:08:51.990> part<01:08:52.370> and<01:08:53.370> this 01:08:53.840 --> 01:08:53.850 align:start position:0% limitless on the right part and this 01:08:53.850 --> 01:08:56.030 align:start position:0% limitless on the right part and this will<01:08:54.060> gives<01:08:54.300> us<01:08:54.390> a<01:08:54.630> smaller<01:08:54.960> approved<01:08:55.410> for<01:08:56.010> a 01:08:56.030 --> 01:08:56.040 align:start position:0% will gives us a smaller approved for a 01:08:56.040 --> 01:08:58.160 align:start position:0% will gives us a smaller approved for a safe<01:08:56.280> sound<01:08:56.610> with<01:08:56.940> you<01:08:57.060> which<01:08:57.330> you<01:08:57.480> think<01:08:57.600> ever 01:08:58.160 --> 01:08:58.170 align:start position:0% safe sound with you which you think ever 01:08:58.170 --> 01:09:01.160 align:start position:0% safe sound with you which you think ever was<01:08:58.770> it<01:08:58.890> allows<01:08:59.220> you<01:08:59.490> to<01:08:59.670> have<01:08:59.910> full<01:09:00.630> benefits 01:09:01.160 --> 01:09:01.170 align:start position:0% was it allows you to have full benefits 01:09:01.170 --> 01:09:05.210 align:start position:0% was it allows you to have full benefits of<01:09:01.290> sobriety<01:09:01.910> but<01:09:02.910> for<01:09:03.240> every<01:09:03.860> pro<01:09:04.860> system 01:09:05.210 --> 01:09:05.220 align:start position:0% of sobriety but for every pro system 01:09:05.220 --> 01:09:13.510 align:start position:0% of sobriety but for every pro system which<01:09:05.400> just<01:09:05.640> uses<01:09:05.820> and<01:09:06.240> demands<01:09:06.600> of<01:09:10.550> yeah<01:09:11.550> a 01:09:13.510 --> 01:09:13.520 align:start position:0% which just uses and demands of yeah a 01:09:13.520 --> 01:09:14.780 align:start position:0% which just uses and demands of yeah a lot 01:09:14.780 --> 01:09:14.790 align:start position:0% lot 01:09:14.790 --> 01:09:17.060 align:start position:0% lot the<01:09:14.940> last<01:09:15.210> thing<01:09:15.450> down<01:09:15.690> here<01:09:15.930> gestures<01:09:16.170> I<01:09:16.650> said 01:09:17.060 --> 01:09:17.070 align:start position:0% the last thing down here gestures I said 01:09:17.070 --> 01:09:19.790 align:start position:0% the last thing down here gestures I said the<01:09:17.850> colonel<01:09:18.420> Kaminsky<01:09:19.080> with<01:09:19.470> the<01:09:19.560> sternum 01:09:19.790 --> 01:09:19.800 align:start position:0% the colonel Kaminsky with the sternum 01:09:19.800 --> 01:09:22.490 align:start position:0% the colonel Kaminsky with the sternum for<01:09:20.280> witnessed<01:09:20.730> animals<01:09:21.210> the<01:09:22.050> relation 01:09:22.490 --> 01:09:22.500 align:start position:0% for witnessed animals the relation 01:09:22.500 --> 01:09:24.830 align:start position:0% for witnessed animals the relation scheme<01:09:22.800> with<01:09:23.550> Jasper<01:09:24.090> as<01:09:24.210> a<01:09:24.240> child<01:09:24.570> for 01:09:24.830 --> 01:09:24.840 align:start position:0% scheme with Jasper as a child for 01:09:24.840 --> 01:09:29.450 align:start position:0% scheme with Jasper as a child for character<01:09:25.410> animals<01:09:25.800> and<01:09:27.770> it<01:09:28.770> will<01:09:29.010> be<01:09:29.130> blind 01:09:29.450 --> 01:09:29.460 align:start position:0% character animals and it will be blind 01:09:29.460 --> 01:09:33.710 align:start position:0% character animals and it will be blind for<01:09:30.650> some<01:09:31.650> zero-knowledge<01:09:32.100> schemes<01:09:32.720> we 01:09:33.710 --> 01:09:33.720 align:start position:0% for some zero-knowledge schemes we 01:09:33.720 --> 01:09:35.750 align:start position:0% for some zero-knowledge schemes we caught<01:09:34.080> both<01:09:34.440> a<01:09:34.680> witness<01:09:34.950> polynomials<01:09:35.520> and 01:09:35.750 --> 01:09:35.760 align:start position:0% caught both a witness polynomials and 01:09:35.760 --> 01:09:38.420 align:start position:0% caught both a witness polynomials and their<01:09:36.180> content<01:09:36.870> on<01:09:37.020> memo<01:09:37.290> and<01:09:37.560> then<01:09:37.860> their 01:09:38.420 --> 01:09:38.430 align:start position:0% their content on memo and then their 01:09:38.430 --> 01:09:40.220 align:start position:0% their content on memo and then their witnesses<01:09:38.910> in<01:09:39.150> constraints<01:09:39.690> enormous 01:09:40.220 --> 01:09:40.230 align:start position:0% witnesses in constraints enormous 01:09:40.230 --> 01:09:43.790 align:start position:0% witnesses in constraints enormous polynomials<01:09:40.770> and<01:09:40.980> then<01:09:41.670> just<01:09:41.970> wear<01:09:42.570> the<01:09:43.080> veil 01:09:43.790 --> 01:09:43.800 align:start position:0% polynomials and then just wear the veil 01:09:43.800 --> 01:09:48.650 align:start position:0% polynomials and then just wear the veil is<01:09:44.040> at<01:09:44.160> some<01:09:44.340> point<01:09:44.370> and<01:09:45.000> check<01:09:45.630> some<01:09:47.660> novel 01:09:48.650 --> 01:09:48.660 align:start position:0% is at some point and check some novel 01:09:48.660 --> 01:09:52.070 align:start position:0% is at some point and check some novel relation<01:09:48.990> between<01:09:49.110> them<01:09:50.060> as<01:09:51.060> used<01:09:51.390> schwarzy 01:09:52.070 --> 01:09:52.080 align:start position:0% relation between them as used schwarzy 01:09:52.080 --> 01:09:55.430 align:start position:0% relation between them as used schwarzy bill<01:09:52.290> this<01:09:53.190> is<01:09:53.340> just<01:09:53.550> exactly<01:09:53.940> bond<01:09:54.330> where<01:09:54.840> are 01:09:55.430 --> 01:09:55.440 align:start position:0% bill this is just exactly bond where are 01:09:55.440 --> 01:10:02.280 align:start position:0% bill this is just exactly bond where are they 01:10:02.280 --> 01:10:02.290 align:start position:0% 01:10:02.290 --> 01:10:07.030 align:start position:0% for<01:10:03.290> example<01:10:04.040> that<01:10:04.730> constraint<01:10:05.590> polymers<01:10:06.590> for 01:10:07.030 --> 01:10:07.040 align:start position:0% for example that constraint polymers for 01:10:07.040 --> 01:10:10.660 align:start position:0% for example that constraint polymers for banca<01:10:07.970> those<01:10:08.210> electrical<01:10:09.080> members<01:10:09.670> cube 01:10:10.660 --> 01:10:10.670 align:start position:0% banca those electrical members cube 01:10:10.670 --> 01:10:14.050 align:start position:0% banca those electrical members cube collect<01:10:11.540> you<01:10:11.930> write<01:10:13.060> multiple 01:10:14.050 --> 01:10:14.060 align:start position:0% collect you write multiple 01:10:14.060 --> 01:10:22.120 align:start position:0% collect you write multiple multiplication<01:10:14.810> so<01:10:14.930> on<01:10:17.740> and<01:10:18.970> he<01:10:19.970> just<01:10:21.130> sending 01:10:22.120 --> 01:10:22.130 align:start position:0% multiplication so on and he just sending 01:10:22.130 --> 01:10:27.760 align:start position:0% multiplication so on and he just sending random<01:10:22.340> various<01:10:23.240> is<01:10:23.630> for<01:10:26.560> assimilation<01:10:27.560> of 01:10:27.760 --> 01:10:27.770 align:start position:0% random various is for assimilation of 01:10:27.770 --> 01:10:32.460 align:start position:0% random various is for assimilation of interaction<01:10:30.310> but<01:10:31.310> the<01:10:31.400> final<01:10:31.760> step<01:10:32.030> of 01:10:32.460 --> 01:10:32.470 align:start position:0% interaction but the final step of 01:10:32.470 --> 01:10:38.050 align:start position:0% interaction but the final step of protocol<01:10:35.080> is<01:10:36.080> a<01:10:36.140> checksum<01:10:37.060> relationship 01:10:38.050 --> 01:10:38.060 align:start position:0% protocol is a checksum relationship 01:10:38.060 --> 01:10:42.430 align:start position:0% protocol is a checksum relationship between<01:10:38.380> animals<01:10:39.380> upon<01:10:40.810> which<01:10:41.810> our<01:10:41.960> customer 01:10:42.430 --> 01:10:42.440 align:start position:0% between animals upon which our customer 01:10:42.440 --> 01:10:46.420 align:start position:0% between animals upon which our customer normals<01:10:43.040> and<01:10:44.290> fixed<01:10:45.290> at<01:10:45.590> the<01:10:45.740> chocolate<01:10:46.160> which 01:10:46.420 --> 01:10:46.430 align:start position:0% normals and fixed at the chocolate which 01:10:46.430 --> 01:10:50.050 align:start position:0% normals and fixed at the chocolate which are<01:10:46.550> called<01:10:46.730> our<01:10:47.060> just<01:10:47.420> problem<01:10:47.870> and<01:10:49.060> with 01:10:50.050 --> 01:10:50.060 align:start position:0% are called our just problem and with 01:10:50.060 --> 01:10:55.960 align:start position:0% are called our just problem and with this<01:10:50.150> phenomenal<01:10:54.250> possibly<01:10:55.250> CJ<01:10:55.550> our 01:10:55.960 --> 01:10:55.970 align:start position:0% this phenomenal possibly CJ our 01:10:55.970 --> 01:11:03.000 align:start position:0% this phenomenal possibly CJ our constraints<01:10:56.810> will<01:10:56.930> be<01:10:56.960> just<01:10:58.300> the<01:10:59.300> other<01:11:00.850> and 01:11:03.000 --> 01:11:03.010 align:start position:0% constraints will be just the other and 01:11:03.010 --> 01:11:06.700 align:start position:0% constraints will be just the other and he<01:11:04.010> advanced<01:11:04.580> areas<01:11:05.000> particularly<01:11:05.440> if<01:11:06.440> this 01:11:06.700 --> 01:11:06.710 align:start position:0% he advanced areas particularly if this 01:11:06.710 --> 01:11:10.240 align:start position:0% he advanced areas particularly if this relation<01:11:07.670> holds<01:11:08.470> if<01:11:09.470> it<01:11:09.800> doesn't<01:11:10.040> called 01:11:10.240 --> 01:11:10.250 align:start position:0% relation holds if it doesn't called 01:11:10.250 --> 01:11:15.010 align:start position:0% relation holds if it doesn't called attack<01:11:10.700> at<01:11:10.880> one<01:11:11.420> point<01:11:11.660> them<01:11:13.000> with<01:11:14.000> a<01:11:14.300> random 01:11:15.010 --> 01:11:15.020 align:start position:0% attack at one point them with a random 01:11:15.020 --> 01:11:17.890 align:start position:0% attack at one point them with a random probability<01:11:15.230> then<01:11:15.890> called<01:11:16.390> at<01:11:17.390> the<01:11:17.540> sweater 01:11:17.890 --> 01:11:17.900 align:start position:0% probability then called at the sweater 01:11:17.900 --> 01:11:20.530 align:start position:0% probability then called at the sweater at<01:11:18.530> the<01:11:18.620> space<01:11:18.860> so<01:11:19.160> we<01:11:19.730> just<01:11:19.940> need<01:11:20.090> to<01:11:20.150> check 01:11:20.530 --> 01:11:20.540 align:start position:0% at the space so we just need to check 01:11:20.540 --> 01:11:23.800 align:start position:0% at the space so we just need to check this<01:11:20.990> relational<01:11:21.620> point<01:11:21.920> and<01:11:22.340> for<01:11:22.610> this<01:11:22.810> we 01:11:23.800 --> 01:11:23.810 align:start position:0% this relational point and for this we 01:11:23.810 --> 01:11:27.910 align:start position:0% this relational point and for this we use<01:11:24.700> the<01:11:25.700> chemical<01:11:26.090> scheme<01:11:26.390> to<01:11:27.320> open<01:11:27.740> the 01:11:27.910 --> 01:11:27.920 align:start position:0% use the chemical scheme to open the 01:11:27.920 --> 01:11:32.260 align:start position:0% use the chemical scheme to open the values<01:11:28.250> of<01:11:28.870> witness<01:11:29.870> polynomials<01:11:30.520> at<01:11:31.520> some 01:11:32.260 --> 01:11:32.270 align:start position:0% values of witness polynomials at some 01:11:32.270 --> 01:11:34.840 align:start position:0% values of witness polynomials at some point<01:11:32.540> C<01:11:32.810> of<01:11:33.110> our<01:11:33.230> choice<01:11:33.590> and<01:11:33.950> use<01:11:34.610> the 01:11:34.840 --> 01:11:34.850 align:start position:0% point C of our choice and use the 01:11:34.850 --> 01:11:37.489 align:start position:0% point C of our choice and use the relation<01:11:35.240> scheme<01:11:35.570> to<01:11:36.140> open<01:11:36.620> the<01:11:36.740> world 01:11:37.489 --> 01:11:37.499 align:start position:0% relation scheme to open the world 01:11:37.499 --> 01:11:40.189 align:start position:0% relation scheme to open the world at<01:11:38.130> the<01:11:38.849> same<01:11:39.059> point<01:11:39.239> see<01:11:39.510> just<01:11:39.840> to<01:11:39.960> speed<01:11:40.170> up 01:11:40.189 --> 01:11:40.199 align:start position:0% at the same point see just to speed up 01:11:40.199 --> 01:11:43.270 align:start position:0% at the same point see just to speed up the<01:11:40.979> calculation<01:11:41.369> of<01:11:41.519> Earth<01:11:41.789> prom<01:11:42.210> terrifies 01:11:43.270 --> 01:11:43.280 align:start position:0% the calculation of Earth prom terrifies 01:11:43.280 --> 01:11:46.250 align:start position:0% the calculation of Earth prom terrifies point<01:11:44.280> of<01:11:44.460> view<01:11:44.639> and<01:11:45.420> then<01:11:45.510> to<01:11:45.690> just<01:11:45.869> check<01:11:46.110> the 01:11:46.250 --> 01:11:46.260 align:start position:0% point of view and then to just check the 01:11:46.260 --> 01:11:48.919 align:start position:0% point of view and then to just check the relation<01:11:46.679> and<01:11:47.190> the<01:11:47.760> siege<01:11:48.090> it<01:11:48.329> seems<01:11:48.570> like<01:11:48.780> to 01:11:48.919 --> 01:11:48.929 align:start position:0% relation and the siege it seems like to 01:11:48.929 --> 01:11:54.910 align:start position:0% relation and the siege it seems like to be<01:11:49.079> in<01:11:49.229> a<01:11:49.469> full<01:11:50.369> the<01:11:50.999> last<01:11:51.150> one<01:11:52.880> it<01:11:53.880> seems<01:11:54.179> to 01:11:54.910 --> 01:11:54.920 align:start position:0% be in a full the last one it seems to 01:11:54.920 --> 01:11:58.580 align:start position:0% be in a full the last one it seems to achieve<01:11:55.920> our<01:11:56.099> goal<01:11:56.400> which<01:11:56.639> is<01:11:56.670> a<01:11:57.440> system<01:11:58.440> which 01:11:58.580 --> 01:11:58.590 align:start position:0% achieve our goal which is a system which 01:11:58.590 --> 01:11:59.959 align:start position:0% achieve our goal which is a system which is<01:11:58.739> for<01:11:59.070> just<01:11:59.369> balance 01:11:59.959 --> 01:11:59.969 align:start position:0% is for just balance 01:11:59.969 --> 01:12:03.709 align:start position:0% is for just balance okay<01:12:00.510> the<01:12:00.659> chakras<01:12:01.170> is<01:12:01.440> logic<01:12:01.889> but<01:12:02.479> the<01:12:03.479> search 01:12:03.709 --> 01:12:03.719 align:start position:0% okay the chakras is logic but the search 01:12:03.719 --> 01:12:06.500 align:start position:0% okay the chakras is logic but the search for<01:12:03.989> the<01:12:04.260> Point<01:12:04.499> C<01:12:04.710> but<01:12:05.510> nevertheless 01:12:06.500 --> 01:12:06.510 align:start position:0% for the Point C but nevertheless 01:12:06.510 --> 01:12:07.609 align:start position:0% for the Point C but nevertheless topology 01:12:07.609 --> 01:12:07.619 align:start position:0% topology 01:12:07.619 --> 01:12:11.479 align:start position:0% topology it's<01:12:07.829> exchangeable<01:12:08.550> at<01:12:08.639> Wonka<01:12:08.969> 716<01:12:09.659> and<01:12:10.309> as<01:12:11.309> we 01:12:11.479 --> 01:12:11.489 align:start position:0% it's exchangeable at Wonka 716 and as we 01:12:11.489 --> 01:12:14.750 align:start position:0% it's exchangeable at Wonka 716 and as we replace<01:12:11.789> our<01:12:12.150> chemical<01:12:12.809> scheme<01:12:13.079> by<01:12:13.409> fry<01:12:14.190> which 01:12:14.750 --> 01:12:14.760 align:start position:0% replace our chemical scheme by fry which 01:12:14.760 --> 01:12:16.989 align:start position:0% replace our chemical scheme by fry which works<01:12:15.059> in<01:12:15.269> interactive<01:12:15.960> Oracle<01:12:16.289> link<01:12:16.499> module 01:12:16.989 --> 01:12:16.999 align:start position:0% works in interactive Oracle link module 01:12:16.999 --> 01:12:20.149 align:start position:0% works in interactive Oracle link module which<01:12:17.999> is<01:12:18.269> just<01:12:18.599> caches<01:12:19.260> a<01:12:19.289> song<01:12:19.590> there<01:12:20.039> were 01:12:20.149 --> 01:12:20.159 align:start position:0% which is just caches a song there were 01:12:20.159 --> 01:12:21.950 align:start position:0% which is just caches a song there were two<01:12:20.309> commercial<01:12:20.760> constructions<01:12:21.329> it<01:12:21.749> is 01:12:21.950 --> 01:12:21.960 align:start position:0% two commercial constructions it is 01:12:21.960 --> 01:12:26.660 align:start position:0% two commercial constructions it is quantum<01:12:22.320> resistance<01:12:24.469> resistance<01:12:25.469> so<01:12:26.429> that's 01:12:26.660 --> 01:12:26.670 align:start position:0% quantum resistance resistance so that's 01:12:26.670 --> 01:12:28.359 align:start position:0% quantum resistance resistance so that's that's<01:12:27.300> it 01:12:28.359 --> 01:12:28.369 align:start position:0% that's it 01:12:28.369 --> 01:12:31.310 align:start position:0% that's it any<01:12:29.369> questions<01:12:29.760> yeah<01:12:30.329> you<01:12:30.780> forget<01:12:31.050> to<01:12:31.170> mention 01:12:31.310 --> 01:12:31.320 align:start position:0% any questions yeah you forget to mention 01:12:31.320 --> 01:12:33.500 align:start position:0% any questions yeah you forget to mention mentions<01:12:32.010> of<01:12:32.099> this<01:12:32.219> in<01:12:32.519> principle<01:12:32.699> because<01:12:33.119> I 01:12:33.500 --> 01:12:33.510 align:start position:0% mentions of this in principle because I 01:12:33.510 --> 01:12:38.029 align:start position:0% mentions of this in principle because I get<01:12:34.349> definitely<01:12:34.889> there<01:12:35.639> was<01:12:36.110> when<01:12:37.110> we<01:12:37.530> are<01:12:37.920> not 01:12:38.029 --> 01:12:38.039 align:start position:0% get definitely there was when we are not 01:12:38.039 --> 01:12:40.729 align:start position:0% get definitely there was when we are not bound<01:12:38.309> by<01:12:38.699> any<01:12:39.510> year<01:12:39.780> parameters<01:12:40.409> and<01:12:40.559> just 01:12:40.729 --> 01:12:40.739 align:start position:0% bound by any year parameters and just 01:12:40.739 --> 01:12:45.109 align:start position:0% bound by any year parameters and just too<01:12:40.889> tough<01:12:41.070> so<01:12:41.460> main<01:12:43.340> when<01:12:44.340> we<01:12:44.460> take<01:12:44.699> as<01:12:44.909> many 01:12:45.109 --> 01:12:45.119 align:start position:0% too tough so main when we take as many 01:12:45.119 --> 01:12:47.779 align:start position:0% too tough so main when we take as many levels<01:12:45.420> of<01:12:46.079> recursion<01:12:46.229> as<01:12:46.679> we<01:12:46.920> need<01:12:47.099> for<01:12:47.699> our 01:12:47.779 --> 01:12:47.789 align:start position:0% levels of recursion as we need for our 01:12:47.789 --> 01:13:09.840 align:start position:0% levels of recursion as we need for our aims<01:12:51.199> all<01:12:52.199> purposes 01:13:09.840 --> 01:13:09.850 align:start position:0% 01:13:09.850 --> 01:13:15.530 align:start position:0% [Music] 01:13:15.530 --> 01:13:15.540 align:start position:0% 01:13:15.540 --> 01:13:18.899 align:start position:0% first<01:13:16.540> of<01:13:16.659> all<01:13:16.840> it's<01:13:17.440> we<01:13:18.280> don't<01:13:18.400> try<01:13:18.610> to<01:13:18.670> make 01:13:18.899 --> 01:13:18.909 align:start position:0% first of all it's we don't try to make 01:13:18.909 --> 01:13:26.580 align:start position:0% first of all it's we don't try to make the<01:13:19.000> grow<01:13:19.179> system<01:13:19.540> it<01:13:20.170> can<01:13:20.380> be<01:13:23.550> okay<01:13:24.580> it<01:13:25.590> just 01:13:26.580 --> 01:13:26.590 align:start position:0% the grow system it can be okay it just 01:13:26.590 --> 01:13:28.020 align:start position:0% the grow system it can be okay it just allows<01:13:27.130> you<01:13:27.280> to<01:13:27.400> take<01:13:27.550> into<01:13:27.730> proof<01:13:27.880> system 01:13:28.020 --> 01:13:28.030 align:start position:0% allows you to take into proof system 01:13:28.030 --> 01:13:30.240 align:start position:0% allows you to take into proof system which<01:13:28.300> is<01:13:28.389> masculine<01:13:28.840> or<01:13:29.020> commitments<01:13:29.500> and<01:13:29.920> we 01:13:30.240 --> 01:13:30.250 align:start position:0% which is masculine or commitments and we 01:13:30.250 --> 01:13:32.669 align:start position:0% which is masculine or commitments and we shall<01:13:30.429> send<01:13:30.639> codes<01:13:31.050> constraints<01:13:32.050> or<01:13:32.440> as<01:13:32.590> a 01:13:32.669 --> 01:13:32.679 align:start position:0% shall send codes constraints or as a 01:13:32.679 --> 01:13:35.070 align:start position:0% shall send codes constraints or as a program<01:13:32.980> itself<01:13:33.219> as<01:13:33.489> a<01:13:33.550> colon<01:13:33.880> or<01:13:34.000> no<01:13:34.150> and<01:13:34.960> all 01:13:35.070 --> 01:13:35.080 align:start position:0% program itself as a colon or no and all 01:13:35.080 --> 01:13:41.820 align:start position:0% program itself as a colon or no and all supplies<01:13:35.560> the<01:13:35.710> city<01:13:40.349> well<01:13:41.349> you<01:13:41.469> can<01:13:41.619> call<01:13:41.770> it 01:13:41.820 --> 01:13:41.830 align:start position:0% supplies the city well you can call it 01:13:41.830 --> 01:13:44.220 align:start position:0% supplies the city well you can call it food<01:13:42.040> restaurant<01:13:42.489> if<01:13:43.000> I<01:13:43.119> mean<01:13:43.270> yeah<01:13:43.360> you<01:13:43.420> you 01:13:44.220 --> 01:13:44.230 align:start position:0% food restaurant if I mean yeah you you 01:13:44.230 --> 01:13:46.410 align:start position:0% food restaurant if I mean yeah you you think<01:13:44.500> the<01:13:44.560> Blanc<01:13:44.830> is<01:13:44.949> a<01:13:44.980> fungus<01:13:45.730> well<01:13:46.119> it's<01:13:46.360> a 01:13:46.410 --> 01:13:46.420 align:start position:0% think the Blanc is a fungus well it's a 01:13:46.420 --> 01:13:48.859 align:start position:0% think the Blanc is a fungus well it's a pro<01:13:46.570> system<01:13:46.750> it<01:13:47.139> tells<01:13:47.710> a<01:13:47.800> decision<01:13:48.520> and<01:13:48.699> just 01:13:48.859 --> 01:13:48.869 align:start position:0% pro system it tells a decision and just 01:13:48.869 --> 01:13:51.720 align:start position:0% pro system it tells a decision and just the<01:13:49.869> east<01:13:50.170> based<01:13:50.530> and<01:13:50.889> the<01:13:50.980> fact<01:13:51.190> that<01:13:51.280> you<01:13:51.460> can 01:13:51.720 --> 01:13:51.730 align:start position:0% the east based and the fact that you can 01:13:51.730 --> 01:13:53.070 align:start position:0% the east based and the fact that you can commit<01:13:51.969> to<01:13:52.090> someone<01:13:52.300> will<01:13:52.599> have<01:13:52.659> interpreted 01:13:53.070 --> 01:13:53.080 align:start position:0% commit to someone will have interpreted 01:13:53.080 --> 01:13:54.450 align:start position:0% commit to someone will have interpreted as<01:13:53.320> a<01:13:53.349> random<01:13:53.679> point<01:13:53.860> and<01:13:54.190> then<01:13:54.340> obviously 01:13:54.450 --> 01:13:54.460 align:start position:0% as a random point and then obviously 01:13:54.460 --> 01:13:56.729 align:start position:0% as a random point and then obviously it's<01:13:54.940> a<01:13:54.969> random<01:13:55.270> point<01:13:55.420> it's<01:13:55.869> out<01:13:56.199> of<01:13:56.260> a<01:13:56.530> system 01:13:56.729 --> 01:13:56.739 align:start position:0% it's a random point it's out of a system 01:13:56.739 --> 01:13:59.129 align:start position:0% it's a random point it's out of a system where<01:13:57.099> you<01:13:57.190> have<01:13:57.550> in<01:13:57.670> mind<01:13:57.849> or<01:13:58.239> not<01:13:58.599> trying<01:13:58.989> to 01:13:59.129 --> 01:13:59.139 align:start position:0% where you have in mind or not trying to 01:13:59.139 --> 01:14:01.919 align:start position:0% where you have in mind or not trying to apply<01:13:59.500> so<01:14:00.099> long<01:14:00.670> and<01:14:01.030> to<01:14:01.179> replace<01:14:01.449> the<01:14:01.719> kids 01:14:01.919 --> 01:14:01.929 align:start position:0% apply so long and to replace the kids 01:14:01.929 --> 01:14:03.810 align:start position:0% apply so long and to replace the kids management<01:14:02.409> which<01:14:02.590> requests<01:14:02.920> as<01:14:03.130> a<01:14:03.159> child<01:14:03.550> by 01:14:03.810 --> 01:14:03.820 align:start position:0% management which requests as a child by 01:14:03.820 --> 01:14:08.100 align:start position:0% management which requests as a child by new<01:14:04.420> commitments<01:14:05.020> and<01:14:05.199> relations<01:14:06.869> in<01:14:07.869> fact 01:14:08.100 --> 01:14:08.110 align:start position:0% new commitments and relations in fact 01:14:08.110 --> 01:14:12.419 align:start position:0% new commitments and relations in fact that<01:14:10.080> we<01:14:11.080> need<01:14:11.230> to<01:14:11.409> our<01:14:11.590> vacation<01:14:12.159> time<01:14:12.369> is 01:14:12.419 --> 01:14:12.429 align:start position:0% that we need to our vacation time is 01:14:12.429 --> 01:14:16.830 align:start position:0% that we need to our vacation time is even<01:14:13.300> to<01:14:13.449> operate<01:14:13.869> I<01:14:14.170> mean<01:14:15.099> sugar<01:14:15.820> girls<01:14:16.179> are<01:14:16.420> I 01:14:16.830 --> 01:14:16.840 align:start position:0% even to operate I mean sugar girls are I 01:14:16.840 --> 01:14:19.470 align:start position:0% even to operate I mean sugar girls are I would<01:14:17.650> it<01:14:17.770> be<01:14:17.889> run<01:14:18.489> time<01:14:18.730> recognition 01:14:19.470 --> 01:14:19.480 align:start position:0% would it be run time recognition 01:14:19.480 --> 01:14:23.280 align:start position:0% would it be run time recognition approving<01:14:19.869> well<01:14:21.480> for<01:14:22.480> now<01:14:22.630> for<01:14:22.690> you<01:14:23.020> do 01:14:23.280 --> 01:14:23.290 align:start position:0% approving well for now for you do 01:14:23.290 --> 01:14:25.500 align:start position:0% approving well for now for you do progressing<01:14:23.860> exactly<01:14:24.280> just<01:14:24.550> twice<01:14:24.969> lowers 01:14:25.500 --> 01:14:25.510 align:start position:0% progressing exactly just twice lowers 01:14:25.510 --> 01:14:28.260 align:start position:0% progressing exactly just twice lowers inverse<01:14:25.929> but<01:14:26.800> should<01:14:27.130> be<01:14:27.239> should<01:14:28.239> be 01:14:28.260 --> 01:14:28.270 align:start position:0% inverse but should be should be 01:14:28.270 --> 01:14:31.800 align:start position:0% inverse but should be should be optimized<01:14:28.900> to<01:14:28.929> the<01:14:29.199> same<01:14:29.409> level<01:14:29.770> yeah<01:14:30.659> yeah<01:14:31.659> it 01:14:31.800 --> 01:14:31.810 align:start position:0% optimized to the same level yeah yeah it 01:14:31.810 --> 01:14:33.240 align:start position:0% optimized to the same level yeah yeah it should<01:14:31.960> be<01:14:31.989> to<01:14:32.260> be<01:14:32.409> the<01:14:32.469> same<01:14:32.739> speed<01:14:33.010> because 01:14:33.240 --> 01:14:33.250 align:start position:0% should be to be the same speed because 01:14:33.250 --> 01:14:36.149 align:start position:0% should be to be the same speed because here<01:14:34.060> or<01:14:34.449> fried<01:14:34.869> particularly<01:14:35.440> capital<01:14:35.830> order 01:14:36.149 --> 01:14:36.159 align:start position:0% here or fried particularly capital order 01:14:36.159 --> 01:14:39.359 align:start position:0% here or fried particularly capital order extensions<01:14:36.730> of<01:14:36.849> the<01:14:36.940> module<01:14:37.300> so<01:14:37.900> which<01:14:38.679> means 01:14:39.359 --> 01:14:39.369 align:start position:0% extensions of the module so which means 01:14:39.369 --> 01:14:41.100 align:start position:0% extensions of the module so which means that<01:14:39.580> you<01:14:39.730> just<01:14:40.030> take<01:14:40.179> the<01:14:40.330> point<01:14:40.540> of<01:14:40.599> degree<01:14:40.900> M 01:14:41.100 --> 01:14:41.110 align:start position:0% that you just take the point of degree M 01:14:41.110 --> 01:14:45.130 align:start position:0% that you just take the point of degree M and<01:14:41.409> you<01:14:41.440> have<01:14:42.040> to<01:14:42.219> calculate<01:14:43.830> equity<01:14:44.830> of 01:14:45.130 --> 01:14:45.140 align:start position:0% and you have to calculate equity of 01:14:45.140 --> 01:14:49.450 align:start position:0% and you have to calculate equity of like<01:14:45.500> sixteen<01:14:45.920> pound<01:14:46.570> which<01:14:47.570> is<01:14:48.070> like<01:14:49.070> which 01:14:49.450 --> 01:14:49.460 align:start position:0% like sixteen pound which is like which 01:14:49.460 --> 01:14:51.820 align:start position:0% like sixteen pound which is like which is<01:14:49.520> a<01:14:49.670> large<01:14:49.910> to<01:14:50.150> share<01:14:50.470> but<01:14:51.470> there's<01:14:51.680> only 01:14:51.820 --> 01:14:51.830 align:start position:0% is a large to share but there's only 01:14:51.830 --> 01:14:54.190 align:start position:0% is a large to share but there's only like<01:14:52.040> now<01:14:52.850> it's<01:14:53.090> already<01:14:53.390> less<01:14:53.810> than<01:14:53.960> 30 01:14:54.190 --> 01:14:54.200 align:start position:0% like now it's already less than 30 01:14:54.200 --> 01:14:55.720 align:start position:0% like now it's already less than 30 percent<01:14:54.230> sons<01:14:54.650> of<01:14:54.740> work<01:14:54.890> so<01:14:55.340> the<01:14:55.400> rest<01:14:55.520> doesn't 01:14:55.720 --> 01:14:55.730 align:start position:0% percent sons of work so the rest doesn't 01:14:55.730 --> 01:14:58.090 align:start position:0% percent sons of work so the rest doesn't work<01:14:55.910> is<01:14:56.030> just<01:14:56.150> actually<01:14:56.510> a<01:14:56.570> little<01:14:56.780> petty<01:14:57.100> but 01:14:58.090 --> 01:14:58.100 align:start position:0% work is just actually a little petty but 01:14:58.100 --> 01:15:00.730 align:start position:0% work is just actually a little petty but can<01:14:58.670> you<01:14:58.790> still<01:14:59.030> look<01:14:59.150> free<01:14:59.390> it<01:15:00.020> it's<01:15:00.440> fast 01:15:00.730 --> 01:15:00.740 align:start position:0% can you still look free it it's fast 01:15:00.740 --> 01:15:03.670 align:start position:0% can you still look free it it's fast it's<01:15:01.160> still<01:15:01.820> not<01:15:01.940> free<01:15:02.150> so<01:15:03.050> yeah<01:15:03.260> it<01:15:03.410> should<01:15:03.560> be 01:15:03.670 --> 01:15:03.680 align:start position:0% it's still not free so yeah it should be 01:15:03.680 --> 01:15:05.860 align:start position:0% it's still not free so yeah it should be on<01:15:03.770> par<01:15:04.010> for<01:15:04.370> replication<01:15:05.090> we<01:15:05.390> will<01:15:05.540> see<01:15:05.690> what 01:15:05.860 --> 01:15:05.870 align:start position:0% on par for replication we will see what 01:15:05.870 --> 01:15:09.550 align:start position:0% on par for replication we will see what what<01:15:06.230> will<01:15:06.470> be<01:15:06.620> there<01:15:06.890> it's<01:15:07.670> a<01:15:07.730> pasta<01:15:07.910> -<01:15:08.170> oops<01:15:09.170> I 01:15:09.550 --> 01:15:09.560 align:start position:0% what will be there it's a pasta - oops I 01:15:09.560 --> 01:15:12.190 align:start position:0% what will be there it's a pasta - oops I mean<01:15:09.770> now<01:15:10.370> it's<01:15:10.610> Elsa<01:15:11.180> freedom<01:15:11.480> of<01:15:11.570> choice<01:15:11.780> if 01:15:12.190 --> 01:15:12.200 align:start position:0% mean now it's Elsa freedom of choice if 01:15:12.200 --> 01:15:14.020 align:start position:0% mean now it's Elsa freedom of choice if you<01:15:12.320> want<01:15:12.470> to<01:15:12.560> be<01:15:12.710> transparent<01:15:13.220> plus<01:15:13.610> repairs 01:15:14.020 --> 01:15:14.030 align:start position:0% you want to be transparent plus repairs 01:15:14.030 --> 01:15:16.360 align:start position:0% you want to be transparent plus repairs it<01:15:14.210> you<01:15:14.840> can<01:15:14.990> do<01:15:15.110> this<01:15:15.290> or<01:15:15.470> you<01:15:15.890> can<01:15:16.040> use<01:15:16.190> this 01:15:16.360 --> 01:15:16.370 align:start position:0% it you can do this or you can use this 01:15:16.370 --> 01:15:19.420 align:start position:0% it you can do this or you can use this if<01:15:17.180> you're<01:15:17.630> don't<01:15:18.140> need<01:15:18.350> recursion<01:15:19.010> and<01:15:19.190> I 01:15:19.420 --> 01:15:19.430 align:start position:0% if you're don't need recursion and I 01:15:19.430 --> 01:15:21.040 align:start position:0% if you're don't need recursion and I mean<01:15:19.580> if<01:15:19.730> you've<01:15:19.880> already<01:15:20.060> has<01:15:20.570> a<01:15:20.600> transit 01:15:21.040 --> 01:15:21.050 align:start position:0% mean if you've already has a transit 01:15:21.050 --> 01:15:23.530 align:start position:0% mean if you've already has a transit setup<01:15:21.350> in<01:15:21.980> terms<01:15:22.250> of<01:15:22.370> powers<01:15:22.790> of<01:15:22.940> towel<01:15:23.180> for<01:15:23.510> a 01:15:23.530 --> 01:15:23.540 align:start position:0% setup in terms of powers of towel for a 01:15:23.540 --> 01:15:25.990 align:start position:0% setup in terms of powers of towel for a cape<01:15:23.570> commitment<01:15:24.280> you<01:15:25.280> can<01:15:25.430> just<01:15:25.580> take<01:15:25.760> those 01:15:25.990 --> 01:15:26.000 align:start position:0% cape commitment you can just take those 01:15:26.000 --> 01:15:29.230 align:start position:0% cape commitment you can just take those and<01:15:26.360> if<01:15:26.600> your<01:15:27.280> beeps<01:15:28.280> good<01:15:28.490> very<01:15:28.730> problem<01:15:29.150> you 01:15:29.230 --> 01:15:29.240 align:start position:0% and if your beeps good very problem you 01:15:29.240 --> 01:15:31.600 align:start position:0% and if your beeps good very problem you can<01:15:29.420> use<01:15:29.600> it<01:15:29.780> it's<01:15:30.110> not<01:15:30.800> a<01:15:30.860> freedom<01:15:31.160> of<01:15:31.370> choice 01:15:31.600 --> 01:15:31.610 align:start position:0% can use it it's not a freedom of choice 01:15:31.610 --> 01:15:34.180 align:start position:0% can use it it's not a freedom of choice I'm<01:15:32.390> not<01:15:32.570> even<01:15:32.870> talking<01:15:32.990> about<01:15:33.170> like<01:15:33.620> exotic 01:15:34.180 --> 01:15:34.190 align:start position:0% I'm not even talking about like exotic 01:15:34.190 --> 01:15:35.550 align:start position:0% I'm not even talking about like exotic instructions<01:15:34.790> where<01:15:34.940> you<01:15:35.000> can<01:15:35.150> use<01:15:35.300> the 01:15:35.550 --> 01:15:35.560 align:start position:0% instructions where you can use the 01:15:35.560 --> 01:15:38.290 align:start position:0% instructions where you can use the transparent<01:15:36.560> parts<01:15:36.890> of<01:15:37.000> transparent<01:15:38.000> one<01:15:38.150> is 01:15:38.290 --> 01:15:38.300 align:start position:0% transparent parts of transparent one is 01:15:38.300 --> 01:15:40.660 align:start position:0% transparent parts of transparent one is like<01:15:38.690> water<01:15:38.990> levels<01:15:39.470> of<01:15:39.590> recursion<01:15:39.740> and<01:15:40.520> then 01:15:40.660 --> 01:15:40.670 align:start position:0% like water levels of recursion and then 01:15:40.670 --> 01:15:42.460 align:start position:0% like water levels of recursion and then you<01:15:40.760> can<01:15:40.880> do<01:15:40.970> the<01:15:41.030> final<01:15:41.300> one<01:15:41.600> with<01:15:41.840> kid 01:15:42.460 --> 01:15:42.470 align:start position:0% you can do the final one with kid 01:15:42.470 --> 01:15:44.380 align:start position:0% you can do the final one with kid commitment<01:15:42.920> because<01:15:43.670> now<01:15:43.940> you<01:15:44.000> don't<01:15:44.150> have<01:15:44.330> a 01:15:44.380 --> 01:15:44.390 align:start position:0% commitment because now you don't have a 01:15:44.390 --> 01:15:46.860 align:start position:0% commitment because now you don't have a problem<01:15:44.720> with<01:15:44.840> curve<01:15:45.020> cycles<01:15:45.470> for<01:15:45.790> sarsen 01:15:46.860 --> 01:15:46.870 align:start position:0% problem with curve cycles for sarsen 01:15:46.870 --> 01:15:49.690 align:start position:0% problem with curve cycles for sarsen like<01:15:47.870> that<01:15:48.080> very<01:15:48.230> friendly<01:15:48.590> curse<01:15:48.830> because 01:15:49.690 --> 01:15:49.700 align:start position:0% like that very friendly curse because 01:15:49.700 --> 01:15:52.150 align:start position:0% like that very friendly curse because here<01:15:50.180> you<01:15:50.330> everything<01:15:50.810> wants<01:15:50.960> to<01:15:51.170> build<01:15:51.410> as 01:15:52.150 --> 01:15:52.160 align:start position:0% here you everything wants to build as 01:15:52.160 --> 01:15:54.070 align:start position:0% here you everything wants to build as already<01:15:52.550> departed<01:15:52.820> for<01:15:53.180> fill<01:15:53.450> the<01:15:53.570> sky<01:15:53.780> -<01:15:53.840> in 01:15:54.070 --> 01:15:54.080 align:start position:0% already departed for fill the sky - in 01:15:54.080 --> 01:15:57.120 align:start position:0% already departed for fill the sky - in DC<01:15:54.230> -<01:15:54.410> which<01:15:54.560> is<01:15:54.680> already<01:15:54.890> a<01:15:55.040> requirement<01:15:55.580> for 01:15:57.120 --> 01:15:57.130 align:start position:0% DC - which is already a requirement for 01:15:57.130 --> 01:16:00.340 align:start position:0% DC - which is already a requirement for every<01:15:58.130> scene<01:15:58.370> for<01:15:58.790> polynomial<01:15:59.750> relationship 01:16:00.340 --> 01:16:00.350 align:start position:0% every scene for polynomial relationship 01:16:00.350 --> 01:16:01.930 align:start position:0% every scene for polynomial relationship and<01:16:00.560> this<01:16:00.740> approach<01:16:00.950> systems<01:16:01.430> over<01:16:01.910> a 01:16:01.930 --> 01:16:01.940 align:start position:0% and this approach systems over a 01:16:01.940 --> 01:16:08.070 align:start position:0% and this approach systems over a parameter<01:16:05.320> what<01:16:06.320> do<01:16:06.380> you<01:16:06.440> mean<01:16:06.590> it<01:16:06.740> does<01:16:07.250> been 01:16:08.070 --> 01:16:08.080 align:start position:0% parameter what do you mean it does been 01:16:08.080 --> 01:16:10.390 align:start position:0% parameter what do you mean it does been just<01:16:09.080> rented<01:16:09.470> means<01:16:09.650> you<01:16:09.770> don't<01:16:09.890> even<01:16:10.100> trust 01:16:10.390 --> 01:16:10.400 align:start position:0% just rented means you don't even trust 01:16:10.400 --> 01:16:12.880 align:start position:0% just rented means you don't even trust setup<01:16:10.850> then<01:16:11.540> four<01:16:11.930> key<01:16:12.110> commitments<01:16:12.500> of<01:16:12.860> the 01:16:12.880 --> 01:16:12.890 align:start position:0% setup then four key commitments of the 01:16:12.890 --> 01:16:13.480 align:start position:0% setup then four key commitments of the curve 01:16:13.480 --> 01:16:13.490 align:start position:0% curve 01:16:13.490 --> 01:16:17.650 align:start position:0% curve yeah<01:16:14.090> well<01:16:14.840> key<01:16:15.380> commitments<01:16:16.150> so<01:16:17.150> small<01:16:17.510> is 01:16:17.650 --> 01:16:17.660 align:start position:0% yeah well key commitments so small is 01:16:17.660 --> 01:16:20.560 align:start position:0% yeah well key commitments so small is outreach<01:16:18.080> the<01:16:18.170> unknown<01:16:18.650> so<01:16:19.430> entry<01:16:20.060> to<01:16:20.120> deserve 01:16:20.560 --> 01:16:20.570 align:start position:0% outreach the unknown so entry to deserve 01:16:20.570 --> 01:16:22.660 align:start position:0% outreach the unknown so entry to deserve an<01:16:20.810> agreeable<01:16:21.200> so<01:16:21.830> you<01:16:22.160> have<01:16:22.340> to<01:16:22.460> produce 01:16:22.660 --> 01:16:22.670 align:start position:0% an agreeable so you have to produce 01:16:22.670 --> 01:16:25.300 align:start position:0% an agreeable so you have to produce yourself<01:16:23.210> out<01:16:23.360> there<01:16:24.020> are<01:16:24.140> wait<01:16:24.350> I'm<01:16:24.620> not<01:16:25.070> we 01:16:25.300 --> 01:16:25.310 align:start position:0% yourself out there are wait I'm not we 01:16:25.310 --> 01:16:26.650 align:start position:0% yourself out there are wait I'm not we know<01:16:25.430> there<01:16:25.760> are<01:16:25.850> ways<01:16:26.030> and<01:16:26.090> efficient 01:16:26.650 --> 01:16:26.660 align:start position:0% know there are ways and efficient 01:16:26.660 --> 01:16:27.570 align:start position:0% know there are ways and efficient ceremonies 01:16:27.570 --> 01:16:27.580 align:start position:0% ceremonies 01:16:27.580 --> 01:16:30.480 align:start position:0% ceremonies uses<01:16:28.090> and<01:16:28.780> it's<01:16:29.110> still<01:16:29.320> commercial<01:16:30.010> it's<01:16:30.340> not 01:16:30.480 --> 01:16:30.490 align:start position:0% uses and it's still commercial it's not 01:16:30.490 --> 01:16:32.310 align:start position:0% uses and it's still commercial it's not per<01:16:30.700> circuit<01:16:30.940> facets<01:16:31.510> but<01:16:31.720> because<01:16:32.140> there's 01:16:32.310 --> 01:16:32.320 align:start position:0% per circuit facets but because there's 01:16:32.320 --> 01:16:33.930 align:start position:0% per circuit facets but because there's only<01:16:32.440> can<01:16:32.710> you<01:16:32.770> come<01:16:33.100> in<01:16:33.190> with<01:16:33.310> this<01:16:33.430> universe 01:16:33.930 --> 01:16:33.940 align:start position:0% only can you come in with this universe 01:16:33.940 --> 01:16:42.800 align:start position:0% only can you come in with this universe on<01:16:34.470> it<01:16:35.470> just<01:16:35.620> requires 01:16:42.800 --> 01:16:42.810 align:start position:0% 01:16:42.810 --> 01:16:45.510 align:start position:0% it's<01:16:43.810> linear<01:16:44.200> in<01:16:44.230> the<01:16:44.350> size<01:16:44.530> of<01:16:44.770> the<01:16:44.830> circle<01:16:45.190> so 01:16:45.510 --> 01:16:45.520 align:start position:0% it's linear in the size of the circle so 01:16:45.520 --> 01:16:47.820 align:start position:0% it's linear in the size of the circle so if<01:16:46.120> you<01:16:46.180> want<01:16:46.360> to<01:16:46.450> do<01:16:46.570> a<01:16:46.600> really<01:16:47.170> huge<01:16:47.410> circuit 01:16:47.820 --> 01:16:47.830 align:start position:0% if you want to do a really huge circuit 01:16:47.830 --> 01:16:50.460 align:start position:0% if you want to do a really huge circuit like<01:16:48.070> I'm<01:16:48.370> able<01:16:48.520> to<01:16:48.840> for<01:16:49.840> all<01:16:50.200> these 01:16:50.460 --> 01:16:50.470 align:start position:0% like I'm able to for all these 01:16:50.470 --> 01:16:58.050 align:start position:0% like I'm able to for all these parameters<01:16:54.840> the<01:16:55.840> constants<01:16:56.380> I<01:16:56.470> said<01:16:57.060> yeah 01:16:58.050 --> 01:16:58.060 align:start position:0% parameters the constants I said yeah 01:16:58.060 --> 01:17:02.370 align:start position:0% parameters the constants I said yeah well<01:16:58.690> just<01:16:59.020> for<01:16:59.170> simple<01:17:00.130> means<01:17:00.820> well<01:17:01.750> now<01:17:02.320> you 01:17:02.370 --> 01:17:02.380 align:start position:0% well just for simple means well now you 01:17:02.380 --> 01:17:04.020 align:start position:0% well just for simple means well now you have<01:17:02.530> a<01:17:02.740> freedom<01:17:02.950> of<01:17:03.130> choice<01:17:03.370> or<01:17:03.520> to<01:17:03.640> fill<01:17:03.820> so 01:17:04.020 --> 01:17:04.030 align:start position:0% have a freedom of choice or to fill so 01:17:04.030 --> 01:17:05.760 align:start position:0% have a freedom of choice or to fill so you<01:17:04.090> can<01:17:04.240> get<01:17:04.390> your<01:17:04.540> multiple<01:17:04.900> domain<01:17:05.440> of<01:17:05.590> the 01:17:05.760 --> 01:17:05.770 align:start position:0% you can get your multiple domain of the 01:17:05.770 --> 01:17:08.310 align:start position:0% you can get your multiple domain of the enormous<01:17:06.490> enormous<01:17:07.030> size<01:17:07.420> after<01:17:07.750> some<01:17:08.080> limit 01:17:08.310 --> 01:17:08.320 align:start position:0% enormous enormous size after some limit 01:17:08.320 --> 01:17:10.350 align:start position:0% enormous enormous size after some limit of<01:17:08.410> course<01:17:08.620> but<01:17:09.250> here<01:17:09.760> is<01:17:09.850> there<01:17:10.030> as<01:17:10.150> well 01:17:10.350 --> 01:17:10.360 align:start position:0% of course but here is there as well 01:17:10.360 --> 01:17:12.240 align:start position:0% of course but here is there as well through<01:17:10.720> certainly<01:17:11.290> is<01:17:11.350> a<01:17:11.440> practical<01:17:11.800> limit 01:17:12.240 --> 01:17:12.250 align:start position:0% through certainly is a practical limit 01:17:12.250 --> 01:17:14.370 align:start position:0% through certainly is a practical limit on<01:17:12.370> the<01:17:12.490> size<01:17:12.670> of<01:17:12.910> the<01:17:13.030> key<01:17:13.210> commitment<01:17:13.780> or<01:17:13.930> oil 01:17:14.370 --> 01:17:14.380 align:start position:0% on the size of the key commitment or oil 01:17:14.380 --> 01:17:16.290 align:start position:0% on the size of the key commitment or oil to<01:17:14.440> a<01:17:14.590> chicken<01:17:14.950> to<01:17:15.040> me<01:17:15.130> most<01:17:15.700> in<01:17:15.850> terms<01:17:15.970> of<01:17:16.180> the 01:17:16.290 --> 01:17:16.300 align:start position:0% to a chicken to me most in terms of the 01:17:16.300 --> 01:17:20.610 align:start position:0% to a chicken to me most in terms of the storage<01:17:16.690> is<01:17:16.840> a<01:17:16.870> parameter<01:17:17.140> and<01:17:17.820> if<01:17:18.820> your<01:17:19.620> penis 01:17:20.610 --> 01:17:20.620 align:start position:0% storage is a parameter and if your penis 01:17:20.620 --> 01:17:22.950 align:start position:0% storage is a parameter and if your penis in<01:17:21.340> a<01:17:21.520> framework<01:17:21.790> example<01:17:22.570> of<01:17:22.690> metal<01:17:22.870> of 01:17:22.950 --> 01:17:22.960 align:start position:0% in a framework example of metal of 01:17:22.960 --> 01:17:25.680 align:start position:0% in a framework example of metal of relationships<01:17:23.970> usually<01:17:24.970> you<01:17:25.270> also<01:17:25.420> found 01:17:25.680 --> 01:17:25.690 align:start position:0% relationships usually you also found 01:17:25.690 --> 01:17:28.200 align:start position:0% relationships usually you also found advisor<01:17:26.280> multi<01:17:27.280> could<01:17:27.430> give<01:17:27.610> several<01:17:27.820> sites 01:17:28.200 --> 01:17:28.210 align:start position:0% advisor multi could give several sites 01:17:28.210 --> 01:17:29.910 align:start position:0% advisor multi could give several sites like<01:17:28.450> for<01:17:28.840> a<01:17:28.870> number<01:17:29.140> of<01:17:29.200> recipients<01:17:29.770> so 01:17:29.910 --> 01:17:29.920 align:start position:0% like for a number of recipients so 01:17:29.920 --> 01:17:33.810 align:start position:0% like for a number of recipients so totally<01:17:30.330> fine<01:17:31.330> by<01:17:31.840> the<01:17:31.900> way<01:17:32.280> human<01:17:33.280> place<01:17:33.520> kid 01:17:33.810 --> 01:17:33.820 align:start position:0% totally fine by the way human place kid 01:17:33.820 --> 01:17:36.170 align:start position:0% totally fine by the way human place kid commitment<01:17:34.330> to<01:17:34.390> even<01:17:34.660> born<01:17:35.050> like<01:17:35.410> systems<01:17:35.860> by 01:17:36.170 --> 01:17:36.180 align:start position:0% commitment to even born like systems by 01:17:36.180 --> 01:17:40.160 align:start position:0% commitment to even born like systems by darkness<01:17:38.070> but<01:17:39.070> to<01:17:39.130> the<01:17:39.280> same<01:17:39.430> thing 01:17:40.160 --> 01:17:40.170 align:start position:0% darkness but to the same thing 01:17:40.170 --> 01:17:42.840 align:start position:0% darkness but to the same thing yes<01:17:41.170> because<01:17:41.710> its<01:17:41.980> commitment<01:17:42.370> coming<01:17:42.670> its 01:17:42.840 --> 01:17:42.850 align:start position:0% yes because its commitment coming its 01:17:42.850 --> 01:17:45.510 align:start position:0% yes because its commitment coming its commitments<01:17:43.510> team<01:17:43.780> service<01:17:44.170> and<01:17:44.440> for<01:17:45.190> all<01:17:45.400> the 01:17:45.510 --> 01:17:45.520 align:start position:0% commitments team service and for all the 01:17:45.520 --> 01:17:48.270 align:start position:0% commitments team service and for all the depends<01:17:45.940> on<01:17:46.090> accessibility<01:17:47.020> if<01:17:47.650> you<01:17:47.800> take<01:17:47.980> 100 01:17:48.270 --> 01:17:48.280 align:start position:0% depends on accessibility if you take 100 01:17:48.280 --> 01:17:50.790 align:start position:0% depends on accessibility if you take 100 beliefs<01:17:48.850> with<01:17:49.090> another<01:17:49.390> so<01:17:50.170> it's<01:17:50.410> just<01:17:50.680> a 01:17:50.790 --> 01:17:50.800 align:start position:0% beliefs with another so it's just a 01:17:50.800 --> 01:17:53.970 align:start position:0% beliefs with another so it's just a retinal<01:17:51.130> trace<01:17:51.340> now<01:17:52.110> it<01:17:53.110> just<01:17:53.170> should<01:17:53.530> be<01:17:53.620> 16 01:17:53.970 --> 01:17:53.980 align:start position:0% retinal trace now it just should be 16 01:17:53.980 --> 01:17:55.640 align:start position:0% retinal trace now it just should be 16 if<01:17:54.100> you<01:17:54.220> want<01:17:54.400> to<01:17:54.460> work<01:17:54.640> with<01:17:54.670> at<01:17:54.880> least<01:17:55.150> was 01:17:55.640 --> 01:17:55.650 align:start position:0% if you want to work with at least was 01:17:55.650 --> 01:17:57.990 align:start position:0% if you want to work with at least was was<01:17:56.650> the<01:17:56.770> Syrian<01:17:57.070> smart<01:17:57.310> contract<01:17:57.670> this<01:17:57.760> great 01:17:57.990 --> 01:17:58.000 align:start position:0% was the Syrian smart contract this great 01:17:58.000 --> 01:18:05.490 align:start position:0% was the Syrian smart contract this great fire<01:18:01.020> yes<01:18:03.210> there<01:18:04.210> was<01:18:04.270> an<01:18:04.420> idea<01:18:04.720> of<01:18:04.840> like<01:18:05.080> for 01:18:05.490 --> 01:18:05.500 align:start position:0% fire yes there was an idea of like for 01:18:05.500 --> 01:18:08.560 align:start position:0% fire yes there was an idea of like for the<01:18:05.590> proof<01:18:05.800> sizes 01:18:08.560 --> 01:18:08.570 align:start position:0% 01:18:08.570 --> 01:18:10.630 align:start position:0% yeah<01:18:08.900> for<01:18:09.260> original<01:18:09.920> commitment<01:18:10.220> scheme 01:18:10.630 --> 01:18:10.640 align:start position:0% yeah for original commitment scheme 01:18:10.640 --> 01:18:14.320 align:start position:0% yeah for original commitment scheme where<01:18:11.450> we<01:18:11.480> wouldn't<01:18:11.990> allow<01:18:12.880> where<01:18:13.880> we<01:18:14.060> would 01:18:14.320 --> 01:18:14.330 align:start position:0% where we wouldn't allow where we would 01:18:14.330 --> 01:18:17.110 align:start position:0% where we wouldn't allow where we would require<01:18:14.660> some<01:18:14.900> uniqueness<01:18:15.140> I<01:18:16.040> see<01:18:16.520> estimated 01:18:17.110 --> 01:18:17.120 align:start position:0% require some uniqueness I see estimated 01:18:17.120 --> 01:18:20.650 align:start position:0% require some uniqueness I see estimated for<01:18:17.360> 228<01:18:18.260> :<01:18:18.650> a<01:18:18.740> role<01:18:18.920> for<01:18:19.070> some<01:18:19.220> types<01:18:19.460> 16<01:18:20.000> 80 01:18:20.650 --> 01:18:20.660 align:start position:0% for 228 : a role for some types 16 80 01:18:20.660 --> 01:18:24.970 align:start position:0% for 228 : a role for some types 16 80 kilobytes<01:18:21.670> without<01:18:22.670> some<01:18:23.980> strong 01:18:24.970 --> 01:18:24.980 align:start position:0% kilobytes without some strong 01:18:24.980 --> 01:18:30.670 align:start position:0% kilobytes without some strong optimizations<01:18:25.700> for<01:18:27.280> relax<01:18:28.280> brother<01:18:29.650> for<01:18:30.650> a 01:18:30.670 --> 01:18:30.680 align:start position:0% optimizations for relax brother for a 01:18:30.680 --> 01:18:32.740 align:start position:0% optimizations for relax brother for a unique<01:18:30.980> liquid<01:18:31.280> in<01:18:31.400> Vegas<01:18:31.750> restrictions 01:18:32.740 --> 01:18:32.750 align:start position:0% unique liquid in Vegas restrictions 01:18:32.750 --> 01:18:34.960 align:start position:0% unique liquid in Vegas restrictions should<01:18:32.810> be<01:18:33.110> 68<01:18:33.890> in<01:18:34.190> a<01:18:34.310> kind<01:18:34.550> of<01:18:34.610> worst<01:18:34.850> case 01:18:34.960 --> 01:18:34.970 align:start position:0% should be 68 in a kind of worst case 01:18:34.970 --> 01:18:37.450 align:start position:0% should be 68 in a kind of worst case without<01:18:35.300> documentation<01:18:35.900> I<01:18:36.290> cannot<01:18:37.250> give<01:18:37.430> a 01:18:37.450 --> 01:18:37.460 align:start position:0% without documentation I cannot give a 01:18:37.460 --> 01:18:38.830 align:start position:0% without documentation I cannot give a number<01:18:37.610> of<01:18:37.820> a<01:18:37.850> septum<01:18:38.150> ization<01:18:38.390> because<01:18:38.750> I 01:18:38.830 --> 01:18:38.840 align:start position:0% number of a septum ization because I 01:18:38.840 --> 01:18:43.530 align:start position:0% number of a septum ization because I kept<01:18:39.140> trying<01:18:39.290> to<01:18:39.850> imitate<01:18:41.350> yeah<01:18:42.350> for 01:18:43.530 --> 01:18:43.540 align:start position:0% kept trying to imitate yeah for 01:18:43.540 --> 01:18:47.010 align:start position:0% kept trying to imitate yeah for indication<01:18:44.540> if<01:18:44.780> we<01:18:44.990> can<01:18:45.140> use<01:18:45.350> this<01:18:45.500> to<01:18:45.710> request 01:18:47.010 --> 01:18:47.020 align:start position:0% indication if we can use this to request 01:18:47.020 --> 01:18:49.660 align:start position:0% indication if we can use this to request evaluation<01:18:48.020> scheme<01:18:48.410> for<01:18:49.010> set<01:18:49.310> up<01:18:49.430> along 01:18:49.660 --> 01:18:49.670 align:start position:0% evaluation scheme for set up along 01:18:49.670 --> 01:18:52.210 align:start position:0% evaluation scheme for set up along normals<01:18:50.000> it<01:18:50.450> should<01:18:50.690> be<01:18:50.810> reused<01:18:51.230> like<01:18:51.560> five<01:18:52.010> to 01:18:52.210 --> 01:18:52.220 align:start position:0% normals it should be reused like five to 01:18:52.220 --> 01:18:56.200 align:start position:0% normals it should be reused like five to six<01:18:52.430> times<01:18:54.250> 20<01:18:55.250> kilobytes<01:18:55.700> limit<01:18:56.030> without 01:18:56.200 --> 01:18:56.210 align:start position:0% six times 20 kilobytes limit without 01:18:56.210 --> 01:18:58.360 align:start position:0% six times 20 kilobytes limit without optimization<01:18:57.020> by<01:18:57.530> the<01:18:57.590> way<01:18:57.740> maybe<01:18:57.980> there<01:18:58.250> was 01:18:58.360 --> 01:18:58.370 align:start position:0% optimization by the way maybe there was 01:18:58.370 --> 01:19:03.160 align:start position:0% optimization by the way maybe there was even<01:18:58.790> no<01:18:58.940> need<01:18:58.970> to<01:18:59.750> find<01:19:00.130> such<01:19:01.130> points<01:19:01.900> set<01:19:02.900> or 01:19:03.160 --> 01:19:03.170 align:start position:0% even no need to find such points set or 01:19:03.170 --> 01:19:06.010 align:start position:0% even no need to find such points set or ablation<01:19:03.770> schemes<01:19:04.040> we<01:19:04.700> maybe<01:19:05.390> we<01:19:05.660> may<01:19:05.780> just 01:19:06.010 --> 01:19:06.020 align:start position:0% ablation schemes we maybe we may just 01:19:06.020 --> 01:19:09.660 align:start position:0% ablation schemes we maybe we may just say<01:19:06.260> that<01:19:07.010> this<01:19:07.880> is<01:19:07.940> kind<01:19:08.510> of<01:19:08.720> swansea 01:19:09.660 --> 01:19:09.670 align:start position:0% say that this is kind of swansea 01:19:09.670 --> 01:19:12.190 align:start position:0% say that this is kind of swansea impossible<01:19:10.670> suits<01:19:10.850> the<01:19:11.210> set<01:19:11.390> up<01:19:11.510> a<01:19:11.630> transfer 01:19:12.190 --> 01:19:12.200 align:start position:0% impossible suits the set up a transfer 01:19:12.200 --> 01:19:18.610 align:start position:0% impossible suits the set up a transfer ability<01:19:12.470> argument<01:19:13.070> here<01:19:16.870> on<01:19:17.870> this<01:19:18.050> side<01:19:18.320> for 01:19:18.610 --> 01:19:18.620 align:start position:0% ability argument here on this side for 01:19:18.620 --> 01:19:19.709 align:start position:0% ability argument here on this side for Allah 01:19:19.709 --> 01:19:19.719 align:start position:0% Allah 01:19:19.719 --> 01:19:23.459 align:start position:0% Allah right<01:19:20.550> for<01:19:21.550> recursion<01:19:22.030> there's<01:19:22.900> only<01:19:23.050> six<01:19:23.349> it 01:19:23.459 --> 01:19:23.469 align:start position:0% right for recursion there's only six it 01:19:23.469 --> 01:19:27.060 align:start position:0% right for recursion there's only six it matters<01:19:23.860> is<01:19:24.249> this<01:19:25.440> circuit<01:19:26.440> size<01:19:26.650> if<01:19:26.889> you<01:19:27.039> have 01:19:27.060 --> 01:19:27.070 align:start position:0% matters is this circuit size if you have 01:19:27.070 --> 01:19:30.299 align:start position:0% matters is this circuit size if you have a<01:19:27.219> plastic<01:19:27.460> very<01:19:27.789> fire<01:19:28.320> biggest<01:19:29.320> with<01:19:29.800> it<01:19:30.039> it's 01:19:30.299 --> 01:19:30.309 align:start position:0% a plastic very fire biggest with it it's 01:19:30.309 --> 01:19:32.430 align:start position:0% a plastic very fire biggest with it it's only<01:19:30.610> staffers<01:19:31.150> will<01:19:31.329> be<01:19:31.479> publicly<01:19:31.960> verified 01:19:32.430 --> 01:19:32.440 align:start position:0% only staffers will be publicly verified 01:19:32.440 --> 01:19:34.680 align:start position:0% only staffers will be publicly verified for<01:19:33.039> everything<01:19:33.489> else<01:19:33.610> you<01:19:33.760> have<01:19:33.820> your<01:19:34.239> pro 01:19:34.680 --> 01:19:34.690 align:start position:0% for everything else you have your pro 01:19:34.690 --> 01:19:37.319 align:start position:0% for everything else you have your pro sizes<01:19:35.139> in<01:19:35.469> within<01:19:35.860> the<01:19:36.039> private<01:19:36.429> living<01:19:36.699> so 01:19:37.319 --> 01:19:37.329 align:start position:0% sizes in within the private living so 01:19:37.329 --> 01:19:39.600 align:start position:0% sizes in within the private living so well<01:19:37.929> it's<01:19:38.110> very<01:19:38.320> fire<01:19:38.499> serving<01:19:38.829> it<01:19:38.949> will 01:19:39.600 --> 01:19:39.610 align:start position:0% well it's very fire serving it will 01:19:39.610 --> 01:19:41.129 align:start position:0% well it's very fire serving it will depends<01:19:39.999> of<01:19:40.090> them<01:19:40.239> choose<01:19:40.690> the<01:19:40.960> cache 01:19:41.129 --> 01:19:41.139 align:start position:0% depends of them choose the cache 01:19:41.139 --> 01:19:42.629 align:start position:0% depends of them choose the cache functional<01:19:41.619> so<01:19:41.800> like<01:19:42.070> how<01:19:42.249> you<01:19:42.309> make<01:19:42.550> the 01:19:42.629 --> 01:19:42.639 align:start position:0% functional so like how you make the 01:19:42.639 --> 01:19:48.120 align:start position:0% functional so like how you make the transcript<01:19:43.150> or<01:19:43.829> principle<01:19:44.829> procedure<01:19:45.159> but<01:19:47.130> by 01:19:48.120 --> 01:19:48.130 align:start position:0% transcript or principle procedure but by 01:19:48.130 --> 01:19:52.319 align:start position:0% transcript or principle procedure but by assuming<01:19:48.400> like<01:19:49.019> two<01:19:50.019> twenty<01:19:50.530> three<01:19:51.030> to<01:19:52.030> four 01:19:52.319 --> 01:19:52.329 align:start position:0% assuming like two twenty three to four 01:19:52.329 --> 01:19:55.169 align:start position:0% assuming like two twenty three to four pull<01:19:52.840> internal<01:19:53.170> what<01:19:53.729> it<01:19:54.729> should<01:19:54.880> be<01:19:55.030> what 01:19:55.169 --> 01:19:55.179 align:start position:0% pull internal what it should be what 01:19:55.179 --> 01:19:57.870 align:start position:0% pull internal what it should be what smaller<01:19:55.449> well<01:19:56.429> recursion<01:19:57.429> gives<01:19:57.610> you<01:19:57.699> such 01:19:57.870 --> 01:19:57.880 align:start position:0% smaller well recursion gives you such 01:19:57.880 --> 01:20:06.029 align:start position:0% smaller well recursion gives you such trade-off<01:19:58.239> between<01:19:58.389> society<01:20:04.889> okay<01:20:05.889> I<01:20:05.920> think 01:20:06.029 --> 01:20:06.039 align:start position:0% trade-off between society okay I think 01:20:06.039 --> 01:20:08.910 align:start position:0% trade-off between society okay I think it's<01:20:06.280> just<01:20:06.519> time<01:20:07.510> but<01:20:08.050> because<01:20:08.349> it<01:20:08.469> was<01:20:08.679> a<01:20:08.710> long 01:20:08.910 --> 01:20:08.920 align:start position:0% it's just time but because it was a long 01:20:08.920 --> 01:20:14.770 align:start position:0% it's just time but because it was a long session<01:20:09.159> you<01:20:09.400> should<01:20:09.610> cover<01:20:09.940> your<01:20:10.150> brain 01:20:14.770 --> 01:20:14.780 align:start position:0% 01:20:14.780 --> 01:20:21.069 align:start position:0% [Applause]