WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.930 align:start position:0% [Applause] 00:00:10.930 --> 00:00:10.940 align:start position:0% 00:00:10.940 --> 00:00:15.859 align:start position:0% well<00:00:11.940> we<00:00:12.360> are<00:00:13.309> actually<00:00:14.309> trying<00:00:14.730> to<00:00:14.849> do<00:00:15.629> some 00:00:15.859 --> 00:00:15.869 align:start position:0% well we are actually trying to do some 00:00:15.869 --> 00:00:18.800 align:start position:0% well we are actually trying to do some practical<00:00:16.200> stuff<00:00:16.529> like<00:00:17.000> implementing<00:00:18.000> a<00:00:18.119> snog 00:00:18.800 --> 00:00:18.810 align:start position:0% practical stuff like implementing a snog 00:00:18.810 --> 00:00:22.370 align:start position:0% practical stuff like implementing a snog circuit<00:00:19.560> to<00:00:19.740> processor<00:00:20.599> convictions<00:00:21.599> so<00:00:22.320> if 00:00:22.370 --> 00:00:22.380 align:start position:0% circuit to processor convictions so if 00:00:22.380 --> 00:00:25.279 align:start position:0% circuit to processor convictions so if you<00:00:22.470> want<00:00:22.680> to<00:00:22.830> follow<00:00:23.070> along<00:00:23.279> you<00:00:24.180> are<00:00:24.289> welcome 00:00:25.279 --> 00:00:25.289 align:start position:0% you want to follow along you are welcome 00:00:25.289 --> 00:00:28.640 align:start position:0% you want to follow along you are welcome to<00:00:25.439> yeah<00:00:26.400> so<00:00:26.760> if<00:00:26.849> you<00:00:26.910> want<00:00:27.150> to<00:00:27.410> solve<00:00:28.410> any 00:00:28.640 --> 00:00:28.650 align:start position:0% to yeah so if you want to solve any 00:00:28.650 --> 00:00:30.769 align:start position:0% to yeah so if you want to solve any requirements<00:00:29.340> they<00:00:29.490> are<00:00:29.550> over<00:00:29.789> here<00:00:30.000> and<00:00:30.300> this 00:00:30.769 --> 00:00:30.779 align:start position:0% requirements they are over here and this 00:00:30.779 --> 00:00:33.650 align:start position:0% requirements they are over here and this this<00:00:31.289> link<00:00:31.710> is<00:00:31.859> public<00:00:32.220> I<00:00:32.580> cannot<00:00:33.420> buy<00:00:33.629> a 00:00:33.650 --> 00:00:33.660 align:start position:0% this link is public I cannot buy a 00:00:33.660 --> 00:00:42.670 align:start position:0% this link is public I cannot buy a domain<00:00:33.930> so<00:00:34.320> you<00:00:35.070> can<00:00:35.760> use<00:00:35.879> this<00:00:36.059> one 00:00:42.670 --> 00:00:42.680 align:start position:0% 00:00:42.680 --> 00:00:45.160 align:start position:0% [Music] 00:00:45.160 --> 00:00:45.170 align:start position:0% [Music] 00:00:45.170 --> 00:00:51.470 align:start position:0% [Music] I<00:00:46.170> live<00:00:46.560> in<00:00:46.650> 238<00:00:47.100> modern<00:00:47.430> all<00:00:47.790> of<00:00:47.910> you<00:00:48.030> Sam<00:00:50.480> yes 00:00:51.470 --> 00:00:51.480 align:start position:0% I live in 238 modern all of you Sam yes 00:00:51.480 --> 00:00:54.530 align:start position:0% I live in 238 modern all of you Sam yes I<00:00:51.900> created<00:00:52.230> this<00:00:52.680> to<00:00:53.550> curative<00:00:54.270> and<00:00:54.420> it's 00:00:54.530 --> 00:00:54.540 align:start position:0% I created this to curative and it's 00:00:54.540 --> 00:00:56.540 align:start position:0% I created this to curative and it's mostly<00:00:55.410> going<00:00:55.590> to<00:00:55.680> be<00:00:55.770> like<00:00:56.040> me<00:00:56.250> painting 00:00:56.540 --> 00:00:56.550 align:start position:0% mostly going to be like me painting 00:00:56.550 --> 00:01:01.280 align:start position:0% mostly going to be like me painting what's<00:00:57.420> what<00:00:58.020> how<00:00:58.730> love<00:00:59.730> works<00:00:59.760> and<00:01:00.690> maybe 00:01:01.280 --> 00:01:01.290 align:start position:0% what's what how love works and maybe 00:01:01.290 --> 00:01:07.230 align:start position:0% what's what how love works and maybe creating<00:01:01.710> a<00:01:01.860> circuit<00:01:02.580> body<00:01:02.790> of<00:01:03.600> light 00:01:07.230 --> 00:01:07.240 align:start position:0% 00:01:07.240 --> 00:01:12.520 align:start position:0% [Music] 00:01:12.520 --> 00:01:12.530 align:start position:0% 00:01:12.530 --> 00:01:38.770 align:start position:0% a<00:01:13.090> little<00:01:14.090> bit<00:01:14.240> on<00:01:14.360> the<00:01:14.450> little<00:01:14.720> show 00:01:38.770 --> 00:01:38.780 align:start position:0% 00:01:38.780 --> 00:01:49.280 align:start position:0% [Music] 00:01:49.280 --> 00:01:49.290 align:start position:0% 00:01:49.290 --> 00:01:54.930 align:start position:0% [Music] 00:01:54.930 --> 00:01:54.940 align:start position:0% 00:01:54.940 --> 00:02:01.520 align:start position:0% yeah<00:01:57.490> so-so 00:02:01.520 --> 00:02:01.530 align:start position:0% 00:02:01.530 --> 00:02:09.129 align:start position:0% [Music] 00:02:09.129 --> 00:02:09.139 align:start position:0% 00:02:09.139 --> 00:02:13.250 align:start position:0% [Music] 00:02:13.250 --> 00:02:13.260 align:start position:0% 00:02:13.260 --> 00:02:21.979 align:start position:0% yeah<00:02:13.920> so<00:02:16.310> yeah<00:02:17.310> so<00:02:18.049> basically<00:02:19.730> the<00:02:20.730> CK<00:02:21.150> column 00:02:21.979 --> 00:02:21.989 align:start position:0% yeah so yeah so basically the CK column 00:02:21.989 --> 00:02:26.449 align:start position:0% yeah so yeah so basically the CK column is<00:02:22.140> all<00:02:22.379> about<00:02:22.830> using<00:02:23.790> snuff<00:02:24.269> for<00:02:25.019> them<00:02:25.459> not 00:02:26.449 --> 00:02:26.459 align:start position:0% is all about using snuff for them not 00:02:26.459 --> 00:02:29.119 align:start position:0% is all about using snuff for them not for<00:02:26.519> their<00:02:26.879> privacy<00:02:27.480> expect<00:02:27.959> for<00:02:28.470> creating 00:02:29.119 --> 00:02:29.129 align:start position:0% for their privacy expect for creating 00:02:29.129 --> 00:02:32.809 align:start position:0% for their privacy expect for creating such<00:02:29.700> improves<00:02:30.150> so<00:02:30.959> that<00:02:31.140> we<00:02:31.799> can<00:02:32.010> verify<00:02:32.519> it 00:02:32.809 --> 00:02:32.819 align:start position:0% such improves so that we can verify it 00:02:32.819 --> 00:02:35.839 align:start position:0% such improves so that we can verify it also<00:02:33.410> computation<00:02:34.410> done<00:02:34.769> off<00:02:35.069> scene<00:02:35.370> you<00:02:35.700> know 00:02:35.839 --> 00:02:35.849 align:start position:0% also computation done off scene you know 00:02:35.849 --> 00:02:39.410 align:start position:0% also computation done off scene you know on<00:02:36.390> a<00:02:36.450> smart<00:02:37.319> contract<00:02:37.530> on<00:02:37.980> its<00:02:38.459> eadamson<00:02:38.760> and 00:02:39.410 --> 00:02:39.420 align:start position:0% on a smart contract on its eadamson and 00:02:39.420 --> 00:02:42.399 align:start position:0% on a smart contract on its eadamson and so<00:02:39.690> forth<00:02:40.230> we<00:02:40.890> basically<00:02:41.370> do<00:02:42.000> all<00:02:42.030> the 00:02:42.399 --> 00:02:42.409 align:start position:0% so forth we basically do all the 00:02:42.409 --> 00:02:45.220 align:start position:0% so forth we basically do all the signature<00:02:43.409> aggregation<00:02:44.250> balance<00:02:44.760> takes 00:02:45.220 --> 00:02:45.230 align:start position:0% signature aggregation balance takes 00:02:45.230 --> 00:02:47.680 align:start position:0% signature aggregation balance takes changing<00:02:46.230> of<00:02:46.410> the<00:02:46.440> balances<00:02:47.310> for<00:02:47.549> the 00:02:47.680 --> 00:02:47.690 align:start position:0% changing of the balances for the 00:02:47.690 --> 00:02:50.330 align:start position:0% changing of the balances for the participants<00:02:48.690> in<00:02:48.900> order<00:02:49.319> to<00:02:49.829> draw<00:02:50.069> lessons 00:02:50.330 --> 00:02:50.340 align:start position:0% participants in order to draw lessons 00:02:50.340 --> 00:02:52.789 align:start position:0% participants in order to draw lessons off<00:02:51.060> scene<00:02:51.390> and<00:02:51.989> we<00:02:52.200> pass<00:02:52.440> all<00:02:52.650> the 00:02:52.789 --> 00:02:52.799 align:start position:0% off scene and we pass all the 00:02:52.799 --> 00:02:55.309 align:start position:0% off scene and we pass all the transaction<00:02:53.579> together<00:02:53.910> and<00:02:54.239> submit<00:02:54.930> the 00:02:55.309 --> 00:02:55.319 align:start position:0% transaction together and submit the 00:02:55.319 --> 00:02:58.789 align:start position:0% transaction together and submit the smart<00:02:56.129> truth<00:02:56.400> as<00:02:56.819> well<00:02:57.480> as<00:02:57.629> the<00:02:57.840> compressed 00:02:58.789 --> 00:02:58.799 align:start position:0% smart truth as well as the compressed 00:02:58.799 --> 00:03:03.440 align:start position:0% smart truth as well as the compressed transactions<00:02:59.609> watching<00:03:00.150> so<00:03:00.959> so<00:03:01.709> so<00:03:02.430> CTO<00:03:03.120> of 00:03:03.440 --> 00:03:03.450 align:start position:0% transactions watching so so so CTO of 00:03:03.450 --> 00:03:05.900 align:start position:0% transactions watching so so so CTO of some<00:03:03.660> basically<00:03:04.109> reduce<00:03:04.650> serration<00:03:05.250> and 00:03:05.900 --> 00:03:05.910 align:start position:0% some basically reduce serration and 00:03:05.910 --> 00:03:08.509 align:start position:0% some basically reduce serration and unlike<00:03:06.599> gamma<00:03:07.019> we<00:03:07.769> don't<00:03:07.950> really<00:03:08.069> have<00:03:08.310> to 00:03:08.509 --> 00:03:08.519 align:start position:0% unlike gamma we don't really have to 00:03:08.519 --> 00:03:10.580 align:start position:0% unlike gamma we don't really have to worry<00:03:08.849> about<00:03:09.030> things<00:03:09.480> like<00:03:09.629> theta<00:03:10.140> being<00:03:10.349> not 00:03:10.580 --> 00:03:10.590 align:start position:0% worry about things like theta being not 00:03:10.590 --> 00:03:16.190 align:start position:0% worry about things like theta being not available<00:03:11.430> and<00:03:12.500> users<00:03:13.500> being<00:03:14.150> like<00:03:15.150> if<00:03:15.720> my 00:03:16.190 --> 00:03:16.200 align:start position:0% available and users being like if my 00:03:16.200 --> 00:03:18.199 align:start position:0% available and users being like if my users<00:03:16.920> office<00:03:17.220> money<00:03:17.370> continuously<00:03:17.910> was 00:03:18.199 --> 00:03:18.209 align:start position:0% users office money continuously was 00:03:18.209 --> 00:03:22.159 align:start position:0% users office money continuously was their<00:03:18.450> coins<00:03:18.889> so<00:03:19.889> they<00:03:20.130> can<00:03:20.280> come<00:03:20.870> it<00:03:21.870> can<00:03:21.930> be 00:03:22.159 --> 00:03:22.169 align:start position:0% their coins so they can come it can be 00:03:22.169 --> 00:03:23.659 align:start position:0% their coins so they can come it can be active<00:03:22.470> and<00:03:22.590> some<00:03:22.829> it<00:03:22.980> challenges<00:03:23.459> if 00:03:23.659 --> 00:03:23.669 align:start position:0% active and some it challenges if 00:03:23.669 --> 00:03:27.699 align:start position:0% active and some it challenges if anything<00:03:24.120> bad<00:03:24.299> happens<00:03:24.720> right<00:03:25.730> has<00:03:26.730> no<00:03:27.329> such 00:03:27.699 --> 00:03:27.709 align:start position:0% anything bad happens right has no such 00:03:27.709 --> 00:03:30.530 align:start position:0% anything bad happens right has no such assumptions<00:03:28.709> so<00:03:28.980> us<00:03:29.130> not<00:03:29.400> proves<00:03:30.269> the 00:03:30.530 --> 00:03:30.540 align:start position:0% assumptions so us not proves the 00:03:30.540 --> 00:03:32.420 align:start position:0% assumptions so us not proves the validity<00:03:30.810> that<00:03:31.440> the<00:03:31.530> transaction<00:03:32.130> the 00:03:32.420 --> 00:03:32.430 align:start position:0% validity that the transaction the 00:03:32.430 --> 00:03:35.659 align:start position:0% validity that the transaction the computation<00:03:33.120> of<00:03:33.510> gene<00:03:33.930> is<00:03:34.410> actually<00:03:35.069> valued 00:03:35.659 --> 00:03:35.669 align:start position:0% computation of gene is actually valued 00:03:35.669 --> 00:03:40.309 align:start position:0% computation of gene is actually valued right<00:03:36.030> so<00:03:36.660> it's<00:03:37.410> um<00:03:37.560> it's<00:03:37.829> pretty<00:03:38.790> simple<00:03:39.319> so 00:03:40.309 --> 00:03:40.319 align:start position:0% right so it's um it's pretty simple so 00:03:40.319 --> 00:03:44.750 align:start position:0% right so it's um it's pretty simple so we<00:03:40.560> have<00:03:40.739> to<00:03:42.109> mean<00:03:43.109> there's<00:03:43.980> a<00:03:44.069> coordinator 00:03:44.750 --> 00:03:44.760 align:start position:0% we have to mean there's a coordinator 00:03:44.760 --> 00:03:48.409 align:start position:0% we have to mean there's a coordinator and<00:03:45.000> there<00:03:45.599> is<00:03:45.720> a<00:03:45.750> user<00:03:46.169> so<00:03:46.919> the<00:03:47.040> coordinator 00:03:48.409 --> 00:03:48.419 align:start position:0% and there is a user so the coordinator 00:03:48.419 --> 00:03:51.740 align:start position:0% and there is a user so the coordinator basically<00:03:49.230> takes<00:03:49.680> other<00:03:50.480> transactions<00:03:51.480> is 00:03:51.740 --> 00:03:51.750 align:start position:0% basically takes other transactions is 00:03:51.750 --> 00:03:54.349 align:start position:0% basically takes other transactions is like<00:03:51.989> inputs<00:03:52.440> and<00:03:53.180> signatures<00:03:54.180> from<00:03:54.269> the 00:03:54.349 --> 00:03:54.359 align:start position:0% like inputs and signatures from the 00:03:54.359 --> 00:03:57.800 align:start position:0% like inputs and signatures from the users<00:03:54.959> by<00:03:55.349> our<00:03:55.530> vision<00:03:56.489> point<00:03:57.000> of<00:03:57.269> API<00:03:57.660> or 00:03:57.800 --> 00:03:57.810 align:start position:0% users by our vision point of API or 00:03:57.810 --> 00:03:59.539 align:start position:0% users by our vision point of API or anything<00:03:58.349> like<00:03:59.069> that 00:03:59.539 --> 00:03:59.549 align:start position:0% anything like that 00:03:59.549 --> 00:04:02.289 align:start position:0% anything like that and<00:03:59.970> he<00:04:00.150> basically<00:04:00.590> generates<00:04:01.590> a<00:04:01.739> batch<00:04:01.950> and 00:04:02.289 --> 00:04:02.299 align:start position:0% and he basically generates a batch and 00:04:02.299 --> 00:04:06.020 align:start position:0% and he basically generates a batch and passes<00:04:03.299> all<00:04:03.750> of<00:04:04.410> the<00:04:04.560> transactions<00:04:05.160> does<00:04:05.790> not 00:04:06.020 --> 00:04:06.030 align:start position:0% passes all of the transactions does not 00:04:06.030 --> 00:04:08.289 align:start position:0% passes all of the transactions does not suck<00:04:06.299> it<00:04:06.480> the<00:04:07.200> stock<00:04:07.440> does<00:04:07.859> not<00:04:07.889> the 00:04:08.289 --> 00:04:08.299 align:start position:0% suck it the stock does not the 00:04:08.299 --> 00:04:11.690 align:start position:0% suck it the stock does not the processing<00:04:09.299> and<00:04:09.629> Emmitt's 00:04:11.690 --> 00:04:11.700 align:start position:0% processing and Emmitt's 00:04:11.700 --> 00:04:14.930 align:start position:0% processing and Emmitt's operated<00:04:12.210> to<00:04:12.330> the<00:04:12.510> blue<00:04:12.690> -<00:04:12.930> and<00:04:13.800> the<00:04:14.220> Snapple 00:04:14.930 --> 00:04:14.940 align:start position:0% operated to the blue - and the Snapple 00:04:14.940 --> 00:04:19.580 align:start position:0% operated to the blue - and the Snapple so<00:04:17.120> or<00:04:18.120> anything<00:04:18.450> of<00:04:18.630> smart<00:04:18.900> contract<00:04:19.320> we 00:04:19.580 --> 00:04:19.590 align:start position:0% so or anything of smart contract we 00:04:19.590 --> 00:04:22.220 align:start position:0% so or anything of smart contract we maintain<00:04:20.310> a<00:04:20.340> balanced<00:04:20.790> system<00:04:20.970> our<00:04:21.870> country 00:04:22.220 --> 00:04:22.230 align:start position:0% maintain a balanced system our country 00:04:22.230 --> 00:04:24.770 align:start position:0% maintain a balanced system our country right<00:04:22.380> so<00:04:22.650> it's<00:04:23.100> like<00:04:23.310> the<00:04:23.550> local<00:04:24.360> tree<00:04:24.510> and 00:04:24.770 --> 00:04:24.780 align:start position:0% right so it's like the local tree and 00:04:24.780 --> 00:04:28.280 align:start position:0% right so it's like the local tree and the<00:04:25.170> leaves<00:04:25.290> contain<00:04:26.420> balances<00:04:27.420> and<00:04:27.750> accounts 00:04:28.280 --> 00:04:28.290 align:start position:0% the leaves contain balances and accounts 00:04:28.290 --> 00:04:32.260 align:start position:0% the leaves contain balances and accounts of<00:04:28.410> all<00:04:28.560> the<00:04:28.710> users<00:04:29.190> right<00:04:29.490> and<00:04:30.020> this<00:04:31.020> this 00:04:32.260 --> 00:04:32.270 align:start position:0% of all the users right and this this 00:04:32.270 --> 00:04:34.880 align:start position:0% of all the users right and this this route<00:04:33.270> acts<00:04:33.480> of<00:04:33.630> this<00:04:33.750> muscle<00:04:33.990> tree<00:04:34.440> can<00:04:34.650> only 00:04:34.880 --> 00:04:34.890 align:start position:0% route acts of this muscle tree can only 00:04:34.890 --> 00:04:40.970 align:start position:0% route acts of this muscle tree can only be<00:04:35.130> updated<00:04:35.850> by<00:04:36.300> us<00:04:36.450> right<00:04:38.210> so<00:04:39.530> as<00:04:40.530> soon<00:04:40.710> as<00:04:40.770> the 00:04:40.970 --> 00:04:40.980 align:start position:0% be updated by us right so as soon as the 00:04:40.980 --> 00:04:43.700 align:start position:0% be updated by us right so as soon as the patch<00:04:41.160> is<00:04:41.400> processed<00:04:41.940> by<00:04:42.210> our<00:04:42.540> coordinator<00:04:43.350> he 00:04:43.700 --> 00:04:43.710 align:start position:0% patch is processed by our coordinator he 00:04:43.710 --> 00:04:47.440 align:start position:0% patch is processed by our coordinator he summons<00:04:44.130> the<00:04:44.220> snap<00:04:44.580> proof<00:04:44.850> watching<00:04:45.660> and<00:04:46.310> the 00:04:47.440 --> 00:04:47.450 align:start position:0% summons the snap proof watching and the 00:04:47.450 --> 00:04:49.909 align:start position:0% summons the snap proof watching and the verifier<00:04:48.450> checks<00:04:49.020> of<00:04:49.200> the<00:04:49.290> proof<00:04:49.500> is<00:04:49.620> correct 00:04:49.909 --> 00:04:49.919 align:start position:0% verifier checks of the proof is correct 00:04:49.919 --> 00:04:52.159 align:start position:0% verifier checks of the proof is correct and<00:04:50.370> the<00:04:50.550> proof<00:04:50.760> is<00:04:50.880> correct<00:04:51.180> the<00:04:51.419> new<00:04:51.720> new 00:04:52.159 --> 00:04:52.169 align:start position:0% and the proof is correct the new new 00:04:52.169 --> 00:04:55.310 align:start position:0% and the proof is correct the new new route<00:04:52.620> is<00:04:53.690> updated<00:04:54.690> in<00:04:54.810> the<00:04:54.840> consummate 00:04:55.310 --> 00:04:55.320 align:start position:0% route is updated in the consummate 00:04:55.320 --> 00:04:59.510 align:start position:0% route is updated in the consummate contract<00:04:55.740> right<00:04:56.060> so<00:04:57.060> yeah<00:04:57.570> this<00:04:58.169> is<00:04:58.230> why<00:04:58.470> a<00:04:58.980> lot 00:04:59.510 --> 00:04:59.520 align:start position:0% contract right so yeah this is why a lot 00:04:59.520 --> 00:05:01.909 align:start position:0% contract right so yeah this is why a lot of<00:04:59.640> scenes<00:04:59.850> really<00:05:00.480> amazing<00:05:01.140> to<00:05:01.260> me<00:05:01.380> so<00:05:01.620> it<00:05:01.770> has 00:05:01.909 --> 00:05:01.919 align:start position:0% of scenes really amazing to me so it has 00:05:01.919 --> 00:05:04.490 align:start position:0% of scenes really amazing to me so it has no<00:05:02.130> it<00:05:02.250> fix<00:05:02.460> it<00:05:02.580> games<00:05:02.820> and<00:05:03.419> it<00:05:04.080> has<00:05:04.200> no 00:05:04.490 --> 00:05:04.500 align:start position:0% no it fix it games and it has no 00:05:04.500 --> 00:05:06.590 align:start position:0% no it fix it games and it has no likeness<00:05:05.150> assumptions<00:05:06.150> no<00:05:06.390> data 00:05:06.590 --> 00:05:06.600 align:start position:0% likeness assumptions no data 00:05:06.600 --> 00:05:08.840 align:start position:0% likeness assumptions no data availability<00:05:07.169> issues<00:05:07.620> that<00:05:08.400> our<00:05:08.580> nation 00:05:08.840 --> 00:05:08.850 align:start position:0% availability issues that our nation 00:05:08.850 --> 00:05:12.080 align:start position:0% availability issues that our nation faces<00:05:08.880> still<00:05:09.870> very<00:05:10.410> very<00:05:10.620> less<00:05:10.830> yeah<00:05:11.820> and 00:05:12.080 --> 00:05:12.090 align:start position:0% faces still very very less yeah and 00:05:12.090 --> 00:05:14.480 align:start position:0% faces still very very less yeah and basically<00:05:12.840> we<00:05:13.169> can<00:05:13.320> create<00:05:13.560> rule<00:05:14.100> of<00:05:14.280> genes 00:05:14.480 --> 00:05:14.490 align:start position:0% basically we can create rule of genes 00:05:14.490 --> 00:05:17.360 align:start position:0% basically we can create rule of genes not<00:05:15.150> only<00:05:15.480> for<00:05:15.750> payments<00:05:16.650> we<00:05:17.040> can<00:05:17.220> do 00:05:17.360 --> 00:05:17.370 align:start position:0% not only for payments we can do 00:05:17.370 --> 00:05:19.840 align:start position:0% not only for payments we can do something<00:05:17.880> like<00:05:17.910> cryptokey<00:05:18.479> bees<00:05:18.660> we<00:05:19.350> can<00:05:19.530> do 00:05:19.840 --> 00:05:19.850 align:start position:0% something like cryptokey bees we can do 00:05:19.850 --> 00:05:23.000 align:start position:0% something like cryptokey bees we can do stuff<00:05:20.850> stuff<00:05:21.210> like<00:05:21.390> what<00:05:21.720> fair<00:05:22.229> event<00:05:22.470> it<00:05:22.740> like 00:05:23.000 --> 00:05:23.010 align:start position:0% stuff stuff like what fair event it like 00:05:23.010 --> 00:05:25.490 align:start position:0% stuff stuff like what fair event it like any<00:05:23.220> any<00:05:23.550> sort<00:05:23.820> of<00:05:23.910> smart<00:05:24.840> product<00:05:25.169> right<00:05:25.260> so 00:05:25.490 --> 00:05:25.500 align:start position:0% any any sort of smart product right so 00:05:25.500 --> 00:05:27.770 align:start position:0% any any sort of smart product right so it's<00:05:25.620> basically<00:05:26.040> a<00:05:26.160> stock<00:05:26.550> storage<00:05:27.150> layer 00:05:27.770 --> 00:05:27.780 align:start position:0% it's basically a stock storage layer 00:05:27.780 --> 00:05:30.710 align:start position:0% it's basically a stock storage layer basically<00:05:28.440> you<00:05:29.220> can<00:05:29.400> put<00:05:29.790> in<00:05:30.030> anything<00:05:30.450> you 00:05:30.710 --> 00:05:30.720 align:start position:0% basically you can put in anything you 00:05:30.720 --> 00:05:32.990 align:start position:0% basically you can put in anything you want<00:05:30.960> you<00:05:31.080> know<00:05:31.260> in<00:05:31.620> the<00:05:32.100> chief<00:05:32.400> of<00:05:32.610> the<00:05:32.760> whole 00:05:32.990 --> 00:05:33.000 align:start position:0% want you know in the chief of the whole 00:05:33.000 --> 00:05:40.460 align:start position:0% want you know in the chief of the whole country<00:05:33.180> and<00:05:33.690> it<00:05:33.780> will<00:05:33.900> work<00:05:37.669> yeah<00:05:38.669> so<00:05:39.380> for<00:05:40.380> the 00:05:40.460 --> 00:05:40.470 align:start position:0% country and it will work yeah so for the 00:05:40.470 --> 00:05:43.640 align:start position:0% country and it will work yeah so for the purpose<00:05:40.860> of<00:05:40.979> this<00:05:41.870> tutorial<00:05:42.870> sort<00:05:43.410> of<00:05:43.500> thing 00:05:43.640 --> 00:05:43.650 align:start position:0% purpose of this tutorial sort of thing 00:05:43.650 --> 00:05:46.670 align:start position:0% purpose of this tutorial sort of thing we<00:05:43.800> are<00:05:43.890> using<00:05:44.430> so<00:05:44.820> calm<00:05:45.090> and<00:05:45.440> snog<00:05:46.440> this 00:05:46.670 --> 00:05:46.680 align:start position:0% we are using so calm and snog this 00:05:46.680 --> 00:05:49.420 align:start position:0% we are using so calm and snog this they're<00:05:47.040> basically<00:05:47.340> dilute<00:05:47.910> based<00:05:48.200> compilers 00:05:49.420 --> 00:05:49.430 align:start position:0% they're basically dilute based compilers 00:05:49.430 --> 00:05:55.070 align:start position:0% they're basically dilute based compilers and<00:05:50.750> these<00:05:51.750> are<00:05:51.930> basic<00:05:52.320> commands<00:05:53.900> you<00:05:54.900> can 00:05:55.070 --> 00:05:55.080 align:start position:0% and these are basic commands you can 00:05:55.080 --> 00:05:57.560 align:start position:0% and these are basic commands you can like<00:05:55.260> back<00:05:56.100> to<00:05:56.460> them 00:05:57.560 --> 00:05:57.570 align:start position:0% like back to them 00:05:57.570 --> 00:06:01.070 align:start position:0% like back to them will<00:05:58.570> mostly<00:05:58.870> need<00:05:59.650> them<00:05:59.860> every<00:06:00.190> time<00:06:00.460> we<00:06:00.610> do<00:06:00.760> a 00:06:01.070 --> 00:06:01.080 align:start position:0% will mostly need them every time we do a 00:06:01.080 --> 00:06:06.920 align:start position:0% will mostly need them every time we do a compilation<00:06:02.080> and<00:06:02.560> we<00:06:02.650> create<00:06:02.890> a<00:06:02.980> input<00:06:03.100> right 00:06:06.920 --> 00:06:06.930 align:start position:0% 00:06:06.930 --> 00:06:10.650 align:start position:0% so<00:06:07.930> I'm<00:06:08.920> just<00:06:08.980> going<00:06:09.460> to<00:06:09.520> show<00:06:09.730> how<00:06:10.180> to<00:06:10.210> create 00:06:10.650 --> 00:06:10.660 align:start position:0% so I'm just going to show how to create 00:06:10.660 --> 00:06:13.100 align:start position:0% so I'm just going to show how to create one<00:06:10.990> one<00:06:11.350> simple<00:06:11.950> constraint<00:06:12.340> is<00:06:12.520> like 00:06:13.100 --> 00:06:13.110 align:start position:0% one one simple constraint is like 00:06:13.110 --> 00:06:15.240 align:start position:0% one one simple constraint is like automatic<00:06:14.110> answering<00:06:14.470> we<00:06:14.650> are<00:06:14.740> going<00:06:14.950> to<00:06:15.070> see 00:06:15.240 --> 00:06:15.250 align:start position:0% automatic answering we are going to see 00:06:15.250 --> 00:06:18.450 align:start position:0% automatic answering we are going to see if<00:06:15.430> a<00:06:15.640> plus<00:06:16.000> B<00:06:16.410> equals<00:06:17.410> C<00:06:17.470> and<00:06:17.830> create<00:06:18.310> a 00:06:18.450 --> 00:06:18.460 align:start position:0% if a plus B equals C and create a 00:06:18.460 --> 00:06:21.780 align:start position:0% if a plus B equals C and create a schnapps<00:06:18.700> not<00:06:19.030> blue<00:06:19.240> for<00:06:19.480> it<00:06:19.600> right<00:06:19.840> so<00:06:20.790> so 00:06:21.780 --> 00:06:21.790 align:start position:0% schnapps not blue for it right so so 00:06:21.790 --> 00:06:24.030 align:start position:0% schnapps not blue for it right so so that<00:06:21.940> we<00:06:22.060> can<00:06:22.240> go<00:06:22.510> anywhere<00:06:23.110> and<00:06:23.290> proof<00:06:23.740> and 00:06:24.030 --> 00:06:24.040 align:start position:0% that we can go anywhere and proof and 00:06:24.040 --> 00:06:25.620 align:start position:0% that we can go anywhere and proof and like<00:06:24.490> prove<00:06:24.730> to<00:06:24.910> someone<00:06:25.180> that<00:06:25.300> this 00:06:25.620 --> 00:06:25.630 align:start position:0% like prove to someone that this 00:06:25.630 --> 00:06:28.380 align:start position:0% like prove to someone that this competition<00:06:26.200> was<00:06:26.350> done<00:06:27.100> correctly<00:06:27.490> right<00:06:27.700> so 00:06:28.380 --> 00:06:28.390 align:start position:0% competition was done correctly right so 00:06:28.390 --> 00:06:30.990 align:start position:0% competition was done correctly right so it's<00:06:28.510> pretty<00:06:28.660> simple<00:06:28.870> as<00:06:29.140> as<00:06:29.640> you<00:06:30.640> can<00:06:30.820> see 00:06:30.990 --> 00:06:31.000 align:start position:0% it's pretty simple as as you can see 00:06:31.000 --> 00:06:32.880 align:start position:0% it's pretty simple as as you can see just<00:06:31.150> like<00:06:31.330> create<00:06:31.750> oh<00:06:31.890> definitely 00:06:32.880 --> 00:06:32.890 align:start position:0% just like create oh definitely 00:06:32.890 --> 00:06:35.910 align:start position:0% just like create oh definitely definitely<00:06:33.160> is<00:06:33.430> just<00:06:33.760> like<00:06:33.910> a<00:06:33.940> socket<00:06:34.600> and<00:06:34.920> we 00:06:35.910 --> 00:06:35.920 align:start position:0% definitely is just like a socket and we 00:06:35.920 --> 00:06:39.800 align:start position:0% definitely is just like a socket and we I<00:06:36.250> mean<00:06:37.090> and<00:06:37.300> the<00:06:38.050> inputs<00:06:38.500> they<00:06:38.860> are<00:06:38.950> world 00:06:39.800 --> 00:06:39.810 align:start position:0% I mean and the inputs they are world 00:06:39.810 --> 00:06:42.780 align:start position:0% I mean and the inputs they are world signal<00:06:40.810> so<00:06:40.960> every<00:06:41.350> every<00:06:41.590> variable<00:06:42.040> is<00:06:42.310> a<00:06:42.460> sort 00:06:42.780 --> 00:06:42.790 align:start position:0% signal so every every variable is a sort 00:06:42.790 --> 00:06:46.110 align:start position:0% signal so every every variable is a sort of<00:06:42.910> signal<00:06:43.270> for<00:06:44.140> you<00:06:44.590> can<00:06:44.740> imagine<00:06:45.120> circuits 00:06:46.110 --> 00:06:46.120 align:start position:0% of signal for you can imagine circuits 00:06:46.120 --> 00:06:48.540 align:start position:0% of signal for you can imagine circuits like<00:06:46.210> electronics<00:06:46.960> circuits<00:06:47.470> right<00:06:47.650> so<00:06:48.190> in 00:06:48.540 --> 00:06:48.550 align:start position:0% like electronics circuits right so in 00:06:48.550 --> 00:06:51.060 align:start position:0% like electronics circuits right so in electronic<00:06:49.330> circuits<00:06:49.780> also<00:06:49.900> we<00:06:50.080> have<00:06:50.200> signals 00:06:51.060 --> 00:06:51.070 align:start position:0% electronic circuits also we have signals 00:06:51.070 --> 00:06:54.360 align:start position:0% electronic circuits also we have signals in<00:06:51.340> the<00:06:51.520> inputs<00:06:52.150> and<00:06:52.390> outputs<00:06:52.660> as<00:06:53.560> well<00:06:53.590> so 00:06:54.360 --> 00:06:54.370 align:start position:0% in the inputs and outputs as well so 00:06:54.370 --> 00:06:55.860 align:start position:0% in the inputs and outputs as well so here<00:06:54.580> we<00:06:54.760> are<00:06:54.820> accepting<00:06:55.270> three<00:06:55.540> private 00:06:55.860 --> 00:06:55.870 align:start position:0% here we are accepting three private 00:06:55.870 --> 00:06:58.409 align:start position:0% here we are accepting three private inputs<00:06:56.200> yeah<00:06:56.680> calling<00:06:57.160> in<00:06:57.280> a<00:06:57.460> B<00:06:57.640> and<00:06:57.790> C<00:06:57.970> and<00:06:58.360> we 00:06:58.409 --> 00:06:58.419 align:start position:0% inputs yeah calling in a B and C and we 00:06:58.419 --> 00:07:00.900 align:start position:0% inputs yeah calling in a B and C and we have<00:06:59.320> one<00:06:59.740> one<00:07:00.130> public<00:07:00.520> input 00:07:00.900 --> 00:07:00.910 align:start position:0% have one one public input 00:07:00.910 --> 00:07:02.970 align:start position:0% have one one public input it's<00:07:01.060> called<00:07:01.300> C<00:07:01.510> right<00:07:01.720> and<00:07:02.290> we<00:07:02.710> create<00:07:02.950> a 00:07:02.970 --> 00:07:02.980 align:start position:0% it's called C right and we create a 00:07:02.980 --> 00:07:06.990 align:start position:0% it's called C right and we create a table<00:07:03.280> for<00:07:03.310> signal<00:07:03.880> color<00:07:04.650> and<00:07:05.650> this<00:07:06.460> this<00:07:06.940> is 00:07:06.990 --> 00:07:07.000 align:start position:0% table for signal color and this this is 00:07:07.000 --> 00:07:08.880 align:start position:0% table for signal color and this this is that<00:07:07.360> we<00:07:07.570> have<00:07:07.660> forcing<00:07:08.290> of<00:07:08.410> constraint<00:07:08.800> we 00:07:08.880 --> 00:07:08.890 align:start position:0% that we have forcing of constraint we 00:07:08.890 --> 00:07:11.940 align:start position:0% that we have forcing of constraint we are<00:07:08.980> basically<00:07:09.280> forcing<00:07:09.820> a<00:07:10.260> plus<00:07:11.260> B<00:07:11.440> to<00:07:11.800> be 00:07:11.940 --> 00:07:11.950 align:start position:0% are basically forcing a plus B to be 00:07:11.950 --> 00:07:14.460 align:start position:0% are basically forcing a plus B to be equal<00:07:12.130> to<00:07:12.400> C<00:07:12.760> which<00:07:13.000> is<00:07:13.210> provided<00:07:13.690> a<00:07:13.780> public 00:07:14.460 --> 00:07:14.470 align:start position:0% equal to C which is provided a public 00:07:14.470 --> 00:07:18.570 align:start position:0% equal to C which is provided a public input<00:07:14.700> so<00:07:15.700> so<00:07:16.210> far<00:07:16.620> we<00:07:17.620> can<00:07:17.770> basically<00:07:18.100> prove 00:07:18.570 --> 00:07:18.580 align:start position:0% input so so far we can basically prove 00:07:18.580 --> 00:07:21.890 align:start position:0% input so so far we can basically prove that<00:07:18.760> two<00:07:19.120> plus<00:07:19.390> two<00:07:19.630> equals<00:07:20.530> four<00:07:20.669> without 00:07:21.890 --> 00:07:21.900 align:start position:0% that two plus two equals four without 00:07:21.900 --> 00:07:25.230 align:start position:0% that two plus two equals four without getting<00:07:22.900> to<00:07:23.020> know<00:07:23.169> what<00:07:23.490> what<00:07:24.490> the<00:07:24.669> first<00:07:25.060> two 00:07:25.230 --> 00:07:25.240 align:start position:0% getting to know what what the first two 00:07:25.240 --> 00:07:27.210 align:start position:0% getting to know what what the first two variables<00:07:25.870> mean<00:07:25.990> we<00:07:26.500> don't<00:07:26.710> need<00:07:26.860> to<00:07:27.070> know 00:07:27.210 --> 00:07:27.220 align:start position:0% variables mean we don't need to know 00:07:27.220 --> 00:07:30.030 align:start position:0% variables mean we don't need to know that<00:07:27.460> they<00:07:27.640> were<00:07:27.760> two<00:07:27.910> and<00:07:27.940> two<00:07:28.380> yeah<00:07:29.380> that's 00:07:30.030 --> 00:07:30.040 align:start position:0% that they were two and two yeah that's 00:07:30.040 --> 00:07:32.850 align:start position:0% that they were two and two yeah that's one<00:07:30.190> so<00:07:30.460> they<00:07:30.970> can<00:07:31.120> be<00:07:31.540> one<00:07:31.840> and<00:07:32.020> three<00:07:32.080> or<00:07:32.470> they 00:07:32.850 --> 00:07:32.860 align:start position:0% one so they can be one and three or they 00:07:32.860 --> 00:07:35.880 align:start position:0% one so they can be one and three or they can<00:07:33.040> be<00:07:33.160> three<00:07:33.400> and<00:07:33.610> one<00:07:34.620> we<00:07:35.620> don't<00:07:35.800> really 00:07:35.880 --> 00:07:35.890 align:start position:0% can be three and one we don't really 00:07:35.890 --> 00:07:36.690 align:start position:0% can be three and one we don't really need<00:07:36.100> to<00:07:36.250> know<00:07:36.280> where 00:07:36.690 --> 00:07:36.700 align:start position:0% need to know where 00:07:36.700 --> 00:07:38.580 align:start position:0% need to know where so<00:07:37.240> this<00:07:37.450> basically<00:07:37.810> creates<00:07:38.169> a<00:07:38.290> constant 00:07:38.580 --> 00:07:38.590 align:start position:0% so this basically creates a constant 00:07:38.590 --> 00:07:42.440 align:start position:0% so this basically creates a constant concern<00:07:39.580> for<00:07:40.060> addition<00:07:40.840> we<00:07:41.500> can<00:07:41.620> do<00:07:41.860> one<00:07:42.070> for 00:07:42.440 --> 00:07:42.450 align:start position:0% concern for addition we can do one for 00:07:42.450 --> 00:07:44.610 align:start position:0% concern for addition we can do one for multiplication<00:07:43.450> as<00:07:43.540> well<00:07:43.750> like<00:07:44.260> this<00:07:44.440> is 00:07:44.610 --> 00:07:44.620 align:start position:0% multiplication as well like this is 00:07:44.620 --> 00:07:46.280 align:start position:0% multiplication as well like this is pretty<00:07:44.800> simple 00:07:46.280 --> 00:07:46.290 align:start position:0% pretty simple 00:07:46.290 --> 00:07:49.740 align:start position:0% pretty simple whatever<00:07:47.290> we<00:07:47.470> need<00:07:47.500> to<00:07:47.740> give<00:07:48.400> as<00:07:48.520> a<00:07:48.550> output<00:07:49.540> we 00:07:49.740 --> 00:07:49.750 align:start position:0% whatever we need to give as a output we 00:07:49.750 --> 00:07:53.280 align:start position:0% whatever we need to give as a output we just<00:07:50.610> force<00:07:51.610> of<00:07:51.820> constrain<00:07:52.210> and<00:07:52.390> we<00:07:52.660> assign<00:07:53.050> to 00:07:53.280 --> 00:07:53.290 align:start position:0% just force of constrain and we assign to 00:07:53.290 --> 00:07:55.770 align:start position:0% just force of constrain and we assign to the<00:07:53.440> variable<00:07:54.090> so<00:07:55.090> as<00:07:55.180> you<00:07:55.330> can<00:07:55.450> see<00:07:55.660> it's 00:07:55.770 --> 00:07:55.780 align:start position:0% the variable so as you can see it's 00:07:55.780 --> 00:08:00.240 align:start position:0% the variable so as you can see it's pretty<00:07:56.050> simple<00:07:56.410> right<00:07:57.540> yeah<00:07:58.540> so 00:08:00.240 --> 00:08:00.250 align:start position:0% pretty simple right yeah so 00:08:00.250 --> 00:08:02.400 align:start position:0% pretty simple right yeah so we<00:08:00.340> are<00:08:00.460> done<00:08:00.670> with<00:08:00.820> the<00:08:01.000> is<00:08:01.750> anyone<00:08:02.200> following 00:08:02.400 --> 00:08:02.410 align:start position:0% we are done with the is anyone following 00:08:02.410 --> 00:08:07.410 align:start position:0% we are done with the is anyone following the<00:08:02.650> number<00:08:02.950> should<00:08:03.460> again<00:08:04.980> yeah<00:08:05.980> cool<00:08:06.550> so<00:08:07.360> if 00:08:07.410 --> 00:08:07.420 align:start position:0% the number should again yeah cool so if 00:08:07.420 --> 00:08:09.360 align:start position:0% the number should again yeah cool so if anyone<00:08:07.870> wants<00:08:08.080> to<00:08:08.110> compile<00:08:08.530> it<00:08:08.740> and<00:08:08.980> generate 00:08:09.360 --> 00:08:09.370 align:start position:0% anyone wants to compile it and generate 00:08:09.370 --> 00:08:13.350 align:start position:0% anyone wants to compile it and generate inputs<00:08:09.790> and<00:08:10.470> so<00:08:11.470> first<00:08:12.160> of<00:08:12.280> all<00:08:12.400> be<00:08:12.610> from<00:08:13.180> the 00:08:13.350 --> 00:08:13.360 align:start position:0% inputs and so first of all be from the 00:08:13.360 --> 00:08:16.290 align:start position:0% inputs and so first of all be from the SOCOM's<00:08:14.230> socket<00:08:14.890> we<00:08:15.160> did<00:08:15.400> our<00:08:15.610> compiled 00:08:16.290 --> 00:08:16.300 align:start position:0% SOCOM's socket we did our compiled 00:08:16.300 --> 00:08:19.050 align:start position:0% SOCOM's socket we did our compiled version<00:08:16.690> and<00:08:17.200> it's<00:08:17.350> called<00:08:17.590> it's<00:08:18.550> a<00:08:18.700> it's 00:08:19.050 --> 00:08:19.060 align:start position:0% version and it's called it's a it's 00:08:19.060 --> 00:08:21.150 align:start position:0% version and it's called it's a it's basically<00:08:19.480> JSON<00:08:19.930> representation<00:08:20.650> of<00:08:21.040> the 00:08:21.150 --> 00:08:21.160 align:start position:0% basically JSON representation of the 00:08:21.160 --> 00:08:23.280 align:start position:0% basically JSON representation of the stock<00:08:21.640> constraint<00:08:22.360> in<00:08:22.480> the<00:08:22.600> circuit<00:08:23.110> right 00:08:23.280 --> 00:08:23.290 align:start position:0% stock constraint in the circuit right 00:08:23.290 --> 00:08:25.650 align:start position:0% stock constraint in the circuit right and<00:08:23.610> then<00:08:24.610> we<00:08:24.730> basically<00:08:24.880> have<00:08:25.330> to<00:08:25.450> create 00:08:25.650 --> 00:08:25.660 align:start position:0% and then we basically have to create 00:08:25.660 --> 00:08:28.800 align:start position:0% and then we basically have to create inputs<00:08:26.110> so<00:08:26.680> the<00:08:26.770> inputs<00:08:27.340> for<00:08:27.550> this<00:08:28.000> would 00:08:28.800 --> 00:08:28.810 align:start position:0% inputs so the inputs for this would 00:08:28.810 --> 00:08:34.260 align:start position:0% inputs so the inputs for this would basically<00:08:28.990> be<00:08:29.700> ABC<00:08:31.169> ABD<00:08:32.169> and<00:08:32.320> c<00:08:32.820> so<00:08:33.820> we<00:08:33.849> just 00:08:34.260 --> 00:08:34.270 align:start position:0% basically be ABC ABD and c so we just 00:08:34.270 --> 00:08:36.779 align:start position:0% basically be ABC ABD and c so we just put<00:08:34.870> that<00:08:35.020> in<00:08:35.169> a<00:08:35.260> file<00:08:35.469> I<00:08:35.680> can<00:08:35.890> show<00:08:36.520> you<00:08:36.610> that 00:08:36.779 --> 00:08:36.789 align:start position:0% put that in a file I can show you that 00:08:36.789 --> 00:08:40.630 align:start position:0% put that in a file I can show you that fine 00:08:40.630 --> 00:08:40.640 align:start position:0% 00:08:40.640 --> 00:08:45.400 align:start position:0% [Music] 00:08:45.400 --> 00:08:45.410 align:start position:0% 00:08:45.410 --> 00:08:50.660 align:start position:0% so<00:08:47.000> this<00:08:48.000> thing<00:08:48.180> basically<00:08:48.660> is<00:08:49.110> the<00:08:49.460> keys<00:08:50.460> of 00:08:50.660 --> 00:08:50.670 align:start position:0% so this thing basically is the keys of 00:08:50.670 --> 00:08:58.210 align:start position:0% so this thing basically is the keys of Inuyasha 00:08:58.210 --> 00:08:58.220 align:start position:0% 00:08:58.220 --> 00:09:02.380 align:start position:0% yeah<00:08:58.760> so<00:08:59.180> yeah<00:08:59.960> we<00:09:00.170> just<00:09:00.320> passed<00:09:00.650> the<00:09:00.710> inputs<00:09:01.390> 2 00:09:02.380 --> 00:09:02.390 align:start position:0% yeah so yeah we just passed the inputs 2 00:09:02.390 --> 00:09:05.880 align:start position:0% yeah so yeah we just passed the inputs 2 4<00:09:02.660> 6<00:09:03.020> and<00:09:03.230> 24<00:09:03.620> and<00:09:03.890> we<00:09:04.370> get<00:09:04.640> input<00:09:05.090> on<00:09:05.330> adjacent 00:09:05.880 --> 00:09:05.890 align:start position:0% 4 6 and 24 and we get input on adjacent 00:09:05.890 --> 00:09:08.770 align:start position:0% 4 6 and 24 and we get input on adjacent right<00:09:06.890> which<00:09:07.280> which<00:09:07.520> has<00:09:07.910> all<00:09:08.390> of<00:09:08.600> these 00:09:08.770 --> 00:09:08.780 align:start position:0% right which which has all of these 00:09:08.780 --> 00:09:16.570 align:start position:0% right which which has all of these variables<00:09:09.310> and<00:09:13.510> then<00:09:14.510> we<00:09:14.690> basically<00:09:15.460> when<00:09:16.460> you 00:09:16.570 --> 00:09:16.580 align:start position:0% variables and then we basically when you 00:09:16.580 --> 00:09:18.370 align:start position:0% variables and then we basically when you have<00:09:16.640> input<00:09:17.330> dot<00:09:17.510> Jason<00:09:17.960> ready 00:09:18.370 --> 00:09:18.380 align:start position:0% have input dot Jason ready 00:09:18.380 --> 00:09:21.670 align:start position:0% have input dot Jason ready we<00:09:18.650> cater<00:09:18.890> we<00:09:19.340> calculate<00:09:20.120> witness<00:09:20.650> which<00:09:21.650> is 00:09:21.670 --> 00:09:21.680 align:start position:0% we cater we calculate witness which is 00:09:21.680 --> 00:09:24.010 align:start position:0% we cater we calculate witness which is like<00:09:21.980> the<00:09:22.430> inputs<00:09:23.240> we<00:09:23.390> are<00:09:23.480> going<00:09:23.660> to<00:09:23.750> provide 00:09:24.010 --> 00:09:24.020 align:start position:0% like the inputs we are going to provide 00:09:24.020 --> 00:09:29.730 align:start position:0% like the inputs we are going to provide us<00:09:24.080> not<00:09:24.440> that<00:09:24.760> what<00:09:25.990> that<00:09:26.990> input<00:09:27.380> basically 00:09:29.730 --> 00:09:29.740 align:start position:0% us not that what that input basically 00:09:29.740 --> 00:09:32.530 align:start position:0% us not that what that input basically satisfies<00:09:30.740> all<00:09:31.010> the<00:09:31.130> constraints<00:09:31.370> defined<00:09:32.150> in 00:09:32.530 --> 00:09:32.540 align:start position:0% satisfies all the constraints defined in 00:09:32.540 --> 00:09:35.740 align:start position:0% satisfies all the constraints defined in the<00:09:32.690> socket<00:09:33.260> so<00:09:33.440> if<00:09:33.590> if<00:09:34.160> this<00:09:34.880> command<00:09:35.300> throws 00:09:35.740 --> 00:09:35.750 align:start position:0% the socket so if if this command throws 00:09:35.750 --> 00:09:37.900 align:start position:0% the socket so if if this command throws an<00:09:35.900> error<00:09:36.080> with<00:09:36.890> that<00:09:36.920> that<00:09:37.250> basically<00:09:37.610> means 00:09:37.900 --> 00:09:37.910 align:start position:0% an error with that that basically means 00:09:37.910 --> 00:09:40.180 align:start position:0% an error with that that basically means your<00:09:38.090> inputs<00:09:38.510> not<00:09:38.900> not<00:09:39.260> going<00:09:39.500> to<00:09:39.620> pass<00:09:39.980> this 00:09:40.180 --> 00:09:40.190 align:start position:0% your inputs not not going to pass this 00:09:40.190 --> 00:09:42.550 align:start position:0% your inputs not not going to pass this is<00:09:40.280> not<00:09:40.400> serving<00:09:41.050> something<00:09:42.050> is<00:09:42.170> wrong<00:09:42.380> with 00:09:42.550 --> 00:09:42.560 align:start position:0% is not serving something is wrong with 00:09:42.560 --> 00:09:47.740 align:start position:0% is not serving something is wrong with the<00:09:42.620> input<00:09:43.330> and<00:09:44.560> this<00:09:45.560> is<00:09:45.710> the<00:09:45.740> does<00:09:46.550> it<00:09:46.700> set<00:09:47.600> up 00:09:47.740 --> 00:09:47.750 align:start position:0% the input and this is the does it set up 00:09:47.750 --> 00:09:49.900 align:start position:0% the input and this is the does it set up it's<00:09:48.080> currently<00:09:48.710> only<00:09:48.830> on<00:09:49.580> your<00:09:49.760> on<00:09:49.880> your 00:09:49.900 --> 00:09:49.910 align:start position:0% it's currently only on your on your 00:09:49.910 --> 00:09:52.990 align:start position:0% it's currently only on your on your laptop<00:09:50.450> so<00:09:50.780> it's<00:09:51.470> it's<00:09:52.100> when<00:09:52.520> do<00:09:52.640> a<00:09:52.670> pretty 00:09:52.990 --> 00:09:53.000 align:start position:0% laptop so it's it's when do a pretty 00:09:53.000 --> 00:09:56.230 align:start position:0% laptop so it's it's when do a pretty unsafe<00:09:53.360> and<00:09:54.190> then<00:09:55.190> we<00:09:55.550> can<00:09:55.700> create<00:09:55.850> a<00:09:55.940> proof 00:09:56.230 --> 00:09:56.240 align:start position:0% unsafe and then we can create a proof 00:09:56.240 --> 00:09:58.750 align:start position:0% unsafe and then we can create a proof and<00:09:56.540> we<00:09:57.290> can<00:09:57.440> just<00:09:57.620> not<00:09:57.800> just<00:09:57.980> verify<00:09:58.430> which<00:09:58.640> is 00:09:58.750 --> 00:09:58.760 align:start position:0% and we can just not just verify which is 00:09:58.760 --> 00:10:01.210 align:start position:0% and we can just not just verify which is basically<00:09:59.090> tell<00:09:59.360> you<00:09:59.480> of<00:09:59.570> the<00:09:59.680> the<00:10:00.680> proof<00:10:00.950> was 00:10:01.210 --> 00:10:01.220 align:start position:0% basically tell you of the the proof was 00:10:01.220 --> 00:10:03.700 align:start position:0% basically tell you of the the proof was right<00:10:01.640> so<00:10:02.180> it<00:10:02.270> if<00:10:02.510> it<00:10:02.690> displays<00:10:03.200> okay<00:10:03.500> and 00:10:03.700 --> 00:10:03.710 align:start position:0% right so it if it displays okay and 00:10:03.710 --> 00:10:05.760 align:start position:0% right so it if it displays okay and those<00:10:03.830> good<00:10:04.040> if<00:10:04.400> it's<00:10:04.610> either<00:10:04.760> invalid 00:10:05.760 --> 00:10:05.770 align:start position:0% those good if it's either invalid 00:10:05.770 --> 00:10:08.920 align:start position:0% those good if it's either invalid something<00:10:06.770> went<00:10:06.950> wrong<00:10:07.130> your<00:10:07.610> input<00:10:08.240> did<00:10:08.540> not 00:10:08.920 --> 00:10:08.930 align:start position:0% something went wrong your input did not 00:10:08.930 --> 00:10:18.360 align:start position:0% something went wrong your input did not satisfy<00:10:09.140> all<00:10:09.620> the<00:10:09.800> constraints<00:10:10.060> defined<00:10:17.200> so 00:10:18.360 --> 00:10:18.370 align:start position:0% satisfy all the constraints defined so 00:10:18.370 --> 00:10:22.300 align:start position:0% satisfy all the constraints defined so growth<00:10:19.370> is<00:10:19.550> like<00:10:19.880> drops<00:10:20.500> 16<00:10:21.500> this<00:10:21.860> is<00:10:21.920> the<00:10:22.130> most 00:10:22.300 --> 00:10:22.310 align:start position:0% growth is like drops 16 this is the most 00:10:22.310 --> 00:10:25.300 align:start position:0% growth is like drops 16 this is the most efficient<00:10:23.120> proven<00:10:23.620> there<00:10:24.620> are<00:10:24.770> some<00:10:24.980> other 00:10:25.300 --> 00:10:25.310 align:start position:0% efficient proven there are some other 00:10:25.310 --> 00:10:27.970 align:start position:0% efficient proven there are some other options<00:10:25.580> you<00:10:26.450> can<00:10:26.600> do<00:10:26.780> that<00:10:27.320> such<00:10:27.560> protocol 00:10:27.970 --> 00:10:27.980 align:start position:0% options you can do that such protocol 00:10:27.980 --> 00:10:32.590 align:start position:0% options you can do that such protocol and<00:10:28.360> help<00:10:29.360> it's<00:10:29.930> like<00:10:30.110> I<00:10:30.410> guess<00:10:30.890> I<00:10:31.220> I<00:10:32.120> don't 00:10:32.590 --> 00:10:32.600 align:start position:0% and help it's like I guess I I don't 00:10:32.600 --> 00:10:35.210 align:start position:0% and help it's like I guess I I don't really<00:10:32.780> know<00:10:32.990> if<00:10:33.020> always<00:10:33.860> been<00:10:34.040> using<00:10:34.490> this 00:10:35.210 --> 00:10:35.220 align:start position:0% really know if always been using this 00:10:35.220 --> 00:10:44.350 align:start position:0% really know if always been using this yeah 00:10:44.350 --> 00:10:44.360 align:start position:0% 00:10:44.360 --> 00:10:46.800 align:start position:0% yeah 00:10:46.800 --> 00:10:46.810 align:start position:0% yeah 00:10:46.810 --> 00:10:49.830 align:start position:0% yeah so<00:10:47.410> if<00:10:47.860> you<00:10:48.040> are<00:10:48.250> if<00:10:48.460> you<00:10:48.610> guys<00:10:48.760> want<00:10:48.970> I<00:10:49.090> can<00:10:49.300> you 00:10:49.830 --> 00:10:49.840 align:start position:0% so if you are if you guys want I can you 00:10:49.840 --> 00:10:52.590 align:start position:0% so if you are if you guys want I can you know<00:10:50.130> learn<00:10:51.130> these<00:10:51.250> and<00:10:51.460> show<00:10:51.760> you<00:10:51.820> what<00:10:52.120> it's 00:10:52.590 --> 00:10:52.600 align:start position:0% know learn these and show you what it's 00:10:52.600 --> 00:10:55.020 align:start position:0% know learn these and show you what it's quite<00:10:53.230> do<00:10:53.620> I<00:10:53.650> do<00:10:54.160> we<00:10:54.400> run<00:10:54.460> all<00:10:54.640> the<00:10:54.790> proofs 00:10:55.020 --> 00:10:55.030 align:start position:0% quite do I do we run all the proofs 00:10:55.030 --> 00:10:58.680 align:start position:0% quite do I do we run all the proofs right<00:10:55.720> so<00:10:56.170> I'm<00:10:56.680> gonna<00:10:56.920> operate<00:10:57.580> if<00:10:57.850> someone 00:10:58.680 --> 00:10:58.690 align:start position:0% right so I'm gonna operate if someone 00:10:58.690 --> 00:11:02.220 align:start position:0% right so I'm gonna operate if someone wants<00:10:58.900> to<00:10:58.930> not<00:10:59.290> be<00:10:59.460> happy<00:11:00.460> do<00:11:00.580> you<00:11:00.790> know<00:11:01.230> debug 00:11:02.220 --> 00:11:02.230 align:start position:0% wants to not be happy do you know debug 00:11:02.230 --> 00:11:06.690 align:start position:0% wants to not be happy do you know debug if<00:11:02.350> there's<00:11:02.560> any<00:11:02.740> issues<00:11:03.750> who<00:11:04.750> so<00:11:05.290> we<00:11:05.550> we<00:11:06.550> are 00:11:06.690 --> 00:11:06.700 align:start position:0% if there's any issues who so we we are 00:11:06.700 --> 00:11:10.650 align:start position:0% if there's any issues who so we we are going<00:11:06.970> to<00:11:07.090> verify<00:11:07.800> EDSA<00:11:08.830> signature<00:11:09.670> next<00:11:09.940> so 00:11:10.650 --> 00:11:10.660 align:start position:0% going to verify EDSA signature next so 00:11:10.660 --> 00:11:14.190 align:start position:0% going to verify EDSA signature next so us<00:11:11.170> when<00:11:11.380> snarks<00:11:11.860> is<00:11:12.070> it's<00:11:12.400> much<00:11:13.240> more<00:11:13.480> easier 00:11:14.190 --> 00:11:14.200 align:start position:0% us when snarks is it's much more easier 00:11:14.200 --> 00:11:18.240 align:start position:0% us when snarks is it's much more easier to<00:11:14.260> verify<00:11:15.360> PDSA<00:11:16.410> signature<00:11:17.410> than<00:11:17.770> in<00:11:17.980> syria 00:11:18.240 --> 00:11:18.250 align:start position:0% to verify PDSA signature than in syria 00:11:18.250 --> 00:11:21.120 align:start position:0% to verify PDSA signature than in syria more<00:11:18.610> bitcoins<00:11:18.930> signature<00:11:20.010> because<00:11:21.010> it 00:11:21.120 --> 00:11:21.130 align:start position:0% more bitcoins signature because it 00:11:21.130 --> 00:11:22.980 align:start position:0% more bitcoins signature because it requires<00:11:21.460> less<00:11:21.550> lesser<00:11:22.480> number<00:11:22.960> of 00:11:22.980 --> 00:11:22.990 align:start position:0% requires less lesser number of 00:11:22.990 --> 00:11:26.580 align:start position:0% requires less lesser number of constraints<00:11:23.730> right<00:11:24.730> so<00:11:25.290> so<00:11:26.290> there's<00:11:26.530> a 00:11:26.580 --> 00:11:26.590 align:start position:0% constraints right so so there's a 00:11:26.590 --> 00:11:30.390 align:start position:0% constraints right so so there's a library<00:11:27.490> called<00:11:27.820> so<00:11:28.690> common<00:11:29.080> and<00:11:29.320> they<00:11:29.860> export 00:11:30.390 --> 00:11:30.400 align:start position:0% library called so common and they export 00:11:30.400 --> 00:11:34.950 align:start position:0% library called so common and they export a<00:11:31.350> template<00:11:32.380> it's<00:11:32.560> called<00:11:32.860> EDD<00:11:33.760> si<00:11:34.090> si<00:11:34.840> we 00:11:34.950 --> 00:11:34.960 align:start position:0% a template it's called EDD si si we 00:11:34.960 --> 00:11:37.530 align:start position:0% a template it's called EDD si si we verified<00:11:35.380> happy<00:11:36.220> heart<00:11:36.430> so<00:11:36.940> this<00:11:37.210> is<00:11:37.360> this<00:11:37.510> a 00:11:37.530 --> 00:11:37.540 align:start position:0% verified happy heart so this is this a 00:11:37.540 --> 00:11:40.460 align:start position:0% verified happy heart so this is this a hash<00:11:37.810> function<00:11:37.840> called<00:11:38.560> gypsy<00:11:39.150> because 00:11:40.460 --> 00:11:40.470 align:start position:0% hash function called gypsy because 00:11:40.470 --> 00:11:43.290 align:start position:0% hash function called gypsy because sha-256<00:11:41.470> is<00:11:41.860> like<00:11:42.190> way<00:11:42.400> too<00:11:42.460> costly<00:11:42.820> to<00:11:43.150> use 00:11:43.290 --> 00:11:43.300 align:start position:0% sha-256 is like way too costly to use 00:11:43.300 --> 00:11:46.500 align:start position:0% sha-256 is like way too costly to use insiders<00:11:43.780> not<00:11:43.930> see<00:11:44.110> this<00:11:44.260> is<00:11:44.380> like<00:11:45.150> so 00:11:46.500 --> 00:11:46.510 align:start position:0% insiders not see this is like so 00:11:46.510 --> 00:11:49.530 align:start position:0% insiders not see this is like so MC<00:11:46.960> uses<00:11:47.350> much<00:11:47.680> less<00:11:48.060> number<00:11:49.060> of<00:11:49.150> constraints 00:11:49.530 --> 00:11:49.540 align:start position:0% MC uses much less number of constraints 00:11:49.540 --> 00:11:51.900 align:start position:0% MC uses much less number of constraints and<00:11:49.870> it's<00:11:50.220> therefore<00:11:51.220> the<00:11:51.280> proven<00:11:51.610> time<00:11:51.790> is 00:11:51.900 --> 00:11:51.910 align:start position:0% and it's therefore the proven time is 00:11:51.910 --> 00:11:54.300 align:start position:0% and it's therefore the proven time is low<00:11:52.090> and<00:11:52.780> for<00:11:53.050> the<00:11:53.170> purpose<00:11:53.500> of<00:11:53.650> this<00:11:53.980> workshop 00:11:54.300 --> 00:11:54.310 align:start position:0% low and for the purpose of this workshop 00:11:54.310 --> 00:11:57.690 align:start position:0% low and for the purpose of this workshop this<00:11:55.020> this<00:11:56.020> level<00:11:56.290> of<00:11:56.470> security<00:11:57.070> should<00:11:57.580> be 00:11:57.690 --> 00:11:57.700 align:start position:0% this this level of security should be 00:11:57.700 --> 00:11:58.140 align:start position:0% this this level of security should be just<00:11:57.880> fine 00:11:58.140 --> 00:11:58.150 align:start position:0% just fine 00:11:58.150 --> 00:12:02.820 align:start position:0% just fine okay<00:11:59.020> so<00:11:59.620> so<00:12:00.370> it's<00:12:00.490> very<00:12:00.730> easy<00:12:01.090> to<00:12:01.510> use<00:12:02.200> this 00:12:02.820 --> 00:12:02.830 align:start position:0% okay so so it's very easy to use this 00:12:02.830 --> 00:12:06.750 align:start position:0% okay so so it's very easy to use this template<00:12:03.310> we<00:12:03.520> just<00:12:03.730> like<00:12:03.910> pass<00:12:04.690> the<00:12:04.930> from<00:12:05.760> the 00:12:06.750 --> 00:12:06.760 align:start position:0% template we just like pass the from the 00:12:06.760 --> 00:12:12.360 align:start position:0% template we just like pass the from the slope<00:12:08.130> you<00:12:09.130> know<00:12:09.450> for<00:12:10.450> a<00:12:10.500> PDSA<00:12:11.500> of<00:12:11.980> key<00:12:12.220> there 00:12:12.360 --> 00:12:12.370 align:start position:0% slope you know for a PDSA of key there 00:12:12.370 --> 00:12:13.920 align:start position:0% slope you know for a PDSA of key there are<00:12:12.430> two<00:12:12.610> parts<00:12:12.910> the<00:12:13.060> x-coordinate<00:12:13.780> and 00:12:13.920 --> 00:12:13.930 align:start position:0% are two parts the x-coordinate and 00:12:13.930 --> 00:12:19.350 align:start position:0% are two parts the x-coordinate and there's<00:12:14.170> a<00:12:14.260> white<00:12:14.410> 5.8<00:12:15.100> right<00:12:15.340> so<00:12:16.200> verify<00:12:17.220> we<00:12:18.360> X 00:12:19.350 --> 00:12:19.360 align:start position:0% there's a white 5.8 right so verify we X 00:12:19.360 --> 00:12:21.420 align:start position:0% there's a white 5.8 right so verify we X because<00:12:19.960> the<00:12:20.140> bees<00:12:20.530> and<00:12:20.770> the<00:12:20.890> x-coordinate 00:12:21.420 --> 00:12:21.430 align:start position:0% because the bees and the x-coordinate 00:12:21.430 --> 00:12:24.050 align:start position:0% because the bees and the x-coordinate and<00:12:21.970> here<00:12:22.390> we<00:12:22.510> signed<00:12:22.690> a<00:12:22.780> y-coordinate<00:12:23.380> and 00:12:24.050 --> 00:12:24.060 align:start position:0% and here we signed a y-coordinate and 00:12:24.060 --> 00:12:29.070 align:start position:0% and here we signed a y-coordinate and this<00:12:25.060> is<00:12:25.270> but<00:12:25.540> parts<00:12:25.960> of<00:12:27.150> signature<00:12:28.150> and<00:12:28.360> this 00:12:29.070 --> 00:12:29.080 align:start position:0% this is but parts of signature and this 00:12:29.080 --> 00:12:31.980 align:start position:0% this is but parts of signature and this is<00:12:29.200> the<00:12:29.380> message<00:12:30.040> that<00:12:30.550> we<00:12:31.120> want<00:12:31.420> to<00:12:31.570> check<00:12:31.930> the 00:12:31.980 --> 00:12:31.990 align:start position:0% is the message that we want to check the 00:12:31.990 --> 00:12:35.610 align:start position:0% is the message that we want to check the signature<00:12:32.710> against<00:12:33.250> right<00:12:33.850> so<00:12:34.390> if<00:12:34.720> it<00:12:34.990> all 00:12:35.610 --> 00:12:35.620 align:start position:0% signature against right so if it all 00:12:35.620 --> 00:12:38.220 align:start position:0% signature against right so if it all gives<00:12:36.040> a<00:12:36.270> calculated<00:12:37.270> goodness 00:12:38.220 --> 00:12:38.230 align:start position:0% gives a calculated goodness 00:12:38.230 --> 00:12:41.490 align:start position:0% gives a calculated goodness run<00:12:38.470> smoothly<00:12:38.980> then<00:12:39.940> your<00:12:40.390> signature<00:12:41.380> was 00:12:41.490 --> 00:12:41.500 align:start position:0% run smoothly then your signature was 00:12:41.500 --> 00:12:50.220 align:start position:0% run smoothly then your signature was basically<00:12:41.950> correct<00:12:42.250> right<00:12:42.940> yeah<00:12:47.940> yeah<00:12:49.230> you 00:12:50.220 --> 00:12:50.230 align:start position:0% basically correct right yeah yeah you 00:12:50.230 --> 00:12:51.900 align:start position:0% basically correct right yeah yeah you say<00:12:50.410> that<00:12:50.620> this<00:12:51.010> kind<00:12:51.220> of<00:12:51.340> fire<00:12:51.520> is<00:12:51.760> something 00:12:51.900 --> 00:12:51.910 align:start position:0% say that this kind of fire is something 00:12:51.910 --> 00:12:59.670 align:start position:0% say that this kind of fire is something for<00:12:52.240> the<00:12:52.330> first<00:12:52.810> time<00:12:56.430> yeah<00:12:57.600> the<00:12:58.600> security<00:12:59.260> is 00:12:59.670 --> 00:12:59.680 align:start position:0% for the first time yeah the security is 00:12:59.680 --> 00:13:04.040 align:start position:0% for the first time yeah the security is not<00:12:59.890> widely<00:13:00.960> researched<00:13:01.960> yet<00:13:02.620> so<00:13:03.010> we<00:13:03.460> will 00:13:04.040 --> 00:13:04.050 align:start position:0% not widely researched yet so we will 00:13:04.050 --> 00:13:06.600 align:start position:0% not widely researched yet so we will generally<00:13:05.050> tend<00:13:05.410> to<00:13:05.470> avoid<00:13:06.040> this<00:13:06.250> because 00:13:06.600 --> 00:13:06.610 align:start position:0% generally tend to avoid this because 00:13:06.610 --> 00:13:10.230 align:start position:0% generally tend to avoid this because it's<00:13:06.760> not<00:13:07.230> the<00:13:08.580> security<00:13:09.580> is<00:13:09.640> not<00:13:09.820> really 00:13:10.230 --> 00:13:10.240 align:start position:0% it's not the security is not really 00:13:10.240 --> 00:13:12.210 align:start position:0% it's not the security is not really proven<00:13:10.600> at<00:13:10.720> the<00:13:10.840> moment<00:13:11.140> but<00:13:11.350> it's<00:13:11.620> not<00:13:11.830> it's 00:13:12.210 --> 00:13:12.220 align:start position:0% proven at the moment but it's not it's 00:13:12.220 --> 00:13:14.520 align:start position:0% proven at the moment but it's not it's not<00:13:12.370> broken<00:13:12.820> it's<00:13:13.120> it's<00:13:13.600> not<00:13:13.960> flow<00:13:14.230> on<00:13:14.410> either 00:13:14.520 --> 00:13:14.530 align:start position:0% not broken it's it's not flow on either 00:13:14.530 --> 00:13:17.520 align:start position:0% not broken it's it's not flow on either so<00:13:15.160> we<00:13:15.310> so<00:13:15.730> people<00:13:16.060> generally<00:13:16.150> tend<00:13:16.570> to<00:13:16.780> avoid 00:13:17.520 --> 00:13:17.530 align:start position:0% so we so people generally tend to avoid 00:13:17.530 --> 00:13:30.429 align:start position:0% so we so people generally tend to avoid it<00:13:17.740> but<00:13:18.400> it's<00:13:18.550> fine<00:13:18.730> for<00:13:18.910> the<00:13:19.030> case<00:13:25.410> today 00:13:30.429 --> 00:13:30.439 align:start position:0% 00:13:30.439 --> 00:13:37.240 align:start position:0% see 00:13:37.240 --> 00:13:37.250 align:start position:0% 00:13:37.250 --> 00:13:43.860 align:start position:0% is<00:13:38.030> there<00:13:38.210> any<00:13:40.540> medicine<00:13:41.540> works<00:13:41.870> pretty<00:13:42.410> good 00:13:43.860 --> 00:13:43.870 align:start position:0% is there any medicine works pretty good 00:13:43.870 --> 00:13:49.660 align:start position:0% is there any medicine works pretty good pretty<00:13:44.870> much<00:13:45.110> yeah<00:13:45.880> that's<00:13:46.880> all<00:13:47.060> right 00:13:49.660 --> 00:13:49.670 align:start position:0% 00:13:49.670 --> 00:13:53.350 align:start position:0% and<00:13:49.940> it's<00:13:50.360> not<00:13:50.960> a<00:13:50.990> school<00:13:51.320> isn't<00:13:51.530> it<00:13:52.360> slow 00:13:53.350 --> 00:13:53.360 align:start position:0% and it's not a school isn't it slow 00:13:53.360 --> 00:13:54.070 align:start position:0% and it's not a school isn't it slow Asians 00:13:54.070 --> 00:13:54.080 align:start position:0% Asians 00:13:54.080 --> 00:13:56.290 align:start position:0% Asians what<00:13:54.350> is<00:13:54.500> the<00:13:54.770> what<00:13:55.130> I<00:13:55.250> intend<00:13:55.610> to<00:13:55.670> be<00:13:55.850> private 00:13:56.290 --> 00:13:56.300 align:start position:0% what is the what I intend to be private 00:13:56.300 --> 00:14:03.790 align:start position:0% what is the what I intend to be private because<00:13:56.870> this<00:13:57.170> is<00:13:57.410> a<00:13:57.560> sobriety<00:13:57.980> kind 00:14:03.790 --> 00:14:03.800 align:start position:0% 00:14:03.800 --> 00:14:07.430 align:start position:0% no<00:14:04.800> in<00:14:05.610> in<00:14:06.060> this<00:14:06.270> we<00:14:06.690> are<00:14:06.720> just<00:14:06.840> trying<00:14:07.140> to 00:14:07.430 --> 00:14:07.440 align:start position:0% no in in this we are just trying to 00:14:07.440 --> 00:14:09.890 align:start position:0% no in in this we are just trying to verify<00:14:07.680> a<00:14:07.950> signature<00:14:08.940> inside<00:14:09.330> is<00:14:09.510> not<00:14:09.660> you're 00:14:09.890 --> 00:14:09.900 align:start position:0% verify a signature inside is not you're 00:14:09.900 --> 00:14:11.660 align:start position:0% verify a signature inside is not you're not<00:14:09.930> trying<00:14:10.260> to<00:14:10.470> make<00:14:10.770> things<00:14:10.950> private<00:14:11.490> in 00:14:11.660 --> 00:14:11.670 align:start position:0% not trying to make things private in 00:14:11.670 --> 00:14:16.970 align:start position:0% not trying to make things private in this<00:14:11.850> circuit<00:14:12.620> yeah<00:14:13.820> yeah<00:14:14.820> because<00:14:15.980> we're 00:14:16.970 --> 00:14:16.980 align:start position:0% this circuit yeah yeah because we're 00:14:16.980 --> 00:14:19.730 align:start position:0% this circuit yeah yeah because we're doing<00:14:17.130> a<00:14:17.520> while<00:14:17.790> verifying<00:14:18.380> Dominic<00:14:19.380> support 00:14:19.730 --> 00:14:19.740 align:start position:0% doing a while verifying Dominic support 00:14:19.740 --> 00:14:23.240 align:start position:0% doing a while verifying Dominic support from<00:14:19.980> for<00:14:20.400> rola<00:14:20.790> we<00:14:21.510> will<00:14:22.230> have<00:14:22.410> to<00:14:22.590> verify<00:14:22.800> if 00:14:23.240 --> 00:14:23.250 align:start position:0% from for rola we will have to verify if 00:14:23.250 --> 00:14:25.730 align:start position:0% from for rola we will have to verify if the<00:14:23.580> if<00:14:24.000> a<00:14:24.120> transactions<00:14:24.690> emitted<00:14:25.260> by<00:14:25.380> a<00:14:25.410> from 00:14:25.730 --> 00:14:25.740 align:start position:0% the if a transactions emitted by a from 00:14:25.740 --> 00:14:34.540 align:start position:0% the if a transactions emitted by a from address<00:14:26.100> is<00:14:26.310> actually<00:14:26.850> signed<00:14:27.360> by<00:14:30.320> yeah<00:14:33.290> so 00:14:34.540 --> 00:14:34.550 align:start position:0% address is actually signed by yeah so 00:14:34.550 --> 00:14:38.540 align:start position:0% address is actually signed by yeah so yeah<00:14:35.550> the<00:14:35.880> next<00:14:36.600> part<00:14:36.780> is<00:14:36.900> like<00:14:37.110> very<00:14:37.980> far<00:14:38.250> like 00:14:38.540 --> 00:14:38.550 align:start position:0% yeah the next part is like very far like 00:14:38.550 --> 00:14:42.440 align:start position:0% yeah the next part is like very far like creating<00:14:39.060> a<00:14:39.470> market<00:14:40.470> route<00:14:40.680> for<00:14:41.550> given<00:14:42.210> leaves 00:14:42.440 --> 00:14:42.450 align:start position:0% creating a market route for given leaves 00:14:42.450 --> 00:14:47.030 align:start position:0% creating a market route for given leaves and<00:14:43.040> yeah<00:14:44.040> so<00:14:44.820> that's<00:14:45.810> so<00:14:45.990> in<00:14:46.080> here<00:14:46.350> we<00:14:46.530> we 00:14:47.030 --> 00:14:47.040 align:start position:0% and yeah so that's so in here we we 00:14:47.040 --> 00:14:49.490 align:start position:0% and yeah so that's so in here we we basically<00:14:47.850> have<00:14:48.390> two<00:14:48.660> or<00:14:48.840> three<00:14:49.050> variables 00:14:49.490 --> 00:14:49.500 align:start position:0% basically have two or three variables 00:14:49.500 --> 00:14:53.590 align:start position:0% basically have two or three variables which<00:14:49.590> like<00:14:49.800> a<00:14:50.010> path<00:14:50.760> to<00:14:50.970> rule<00:14:51.150> this<00:14:51.770> basically 00:14:53.590 --> 00:14:53.600 align:start position:0% which like a path to rule this basically 00:14:53.600 --> 00:14:57.980 align:start position:0% which like a path to rule this basically the<00:14:54.600> leaves<00:14:54.870> in<00:14:55.140> the<00:14:55.170> market<00:14:56.160> aloof<00:14:56.400> right<00:14:56.990> and 00:14:57.980 --> 00:14:57.990 align:start position:0% the leaves in the market aloof right and 00:14:57.990 --> 00:15:01.070 align:start position:0% the leaves in the market aloof right and part<00:14:58.470> 2<00:14:58.680> route<00:14:58.830> poison<00:14:59.460> is<00:14:59.550> basically<00:15:00.080> binary 00:15:01.070 --> 00:15:01.080 align:start position:0% part 2 route poison is basically binary 00:15:01.080 --> 00:15:05.000 align:start position:0% part 2 route poison is basically binary vector<00:15:01.440> so<00:15:01.680> if<00:15:01.800> so<00:15:02.340> if<00:15:02.370> the<00:15:02.550> leaf<00:15:03.110> so<00:15:04.110> let's<00:15:04.860> say 00:15:05.000 --> 00:15:05.010 align:start position:0% vector so if so if the leaf so let's say 00:15:05.010 --> 00:15:08.000 align:start position:0% vector so if so if the leaf so let's say as<00:15:05.280> the<00:15:05.550> reef<00:15:05.760> an<00:15:06.030> index<00:15:06.840> 0<00:15:07.110> in<00:15:07.350> part<00:15:07.680> to<00:15:07.830> route 00:15:08.000 --> 00:15:08.010 align:start position:0% as the reef an index 0 in part to route 00:15:08.010 --> 00:15:11.030 align:start position:0% as the reef an index 0 in part to route so<00:15:08.730> part<00:15:09.330> the<00:15:09.480> root<00:15:09.630> position<00:15:09.870> at<00:15:10.380> index<00:15:10.770> 0 00:15:11.030 --> 00:15:11.040 align:start position:0% so part the root position at index 0 00:15:11.040 --> 00:15:14.030 align:start position:0% so part the root position at index 0 will<00:15:11.430> basically<00:15:11.760> have<00:15:12.150> 0<00:15:12.540> or<00:15:12.570> 1<00:15:12.900> 0<00:15:13.110> means<00:15:13.950> that 00:15:14.030 --> 00:15:14.040 align:start position:0% will basically have 0 or 1 0 means that 00:15:14.040 --> 00:15:16.730 align:start position:0% will basically have 0 or 1 0 means that the<00:15:14.250> leaf<00:15:14.430> is<00:15:14.700> left<00:15:15.120> 1<00:15:15.810> means<00:15:16.080> it<00:15:16.260> it's<00:15:16.560> right 00:15:16.730 --> 00:15:16.740 align:start position:0% the leaf is left 1 means it it's right 00:15:16.740 --> 00:15:21.610 align:start position:0% the leaf is left 1 means it it's right right<00:15:17.610> so<00:15:18.210> we'll<00:15:18.390> see<00:15:18.600> how<00:15:18.780> how<00:15:18.990> that<00:15:19.380> is<00:15:19.680> used 00:15:21.610 --> 00:15:21.620 align:start position:0% right so we'll see how how that is used 00:15:21.620 --> 00:15:27.110 align:start position:0% right so we'll see how how that is used later<00:15:22.850> this<00:15:23.850> output<00:15:24.660> signal<00:15:24.930> so<00:15:25.800> what<00:15:26.610> you<00:15:26.790> see 00:15:27.110 --> 00:15:27.120 align:start position:0% later this output signal so what you see 00:15:27.120 --> 00:15:31.040 align:start position:0% later this output signal so what you see seven<00:15:27.600> basically<00:15:28.200> creates<00:15:29.480> ash<00:15:30.480> if<00:15:30.930> you 00:15:31.040 --> 00:15:31.050 align:start position:0% seven basically creates ash if you 00:15:31.050 --> 00:15:35.810 align:start position:0% seven basically creates ash if you provided<00:15:32.390> inputs<00:15:33.500> the<00:15:34.500> first<00:15:35.040> parameter<00:15:35.430> here 00:15:35.810 --> 00:15:35.820 align:start position:0% provided inputs the first parameter here 00:15:35.820 --> 00:15:37.330 align:start position:0% provided inputs the first parameter here to<00:15:36.090> is<00:15:36.240> like<00:15:36.480> the<00:15:36.660> number<00:15:36.930> of 00:15:37.330 --> 00:15:37.340 align:start position:0% to is like the number of 00:15:37.340 --> 00:15:42.220 align:start position:0% to is like the number of you<00:15:37.520> want<00:15:37.700> to<00:15:37.790> give<00:15:37.970> it<00:15:38.120> right<00:15:38.990> so<00:15:40.360> so<00:15:41.360> yeah<00:15:41.510> so 00:15:42.220 --> 00:15:42.230 align:start position:0% you want to give it right so so yeah so 00:15:42.230 --> 00:15:47.700 align:start position:0% you want to give it right so so yeah so if<00:15:42.560> if<00:15:43.370> but<00:15:43.940> five<00:15:44.390> total<00:15:44.570> poison<00:15:45.080> is<00:15:45.200> zero<00:15:46.570> the 00:15:47.700 --> 00:15:47.710 align:start position:0% if if but five total poison is zero the 00:15:47.710 --> 00:15:52.380 align:start position:0% if if but five total poison is zero the mark<00:15:48.710> on<00:15:48.830> the<00:15:49.310> first<00:15:49.580> input<00:15:49.850> to<00:15:50.330> MC<00:15:50.930> becomes 00:15:52.380 --> 00:15:52.390 align:start position:0% mark on the first input to MC becomes 00:15:52.390 --> 00:15:55.750 align:start position:0% mark on the first input to MC becomes the<00:15:53.390> leaf<00:15:54.080> itself<00:15:54.260> right<00:15:54.680> so<00:15:54.980> this<00:15:55.370> is<00:15:55.550> how<00:15:55.700> the 00:15:55.750 --> 00:15:55.760 align:start position:0% the leaf itself right so this is how the 00:15:55.760 --> 00:16:00.520 align:start position:0% the leaf itself right so this is how the binary<00:15:56.680> factorization<00:15:57.680> was<00:15:58.340> so<00:15:59.120> so<00:15:59.840> if<00:15:59.930> if 00:16:00.520 --> 00:16:00.530 align:start position:0% binary factorization was so so if if 00:16:00.530 --> 00:16:03.610 align:start position:0% binary factorization was so so if if this<00:16:01.310> this<00:16:01.700> thing<00:16:01.970> is<00:16:02.090> zero<00:16:02.360> then<00:16:02.960> the<00:16:03.410> first 00:16:03.610 --> 00:16:03.620 align:start position:0% this this thing is zero then the first 00:16:03.620 --> 00:16:06.850 align:start position:0% this this thing is zero then the first input<00:16:03.890> becomes<00:16:04.220> leaf<00:16:04.610> and<00:16:05.470> because<00:16:06.470> this 00:16:06.850 --> 00:16:06.860 align:start position:0% input becomes leaf and because this 00:16:06.860 --> 00:16:09.070 align:start position:0% input becomes leaf and because this thing<00:16:07.070> is<00:16:07.100> also<00:16:07.430> zero<00:16:07.790> the<00:16:08.420> second<00:16:08.960> input 00:16:09.070 --> 00:16:09.080 align:start position:0% thing is also zero the second input 00:16:09.080 --> 00:16:13.480 align:start position:0% thing is also zero the second input becomes<00:16:09.410> the<00:16:10.690> sibling<00:16:11.690> right<00:16:12.080> and<00:16:12.590> if<00:16:12.860> if<00:16:13.280> it's 00:16:13.480 --> 00:16:13.490 align:start position:0% becomes the sibling right and if if it's 00:16:13.490 --> 00:16:18.520 align:start position:0% becomes the sibling right and if if it's one<00:16:13.700> then<00:16:15.130> the<00:16:16.130> first<00:16:16.580> input<00:16:17.120> becomes<00:16:17.300> but<00:16:18.080> in 00:16:18.520 --> 00:16:18.530 align:start position:0% one then the first input becomes but in 00:16:18.530 --> 00:16:21.880 align:start position:0% one then the first input becomes but in the<00:16:18.950> leaf<00:16:19.400> and<00:16:19.700> the<00:16:20.510> second<00:16:21.470> input<00:16:21.590> becomes 00:16:21.880 --> 00:16:21.890 align:start position:0% the leaf and the second input becomes 00:16:21.890 --> 00:16:24.160 align:start position:0% the leaf and the second input becomes the<00:16:22.250> actual<00:16:22.700> leaves<00:16:23.030> that<00:16:23.510> we<00:16:23.660> want<00:16:23.870> to<00:16:23.960> prove 00:16:24.160 --> 00:16:24.170 align:start position:0% the actual leaves that we want to prove 00:16:24.170 --> 00:16:28.660 align:start position:0% the actual leaves that we want to prove the<00:16:24.970> path<00:16:25.970> path<00:16:26.270> for<00:16:26.510> like<00:16:27.400> does<00:16:28.400> that<00:16:28.520> make 00:16:28.660 --> 00:16:28.670 align:start position:0% the path path for like does that make 00:16:28.670 --> 00:16:31.950 align:start position:0% the path path for like does that make sense 00:16:31.950 --> 00:16:31.960 align:start position:0% 00:16:31.960 --> 00:16:35.740 align:start position:0% so<00:16:32.960> we<00:16:33.110> then<00:16:33.560> then<00:16:34.220> we<00:16:34.370> basically<00:16:34.940> just<00:16:35.330> do<00:16:35.600> the 00:16:35.740 --> 00:16:35.750 align:start position:0% so we then then we basically just do the 00:16:35.750 --> 00:16:39.550 align:start position:0% so we then then we basically just do the same<00:16:36.110> thing<00:16:36.380> but<00:16:36.620> over<00:16:37.460> a<00:16:37.490> loop<00:16:37.760> right<00:16:38.690> and 00:16:39.550 --> 00:16:39.560 align:start position:0% same thing but over a loop right and 00:16:39.560 --> 00:16:41.860 align:start position:0% same thing but over a loop right and like<00:16:39.860> I<00:16:40.070> can<00:16:40.400> just<00:16:40.550> basically<00:16:40.880> copy<00:16:41.570> paste 00:16:41.860 --> 00:16:41.870 align:start position:0% like I can just basically copy paste 00:16:41.870 --> 00:16:44.980 align:start position:0% like I can just basically copy paste this<00:16:42.290> part<00:16:42.590> over<00:16:42.770> here<00:16:42.860> and<00:16:43.390> as<00:16:44.390> soon<00:16:44.660> as<00:16:44.810> we 00:16:44.980 --> 00:16:44.990 align:start position:0% this part over here and as soon as we 00:16:44.990 --> 00:16:49.330 align:start position:0% this part over here and as soon as we have<00:16:45.290> filled<00:16:45.590> all<00:16:45.740> the<00:16:46.810> other<00:16:47.810> inputs<00:16:48.440> if<00:16:49.100> we 00:16:49.330 --> 00:16:49.340 align:start position:0% have filled all the other inputs if we 00:16:49.340 --> 00:16:53.410 align:start position:0% have filled all the other inputs if we if<00:16:49.970> we<00:16:50.000> do<00:16:50.950> maca<00:16:51.950> root<00:16:52.100> dot<00:16:52.580> out<00:16:52.820> which<00:16:53.270> is 00:16:53.410 --> 00:16:53.420 align:start position:0% if we do maca root dot out which is 00:16:53.420 --> 00:16:57.340 align:start position:0% if we do maca root dot out which is basically<00:16:54.100> this<00:16:55.100> this<00:16:55.430> template<00:16:55.940> dot<00:16:56.480> out<00:16:56.720> so 00:16:57.340 --> 00:16:57.350 align:start position:0% basically this this template dot out so 00:16:57.350 --> 00:16:59.650 align:start position:0% basically this this template dot out so it<00:16:57.440> basically<00:16:57.620> gives<00:16:58.190> us<00:16:58.700> the<00:16:59.030> hash<00:16:59.210> of<00:16:59.450> the 00:16:59.650 --> 00:16:59.660 align:start position:0% it basically gives us the hash of the 00:16:59.660 --> 00:17:03.160 align:start position:0% it basically gives us the hash of the leaf<00:17:00.380> right<00:17:00.650> so<00:17:01.570> whatever<00:17:02.570> we<00:17:02.750> have<00:17:02.780> passed 00:17:03.160 --> 00:17:03.170 align:start position:0% leaf right so whatever we have passed 00:17:03.170 --> 00:17:05.650 align:start position:0% leaf right so whatever we have passed passed<00:17:03.530> over<00:17:03.830> here<00:17:04.040> doing<00:17:04.340> not<00:17:04.610> out<00:17:04.850> over<00:17:05.510> it 00:17:05.650 --> 00:17:05.660 align:start position:0% passed over here doing not out over it 00:17:05.660 --> 00:17:08.199 align:start position:0% passed over here doing not out over it gives<00:17:06.140> us<00:17:06.320> a<00:17:06.440> flash<00:17:06.650> so<00:17:07.070> if<00:17:07.160> you<00:17:07.250> give<00:17:07.459> like<00:17:07.640> two 00:17:08.199 --> 00:17:08.209 align:start position:0% gives us a flash so if you give like two 00:17:08.209 --> 00:17:10.510 align:start position:0% gives us a flash so if you give like two and<00:17:08.420> three<00:17:08.480> dot<00:17:09.080> out<00:17:09.260> gives<00:17:09.830> us<00:17:09.980> a<00:17:10.070> hash<00:17:10.280> of 00:17:10.510 --> 00:17:10.520 align:start position:0% and three dot out gives us a hash of 00:17:10.520 --> 00:17:13.300 align:start position:0% and three dot out gives us a hash of those<00:17:11.000> three<00:17:11.180> inputs<00:17:11.450> right<00:17:12.230> so<00:17:12.830> basically 00:17:13.300 --> 00:17:13.310 align:start position:0% those three inputs right so basically 00:17:13.310 --> 00:17:15.699 align:start position:0% those three inputs right so basically used<00:17:13.550> to<00:17:13.730> create<00:17:13.970> hashes<00:17:14.450> of<00:17:14.570> leaves<00:17:14.840> so<00:17:15.680> that 00:17:15.699 --> 00:17:15.709 align:start position:0% used to create hashes of leaves so that 00:17:15.709 --> 00:17:17.130 align:start position:0% used to create hashes of leaves so that we<00:17:15.920> can<00:17:16.070> get<00:17:16.220> them<00:17:16.340> up<00:17:16.490> the<00:17:16.640> tree 00:17:17.130 --> 00:17:17.140 align:start position:0% we can get them up the tree 00:17:17.140 --> 00:17:19.270 align:start position:0% we can get them up the tree [Music] 00:17:19.270 --> 00:17:19.280 align:start position:0% [Music] 00:17:19.280 --> 00:17:22.420 align:start position:0% [Music] yeah<00:17:19.910> and<00:17:20.319> this<00:17:21.319> part<00:17:21.620> is<00:17:21.740> taking<00:17:22.280> the 00:17:22.420 --> 00:17:22.430 align:start position:0% yeah and this part is taking the 00:17:22.430 --> 00:17:25.000 align:start position:0% yeah and this part is taking the existence<00:17:22.819> of<00:17:22.939> a<00:17:23.089> leaf<00:17:23.329> in<00:17:23.540> a<00:17:23.569> tree<00:17:23.810> it's<00:17:24.350> it's 00:17:25.000 --> 00:17:25.010 align:start position:0% existence of a leaf in a tree it's it's 00:17:25.010 --> 00:17:28.150 align:start position:0% existence of a leaf in a tree it's it's it's<00:17:25.610> also<00:17:25.760> pretty<00:17:26.000> pretty<00:17:26.870> basic<00:17:27.110> we<00:17:27.920> just 00:17:28.150 --> 00:17:28.160 align:start position:0% it's also pretty pretty basic we just 00:17:28.160 --> 00:17:32.440 align:start position:0% it's also pretty pretty basic we just like<00:17:28.420> take<00:17:29.420> the<00:17:29.630> paths<00:17:30.100> and<00:17:31.100> we<00:17:31.580> assign 00:17:32.440 --> 00:17:32.450 align:start position:0% like take the paths and we assign 00:17:32.450 --> 00:17:35.460 align:start position:0% like take the paths and we assign elements<00:17:33.260> like<00:17:33.890> we<00:17:34.040> did<00:17:34.220> over<00:17:34.490> here 00:17:35.460 --> 00:17:35.470 align:start position:0% elements like we did over here 00:17:35.470 --> 00:17:40.240 align:start position:0% elements like we did over here Ohio<00:17:36.470> on<00:17:37.300> this<00:17:38.300> but<00:17:38.660> basically<00:17:39.320> just<00:17:39.680> as<00:17:39.890> of<00:17:40.070> if 00:17:40.240 --> 00:17:40.250 align:start position:0% Ohio on this but basically just as of if 00:17:40.250 --> 00:17:44.110 align:start position:0% Ohio on this but basically just as of if the<00:17:40.550> DX<00:17:41.210> road<00:17:41.540> that<00:17:41.780> we<00:17:41.990> have<00:17:42.020> given<00:17:42.910> if<00:17:43.910> the 00:17:44.110 --> 00:17:44.120 align:start position:0% the DX road that we have given if the 00:17:44.120 --> 00:17:47.320 align:start position:0% the DX road that we have given if the route<00:17:44.930> given<00:17:45.290> over<00:17:45.500> here<00:17:45.700> much<00:17:46.700> is<00:17:46.910> the<00:17:47.120> route 00:17:47.320 --> 00:17:47.330 align:start position:0% route given over here much is the route 00:17:47.330 --> 00:17:53.290 align:start position:0% route given over here much is the route that<00:17:47.570> we<00:17:47.990> have<00:17:48.590> just<00:17:49.010> created<00:17:49.160> inside<00:17:49.700> the 00:17:53.290 --> 00:17:53.300 align:start position:0% 00:17:53.300 --> 00:17:57.570 align:start position:0% [Music] 00:17:57.570 --> 00:17:57.580 align:start position:0% [Music] 00:17:57.580 --> 00:17:59.650 align:start position:0% [Music] this<00:17:58.580> was<00:17:58.790> basically<00:17:58.940> designed<00:17:59.480> as<00:17:59.630> a 00:17:59.650 --> 00:17:59.660 align:start position:0% this was basically designed as a 00:17:59.660 --> 00:18:03.670 align:start position:0% this was basically designed as a workshop<00:18:00.200> so<00:18:00.650> because<00:18:01.640> of<00:18:01.790> bad<00:18:02.120> intentions 00:18:03.670 --> 00:18:03.680 align:start position:0% workshop so because of bad intentions 00:18:03.680 --> 00:18:07.360 align:start position:0% workshop so because of bad intentions try<00:18:04.640> to<00:18:04.700> skip<00:18:05.060> it<00:18:05.210> but<00:18:05.420> so<00:18:06.230> so<00:18:06.800> three<00:18:07.040> people 00:18:07.360 --> 00:18:07.370 align:start position:0% try to skip it but so so three people 00:18:07.370 --> 00:18:10.380 align:start position:0% try to skip it but so so three people this<00:18:07.490> we<00:18:07.640> had<00:18:07.910> to<00:18:08.120> enter<00:18:09.050> this<00:18:09.200> values<00:18:09.560> but<00:18:09.950> I 00:18:10.380 --> 00:18:10.390 align:start position:0% this we had to enter this values but I 00:18:10.390 --> 00:18:17.409 align:start position:0% this we had to enter this values but I show<00:18:11.390> you<00:18:11.420> this<00:18:11.600> now<00:18:11.810> circuit<00:18:12.230> over<00:18:12.440> here 00:18:17.409 --> 00:18:17.419 align:start position:0% 00:18:17.419 --> 00:18:23.380 align:start position:0% so<00:18:18.320> yeah<00:18:19.119> they've<00:18:20.119> got<00:18:20.299> a<00:18:20.509> and<00:18:21.169> you<00:18:21.320> can<00:18:22.219> buy 00:18:23.380 --> 00:18:23.390 align:start position:0% so yeah they've got a and you can buy 00:18:23.390 --> 00:18:26.710 align:start position:0% so yeah they've got a and you can buy [Music] 00:18:26.710 --> 00:18:26.720 align:start position:0% 00:18:26.720 --> 00:18:35.430 align:start position:0% yeah<00:18:31.420> so<00:18:32.420> just<00:18:32.810> to<00:18:32.960> show<00:18:33.740> you<00:18:34.070> the<00:18:34.420> circuit 00:18:35.430 --> 00:18:35.440 align:start position:0% yeah so just to show you the circuit 00:18:35.440 --> 00:18:38.080 align:start position:0% yeah so just to show you the circuit whatever<00:18:36.440> once<00:18:36.920> was<00:18:37.220> was<00:18:37.550> missing<00:18:37.940> is 00:18:38.080 --> 00:18:38.090 align:start position:0% whatever once was was missing is 00:18:38.090 --> 00:18:40.960 align:start position:0% whatever once was was missing is present-day<00:18:38.570> now<00:18:38.810> in<00:18:39.740> in<00:18:40.370> this<00:18:40.580> fight 00:18:40.960 --> 00:18:40.970 align:start position:0% present-day now in in this fight 00:18:40.970 --> 00:18:45.400 align:start position:0% present-day now in in this fight it's<00:18:41.690> since<00:18:42.380> present<00:18:42.800> not<00:18:42.920> get<00:18:43.340> up<00:18:43.490> I'll<00:18:44.410> give 00:18:45.400 --> 00:18:45.410 align:start position:0% it's since present not get up I'll give 00:18:45.410 --> 00:18:51.340 align:start position:0% it's since present not get up I'll give up<00:18:45.560> the<00:18:45.740> link<00:18:45.950> you<00:18:46.340> know<00:18:46.430> I<00:18:49.660> so<00:18:50.660> it<00:18:51.170> does 00:18:51.340 --> 00:18:51.350 align:start position:0% up the link you know I so it does 00:18:51.350 --> 00:18:54.370 align:start position:0% up the link you know I so it does samples<00:18:52.130> sockets<00:18:52.910> are<00:18:53.030> present<00:18:53.360> here<00:18:53.510> right 00:18:54.370 --> 00:18:54.380 align:start position:0% samples sockets are present here right 00:18:54.380 --> 00:19:01.860 align:start position:0% samples sockets are present here right so<00:18:54.640> whatever<00:18:55.640> was<00:18:55.850> missing<00:18:56.210> over<00:18:56.330> there<00:18:56.600> is 00:19:01.860 --> 00:19:01.870 align:start position:0% 00:19:01.870 --> 00:19:09.220 align:start position:0% yes<00:19:02.870> so<00:19:05.980> so<00:19:06.980> I'm<00:19:07.940> just<00:19:08.120> going<00:19:08.570> to<00:19:08.660> do<00:19:08.840> how 00:19:09.220 --> 00:19:09.230 align:start position:0% yes so so I'm just going to do how 00:19:09.230 --> 00:19:11.530 align:start position:0% yes so so I'm just going to do how deposits<00:19:09.980> work<00:19:10.190> how<00:19:10.550> we<00:19:10.610> drove<00:19:11.000> up<00:19:11.210> in<00:19:11.270> a 00:19:11.530 --> 00:19:11.540 align:start position:0% deposits work how we drove up in a 00:19:11.540 --> 00:19:16.420 align:start position:0% deposits work how we drove up in a run-up<00:19:12.530> chain<00:19:12.740> right<00:19:12.950> so<00:19:13.930> basically<00:19:15.430> operator 00:19:16.420 --> 00:19:16.430 align:start position:0% run-up chain right so basically operator 00:19:16.430 --> 00:19:21.850 align:start position:0% run-up chain right so basically operator it's<00:19:17.030> all<00:19:17.240> third<00:19:17.420> transaction<00:19:17.930> and<00:19:20.860> like 00:19:21.850 --> 00:19:21.860 align:start position:0% it's all third transaction and like 00:19:21.860 --> 00:19:24.340 align:start position:0% it's all third transaction and like let's<00:19:22.790> say<00:19:22.970> a<00:19:23.000> snack<00:19:23.300> that's<00:19:23.600> supposed<00:19:24.140> to<00:19:24.200> be 00:19:24.340 --> 00:19:24.350 align:start position:0% let's say a snack that's supposed to be 00:19:24.350 --> 00:19:26.590 align:start position:0% let's say a snack that's supposed to be up<00:19:24.440> in<00:19:24.650> international<00:19:25.520> right<00:19:25.670> so<00:19:26.360> the 00:19:26.590 --> 00:19:26.600 align:start position:0% up in international right so the 00:19:26.600 --> 00:19:29.380 align:start position:0% up in international right so the operator<00:19:27.230> if<00:19:28.130> he<00:19:28.310> if<00:19:28.550> he<00:19:28.580> has<00:19:28.820> 20<00:19:29.090> run 00:19:29.380 --> 00:19:29.390 align:start position:0% operator if he if he has 20 run 00:19:29.390 --> 00:19:31.120 align:start position:0% operator if he if he has 20 run excellence<00:19:29.720> he<00:19:29.840> picks<00:19:30.170> up<00:19:30.320> top<00:19:30.590> docked<00:19:30.920> in 00:19:31.120 --> 00:19:31.130 align:start position:0% excellence he picks up top docked in 00:19:31.130 --> 00:19:34.630 align:start position:0% excellence he picks up top docked in according<00:19:32.000> to<00:19:32.120> the<00:19:32.180> correct<00:19:32.870> nuns<00:19:33.680> and<00:19:33.950> he 00:19:34.630 --> 00:19:34.640 align:start position:0% according to the correct nuns and he 00:19:34.640 --> 00:19:38.260 align:start position:0% according to the correct nuns and he provides<00:19:35.480> it<00:19:35.600> to<00:19:35.660> the<00:19:35.930> snack<00:19:36.710> circuit<00:19:37.130> and<00:19:37.520> we 00:19:38.260 --> 00:19:38.270 align:start position:0% provides it to the snack circuit and we 00:19:38.270 --> 00:19:41.560 align:start position:0% provides it to the snack circuit and we go<00:19:38.930> from<00:19:39.140> Route<00:19:39.410> one<00:19:39.650> the<00:19:40.130> route<00:19:40.340> and<00:19:40.850> we 00:19:41.560 --> 00:19:41.570 align:start position:0% go from Route one the route and we 00:19:41.570 --> 00:19:43.900 align:start position:0% go from Route one the route and we submit<00:19:42.380> all<00:19:42.590> the<00:19:42.770> transactions<00:19:43.340> and<00:19:43.550> the 00:19:43.900 --> 00:19:43.910 align:start position:0% submit all the transactions and the 00:19:43.910 --> 00:19:46.990 align:start position:0% submit all the transactions and the South<00:19:44.150> broken<00:19:44.540> chain<00:19:44.780> so<00:19:45.470> yeah<00:19:46.040> the<00:19:46.370> co-state 00:19:46.990 --> 00:19:47.000 align:start position:0% South broken chain so yeah the co-state 00:19:47.000 --> 00:19:52.030 align:start position:0% South broken chain so yeah the co-state the<00:19:47.810> transitions<00:19:48.290> work<00:19:48.530> first<00:19:48.830> off<00:19:49.090> for<00:19:51.040> so 00:19:52.030 --> 00:19:52.040 align:start position:0% the transitions work first off for so 00:19:52.040 --> 00:19:56.010 align:start position:0% the transitions work first off for so the<00:19:52.190> account<00:19:52.700> is<00:19:52.970> we<00:19:53.570> basically<00:19:53.900> like<00:19:54.170> this<00:19:54.320> of 00:19:56.010 --> 00:19:56.020 align:start position:0% the account is we basically like this of 00:19:56.020 --> 00:19:58.690 align:start position:0% the account is we basically like this of the<00:19:57.020> x-coordinate<00:19:57.560> of<00:19:57.650> the<00:19:57.770> public<00:19:58.100> the 00:19:58.690 --> 00:19:58.700 align:start position:0% the x-coordinate of the public the 00:19:58.700 --> 00:20:01.360 align:start position:0% the x-coordinate of the public the y-coordinate<00:19:59.330> the<00:19:59.600> balance<00:20:00.250> non-standard<00:20:01.250> to 00:20:01.360 --> 00:20:01.370 align:start position:0% y-coordinate the balance non-standard to 00:20:01.370 --> 00:20:04.630 align:start position:0% y-coordinate the balance non-standard to indict<00:20:01.700> right<00:20:02.360> and<00:20:02.860> the<00:20:03.860> leaf<00:20:04.040> is<00:20:04.310> basically 00:20:04.630 --> 00:20:04.640 align:start position:0% indict right and the leaf is basically 00:20:04.640 --> 00:20:09.640 align:start position:0% indict right and the leaf is basically the<00:20:04.850> hash<00:20:05.030> of<00:20:05.300> all<00:20:06.140> of<00:20:06.260> these<00:20:08.350> but<00:20:09.350> for<00:20:09.500> the 00:20:09.640 --> 00:20:09.650 align:start position:0% the hash of all of these but for the 00:20:09.650 --> 00:20:11.380 align:start position:0% the hash of all of these but for the walk<00:20:10.010> so<00:20:10.190> we're<00:20:10.370> just<00:20:10.430> going<00:20:10.730> to<00:20:10.820> do<00:20:11.060> back<00:20:11.330> in 00:20:11.380 --> 00:20:11.390 align:start position:0% walk so we're just going to do back in 00:20:11.390 --> 00:20:14.580 align:start position:0% walk so we're just going to do back in slowly 00:20:14.580 --> 00:20:14.590 align:start position:0% 00:20:14.590 --> 00:20:16.680 align:start position:0% but<00:20:14.769> we<00:20:14.919> can<00:20:15.100> enable<00:20:15.789> of<00:20:16.210> gene<00:20:16.419> we<00:20:16.570> can 00:20:16.680 --> 00:20:16.690 align:start position:0% but we can enable of gene we can 00:20:16.690 --> 00:20:18.989 align:start position:0% but we can enable of gene we can actually<00:20:17.080> have<00:20:17.200> multiple<00:20:17.440> tokens<00:20:17.999> trading 00:20:18.989 --> 00:20:18.999 align:start position:0% actually have multiple tokens trading 00:20:18.999 --> 00:20:21.899 align:start position:0% actually have multiple tokens trading this<00:20:20.100> simultaneously<00:20:21.100> and<00:20:21.249> the<00:20:21.399> operator<00:20:21.730> can 00:20:21.899 --> 00:20:21.909 align:start position:0% this simultaneously and the operator can 00:20:21.909 --> 00:20:29.480 align:start position:0% this simultaneously and the operator can accept<00:20:22.360> fries<00:20:22.659> in<00:20:22.899> any<00:20:23.740> or<00:20:24.009> all<00:20:24.279> of<00:20:24.610> this<00:20:24.809> right 00:20:29.480 --> 00:20:29.490 align:start position:0% 00:20:29.490 --> 00:20:35.279 align:start position:0% so<00:20:30.690> this<00:20:31.690> is<00:20:31.840> how<00:20:32.039> come<00:20:33.070> looks<00:20:33.820> like<00:20:34.029> since<00:20:34.509> of 00:20:35.279 --> 00:20:35.289 align:start position:0% so this is how come looks like since of 00:20:35.289 --> 00:20:38.039 align:start position:0% so this is how come looks like since of Kiev<00:20:35.649> and<00:20:35.799> on<00:20:36.159> satellite<00:20:36.519> and<00:20:36.700> the<00:20:37.659> balance 00:20:38.039 --> 00:20:38.049 align:start position:0% Kiev and on satellite and the balance 00:20:38.049 --> 00:20:42.360 align:start position:0% Kiev and on satellite and the balance history<00:20:38.409> is<00:20:38.559> this<00:20:39.720> so<00:20:40.720> we<00:20:41.080> change<00:20:41.919> the<00:20:42.100> account 00:20:42.360 --> 00:20:42.370 align:start position:0% history is this so we change the account 00:20:42.370 --> 00:20:45.389 align:start position:0% history is this so we change the account route<00:20:42.700> every<00:20:43.360> time<00:20:43.389> to<00:20:44.169> be<00:20:44.320> somewhat<00:20:45.100> a<00:20:45.159> batch 00:20:45.389 --> 00:20:45.399 align:start position:0% route every time to be somewhat a batch 00:20:45.399 --> 00:20:52.019 align:start position:0% route every time to be somewhat a batch on<00:20:45.730> sale<00:20:49.409> yeah<00:20:50.440> and<00:20:50.649> in<00:20:51.009> a<00:20:51.070> transaction<00:20:51.700> we 00:20:52.019 --> 00:20:52.029 align:start position:0% on sale yeah and in a transaction we 00:20:52.029 --> 00:20:54.659 align:start position:0% on sale yeah and in a transaction we have<00:20:52.210> from<00:20:52.539> we<00:20:53.019> have<00:20:53.110> from<00:20:53.350> from<00:20:53.649> index<00:20:54.070> which 00:20:54.659 --> 00:20:54.669 align:start position:0% have from we have from from index which 00:20:54.669 --> 00:20:57.799 align:start position:0% have from we have from from index which is<00:20:54.759> like<00:20:54.909> the<00:20:55.090> leaf<00:20:55.299> index<00:20:55.869> in<00:20:56.080> the<00:20:56.409> local<00:20:57.249> tree 00:20:57.799 --> 00:20:57.809 align:start position:0% is like the leaf index in the local tree 00:20:57.809 --> 00:21:06.499 align:start position:0% is like the leaf index in the local tree and<00:20:58.809> we<00:20:58.990> have<00:20:59.519> to<00:21:00.519> waitress<00:21:03.360> open<00:21:04.360> time<00:21:05.039> yeah 00:21:06.499 --> 00:21:06.509 align:start position:0% and we have to waitress open time yeah 00:21:06.509 --> 00:21:13.139 align:start position:0% and we have to waitress open time yeah so<00:21:07.509> it<00:21:08.409> was<00:21:08.619> it's<00:21:08.799> too<00:21:10.289> like<00:21:11.490> they're<00:21:12.490> pretty 00:21:13.139 --> 00:21:13.149 align:start position:0% so it was it's too like they're pretty 00:21:13.149 --> 00:21:16.320 align:start position:0% so it was it's too like they're pretty interesting<00:21:13.720> so<00:21:14.499> what<00:21:15.369> we<00:21:15.519> do<00:21:15.639> here<00:21:15.940> is<00:21:16.090> the 00:21:16.320 --> 00:21:16.330 align:start position:0% interesting so what we do here is the 00:21:16.330 --> 00:21:19.710 align:start position:0% interesting so what we do here is the deposits<00:21:17.049> happen<00:21:17.379> totally<00:21:18.039> on<00:21:18.159> chain<00:21:18.460> 5<00:21:18.669> so<00:21:19.269> as 00:21:19.710 --> 00:21:19.720 align:start position:0% deposits happen totally on chain 5 so as 00:21:19.720 --> 00:21:23.100 align:start position:0% deposits happen totally on chain 5 so as soon<00:21:19.869> as<00:21:19.960> someone<00:21:20.289> or<00:21:20.860> deposits<00:21:21.749> it's<00:21:22.749> a<00:21:22.869> one 00:21:23.100 --> 00:21:23.110 align:start position:0% soon as someone or deposits it's a one 00:21:23.110 --> 00:21:26.549 align:start position:0% soon as someone or deposits it's a one one<00:21:23.409> eat<00:21:23.679> it's<00:21:24.490> pushed<00:21:24.940> to<00:21:25.090> and<00:21:25.240> I<00:21:25.330> as<00:21:26.259> soon<00:21:26.440> as 00:21:26.549 --> 00:21:26.559 align:start position:0% one eat it's pushed to and I as soon as 00:21:26.559 --> 00:21:29.399 align:start position:0% one eat it's pushed to and I as soon as someone<00:21:26.799> deposits<00:21:27.869> someone<00:21:28.869> does<00:21:28.990> the<00:21:29.049> second 00:21:29.399 --> 00:21:29.409 align:start position:0% someone deposits someone does the second 00:21:29.409 --> 00:21:32.549 align:start position:0% someone deposits someone does the second deposit<00:21:29.799> what<00:21:30.549> the<00:21:30.639> deposits<00:21:31.119> are<00:21:31.559> together 00:21:32.549 --> 00:21:32.559 align:start position:0% deposit what the deposits are together 00:21:32.559 --> 00:21:36.659 align:start position:0% deposit what the deposits are together and<00:21:33.039> they<00:21:33.490> are<00:21:33.960> like<00:21:34.960> a<00:21:35.470> tree<00:21:36.100> straight<00:21:36.460> route 00:21:36.659 --> 00:21:36.669 align:start position:0% and they are like a tree straight route 00:21:36.669 --> 00:21:39.539 align:start position:0% and they are like a tree straight route right<00:21:37.330> so<00:21:37.840> yeah<00:21:38.200> this<00:21:38.409> the<00:21:38.559> first<00:21:38.830> first<00:21:39.249> first 00:21:39.539 --> 00:21:39.549 align:start position:0% right so yeah this the first first first 00:21:39.549 --> 00:21:41.940 align:start position:0% right so yeah this the first first first deposit<00:21:39.999> the<00:21:40.240> second<00:21:40.509> deposit<00:21:40.929> and<00:21:41.139> it's<00:21:41.799> the 00:21:41.940 --> 00:21:41.950 align:start position:0% deposit the second deposit and it's the 00:21:41.950 --> 00:21:44.190 align:start position:0% deposit the second deposit and it's the hash<00:21:42.210> then<00:21:43.210> as<00:21:43.389> soon<00:21:43.539> as<00:21:43.629> we<00:21:43.749> have<00:21:43.869> a<00:21:43.899> third 00:21:44.190 --> 00:21:44.200 align:start position:0% hash then as soon as we have a third 00:21:44.200 --> 00:21:47.220 align:start position:0% hash then as soon as we have a third deposit<00:21:45.059> then<00:21:46.059> you<00:21:46.179> paid<00:21:46.389> for<00:21:46.629> a<00:21:46.659> deposit 00:21:47.220 --> 00:21:47.230 align:start position:0% deposit then you paid for a deposit 00:21:47.230 --> 00:21:49.619 align:start position:0% deposit then you paid for a deposit affluence<00:21:48.190> is<00:21:48.340> as<00:21:48.700> it's<00:21:48.940> done<00:21:49.119> to<00:21:49.269> be<00:21:49.360> create<00:21:49.600> a 00:21:49.619 --> 00:21:49.629 align:start position:0% affluence is as it's done to be create a 00:21:49.629 --> 00:21:52.139 align:start position:0% affluence is as it's done to be create a hash<00:21:49.869> and<00:21:50.110> we<00:21:50.379> combine<00:21:50.950> them<00:21:51.100> together<00:21:51.249> so 00:21:52.139 --> 00:21:52.149 align:start position:0% hash and we combine them together so 00:21:52.149 --> 00:21:54.539 align:start position:0% hash and we combine them together so what<00:21:52.299> what<00:21:52.960> what<00:21:53.409> what<00:21:53.950> we<00:21:54.070> can<00:21:54.220> do<00:21:54.399> is 00:21:54.539 --> 00:21:54.549 align:start position:0% what what what what we can do is 00:21:54.549 --> 00:21:57.779 align:start position:0% what what what what we can do is whenever<00:21:55.389> we<00:21:55.570> want<00:21:56.379> to<00:21:56.529> include<00:21:56.950> the<00:21:57.249> deposits 00:21:57.779 --> 00:21:57.789 align:start position:0% whenever we want to include the deposits 00:21:57.789 --> 00:22:01.470 align:start position:0% whenever we want to include the deposits in<00:21:57.970> the<00:21:58.330> role<00:21:59.139> of<00:21:59.230> chain<00:21:59.470> we<00:22:00.190> just<00:22:00.429> pick<00:22:01.090> up<00:22:01.269> the 00:22:01.470 --> 00:22:01.480 align:start position:0% in the role of chain we just pick up the 00:22:01.480 --> 00:22:04.379 align:start position:0% in the role of chain we just pick up the latest<00:22:02.169> food<00:22:02.559> and<00:22:02.830> we<00:22:03.279> attach<00:22:03.850> it<00:22:03.879> to<00:22:04.210> the 00:22:04.379 --> 00:22:04.389 align:start position:0% latest food and we attach it to the 00:22:04.389 --> 00:22:07.230 align:start position:0% latest food and we attach it to the existing<00:22:04.869> balance<00:22:05.230> stream<00:22:05.590> so<00:22:06.549> so<00:22:06.879> we<00:22:06.999> create 00:22:07.230 --> 00:22:07.240 align:start position:0% existing balance stream so so we create 00:22:07.240 --> 00:22:10.859 align:start position:0% existing balance stream so so we create a<00:22:07.330> volume<00:22:07.480> to<00:22:08.019> suffering<00:22:08.799> and<00:22:09.480> snap<00:22:10.480> proof<00:22:10.720> is 00:22:10.859 --> 00:22:10.869 align:start position:0% a volume to suffering and snap proof is 00:22:10.869 --> 00:22:13.409 align:start position:0% a volume to suffering and snap proof is created<00:22:11.619> which<00:22:12.190> which<00:22:12.669> basically<00:22:13.240> just 00:22:13.409 --> 00:22:13.419 align:start position:0% created which which basically just 00:22:13.419 --> 00:22:16.180 align:start position:0% created which which basically just proves<00:22:13.960> that<00:22:14.200> this<00:22:15.190> is 00:22:16.180 --> 00:22:16.190 align:start position:0% proves that this is 00:22:16.190 --> 00:22:20.379 align:start position:0% proves that this is sleeve<00:22:16.429> was<00:22:17.059> empty<00:22:17.509> and<00:22:18.129> the<00:22:19.210> depository<00:22:20.210> has 00:22:20.379 --> 00:22:20.389 align:start position:0% sleeve was empty and the depository has 00:22:20.389 --> 00:22:27.600 align:start position:0% sleeve was empty and the depository has been<00:22:20.539> inserted<00:22:20.840> over<00:22:21.200> here<00:22:21.850> yeah<00:22:25.269> yeah<00:22:26.269> so 00:22:27.600 --> 00:22:27.610 align:start position:0% been inserted over here yeah yeah so 00:22:27.610 --> 00:22:30.369 align:start position:0% been inserted over here yeah yeah so this<00:22:28.610> was<00:22:28.850> the<00:22:29.000> holder<00:22:29.360> downstream<00:22:29.809> and<00:22:30.049> now 00:22:30.369 --> 00:22:30.379 align:start position:0% this was the holder downstream and now 00:22:30.379 --> 00:22:32.799 align:start position:0% this was the holder downstream and now the<00:22:30.440> new<00:22:30.710> mobility<00:22:30.980> comes<00:22:31.549> of<00:22:32.090> that<00:22:32.120> that 00:22:32.799 --> 00:22:32.809 align:start position:0% the new mobility comes of that that 00:22:32.809 --> 00:22:35.919 align:start position:0% the new mobility comes of that that whole<00:22:32.990> thing<00:22:33.230> the<00:22:34.190> deposit<00:22:35.059> Ruth<00:22:35.240> gets<00:22:35.720> place 00:22:35.919 --> 00:22:35.929 align:start position:0% whole thing the deposit Ruth gets place 00:22:35.929 --> 00:22:37.960 align:start position:0% whole thing the deposit Ruth gets place no<00:22:36.110> idea 00:22:37.960 --> 00:22:37.970 align:start position:0% no idea 00:22:37.970 --> 00:22:41.030 align:start position:0% no idea [Music] 00:22:41.030 --> 00:22:41.040 align:start position:0% [Music] 00:22:41.040 --> 00:22:44.540 align:start position:0% [Music] so<00:22:41.720> we're<00:22:42.720> doing<00:22:42.840> all<00:22:43.110> the<00:22:43.860> drawing<00:22:44.100> is<00:22:44.220> also 00:22:44.540 --> 00:22:44.550 align:start position:0% so we're doing all the drawing is also 00:22:44.550 --> 00:22:46.460 align:start position:0% so we're doing all the drawing is also like<00:22:44.790> a<00:22:44.820> simple<00:22:45.330> state<00:22:45.780> transition<00:22:46.290> like 00:22:46.460 --> 00:22:46.470 align:start position:0% like a simple state transition like 00:22:46.470 --> 00:22:48.830 align:start position:0% like a simple state transition like metal<00:22:46.800> transfer<00:22:47.160> state<00:22:47.490> to<00:22:47.670> state<00:22:47.880> transition 00:22:48.830 --> 00:22:48.840 align:start position:0% metal transfer state to state transition 00:22:48.840 --> 00:22:52.730 align:start position:0% metal transfer state to state transition so<00:22:49.560> like<00:22:49.860> people<00:22:50.130> just<00:22:50.580> send<00:22:51.090> their<00:22:51.540> tokens<00:22:52.080> to 00:22:52.730 --> 00:22:52.740 align:start position:0% so like people just send their tokens to 00:22:52.740 --> 00:22:55.790 align:start position:0% so like people just send their tokens to leave<00:22:53.310> index<00:22:53.760> 0<00:22:54.030> which<00:22:54.840> is<00:22:55.020> which<00:22:55.440> can<00:22:55.620> only 00:22:55.790 --> 00:22:55.800 align:start position:0% leave index 0 which is which can only 00:22:55.800 --> 00:22:56.990 align:start position:0% leave index 0 which is which can only receive<00:22:56.460> tokens 00:22:56.990 --> 00:22:57.000 align:start position:0% receive tokens 00:22:57.000 --> 00:22:59.630 align:start position:0% receive tokens Leif<00:22:57.570> Leif<00:22:58.200> Leif<00:22:58.500> Leif<00:22:58.860> number<00:22:59.160> zero<00:22:59.370> cannot 00:22:59.630 --> 00:22:59.640 align:start position:0% Leif Leif Leif Leif number zero cannot 00:22:59.640 --> 00:23:01.760 align:start position:0% Leif Leif Leif Leif number zero cannot actually<00:22:59.940> spend<00:23:00.450> any<00:23:00.660> token<00:23:00.960> this<00:23:01.080> defined<00:23:01.650> in 00:23:01.760 --> 00:23:01.770 align:start position:0% actually spend any token this defined in 00:23:01.770 --> 00:23:03.980 align:start position:0% actually spend any token this defined in this<00:23:01.830> norm<00:23:02.100> so<00:23:02.670> he<00:23:03.090> was<00:23:03.240> have<00:23:03.690> to<00:23:03.840> do<00:23:03.960> a 00:23:03.980 --> 00:23:03.990 align:start position:0% this norm so he was have to do a 00:23:03.990 --> 00:23:06.860 align:start position:0% this norm so he was have to do a transfer<00:23:04.500> to<00:23:04.650> relief<00:23:04.890> index<00:23:05.280> 0<00:23:05.520> and<00:23:06.030> then<00:23:06.660> they 00:23:06.860 --> 00:23:06.870 align:start position:0% transfer to relief index 0 and then they 00:23:06.870 --> 00:23:09.170 align:start position:0% transfer to relief index 0 and then they can<00:23:07.050> go<00:23:07.230> on<00:23:07.380> scene<00:23:07.650> and<00:23:07.830> then<00:23:08.610> they<00:23:08.820> can<00:23:08.970> prove 00:23:09.170 --> 00:23:09.180 align:start position:0% can go on scene and then they can prove 00:23:09.180 --> 00:23:13.700 align:start position:0% can go on scene and then they can prove in<00:23:09.360> the<00:23:09.480> latest<00:23:10.460> local<00:23:11.460> group<00:23:11.640> that<00:23:12.710> reduction 00:23:13.700 --> 00:23:13.710 align:start position:0% in the latest local group that reduction 00:23:13.710 --> 00:23:16.220 align:start position:0% in the latest local group that reduction buoy<00:23:14.190> friend<00:23:14.670> X<00:23:14.820> 0<00:23:15.090> and<00:23:15.300> they'll<00:23:15.750> get<00:23:15.990> their 00:23:16.220 --> 00:23:16.230 align:start position:0% buoy friend X 0 and they'll get their 00:23:16.230 --> 00:23:24.620 align:start position:0% buoy friend X 0 and they'll get their token<00:23:16.560> back<00:23:16.770> from<00:23:17.010> the<00:23:17.190> deposit<00:23:18.080> right 00:23:24.620 --> 00:23:24.630 align:start position:0% 00:23:24.630 --> 00:23:30.330 align:start position:0% yeah 00:23:30.330 --> 00:23:30.340 align:start position:0% 00:23:30.340 --> 00:23:31.960 align:start position:0% [Music] 00:23:31.960 --> 00:23:31.970 align:start position:0% [Music] 00:23:31.970 --> 00:23:35.090 align:start position:0% [Music] the<00:23:32.970> assumption<00:23:33.450> which<00:23:33.659> I<00:23:33.809> don't<00:23:34.620> you<00:23:34.830> need 00:23:35.090 --> 00:23:35.100 align:start position:0% the assumption which I don't you need 00:23:35.100 --> 00:23:37.770 align:start position:0% the assumption which I don't you need data<00:23:35.400> Philippines 00:23:37.770 --> 00:23:37.780 align:start position:0% data Philippines 00:23:37.780 --> 00:23:47.070 align:start position:0% data Philippines [Music] 00:23:47.070 --> 00:23:47.080 align:start position:0% 00:23:47.080 --> 00:23:50.790 align:start position:0% so<00:23:47.620> so<00:23:48.370> with<00:23:48.520> every<00:23:48.910> stop<00:23:49.210> proof<00:23:50.170> that<00:23:50.620> is 00:23:50.790 --> 00:23:50.800 align:start position:0% so so with every stop proof that is 00:23:50.800 --> 00:23:53.880 align:start position:0% so so with every stop proof that is somewhat<00:23:51.040> daunting<00:23:51.220> we<00:23:52.060> submit<00:23:52.900> a<00:23:53.050> condensed 00:23:53.880 --> 00:23:53.890 align:start position:0% somewhat daunting we submit a condensed 00:23:53.890 --> 00:23:56.220 align:start position:0% somewhat daunting we submit a condensed form<00:23:54.130> of<00:23:54.780> transaction<00:23:55.780> right 00:23:56.220 --> 00:23:56.230 align:start position:0% form of transaction right 00:23:56.230 --> 00:24:00.450 align:start position:0% form of transaction right so<00:23:57.330> using<00:23:58.330> that<00:23:58.680> anyone<00:23:59.680> can<00:23:59.830> come<00:24:00.070> and<00:24:00.100> prove 00:24:00.450 --> 00:24:00.460 align:start position:0% so using that anyone can come and prove 00:24:00.460 --> 00:24:04.080 align:start position:0% so using that anyone can come and prove that<00:24:01.050> like<00:24:02.080> Biscay<00:24:02.740> of<00:24:02.830> all<00:24:03.160> the<00:24:03.370> other 00:24:04.080 --> 00:24:04.090 align:start position:0% that like Biscay of all the other 00:24:04.090 --> 00:24:06.270 align:start position:0% that like Biscay of all the other transactions<00:24:04.780> that<00:24:05.290> have<00:24:05.530> been<00:24:05.740> processed<00:24:06.100> in 00:24:06.270 --> 00:24:06.280 align:start position:0% transactions that have been processed in 00:24:06.280 --> 00:24:09.840 align:start position:0% transactions that have been processed in the<00:24:06.640> latest<00:24:08.220> non-resident<00:24:09.220> on<00:24:09.400> chain<00:24:09.640> so 00:24:09.840 --> 00:24:09.850 align:start position:0% the latest non-resident on chain so 00:24:09.850 --> 00:24:12.660 align:start position:0% the latest non-resident on chain so third<00:24:10.030> data<00:24:10.270> validity<00:24:10.960> is<00:24:11.500> same<00:24:11.770> as<00:24:11.980> a<00:24:12.280> theorem 00:24:12.660 --> 00:24:12.670 align:start position:0% third data validity is same as a theorem 00:24:12.670 --> 00:24:18.860 align:start position:0% third data validity is same as a theorem gene<00:24:16.470> dismisses<00:24:17.470> the<00:24:17.560> being<00:24:17.770> it<00:24:18.280> seems<00:24:18.310> like 00:24:18.860 --> 00:24:18.870 align:start position:0% gene dismisses the being it seems like 00:24:18.870 --> 00:24:21.210 align:start position:0% gene dismisses the being it seems like it<00:24:19.870> is<00:24:19.960> this<00:24:20.170> example<00:24:20.530> really<00:24:20.860> have<00:24:21.070> any 00:24:21.210 --> 00:24:21.220 align:start position:0% it is this example really have any 00:24:21.220 --> 00:24:24.570 align:start position:0% it is this example really have any council<00:24:22.120> houses<00:24:22.930> or<00:24:23.380> their<00:24:23.500> systems<00:24:23.890> they 00:24:24.570 --> 00:24:24.580 align:start position:0% council houses or their systems they 00:24:24.580 --> 00:24:26.640 align:start position:0% council houses or their systems they transition<00:24:25.090> function<00:24:25.270> from<00:24:25.630> trees<00:24:25.960> trees<00:24:26.380> and 00:24:26.640 --> 00:24:26.650 align:start position:0% transition function from trees trees and 00:24:26.650 --> 00:24:34.960 align:start position:0% transition function from trees trees and you're<00:24:26.860> trying<00:24:27.700> to<00:24:27.790> show<00:24:28.000> that 00:24:34.960 --> 00:24:34.970 align:start position:0% 00:24:34.970 --> 00:24:38.300 align:start position:0% yeah<00:24:35.970> so<00:24:36.480> it's<00:24:36.750> under<00:24:37.020> state<00:24:37.310> transition 00:24:38.300 --> 00:24:38.310 align:start position:0% yeah so it's under state transition 00:24:38.310 --> 00:24:40.280 align:start position:0% yeah so it's under state transition function<00:24:38.340> right<00:24:38.850> it's<00:24:39.510> just<00:24:39.660> like<00:24:39.840> you're 00:24:40.280 --> 00:24:40.290 align:start position:0% function right it's just like you're 00:24:40.290 --> 00:24:43.010 align:start position:0% function right it's just like you're done<00:24:40.410> in<00:24:40.530> science<00:24:40.860> math<00:24:41.040> we<00:24:41.660> basically<00:24:42.660> say 00:24:43.010 --> 00:24:43.020 align:start position:0% done in science math we basically say 00:24:43.020 --> 00:24:47.540 align:start position:0% done in science math we basically say that<00:24:43.220> let's<00:24:44.220> say<00:24:44.340> Alice's<00:24:44.820> transferring<00:24:46.550> $50 00:24:47.540 --> 00:24:47.550 align:start position:0% that let's say Alice's transferring $50 00:24:47.550 --> 00:24:50.360 align:start position:0% that let's say Alice's transferring $50 to<00:24:47.730> Bob<00:24:48.060> right<00:24:48.270> so<00:24:48.690> in<00:24:48.960> that<00:24:49.140> people<00:24:49.380> check<00:24:50.190> if 00:24:50.360 --> 00:24:50.370 align:start position:0% to Bob right so in that people check if 00:24:50.370 --> 00:24:54.440 align:start position:0% to Bob right so in that people check if Alice<00:24:50.910> exists<00:24:51.780> in<00:24:51.900> her<00:24:52.020> dream<00:24:52.230> if<00:24:53.040> she<00:24:53.370> has<00:24:53.580> 50 00:24:54.440 --> 00:24:54.450 align:start position:0% Alice exists in her dream if she has 50 00:24:54.450 --> 00:24:57.050 align:start position:0% Alice exists in her dream if she has 50 dollars<00:24:55.020> to<00:24:55.170> spend<00:24:55.410> and<00:24:56.220> then<00:24:56.580> we<00:24:56.760> basically 00:24:57.050 --> 00:24:57.060 align:start position:0% dollars to spend and then we basically 00:24:57.060 --> 00:25:00.620 align:start position:0% dollars to spend and then we basically change<00:24:57.540> his<00:24:57.840> let's<00:24:58.830> say<00:24:58.980> is<00:24:59.340> 500<00:24:59.880> right<00:25:00.030> so<00:25:00.480> it 00:25:00.620 --> 00:25:00.630 align:start position:0% change his let's say is 500 right so it 00:25:00.630 --> 00:25:03.080 align:start position:0% change his let's say is 500 right so it changes<00:25:00.930> balance<00:25:01.260> from<00:25:01.440> 100<00:25:01.860> to<00:25:01.950> 50<00:25:02.190> and<00:25:02.790> we 00:25:03.080 --> 00:25:03.090 align:start position:0% changes balance from 100 to 50 and we 00:25:03.090 --> 00:25:05.540 align:start position:0% changes balance from 100 to 50 and we increment<00:25:03.630> box<00:25:04.020> balance<00:25:04.440> if<00:25:04.740> it<00:25:04.950> exists<00:25:05.370> in<00:25:05.460> a 00:25:05.540 --> 00:25:05.550 align:start position:0% increment box balance if it exists in a 00:25:05.550 --> 00:25:07.850 align:start position:0% increment box balance if it exists in a dream<00:25:05.760> from<00:25:06.300> zero<00:25:06.690> to<00:25:06.870> let's<00:25:07.170> say<00:25:07.290> 50 00:25:07.850 --> 00:25:07.860 align:start position:0% dream from zero to let's say 50 00:25:07.860 --> 00:25:11.390 align:start position:0% dream from zero to let's say 50 and<00:25:08.460> we<00:25:08.610> update<00:25:09.030> the<00:25:09.540> stock<00:25:09.810> saga<00:25:10.280> maca<00:25:11.280> root 00:25:11.390 --> 00:25:11.400 align:start position:0% and we update the stock saga maca root 00:25:11.400 --> 00:25:14.480 align:start position:0% and we update the stock saga maca root yeah<00:25:12.300> so<00:25:12.510> this<00:25:12.990> is<00:25:13.080> all<00:25:13.170> state<00:25:13.530> transition 00:25:14.480 --> 00:25:14.490 align:start position:0% yeah so this is all state transition 00:25:14.490 --> 00:25:18.110 align:start position:0% yeah so this is all state transition happened<00:25:14.880> and<00:25:15.450> we<00:25:16.160> submitted<00:25:17.160> the<00:25:17.400> updated 00:25:18.110 --> 00:25:18.120 align:start position:0% happened and we submitted the updated 00:25:18.120 --> 00:25:20.450 align:start position:0% happened and we submitted the updated Prudhomme<00:25:18.600> she<00:25:19.010> doesn't<00:25:20.010> smell<00:25:20.130> good 00:25:20.450 --> 00:25:20.460 align:start position:0% Prudhomme she doesn't smell good 00:25:20.460 --> 00:25:23.300 align:start position:0% Prudhomme she doesn't smell good yes<00:25:21.120> it's<00:25:21.450> not<00:25:21.570> really<00:25:21.870> bad<00:25:22.050> it's<00:25:23.010> pretty 00:25:23.300 --> 00:25:23.310 align:start position:0% yes it's not really bad it's pretty 00:25:23.310 --> 00:25:27.080 align:start position:0% yes it's not really bad it's pretty gerald<00:25:24.000> yes<00:25:24.240> generally<00:25:24.900> you<00:25:25.350> yeah<00:25:26.340> you<00:25:26.940> can 00:25:27.080 --> 00:25:27.090 align:start position:0% gerald yes generally you yeah you can 00:25:27.090 --> 00:25:29.030 align:start position:0% gerald yes generally you yeah you can restore<00:25:27.600> anything<00:25:28.080> inside<00:25:28.470> the<00:25:28.620> leaf<00:25:28.800> and 00:25:29.030 --> 00:25:29.040 align:start position:0% restore anything inside the leaf and 00:25:29.040 --> 00:25:31.100 align:start position:0% restore anything inside the leaf and right<00:25:29.220> just<00:25:29.460> a<00:25:29.610> transitional<00:25:30.180> weight<00:25:30.660> sample 00:25:31.100 --> 00:25:31.110 align:start position:0% right just a transitional weight sample 00:25:31.110 --> 00:25:33.020 align:start position:0% right just a transitional weight sample you<00:25:31.590> have<00:25:31.620> it<00:25:31.800> some<00:25:31.980> conditions<00:25:32.400> anything 00:25:33.020 --> 00:25:33.030 align:start position:0% you have it some conditions anything 00:25:33.030 --> 00:25:40.370 align:start position:0% you have it some conditions anything that<00:25:33.150> man<00:25:34.970> yes<00:25:35.970> so<00:25:37.130> this<00:25:38.130> is<00:25:39.260> basically<00:25:40.260> just 00:25:40.370 --> 00:25:40.380 align:start position:0% that man yes so this is basically just 00:25:40.380 --> 00:25:43.280 align:start position:0% that man yes so this is basically just like<00:25:41.330> doing<00:25:42.330> all<00:25:42.480> the<00:25:42.600> checks<00:25:42.840> inside<00:25:43.050> the 00:25:43.280 --> 00:25:43.290 align:start position:0% like doing all the checks inside the 00:25:43.290 --> 00:25:45.650 align:start position:0% like doing all the checks inside the stock<00:25:43.530> um<00:25:43.830> I<00:25:44.250> think<00:25:44.550> I'm<00:25:44.760> going<00:25:44.970> to<00:25:45.060> skip<00:25:45.390> all 00:25:45.650 --> 00:25:45.660 align:start position:0% stock um I think I'm going to skip all 00:25:45.660 --> 00:25:47.120 align:start position:0% stock um I think I'm going to skip all the<00:25:45.810> steps<00:25:46.050> and<00:25:46.230> we<00:25:46.350> are<00:25:46.440> going<00:25:46.650> to<00:25:46.740> go<00:25:46.890> to<00:25:46.950> the 00:25:47.120 --> 00:25:47.130 align:start position:0% the steps and we are going to go to the 00:25:47.130 --> 00:25:49.030 align:start position:0% the steps and we are going to go to the final<00:25:47.460> circuit<00:25:47.760> so<00:25:47.880> I<00:25:47.940> can<00:25:48.150> show<00:25:48.570> you<00:25:48.630> what's 00:25:49.030 --> 00:25:49.040 align:start position:0% final circuit so I can show you what's 00:25:49.040 --> 00:26:00.920 align:start position:0% final circuit so I can show you what's actually<00:25:50.040> happening 00:26:00.920 --> 00:26:00.930 align:start position:0% 00:26:00.930 --> 00:26:04.620 align:start position:0% for<00:26:01.930> correcting<00:26:02.410> multiple<00:26:03.040> transactions<00:26:04.000> you 00:26:04.620 --> 00:26:04.630 align:start position:0% for correcting multiple transactions you 00:26:04.630 --> 00:26:07.200 align:start position:0% for correcting multiple transactions you you<00:26:05.080> just<00:26:05.320> do<00:26:05.830> the<00:26:05.950> same<00:26:06.220> thing<00:26:06.490> with<00:26:06.640> a<00:26:06.670> for 00:26:07.200 --> 00:26:07.210 align:start position:0% you just do the same thing with a for 00:26:07.210 --> 00:26:08.400 align:start position:0% you just do the same thing with a for loop<00:26:07.240> for<00:26:07.540> the<00:26:07.720> number<00:26:07.930> of<00:26:07.960> number<00:26:08.380> of 00:26:08.400 --> 00:26:08.410 align:start position:0% loop for the number of number of 00:26:08.410 --> 00:26:10.980 align:start position:0% loop for the number of number of projects<00:26:08.830> when<00:26:08.950> you<00:26:08.980> want<00:26:09.430> to<00:26:09.520> process<00:26:09.990> right 00:26:10.980 --> 00:26:10.990 align:start position:0% projects when you want to process right 00:26:10.990 --> 00:26:13.170 align:start position:0% projects when you want to process right now<00:26:11.050> who<00:26:11.410> says<00:26:11.590> only<00:26:11.860> one<00:26:12.040> but<00:26:12.760> I<00:26:12.790> have<00:26:13.060> the 00:26:13.170 --> 00:26:13.180 align:start position:0% now who says only one but I have the 00:26:13.180 --> 00:26:17.010 align:start position:0% now who says only one but I have the section<00:26:13.630> over<00:26:13.780> here<00:26:13.810> which<00:26:14.490> you<00:26:15.490> can 00:26:17.010 --> 00:26:17.020 align:start position:0% section over here which you can 00:26:17.020 --> 00:26:22.350 align:start position:0% section over here which you can [Music] 00:26:22.350 --> 00:26:22.360 align:start position:0% 00:26:22.360 --> 00:26:27.120 align:start position:0% yeah<00:26:23.390> so<00:26:23.860> yeah<00:26:24.860> so<00:26:25.100> often 00:26:27.120 --> 00:26:27.130 align:start position:0% yeah so yeah so often 00:26:27.130 --> 00:26:32.550 align:start position:0% yeah so yeah so often there<00:26:27.640> was<00:26:28.540> a<00:26:28.570> previous<00:26:28.870> page 00:26:32.550 --> 00:26:32.560 align:start position:0% 00:26:32.560 --> 00:26:35.130 align:start position:0% so<00:26:33.040> the<00:26:33.130> thing<00:26:33.280> is<00:26:33.310> as<00:26:34.000> soon<00:26:34.060> as<00:26:34.270> we<00:26:34.570> process 00:26:35.130 --> 00:26:35.140 align:start position:0% so the thing is as soon as we process 00:26:35.140 --> 00:26:39.570 align:start position:0% so the thing is as soon as we process one<00:26:35.380> input<00:26:35.740> we<00:26:36.250> should<00:26:36.460> update<00:26:37.180> the<00:26:38.580> accounts 00:26:39.570 --> 00:26:39.580 align:start position:0% one input we should update the accounts 00:26:39.580 --> 00:26:43.050 align:start position:0% one input we should update the accounts tree<00:26:40.240> otherwise<00:26:40.810> if<00:26:41.590> a<00:26:42.160> leaf<00:26:42.340> is<00:26:42.580> printing 00:26:43.050 --> 00:26:43.060 align:start position:0% tree otherwise if a leaf is printing 00:26:43.060 --> 00:26:44.910 align:start position:0% tree otherwise if a leaf is printing multiple<00:26:43.270> times<00:26:43.780> inside<00:26:44.140> the<00:26:44.470> same<00:26:44.650> batch 00:26:44.910 --> 00:26:44.920 align:start position:0% multiple times inside the same batch 00:26:44.920 --> 00:26:47.430 align:start position:0% multiple times inside the same batch then<00:26:45.760> it<00:26:45.910> may<00:26:46.090> be<00:26:46.150> able<00:26:46.330> to<00:26:46.630> double<00:26:47.230> spend 00:26:47.430 --> 00:26:47.440 align:start position:0% then it may be able to double spend 00:26:47.440 --> 00:26:51.360 align:start position:0% then it may be able to double spend right<00:26:47.590> so<00:26:48.130> let's<00:26:49.000> say<00:26:49.150> in<00:26:49.210> a<00:26:49.330> batch<00:26:50.160> Alice<00:26:51.160> was 00:26:51.360 --> 00:26:51.370 align:start position:0% right so let's say in a batch Alice was 00:26:51.370 --> 00:26:56.610 align:start position:0% right so let's say in a batch Alice was Alice<00:26:52.060> had<00:26:52.240> only<00:26:52.830> 50<00:26:53.830> bucks<00:26:54.040> and<00:26:54.250> she<00:26:54.940> was<00:26:55.620> able 00:26:56.610 --> 00:26:56.620 align:start position:0% Alice had only 50 bucks and she was able 00:26:56.620 --> 00:26:58.800 align:start position:0% Alice had only 50 bucks and she was able to<00:26:56.770> get<00:26:57.010> both<00:26:57.370> of<00:26:57.550> those<00:26:57.700> from<00:26:57.970> the<00:26:58.300> same<00:26:58.600> batch 00:26:58.800 --> 00:26:58.810 align:start position:0% to get both of those from the same batch 00:26:58.810 --> 00:27:01.980 align:start position:0% to get both of those from the same batch so<00:26:59.350> if<00:26:59.470> we<00:26:59.620> don't<00:26:59.830> update<00:27:00.460> the<00:27:01.000> root<00:27:01.750> after 00:27:01.980 --> 00:27:01.990 align:start position:0% so if we don't update the root after 00:27:01.990 --> 00:27:04.860 align:start position:0% so if we don't update the root after processing<00:27:02.500> every<00:27:03.040> transaction<00:27:03.430> then<00:27:04.390> when 00:27:04.860 --> 00:27:04.870 align:start position:0% processing every transaction then when 00:27:04.870 --> 00:27:07.380 align:start position:0% processing every transaction then when the<00:27:05.230> vendors<00:27:05.770> not<00:27:05.950> discreet<00:27:06.370> processing<00:27:07.240> the 00:27:07.380 --> 00:27:07.390 align:start position:0% the vendors not discreet processing the 00:27:07.390 --> 00:27:10.620 align:start position:0% the vendors not discreet processing the second<00:27:07.870> condition<00:27:08.410> of<00:27:08.500> Alice<00:27:09.090> the<00:27:10.090> circuit 00:27:10.620 --> 00:27:10.630 align:start position:0% second condition of Alice the circuit 00:27:10.630 --> 00:27:13.230 align:start position:0% second condition of Alice the circuit will<00:27:10.780> never<00:27:10.930> know<00:27:11.590> that<00:27:12.240> previous 00:27:13.230 --> 00:27:13.240 align:start position:0% will never know that previous 00:27:13.240 --> 00:27:15.990 align:start position:0% will never know that previous transaction<00:27:13.810> already<00:27:14.410> spent<00:27:14.710> 250<00:27:15.490> bucks 00:27:15.990 --> 00:27:16.000 align:start position:0% transaction already spent 250 bucks 00:27:16.000 --> 00:27:21.360 align:start position:0% transaction already spent 250 bucks gotcha<00:27:16.960> right<00:27:20.220> yeah 00:27:21.360 --> 00:27:21.370 align:start position:0% gotcha right yeah 00:27:21.370 --> 00:27:25.380 align:start position:0% gotcha right yeah so<00:27:21.550> this<00:27:22.060> is<00:27:22.680> every<00:27:23.680> standard<00:27:24.010> we<00:27:24.190> we<00:27:24.730> expiry 00:27:25.380 --> 00:27:25.390 align:start position:0% so this is every standard we we expiry 00:27:25.390 --> 00:27:28.440 align:start position:0% so this is every standard we we expiry take<00:27:26.290> the<00:27:26.470> inputs<00:27:26.800> as<00:27:27.010> like<00:27:27.550> the<00:27:28.150> previous 00:27:28.440 --> 00:27:28.450 align:start position:0% take the inputs as like the previous 00:27:28.450 --> 00:27:31.590 align:start position:0% take the inputs as like the previous account<00:27:28.840> rules<00:27:29.400> the<00:27:30.400> intermediate<00:27:31.390> root 00:27:31.590 --> 00:27:31.600 align:start position:0% account rules the intermediate root 00:27:31.600 --> 00:27:34.170 align:start position:0% account rules the intermediate root since<00:27:32.380> this<00:27:32.800> is<00:27:32.950> all<00:27:33.070> just<00:27:33.430> for<00:27:33.520> one's<00:27:34.030> actions 00:27:34.170 --> 00:27:34.180 align:start position:0% since this is all just for one's actions 00:27:34.180 --> 00:27:36.870 align:start position:0% since this is all just for one's actions so<00:27:34.540> it<00:27:34.690> has<00:27:34.840> only<00:27:34.870> one<00:27:35.260> intermediate<00:27:35.890> root<00:27:36.310> if 00:27:36.870 --> 00:27:36.880 align:start position:0% so it has only one intermediate root if 00:27:36.880 --> 00:27:39.150 align:start position:0% so it has only one intermediate root if you<00:27:36.940> want<00:27:37.180> it<00:27:37.330> to<00:27:37.450> do<00:27:37.570> multiple<00:27:38.020> this<00:27:38.830> would<00:27:39.010> be 00:27:39.150 --> 00:27:39.160 align:start position:0% you want it to do multiple this would be 00:27:39.160 --> 00:27:43.380 align:start position:0% you want it to do multiple this would be an<00:27:39.280> eye<00:27:39.520> and<00:27:40.480> here<00:27:41.260> is<00:27:41.640> fear<00:27:42.640> of<00:27:42.760> the<00:27:42.880> pounds 00:27:43.380 --> 00:27:43.390 align:start position:0% an eye and here is fear of the pounds 00:27:43.390 --> 00:27:46.680 align:start position:0% an eye and here is fear of the pounds these<00:27:44.200> are<00:27:44.320> all<00:27:44.410> the<00:27:44.530> balances<00:27:45.280> the<00:27:46.120> balances 00:27:46.680 --> 00:27:46.690 align:start position:0% these are all the balances the balances 00:27:46.690 --> 00:27:51.890 align:start position:0% these are all the balances the balances in<00:27:47.560> an<00:27:48.010> Internet<00:27:48.490> heading<00:27:48.760> and<00:27:50.340> co-ceo 00:27:51.890 --> 00:27:51.900 align:start position:0% in an Internet heading and co-ceo 00:27:51.900 --> 00:27:54.060 align:start position:0% in an Internet heading and co-ceo provide<00:27:52.900> all<00:27:53.020> the<00:27:53.140> transaction<00:27:53.620> input<00:27:53.890> right 00:27:54.060 --> 00:27:54.070 align:start position:0% provide all the transaction input right 00:27:54.070 --> 00:27:57.090 align:start position:0% provide all the transaction input right which<00:27:54.700> is<00:27:54.790> like<00:27:54.940> the<00:27:55.090> send<00:27:55.960> up<00:27:56.080> of<00:27:56.170> key<00:27:56.410> sender 00:27:57.090 --> 00:27:57.100 align:start position:0% which is like the send up of key sender 00:27:57.100 --> 00:27:59.370 align:start position:0% which is like the send up of key sender balance<00:27:57.460> this<00:27:58.060> yoke<00:27:58.270> of<00:27:58.480> receiver<00:27:58.990> balance 00:27:59.370 --> 00:27:59.380 align:start position:0% balance this yoke of receiver balance 00:27:59.380 --> 00:28:03.960 align:start position:0% balance this yoke of receiver balance amount<00:28:00.250> of<00:28:00.760> the<00:28:00.940> sender<00:28:01.690> signatures<00:28:02.620> and<00:28:02.970> the 00:28:03.960 --> 00:28:03.970 align:start position:0% amount of the sender signatures and the 00:28:03.970 --> 00:28:06.750 align:start position:0% amount of the sender signatures and the proof<00:28:04.900> of<00:28:05.050> existence<00:28:05.410> for<00:28:06.040> sender<00:28:06.460> and 00:28:06.750 --> 00:28:06.760 align:start position:0% proof of existence for sender and 00:28:06.760 --> 00:28:11.180 align:start position:0% proof of existence for sender and receiver<00:28:07.720> right<00:28:08.410> and<00:28:08.710> we<00:28:09.220> output<00:28:09.850> new 00:28:11.180 --> 00:28:11.190 align:start position:0% receiver right and we output new 00:28:11.190 --> 00:28:18.410 align:start position:0% receiver right and we output new after<00:28:11.550> processing<00:28:11.960> everything<00:28:13.250> right<00:28:15.950> so<00:28:17.420> in 00:28:18.410 --> 00:28:18.420 align:start position:0% after processing everything right so in 00:28:18.420 --> 00:28:23.600 align:start position:0% after processing everything right so in the<00:28:18.840> so<00:28:19.370> since<00:28:20.370> I<00:28:21.060> guess<00:28:21.620> part<00:28:22.620> three<00:28:22.920> we<00:28:23.250> we 00:28:23.600 --> 00:28:23.610 align:start position:0% the so since I guess part three we we 00:28:23.610 --> 00:28:28.550 align:start position:0% the so since I guess part three we we did<00:28:24.120> a<00:28:24.150> part<00:28:24.450> where<00:28:24.660> we<00:28:25.370> and<00:28:26.370> but<00:28:27.060> -<00:28:27.540> we<00:28:27.780> did<00:28:28.530> a 00:28:28.550 --> 00:28:28.560 align:start position:0% did a part where we and but - we did a 00:28:28.560 --> 00:28:32.170 align:start position:0% did a part where we and but - we did a part<00:28:28.830> where<00:28:29.040> we<00:28:29.220> showed<00:28:30.000> the<00:28:30.530> existence<00:28:31.530> of 00:28:32.170 --> 00:28:32.180 align:start position:0% part where we showed the existence of 00:28:32.180 --> 00:28:37.400 align:start position:0% part where we showed the existence of Merkel<00:28:33.180> please<00:28:33.570> I<00:28:33.900> guess<00:28:35.330> yeah<00:28:36.330> please 00:28:37.400 --> 00:28:37.410 align:start position:0% Merkel please I guess yeah please 00:28:37.410 --> 00:28:40.220 align:start position:0% Merkel please I guess yeah please existence<00:28:37.950> right<00:28:38.160> so<00:28:38.760> do<00:28:39.300> you<00:28:39.390> think<00:28:39.420> this<00:28:39.780> M 00:28:40.220 --> 00:28:40.230 align:start position:0% existence right so do you think this M 00:28:40.230 --> 00:28:45.700 align:start position:0% existence right so do you think this M plate<00:28:40.970> over<00:28:41.970> here 00:28:45.700 --> 00:28:45.710 align:start position:0% 00:28:45.710 --> 00:28:50.210 align:start position:0% yeah<00:28:46.710> so<00:28:48.140> using<00:28:49.140> that<00:28:49.350> we<00:28:49.590> are<00:28:49.800> basically 00:28:50.210 --> 00:28:50.220 align:start position:0% yeah so using that we are basically 00:28:50.220 --> 00:28:53.390 align:start position:0% yeah so using that we are basically going<00:28:50.430> to<00:28:50.580> prove<00:28:51.330> that<00:28:51.470> Center<00:28:52.470> account 00:28:53.390 --> 00:28:53.400 align:start position:0% going to prove that Center account 00:28:53.400 --> 00:28:56.630 align:start position:0% going to prove that Center account exists<00:28:54.180> in<00:28:54.360> the<00:28:54.660> previous<00:28:55.620> account<00:28:55.950> which<00:28:56.490> is 00:28:56.630 --> 00:28:56.640 align:start position:0% exists in the previous account which is 00:28:56.640 --> 00:29:00.230 align:start position:0% exists in the previous account which is provided<00:28:57.270> I<00:28:57.420> input<00:28:57.630> right<00:28:58.170> so<00:28:58.890> we<00:28:59.820> just<00:28:59.850> passed 00:29:00.230 --> 00:29:00.240 align:start position:0% provided I input right so we just passed 00:29:00.240 --> 00:29:05.240 align:start position:0% provided I input right so we just passed the<00:29:00.360> of<00:29:00.960> ease<00:29:01.230> and<00:29:01.500> balance<00:29:03.290> ARP<00:29:04.290> do<00:29:04.920> the<00:29:05.040> same 00:29:05.240 --> 00:29:05.250 align:start position:0% the of ease and balance ARP do the same 00:29:05.250 --> 00:29:07.520 align:start position:0% the of ease and balance ARP do the same thing<00:29:05.490> for<00:29:05.730> all<00:29:05.940> the<00:29:05.970> senders<00:29:06.870> given<00:29:07.350> given 00:29:07.520 --> 00:29:07.530 align:start position:0% thing for all the senders given given 00:29:07.530 --> 00:29:11.170 align:start position:0% thing for all the senders given given the<00:29:07.950> pathway<00:29:08.400> and<00:29:09.230> then<00:29:10.230> we<00:29:10.380> just<00:29:10.590> do<00:29:10.710> a<00:29:10.740> simple 00:29:11.170 --> 00:29:11.180 align:start position:0% the pathway and then we just do a simple 00:29:11.180 --> 00:29:14.750 align:start position:0% the pathway and then we just do a simple signature<00:29:12.180> thing<00:29:12.510> that<00:29:13.170> if<00:29:13.320> the<00:29:13.490> center<00:29:14.490> has 00:29:14.750 --> 00:29:14.760 align:start position:0% signature thing that if the center has 00:29:14.760 --> 00:29:21.290 align:start position:0% signature thing that if the center has actually<00:29:15.390> signed<00:29:16.580> the<00:29:17.580> message<00:29:19.970> yeah<00:29:20.970> and 00:29:21.290 --> 00:29:21.300 align:start position:0% actually signed the message yeah and 00:29:21.300 --> 00:29:27.650 align:start position:0% actually signed the message yeah and then<00:29:21.810> we<00:29:22.170> create<00:29:22.500> a<00:29:22.530> new<00:29:23.630> leaf<00:29:24.630> -<00:29:25.140> so<00:29:26.060> the<00:29:27.060> v5 00:29:27.650 --> 00:29:27.660 align:start position:0% then we create a new leaf - so the v5 00:29:27.660 --> 00:29:30.280 align:start position:0% then we create a new leaf - so the v5 previously<00:29:28.200> could<00:29:28.410> contain<00:29:28.830> like<00:29:29.100> of<00:29:29.910> key 00:29:30.280 --> 00:29:30.290 align:start position:0% previously could contain like of key 00:29:30.290 --> 00:29:33.410 align:start position:0% previously could contain like of key balance<00:29:31.290> which<00:29:31.800> all<00:29:31.950> strip<00:29:32.130> tease<00:29:32.370> then<00:29:32.940> after 00:29:33.410 --> 00:29:33.420 align:start position:0% balance which all strip tease then after 00:29:33.420 --> 00:29:38.600 align:start position:0% balance which all strip tease then after after<00:29:34.340> spending<00:29:35.340> 50<00:29:35.880> is<00:29:36.470> leave<00:29:37.470> like<00:29:38.160> perky 00:29:38.600 --> 00:29:38.610 align:start position:0% after spending 50 is leave like perky 00:29:38.610 --> 00:29:40.760 align:start position:0% after spending 50 is leave like perky and<00:29:38.880> zero<00:29:39.270> so<00:29:39.810> we<00:29:39.900> need<00:29:40.050> to<00:29:40.170> create<00:29:40.290> a<00:29:40.440> new<00:29:40.470> ash 00:29:40.760 --> 00:29:40.770 align:start position:0% and zero so we need to create a new ash 00:29:40.770 --> 00:29:43.880 align:start position:0% and zero so we need to create a new ash for<00:29:41.040> this<00:29:41.160> and<00:29:41.940> we<00:29:42.390> need<00:29:42.930> to<00:29:43.080> update<00:29:43.620> the 00:29:43.880 --> 00:29:43.890 align:start position:0% for this and we need to update the 00:29:43.890 --> 00:29:47.630 align:start position:0% for this and we need to update the accounts<00:29:44.730> root<00:29:44.910> so<00:29:45.390> this<00:29:45.980> this<00:29:46.980> this<00:29:47.280> whiskey 00:29:47.630 --> 00:29:47.640 align:start position:0% accounts root so this this this whiskey 00:29:47.640 --> 00:29:53.300 align:start position:0% accounts root so this this this whiskey or<00:29:47.880> puts<00:29:48.330> the<00:29:48.890> intermediate<00:29:51.320> and<00:29:52.320> using<00:29:53.010> this 00:29:53.300 --> 00:29:53.310 align:start position:0% or puts the intermediate and using this 00:29:53.310 --> 00:29:55.430 align:start position:0% or puts the intermediate and using this intermediate<00:29:54.060> root<00:29:54.300> we<00:29:54.540> basically<00:29:54.840> check<00:29:54.990> if 00:29:55.430 --> 00:29:55.440 align:start position:0% intermediate root we basically check if 00:29:55.440 --> 00:29:59.570 align:start position:0% intermediate root we basically check if the<00:29:55.890> receiver<00:29:56.580> exists<00:29:57.570> in<00:29:57.810> in<00:29:58.110> the<00:29:58.230> Breanna<00:29:58.680> if 00:29:59.570 --> 00:29:59.580 align:start position:0% the receiver exists in in the Breanna if 00:29:59.580 --> 00:30:03.080 align:start position:0% the receiver exists in in the Breanna if we<00:29:59.790> exist<00:30:00.480> then<00:30:01.110> we<00:30:01.320> credit<00:30:01.860> the<00:30:02.090> receiver 00:30:03.080 --> 00:30:03.090 align:start position:0% we exist then we credit the receiver 00:30:03.090 --> 00:30:06.490 align:start position:0% we exist then we credit the receiver with<00:30:03.300> whatever<00:30:04.050> amount<00:30:04.440> was<00:30:05.040> sent<00:30:05.310> by<00:30:05.790> the 00:30:06.490 --> 00:30:06.500 align:start position:0% with whatever amount was sent by the 00:30:06.500 --> 00:30:08.509 align:start position:0% with whatever amount was sent by the sender 00:30:08.509 --> 00:30:08.519 align:start position:0% sender 00:30:08.519 --> 00:30:12.590 align:start position:0% sender yeah<00:30:09.519> yes<00:30:10.120> he<00:30:10.360> is<00:30:10.450> very<00:30:10.480> typical<00:30:11.320> center<00:30:11.950> and 00:30:12.590 --> 00:30:12.600 align:start position:0% yeah yes he is very typical center and 00:30:12.600 --> 00:30:15.870 align:start position:0% yeah yes he is very typical center and this<00:30:13.600> is<00:30:13.659> where<00:30:13.990> we<00:30:14.169> created<00:30:14.740> the<00:30:14.880> receiver 00:30:15.870 --> 00:30:15.880 align:start position:0% this is where we created the receiver 00:30:15.880 --> 00:30:19.080 align:start position:0% this is where we created the receiver and<00:30:16.210> then<00:30:16.419> we<00:30:16.600> basically<00:30:16.750> just<00:30:17.760> they<00:30:18.760> create<00:30:19.059> a 00:30:19.080 --> 00:30:19.090 align:start position:0% and then we basically just they create a 00:30:19.090 --> 00:30:21.299 align:start position:0% and then we basically just they create a new<00:30:19.179> moon<00:30:19.510> you<00:30:19.659> leave<00:30:19.840> for<00:30:20.320> the<00:30:20.500> receivers<00:30:21.039> in 00:30:21.299 --> 00:30:21.309 align:start position:0% new moon you leave for the receivers in 00:30:21.309 --> 00:30:32.009 align:start position:0% new moon you leave for the receivers in and<00:30:21.610> we<00:30:21.760> update<00:30:22.450> the<00:30:22.899> route<00:30:30.539> of<00:30:31.539> the<00:30:31.720> new 00:30:32.009 --> 00:30:32.019 align:start position:0% and we update the route of the new 00:30:32.019 --> 00:30:40.970 align:start position:0% and we update the route of the new mobility<00:30:32.679> with<00:30:33.090> updated<00:30:34.090> balance<00:30:38.669> and<00:30:39.669> we 00:30:40.970 --> 00:30:40.980 align:start position:0% mobility with updated balance and we 00:30:40.980 --> 00:30:43.379 align:start position:0% mobility with updated balance and we switch<00:30:41.980> switch<00:30:42.159> switch<00:30:42.220> we<00:30:42.639> can<00:30:42.669> summit<00:30:43.210> on 00:30:43.379 --> 00:30:43.389 align:start position:0% switch switch switch we can summit on 00:30:43.389 --> 00:30:46.950 align:start position:0% switch switch switch we can summit on gene<00:30:43.659> so<00:30:44.159> many<00:30:45.159> fight<00:30:45.399> down<00:30:45.610> that<00:30:45.789> just<00:30:46.000> right 00:30:46.950 --> 00:30:46.960 align:start position:0% gene so many fight down that just right 00:30:46.960 --> 00:30:50.399 align:start position:0% gene so many fight down that just right so<00:30:47.740> that<00:30:47.769> we<00:30:48.100> basically<00:30:48.279> rules<00:30:48.880> that<00:30:49.409> stay 00:30:50.399 --> 00:30:50.409 align:start position:0% so that we basically rules that stay 00:30:50.409 --> 00:30:52.799 align:start position:0% so that we basically rules that stay trans<00:30:50.730> transition<00:30:51.730> that<00:30:51.940> was<00:30:52.090> run<00:30:52.360> off<00:30:52.539> scene 00:30:52.799 --> 00:30:52.809 align:start position:0% trans transition that was run off scene 00:30:52.809 --> 00:30:55.409 align:start position:0% trans transition that was run off scene was<00:30:53.080> valid<00:30:53.440> and<00:30:53.649> we<00:30:54.460> pushed<00:30:54.730> our<00:30:54.970> next 00:30:55.409 --> 00:30:55.419 align:start position:0% was valid and we pushed our next 00:30:55.419 --> 00:30:59.909 align:start position:0% was valid and we pushed our next mountain<00:30:55.840> for<00:30:56.110> it<00:30:56.409> out<00:30:58.320> what<00:30:59.320> was<00:30:59.470> it<00:30:59.649> check 00:30:59.909 --> 00:30:59.919 align:start position:0% mountain for it out what was it check 00:30:59.919 --> 00:31:02.210 align:start position:0% mountain for it out what was it check that<00:31:00.340> transaction 00:31:02.210 --> 00:31:02.220 align:start position:0% that transaction 00:31:02.220 --> 00:31:08.070 align:start position:0% that transaction course<00:31:02.490> boys 00:31:08.070 --> 00:31:08.080 align:start position:0% 00:31:08.080 --> 00:31:11.100 align:start position:0% official<00:31:09.080> that<00:31:09.500> the<00:31:09.650> transaction<00:31:10.310> touch 00:31:11.100 --> 00:31:11.110 align:start position:0% official that the transaction touch 00:31:11.110 --> 00:31:14.590 align:start position:0% official that the transaction touch previous<00:31:12.110> transaction<00:31:12.820> so<00:31:13.820> effectively<00:31:14.420> at 00:31:14.590 --> 00:31:14.600 align:start position:0% previous transaction so effectively at 00:31:14.600 --> 00:31:22.210 align:start position:0% previous transaction so effectively at home<00:31:16.030> majesty<00:31:20.950> account<00:31:21.950> information 00:31:22.210 --> 00:31:22.220 align:start position:0% home majesty account information 00:31:22.220 --> 00:31:31.880 align:start position:0% home majesty account information previous<00:31:22.910> application<00:31:23.720> matches 00:31:31.880 --> 00:31:31.890 align:start position:0% 00:31:31.890 --> 00:31:33.820 align:start position:0% [Music] 00:31:33.820 --> 00:31:33.830 align:start position:0% [Music] 00:31:33.830 --> 00:31:36.570 align:start position:0% [Music] yeah<00:31:34.399> yeah<00:31:34.879> so 00:31:36.570 --> 00:31:36.580 align:start position:0% yeah yeah so 00:31:36.580 --> 00:31:42.089 align:start position:0% yeah yeah so basically<00:31:38.609> so<00:31:39.989> let<00:31:40.989> me<00:31:41.080> give<00:31:41.349> you<00:31:41.469> face<00:31:41.979> the 00:31:42.089 --> 00:31:42.099 align:start position:0% basically so let me give you face the 00:31:42.099 --> 00:31:44.879 align:start position:0% basically so let me give you face the question<00:31:42.219> you<00:31:42.940> can<00:31:43.149> be<00:31:44.049> found<00:31:44.259> directly 00:31:44.879 --> 00:31:44.889 align:start position:0% question you can be found directly 00:31:44.889 --> 00:31:47.070 align:start position:0% question you can be found directly so<00:31:45.399> you're<00:31:45.940> basically<00:31:46.119> asking<00:31:46.509> if<00:31:46.869> the 00:31:47.070 --> 00:31:47.080 align:start position:0% so you're basically asking if the 00:31:47.080 --> 00:31:49.919 align:start position:0% so you're basically asking if the accounts<00:31:47.589> would<00:31:47.940> summon<00:31:48.940> it<00:31:49.029> over<00:31:49.239> here<00:31:49.450> if<00:31:49.749> it 00:31:49.919 --> 00:31:49.929 align:start position:0% accounts would summon it over here if it 00:31:49.929 --> 00:31:52.169 align:start position:0% accounts would summon it over here if it had<00:31:50.139> if<00:31:50.469> it<00:31:50.649> had<00:31:50.859> the<00:31:51.039> correct<00:31:51.309> balance<00:31:51.729> that 00:31:52.169 --> 00:31:52.179 align:start position:0% had if it had the correct balance that 00:31:52.179 --> 00:31:56.249 align:start position:0% had if it had the correct balance that Alice<00:31:52.779> give<00:31:53.080> me<00:31:53.639> if<00:31:54.639> it<00:31:54.789> did<00:31:55.239> not<00:31:55.269> then<00:31:55.629> when<00:31:56.139> I 00:31:56.249 --> 00:31:56.259 align:start position:0% Alice give me if it did not then when I 00:31:56.259 --> 00:32:01.859 align:start position:0% Alice give me if it did not then when I submit<00:31:57.009> launching<00:31:57.519> the<00:31:58.799> previous<00:32:00.629> row<00:32:01.629> - 00:32:01.859 --> 00:32:01.869 align:start position:0% submit launching the previous row - 00:32:01.869 --> 00:32:04.019 align:start position:0% submit launching the previous row - which<00:32:02.259> is<00:32:02.409> submitted<00:32:02.799> on<00:32:02.950> a<00:32:03.129> one-to-one<00:32:03.609> match 00:32:04.019 --> 00:32:04.029 align:start position:0% which is submitted on a one-to-one match 00:32:04.029 --> 00:32:06.329 align:start position:0% which is submitted on a one-to-one match with<00:32:04.269> the<00:32:04.389> inputs<00:32:04.749> emitted<00:32:05.229> over<00:32:05.440> here<00:32:05.649> right 00:32:06.329 --> 00:32:06.339 align:start position:0% with the inputs emitted over here right 00:32:06.339 --> 00:32:09.389 align:start position:0% with the inputs emitted over here right so<00:32:06.609> it<00:32:06.940> has<00:32:07.149> to<00:32:07.330> it<00:32:07.509> has<00:32:07.539> to<00:32:07.899> be<00:32:08.019> changed<00:32:08.409> that 00:32:09.389 --> 00:32:09.399 align:start position:0% so it has to it has to be changed that 00:32:09.399 --> 00:32:15.910 align:start position:0% so it has to it has to be changed that makes<00:32:09.639> sense 00:32:15.910 --> 00:32:15.920 align:start position:0% 00:32:15.920 --> 00:32:22.370 align:start position:0% yeah<00:32:17.070> so<00:32:17.190> I<00:32:17.220> want<00:32:17.520> to<00:32:17.640> do<00:32:17.790> they<00:32:18.120> like<00:32:21.380> greatest 00:32:22.370 --> 00:32:22.380 align:start position:0% yeah so I want to do they like greatest 00:32:22.380 --> 00:32:25.540 align:start position:0% yeah so I want to do they like greatest man<00:32:22.830> contract<00:32:23.280> but<00:32:23.850> why<00:32:24.150> I<00:32:24.180> dislike<00:32:24.900> generate 00:32:25.540 --> 00:32:25.550 align:start position:0% man contract but why I dislike generate 00:32:25.550 --> 00:32:28.370 align:start position:0% man contract but why I dislike generate verifiable<00:32:26.550> this<00:32:27.210> basically<00:32:27.570> creates<00:32:27.960> what 00:32:28.370 --> 00:32:28.380 align:start position:0% verifiable this basically creates what 00:32:28.380 --> 00:32:30.110 align:start position:0% verifiable this basically creates what all<00:32:28.530> of<00:32:28.800> the<00:32:28.980> proof<00:32:29.220> that<00:32:29.250> we<00:32:29.580> need<00:32:29.730> to<00:32:29.910> push 00:32:30.110 --> 00:32:30.120 align:start position:0% all of the proof that we need to push 00:32:30.120 --> 00:32:33.710 align:start position:0% all of the proof that we need to push the<00:32:30.240> punches<00:32:30.660> like<00:32:31.530> if<00:32:31.770> you<00:32:31.920> guys<00:32:32.250> want<00:32:32.520> to<00:32:32.720> try 00:32:33.710 --> 00:32:33.720 align:start position:0% the punches like if you guys want to try 00:32:33.720 --> 00:32:36.970 align:start position:0% the punches like if you guys want to try this<00:32:33.840> out<00:32:34.110> and<00:32:34.410> maybe<00:32:34.860> we<00:32:35.130> can<00:32:35.310> do<00:32:35.700> that<00:32:35.730> now 00:32:36.970 --> 00:32:36.980 align:start position:0% this out and maybe we can do that now 00:32:36.980 --> 00:32:45.920 align:start position:0% this out and maybe we can do that now yeah<00:32:38.010> are<00:32:38.700> there<00:32:38.880> any<00:32:38.970> questions<00:32:39.890> this 00:32:45.920 --> 00:32:45.930 align:start position:0% 00:32:45.930 --> 00:32:49.510 align:start position:0% yes<00:32:46.500> Oh 00:32:49.510 --> 00:32:49.520 align:start position:0% 00:32:49.520 --> 00:33:05.520 align:start position:0% I<00:32:49.550> think 00:33:05.520 --> 00:33:05.530 align:start position:0% 00:33:05.530 --> 00:33:11.920 align:start position:0% this<00:33:05.830> link<00:33:06.520> of<00:33:06.670> the<00:33:06.820> wolf 00:33:11.920 --> 00:33:11.930 align:start position:0% 00:33:11.930 --> 00:33:27.750 align:start position:0% [Music] 00:33:27.750 --> 00:33:27.760 align:start position:0% 00:33:27.760 --> 00:33:38.650 align:start position:0% [Music] 00:33:38.650 --> 00:33:38.660 align:start position:0% 00:33:38.660 --> 00:33:55.890 align:start position:0% [Music] 00:33:55.890 --> 00:33:55.900 align:start position:0% 00:33:55.900 --> 00:33:58.840 align:start position:0% [Music] 00:33:58.840 --> 00:33:58.850 align:start position:0% [Music] 00:33:58.850 --> 00:34:04.760 align:start position:0% [Music] lady<00:33:59.850> Tommy 00:34:04.760 --> 00:34:04.770 align:start position:0% 00:34:04.770 --> 00:34:10.080 align:start position:0% a<00:34:05.770> burger<00:34:06.490> that<00:34:06.610> 20%<00:34:07.919> yeah<00:34:08.919> so<00:34:09.220> sometime<00:34:09.730> so 00:34:10.080 --> 00:34:10.090 align:start position:0% a burger that 20% yeah so sometime so 00:34:10.090 --> 00:34:13.500 align:start position:0% a burger that 20% yeah so sometime so that<00:34:10.120> basically<00:34:10.600> assigns<00:34:11.290> the<00:34:12.179> signal<00:34:13.179> value 00:34:13.500 --> 00:34:13.510 align:start position:0% that basically assigns the signal value 00:34:13.510 --> 00:34:26.520 align:start position:0% that basically assigns the signal value and<00:34:19.530> yeah<00:34:21.210> let's<00:34:22.210> say<00:34:23.159> signal<00:34:24.159> right<00:34:25.530> let's 00:34:26.520 --> 00:34:26.530 align:start position:0% and yeah let's say signal right let's 00:34:26.530 --> 00:34:29.820 align:start position:0% and yeah let's say signal right let's say<00:34:26.679> there<00:34:26.889> are<00:34:27.220> two<00:34:27.460> signals<00:34:28.240> a<00:34:28.659> and<00:34:28.840> B<00:34:29.020> and<00:34:29.649> I 00:34:29.820 --> 00:34:29.830 align:start position:0% say there are two signals a and B and I 00:34:29.830 --> 00:34:34.020 align:start position:0% say there are two signals a and B and I want<00:34:30.129> to<00:34:30.600> like<00:34:31.600> put<00:34:32.409> the<00:34:32.590> input<00:34:33.129> in<00:34:33.280> C<00:34:33.520> and<00:34:33.909> I 00:34:34.020 --> 00:34:34.030 align:start position:0% want to like put the input in C and I 00:34:34.030 --> 00:34:37.080 align:start position:0% want to like put the input in C and I want<00:34:34.060> to<00:34:34.389> make<00:34:34.929> sure<00:34:34.960> it<00:34:35.290> checks<00:34:36.159> like<00:34:36.790> there's 00:34:37.080 --> 00:34:37.090 align:start position:0% want to make sure it checks like there's 00:34:37.090 --> 00:34:39.300 align:start position:0% want to make sure it checks like there's a<00:34:37.179> constraint<00:34:37.570> that<00:34:37.780> C<00:34:38.260> should<00:34:38.500> always<00:34:38.770> equal 00:34:39.300 --> 00:34:39.310 align:start position:0% a constraint that C should always equal 00:34:39.310 --> 00:34:43.110 align:start position:0% a constraint that C should always equal a<00:34:39.580> plus<00:34:39.760> B<00:34:40.030> at<00:34:40.929> that<00:34:41.260> time<00:34:41.800> I<00:34:42.429> do<00:34:42.610> that<00:34:42.879> and 00:34:43.110 --> 00:34:43.120 align:start position:0% a plus B at that time I do that and 00:34:43.120 --> 00:34:47.430 align:start position:0% a plus B at that time I do that and bracket<00:34:43.480> and<00:34:43.600> equals<00:34:44.050> right<00:34:45.040> so<00:34:46.350> there's<00:34:47.350> a 00:34:47.430 --> 00:34:47.440 align:start position:0% bracket and equals right so there's a 00:34:47.440 --> 00:34:50.040 align:start position:0% bracket and equals right so there's a link<00:34:47.710> in<00:34:48.100> this<00:34:49.030> workshop<00:34:49.450> which<00:34:49.780> which 00:34:50.040 --> 00:34:50.050 align:start position:0% link in this workshop which which 00:34:50.050 --> 00:34:52.950 align:start position:0% link in this workshop which which basically<00:34:50.379> directs<00:34:50.919> -<00:34:51.190> I<00:34:51.550> did<00:34:52.240> three<00:34:52.360> slokas 00:34:52.950 --> 00:34:52.960 align:start position:0% basically directs - I did three slokas 00:34:52.960 --> 00:34:58.730 align:start position:0% basically directs - I did three slokas on<00:34:53.200> how<00:34:53.889> to<00:34:54.129> use<00:34:54.399> not<00:34:54.639> use<00:34:54.909> and<00:34:55.980> circum 00:34:58.730 --> 00:34:58.740 align:start position:0% on how to use not use and circum 00:34:58.740 --> 00:35:14.670 align:start position:0% on how to use not use and circum explanation<00:34:59.740> on<00:34:59.860> how<00:35:00.070> to<00:35:00.250> use<00:35:00.750> of<00:35:01.750> the 00:35:14.670 --> 00:35:14.680 align:start position:0% 00:35:14.680 --> 00:35:19.089 align:start position:0% this<00:35:15.680> is<00:35:16.430> level<00:35:16.789> 4<00:35:17.180> although<00:35:17.680> work<00:35:18.680> days<00:35:18.890> of 00:35:19.089 --> 00:35:19.099 align:start position:0% this is level 4 although work days of 00:35:19.099 --> 00:35:21.849 align:start position:0% this is level 4 although work days of the<00:35:19.250> sample<00:35:19.609> subjects<00:35:20.089> and<00:35:20.299> input<00:35:20.990> rousted 00:35:21.849 --> 00:35:21.859 align:start position:0% the sample subjects and input rousted 00:35:21.859 --> 00:35:30.490 align:start position:0% the sample subjects and input rousted files 00:35:30.490 --> 00:35:30.500 align:start position:0% 00:35:30.500 --> 00:35:31.809 align:start position:0% it's<00:35:30.829> going<00:35:30.980> to<00:35:31.069> be<00:35:31.160> enough<00:35:31.369> after<00:35:31.550> the 00:35:31.809 --> 00:35:31.819 align:start position:0% it's going to be enough after the 00:35:31.819 --> 00:35:41.690 align:start position:0% it's going to be enough after the conference 00:35:41.690 --> 00:35:41.700 align:start position:0% 00:35:41.700 --> 00:35:51.460 align:start position:0% everybody<00:35:42.180> else<00:35:42.359> learn<00:35:42.539> anything 00:35:51.460 --> 00:35:51.470 align:start position:0% 00:35:51.470 --> 00:35:57.430 align:start position:0% [Music] 00:35:57.430 --> 00:35:57.440 align:start position:0% 00:35:57.440 --> 00:36:07.160 align:start position:0% oh<00:35:57.640> sorry 00:36:07.160 --> 00:36:07.170 align:start position:0% 00:36:07.170 --> 00:36:11.160 align:start position:0% we<00:36:08.170> can<00:36:08.350> actually<00:36:08.760> you<00:36:09.760> might<00:36:10.240> people<00:36:10.420> you<00:36:11.020> can 00:36:11.160 --> 00:36:11.170 align:start position:0% we can actually you might people you can 00:36:11.170 --> 00:36:12.930 align:start position:0% we can actually you might people you can use<00:36:11.380> multiple<00:36:11.620> circuits<00:36:12.220> from<00:36:12.430> a<00:36:12.580> single 00:36:12.930 --> 00:36:12.940 align:start position:0% use multiple circuits from a single 00:36:12.940 --> 00:36:17.040 align:start position:0% use multiple circuits from a single circuit<00:36:13.240> so<00:36:13.720> for<00:36:14.040> multiple<00:36:15.150> projects<00:36:16.150> it's 00:36:17.040 --> 00:36:17.050 align:start position:0% circuit so for multiple projects it's 00:36:17.050 --> 00:36:20.400 align:start position:0% circuit so for multiple projects it's hard<00:36:17.290> to<00:36:17.500> know<00:36:18.400> what<00:36:18.880> for<00:36:19.330> the<00:36:19.480> for<00:36:20.110> single 00:36:20.400 --> 00:36:20.410 align:start position:0% hard to know what for the for single 00:36:20.410 --> 00:36:23.430 align:start position:0% hard to know what for the for single projects<00:36:20.740> have<00:36:21.400> to<00:36:21.520> give<00:36:22.290> intermediate<00:36:23.290> room 00:36:23.430 --> 00:36:23.440 align:start position:0% projects have to give intermediate room 00:36:23.440 --> 00:36:26.520 align:start position:0% projects have to give intermediate room after<00:36:23.980> after<00:36:24.490> processing<00:36:24.820> every<00:36:25.690> week<00:36:25.930> right 00:36:26.520 --> 00:36:26.530 align:start position:0% after after processing every week right 00:36:26.530 --> 00:36:33.300 align:start position:0% after after processing every week right so<00:36:27.100> just<00:36:27.280> putting<00:36:27.490> of<00:36:27.670> what<00:36:28.450> it<00:36:28.540> was<00:36:31.770> yeah<00:36:32.770> it 00:36:33.300 --> 00:36:33.310 align:start position:0% so just putting of what it was yeah it 00:36:33.310 --> 00:36:35.670 align:start position:0% so just putting of what it was yeah it gets<00:36:33.490> pretty<00:36:33.670> big<00:36:34.060> that's<00:36:34.510> why<00:36:34.720> did<00:36:34.870> not<00:36:34.990> we 00:36:35.670 --> 00:36:35.680 align:start position:0% gets pretty big that's why did not we 00:36:35.680 --> 00:36:42.140 align:start position:0% gets pretty big that's why did not we take<00:36:36.040> like<00:36:37.530> of<00:36:38.530> my 00:36:42.140 --> 00:36:42.150 align:start position:0% 00:36:42.150 --> 00:36:52.560 align:start position:0% with<00:36:43.150> the<00:36:43.300> balance<00:36:47.670> yes<00:36:48.670> definitely 00:36:52.560 --> 00:36:52.570 align:start position:0% 00:36:52.570 --> 00:36:58.710 align:start position:0% what<00:36:53.570> is<00:36:53.750> a<00:36:53.780> side<00:36:54.140> of<00:36:54.170> the<00:36:54.500> committee<00:36:57.070> for 00:36:58.710 --> 00:36:58.720 align:start position:0% what is a side of the committee for 00:36:58.720 --> 00:37:02.890 align:start position:0% what is a side of the committee for immediate<00:36:59.720> connection<00:37:00.880> it<00:37:01.880> is<00:37:02.060> in<00:37:02.330> especially 00:37:02.890 --> 00:37:02.900 align:start position:0% immediate connection it is in especially 00:37:02.900 --> 00:37:04.840 align:start position:0% immediate connection it is in especially I<00:37:03.200> don't<00:37:03.650> really<00:37:03.800> have<00:37:04.040> the<00:37:04.160> number<00:37:04.460> right<00:37:04.640> now 00:37:04.840 --> 00:37:04.850 align:start position:0% I don't really have the number right now 00:37:04.850 --> 00:37:15.340 align:start position:0% I don't really have the number right now but<00:37:05.650> yeah<00:37:06.650> there's<00:37:07.430> a<00:37:07.520> link<00:37:07.790> here<00:37:07.910> if<00:37:08.390> you<00:37:14.350> if 00:37:15.340 --> 00:37:15.350 align:start position:0% but yeah there's a link here if you if 00:37:15.350 --> 00:37:18.820 align:start position:0% but yeah there's a link here if you if you<00:37:15.530> if<00:37:15.800> you<00:37:15.980> want<00:37:16.160> to<00:37:16.220> check<00:37:16.610> how<00:37:17.830> different 00:37:18.820 --> 00:37:18.830 align:start position:0% you if you want to check how different 00:37:18.830 --> 00:37:21.400 align:start position:0% you if you want to check how different answers<00:37:19.160> book<00:37:19.310> there<00:37:19.730> are<00:37:19.760> is<00:37:20.240> is<00:37:20.630> it<00:37:20.810> an<00:37:20.990> input 00:37:21.400 --> 00:37:21.410 align:start position:0% answers book there are is is it an input 00:37:21.410 --> 00:37:26.860 align:start position:0% answers book there are is is it an input file<00:37:21.620> so<00:37:21.830> we<00:37:21.950> have<00:37:22.070> we<00:37:22.880> do<00:37:25.300> it<00:37:26.300> so<00:37:26.480> very<00:37:26.630> deep 00:37:26.860 --> 00:37:26.870 align:start position:0% file so we have we do it so very deep 00:37:26.870 --> 00:37:29.560 align:start position:0% file so we have we do it so very deep regenerating<00:37:27.650> Angie<00:37:27.920> today<00:37:28.310> yeah<00:37:29.030> yes<00:37:29.390> they 00:37:29.560 --> 00:37:29.570 align:start position:0% regenerating Angie today yeah yes they 00:37:29.570 --> 00:38:19.800 align:start position:0% regenerating Angie today yeah yes they are 00:38:19.800 --> 00:38:19.810 align:start position:0% 00:38:19.810 --> 00:38:24.720 align:start position:0% so<00:38:20.850> the<00:38:21.990> language<00:38:22.990> that<00:38:23.140> allows<00:38:23.530> us<00:38:23.590> to<00:38:23.800> verify 00:38:24.720 --> 00:38:24.730 align:start position:0% so the language that allows us to verify 00:38:24.730 --> 00:38:27.960 align:start position:0% so the language that allows us to verify the<00:38:24.790> pulse<00:38:25.120> energy<00:38:25.270> theorem<00:38:25.660> so<00:38:26.790> then<00:38:27.790> the 00:38:27.960 --> 00:38:27.970 align:start position:0% the pulse energy theorem so then the 00:38:27.970 --> 00:38:35.430 align:start position:0% the pulse energy theorem so then the last<00:38:28.270> step<00:38:28.600> over<00:38:28.870> here<00:38:29.820> if<00:38:30.820> you<00:38:33.480> if<00:38:34.480> you<00:38:34.660> this 00:38:35.430 --> 00:38:35.440 align:start position:0% last step over here if you if you this 00:38:35.440 --> 00:38:39.260 align:start position:0% last step over here if you if you this thing<00:38:35.680> then<00:38:36.580> it<00:38:36.670> really<00:38:36.880> create<00:38:37.210> a<00:38:37.360> verifier 00:38:39.260 --> 00:38:39.270 align:start position:0% thing then it really create a verifier 00:38:39.270 --> 00:38:41.850 align:start position:0% thing then it really create a verifier soil<00:38:40.270> it<00:38:40.360> agonic<00:38:40.750> for<00:38:40.960> now<00:38:41.050> and<00:38:41.380> then<00:38:41.740> you<00:38:41.830> can 00:38:41.850 --> 00:38:41.860 align:start position:0% soil it agonic for now and then you can 00:38:41.860 --> 00:38:44.490 align:start position:0% soil it agonic for now and then you can just<00:38:42.130> deploy<00:38:42.310> it<00:38:42.550> remix<00:38:42.910> and<00:38:43.210> take<00:38:44.200> the<00:38:44.320> loop 00:38:44.490 --> 00:38:44.500 align:start position:0% just deploy it remix and take the loop 00:38:44.500 --> 00:38:45.240 align:start position:0% just deploy it remix and take the loop so<00:38:44.680> each<00:38:44.830> part 00:38:45.240 --> 00:38:45.250 align:start position:0% so each part 00:38:45.250 --> 00:38:51.709 align:start position:0% so each part it's<00:38:45.580> not<00:38:45.790> easy 00:38:51.709 --> 00:38:51.719 align:start position:0% 00:38:51.719 --> 00:38:55.499 align:start position:0% yes<00:38:52.719> so<00:38:52.900> if<00:38:53.049> you<00:38:53.170> want<00:38:53.380> to<00:38:53.969> follow<00:38:54.969> along<00:38:55.150> it's 00:38:55.499 --> 00:38:55.509 align:start position:0% yes so if you want to follow along it's 00:38:55.509 --> 00:38:57.390 align:start position:0% yes so if you want to follow along it's like<00:38:55.989> pretty<00:38:56.410> simple<00:38:56.829> all<00:38:56.859> the<00:38:57.099> code<00:38:57.309> is 00:38:57.390 --> 00:38:57.400 align:start position:0% like pretty simple all the code is 00:38:57.400 --> 00:38:59.969 align:start position:0% like pretty simple all the code is present<00:38:57.729> here<00:38:57.869> you<00:38:58.869> just<00:38:59.019> have<00:38:59.199> to<00:38:59.319> move<00:38:59.440> but 00:38:59.969 --> 00:38:59.979 align:start position:0% present here you just have to move but 00:38:59.979 --> 00:39:03.509 align:start position:0% present here you just have to move but in<00:39:00.099> your<00:39:00.219> most<00:39:00.489> of<00:39:00.640> the<00:39:00.699> files<00:39:01.650> so<00:39:02.650> if<00:39:03.009> you<00:39:03.160> just 00:39:03.509 --> 00:39:03.519 align:start position:0% in your most of the files so if you just 00:39:03.519 --> 00:39:05.309 align:start position:0% in your most of the files so if you just clone<00:39:03.999> this<00:39:04.269> then<00:39:04.569> it<00:39:04.719> should<00:39:04.869> go<00:39:05.019> pretty<00:39:05.049> well 00:39:05.309 --> 00:39:05.319 align:start position:0% clone this then it should go pretty well 00:39:05.319 --> 00:39:09.329 align:start position:0% clone this then it should go pretty well for<00:39:05.619> you<00:39:05.880> on<00:39:07.079> this<00:39:08.079> and<00:39:08.440> this<00:39:08.650> link<00:39:08.890> is<00:39:08.979> valid 00:39:09.329 --> 00:39:09.339 align:start position:0% for you on this and this link is valid 00:39:09.339 --> 00:39:20.539 align:start position:0% for you on this and this link is valid into<00:39:09.609> both<00:39:09.819> departments<00:39:10.150> over<00:39:10.630> here 00:39:20.539 --> 00:39:20.549 align:start position:0% 00:39:20.549 --> 00:39:26.849 align:start position:0% yeah<00:39:22.170> well<00:39:23.170> I<00:39:24.119> can<00:39:25.119> be<00:39:25.240> mean<00:39:25.420> to<00:39:25.960> disbar 00:39:26.849 --> 00:39:26.859 align:start position:0% yeah well I can be mean to disbar 00:39:26.859 --> 00:39:51.610 align:start position:0% yeah well I can be mean to disbar quickly<00:39:27.279> do<00:39:27.609> this<00:39:27.819> show<00:39:28.390> how<00:39:28.960> it<00:39:29.140> works 00:39:51.610 --> 00:39:51.620 align:start position:0% 00:39:51.620 --> 00:39:59.550 align:start position:0% [Music] 00:39:59.550 --> 00:39:59.560 align:start position:0% 00:39:59.560 --> 00:40:05.690 align:start position:0% I<00:40:00.930> decided<00:40:01.930> to 00:40:05.690 --> 00:40:05.700 align:start position:0% 00:40:05.700 --> 00:40:09.990 align:start position:0% seriously<00:40:07.000> create<00:40:07.690> a<00:40:07.720> file<00:40:08.020> called<00:40:08.760> sake<00:40:09.760> not 00:40:09.990 --> 00:40:10.000 align:start position:0% seriously create a file called sake not 00:40:10.000 --> 00:40:15.630 align:start position:0% seriously create a file called sake not common<00:40:10.960> hobby<00:40:11.500> business 00:40:15.630 --> 00:40:15.640 align:start position:0% 00:40:15.640 --> 00:40:37.150 align:start position:0% over 00:40:37.150 --> 00:40:37.160 align:start position:0% 00:40:37.160 --> 00:40:45.939 align:start position:0% so<00:40:37.730> I<00:40:38.089> have<00:40:38.450> this<00:40:38.599> fight 00:40:45.939 --> 00:40:45.949 align:start position:0% 00:40:45.949 --> 00:40:49.219 align:start position:0% so<00:40:46.949> is<00:40:47.519> I<00:40:47.880> have<00:40:48.569> this<00:40:48.749> fight 00:40:49.219 --> 00:40:49.229 align:start position:0% so is I have this fight 00:40:49.229 --> 00:40:51.199 align:start position:0% so is I have this fight ready<00:40:49.589> now<00:40:49.769> I<00:40:49.979> just<00:40:50.189> have<00:40:50.459> to<00:40:50.609> do<00:40:50.759> the 00:40:51.199 --> 00:40:51.209 align:start position:0% ready now I just have to do the 00:40:51.209 --> 00:41:01.090 align:start position:0% ready now I just have to do the compilation<00:40:51.630> of<00:40:52.049> Korea 00:41:01.090 --> 00:41:01.100 align:start position:0% 00:41:01.100 --> 00:41:09.680 align:start position:0% [Music] 00:41:09.680 --> 00:41:09.690 align:start position:0% [Music] 00:41:09.690 --> 00:41:16.170 align:start position:0% [Music] it's<00:41:12.840> basically<00:41:13.840> the<00:41:14.560> isms<00:41:15.070> of<00:41:15.250> the<00:41:15.460> gun 00:41:16.170 --> 00:41:16.180 align:start position:0% it's basically the isms of the gun 00:41:16.180 --> 00:41:18.350 align:start position:0% it's basically the isms of the gun chains 00:41:18.350 --> 00:41:18.360 align:start position:0% chains 00:41:18.360 --> 00:41:24.510 align:start position:0% chains and<00:41:19.360> then<00:41:19.570> I<00:41:19.690> can<00:41:19.900> this<00:41:20.970> meaningless 00:41:24.510 --> 00:41:24.520 align:start position:0% 00:41:24.520 --> 00:41:25.859 align:start position:0% [Music] 00:41:25.859 --> 00:41:25.869 align:start position:0% [Music] 00:41:25.869 --> 00:41:27.749 align:start position:0% [Music] this<00:41:26.049> is<00:41:26.229> very<00:41:26.410> important<00:41:27.009> started<00:41:27.430> dissing 00:41:27.749 --> 00:41:27.759 align:start position:0% this is very important started dissing 00:41:27.759 --> 00:41:30.179 align:start position:0% this is very important started dissing for<00:41:27.939> me<00:41:28.059> it's<00:41:28.420> basically<00:41:28.630> the<00:41:29.049> way<00:41:29.079> was<00:41:29.439> ABC 00:41:30.179 --> 00:41:30.189 align:start position:0% for me it's basically the way was ABC 00:41:30.189 --> 00:41:35.249 align:start position:0% for me it's basically the way was ABC and<00:41:30.339> D<00:41:30.459> right<00:41:32.130> so<00:41:33.130> just<00:41:33.849> to<00:41:33.969> remind<00:41:34.660> you<00:41:34.959> we<00:41:35.170> are 00:41:35.249 --> 00:41:35.259 align:start position:0% and D right so just to remind you we are 00:41:35.259 --> 00:41:38.009 align:start position:0% and D right so just to remind you we are we<00:41:35.559> are<00:41:35.589> the<00:41:35.680> cutting<00:41:36.670> up<00:41:36.759> a<00:41:36.910> chain<00:41:37.150> that<00:41:37.390> is<00:41:37.869> I 00:41:38.009 --> 00:41:38.019 align:start position:0% we are the cutting up a chain that is I 00:41:38.019 --> 00:41:42.650 align:start position:0% we are the cutting up a chain that is I should<00:41:38.529> be<00:41:38.680> see 00:41:42.650 --> 00:41:42.660 align:start position:0% 00:41:42.660 --> 00:41:55.230 align:start position:0% [Music] 00:41:55.230 --> 00:41:55.240 align:start position:0% 00:41:55.240 --> 00:41:58.380 align:start position:0% so<00:41:56.010> calculate<00:41:57.010> witness<00:41:57.849> runs<00:41:58.150> correctly 00:41:58.380 --> 00:41:58.390 align:start position:0% so calculate witness runs correctly 00:41:58.390 --> 00:42:01.829 align:start position:0% so calculate witness runs correctly which<00:41:59.109> basically<00:41:59.500> means<00:41:59.859> that<00:42:00.720> we<00:42:01.720> are 00:42:01.829 --> 00:42:01.839 align:start position:0% which basically means that we are 00:42:01.839 --> 00:42:04.200 align:start position:0% which basically means that we are running<00:42:02.470> the<00:42:02.800> input<00:42:03.250> that<00:42:03.700> we<00:42:03.849> created 00:42:04.200 --> 00:42:04.210 align:start position:0% running the input that we created 00:42:04.210 --> 00:42:05.820 align:start position:0% running the input that we created against<00:42:04.660> all<00:42:04.780> the<00:42:04.960> constraints<00:42:05.380> and<00:42:05.650> the 00:42:05.820 --> 00:42:05.830 align:start position:0% against all the constraints and the 00:42:05.830 --> 00:42:08.280 align:start position:0% against all the constraints and the socket<00:42:06.550> then<00:42:07.119> it<00:42:07.270> basically<00:42:07.570> means<00:42:08.020> other 00:42:08.280 --> 00:42:08.290 align:start position:0% socket then it basically means other 00:42:08.290 --> 00:42:10.680 align:start position:0% socket then it basically means other proof<00:42:08.650> which<00:42:09.099> is<00:42:09.300> generated<00:42:10.300> would<00:42:10.450> most 00:42:10.680 --> 00:42:10.690 align:start position:0% proof which is generated would most 00:42:10.690 --> 00:42:14.339 align:start position:0% proof which is generated would most likely<00:42:10.930> be<00:42:11.200> correct<00:42:11.490> we<00:42:12.490> can<00:42:12.670> I<00:42:13.240> can<00:42:13.930> find 00:42:14.339 --> 00:42:14.349 align:start position:0% likely be correct we can I can find 00:42:14.349 --> 00:42:15.810 align:start position:0% likely be correct we can I can find changing<00:42:14.710> the<00:42:14.800> input<00:42:15.040> and<00:42:15.160> see<00:42:15.369> if<00:42:15.490> it<00:42:15.609> breaks 00:42:15.810 --> 00:42:15.820 align:start position:0% changing the input and see if it breaks 00:42:15.820 --> 00:42:29.660 align:start position:0% changing the input and see if it breaks right 00:42:29.660 --> 00:42:29.670 align:start position:0% 00:42:29.670 --> 00:42:32.599 align:start position:0% yeah<00:42:30.420> so<00:42:30.690> if<00:42:31.049> I<00:42:31.230> if<00:42:31.410> I<00:42:31.559> change<00:42:31.799> any<00:42:32.010> inputs<00:42:32.369> and 00:42:32.599 --> 00:42:32.609 align:start position:0% yeah so if I if I change any inputs and 00:42:32.609 --> 00:42:37.059 align:start position:0% yeah so if I if I change any inputs and you<00:42:32.819> must<00:42:33.089> be<00:42:33.240> don't<00:42:33.750> don't<00:42:34.349> eat<00:42:34.819> the<00:42:35.819> sea 00:42:37.059 --> 00:42:37.069 align:start position:0% you must be don't don't eat the sea 00:42:37.069 --> 00:42:40.010 align:start position:0% you must be don't don't eat the sea seething<00:42:38.069> then<00:42:38.339> it<00:42:39.270> will<00:42:39.420> be<00:42:39.540> series<00:42:39.780> to<00:42:39.960> show 00:42:40.010 --> 00:42:40.020 align:start position:0% seething then it will be series to show 00:42:40.020 --> 00:42:44.049 align:start position:0% seething then it will be series to show that<00:42:40.290> the<00:42:40.440> constraint<00:42:40.920> does<00:42:41.160> not<00:42:41.819> match<00:42:42.230> right 00:42:44.049 --> 00:42:44.059 align:start position:0% that the constraint does not match right 00:42:44.059 --> 00:42:49.280 align:start position:0% that the constraint does not match right so<00:42:46.099> you<00:42:47.099> can<00:42:47.250> do<00:42:47.339> the<00:42:47.460> same<00:42:48.119> thing<00:42:48.420> for<00:42:48.690> very 00:42:49.280 --> 00:42:49.290 align:start position:0% so you can do the same thing for very 00:42:49.290 --> 00:42:54.829 align:start position:0% so you can do the same thing for very fine<00:42:49.579> EBD<00:42:50.579> is<00:42:50.670> a<00:42:50.960> signature<00:42:52.010> ring<00:42:53.010> of<00:42:53.970> Motor 00:42:54.829 --> 00:42:54.839 align:start position:0% fine EBD is a signature ring of Motor 00:42:54.839 --> 00:42:58.339 align:start position:0% fine EBD is a signature ring of Motor Vehicles<00:42:55.260> like<00:42:56.270> proving<00:42:57.270> that<00:42:57.390> a<00:42:57.450> leaf<00:42:57.690> exists 00:42:58.339 --> 00:42:58.349 align:start position:0% Vehicles like proving that a leaf exists 00:42:58.349 --> 00:43:01.180 align:start position:0% Vehicles like proving that a leaf exists in<00:42:58.470> a<00:42:58.559> mockery<00:42:59.069> and<00:42:59.309> creating<00:42:59.700> a<00:42:59.790> muggle<00:43:00.150> rule 00:43:01.180 --> 00:43:01.190 align:start position:0% in a mockery and creating a muggle rule 00:43:01.190 --> 00:43:07.630 align:start position:0% in a mockery and creating a muggle rule all<00:43:02.190> of<00:43:02.250> that<00:43:02.520> stuff<00:43:04.430> yeah<00:43:05.430> I'm<00:43:06.359> gonna<00:43:06.540> try 00:43:07.630 --> 00:43:07.640 align:start position:0% all of that stuff yeah I'm gonna try 00:43:07.640 --> 00:43:10.329 align:start position:0% all of that stuff yeah I'm gonna try [Music] 00:43:10.329 --> 00:43:10.339 align:start position:0% [Music] 00:43:10.339 --> 00:43:14.329 align:start position:0% [Music] processing<00:43:11.339> a<00:43:11.430> single<00:43:11.790> transaction<00:43:13.040> and<00:43:14.040> so 00:43:14.329 --> 00:43:14.339 align:start position:0% processing a single transaction and so 00:43:14.339 --> 00:43:15.960 align:start position:0% processing a single transaction and so in<00:43:14.910> the<00:43:15.299> file<00:43:15.510> structure 00:43:15.960 --> 00:43:15.970 align:start position:0% in the file structure 00:43:15.970 --> 00:43:20.500 align:start position:0% in the file structure [Music] 00:43:20.500 --> 00:43:20.510 align:start position:0% 00:43:20.510 --> 00:43:24.339 align:start position:0% yes<00:43:21.320> you<00:43:21.619> if<00:43:22.190> people<00:43:22.339> do<00:43:22.730> the<00:43:23.660> fourth<00:43:23.930> folder 00:43:24.339 --> 00:43:24.349 align:start position:0% yes you if people do the fourth folder 00:43:24.349 --> 00:43:27.310 align:start position:0% yes you if people do the fourth folder or<00:43:24.589> single<00:43:24.980> yes<00:43:25.220> it<00:43:25.670> basically<00:43:26.540> has<00:43:27.079> the 00:43:27.310 --> 00:43:27.320 align:start position:0% or single yes it basically has the 00:43:27.320 --> 00:43:44.770 align:start position:0% or single yes it basically has the socket<00:43:27.950> and<00:43:28.450> yeah<00:43:39.910> it's<00:43:40.910> a<00:43:41.060> fire<00:43:41.270> code<00:43:43.660> and<00:43:44.660> it 00:43:44.770 --> 00:43:44.780 align:start position:0% socket and yeah it's a fire code and it 00:43:44.780 --> 00:43:46.660 align:start position:0% socket and yeah it's a fire code and it has<00:43:44.990> all<00:43:45.200> the<00:43:45.349> public<00:43:45.740> and<00:43:45.920> private<00:43:46.250> involves 00:43:46.660 --> 00:43:46.670 align:start position:0% has all the public and private involves 00:43:46.670 --> 00:43:59.030 align:start position:0% has all the public and private involves although<00:43:47.740> yeah<00:43:50.710> same<00:43:51.710> as<00:43:51.740> a 00:43:59.030 --> 00:43:59.040 align:start position:0% 00:43:59.040 --> 00:44:02.790 align:start position:0% you<00:44:00.040> need<00:44:00.250> to<00:44:00.640> provide<00:44:01.030> a<00:44:01.390> local<00:44:01.960> but<00:44:02.200> you<00:44:02.589> need 00:44:02.790 --> 00:44:02.800 align:start position:0% you need to provide a local but you need 00:44:02.800 --> 00:44:04.829 align:start position:0% you need to provide a local but you need to<00:44:02.890> provide<00:44:03.160> to<00:44:03.280> calculate<00:44:03.760> witness<00:44:04.089> to<00:44:04.630> get<00:44:04.810> a 00:44:04.829 --> 00:44:04.839 align:start position:0% to provide to calculate witness to get a 00:44:04.839 --> 00:44:14.460 align:start position:0% to provide to calculate witness to get a witness 00:44:14.460 --> 00:44:14.470 align:start position:0% 00:44:14.470 --> 00:44:16.740 align:start position:0% [Music] 00:44:16.740 --> 00:44:16.750 align:start position:0% [Music] 00:44:16.750 --> 00:44:21.710 align:start position:0% [Music] and<00:44:17.750> so<00:44:19.300> it<00:44:20.300> HUS 00:44:21.710 --> 00:44:21.720 align:start position:0% and so it HUS 00:44:21.720 --> 00:44:23.980 align:start position:0% and so it HUS just<00:44:22.230> the<00:44:22.500> numbers<00:44:22.800> they're<00:44:22.950> listed<00:44:23.280> here<00:44:23.310> I 00:44:23.980 --> 00:44:23.990 align:start position:0% just the numbers they're listed here I 00:44:23.990 --> 00:44:26.510 align:start position:0% just the numbers they're listed here I mean<00:44:24.990> they're<00:44:25.140> they<00:44:26.010> don't<00:44:26.190> really<00:44:26.340> they 00:44:26.510 --> 00:44:26.520 align:start position:0% mean they're they don't really they 00:44:26.520 --> 00:44:27.890 align:start position:0% mean they're they don't really they don't<00:44:26.820> need<00:44:27.090> anything<00:44:27.330> like<00:44:27.630> wherever 00:44:27.890 --> 00:44:27.900 align:start position:0% don't need anything like wherever 00:44:27.900 --> 00:44:29.060 align:start position:0% don't need anything like wherever they're<00:44:28.140> bad<00:44:28.290> enough<00:44:28.440> or<00:44:28.680> they're<00:44:28.800> kind<00:44:28.950> of 00:44:29.060 --> 00:44:29.070 align:start position:0% they're bad enough or they're kind of 00:44:29.070 --> 00:44:31.100 align:start position:0% they're bad enough or they're kind of like<00:44:29.220> random<00:44:29.550> but<00:44:29.760> yeah<00:44:30.240> link<00:44:30.540> to<00:44:30.690> this<00:44:30.840> thing 00:44:31.100 --> 00:44:31.110 align:start position:0% like random but yeah link to this thing 00:44:31.110 --> 00:44:33.110 align:start position:0% like random but yeah link to this thing is<00:44:31.290> because<00:44:31.650> short<00:44:32.070> you're<00:44:32.430> a<00:44:32.460> spacey<00:44:32.730> let's 00:44:33.110 --> 00:44:33.120 align:start position:0% is because short you're a spacey let's 00:44:33.120 --> 00:44:34.040 align:start position:0% is because short you're a spacey let's say<00:44:33.180> that<00:44:33.300> the<00:44:33.420> length<00:44:33.450> of<00:44:33.690> this<00:44:33.750> name<00:44:33.930> is 00:44:34.040 --> 00:44:34.050 align:start position:0% say that the length of this name is 00:44:34.050 --> 00:44:37.250 align:start position:0% say that the length of this name is short<00:44:34.290> because<00:44:34.590> it's<00:44:34.800> simply<00:44:35.130> I<00:44:36.260> just 00:44:37.250 --> 00:44:37.260 align:start position:0% short because it's simply I just 00:44:37.260 --> 00:44:38.590 align:start position:0% short because it's simply I just understand<00:44:37.800> like<00:44:37.950> the<00:44:38.100> length 00:44:38.590 --> 00:44:38.600 align:start position:0% understand like the length 00:44:38.600 --> 00:44:41.790 align:start position:0% understand like the length this<00:44:39.110> is<00:44:39.260> array<00:44:39.770> of<00:44:39.980> whatever<00:44:40.340> five<00:44:40.850> numbers 00:44:41.790 --> 00:44:41.800 align:start position:0% this is array of whatever five numbers 00:44:41.800 --> 00:44:44.260 align:start position:0% this is array of whatever five numbers as<00:44:42.800> young<00:44:43.040> as<00:44:43.190> the<00:44:43.310> survey<00:44:43.640> is<00:44:43.700> very<00:44:43.850> simple 00:44:44.260 --> 00:44:44.270 align:start position:0% as young as the survey is very simple 00:44:44.270 --> 00:44:47.470 align:start position:0% as young as the survey is very simple you<00:44:44.600> have<00:44:44.630> exactly<00:44:45.140> exactly<00:44:45.350> so<00:44:45.800> so<00:44:46.520> so<00:44:47.090> so 00:44:47.470 --> 00:44:47.480 align:start position:0% you have exactly exactly so so so so 00:44:47.480 --> 00:44:51.820 align:start position:0% you have exactly exactly so so so so what<00:44:47.750> of<00:44:47.870> okay<00:44:48.740> with<00:44:49.270> the<00:44:50.270> growth<00:44:51.170> plan<00:44:51.530> seems 00:44:51.820 --> 00:44:51.830 align:start position:0% what of okay with the growth plan seems 00:44:51.830 --> 00:44:54.310 align:start position:0% what of okay with the growth plan seems the<00:44:52.520> witness<00:44:52.910> is<00:44:53.030> vitamin<00:44:53.600> of<00:44:53.720> almost<00:44:54.140> similar 00:44:54.310 --> 00:44:54.320 align:start position:0% the witness is vitamin of almost similar 00:44:54.320 --> 00:44:57.280 align:start position:0% the witness is vitamin of almost similar to<00:44:54.500> take<00:44:55.430> one<00:44:55.810> given<00:44:56.810> on<00:44:56.960> the<00:44:57.020> number<00:44:57.230> of 00:44:57.280 --> 00:44:57.290 align:start position:0% to take one given on the number of 00:44:57.290 --> 00:44:59.800 align:start position:0% to take one given on the number of inputs<00:44:57.680> you<00:44:57.800> are<00:44:57.920> getting<00:44:58.160> and<00:44:58.700> this<00:44:59.690> is 00:44:59.800 --> 00:44:59.810 align:start position:0% inputs you are getting and this is 00:44:59.810 --> 00:45:03.280 align:start position:0% inputs you are getting and this is obviously<00:45:00.500> so<00:45:00.940> the<00:45:01.990> constraints<00:45:02.990> that<00:45:03.050> are 00:45:03.280 --> 00:45:03.290 align:start position:0% obviously so the constraints that are 00:45:03.290 --> 00:45:05.320 align:start position:0% obviously so the constraints that are there<00:45:03.500> versus<00:45:04.460> the<00:45:04.610> computation<00:45:05.300> that 00:45:05.320 --> 00:45:05.330 align:start position:0% there versus the computation that 00:45:05.330 --> 00:45:08.020 align:start position:0% there versus the computation that happens<00:45:05.810> like<00:45:06.170> how<00:45:06.410> does<00:45:06.470> that 00:45:08.020 --> 00:45:08.030 align:start position:0% happens like how does that 00:45:08.030 --> 00:45:11.110 align:start position:0% happens like how does that like<00:45:08.600> if<00:45:08.720> the<00:45:08.840> constraints<00:45:09.410> are<00:45:09.580> like<00:45:10.580> you 00:45:11.110 --> 00:45:11.120 align:start position:0% like if the constraints are like you 00:45:11.120 --> 00:45:13.120 align:start position:0% like if the constraints are like you know<00:45:11.210> for<00:45:11.570> example<00:45:11.600> communication<00:45:12.130> perhaps 00:45:13.120 --> 00:45:13.130 align:start position:0% know for example communication perhaps 00:45:13.130 --> 00:45:14.500 align:start position:0% know for example communication perhaps you<00:45:13.250> said<00:45:13.490> I<00:45:13.700> mean<00:45:13.850> I<00:45:13.970> there's<00:45:14.210> lots<00:45:14.420> of 00:45:14.500 --> 00:45:14.510 align:start position:0% you said I mean I there's lots of 00:45:14.510 --> 00:45:15.970 align:start position:0% you said I mean I there's lots of commutation<00:45:15.080> there<00:45:15.530> but<00:45:15.710> there's<00:45:15.830> very 00:45:15.970 --> 00:45:15.980 align:start position:0% commutation there but there's very 00:45:15.980 --> 00:45:17.950 align:start position:0% commutation there but there's very little<00:45:16.190> logical<00:45:16.790> constructs<00:45:17.180> about<00:45:17.540> language 00:45:17.950 --> 00:45:17.960 align:start position:0% little logical constructs about language 00:45:17.960 --> 00:45:20.010 align:start position:0% little logical constructs about language sites<00:45:18.230> the<00:45:18.950> assertions<00:45:19.400> that<00:45:19.580> you<00:45:19.670> make 00:45:20.010 --> 00:45:20.020 align:start position:0% sites the assertions that you make 00:45:20.020 --> 00:45:22.280 align:start position:0% sites the assertions that you make like<00:45:20.890> here<00:45:21.190> you<00:45:21.310> have<00:45:21.400> assertions<00:45:21.880> tonight 00:45:22.280 --> 00:45:22.290 align:start position:0% like here you have assertions tonight 00:45:22.290 --> 00:45:25.050 align:start position:0% like here you have assertions tonight about<00:45:23.290> those<00:45:23.710> arguments<00:45:24.130> but<00:45:24.490> then<00:45:24.670> you<00:45:24.880> dope 00:45:25.050 --> 00:45:25.060 align:start position:0% about those arguments but then you dope 00:45:25.060 --> 00:45:28.230 align:start position:0% about those arguments but then you dope you<00:45:25.150> main<00:45:25.360> produce<00:45:26.010> like<00:45:27.010> bindings<00:45:27.730> inside<00:45:27.970> of 00:45:28.230 --> 00:45:28.240 align:start position:0% you main produce like bindings inside of 00:45:28.240 --> 00:45:30.690 align:start position:0% you main produce like bindings inside of a<00:45:28.300> circuit<00:45:28.720> to<00:45:28.960> like<00:45:29.110> buy<00:45:29.530> new<00:45:29.980> variables<00:45:30.460> and 00:45:30.690 --> 00:45:30.700 align:start position:0% a circuit to like buy new variables and 00:45:30.700 --> 00:45:32.910 align:start position:0% a circuit to like buy new variables and say<00:45:30.820> they're<00:45:30.970> like<00:45:31.060> pulse<00:45:31.360> of<00:45:31.510> this<00:45:31.740> so<00:45:32.740> like 00:45:32.910 --> 00:45:32.920 align:start position:0% say they're like pulse of this so like 00:45:32.920 --> 00:45:35.310 align:start position:0% say they're like pulse of this so like does<00:45:33.369> that<00:45:33.430> make<00:45:33.670> sense<00:45:33.700> like<00:45:34.150> when<00:45:35.050> you<00:45:35.140> make 00:45:35.310 --> 00:45:35.320 align:start position:0% does that make sense like when you make 00:45:35.320 --> 00:45:37.020 align:start position:0% does that make sense like when you make circuits<00:45:35.650> like<00:45:35.740> visitors<00:45:36.190> like<00:45:36.400> what 00:45:37.020 --> 00:45:37.030 align:start position:0% circuits like visitors like what 00:45:37.030 --> 00:45:40.050 align:start position:0% circuits like visitors like what constraints<00:45:37.780> on<00:45:37.960> things<00:45:38.710> matter<00:45:39.369> versus<00:45:39.880> like 00:45:40.050 --> 00:45:40.060 align:start position:0% constraints on things matter versus like 00:45:40.060 --> 00:45:43.500 align:start position:0% constraints on things matter versus like just<00:45:40.330> raw<00:45:40.510> computation<00:45:41.260> really<00:45:42.060> yeah<00:45:43.060> so<00:45:43.330> like 00:45:43.500 --> 00:45:43.510 align:start position:0% just raw computation really yeah so like 00:45:43.510 --> 00:45:49.930 align:start position:0% just raw computation really yeah so like every<00:45:44.220> you<00:45:45.220> will<00:45:45.369> know<00:45:45.460> it<00:45:47.340> so<00:45:48.340> let<00:45:48.490> me<00:45:48.520> request 00:45:49.930 --> 00:45:49.940 align:start position:0% every you will know it so let me request 00:45:49.940 --> 00:45:52.150 align:start position:0% every you will know it so let me request so<00:45:50.900> why<00:45:51.079> you<00:45:51.140> trying<00:45:51.410> to<00:45:51.470> get<00:45:51.799> an<00:45:51.890> intuition 00:45:52.150 --> 00:45:52.160 align:start position:0% so why you trying to get an intuition 00:45:52.160 --> 00:45:55.569 align:start position:0% so why you trying to get an intuition for<00:45:52.490> like<00:45:53.470> his<00:45:54.470> idea<00:45:54.770> of<00:45:54.829> Constraints<00:45:55.400> my 00:45:55.569 --> 00:45:55.579 align:start position:0% for like his idea of Constraints my 00:45:55.579 --> 00:46:00.309 align:start position:0% for like his idea of Constraints my company<00:45:58.059> versus<00:45:59.059> like<00:45:59.299> raw<00:45:59.599> computation 00:46:00.309 --> 00:46:00.319 align:start position:0% company versus like raw computation 00:46:00.319 --> 00:46:01.720 align:start position:0% company versus like raw computation error<00:46:00.470> so<00:46:00.740> like<00:46:00.890> I<00:46:01.069> could<00:46:01.220> say<00:46:01.339> something<00:46:01.579> like 00:46:01.720 --> 00:46:01.730 align:start position:0% error so like I could say something like 00:46:01.730 --> 00:46:03.670 align:start position:0% error so like I could say something like a<00:46:02.119> Gillette<00:46:02.690> binding<00:46:03.140> in<00:46:03.319> this<00:46:03.440> language 00:46:03.670 --> 00:46:03.680 align:start position:0% a Gillette binding in this language 00:46:03.680 --> 00:46:05.170 align:start position:0% a Gillette binding in this language where<00:46:04.039> everyone<00:46:04.400> says<00:46:04.549> like<00:46:04.700> let<00:46:04.940> a<00:46:04.970> equal 00:46:05.170 --> 00:46:05.180 align:start position:0% where everyone says like let a equal 00:46:05.180 --> 00:46:09.039 align:start position:0% where everyone says like let a equal hash<00:46:06.109> of<00:46:06.470> these<00:46:06.680> things<00:46:06.950> versus<00:46:07.549> like<00:46:07.789> a<00:46:08.049> plus 00:46:09.039 --> 00:46:09.049 align:start position:0% hash of these things versus like a plus 00:46:09.049 --> 00:46:13.270 align:start position:0% hash of these things versus like a plus B<00:46:09.289> equals<00:46:09.319> C<00:46:09.859> is<00:46:10.490> like<00:46:10.670> they're<00:46:10.849> searching<00:46:12.280> so 00:46:13.270 --> 00:46:13.280 align:start position:0% B equals C is like they're searching so 00:46:13.280 --> 00:46:17.589 align:start position:0% B equals C is like they're searching so you<00:46:13.549> want<00:46:13.789> to<00:46:13.880> see<00:46:14.119> what<00:46:15.400> diminishment<00:46:16.400> yes<00:46:16.970> so 00:46:17.589 --> 00:46:17.599 align:start position:0% you want to see what diminishment yes so 00:46:17.599 --> 00:46:24.140 align:start position:0% you want to see what diminishment yes so with 00:46:24.140 --> 00:46:24.150 align:start position:0% 00:46:24.150 --> 00:46:26.180 align:start position:0% yeah<00:46:24.780> it's<00:46:24.930> just<00:46:24.990> like<00:46:25.170> come<00:46:25.470> yet<00:46:25.680> I<00:46:25.830> mean<00:46:26.070> in 00:46:26.180 --> 00:46:26.190 align:start position:0% yeah it's just like come yet I mean in 00:46:26.190 --> 00:46:28.070 align:start position:0% yeah it's just like come yet I mean in some<00:46:26.820> languages<00:46:27.270> it<00:46:27.450> takes<00:46:27.630> longer<00:46:27.870> but 00:46:28.070 --> 00:46:28.080 align:start position:0% some languages it takes longer but 00:46:28.080 --> 00:46:29.280 align:start position:0% some languages it takes longer but that's<00:46:28.200> just<00:46:28.350> a<00:46:28.530> girl 00:46:29.280 --> 00:46:29.290 align:start position:0% that's just a girl 00:46:29.290 --> 00:46:32.620 align:start position:0% that's just a girl but<00:46:30.290> like<00:46:30.530> when<00:46:30.710> you<00:46:30.830> when<00:46:31.070> you<00:46:31.190> get<00:46:31.370> off<00:46:31.630> it's 00:46:32.620 --> 00:46:32.630 align:start position:0% but like when you when you get off it's 00:46:32.630 --> 00:46:39.850 align:start position:0% but like when you when you get off it's always 00:46:39.850 --> 00:46:39.860 align:start position:0% 00:46:39.860 --> 00:46:42.010 align:start position:0% yeah<00:46:40.160> so<00:46:40.430> it's<00:46:40.850> like<00:46:41.030> if<00:46:41.180> you<00:46:41.270> had<00:46:41.420> a<00:46:41.450> Dex<00:46:41.750> you 00:46:42.010 --> 00:46:42.020 align:start position:0% yeah so it's like if you had a Dex you 00:46:42.020 --> 00:46:45.010 align:start position:0% yeah so it's like if you had a Dex you would<00:46:42.440> spend<00:46:42.710> like<00:46:43.540> 0.0001<00:46:44.540> percent<00:46:44.570> of<00:46:44.930> your 00:46:45.010 --> 00:46:45.020 align:start position:0% would spend like 0.0001 percent of your 00:46:45.020 --> 00:46:46.540 align:start position:0% would spend like 0.0001 percent of your time<00:46:45.230> how<00:46:45.860> big<00:46:46.100> it<00:46:46.370> is 00:46:46.540 --> 00:46:46.550 align:start position:0% time how big it is 00:46:46.550 --> 00:46:54.490 align:start position:0% time how big it is always 00:46:54.490 --> 00:46:54.500 align:start position:0% 00:46:54.500 --> 00:46:59.140 align:start position:0% yeah<00:46:55.070> so<00:46:55.510> can<00:46:56.510> we<00:46:56.810> do<00:46:57.770> this<00:46:57.800> same<00:46:58.700> thing<00:46:58.760> we 00:46:59.140 --> 00:46:59.150 align:start position:0% yeah so can we do this same thing we 00:46:59.150 --> 00:47:02.290 align:start position:0% yeah so can we do this same thing we just<00:46:59.359> have<00:46:59.630> to<00:46:59.750> write<00:47:00.230> and<00:47:00.470> use<00:47:00.619> sake<00:47:01.220> but<00:47:02.090> that 00:47:02.290 --> 00:47:02.300 align:start position:0% just have to write and use sake but that 00:47:02.300 --> 00:47:04.359 align:start position:0% just have to write and use sake but that we<00:47:02.450> defined<00:47:02.750> in<00:47:02.840> the<00:47:02.869> previous<00:47:02.960> parts<00:47:03.619> and<00:47:03.830> we 00:47:04.359 --> 00:47:04.369 align:start position:0% we defined in the previous parts and we 00:47:04.369 --> 00:47:09.210 align:start position:0% we defined in the previous parts and we really<00:47:04.970> have<00:47:05.090> to<00:47:05.770> check<00:47:06.770> the<00:47:07.270> center's<00:47:08.270> leave 00:47:09.210 --> 00:47:09.220 align:start position:0% really have to check the center's leave 00:47:09.220 --> 00:47:12.609 align:start position:0% really have to check the center's leave receivers<00:47:10.220> II<00:47:10.490> the<00:47:11.000> balances<00:47:11.540> and<00:47:12.170> we<00:47:12.320> need<00:47:12.470> to 00:47:12.609 --> 00:47:12.619 align:start position:0% receivers II the balances and we need to 00:47:12.619 --> 00:47:18.040 align:start position:0% receivers II the balances and we need to update<00:47:13.220> the<00:47:15.280> two<00:47:16.280> like<00:47:16.520> posting<00:47:17.510> a<00:47:17.599> single 00:47:18.040 --> 00:47:18.050 align:start position:0% update the two like posting a single 00:47:18.050 --> 00:47:20.730 align:start position:0% update the two like posting a single transaction 00:47:20.730 --> 00:47:20.740 align:start position:0% 00:47:20.740 --> 00:47:23.130 align:start position:0% you<00:47:21.250> guys<00:47:21.460> can<00:47:21.670> try<00:47:21.849> out<00:47:22.089> the<00:47:22.300> best<00:47:22.630> parts<00:47:22.960> and 00:47:23.130 --> 00:47:23.140 align:start position:0% you guys can try out the best parts and 00:47:23.140 --> 00:47:48.420 align:start position:0% you guys can try out the best parts and I'll<00:47:23.470> be<00:47:23.650> here<00:47:23.829> do<00:47:24.010> a<00:47:24.280> twirl 00:47:48.420 --> 00:47:48.430 align:start position:0% 00:47:48.430 --> 00:48:05.100 align:start position:0% [Music] 00:48:05.100 --> 00:48:05.110 align:start position:0% 00:48:05.110 --> 00:48:12.320 align:start position:0% the<00:48:05.440> same<00:48:05.790> circuit<00:48:06.790> that<00:48:07.090> was<00:48:07.300> present<00:48:08.080> in<00:48:08.140> the 00:48:12.320 --> 00:48:12.330 align:start position:0% 00:48:12.330 --> 00:48:20.930 align:start position:0% website<00:48:13.330> so<00:48:13.930> I<00:48:14.230> just<00:48:14.560> like<00:48:14.710> of<00:48:15.400> us<00:48:15.670> today<00:48:18.000> as<00:48:19.000> to 00:48:20.930 --> 00:48:20.940 align:start position:0% website so I just like of us today as to 00:48:20.940 --> 00:48:25.290 align:start position:0% website so I just like of us today as to st.<00:48:21.940> amounts<00:48:22.830> and<00:48:23.830> I<00:48:24.100> just<00:48:24.430> go<00:48:24.880> through<00:48:24.910> how<00:48:25.270> to 00:48:25.290 --> 00:48:25.300 align:start position:0% st. amounts and I just go through how to 00:48:25.300 --> 00:48:27.420 align:start position:0% st. amounts and I just go through how to create<00:48:25.570> the<00:48:25.780> inputs<00:48:26.170> for<00:48:26.350> this<00:48:26.530> and<00:48:27.220> then 00:48:27.420 --> 00:48:27.430 align:start position:0% create the inputs for this and then 00:48:27.430 --> 00:48:39.009 align:start position:0% create the inputs for this and then maybe<00:48:28.000> you<00:48:28.180> guys<00:48:28.360> can<00:48:28.540> write 00:48:39.009 --> 00:48:39.019 align:start position:0% 00:48:39.019 --> 00:48:42.349 align:start position:0% for<00:48:40.019> this<00:48:40.109> workshop<00:48:40.859> is<00:48:41.039> basically<00:48:41.849> created<00:48:42.299> a 00:48:42.349 --> 00:48:42.359 align:start position:0% for this workshop is basically created a 00:48:42.359 --> 00:48:44.660 align:start position:0% for this workshop is basically created a script<00:48:42.599> with<00:48:42.869> it's<00:48:43.170> like<00:48:43.319> 10<00:48:43.740> it's<00:48:43.950> the<00:48:44.039> input 00:48:44.660 --> 00:48:44.670 align:start position:0% script with it's like 10 it's the input 00:48:44.670 --> 00:48:46.940 align:start position:0% script with it's like 10 it's the input for<00:48:44.940> your<00:48:45.559> sake 00:48:46.940 --> 00:48:46.950 align:start position:0% for your sake 00:48:46.950 --> 00:48:49.460 align:start position:0% for your sake so<00:48:47.460> we<00:48:47.640> basically<00:48:47.880> here<00:48:48.599> create<00:48:49.259> a<00:48:49.440> new 00:48:49.460 --> 00:48:49.470 align:start position:0% so we basically here create a new 00:48:49.470 --> 00:48:51.440 align:start position:0% so we basically here create a new private<00:48:49.890> key<00:48:50.220> and<00:48:50.339> we<00:48:50.460> declared<00:48:50.880> it<00:48:50.999> that<00:48:51.269> it's 00:48:51.440 --> 00:48:51.450 align:start position:0% private key and we declared it that it's 00:48:51.450 --> 00:48:53.660 align:start position:0% private key and we declared it that it's Alice's<00:48:51.960> private<00:48:52.109> key<00:48:52.319> and<00:48:52.619> we<00:48:53.190> create<00:48:53.400> a<00:48:53.430> box 00:48:53.660 --> 00:48:53.670 align:start position:0% Alice's private key and we create a box 00:48:53.670 --> 00:48:55.730 align:start position:0% Alice's private key and we create a box private<00:48:54.089> key<00:48:54.269> right<00:48:54.630> and<00:48:55.049> we<00:48:55.259> have<00:48:55.410> palaces 00:48:55.730 --> 00:48:55.740 align:start position:0% private key right and we have palaces 00:48:55.740 --> 00:48:58.039 align:start position:0% private key right and we have palaces property<00:48:56.339> we<00:48:56.759> have<00:48:56.849> both<00:48:57.119> puppy<00:48:57.630> and<00:48:57.809> we<00:48:57.930> are 00:48:58.039 --> 00:48:58.049 align:start position:0% property we have both puppy and we are 00:48:58.049 --> 00:49:00.980 align:start position:0% property we have both puppy and we are basically<00:48:58.470> using<00:48:58.859> these<00:48:59.490> two<00:48:59.749> helper<00:49:00.749> files 00:49:00.980 --> 00:49:00.990 align:start position:0% basically using these two helper files 00:49:00.990 --> 00:49:05.390 align:start position:0% basically using these two helper files from<00:49:01.460> sagami-ya<00:49:03.079> and<00:49:04.079> we<00:49:04.440> basically<00:49:04.890> created 00:49:05.390 --> 00:49:05.400 align:start position:0% from sagami-ya and we basically created 00:49:05.400 --> 00:49:07.579 align:start position:0% from sagami-ya and we basically created a<00:49:05.490> bound<00:49:05.730> for<00:49:05.880> Alice<00:49:06.420> and<00:49:06.690> Nikita<00:49:07.319> come 00:49:07.579 --> 00:49:07.589 align:start position:0% a bound for Alice and Nikita come 00:49:07.589 --> 00:49:11.269 align:start position:0% a bound for Alice and Nikita come forward<00:49:08.069> and<00:49:08.609> we<00:49:09.230> hash<00:49:10.230> the<00:49:10.259> puppies<00:49:10.890> and<00:49:11.220> the 00:49:11.269 --> 00:49:11.279 align:start position:0% forward and we hash the puppies and the 00:49:11.279 --> 00:49:13.539 align:start position:0% forward and we hash the puppies and the balance<00:49:11.609> is<00:49:11.700> together<00:49:12.029> as<00:49:12.509> it<00:49:12.720> was<00:49:12.900> during<00:49:13.259> the 00:49:13.539 --> 00:49:13.549 align:start position:0% balance is together as it was during the 00:49:13.549 --> 00:49:19.099 align:start position:0% balance is together as it was during the tutorial<00:49:14.549> right<00:49:14.910> and<00:49:15.269> we<00:49:15.359> used<00:49:15.539> in<00:49:16.410> C<00:49:16.970> and<00:49:18.109> then 00:49:19.099 --> 00:49:19.109 align:start position:0% tutorial right and we used in C and then 00:49:19.109 --> 00:49:22.970 align:start position:0% tutorial right and we used in C and then we<00:49:19.230> greater<00:49:19.440> leave<00:49:20.420> account<00:49:21.420> for<00:49:21.630> Bo<00:49:22.319> and<00:49:22.799> we 00:49:22.970 --> 00:49:22.980 align:start position:0% we greater leave account for Bo and we 00:49:22.980 --> 00:49:27.829 align:start position:0% we greater leave account for Bo and we create<00:49:23.190> a<00:49:23.220> DFAS<00:49:23.900> provoke<00:49:25.069> and<00:49:26.069> we<00:49:26.509> and<00:49:27.509> we<00:49:27.539> will 00:49:27.829 --> 00:49:27.839 align:start position:0% create a DFAS provoke and we and we will 00:49:27.839 --> 00:49:30.559 align:start position:0% create a DFAS provoke and we and we will disagree<00:49:28.109> tenets<00:49:28.559> of<00:49:29.089> initial<00:49:30.089> account<00:49:30.329> root 00:49:30.559 --> 00:49:30.569 align:start position:0% disagree tenets of initial account root 00:49:30.569 --> 00:49:33.559 align:start position:0% disagree tenets of initial account root for<00:49:31.049> both<00:49:31.289> the<00:49:31.440> circle<00:49:31.740> so<00:49:32.309> since<00:49:33.210> it's<00:49:33.420> only 00:49:33.559 --> 00:49:33.569 align:start position:0% for both the circle so since it's only 00:49:33.569 --> 00:49:35.120 align:start position:0% for both the circle so since it's only two<00:49:33.809> account<00:49:34.140> which<00:49:34.529> need<00:49:34.799> to<00:49:34.920> package 00:49:35.120 --> 00:49:35.130 align:start position:0% two account which need to package 00:49:35.130 --> 00:49:39.980 align:start position:0% two account which need to package together<00:49:35.430> we<00:49:35.880> get<00:49:36.029> out<00:49:36.210> mother<00:49:37.019> aside<00:49:38.900> then<00:49:39.900> we 00:49:39.980 --> 00:49:39.990 align:start position:0% together we get out mother aside then we 00:49:39.990 --> 00:49:42.620 align:start position:0% together we get out mother aside then we need<00:49:40.140> to<00:49:40.289> do<00:49:40.380> a<00:49:40.410> simple<00:49:40.710> transaction<00:49:41.460> and<00:49:41.880> from 00:49:42.620 --> 00:49:42.630 align:start position:0% need to do a simple transaction and from 00:49:42.630 --> 00:49:47.059 align:start position:0% need to do a simple transaction and from Alice<00:49:43.049> to<00:49:43.289> Bob<00:49:43.970> and<00:49:45.109> Alice<00:49:46.109> needs<00:49:46.589> to<00:49:46.859> sign 00:49:47.059 --> 00:49:47.069 align:start position:0% Alice to Bob and Alice needs to sign 00:49:47.069 --> 00:49:50.180 align:start position:0% Alice to Bob and Alice needs to sign that<00:49:47.309> connection<00:49:48.180> so<00:49:48.809> we<00:49:48.839> sent<00:49:49.739> our<00:49:49.859> private 00:49:50.180 --> 00:49:50.190 align:start position:0% that connection so we sent our private 00:49:50.190 --> 00:49:53.979 align:start position:0% that connection so we sent our private key<00:49:50.339> over<00:49:50.460> here<00:49:50.489> and<00:49:50.849> we<00:49:50.970> get<00:49:51.089> a<00:49:51.650> signature<00:49:52.650> you 00:49:53.979 --> 00:49:53.989 align:start position:0% key over here and we get a signature you 00:49:53.989 --> 00:49:57.609 align:start position:0% key over here and we get a signature you that<00:49:54.989> we<00:49:55.140> generate<00:49:55.410> a<00:49:55.440> new 00:49:57.609 --> 00:49:57.619 align:start position:0% that we generate a new 00:49:57.619 --> 00:50:02.960 align:start position:0% that we generate a new this<00:49:58.619> first<00:49:59.099> visit<00:50:00.059> like<00:50:00.480> to<00:50:00.869> send<00:50:01.849> 500<00:50:02.849> to 00:50:02.960 --> 00:50:02.970 align:start position:0% this first visit like to send 500 to 00:50:02.970 --> 00:50:06.589 align:start position:0% this first visit like to send 500 to with<00:50:03.150> year<00:50:03.530> list<00:50:04.730> in<00:50:05.730> the<00:50:05.940> previous<00:50:06.329> state 00:50:06.589 --> 00:50:06.599 align:start position:0% with year list in the previous state 00:50:06.599 --> 00:50:09.950 align:start position:0% with year list in the previous state state<00:50:06.990> or<00:50:07.200> our<00:50:07.470> heart<00:50:08.270> 500<00:50:09.270> organs<00:50:09.630> and 00:50:09.950 --> 00:50:09.960 align:start position:0% state or our heart 500 organs and 00:50:09.960 --> 00:50:13.760 align:start position:0% state or our heart 500 organs and bobcats<00:50:10.650> 0<00:50:11.460> so<00:50:12.240> after<00:50:12.809> transferring<00:50:13.260> Alice 00:50:13.760 --> 00:50:13.770 align:start position:0% bobcats 0 so after transferring Alice 00:50:13.770 --> 00:50:18.109 align:start position:0% bobcats 0 so after transferring Alice should<00:50:14.400> have<00:50:14.839> 0<00:50:15.839> right<00:50:16.770> so<00:50:17.040> being<00:50:17.640> with<00:50:17.970> the 00:50:18.109 --> 00:50:18.119 align:start position:0% should have 0 right so being with the 00:50:18.119 --> 00:50:20.510 align:start position:0% should have 0 right so being with the intermediate<00:50:18.750> route<00:50:18.900> as<00:50:19.859> soon<00:50:20.010> as<00:50:20.130> we<00:50:20.250> process 00:50:20.510 --> 00:50:20.520 align:start position:0% intermediate route as soon as we process 00:50:20.520 --> 00:50:23.450 align:start position:0% intermediate route as soon as we process a<00:50:20.700> leaf<00:50:20.940> we<00:50:21.359> need<00:50:21.900> to<00:50:22.020> create<00:50:22.460> intermediate 00:50:23.450 --> 00:50:23.460 align:start position:0% a leaf we need to create intermediate 00:50:23.460 --> 00:50:26.950 align:start position:0% a leaf we need to create intermediate room<00:50:23.640> so<00:50:24.210> that<00:50:24.390> is<00:50:25.290> is<00:50:25.589> not<00:50:25.619> able<00:50:26.040> to<00:50:26.099> spend<00:50:26.490> the 00:50:26.950 --> 00:50:26.960 align:start position:0% room so that is is not able to spend the 00:50:26.960 --> 00:50:28.520 align:start position:0% room so that is is not able to spend the 500<00:50:27.960> tokens 00:50:28.520 --> 00:50:28.530 align:start position:0% 500 tokens 00:50:28.530 --> 00:50:31.339 align:start position:0% 500 tokens she<00:50:28.799> spent<00:50:29.130> earlier<00:50:29.460> again<00:50:29.849> right<00:50:30.720> so<00:50:31.020> we 00:50:31.339 --> 00:50:31.349 align:start position:0% she spent earlier again right so we 00:50:31.349 --> 00:50:35.120 align:start position:0% she spent earlier again right so we create<00:50:31.559> a<00:50:31.650> new<00:50:32.119> be<00:50:33.119> so<00:50:34.020> agreed<00:50:34.319> a<00:50:34.349> new<00:50:34.589> leaf<00:50:34.890> ash 00:50:35.120 --> 00:50:35.130 align:start position:0% create a new be so agreed a new leaf ash 00:50:35.130 --> 00:50:37.670 align:start position:0% create a new be so agreed a new leaf ash and<00:50:35.849> we<00:50:36.059> declare<00:50:36.299> it<00:50:36.569> as<00:50:36.720> the<00:50:36.930> intermediate 00:50:37.670 --> 00:50:37.680 align:start position:0% and we declare it as the intermediate 00:50:37.680 --> 00:50:38.410 align:start position:0% and we declare it as the intermediate room 00:50:38.410 --> 00:50:38.420 align:start position:0% room 00:50:38.420 --> 00:50:43.000 align:start position:0% room then<00:50:39.420> he<00:50:39.510> update<00:50:40.349> though<00:50:40.559> Bob<00:50:41.490> succumb<00:50:41.880> right 00:50:43.000 --> 00:50:43.010 align:start position:0% then he update though Bob succumb right 00:50:43.010 --> 00:50:46.640 align:start position:0% then he update though Bob succumb right with<00:50:44.010> the<00:50:44.130> money<00:50:44.309> he<00:50:44.490> got<00:50:44.640> from<00:50:44.790> Alice<00:50:45.119> and<00:50:45.960> we 00:50:46.640 --> 00:50:46.650 align:start position:0% with the money he got from Alice and we 00:50:46.650 --> 00:50:49.849 align:start position:0% with the money he got from Alice and we did<00:50:46.859> a<00:50:47.780> great<00:50:48.780> early<00:50:48.900> match<00:50:49.230> for<00:50:49.440> it<00:50:49.559> and 00:50:49.849 --> 00:50:49.859 align:start position:0% did a great early match for it and 00:50:49.859 --> 00:50:52.309 align:start position:0% did a great early match for it and that's<00:50:50.160> the<00:50:50.280> final<00:50:50.460> rule<00:50:50.730> and<00:50:51.450> we<00:50:51.569> pass<00:50:51.809> all<00:50:52.200> of 00:50:52.309 --> 00:50:52.319 align:start position:0% that's the final rule and we pass all of 00:50:52.319 --> 00:50:58.730 align:start position:0% that's the final rule and we pass all of this<00:50:52.470> as<00:50:52.680> inputs<00:50:56.210> we<00:50:57.210> must<00:50:57.510> all<00:50:58.230> of<00:50:58.410> this<00:50:58.530> has 00:50:58.730 --> 00:50:58.740 align:start position:0% this as inputs we must all of this has 00:50:58.740 --> 00:51:01.579 align:start position:0% this as inputs we must all of this has inputs<00:50:59.160> to<00:50:59.400> the<00:50:59.549> circuit<00:51:00.359> and<00:51:00.660> we<00:51:00.809> dump<00:51:01.049> all<00:51:01.319> of 00:51:01.579 --> 00:51:01.589 align:start position:0% inputs to the circuit and we dump all of 00:51:01.589 --> 00:51:06.140 align:start position:0% inputs to the circuit and we dump all of this<00:51:01.950> data<00:51:02.220> in<00:51:02.430> input<00:51:03.150> or<00:51:03.299> JSON<00:51:03.690> file<00:51:04.460> and<00:51:05.460> when 00:51:06.140 --> 00:51:06.150 align:start position:0% this data in input or JSON file and when 00:51:06.150 --> 00:51:08.450 align:start position:0% this data in input or JSON file and when we're<00:51:06.299> not<00:51:06.450> and<00:51:06.869> we<00:51:07.410> basically<00:51:07.650> run<00:51:07.920> calculate 00:51:08.450 --> 00:51:08.460 align:start position:0% we're not and we basically run calculate 00:51:08.460 --> 00:51:10.880 align:start position:0% we're not and we basically run calculate witness<00:51:08.819> it<00:51:09.030> uses<00:51:09.630> these<00:51:09.839> inputs<00:51:10.319> to<00:51:10.500> generate 00:51:10.880 --> 00:51:10.890 align:start position:0% witness it uses these inputs to generate 00:51:10.890 --> 00:51:13.789 align:start position:0% witness it uses these inputs to generate a<00:51:10.920> witness<00:51:11.339> and<00:51:11.970> later<00:51:12.960> we<00:51:13.260> can<00:51:13.470> use<00:51:13.650> the 00:51:13.789 --> 00:51:13.799 align:start position:0% a witness and later we can use the 00:51:13.799 --> 00:51:15.270 align:start position:0% a witness and later we can use the witness<00:51:14.130> file<00:51:14.339> vehicles 00:51:15.270 --> 00:51:15.280 align:start position:0% witness file vehicles 00:51:15.280 --> 00:51:43.520 align:start position:0% witness file vehicles like<00:51:16.620> do<00:51:17.620> you<00:51:17.680> want<00:51:17.890> me<00:51:18.010> to<00:51:18.100> write<00:51:18.310> over<00:51:18.430> you 00:51:43.520 --> 00:51:43.530 align:start position:0% 00:51:43.530 --> 00:51:50.620 align:start position:0% [Music] 00:51:50.620 --> 00:51:50.630 align:start position:0% 00:51:50.630 --> 00:51:52.779 align:start position:0% so<00:51:51.559> certain<00:51:51.950> thing<00:51:52.099> takes<00:51:52.339> a<00:51:52.460> while<00:51:52.609> because 00:51:52.779 --> 00:51:52.789 align:start position:0% so certain thing takes a while because 00:51:52.789 --> 00:51:55.269 align:start position:0% so certain thing takes a while because this<00:51:53.119> socket<00:51:53.960> has<00:51:54.079> not<00:51:54.380> not<00:51:54.710> not<00:51:55.039> many 00:51:55.269 --> 00:51:55.279 align:start position:0% this socket has not not not many 00:51:55.279 --> 00:51:57.249 align:start position:0% this socket has not not not many constraints<00:51:55.729> than<00:51:56.029> the<00:51:56.180> previous<00:51:56.479> month<00:51:56.660> and 00:51:57.249 --> 00:51:57.259 align:start position:0% constraints than the previous month and 00:51:57.259 --> 00:52:00.309 align:start position:0% constraints than the previous month and it<00:51:57.380> basically<00:51:57.799> uses<00:51:58.099> the<00:51:58.789> circuit<00:51:59.359> so<00:51:59.599> so<00:52:00.170> like 00:52:00.309 --> 00:52:00.319 align:start position:0% it basically uses the circuit so so like 00:52:00.319 --> 00:52:03.400 align:start position:0% it basically uses the circuit so so like every<00:52:00.910> signature<00:52:01.910> verification<00:52:02.150> has<00:52:02.839> its<00:52:03.109> own 00:52:03.400 --> 00:52:03.410 align:start position:0% every signature verification has its own 00:52:03.410 --> 00:52:06.460 align:start position:0% every signature verification has its own constraints<00:52:04.390> taken<00:52:05.390> mobile<00:52:05.869> root<00:52:06.019> has<00:52:06.259> its 00:52:06.460 --> 00:52:06.470 align:start position:0% constraints taken mobile root has its 00:52:06.470 --> 00:52:07.779 align:start position:0% constraints taken mobile root has its own<00:52:06.619> constraints<00:52:06.829> right<00:52:07.190> so<00:52:07.400> it<00:52:07.489> takes<00:52:07.670> a 00:52:07.779 --> 00:52:07.789 align:start position:0% own constraints right so it takes a 00:52:07.789 --> 00:52:23.500 align:start position:0% own constraints right so it takes a while<00:52:12.460> this<00:52:13.460> will<00:52:13.640> be<00:52:13.789> the<00:52:13.940> input<00:52:14.119> file<00:52:14.690> for<00:52:14.930> us 00:52:23.500 --> 00:52:23.510 align:start position:0% 00:52:23.510 --> 00:52:26.950 align:start position:0% if<00:52:23.990> I<00:52:24.109> try<00:52:24.320> to<00:52:24.380> change<00:52:25.220> the<00:52:25.490> input<00:52:26.270> already 00:52:26.950 --> 00:52:26.960 align:start position:0% if I try to change the input already 00:52:26.960 --> 00:52:33.330 align:start position:0% if I try to change the input already nation<00:52:27.290> after<00:52:27.470> this<00:52:27.859> it<00:52:28.369> won't<00:52:28.880> work 00:52:33.330 --> 00:52:33.340 align:start position:0% 00:52:33.340 --> 00:52:45.940 align:start position:0% [Music] 00:52:45.940 --> 00:52:45.950 align:start position:0% 00:52:45.950 --> 00:52:58.380 align:start position:0% [Music] 00:52:58.380 --> 00:52:58.390 align:start position:0% 00:52:58.390 --> 00:53:04.650 align:start position:0% yep 00:53:04.650 --> 00:53:04.660 align:start position:0% 00:53:04.660 --> 00:53:10.980 align:start position:0% you're<00:53:05.290> saying<00:53:05.620> that<00:53:05.800> like<00:53:06.360> you<00:53:08.220> know<00:53:09.990> sha-256 00:53:10.980 --> 00:53:10.990 align:start position:0% you're saying that like you know sha-256 00:53:10.990 --> 00:53:17.850 align:start position:0% you're saying that like you know sha-256 s<00:53:11.170> that's<00:53:11.950> it<00:53:13.860> yeah<00:53:14.860> so<00:53:15.250> it<00:53:16.030> is<00:53:16.180> enough<00:53:17.170> lots<00:53:17.710> of 00:53:17.850 --> 00:53:17.860 align:start position:0% s that's it yeah so it is enough lots of 00:53:17.860 --> 00:53:21.680 align:start position:0% s that's it yeah so it is enough lots of punching<00:53:18.310> so<00:53:18.610> yeah<00:53:18.990> but<00:53:19.990> in<00:53:20.620> theory<00:53:20.980> like 00:53:21.680 --> 00:53:21.690 align:start position:0% punching so yeah but in theory like 00:53:21.690 --> 00:53:23.850 align:start position:0% punching so yeah but in theory like right<00:53:22.690> over<00:53:22.720> when<00:53:23.170> you're<00:53:23.290> saying<00:53:23.530> is<00:53:23.680> that 00:53:23.850 --> 00:53:23.860 align:start position:0% right over when you're saying is that 00:53:23.860 --> 00:53:26.550 align:start position:0% right over when you're saying is that the<00:53:24.190> USS<00:53:24.640> satellite<00:53:25.150> once<00:53:25.900> you're<00:53:26.230> saying 00:53:26.550 --> 00:53:26.560 align:start position:0% the USS satellite once you're saying 00:53:26.560 --> 00:53:31.440 align:start position:0% the USS satellite once you're saying that<00:53:26.650> built<00:53:26.950> the<00:53:27.160> calculation<00:53:27.730> is<00:53:27.850> celery 00:53:31.440 --> 00:53:31.450 align:start position:0% 00:53:31.450 --> 00:53:33.350 align:start position:0% brewing 00:53:33.350 --> 00:53:33.360 align:start position:0% brewing 00:53:33.360 --> 00:53:40.380 align:start position:0% brewing so<00:53:34.980> what<00:53:35.980> if<00:53:38.340> is<00:53:39.340> there<00:53:39.580> I<00:53:39.790> guess<00:53:40.000> about<00:53:40.180> us 00:53:40.380 --> 00:53:40.390 align:start position:0% so what if is there I guess about us 00:53:40.390 --> 00:53:42.000 align:start position:0% so what if is there I guess about us there<00:53:40.660> I<00:53:40.690> said<00:53:40.990> like<00:53:41.170> there's<00:53:41.680> something<00:53:41.890> that 00:53:42.000 --> 00:53:42.010 align:start position:0% there I said like there's something that 00:53:42.010 --> 00:53:43.140 align:start position:0% there I said like there's something that you<00:53:42.190> did<00:53:42.400> it<00:53:42.520> once 00:53:43.140 --> 00:53:43.150 align:start position:0% you did it once 00:53:43.150 --> 00:53:45.030 align:start position:0% you did it once is<00:53:43.330> there<00:53:43.510> are<00:53:43.630> some<00:53:43.840> money<00:53:44.050> of<00:53:44.200> like<00:53:44.410> kind<00:53:44.920> of 00:53:45.030 --> 00:53:45.040 align:start position:0% is there are some money of like kind of 00:53:45.040 --> 00:53:49.590 align:start position:0% is there are some money of like kind of like<00:53:45.100> some<00:53:46.060> roll<00:53:46.780> up<00:53:46.990> jet<00:53:47.590> where<00:53:48.340> you<00:53:49.300> just 00:53:49.590 --> 00:53:49.600 align:start position:0% like some roll up jet where you just 00:53:49.600 --> 00:53:58.400 align:start position:0% like some roll up jet where you just like<00:53:49.840> you<00:53:50.140> did<00:53:50.290> that<00:53:50.320> one<00:53:50.680> time<00:53:50.890> that<00:53:50.920> you<00:53:51.130> made 00:53:58.400 --> 00:53:58.410 align:start position:0% 00:53:58.410 --> 00:54:00.930 align:start position:0% so<00:53:59.410> you<00:53:59.500> basically<00:53:59.619> have<00:54:00.130> to<00:54:00.310> grade<00:54:00.520> improve 00:54:00.930 --> 00:54:00.940 align:start position:0% so you basically have to grade improve 00:54:00.940 --> 00:54:03.150 align:start position:0% so you basically have to grade improve every<00:54:01.750> time<00:54:01.930> you<00:54:02.080> create<00:54:02.260> a<00:54:02.410> new<00:54:02.440> batch<00:54:02.800> right 00:54:03.150 --> 00:54:03.160 align:start position:0% every time you create a new batch right 00:54:03.160 --> 00:54:03.599 align:start position:0% every time you create a new batch right now 00:54:03.599 --> 00:54:03.609 align:start position:0% now 00:54:03.609 --> 00:54:07.589 align:start position:0% now so<00:54:04.410> yeah<00:54:05.410> at<00:54:05.980> most<00:54:06.280> we<00:54:06.430> can<00:54:06.580> do<00:54:06.910> or<00:54:07.180> we<00:54:07.210> can<00:54:07.450> like 00:54:07.589 --> 00:54:07.599 align:start position:0% so yeah at most we can do or we can like 00:54:07.599 --> 00:54:11.430 align:start position:0% so yeah at most we can do or we can like paralyze<00:54:08.470> it<00:54:08.500> sounds<00:54:09.099> like<00:54:09.810> using<00:54:10.810> like<00:54:10.869> what 00:54:11.430 --> 00:54:11.440 align:start position:0% paralyze it sounds like using like what 00:54:11.440 --> 00:54:13.470 align:start position:0% paralyze it sounds like using like what a<00:54:11.470> lot<00:54:11.680> is<00:54:11.830> we<00:54:12.099> can<00:54:12.250> predict<00:54:12.520> if<00:54:12.970> I<00:54:13.089> process 00:54:13.470 --> 00:54:13.480 align:start position:0% a lot is we can predict if I process 00:54:13.480 --> 00:54:15.570 align:start position:0% a lot is we can predict if I process this<00:54:13.839> is<00:54:13.960> this<00:54:14.080> path<00:54:14.290> of<00:54:14.470> transactions<00:54:15.040> the 00:54:15.570 --> 00:54:15.580 align:start position:0% this is this path of transactions the 00:54:15.580 --> 00:54:17.820 align:start position:0% this is this path of transactions the new<00:54:15.730> vocal<00:54:16.150> rule<00:54:16.450> with<00:54:16.630> this<00:54:16.810> and<00:54:17.080> I<00:54:17.619> can 00:54:17.820 --> 00:54:17.830 align:start position:0% new vocal rule with this and I can 00:54:17.830 --> 00:54:21.300 align:start position:0% new vocal rule with this and I can interval<00:54:18.790> start<00:54:19.060> processing<00:54:19.800> next<00:54:20.800> next<00:54:21.130> pass 00:54:21.300 --> 00:54:21.310 align:start position:0% interval start processing next next pass 00:54:21.310 --> 00:54:22.950 align:start position:0% interval start processing next next pass while<00:54:21.580> the<00:54:21.880> proof<00:54:22.210> for<00:54:22.480> previous<00:54:22.750> verses 00:54:22.950 --> 00:54:22.960 align:start position:0% while the proof for previous verses 00:54:22.960 --> 00:54:34.160 align:start position:0% while the proof for previous verses being<00:54:23.260> good<00:54:23.730> yeah 00:54:34.160 --> 00:54:34.170 align:start position:0% 00:54:34.170 --> 00:54:38.160 align:start position:0% so<00:54:35.170> I<00:54:35.200> click<00:54:35.470> create<00:54:36.220> the<00:54:36.730> proof<00:54:37.690> before 00:54:38.160 --> 00:54:38.170 align:start position:0% so I click create the proof before 00:54:38.170 --> 00:54:40.590 align:start position:0% so I click create the proof before coming<00:54:38.890> every<00:54:39.130> part<00:54:39.340> because<00:54:39.670> it<00:54:39.790> takes<00:54:39.970> a<00:54:40.120> lot 00:54:40.590 --> 00:54:40.600 align:start position:0% coming every part because it takes a lot 00:54:40.600 --> 00:54:42.930 align:start position:0% coming every part because it takes a lot of<00:54:40.630> time<00:54:40.960> if<00:54:41.500> you<00:54:41.620> guys<00:54:41.800> want<00:54:42.040> to<00:54:42.160> try<00:54:42.670> it<00:54:42.820> out 00:54:42.930 --> 00:54:42.940 align:start position:0% of time if you guys want to try it out 00:54:42.940 --> 00:54:46.710 align:start position:0% of time if you guys want to try it out maybe<00:54:43.330> you<00:54:43.480> can<00:54:43.630> run<00:54:44.530> these<00:54:44.620> commands<00:54:45.010> I<00:54:45.420> can<00:54:46.420> I 00:54:46.710 --> 00:54:46.720 align:start position:0% maybe you can run these commands I can I 00:54:46.720 --> 00:54:48.600 align:start position:0% maybe you can run these commands I can I can<00:54:46.990> try<00:54:47.110> it<00:54:47.170> with<00:54:47.320> running<00:54:47.620> but<00:54:47.860> it<00:54:47.980> takes<00:54:48.130> a 00:54:48.600 --> 00:54:48.610 align:start position:0% can try it with running but it takes a 00:54:48.610 --> 00:54:53.550 align:start position:0% can try it with running but it takes a lot<00:54:49.300> of<00:54:49.330> time<00:54:52.020> depends<00:54:53.020> on<00:54:53.080> the<00:54:53.140> number<00:54:53.530> of 00:54:53.550 --> 00:54:53.560 align:start position:0% lot of time depends on the number of 00:54:53.560 --> 00:54:55.650 align:start position:0% lot of time depends on the number of constraints<00:54:54.070> forward<00:54:54.550> but<00:54:54.820> this<00:54:55.000> it<00:54:55.420> won't 00:54:55.650 --> 00:54:55.660 align:start position:0% constraints forward but this it won't 00:54:55.660 --> 00:55:01.380 align:start position:0% constraints forward but this it won't take<00:54:55.840> like<00:54:56.020> it<00:54:56.590> will<00:54:56.770> take<00:54:56.890> like<00:54:57.040> 2<00:54:57.640> minutes 00:55:01.380 --> 00:55:01.390 align:start position:0% 00:55:01.390 --> 00:55:10.700 align:start position:0% [Music] 00:55:10.700 --> 00:55:10.710 align:start position:0% 00:55:10.710 --> 00:55:14.310 align:start position:0% [Music] 00:55:14.310 --> 00:55:14.320 align:start position:0% 00:55:14.320 --> 00:55:18.339 align:start position:0% yes<00:55:15.320> so<00:55:15.530> so<00:55:16.340> this<00:55:16.490> clustered<00:55:17.330> setup<00:55:18.230> is 00:55:18.339 --> 00:55:18.349 align:start position:0% yes so so this clustered setup is 00:55:18.349 --> 00:55:20.530 align:start position:0% yes so so this clustered setup is basically<00:55:18.380> one<00:55:18.950> party<00:55:19.310> right<00:55:19.550> now<00:55:19.790> but<00:55:20.359> I 00:55:20.530 --> 00:55:20.540 align:start position:0% basically one party right now but I 00:55:20.540 --> 00:55:23.290 align:start position:0% basically one party right now but I guess<00:55:20.840> I<00:55:21.530> didn't<00:55:22.250> leave<00:55:22.340> people<00:55:22.609> have<00:55:23.150> been 00:55:23.290 --> 00:55:23.300 align:start position:0% guess I didn't leave people have been 00:55:23.300 --> 00:55:26.349 align:start position:0% guess I didn't leave people have been working<00:55:23.570> on<00:55:23.810> doing<00:55:24.050> him<00:55:24.349> MPC<00:55:25.190> you<00:55:25.460> will<00:55:25.640> not<00:55:26.060> GS 00:55:26.349 --> 00:55:26.359 align:start position:0% working on doing him MPC you will not GS 00:55:26.359 --> 00:55:33.550 align:start position:0% working on doing him MPC you will not GS as<00:55:26.540> well<00:55:26.750> so<00:55:31.570> so<00:55:32.570> it's<00:55:32.720> like<00:55:32.869> multi-party 00:55:33.550 --> 00:55:33.560 align:start position:0% as well so so it's like multi-party 00:55:33.560 --> 00:55:37.300 align:start position:0% as well so so it's like multi-party computation<00:55:34.190> and<00:55:34.670> a<00:55:35.450> lot<00:55:36.410> of<00:55:36.560> people<00:55:36.859> on<00:55:37.160> the 00:55:37.300 --> 00:55:37.310 align:start position:0% computation and a lot of people on the 00:55:37.310 --> 00:55:39.700 align:start position:0% computation and a lot of people on the set<00:55:37.490> up<00:55:37.640> and<00:55:37.849> they're<00:55:38.210> supposed<00:55:38.480> to<00:55:38.720> discard 00:55:39.700 --> 00:55:39.710 align:start position:0% set up and they're supposed to discard 00:55:39.710 --> 00:55:44.609 align:start position:0% set up and they're supposed to discard the<00:55:39.890> toxic<00:55:40.190> waste<00:55:41.619> so<00:55:42.619> that's<00:55:43.609> it<00:55:43.790> then<00:55:43.970> people 00:55:44.609 --> 00:55:44.619 align:start position:0% the toxic waste so that's it then people 00:55:44.619 --> 00:55:46.960 align:start position:0% the toxic waste so that's it then people participate<00:55:45.619> and<00:55:45.800> even<00:55:46.099> if<00:55:46.220> one<00:55:46.580> of<00:55:46.609> them<00:55:46.820> is 00:55:46.960 --> 00:55:46.970 align:start position:0% participate and even if one of them is 00:55:46.970 --> 00:55:49.410 align:start position:0% participate and even if one of them is honest<00:55:47.270> then<00:55:47.930> it<00:55:48.050> should<00:55:48.260> be<00:55:48.290> fine 00:55:49.410 --> 00:55:49.420 align:start position:0% honest then it should be fine 00:55:49.420 --> 00:55:52.210 align:start position:0% honest then it should be fine because<00:55:50.420> we<00:55:50.570> are<00:55:50.690> we<00:55:51.440> have<00:55:51.560> to<00:55:51.680> participate 00:55:52.210 --> 00:55:52.220 align:start position:0% because we are we have to participate 00:55:52.220 --> 00:55:55.740 align:start position:0% because we are we have to participate over<00:55:52.640> here<00:55:52.849> if<00:55:53.420> we<00:55:53.750> can<00:55:54.320> basically<00:55:54.560> clear<00:55:55.010> like 00:55:55.740 --> 00:55:55.750 align:start position:0% over here if we can basically clear like 00:55:55.750 --> 00:55:59.770 align:start position:0% over here if we can basically clear like it's<00:55:56.750> false<00:55:57.170> proofs<00:55:57.470> but<00:55:58.369> if<00:55:58.550> we<00:55:58.730> had<00:55:59.090> multiple 00:55:59.770 --> 00:55:59.780 align:start position:0% it's false proofs but if we had multiple 00:55:59.780 --> 00:56:02.050 align:start position:0% it's false proofs but if we had multiple participants<00:56:00.230> like<00:56:00.680> let's<00:56:00.920> say<00:56:01.070> 100<00:56:01.580> 200 00:56:02.050 --> 00:56:02.060 align:start position:0% participants like let's say 100 200 00:56:02.060 --> 00:56:11.930 align:start position:0% participants like let's say 100 200 times 00:56:11.930 --> 00:56:11.940 align:start position:0% 00:56:11.940 --> 00:56:15.670 align:start position:0% yes<00:56:12.510> a<00:56:13.109> lot<00:56:13.230> of<00:56:13.700> things<00:56:14.700> if<00:56:15.119> you<00:56:15.240> like<00:56:15.359> want<00:56:15.569> to 00:56:15.670 --> 00:56:15.680 align:start position:0% yes a lot of things if you like want to 00:56:15.680 --> 00:56:19.160 align:start position:0% yes a lot of things if you like want to ride<00:56:16.680> out<00:56:16.829> and<00:56:17.730> be<00:56:17.970> there<00:56:18.119> do<00:56:18.270> about<00:56:18.839> and<00:56:19.109> I 00:56:19.160 --> 00:56:19.170 align:start position:0% ride out and be there do about and I 00:56:19.170 --> 00:56:31.540 align:start position:0% ride out and be there do about and I will<00:56:19.230> do<00:56:19.619> if<00:56:20.400> you<00:56:20.430> have<00:56:20.700> any<00:56:20.849> motion<00:56:21.210> and<00:56:21.329> stuff 00:56:31.540 --> 00:56:31.550 align:start position:0% 00:56:31.550 --> 00:56:34.870 align:start position:0% I<00:56:31.580> think<00:56:32.090> there's<00:56:32.270> a<00:56:32.330> log-log<00:56:33.260> slide<00:56:33.800> so<00:56:34.790> you 00:56:34.870 --> 00:56:34.880 align:start position:0% I think there's a log-log slide so you 00:56:34.880 --> 00:56:37.420 align:start position:0% I think there's a log-log slide so you can<00:56:35.330> actually<00:56:35.540> write<00:56:35.900> if<00:56:36.110> I<00:56:36.230> close<00:56:36.470> but<00:56:37.220> I 00:56:37.420 --> 00:56:37.430 align:start position:0% can actually write if I close but I 00:56:37.430 --> 00:56:39.760 align:start position:0% can actually write if I close but I guess<00:56:37.730> how<00:56:37.940> people<00:56:38.840> are<00:56:38.960> still<00:56:39.140> working<00:56:39.500> on<00:56:39.710> a 00:56:39.760 --> 00:56:39.770 align:start position:0% guess how people are still working on a 00:56:39.770 --> 00:56:48.900 align:start position:0% guess how people are still working on a compiler<00:56:40.220> so<00:56:41.030> I<00:56:41.300> guess<00:56:41.450> it<00:56:41.600> should<00:56:41.780> be<00:56:41.900> out 00:56:48.900 --> 00:56:48.910 align:start position:0% 00:56:48.910 --> 00:56:55.790 align:start position:0% [Music] 00:56:55.790 --> 00:56:55.800 align:start position:0% 00:56:55.800 --> 00:56:58.820 align:start position:0% which<00:56:56.280> of<00:56:56.460> these<00:56:56.640> life<00:56:56.880> is<00:56:57.060> to<00:56:57.470> reduce<00:56:58.470> and 00:56:58.820 --> 00:56:58.830 align:start position:0% which of these life is to reduce and 00:56:58.830 --> 00:57:02.270 align:start position:0% which of these life is to reduce and which<00:56:59.160> you<00:56:59.340> have<00:56:59.370> to<00:56:59.670> throw<00:56:59.880> away<00:57:01.130> is<00:57:02.130> there 00:57:02.270 --> 00:57:02.280 align:start position:0% which you have to throw away is there 00:57:02.280 --> 00:57:06.530 align:start position:0% which you have to throw away is there anything<00:57:02.700> that<00:57:02.880> you<00:57:03.210> are<00:57:03.360> using<00:57:03.920> change<00:57:05.540> I 00:57:06.530 --> 00:57:06.540 align:start position:0% anything that you are using change I 00:57:06.540 --> 00:57:09.500 align:start position:0% anything that you are using change I guess<00:57:07.230> we<00:57:07.560> will<00:57:07.830> have<00:57:07.890> to<00:57:08.070> create<00:57:08.510> new 00:57:09.500 --> 00:57:09.510 align:start position:0% guess we will have to create new 00:57:09.510 --> 00:57:11.930 align:start position:0% guess we will have to create new language<00:57:10.290> for<00:57:10.530> the<00:57:10.650> new<00:57:10.800> blooming<00:57:11.160> systems 00:57:11.930 --> 00:57:11.940 align:start position:0% language for the new blooming systems 00:57:11.940 --> 00:57:20.620 align:start position:0% language for the new blooming systems yes<00:57:12.690> so<00:57:12.870> I<00:57:13.140> guess<00:57:13.470> you'll<00:57:13.620> have<00:57:13.650> to<00:57:13.770> create<00:57:17.540> a 00:57:20.620 --> 00:57:20.630 align:start position:0% 00:57:20.630 --> 00:57:24.320 align:start position:0% subject<00:57:21.630> of<00:57:21.930> the<00:57:22.340> compilers<00:57:23.340> just<00:57:24.120> for<00:57:24.300> a 00:57:24.320 --> 00:57:24.330 align:start position:0% subject of the compilers just for a 00:57:24.330 --> 00:57:27.650 align:start position:0% subject of the compilers just for a lightweight<00:57:24.750> from<00:57:25.580> Sikkim<00:57:26.580> language<00:57:27.090> through 00:57:27.650 --> 00:57:27.660 align:start position:0% lightweight from Sikkim language through 00:57:27.660 --> 00:57:32.540 align:start position:0% lightweight from Sikkim language through the<00:57:28.370> harmonious<00:57:29.510> constraints<00:57:30.740> that<00:57:31.740> that 00:57:32.540 --> 00:57:32.550 align:start position:0% the harmonious constraints that that 00:57:32.550 --> 00:57:34.550 align:start position:0% the harmonious constraints that that what<00:57:32.790> can<00:57:32.970> almost<00:57:33.300> probably<00:57:33.840> stick<00:57:34.080> from 00:57:34.550 --> 00:57:34.560 align:start position:0% what can almost probably stick from 00:57:34.560 --> 00:57:36.560 align:start position:0% what can almost probably stick from there<00:57:34.770> if<00:57:35.130> there's<00:57:35.610> a<00:57:35.670> new<00:57:35.850> moving<00:57:36.150> system<00:57:36.300> of 00:57:36.560 --> 00:57:36.570 align:start position:0% there if there's a new moving system of 00:57:36.570 --> 00:57:43.680 align:start position:0% there if there's a new moving system of you<00:57:36.750> can<00:57:36.930> maybe<00:57:37.140> use<00:57:37.680> that 00:57:43.680 --> 00:57:43.690 align:start position:0% 00:57:43.690 --> 00:57:46.320 align:start position:0% the<00:57:43.930> optimizer 00:57:46.320 --> 00:57:46.330 align:start position:0% the optimizer 00:57:46.330 --> 00:57:49.150 align:start position:0% the optimizer [Music] 00:57:49.150 --> 00:57:49.160 align:start position:0% [Music] 00:57:49.160 --> 00:57:51.479 align:start position:0% [Music] yes 00:57:51.479 --> 00:57:51.489 align:start position:0% yes 00:57:51.489 --> 00:57:58.740 align:start position:0% yes why<00:57:52.489> did<00:57:52.699> you<00:57:52.819> want<00:57:53.029> to<00:57:53.119> be<00:57:53.239> stars 00:57:58.740 --> 00:57:58.750 align:start position:0% 00:57:58.750 --> 00:58:14.610 align:start position:0% [Music] 00:58:14.610 --> 00:58:14.620 align:start position:0% 00:58:14.620 --> 00:58:22.080 align:start position:0% [Music] 00:58:22.080 --> 00:58:22.090 align:start position:0% 00:58:22.090 --> 00:58:26.160 align:start position:0% so<00:58:22.540> these<00:58:23.170> these<00:58:23.500> things<00:58:23.920> would<00:58:24.250> be<00:58:24.490> Elena 00:58:26.160 --> 00:58:26.170 align:start position:0% so these these things would be Elena 00:58:26.170 --> 00:58:30.120 align:start position:0% so these these things would be Elena by<00:58:26.770> the<00:58:26.830> month<00:58:27.840> makes<00:58:28.840> me<00:58:28.990> alone<00:58:29.320> betting<00:58:30.040> I 00:58:30.120 --> 00:58:30.130 align:start position:0% by the month makes me alone betting I 00:58:30.130 --> 00:58:32.550 align:start position:0% by the month makes me alone betting I want<00:58:30.370> to<00:58:31.120> have<00:58:31.300> any<00:58:31.540> personal<00:58:31.900> collection<00:58:32.500> of 00:58:32.550 --> 00:58:32.560 align:start position:0% want to have any personal collection of 00:58:32.560 --> 00:58:44.780 align:start position:0% want to have any personal collection of clothes<00:58:32.800> what's<00:58:33.670> your<00:58:33.820> name<00:58:34.000> pass<00:58:34.810> it<00:58:35.140> on 00:58:44.780 --> 00:58:44.790 align:start position:0% 00:58:44.790 --> 00:58:51.820 align:start position:0% we're<00:58:45.790> going<00:58:46.120> on 00:58:51.820 --> 00:58:51.830 align:start position:0% 00:58:51.830 --> 00:58:55.350 align:start position:0% [Music] 00:58:55.350 --> 00:58:55.360 align:start position:0% 00:58:55.360 --> 00:58:58.570 align:start position:0% I<00:58:55.390> have<00:58:56.020> I<00:58:56.560> have<00:58:56.950> some<00:58:57.160> links 00:58:58.570 --> 00:58:58.580 align:start position:0% I have I have some links 00:58:58.580 --> 00:59:00.930 align:start position:0% I have I have some links get<00:58:59.120> out 00:59:00.930 --> 00:59:00.940 align:start position:0% get out 00:59:00.940 --> 00:59:19.040 align:start position:0% get out this<00:59:01.600> was<00:59:02.020> one<00:59:02.230> day 00:59:19.040 --> 00:59:19.050 align:start position:0% 00:59:19.050 --> 00:59:21.960 align:start position:0% and<00:59:20.050> we<00:59:20.200> have<00:59:20.380> been<00:59:20.560> working<00:59:21.250> on<00:59:21.340> a<00:59:21.370> thing<00:59:21.730> for 00:59:21.960 --> 00:59:21.970 align:start position:0% and we have been working on a thing for 00:59:21.970 --> 00:59:25.710 align:start position:0% and we have been working on a thing for grown-up<00:59:22.600> things<00:59:23.100> enormous<00:59:24.100> xxx<00:59:24.610> what<00:59:25.570> it 00:59:25.710 --> 00:59:25.720 align:start position:0% grown-up things enormous xxx what it 00:59:25.720 --> 00:59:28.740 align:start position:0% grown-up things enormous xxx what it does<00:59:25.870> is<00:59:26.080> that<00:59:26.110> it<00:59:27.030> does<00:59:28.030> not<00:59:28.060> pushed<00:59:28.510> around 00:59:28.740 --> 00:59:28.750 align:start position:0% does is that it does not pushed around 00:59:28.750 --> 00:59:31.920 align:start position:0% does is that it does not pushed around us<00:59:29.110> announcing<00:59:29.620> so<00:59:30.460> when<00:59:31.330> you<00:59:31.420> try<00:59:31.570> to<00:59:31.630> push 00:59:31.920 --> 00:59:31.930 align:start position:0% us announcing so when you try to push 00:59:31.930 --> 00:59:33.750 align:start position:0% us announcing so when you try to push down<00:59:32.110> that<00:59:32.290> small<00:59:32.410> chain<00:59:32.860> that<00:59:33.520> that 00:59:33.750 --> 00:59:33.760 align:start position:0% down that small chain that that 00:59:33.760 --> 00:59:36.960 align:start position:0% down that small chain that that basically<00:59:34.090> limits<00:59:34.540> the<00:59:35.310> amount<00:59:36.310> of<00:59:36.610> traumas 00:59:36.960 --> 00:59:36.970 align:start position:0% basically limits the amount of traumas 00:59:36.970 --> 00:59:38.850 align:start position:0% basically limits the amount of traumas and<00:59:37.150> that<00:59:37.270> we<00:59:37.390> can<00:59:37.570> close<00:59:37.750> it<00:59:37.900> with<00:59:38.530> the<00:59:38.560> amount 00:59:38.850 --> 00:59:38.860 align:start position:0% and that we can close it with the amount 00:59:38.860 --> 00:59:41.730 align:start position:0% and that we can close it with the amount of<00:59:38.950> transactions<00:59:39.580> that<00:59:39.700> can<00:59:39.820> be<00:59:40.180> submitted<00:59:40.740> in 00:59:41.730 --> 00:59:41.740 align:start position:0% of transactions that can be submitted in 00:59:41.740 --> 00:59:45.210 align:start position:0% of transactions that can be submitted in we<00:59:42.640> are<00:59:42.730> limited<00:59:43.060> by<00:59:43.090> the<00:59:43.240> gas<00:59:43.510> gasoline<00:59:44.380> but 00:59:45.210 --> 00:59:45.220 align:start position:0% we are limited by the gas gasoline but 00:59:45.220 --> 00:59:47.610 align:start position:0% we are limited by the gas gasoline but if<00:59:45.370> we<00:59:45.490> don't<00:59:45.610> push<00:59:46.140> restaurant<00:59:47.140> chain<00:59:47.380> and 00:59:47.610 --> 00:59:47.620 align:start position:0% if we don't push restaurant chain and 00:59:47.620 --> 00:59:50.400 align:start position:0% if we don't push restaurant chain and then<00:59:47.770> we<00:59:47.890> can<00:59:48.040> process<00:59:48.640> a<00:59:49.030> lot<00:59:49.450> more<00:59:49.900> drama<00:59:50.290> and 00:59:50.400 --> 00:59:50.410 align:start position:0% then we can process a lot more drama and 00:59:50.410 --> 00:59:53.490 align:start position:0% then we can process a lot more drama and in<00:59:50.710> a<00:59:50.770> single<00:59:50.950> batch<00:59:51.250> so<00:59:52.090> this<00:59:52.720> is<00:59:52.900> for<00:59:53.110> things 00:59:53.490 --> 00:59:53.500 align:start position:0% in a single batch so this is for things 00:59:53.500 --> 01:00:10.200 align:start position:0% in a single batch so this is for things like<00:59:53.590> if<00:59:53.920> you<00:59:54.040> want<00:59:54.220> to<00:59:54.280> make<00:59:54.790> sure<01:00:09.120> when<01:00:10.120> you 01:00:10.200 --> 01:00:10.210 align:start position:0% like if you want to make sure when you 01:00:10.210 --> 01:00:12.490 align:start position:0% like if you want to make sure when you say<01:00:10.390> about<01:00:10.570> that 01:00:12.490 --> 01:00:12.500 align:start position:0% say about that 01:00:12.500 --> 01:00:14.349 align:start position:0% say about that is<01:00:12.680> it<01:00:12.920> possible<01:00:13.280> to<01:00:13.460> live<01:00:13.640> like<01:00:13.940> a<01:00:13.970> proof 01:00:14.349 --> 01:00:14.359 align:start position:0% is it possible to live like a proof 01:00:14.359 --> 01:00:17.160 align:start position:0% is it possible to live like a proof constraint<01:00:15.080> in<01:00:15.290> this<01:00:15.500> language<01:00:15.950> also<01:00:16.369> like 01:00:17.160 --> 01:00:17.170 align:start position:0% constraint in this language also like 01:00:17.170 --> 01:00:19.359 align:start position:0% constraint in this language also like basically<01:00:18.170> like<01:00:18.349> what<01:00:18.890> I<01:00:18.920> would<01:00:19.099> say<01:00:19.220> it's 01:00:19.359 --> 01:00:19.369 align:start position:0% basically like what I would say it's 01:00:19.369 --> 01:00:21.609 align:start position:0% basically like what I would say it's like<01:00:19.520> these<01:00:19.820> arguments<01:00:20.119> satisfy<01:00:20.810> like<01:00:21.380> let's 01:00:21.609 --> 01:00:21.619 align:start position:0% like these arguments satisfy like let's 01:00:21.619 --> 01:00:25.210 align:start position:0% like these arguments satisfy like let's say<01:00:21.740> you<01:00:21.800> wanted<01:00:22.070> to<01:00:22.130> run<01:00:22.369> something<01:00:22.640> like<01:00:24.220> in 01:00:25.210 --> 01:00:25.220 align:start position:0% say you wanted to run something like in 01:00:25.220 --> 01:00:27.280 align:start position:0% say you wanted to run something like in parallel<01:00:25.910> or<01:00:26.150> whatever<01:00:26.450> like<01:00:26.660> I<01:00:26.780> had<01:00:26.930> some 01:00:27.280 --> 01:00:27.290 align:start position:0% parallel or whatever like I had some 01:00:27.290 --> 01:00:30.190 align:start position:0% parallel or whatever like I had some which<01:00:28.070> is<01:00:28.220> like<01:00:28.369> yeah<01:00:28.580> the<01:00:28.970> arguments<01:00:29.510> to<01:00:30.050> this 01:00:30.190 --> 01:00:30.200 align:start position:0% which is like yeah the arguments to this 01:00:30.200 --> 01:00:32.820 align:start position:0% which is like yeah the arguments to this thing<01:00:30.440> also<01:00:30.680> satisfied<01:00:31.340> like<01:00:32.240> this 01:00:32.820 --> 01:00:32.830 align:start position:0% thing also satisfied like this 01:00:32.830 --> 01:00:35.170 align:start position:0% thing also satisfied like this relationship<01:00:33.830> between<01:00:34.430> each<01:00:34.640> other<01:00:34.849> and<01:00:35.060> I 01:00:35.170 --> 01:00:35.180 align:start position:0% relationship between each other and I 01:00:35.180 --> 01:00:36.940 align:start position:0% relationship between each other and I wanted<01:00:35.869> to<01:00:35.930> express<01:00:36.260> the<01:00:36.410> fact<01:00:36.440> that<01:00:36.680> there's 01:00:36.940 --> 01:00:36.950 align:start position:0% wanted to express the fact that there's 01:00:36.950 --> 01:00:39.070 align:start position:0% wanted to express the fact that there's a<01:00:37.040> proof<01:00:37.310> of<01:00:37.460> this<01:00:37.640> in<01:00:37.880> you<01:00:38.030> all<01:00:38.570> right<01:00:38.660> I<01:00:38.840> guess 01:00:39.070 --> 01:00:39.080 align:start position:0% a proof of this in you all right I guess 01:00:39.080 --> 01:00:40.089 align:start position:0% a proof of this in you all right I guess what<01:00:39.200> I'm<01:00:39.260> saying<01:00:39.349> is<01:00:39.530> that<01:00:39.590> you<01:00:39.830> what<01:00:39.980> are 01:00:40.089 --> 01:00:40.099 align:start position:0% what I'm saying is that you what are 01:00:40.099 --> 01:00:41.620 align:start position:0% what I'm saying is that you what are they<01:00:40.220> parallel<01:00:40.490> and<01:00:40.849> saying<01:00:41.060> I<01:00:41.300> said<01:00:41.510> really 01:00:41.620 --> 01:00:41.630 align:start position:0% they parallel and saying I said really 01:00:41.630 --> 01:00:43.390 align:start position:0% they parallel and saying I said really expensive<01:00:41.930> to<01:00:42.200> do<01:00:42.349> of<01:00:42.800> course<01:00:42.950> a<01:00:43.130> lot<01:00:43.280> of 01:00:43.390 --> 01:00:43.400 align:start position:0% expensive to do of course a lot of 01:00:43.400 --> 01:00:45.040 align:start position:0% expensive to do of course a lot of really<01:00:43.520> expensive<01:00:43.700> just<01:00:44.480> wanted<01:00:44.750> to<01:00:44.810> express 01:00:45.040 --> 01:00:45.050 align:start position:0% really expensive just wanted to express 01:00:45.050 --> 01:00:47.020 align:start position:0% really expensive just wanted to express that<01:00:45.380> like<01:00:45.530> it<01:00:46.010> was<01:00:46.130> like<01:00:46.220> a<01:00:46.430> match<01:00:46.580> up<01:00:46.790> if<01:00:46.910> you 01:00:47.020 --> 01:00:47.030 align:start position:0% that like it was like a match up if you 01:00:47.030 --> 01:00:48.790 align:start position:0% that like it was like a match up if you did<01:00:47.270> to<01:00:47.480> create<01:00:47.720> like<01:00:48.020> certainly<01:00:48.380> between<01:00:48.560> the 01:00:48.790 --> 01:00:48.800 align:start position:0% did to create like certainly between the 01:00:48.800 --> 01:00:50.830 align:start position:0% did to create like certainly between the two<01:00:48.980> of<01:00:49.070> them<01:00:49.220> like<01:00:50.119> rather<01:00:50.270> than<01:00:50.390> having<01:00:50.750> like 01:00:50.830 --> 01:00:50.840 align:start position:0% two of them like rather than having like 01:00:50.840 --> 01:00:53.650 align:start position:0% two of them like rather than having like one<01:00:50.960> function<01:00:51.560> in<01:00:51.710> describing<01:00:52.540> you<01:00:53.540> could 01:00:53.650 --> 01:00:53.660 align:start position:0% one function in describing you could 01:00:53.660 --> 01:00:56.530 align:start position:0% one function in describing you could break<01:00:53.869> it<01:00:54.020> up<01:00:54.140> and<01:00:54.380> then<01:00:55.090> basically<01:00:56.090> like<01:00:56.300> you 01:00:56.530 --> 01:00:56.540 align:start position:0% break it up and then basically like you 01:00:56.540 --> 01:00:58.920 align:start position:0% break it up and then basically like you don't<01:00:56.720> save<01:00:56.900> you<01:00:57.050> time<01:00:57.230> by<01:00:57.500> right 01:00:58.920 --> 01:00:58.930 align:start position:0% don't save you time by right 01:00:58.930 --> 01:01:01.140 align:start position:0% don't save you time by right two<01:00:59.170> smaller<01:00:59.470> pieces<01:00:59.710> that 01:01:01.140 --> 01:01:01.150 align:start position:0% two smaller pieces that 01:01:01.150 --> 01:01:04.240 align:start position:0% two smaller pieces that waiting<01:01:02.150> post<01:01:02.420> like<01:01:02.750> a<01:01:02.780> larger<01:01:03.260> set<01:01:03.830> drivers 01:01:04.240 --> 01:01:04.250 align:start position:0% waiting post like a larger set drivers 01:01:04.250 --> 01:01:06.460 align:start position:0% waiting post like a larger set drivers because<01:01:04.520> you<01:01:04.640> have<01:01:05.020> you<01:01:06.020> have<01:01:06.140> tons<01:01:06.350> of 01:01:06.460 --> 01:01:06.470 align:start position:0% because you have you have tons of 01:01:06.470 --> 01:01:08.620 align:start position:0% because you have you have tons of constraints<01:01:07.010> or<01:01:07.130> whatever<01:01:07.340> if<01:01:07.880> you<01:01:08.030> that<01:01:08.510> are 01:01:08.620 --> 01:01:08.630 align:start position:0% constraints or whatever if you that are 01:01:08.630 --> 01:01:14.500 align:start position:0% constraints or whatever if you that are all<01:01:08.720> related<01:01:10.930> in<01:01:11.930> parallel<01:01:13.090> by<01:01:14.090> splitting 01:01:14.500 --> 01:01:14.510 align:start position:0% all related in parallel by splitting 01:01:14.510 --> 01:01:19.150 align:start position:0% all related in parallel by splitting apart<01:01:16.480> I<01:01:17.480> guess<01:01:17.870> you<01:01:18.080> already<01:01:18.560> straightened 01:01:19.150 --> 01:01:19.160 align:start position:0% apart I guess you already straightened 01:01:19.160 --> 01:01:22.120 align:start position:0% apart I guess you already straightened them<01:01:19.340> off<01:01:19.550> in<01:01:19.730> two<01:01:19.880> different<01:01:20.350> circuits<01:01:21.350> so 01:01:22.120 --> 01:01:22.130 align:start position:0% them off in two different circuits so 01:01:22.130 --> 01:01:25.660 align:start position:0% them off in two different circuits so yeah<01:01:22.630> basically<01:01:23.630> this<01:01:24.080> nazi<01:01:24.470> was<01:01:24.620> first<01:01:25.490> time 01:01:25.660 --> 01:01:25.670 align:start position:0% yeah basically this nazi was first time 01:01:25.670 --> 01:01:28.030 align:start position:0% yeah basically this nazi was first time because<01:01:25.820> the<01:01:26.270> circuit<01:01:27.140> the<01:01:27.440> constraints<01:01:27.920> of 01:01:28.030 --> 01:01:28.040 align:start position:0% because the circuit the constraints of 01:01:28.040 --> 01:01:28.900 align:start position:0% because the circuit the constraints of those<01:01:28.250> circuits 01:01:28.900 --> 01:01:28.910 align:start position:0% those circuits 01:01:28.910 --> 01:01:31.840 align:start position:0% those circuits haha<01:01:29.330> combined<01:01:30.080> and<01:01:30.440> they're<01:01:31.190> taken<01:01:31.640> in<01:01:31.730> to 01:01:31.840 --> 01:01:31.850 align:start position:0% haha combined and they're taken in to 01:01:31.850 --> 01:01:33.970 align:start position:0% haha combined and they're taken in to move<01:01:32.030> like<01:01:32.360> when<01:01:32.960> me<01:01:33.170> Jenny 01:01:33.970 --> 01:01:33.980 align:start position:0% move like when me Jenny 01:01:33.980 --> 01:01:36.670 align:start position:0% move like when me Jenny generator<01:01:34.940> proof<01:01:35.300> was<01:01:35.810> those<01:01:36.440> ones 01:01:36.670 --> 01:01:36.680 align:start position:0% generator proof was those ones 01:01:36.680 --> 01:01:38.440 align:start position:0% generator proof was those ones constraints<01:01:37.220> are<01:01:37.430> still<01:01:37.790> added<01:01:38.180> to<01:01:38.330> the 01:01:38.440 --> 01:01:38.450 align:start position:0% constraints are still added to the 01:01:38.450 --> 01:01:40.330 align:start position:0% constraints are still added to the constraints<01:01:38.900> of<01:01:39.020> the<01:01:39.050> Buddhism<01:01:39.830> something 01:01:40.330 --> 01:01:40.340 align:start position:0% constraints of the Buddhism something 01:01:40.340 --> 01:01:43.180 align:start position:0% constraints of the Buddhism something yes<01:01:41.240> so<01:01:41.390> there's<01:01:41.990> no<01:01:42.470> such<01:01:42.650> thing<01:01:42.860> as<01:01:43.010> like 01:01:43.180 --> 01:01:43.190 align:start position:0% yes so there's no such thing as like 01:01:43.190 --> 01:01:47.810 align:start position:0% yes so there's no such thing as like multiple<01:01:43.700> circuits<01:01:45.310> one<01:01:46.310> one<01:01:46.700> one 01:01:47.810 --> 01:01:47.820 align:start position:0% multiple circuits one one one 01:01:47.820 --> 01:01:50.910 align:start position:0% multiple circuits one one one there<01:01:48.820> is<01:01:48.970> kind<01:01:49.300> of<01:01:49.510> this<01:01:50.140> idea<01:01:50.380> of<01:01:50.620> putting 01:01:50.910 --> 01:01:50.920 align:start position:0% there is kind of this idea of putting 01:01:50.920 --> 01:01:56.400 align:start position:0% there is kind of this idea of putting multiple<01:01:51.660> nesting<01:01:52.660> snakes 01:01:56.400 --> 01:01:56.410 align:start position:0% 01:01:56.410 --> 01:01:58.890 align:start position:0% are<01:01:57.190> you<01:01:57.339> just<01:01:57.460> like<01:01:57.640> he<01:01:57.940> loves<01:01:58.240> it<01:01:58.450> and<01:01:58.809> you 01:01:58.890 --> 01:01:58.900 align:start position:0% are you just like he loves it and you 01:01:58.900 --> 01:02:00.930 align:start position:0% are you just like he loves it and you had<01:01:59.049> some<01:01:59.230> initiatives<01:01:59.740> about<01:01:59.829> the<01:02:00.099> data<01:02:00.609> that 01:02:00.930 --> 01:02:00.940 align:start position:0% had some initiatives about the data that 01:02:00.940 --> 01:02:03.920 align:start position:0% had some initiatives about the data that like<01:02:01.119> some<01:02:01.329> of<01:02:01.450> them<01:02:01.599> meet<01:02:02.289> some<01:02:02.769> of<01:02:02.859> them<01:02:02.950> are 01:02:03.920 --> 01:02:03.930 align:start position:0% like some of them meet some of them are 01:02:03.930 --> 01:02:15.860 align:start position:0% like some of them meet some of them are like 01:02:15.860 --> 01:02:15.870 align:start position:0% 01:02:15.870 --> 01:02:59.870 align:start position:0% yeah<01:02:16.900> so<01:02:20.790> you<01:02:28.020> can 01:02:59.870 --> 01:02:59.880 align:start position:0% 01:02:59.880 --> 01:03:04.329 align:start position:0% [Applause]