WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.740 align:start position:0% [Applause] 00:00:10.740 --> 00:00:10.750 align:start position:0% 00:00:10.750 --> 00:00:14.200 align:start position:0% yeah<00:00:11.780> so<00:00:12.050> thanks<00:00:12.710> for<00:00:13.070> going<00:00:13.700> to<00:00:13.820> be<00:00:13.969> another 00:00:14.200 --> 00:00:14.210 align:start position:0% yeah so thanks for going to be another 00:00:14.210 --> 00:00:17.650 align:start position:0% yeah so thanks for going to be another the<00:00:14.750> 10th<00:00:14.960> of<00:00:15.200> a<00:00:15.350> long<00:00:15.559> day<00:00:15.740> so<00:00:16.219> I'm<00:00:17.060> upset<00:00:17.450> I'm 00:00:17.650 --> 00:00:17.660 align:start position:0% the 10th of a long day so I'm upset I'm 00:00:17.660 --> 00:00:19.359 align:start position:0% the 10th of a long day so I'm upset I'm the<00:00:17.720> CTO<00:00:17.900> of<00:00:18.110> the<00:00:18.349> a<00:00:18.380> secret<00:00:18.830> but<00:00:19.070> we<00:00:19.189> are<00:00:19.340> a 00:00:19.359 --> 00:00:19.369 align:start position:0% the CTO of the a secret but we are a 00:00:19.369 --> 00:00:23.170 align:start position:0% the CTO of the a secret but we are a very<00:00:19.700> soon<00:00:21.010> solution<00:00:22.010> for<00:00:22.310> theorems<00:00:22.790> will<00:00:23.029> be 00:00:23.170 --> 00:00:23.180 align:start position:0% very soon solution for theorems will be 00:00:23.180 --> 00:00:25.030 align:start position:0% very soon solution for theorems will be for<00:00:23.720> the<00:00:23.810> tooling<00:00:24.110> resources<00:00:24.590> that<00:00:24.740> may<00:00:24.860> cause 00:00:25.030 --> 00:00:25.040 align:start position:0% for the tooling resources that may cause 00:00:25.040 --> 00:00:26.920 align:start position:0% for the tooling resources that may cause people<00:00:25.189> to<00:00:25.400> go<00:00:25.520> private<00:00:25.790> a<00:00:26.240> small<00:00:26.539> types<00:00:26.840> of 00:00:26.920 --> 00:00:26.930 align:start position:0% people to go private a small types of 00:00:26.930 --> 00:00:28.960 align:start position:0% people to go private a small types of private<00:00:27.110> records<00:00:27.470> and<00:00:28.130> I<00:00:28.369> want<00:00:28.610> to<00:00:28.699> talk<00:00:28.850> about 00:00:28.960 --> 00:00:28.970 align:start position:0% private records and I want to talk about 00:00:28.970 --> 00:00:33.130 align:start position:0% private records and I want to talk about today<00:00:29.330> is<00:00:29.720> a<00:00:30.350> new<00:00:30.859> piece<00:00:31.760> of<00:00:31.910> technology<00:00:32.239> that 00:00:33.130 --> 00:00:33.140 align:start position:0% today is a new piece of technology that 00:00:33.140 --> 00:00:34.630 align:start position:0% today is a new piece of technology that we<00:00:33.230> developed<00:00:33.590> in<00:00:33.800> collaboration<00:00:34.100> in 00:00:34.630 --> 00:00:34.640 align:start position:0% we developed in collaboration in 00:00:34.640 --> 00:00:41.350 align:start position:0% we developed in collaboration in clinical<00:00:35.000> labs<00:00:35.210> a<00:00:35.809> new<00:00:36.199> universal<00:00:39.340> way<00:00:40.360> as 00:00:41.350 --> 00:00:41.360 align:start position:0% clinical labs a new universal way as 00:00:41.360 --> 00:00:43.630 align:start position:0% clinical labs a new universal way as much<00:00:41.510> as<00:00:41.570> its<00:00:41.870> width<00:00:42.019> around<00:00:42.199> your<00:00:42.500> oh<00:00:42.800> thanks 00:00:43.630 --> 00:00:43.640 align:start position:0% much as its width around your oh thanks 00:00:43.640 --> 00:00:51.160 align:start position:0% much as its width around your oh thanks man<00:00:43.790> yeah<00:00:43.970> okay<00:00:45.280> so<00:00:49.600> kind<00:00:50.600> of<00:00:50.750> high<00:00:50.870> level<00:00:50.900> I 00:00:51.160 --> 00:00:51.170 align:start position:0% man yeah okay so kind of high level I 00:00:51.170 --> 00:00:52.450 align:start position:0% man yeah okay so kind of high level I got<00:00:51.320> to<00:00:51.500> kind<00:00:51.650> of<00:00:51.769> skim<00:00:52.040> in<00:00:52.159> a<00:00:52.190> bit<00:00:52.309> of<00:00:52.370> an 00:00:52.450 --> 00:00:52.460 align:start position:0% got to kind of skim in a bit of an 00:00:52.460 --> 00:00:54.130 align:start position:0% got to kind of skim in a bit of an interview<00:00:52.640> about<00:00:52.790> you<00:00:53.239> know<00:00:53.360> why<00:00:53.659> it's<00:00:53.839> not<00:00:53.900> to 00:00:54.130 --> 00:00:54.140 align:start position:0% interview about you know why it's not to 00:00:54.140 --> 00:00:55.030 align:start position:0% interview about you know why it's not to you<00:00:54.229> so<00:00:54.379> why<00:00:54.470> they're<00:00:54.589> important<00:00:54.920> we're 00:00:55.030 --> 00:00:55.040 align:start position:0% you so why they're important we're 00:00:55.040 --> 00:00:57.130 align:start position:0% you so why they're important we're trying<00:00:55.220> to<00:00:55.280> deal<00:00:55.400> with<00:00:55.430> them<00:00:55.690> and<00:00:56.690> then<00:00:56.900> go 00:00:57.130 --> 00:00:57.140 align:start position:0% trying to deal with them and then go 00:00:57.140 --> 00:00:59.430 align:start position:0% trying to deal with them and then go into<00:00:57.620> a<00:00:57.680> little<00:00:57.769> bit<00:00:57.890> about<00:00:58.100> into<00:00:58.970> a<00:00:59.000> rather 00:00:59.430 --> 00:00:59.440 align:start position:0% into a little bit about into a rather 00:00:59.440 --> 00:01:02.320 align:start position:0% into a little bit about into a rather low<00:01:00.440> level<00:01:00.710> dense<00:01:00.890> about<00:01:01.250> plop<00:01:01.549> this<00:01:01.850> universe 00:01:02.320 --> 00:01:02.330 align:start position:0% low level dense about plop this universe 00:01:02.330 --> 00:01:05.170 align:start position:0% low level dense about plop this universe as<00:01:02.420> long<00:01:02.570> inspected<00:01:03.170> and<00:01:03.860> try<00:01:04.280> and<00:01:04.489> I<00:01:04.729> guess 00:01:05.170 --> 00:01:05.180 align:start position:0% as long inspected and try and I guess 00:01:05.180 --> 00:01:09.940 align:start position:0% as long inspected and try and I guess dispel<00:01:05.720> some<00:01:06.170> of<00:01:06.229> the<00:01:08.409> some<00:01:09.409> of<00:01:09.440> the<00:01:09.590> mysticism 00:01:09.940 --> 00:01:09.950 align:start position:0% dispel some of the some of the mysticism 00:01:09.950 --> 00:01:12.789 align:start position:0% dispel some of the some of the mysticism behind<00:01:10.460> stocks<00:01:10.700> and<00:01:11.360> actually<00:01:11.799> provides 00:01:12.789 --> 00:01:12.799 align:start position:0% behind stocks and actually provides 00:01:12.799 --> 00:01:16.139 align:start position:0% behind stocks and actually provides insight<00:01:13.190> into<00:01:13.220> issues<00:01:13.729> by<00:01:13.880> how<00:01:14.359> they<00:01:14.479> work<00:01:15.130> so 00:01:16.139 --> 00:01:16.149 align:start position:0% insight into issues by how they work so 00:01:16.149 --> 00:01:18.399 align:start position:0% insight into issues by how they work so what's<00:01:17.149> the<00:01:17.450> fuss<00:01:17.659> about<00:01:17.689> stocks 00:01:18.399 --> 00:01:18.409 align:start position:0% what's the fuss about stocks 00:01:18.409 --> 00:01:21.130 align:start position:0% what's the fuss about stocks imagine<00:01:19.399> everyone<00:01:19.969> is<00:01:20.210> kind<00:01:20.509> of<00:01:20.630> relatively 00:01:21.130 --> 00:01:21.140 align:start position:0% imagine everyone is kind of relatively 00:01:21.140 --> 00:01:22.719 align:start position:0% imagine everyone is kind of relatively familiar<00:01:21.619> with<00:01:21.979> the<00:01:22.130> with<00:01:22.310> the<00:01:22.399> high<00:01:22.520> level 00:01:22.719 --> 00:01:22.729 align:start position:0% familiar with the with the high level 00:01:22.729 --> 00:01:25.539 align:start position:0% familiar with the with the high level stuff<00:01:22.880> that's<00:01:23.680> you<00:01:24.680> can<00:01:24.829> use<00:01:24.979> starts<00:01:25.369> to 00:01:25.539 --> 00:01:25.549 align:start position:0% stuff that's you can use starts to 00:01:25.549 --> 00:01:27.880 align:start position:0% stuff that's you can use starts to effectively<00:01:26.030> make<00:01:26.149> computation<00:01:27.109> free<00:01:27.710> of<00:01:27.829> a 00:01:27.880 --> 00:01:27.890 align:start position:0% effectively make computation free of a 00:01:27.890 --> 00:01:29.230 align:start position:0% effectively make computation free of a theory<00:01:28.189> why<00:01:28.399> just<00:01:28.609> having<00:01:28.820> a<00:01:28.880> proof<00:01:29.119> of 00:01:29.230 --> 00:01:29.240 align:start position:0% theory why just having a proof of 00:01:29.240 --> 00:01:30.550 align:start position:0% theory why just having a proof of computations<00:01:29.780> that<00:01:29.869> are<00:01:29.990> actually<00:01:30.259> requiring 00:01:30.550 --> 00:01:30.560 align:start position:0% computations that are actually requiring 00:01:30.560 --> 00:01:32.399 align:start position:0% computations that are actually requiring every<00:01:30.799> notes<00:01:30.979> to<00:01:31.219> perform<00:01:31.609> computation 00:01:32.399 --> 00:01:32.409 align:start position:0% every notes to perform computation 00:01:32.409 --> 00:01:36.160 align:start position:0% every notes to perform computation themselves<00:01:33.729> in<00:01:34.729> addition<00:01:35.210> to<00:01:35.270> that<00:01:35.420> we<00:01:35.719> had 00:01:36.160 --> 00:01:36.170 align:start position:0% themselves in addition to that we had 00:01:36.170 --> 00:01:39.010 align:start position:0% themselves in addition to that we had mercy<00:01:36.679> because<00:01:36.859> with<00:01:37.310> a<00:01:37.399> snug<00:01:38.060> you<00:01:38.450> can<00:01:38.689> hide 00:01:39.010 --> 00:01:39.020 align:start position:0% mercy because with a snug you can hide 00:01:39.020 --> 00:01:41.859 align:start position:0% mercy because with a snug you can hide the<00:01:39.200> improvements<00:01:39.859> to<00:01:40.009> your<00:01:40.039> proof<00:01:40.869> the 00:01:41.859 --> 00:01:41.869 align:start position:0% the improvements to your proof the 00:01:41.869 --> 00:01:43.390 align:start position:0% the improvements to your proof the apotheosis<00:01:42.350> of<00:01:42.740> this 00:01:43.390 --> 00:01:43.400 align:start position:0% apotheosis of this 00:01:43.400 --> 00:01:45.100 align:start position:0% apotheosis of this if<00:01:43.760> you<00:01:43.850> find<00:01:44.090> the<00:01:44.210> it<00:01:44.480> was<00:01:44.600> an<00:01:44.690> alpha<00:01:44.840> steel 00:01:45.100 --> 00:01:45.110 align:start position:0% if you find the it was an alpha steel 00:01:45.110 --> 00:01:46.540 align:start position:0% if you find the it was an alpha steel preview<00:01:45.470> but<00:01:45.860> also<00:01:45.980> if<00:01:46.190> you've<00:01:46.280> liked<00:01:46.430> the 00:01:46.540 --> 00:01:46.550 align:start position:0% preview but also if you've liked the 00:01:46.550 --> 00:01:47.800 align:start position:0% preview but also if you've liked the identities<00:01:47.000> of<00:01:47.030> the<00:01:47.210> people<00:01:47.240> sending 00:01:47.800 --> 00:01:47.810 align:start position:0% identities of the people sending 00:01:47.810 --> 00:01:49.540 align:start position:0% identities of the people sending transactions<00:01:48.290> and<00:01:48.590> if<00:01:48.950> you<00:01:49.070> hide<00:01:49.250> the<00:01:49.430> actual 00:01:49.540 --> 00:01:49.550 align:start position:0% transactions and if you hide the actual 00:01:49.550 --> 00:01:52.200 align:start position:0% transactions and if you hide the actual smart<00:01:50.060> contact<00:01:50.390> code<00:01:50.600> there's<00:01:50.840> been<00:01:50.990> executed 00:01:52.200 --> 00:01:52.210 align:start position:0% smart contact code there's been executed 00:01:52.210 --> 00:01:54.130 align:start position:0% smart contact code there's been executed unless<00:01:53.210> it<00:01:53.450> can<00:01:53.510> all<00:01:53.660> be<00:01:53.690> achieved<00:01:53.990> with 00:01:54.130 --> 00:01:54.140 align:start position:0% unless it can all be achieved with 00:01:54.140 --> 00:01:58.990 align:start position:0% unless it can all be achieved with varying<00:01:55.040> degrees<00:01:55.160> of<00:01:55.400> practicality<00:01:56.890> so<00:01:58.000> how 00:01:58.990 --> 00:01:59.000 align:start position:0% varying degrees of practicality so how 00:01:59.000 --> 00:02:00.840 align:start position:0% varying degrees of practicality so how does<00:01:59.060> pontifical<00:01:59.660> it's<00:02:00.230> been<00:02:00.380> a<00:02:00.410> rather<00:02:00.560> a 00:02:00.840 --> 00:02:00.850 align:start position:0% does pontifical it's been a rather a 00:02:00.850 --> 00:02:03.430 align:start position:0% does pontifical it's been a rather a snarky<00:02:01.850> summer<00:02:02.270> what<00:02:02.810> you<00:02:02.900> say<00:02:03.020> between<00:02:03.200> a<00:02:03.290> lot 00:02:03.430 --> 00:02:03.440 align:start position:0% snarky summer what you say between a lot 00:02:03.440 --> 00:02:04.840 align:start position:0% snarky summer what you say between a lot of<00:02:03.530> them<00:02:03.680> a<00:02:03.980> lot<00:02:04.100> of<00:02:04.370> a<00:02:04.520> lot<00:02:04.670> of<00:02:04.700> new 00:02:04.840 --> 00:02:04.850 align:start position:0% of them a lot of a lot of new 00:02:04.850 --> 00:02:06.870 align:start position:0% of them a lot of a lot of new technologies<00:02:05.270> that<00:02:05.300> have<00:02:05.600> been<00:02:05.690> put<00:02:05.930> out<00:02:06.020> and 00:02:06.870 --> 00:02:06.880 align:start position:0% technologies that have been put out and 00:02:06.880 --> 00:02:09.280 align:start position:0% technologies that have been put out and yeah<00:02:07.880> focus<00:02:08.240> upon<00:02:08.390> a<00:02:08.750> small<00:02:08.990> part<00:02:09.140> of<00:02:09.170> this 00:02:09.280 --> 00:02:09.290 align:start position:0% yeah focus upon a small part of this 00:02:09.290 --> 00:02:14.230 align:start position:0% yeah focus upon a small part of this landscape<00:02:10.160> of<00:02:10.610> tech<00:02:10.790> and<00:02:12.370> so<00:02:13.370> I<00:02:13.400> kind<00:02:13.850> of<00:02:13.880> want 00:02:14.230 --> 00:02:14.240 align:start position:0% landscape of tech and so I kind of want 00:02:14.240 --> 00:02:15.910 align:start position:0% landscape of tech and so I kind of want to<00:02:14.270> talk<00:02:14.450> about<00:02:14.540> yeah<00:02:15.200> so<00:02:15.440> the<00:02:15.560> intrusions 00:02:15.910 --> 00:02:15.920 align:start position:0% to talk about yeah so the intrusions 00:02:15.920 --> 00:02:17.440 align:start position:0% to talk about yeah so the intrusions behind<00:02:16.160> it<00:02:16.250> but<00:02:16.310> it<00:02:16.400> does<00:02:16.580> why<00:02:17.270> do<00:02:17.330> you<00:02:17.390> think 00:02:17.440 --> 00:02:17.450 align:start position:0% behind it but it does why do you think 00:02:17.450 --> 00:02:19.990 align:start position:0% behind it but it does why do you think is<00:02:17.570> useful<00:02:18.130> so<00:02:19.130> it's<00:02:19.400> the<00:02:19.460> universal<00:02:19.820> stock 00:02:19.990 --> 00:02:20.000 align:start position:0% is useful so it's the universal stock 00:02:20.000 --> 00:02:20.890 align:start position:0% is useful so it's the universal stock that<00:02:20.090> was<00:02:20.210> kind<00:02:20.390> of<00:02:20.420> designed<00:02:20.720> from<00:02:20.780> the 00:02:20.890 --> 00:02:20.900 align:start position:0% that was kind of designed from the 00:02:20.900 --> 00:02:22.540 align:start position:0% that was kind of designed from the ground<00:02:20.930> up<00:02:21.170> glass<00:02:21.230> to<00:02:21.590> be<00:02:21.710> viable<00:02:22.250> lot<00:02:22.460> of 00:02:22.540 --> 00:02:22.550 align:start position:0% ground up glass to be viable lot of 00:02:22.550 --> 00:02:24.610 align:start position:0% ground up glass to be viable lot of theory<00:02:22.820> but<00:02:22.940> by<00:02:23.030> that<00:02:23.150> I<00:02:23.300> mean<00:02:23.530> showing<00:02:24.530> that 00:02:24.610 --> 00:02:24.620 align:start position:0% theory but by that I mean showing that 00:02:24.620 --> 00:02:26.920 align:start position:0% theory but by that I mean showing that the<00:02:24.740> verification<00:02:24.950> run<00:02:25.790> time<00:02:26.030> was<00:02:26.660> fast 00:02:26.920 --> 00:02:26.930 align:start position:0% the verification run time was fast 00:02:26.930 --> 00:02:28.990 align:start position:0% the verification run time was fast enough<00:02:27.080> to<00:02:27.320> be<00:02:27.520> gasps<00:02:28.520> a<00:02:28.550> vintage<00:02:28.670> and 00:02:28.990 --> 00:02:29.000 align:start position:0% enough to be gasps a vintage and 00:02:29.000 --> 00:02:31.900 align:start position:0% enough to be gasps a vintage and ethereal<00:02:29.360> and<00:02:30.160> proves<00:02:31.160> to<00:02:31.310> be<00:02:31.340> a<00:02:31.430> destructive 00:02:31.900 --> 00:02:31.910 align:start position:0% ethereal and proves to be a destructive 00:02:31.910 --> 00:02:33.870 align:start position:0% ethereal and proves to be a destructive relatively<00:02:32.840> complicated<00:02:32.990> circuits<00:02:33.650> on 00:02:33.870 --> 00:02:33.880 align:start position:0% relatively complicated circuits on 00:02:33.880 --> 00:02:36.670 align:start position:0% relatively complicated circuits on average<00:02:34.880> can<00:02:35.120> seem<00:02:35.270> a<00:02:35.300> bit<00:02:35.390> hot<00:02:35.660> their<00:02:35.870> signals 00:02:36.670 --> 00:02:36.680 align:start position:0% average can seem a bit hot their signals 00:02:36.680 --> 00:02:39.700 align:start position:0% average can seem a bit hot their signals as<00:02:36.770> well<00:02:36.800> presently<00:02:38.260> consumer<00:02:39.260> grade<00:02:39.380> laptops 00:02:39.700 --> 00:02:39.710 align:start position:0% as well presently consumer grade laptops 00:02:39.710 --> 00:02:43.330 align:start position:0% as well presently consumer grade laptops basically<00:02:40.750> and<00:02:41.750> yes<00:02:41.990> inspired<00:02:42.440> by<00:02:42.680> its 00:02:43.330 --> 00:02:43.340 align:start position:0% basically and yes inspired by its 00:02:43.340 --> 00:02:45.700 align:start position:0% basically and yes inspired by its predecessor<00:02:43.520> sonic<00:02:44.510> like<00:02:45.350> the<00:02:45.470> first 00:02:45.700 --> 00:02:45.710 align:start position:0% predecessor sonic like the first 00:02:45.710 --> 00:02:47.880 align:start position:0% predecessor sonic like the first universe<00:02:46.070> or<00:02:46.190> something<00:02:46.310> what<00:02:46.850> that<00:02:47.000> was<00:02:47.150> a 00:02:47.880 --> 00:02:47.890 align:start position:0% universe or something what that was a 00:02:47.890 --> 00:02:50.979 align:start position:0% universe or something what that was a tactical<00:02:49.000> as<00:02:50.000> it<00:02:50.150> didn't<00:02:50.570> require<00:02:50.720> like<00:02:50.959> a 00:02:50.979 --> 00:02:50.989 align:start position:0% tactical as it didn't require like a 00:02:50.989 --> 00:02:53.500 align:start position:0% tactical as it didn't require like a quadratic<00:02:51.200> a<00:02:51.530> size<00:02:51.709> reference<00:02:51.890> tree<00:02:52.270> and<00:02:53.270> some 00:02:53.500 --> 00:02:53.510 align:start position:0% quadratic a size reference tree and some 00:02:53.510 --> 00:02:55.360 align:start position:0% quadratic a size reference tree and some and<00:02:53.750> you<00:02:54.350> know<00:02:54.470> if<00:02:54.709> J<00:02:54.860> different<00:02:55.130> fingers 00:02:55.360 --> 00:02:55.370 align:start position:0% and you know if J different fingers 00:02:55.370 --> 00:02:58.840 align:start position:0% and you know if J different fingers works<00:02:55.550> by<00:02:55.730> control<00:02:56.000> and<00:02:56.330> plan<00:02:56.810> so<00:02:57.850> we 00:02:58.840 --> 00:02:58.850 align:start position:0% works by control and plan so we 00:02:58.850 --> 00:03:00.430 align:start position:0% works by control and plan so we published<00:02:59.060> talk<00:02:59.570> about<00:02:59.810> one<00:02:59.989> well<00:03:00.140> half<00:03:00.320> a 00:03:00.430 --> 00:03:00.440 align:start position:0% published talk about one well half a 00:03:00.440 --> 00:03:01.810 align:start position:0% published talk about one well half a month<00:03:00.739> and<00:03:00.860> a<00:03:00.890> half<00:03:00.920> ago<00:03:01.100> and<00:03:01.400> we'd<00:03:01.700> be<00:03:01.790> very 00:03:01.810 --> 00:03:01.820 align:start position:0% month and a half ago and we'd be very 00:03:01.820 --> 00:03:05.830 align:start position:0% month and a half ago and we'd be very busy<00:03:02.239> building<00:03:02.510> implementation<00:03:03.350> of<00:03:03.910> a<00:03:04.910> proven 00:03:05.830 --> 00:03:05.840 align:start position:0% busy building implementation of a proven 00:03:05.840 --> 00:03:08.530 align:start position:0% busy building implementation of a proven verify<00:03:06.290> algorithm<00:03:07.160> this<00:03:07.370> is<00:03:07.520> also<00:03:07.700> very<00:03:07.970> very 00:03:08.530 --> 00:03:08.540 align:start position:0% verify algorithm this is also very very 00:03:08.540 --> 00:03:10.690 align:start position:0% verify algorithm this is also very very impressive<00:03:09.410> stuff<00:03:09.739> it's<00:03:09.980> in<00:03:10.070> an<00:03:10.160> advanced<00:03:10.550> my 00:03:10.690 --> 00:03:10.700 align:start position:0% impressive stuff it's in an advanced my 00:03:10.700 --> 00:03:13.690 align:start position:0% impressive stuff it's in an advanced my State<00:03:10.910> Department<00:03:11.900> so<00:03:12.860> this<00:03:13.010> is<00:03:13.130> over<00:03:13.280> the<00:03:13.400> BNT 00:03:13.690 --> 00:03:13.700 align:start position:0% State Department so this is over the BNT 00:03:13.700 --> 00:03:16.300 align:start position:0% State Department so this is over the BNT FIFO<00:03:14.030> curve<00:03:14.270> so<00:03:15.170> the<00:03:15.320> feather<00:03:15.500> if<00:03:15.950> there<00:03:16.160> has 00:03:16.300 --> 00:03:16.310 align:start position:0% FIFO curve so the feather if there has 00:03:16.310 --> 00:03:20.500 align:start position:0% FIFO curve so the feather if there has people<00:03:16.580> possible<00:03:17.140> and<00:03:18.700> the<00:03:19.700> relevant<00:03:20.360> graph 00:03:20.500 --> 00:03:20.510 align:start position:0% people possible and the relevant graph 00:03:20.510 --> 00:03:23.350 align:start position:0% people possible and the relevant graph is<00:03:20.630> the<00:03:20.750> top<00:03:20.930> left<00:03:21.140> this<00:03:21.739> is<00:03:21.920> the<00:03:22.550> certain 00:03:23.350 --> 00:03:23.360 align:start position:0% is the top left this is the certain 00:03:23.360 --> 00:03:24.580 align:start position:0% is the top left this is the certain times<00:03:23.570> for 00:03:24.580 --> 00:03:24.590 align:start position:0% times for 00:03:24.590 --> 00:03:27.700 align:start position:0% times for like<00:03:24.950> a<00:03:25.070> selection<00:03:25.640> for<00:03:26.440> cervix<00:03:27.440> but<00:03:27.530> very 00:03:27.700 --> 00:03:27.710 align:start position:0% like a selection for cervix but very 00:03:27.710 --> 00:03:30.670 align:start position:0% like a selection for cervix but very number<00:03:27.920> of<00:03:27.980> gates<00:03:28.190> and<00:03:28.400> I<00:03:29.270> guess<00:03:29.750> the<00:03:29.930> the<00:03:30.350> take 00:03:30.670 --> 00:03:30.680 align:start position:0% number of gates and I guess the the take 00:03:30.680 --> 00:03:32.230 align:start position:0% number of gates and I guess the the take away<00:03:30.800> this<00:03:30.950> is<00:03:31.130> that<00:03:31.280> there<00:03:31.670> were<00:03:31.790> many<00:03:31.970> gates 00:03:32.230 --> 00:03:32.240 align:start position:0% away this is that there were many gates 00:03:32.240 --> 00:03:35.950 align:start position:0% away this is that there were many gates a<00:03:32.510> pre-construction<00:03:33.290> on<00:03:33.800> like<00:03:34.760> a<00:03:34.790> my<00:03:35.210> service 00:03:35.950 --> 00:03:35.960 align:start position:0% a pre-construction on like a my service 00:03:35.960 --> 00:03:38.890 align:start position:0% a pre-construction on like a my service probe<00:03:36.200> is<00:03:36.350> under<00:03:36.950> 23<00:03:37.370> cents<00:03:37.700> and<00:03:37.850> when<00:03:38.720> you<00:03:38.810> get 00:03:38.890 --> 00:03:38.900 align:start position:0% probe is under 23 cents and when you get 00:03:38.900 --> 00:03:40.030 align:start position:0% probe is under 23 cents and when you get tons<00:03:39.080> of<00:03:39.170> things<00:03:39.260> a<00:03:39.380> particular<00:03:39.710> seventeen 00:03:40.030 --> 00:03:40.040 align:start position:0% tons of things a particular seventeen 00:03:40.040 --> 00:03:41.860 align:start position:0% tons of things a particular seventeen gates<00:03:40.250> the<00:03:40.940> group<00:03:41.090> instructions<00:03:41.480> on<00:03:41.720> three 00:03:41.860 --> 00:03:41.870 align:start position:0% gates the group instructions on three 00:03:41.870 --> 00:03:48.190 align:start position:0% gates the group instructions on three things<00:03:42.050> and<00:03:42.830> so<00:03:44.560> this<00:03:45.560> is<00:03:46.690> the<00:03:47.690> entire<00:03:47.900> movie 00:03:48.190 --> 00:03:48.200 align:start position:0% things and so this is the entire movie 00:03:48.200 --> 00:03:49.330 align:start position:0% things and so this is the entire movie nearly<00:03:48.470> means<00:03:48.620> the<00:03:48.709> synostosis<00:03:49.040> was 00:03:49.330 --> 00:03:49.340 align:start position:0% nearly means the synostosis was 00:03:49.340 --> 00:03:52.510 align:start position:0% nearly means the synostosis was practical<00:03:49.760> for<00:03:49.940> databases<00:03:50.600> on<00:03:51.170> a<00:03:51.200> theory<00:03:51.520> we 00:03:52.510 --> 00:03:52.520 align:start position:0% practical for databases on a theory we 00:03:52.520 --> 00:03:54.880 align:start position:0% practical for databases on a theory we estimate<00:03:53.030> that<00:03:53.090> typical<00:03:53.840> like<00:03:54.530> a<00:03:54.560> private 00:03:54.880 --> 00:03:54.890 align:start position:0% estimate that typical like a private 00:03:54.890 --> 00:03:56.230 align:start position:0% estimate that typical like a private transaction<00:03:55.070> stock<00:03:55.520> will<00:03:55.730> run<00:03:55.880> even<00:03:55.910> about<00:03:56.209> a 00:03:56.230 --> 00:03:56.240 align:start position:0% transaction stock will run even about a 00:03:56.240 --> 00:03:57.610 align:start position:0% transaction stock will run even about a hundred<00:03:56.510> twenty<00:03:56.630> eight<00:03:56.840> thousand<00:03:57.230> two<00:03:57.320> eleven 00:03:57.610 --> 00:03:57.620 align:start position:0% hundred twenty eight thousand two eleven 00:03:57.620 --> 00:04:01.540 align:start position:0% hundred twenty eight thousand two eleven to<00:03:57.830> twelve<00:03:58.040> thousand<00:03:58.400> twelve<00:03:58.610> gates<00:04:00.370> and<00:04:01.370> yeah 00:04:01.540 --> 00:04:01.550 align:start position:0% to twelve thousand twelve gates and yeah 00:04:01.550 --> 00:04:03.640 align:start position:0% to twelve thousand twelve gates and yeah this<00:04:01.730> is<00:04:01.850> the<00:04:01.989> theme<00:04:02.989> of<00:04:03.140> the<00:04:03.230> library<00:04:03.530> we've 00:04:03.640 --> 00:04:03.650 align:start position:0% this is the theme of the library we've 00:04:03.650 --> 00:04:05.110 align:start position:0% this is the theme of the library we've been<00:04:03.770> building<00:04:03.920> has<00:04:04.489> been<00:04:04.700> a<00:04:04.790> source<00:04:05.000> of 00:04:05.110 --> 00:04:05.120 align:start position:0% been building has been a source of 00:04:05.120 --> 00:04:06.910 align:start position:0% been building has been a source of iterations<00:04:05.570> very<00:04:05.989> welcome<00:04:06.380> feel<00:04:06.770> free<00:04:06.830> to 00:04:06.910 --> 00:04:06.920 align:start position:0% iterations very welcome feel free to 00:04:06.920 --> 00:04:12.610 align:start position:0% iterations very welcome feel free to tinker<00:04:07.250> around<00:04:07.280> it<00:04:08.350> so<00:04:10.989> that's<00:04:11.989> the<00:04:12.290> final 00:04:12.610 --> 00:04:12.620 align:start position:0% tinker around it so that's the final 00:04:12.620 --> 00:04:16.180 align:start position:0% tinker around it so that's the final stuff<00:04:12.970> so<00:04:13.970> why<00:04:14.209> don't<00:04:14.360> we<00:04:14.860> kind<00:04:15.860> of<00:04:15.920> get<00:04:16.040> to<00:04:16.160> the 00:04:16.180 --> 00:04:16.190 align:start position:0% stuff so why don't we kind of get to the 00:04:16.190 --> 00:04:20.440 align:start position:0% stuff so why don't we kind of get to the guts<00:04:16.430> of<00:04:16.730> house<00:04:17.000> as<00:04:17.299> well<00:04:18.340> and<00:04:19.340> what's<00:04:20.269> going 00:04:20.440 --> 00:04:20.450 align:start position:0% guts of house as well and what's going 00:04:20.450 --> 00:04:28.659 align:start position:0% guts of house as well and what's going on<00:04:20.570> with<00:04:20.660> them<00:04:22.960> second<00:04:26.680> and<00:04:27.680> so<00:04:28.010> we<00:04:28.550> use 00:04:28.659 --> 00:04:28.669 align:start position:0% on with them second and so we use 00:04:28.669 --> 00:04:30.790 align:start position:0% on with them second and so we use polynomial<00:04:29.120> commitments<00:04:29.450> meters<00:04:29.720> long<00:04:29.900> so 00:04:30.790 --> 00:04:30.800 align:start position:0% polynomial commitments meters long so 00:04:30.800 --> 00:04:34.860 align:start position:0% polynomial commitments meters long so being<00:04:31.760> hands<00:04:31.910> upon<00:04:32.210> with<00:04:32.680> Sonic<00:04:33.680> and<00:04:33.890> monitor 00:04:34.860 --> 00:04:34.870 align:start position:0% being hands upon with Sonic and monitor 00:04:34.870 --> 00:04:38.230 align:start position:0% being hands upon with Sonic and monitor contemporaneous<00:04:35.870> previous<00:04:36.830> system<00:04:37.070> and<00:04:37.520> then 00:04:38.230 --> 00:04:38.240 align:start position:0% contemporaneous previous system and then 00:04:38.240 --> 00:04:39.520 align:start position:0% contemporaneous previous system and then we<00:04:38.300> sum<00:04:38.450> all<00:04:38.510> these<00:04:38.660> polygons<00:04:39.050> conveyances 00:04:39.520 --> 00:04:39.530 align:start position:0% we sum all these polygons conveyances 00:04:39.530 --> 00:04:42.969 align:start position:0% we sum all these polygons conveyances because<00:04:39.710> it's<00:04:40.100> a<00:04:40.190> very<00:04:41.860> efficient<00:04:42.860> way<00:04:42.890> of 00:04:42.969 --> 00:04:42.979 align:start position:0% because it's a very efficient way of 00:04:42.979 --> 00:04:44.650 align:start position:0% because it's a very efficient way of achieving<00:04:43.100> is<00:04:43.400> a<00:04:43.460> sickness<00:04:43.700> it<00:04:44.150> was<00:04:44.270> not<00:04:44.510> an 00:04:44.650 --> 00:04:44.660 align:start position:0% achieving is a sickness it was not an 00:04:44.660 --> 00:04:47.650 align:start position:0% achieving is a sickness it was not an assistant<00:04:45.760> effectively<00:04:46.760> we<00:04:47.120> know<00:04:47.240> how<00:04:47.419> to<00:04:47.479> use 00:04:47.650 --> 00:04:47.660 align:start position:0% assistant effectively we know how to use 00:04:47.660 --> 00:04:49.300 align:start position:0% assistant effectively we know how to use the<00:04:47.870> simply<00:04:48.140> commit<00:04:48.530> to<00:04:48.620> pollen<00:04:48.830> Ethel<00:04:49.100> so<00:04:49.190> you 00:04:49.300 --> 00:04:49.310 align:start position:0% the simply commit to pollen Ethel so you 00:04:49.310 --> 00:04:51.280 align:start position:0% the simply commit to pollen Ethel so you can<00:04:49.490> take<00:04:49.760> of<00:04:49.910> polynomial<00:04:50.840> with<00:04:50.960> a<00:04:51.020> very 00:04:51.280 --> 00:04:51.290 align:start position:0% can take of polynomial with a very 00:04:51.290 --> 00:04:52.450 align:start position:0% can take of polynomial with a very health<00:04:51.530> degree<00:04:51.770> which<00:04:52.040> is<00:04:52.070> because<00:04:52.310> an 00:04:52.450 --> 00:04:52.460 align:start position:0% health degree which is because an 00:04:52.460 --> 00:04:53.700 align:start position:0% health degree which is because an enormous<00:04:52.760> amount<00:04:52.850> of<00:04:52.940> information<00:04:53.120> and 00:04:53.700 --> 00:04:53.710 align:start position:0% enormous amount of information and 00:04:53.710 --> 00:04:55.540 align:start position:0% enormous amount of information and represented<00:04:54.710> within<00:04:54.830> a<00:04:54.950> single<00:04:55.130> elliptic 00:04:55.540 --> 00:04:55.550 align:start position:0% represented within a single elliptic 00:04:55.550 --> 00:04:58.750 align:start position:0% represented within a single elliptic curve<00:04:55.700> point<00:04:55.910> and<00:04:56.750> you<00:04:57.440> can<00:04:57.620> then<00:04:57.800> have<00:04:58.400> if<00:04:58.669> you 00:04:58.750 --> 00:04:58.760 align:start position:0% curve point and you can then have if you 00:04:58.760 --> 00:05:01.560 align:start position:0% curve point and you can then have if you can<00:04:58.910> represent<00:04:59.090> your<00:04:59.570> snarks<00:05:00.410> template<00:05:00.860> bias 00:05:01.560 --> 00:05:01.570 align:start position:0% can represent your snarks template bias 00:05:01.570 --> 00:05:03.580 align:start position:0% can represent your snarks template bias polynomial<00:05:02.570> identity<00:05:02.960> involving<00:05:03.080> other 00:05:03.580 --> 00:05:03.590 align:start position:0% polynomial identity involving other 00:05:03.590 --> 00:05:05.260 align:start position:0% polynomial identity involving other neighborhood<00:05:03.919> commitments<00:05:04.340> then<00:05:04.940> a 00:05:05.260 --> 00:05:05.270 align:start position:0% neighborhood commitments then a 00:05:05.270 --> 00:05:06.940 align:start position:0% neighborhood commitments then a verification<00:05:05.780> algorithm<00:05:06.290> Contessa's 00:05:06.940 --> 00:05:06.950 align:start position:0% verification algorithm Contessa's 00:05:06.950 --> 00:05:09.760 align:start position:0% verification algorithm Contessa's polynomial<00:05:07.400> identity<00:05:07.820> by<00:05:08.180> testing<00:05:08.870> it<00:05:08.930> at<00:05:09.140> a 00:05:09.760 --> 00:05:09.770 align:start position:0% polynomial identity by testing it at a 00:05:09.770 --> 00:05:12.850 align:start position:0% polynomial identity by testing it at a random<00:05:10.280> evaluation<00:05:10.940> point<00:05:11.180> and<00:05:12.080> have 00:05:12.850 --> 00:05:12.860 align:start position:0% random evaluation point and have 00:05:12.860 --> 00:05:13.750 align:start position:0% random evaluation point and have confidence<00:05:13.040> over<00:05:13.340> they<00:05:13.430> were<00:05:13.490> whelming 00:05:13.750 --> 00:05:13.760 align:start position:0% confidence over they were whelming 00:05:13.760 --> 00:05:17.080 align:start position:0% confidence over they were whelming probability<00:05:14.270> if<00:05:14.720> you're<00:05:15.640> if<00:05:16.640> you're<00:05:16.700> kind<00:05:17.030> of 00:05:17.080 --> 00:05:17.090 align:start position:0% probability if you're if you're kind of 00:05:17.090 --> 00:05:18.850 align:start position:0% probability if you're if you're kind of snot<00:05:17.450> description<00:05:18.169> holds<00:05:18.440> it<00:05:18.530> randomly 00:05:18.850 --> 00:05:18.860 align:start position:0% snot description holds it randomly 00:05:18.860 --> 00:05:22.350 align:start position:0% snot description holds it randomly points<00:05:19.190> of<00:05:19.250> a<00:05:19.340> lot<00:05:19.460> of<00:05:19.580> everyone<00:05:20.440> this<00:05:21.440> also 00:05:22.350 --> 00:05:22.360 align:start position:0% points of a lot of everyone this also 00:05:22.360 --> 00:05:25.300 align:start position:0% points of a lot of everyone this also interesting<00:05:23.530> divorces<00:05:24.530> plot<00:05:24.740> from<00:05:25.040> the 00:05:25.300 --> 00:05:25.310 align:start position:0% interesting divorces plot from the 00:05:25.310 --> 00:05:25.960 align:start position:0% interesting divorces plot from the underlying 00:05:25.960 --> 00:05:25.970 align:start position:0% underlying 00:05:25.970 --> 00:05:27.220 align:start position:0% underlying there's<00:05:26.150> characteristics<00:05:26.780> that<00:05:26.870> are<00:05:26.990> used<00:05:27.110> in 00:05:27.220 --> 00:05:27.230 align:start position:0% there's characteristics that are used in 00:05:27.230 --> 00:05:28.600 align:start position:0% there's characteristics that are used in sensitive<00:05:27.620> the<00:05:27.740> planning<00:05:28.070> commitment<00:05:28.370> skin 00:05:28.600 --> 00:05:28.610 align:start position:0% sensitive the planning commitment skin 00:05:28.610 --> 00:05:30.790 align:start position:0% sensitive the planning commitment skin you<00:05:28.730> can<00:05:28.880> run<00:05:29.000> not<00:05:29.420> a<00:05:29.450> solid<00:05:29.840> two<00:05:29.930> curves<00:05:30.170> just 00:05:30.790 --> 00:05:30.800 align:start position:0% you can run not a solid two curves just 00:05:30.800 --> 00:05:31.990 align:start position:0% you can run not a solid two curves just I<00:05:30.950> published<00:05:31.340> at<00:05:31.430> BU<00:05:31.550> closer 00:05:31.990 --> 00:05:32.000 align:start position:0% I published at BU closer 00:05:32.000 --> 00:05:34.180 align:start position:0% I published at BU closer essentially<00:05:32.840> did<00:05:32.960> over<00:05:33.110> the<00:05:33.260> in<00:05:33.860> commitment 00:05:34.180 --> 00:05:34.190 align:start position:0% essentially did over the in commitment 00:05:34.190 --> 00:05:35.560 align:start position:0% essentially did over the in commitment skin<00:05:34.340> that<00:05:34.460> uses<00:05:34.640> a<00:05:34.700> tractor<00:05:34.970> coral<00:05:35.210> proves 00:05:35.560 --> 00:05:35.570 align:start position:0% skin that uses a tractor coral proves 00:05:35.570 --> 00:05:39.580 align:start position:0% skin that uses a tractor coral proves even<00:05:37.570> possibilities<00:05:38.570> as<00:05:38.660> reliability<00:05:39.200> groups 00:05:39.580 --> 00:05:39.590 align:start position:0% even possibilities as reliability groups 00:05:39.590 --> 00:05:44.230 align:start position:0% even possibilities as reliability groups Christine<00:05:41.080> so<00:05:42.550> actually<00:05:43.550> okay<00:05:43.790> so<00:05:43.850> you<00:05:44.120> think 00:05:44.230 --> 00:05:44.240 align:start position:0% Christine so actually okay so you think 00:05:44.240 --> 00:05:45.580 align:start position:0% Christine so actually okay so you think will<00:05:44.330> not<00:05:44.390> make<00:05:44.540> the<00:05:44.660> list<00:05:44.780> of<00:05:44.960> a<00:05:45.020> wish<00:05:45.170> list<00:05:45.350> of 00:05:45.580 --> 00:05:45.590 align:start position:0% will not make the list of a wish list of 00:05:45.590 --> 00:05:47.590 align:start position:0% will not make the list of a wish list of what<00:05:46.040> you<00:05:46.370> need<00:05:46.400> to<00:05:46.640> make<00:05:46.670> Universal<00:05:47.270> to<00:05:47.510> make 00:05:47.590 --> 00:05:47.600 align:start position:0% what you need to make Universal to make 00:05:47.600 --> 00:05:49.630 align:start position:0% what you need to make Universal to make it's<00:05:47.720> not<00:05:48.040> obviously<00:05:49.040> me<00:05:49.190> wants<00:05:49.400> a<00:05:49.430> way<00:05:49.550> of 00:05:49.630 --> 00:05:49.640 align:start position:0% it's not obviously me wants a way of 00:05:49.640 --> 00:05:53.170 align:start position:0% it's not obviously me wants a way of constructing<00:05:51.550> turning<00:05:52.550> a<00:05:52.610> program<00:05:52.910> integrity 00:05:53.170 --> 00:05:53.180 align:start position:0% constructing turning a program integrity 00:05:53.180 --> 00:05:54.730 align:start position:0% constructing turning a program integrity for<00:05:53.450> knowledge<00:05:53.570> and<00:05:53.780> services<00:05:54.380> totally<00:05:54.620> done 00:05:54.730 --> 00:05:54.740 align:start position:0% for knowledge and services totally done 00:05:54.740 --> 00:05:57.220 align:start position:0% for knowledge and services totally done with<00:05:54.940> addition<00:05:55.940> to<00:05:56.000> multiplication<00:05:56.240> games 00:05:57.220 --> 00:05:57.230 align:start position:0% with addition to multiplication games 00:05:57.230 --> 00:05:58.390 align:start position:0% with addition to multiplication games that<00:05:57.470> are<00:05:57.560> stitched<00:05:57.770> together<00:05:57.860> to<00:05:58.130> the<00:05:58.220> former 00:05:58.390 --> 00:05:58.400 align:start position:0% that are stitched together to the former 00:05:58.400 --> 00:05:59.620 align:start position:0% that are stitched together to the former self<00:05:58.640> because<00:05:58.910> this<00:05:59.060> is<00:05:59.180> a<00:05:59.210> relatively 00:05:59.620 --> 00:05:59.630 align:start position:0% self because this is a relatively 00:05:59.630 --> 00:06:02.110 align:start position:0% self because this is a relatively natural<00:06:00.380> way<00:06:00.770> of<00:06:00.800> representing<00:06:01.430> problem 00:06:02.110 --> 00:06:02.120 align:start position:0% natural way of representing problem 00:06:02.120 --> 00:06:04.090 align:start position:0% natural way of representing problem statements<00:06:02.540> when<00:06:02.930> your<00:06:03.080> underlying<00:06:03.650> when<00:06:04.010> you 00:06:04.090 --> 00:06:04.100 align:start position:0% statements when your underlying when you 00:06:04.100 --> 00:06:05.290 align:start position:0% statements when your underlying when you actually<00:06:04.220> do<00:06:04.430> that<00:06:04.580> when<00:06:04.910> you're<00:06:05.030> testing 00:06:05.290 --> 00:06:05.300 align:start position:0% actually do that when you're testing 00:06:05.300 --> 00:06:09.310 align:start position:0% actually do that when you're testing these<00:06:05.860> proofs<00:06:06.860> of<00:06:06.950> knowledge<00:06:07.240> in<00:06:08.320> using 00:06:09.310 --> 00:06:09.320 align:start position:0% these proofs of knowledge in using 00:06:09.320 --> 00:06:11.200 align:start position:0% these proofs of knowledge in using persistence<00:06:09.890> that<00:06:09.950> you<00:06:10.400> have<00:06:10.550> used<00:06:10.730> a<00:06:10.850> filter 00:06:11.200 --> 00:06:11.210 align:start position:0% persistence that you have used a filter 00:06:11.210 --> 00:06:13.240 align:start position:0% persistence that you have used a filter of<00:06:11.270> particular<00:06:11.770> we<00:06:12.770> want<00:06:12.920> them<00:06:13.100> you<00:06:13.160> know 00:06:13.240 --> 00:06:13.250 align:start position:0% of particular we want them you know 00:06:13.250 --> 00:06:14.650 align:start position:0% of particular we want them you know pheromone<00:06:13.640> running<00:06:13.940> effectively<00:06:14.180> constant 00:06:14.650 --> 00:06:14.660 align:start position:0% pheromone running effectively constant 00:06:14.660 --> 00:06:16.840 align:start position:0% pheromone running effectively constant time<00:06:14.840> animals<00:06:15.740> Universal<00:06:16.280> so<00:06:16.370> we<00:06:16.460> want<00:06:16.640> there 00:06:16.840 --> 00:06:16.850 align:start position:0% time animals Universal so we want there 00:06:16.850 --> 00:06:19.450 align:start position:0% time animals Universal so we want there to<00:06:16.880> be<00:06:17.000> any<00:06:17.270> want<00:06:17.480> us<00:06:17.660> to<00:06:17.780> set<00:06:17.960> up<00:06:18.130> to<00:06:19.130> be<00:06:19.280> to 00:06:19.450 --> 00:06:19.460 align:start position:0% to be any want us to set up to be to 00:06:19.460 --> 00:06:22.590 align:start position:0% to be any want us to set up to be to each<00:06:20.030> other<00:06:20.270> system<00:06:20.630> and<00:06:20.750> then<00:06:20.840> you<00:06:20.960> can 00:06:22.590 --> 00:06:22.600 align:start position:0% each other system and then you can 00:06:22.600 --> 00:06:25.450 align:start position:0% each other system and then you can include<00:06:23.630> arbitary<00:06:23.960> programs<00:06:24.440> as<00:06:25.040> snot 00:06:25.450 --> 00:06:25.460 align:start position:0% include arbitary programs as snot 00:06:25.460 --> 00:06:28.480 align:start position:0% include arbitary programs as snot circuits<00:06:25.970> without<00:06:26.180> additional<00:06:26.630> 50<00:06:27.050> subs<00:06:27.490> in 00:06:28.480 --> 00:06:28.490 align:start position:0% circuits without additional 50 subs in 00:06:28.490 --> 00:06:30.190 align:start position:0% circuits without additional 50 subs in at<00:06:28.640> a<00:06:28.730> that<00:06:28.910> wealth<00:06:29.060> human<00:06:29.540> creator<00:06:29.810> to<00:06:30.020> set 00:06:30.190 --> 00:06:30.200 align:start position:0% at a that wealth human creator to set 00:06:30.200 --> 00:06:34.810 align:start position:0% at a that wealth human creator to set ups<00:06:30.320> but<00:06:30.560> then<00:06:30.790> you<00:06:31.790> miss<00:06:31.940> philosophers<00:06:33.820> shoe 00:06:34.810 --> 00:06:34.820 align:start position:0% ups but then you miss philosophers shoe 00:06:34.820 --> 00:06:38.110 align:start position:0% ups but then you miss philosophers shoe sizes<00:06:35.090> which<00:06:36.020> is<00:06:36.169> a<00:06:36.730> little<00:06:37.730> bit<00:06:37.820> of<00:06:37.910> a<00:06:37.970> problem 00:06:38.110 --> 00:06:38.120 align:start position:0% sizes which is a little bit of a problem 00:06:38.120 --> 00:06:39.480 align:start position:0% sizes which is a little bit of a problem for<00:06:38.240> it<00:06:38.419> there 00:06:39.480 --> 00:06:39.490 align:start position:0% for it there 00:06:39.490 --> 00:06:43.270 align:start position:0% for it there so<00:06:40.780> you<00:06:41.780> notice<00:06:41.990> last<00:06:42.110> he<00:06:42.530> doesn't<00:06:42.950> is<00:06:43.130> not 00:06:43.270 --> 00:06:43.280 align:start position:0% so you notice last he doesn't is not 00:06:43.280 --> 00:06:45.610 align:start position:0% so you notice last he doesn't is not familiar<00:06:43.730> with<00:06:43.940> the<00:06:44.060> concept<00:06:44.240> of<00:06:44.510> a<00:06:44.600> gate<00:06:44.810> in 00:06:45.610 --> 00:06:45.620 align:start position:0% familiar with the concept of a gate in 00:06:45.620 --> 00:06:50.650 align:start position:0% familiar with the concept of a gate in the<00:06:45.770> context<00:06:46.040> of<00:06:46.100> stars<00:06:48.430> okay<00:06:49.430> so<00:06:49.820> basically 00:06:50.650 --> 00:06:50.660 align:start position:0% the context of stars okay so basically 00:06:50.660 --> 00:06:56.830 align:start position:0% the context of stars okay so basically the<00:06:51.050> games<00:06:51.260> has<00:06:51.770> ended<00:06:52.220> and<00:06:52.370> the<00:06:52.460> wires<00:06:52.660> and<00:06:55.840> so 00:06:56.830 --> 00:06:56.840 align:start position:0% the games has ended and the wires and so 00:06:56.840 --> 00:07:01.270 align:start position:0% the games has ended and the wires and so ok<00:06:57.140> so<00:06:57.490> basically<00:06:58.490> you<00:06:59.120> have<00:06:59.270> is<00:07:00.280> basically 00:07:01.270 --> 00:07:01.280 align:start position:0% ok so basically you have is basically 00:07:01.280 --> 00:07:03.640 align:start position:0% ok so basically you have is basically that<00:07:01.460> the<00:07:01.520> the<00:07:02.150> the<00:07:02.390> primitive<00:07:03.290> hazardous 00:07:03.640 --> 00:07:03.650 align:start position:0% that the the the primitive hazardous 00:07:03.650 --> 00:07:05.590 align:start position:0% that the the the primitive hazardous collaborations<00:07:04.130> that<00:07:04.250> he<00:07:04.310> wants<00:07:04.490> a<00:07:04.600> parameter 00:07:05.590 --> 00:07:05.600 align:start position:0% collaborations that he wants a parameter 00:07:05.600 --> 00:07:07.630 align:start position:0% collaborations that he wants a parameter in<00:07:06.169> the<00:07:06.290> same<00:07:06.470> way<00:07:06.620> that<00:07:06.800> you<00:07:07.220> can<00:07:07.340> take<00:07:07.490> any 00:07:07.630 --> 00:07:07.640 align:start position:0% in the same way that you can take any 00:07:07.640 --> 00:07:09.100 align:start position:0% in the same way that you can take any computer<00:07:07.940> paramount<00:07:08.300> and<00:07:08.419> decompose<00:07:08.780> it<00:07:08.930> into 00:07:09.100 --> 00:07:09.110 align:start position:0% computer paramount and decompose it into 00:07:09.110 --> 00:07:10.960 align:start position:0% computer paramount and decompose it into a<00:07:09.560> sequence<00:07:09.980> of<00:07:10.160> mandates<00:07:10.580> accessible 00:07:10.960 --> 00:07:10.970 align:start position:0% a sequence of mandates accessible 00:07:10.970 --> 00:07:13.630 align:start position:0% a sequence of mandates accessible successional<00:07:11.390> CPU<00:07:11.870> ship<00:07:12.050> you<00:07:12.530> can<00:07:12.680> take<00:07:13.220> you 00:07:13.630 --> 00:07:13.640 align:start position:0% successional CPU ship you can take you 00:07:13.640 --> 00:07:15.080 align:start position:0% successional CPU ship you can take you can<00:07:13.669> also<00:07:13.910> take<00:07:14.120> in<00:07:14.330> computer 00:07:15.080 --> 00:07:15.090 align:start position:0% can also take in computer 00:07:15.090 --> 00:07:16.640 align:start position:0% can also take in computer into<00:07:15.720> a<00:07:15.750> sequence<00:07:16.020> of<00:07:16.169> additions<00:07:16.290> and 00:07:16.640 --> 00:07:16.650 align:start position:0% into a sequence of additions and 00:07:16.650 --> 00:07:19.250 align:start position:0% into a sequence of additions and multiplications<00:07:17.240> and<00:07:18.240> so<00:07:18.510> that's<00:07:18.930> what<00:07:19.110> we're 00:07:19.250 --> 00:07:19.260 align:start position:0% multiplications and so that's what we're 00:07:19.260 --> 00:07:21.260 align:start position:0% multiplications and so that's what we're doing<00:07:19.860> when<00:07:19.980> we<00:07:20.040> create<00:07:20.280> start<00:07:20.520> snack<00:07:20.850> seconds 00:07:21.260 --> 00:07:21.270 align:start position:0% doing when we create start snack seconds 00:07:21.270 --> 00:07:23.390 align:start position:0% doing when we create start snack seconds we're<00:07:21.449> actually<00:07:21.980> taking<00:07:22.980> these<00:07:23.160> things 00:07:23.390 --> 00:07:23.400 align:start position:0% we're actually taking these things 00:07:23.400 --> 00:07:25.400 align:start position:0% we're actually taking these things equals<00:07:23.699> premise<00:07:24.030> of<00:07:24.120> gates<00:07:24.330> and<00:07:24.540> thus 00:07:25.400 --> 00:07:25.410 align:start position:0% equals premise of gates and thus 00:07:25.410 --> 00:07:28.310 align:start position:0% equals premise of gates and thus additionally<00:07:25.860> together<00:07:26.130> to<00:07:27.199> make<00:07:28.199> the 00:07:28.310 --> 00:07:28.320 align:start position:0% additionally together to make the 00:07:28.320 --> 00:07:29.530 align:start position:0% additionally together to make the representation<00:07:28.860> for<00:07:28.889> more<00:07:29.130> complicated 00:07:29.530 --> 00:07:29.540 align:start position:0% representation for more complicated 00:07:29.540 --> 00:07:33.230 align:start position:0% representation for more complicated public<00:07:30.540> permanent<00:07:31.020> consent<00:07:31.880> and<00:07:32.880> we<00:07:33.090> have 00:07:33.230 --> 00:07:33.240 align:start position:0% public permanent consent and we have 00:07:33.240 --> 00:07:35.000 align:start position:0% public permanent consent and we have issuance<00:07:33.720> of<00:07:33.780> educates<00:07:34.440> and<00:07:34.680> they<00:07:34.830> will<00:07:34.919> have 00:07:35.000 --> 00:07:35.010 align:start position:0% issuance of educates and they will have 00:07:35.010 --> 00:07:36.409 align:start position:0% issuance of educates and they will have given<00:07:35.310> us<00:07:35.430> another<00:07:35.790> bite 00:07:36.409 --> 00:07:36.419 align:start position:0% given us another bite 00:07:36.419 --> 00:07:38.290 align:start position:0% given us another bite and<00:07:36.600> you<00:07:36.750> can<00:07:36.870> make<00:07:36.960> a<00:07:36.990> circuit<00:07:37.350> by<00:07:37.560> stitching 00:07:38.290 --> 00:07:38.300 align:start position:0% and you can make a circuit by stitching 00:07:38.300 --> 00:07:39.950 align:start position:0% and you can make a circuit by stitching in<00:07:39.300> this<00:07:39.389> case<00:07:39.600> together 00:07:39.950 --> 00:07:39.960 align:start position:0% in this case together 00:07:39.960 --> 00:07:42.050 align:start position:0% in this case together we're<00:07:40.860> like<00:07:41.100> the<00:07:41.190> ordering<00:07:41.520> of<00:07:41.639> can<00:07:41.910> see 00:07:42.050 --> 00:07:42.060 align:start position:0% we're like the ordering of can see 00:07:42.060 --> 00:07:43.640 align:start position:0% we're like the ordering of can see personal<00:07:42.510> where's<00:07:43.020> Weiss<00:07:43.199> will<00:07:43.530> be 00:07:43.640 --> 00:07:43.650 align:start position:0% personal where's Weiss will be 00:07:43.650 --> 00:07:45.650 align:start position:0% personal where's Weiss will be completely<00:07:44.610> Donnelly<00:07:45.030> in<00:07:45.120> a<00:07:45.180> rather<00:07:45.300> he<00:07:45.540> also 00:07:45.650 --> 00:07:45.660 align:start position:0% completely Donnelly in a rather he also 00:07:45.660 --> 00:07:47.300 align:start position:0% completely Donnelly in a rather he also probably<00:07:46.260> created<00:07:46.620> by<00:07:46.710> the<00:07:46.770> compiler<00:07:47.040> with 00:07:47.300 --> 00:07:47.310 align:start position:0% probably created by the compiler with 00:07:47.310 --> 00:07:51.200 align:start position:0% probably created by the compiler with human<00:07:49.280> and<00:07:50.280> you<00:07:50.430> know<00:07:50.610> pretty<00:07:51.000> you<00:07:51.120> have 00:07:51.200 --> 00:07:51.210 align:start position:0% human and you know pretty you have 00:07:51.210 --> 00:07:53.450 align:start position:0% human and you know pretty you have satisfied<00:07:51.510> Sanders<00:07:52.169> has<00:07:52.320> evolved<00:07:52.650> Co<00:07:53.310> to 00:07:53.450 --> 00:07:53.460 align:start position:0% satisfied Sanders has evolved Co to 00:07:53.460 --> 00:07:54.830 align:start position:0% satisfied Sanders has evolved Co to prove<00:07:53.580> that<00:07:53.669> all<00:07:53.790> the<00:07:53.880> Y<00:07:54.030> values<00:07:54.060> are<00:07:54.570> what 00:07:54.830 --> 00:07:54.840 align:start position:0% prove that all the Y values are what 00:07:54.840 --> 00:07:56.719 align:start position:0% prove that all the Y values are what they<00:07:54.960> they<00:07:55.350> ought<00:07:55.740> to<00:07:55.770> be<00:07:56.040> acting<00:07:56.610> on 00:07:56.719 --> 00:07:56.729 align:start position:0% they they ought to be acting on 00:07:56.729 --> 00:08:01.670 align:start position:0% they they ought to be acting on interface<00:07:58.040> so<00:07:59.150> you<00:08:00.150> know<00:08:01.020> when<00:08:01.560> you're 00:08:01.670 --> 00:08:01.680 align:start position:0% interface so you know when you're 00:08:01.680 --> 00:08:02.900 align:start position:0% interface so you know when you're stitching<00:08:01.889> together<00:08:02.190> all<00:08:02.520> of<00:08:02.580> these<00:08:02.669> gates 00:08:02.900 --> 00:08:02.910 align:start position:0% stitching together all of these gates 00:08:02.910 --> 00:08:06.950 align:start position:0% stitching together all of these gates you<00:08:03.180> have<00:08:04.169> to<00:08:04.260> kind<00:08:04.470> of<00:08:04.530> you<00:08:05.010> you<00:08:05.040> you<00:08:05.960> whenever 00:08:06.950 --> 00:08:06.960 align:start position:0% you have to kind of you you you whenever 00:08:06.960 --> 00:08:08.150 align:start position:0% you have to kind of you you you whenever you<00:08:07.169> make<00:08:07.260> you<00:08:07.380> connection<00:08:07.680> which<00:08:07.889> of<00:08:07.979> your 00:08:08.150 --> 00:08:08.160 align:start position:0% you make you connection which of your 00:08:08.160 --> 00:08:10.010 align:start position:0% you make you connection which of your gates<00:08:08.340> are<00:08:09.000> your<00:08:09.150> federal<00:08:09.389> city<00:08:09.630> two<00:08:09.840> wires 00:08:10.010 --> 00:08:10.020 align:start position:0% gates are your federal city two wires 00:08:10.020 --> 00:08:13.100 align:start position:0% gates are your federal city two wires together<00:08:11.090> together<00:08:12.090> as<00:08:12.419> you<00:08:12.510> can<00:08:12.630> have<00:08:12.750> that 00:08:13.100 --> 00:08:13.110 align:start position:0% together together as you can have that 00:08:13.110 --> 00:08:16.210 align:start position:0% together together as you can have that possible<00:08:13.590> but<00:08:14.160> minor<00:08:14.880> physical<00:08:15.120> otherwise 00:08:16.210 --> 00:08:16.220 align:start position:0% possible but minor physical otherwise 00:08:16.220 --> 00:08:19.000 align:start position:0% possible but minor physical otherwise and<00:08:17.220> then<00:08:17.340> you've<00:08:17.430> got<00:08:17.520> to<00:08:17.639> kind<00:08:17.789> of<00:08:17.990> validate 00:08:19.000 --> 00:08:19.010 align:start position:0% and then you've got to kind of validate 00:08:19.010 --> 00:08:22.010 align:start position:0% and then you've got to kind of validate that's<00:08:20.010> if<00:08:20.760> you<00:08:20.910> sell<00:08:21.150> odds<00:08:21.570> that<00:08:21.900> you've 00:08:22.010 --> 00:08:22.020 align:start position:0% that's if you sell odds that you've 00:08:22.020 --> 00:08:23.510 align:start position:0% that's if you sell odds that you've actually<00:08:22.169> that<00:08:22.590> you've<00:08:22.770> run<00:08:23.070> the<00:08:23.220> program 00:08:23.510 --> 00:08:23.520 align:start position:0% actually that you've run the program 00:08:23.520 --> 00:08:25.190 align:start position:0% actually that you've run the program opportunity<00:08:24.090> in<00:08:24.240> favor<00:08:24.450> to<00:08:24.630> the<00:08:24.720> circuit<00:08:25.050> and 00:08:25.190 --> 00:08:25.200 align:start position:0% opportunity in favor to the circuit and 00:08:25.200 --> 00:08:28.700 align:start position:0% opportunity in favor to the circuit and all<00:08:26.039> of<00:08:26.250> the<00:08:26.370> whites<00:08:27.289> have<00:08:28.289> the<00:08:28.440> current 00:08:28.700 --> 00:08:28.710 align:start position:0% all of the whites have the current 00:08:28.710 --> 00:08:30.200 align:start position:0% all of the whites have the current values<00:08:29.039> and<00:08:29.580> they<00:08:29.669> should<00:08:29.850> have<00:08:30.000> at<00:08:30.120> you 00:08:30.200 --> 00:08:30.210 align:start position:0% values and they should have at you 00:08:30.210 --> 00:08:34.010 align:start position:0% values and they should have at you acting<00:08:30.389> constant<00:08:31.159> so<00:08:32.360> fundamentally<00:08:33.360> if<00:08:33.870> you 00:08:34.010 --> 00:08:34.020 align:start position:0% acting constant so fundamentally if you 00:08:34.020 --> 00:08:37.459 align:start position:0% acting constant so fundamentally if you want<00:08:34.200> to<00:08:34.469> represent<00:08:35.459> a<00:08:35.940> program<00:08:36.450> as<00:08:36.659> the 00:08:37.459 --> 00:08:37.469 align:start position:0% want to represent a program as the 00:08:37.469 --> 00:08:39.860 align:start position:0% want to represent a program as the quantities<00:08:37.979> to<00:08:38.610> the<00:08:38.789> College<00:08:39.000> you<00:08:39.240> only<00:08:39.750> have 00:08:39.860 --> 00:08:39.870 align:start position:0% quantities to the College you only have 00:08:39.870 --> 00:08:42.079 align:start position:0% quantities to the College you only have to<00:08:39.959> do<00:08:40.020> two<00:08:40.050> things<00:08:40.169> you<00:08:41.039> have<00:08:41.190> to<00:08:41.219> perform<00:08:41.760> an 00:08:42.079 --> 00:08:42.089 align:start position:0% to do two things you have to perform an 00:08:42.089 --> 00:08:43.940 align:start position:0% to do two things you have to perform an a<00:08:42.150> little<00:08:42.419> asthmatic<00:08:42.779> so<00:08:43.500> you<00:08:43.560> need<00:08:43.680> to<00:08:43.770> check 00:08:43.940 --> 00:08:43.950 align:start position:0% a little asthmatic so you need to check 00:08:43.950 --> 00:08:45.380 align:start position:0% a little asthmatic so you need to check that<00:08:43.979> the<00:08:44.310> announced<00:08:44.670> metric<00:08:45.000> relationship 00:08:45.380 --> 00:08:45.390 align:start position:0% that the announced metric relationship 00:08:45.390 --> 00:08:46.730 align:start position:0% that the announced metric relationship that<00:08:45.540> every<00:08:45.720> single<00:08:45.839> Gators<00:08:46.200> been<00:08:46.290> satisfied 00:08:46.730 --> 00:08:46.740 align:start position:0% that every single Gators been satisfied 00:08:46.740 --> 00:08:48.560 align:start position:0% that every single Gators been satisfied that<00:08:47.370> the<00:08:47.490> two<00:08:47.640> o'clock<00:08:47.850> whites<00:08:48.060> either<00:08:48.270> soft 00:08:48.560 --> 00:08:48.570 align:start position:0% that the two o'clock whites either soft 00:08:48.570 --> 00:08:49.670 align:start position:0% that the two o'clock whites either soft and<00:08:48.690> multiplied<00:08:49.020> together<00:08:49.140> is<00:08:49.410> you<00:08:49.440> must<00:08:49.620> be 00:08:49.670 --> 00:08:49.680 align:start position:0% and multiplied together is you must be 00:08:49.680 --> 00:08:51.980 align:start position:0% and multiplied together is you must be on<00:08:49.830> the<00:08:49.980> wire<00:08:50.160> and<00:08:50.550> there<00:08:51.180> is<00:08:51.300> a<00:08:51.450> point<00:08:51.600> global 00:08:51.980 --> 00:08:51.990 align:start position:0% on the wire and there is a point global 00:08:51.990 --> 00:08:55.269 align:start position:0% on the wire and there is a point global consistency<00:08:52.290> you<00:08:53.040> need<00:08:53.190> to<00:08:53.570> validate<00:08:54.570> that 00:08:55.269 --> 00:08:55.279 align:start position:0% consistency you need to validate that 00:08:55.279 --> 00:08:58.280 align:start position:0% consistency you need to validate that the<00:08:56.279> wires<00:08:56.790> are<00:08:57.150> correctly<00:08:57.540> citing<00:08:58.080> all<00:08:58.170> of 00:08:58.280 --> 00:08:58.290 align:start position:0% the wires are correctly citing all of 00:08:58.290 --> 00:09:01.370 align:start position:0% the wires are correctly citing all of the<00:08:58.350> gates<00:08:58.790> so<00:08:59.790> that<00:08:59.820> if<00:09:00.150> one<00:09:00.570> Apple<00:09:00.839> artisans 00:09:01.370 --> 00:09:01.380 align:start position:0% the gates so that if one Apple artisans 00:09:01.380 --> 00:09:02.840 align:start position:0% the gates so that if one Apple artisans are<00:09:01.470> like<00:09:01.589> several<00:09:01.830> other<00:09:02.160> wise<00:09:02.550> of<00:09:02.730> other 00:09:02.840 --> 00:09:02.850 align:start position:0% are like several other wise of other 00:09:02.850 --> 00:09:04.190 align:start position:0% are like several other wise of other games<00:09:03.060> that<00:09:03.240> that's<00:09:03.390> actually<00:09:03.690> done 00:09:04.190 --> 00:09:04.200 align:start position:0% games that that's actually done 00:09:04.200 --> 00:09:07.250 align:start position:0% games that that's actually done correctly<00:09:04.589> from<00:09:05.570> the<00:09:06.570> first<00:09:06.870> check<00:09:07.140> is 00:09:07.250 --> 00:09:07.260 align:start position:0% correctly from the first check is 00:09:07.260 --> 00:09:08.630 align:start position:0% correctly from the first check is reasonably<00:09:07.830> easy<00:09:08.040> to<00:09:08.130> do<00:09:08.310> this 00:09:08.630 --> 00:09:08.640 align:start position:0% reasonably easy to do this 00:09:08.640 --> 00:09:10.070 align:start position:0% reasonably easy to do this the<00:09:09.090> Secretary<00:09:09.510> has<00:09:09.570> been<00:09:09.660> the<00:09:09.900> bane<00:09:10.050> of 00:09:10.070 --> 00:09:10.080 align:start position:0% the Secretary has been the bane of 00:09:10.080 --> 00:09:12.280 align:start position:0% the Secretary has been the bane of unisys<00:09:10.770> not<00:09:10.920> sisters<00:09:11.250> for<00:09:11.370> quite<00:09:11.520> some<00:09:11.700> time 00:09:12.280 --> 00:09:12.290 align:start position:0% unisys not sisters for quite some time 00:09:12.290 --> 00:09:14.930 align:start position:0% unisys not sisters for quite some time that<00:09:13.290> was<00:09:13.830> something<00:09:14.400> which<00:09:14.460> we<00:09:14.640> think<00:09:14.760> there 00:09:14.930 --> 00:09:14.940 align:start position:0% that was something which we think there 00:09:14.940 --> 00:09:17.750 align:start position:0% that was something which we think there now<00:09:15.030> we've<00:09:15.360> made<00:09:16.350> some<00:09:16.590> brother<00:09:16.920> huge<00:09:17.220> of<00:09:17.580> some 00:09:17.750 --> 00:09:17.760 align:start position:0% now we've made some brother huge of some 00:09:17.760 --> 00:09:20.990 align:start position:0% now we've made some brother huge of some huge<00:09:18.330> family<00:09:18.980> so<00:09:19.980> I'll<00:09:20.430> start<00:09:20.610> the<00:09:20.670> little 00:09:20.990 --> 00:09:21.000 align:start position:0% huge family so I'll start the little 00:09:21.000 --> 00:09:23.000 align:start position:0% huge family so I'll start the little check<00:09:21.150> because<00:09:21.660> that's<00:09:21.960> the<00:09:22.080> relative<00:09:22.710> easy 00:09:23.000 --> 00:09:23.010 align:start position:0% check because that's the relative easy 00:09:23.010 --> 00:09:25.130 align:start position:0% check because that's the relative easy part<00:09:23.690> one<00:09:24.690> second 00:09:25.130 --> 00:09:25.140 align:start position:0% part one second 00:09:25.140 --> 00:09:30.890 align:start position:0% part one second and<00:09:25.610> I<00:09:26.810> like<00:09:27.810> to<00:09:28.020> think<00:09:28.070> about<00:09:29.660> snap<00:09:30.660> circuits 00:09:30.890 --> 00:09:30.900 align:start position:0% and I like to think about snap circuits 00:09:30.900 --> 00:09:34.730 align:start position:0% and I like to think about snap circuits and<00:09:31.290> using<00:09:31.980> vectors<00:09:33.290> assembled<00:09:34.290> angles<00:09:34.620> is 00:09:34.730 --> 00:09:34.740 align:start position:0% and using vectors assembled angles is 00:09:34.740 --> 00:09:36.530 align:start position:0% and using vectors assembled angles is polynomial<00:09:35.070> so<00:09:35.430> what<00:09:35.700> abstracting<00:09:36.300> public 00:09:36.530 --> 00:09:36.540 align:start position:0% polynomial so what abstracting public 00:09:36.540 --> 00:09:38.540 align:start position:0% polynomial so what abstracting public that<00:09:36.750> little<00:09:37.260> bit<00:09:37.350> unintuitive<00:09:37.550> factors 00:09:38.540 --> 00:09:38.550 align:start position:0% that little bit unintuitive factors 00:09:38.550 --> 00:09:39.920 align:start position:0% that little bit unintuitive factors almost<00:09:38.790> as<00:09:38.880> soon<00:09:38.970> as<00:09:39.090> well<00:09:39.300> and<00:09:39.630> then<00:09:39.750> we<00:09:39.810> can 00:09:39.920 --> 00:09:39.930 align:start position:0% almost as soon as well and then we can 00:09:39.930 --> 00:09:41.660 align:start position:0% almost as soon as well and then we can map<00:09:40.050> the<00:09:40.080> effectiveness<00:09:40.740> later<00:09:41.220> on 00:09:41.660 --> 00:09:41.670 align:start position:0% map the effectiveness later on 00:09:41.670 --> 00:09:47.540 align:start position:0% map the effectiveness later on so<00:09:42.410> in<00:09:43.410> song<00:09:43.680> we<00:09:44.070> have<00:09:44.720> one<00:09:46.070> we<00:09:47.070> want<00:09:47.250> we<00:09:47.370> want 00:09:47.540 --> 00:09:47.550 align:start position:0% so in song we have one we want we want 00:09:47.550 --> 00:09:48.760 align:start position:0% so in song we have one we want we want one<00:09:47.760> a<00:09:47.790> let<00:09:48.060> expression 00:09:48.760 --> 00:09:48.770 align:start position:0% one a let expression 00:09:48.770 --> 00:09:50.720 align:start position:0% one a let expression what<00:09:49.770> about<00:09:49.860> gates<00:09:50.100> whether<00:09:50.340> they<00:09:50.490> can<00:09:50.610> also 00:09:50.720 --> 00:09:50.730 align:start position:0% what about gates whether they can also 00:09:50.730 --> 00:09:53.620 align:start position:0% what about gates whether they can also pick<00:09:50.910> a<00:09:50.940> traditional<00:09:51.330> Gators<00:09:51.630> is<00:09:51.750> suffice<00:09:52.470> the 00:09:53.620 --> 00:09:53.630 align:start position:0% pick a traditional Gators is suffice the 00:09:53.630 --> 00:09:57.740 align:start position:0% pick a traditional Gators is suffice the verification<00:09:56.000> and<00:09:57.000> so<00:09:57.150> you<00:09:57.240> can<00:09:57.360> do<00:09:57.480> this<00:09:57.570> with 00:09:57.740 --> 00:09:57.750 align:start position:0% verification and so you can do this with 00:09:57.750 --> 00:10:00.410 align:start position:0% verification and so you can do this with a<00:09:57.780> positive<00:09:57.960> selector<00:09:58.590> factors<00:09:59.370> so<00:09:59.700> if<00:09:59.880> W<00:10:00.330> a 00:10:00.410 --> 00:10:00.420 align:start position:0% a positive selector factors so if W a 00:10:00.420 --> 00:10:02.330 align:start position:0% a positive selector factors so if W a help<00:10:00.570> them<00:10:00.660> depart<00:10:00.930> on<00:10:01.170> the<00:10:01.260> vector<00:10:01.830> say<00:10:02.070> look 00:10:02.330 --> 00:10:02.340 align:start position:0% help them depart on the vector say look 00:10:02.340 --> 00:10:04.250 align:start position:0% help them depart on the vector say look at<00:10:02.430> the<00:10:02.520> first<00:10:02.760> man<00:10:02.910> acquires<00:10:03.120> the<00:10:03.960> gates<00:10:04.140> into 00:10:04.250 --> 00:10:04.260 align:start position:0% at the first man acquires the gates into 00:10:04.260 --> 00:10:07.670 align:start position:0% at the first man acquires the gates into a<00:10:04.350> circuit<00:10:04.680> then<00:10:05.340> by<00:10:06.090> taking<00:10:06.630> dot<00:10:07.350> products 00:10:07.670 --> 00:10:07.680 align:start position:0% a circuit then by taking dot products 00:10:07.680 --> 00:10:09.830 align:start position:0% a circuit then by taking dot products with<00:10:08.040> these<00:10:08.340> vectors<00:10:08.670> and<00:10:08.820> selector<00:10:09.600> vectors 00:10:09.830 --> 00:10:09.840 align:start position:0% with these vectors and selector vectors 00:10:09.840 --> 00:10:11.180 align:start position:0% with these vectors and selector vectors that<00:10:09.960> kind<00:10:10.260> of<00:10:10.290> defines<00:10:10.650> when<00:10:11.070> you've 00:10:11.180 --> 00:10:11.190 align:start position:0% that kind of defines when you've 00:10:11.190 --> 00:10:13.850 align:start position:0% that kind of defines when you've compiled<00:10:11.640> the<00:10:11.850> circuit<00:10:12.380> because<00:10:13.380> so<00:10:13.590> they 00:10:13.850 --> 00:10:13.860 align:start position:0% compiled the circuit because so they 00:10:13.860 --> 00:10:16.400 align:start position:0% compiled the circuit because so they they<00:10:14.130> they<00:10:14.490> face<00:10:15.210> it<00:10:15.330> by<00:10:15.390> the<00:10:15.450> circuit<00:10:15.810> very<00:10:16.200> or 00:10:16.400 --> 00:10:16.410 align:start position:0% they they face it by the circuit very or 00:10:16.410 --> 00:10:18.260 align:start position:0% they they face it by the circuit very or not<00:10:16.680> be<00:10:16.860> that<00:10:17.160> not<00:10:17.370> be<00:10:17.520> improved<00:10:17.880> constructor 00:10:18.260 --> 00:10:18.270 align:start position:0% not be that not be improved constructor 00:10:18.270 --> 00:10:20.270 align:start position:0% not be that not be improved constructor then<00:10:19.260> you<00:10:19.380> can<00:10:19.500> either<00:10:19.590> turn<00:10:19.830> over<00:10:20.070> other 00:10:20.270 --> 00:10:20.280 align:start position:0% then you can either turn over other 00:10:20.280 --> 00:10:21.650 align:start position:0% then you can either turn over other multiplication<00:10:20.880> people<00:10:21.120> in<00:10:21.180> addition<00:10:21.480> games 00:10:21.650 --> 00:10:21.660 align:start position:0% multiplication people in addition games 00:10:21.660 --> 00:10:23.930 align:start position:0% multiplication people in addition games for<00:10:21.900> one<00:10:22.020> of<00:10:22.140> these<00:10:22.200> indices<00:10:22.560> so<00:10:23.490> this<00:10:23.850> you 00:10:23.930 --> 00:10:23.940 align:start position:0% for one of these indices so this you 00:10:23.940 --> 00:10:26.810 align:start position:0% for one of these indices so this you kind<00:10:24.180> of<00:10:24.920> clarify<00:10:25.920> if<00:10:26.130> you<00:10:26.160> want<00:10:26.430> so<00:10:26.580> it's<00:10:26.700> one 00:10:26.810 --> 00:10:26.820 align:start position:0% kind of clarify if you want so it's one 00:10:26.820 --> 00:10:28.580 align:start position:0% kind of clarify if you want so it's one of<00:10:26.910> these<00:10:27.030> rooms<00:10:27.630> to<00:10:27.930> be<00:10:28.050> a<00:10:28.080> multiplication 00:10:28.580 --> 00:10:28.590 align:start position:0% of these rooms to be a multiplication 00:10:28.590 --> 00:10:30.800 align:start position:0% of these rooms to be a multiplication native<00:10:29.190> make<00:10:29.340> sure<00:10:29.460> that<00:10:29.640> the<00:10:29.790> QL<00:10:30.150> value<00:10:30.720> at 00:10:30.800 --> 00:10:30.810 align:start position:0% native make sure that the QL value at 00:10:30.810 --> 00:10:32.810 align:start position:0% native make sure that the QL value at that<00:10:30.870> you<00:10:30.990> are<00:10:31.110> 1936<00:10:31.710> Ponderosa<00:10:32.310> Center<00:10:32.550> serum 00:10:32.810 --> 00:10:32.820 align:start position:0% that you are 1936 Ponderosa Center serum 00:10:32.820 --> 00:10:34.880 align:start position:0% that you are 1936 Ponderosa Center serum that<00:10:33.570> I<00:10:33.690> have<00:10:33.900> complications<00:10:34.500> and<00:10:34.590> civility 00:10:34.880 --> 00:10:34.890 align:start position:0% that I have complications and civility 00:10:34.890 --> 00:10:36.620 align:start position:0% that I have complications and civility perdition's<00:10:35.340> you<00:10:35.880> would<00:10:36.000> simply<00:10:36.240> the 00:10:36.620 --> 00:10:36.630 align:start position:0% perdition's you would simply the 00:10:36.630 --> 00:10:38.150 align:start position:0% perdition's you would simply the multiplication<00:10:36.840> will<00:10:37.440> get<00:10:37.560> sir<00:10:37.680> to<00:10:37.890> deserve 00:10:38.150 --> 00:10:38.160 align:start position:0% multiplication will get sir to deserve 00:10:38.160 --> 00:10:41.750 align:start position:0% multiplication will get sir to deserve you<00:10:38.940> can<00:10:39.090> also<00:10:39.530> use<00:10:40.530> these<00:10:40.680> selector<00:10:41.250> vectors 00:10:41.750 --> 00:10:41.760 align:start position:0% you can also use these selector vectors 00:10:41.760 --> 00:10:43.820 align:start position:0% you can also use these selector vectors to<00:10:42.030> scale<00:10:42.360> up<00:10:42.600> or<00:10:42.780> down<00:10:42.930> values<00:10:43.440> of<00:10:43.590> the<00:10:43.680> wire 00:10:43.820 --> 00:10:43.830 align:start position:0% to scale up or down values of the wire 00:10:43.830 --> 00:10:46.370 align:start position:0% to scale up or down values of the wire speaking<00:10:44.220> to<00:10:44.340> this<00:10:44.400> case<00:10:44.780> necessary<00:10:45.780> and<00:10:45.960> you 00:10:46.370 --> 00:10:46.380 align:start position:0% speaking to this case necessary and you 00:10:46.380 --> 00:10:48.500 align:start position:0% speaking to this case necessary and you also<00:10:46.530> have<00:10:46.740> invented<00:10:47.580> a<00:10:47.730> constant 00:10:48.500 --> 00:10:48.510 align:start position:0% also have invented a constant 00:10:48.510 --> 00:10:51.920 align:start position:0% also have invented a constant coefficients<00:10:48.990> of<00:10:49.020> doing<00:10:49.290> it<00:10:49.380> so<00:10:50.750> this<00:10:51.750> is<00:10:51.900> a 00:10:51.920 --> 00:10:51.930 align:start position:0% coefficients of doing it so this is a 00:10:51.930 --> 00:10:55.400 align:start position:0% coefficients of doing it so this is a kind<00:10:52.110> of<00:10:52.460> example<00:10:53.460> to<00:10:53.940> help<00:10:54.000> that<00:10:54.510> vitalik<00:10:54.990> the 00:10:55.400 --> 00:10:55.410 align:start position:0% kind of example to help that vitalik the 00:10:55.410 --> 00:10:57.060 align:start position:0% kind of example to help that vitalik the dominant<00:10:55.890> in<00:10:56.460> his<00:10:56.610> blog 00:10:57.060 --> 00:10:57.070 align:start position:0% dominant in his blog 00:10:57.070 --> 00:10:59.129 align:start position:0% dominant in his blog never<00:10:57.550> would<00:10:58.240> be<00:10:58.329> healthy<00:10:58.570> to<00:10:58.660> go<00:10:58.750> through<00:10:58.930> the 00:10:59.129 --> 00:10:59.139 align:start position:0% never would be healthy to go through the 00:10:59.139 --> 00:11:01.230 align:start position:0% never would be healthy to go through the kindest<00:10:59.470> elucidate<00:10:59.980> a<00:11:00.250> little<00:11:00.850> bit<00:11:00.970> what<00:11:01.120> it 00:11:01.230 --> 00:11:01.240 align:start position:0% kindest elucidate a little bit what it 00:11:01.240 --> 00:11:02.129 align:start position:0% kindest elucidate a little bit what it looks<00:11:01.389> like<00:11:01.540> to<00:11:01.690> actually<00:11:01.779> represent 00:11:02.129 --> 00:11:02.139 align:start position:0% looks like to actually represent 00:11:02.139 --> 00:11:06.480 align:start position:0% looks like to actually represent programís<00:11:02.769> episode<00:11:03.190> so<00:11:03.970> this<00:11:04.120> is<00:11:04.209> a<00:11:05.490> small 00:11:06.480 --> 00:11:06.490 align:start position:0% programís episode so this is a small 00:11:06.490 --> 00:11:08.100 align:start position:0% programís episode so this is a small example<00:11:06.699> where<00:11:07.029> you<00:11:07.509> have<00:11:07.540> a<00:11:07.630> circuit<00:11:07.990> where 00:11:08.100 --> 00:11:08.110 align:start position:0% example where you have a circuit where 00:11:08.110 --> 00:11:10.230 align:start position:0% example where you have a circuit where you<00:11:08.230> have<00:11:08.380> some<00:11:08.560> input<00:11:08.740> value<00:11:09.250> x1<00:11:09.670> check<00:11:10.060> that 00:11:10.230 --> 00:11:10.240 align:start position:0% you have some input value x1 check that 00:11:10.240 --> 00:11:12.829 align:start position:0% you have some input value x1 check that the<00:11:10.300> amplifier<00:11:10.690> is<00:11:10.959> executors<00:11:11.440> sexual<00:11:11.740> spoken 00:11:12.829 --> 00:11:12.839 align:start position:0% the amplifier is executors sexual spoken 00:11:12.839 --> 00:11:15.090 align:start position:0% the amplifier is executors sexual spoken and<00:11:13.839> so<00:11:14.079> you<00:11:14.139> have<00:11:14.410> their<00:11:14.829> first 00:11:15.090 --> 00:11:15.100 align:start position:0% and so you have their first 00:11:15.100 --> 00:11:16.319 align:start position:0% and so you have their first multiplication<00:11:15.370> gate<00:11:15.759> to<00:11:15.880> the<00:11:15.970> left<00:11:16.120> of<00:11:16.209> my 00:11:16.319 --> 00:11:16.329 align:start position:0% multiplication gate to the left of my 00:11:16.329 --> 00:11:19.079 align:start position:0% multiplication gate to the left of my wires<00:11:16.569> are<00:11:16.930> going<00:11:16.959> to<00:11:17.199> be<00:11:17.319> feeding<00:11:18.279> X<00:11:18.550> into<00:11:19.000> the 00:11:19.079 --> 00:11:19.089 align:start position:0% wires are going to be feeding X into the 00:11:19.089 --> 00:11:20.340 align:start position:0% wires are going to be feeding X into the gates<00:11:19.269> of<00:11:19.449> the<00:11:19.540> album<00:11:19.720> should<00:11:19.870> be<00:11:19.959> AB<00:11:20.050> squared 00:11:20.340 --> 00:11:20.350 align:start position:0% gates of the album should be AB squared 00:11:20.350 --> 00:11:22.290 align:start position:0% gates of the album should be AB squared and<00:11:20.740> then<00:11:21.040> in<00:11:21.399> the<00:11:21.550> second<00:11:21.819> gate<00:11:21.940> people<00:11:22.089> that 00:11:22.290 --> 00:11:22.300 align:start position:0% and then in the second gate people that 00:11:22.300 --> 00:11:24.600 align:start position:0% and then in the second gate people that wasn't<00:11:22.540> planning<00:11:22.720> place<00:11:23.019> square<00:11:23.769> by<00:11:23.980> X<00:11:24.100> well 00:11:24.600 --> 00:11:24.610 align:start position:0% wasn't planning place square by X well 00:11:24.610 --> 00:11:26.189 align:start position:0% wasn't planning place square by X well I'll<00:11:24.730> get<00:11:24.940> X<00:11:25.089> cubed<00:11:25.360> because<00:11:25.810> then<00:11:25.930> having 00:11:26.189 --> 00:11:26.199 align:start position:0% I'll get X cubed because then having 00:11:26.199 --> 00:11:28.920 align:start position:0% I'll get X cubed because then having that<00:11:26.230> together<00:11:26.829> with<00:11:27.160> X<00:11:27.490> and<00:11:28.480> then<00:11:28.600> finally 00:11:28.920 --> 00:11:28.930 align:start position:0% that together with X and then finally 00:11:28.930 --> 00:11:32.850 align:start position:0% that together with X and then finally having<00:11:29.079> yeah<00:11:30.069> that<00:11:30.430> 5<00:11:31.139> just<00:11:32.139> one<00:11:32.380> small<00:11:32.680> caveat 00:11:32.850 --> 00:11:32.860 align:start position:0% having yeah that 5 just one small caveat 00:11:32.860 --> 00:11:34.559 align:start position:0% having yeah that 5 just one small caveat actually<00:11:33.279> you<00:11:33.759> don't<00:11:33.940> need<00:11:34.269> that<00:11:34.389> much 00:11:34.559 --> 00:11:34.569 align:start position:0% actually you don't need that much 00:11:34.569 --> 00:11:36.379 align:start position:0% actually you don't need that much multiplication<00:11:35.199> table<00:11:35.440> because<00:11:35.680> you<00:11:35.709> can 00:11:36.379 --> 00:11:36.389 align:start position:0% multiplication table because you can 00:11:36.389 --> 00:11:38.840 align:start position:0% multiplication table because you can feed<00:11:37.389> five<00:11:37.660> hits<00:11:37.839> and<00:11:37.930> constant<00:11:38.319> to<00:11:38.380> this<00:11:38.500> game 00:11:38.840 --> 00:11:38.850 align:start position:0% feed five hits and constant to this game 00:11:38.850 --> 00:11:42.030 align:start position:0% feed five hits and constant to this game until<00:11:39.850> miss<00:11:40.180> ball<00:11:40.589> and<00:11:41.589> then<00:11:41.680> the<00:11:41.769> object 00:11:42.030 --> 00:11:42.040 align:start position:0% until miss ball and then the object 00:11:42.040 --> 00:11:45.449 align:start position:0% until miss ball and then the object should<00:11:42.160> be<00:11:42.220> certified<00:11:42.759> and<00:11:43.630> then<00:11:43.750> you<00:11:44.459> verify 00:11:45.449 --> 00:11:45.459 align:start position:0% should be certified and then you verify 00:11:45.459 --> 00:11:49.199 align:start position:0% should be certified and then you verify is<00:11:45.940> to<00:11:46.120> check<00:11:46.329> that<00:11:47.009> that's<00:11:48.009> the<00:11:48.459> that<00:11:49.120> you 00:11:49.199 --> 00:11:49.209 align:start position:0% is to check that that's the that you 00:11:49.209 --> 00:11:50.220 align:start position:0% is to check that that's the that you have<00:11:49.389> actually<00:11:49.660> supplied<00:11:49.930> the<00:11:50.019> correct 00:11:50.220 --> 00:11:50.230 align:start position:0% have actually supplied the correct 00:11:50.230 --> 00:11:53.189 align:start position:0% have actually supplied the correct y-values<00:11:51.420> thanks<00:11:52.420> ed<00:11:52.509> let's<00:11:52.750> watch<00:11:52.870> the<00:11:53.019> tape 00:11:53.189 --> 00:11:53.199 align:start position:0% y-values thanks ed let's watch the tape 00:11:53.199 --> 00:12:02.879 align:start position:0% y-values thanks ed let's watch the tape if<00:11:53.529> X<00:11:54.250> is<00:11:56.970> so<00:11:57.970> a<00:11:59.699> little<00:12:00.699> bit<00:12:00.910> more<00:12:01.389> of<00:12:02.170> each<00:12:02.440> so 00:12:02.879 --> 00:12:02.889 align:start position:0% if X is so a little bit more of each so 00:12:02.889 --> 00:12:05.850 align:start position:0% if X is so a little bit more of each so might<00:12:03.160> be<00:12:03.279> talking<00:12:03.459> about<00:12:03.610> vectors<00:12:04.029> but<00:12:04.860> we 00:12:05.850 --> 00:12:05.860 align:start position:0% might be talking about vectors but we 00:12:05.860 --> 00:12:07.650 align:start position:0% might be talking about vectors but we actually<00:12:06.100> want<00:12:06.279> to<00:12:06.310> be<00:12:06.399> asking<00:12:06.699> like<00:12:07.209> verify 00:12:07.650 --> 00:12:07.660 align:start position:0% actually want to be asking like verify 00:12:07.660 --> 00:12:10.379 align:start position:0% actually want to be asking like verify personales<00:12:08.230> using<00:12:08.730> polynomial<00:12:09.730> per<00:12:10.149> fitting 00:12:10.379 --> 00:12:10.389 align:start position:0% personales using polynomial per fitting 00:12:10.389 --> 00:12:12.329 align:start position:0% personales using polynomial per fitting so<00:12:11.230> how<00:12:11.410> I<00:12:11.440> treat<00:12:11.769> Matt<00:12:11.889> protectors<00:12:12.310> of 00:12:12.329 --> 00:12:12.339 align:start position:0% so how I treat Matt protectors of 00:12:12.339 --> 00:12:14.250 align:start position:0% so how I treat Matt protectors of polynomials<00:12:12.940> well<00:12:13.089> the<00:12:13.300> the<00:12:13.750> solutions<00:12:14.110> to 00:12:14.250 --> 00:12:14.260 align:start position:0% polynomials well the the solutions to 00:12:14.260 --> 00:12:17.600 align:start position:0% polynomials well the the solutions to use<00:12:14.380> something<00:12:14.529> go<00:12:14.680> to<00:12:14.709> the<00:12:14.889> brand<00:12:15.100> base<00:12:15.310> where 00:12:17.600 --> 00:12:17.610 align:start position:0% use something go to the brand base where 00:12:17.610 --> 00:12:23.370 align:start position:0% use something go to the brand base where is<00:12:20.699> any<00:12:21.699> pick<00:12:21.910> so<00:12:22.510> it's<00:12:22.690> a<00:12:22.870> special<00:12:23.050> set<00:12:23.350> of 00:12:23.370 --> 00:12:23.380 align:start position:0% is any pick so it's a special set of 00:12:23.380 --> 00:12:24.660 align:start position:0% is any pick so it's a special set of points<00:12:23.649> on<00:12:23.709> the<00:12:23.800> x-axis<00:12:24.040> so<00:12:24.399> you<00:12:24.519> have<00:12:24.639> a 00:12:24.660 --> 00:12:24.670 align:start position:0% points on the x-axis so you have a 00:12:24.670 --> 00:12:26.370 align:start position:0% points on the x-axis so you have a vector<00:12:25.000> of<00:12:25.149> Telamon<00:12:25.540> tentative<00:12:26.110> something 00:12:26.370 --> 00:12:26.380 align:start position:0% vector of Telamon tentative something 00:12:26.380 --> 00:12:30.449 align:start position:0% vector of Telamon tentative something ten<00:12:26.589> points<00:12:26.980> on<00:12:27.160> your<00:12:27.339> x<00:12:27.670> axis<00:12:28.500> so<00:12:29.500> we<00:12:29.769> use<00:12:30.310> the 00:12:30.449 --> 00:12:30.459 align:start position:0% ten points on your x axis so we use the 00:12:30.459 --> 00:12:32.699 align:start position:0% ten points on your x axis so we use the reserve<00:12:30.610> unity<00:12:30.970> for<00:12:31.149> a<00:12:31.180> further<00:12:31.569> from<00:12:32.050> the 00:12:32.699 --> 00:12:32.709 align:start position:0% reserve unity for a further from the 00:12:32.709 --> 00:12:35.189 align:start position:0% reserve unity for a further from the range<00:12:33.550> of<00:12:33.670> reasons<00:12:33.940> but<00:12:34.149> they<00:12:34.420> don't<00:12:34.600> need<00:12:35.079> to 00:12:35.189 --> 00:12:35.199 align:start position:0% range of reasons but they don't need to 00:12:35.199 --> 00:12:37.559 align:start position:0% range of reasons but they don't need to be<00:12:35.290> this<00:12:35.440> toy<00:12:35.589> example<00:12:36.060> another<00:12:37.060> gospel<00:12:37.329> a 00:12:37.559 --> 00:12:37.569 align:start position:0% be this toy example another gospel a 00:12:37.569 --> 00:12:41.009 align:start position:0% be this toy example another gospel a negative<00:12:37.899> was<00:12:38.130> being<00:12:39.130> polynomial<00:12:39.790> web<00:12:40.060> and 00:12:41.009 --> 00:12:41.019 align:start position:0% negative was being polynomial web and 00:12:41.019 --> 00:12:43.259 align:start position:0% negative was being polynomial web and one<00:12:41.199> of<00:12:41.290> the<00:12:41.380> special<00:12:41.680> points<00:12:42.029> will<00:12:43.029> evaluate 00:12:43.259 --> 00:12:43.269 align:start position:0% one of the special points will evaluate 00:12:43.269 --> 00:12:45.449 align:start position:0% one of the special points will evaluate to<00:12:43.569> 1<00:12:43.810> and<00:12:44.199> all<00:12:44.620> the<00:12:44.829> rest<00:12:45.069> it<00:12:45.189> will<00:12:45.250> evaluate 00:12:45.449 --> 00:12:45.459 align:start position:0% to 1 and all the rest it will evaluate 00:12:45.459 --> 00:12:48.500 align:start position:0% to 1 and all the rest it will evaluate to<00:12:45.760> 0<00:12:45.939> it's<00:12:46.360> effectively<00:12:46.750> a<00:12:47.649> delta<00:12:48.100> function 00:12:48.500 --> 00:12:48.510 align:start position:0% to 0 it's effectively a delta function 00:12:48.510 --> 00:12:52.079 align:start position:0% to 0 it's effectively a delta function and<00:12:49.510> you<00:12:50.019> can<00:12:50.170> use<00:12:50.319> these<00:12:50.500> two<00:12:50.709> even<00:12:50.980> code<00:12:51.160> so 00:12:52.079 --> 00:12:52.089 align:start position:0% and you can use these two even code so 00:12:52.089 --> 00:12:53.879 align:start position:0% and you can use these two even code so to<00:12:52.120> tender-back<00:12:52.720> materials<00:12:53.529> because<00:12:53.769> you 00:12:53.879 --> 00:12:53.889 align:start position:0% to tender-back materials because you 00:12:53.889 --> 00:12:59.800 align:start position:0% to tender-back materials because you take<00:12:54.160> you<00:12:55.000> map<00:12:56.790> each<00:12:57.790> vector<00:12:58.029> index<00:12:58.269> to 00:12:59.800 --> 00:12:59.810 align:start position:0% take you map each vector index to 00:12:59.810 --> 00:13:03.310 align:start position:0% take you map each vector index to the<00:13:00.020> special<00:13:01.360> points<00:13:02.360> that<00:13:02.750> you're<00:13:02.870> using<00:13:03.200> to 00:13:03.310 --> 00:13:03.320 align:start position:0% the special points that you're using to 00:13:03.320 --> 00:13:05.019 align:start position:0% the special points that you're using to be<00:13:03.380> funny<00:13:03.560> reversible<00:13:03.980> inhibits<00:13:04.370> and<00:13:04.940> then 00:13:05.019 --> 00:13:05.029 align:start position:0% be funny reversible inhibits and then 00:13:05.029 --> 00:13:06.760 align:start position:0% be funny reversible inhibits and then you<00:13:05.180> particularly<00:13:06.110> in<00:13:06.230> a<00:13:06.260> song<00:13:06.470> so<00:13:06.620> you're 00:13:06.760 --> 00:13:06.770 align:start position:0% you particularly in a song so you're 00:13:06.770 --> 00:13:08.230 align:start position:0% you particularly in a song so you're multiply<00:13:07.130> each<00:13:07.279> vector<00:13:07.460> element<00:13:07.850> by<00:13:07.910> success 00:13:08.230 --> 00:13:08.240 align:start position:0% multiply each vector element by success 00:13:08.240 --> 00:13:09.519 align:start position:0% multiply each vector element by success key<00:13:08.360> to<00:13:08.390> the<00:13:08.540> launch<00:13:08.779> mother-in-law<00:13:09.320> and<00:13:09.470> they 00:13:09.519 --> 00:13:09.529 align:start position:0% key to the launch mother-in-law and they 00:13:09.529 --> 00:13:11.380 align:start position:0% key to the launch mother-in-law and they are<00:13:09.620> something<00:13:09.830> together<00:13:10.040> and<00:13:10.400> you<00:13:11.090> will<00:13:11.180> have 00:13:11.380 --> 00:13:11.390 align:start position:0% are something together and you will have 00:13:11.390 --> 00:13:14.230 align:start position:0% are something together and you will have a<00:13:11.660> polynomial<00:13:12.110> where<00:13:12.740> at<00:13:13.310> those<00:13:13.730> special 00:13:14.230 --> 00:13:14.240 align:start position:0% a polynomial where at those special 00:13:14.240 --> 00:13:16.300 align:start position:0% a polynomial where at those special x-coordinates<00:13:14.930> a<00:13:15.020> certain<00:13:15.440> advanced<00:13:15.950> Y 00:13:16.300 --> 00:13:16.310 align:start position:0% x-coordinates a certain advanced Y 00:13:16.310 --> 00:13:18.610 align:start position:0% x-coordinates a certain advanced Y values<00:13:16.730> will<00:13:16.910> be<00:13:17.060> the<00:13:17.270> values<00:13:17.570> of<00:13:18.110> your<00:13:18.230> vector 00:13:18.610 --> 00:13:18.620 align:start position:0% values will be the values of your vector 00:13:18.620 --> 00:13:23.890 align:start position:0% values will be the values of your vector words<00:13:19.900> this<00:13:20.900> is<00:13:21.050> a<00:13:21.080> relatively<00:13:22.900> convenient 00:13:23.890 --> 00:13:23.900 align:start position:0% words this is a relatively convenient 00:13:23.900 --> 00:13:25.660 align:start position:0% words this is a relatively convenient way<00:13:24.140> of<00:13:24.170> representing<00:13:24.680> vectors<00:13:25.580> as 00:13:25.660 --> 00:13:25.670 align:start position:0% way of representing vectors as 00:13:25.670 --> 00:13:28.390 align:start position:0% way of representing vectors as polynomials<00:13:25.970> because<00:13:26.600> it<00:13:26.900> preserves<00:13:27.500> effects 00:13:28.390 --> 00:13:28.400 align:start position:0% polynomials because it preserves effects 00:13:28.400 --> 00:13:29.980 align:start position:0% polynomials because it preserves effects represent<00:13:28.910> and<00:13:29.240> that's<00:13:29.450> three<00:13:29.630> important 00:13:29.980 --> 00:13:29.990 align:start position:0% represent and that's three important 00:13:29.990 --> 00:13:30.280 align:start position:0% represent and that's three important thing 00:13:30.280 --> 00:13:30.290 align:start position:0% thing 00:13:30.290 --> 00:13:36.150 align:start position:0% thing so<00:13:31.100> mr.<00:13:31.370> Scheffer<00:13:31.760> don't<00:13:31.970> look<00:13:32.060> here<00:13:32.210> so<00:13:32.450> this 00:13:36.150 --> 00:13:36.160 align:start position:0% 00:13:36.160 --> 00:13:39.160 align:start position:0% disciplinary<00:13:37.160> series<00:13:37.580> community<00:13:37.730> and<00:13:38.270> if 00:13:39.160 --> 00:13:39.170 align:start position:0% disciplinary series community and if 00:13:39.170 --> 00:13:40.360 align:start position:0% disciplinary series community and if you're<00:13:39.350> on<00:13:39.440> the<00:13:39.500> mathematics<00:13:39.860> this'll<00:13:40.130> be 00:13:40.360 --> 00:13:40.370 align:start position:0% you're on the mathematics this'll be 00:13:40.370 --> 00:13:43.510 align:start position:0% you're on the mathematics this'll be equal<00:13:40.670> to<00:13:40.910> you<00:13:41.480> that<00:13:41.779> the<00:13:42.589> my<00:13:42.800> fruits<00:13:43.100> in<00:13:43.220> unity 00:13:43.510 --> 00:13:43.520 align:start position:0% equal to you that the my fruits in unity 00:13:43.520 --> 00:13:45.430 align:start position:0% equal to you that the my fruits in unity in<00:13:43.640> Li<00:13:43.790> X<00:13:44.089> will<00:13:44.240> be<00:13:44.330> barman<00:13:44.839> at<00:13:44.990> the<00:13:45.080> G<00:13:45.260> through 00:13:45.430 --> 00:13:45.440 align:start position:0% in Li X will be barman at the G through 00:13:45.440 --> 00:13:46.570 align:start position:0% in Li X will be barman at the G through some<00:13:45.589> than<00:13:45.710> any<00:13:45.830> other<00:13:46.040> words<00:13:46.220> we<00:13:46.339> use<00:13:46.460> is 00:13:46.570 --> 00:13:46.580 align:start position:0% some than any other words we use is 00:13:46.580 --> 00:13:51.400 align:start position:0% some than any other words we use is equal<00:13:46.940> to<00:13:47.029> zero<00:13:47.440> so<00:13:48.970> we<00:13:49.970> can<00:13:50.120> now<00:13:50.210> take<00:13:50.510> four 00:13:51.400 --> 00:13:51.410 align:start position:0% equal to zero so we can now take four 00:13:51.410 --> 00:13:52.540 align:start position:0% equal to zero so we can now take four more<00:13:51.560> vectors<00:13:51.890> and<00:13:52.190> turn<00:13:52.430> them<00:13:52.520> into 00:13:52.540 --> 00:13:52.550 align:start position:0% more vectors and turn them into 00:13:52.550 --> 00:13:55.690 align:start position:0% more vectors and turn them into polynomials<00:13:53.890> so<00:13:54.890> we're<00:13:55.070> taking<00:13:55.339> those<00:13:55.460> linear 00:13:55.690 --> 00:13:55.700 align:start position:0% polynomials so we're taking those linear 00:13:55.700 --> 00:13:56.950 align:start position:0% polynomials so we're taking those linear some<00:13:55.910> submissions<00:13:56.089> earlier<00:13:56.570> we<00:13:56.720> take 00:13:56.950 --> 00:13:56.960 align:start position:0% some submissions earlier we take 00:13:56.960 --> 00:14:02.050 align:start position:0% some submissions earlier we take elements<00:13:58.750> on<00:13:59.750> the<00:13:59.810> meticulous<00:14:00.380> on<00:14:00.910> you<00:14:01.910> this 00:14:02.050 --> 00:14:02.060 align:start position:0% elements on the meticulous on you this 00:14:02.060 --> 00:14:03.970 align:start position:0% elements on the meticulous on you this will<00:14:02.270> these<00:14:02.390> the<00:14:02.779> selector<00:14:03.320> polynomials<00:14:03.770> and 00:14:03.970 --> 00:14:03.980 align:start position:0% will these the selector polynomials and 00:14:03.980 --> 00:14:06.160 align:start position:0% will these the selector polynomials and that<00:14:04.280> uniquely<00:14:04.580> defines<00:14:05.000> a<00:14:05.330> circuit<00:14:06.020> whose 00:14:06.160 --> 00:14:06.170 align:start position:0% that uniquely defines a circuit whose 00:14:06.170 --> 00:14:07.780 align:start position:0% that uniquely defines a circuit whose mark<00:14:06.470> and<00:14:06.650> then<00:14:06.740> you<00:14:06.830> do<00:14:06.980> that<00:14:07.130> for<00:14:07.370> the<00:14:07.520> Y 00:14:07.780 --> 00:14:07.790 align:start position:0% mark and then you do that for the Y 00:14:07.790 --> 00:14:09.610 align:start position:0% mark and then you do that for the Y values<00:14:08.150> which<00:14:08.300> define<00:14:08.420> sir<00:14:08.900> one<00:14:09.170> of<00:14:09.260> the<00:14:09.440> good 00:14:09.610 --> 00:14:09.620 align:start position:0% values which define sir one of the good 00:14:09.620 --> 00:14:13.750 align:start position:0% values which define sir one of the good must<00:14:09.770> satisfy<00:14:09.920> exam<00:14:10.490> to<00:14:10.730> yourself<00:14:12.370> if<00:14:13.370> any<00:14:13.610> of 00:14:13.750 --> 00:14:13.760 align:start position:0% must satisfy exam to yourself if any of 00:14:13.760 --> 00:14:15.280 align:start position:0% must satisfy exam to yourself if any of this<00:14:13.850> is<00:14:14.030> that<00:14:14.150> you<00:14:14.240> can<00:14:14.390> take<00:14:14.570> the<00:14:14.990> vector 00:14:15.280 --> 00:14:15.290 align:start position:0% this is that you can take the vector 00:14:15.290 --> 00:14:17.380 align:start position:0% this is that you can take the vector arithmetic<00:14:15.560> that<00:14:16.490> used<00:14:16.700> to<00:14:16.820> describe<00:14:17.210> your 00:14:17.380 --> 00:14:17.390 align:start position:0% arithmetic that used to describe your 00:14:17.390 --> 00:14:19.750 align:start position:0% arithmetic that used to describe your gauge<00:14:17.660> equations<00:14:18.140> and<00:14:18.410> directly<00:14:19.400> matter<00:14:19.580> to 00:14:19.750 --> 00:14:19.760 align:start position:0% gauge equations and directly matter to 00:14:19.760 --> 00:14:21.490 align:start position:0% gauge equations and directly matter to polynomial<00:14:20.240> realtor<00:14:20.630> is<00:14:21.200> if<00:14:21.350> you<00:14:21.410> have 00:14:21.490 --> 00:14:21.500 align:start position:0% polynomial realtor is if you have 00:14:21.500 --> 00:14:23.020 align:start position:0% polynomial realtor is if you have effective<00:14:21.860> identity<00:14:22.250> which<00:14:22.400> is<00:14:22.430> equal<00:14:22.730> to<00:14:22.760> 0 00:14:23.020 --> 00:14:23.030 align:start position:0% effective identity which is equal to 0 00:14:23.030 --> 00:14:25.450 align:start position:0% effective identity which is equal to 0 everywhere<00:14:23.390> then<00:14:24.200> the<00:14:24.860> resulting<00:14:25.280> polynomial 00:14:25.450 --> 00:14:25.460 align:start position:0% everywhere then the resulting polynomial 00:14:25.460 --> 00:14:28.090 align:start position:0% everywhere then the resulting polynomial identity<00:14:26.240> will<00:14:26.720> be<00:14:26.750> equal<00:14:27.080> to<00:14:27.170> 0<00:14:27.350> modulus<00:14:27.740> this 00:14:28.090 --> 00:14:28.100 align:start position:0% identity will be equal to 0 modulus this 00:14:28.100 --> 00:14:31.240 align:start position:0% identity will be equal to 0 modulus this simple<00:14:28.820> fashion<00:14:29.150> polynomial<00:14:30.080> to<00:14:30.980> give<00:14:31.130> some 00:14:31.240 --> 00:14:31.250 align:start position:0% simple fashion polynomial to give some 00:14:31.250 --> 00:14:35.590 align:start position:0% simple fashion polynomial to give some intuition<00:14:31.430> about<00:14:31.700> why<00:14:32.030> this<00:14:32.089> is<00:14:34.360> if<00:14:35.360> we 00:14:35.590 --> 00:14:35.600 align:start position:0% intuition about why this is if we 00:14:35.600 --> 00:14:37.600 align:start position:0% intuition about why this is if we consider<00:14:35.810> like<00:14:36.710> one<00:14:36.980> of<00:14:37.070> the<00:14:37.130> special<00:14:37.400> points 00:14:37.600 --> 00:14:37.610 align:start position:0% consider like one of the special points 00:14:37.610 --> 00:14:39.820 align:start position:0% consider like one of the special points that<00:14:37.700> people<00:14:37.810> that<00:14:38.810> we<00:14:38.900> used<00:14:39.200> to<00:14:39.380> encode<00:14:39.620> these 00:14:39.820 --> 00:14:39.830 align:start position:0% that people that we used to encode these 00:14:39.830 --> 00:14:44.620 align:start position:0% that people that we used to encode these polynomials<00:14:40.900> so<00:14:41.900> say<00:14:42.140> a<00:14:42.170> peon<00:14:42.530> first<00:14:43.510> like<00:14:44.510> the 00:14:44.620 --> 00:14:44.630 align:start position:0% polynomials so say a peon first like the 00:14:44.630 --> 00:14:49.720 align:start position:0% polynomials so say a peon first like the second<00:14:45.020> is<00:14:45.290> vectors<00:14:47.709> if<00:14:48.709> we<00:14:48.860> you'd<00:14:49.370> like<00:14:49.550> you 00:14:49.720 --> 00:14:49.730 align:start position:0% second is vectors if we you'd like you 00:14:49.730 --> 00:14:50.949 align:start position:0% second is vectors if we you'd like you the<00:14:49.880> resulting<00:14:50.270> for<00:14:50.450> neighbors<00:14:50.720> that<00:14:50.839> you're 00:14:50.949 --> 00:14:50.959 align:start position:0% the resulting for neighbors that you're 00:14:50.959 --> 00:14:51.370 align:start position:0% the resulting for neighbors that you're crazy 00:14:51.370 --> 00:14:51.380 align:start position:0% crazy 00:14:51.380 --> 00:14:53.020 align:start position:0% crazy let<00:14:51.740> me<00:14:51.830> set<00:14:51.980> the<00:14:52.070> second 00:14:53.020 --> 00:14:53.030 align:start position:0% let me set the second 00:14:53.030 --> 00:14:56.320 align:start position:0% let me set the second unity<00:14:54.160> your<00:14:55.160> polynomials<00:14:55.760> will<00:14:55.880> have<00:14:56.180> the 00:14:56.320 --> 00:14:56.330 align:start position:0% unity your polynomials will have the 00:14:56.330 --> 00:15:00.010 align:start position:0% unity your polynomials will have the will<00:14:57.320> be<00:14:57.440> a<00:14:58.120> value<00:14:59.120> evaluates<00:14:59.720> to<00:14:59.990> the 00:15:00.010 --> 00:15:00.020 align:start position:0% will be a value evaluates to the 00:15:00.020 --> 00:15:02.650 align:start position:0% will be a value evaluates to the invitation<00:15:00.500> for<00:15:01.040> vectors<00:15:01.610> which<00:15:02.210> means<00:15:02.450> that 00:15:02.650 --> 00:15:02.660 align:start position:0% invitation for vectors which means that 00:15:02.660 --> 00:15:04.660 align:start position:0% invitation for vectors which means that if<00:15:02.780> you<00:15:03.170> take<00:15:03.410> a<00:15:03.620> vector<00:15:03.860> identity<00:15:04.340> was<00:15:04.460> equal 00:15:04.660 --> 00:15:04.670 align:start position:0% if you take a vector identity was equal 00:15:04.670 --> 00:15:06.880 align:start position:0% if you take a vector identity was equal to<00:15:04.730> zero<00:15:04.910> then<00:15:05.720> there<00:15:06.350> was<00:15:06.440> a<00:15:06.560> common<00:15:06.830> a 00:15:06.880 --> 00:15:06.890 align:start position:0% to zero then there was a common a 00:15:06.890 --> 00:15:08.410 align:start position:0% to zero then there was a common a validity<00:15:07.130> or<00:15:07.370> physical<00:15:07.760> polynomial<00:15:08.240> where 00:15:08.410 --> 00:15:08.420 align:start position:0% validity or physical polynomial where 00:15:08.420 --> 00:15:10.830 align:start position:0% validity or physical polynomial where and<00:15:08.990> that<00:15:09.590> immunity<00:15:10.190> would<00:15:10.280> also<00:15:10.430> be<00:15:10.640> zero 00:15:10.830 --> 00:15:10.840 align:start position:0% and that immunity would also be zero 00:15:10.840 --> 00:15:13.000 align:start position:0% and that immunity would also be zero which<00:15:11.840> means<00:15:11.900> a<00:15:12.140> if<00:15:12.260> the<00:15:12.380> specter<00:15:12.710> identity 00:15:13.000 --> 00:15:13.010 align:start position:0% which means a if the specter identity 00:15:13.010 --> 00:15:16.180 align:start position:0% which means a if the specter identity holds<00:15:13.130> then<00:15:13.790> the<00:15:13.940> resulting<00:15:14.720> polynomial<00:15:15.190> will 00:15:16.180 --> 00:15:16.190 align:start position:0% holds then the resulting polynomial will 00:15:16.190 --> 00:15:18.730 align:start position:0% holds then the resulting polynomial will be<00:15:16.220> zero<00:15:16.790> at<00:15:17.090> all<00:15:17.270> of<00:15:17.420> the<00:15:17.570> recipients<00:15:18.290> special 00:15:18.730 --> 00:15:18.740 align:start position:0% be zero at all of the recipients special 00:15:18.740 --> 00:15:21.010 align:start position:0% be zero at all of the recipients special axis<00:15:19.070> once<00:15:19.340> they<00:15:19.490> introduce<00:15:19.970> you<00:15:20.420> in<00:15:20.600> advance 00:15:21.010 --> 00:15:21.020 align:start position:0% axis once they introduce you in advance 00:15:21.020 --> 00:15:23.950 align:start position:0% axis once they introduce you in advance and<00:15:21.830> so<00:15:22.190> the<00:15:22.340> banishing<00:15:22.610> polynomial<00:15:23.180> is<00:15:23.420> the 00:15:23.950 --> 00:15:23.960 align:start position:0% and so the banishing polynomial is the 00:15:23.960 --> 00:15:25.480 align:start position:0% and so the banishing polynomial is the lowest<00:15:24.260> to<00:15:24.350> be<00:15:24.440> polynomial<00:15:24.950> that<00:15:25.040> is<00:15:25.100> also 00:15:25.480 --> 00:15:25.490 align:start position:0% lowest to be polynomial that is also 00:15:25.490 --> 00:15:27.370 align:start position:0% lowest to be polynomial that is also equal<00:15:25.970> to<00:15:26.000> zero<00:15:26.270> at<00:15:26.540> all<00:15:26.750> the<00:15:26.840> rest<00:15:26.990> of<00:15:27.110> unity 00:15:27.370 --> 00:15:27.380 align:start position:0% equal to zero at all the rest of unity 00:15:27.380 --> 00:15:29.260 align:start position:0% equal to zero at all the rest of unity so<00:15:27.710> you<00:15:27.770> know<00:15:28.190> that<00:15:28.430> if<00:15:29.030> you<00:15:29.150> have<00:15:29.240> a 00:15:29.260 --> 00:15:29.270 align:start position:0% so you know that if you have a 00:15:29.270 --> 00:15:30.580 align:start position:0% so you know that if you have a satisfying<00:15:29.690> assignment<00:15:30.110> you're<00:15:30.200> a<00:15:30.230> second 00:15:30.580 --> 00:15:30.590 align:start position:0% satisfying assignment you're a second 00:15:30.590 --> 00:15:33.070 align:start position:0% satisfying assignment you're a second then<00:15:31.250> this<00:15:31.820> polynomial<00:15:32.150> is<00:15:32.480> he<00:15:32.660> will<00:15:32.780> always 00:15:33.070 --> 00:15:33.080 align:start position:0% then this polynomial is he will always 00:15:33.080 --> 00:15:34.450 align:start position:0% then this polynomial is he will always be<00:15:33.200> divisible<00:15:33.440> by<00:15:33.680> that<00:15:33.890> vanishing<00:15:34.250> to<00:15:34.340> the 00:15:34.450 --> 00:15:34.460 align:start position:0% be divisible by that vanishing to the 00:15:34.460 --> 00:15:36.730 align:start position:0% be divisible by that vanishing to the number<00:15:34.700> and<00:15:35.000> you<00:15:35.060> can<00:15:35.390> test<00:15:35.870> for<00:15:36.020> that<00:15:36.080> so 00:15:36.730 --> 00:15:36.740 align:start position:0% number and you can test for that so 00:15:36.740 --> 00:15:51.160 align:start position:0% number and you can test for that so check<00:15:36.980> that<00:15:37.010> you've<00:15:37.220> correctly 00:15:51.160 --> 00:15:51.170 align:start position:0% 00:15:51.170 --> 00:15:54.190 align:start position:0% [Music] 00:15:54.190 --> 00:15:54.200 align:start position:0% [Music] 00:15:54.200 --> 00:15:55.780 align:start position:0% [Music] by<00:15:54.710> the<00:15:54.770> way<00:15:54.920> feel<00:15:55.100> free<00:15:55.160> to<00:15:55.280> ask<00:15:55.550> such<00:15:55.700> a 00:15:55.780 --> 00:15:55.790 align:start position:0% by the way feel free to ask such a 00:15:55.790 --> 00:15:59.170 align:start position:0% by the way feel free to ask such a question<00:15:55.820> settle<00:15:56.480> anything<00:15:57.070> imagine<00:15:58.180> you 00:15:59.170 --> 00:15:59.180 align:start position:0% question settle anything imagine you 00:15:59.180 --> 00:16:00.910 align:start position:0% question settle anything imagine you have<00:15:59.330> any<00:15:59.480> questions<00:15:59.960> it's<00:16:00.440> suspected<00:16:00.710> not 00:16:00.910 --> 00:16:00.920 align:start position:0% have any questions it's suspected not 00:16:00.920 --> 00:16:03.370 align:start position:0% have any questions it's suspected not than<00:16:01.040> he<00:16:01.130> was<00:16:01.570> so<00:16:02.570> if<00:16:02.870> you<00:16:02.960> have<00:16:03.170> you<00:16:03.260> met 00:16:03.370 --> 00:16:03.380 align:start position:0% than he was so if you have you met 00:16:03.380 --> 00:16:05.200 align:start position:0% than he was so if you have you met review<00:16:03.620> the<00:16:03.710> bill<00:16:03.860> now<00:16:04.280> now<00:16:04.640> we've<00:16:04.790> talked 00:16:05.200 --> 00:16:05.210 align:start position:0% review the bill now now we've talked 00:16:05.210 --> 00:16:07.630 align:start position:0% review the bill now now we've talked about<00:16:05.420> great<00:16:05.900> you<00:16:06.800> can<00:16:06.950> you<00:16:07.160> can<00:16:07.280> check<00:16:07.460> their 00:16:07.630 --> 00:16:07.640 align:start position:0% about great you can you can check their 00:16:07.640 --> 00:16:10.260 align:start position:0% about great you can you can check their every<00:16:07.820> case<00:16:08.270> in<00:16:08.600> your<00:16:08.900> circuit<00:16:09.620> isn't 00:16:10.260 --> 00:16:10.270 align:start position:0% every case in your circuit isn't 00:16:10.270 --> 00:16:12.040 align:start position:0% every case in your circuit isn't currently<00:16:11.270> evaluated<00:16:11.750> but<00:16:11.840> have<00:16:11.960> you 00:16:12.040 --> 00:16:12.050 align:start position:0% currently evaluated but have you 00:16:12.050 --> 00:16:14.010 align:start position:0% currently evaluated but have you technically<00:16:12.350> battery<00:16:12.650> miserable<00:16:13.490> -<00:16:13.610> together 00:16:14.010 --> 00:16:14.020 align:start position:0% technically battery miserable - together 00:16:14.020 --> 00:16:16.410 align:start position:0% technically battery miserable - together well<00:16:15.020> that's<00:16:15.110> a<00:16:15.260> little<00:16:15.410> bit<00:16:15.590> tricky<00:16:16.070> because 00:16:16.410 --> 00:16:16.420 align:start position:0% well that's a little bit tricky because 00:16:16.420 --> 00:16:19.420 align:start position:0% well that's a little bit tricky because all<00:16:17.420> you<00:16:17.540> need<00:16:17.600> to<00:16:17.780> do<00:16:17.900> effectively<00:16:18.320> is<00:16:18.590> if<00:16:19.370> you 00:16:19.420 --> 00:16:19.430 align:start position:0% all you need to do effectively is if you 00:16:19.430 --> 00:16:21.010 align:start position:0% all you need to do effectively is if you have<00:16:19.610> a<00:16:19.640> look<00:16:19.820> at<00:16:19.880> an<00:16:20.030> apple<00:16:20.210> wire<00:16:20.510> from<00:16:20.960> one 00:16:21.010 --> 00:16:21.020 align:start position:0% have a look at an apple wire from one 00:16:21.020 --> 00:16:23.260 align:start position:0% have a look at an apple wire from one day<00:16:21.260> that<00:16:21.440> leads<00:16:21.650> to<00:16:21.800> multiple<00:16:21.950> amplifiers<00:16:22.550> in 00:16:23.260 --> 00:16:23.270 align:start position:0% day that leads to multiple amplifiers in 00:16:23.270 --> 00:16:24.040 align:start position:0% day that leads to multiple amplifiers in the<00:16:23.420> polychaetes 00:16:24.040 --> 00:16:24.050 align:start position:0% the polychaetes 00:16:24.050 --> 00:16:26.290 align:start position:0% the polychaetes each<00:16:24.770> fx50<00:16:25.190> check<00:16:25.490> that<00:16:25.610> that<00:16:25.730> wire<00:16:25.910> values 00:16:26.290 --> 00:16:26.300 align:start position:0% each fx50 check that that wire values 00:16:26.300 --> 00:16:34.360 align:start position:0% each fx50 check that that wire values being<00:16:26.480> copied<00:16:26.720> correctly<00:16:27.490> that's<00:16:33.370> something 00:16:34.360 --> 00:16:34.370 align:start position:0% being copied correctly that's something 00:16:34.370 --> 00:16:36.690 align:start position:0% being copied correctly that's something like<00:16:34.460> that's<00:16:34.580> a<00:16:34.700> little<00:16:34.910> bit<00:16:35.000> odd<00:16:35.300> nonlinear 00:16:36.690 --> 00:16:36.700 align:start position:0% like that's a little bit odd nonlinear 00:16:36.700 --> 00:16:38.740 align:start position:0% like that's a little bit odd nonlinear and<00:16:37.700> the<00:16:37.820> way<00:16:37.940> that<00:16:38.090> we<00:16:38.180> achieve<00:16:38.240> is<00:16:38.510> applause 00:16:38.740 --> 00:16:38.750 align:start position:0% and the way that we achieve is applause 00:16:38.750 --> 00:16:40.690 align:start position:0% and the way that we achieve is applause with<00:16:38.930> the<00:16:38.990> permutation<00:16:39.500> check<00:16:39.650> and<00:16:40.550> so 00:16:40.690 --> 00:16:40.700 align:start position:0% with the permutation check and so 00:16:40.700 --> 00:16:44.410 align:start position:0% with the permutation check and so limitations<00:16:42.790> somewhat<00:16:43.790> the<00:16:43.910> Heights<00:16:44.120> event 00:16:44.410 --> 00:16:44.420 align:start position:0% limitations somewhat the Heights event 00:16:44.420 --> 00:16:46.180 align:start position:0% limitations somewhat the Heights event brother<00:16:44.690> they're<00:16:44.960> rather<00:16:45.110> terrifying<00:16:46.070> this 00:16:46.180 --> 00:16:46.190 align:start position:0% brother they're rather terrifying this 00:16:46.190 --> 00:16:48.130 align:start position:0% brother they're rather terrifying this to<00:16:46.310> moments<00:16:46.670> but<00:16:46.910> I<00:16:47.000> will<00:16:47.120> find<00:16:47.360> this<00:16:47.540> trying 00:16:48.130 --> 00:16:48.140 align:start position:0% to moments but I will find this trying 00:16:48.140 --> 00:16:49.960 align:start position:0% to moments but I will find this trying to<00:16:48.260> dense<00:16:48.440> down<00:16:48.680> the<00:16:49.130> intuition<00:16:49.550> behind<00:16:49.580> why 00:16:49.960 --> 00:16:49.970 align:start position:0% to dense down the intuition behind why 00:16:49.970 --> 00:16:52.120 align:start position:0% to dense down the intuition behind why do<00:16:50.030> you<00:16:50.210> some<00:16:50.360> permutations<00:16:51.130> effectively 00:16:52.120 --> 00:16:52.130 align:start position:0% do you some permutations effectively 00:16:52.130 --> 00:16:54.220 align:start position:0% do you some permutations effectively what<00:16:52.250> we're<00:16:52.400> doing<00:16:52.640> is<00:16:52.970> if<00:16:53.660> you<00:16:53.780> take<00:16:53.930> all<00:16:54.200> of 00:16:54.220 --> 00:16:54.230 align:start position:0% what we're doing is if you take all of 00:16:54.230 --> 00:16:57.340 align:start position:0% what we're doing is if you take all of the<00:16:54.410> wire<00:16:54.620> that<00:16:55.340> wire<00:16:55.760> values<00:16:56.540> in<00:16:57.200> your 00:16:57.340 --> 00:16:57.350 align:start position:0% the wire that wire values in your 00:16:57.350 --> 00:17:00.670 align:start position:0% the wire that wire values in your circuit<00:16:58.000> you<00:16:59.000> can<00:16:59.030> map<00:16:59.750> them<00:16:59.990> to<00:17:00.230> us<00:17:00.350> into<00:17:00.590> a 00:17:00.670 --> 00:17:00.680 align:start position:0% circuit you can map them to us into a 00:17:00.680 --> 00:17:02.500 align:start position:0% circuit you can map them to us into a car<00:17:00.890> market<00:17:01.160> you<00:17:01.310> deform<00:17:01.610> in<00:17:01.760> space<00:17:01.970> you<00:17:02.300> take 00:17:02.500 --> 00:17:02.510 align:start position:0% car market you deform in space you take 00:17:02.510 --> 00:17:04.720 align:start position:0% car market you deform in space you take the<00:17:02.840> the<00:17:03.170> value<00:17:03.440> of<00:17:03.500> the<00:17:03.560> wire<00:17:03.770> and<00:17:04.100> remember 00:17:04.720 --> 00:17:04.730 align:start position:0% the the value of the wire and remember 00:17:04.730 --> 00:17:08.860 align:start position:0% the the value of the wire and remember to<00:17:04.910> look<00:17:05.000> at<00:17:05.150> unique<00:17:05.829> a<00:17:06.829> unique<00:17:07.120> value<00:17:08.120> on 00:17:08.860 --> 00:17:08.870 align:start position:0% to look at unique a unique value on 00:17:08.870 --> 00:17:11.800 align:start position:0% to look at unique a unique value on right<00:17:09.140> senses<00:17:09.530> and<00:17:10.209> there<00:17:11.209> isn't<00:17:11.449> been<00:17:11.570> the 00:17:11.800 --> 00:17:11.810 align:start position:0% right senses and there isn't been the 00:17:11.810 --> 00:17:13.199 align:start position:0% right senses and there isn't been the results<00:17:12.140> that<00:17:12.199> actually<00:17:12.290> have<00:17:12.530> set<00:17:12.709> up<00:17:12.829> once 00:17:13.199 --> 00:17:13.209 align:start position:0% results that actually have set up once 00:17:13.209 --> 00:17:16.390 align:start position:0% results that actually have set up once one<00:17:14.209> for<00:17:14.329> each<00:17:14.420> of<00:17:14.449> the<00:17:14.630> items<00:17:14.660> you<00:17:15.260> can<00:17:16.220> then 00:17:16.390 --> 00:17:16.400 align:start position:0% one for each of the items you can then 00:17:16.400 --> 00:17:19.390 align:start position:0% one for each of the items you can then perform<00:17:17.329> the<00:17:17.570> same<00:17:17.780> mapping<00:17:18.170> but<00:17:18.650> instead<00:17:19.040> you 00:17:19.390 --> 00:17:19.400 align:start position:0% perform the same mapping but instead you 00:17:19.400 --> 00:17:22.770 align:start position:0% perform the same mapping but instead you map<00:17:19.699> your<00:17:20.360> you<00:17:21.230> map<00:17:21.410> your<00:17:21.440> Y<00:17:21.770> values<00:17:22.130> to 00:17:22.770 --> 00:17:22.780 align:start position:0% map your you map your Y values to 00:17:22.780 --> 00:17:27.160 align:start position:0% map your you map your Y values to different<00:17:23.780> form<00:17:24.020> but<00:17:24.820> in<00:17:25.820> such<00:17:26.420> a<00:17:26.449> way<00:17:26.839> that 00:17:27.160 --> 00:17:27.170 align:start position:0% different form but in such a way that 00:17:27.170 --> 00:17:29.230 align:start position:0% different form but in such a way that for<00:17:27.980> example<00:17:28.040> if<00:17:28.370> you<00:17:28.459> have<00:17:28.610> three<00:17:28.640> values 00:17:29.230 --> 00:17:29.240 align:start position:0% for example if you have three values 00:17:29.240 --> 00:17:31.150 align:start position:0% for example if you have three values that<00:17:29.570> need<00:17:29.780> to<00:17:30.080> be<00:17:30.110> the<00:17:30.290> same<00:17:30.530> because<00:17:30.830> they're 00:17:31.150 --> 00:17:31.160 align:start position:0% that need to be the same because they're 00:17:31.160 --> 00:17:34.060 align:start position:0% that need to be the same because they're they're<00:17:31.430> copies<00:17:31.700> of<00:17:31.820> each<00:17:31.880> other<00:17:32.090> then<00:17:33.070> you 00:17:34.060 --> 00:17:34.070 align:start position:0% they're copies of each other then you 00:17:34.070 --> 00:17:36.340 align:start position:0% they're copies of each other then you want<00:17:34.220> to<00:17:34.340> effectively<00:17:35.180> map<00:17:35.540> those<00:17:36.140> three 00:17:36.340 --> 00:17:36.350 align:start position:0% want to effectively map those three 00:17:36.350 --> 00:17:38.320 align:start position:0% want to effectively map those three wires<00:17:36.560> into<00:17:36.980> the<00:17:37.070> single<00:17:37.460> net<00:17:37.580> space<00:17:37.760> visited 00:17:38.320 --> 00:17:38.330 align:start position:0% wires into the single net space visited 00:17:38.330 --> 00:17:39.910 align:start position:0% wires into the single net space visited form<00:17:38.510> order<00:17:38.720> and<00:17:39.020> what<00:17:39.110> I<00:17:39.140> mean<00:17:39.320> by<00:17:39.440> this<00:17:39.500> is 00:17:39.910 --> 00:17:39.920 align:start position:0% form order and what I mean by this is 00:17:39.920 --> 00:17:43.270 align:start position:0% form order and what I mean by this is for<00:17:40.400> example<00:17:40.490> imagine<00:17:40.880> you<00:17:41.750> have<00:17:42.070> three<00:17:43.070> wires 00:17:43.270 --> 00:17:43.280 align:start position:0% for example imagine you have three wires 00:17:43.280 --> 00:17:45.460 align:start position:0% for example imagine you have three wires in<00:17:43.430> your<00:17:43.490> circuit<00:17:43.880> and<00:17:44.110> they<00:17:45.110> need<00:17:45.260> to<00:17:45.320> be<00:17:45.380> the 00:17:45.460 --> 00:17:45.470 align:start position:0% in your circuit and they need to be the 00:17:45.470 --> 00:17:47.200 align:start position:0% in your circuit and they need to be the same<00:17:45.590> values<00:17:45.860> then<00:17:46.370> you<00:17:46.700> can 00:17:47.200 --> 00:17:47.210 align:start position:0% same values then you can 00:17:47.210 --> 00:17:51.160 align:start position:0% same values then you can and<00:17:47.330> kind<00:17:47.510> of<00:17:47.570> create<00:17:47.870> two<00:17:48.860> vectors<00:17:50.170> where 00:17:51.160 --> 00:17:51.170 align:start position:0% and kind of create two vectors where 00:17:51.170 --> 00:17:52.360 align:start position:0% and kind of create two vectors where you're<00:17:51.320> you're<00:17:51.650> basically<00:17:52.070> your<00:17:52.220> first 00:17:52.360 --> 00:17:52.370 align:start position:0% you're you're basically your first 00:17:52.370 --> 00:17:54.400 align:start position:0% you're you're basically your first vector<00:17:52.700> is<00:17:52.790> you<00:17:52.910> map<00:17:53.090> your<00:17:53.720> wires<00:17:54.110> into<00:17:54.290> this 00:17:54.400 --> 00:17:54.410 align:start position:0% vector is you map your wires into this 00:17:54.410 --> 00:17:56.680 align:start position:0% vector is you map your wires into this corner<00:17:54.680> space<00:17:54.950> and<00:17:55.340> then<00:17:55.550> your<00:17:55.970> second<00:17:56.570> vector 00:17:56.680 --> 00:17:56.690 align:start position:0% corner space and then your second vector 00:17:56.690 --> 00:17:59.710 align:start position:0% corner space and then your second vector is<00:17:56.840> your<00:17:56.930> mapping<00:17:57.110> the<00:17:57.350> same<00:17:57.530> wires<00:17:57.770> into<00:17:58.720> so 00:17:59.710 --> 00:17:59.720 align:start position:0% is your mapping the same wires into so 00:17:59.720 --> 00:18:02.170 align:start position:0% is your mapping the same wires into so if<00:17:59.840> you're<00:17:59.990> mapping<00:18:00.250> that<00:18:01.250> we<00:18:01.310> want<00:18:01.640> B<00:18:01.790> to<00:18:01.820> be 00:18:02.170 --> 00:18:02.180 align:start position:0% if you're mapping that we want B to be 00:18:02.180 --> 00:18:04.690 align:start position:0% if you're mapping that we want B to be three<00:18:02.450> like<00:18:03.140> three<00:18:03.410> wires<00:18:03.620> into<00:18:03.890> it<00:18:04.250> so<00:18:04.400> I<00:18:04.430> can 00:18:04.690 --> 00:18:04.700 align:start position:0% three like three wires into it so I can 00:18:04.700 --> 00:18:10.930 align:start position:0% three like three wires into it so I can turn<00:18:05.390> this<00:18:05.540> so<00:18:07.510> let's<00:18:08.510> say<00:18:08.720> that<00:18:08.900> we<00:18:09.020> assign<00:18:09.940> if 00:18:10.930 --> 00:18:10.940 align:start position:0% turn this so let's say that we assign if 00:18:10.940 --> 00:18:12.520 align:start position:0% turn this so let's say that we assign if you<00:18:11.060> have<00:18:11.150> three<00:18:11.330> wires<00:18:11.570> like<00:18:12.050> the<00:18:12.230> first<00:18:12.410> few 00:18:12.520 --> 00:18:12.530 align:start position:0% you have three wires like the first few 00:18:12.530 --> 00:18:13.750 align:start position:0% you have three wires like the first few artistic<00:18:12.980> imagine<00:18:13.340> they<00:18:13.400> need<00:18:13.520> to<00:18:13.610> be<00:18:13.670> the 00:18:13.750 --> 00:18:13.760 align:start position:0% artistic imagine they need to be the 00:18:13.760 --> 00:18:16.480 align:start position:0% artistic imagine they need to be the same<00:18:13.940> and<00:18:14.090> then<00:18:14.900> you<00:18:15.230> can<00:18:15.350> assign<00:18:15.560> indices<00:18:16.190> gb 00:18:16.480 --> 00:18:16.490 align:start position:0% same and then you can assign indices gb 00:18:16.490 --> 00:18:17.920 align:start position:0% same and then you can assign indices gb is<00:18:16.550> what<00:18:16.670> I<00:18:16.700> see<00:18:16.940> and<00:18:17.150> say<00:18:17.330> okay<00:18:17.540> fine<00:18:17.720> I'm 00:18:17.920 --> 00:18:17.930 align:start position:0% is what I see and say okay fine I'm 00:18:17.930 --> 00:18:19.630 align:start position:0% is what I see and say okay fine I'm gonna<00:18:18.050> map<00:18:18.260> the<00:18:18.620> first<00:18:18.740> words<00:18:19.040> at<00:18:19.250> one<00:18:19.490> the 00:18:19.630 --> 00:18:19.640 align:start position:0% gonna map the first words at one the 00:18:19.640 --> 00:18:21.040 align:start position:0% gonna map the first words at one the second<00:18:19.910> one<00:18:20.030> to<00:18:20.270> the<00:18:20.300> third<00:18:20.450> one<00:18:20.690> two<00:18:20.840> three 00:18:21.040 --> 00:18:21.050 align:start position:0% second one to the third one two three 00:18:21.050 --> 00:18:24.130 align:start position:0% second one to the third one two three yeah<00:18:21.980> then<00:18:22.580> you<00:18:23.330> also<00:18:23.510> know<00:18:23.720> you<00:18:23.780> to<00:18:24.020> do 00:18:24.130 --> 00:18:24.140 align:start position:0% yeah then you also know you to do 00:18:24.140 --> 00:18:25.630 align:start position:0% yeah then you also know you to do meditation<00:18:24.440> so<00:18:24.710> you<00:18:24.800> say<00:18:24.950> okay<00:18:25.220> now<00:18:25.340> get<00:18:25.550> them 00:18:25.630 --> 00:18:25.640 align:start position:0% meditation so you say okay now get them 00:18:25.640 --> 00:18:29.050 align:start position:0% meditation so you say okay now get them at<00:18:25.760> my<00:18:25.970> first<00:18:26.180> wire<00:18:26.420> to<00:18:26.830> coordinate<00:18:27.830> three<00:18:28.490> my 00:18:29.050 --> 00:18:29.060 align:start position:0% at my first wire to coordinate three my 00:18:29.060 --> 00:18:30.940 align:start position:0% at my first wire to coordinate three my second<00:18:29.390> wire<00:18:29.510> to<00:18:29.660> coordinate<00:18:30.020> to<00:18:30.200> my<00:18:30.590> first<00:18:30.770> by 00:18:30.940 --> 00:18:30.950 align:start position:0% second wire to coordinate to my first by 00:18:30.950 --> 00:18:33.490 align:start position:0% second wire to coordinate to my first by the<00:18:31.010> coordinate<00:18:31.370> one<00:18:31.990> you<00:18:32.990> now<00:18:33.140> have<00:18:33.350> two 00:18:33.490 --> 00:18:33.500 align:start position:0% the coordinate one you now have two 00:18:33.500 --> 00:18:34.780 align:start position:0% the coordinate one you now have two paths<00:18:33.680> you<00:18:33.890> have<00:18:34.130> two<00:18:34.280> collections<00:18:34.550> of 00:18:34.780 --> 00:18:34.790 align:start position:0% paths you have two collections of 00:18:34.790 --> 00:18:39.070 align:start position:0% paths you have two collections of coordinates<00:18:35.180> where<00:18:36.670> those<00:18:37.670> do<00:18:38.300> sets<00:18:38.570> they 00:18:39.070 --> 00:18:39.080 align:start position:0% coordinates where those do sets they 00:18:39.080 --> 00:18:41.860 align:start position:0% coordinates where those do sets they need<00:18:39.650> to<00:18:39.800> they<00:18:40.010> if<00:18:40.310> the<00:18:40.850> the<00:18:41.210> Y's<00:18:41.360> continuing 00:18:41.860 --> 00:18:41.870 align:start position:0% need to they if the the Y's continuing 00:18:41.870 --> 00:18:43.210 align:start position:0% need to they if the the Y's continuing opposite<00:18:42.230> each<00:18:42.350> other<00:18:42.440> in<00:18:42.680> those<00:18:42.770> coordinates 00:18:43.210 --> 00:18:43.220 align:start position:0% opposite each other in those coordinates 00:18:43.220 --> 00:18:44.650 align:start position:0% opposite each other in those coordinates will<00:18:43.370> be<00:18:43.460> the<00:18:43.580> same<00:18:43.790> but<00:18:43.940> in<00:18:44.180> different<00:18:44.210> order 00:18:44.650 --> 00:18:44.660 align:start position:0% will be the same but in different order 00:18:44.660 --> 00:18:47.290 align:start position:0% will be the same but in different order and<00:18:44.900> that's<00:18:45.230> what<00:18:45.410> that's<00:18:45.500> why<00:18:46.130> we<00:18:46.280> why<00:18:47.240> we 00:18:47.290 --> 00:18:47.300 align:start position:0% and that's what that's why we why we 00:18:47.300 --> 00:18:51.280 align:start position:0% and that's what that's why we why we call<00:18:47.510> it<00:18:47.540> to<00:18:47.690> permutation<00:18:48.880> the<00:18:49.880> reason<00:18:50.120> we<00:18:50.290> do 00:18:51.280 --> 00:18:51.290 align:start position:0% call it to permutation the reason we do 00:18:51.290 --> 00:18:53.320 align:start position:0% call it to permutation the reason we do this<00:18:51.440> problem<00:18:51.620> Conda<00:18:51.920> to<00:18:52.100> think<00:18:52.310> to<00:18:52.400> go<00:18:52.610> to<00:18:53.210> me 00:18:53.320 --> 00:18:53.330 align:start position:0% this problem Conda to think to go to me 00:18:53.330 --> 00:18:54.820 align:start position:0% this problem Conda to think to go to me to<00:18:53.480> check<00:18:53.600> the<00:18:53.720> copy<00:18:53.870> registers<00:18:54.320> because<00:18:54.590> we 00:18:54.820 --> 00:18:54.830 align:start position:0% to check the copy registers because we 00:18:54.830 --> 00:18:55.690 align:start position:0% to check the copy registers because we know<00:18:55.010> how<00:18:55.070> to<00:18:55.100> do<00:18:55.310> with<00:18:55.430> annotations 00:18:55.690 --> 00:18:55.700 align:start position:0% know how to do with annotations 00:18:55.700 --> 00:18:57.520 align:start position:0% know how to do with annotations succinctly<00:18:56.210> and<00:18:56.360> efficiently<00:18:56.690> that<00:18:57.260> was<00:18:57.380> one 00:18:57.520 --> 00:18:57.530 align:start position:0% succinctly and efficiently that was one 00:18:57.530 --> 00:18:59.710 align:start position:0% succinctly and efficiently that was one of<00:18:57.560> the<00:18:57.650> innovations<00:18:58.100> of<00:18:58.310> plum<00:18:58.520> effectively<00:18:59.510> a 00:18:59.710 --> 00:18:59.720 align:start position:0% of the innovations of plum effectively a 00:18:59.720 --> 00:19:01.090 align:start position:0% of the innovations of plum effectively a policy<00:19:00.260> that<00:19:00.380> choose<00:19:00.710> the<00:19:00.740> two<00:19:00.950> vectors 00:19:01.090 --> 00:19:01.100 align:start position:0% policy that choose the two vectors 00:19:01.100 --> 00:19:04.080 align:start position:0% policy that choose the two vectors identical<00:19:01.670> top<00:19:01.820> reputation<00:19:02.300> what<00:19:03.110> you<00:19:03.230> do<00:19:03.410> is 00:19:04.080 --> 00:19:04.090 align:start position:0% identical top reputation what you do is 00:19:04.090 --> 00:19:07.840 align:start position:0% identical top reputation what you do is you<00:19:06.040> inject<00:19:07.040> some<00:19:07.130> randomness<00:19:07.400> and<00:19:07.640> you<00:19:07.730> look 00:19:07.840 --> 00:19:07.850 align:start position:0% you inject some randomness and you look 00:19:07.850 --> 00:19:09.049 align:start position:0% you inject some randomness and you look into<00:19:08.000> your<00:19:08.120> into<00:19:08.600> your 00:19:09.049 --> 00:19:09.059 align:start position:0% into your into your 00:19:09.059 --> 00:19:11.659 align:start position:0% into your into your measurements<00:19:10.049> so<00:19:10.739> take<00:19:10.950> around<00:19:11.190> a<00:19:11.309> meter<00:19:11.489> for 00:19:11.659 --> 00:19:11.669 align:start position:0% measurements so take around a meter for 00:19:11.669 --> 00:19:14.749 align:start position:0% measurements so take around a meter for example<00:19:12.090> and<00:19:12.529> you<00:19:13.529> then<00:19:13.739> multiply<00:19:14.159> pizza<00:19:14.519> by 00:19:14.749 --> 00:19:14.759 align:start position:0% example and you then multiply pizza by 00:19:14.759 --> 00:19:19.430 align:start position:0% example and you then multiply pizza by the<00:19:15.359> index<00:19:16.349> of<00:19:16.590> your<00:19:16.979> that<00:19:17.639> rectum<00:19:18.599> so<00:19:18.779> you 00:19:19.430 --> 00:19:19.440 align:start position:0% the index of your that rectum so you 00:19:19.440 --> 00:19:21.950 align:start position:0% the index of your that rectum so you take<00:19:19.799> a<00:19:19.950> 1<00:19:20.190> you<00:19:20.340> have<00:19:20.489> me<00:19:20.609> to<00:19:20.669> Telegraph<00:19:21.059> it<00:19:21.299> to 00:19:21.950 --> 00:19:21.960 align:start position:0% take a 1 you have me to Telegraph it to 00:19:21.960 --> 00:19:24.229 align:start position:0% take a 1 you have me to Telegraph it to me<00:19:22.080> to<00:19:22.139> 80<00:19:22.379> you<00:19:22.559> have<00:19:22.649> 3<00:19:22.830> meters<00:19:22.919> a<00:19:23.129> 3<00:19:23.399> we<00:19:24.090> then 00:19:24.229 --> 00:19:24.239 align:start position:0% me to 80 you have 3 meters a 3 we then 00:19:24.239 --> 00:19:28.099 align:start position:0% me to 80 you have 3 meters a 3 we then take<00:19:24.450> your<00:19:24.769> fields<00:19:25.769> and<00:19:26.609> you<00:19:27.119> multiply<00:19:27.659> give 00:19:28.099 --> 00:19:28.109 align:start position:0% take your fields and you multiply give 00:19:28.109 --> 00:19:31.279 align:start position:0% take your fields and you multiply give what<00:19:28.259> you<00:19:28.289> add<00:19:28.529> 3<00:19:29.129> means<00:19:29.309> to<00:19:29.460> B<00:19:29.549> 1<00:19:29.700> B<00:19:30.419> 2<00:19:30.450> B<00:19:30.659> 2<00:19:30.749> a<00:19:30.929> 2 00:19:31.279 --> 00:19:31.289 align:start position:0% what you add 3 means to B 1 B 2 B 2 a 2 00:19:31.289 --> 00:19:34.070 align:start position:0% what you add 3 means to B 1 B 2 B 2 a 2 is<00:19:31.320> 2<00:19:31.529> B<00:19:31.619> 3<00:19:31.649> and<00:19:31.950> so<00:19:32.539> well<00:19:33.539> this<00:19:33.690> is<00:19:33.840> trying<00:19:34.019> to 00:19:34.070 --> 00:19:34.080 align:start position:0% is 2 B 3 and so well this is trying to 00:19:34.080 --> 00:19:36.859 align:start position:0% is 2 B 3 and so well this is trying to capture<00:19:34.289> is<00:19:34.679> that<00:19:34.889> those<00:19:35.249> this<00:19:35.519> pieces<00:19:35.869> they 00:19:36.859 --> 00:19:36.869 align:start position:0% capture is that those this pieces they 00:19:36.869 --> 00:19:42.499 align:start position:0% capture is that those this pieces they are<00:19:38.929> that<00:19:39.929> they<00:19:40.529> appear<00:19:41.119> exactly<00:19:42.119> once<00:19:42.299> in 00:19:42.499 --> 00:19:42.509 align:start position:0% are that they appear exactly once in 00:19:42.509 --> 00:19:44.810 align:start position:0% are that they appear exactly once in both<00:19:42.690> of<00:19:42.840> these<00:19:42.929> 3<00:19:43.200> and<00:19:43.409> 3<00:19:43.559> sets<00:19:44.159> but<00:19:44.700> in 00:19:44.810 --> 00:19:44.820 align:start position:0% both of these 3 and 3 sets but in 00:19:44.820 --> 00:19:46.759 align:start position:0% both of these 3 and 3 sets but in different<00:19:44.909> orders<00:19:45.269> from<00:19:45.419> so<00:19:45.869> for<00:19:46.019> example<00:19:46.409> the 00:19:46.759 --> 00:19:46.769 align:start position:0% different orders from so for example the 00:19:46.769 --> 00:19:50.989 align:start position:0% different orders from so for example the only<00:19:46.950> way<00:19:47.070> a<00:19:47.399> 1<00:19:47.609> plus<00:19:47.759> Peter<00:19:48.090> and<00:19:49.999> consumers 00:19:50.989 --> 00:19:50.999 align:start position:0% only way a 1 plus Peter and consumers 00:19:50.999 --> 00:19:52.820 align:start position:0% only way a 1 plus Peter and consumers mean<00:19:51.149> look<00:19:51.389> thank<00:19:51.779> you<00:19:51.899> they<00:19:52.049> wanted<00:19:52.289> speech<00:19:52.470> B 00:19:52.820 --> 00:19:52.830 align:start position:0% mean look thank you they wanted speech B 00:19:52.830 --> 00:19:55.399 align:start position:0% mean look thank you they wanted speech B 2<00:19:52.950> plus<00:19:53.129> B<00:19:53.159> so<00:19:53.399> musically<00:19:54.239> the<00:19:54.299> same<00:19:54.570> and<00:19:55.259> then 00:19:55.399 --> 00:19:55.409 align:start position:0% 2 plus B so musically the same and then 00:19:55.409 --> 00:19:57.320 align:start position:0% 2 plus B so musically the same and then that<00:19:55.619> may<00:19:55.799> be<00:19:55.979> the<00:19:56.070> case<00:19:56.190> if<00:19:56.519> a<00:19:56.609> 1<00:19:56.789> equals<00:19:57.029> B<00:19:57.149> 2 00:19:57.320 --> 00:19:57.330 align:start position:0% that may be the case if a 1 equals B 2 00:19:57.330 --> 00:19:58.909 align:start position:0% that may be the case if a 1 equals B 2 and<00:19:58.109> you<00:19:58.229> can<00:19:58.379> make<00:19:58.499> it<00:19:58.529> around<00:19:58.739> this 00:19:58.909 --> 00:19:58.919 align:start position:0% and you can make it around this 00:19:58.919 --> 00:20:00.769 align:start position:0% and you can make it around this permutation<00:19:59.159> checker<00:19:59.609> you<00:19:59.940> know<00:20:00.029> effectively 00:20:00.769 --> 00:20:00.779 align:start position:0% permutation checker you know effectively 00:20:00.779 --> 00:20:04.849 align:start position:0% permutation checker you know effectively if<00:20:01.529> these<00:20:02.489> three<00:20:02.789> says<00:20:03.419> form<00:20:04.139> s<00:20:04.259> equals<00:20:04.590> it<00:20:04.710> by 00:20:04.849 --> 00:20:04.859 align:start position:0% if these three says form s equals it by 00:20:04.859 --> 00:20:06.409 align:start position:0% if these three says form s equals it by equals<00:20:05.129> of<00:20:05.249> the<00:20:05.369> other<00:20:05.789> birds<00:20:05.940> to<00:20:06.179> eat 00:20:06.409 --> 00:20:06.419 align:start position:0% equals of the other birds to eat 00:20:06.419 --> 00:20:12.919 align:start position:0% equals of the other birds to eat coordinates<00:20:07.049> then<00:20:09.919> in<00:20:10.919> case<00:20:11.749> one<00:20:12.749> of<00:20:12.840> the 00:20:12.919 --> 00:20:12.929 align:start position:0% coordinates then in case one of the 00:20:12.929 --> 00:20:18.950 align:start position:0% coordinates then in case one of the enemy<00:20:13.259> or<00:20:13.470> that's<00:20:13.590> the<00:20:13.710> same<00:20:13.889> thang<00:20:15.830> so<00:20:17.960> until 00:20:18.950 --> 00:20:18.960 align:start position:0% enemy or that's the same thang so until 00:20:18.960 --> 00:20:21.349 align:start position:0% enemy or that's the same thang so until the<00:20:19.109> Oscars<00:20:19.529> is<00:20:19.739> not<00:20:20.309> there<00:20:20.489> today<00:20:20.789> the<00:20:20.999> normal 00:20:21.349 --> 00:20:21.359 align:start position:0% the Oscars is not there today the normal 00:20:21.359 --> 00:20:24.139 align:start position:0% the Oscars is not there today the normal 70<00:20:21.509> the<00:20:21.809> set<00:20:21.989> of<00:20:22.169> a<00:20:23.009> bonus<00:20:23.340> once<00:20:23.970> you<00:20:24.059> have 00:20:24.139 --> 00:20:24.149 align:start position:0% 70 the set of a bonus once you have 00:20:24.149 --> 00:20:26.060 align:start position:0% 70 the set of a bonus once you have those<00:20:24.629> around<00:20:24.809> the<00:20:24.929> meter<00:20:25.139> times<00:20:25.289> will<00:20:25.979> be<00:20:26.009> the 00:20:26.060 --> 00:20:26.070 align:start position:0% those around the meter times will be the 00:20:26.070 --> 00:20:32.089 align:start position:0% those around the meter times will be the same<00:20:26.159> as<00:20:26.429> the<00:20:26.789> B<00:20:26.940> points<00:20:30.019> and<00:20:31.019> then<00:20:31.349> so<00:20:31.830> here 00:20:32.089 --> 00:20:32.099 align:start position:0% same as the B points and then so here 00:20:32.099 --> 00:20:33.619 align:start position:0% same as the B points and then so here the<00:20:32.220> final<00:20:32.489> step<00:20:32.669> is<00:20:32.789> defend<00:20:33.179> the<00:20:33.269> people<00:20:33.389> that 00:20:33.619 --> 00:20:33.629 align:start position:0% the final step is defend the people that 00:20:33.629 --> 00:20:36.139 align:start position:0% the final step is defend the people that will<00:20:33.720> prove<00:20:33.960> to<00:20:34.019> you<00:20:34.200> is<00:20:34.379> that<00:20:34.529> you<00:20:34.979> if<00:20:35.879> you 00:20:36.139 --> 00:20:36.149 align:start position:0% will prove to you is that you if you 00:20:36.149 --> 00:20:39.739 align:start position:0% will prove to you is that you if you with<00:20:36.509> just<00:20:36.779> adding<00:20:36.989> one<00:20:37.849> random<00:20:38.849> element<00:20:39.119> into 00:20:39.739 --> 00:20:39.749 align:start position:0% with just adding one random element into 00:20:39.749 --> 00:20:42.859 align:start position:0% with just adding one random element into your<00:20:39.779> kind<00:20:40.169> of<00:20:40.340> collectibles<00:20:41.340> that<00:20:41.580> was<00:20:42.570> able 00:20:42.859 --> 00:20:42.869 align:start position:0% your kind of collectibles that was able 00:20:42.869 --> 00:20:45.349 align:start position:0% your kind of collectibles that was able to<00:20:42.899> prove<00:20:43.200> that<00:20:43.739> you<00:20:44.489> have<00:20:44.669> two<00:20:44.849> sets<00:20:45.179> of 00:20:45.349 --> 00:20:45.359 align:start position:0% to prove that you have two sets of 00:20:45.359 --> 00:20:48.769 align:start position:0% to prove that you have two sets of coordinates<00:20:45.629> that<00:20:47.239> have<00:20:48.239> asset<00:20:48.479> management 00:20:48.769 --> 00:20:48.779 align:start position:0% coordinates that have asset management 00:20:48.779 --> 00:20:50.599 align:start position:0% coordinates that have asset management in<00:20:48.960> a<00:20:49.049> corner<00:20:49.409> but<00:20:49.950> you've<00:20:50.099> not<00:20:50.220> yet<00:20:50.369> proven 00:20:50.599 --> 00:20:50.609 align:start position:0% in a corner but you've not yet proven 00:20:50.609 --> 00:20:54.919 align:start position:0% in a corner but you've not yet proven that<00:20:50.840> that<00:20:52.070> those<00:20:53.070> those<00:20:53.549> corner<00:20:54.479> tables<00:20:54.779> are 00:20:54.919 --> 00:20:54.929 align:start position:0% that that those those corner tables are 00:20:54.929 --> 00:20:58.040 align:start position:0% that that those those corner tables are in<00:20:54.960> the<00:20:55.200> correct<00:20:55.379> or<00:20:55.710> they<00:20:56.220> need<00:20:56.460> to<00:20:56.729> genuinely 00:20:58.040 --> 00:20:58.050 align:start position:0% in the correct or they need to genuinely 00:20:58.050 --> 00:21:02.780 align:start position:0% in the correct or they need to genuinely so<00:20:58.440> he<00:20:58.590> had<00:20:58.890> a<00:20:59.450> second<00:21:00.450> recording<00:21:00.930> um<00:21:01.670> mm<00:21:02.670> this 00:21:02.780 --> 00:21:02.790 align:start position:0% so he had a second recording um mm this 00:21:02.790 --> 00:21:06.620 align:start position:0% so he had a second recording um mm this effectively<00:21:03.720> we<00:21:03.960> take<00:21:05.030> each<00:21:06.030> one<00:21:06.210> of<00:21:06.270> them<00:21:06.450> is 00:21:06.620 --> 00:21:06.630 align:start position:0% effectively we take each one of them is 00:21:06.630 --> 00:21:09.020 align:start position:0% effectively we take each one of them is coordinates<00:21:07.560> two<00:21:08.280> more<00:21:08.430> second<00:21:08.670> craters 00:21:09.020 --> 00:21:09.030 align:start position:0% coordinates two more second craters 00:21:09.030 --> 00:21:12.050 align:start position:0% coordinates two more second craters family<00:21:09.360> man<00:21:09.600> and<00:21:09.900> commissars<00:21:10.850> and<00:21:11.850> then<00:21:12.000> we 00:21:12.050 --> 00:21:12.060 align:start position:0% family man and commissars and then we 00:21:12.060 --> 00:21:14.330 align:start position:0% family man and commissars and then we take<00:21:12.210> the<00:21:12.360> product<00:21:12.600> of<00:21:12.780> them<00:21:12.900> and<00:21:13.140> so<00:21:13.590> the 00:21:14.330 --> 00:21:14.340 align:start position:0% take the product of them and so the 00:21:14.340 --> 00:21:17.720 align:start position:0% take the product of them and so the point<00:21:14.520> of<00:21:14.700> this<00:21:14.820> is<00:21:15.650> effectively<00:21:16.650> we've<00:21:17.490> met 00:21:17.720 --> 00:21:17.730 align:start position:0% point of this is effectively we've met 00:21:17.730 --> 00:21:20.480 align:start position:0% point of this is effectively we've met we've<00:21:18.450> met<00:21:19.050> our<00:21:19.080> Y<00:21:19.380> values<00:21:19.740> in<00:21:19.860> between<00:21:19.920> corner 00:21:20.480 --> 00:21:20.490 align:start position:0% we've met our Y values in between corner 00:21:20.490 --> 00:21:26.500 align:start position:0% we've met our Y values in between corner spaces<00:21:20.910> where<00:21:21.270> the<00:21:24.500> these<00:21:25.500> sets<00:21:25.920> of<00:21:26.010> owners 00:21:26.500 --> 00:21:26.510 align:start position:0% spaces where the these sets of owners 00:21:26.510 --> 00:21:28.610 align:start position:0% spaces where the these sets of owners need<00:21:27.510> to<00:21:27.540> be<00:21:27.720> the<00:21:27.810> same<00:21:28.050> but<00:21:28.260> they<00:21:28.350> will<00:21:28.470> be<00:21:28.560> in 00:21:28.610 --> 00:21:28.620 align:start position:0% need to be the same but they will be in 00:21:28.620 --> 00:21:29.900 align:start position:0% need to be the same but they will be in a<00:21:28.680> Verity<00:21:28.920> the<00:21:29.040> different<00:21:29.340> jumbled<00:21:29.610> up<00:21:29.670> order 00:21:29.900 --> 00:21:29.910 align:start position:0% a Verity the different jumbled up order 00:21:29.910 --> 00:21:31.550 align:start position:0% a Verity the different jumbled up order and<00:21:30.450> so<00:21:30.600> the<00:21:30.690> way<00:21:30.780> to<00:21:30.870> check<00:21:31.020> that<00:21:31.080> is<00:21:31.230> what<00:21:31.470> we 00:21:31.550 --> 00:21:31.560 align:start position:0% and so the way to check that is what we 00:21:31.560 --> 00:21:33.350 align:start position:0% and so the way to check that is what we just<00:21:31.650> take<00:21:31.800> the<00:21:31.890> product<00:21:32.070> on<00:21:32.280> them<00:21:32.460> and<00:21:33.090> if<00:21:33.240> the 00:21:33.350 --> 00:21:33.360 align:start position:0% just take the product on them and if the 00:21:33.360 --> 00:21:35.810 align:start position:0% just take the product on them and if the products<00:21:33.630> the<00:21:33.780> same<00:21:33.960> then<00:21:34.440> we<00:21:35.040> have<00:21:35.160> a<00:21:35.190> mapping 00:21:35.810 --> 00:21:35.820 align:start position:0% products the same then we have a mapping 00:21:35.820 --> 00:21:37.310 align:start position:0% products the same then we have a mapping which<00:21:36.120> means<00:21:36.360> that<00:21:36.600> your<00:21:36.840> wires<00:21:37.110> have 00:21:37.310 --> 00:21:37.320 align:start position:0% which means that your wires have 00:21:37.320 --> 00:21:38.810 align:start position:0% which means that your wires have incredibly<00:21:37.650> copied<00:21:37.980> which<00:21:38.190> means<00:21:38.400> that 00:21:38.810 --> 00:21:38.820 align:start position:0% incredibly copied which means that 00:21:38.820 --> 00:21:40.490 align:start position:0% incredibly copied which means that you've<00:21:39.180> correctly<00:21:39.660> a<00:21:39.720> songster<00:21:40.320> stuff 00:21:40.490 --> 00:21:40.500 align:start position:0% you've correctly a songster stuff 00:21:40.500 --> 00:21:46.460 align:start position:0% you've correctly a songster stuff otherwise<00:21:40.710> no<00:21:41.010> second<00:21:41.340> yes<00:21:44.810> yes<00:21:45.810> it<00:21:46.110> should<00:21:46.290> be 00:21:46.460 --> 00:21:46.470 align:start position:0% otherwise no second yes yes it should be 00:21:46.470 --> 00:21:56.090 align:start position:0% otherwise no second yes yes it should be sorry<00:21:46.920> it<00:21:47.160> was<00:21:47.340> like<00:21:47.460> that<00:21:52.970> so<00:21:54.380> because<00:21:55.380> it's 00:21:56.090 --> 00:21:56.100 align:start position:0% sorry it was like that so because it's 00:21:56.100 --> 00:21:59.240 align:start position:0% sorry it was like that so because it's okay<00:21:56.490> into<00:21:56.730> an<00:21:56.820> asset<00:21:57.090> today<00:21:57.270> so<00:21:57.710> I<00:21:58.710> just<00:21:59.010> won 00:21:59.240 --> 00:21:59.250 align:start position:0% okay into an asset today so I just won 00:21:59.250 --> 00:22:01.460 align:start position:0% okay into an asset today so I just won so<00:21:59.640> what<00:22:00.420> we<00:22:00.510> ask<00:22:00.600> you<00:22:00.780> since<00:22:00.900> most<00:22:01.230> of<00:22:01.380> all 00:22:01.460 --> 00:22:01.470 align:start position:0% so what we ask you since most of all 00:22:01.470 --> 00:22:04.550 align:start position:0% so what we ask you since most of all what's<00:22:01.620> the<00:22:01.710> purpose<00:22:02.040> I<00:22:02.370> mean<00:22:03.360> assistance<00:22:03.870> we 00:22:04.550 --> 00:22:04.560 align:start position:0% what's the purpose I mean assistance we 00:22:04.560 --> 00:22:05.780 align:start position:0% what's the purpose I mean assistance we think<00:22:04.710> is<00:22:04.800> pretty<00:22:04.950> cool<00:22:05.100> technology<00:22:05.250> but 00:22:05.780 --> 00:22:05.790 align:start position:0% think is pretty cool technology but 00:22:05.790 --> 00:22:08.120 align:start position:0% think is pretty cool technology but without<00:22:06.300> the<00:22:06.420> use<00:22:06.540> case<00:22:06.750> is<00:22:07.080> just<00:22:07.710> a<00:22:07.770> toy<00:22:07.920> and 00:22:08.120 --> 00:22:08.130 align:start position:0% without the use case is just a toy and 00:22:08.130 --> 00:22:09.800 align:start position:0% without the use case is just a toy and we<00:22:08.490> aren't<00:22:08.670> the<00:22:08.760> we<00:22:09.120> haven't<00:22:09.510> or<00:22:09.600> that<00:22:09.720> aspect 00:22:09.800 --> 00:22:09.810 align:start position:0% we aren't the we haven't or that aspect 00:22:09.810 --> 00:22:13.400 align:start position:0% we aren't the we haven't or that aspect though<00:22:10.650> the<00:22:11.190> SS<00:22:12.150> missile<00:22:12.450> is<00:22:12.900> to<00:22:13.110> do<00:22:13.230> other 00:22:13.400 --> 00:22:13.410 align:start position:0% though the SS missile is to do other 00:22:13.410 --> 00:22:14.900 align:start position:0% though the SS missile is to do other payments<00:22:13.860> to<00:22:13.980> do<00:22:14.100> private<00:22:14.310> odysseas<00:22:14.880> elytis 00:22:14.900 --> 00:22:14.910 align:start position:0% payments to do private odysseas elytis 00:22:14.910 --> 00:22:17.420 align:start position:0% payments to do private odysseas elytis loans<00:22:15.710> effectively<00:22:16.710> worth<00:22:16.860> all<00:22:17.190> of<00:22:17.340> the 00:22:17.420 --> 00:22:17.430 align:start position:0% loans effectively worth all of the 00:22:17.430 --> 00:22:18.770 align:start position:0% loans effectively worth all of the traditional<00:22:17.790> financial<00:22:17.970> services<00:22:18.510> that<00:22:18.690> you 00:22:18.770 --> 00:22:18.780 align:start position:0% traditional financial services that you 00:22:18.780 --> 00:22:20.840 align:start position:0% traditional financial services that you do<00:22:18.990> today<00:22:19.380> in<00:22:19.590> which<00:22:19.710> where<00:22:19.980> you<00:22:20.100> expect<00:22:20.460> it<00:22:20.550> by 00:22:20.840 --> 00:22:20.850 align:start position:0% do today in which where you expect it by 00:22:20.850 --> 00:22:23.060 align:start position:0% do today in which where you expect it by default<00:22:21.240> where<00:22:21.840> you<00:22:21.930> might<00:22:22.110> want<00:22:22.140> to<00:22:22.530> use<00:22:22.800> the 00:22:23.060 --> 00:22:23.070 align:start position:0% default where you might want to use the 00:22:23.070 --> 00:22:26.420 align:start position:0% default where you might want to use the consensus<00:22:23.550> of<00:22:23.580> a<00:22:23.670> public<00:22:23.940> gloating<00:22:25.430> because 00:22:26.420 --> 00:22:26.430 align:start position:0% consensus of a public gloating because 00:22:26.430 --> 00:22:27.620 align:start position:0% consensus of a public gloating because you<00:22:26.520> might<00:22:26.640> not<00:22:26.700> foster<00:22:26.910> care<00:22:27.150> about<00:22:27.360> this<00:22:27.450> but 00:22:27.620 --> 00:22:27.630 align:start position:0% you might not foster care about this but 00:22:27.630 --> 00:22:29.730 align:start position:0% you might not foster care about this but you<00:22:27.780> don't<00:22:27.990> want<00:22:28.110> to<00:22:28.170> give<00:22:28.260> it<00:22:28.350> and<00:22:28.470> for<00:22:28.650> in 00:22:29.730 --> 00:22:29.740 align:start position:0% you don't want to give it and for in 00:22:29.740 --> 00:22:31.950 align:start position:0% you don't want to give it and for in your<00:22:30.610> salaries<00:22:30.970> being<00:22:31.330> publicly<00:22:31.659> you<00:22:31.809> don't 00:22:31.950 --> 00:22:31.960 align:start position:0% your salaries being publicly you don't 00:22:31.960 --> 00:22:33.779 align:start position:0% your salaries being publicly you don't even<00:22:32.080> that<00:22:32.230> isn't<00:22:32.409> publicly<00:22:32.890> don't<00:22:33.130> miss 00:22:33.779 --> 00:22:33.789 align:start position:0% even that isn't publicly don't miss 00:22:33.789 --> 00:22:35.730 align:start position:0% even that isn't publicly don't miss assume<00:22:34.090> you<00:22:34.240> plan<00:22:34.450> to<00:22:34.480> focus<00:22:34.690> if<00:22:35.590> they're 00:22:35.730 --> 00:22:35.740 align:start position:0% assume you plan to focus if they're 00:22:35.740 --> 00:22:37.950 align:start position:0% assume you plan to focus if they're public<00:22:36.010> in<00:22:36.610> my<00:22:36.760> training<00:22:37.539> decisions<00:22:37.899> in 00:22:37.950 --> 00:22:37.960 align:start position:0% public in my training decisions in 00:22:37.960 --> 00:22:39.630 align:start position:0% public in my training decisions in public<00:22:38.289> because<00:22:38.380> that<00:22:38.649> massive<00:22:39.190> competitive 00:22:39.630 --> 00:22:39.640 align:start position:0% public because that massive competitive 00:22:39.640 --> 00:22:41.760 align:start position:0% public because that massive competitive disadvantage<00:22:39.840> you're<00:22:40.840> looking<00:22:41.080> to<00:22:41.169> sell<00:22:41.380> and 00:22:41.760 --> 00:22:41.770 align:start position:0% disadvantage you're looking to sell and 00:22:41.770 --> 00:22:45.810 align:start position:0% disadvantage you're looking to sell and exit<00:22:42.429> from<00:22:42.490> the<00:22:42.610> last<00:22:42.760> position<00:22:43.000> so<00:22:44.700> aspect<00:22:45.700> as 00:22:45.810 --> 00:22:45.820 align:start position:0% exit from the last position so aspect as 00:22:45.820 --> 00:22:49.500 align:start position:0% exit from the last position so aspect as we<00:22:46.029> has<00:22:46.149> Oconee<00:22:46.480> stance<00:22:46.779> but<00:22:47.230> we<00:22:48.270> have<00:22:49.270> a<00:22:49.299> kind 00:22:49.500 --> 00:22:49.510 align:start position:0% we has Oconee stance but we have a kind 00:22:49.510 --> 00:22:50.940 align:start position:0% we has Oconee stance but we have a kind of<00:22:49.570> a<00:22:49.630> collection<00:22:49.929> of<00:22:50.169> proves<00:22:50.440> that<00:22:50.649> were<00:22:50.740> in<00:22:50.860> a 00:22:50.940 --> 00:22:50.950 align:start position:0% of a collection of proves that were in a 00:22:50.950 --> 00:22:52.409 align:start position:0% of a collection of proves that were in a supportive<00:22:51.460> manner 00:22:52.409 --> 00:22:52.419 align:start position:0% supportive manner 00:22:52.419 --> 00:22:54.269 align:start position:0% supportive manner this<00:22:52.659> isn't<00:22:52.960> plot<00:22:53.260> this<00:22:53.440> is<00:22:53.590> a<00:22:53.620> slightly<00:22:54.220> older 00:22:54.269 --> 00:22:54.279 align:start position:0% this isn't plot this is a slightly older 00:22:54.279 --> 00:22:55.590 align:start position:0% this isn't plot this is a slightly older technology<00:22:54.820> were<00:22:54.940> using<00:22:54.970> the<00:22:55.270> smokers 00:22:55.590 --> 00:22:55.600 align:start position:0% technology were using the smokers 00:22:55.600 --> 00:22:57.930 align:start position:0% technology were using the smokers breathing<00:22:56.020> quite<00:22:56.529> recent<00:22:56.980> they're<00:22:57.700> going<00:22:57.850> to 00:22:57.930 --> 00:22:57.940 align:start position:0% breathing quite recent they're going to 00:22:57.940 --> 00:23:01.350 align:start position:0% breathing quite recent they're going to be<00:22:58.059> a<00:22:58.360> recipe<00:22:59.080> to<00:22:59.230> go<00:22:59.320> to<00:22:59.380> interesting<00:23:00.210> so<00:23:01.210> now 00:23:01.350 --> 00:23:01.360 align:start position:0% be a recipe to go to interesting so now 00:23:01.360 --> 00:23:04.139 align:start position:0% be a recipe to go to interesting so now we<00:23:01.419> kind<00:23:01.720> of<00:23:01.809> have<00:23:01.870> a<00:23:02.200> suite<00:23:02.919> of<00:23:03.279> three 00:23:04.139 --> 00:23:04.149 align:start position:0% we kind of have a suite of three 00:23:04.149 --> 00:23:05.370 align:start position:0% we kind of have a suite of three receivers<00:23:04.539> Emmys<00:23:04.779> generals<00:23:05.020> troops<00:23:05.260> that 00:23:05.370 --> 00:23:05.380 align:start position:0% receivers Emmys generals troops that 00:23:05.380 --> 00:23:06.570 align:start position:0% receivers Emmys generals troops that allows<00:23:05.559> you<00:23:05.710> to<00:23:05.830> basics<00:23:06.220> financial 00:23:06.570 --> 00:23:06.580 align:start position:0% allows you to basics financial 00:23:06.580 --> 00:23:09.810 align:start position:0% allows you to basics financial transactions<00:23:08.159> where<00:23:09.159> the<00:23:09.399> values<00:23:09.669> in<00:23:09.760> our 00:23:09.810 --> 00:23:09.820 align:start position:0% transactions where the values in our 00:23:09.820 --> 00:23:12.019 align:start position:0% transactions where the values in our group<00:23:10.029> so<00:23:10.539> sense<00:23:10.840> folks<00:23:11.020> incumbents<00:23:11.649> and<00:23:11.740> that 00:23:12.019 --> 00:23:12.029 align:start position:0% group so sense folks incumbents and that 00:23:12.029 --> 00:23:15.659 align:start position:0% group so sense folks incumbents and that and<00:23:13.470> so<00:23:14.470> it<00:23:14.559> doesn't<00:23:14.799> fall<00:23:14.980> for<00:23:15.309> a<00:23:15.399> finished 00:23:15.659 --> 00:23:15.669 align:start position:0% and so it doesn't fall for a finished 00:23:15.669 --> 00:23:17.370 align:start position:0% and so it doesn't fall for a finished where<00:23:16.090> everyone<00:23:16.419> get<00:23:16.720> onto<00:23:16.840> is<00:23:17.080> that<00:23:17.260> this 00:23:17.370 --> 00:23:17.380 align:start position:0% where everyone get onto is that this 00:23:17.380 --> 00:23:17.970 align:start position:0% where everyone get onto is that this issue 00:23:17.970 --> 00:23:17.980 align:start position:0% issue 00:23:17.980 --> 00:23:19.590 align:start position:0% issue this<00:23:18.100> is<00:23:18.220> astok<00:23:18.700> trusted<00:23:19.029> senator<00:23:19.360> yeah<00:23:19.570> I 00:23:19.590 --> 00:23:19.600 align:start position:0% this is astok trusted senator yeah I 00:23:19.600 --> 00:23:20.970 align:start position:0% this is astok trusted senator yeah I mentioned<00:23:19.929> that<00:23:20.020> the<00:23:20.140> stuff<00:23:20.380> on<00:23:20.710> needs 00:23:20.970 --> 00:23:20.980 align:start position:0% mentioned that the stuff on needs 00:23:20.980 --> 00:23:23.310 align:start position:0% mentioned that the stuff on needs adjuster<00:23:21.370> seller<00:23:21.580> in<00:23:21.940> teams<00:23:22.360> one<00:23:22.539> and<00:23:22.840> that 00:23:23.310 --> 00:23:23.320 align:start position:0% adjuster seller in teams one and that 00:23:23.320 --> 00:23:24.510 align:start position:0% adjuster seller in teams one and that one<00:23:23.500> trust<00:23:23.679> ourself<00:23:23.950> is<00:23:24.159> going<00:23:24.370> to<00:23:24.460> be 00:23:24.510 --> 00:23:24.520 align:start position:0% one trust ourself is going to be 00:23:24.520 --> 00:23:27.450 align:start position:0% one trust ourself is going to be happening<00:23:24.880> pre<00:23:25.779> immediately<00:23:26.230> after<00:23:26.500> death<00:23:26.620> so 00:23:27.450 --> 00:23:27.460 align:start position:0% happening pre immediately after death so 00:23:27.460 --> 00:23:30.750 align:start position:0% happening pre immediately after death so we<00:23:27.490> are<00:23:27.850> going<00:23:28.240> to<00:23:28.390> sign<00:23:28.570> ups<00:23:29.340> to<00:23:30.340> be<00:23:30.460> a<00:23:30.490> bit<00:23:30.640> has 00:23:30.750 --> 00:23:30.760 align:start position:0% we are going to sign ups to be a bit has 00:23:30.760 --> 00:23:32.190 align:start position:0% we are going to sign ups to be a bit has meant<00:23:30.909> to<00:23:30.940> the<00:23:31.059> sermon<00:23:31.360> everyone's<00:23:31.779> as<00:23:31.870> many 00:23:32.190 --> 00:23:32.200 align:start position:0% meant to the sermon everyone's as many 00:23:32.200 --> 00:23:34.519 align:start position:0% meant to the sermon everyone's as many people<00:23:32.500> as<00:23:32.590> possible<00:23:33.120> we're<00:23:34.120> going<00:23:34.240> to<00:23:34.299> be<00:23:34.360> my 00:23:34.519 --> 00:23:34.529 align:start position:0% people as possible we're going to be my 00:23:34.529 --> 00:23:37.440 align:start position:0% people as possible we're going to be my ignition<00:23:35.529> for<00:23:35.740> with<00:23:35.860> month<00:23:36.100> and<00:23:36.730> anybody<00:23:37.270> can 00:23:37.440 --> 00:23:37.450 align:start position:0% ignition for with month and anybody can 00:23:37.450 --> 00:23:38.820 align:start position:0% ignition for with month and anybody can take<00:23:37.600> parts<00:23:37.870> of<00:23:37.960> these<00:23:38.110> then<00:23:38.500> feel<00:23:38.679> free<00:23:38.710> to 00:23:38.820 --> 00:23:38.830 align:start position:0% take parts of these then feel free to 00:23:38.830 --> 00:23:41.909 align:start position:0% take parts of these then feel free to stop<00:23:39.360> the<00:23:40.360> idea<00:23:40.450> is<00:23:40.840> this<00:23:41.350> program<00:23:41.770> is 00:23:41.909 --> 00:23:41.919 align:start position:0% stop the idea is this program is 00:23:41.919 --> 00:23:44.820 align:start position:0% stop the idea is this program is drinkability<00:23:42.630> even<00:23:43.630> 31<00:23:43.990> participants<00:23:44.529> in<00:23:44.740> our 00:23:44.820 --> 00:23:44.830 align:start position:0% drinkability even 31 participants in our 00:23:44.830 --> 00:23:46.620 align:start position:0% drinkability even 31 participants in our ceremony<00:23:45.190> tax<00:23:45.460> policy<00:23:45.880> and<00:23:46.000> destroys<00:23:46.360> the 00:23:46.620 --> 00:23:46.630 align:start position:0% ceremony tax policy and destroys the 00:23:46.630 --> 00:23:48.539 align:start position:0% ceremony tax policy and destroys the toxic<00:23:47.380> waste<00:23:47.470> that<00:23:47.710> they<00:23:47.830> generate<00:23:48.159> and<00:23:48.490> a 00:23:48.539 --> 00:23:48.549 align:start position:0% toxic waste that they generate and a 00:23:48.549 --> 00:23:50.730 align:start position:0% toxic waste that they generate and a similar<00:23:48.760> into<00:23:49.029> Z<00:23:49.149> cash<00:23:49.390> the<00:23:50.200> entire<00:23:50.470> scheme 00:23:50.730 --> 00:23:50.740 align:start position:0% similar into Z cash the entire scheme 00:23:50.740 --> 00:23:52.799 align:start position:0% similar into Z cash the entire scheme the<00:23:51.130> the<00:23:51.490> the<00:23:51.820> results<00:23:52.149> material<00:23:52.450> system<00:23:52.720> will 00:23:52.799 --> 00:23:52.809 align:start position:0% the the the results material system will 00:23:52.809 --> 00:23:54.630 align:start position:0% the the the results material system will be<00:23:52.899> secured<00:23:53.320> the<00:23:53.470> traditional<00:23:53.980> pair<00:23:54.580> of 00:23:54.630 --> 00:23:54.640 align:start position:0% be secured the traditional pair of 00:23:54.640 --> 00:23:56.039 align:start position:0% be secured the traditional pair of assumptions<00:23:55.330> so<00:23:55.570> he<00:23:55.659> thought<00:23:55.779> this<00:23:55.899> would<00:23:56.020> be 00:23:56.039 --> 00:23:56.049 align:start position:0% assumptions so he thought this would be 00:23:56.049 --> 00:23:58.440 align:start position:0% assumptions so he thought this would be a<00:23:56.140> common<00:23:57.010> good<00:23:57.190> that<00:23:57.490> will<00:23:58.029> be<00:23:58.149> able<00:23:58.270> to<00:23:58.390> be 00:23:58.440 --> 00:23:58.450 align:start position:0% a common good that will be able to be 00:23:58.450 --> 00:24:00.210 align:start position:0% a common good that will be able to be used<00:23:58.600> by<00:23:58.809> a<00:23:58.840> lot<00:23:59.260> of<00:23:59.289> different<00:23:59.710> projects<00:24:00.070> on 00:24:00.210 --> 00:24:00.220 align:start position:0% used by a lot of different projects on 00:24:00.220 --> 00:24:01.789 align:start position:0% used by a lot of different projects on ethereum<00:24:00.600> Elsa 00:24:01.789 --> 00:24:01.799 align:start position:0% ethereum Elsa 00:24:01.799 --> 00:24:05.669 align:start position:0% ethereum Elsa that<00:24:02.799> was<00:24:02.919> essentially<00:24:03.870> his<00:24:04.870> succinct 00:24:05.669 --> 00:24:05.679 align:start position:0% that was essentially his succinct 00:24:05.679 --> 00:24:09.240 align:start position:0% that was essentially his succinct proving<00:24:05.950> systems<00:24:06.250> further<00:24:06.460> reduces<00:24:07.169> and<00:24:08.169> so 00:24:09.240 --> 00:24:09.250 align:start position:0% proving systems further reduces and so 00:24:09.250 --> 00:24:12.570 align:start position:0% proving systems further reduces and so -<00:24:10.150> what<00:24:10.690> we<00:24:11.080> look<00:24:11.380> like<00:24:11.559> we<00:24:11.620> have<00:24:11.740> a<00:24:11.770> front<00:24:12.460> end 00:24:12.570 --> 00:24:12.580 align:start position:0% - what we look like we have a front end 00:24:12.580 --> 00:24:14.580 align:start position:0% - what we look like we have a front end that<00:24:12.730> even<00:24:13.000> she<00:24:13.240> needs<00:24:13.809> you<00:24:13.960> to<00:24:13.990> see<00:24:14.260> fuse 00:24:14.580 --> 00:24:14.590 align:start position:0% that even she needs you to see fuse 00:24:14.590 --> 00:24:17.190 align:start position:0% that even she needs you to see fuse before<00:24:14.950> we<00:24:15.039> discern<00:24:15.309> in<00:24:15.549> a<00:24:15.580> given<00:24:16.030> time<00:24:16.200> and 00:24:17.190 --> 00:24:17.200 align:start position:0% before we discern in a given time and 00:24:17.200 --> 00:24:19.200 align:start position:0% before we discern in a given time and see<00:24:17.650> if<00:24:17.740> I<00:24:17.860> thought<00:24:18.100> your<00:24:18.340> theory<00:24:18.640> doesn't<00:24:18.820> you 00:24:19.200 --> 00:24:19.210 align:start position:0% see if I thought your theory doesn't you 00:24:19.210 --> 00:24:21.870 align:start position:0% see if I thought your theory doesn't you if<00:24:19.630> you<00:24:19.750> sign<00:24:19.990> on<00:24:20.110> the<00:24:20.200> New<00:24:20.320> Sun<00:24:20.760> so<00:24:21.760> yeah<00:24:21.850> I 00:24:21.870 --> 00:24:21.880 align:start position:0% if you sign on the New Sun so yeah I 00:24:21.880 --> 00:24:23.659 align:start position:0% if you sign on the New Sun so yeah I believe<00:24:21.909> that<00:24:22.390> is<00:24:22.570> true 00:24:23.659 --> 00:24:23.669 align:start position:0% believe that is true 00:24:23.669 --> 00:24:30.870 align:start position:0% believe that is true thank<00:24:24.669> you<00:24:24.730> very<00:24:24.880> much 00:24:30.870 --> 00:24:30.880 align:start position:0% 00:24:30.880 --> 00:24:40.080 align:start position:0% [Applause] 00:24:40.080 --> 00:24:40.090 align:start position:0% 00:24:40.090 --> 00:24:42.150 align:start position:0% you