WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.690 align:start position:0% [Applause] 00:00:10.690 --> 00:00:10.700 align:start position:0% 00:00:10.700 --> 00:00:13.129 align:start position:0% everyone<00:00:11.700> today<00:00:12.389> I'm<00:00:12.509> going<00:00:12.719> to<00:00:12.839> be<00:00:12.959> talking 00:00:13.129 --> 00:00:13.139 align:start position:0% everyone today I'm going to be talking 00:00:13.139 --> 00:00:15.740 align:start position:0% everyone today I'm going to be talking about<00:00:13.379> snacks<00:00:13.950> on<00:00:14.699> this<00:00:14.910> talk<00:00:15.119> is<00:00:15.299> going<00:00:15.389> to<00:00:15.629> be 00:00:15.740 --> 00:00:15.750 align:start position:0% about snacks on this talk is going to be 00:00:15.750 --> 00:00:17.120 align:start position:0% about snacks on this talk is going to be fairly<00:00:16.230> high-level 00:00:17.120 --> 00:00:17.130 align:start position:0% fairly high-level 00:00:17.130 --> 00:00:18.950 align:start position:0% fairly high-level I'm<00:00:17.310> going<00:00:17.759> to<00:00:17.910> start<00:00:18.150> by<00:00:18.300> just<00:00:18.450> giving<00:00:18.630> an 00:00:18.950 --> 00:00:18.960 align:start position:0% I'm going to start by just giving an 00:00:18.960 --> 00:00:20.569 align:start position:0% I'm going to start by just giving an execute<00:00:19.439> of<00:00:19.619> what<00:00:19.890> they<00:00:19.980> are<00:00:20.009> and<00:00:20.160> why<00:00:20.520> you 00:00:20.569 --> 00:00:20.579 align:start position:0% execute of what they are and why you 00:00:20.579 --> 00:00:22.609 align:start position:0% execute of what they are and why you might<00:00:20.789> want<00:00:21.000> to<00:00:21.029> use<00:00:21.210> them<00:00:21.450> and<00:00:21.930> then<00:00:22.500> I'm 00:00:22.609 --> 00:00:22.619 align:start position:0% might want to use them and then I'm 00:00:22.619 --> 00:00:24.260 align:start position:0% might want to use them and then I'm going<00:00:22.800> to<00:00:22.919> run<00:00:23.070> them<00:00:23.220> through<00:00:23.250> a<00:00:23.579> selection<00:00:24.000> of 00:00:24.260 --> 00:00:24.270 align:start position:0% going to run them through a selection of 00:00:24.270 --> 00:00:26.810 align:start position:0% going to run them through a selection of options<00:00:25.079> which<00:00:25.380> are<00:00:25.529> partly<00:00:25.829> available<00:00:26.279> which 00:00:26.810 --> 00:00:26.820 align:start position:0% options which are partly available which 00:00:26.820 --> 00:00:28.909 align:start position:0% options which are partly available which I<00:00:27.029> think<00:00:27.270> a<00:00:27.450> school<00:00:27.750> for<00:00:27.960> various<00:00:28.439> reasons 00:00:28.909 --> 00:00:28.919 align:start position:0% I think a school for various reasons 00:00:28.919 --> 00:00:31.369 align:start position:0% I think a school for various reasons Fuko<00:00:29.489> support<00:00:30.029> second<00:00:30.660> can<00:00:31.079> you<00:00:31.110> hear<00:00:31.290> me 00:00:31.369 --> 00:00:31.379 align:start position:0% Fuko support second can you hear me 00:00:31.379 --> 00:00:31.959 align:start position:0% Fuko support second can you hear me better<00:00:31.529> now 00:00:31.959 --> 00:00:31.969 align:start position:0% better now 00:00:31.969 --> 00:00:37.700 align:start position:0% better now yeah<00:00:34.489> such<00:00:35.489> as<00:00:35.670> a<00:00:35.700> Serenata<00:00:36.570> shock<00:00:36.899> it<00:00:37.200> says<00:00:37.469> a 00:00:37.700 --> 00:00:37.710 align:start position:0% yeah such as a Serenata shock it says a 00:00:37.710 --> 00:00:39.740 align:start position:0% yeah such as a Serenata shock it says a subset<00:00:38.460> of<00:00:38.489> zero<00:00:38.850> knowledge<00:00:39.000> previous<00:00:39.539> which 00:00:39.740 --> 00:00:39.750 align:start position:0% subset of zero knowledge previous which 00:00:39.750 --> 00:00:41.900 align:start position:0% subset of zero knowledge previous which have<00:00:40.379> additional<00:00:40.920> properties<00:00:41.340> such<00:00:41.550> as<00:00:41.640> being 00:00:41.900 --> 00:00:41.910 align:start position:0% have additional properties such as being 00:00:41.910 --> 00:00:44.630 align:start position:0% have additional properties such as being very<00:00:42.180> similar<00:00:42.420> needs<00:00:42.839> to<00:00:43.019> verify<00:00:43.399> and<00:00:44.399> it 00:00:44.630 --> 00:00:44.640 align:start position:0% very similar needs to verify and it 00:00:44.640 --> 00:00:46.040 align:start position:0% very similar needs to verify and it stands<00:00:44.879> close<00:00:45.179> they're<00:00:45.449> a<00:00:45.480> nursing<00:00:46.019> home 00:00:46.040 --> 00:00:46.050 align:start position:0% stands close they're a nursing home 00:00:46.050 --> 00:00:50.160 align:start position:0% stands close they're a nursing home interactive<00:00:46.649> document<00:00:46.980> of<00:00:47.070> knowledge 00:00:50.160 --> 00:00:50.170 align:start position:0% 00:00:50.170 --> 00:00:52.860 align:start position:0% and<00:00:50.380> I<00:00:51.070> claim<00:00:51.370> that<00:00:51.730> they<00:00:52.090> are<00:00:52.120> useful<00:00:52.630> for 00:00:52.860 --> 00:00:52.870 align:start position:0% and I claim that they are useful for 00:00:52.870 --> 00:00:58.049 align:start position:0% and I claim that they are useful for poaching<00:00:53.230> applications<00:00:56.520> what<00:00:57.520> cell<00:00:57.760> are<00:00:57.940> you 00:00:58.049 --> 00:00:58.059 align:start position:0% poaching applications what cell are you 00:00:58.059 --> 00:01:00.540 align:start position:0% poaching applications what cell are you today<00:00:58.180> the<00:00:59.050> Syrian<00:00:59.290> election<00:00:59.650> proof<00:01:00.129> allows 00:01:00.540 --> 00:01:00.550 align:start position:0% today the Syrian election proof allows 00:01:00.550 --> 00:01:03.660 align:start position:0% today the Syrian election proof allows you<00:01:00.940> to<00:01:01.180> demonstrate<00:01:01.960> that<00:01:02.260> you<00:01:02.559> have<00:01:02.670> run 00:01:03.660 --> 00:01:03.670 align:start position:0% you to demonstrate that you have run 00:01:03.670 --> 00:01:06.270 align:start position:0% you to demonstrate that you have run some<00:01:04.119> protocol<00:01:04.720> incorrectly<00:01:05.260> and<00:01:05.920> precisely 00:01:06.270 --> 00:01:06.280 align:start position:0% some protocol incorrectly and precisely 00:01:06.280 --> 00:01:07.830 align:start position:0% some protocol incorrectly and precisely what<00:01:06.550> the<00:01:06.640> protocol<00:01:06.970> is<00:01:07.030> it<00:01:07.360> might<00:01:07.509> be<00:01:07.540> a<00:01:07.690> way 00:01:07.830 --> 00:01:07.840 align:start position:0% what the protocol is it might be a way 00:01:07.840 --> 00:01:09.330 align:start position:0% what the protocol is it might be a way of<00:01:07.869> saying<00:01:08.110> that<00:01:08.500> you<00:01:08.619> have<00:01:08.860> done<00:01:09.009> your<00:01:09.130> tax 00:01:09.330 --> 00:01:09.340 align:start position:0% of saying that you have done your tax 00:01:09.340 --> 00:01:11.190 align:start position:0% of saying that you have done your tax return<00:01:10.180> correctly<00:01:10.600> it<00:01:10.780> might<00:01:10.900> be<00:01:11.050> a<00:01:11.080> way<00:01:11.170> of 00:01:11.190 --> 00:01:11.200 align:start position:0% return correctly it might be a way of 00:01:11.200 --> 00:01:12.630 align:start position:0% return correctly it might be a way of saying<00:01:11.530> that<00:01:11.650> you<00:01:11.740> have<00:01:11.860> encrypted<00:01:12.190> a<00:01:12.340> message 00:01:12.630 --> 00:01:12.640 align:start position:0% saying that you have encrypted a message 00:01:12.640 --> 00:01:13.680 align:start position:0% saying that you have encrypted a message correctly<00:01:12.850> it<00:01:13.150> doesn't<00:01:13.270> really<00:01:13.479> matter 00:01:13.680 --> 00:01:13.690 align:start position:0% correctly it doesn't really matter 00:01:13.690 --> 00:01:15.719 align:start position:0% correctly it doesn't really matter what's<00:01:14.680> important<00:01:15.159> is<00:01:15.310> that<00:01:15.340> there<00:01:15.610> is<00:01:15.700> a 00:01:15.719 --> 00:01:15.729 align:start position:0% what's important is that there is a 00:01:15.729 --> 00:01:18.240 align:start position:0% what's important is that there is a protocol<00:01:16.210> and<00:01:16.509> you<00:01:16.659> have<00:01:16.900> run<00:01:17.650> the<00:01:17.830> pentacle 00:01:18.240 --> 00:01:18.250 align:start position:0% protocol and you have run the pentacle 00:01:18.250 --> 00:01:20.580 align:start position:0% protocol and you have run the pentacle exactly<00:01:18.759> as<00:01:18.880> it<00:01:19.030> is<00:01:19.060> specified<00:01:19.690> and<00:01:20.320> then 00:01:20.580 --> 00:01:20.590 align:start position:0% exactly as it is specified and then 00:01:20.590 --> 00:01:22.050 align:start position:0% exactly as it is specified and then what's<00:01:20.800> a<00:01:20.890> verifiable<00:01:21.250> will<00:01:21.550> do<00:01:21.700> is<00:01:21.850> it<00:01:21.970> will 00:01:22.050 --> 00:01:22.060 align:start position:0% what's a verifiable will do is it will 00:01:22.060 --> 00:01:23.999 align:start position:0% what's a verifiable will do is it will just<00:01:22.119> take<00:01:22.360> approve<00:01:22.720> and<00:01:22.899> say<00:01:23.020> yes<00:01:23.259> I<00:01:23.410> agree<00:01:23.530> or 00:01:23.999 --> 00:01:24.009 align:start position:0% just take approve and say yes I agree or 00:01:24.009 --> 00:01:27.300 align:start position:0% just take approve and say yes I agree or no<00:01:24.340> I<00:01:24.369> don't<00:01:24.610> agree<00:01:25.860> the<00:01:26.860> other<00:01:27.100> nice<00:01:27.280> thing 00:01:27.300 --> 00:01:27.310 align:start position:0% no I don't agree the other nice thing 00:01:27.310 --> 00:01:29.340 align:start position:0% no I don't agree the other nice thing about<00:01:27.520> them<00:01:27.820> is<00:01:28.210> that<00:01:28.600> they<00:01:28.869> allow<00:01:29.140> the<00:01:29.200> user 00:01:29.340 --> 00:01:29.350 align:start position:0% about them is that they allow the user 00:01:29.350 --> 00:01:31.560 align:start position:0% about them is that they allow the user to<00:01:29.680> keep<00:01:29.950> some<00:01:30.190> of<00:01:30.220> their<00:01:30.460> inputs<00:01:30.940> to<00:01:31.360> the 00:01:31.560 --> 00:01:31.570 align:start position:0% to keep some of their inputs to the 00:01:31.570 --> 00:01:34.320 align:start position:0% to keep some of their inputs to the protocol<00:01:32.440> confidential<00:01:33.220> so<00:01:33.729> for<00:01:33.910> example 00:01:34.320 --> 00:01:34.330 align:start position:0% protocol confidential so for example 00:01:34.330 --> 00:01:36.960 align:start position:0% protocol confidential so for example with<00:01:34.539> I<00:01:35.110> have<00:01:35.530> encrypted<00:01:35.890> message<00:01:36.340> example 00:01:36.960 --> 00:01:36.970 align:start position:0% with I have encrypted message example 00:01:36.970 --> 00:01:38.639 align:start position:0% with I have encrypted message example you<00:01:37.149> could<00:01:37.420> do<00:01:37.630> that<00:01:37.810> without<00:01:38.020> revealing<00:01:38.380> what 00:01:38.639 --> 00:01:38.649 align:start position:0% you could do that without revealing what 00:01:38.649 --> 00:01:40.870 align:start position:0% you could do that without revealing what the<00:01:38.740> message<00:01:38.979> actually<00:01:39.130> was 00:01:40.870 --> 00:01:40.880 align:start position:0% the message actually was 00:01:40.880 --> 00:01:43.220 align:start position:0% the message actually was so<00:01:41.880> the<00:01:41.970> example<00:01:42.300> we've<00:01:42.390> just<00:01:42.600> seen<00:01:42.750> the<00:01:43.050> role 00:01:43.220 --> 00:01:43.230 align:start position:0% so the example we've just seen the role 00:01:43.230 --> 00:01:45.950 align:start position:0% so the example we've just seen the role of<00:01:43.260> example<00:01:43.920> is<00:01:44.450> classic<00:01:45.450> thing<00:01:45.630> what's<00:01:45.810> not 00:01:45.950 --> 00:01:45.960 align:start position:0% of example is classic thing what's not 00:01:45.960 --> 00:01:47.960 align:start position:0% of example is classic thing what's not so<00:01:46.140> good<00:01:46.290> because<00:01:46.650> the<00:01:47.040> verification<00:01:47.700> is 00:01:47.960 --> 00:01:47.970 align:start position:0% so good because the verification is 00:01:47.970 --> 00:01:49.550 align:start position:0% so good because the verification is cheaper<00:01:48.420> than<00:01:48.540> the<00:01:48.660> natural<00:01:48.840> computation 00:01:49.550 --> 00:01:49.560 align:start position:0% cheaper than the natural computation 00:01:49.560 --> 00:01:53.660 align:start position:0% cheaper than the natural computation itself<00:01:50.450> so<00:01:51.450> it<00:01:51.540> was<00:01:51.690> it<00:01:52.070> essentially<00:01:53.070> means<00:01:53.220> is 00:01:53.660 --> 00:01:53.670 align:start position:0% itself so it was it essentially means is 00:01:53.670 --> 00:01:57.110 align:start position:0% itself so it was it essentially means is that<00:01:54.150> we<00:01:54.720> can<00:01:54.750> have<00:01:55.110> a<00:01:55.500> I'm<00:01:56.220> saying<00:01:56.610> minor<00:01:56.820> it 00:01:57.110 --> 00:01:57.120 align:start position:0% that we can have a I'm saying minor it 00:01:57.120 --> 00:01:59.240 align:start position:0% that we can have a I'm saying minor it probably<00:01:57.570> wouldn't<00:01:57.750> be<00:01:57.810> my<00:01:58.020> number<00:01:58.350> let's<00:01:59.100> say 00:01:59.240 --> 00:01:59.250 align:start position:0% probably wouldn't be my number let's say 00:01:59.250 --> 00:02:01.400 align:start position:0% probably wouldn't be my number let's say that<00:01:59.430> it's<00:01:59.640> a<00:01:59.700> minor<00:01:59.850> he<00:02:00.510> receives<00:02:01.020> lots<00:02:01.230> and 00:02:01.400 --> 00:02:01.410 align:start position:0% that it's a minor he receives lots and 00:02:01.410 --> 00:02:02.900 align:start position:0% that it's a minor he receives lots and lots<00:02:01.530> of<00:02:01.620> transactions<00:02:02.160> and<00:02:02.430> all<00:02:02.640> of<00:02:02.790> these 00:02:02.900 --> 00:02:02.910 align:start position:0% lots of transactions and all of these 00:02:02.910 --> 00:02:05.210 align:start position:0% lots of transactions and all of these transactions<00:02:03.420> have<00:02:03.570> been<00:02:03.600> signed<00:02:04.010> the<00:02:05.010> minor 00:02:05.210 --> 00:02:05.220 align:start position:0% transactions have been signed the minor 00:02:05.220 --> 00:02:08.719 align:start position:0% transactions have been signed the minor can<00:02:05.490> then<00:02:05.990> create<00:02:06.990> a<00:02:07.200> proof<00:02:07.530> that<00:02:07.800> it<00:02:08.190> has<00:02:08.460> run 00:02:08.719 --> 00:02:08.729 align:start position:0% can then create a proof that it has run 00:02:08.729 --> 00:02:10.550 align:start position:0% can then create a proof that it has run the<00:02:08.850> verification<00:02:09.509> algorithm<00:02:09.810> for<00:02:10.170> each<00:02:10.320> of 00:02:10.550 --> 00:02:10.560 align:start position:0% the verification algorithm for each of 00:02:10.560 --> 00:02:12.350 align:start position:0% the verification algorithm for each of these<00:02:10.770> signatures<00:02:11.370> and<00:02:11.670> these<00:02:11.790> transactions 00:02:12.350 --> 00:02:12.360 align:start position:0% these signatures and these transactions 00:02:12.360 --> 00:02:14.000 align:start position:0% these signatures and these transactions and<00:02:12.510> the<00:02:12.570> verification<00:02:13.200> has<00:02:13.350> returned<00:02:13.710> true 00:02:14.000 --> 00:02:14.010 align:start position:0% and the verification has returned true 00:02:14.010 --> 00:02:16.970 align:start position:0% and the verification has returned true and<00:02:14.730> then<00:02:15.270> when<00:02:15.930> it<00:02:16.050> broadcasts<00:02:16.290> a 00:02:16.970 --> 00:02:16.980 align:start position:0% and then when it broadcasts a 00:02:16.980 --> 00:02:18.610 align:start position:0% and then when it broadcasts a transaction<00:02:17.340> to<00:02:17.700> all<00:02:17.790> of<00:02:17.940> the<00:02:18.030> other<00:02:18.120> nodes 00:02:18.610 --> 00:02:18.620 align:start position:0% transaction to all of the other nodes 00:02:18.620 --> 00:02:20.660 align:start position:0% transaction to all of the other nodes rather<00:02:19.620> than<00:02:19.860> having<00:02:20.040> to<00:02:20.280> complete<00:02:20.580> this 00:02:20.660 --> 00:02:20.670 align:start position:0% rather than having to complete this 00:02:20.670 --> 00:02:22.520 align:start position:0% rather than having to complete this verification<00:02:20.970> themselves<00:02:21.780> they<00:02:22.170> could<00:02:22.320> just 00:02:22.520 --> 00:02:22.530 align:start position:0% verification themselves they could just 00:02:22.530 --> 00:02:24.110 align:start position:0% verification themselves they could just check<00:02:22.680> the<00:02:22.860> proof<00:02:23.070> and<00:02:23.310> this<00:02:23.640> is<00:02:23.760> much<00:02:23.970> much 00:02:24.110 --> 00:02:24.120 align:start position:0% check the proof and this is much much 00:02:24.120 --> 00:02:25.699 align:start position:0% check the proof and this is much much cheaper<00:02:24.480> for<00:02:24.510> them<00:02:24.900> to<00:02:25.050> do<00:02:25.170> this<00:02:25.230> thing<00:02:25.470> that's 00:02:25.699 --> 00:02:25.709 align:start position:0% cheaper for them to do this thing that's 00:02:25.709 --> 00:02:27.570 align:start position:0% cheaper for them to do this thing that's great 00:02:27.570 --> 00:02:27.580 align:start position:0% great 00:02:27.580 --> 00:02:29.550 align:start position:0% great the<00:02:28.090> other<00:02:28.300> nice<00:02:28.690> thing<00:02:28.720> that<00:02:28.990> snacks<00:02:29.290> about 00:02:29.550 --> 00:02:29.560 align:start position:0% the other nice thing that snacks about 00:02:29.560 --> 00:02:31.350 align:start position:0% the other nice thing that snacks about you<00:02:29.650> to<00:02:29.770> do<00:02:29.950> is<00:02:30.280> they<00:02:30.490> allow<00:02:30.610> you<00:02:30.760> to<00:02:31.090> achieve 00:02:31.350 --> 00:02:31.360 align:start position:0% you to do is they allow you to achieve 00:02:31.360 --> 00:02:34.350 align:start position:0% you to do is they allow you to achieve some<00:02:31.600> more<00:02:31.900> privacy<00:02:32.340> so<00:02:33.340> if<00:02:33.760> you<00:02:33.880> want<00:02:34.060> them<00:02:34.180> to 00:02:34.350 --> 00:02:34.360 align:start position:0% some more privacy so if you want them to 00:02:34.360 --> 00:02:37.080 align:start position:0% some more privacy so if you want them to hide<00:02:34.570> the<00:02:34.780> contents<00:02:35.200> of<00:02:35.260> a<00:02:35.350> transaction<00:02:36.090> for 00:02:37.080 --> 00:02:37.090 align:start position:0% hide the contents of a transaction for 00:02:37.090 --> 00:02:38.880 align:start position:0% hide the contents of a transaction for example<00:02:37.570> suppose<00:02:37.900> you<00:02:37.990> have<00:02:38.020> a<00:02:38.170> fireplace<00:02:38.440> you 00:02:38.880 --> 00:02:38.890 align:start position:0% example suppose you have a fireplace you 00:02:38.890 --> 00:02:41.250 align:start position:0% example suppose you have a fireplace you have<00:02:39.100> urgent<00:02:39.340> and<00:02:39.910> goodbye<00:02:40.600> abundance<00:02:41.080> to 00:02:41.250 --> 00:02:41.260 align:start position:0% have urgent and goodbye abundance to 00:02:41.260 --> 00:02:44.340 align:start position:0% have urgent and goodbye abundance to room<00:02:41.440> and<00:02:41.710> buy<00:02:41.830> some<00:02:42.040> produce<00:02:42.250> but<00:02:43.210> they<00:02:44.110> don't 00:02:44.340 --> 00:02:44.350 align:start position:0% room and buy some produce but they don't 00:02:44.350 --> 00:02:45.780 align:start position:0% room and buy some produce but they don't necessarily<00:02:44.590> want<00:02:45.280> you<00:02:45.400> to<00:02:45.520> know<00:02:45.670> exactly 00:02:45.780 --> 00:02:45.790 align:start position:0% necessarily want you to know exactly 00:02:45.790 --> 00:02:48.180 align:start position:0% necessarily want you to know exactly what<00:02:46.210> they're<00:02:46.330> buying<00:02:46.740> so<00:02:47.740> the<00:02:47.860> case<00:02:48.040> I<00:02:48.160> have 00:02:48.180 --> 00:02:48.190 align:start position:0% what they're buying so the case I have 00:02:48.190 --> 00:02:50.940 align:start position:0% what they're buying so the case I have given<00:02:48.730> is<00:02:48.970> for<00:02:49.300> apples<00:02:49.660> but<00:02:50.260> actually<00:02:50.680> if 00:02:50.940 --> 00:02:50.950 align:start position:0% given is for apples but actually if 00:02:50.950 --> 00:02:52.800 align:start position:0% given is for apples but actually if you're<00:02:51.100> talking<00:02:51.310> in<00:02:51.700> the<00:02:51.850> business<00:02:52.210> situation 00:02:52.800 --> 00:02:52.810 align:start position:0% you're talking in the business situation 00:02:52.810 --> 00:02:55.140 align:start position:0% you're talking in the business situation if<00:02:52.930> you<00:02:53.050> have<00:02:53.200> companies<00:02:53.650> and<00:02:53.950> the<00:02:54.400> chances<00:02:54.790> of 00:02:55.140 --> 00:02:55.150 align:start position:0% if you have companies and the chances of 00:02:55.150 --> 00:02:57.510 align:start position:0% if you have companies and the chances of them<00:02:55.390> wanting<00:02:55.750> to<00:02:55.870> broadcast<00:02:56.350> to<00:02:56.740> you<00:02:56.830> in<00:02:56.890> 12<00:02:57.160> - 00:02:57.510 --> 00:02:57.520 align:start position:0% them wanting to broadcast to you in 12 - 00:02:57.520 --> 00:02:59.070 align:start position:0% them wanting to broadcast to you in 12 - the<00:02:57.550> competitors<00:02:58.210> precisely<00:02:58.690> what<00:02:58.930> they're 00:02:59.070 --> 00:02:59.080 align:start position:0% the competitors precisely what they're 00:02:59.080 --> 00:03:00.360 align:start position:0% the competitors precisely what they're buying<00:02:59.260> and<00:02:59.530> every<00:02:59.770> single<00:02:59.920> time<00:03:00.130> you<00:03:00.190> use<00:03:00.280> a 00:03:00.360 --> 00:03:00.370 align:start position:0% buying and every single time you use a 00:03:00.370 --> 00:03:02.640 align:start position:0% buying and every single time you use a blockchain<00:03:00.640> is<00:03:01.000> quite<00:03:01.300> small<00:03:01.570> so<00:03:01.900> this<00:03:02.530> is 00:03:02.640 --> 00:03:02.650 align:start position:0% blockchain is quite small so this is 00:03:02.650 --> 00:03:05.310 align:start position:0% blockchain is quite small so this is quite<00:03:02.830> realistic<00:03:03.010> application<00:03:04.170> so<00:03:05.170> what 00:03:05.310 --> 00:03:05.320 align:start position:0% quite realistic application so what 00:03:05.320 --> 00:03:07.080 align:start position:0% quite realistic application so what happened<00:03:05.800> you'd<00:03:06.010> have<00:03:06.040> a<00:03:06.220> transaction<00:03:06.520> which 00:03:07.080 --> 00:03:07.090 align:start position:0% happened you'd have a transaction which 00:03:07.090 --> 00:03:09.420 align:start position:0% happened you'd have a transaction which would<00:03:07.270> say<00:03:07.480> sends<00:03:08.320> 10<00:03:08.500> Americans<00:03:08.920> to<00:03:09.010> buy<00:03:09.130> an<00:03:09.280> A 00:03:09.420 --> 00:03:09.430 align:start position:0% would say sends 10 Americans to buy an A 00:03:09.430 --> 00:03:12.240 align:start position:0% would say sends 10 Americans to buy an A and<00:03:10.050> encrypt<00:03:11.050> that<00:03:11.110> transaction<00:03:11.560> for<00:03:11.830> W<00:03:12.130> block 00:03:12.240 --> 00:03:12.250 align:start position:0% and encrypt that transaction for W block 00:03:12.250 --> 00:03:14.520 align:start position:0% and encrypt that transaction for W block chain<00:03:12.490> but<00:03:13.000> the<00:03:13.090> thing<00:03:13.270> is<00:03:13.300> you<00:03:13.930> now<00:03:14.080> need<00:03:14.320> to 00:03:14.520 --> 00:03:14.530 align:start position:0% chain but the thing is you now need to 00:03:14.530 --> 00:03:17.490 align:start position:0% chain but the thing is you now need to additionally<00:03:14.980> prove<00:03:15.670> that<00:03:16.390> you<00:03:16.870> actually<00:03:17.050> do 00:03:17.490 --> 00:03:17.500 align:start position:0% additionally prove that you actually do 00:03:17.500 --> 00:03:20.490 align:start position:0% additionally prove that you actually do have<00:03:17.530> 10<00:03:18.160> apples<00:03:18.370> to<00:03:18.700> send<00:03:18.940> by<00:03:19.180> a<00:03:19.500> because 00:03:20.490 --> 00:03:20.500 align:start position:0% have 10 apples to send by a because 00:03:20.500 --> 00:03:23.730 align:start position:0% have 10 apples to send by a because otherwise<00:03:20.920> this<00:03:21.790> would<00:03:22.090> be<00:03:22.620> something<00:03:23.620> which 00:03:23.730 --> 00:03:23.740 align:start position:0% otherwise this would be something which 00:03:23.740 --> 00:03:25.350 align:start position:0% otherwise this would be something which would<00:03:23.980> completely<00:03:24.370> break<00:03:24.550> the<00:03:24.820> integrity<00:03:25.210> of 00:03:25.350 --> 00:03:25.360 align:start position:0% would completely break the integrity of 00:03:25.360 --> 00:03:28.350 align:start position:0% would completely break the integrity of the<00:03:26.190> blockchain<00:03:27.190> and<00:03:27.640> that<00:03:28.120> would<00:03:28.210> be<00:03:28.330> a 00:03:28.350 --> 00:03:28.360 align:start position:0% the blockchain and that would be a 00:03:28.360 --> 00:03:31.680 align:start position:0% the blockchain and that would be a problem<00:03:28.650> so<00:03:29.650> bread<00:03:30.250> snack<00:03:30.550> it's<00:03:31.180> not<00:03:31.360> pie<00:03:31.630> is 00:03:31.680 --> 00:03:31.690 align:start position:0% problem so bread snack it's not pie is 00:03:31.690 --> 00:03:35.160 align:start position:0% problem so bread snack it's not pie is precisely<00:03:32.459> what<00:03:33.459> the<00:03:34.270> Jim<00:03:34.810> dice<00:03:34.989> you're 00:03:35.160 --> 00:03:35.170 align:start position:0% precisely what the Jim dice you're 00:03:35.170 --> 00:03:37.560 align:start position:0% precisely what the Jim dice you're sending<00:03:35.590> and<00:03:35.800> all<00:03:36.400> you<00:03:36.520> can<00:03:36.700> see<00:03:36.940> is<00:03:37.150> that<00:03:37.209> yes 00:03:37.560 --> 00:03:37.570 align:start position:0% sending and all you can see is that yes 00:03:37.570 --> 00:03:39.240 align:start position:0% sending and all you can see is that yes I<00:03:37.750> do<00:03:37.810> actually<00:03:38.110> have<00:03:38.500> the<00:03:38.650> merchandise<00:03:39.040> that 00:03:39.240 --> 00:03:39.250 align:start position:0% I do actually have the merchandise that 00:03:39.250 --> 00:03:43.180 align:start position:0% I do actually have the merchandise that I'm<00:03:39.430> sending<00:03:39.730> in<00:03:39.820> this 00:03:43.180 --> 00:03:43.190 align:start position:0% 00:03:43.190 --> 00:03:46.490 align:start position:0% so<00:03:44.190> for<00:03:45.030> developers<00:03:45.510> if<00:03:45.690> you<00:03:45.810> wanted<00:03:46.080> to<00:03:46.290> use 00:03:46.490 --> 00:03:46.500 align:start position:0% so for developers if you wanted to use 00:03:46.500 --> 00:03:48.620 align:start position:0% so for developers if you wanted to use these<00:03:46.680> things<00:03:47.010> but<00:03:47.340> you<00:03:47.400> don't<00:03:47.430> want<00:03:48.030> to<00:03:48.209> get 00:03:48.620 --> 00:03:48.630 align:start position:0% these things but you don't want to get 00:03:48.630 --> 00:03:51.020 align:start position:0% these things but you don't want to get into<00:03:48.870> the<00:03:48.959> details<00:03:49.349> of<00:03:49.530> how<00:03:49.590> that<00:03:49.709> work<00:03:50.010> then<00:03:50.819> a 00:03:51.020 --> 00:03:51.030 align:start position:0% into the details of how that work then a 00:03:51.030 --> 00:03:52.370 align:start position:0% into the details of how that work then a great<00:03:51.209> tool<00:03:51.390> you<00:03:51.450> can<00:03:51.660> use<00:03:51.720> because<00:03:52.170> Socrates 00:03:52.370 --> 00:03:52.380 align:start position:0% great tool you can use because Socrates 00:03:52.380 --> 00:03:55.640 align:start position:0% great tool you can use because Socrates and<00:03:53.209> you<00:03:54.209> will<00:03:54.390> need<00:03:54.569> to<00:03:54.720> learn<00:03:54.840> precisely<00:03:55.410> how 00:03:55.640 --> 00:03:55.650 align:start position:0% and you will need to learn precisely how 00:03:55.650 --> 00:03:57.710 align:start position:0% and you will need to learn precisely how to<00:03:55.680> encode<00:03:56.310> the<00:03:56.489> programs<00:03:56.880> but<00:03:57.330> is<00:03:57.480> that 00:03:57.710 --> 00:03:57.720 align:start position:0% to encode the programs but is that 00:03:57.720 --> 00:03:59.780 align:start position:0% to encode the programs but is that firing<00:03:58.380> to<00:03:58.500> entry<00:03:58.830> but<00:03:59.310> you<00:03:59.400> don't<00:03:59.580> need<00:03:59.730> to 00:03:59.780 --> 00:03:59.790 align:start position:0% firing to entry but you don't need to 00:03:59.790 --> 00:04:01.760 align:start position:0% firing to entry but you don't need to learn<00:03:59.970> how<00:04:00.270> that<00:04:00.300> approving<00:04:00.959> algorithm<00:04:01.560> works 00:04:01.760 --> 00:04:01.770 align:start position:0% learn how that approving algorithm works 00:04:01.770 --> 00:04:03.410 align:start position:0% learn how that approving algorithm works for<00:04:02.040> size<00:04:02.250> you<00:04:02.280> can<00:04:02.610> listen<00:04:02.790> to<00:04:02.940> take<00:04:03.180> that<00:04:03.330> as 00:04:03.410 --> 00:04:03.420 align:start position:0% for size you can listen to take that as 00:04:03.420 --> 00:04:11.360 align:start position:0% for size you can listen to take that as given<00:04:06.110> that<00:04:07.110> one<00:04:07.350> aside<00:04:10.040> so<00:04:11.040> just<00:04:11.250> to 00:04:11.360 --> 00:04:11.370 align:start position:0% given that one aside so just to 00:04:11.370 --> 00:04:13.070 align:start position:0% given that one aside so just to summarize<00:04:11.790> what<00:04:11.819> these<00:04:12.090> things<00:04:12.269> are<00:04:12.480> they<00:04:12.930> are 00:04:13.070 --> 00:04:13.080 align:start position:0% summarize what these things are they are 00:04:13.080 --> 00:04:15.020 align:start position:0% summarize what these things are they are an<00:04:13.380> interaction<00:04:14.010> between<00:04:14.040> approver<00:04:14.819> and<00:04:14.940> a 00:04:15.020 --> 00:04:15.030 align:start position:0% an interaction between approver and a 00:04:15.030 --> 00:04:16.460 align:start position:0% an interaction between approver and a verifier<00:04:15.480> with<00:04:15.750> a<00:04:15.780> previous<00:04:16.139> showing<00:04:16.380> that 00:04:16.460 --> 00:04:16.470 align:start position:0% verifier with a previous showing that 00:04:16.470 --> 00:04:17.750 align:start position:0% verifier with a previous showing that they<00:04:16.590> have<00:04:16.709> followed<00:04:16.889> a<00:04:17.130> French<00:04:17.340> go<00:04:17.519> and<00:04:17.729> a 00:04:17.750 --> 00:04:17.760 align:start position:0% they have followed a French go and a 00:04:17.760 --> 00:04:19.520 align:start position:0% they have followed a French go and a verifier<00:04:18.180> is<00:04:18.209> saying<00:04:18.959> whether<00:04:19.139> or<00:04:19.260> not<00:04:19.350> they 00:04:19.520 --> 00:04:19.530 align:start position:0% verifier is saying whether or not they 00:04:19.530 --> 00:04:21.940 align:start position:0% verifier is saying whether or not they believe<00:04:19.560> you<00:04:19.979> they<00:04:20.940> need<00:04:21.090> to<00:04:21.180> be<00:04:21.269> correct<00:04:21.570> an 00:04:21.940 --> 00:04:21.950 align:start position:0% believe you they need to be correct an 00:04:21.950 --> 00:04:24.440 align:start position:0% believe you they need to be correct an honest<00:04:22.950> prayer<00:04:23.070> become<00:04:23.490> always<00:04:23.820> convinced<00:04:24.150> - 00:04:24.440 --> 00:04:24.450 align:start position:0% honest prayer become always convinced - 00:04:24.450 --> 00:04:26.750 align:start position:0% honest prayer become always convinced - verified<00:04:24.900> they<00:04:25.650> need<00:04:25.800> to<00:04:25.919> be<00:04:26.100> zero<00:04:26.580> knowledge 00:04:26.750 --> 00:04:26.760 align:start position:0% verified they need to be zero knowledge 00:04:26.760 --> 00:04:29.540 align:start position:0% verified they need to be zero knowledge the<00:04:27.570> verify<00:04:28.020> events<00:04:28.410> nothing<00:04:29.100> from<00:04:29.370> the 00:04:29.540 --> 00:04:29.550 align:start position:0% the verify events nothing from the 00:04:29.550 --> 00:04:31.340 align:start position:0% the verify events nothing from the prover<00:04:29.940> apart<00:04:30.630> from<00:04:30.750> the<00:04:30.870> fact<00:04:31.080> that<00:04:31.169> the 00:04:31.340 --> 00:04:31.350 align:start position:0% prover apart from the fact that the 00:04:31.350 --> 00:04:34.370 align:start position:0% prover apart from the fact that the statement<00:04:31.740> is<00:04:31.830> true<00:04:32.010> and<00:04:32.960> most<00:04:33.960> important 00:04:34.370 --> 00:04:34.380 align:start position:0% statement is true and most important 00:04:34.380 --> 00:04:35.840 align:start position:0% statement is true and most important thing<00:04:34.500> and<00:04:34.710> actually<00:04:34.800> most<00:04:35.130> difficult<00:04:35.639> to 00:04:35.840 --> 00:04:35.850 align:start position:0% thing and actually most difficult to 00:04:35.850 --> 00:04:38.350 align:start position:0% thing and actually most difficult to achieve<00:04:36.300> zero<00:04:36.780> knowledge<00:04:37.290> is<00:04:37.410> quite<00:04:37.620> easy 00:04:38.350 --> 00:04:38.360 align:start position:0% achieve zero knowledge is quite easy 00:04:38.360 --> 00:04:41.420 align:start position:0% achieve zero knowledge is quite easy somnus<00:04:39.389> it's<00:04:40.080> not<00:04:40.229> easy<00:04:40.470> when<00:04:40.889> 30<00:04:41.190> years 00:04:41.420 --> 00:04:41.430 align:start position:0% somnus it's not easy when 30 years 00:04:41.430 --> 00:04:43.070 align:start position:0% somnus it's not easy when 30 years trying<00:04:41.639> to<00:04:41.700> get<00:04:41.850> somewhere<00:04:42.210> sufficient<00:04:42.720> and 00:04:43.070 --> 00:04:43.080 align:start position:0% trying to get somewhere sufficient and 00:04:43.080 --> 00:04:46.100 align:start position:0% trying to get somewhere sufficient and this<00:04:43.680> is<00:04:43.889> the<00:04:44.010> idea<00:04:44.280> that<00:04:44.370> only<00:04:44.789> a<00:04:45.300> prefer<00:04:45.960> who 00:04:46.100 --> 00:04:46.110 align:start position:0% this is the idea that only a prefer who 00:04:46.110 --> 00:04:48.920 align:start position:0% this is the idea that only a prefer who has<00:04:46.380> actually<00:04:46.979> followed<00:04:47.130> the<00:04:47.430> protocol<00:04:47.970> can 00:04:48.920 --> 00:04:48.930 align:start position:0% has actually followed the protocol can 00:04:48.930 --> 00:04:51.540 align:start position:0% has actually followed the protocol can convince<00:04:49.320> an<00:04:49.440> honest<00:04:49.620> verify 00:04:51.540 --> 00:04:51.550 align:start position:0% convince an honest verify 00:04:51.550 --> 00:04:53.400 align:start position:0% convince an honest verify [Music] 00:04:53.400 --> 00:04:53.410 align:start position:0% [Music] 00:04:53.410 --> 00:04:56.020 align:start position:0% [Music] so<00:04:54.410> with<00:04:54.560> all<00:04:54.710> I<00:04:54.740> ran<00:04:55.100> through<00:04:55.340> promo<00:04:55.700> snacks 00:04:56.020 --> 00:04:56.030 align:start position:0% so with all I ran through promo snacks 00:04:56.030 --> 00:04:58.180 align:start position:0% so with all I ran through promo snacks which<00:04:56.870> is<00:04:57.110> sort<00:04:57.410> of<00:04:57.500> what<00:04:57.770> I'm<00:04:57.920> mostly 00:04:58.180 --> 00:04:58.190 align:start position:0% which is sort of what I'm mostly 00:04:58.190 --> 00:05:00.700 align:start position:0% which is sort of what I'm mostly focusing<00:04:58.670> on<00:04:58.790> I'm<00:04:59.360> going<00:04:59.720> to<00:04:59.840> talk<00:05:00.230> about<00:05:00.380> some 00:05:00.700 --> 00:05:00.710 align:start position:0% focusing on I'm going to talk about some 00:05:00.710 --> 00:05:03.070 align:start position:0% focusing on I'm going to talk about some situations<00:05:01.310> where<00:05:01.640> you<00:05:01.850> would<00:05:02.060> perhaps<00:05:02.540> not 00:05:03.070 --> 00:05:03.080 align:start position:0% situations where you would perhaps not 00:05:03.080 --> 00:05:04.720 align:start position:0% situations where you would perhaps not want<00:05:03.410> to<00:05:03.530> use<00:05:03.680> apparent<00:05:04.040> basemap<00:05:04.400> where<00:05:04.610> there 00:05:04.720 --> 00:05:04.730 align:start position:0% want to use apparent basemap where there 00:05:04.730 --> 00:05:07.030 align:start position:0% want to use apparent basemap where there would<00:05:04.820> be<00:05:04.850> better<00:05:05.590> solutions<00:05:06.590> in<00:05:06.860> the 00:05:07.030 --> 00:05:07.040 align:start position:0% would be better solutions in the 00:05:07.040 --> 00:05:10.150 align:start position:0% would be better solutions in the literature<00:05:07.370> that<00:05:08.360> you<00:05:08.450> could<00:05:08.630> use<00:05:08.890> the<00:05:09.890> first 00:05:10.150 --> 00:05:10.160 align:start position:0% literature that you could use the first 00:05:10.160 --> 00:05:13.060 align:start position:0% literature that you could use the first one<00:05:10.370> being<00:05:10.610> if<00:05:10.970> your<00:05:11.480> only<00:05:11.720> train<00:05:12.140> intending 00:05:13.060 --> 00:05:13.070 align:start position:0% one being if your only train intending 00:05:13.070 --> 00:05:16.120 align:start position:0% one being if your only train intending to<00:05:13.100> run<00:05:13.370> your<00:05:13.670> computation<00:05:14.240> once<00:05:15.040> so<00:05:16.040> the 00:05:16.120 --> 00:05:16.130 align:start position:0% to run your computation once so the 00:05:16.130 --> 00:05:17.830 align:start position:0% to run your computation once so the thing<00:05:16.280> with<00:05:16.430> snacks<00:05:16.610> is<00:05:16.940> kind<00:05:17.540> of<00:05:17.600> the<00:05:17.720> way 00:05:17.830 --> 00:05:17.840 align:start position:0% thing with snacks is kind of the way 00:05:17.840 --> 00:05:19.270 align:start position:0% thing with snacks is kind of the way they<00:05:17.990> work<00:05:18.200> and<00:05:18.500> the<00:05:18.620> way<00:05:18.860> they<00:05:19.040> get<00:05:19.130> their 00:05:19.270 --> 00:05:19.280 align:start position:0% they work and the way they get their 00:05:19.280 --> 00:05:21.280 align:start position:0% they work and the way they get their efficiency<00:05:19.880> is<00:05:20.060> they<00:05:20.660> have<00:05:20.870> is<00:05:20.990> the<00:05:21.110> big 00:05:21.280 --> 00:05:21.290 align:start position:0% efficiency is they have is the big 00:05:21.290 --> 00:05:23.140 align:start position:0% efficiency is they have is the big pre-processing<00:05:22.040> phase<00:05:22.280> right<00:05:22.580> at<00:05:22.790> the<00:05:22.880> start 00:05:23.140 --> 00:05:23.150 align:start position:0% pre-processing phase right at the start 00:05:23.150 --> 00:05:25.720 align:start position:0% pre-processing phase right at the start but<00:05:23.960> the<00:05:24.110> verifier<00:05:24.620> is<00:05:24.860> going<00:05:25.130> to<00:05:25.280> do<00:05:25.370> a<00:05:25.400> ton<00:05:25.700> of 00:05:25.720 --> 00:05:25.730 align:start position:0% but the verifier is going to do a ton of 00:05:25.730 --> 00:05:28.659 align:start position:0% but the verifier is going to do a ton of work<00:05:25.850> just<00:05:26.300> to<00:05:26.480> get<00:05:26.630> a<00:05:27.010> string<00:05:28.010> of<00:05:28.100> information 00:05:28.659 --> 00:05:28.669 align:start position:0% work just to get a string of information 00:05:28.669 --> 00:05:30.820 align:start position:0% work just to get a string of information which<00:05:28.790> you<00:05:28.820> can<00:05:29.120> later<00:05:29.300> refer<00:05:29.750> to<00:05:29.930> in<00:05:30.260> order<00:05:30.680> to 00:05:30.820 --> 00:05:30.830 align:start position:0% which you can later refer to in order to 00:05:30.830 --> 00:05:33.670 align:start position:0% which you can later refer to in order to massively<00:05:31.370> speed<00:05:31.669> up<00:05:31.820> this<00:05:31.970> verification<00:05:32.680> and 00:05:33.670 --> 00:05:33.680 align:start position:0% massively speed up this verification and 00:05:33.680 --> 00:05:35.260 align:start position:0% massively speed up this verification and this<00:05:33.919> means<00:05:34.130> that<00:05:34.310> if<00:05:34.460> your<00:05:34.640> mates<00:05:35.090> they're 00:05:35.260 --> 00:05:35.270 align:start position:0% this means that if your mates they're 00:05:35.270 --> 00:05:37.080 align:start position:0% this means that if your mates they're verifying<00:05:35.660> 100<00:05:36.110> proofs<00:05:36.320> of<00:05:36.470> thousand<00:05:36.830> proofs 00:05:37.080 --> 00:05:37.090 align:start position:0% verifying 100 proofs of thousand proofs 00:05:37.090 --> 00:05:40.300 align:start position:0% verifying 100 proofs of thousand proofs it's<00:05:38.090> really<00:05:38.360> good<00:05:38.510> but<00:05:39.470> if<00:05:39.620> you<00:05:39.650> only<00:05:40.040> need<00:05:40.160> to 00:05:40.300 --> 00:05:40.310 align:start position:0% it's really good but if you only need to 00:05:40.310 --> 00:05:42.520 align:start position:0% it's really good but if you only need to make<00:05:40.340> to<00:05:40.520> use<00:05:40.640> it<00:05:40.760> once<00:05:41.030> and<00:05:41.870> that's<00:05:42.050> a<00:05:42.230> total 00:05:42.520 --> 00:05:42.530 align:start position:0% make to use it once and that's a total 00:05:42.530 --> 00:05:43.600 align:start position:0% make to use it once and that's a total waste<00:05:42.680> of<00:05:42.770> time<00:05:42.830> you'd<00:05:43.160> be<00:05:43.250> better<00:05:43.400> off<00:05:43.520> using 00:05:43.600 --> 00:05:43.610 align:start position:0% waste of time you'd be better off using 00:05:43.610 --> 00:05:46.420 align:start position:0% waste of time you'd be better off using something<00:05:44.120> else<00:05:44.270> and<00:05:44.830> in<00:05:45.830> particular<00:05:45.950> things 00:05:46.420 --> 00:05:46.430 align:start position:0% something else and in particular things 00:05:46.430 --> 00:05:48.370 align:start position:0% something else and in particular things that<00:05:46.490> are<00:05:46.730> good<00:05:46.970> for<00:05:47.150> this<00:05:47.300> test<00:05:47.660> be<00:05:47.900> the<00:05:48.200> Guru 00:05:48.370 --> 00:05:48.380 align:start position:0% that are good for this test be the Guru 00:05:48.380 --> 00:05:52.510 align:start position:0% that are good for this test be the Guru starts<00:05:49.100> area<00:05:49.610> Aurora<00:05:50.180> and<00:05:51.190> these<00:05:52.190> are 00:05:52.510 --> 00:05:52.520 align:start position:0% starts area Aurora and these are 00:05:52.520 --> 00:05:54.700 align:start position:0% starts area Aurora and these are designed<00:05:52.940> for<00:05:53.120> one<00:05:53.360> of<00:05:53.720> the<00:05:53.780> computations<00:05:54.410> and 00:05:54.700 --> 00:05:54.710 align:start position:0% designed for one of the computations and 00:05:54.710 --> 00:05:57.159 align:start position:0% designed for one of the computations and another<00:05:55.520> nice<00:05:56.060> benefit<00:05:56.450> of<00:05:56.600> them<00:05:56.720> is<00:05:56.960> that 00:05:57.159 --> 00:05:57.169 align:start position:0% another nice benefit of them is that 00:05:57.169 --> 00:06:00.010 align:start position:0% another nice benefit of them is that they<00:05:57.290> have<00:05:57.410> typically<00:05:57.770> quantum<00:05:58.160> secure<00:05:59.020> also 00:06:00.010 --> 00:06:00.020 align:start position:0% they have typically quantum secure also 00:06:00.020 --> 00:06:03.520 align:start position:0% they have typically quantum secure also they<00:06:00.110> have<00:06:00.260> very<00:06:00.440> fast<00:06:00.590> breeders 00:06:03.520 --> 00:06:03.530 align:start position:0% 00:06:03.530 --> 00:06:05.440 align:start position:0% another<00:06:04.250> situation<00:06:04.580> where<00:06:05.030> you<00:06:05.120> would<00:06:05.270> not 00:06:05.440 --> 00:06:05.450 align:start position:0% another situation where you would not 00:06:05.450 --> 00:06:07.990 align:start position:0% another situation where you would not use<00:06:05.600> schnapps<00:06:06.170> if<00:06:06.980> the<00:06:07.220> program<00:06:07.640> that<00:06:07.850> you're 00:06:07.990 --> 00:06:08.000 align:start position:0% use schnapps if the program that you're 00:06:08.000 --> 00:06:10.600 align:start position:0% use schnapps if the program that you're trying<00:06:08.240> to<00:06:08.270> prove<00:06:08.510> it's<00:06:08.840> very<00:06:09.200> very<00:06:09.440> small<00:06:09.680> so 00:06:10.600 --> 00:06:10.610 align:start position:0% trying to prove it's very very small so 00:06:10.610 --> 00:06:12.280 align:start position:0% trying to prove it's very very small so typical<00:06:11.210> example<00:06:11.630> of<00:06:11.690> this<00:06:11.810> would<00:06:11.960> be<00:06:12.020> range 00:06:12.280 --> 00:06:12.290 align:start position:0% typical example of this would be range 00:06:12.290 --> 00:06:13.570 align:start position:0% typical example of this would be range previous<00:06:12.620> if<00:06:12.740> you're<00:06:12.890> trying<00:06:13.100> to<00:06:13.220> prove<00:06:13.400> that 00:06:13.570 --> 00:06:13.580 align:start position:0% previous if you're trying to prove that 00:06:13.580 --> 00:06:17.200 align:start position:0% previous if you're trying to prove that something<00:06:13.970> is<00:06:14.210> between<00:06:14.570> 0<00:06:15.380> &<00:06:15.680> 2<00:06:15.710> to<00:06:15.950> the<00:06:16.010> 64<00:06:16.460> we 00:06:17.200 --> 00:06:17.210 align:start position:0% something is between 0 & 2 to the 64 we 00:06:17.210 --> 00:06:18.580 align:start position:0% something is between 0 & 2 to the 64 we can<00:06:17.360> represent<00:06:17.540> my<00:06:17.900> program<00:06:18.290> very 00:06:18.580 --> 00:06:18.590 align:start position:0% can represent my program very 00:06:18.590 --> 00:06:20.860 align:start position:0% can represent my program very efficiently<00:06:19.010> it<00:06:19.280> cost<00:06:19.520> us<00:06:19.670> a<00:06:19.970> hundred<00:06:20.240> twenty 00:06:20.860 --> 00:06:20.870 align:start position:0% efficiently it cost us a hundred twenty 00:06:20.870 --> 00:06:23.110 align:start position:0% efficiently it cost us a hundred twenty cakes<00:06:21.140> or<00:06:21.320> something<00:06:21.530> like<00:06:21.650> that<00:06:21.970> so<00:06:22.970> in<00:06:23.030> this 00:06:23.110 --> 00:06:23.120 align:start position:0% cakes or something like that so in this 00:06:23.120 --> 00:06:25.390 align:start position:0% cakes or something like that so in this situation<00:06:23.410> the<00:06:24.410> stock<00:06:24.650> is<00:06:24.830> actually<00:06:25.100> going<00:06:25.220> to 00:06:25.390 --> 00:06:25.400 align:start position:0% situation the stock is actually going to 00:06:25.400 --> 00:06:27.340 align:start position:0% situation the stock is actually going to give<00:06:25.550> you<00:06:25.730> some<00:06:26.120> concrete<00:06:26.450> vapor<00:06:26.810> head<00:06:27.080> which 00:06:27.340 --> 00:06:27.350 align:start position:0% give you some concrete vapor head which 00:06:27.350 --> 00:06:29.500 align:start position:0% give you some concrete vapor head which we<00:06:27.500> celebrate<00:06:27.850> asymptotics<00:06:28.850> and<00:06:29.090> you<00:06:29.210> were<00:06:29.360> to 00:06:29.500 --> 00:06:29.510 align:start position:0% we celebrate asymptotics and you were to 00:06:29.510 --> 00:06:31.620 align:start position:0% we celebrate asymptotics and you were to be<00:06:29.630> benefiting<00:06:30.170> from<00:06:30.350> a<00:06:30.710> more<00:06:30.890> large 00:06:31.620 --> 00:06:31.630 align:start position:0% be benefiting from a more large 00:06:31.630 --> 00:06:34.000 align:start position:0% be benefiting from a more large computation<00:06:32.630> you<00:06:33.380> wouldn't<00:06:33.650> see<00:06:33.830> the 00:06:34.000 --> 00:06:34.010 align:start position:0% computation you wouldn't see the 00:06:34.010 --> 00:06:36.260 align:start position:0% computation you wouldn't see the benefits<00:06:34.430> of<00:06:34.550> this<00:06:34.700> in<00:06:34.970> our<00:06:35.210> situation 00:06:36.260 --> 00:06:36.270 align:start position:0% benefits of this in our situation 00:06:36.270 --> 00:06:39.430 align:start position:0% benefits of this in our situation got<00:06:36.870> your<00:06:37.020> fuses<00:06:37.380> unapproved<00:06:38.310> switch<00:06:38.699> well 00:06:39.430 --> 00:06:39.440 align:start position:0% got your fuses unapproved switch well 00:06:39.440 --> 00:06:42.890 align:start position:0% got your fuses unapproved switch well practically<00:06:40.440> it's<00:06:41.150> so<00:06:42.150> well<00:06:42.449> asymptotically 00:06:42.890 --> 00:06:42.900 align:start position:0% practically it's so well asymptotically 00:06:42.900 --> 00:06:45.320 align:start position:0% practically it's so well asymptotically it's<00:06:43.350> perhaps<00:06:43.650> let's<00:06:43.919> get<00:06:44.130> the<00:06:44.910> very<00:06:45.090> small 00:06:45.320 --> 00:06:45.330 align:start position:0% it's perhaps let's get the very small 00:06:45.330 --> 00:06:47.570 align:start position:0% it's perhaps let's get the very small statements<00:06:45.930> that<00:06:46.440> actually<00:06:47.160> take<00:06:47.340> the<00:06:47.430> head 00:06:47.570 --> 00:06:47.580 align:start position:0% statements that actually take the head 00:06:47.580 --> 00:06:49.010 align:start position:0% statements that actually take the head is<00:06:47.729> so<00:06:47.880> small<00:06:48.150> that<00:06:48.210> that's<00:06:48.539> not<00:06:48.720> going<00:06:48.870> to 00:06:49.010 --> 00:06:49.020 align:start position:0% is so small that that's not going to 00:06:49.020 --> 00:06:54.439 align:start position:0% is so small that that's not going to come<00:06:49.139> into<00:06:49.259> effect<00:06:51.319> and<00:06:53.000> one<00:06:54.000> last<00:06:54.240> situation 00:06:54.439 --> 00:06:54.449 align:start position:0% come into effect and one last situation 00:06:54.449 --> 00:06:56.960 align:start position:0% come into effect and one last situation is<00:06:55.050> when<00:06:55.860> the<00:06:56.069> thing<00:06:56.250> that<00:06:56.400> you're<00:06:56.550> approving 00:06:56.960 --> 00:06:56.970 align:start position:0% is when the thing that you're approving 00:06:56.970 --> 00:06:59.990 align:start position:0% is when the thing that you're approving is<00:06:57.120> a<00:06:57.150> very<00:06:57.509> specific<00:06:57.810> computation<00:06:58.849> for<00:06:59.849> which 00:06:59.990 --> 00:07:00.000 align:start position:0% is a very specific computation for which 00:07:00.000 --> 00:07:01.700 align:start position:0% is a very specific computation for which we<00:07:00.180> have<00:07:00.300> a<00:07:00.330> very<00:07:00.479> specific<00:07:00.780> solution 00:07:01.700 --> 00:07:01.710 align:start position:0% we have a very specific solution 00:07:01.710 --> 00:07:04.730 align:start position:0% we have a very specific solution okay<00:07:02.490> so<00:07:02.569> starts<00:07:03.569> a<00:07:03.720> quite<00:07:04.110> powerful<00:07:04.289> and<00:07:04.680> they 00:07:04.730 --> 00:07:04.740 align:start position:0% okay so starts a quite powerful and they 00:07:04.740 --> 00:07:06.140 align:start position:0% okay so starts a quite powerful and they cover<00:07:04.919> it<00:07:04.979> here<00:07:05.310> you<00:07:05.460> can<00:07:05.610> do<00:07:05.729> general-purpose 00:07:06.140 --> 00:07:06.150 align:start position:0% cover it here you can do general-purpose 00:07:06.150 --> 00:07:08.480 align:start position:0% cover it here you can do general-purpose computations<00:07:06.870> with<00:07:07.050> them<00:07:07.289> but<00:07:08.039> sometimes<00:07:08.250> you 00:07:08.480 --> 00:07:08.490 align:start position:0% computations with them but sometimes you 00:07:08.490 --> 00:07:10.909 align:start position:0% computations with them but sometimes you don't<00:07:08.610> need<00:07:08.820> that<00:07:08.970> sometimes<00:07:09.870> for<00:07:10.289> example<00:07:10.710> if 00:07:10.909 --> 00:07:10.919 align:start position:0% don't need that sometimes for example if 00:07:10.919 --> 00:07:12.589 align:start position:0% don't need that sometimes for example if not<00:07:11.130> proofs<00:07:11.430> if<00:07:11.639> you're<00:07:11.789> trying<00:07:12.000> to<00:07:12.060> say<00:07:12.330> I 00:07:12.589 --> 00:07:12.599 align:start position:0% not proofs if you're trying to say I 00:07:12.599 --> 00:07:16.310 align:start position:0% not proofs if you're trying to say I know<00:07:12.930> a<00:07:13.530> secret<00:07:13.590> key<00:07:14.419> you<00:07:15.419> could<00:07:15.810> run<00:07:16.229> the 00:07:16.310 --> 00:07:16.320 align:start position:0% know a secret key you could run the 00:07:16.320 --> 00:07:17.570 align:start position:0% know a secret key you could run the operation<00:07:16.830> and<00:07:16.919> that<00:07:16.949> would<00:07:17.130> be<00:07:17.220> far<00:07:17.430> better 00:07:17.570 --> 00:07:17.580 align:start position:0% operation and that would be far better 00:07:17.580 --> 00:07:22.320 align:start position:0% operation and that would be far better than<00:07:17.880> running<00:07:18.060> a<00:07:18.180> snack 00:07:22.320 --> 00:07:22.330 align:start position:0% 00:07:22.330 --> 00:07:24.689 align:start position:0% the<00:07:23.110> time<00:07:23.319> when<00:07:23.470> you<00:07:23.560> do<00:07:23.830> want<00:07:24.039> to<00:07:24.099> use<00:07:24.340> a<00:07:24.370> stock 00:07:24.689 --> 00:07:24.699 align:start position:0% the time when you do want to use a stock 00:07:24.699 --> 00:07:27.420 align:start position:0% the time when you do want to use a stock is<00:07:25.120> when<00:07:25.569> you<00:07:25.780> are<00:07:25.930> proving<00:07:26.409> the<00:07:26.650> same<00:07:26.680> theorem 00:07:27.420 --> 00:07:27.430 align:start position:0% is when you are proving the same theorem 00:07:27.430 --> 00:07:29.550 align:start position:0% is when you are proving the same theorem same<00:07:27.909> application<00:07:28.419> the<00:07:28.539> same<00:07:28.750> set<00:07:29.440> of 00:07:29.550 --> 00:07:29.560 align:start position:0% same application the same set of 00:07:29.560 --> 00:07:32.059 align:start position:0% same application the same set of constraints<00:07:29.949> many<00:07:30.759> many<00:07:31.030> many<00:07:31.240> many<00:07:31.479> times 00:07:32.059 --> 00:07:32.069 align:start position:0% constraints many many many many times 00:07:32.069 --> 00:07:34.409 align:start position:0% constraints many many many many times okay<00:07:33.069> because<00:07:33.580> this<00:07:33.879> is<00:07:34.000> really<00:07:34.270> the 00:07:34.409 --> 00:07:34.419 align:start position:0% okay because this is really the 00:07:34.419 --> 00:07:36.540 align:start position:0% okay because this is really the situation<00:07:35.110> where<00:07:35.349> the<00:07:35.500> pre-processing<00:07:36.220> stage 00:07:36.540 --> 00:07:36.550 align:start position:0% situation where the pre-processing stage 00:07:36.550 --> 00:07:39.420 align:start position:0% situation where the pre-processing stage that<00:07:36.879> you<00:07:36.970> can't<00:07:37.180> start<00:07:37.509> is<00:07:38.020> going<00:07:38.560> to<00:07:38.680> benefit 00:07:39.420 --> 00:07:39.430 align:start position:0% that you can't start is going to benefit 00:07:39.430 --> 00:07:44.540 align:start position:0% that you can't start is going to benefit you<00:07:39.580> you<00:07:39.610> are<00:07:39.789> going<00:07:39.909> to<00:07:40.150> reap<00:07:41.080> the<00:07:41.259> rewards 00:07:44.540 --> 00:07:44.550 align:start position:0% 00:07:44.550 --> 00:07:49.290 align:start position:0% so<00:07:45.870> the<00:07:46.870> permits<00:07:47.800> it<00:07:48.370> does<00:07:48.550> have<00:07:48.759> very<00:07:49.000> similar 00:07:49.290 --> 00:07:49.300 align:start position:0% so the permits it does have very similar 00:07:49.300 --> 00:07:51.059 align:start position:0% so the permits it does have very similar sizes<00:07:49.720> and<00:07:50.050> by<00:07:50.139> small<00:07:50.199> I<00:07:50.440> mean<00:07:50.560> a<00:07:50.710> couple<00:07:51.009> of 00:07:51.059 --> 00:07:51.069 align:start position:0% sizes and by small I mean a couple of 00:07:51.069 --> 00:07:53.850 align:start position:0% sizes and by small I mean a couple of hundred<00:07:51.340> bytes<00:07:52.409> likewise<00:07:53.409> a<00:07:53.440> verification 00:07:53.850 --> 00:07:53.860 align:start position:0% hundred bytes likewise a verification 00:07:53.860 --> 00:07:57.209 align:start position:0% hundred bytes likewise a verification tends<00:07:54.370> to<00:07:54.490> be<00:07:54.610> really<00:07:55.090> fast<00:07:55.800> but<00:07:56.800> if<00:07:56.949> you<00:07:57.039> often 00:07:57.209 --> 00:07:57.219 align:start position:0% tends to be really fast but if you often 00:07:57.219 --> 00:08:00.260 align:start position:0% tends to be really fast but if you often eat<00:07:57.400> rustic<00:07:57.789> setup<00:07:58.180> which<00:07:58.780> is<00:07:59.289> a<00:07:59.349> downside 00:08:00.260 --> 00:08:00.270 align:start position:0% eat rustic setup which is a downside 00:08:00.270 --> 00:08:02.430 align:start position:0% eat rustic setup which is a downside also<00:08:01.270> they<00:08:01.449> rely<00:08:01.690> on<00:08:01.719> for<00:08:02.020> some<00:08:02.169> funky 00:08:02.430 --> 00:08:02.440 align:start position:0% also they rely on for some funky 00:08:02.440 --> 00:08:03.899 align:start position:0% also they rely on for some funky assumptions<00:08:02.919> and<00:08:03.039> my<00:08:03.099> funky<00:08:03.430> assumptions<00:08:03.819> I 00:08:03.899 --> 00:08:03.909 align:start position:0% assumptions and my funky assumptions I 00:08:03.909 --> 00:08:05.339 align:start position:0% assumptions and my funky assumptions I do<00:08:03.969> not<00:08:04.150> mean<00:08:04.330> wrong<00:08:04.479> assumptions<00:08:04.960> we<00:08:05.139> can't 00:08:05.339 --> 00:08:05.349 align:start position:0% do not mean wrong assumptions we can't 00:08:05.349 --> 00:08:07.890 align:start position:0% do not mean wrong assumptions we can't break<00:08:05.560> them<00:08:05.800> what<00:08:06.729> I<00:08:06.759> mean<00:08:07.090> is<00:08:07.449> that<00:08:07.629> we<00:08:07.780> don't 00:08:07.890 --> 00:08:07.900 align:start position:0% break them what I mean is that we don't 00:08:07.900 --> 00:08:09.360 align:start position:0% break them what I mean is that we don't understand<00:08:08.440> them<00:08:08.560> very<00:08:08.590> well<00:08:08.919> and<00:08:08.979> that<00:08:09.190> makes 00:08:09.360 --> 00:08:09.370 align:start position:0% understand them very well and that makes 00:08:09.370 --> 00:08:13.770 align:start position:0% understand them very well and that makes us<00:08:09.460> uncomfortable<00:08:11.310> and<00:08:12.310> finally<00:08:13.270> and<00:08:13.569> this<00:08:13.599> is 00:08:13.770 --> 00:08:13.780 align:start position:0% us uncomfortable and finally and this is 00:08:13.780 --> 00:08:15.240 align:start position:0% us uncomfortable and finally and this is also<00:08:14.110> a<00:08:14.259> pretty<00:08:14.560> important<00:08:14.949> point<00:08:15.099> the 00:08:15.240 --> 00:08:15.250 align:start position:0% also a pretty important point the 00:08:15.250 --> 00:08:17.640 align:start position:0% also a pretty important point the previous<00:08:15.520> are<00:08:15.639> not<00:08:15.849> cheap<00:08:16.120> the<00:08:16.960> previous<00:08:17.349> can 00:08:17.640 --> 00:08:17.650 align:start position:0% previous are not cheap the previous can 00:08:17.650 --> 00:08:19.200 align:start position:0% previous are not cheap the previous can be<00:08:17.800> a<00:08:17.830> big<00:08:18.069> barrier<00:08:18.310> to<00:08:18.520> actually<00:08:18.789> using<00:08:19.090> these 00:08:19.200 --> 00:08:19.210 align:start position:0% be a big barrier to actually using these 00:08:19.210 --> 00:08:24.240 align:start position:0% be a big barrier to actually using these things<00:08:19.389> in<00:08:19.509> practice<00:08:22.409> so<00:08:23.409> now<00:08:23.770> to<00:08:23.830> run<00:08:24.069> through 00:08:24.240 --> 00:08:24.250 align:start position:0% things in practice so now to run through 00:08:24.250 --> 00:08:27.390 align:start position:0% things in practice so now to run through a<00:08:24.310> few<00:08:24.340> schemes<00:08:25.020> the<00:08:26.020> first<00:08:26.409> one<00:08:26.590> if<00:08:26.860> will<00:08:27.250> you 00:08:27.390 --> 00:08:27.400 align:start position:0% a few schemes the first one if will you 00:08:27.400 --> 00:08:30.809 align:start position:0% a few schemes the first one if will you either<00:08:27.610> speed<00:08:28.000> grow<00:08:28.990> 16<00:08:29.560> is<00:08:29.860> the<00:08:29.919> fastest 00:08:30.809 --> 00:08:30.819 align:start position:0% either speed grow 16 is the fastest 00:08:30.819 --> 00:08:32.370 align:start position:0% either speed grow 16 is the fastest snack<00:08:31.060> in<00:08:31.240> the<00:08:31.270> literature<00:08:31.630> which<00:08:32.079> has<00:08:32.140> the 00:08:32.370 --> 00:08:32.380 align:start position:0% snack in the literature which has the 00:08:32.380 --> 00:08:34.649 align:start position:0% snack in the literature which has the smallest<00:08:32.680> criticize<00:08:33.250> fastest<00:08:33.909> verification 00:08:34.649 --> 00:08:34.659 align:start position:0% smallest criticize fastest verification 00:08:34.659 --> 00:08:37.290 align:start position:0% smallest criticize fastest verification time<00:08:34.899> the<00:08:35.260> fastest<00:08:35.740> approval<00:08:36.099> time<00:08:36.310> is 00:08:37.290 --> 00:08:37.300 align:start position:0% time the fastest approval time is 00:08:37.300 --> 00:08:40.400 align:start position:0% time the fastest approval time is generally<00:08:37.750> great 00:08:40.400 --> 00:08:40.410 align:start position:0% 00:08:40.410 --> 00:08:43.460 align:start position:0% this<00:08:41.419> wasn't<00:08:42.419> just<00:08:42.599> as<00:08:42.840> I've<00:08:42.960> made<00:08:43.080> a<00:08:43.110> part<00:08:43.380> of 00:08:43.460 --> 00:08:43.470 align:start position:0% this wasn't just as I've made a part of 00:08:43.470 --> 00:08:45.230 align:start position:0% this wasn't just as I've made a part of thinner<00:08:43.710> it's<00:08:44.070> actually<00:08:44.250> the<00:08:44.580> result<00:08:44.910> of<00:08:44.970> a 00:08:45.230 --> 00:08:45.240 align:start position:0% thinner it's actually the result of a 00:08:45.240 --> 00:08:46.460 align:start position:0% thinner it's actually the result of a huge<00:08:45.450> line<00:08:45.750> of<00:08:45.780> Wax 00:08:46.460 --> 00:08:46.470 align:start position:0% huge line of Wax 00:08:46.470 --> 00:08:48.320 align:start position:0% huge line of Wax starting<00:08:47.190> from<00:08:47.370> Janeiro<00:08:47.790> and<00:08:47.880> others<00:08:48.180> who 00:08:48.320 --> 00:08:48.330 align:start position:0% starting from Janeiro and others who 00:08:48.330 --> 00:08:50.330 align:start position:0% starting from Janeiro and others who found<00:08:48.570> a<00:08:48.720> really<00:08:48.960> nice<00:08:49.140> way<00:08:49.440> to<00:08:49.500> encode<00:08:50.160> the 00:08:50.330 --> 00:08:50.340 align:start position:0% found a really nice way to encode the 00:08:50.340 --> 00:08:51.560 align:start position:0% found a really nice way to encode the programs<00:08:50.730> that<00:08:50.880> we're<00:08:51.030> trying<00:08:51.180> to<00:08:51.300> prove 00:08:51.560 --> 00:08:51.570 align:start position:0% programs that we're trying to prove 00:08:51.570 --> 00:08:55.100 align:start position:0% programs that we're trying to prove which<00:08:52.380> was<00:08:52.590> later<00:08:53.010> than<00:08:53.720> people<00:08:54.720> found<00:08:54.930> where 00:08:55.100 --> 00:08:55.110 align:start position:0% which was later than people found where 00:08:55.110 --> 00:08:57.230 align:start position:0% which was later than people found where to<00:08:55.290> turn<00:08:56.010> us<00:08:56.190> into<00:08:56.220> rank<00:08:56.670> on<00:08:56.820> constraint 00:08:57.230 --> 00:08:57.240 align:start position:0% to turn us into rank on constraint 00:08:57.240 --> 00:08:59.240 align:start position:0% to turn us into rank on constraint systems<00:08:57.660> which<00:08:57.870> are<00:08:58.080> the<00:08:58.320> general<00:08:58.860> standard 00:08:59.240 --> 00:08:59.250 align:start position:0% systems which are the general standard 00:08:59.250 --> 00:09:01.100 align:start position:0% systems which are the general standard people<00:08:59.580> tend<00:08:59.730> to<00:08:59.760> use<00:08:59.820> now<00:09:00.090> for<00:09:00.450> computing<00:09:01.050> the 00:09:01.100 --> 00:09:01.110 align:start position:0% people tend to use now for computing the 00:09:01.110 --> 00:09:03.290 align:start position:0% people tend to use now for computing the constraints<00:09:01.560> and<00:09:01.710> then<00:09:02.610> there<00:09:02.820> was<00:09:02.940> a<00:09:02.970> line<00:09:03.270> of 00:09:03.290 --> 00:09:03.300 align:start position:0% constraints and then there was a line of 00:09:03.300 --> 00:09:05.240 align:start position:0% constraints and then there was a line of papers<00:09:03.870> that<00:09:04.140> way<00:09:04.230> each<00:09:04.410> optimizing<00:09:05.130> the 00:09:05.240 --> 00:09:05.250 align:start position:0% papers that way each optimizing the 00:09:05.250 --> 00:09:06.830 align:start position:0% papers that way each optimizing the rezidentura<00:09:05.730> governments<00:09:06.270> immediate 00:09:06.830 --> 00:09:06.840 align:start position:0% rezidentura governments immediate 00:09:06.840 --> 00:09:09.250 align:start position:0% rezidentura governments immediate gratification<00:09:07.280> processes<00:09:08.280> that<00:09:08.430> were<00:09:08.550> needed 00:09:09.250 --> 00:09:09.260 align:start position:0% gratification processes that were needed 00:09:09.260 --> 00:09:11.270 align:start position:0% gratification processes that were needed finishing<00:09:10.260> them<00:09:10.410> with<00:09:10.560> broad<00:09:10.800> scheme<00:09:11.070> which 00:09:11.270 --> 00:09:11.280 align:start position:0% finishing them with broad scheme which 00:09:11.280 --> 00:09:15.560 align:start position:0% finishing them with broad scheme which is<00:09:11.310> in<00:09:11.550> the<00:09:11.640> generic<00:09:11.940> great<00:09:12.090> model<00:09:14.570> the 00:09:15.560 --> 00:09:15.570 align:start position:0% is in the generic great model the 00:09:15.570 --> 00:09:17.900 align:start position:0% is in the generic great model the downside<00:09:16.050> here<00:09:16.260> is<00:09:16.500> that<00:09:16.740> there<00:09:17.040> is<00:09:17.250> a<00:09:17.520> trusted 00:09:17.900 --> 00:09:17.910 align:start position:0% downside here is that there is a trusted 00:09:17.910 --> 00:09:21.350 align:start position:0% downside here is that there is a trusted set<00:09:18.120> up<00:09:18.300> and<00:09:18.890> I'm<00:09:19.890> going<00:09:20.100> to<00:09:20.190> do<00:09:20.430> a<00:09:20.460> very<00:09:21.210> very 00:09:21.350 --> 00:09:21.360 align:start position:0% set up and I'm going to do a very very 00:09:21.360 --> 00:09:23.390 align:start position:0% set up and I'm going to do a very very quick<00:09:21.900> explanation<00:09:22.230> of<00:09:22.740> what<00:09:22.920> they<00:09:23.040> mean<00:09:23.190> by 00:09:23.390 --> 00:09:23.400 align:start position:0% quick explanation of what they mean by 00:09:23.400 --> 00:09:25.370 align:start position:0% quick explanation of what they mean by that<00:09:23.430> a<00:09:23.880> secure<00:09:24.390> don't<00:09:24.570> understand<00:09:24.990> me<00:09:25.200> then 00:09:25.370 --> 00:09:25.380 align:start position:0% that a secure don't understand me then 00:09:25.380 --> 00:09:26.750 align:start position:0% that a secure don't understand me then Nagori<00:09:25.950> because<00:09:26.160> it<00:09:26.280> would<00:09:26.400> be<00:09:26.460> quite<00:09:26.640> bad 00:09:26.750 --> 00:09:26.760 align:start position:0% Nagori because it would be quite bad 00:09:26.760 --> 00:09:30.710 align:start position:0% Nagori because it would be quite bad promise<00:09:28.640> so<00:09:29.640> before<00:09:30.030> the<00:09:30.210> proven<00:09:30.570> and<00:09:30.630> the 00:09:30.710 --> 00:09:30.720 align:start position:0% promise so before the proven and the 00:09:30.720 --> 00:09:32.270 align:start position:0% promise so before the proven and the verify<00:09:31.140> can<00:09:31.380> grant<00:09:31.620> I<00:09:31.770> was<00:09:31.920> saying<00:09:32.130> that 00:09:32.270 --> 00:09:32.280 align:start position:0% verify can grant I was saying that 00:09:32.280 --> 00:09:33.860 align:start position:0% verify can grant I was saying that there's<00:09:32.490> this<00:09:32.640> expensive<00:09:33.240> trust<00:09:33.510> in<00:09:33.660> such<00:09:33.840> a 00:09:33.860 --> 00:09:33.870 align:start position:0% there's this expensive trust in such a 00:09:33.870 --> 00:09:36.170 align:start position:0% there's this expensive trust in such a process<00:09:34.440> what<00:09:35.010> sorry<00:09:35.460> this<00:09:35.700> expensive 00:09:36.170 --> 00:09:36.180 align:start position:0% process what sorry this expensive 00:09:36.180 --> 00:09:37.130 align:start position:0% process what sorry this expensive progressing 00:09:37.130 --> 00:09:37.140 align:start position:0% progressing 00:09:37.140 --> 00:09:39.830 align:start position:0% progressing step<00:09:37.950> but<00:09:38.850> impairing<00:09:39.210> mistakes<00:09:39.630> it's 00:09:39.830 --> 00:09:39.840 align:start position:0% step but impairing mistakes it's 00:09:39.840 --> 00:09:42.400 align:start position:0% step but impairing mistakes it's actually<00:09:40.110> worse<00:09:40.290> than<00:09:40.320> that<00:09:40.740> because<00:09:41.400> the 00:09:42.400 --> 00:09:42.410 align:start position:0% actually worse than that because the 00:09:42.410 --> 00:09:45.080 align:start position:0% actually worse than that because the needs<00:09:43.410> don't<00:09:43.620> we<00:09:43.710> do<00:09:43.800> at<00:09:43.890> the<00:09:43.980> start<00:09:44.190> some<00:09:45.060> of 00:09:45.080 --> 00:09:45.090 align:start position:0% needs don't we do at the start some of 00:09:45.090 --> 00:09:47.180 align:start position:0% needs don't we do at the start some of the<00:09:45.300> inputs<00:09:45.810> to<00:09:46.050> this<00:09:46.140> pre-processing<00:09:46.800> have 00:09:47.180 --> 00:09:47.190 align:start position:0% the inputs to this pre-processing have 00:09:47.190 --> 00:09:49.640 align:start position:0% the inputs to this pre-processing have to<00:09:47.340> be<00:09:47.430> secret<00:09:47.910> in<00:09:48.210> order<00:09:48.840> for<00:09:49.200> you<00:09:49.350> to<00:09:49.380> have<00:09:49.620> a 00:09:49.640 --> 00:09:49.650 align:start position:0% to be secret in order for you to have a 00:09:49.650 --> 00:09:53.540 align:start position:0% to be secret in order for you to have a secure<00:09:50.040> scheme<00:09:50.280> at<00:09:50.400> the<00:09:50.460> end<00:09:50.610> and<00:09:52.370> worse<00:09:53.370> than 00:09:53.540 --> 00:09:53.550 align:start position:0% secure scheme at the end and worse than 00:09:53.550 --> 00:09:56.600 align:start position:0% secure scheme at the end and worse than that<00:09:53.730> the<00:09:54.090> secrets<00:09:54.660> are<00:09:54.870> very<00:09:55.230> structured<00:09:55.610> and 00:09:56.600 --> 00:09:56.610 align:start position:0% that the secrets are very structured and 00:09:56.610 --> 00:09:57.740 align:start position:0% that the secrets are very structured and we<00:09:56.730> actually<00:09:57.000> don't<00:09:57.120> know<00:09:57.240> how<00:09:57.390> to<00:09:57.450> generate 00:09:57.740 --> 00:09:57.750 align:start position:0% we actually don't know how to generate 00:09:57.750 --> 00:10:01.010 align:start position:0% we actually don't know how to generate them<00:09:58.290> without<00:09:59.130> somebody<00:09:59.660> knowing<00:10:00.660> what<00:10:00.930> they 00:10:01.010 --> 00:10:01.020 align:start position:0% them without somebody knowing what they 00:10:01.020 --> 00:10:04.730 align:start position:0% them without somebody knowing what they are<00:10:01.550> so<00:10:02.550> we<00:10:02.910> can<00:10:03.420> get<00:10:03.570> around<00:10:03.810> this<00:10:04.020> but 00:10:04.730 --> 00:10:04.740 align:start position:0% are so we can get around this but 00:10:04.740 --> 00:10:06.590 align:start position:0% are so we can get around this but largely<00:10:05.250> the<00:10:05.490> way<00:10:05.580> we<00:10:05.730> get<00:10:05.820> around<00:10:06.090> this<00:10:06.270> is<00:10:06.450> we 00:10:06.590 --> 00:10:06.600 align:start position:0% largely the way we get around this is we 00:10:06.600 --> 00:10:09.590 align:start position:0% largely the way we get around this is we have<00:10:06.810> many<00:10:07.350> many<00:10:07.800> participants<00:10:08.210> all<00:10:09.210> having<00:10:09.540> a 00:10:09.590 --> 00:10:09.600 align:start position:0% have many many participants all having a 00:10:09.600 --> 00:10:11.199 align:start position:0% have many many participants all having a little<00:10:09.900> bit<00:10:10.020> of<00:10:10.140> the<00:10:10.230> secret 00:10:11.199 --> 00:10:11.209 align:start position:0% little bit of the secret 00:10:11.209 --> 00:10:13.929 align:start position:0% little bit of the secret and<00:10:11.329> working<00:10:12.199> together<00:10:12.470> to<00:10:13.009> output<00:10:13.610> the 00:10:13.929 --> 00:10:13.939 align:start position:0% and working together to output the 00:10:13.939 --> 00:10:16.449 align:start position:0% and working together to output the parameters<00:10:14.839> that<00:10:15.050> the<00:10:15.199> actual<00:10:15.559> prefer<00:10:16.249> and 00:10:16.449 --> 00:10:16.459 align:start position:0% parameters that the actual prefer and 00:10:16.459 --> 00:10:22.359 align:start position:0% parameters that the actual prefer and verify<00:10:16.850> use<00:10:17.240> and<00:10:19.660> this<00:10:20.660> is<00:10:20.899> kind<00:10:21.740> of<00:10:21.860> nice<00:10:22.100> in 00:10:22.359 --> 00:10:22.369 align:start position:0% verify use and this is kind of nice in 00:10:22.369 --> 00:10:25.739 align:start position:0% verify use and this is kind of nice in the<00:10:22.639> sense<00:10:22.879> that<00:10:23.029> if<00:10:23.869> all<00:10:24.410> of<00:10:24.769> the<00:10:24.889> parties 00:10:25.739 --> 00:10:25.749 align:start position:0% the sense that if all of the parties 00:10:25.749 --> 00:10:28.210 align:start position:0% the sense that if all of the parties collude<00:10:26.749> then<00:10:27.230> sure<00:10:27.499> you<00:10:27.829> don't<00:10:28.009> get<00:10:28.100> any 00:10:28.210 --> 00:10:28.220 align:start position:0% collude then sure you don't get any 00:10:28.220 --> 00:10:30.609 align:start position:0% collude then sure you don't get any guarantees<00:10:28.910> whatsoever<00:10:29.110> but<00:10:30.110> if<00:10:30.259> a<00:10:30.350> single 00:10:30.609 --> 00:10:30.619 align:start position:0% guarantees whatsoever but if a single 00:10:30.619 --> 00:10:34.059 align:start position:0% guarantees whatsoever but if a single one<00:10:30.889> of<00:10:30.920> those<00:10:31.129> parties<00:10:31.550> is<00:10:31.730> honest<00:10:32.319> then<00:10:33.319> sure 00:10:34.059 --> 00:10:34.069 align:start position:0% one of those parties is honest then sure 00:10:34.069 --> 00:10:35.470 align:start position:0% one of those parties is honest then sure there<00:10:34.309> could<00:10:34.490> be<00:10:34.519> other<00:10:34.790> points<00:10:35.179> of<00:10:35.300> failure 00:10:35.470 --> 00:10:35.480 align:start position:0% there could be other points of failure 00:10:35.480 --> 00:10:38.290 align:start position:0% there could be other points of failure but<00:10:36.319> you'll<00:10:36.860> need<00:10:37.040> that<00:10:37.610> you're<00:10:37.790> not<00:10:37.939> going<00:10:38.179> to 00:10:38.290 --> 00:10:38.300 align:start position:0% but you'll need that you're not going to 00:10:38.300 --> 00:10:39.939 align:start position:0% but you'll need that you're not going to have<00:10:38.480> the<00:10:38.629> point<00:10:38.839> of<00:10:38.929> failure<00:10:39.110> being<00:10:39.439> that<00:10:39.679> the 00:10:39.939 --> 00:10:39.949 align:start position:0% have the point of failure being that the 00:10:39.949 --> 00:10:41.319 align:start position:0% have the point of failure being that the trusted<00:10:40.369> stuffs<00:10:40.550> I've<00:10:40.699> had<00:10:40.879> commuting 00:10:41.319 --> 00:10:41.329 align:start position:0% trusted stuffs I've had commuting 00:10:41.329 --> 00:10:48.699 align:start position:0% trusted stuffs I've had commuting parties<00:10:42.339> okay<00:10:44.199> and<00:10:46.269> sometimes<00:10:47.439> this<00:10:48.439> is 00:10:48.699 --> 00:10:48.709 align:start position:0% parties okay and sometimes this is 00:10:48.709 --> 00:10:52.030 align:start position:0% parties okay and sometimes this is enough<00:10:49.249> for<00:10:49.600> example<00:10:50.600> if<00:10:50.689> you<00:10:50.809> have<00:10:51.019> a<00:10:51.290> closed 00:10:52.030 --> 00:10:52.040 align:start position:0% enough for example if you have a closed 00:10:52.040 --> 00:10:54.669 align:start position:0% enough for example if you have a closed set<00:10:52.519> of<00:10:52.639> participants<00:10:53.209> where<00:10:54.170> you<00:10:54.290> don't<00:10:54.499> have 00:10:54.669 --> 00:10:54.679 align:start position:0% set of participants where you don't have 00:10:54.679 --> 00:10:56.350 align:start position:0% set of participants where you don't have people<00:10:55.069> joining<00:10:55.339> and<00:10:55.610> leaving<00:10:55.639> at<00:10:55.970> any<00:10:56.089> point 00:10:56.350 --> 00:10:56.360 align:start position:0% people joining and leaving at any point 00:10:56.360 --> 00:10:59.139 align:start position:0% people joining and leaving at any point in<00:10:56.509> time<00:10:56.540> but<00:10:57.290> you<00:10:57.410> just<00:10:57.589> say<00:10:57.800> have<00:10:58.160> a<00:10:58.519> hundred 00:10:59.139 --> 00:10:59.149 align:start position:0% in time but you just say have a hundred 00:10:59.149 --> 00:11:01.359 align:start position:0% in time but you just say have a hundred people<00:10:59.449> that<00:10:59.809> are<00:10:59.959> always<00:11:00.259> the<00:11:00.410> same<00:11:00.439> then 00:11:01.359 --> 00:11:01.369 align:start position:0% people that are always the same then 00:11:01.369 --> 00:11:02.590 align:start position:0% people that are always the same then they<00:11:01.519> can<00:11:01.699> just<00:11:01.730> run<00:11:01.939> the<00:11:02.059> trust<00:11:02.240> setup 00:11:02.590 --> 00:11:02.600 align:start position:0% they can just run the trust setup 00:11:02.600 --> 00:11:05.109 align:start position:0% they can just run the trust setup process<00:11:02.749> themselves<00:11:03.110> and<00:11:03.740> because<00:11:04.309> they<00:11:04.939> have 00:11:05.109 --> 00:11:05.119 align:start position:0% process themselves and because they have 00:11:05.119 --> 00:11:06.910 align:start position:0% process themselves and because they have run<00:11:05.269> it's<00:11:05.449> been<00:11:05.959> part<00:11:06.230> of<00:11:06.290> the<00:11:06.379> process<00:11:06.589> if 00:11:06.910 --> 00:11:06.920 align:start position:0% run it's been part of the process if 00:11:06.920 --> 00:11:08.739 align:start position:0% run it's been part of the process if they<00:11:07.069> know<00:11:07.249> that<00:11:07.279> it's<00:11:07.639> okay<00:11:07.970> they<00:11:08.389> know<00:11:08.600> that 00:11:08.739 --> 00:11:08.749 align:start position:0% they know that it's okay they know that 00:11:08.749 --> 00:11:10.600 align:start position:0% they know that it's okay they know that they<00:11:08.899> themselves<00:11:09.050> are<00:11:09.499> honest<00:11:09.860> and<00:11:10.459> that's 00:11:10.600 --> 00:11:10.610 align:start position:0% they themselves are honest and that's 00:11:10.610 --> 00:11:11.169 align:start position:0% they themselves are honest and that's great 00:11:11.169 --> 00:11:11.179 align:start position:0% great 00:11:11.179 --> 00:11:13.359 align:start position:0% great and<00:11:11.269> the<00:11:11.600> main<00:11:11.779> thing<00:11:11.809> they<00:11:12.499> can<00:11:12.649> use<00:11:12.800> cross<00:11:12.980> 16 00:11:13.359 --> 00:11:13.369 align:start position:0% and the main thing they can use cross 16 00:11:13.369 --> 00:11:15.689 align:start position:0% and the main thing they can use cross 16 which<00:11:13.610> is<00:11:13.639> the<00:11:13.999> scheme<00:11:14.389> in<00:11:14.480> the<00:11:14.540> literature 00:11:15.689 --> 00:11:15.699 align:start position:0% which is the scheme in the literature 00:11:15.699 --> 00:11:18.100 align:start position:0% which is the scheme in the literature likewise<00:11:16.699> if<00:11:16.939> you<00:11:17.029> have<00:11:17.209> a<00:11:17.240> way<00:11:17.449> to<00:11:17.509> actually 00:11:18.100 --> 00:11:18.110 align:start position:0% likewise if you have a way to actually 00:11:18.110 --> 00:11:21.910 align:start position:0% likewise if you have a way to actually verify<00:11:18.529> that<00:11:19.389> that's<00:11:20.389> any<00:11:20.809> given<00:11:21.259> computation 00:11:21.910 --> 00:11:21.920 align:start position:0% verify that that's any given computation 00:11:21.920 --> 00:11:24.639 align:start position:0% verify that that's any given computation that<00:11:21.949> has<00:11:22.579> been<00:11:22.879> proven<00:11:23.389> is<00:11:23.720> wrong<00:11:23.990> and<00:11:24.259> at 00:11:24.639 --> 00:11:24.649 align:start position:0% that has been proven is wrong and at 00:11:24.649 --> 00:11:26.109 align:start position:0% that has been proven is wrong and at least<00:11:24.769> you<00:11:24.949> would<00:11:25.069> know<00:11:25.249> something<00:11:25.730> bad<00:11:25.879> has 00:11:26.109 --> 00:11:26.119 align:start position:0% least you would know something bad has 00:11:26.119 --> 00:11:28.419 align:start position:0% least you would know something bad has happened<00:11:26.149> and<00:11:26.689> this<00:11:26.809> can<00:11:27.069> can't<00:11:28.069> be<00:11:28.189> the<00:11:28.279> case 00:11:28.419 --> 00:11:28.429 align:start position:0% happened and this can can't be the case 00:11:28.429 --> 00:11:29.550 align:start position:0% happened and this can can't be the case for<00:11:28.639> example<00:11:28.699> you 00:11:29.550 --> 00:11:29.560 align:start position:0% for example you 00:11:29.560 --> 00:11:31.139 align:start position:0% for example you these<00:11:29.769> things<00:11:30.009> put<00:11:30.160> sharks<00:11:30.639> which<00:11:30.850> is<00:11:30.999> where 00:11:31.139 --> 00:11:31.149 align:start position:0% these things put sharks which is where 00:11:31.149 --> 00:11:32.249 align:start position:0% these things put sharks which is where you<00:11:31.300> have<00:11:31.480> your<00:11:31.600> prove<00:11:31.779> being<00:11:32.019> like<00:11:32.230> a 00:11:32.249 --> 00:11:32.259 align:start position:0% you have your prove being like a 00:11:32.259 --> 00:11:33.749 align:start position:0% you have your prove being like a bulletproof<00:11:32.649> thing<00:11:32.980> which<00:11:33.160> don't<00:11:33.430> have<00:11:33.610> try 00:11:33.749 --> 00:11:33.759 align:start position:0% bulletproof thing which don't have try 00:11:33.759 --> 00:11:35.819 align:start position:0% bulletproof thing which don't have try success<00:11:34.089> up<00:11:34.240> but<00:11:34.810> then<00:11:34.899> you<00:11:34.990> also<00:11:35.199> rather<00:11:35.529> snap 00:11:35.819 --> 00:11:35.829 align:start position:0% success up but then you also rather snap 00:11:35.829 --> 00:11:37.079 align:start position:0% success up but then you also rather snap on<00:11:36.040> top<00:11:36.189> of<00:11:36.339> it<00:11:36.490> in<00:11:36.610> order<00:11:36.699> to<00:11:36.850> get<00:11:36.970> the 00:11:37.079 --> 00:11:37.089 align:start position:0% on top of it in order to get the 00:11:37.089 --> 00:11:39.239 align:start position:0% on top of it in order to get the verification<00:11:37.629> costs<00:11:37.990> down<00:11:38.230> but<00:11:38.920> you<00:11:39.040> still 00:11:39.239 --> 00:11:39.249 align:start position:0% verification costs down but you still 00:11:39.249 --> 00:11:40.679 align:start position:0% verification costs down but you still have<00:11:39.399> the<00:11:39.490> original<00:11:39.579> proof<00:11:40.060> so<00:11:40.209> you<00:11:40.269> can<00:11:40.480> still 00:11:40.679 --> 00:11:40.689 align:start position:0% have the original proof so you can still 00:11:40.689 --> 00:11:42.300 align:start position:0% have the original proof so you can still at<00:11:40.810> least<00:11:41.019> check<00:11:41.319> that<00:11:41.949> we<00:11:42.069> originally 00:11:42.300 --> 00:11:42.310 align:start position:0% at least check that we originally 00:11:42.310 --> 00:11:47.009 align:start position:0% at least check that we originally proposed<00:11:44.129> also<00:11:45.129> very<00:11:45.790> rare<00:11:46.089> situation<00:11:46.749> for 00:11:47.009 --> 00:11:47.019 align:start position:0% proposed also very rare situation for 00:11:47.019 --> 00:11:49.350 align:start position:0% proposed also very rare situation for decentralized<00:11:47.529> technologies<00:11:48.339> thus<00:11:49.120> if<00:11:49.329> you 00:11:49.350 --> 00:11:49.360 align:start position:0% decentralized technologies thus if you 00:11:49.360 --> 00:11:51.900 align:start position:0% decentralized technologies thus if you do<00:11:49.569> have<00:11:49.779> a<00:11:49.809> central<00:11:50.259> traffic<00:11:50.439> passing<00:11:51.040> and<00:11:51.249> no 00:11:51.900 --> 00:11:51.910 align:start position:0% do have a central traffic passing and no 00:11:51.910 --> 00:11:52.760 align:start position:0% do have a central traffic passing and no problem 00:11:52.760 --> 00:11:52.770 align:start position:0% problem 00:11:52.770 --> 00:11:55.610 align:start position:0% problem [Music] 00:11:55.610 --> 00:11:55.620 align:start position:0% [Music] 00:11:55.620 --> 00:11:57.749 align:start position:0% [Music] one<00:11:56.620> nice<00:11:56.829> thing<00:11:56.860> about<00:11:57.069> science<00:11:57.550> is<00:11:57.699> that 00:11:57.749 --> 00:11:57.759 align:start position:0% one nice thing about science is that 00:11:57.759 --> 00:11:59.730 align:start position:0% one nice thing about science is that they<00:11:58.059> are<00:11:58.149> very<00:11:58.480> highly<00:11:58.720> paralyzed<00:11:59.230> book<00:11:59.499> and 00:11:59.730 --> 00:11:59.740 align:start position:0% they are very highly paralyzed book and 00:11:59.740 --> 00:12:01.650 align:start position:0% they are very highly paralyzed book and there's<00:12:00.430> a<00:12:00.550> work<00:12:00.790> crew<00:12:01.089> disick<00:12:01.480> which 00:12:01.650 --> 00:12:01.660 align:start position:0% there's a work crew disick which 00:12:01.660 --> 00:12:03.239 align:start position:0% there's a work crew disick which explains<00:12:02.139> exactly<00:12:02.319> how<00:12:02.620> to<00:12:02.680> do<00:12:02.889> there's<00:12:03.069> not 00:12:03.239 --> 00:12:03.249 align:start position:0% explains exactly how to do there's not 00:12:03.249 --> 00:12:05.340 align:start position:0% explains exactly how to do there's not just<00:12:03.279> for<00:12:03.730> the<00:12:03.939> great<00:12:04.300> exponentiations<00:12:04.990> but 00:12:05.340 --> 00:12:05.350 align:start position:0% just for the great exponentiations but 00:12:05.350 --> 00:12:07.920 align:start position:0% just for the great exponentiations but also<00:12:05.499> for<00:12:05.829> the<00:12:05.980> fast<00:12:06.189> Fourier<00:12:06.519> transforms<00:12:07.120> so 00:12:07.920 --> 00:12:07.930 align:start position:0% also for the fast Fourier transforms so 00:12:07.930 --> 00:12:09.840 align:start position:0% also for the fast Fourier transforms so if<00:12:08.110> you're<00:12:08.259> looking<00:12:08.410> to<00:12:08.769> paralyze<00:12:09.279> snacks<00:12:09.639> and 00:12:09.840 --> 00:12:09.850 align:start position:0% if you're looking to paralyze snacks and 00:12:09.850 --> 00:12:11.220 align:start position:0% if you're looking to paralyze snacks and I<00:12:09.939> definitely<00:12:10.120> recommend<00:12:10.779> taking<00:12:10.899> that<00:12:11.139> one 00:12:11.220 --> 00:12:11.230 align:start position:0% I definitely recommend taking that one 00:12:11.230 --> 00:12:15.900 align:start position:0% I definitely recommend taking that one out<00:12:13.889> another<00:12:14.889> really<00:12:15.189> cool<00:12:15.339> thing<00:12:15.399> you<00:12:15.579> can<00:12:15.699> do 00:12:15.900 --> 00:12:15.910 align:start position:0% out another really cool thing you can do 00:12:15.910 --> 00:12:18.210 align:start position:0% out another really cool thing you can do with<00:12:16.089> starts<00:12:16.480> you<00:12:17.410> can<00:12:17.589> have<00:12:17.800> the<00:12:17.949> snack<00:12:18.189> of 00:12:18.210 --> 00:12:18.220 align:start position:0% with starts you can have the snack of 00:12:18.220 --> 00:12:20.160 align:start position:0% with starts you can have the snack of the<00:12:18.459> staff<00:12:18.670> it's<00:12:18.939> not<00:12:19.120> the<00:12:19.389> snack<00:12:19.600> that<00:12:19.809> is<00:12:19.870> not 00:12:20.160 --> 00:12:20.170 align:start position:0% the staff it's not the snack that is not 00:12:20.170 --> 00:12:23.850 align:start position:0% the staff it's not the snack that is not gives<00:12:20.439> verifies<00:12:21.129> and<00:12:21.990> every<00:12:22.990> single<00:12:23.230> time<00:12:23.439> you 00:12:23.850 --> 00:12:23.860 align:start position:0% gives verifies and every single time you 00:12:23.860 --> 00:12:26.360 align:start position:0% gives verifies and every single time you run<00:12:24.610> a<00:12:24.939> numbers<00:12:25.329> expecting<00:12:25.839> the<00:12:25.899> recursion 00:12:26.360 --> 00:12:26.370 align:start position:0% run a numbers expecting the recursion 00:12:26.370 --> 00:12:29.009 align:start position:0% run a numbers expecting the recursion run<00:12:27.370> another<00:12:27.579> snack<00:12:27.879> you<00:12:28.509> get<00:12:28.689> something 00:12:29.009 --> 00:12:29.019 align:start position:0% run another snack you get something 00:12:29.019 --> 00:12:30.660 align:start position:0% run another snack you get something which<00:12:29.170> is<00:12:29.319> smaller<00:12:29.589> and<00:12:29.860> cheaper<00:12:29.889> to<00:12:30.220> verify 00:12:30.660 --> 00:12:30.670 align:start position:0% which is smaller and cheaper to verify 00:12:30.670 --> 00:12:32.579 align:start position:0% which is smaller and cheaper to verify meaning<00:12:31.360> about<00:12:31.509> the<00:12:31.600> full<00:12:31.809> system<00:12:32.079> would<00:12:32.439> be 00:12:32.579 --> 00:12:32.589 align:start position:0% meaning about the full system would be 00:12:32.589 --> 00:12:35.869 align:start position:0% meaning about the full system would be really<00:12:33.160> small<00:12:33.939> and<00:12:34.120> really<00:12:34.180> fast<00:12:34.600> a<00:12:34.689> verify 00:12:35.869 --> 00:12:35.879 align:start position:0% really small and really fast a verify 00:12:35.879 --> 00:12:39.269 align:start position:0% really small and really fast a verify this<00:12:37.110> isn't<00:12:38.110> as<00:12:38.290> simple<00:12:38.319> as<00:12:38.649> it<00:12:38.800> sounds 00:12:39.269 --> 00:12:39.279 align:start position:0% this isn't as simple as it sounds 00:12:39.279 --> 00:12:42.569 align:start position:0% this isn't as simple as it sounds in<00:12:39.879> particular<00:12:40.290> the<00:12:41.290> security<00:12:42.069> assumptions 00:12:42.569 --> 00:12:42.579 align:start position:0% in particular the security assumptions 00:12:42.579 --> 00:12:43.980 align:start position:0% in particular the security assumptions which<00:12:42.819> are<00:12:42.939> based<00:12:43.149> on<00:12:43.269> yourself 00:12:43.980 --> 00:12:43.990 align:start position:0% which are based on yourself 00:12:43.990 --> 00:12:46.980 align:start position:0% which are based on yourself can<00:12:44.230> blow<00:12:44.530> up<00:12:44.680> in<00:12:44.860> size<00:12:45.100> if<00:12:45.430> you<00:12:45.520> do<00:12:45.640> throne<00:12:46.030> so 00:12:46.980 --> 00:12:46.990 align:start position:0% can blow up in size if you do throne so 00:12:46.990 --> 00:12:48.750 align:start position:0% can blow up in size if you do throne so that<00:12:47.200> happen<00:12:47.500> works<00:12:47.680> which<00:12:48.010> have<00:12:48.250> looked<00:12:48.490> into 00:12:48.750 --> 00:12:48.760 align:start position:0% that happen works which have looked into 00:12:48.760 --> 00:12:50.730 align:start position:0% that happen works which have looked into precisely<00:12:49.360> how<00:12:49.660> you<00:12:49.720> should<00:12:50.050> lay<00:12:50.350> out<00:12:50.500> the 00:12:50.730 --> 00:12:50.740 align:start position:0% precisely how you should lay out the 00:12:50.740 --> 00:12:52.920 align:start position:0% precisely how you should lay out the fullness<00:12:50.950> of<00:12:51.100> your<00:12:51.250> recursion<00:12:51.880> such<00:12:52.540> thing<00:12:52.780> as 00:12:52.920 --> 00:12:52.930 align:start position:0% fullness of your recursion such thing as 00:12:52.930 --> 00:12:59.000 align:start position:0% fullness of your recursion such thing as security<00:12:53.170> assumptions<00:12:53.770> still<00:12:54.010> hold<00:12:57.570> also 00:12:59.000 --> 00:12:59.010 align:start position:0% security assumptions still hold also 00:12:59.010 --> 00:13:01.410 align:start position:0% security assumptions still hold also important<00:13:00.010> in<00:13:00.160> the<00:13:00.190> least<00:13:00.430> it's<00:13:00.970> not<00:13:01.150> so<00:13:01.300> you 00:13:01.410 --> 00:13:01.420 align:start position:0% important in the least it's not so you 00:13:01.420 --> 00:13:04.620 align:start position:0% important in the least it's not so you have<00:13:01.600> this<00:13:01.720> specific<00:13:02.320> way<00:13:02.470> of<00:13:03.630> representing 00:13:04.620 --> 00:13:04.630 align:start position:0% have this specific way of representing 00:13:04.630 --> 00:13:06.690 align:start position:0% have this specific way of representing with<00:13:04.810> your<00:13:04.930> program<00:13:05.380> if<00:13:06.130> you<00:13:06.280> need<00:13:06.430> to<00:13:06.520> be<00:13:06.610> able 00:13:06.690 --> 00:13:06.700 align:start position:0% with your program if you need to be able 00:13:06.700 --> 00:13:09.120 align:start position:0% with your program if you need to be able to<00:13:06.910> represent<00:13:07.060> your<00:13:07.390> snack<00:13:08.110> verifier<00:13:08.650> and 00:13:09.120 --> 00:13:09.130 align:start position:0% to represent your snack verifier and 00:13:09.130 --> 00:13:11.640 align:start position:0% to represent your snack verifier and this<00:13:09.760> is<00:13:09.970> what<00:13:10.240> Monsanto<00:13:10.450> mothers<00:13:11.200> did<00:13:11.440> when 00:13:11.640 --> 00:13:11.650 align:start position:0% this is what Monsanto mothers did when 00:13:11.650 --> 00:13:13.350 align:start position:0% this is what Monsanto mothers did when they<00:13:11.860> introduced<00:13:12.310> something<00:13:12.520> called<00:13:12.640> MT 00:13:13.350 --> 00:13:13.360 align:start position:0% they introduced something called MT 00:13:13.360 --> 00:13:15.930 align:start position:0% they introduced something called MT curves<00:13:13.630> which<00:13:14.590> are<00:13:14.740> basically<00:13:15.160> a<00:13:15.280> specific 00:13:15.930 --> 00:13:15.940 align:start position:0% curves which are basically a specific 00:13:15.940 --> 00:13:19.200 align:start position:0% curves which are basically a specific type<00:13:16.150> of<00:13:16.590> pairing<00:13:17.590> which<00:13:18.430> you<00:13:18.640> are<00:13:18.790> able<00:13:19.030> to 00:13:19.200 --> 00:13:19.210 align:start position:0% type of pairing which you are able to 00:13:19.210 --> 00:13:22.020 align:start position:0% type of pairing which you are able to represent<00:13:19.480> inside<00:13:20.290> a<00:13:20.320> snack<00:13:20.820> which<00:13:21.820> means 00:13:22.020 --> 00:13:22.030 align:start position:0% represent inside a snack which means 00:13:22.030 --> 00:13:23.100 align:start position:0% represent inside a snack which means that<00:13:22.150> if<00:13:22.240> you<00:13:22.330> want<00:13:22.510> to<00:13:22.600> do<00:13:22.720> layers<00:13:22.930> of 00:13:23.100 --> 00:13:23.110 align:start position:0% that if you want to do layers of 00:13:23.110 --> 00:13:30.180 align:start position:0% that if you want to do layers of recursion<00:13:23.410> you<00:13:23.890> can<00:13:28.560> another<00:13:29.560> situation<00:13:29.860> you 00:13:30.180 --> 00:13:30.190 align:start position:0% recursion you can another situation you 00:13:30.190 --> 00:13:33.030 align:start position:0% recursion you can another situation you might<00:13:30.340> come<00:13:30.490> across<00:13:30.520> is<00:13:31.090> if<00:13:31.660> you<00:13:32.110> cannot<00:13:32.680> do<00:13:33.010> a 00:13:33.030 --> 00:13:33.040 align:start position:0% might come across is if you cannot do a 00:13:33.040 --> 00:13:38.190 align:start position:0% might come across is if you cannot do a setup<00:13:33.340> I<00:13:33.570> mean<00:13:34.570> this<00:13:34.690> is<00:13:36.780> you're<00:13:37.780> still<00:13:38.020> going 00:13:38.190 --> 00:13:38.200 align:start position:0% setup I mean this is you're still going 00:13:38.200 --> 00:13:39.540 align:start position:0% setup I mean this is you're still going to<00:13:38.260> need<00:13:38.350> to<00:13:38.620> have<00:13:38.830> some<00:13:38.860> kind<00:13:39.220> of<00:13:39.340> setup 00:13:39.540 --> 00:13:39.550 align:start position:0% to need to have some kind of setup 00:13:39.550 --> 00:13:41.580 align:start position:0% to need to have some kind of setup process<00:13:39.850> to<00:13:40.210> be<00:13:40.300> honest<00:13:40.540> but<00:13:40.780> you<00:13:41.170> can<00:13:41.380> have<00:13:41.560> a 00:13:41.580 --> 00:13:41.590 align:start position:0% process to be honest but you can have a 00:13:41.590 --> 00:13:43.140 align:start position:0% process to be honest but you can have a situation<00:13:41.890> where<00:13:42.220> you<00:13:42.310> have<00:13:42.460> an<00:13:42.580> updatable 00:13:43.140 --> 00:13:43.150 align:start position:0% situation where you have an updatable 00:13:43.150 --> 00:13:45.750 align:start position:0% situation where you have an updatable setup<00:13:43.690> where<00:13:44.290> at<00:13:44.530> any<00:13:44.770> point<00:13:45.100> in<00:13:45.220> time<00:13:45.250> a<00:13:45.490> new 00:13:45.750 --> 00:13:45.760 align:start position:0% setup where at any point in time a new 00:13:45.760 --> 00:13:48.270 align:start position:0% setup where at any point in time a new person<00:13:46.330> can<00:13:46.540> come<00:13:46.750> along<00:13:46.990> add<00:13:47.740> some<00:13:48.100> new 00:13:48.270 --> 00:13:48.280 align:start position:0% person can come along add some new 00:13:48.280 --> 00:13:51.180 align:start position:0% person can come along add some new randomness<00:13:48.820> to<00:13:48.940> the<00:13:49.060> system<00:13:49.450> and<00:13:49.750> then<00:13:50.190> be 00:13:51.180 --> 00:13:51.190 align:start position:0% randomness to the system and then be 00:13:51.190 --> 00:13:53.100 align:start position:0% randomness to the system and then be part<00:13:51.460> of<00:13:51.640> that<00:13:51.790> setup<00:13:52.030> process<00:13:52.360> so<00:13:52.750> it<00:13:52.870> doesn't 00:13:53.100 --> 00:13:53.110 align:start position:0% part of that setup process so it doesn't 00:13:53.110 --> 00:13:55.590 align:start position:0% part of that setup process so it doesn't need<00:13:53.200> to<00:13:53.350> be<00:13:53.380> a<00:13:53.830> fixed<00:13:54.670> thing<00:13:54.730> with<00:13:55.150> the<00:13:55.300> face 00:13:55.590 --> 00:13:55.600 align:start position:0% need to be a fixed thing with the face 00:13:55.600 --> 00:13:58.920 align:start position:0% need to be a fixed thing with the face set<00:13:56.050> of<00:13:56.200> cutter<00:13:57.160> point<00:13:57.550> and<00:13:58.000> this<00:13:58.330> basically 00:13:58.920 --> 00:13:58.930 align:start position:0% set of cutter point and this basically 00:13:58.930 --> 00:14:02.040 align:start position:0% set of cutter point and this basically means<00:13:59.170> that<00:13:59.350> it's<00:13:59.680> much<00:13:59.890> easier<00:14:00.460> to<00:14:01.240> actually 00:14:02.040 --> 00:14:02.050 align:start position:0% means that it's much easier to actually 00:14:02.050 --> 00:14:04.350 align:start position:0% means that it's much easier to actually brand<00:14:02.500> new<00:14:02.680> trusted<00:14:03.040> setup<00:14:03.370> process<00:14:03.610> which<00:14:04.120> is 00:14:04.350 --> 00:14:04.360 align:start position:0% brand new trusted setup process which is 00:14:04.360 --> 00:14:06.360 align:start position:0% brand new trusted setup process which is secure<00:14:04.780> much<00:14:05.080> easier<00:14:05.380> to<00:14:05.500> audit<00:14:05.860> much<00:14:06.010> ease<00:14:06.190> in 00:14:06.360 --> 00:14:06.370 align:start position:0% secure much easier to audit much ease in 00:14:06.370 --> 00:14:08.310 align:start position:0% secure much easier to audit much ease in how<00:14:06.580> people<00:14:06.760> taking<00:14:07.180> part<00:14:07.330> much<00:14:07.690> easier<00:14:08.080> to 00:14:08.310 --> 00:14:08.320 align:start position:0% how people taking part much easier to 00:14:08.320 --> 00:14:13.530 align:start position:0% how people taking part much easier to just<00:14:09.040> generally<00:14:09.400> manage<00:14:12.030> but<00:14:13.030> probably<00:14:13.330> more 00:14:13.530 --> 00:14:13.540 align:start position:0% just generally manage but probably more 00:14:13.540 --> 00:14:16.110 align:start position:0% just generally manage but probably more importantly<00:14:14.110> you<00:14:14.830> can<00:14:14.860> have<00:14:15.190> a<00:14:15.220> universal<00:14:15.910> set 00:14:16.110 --> 00:14:16.120 align:start position:0% importantly you can have a universal set 00:14:16.120 --> 00:14:19.320 align:start position:0% importantly you can have a universal set up<00:14:16.300> so<00:14:17.290> typically<00:14:17.830> when<00:14:18.070> you're<00:14:18.160> doing<00:14:18.490> snack 00:14:19.320 --> 00:14:19.330 align:start position:0% up so typically when you're doing snack 00:14:19.330 --> 00:14:21.540 align:start position:0% up so typically when you're doing snack setups<00:14:19.780> you<00:14:20.110> would<00:14:20.230> have<00:14:20.410> one<00:14:20.860> setup<00:14:21.220> per 00:14:21.540 --> 00:14:21.550 align:start position:0% setups you would have one setup per 00:14:21.550 --> 00:14:23.760 align:start position:0% setups you would have one setup per application<00:14:22.120> so<00:14:23.080> if<00:14:23.200> you're<00:14:23.350> doing<00:14:23.440> range 00:14:23.760 --> 00:14:23.770 align:start position:0% application so if you're doing range 00:14:23.770 --> 00:14:25.450 align:start position:0% application so if you're doing range proof<00:14:24.010> you<00:14:24.160> need<00:14:24.310> a<00:14:24.370> setup<00:14:24.580> if<00:14:24.880> you're<00:14:25.000> doing 00:14:25.450 --> 00:14:25.460 align:start position:0% proof you need a setup if you're doing 00:14:25.460 --> 00:14:28.150 align:start position:0% proof you need a setup if you're doing that<00:14:26.210> Z<00:14:26.900> caching<00:14:27.320> is<00:14:27.410> set<00:14:27.710> up<00:14:27.890> it<00:14:28.040> could 00:14:28.150 --> 00:14:28.160 align:start position:0% that Z caching is set up it could 00:14:28.160 --> 00:14:31.350 align:start position:0% that Z caching is set up it could encounter<00:14:28.490> you<00:14:28.760> need<00:14:28.910> Assessor<00:14:29.210> and<00:14:29.660> also<00:14:30.650> if 00:14:31.350 --> 00:14:31.360 align:start position:0% encounter you need Assessor and also if 00:14:31.360 --> 00:14:34.000 align:start position:0% encounter you need Assessor and also if you're<00:14:32.360> set<00:14:32.570> up<00:14:32.600> you<00:14:33.050> do<00:14:33.200> your<00:14:33.230> setup<00:14:33.680> and<00:14:33.800> then 00:14:34.000 --> 00:14:34.010 align:start position:0% you're set up you do your setup and then 00:14:34.010 --> 00:14:36.310 align:start position:0% you're set up you do your setup and then you<00:14:34.100> happen<00:14:34.400> to<00:14:34.430> learn<00:14:34.700> that<00:14:35.230> something<00:14:36.230> you 00:14:36.310 --> 00:14:36.320 align:start position:0% you happen to learn that something you 00:14:36.320 --> 00:14:37.630 align:start position:0% you happen to learn that something you didn't<00:14:36.529> your<00:14:36.650> protocol<00:14:37.010> is<00:14:37.100> actually<00:14:37.400> wrong 00:14:37.630 --> 00:14:37.640 align:start position:0% didn't your protocol is actually wrong 00:14:37.640 --> 00:14:40.210 align:start position:0% didn't your protocol is actually wrong and<00:14:37.910> maybe<00:14:38.060> you<00:14:38.180> missed<00:14:38.360> a<00:14:38.450> minus<00:14:38.810> sign<00:14:39.220> they 00:14:40.210 --> 00:14:40.220 align:start position:0% and maybe you missed a minus sign they 00:14:40.220 --> 00:14:44.900 align:start position:0% and maybe you missed a minus sign they have<00:14:40.430> to<00:14:40.520> do<00:14:40.610> the<00:14:40.700> whole<00:14:40.850> process<00:14:41.000> again 00:14:44.900 --> 00:14:44.910 align:start position:0% 00:14:44.910 --> 00:14:47.390 align:start position:0% whereas<00:14:45.570> with<00:14:45.750> an<00:14:45.870> updatable<00:14:46.290> setup<00:14:46.770> you 00:14:47.390 --> 00:14:47.400 align:start position:0% whereas with an updatable setup you 00:14:47.400 --> 00:14:48.980 align:start position:0% whereas with an updatable setup you don't<00:14:47.610> need<00:14:47.790> to<00:14:47.880> do<00:14:48.000> that<00:14:48.030> you<00:14:48.360> have<00:14:48.570> just<00:14:48.810> a 00:14:48.980 --> 00:14:48.990 align:start position:0% don't need to do that you have just a 00:14:48.990 --> 00:14:52.700 align:start position:0% don't need to do that you have just a single<00:14:49.260> setup<00:14:49.650> fit<00:14:50.250> so<00:14:50.490> and<00:14:51.290> this<00:14:52.290> is<00:14:52.470> quite 00:14:52.700 --> 00:14:52.710 align:start position:0% single setup fit so and this is quite 00:14:52.710 --> 00:14:54.170 align:start position:0% single setup fit so and this is quite nice<00:14:52.890> because<00:14:52.950> it<00:14:53.460> means<00:14:53.580> that<00:14:53.880> you<00:14:53.970> can 00:14:54.170 --> 00:14:54.180 align:start position:0% nice because it means that you can 00:14:54.180 --> 00:14:56.480 align:start position:0% nice because it means that you can coordinate<00:14:54.360> sets<00:14:55.110> you<00:14:55.350> can<00:14:55.590> make<00:14:55.830> sure<00:14:56.040> that 00:14:56.480 --> 00:14:56.490 align:start position:0% coordinate sets you can make sure that 00:14:56.490 --> 00:14:58.490 align:start position:0% coordinate sets you can make sure that there's<00:14:56.880> lots<00:14:57.210> of<00:14:57.360> the<00:14:57.510> companies<00:14:57.900> lots<00:14:58.260> of 00:14:58.490 --> 00:14:58.500 align:start position:0% there's lots of the companies lots of 00:14:58.500 --> 00:15:00.290 align:start position:0% there's lots of the companies lots of participants<00:14:59.160> lots<00:14:59.460> of<00:14:59.520> governments<00:15:00.000> lots<00:15:00.210> of 00:15:00.290 --> 00:15:00.300 align:start position:0% participants lots of governments lots of 00:15:00.300 --> 00:15:01.970 align:start position:0% participants lots of governments lots of individual<00:15:00.810> people<00:15:00.960> taking<00:15:01.410> part<00:15:01.620> and<00:15:01.800> just 00:15:01.970 --> 00:15:01.980 align:start position:0% individual people taking part and just 00:15:01.980 --> 00:15:03.890 align:start position:0% individual people taking part and just have<00:15:02.160> one<00:15:02.190> set<00:15:02.610> up<00:15:02.850> and<00:15:03.090> that<00:15:03.480> would<00:15:03.600> be<00:15:03.750> the 00:15:03.890 --> 00:15:03.900 align:start position:0% have one set up and that would be the 00:15:03.900 --> 00:15:09.280 align:start position:0% have one set up and that would be the only<00:15:04.110> setup<00:15:04.590> that<00:15:04.710> you<00:15:04.770> would<00:15:04.920> need<00:15:05.040> to<00:15:05.100> audit 00:15:09.280 --> 00:15:09.290 align:start position:0% 00:15:09.290 --> 00:15:12.550 align:start position:0% so<00:15:10.290> this<00:15:10.470> is<00:15:10.650> what<00:15:11.010> sonic<00:15:11.430> sonic<00:15:11.820> briefs<00:15:12.240> do 00:15:12.550 --> 00:15:12.560 align:start position:0% so this is what sonic sonic briefs do 00:15:12.560 --> 00:15:15.080 align:start position:0% so this is what sonic sonic briefs do they<00:15:13.560> designed<00:15:14.220> their<00:15:14.550> knowledge<00:15:14.820> briefs 00:15:15.080 --> 00:15:15.090 align:start position:0% they designed their knowledge briefs 00:15:15.090 --> 00:15:18.590 align:start position:0% they designed their knowledge briefs which<00:15:15.420> are<00:15:15.720> very<00:15:16.110> nice<00:15:17.010> if<00:15:17.370> you<00:15:17.790> want<00:15:18.390> to<00:15:18.480> the 00:15:18.590 --> 00:15:18.600 align:start position:0% which are very nice if you want to the 00:15:18.600 --> 00:15:20.990 align:start position:0% which are very nice if you want to the universal<00:15:19.140> set<00:15:19.290> up<00:15:19.470> the<00:15:20.280> catch<00:15:20.460> with<00:15:20.700> these<00:15:20.820> is 00:15:20.990 --> 00:15:21.000 align:start position:0% universal set up the catch with these is 00:15:21.000 --> 00:15:22.580 align:start position:0% universal set up the catch with these is that<00:15:21.120> they<00:15:21.300> are<00:15:21.420> actually<00:15:21.870> only<00:15:21.990> efficient<00:15:22.470> if 00:15:22.580 --> 00:15:22.590 align:start position:0% that they are actually only efficient if 00:15:22.590 --> 00:15:23.510 align:start position:0% that they are actually only efficient if you're<00:15:22.740> in<00:15:22.830> a<00:15:22.890> position<00:15:23.010> where<00:15:23.400> you<00:15:23.490> can 00:15:23.510 --> 00:15:23.520 align:start position:0% you're in a position where you can 00:15:23.520 --> 00:15:26.720 align:start position:0% you're in a position where you can aggregate<00:15:24.170> so<00:15:25.170> if<00:15:25.440> you<00:15:25.590> have<00:15:25.830> an<00:15:26.160> aggregation 00:15:26.720 --> 00:15:26.730 align:start position:0% aggregate so if you have an aggregation 00:15:26.730 --> 00:15:28.280 align:start position:0% aggregate so if you have an aggregation party<00:15:27.270> you<00:15:27.480> can<00:15:27.630> fit<00:15:27.870> all<00:15:27.990> the<00:15:28.080> proofs 00:15:28.280 --> 00:15:28.290 align:start position:0% party you can fit all the proofs 00:15:28.290 --> 00:15:30.410 align:start position:0% party you can fit all the proofs together<00:15:28.620> and<00:15:29.040> help<00:15:29.430> out<00:15:29.640> other<00:15:29.910> verifies 00:15:30.410 --> 00:15:30.420 align:start position:0% together and help out other verifies 00:15:30.420 --> 00:15:32.120 align:start position:0% together and help out other verifies than<00:15:31.140> they're<00:15:31.320> really<00:15:31.530> efficient<00:15:31.860> on<00:15:32.070> the 00:15:32.120 --> 00:15:32.130 align:start position:0% than they're really efficient on the 00:15:32.130 --> 00:15:36.170 align:start position:0% than they're really efficient on the great<00:15:32.810> and<00:15:33.810> these<00:15:34.410> the<00:15:34.950> these<00:15:35.700> levels<00:15:36.060> have 00:15:36.170 --> 00:15:36.180 align:start position:0% great and these the these levels have 00:15:36.180 --> 00:15:39.920 align:start position:0% great and these the these levels have been<00:15:36.300> improved<00:15:36.660> by<00:15:36.780> awesome<00:15:38.390> if<00:15:39.390> you<00:15:39.660> cannot 00:15:39.920 --> 00:15:39.930 align:start position:0% been improved by awesome if you cannot 00:15:39.930 --> 00:15:41.330 align:start position:0% been improved by awesome if you cannot segregate<00:15:40.200> then<00:15:40.830> there<00:15:41.010> have<00:15:41.130> been<00:15:41.220> a<00:15:41.310> couple 00:15:41.330 --> 00:15:41.340 align:start position:0% segregate then there have been a couple 00:15:41.340 --> 00:15:43.340 align:start position:0% segregate then there have been a couple of<00:15:41.580> works<00:15:41.820> recently<00:15:42.300> on<00:15:42.480> completely<00:15:43.050> of<00:15:43.140> code 00:15:43.340 --> 00:15:43.350 align:start position:0% of works recently on completely of code 00:15:43.350 --> 00:15:46.030 align:start position:0% of works recently on completely of code Marlin<00:15:43.800> which<00:15:44.400> do<00:15:44.820> not<00:15:44.850> need<00:15:45.120> any<00:15:45.330> very 00:15:46.030 --> 00:15:46.040 align:start position:0% Marlin which do not need any very 00:15:46.040 --> 00:15:48.710 align:start position:0% Marlin which do not need any very aggregation<00:15:47.040> but<00:15:47.580> do<00:15:47.880> have<00:15:48.120> the<00:15:48.240> downside 00:15:48.710 --> 00:15:48.720 align:start position:0% aggregation but do have the downside 00:15:48.720 --> 00:15:50.630 align:start position:0% aggregation but do have the downside that<00:15:49.080> the<00:15:49.200> proof<00:15:49.410> sizes<00:15:49.830> are<00:15:50.100> a<00:15:50.130> bit<00:15:50.280> larger 00:15:50.630 --> 00:15:50.640 align:start position:0% that the proof sizes are a bit larger 00:15:50.640 --> 00:15:52.370 align:start position:0% that the proof sizes are a bit larger when<00:15:50.820> I'm<00:15:50.910> looking<00:15:51.090> like<00:15:51.450> a<00:15:51.660> kilobyte<00:15:51.960> rather 00:15:52.370 --> 00:15:52.380 align:start position:0% when I'm looking like a kilobyte rather 00:15:52.380 --> 00:15:55.340 align:start position:0% when I'm looking like a kilobyte rather than<00:15:52.560> a<00:15:52.590> couple<00:15:52.830> hundred<00:15:52.890> bytes<00:15:53.420> but<00:15:54.420> they 00:15:55.340 --> 00:15:55.350 align:start position:0% than a couple hundred bytes but they 00:15:55.350 --> 00:15:57.990 align:start position:0% than a couple hundred bytes but they don't<00:15:55.530> need<00:15:55.620> aggregator 00:15:57.990 --> 00:15:58.000 align:start position:0% don't need aggregator 00:15:58.000 --> 00:15:59.440 align:start position:0% don't need aggregator [Music] 00:15:59.440 --> 00:15:59.450 align:start position:0% [Music] 00:15:59.450 --> 00:16:02.060 align:start position:0% [Music] if<00:16:00.450> you<00:16:00.630> want<00:16:00.810> to<00:16:00.960> have<00:16:01.140> your<00:16:01.230> proofs<00:16:01.500> being<00:16:01.830> a 00:16:02.060 --> 00:16:02.070 align:start position:0% if you want to have your proofs being a 00:16:02.070 --> 00:16:03.470 align:start position:0% if you want to have your proofs being a bit<00:16:02.220> bigger<00:16:02.490> there's<00:16:02.670> also<00:16:02.820> quite<00:16:03.180> a<00:16:03.240> nice 00:16:03.470 --> 00:16:03.480 align:start position:0% bit bigger there's also quite a nice 00:16:03.480 --> 00:16:07.100 align:start position:0% bit bigger there's also quite a nice length<00:16:03.750> lengths<00:16:04.350> which<00:16:04.560> is<00:16:05.210> what<00:16:06.210> which<00:16:06.810> is 00:16:07.100 --> 00:16:07.110 align:start position:0% length lengths which is what which is 00:16:07.110 --> 00:16:09.830 align:start position:0% length lengths which is what which is also<00:16:07.470> universal<00:16:08.100> an<00:16:08.160> updated<00:16:08.580> book<00:16:08.730> which<00:16:09.510> is 00:16:09.830 --> 00:16:09.840 align:start position:0% also universal an updated book which is 00:16:09.840 --> 00:16:12.880 align:start position:0% also universal an updated book which is called<00:16:10.350> Libra<00:16:10.850> not<00:16:11.850> the<00:16:12.060> Facebook<00:16:12.390> currency 00:16:12.880 --> 00:16:12.890 align:start position:0% called Libra not the Facebook currency 00:16:12.890 --> 00:16:17.270 align:start position:0% called Libra not the Facebook currency and<00:16:14.390> the<00:16:15.390> nice<00:16:16.320> thing<00:16:16.350> about<00:16:16.650> this<00:16:16.980> I<00:16:17.250> mean 00:16:17.270 --> 00:16:17.280 align:start position:0% and the nice thing about this I mean 00:16:17.280 --> 00:16:18.860 align:start position:0% and the nice thing about this I mean what<00:16:17.520> they<00:16:17.640> were<00:16:17.700> focusing<00:16:17.910> on<00:16:18.270> is<00:16:18.840> getting 00:16:18.860 --> 00:16:18.870 align:start position:0% what they were focusing on is getting 00:16:18.870 --> 00:16:20.720 align:start position:0% what they were focusing on is getting moved<00:16:19.440> down<00:16:19.620> the<00:16:19.770> creeper<00:16:19.980> computation<00:16:20.580> but 00:16:20.720 --> 00:16:20.730 align:start position:0% moved down the creeper computation but 00:16:20.730 --> 00:16:22.370 align:start position:0% moved down the creeper computation but what<00:16:20.850> I<00:16:20.880> think<00:16:21.240> is<00:16:21.330> really<00:16:21.450> cool<00:16:21.720> about<00:16:21.750> it<00:16:21.990> is 00:16:22.370 --> 00:16:22.380 align:start position:0% what I think is really cool about it is 00:16:22.380 --> 00:16:25.580 align:start position:0% what I think is really cool about it is that<00:16:23.010> they<00:16:23.520> do<00:16:23.580> not<00:16:23.880> need<00:16:24.090> very<00:16:24.900> large<00:16:25.110> fast 00:16:25.580 --> 00:16:25.590 align:start position:0% that they do not need very large fast 00:16:25.590 --> 00:16:27.080 align:start position:0% that they do not need very large fast fourier<00:16:25.920> transforms<00:16:26.430> they<00:16:26.550> can<00:16:26.700> get<00:16:26.820> away<00:16:27.000> of 00:16:27.080 --> 00:16:27.090 align:start position:0% fourier transforms they can get away of 00:16:27.090 --> 00:16:29.240 align:start position:0% fourier transforms they can get away of just<00:16:27.270> very<00:16:27.450> little<00:16:27.600> ones<00:16:27.920> and<00:16:28.920> this<00:16:29.070> means 00:16:29.240 --> 00:16:29.250 align:start position:0% just very little ones and this means 00:16:29.250 --> 00:16:30.920 align:start position:0% just very little ones and this means that<00:16:29.430> you're<00:16:29.610> actually<00:16:29.700> trying<00:16:30.120> to<00:16:30.360> represent 00:16:30.920 --> 00:16:30.930 align:start position:0% that you're actually trying to represent 00:16:30.930 --> 00:16:33.800 align:start position:0% that you're actually trying to represent the<00:16:31.440> program<00:16:31.860> and<00:16:32.370> then<00:16:32.940> you<00:16:33.120> can<00:16:33.300> use<00:16:33.450> a<00:16:33.480> field 00:16:33.800 --> 00:16:33.810 align:start position:0% the program and then you can use a field 00:16:33.810 --> 00:16:35.930 align:start position:0% the program and then you can use a field which<00:16:34.530> doesn't<00:16:34.980> need<00:16:35.100> to<00:16:35.190> have<00:16:35.370> a<00:16:35.610> large 00:16:35.930 --> 00:16:35.940 align:start position:0% which doesn't need to have a large 00:16:35.940 --> 00:16:37.610 align:start position:0% which doesn't need to have a large device<00:16:36.270> repetier<00:16:36.660> this<00:16:36.810> gives<00:16:37.020> us<00:16:37.170> a<00:16:37.200> lot<00:16:37.500> more 00:16:37.610 --> 00:16:37.620 align:start position:0% device repetier this gives us a lot more 00:16:37.620 --> 00:16:42.370 align:start position:0% device repetier this gives us a lot more flexibility<00:16:38.190> when<00:16:38.430> were<00:16:38.520> actually<00:16:38.640> using<00:16:38.970> it 00:16:42.370 --> 00:16:42.380 align:start position:0% 00:16:42.380 --> 00:16:46.310 align:start position:0% so<00:16:43.380> to<00:16:43.440> summarize<00:16:44.330> Perry<00:16:45.330> Mason<00:16:45.570> axe<00:16:45.870> can<00:16:46.110> be 00:16:46.310 --> 00:16:46.320 align:start position:0% so to summarize Perry Mason axe can be 00:16:46.320 --> 00:16:48.440 align:start position:0% so to summarize Perry Mason axe can be small<00:16:47.130> and<00:16:47.310> pasta<00:16:47.580> verify<00:16:47.910> the<00:16:47.970> can't<00:16:48.240> be 00:16:48.440 --> 00:16:48.450 align:start position:0% small and pasta verify the can't be 00:16:48.450 --> 00:16:51.500 align:start position:0% small and pasta verify the can't be paralyzed<00:16:49.430> apart<00:16:50.430> they<00:16:50.730> can<00:16:50.910> be<00:16:51.030> quickly<00:16:51.210> they 00:16:51.500 --> 00:16:51.510 align:start position:0% paralyzed apart they can be quickly they 00:16:51.510 --> 00:16:53.570 align:start position:0% paralyzed apart they can be quickly they can<00:16:51.660> be<00:16:51.780> universal<00:16:52.230> and<00:16:52.320> updatable<00:16:52.830> and<00:16:53.040> they 00:16:53.570 --> 00:16:53.580 align:start position:0% can be universal and updatable and they 00:16:53.580 --> 00:16:55.550 align:start position:0% can be universal and updatable and they can<00:16:53.790> be<00:16:53.910> made<00:16:54.090> on<00:16:54.360> it<00:16:54.480> to<00:16:54.570> prove<00:16:54.840> that<00:16:55.140> slower 00:16:55.550 --> 00:16:55.560 align:start position:0% can be made on it to prove that slower 00:16:55.560 --> 00:16:59.390 align:start position:0% can be made on it to prove that slower to<00:16:55.770> verify<00:16:56.160> if<00:16:56.850> that's<00:16:57.480> what<00:16:57.690> you<00:16:57.810> want 00:16:59.390 --> 00:16:59.400 align:start position:0% to verify if that's what you want 00:16:59.400 --> 00:17:07.790 align:start position:0% to verify if that's what you want [Music] 00:17:07.790 --> 00:17:07.800 align:start position:0% 00:17:07.800 --> 00:17:27.950 align:start position:0% I<00:17:23.690> say<00:17:24.740> yeah<00:17:25.740> this<00:17:25.920> one<00:17:26.100> has<00:17:26.300> larger<00:17:27.300> for<00:17:27.750> even 00:17:27.950 --> 00:17:27.960 align:start position:0% I say yeah this one has larger for even 00:17:27.960 --> 00:17:30.050 align:start position:0% I say yeah this one has larger for even smaller<00:17:28.520> premeditation<00:17:29.520> that's<00:17:29.700> regular 00:17:30.050 --> 00:17:30.060 align:start position:0% smaller premeditation that's regular 00:17:30.060 --> 00:17:34.690 align:start position:0% smaller premeditation that's regular troops 00:17:34.690 --> 00:17:34.700 align:start position:0% 00:17:34.700 --> 00:17:37.940 align:start position:0% you<00:17:35.700> mentioned<00:17:36.090> the<00:17:36.240> shuffle<00:17:36.840> arguments<00:17:37.530> when 00:17:37.940 --> 00:17:37.950 align:start position:0% you mentioned the shuffle arguments when 00:17:37.950 --> 00:17:39.410 align:start position:0% you mentioned the shuffle arguments when you<00:17:38.070> said<00:17:38.460> Jets<00:17:38.730> growth<00:17:39.090> and<00:17:39.360> the 00:17:39.410 --> 00:17:39.420 align:start position:0% you said Jets growth and the 00:17:39.420 --> 00:17:43.460 align:start position:0% you said Jets growth and the accumulators<00:17:40.140> who<00:17:41.010> wrote<00:17:41.220> that<00:17:41.250> paper<00:17:42.470> I 00:17:43.460 --> 00:17:43.470 align:start position:0% accumulators who wrote that paper I 00:17:43.470 --> 00:17:47.660 align:start position:0% accumulators who wrote that paper I think<00:17:44.010> an<00:17:44.250> official<00:17:44.700> actions<00:17:45.500> by<00:17:46.500> a<00:17:46.530> jumbo 00:17:47.660 --> 00:17:47.670 align:start position:0% think an official actions by a jumbo 00:17:47.670 --> 00:17:58.169 align:start position:0% think an official actions by a jumbo resource<00:17:48.510> research 00:17:58.169 --> 00:17:58.179 align:start position:0% 00:17:58.179 --> 00:18:05.980 align:start position:0% good 00:18:05.980 --> 00:18:05.990 align:start position:0% 00:18:05.990 --> 00:18:07.990 align:start position:0% [Music] 00:18:07.990 --> 00:18:08.000 align:start position:0% [Music] 00:18:08.000 --> 00:18:13.039 align:start position:0% [Music] say<00:18:09.000> one<00:18:09.480> recent<00:18:10.140> one<00:18:10.320> was<00:18:10.830> love<00:18:11.600> if<00:18:12.600> you<00:18:12.840> use 00:18:13.039 --> 00:18:13.049 align:start position:0% say one recent one was love if you use 00:18:13.049 --> 00:18:14.510 align:start position:0% say one recent one was love if you use the<00:18:13.170> better<00:18:13.350> person<00:18:13.679> to<00:18:13.740> protect<00:18:14.070> documents 00:18:14.510 --> 00:18:14.520 align:start position:0% the better person to protect documents 00:18:14.520 --> 00:18:15.650 align:start position:0% the better person to protect documents than<00:18:14.670> just<00:18:14.940> another<00:18:15.090> put<00:18:15.390> in<00:18:15.480> a<00:18:15.540> new 00:18:15.650 --> 00:18:15.660 align:start position:0% than just another put in a new 00:18:15.660 --> 00:18:17.600 align:start position:0% than just another put in a new commitment<00:18:15.990> scheme<00:18:16.410> and<00:18:17.010> this<00:18:17.220> is<00:18:17.370> how<00:18:17.580> I 00:18:17.600 --> 00:18:17.610 align:start position:0% commitment scheme and this is how I 00:18:17.610 --> 00:18:19.910 align:start position:0% commitment scheme and this is how I behave<00:18:18.210> data<00:18:18.420> released<00:18:18.960> by<00:18:19.049> NC<00:18:19.500> cash<00:18:19.679> does 00:18:19.910 --> 00:18:19.920 align:start position:0% behave data released by NC cash does 00:18:19.920 --> 00:18:22.010 align:start position:0% behave data released by NC cash does they<00:18:20.250> use<00:18:20.520> a<00:18:20.549> person<00:18:21.299> in<00:18:21.390> front<00:18:21.540> of<00:18:21.600> document 00:18:22.010 --> 00:18:22.020 align:start position:0% they use a person in front of document 00:18:22.020 --> 00:18:24.320 align:start position:0% they use a person in front of document which<00:18:22.710> has<00:18:23.250> a<00:18:23.280> downside<00:18:23.610> that<00:18:23.850> have<00:18:24.150> new 00:18:24.320 --> 00:18:24.330 align:start position:0% which has a downside that have new 00:18:24.330 --> 00:18:26.299 align:start position:0% which has a downside that have new clarification<00:18:25.110> if<00:18:25.500> you<00:18:25.679> just<00:18:25.830> run<00:18:26.010> it<00:18:26.070> as<00:18:26.280> a 00:18:26.299 --> 00:18:26.309 align:start position:0% clarification if you just run it as a 00:18:26.309 --> 00:18:30.490 align:start position:0% clarification if you just run it as a run<00:18:26.580> off<00:18:26.730> but<00:18:27.720> if<00:18:27.960> you're<00:18:28.290> aggregating<00:18:29.330> then 00:18:30.490 --> 00:18:30.500 align:start position:0% run off but if you're aggregating then 00:18:30.500 --> 00:18:33.789 align:start position:0% run off but if you're aggregating then you<00:18:31.500> have<00:18:31.740> the<00:18:31.890> situation<00:18:32.130> where<00:18:32.670> you<00:18:32.910> can 00:18:33.789 --> 00:18:33.799 align:start position:0% you have the situation where you can 00:18:33.799 --> 00:18:37.039 align:start position:0% you have the situation where you can have<00:18:34.799> the<00:18:35.160> linear<00:18:35.340> verification<00:18:36.210> via<00:18:36.630> one<00:18:36.929> of 00:18:37.039 --> 00:18:37.049 align:start position:0% have the linear verification via one of 00:18:37.049 --> 00:18:38.720 align:start position:0% have the linear verification via one of the<00:18:37.140> cost<00:18:37.410> and<00:18:37.770> then<00:18:38.130> just<00:18:38.309> have<00:18:38.460> a<00:18:38.490> lot<00:18:38.700> of 00:18:38.720 --> 00:18:38.730 align:start position:0% the cost and then just have a lot of 00:18:38.730 --> 00:18:40.640 align:start position:0% the cost and then just have a lot of rhythmic<00:18:38.970> factor<00:18:39.600> on<00:18:39.870> top<00:18:39.900> of<00:18:40.200> that<00:18:40.320> for<00:18:40.530> each 00:18:40.640 --> 00:18:40.650 align:start position:0% rhythmic factor on top of that for each 00:18:40.650 --> 00:18:42.680 align:start position:0% rhythmic factor on top of that for each individual<00:18:41.070> proof<00:18:41.309> which<00:18:41.970> means<00:18:42.240> that<00:18:42.510> you 00:18:42.680 --> 00:18:42.690 align:start position:0% individual proof which means that you 00:18:42.690 --> 00:18:44.510 align:start position:0% individual proof which means that you can<00:18:42.929> get<00:18:43.290> something<00:18:43.500> that's<00:18:43.770> quite<00:18:43.980> fast<00:18:44.250> on 00:18:44.510 --> 00:18:44.520 align:start position:0% can get something that's quite fast on 00:18:44.520 --> 00:18:55.950 align:start position:0% can get something that's quite fast on saturation 00:18:55.950 --> 00:18:55.960 align:start position:0% 00:18:55.960 --> 00:19:07.490 align:start position:0% [Music] 00:19:07.490 --> 00:19:07.500 align:start position:0% 00:19:07.500 --> 00:19:15.640 align:start position:0% [Applause]