WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:03.230 align:start position:0% okay<00:00:00.659> so<00:00:00.719> last<00:00:01.410> year<00:00:01.680> around<00:00:02.010> January<00:00:02.550> no<00:00:03.000> Iran 00:00:03.230 --> 00:00:03.240 align:start position:0% okay so last year around January no Iran 00:00:03.240 --> 00:00:05.960 align:start position:0% okay so last year around January no Iran December<00:00:03.689> the<00:00:04.080> year<00:00:04.230> before<00:00:04.609> yeah<00:00:05.640> around 00:00:05.960 --> 00:00:05.970 align:start position:0% December the year before yeah around 00:00:05.970 --> 00:00:07.309 align:start position:0% December the year before yeah around December<00:00:06.330> last<00:00:06.450> year<00:00:06.600> I<00:00:06.870> started<00:00:07.140> to<00:00:07.230> work 00:00:07.309 --> 00:00:07.319 align:start position:0% December last year I started to work 00:00:07.319 --> 00:00:09.320 align:start position:0% December last year I started to work with<00:00:07.350> snacks<00:00:07.649> and<00:00:08.400> thanks<00:00:08.760> are<00:00:08.849> applicable<00:00:09.000> to 00:00:09.320 --> 00:00:09.330 align:start position:0% with snacks and thanks are applicable to 00:00:09.330 --> 00:00:12.890 align:start position:0% with snacks and thanks are applicable to two<00:00:09.510> major<00:00:09.780> things<00:00:10.759> for<00:00:11.759> privacy<00:00:12.480> and<00:00:12.690> for 00:00:12.890 --> 00:00:12.900 align:start position:0% two major things for privacy and for 00:00:12.900 --> 00:00:15.200 align:start position:0% two major things for privacy and for scalability<00:00:13.230> so<00:00:14.099> today<00:00:14.759> I'm<00:00:14.849> gonna<00:00:15.000> talk 00:00:15.200 --> 00:00:15.210 align:start position:0% scalability so today I'm gonna talk 00:00:15.210 --> 00:00:17.450 align:start position:0% scalability so today I'm gonna talk about<00:00:15.470> two<00:00:16.470> applications<00:00:16.980> to<00:00:17.039> privacy<00:00:17.340> and 00:00:17.450 --> 00:00:17.460 align:start position:0% about two applications to privacy and 00:00:17.460 --> 00:00:20.720 align:start position:0% about two applications to privacy and one<00:00:17.760> application<00:00:18.210> to<00:00:18.330> scalability<00:00:19.220> so<00:00:20.220> the 00:00:20.720 --> 00:00:20.730 align:start position:0% one application to scalability so the 00:00:20.730 --> 00:00:22.490 align:start position:0% one application to scalability so the privacy<00:00:21.210> projects<00:00:21.630> are<00:00:21.750> called<00:00:21.960> Maximus<00:00:22.350> in 00:00:22.490 --> 00:00:22.500 align:start position:0% privacy projects are called Maximus in 00:00:22.500 --> 00:00:25.250 align:start position:0% privacy projects are called Maximus in semaphore<00:00:22.949> so<00:00:23.430> makes<00:00:23.699> a<00:00:23.789> mess<00:00:23.939> is<00:00:24.150> uh<00:00:24.180> is<00:00:24.960> that 00:00:25.250 --> 00:00:25.260 align:start position:0% semaphore so makes a mess is uh is that 00:00:25.260 --> 00:00:29.450 align:start position:0% semaphore so makes a mess is uh is that is<00:00:25.529> a<00:00:25.590> generic<00:00:27.109> either<00:00:28.109> an<00:00:28.470> e<00:00:28.560> or<00:00:28.710> C<00:00:28.890> 20<00:00:29.189> token 00:00:29.450 --> 00:00:29.460 align:start position:0% is a generic either an e or C 20 token 00:00:29.460 --> 00:00:31.550 align:start position:0% is a generic either an e or C 20 token mixer<00:00:29.760> where<00:00:30.449> you<00:00:30.539> can<00:00:30.689> deposit<00:00:30.929> money<00:00:31.230> thir 00:00:31.550 --> 00:00:31.560 align:start position:0% mixer where you can deposit money thir 00:00:31.560 --> 00:00:33.440 align:start position:0% mixer where you can deposit money thir and<00:00:31.859> later<00:00:32.489> you<00:00:32.669> can<00:00:32.820> withdraw<00:00:32.969> one<00:00:33.300> either 00:00:33.440 --> 00:00:33.450 align:start position:0% and later you can withdraw one either 00:00:33.450 --> 00:00:35.120 align:start position:0% and later you can withdraw one either and<00:00:33.809> there's<00:00:34.350> no<00:00:34.469> way<00:00:34.590> to<00:00:34.649> connect<00:00:35.010> the 00:00:35.120 --> 00:00:35.130 align:start position:0% and there's no way to connect the 00:00:35.130 --> 00:00:38.330 align:start position:0% and there's no way to connect the deposit<00:00:35.670> to<00:00:35.700> the<00:00:35.969> withdrawal<00:00:36.649> and<00:00:37.649> Saima<00:00:38.070> four 00:00:38.330 --> 00:00:38.340 align:start position:0% deposit to the withdrawal and Saima four 00:00:38.340 --> 00:00:39.920 align:start position:0% deposit to the withdrawal and Saima four is<00:00:38.460> if<00:00:38.760> all<00:00:39.000> it<00:00:39.210> is<00:00:39.420> very<00:00:39.750> similar 00:00:39.920 --> 00:00:39.930 align:start position:0% is if all it is very similar 00:00:39.930 --> 00:00:44.540 align:start position:0% is if all it is very similar architecture<00:00:40.530> and<00:00:40.770> we<00:00:40.950> use<00:00:41.100> that<00:00:41.280> to<00:00:41.489> do<00:00:43.250> to<00:00:44.250> do 00:00:44.540 --> 00:00:44.550 align:start position:0% architecture and we use that to do to do 00:00:44.550 --> 00:00:48.170 align:start position:0% architecture and we use that to do to do general<00:00:45.000> reputation<00:00:45.270> mixing<00:00:46.020> yeah<00:00:46.469> so<00:00:46.980> so<00:00:47.340> you 00:00:48.170 --> 00:00:48.180 align:start position:0% general reputation mixing yeah so so you 00:00:48.180 --> 00:00:49.940 align:start position:0% general reputation mixing yeah so so you can<00:00:48.390> you<00:00:48.690> can<00:00:48.719> become<00:00:49.110> part<00:00:49.320> of<00:00:49.379> a<00:00:49.469> group<00:00:49.649> and 00:00:49.940 --> 00:00:49.950 align:start position:0% can you can become part of a group and 00:00:49.950 --> 00:00:52.670 align:start position:0% can you can become part of a group and you<00:00:50.219> can<00:00:50.430> signal<00:00:50.940> things<00:00:51.510> about<00:00:51.840> your 00:00:52.670 --> 00:00:52.680 align:start position:0% you can signal things about your 00:00:52.680 --> 00:00:56.799 align:start position:0% you can signal things about your thoughts<00:00:53.100> or<00:00:53.399> beliefs<00:00:53.789> or<00:00:54.210> other<00:00:54.960> things<00:00:55.320> and 00:00:56.799 --> 00:00:56.809 align:start position:0% thoughts or beliefs or other things and 00:00:56.809 --> 00:01:00.410 align:start position:0% thoughts or beliefs or other things and no<00:00:57.809> one<00:00:57.960> can<00:00:58.140> connect<00:00:58.670> all<00:00:59.670> people<00:01:00.149> will<00:01:00.300> know 00:01:00.410 --> 00:01:00.420 align:start position:0% no one can connect all people will know 00:01:00.420 --> 00:01:01.580 align:start position:0% no one can connect all people will know is<00:01:00.570> that<00:01:00.719> you're<00:01:00.840> a<00:01:00.870> member<00:01:01.140> of<00:01:01.289> that<00:01:01.410> group 00:01:01.580 --> 00:01:01.590 align:start position:0% is that you're a member of that group 00:01:01.590 --> 00:01:03.439 align:start position:0% is that you're a member of that group and<00:01:02.129> then<00:01:02.280> we<00:01:02.399> also<00:01:02.520> have<00:01:02.730> some<00:01:02.910> rate<00:01:03.120> limiting 00:01:03.439 --> 00:01:03.449 align:start position:0% and then we also have some rate limiting 00:01:03.449 --> 00:01:05.030 align:start position:0% and then we also have some rate limiting things<00:01:03.660> there<00:01:03.870> as<00:01:03.989> well<00:01:04.170> so<00:01:04.470> that<00:01:04.650> we<00:01:04.739> can<00:01:04.890> do 00:01:05.030 --> 00:01:05.040 align:start position:0% things there as well so that we can do 00:01:05.040 --> 00:01:08.390 align:start position:0% things there as well so that we can do like<00:01:05.270> cooler<00:01:06.270> public<00:01:06.960> systems<00:01:07.320> and<00:01:07.650> then 00:01:08.390 --> 00:01:08.400 align:start position:0% like cooler public systems and then 00:01:08.400 --> 00:01:09.890 align:start position:0% like cooler public systems and then we'll<00:01:08.729> talk<00:01:09.000> about<00:01:09.180> snacks<00:01:09.510> with<00:01:09.659> scalability 00:01:09.890 --> 00:01:09.900 align:start position:0% we'll talk about snacks with scalability 00:01:09.900 --> 00:01:14.300 align:start position:0% we'll talk about snacks with scalability it's<00:01:10.799> okay<00:01:10.950> you<00:01:11.010> can<00:01:11.189> come<00:01:11.220> in<00:01:12.890> and<00:01:13.890> we'll<00:01:14.159> talk 00:01:14.300 --> 00:01:14.310 align:start position:0% it's okay you can come in and we'll talk 00:01:14.310 --> 00:01:15.590 align:start position:0% it's okay you can come in and we'll talk about<00:01:14.430> we'll<00:01:14.909> talk<00:01:15.090> about<00:01:15.180> snacks<00:01:15.450> with 00:01:15.590 --> 00:01:15.600 align:start position:0% about we'll talk about snacks with 00:01:15.600 --> 00:01:19.429 align:start position:0% about we'll talk about snacks with scalability<00:01:17.210> so<00:01:18.210> so<00:01:18.509> basically<00:01:18.869> we'll<00:01:19.110> we'll 00:01:19.429 --> 00:01:19.439 align:start position:0% scalability so so basically we'll we'll 00:01:19.439 --> 00:01:21.560 align:start position:0% scalability so so basically we'll we'll build<00:01:19.770> an<00:01:19.979> elliptic<00:01:20.400> curve<00:01:20.580> inside<00:01:21.210> the<00:01:21.360> snark 00:01:21.560 --> 00:01:21.570 align:start position:0% build an elliptic curve inside the snark 00:01:21.570 --> 00:01:23.240 align:start position:0% build an elliptic curve inside the snark and<00:01:22.140> we'll<00:01:22.320> use<00:01:22.470> that<00:01:22.590> to<00:01:22.650> make<00:01:22.799> signatures 00:01:23.240 --> 00:01:23.250 align:start position:0% and we'll use that to make signatures 00:01:23.250 --> 00:01:25.190 align:start position:0% and we'll use that to make signatures and<00:01:23.460> we'll<00:01:23.580> use<00:01:23.610> that<00:01:23.759> also<00:01:24.090> to<00:01:24.270> Patterson 00:01:25.190 --> 00:01:25.200 align:start position:0% and we'll use that also to Patterson 00:01:25.200 --> 00:01:27.679 align:start position:0% and we'll use that also to Patterson commitments<00:01:25.710> and<00:01:26.310> then<00:01:26.820> we<00:01:26.970> then<00:01:27.299> we<00:01:27.360> sort<00:01:27.659> of 00:01:27.679 --> 00:01:27.689 align:start position:0% commitments and then we then we sort of 00:01:27.689 --> 00:01:28.880 align:start position:0% commitments and then we then we sort of join<00:01:27.869> that<00:01:28.020> all<00:01:28.170> together<00:01:28.320> to<00:01:28.590> make<00:01:28.619> something 00:01:28.880 --> 00:01:28.890 align:start position:0% join that all together to make something 00:01:28.890 --> 00:01:31.100 align:start position:0% join that all together to make something called<00:01:29.070> roll-up<00:01:29.460> where<00:01:29.939> and<00:01:30.509> how<00:01:30.630> what 00:01:31.100 --> 00:01:31.110 align:start position:0% called roll-up where and how what 00:01:31.110 --> 00:01:32.899 align:start position:0% called roll-up where and how what roll-up<00:01:31.380> is<00:01:31.530> is<00:01:31.740> roll-up<00:01:32.340> aggregates 00:01:32.899 --> 00:01:32.909 align:start position:0% roll-up is is roll-up aggregates 00:01:32.909 --> 00:01:36.260 align:start position:0% roll-up is is roll-up aggregates transactions<00:01:33.420> together<00:01:33.659> in<00:01:33.900> order<00:01:34.020> to<00:01:35.270> it 00:01:36.260 --> 00:01:36.270 align:start position:0% transactions together in order to it 00:01:36.270 --> 00:01:38.210 align:start position:0% transactions together in order to it aggregates<00:01:36.570> transaction<00:01:37.200> validation<00:01:37.740> so 00:01:38.210 --> 00:01:38.220 align:start position:0% aggregates transaction validation so 00:01:38.220 --> 00:01:40.819 align:start position:0% aggregates transaction validation so instead<00:01:38.490> of<00:01:38.549> having<00:01:38.729> to<00:01:39.170> verify<00:01:40.170> 10,000 00:01:40.819 --> 00:01:40.829 align:start position:0% instead of having to verify 10,000 00:01:40.829 --> 00:01:43.249 align:start position:0% instead of having to verify 10,000 signatures<00:01:41.400> inside<00:01:41.850> the<00:01:42.090> EVM<00:01:42.479> you<00:01:42.990> have<00:01:43.140> to 00:01:43.249 --> 00:01:43.259 align:start position:0% signatures inside the EVM you have to 00:01:43.259 --> 00:01:47.780 align:start position:0% signatures inside the EVM you have to verify<00:01:43.740> a<00:01:43.770> single<00:01:44.189> snag<00:01:44.670> proof<00:01:46.520> you<00:01:47.520> can<00:01:47.640> come 00:01:47.780 --> 00:01:47.790 align:start position:0% verify a single snag proof you can come 00:01:47.790 --> 00:01:59.620 align:start position:0% verify a single snag proof you can come in<00:01:47.880> it's<00:01:48.000> okay<00:01:48.149> oh<00:01:51.079> yeah<00:01:52.970> who<00:01:53.970> said<00:01:54.180> that 00:01:59.620 --> 00:01:59.630 align:start position:0% 00:01:59.630 --> 00:02:03.560 align:start position:0% okay<00:02:00.630> so<00:02:00.829> yeah<00:02:01.829> so<00:02:02.100> then<00:02:02.609> so<00:02:03.119> that's<00:02:03.299> that's 00:02:03.560 --> 00:02:03.570 align:start position:0% okay so yeah so then so that's that's 00:02:03.570 --> 00:02:05.539 align:start position:0% okay so yeah so then so that's that's what<00:02:03.780> we<00:02:03.869> use<00:02:04.049> we<00:02:04.409> use<00:02:04.439> that's<00:02:05.189> what<00:02:05.310> roll<00:02:05.460> up 00:02:05.539 --> 00:02:05.549 align:start position:0% what we use we use that's what roll up 00:02:05.549 --> 00:02:07.340 align:start position:0% what we use we use that's what roll up it's<00:02:05.700> yeah<00:02:05.939> it's<00:02:06.119> just<00:02:06.270> it's<00:02:06.869> a<00:02:06.960> scalability 00:02:07.340 --> 00:02:07.350 align:start position:0% it's yeah it's just it's a scalability 00:02:07.350 --> 00:02:08.949 align:start position:0% it's yeah it's just it's a scalability solution<00:02:07.890> okay 00:02:08.949 --> 00:02:08.959 align:start position:0% solution okay 00:02:08.959 --> 00:02:12.830 align:start position:0% solution okay so<00:02:09.959> first<00:02:10.259> what<00:02:10.470> is<00:02:10.500> a<00:02:10.649> snack<00:02:10.950> okay<00:02:11.760> so<00:02:12.510> a<00:02:12.540> snake 00:02:12.830 --> 00:02:12.840 align:start position:0% so first what is a snack okay so a snake 00:02:12.840 --> 00:02:15.320 align:start position:0% so first what is a snack okay so a snake is<00:02:13.049> a<00:02:13.440> snake<00:02:13.920> is<00:02:14.340> a<00:02:14.370> way<00:02:14.580> of<00:02:14.760> proving<00:02:14.940> that<00:02:15.120> you 00:02:15.320 --> 00:02:15.330 align:start position:0% is a snake is a way of proving that you 00:02:15.330 --> 00:02:18.920 align:start position:0% is a snake is a way of proving that you did<00:02:15.480> a<00:02:15.510> computation<00:02:16.140> without<00:02:17.660> proving<00:02:18.660> out 00:02:18.920 --> 00:02:18.930 align:start position:0% did a computation without proving out 00:02:18.930 --> 00:02:20.180 align:start position:0% did a computation without proving out proving<00:02:19.319> that<00:02:19.379> you<00:02:19.500> did<00:02:19.620> a<00:02:19.650> computation 00:02:20.180 --> 00:02:20.190 align:start position:0% proving that you did a computation 00:02:20.190 --> 00:02:22.670 align:start position:0% proving that you did a computation correctly<00:02:20.640> yeah<00:02:21.060> so<00:02:21.750> the<00:02:21.870> verification<00:02:22.500> of<00:02:22.590> a 00:02:22.670 --> 00:02:22.680 align:start position:0% correctly yeah so the verification of a 00:02:22.680 --> 00:02:26.960 align:start position:0% correctly yeah so the verification of a snark<00:02:22.920> is<00:02:23.690> succinct<00:02:24.690> oh<00:02:25.610> wait<00:02:26.610> I'll<00:02:26.700> say<00:02:26.849> that 00:02:26.960 --> 00:02:26.970 align:start position:0% snark is succinct oh wait I'll say that 00:02:26.970 --> 00:02:31.220 align:start position:0% snark is succinct oh wait I'll say that later<00:02:27.120> so<00:02:28.099> given<00:02:29.099> given<00:02:29.489> some<00:02:30.049> inputs<00:02:31.049> and 00:02:31.220 --> 00:02:31.230 align:start position:0% later so given given some inputs and 00:02:31.230 --> 00:02:33.410 align:start position:0% later so given given some inputs and some<00:02:32.069> code<00:02:32.340> that<00:02:32.489> we<00:02:32.579> predefined<00:02:33.120> before 00:02:33.410 --> 00:02:33.420 align:start position:0% some code that we predefined before 00:02:33.420 --> 00:02:36.259 align:start position:0% some code that we predefined before we'll<00:02:34.260> get<00:02:34.470> some<00:02:34.680> outputs<00:02:35.099> yeah<00:02:35.760> that's<00:02:36.090> what 00:02:36.259 --> 00:02:36.269 align:start position:0% we'll get some outputs yeah that's what 00:02:36.269 --> 00:02:39.199 align:start position:0% we'll get some outputs yeah that's what that's<00:02:36.450> what<00:02:36.599> a<00:02:36.630> snack<00:02:36.840> proves<00:02:37.110> yeah<00:02:38.209> prove 00:02:39.199 --> 00:02:39.209 align:start position:0% that's what a snack proves yeah prove 00:02:39.209 --> 00:02:40.280 align:start position:0% that's what a snack proves yeah prove that<00:02:39.329> we<00:02:39.420> run<00:02:39.510> the<00:02:39.630> code<00:02:39.720> with<00:02:39.900> the<00:02:39.959> inputs<00:02:40.200> and 00:02:40.280 --> 00:02:40.290 align:start position:0% that we run the code with the inputs and 00:02:40.290 --> 00:02:42.890 align:start position:0% that we run the code with the inputs and got<00:02:40.410> the<00:02:40.500> outputs<00:02:40.799> yeah<00:02:41.480> but<00:02:42.480> then<00:02:42.630> we<00:02:42.720> can<00:02:42.840> do 00:02:42.890 --> 00:02:42.900 align:start position:0% got the outputs yeah but then we can do 00:02:42.900 --> 00:02:44.420 align:start position:0% got the outputs yeah but then we can do cool<00:02:43.079> things<00:02:43.140> right<00:02:43.680> we<00:02:43.860> can<00:02:44.010> sort<00:02:44.220> of<00:02:44.280> hide 00:02:44.420 --> 00:02:44.430 align:start position:0% cool things right we can sort of hide 00:02:44.430 --> 00:02:45.770 align:start position:0% cool things right we can sort of hide some<00:02:44.700> of<00:02:44.730> the<00:02:44.880> inputs<00:02:45.150> and<00:02:45.360> some<00:02:45.569> of<00:02:45.690> the 00:02:45.770 --> 00:02:45.780 align:start position:0% some of the inputs and some of the 00:02:45.780 --> 00:02:48.500 align:start position:0% some of the inputs and some of the outputs<00:02:46.430> yeah<00:02:47.430> and<00:02:47.610> that's<00:02:47.700> this<00:02:48.060> is<00:02:48.209> where<00:02:48.390> we 00:02:48.500 --> 00:02:48.510 align:start position:0% outputs yeah and that's this is where we 00:02:48.510 --> 00:02:52.789 align:start position:0% outputs yeah and that's this is where we get<00:02:48.660> our<00:02:49.340> privacy<00:02:50.870> properties<00:02:51.870> right<00:02:52.440> because 00:02:52.789 --> 00:02:52.799 align:start position:0% get our privacy properties right because 00:02:52.799 --> 00:02:55.400 align:start position:0% get our privacy properties right because we<00:02:52.920> can<00:02:53.040> start<00:02:53.220> to<00:02:53.280> hide<00:02:53.430> things<00:02:53.930> so<00:02:54.930> or<00:02:55.170> we<00:02:55.290> can 00:02:55.400 --> 00:02:55.410 align:start position:0% we can start to hide things so or we can 00:02:55.410 --> 00:02:56.300 align:start position:0% we can start to hide things so or we can hide<00:02:55.560> everything<00:02:55.769> but<00:02:55.980> that<00:02:56.069> doesn't<00:02:56.250> really 00:02:56.300 --> 00:02:56.310 align:start position:0% hide everything but that doesn't really 00:02:56.310 --> 00:02:57.949 align:start position:0% hide everything but that doesn't really make<00:02:56.489> much<00:02:56.700> that<00:02:57.120> that<00:02:57.360> kind<00:02:57.660> of<00:02:57.690> makes<00:02:57.840> sense 00:02:57.949 --> 00:02:57.959 align:start position:0% make much that that kind of makes sense 00:02:57.959 --> 00:03:02.349 align:start position:0% make much that that kind of makes sense but<00:02:58.170> not<00:02:58.319> in<00:02:58.500> not<00:02:58.769> in<00:02:58.799> a<00:02:58.980> lot<00:02:59.129> of<00:02:59.160> applications 00:03:02.349 --> 00:03:02.359 align:start position:0% 00:03:02.359 --> 00:03:05.479 align:start position:0% okay<00:03:03.359> so<00:03:04.049> so<00:03:04.590> for<00:03:04.829> the<00:03:04.920> rest<00:03:05.069> of<00:03:05.190> the<00:03:05.310> talk 00:03:05.479 --> 00:03:05.489 align:start position:0% okay so so for the rest of the talk 00:03:05.489 --> 00:03:07.580 align:start position:0% okay so so for the rest of the talk we'll<00:03:05.700> just<00:03:05.910> talk<00:03:06.060> about<00:03:06.299> this<00:03:06.420> code<00:03:06.690> yeah<00:03:07.260> so 00:03:07.580 --> 00:03:07.590 align:start position:0% we'll just talk about this code yeah so 00:03:07.590 --> 00:03:09.650 align:start position:0% we'll just talk about this code yeah so in<00:03:07.769> the<00:03:07.889> center<00:03:08.160> box<00:03:08.310> inside<00:03:08.670> the<00:03:08.790> snake<00:03:09.000> we 00:03:09.650 --> 00:03:09.660 align:start position:0% in the center box inside the snake we 00:03:09.660 --> 00:03:11.629 align:start position:0% in the center box inside the snake we have<00:03:09.840> this<00:03:09.959> code<00:03:10.290> that<00:03:10.799> defines<00:03:11.190> what<00:03:11.370> we're 00:03:11.629 --> 00:03:11.639 align:start position:0% have this code that defines what we're 00:03:11.639 --> 00:03:16.009 align:start position:0% have this code that defines what we're verifying<00:03:13.160> so<00:03:14.160> we'd<00:03:14.310> use<00:03:14.340> that<00:03:14.459> to<00:03:15.019> verify 00:03:16.009 --> 00:03:16.019 align:start position:0% verifying so we'd use that to verify 00:03:16.019 --> 00:03:17.780 align:start position:0% verifying so we'd use that to verify that<00:03:16.049> yeah<00:03:16.620> so<00:03:16.829> so<00:03:17.040> that's<00:03:17.220> the<00:03:17.459> central 00:03:17.780 --> 00:03:17.790 align:start position:0% that yeah so so that's the central 00:03:17.790 --> 00:03:19.759 align:start position:0% that yeah so so that's the central problem<00:03:18.120> that<00:03:18.389> we're<00:03:18.569> trying<00:03:18.989> to<00:03:19.109> solve<00:03:19.290> yeah 00:03:19.759 --> 00:03:19.769 align:start position:0% problem that we're trying to solve yeah 00:03:19.769 --> 00:03:21.670 align:start position:0% problem that we're trying to solve yeah that<00:03:19.950> it's<00:03:20.069> difficult<00:03:20.250> to<00:03:20.609> make<00:03:21.239> this<00:03:21.359> code 00:03:21.670 --> 00:03:21.680 align:start position:0% that it's difficult to make this code 00:03:21.680 --> 00:03:25.729 align:start position:0% that it's difficult to make this code that<00:03:22.680> verifies<00:03:23.280> that<00:03:24.380> yeah<00:03:25.380> so<00:03:25.620> it's 00:03:25.729 --> 00:03:25.739 align:start position:0% that verifies that yeah so it's 00:03:25.739 --> 00:03:27.530 align:start position:0% that verifies that yeah so it's difficult<00:03:25.950> to<00:03:26.250> define<00:03:26.549> the<00:03:26.760> computation<00:03:27.359> that 00:03:27.530 --> 00:03:27.540 align:start position:0% difficult to define the computation that 00:03:27.540 --> 00:03:30.140 align:start position:0% difficult to define the computation that you're<00:03:28.049> verifying<00:03:28.530> you<00:03:28.680> did<00:03:28.829> correctly<00:03:29.280> so<00:03:29.790> so 00:03:30.140 --> 00:03:30.150 align:start position:0% you're verifying you did correctly so so 00:03:30.150 --> 00:03:31.610 align:start position:0% you're verifying you did correctly so so that's<00:03:30.329> what<00:03:30.480> we're<00:03:30.569> gonna<00:03:30.660> talk<00:03:30.870> about<00:03:30.900> later 00:03:31.610 --> 00:03:31.620 align:start position:0% that's what we're gonna talk about later 00:03:31.620 --> 00:03:33.289 align:start position:0% that's what we're gonna talk about later or<00:03:31.950> that's<00:03:32.400> like<00:03:32.639> that's<00:03:32.910> like<00:03:33.030> the<00:03:33.180> main 00:03:33.289 --> 00:03:33.299 align:start position:0% or that's like that's like the main 00:03:33.299 --> 00:03:34.819 align:start position:0% or that's like that's like the main theme<00:03:33.540> of<00:03:33.569> this<00:03:33.810> talk<00:03:34.019> yeah<00:03:34.470> that<00:03:34.620> will<00:03:34.739> go 00:03:34.819 --> 00:03:34.829 align:start position:0% theme of this talk yeah that will go 00:03:34.829 --> 00:03:36.589 align:start position:0% theme of this talk yeah that will go through<00:03:35.040> that<00:03:35.160> and<00:03:35.639> we'll<00:03:35.849> see<00:03:36.150> how<00:03:36.389> it 00:03:36.589 --> 00:03:36.599 align:start position:0% through that and we'll see how it 00:03:36.599 --> 00:03:38.960 align:start position:0% through that and we'll see how it applies<00:03:36.989> to<00:03:37.019> three<00:03:37.440> different<00:03:37.970> solutions 00:03:38.960 --> 00:03:38.970 align:start position:0% applies to three different solutions 00:03:38.970 --> 00:03:46.280 align:start position:0% applies to three different solutions okay<00:03:39.299> oh<00:03:43.669> yeah<00:03:44.669> okay<00:03:45.510> so<00:03:45.569> how<00:03:46.049> does<00:03:46.109> this 00:03:46.280 --> 00:03:46.290 align:start position:0% okay oh yeah okay so how does this 00:03:46.290 --> 00:03:47.870 align:start position:0% okay oh yeah okay so how does this relate<00:03:46.500> to<00:03:46.620> aetherium<00:03:47.010> so<00:03:47.370> so<00:03:47.639> we<00:03:47.760> can 00:03:47.870 --> 00:03:47.880 align:start position:0% relate to aetherium so so we can 00:03:47.880 --> 00:03:51.140 align:start position:0% relate to aetherium so so we can validate<00:03:48.000> thanks<00:03:48.510> inside<00:03:48.750> the<00:03:48.840> EBM<00:03:50.150> although 00:03:51.140 --> 00:03:51.150 align:start position:0% validate thanks inside the EBM although 00:03:51.150 --> 00:03:52.250 align:start position:0% validate thanks inside the EBM although it's<00:03:51.299> a<00:03:51.359> little<00:03:51.450> bit<00:03:51.569> expensive<00:03:51.720> it<00:03:52.169> costs 00:03:52.250 --> 00:03:52.260 align:start position:0% it's a little bit expensive it costs 00:03:52.260 --> 00:03:53.930 align:start position:0% it's a little bit expensive it costs about<00:03:52.530> five<00:03:52.739> hundred<00:03:52.859> thousand<00:03:53.250> gasp<00:03:53.370> at 00:03:53.930 --> 00:03:53.940 align:start position:0% about five hundred thousand gasp at 00:03:53.940 --> 00:03:55.490 align:start position:0% about five hundred thousand gasp at optimal<00:03:54.450> to<00:03:54.780> do<00:03:55.049> that<00:03:55.200> right<00:03:55.319> now 00:03:55.490 --> 00:03:55.500 align:start position:0% optimal to do that right now 00:03:55.500 --> 00:03:57.500 align:start position:0% optimal to do that right now but<00:03:55.769> there's<00:03:55.950> the<00:03:56.190> there<00:03:56.519> is<00:03:56.639> scope<00:03:56.910> to<00:03:57.090> reduce 00:03:57.500 --> 00:03:57.510 align:start position:0% but there's the there is scope to reduce 00:03:57.510 --> 00:04:01.490 align:start position:0% but there's the there is scope to reduce those<00:03:57.660> costs<00:03:58.760> so<00:04:00.019> and<00:04:01.019> this<00:04:01.200> means<00:04:01.349> we<00:04:01.440> can 00:04:01.490 --> 00:04:01.500 align:start position:0% those costs so and this means we can 00:04:01.500 --> 00:04:03.500 align:start position:0% those costs so and this means we can have<00:04:01.680> privacy<00:04:01.980> and<00:04:02.160> scalability<00:04:02.519> yeah<00:04:03.180> we<00:04:03.389> can 00:04:03.500 --> 00:04:03.510 align:start position:0% have privacy and scalability yeah we can 00:04:03.510 --> 00:04:05.240 align:start position:0% have privacy and scalability yeah we can have<00:04:03.599> privacy<00:04:04.019> by<00:04:04.169> just<00:04:04.380> hiding<00:04:04.680> the<00:04:04.799> inputs 00:04:05.240 --> 00:04:05.250 align:start position:0% have privacy by just hiding the inputs 00:04:05.250 --> 00:04:07.340 align:start position:0% have privacy by just hiding the inputs that<00:04:05.400> we<00:04:05.519> have<00:04:05.699> and<00:04:06.000> we<00:04:06.479> can<00:04:06.630> add<00:04:06.750> scalability 00:04:07.340 --> 00:04:07.350 align:start position:0% that we have and we can add scalability 00:04:07.350 --> 00:04:08.280 align:start position:0% that we have and we can add scalability because<00:04:07.650> the 00:04:08.280 --> 00:04:08.290 align:start position:0% because the 00:04:08.290 --> 00:04:10.440 align:start position:0% because the the<00:04:08.409> ballot<00:04:09.220> the<00:04:09.459> verification<00:04:10.090> of<00:04:10.150> a<00:04:10.269> proof 00:04:10.440 --> 00:04:10.450 align:start position:0% the ballot the verification of a proof 00:04:10.450 --> 00:04:12.030 align:start position:0% the ballot the verification of a proof is<00:04:10.599> succinct<00:04:11.019> it<00:04:11.349> takes<00:04:11.500> the<00:04:11.590> same<00:04:11.739> amount<00:04:11.799> of 00:04:12.030 --> 00:04:12.040 align:start position:0% is succinct it takes the same amount of 00:04:12.040 --> 00:04:14.130 align:start position:0% is succinct it takes the same amount of time<00:04:12.220> no<00:04:12.370> matter<00:04:12.489> how<00:04:12.640> complicated<00:04:13.000> the<00:04:13.360> the 00:04:14.130 --> 00:04:14.140 align:start position:0% time no matter how complicated the the 00:04:14.140 --> 00:04:17.670 align:start position:0% time no matter how complicated the the code<00:04:14.319> that<00:04:14.470> you<00:04:14.590> are<00:04:14.860> verifying<00:04:15.459> is<00:04:16.269> yeah<00:04:17.019> so 00:04:17.670 --> 00:04:17.680 align:start position:0% code that you are verifying is yeah so 00:04:17.680 --> 00:04:18.810 align:start position:0% code that you are verifying is yeah so for<00:04:17.889> the<00:04:17.949> rest<00:04:18.100> of<00:04:18.220> the<00:04:18.310> talk<00:04:18.459> we're<00:04:18.639> gonna 00:04:18.810 --> 00:04:18.820 align:start position:0% for the rest of the talk we're gonna 00:04:18.820 --> 00:04:20.580 align:start position:0% for the rest of the talk we're gonna define<00:04:19.090> the<00:04:19.239> code<00:04:19.660> that<00:04:20.049> we<00:04:20.169> saw<00:04:20.320> in<00:04:20.500> the 00:04:20.580 --> 00:04:20.590 align:start position:0% define the code that we saw in the 00:04:20.590 --> 00:04:22.230 align:start position:0% define the code that we saw in the previous<00:04:20.769> figure<00:04:21.130> here<00:04:21.489> yeah 00:04:22.230 --> 00:04:22.240 align:start position:0% previous figure here yeah 00:04:22.240 --> 00:04:23.520 align:start position:0% previous figure here yeah we're<00:04:22.479> just<00:04:22.600> going<00:04:22.810> to<00:04:22.870> define<00:04:22.960> the<00:04:23.169> code<00:04:23.350> that 00:04:23.520 --> 00:04:23.530 align:start position:0% we're just going to define the code that 00:04:23.530 --> 00:04:27.270 align:start position:0% we're just going to define the code that defines<00:04:23.830> the<00:04:23.979> snack<00:04:24.160> okay<00:04:24.910> so<00:04:25.750> a<00:04:26.169> lot<00:04:27.130> of<00:04:27.190> the 00:04:27.270 --> 00:04:27.280 align:start position:0% defines the snack okay so a lot of the 00:04:27.280 --> 00:04:30.480 align:start position:0% defines the snack okay so a lot of the time<00:04:27.430> in<00:04:27.550> boxing<00:04:27.789> we<00:04:27.940> talk<00:04:28.090> about<00:04:28.240> a<00:04:29.430> lot<00:04:30.430> of 00:04:30.480 --> 00:04:30.490 align:start position:0% time in boxing we talk about a lot of 00:04:30.490 --> 00:04:32.460 align:start position:0% time in boxing we talk about a lot of the<00:04:30.610> time<00:04:30.760> in<00:04:30.880> boxing<00:04:31.180> we<00:04:31.270> talk<00:04:31.449> about<00:04:31.600> Merkle 00:04:32.460 --> 00:04:32.470 align:start position:0% the time in boxing we talk about Merkle 00:04:32.470 --> 00:04:33.750 align:start position:0% the time in boxing we talk about Merkle trees<00:04:32.620> right<00:04:32.830> because<00:04:33.100> Merkle<00:04:33.490> trees<00:04:33.610> are<00:04:33.729> a 00:04:33.750 --> 00:04:33.760 align:start position:0% trees right because Merkle trees are a 00:04:33.760 --> 00:04:35.610 align:start position:0% trees right because Merkle trees are a good<00:04:33.910> aggregator<00:04:34.270> of<00:04:34.360> information<00:04:34.900> so<00:04:35.380> this 00:04:35.610 --> 00:04:35.620 align:start position:0% good aggregator of information so this 00:04:35.620 --> 00:04:38.400 align:start position:0% good aggregator of information so this is<00:04:35.860> how<00:04:36.039> a<00:04:36.070> Merkle<00:04:36.430> tree<00:04:36.550> works<00:04:37.050> so<00:04:38.050> basically 00:04:38.400 --> 00:04:38.410 align:start position:0% is how a Merkle tree works so basically 00:04:38.410 --> 00:04:40.379 align:start position:0% is how a Merkle tree works so basically you<00:04:38.530> have<00:04:38.650> ABC<00:04:39.010> and<00:04:39.310> D<00:04:39.460> and<00:04:39.729> those<00:04:40.120> are<00:04:40.270> the 00:04:40.379 --> 00:04:40.389 align:start position:0% you have ABC and D and those are the 00:04:40.389 --> 00:04:43.050 align:start position:0% you have ABC and D and those are the members<00:04:40.720> of<00:04:40.870> our<00:04:40.990> group<00:04:41.020> and<00:04:41.470> we<00:04:42.000> want<00:04:43.000> to 00:04:43.050 --> 00:04:43.060 align:start position:0% members of our group and we want to 00:04:43.060 --> 00:04:44.670 align:start position:0% members of our group and we want to aggregate<00:04:43.360> those<00:04:43.660> together<00:04:44.020> to<00:04:44.260> a<00:04:44.289> single 00:04:44.670 --> 00:04:44.680 align:start position:0% aggregate those together to a single 00:04:44.680 --> 00:04:47.580 align:start position:0% aggregate those together to a single root<00:04:45.550> yeah<00:04:46.030> so<00:04:46.539> what<00:04:46.660> we<00:04:46.750> do<00:04:46.900> is<00:04:47.050> we<00:04:47.169> hash<00:04:47.320> A<00:04:47.470> and 00:04:47.580 --> 00:04:47.590 align:start position:0% root yeah so what we do is we hash A and 00:04:47.590 --> 00:04:49.080 align:start position:0% root yeah so what we do is we hash A and B<00:04:47.680> together<00:04:47.770> we<00:04:48.100> have<00:04:48.220> C<00:04:48.370> and<00:04:48.490> D<00:04:48.550> together<00:04:48.699> and 00:04:49.080 --> 00:04:49.090 align:start position:0% B together we have C and D together and 00:04:49.090 --> 00:04:51.000 align:start position:0% B together we have C and D together and then<00:04:49.210> we<00:04:49.300> hash<00:04:49.539> a<00:04:49.810> and<00:04:50.320> B<00:04:50.440> C<00:04:50.650> and<00:04:50.800> D<00:04:50.889> together 00:04:51.000 --> 00:04:51.010 align:start position:0% then we hash a and B C and D together 00:04:51.010 --> 00:04:52.920 align:start position:0% then we hash a and B C and D together and<00:04:51.340> that<00:04:51.430> gives<00:04:51.520> us<00:04:51.669> the<00:04:52.000> root<00:04:52.150> yeah 00:04:52.920 --> 00:04:52.930 align:start position:0% and that gives us the root yeah 00:04:52.930 --> 00:04:55.529 align:start position:0% and that gives us the root yeah so<00:04:53.260> so<00:04:53.620> sorry<00:04:53.889> so<00:04:54.100> we<00:04:54.220> hash<00:04:54.430> the<00:04:54.760> hash<00:04:55.150> of<00:04:55.330> a<00:04:55.389> and 00:04:55.529 --> 00:04:55.539 align:start position:0% so so sorry so we hash the hash of a and 00:04:55.539 --> 00:04:57.090 align:start position:0% so so sorry so we hash the hash of a and B<00:04:55.660> and<00:04:55.840> the<00:04:55.930> hash<00:04:56.080> of<00:04:56.229> C<00:04:56.350> and<00:04:56.500> D<00:04:56.560> together<00:04:56.710> and 00:04:57.090 --> 00:04:57.100 align:start position:0% B and the hash of C and D together and 00:04:57.100 --> 00:05:00.600 align:start position:0% B and the hash of C and D together and we<00:04:57.190> get<00:04:57.280> the<00:04:57.400> root<00:04:58.199> so<00:04:59.199> and<00:04:59.680> then<00:05:00.250> we<00:05:00.370> can<00:05:00.490> make 00:05:00.600 --> 00:05:00.610 align:start position:0% we get the root so and then we can make 00:05:00.610 --> 00:05:01.980 align:start position:0% we get the root so and then we can make something<00:05:00.820> called<00:05:00.940> mirco<00:05:01.270> proof<00:05:01.479> and<00:05:01.720> prove 00:05:01.980 --> 00:05:01.990 align:start position:0% something called mirco proof and prove 00:05:01.990 --> 00:05:03.540 align:start position:0% something called mirco proof and prove that<00:05:02.020> we<00:05:02.260> remember<00:05:02.440> and<00:05:03.010> we<00:05:03.130> can<00:05:03.280> prove<00:05:03.490> that 00:05:03.540 --> 00:05:03.550 align:start position:0% that we remember and we can prove that 00:05:03.550 --> 00:05:06.659 align:start position:0% that we remember and we can prove that we're<00:05:03.820> a<00:05:03.850> member<00:05:04.150> of<00:05:04.240> that<00:05:04.330> set<00:05:04.650> okay<00:05:05.650> but<00:05:06.039> so 00:05:06.659 --> 00:05:06.669 align:start position:0% we're a member of that set okay but so 00:05:06.669 --> 00:05:09.120 align:start position:0% we're a member of that set okay but so let's<00:05:06.910> go<00:05:07.060> forward<00:05:07.539> okay<00:05:08.440> so<00:05:08.500> let's<00:05:08.860> let's 00:05:09.120 --> 00:05:09.130 align:start position:0% let's go forward okay so let's let's 00:05:09.130 --> 00:05:11.450 align:start position:0% let's go forward okay so let's let's think<00:05:09.280> about<00:05:09.490> this<00:05:09.760> now<00:05:09.880> so<00:05:10.120> so<00:05:10.389> we<00:05:10.539> can<00:05:10.570> move 00:05:11.450 --> 00:05:11.460 align:start position:0% think about this now so so we can move 00:05:11.460 --> 00:05:15.719 align:start position:0% think about this now so so we can move we<00:05:12.460> can<00:05:12.610> move<00:05:12.820> that<00:05:13.830> Merkle<00:05:14.830> proof<00:05:15.039> inside<00:05:15.699> a 00:05:15.719 --> 00:05:15.729 align:start position:0% we can move that Merkle proof inside a 00:05:15.729 --> 00:05:18.270 align:start position:0% we can move that Merkle proof inside a snack<00:05:16.289> yeah<00:05:17.289> and<00:05:17.500> this<00:05:17.560> lets<00:05:17.800> us<00:05:17.949> do<00:05:18.099> some 00:05:18.270 --> 00:05:18.280 align:start position:0% snack yeah and this lets us do some 00:05:18.280 --> 00:05:25.110 align:start position:0% snack yeah and this lets us do some really<00:05:18.460> cool<00:05:18.639> things<00:05:19.320> okay<00:05:21.599> yeah<00:05:23.280> okay<00:05:24.280> so<00:05:24.880> but 00:05:25.110 --> 00:05:25.120 align:start position:0% really cool things okay yeah okay so but 00:05:25.120 --> 00:05:27.719 align:start position:0% really cool things okay yeah okay so but but<00:05:25.510> in<00:05:25.660> order<00:05:25.900> in<00:05:26.139> order<00:05:26.289> to<00:05:26.560> so<00:05:27.099> we<00:05:27.520> can<00:05:27.639> do 00:05:27.719 --> 00:05:27.729 align:start position:0% but in order in order to so we can do 00:05:27.729 --> 00:05:30.300 align:start position:0% but in order in order to so we can do cool<00:05:27.940> things<00:05:28.180> here<00:05:28.389> but<00:05:28.930> but<00:05:29.110> it's<00:05:29.320> there's 00:05:30.300 --> 00:05:30.310 align:start position:0% cool things here but but it's there's 00:05:30.310 --> 00:05:32.250 align:start position:0% cool things here but but it's there's nobody<00:05:30.729> has<00:05:30.849> any<00:05:31.000> permissions<00:05:31.479> here<00:05:31.630> right 00:05:32.250 --> 00:05:32.260 align:start position:0% nobody has any permissions here right 00:05:32.260 --> 00:05:34.320 align:start position:0% nobody has any permissions here right because<00:05:32.410> ABC<00:05:33.190> and<00:05:33.340> D<00:05:33.430> are<00:05:33.550> all<00:05:33.669> public<00:05:34.060> and 00:05:34.320 --> 00:05:34.330 align:start position:0% because ABC and D are all public and 00:05:34.330 --> 00:05:36.060 align:start position:0% because ABC and D are all public and that<00:05:34.360> means<00:05:34.750> anyone<00:05:35.169> can<00:05:35.229> prove<00:05:35.500> that<00:05:35.620> a<00:05:35.680> B<00:05:35.919> and 00:05:36.060 --> 00:05:36.070 align:start position:0% that means anyone can prove that a B and 00:05:36.070 --> 00:05:38.580 align:start position:0% that means anyone can prove that a B and C<00:05:36.220> in<00:05:36.310> the<00:05:36.460> ABC<00:05:37.389> or<00:05:37.599> D<00:05:37.780> are<00:05:38.020> a<00:05:38.050> member<00:05:38.320> of<00:05:38.440> our 00:05:38.580 --> 00:05:38.590 align:start position:0% C in the ABC or D are a member of our 00:05:38.590 --> 00:05:40.740 align:start position:0% C in the ABC or D are a member of our group<00:05:38.860> but<00:05:39.639> that<00:05:39.699> doesn't<00:05:40.060> really<00:05:40.120> that 00:05:40.740 --> 00:05:40.750 align:start position:0% group but that doesn't really that 00:05:40.750 --> 00:05:42.629 align:start position:0% group but that doesn't really that doesn't<00:05:40.990> really<00:05:41.110> help<00:05:41.260> us<00:05:41.470> we<00:05:42.099> want<00:05:42.310> to<00:05:42.400> we 00:05:42.629 --> 00:05:42.639 align:start position:0% doesn't really help us we want to we 00:05:42.639 --> 00:05:44.159 align:start position:0% doesn't really help us we want to we want<00:05:42.669> to<00:05:42.849> have<00:05:43.000> a<00:05:43.030> way<00:05:43.270> that<00:05:43.510> that<00:05:43.750> people<00:05:44.050> have 00:05:44.159 --> 00:05:44.169 align:start position:0% want to have a way that that people have 00:05:44.169 --> 00:05:45.360 align:start position:0% want to have a way that that people have some<00:05:44.320> private<00:05:44.500> information<00:05:44.770> and<00:05:45.250> they<00:05:45.310> can 00:05:45.360 --> 00:05:45.370 align:start position:0% some private information and they can 00:05:45.370 --> 00:05:46.860 align:start position:0% some private information and they can use<00:05:45.610> that<00:05:45.639> private<00:05:46.000> information<00:05:46.120> to<00:05:46.510> signal 00:05:46.860 --> 00:05:46.870 align:start position:0% use that private information to signal 00:05:46.870 --> 00:05:51.089 align:start position:0% use that private information to signal about<00:05:47.020> to<00:05:49.199> we<00:05:50.199> want<00:05:50.410> it<00:05:50.500> we<00:05:50.650> want<00:05:50.830> to<00:05:50.860> limit 00:05:51.089 --> 00:05:51.099 align:start position:0% about to we want it we want to limit 00:05:51.099 --> 00:05:52.320 align:start position:0% about to we want it we want to limit what<00:05:51.340> people<00:05:51.550> are<00:05:51.639> able<00:05:51.729> to<00:05:51.849> do<00:05:51.970> inside<00:05:52.240> our 00:05:52.320 --> 00:05:52.330 align:start position:0% what people are able to do inside our 00:05:52.330 --> 00:05:54.149 align:start position:0% what people are able to do inside our system<00:05:52.449> so<00:05:53.260> the<00:05:53.470> way<00:05:53.560> that<00:05:53.590> we<00:05:53.740> do<00:05:53.860> that<00:05:53.979> is 00:05:54.149 --> 00:05:54.159 align:start position:0% system so the way that we do that is 00:05:54.159 --> 00:05:55.560 align:start position:0% system so the way that we do that is this<00:05:54.370> that<00:05:54.699> we<00:05:54.789> come<00:05:54.970> up<00:05:55.090> with<00:05:55.180> this<00:05:55.330> really 00:05:55.560 --> 00:05:55.570 align:start position:0% this that we come up with this really 00:05:55.570 --> 00:05:58.379 align:start position:0% this that we come up with this really kind<00:05:56.050> of<00:05:56.260> naive<00:05:57.030> we<00:05:58.030> come<00:05:58.150> up<00:05:58.240> with<00:05:58.330> this 00:05:58.379 --> 00:05:58.389 align:start position:0% kind of naive we come up with this 00:05:58.389 --> 00:06:00.300 align:start position:0% kind of naive we come up with this really<00:05:58.539> naive<00:05:58.840> kind<00:05:59.320> of<00:05:59.409> public<00:05:59.740> key<00:05:59.889> private 00:06:00.300 --> 00:06:00.310 align:start position:0% really naive kind of public key private 00:06:00.310 --> 00:06:02.370 align:start position:0% really naive kind of public key private key<00:06:00.430> scheme<00:06:00.669> yeah<00:06:01.030> and<00:06:01.330> the<00:06:01.840> public<00:06:02.110> key<00:06:02.229> is 00:06:02.370 --> 00:06:02.380 align:start position:0% key scheme yeah and the public key is 00:06:02.380 --> 00:06:06.629 align:start position:0% key scheme yeah and the public key is defined<00:06:02.800> as<00:06:03.010> the<00:06:03.400> hash<00:06:03.580> of<00:06:03.849> of<00:06:04.800> two<00:06:05.800> inputs<00:06:06.520> one 00:06:06.629 --> 00:06:06.639 align:start position:0% defined as the hash of of two inputs one 00:06:06.639 --> 00:06:07.980 align:start position:0% defined as the hash of of two inputs one called<00:06:07.000> it's<00:06:07.180> not<00:06:07.360> a<00:06:07.389> fire<00:06:07.599> one<00:06:07.810> called<00:06:07.960> a 00:06:07.980 --> 00:06:07.990 align:start position:0% called it's not a fire one called a 00:06:07.990 --> 00:06:09.629 align:start position:0% called it's not a fire one called a secret<00:06:08.320> and<00:06:08.650> another<00:06:08.919> fire<00:06:09.099> in<00:06:09.190> the<00:06:09.280> secret<00:06:09.580> I 00:06:09.629 --> 00:06:09.639 align:start position:0% secret and another fire in the secret I 00:06:09.639 --> 00:06:11.219 align:start position:0% secret and another fire in the secret I just<00:06:09.820> random<00:06:10.180> numbers<00:06:10.300> we<00:06:10.599> just<00:06:10.630> regenerate 00:06:11.219 --> 00:06:11.229 align:start position:0% just random numbers we just regenerate 00:06:11.229 --> 00:06:14.850 align:start position:0% just random numbers we just regenerate these<00:06:11.349> random<00:06:11.680> numbers<00:06:11.710> and<00:06:13.500> we<00:06:14.500> hash<00:06:14.740> them 00:06:14.850 --> 00:06:14.860 align:start position:0% these random numbers and we hash them 00:06:14.860 --> 00:06:16.680 align:start position:0% these random numbers and we hash them together<00:06:15.099> to<00:06:15.550> create<00:06:15.580> our<00:06:15.820> public<00:06:16.150> key<00:06:16.270> and<00:06:16.570> we 00:06:16.680 --> 00:06:16.690 align:start position:0% together to create our public key and we 00:06:16.690 --> 00:06:18.390 align:start position:0% together to create our public key and we and<00:06:17.289> we<00:06:17.320> give<00:06:17.560> our<00:06:17.710> public<00:06:17.979> and<00:06:18.099> then<00:06:18.219> we<00:06:18.280> do 00:06:18.390 --> 00:06:18.400 align:start position:0% and we give our public and then we do 00:06:18.400 --> 00:06:19.560 align:start position:0% and we give our public and then we do something<00:06:18.580> else<00:06:18.700> with<00:06:18.849> the<00:06:18.909> public<00:06:19.150> key<00:06:19.240> so 00:06:19.560 --> 00:06:19.570 align:start position:0% something else with the public key so 00:06:19.570 --> 00:06:21.000 align:start position:0% something else with the public key so anyone<00:06:19.840> who<00:06:20.110> knows<00:06:20.229> the<00:06:20.289> private<00:06:20.710> key<00:06:20.800> of<00:06:20.830> the 00:06:21.000 --> 00:06:21.010 align:start position:0% anyone who knows the private key of the 00:06:21.010 --> 00:06:23.840 align:start position:0% anyone who knows the private key of the public<00:06:21.250> key<00:06:21.370> is<00:06:21.490> able<00:06:21.700> to<00:06:21.760> make<00:06:21.880> a<00:06:21.909> C 00:06:23.840 --> 00:06:23.850 align:start position:0% public key is able to make a C 00:06:23.850 --> 00:06:26.340 align:start position:0% public key is able to make a C but<00:06:24.850> this<00:06:25.030> is<00:06:25.180> a<00:06:25.210> little<00:06:25.419> bit<00:06:25.600> naive<00:06:25.810> because 00:06:26.340 --> 00:06:26.350 align:start position:0% but this is a little bit naive because 00:06:26.350 --> 00:06:28.379 align:start position:0% but this is a little bit naive because if<00:06:26.770> if<00:06:27.550> people<00:06:27.610> are<00:06:27.910> able<00:06:28.000> to<00:06:28.090> make<00:06:28.270> the 00:06:28.379 --> 00:06:28.389 align:start position:0% if if people are able to make the 00:06:28.389 --> 00:06:31.740 align:start position:0% if if people are able to make the signatures<00:06:28.900> then<00:06:29.860> they<00:06:30.039> can<00:06:30.250> always<00:06:30.580> then<00:06:30.910> as 00:06:31.740 --> 00:06:31.750 align:start position:0% signatures then they can always then as 00:06:31.750 --> 00:06:33.059 align:start position:0% signatures then they can always then as soon<00:06:31.900> as<00:06:32.050> you<00:06:32.169> make<00:06:32.289> a<00:06:32.319> signature<00:06:32.650> someone 00:06:33.059 --> 00:06:33.069 align:start position:0% soon as you make a signature someone 00:06:33.069 --> 00:06:34.290 align:start position:0% soon as you make a signature someone else<00:06:33.190> can<00:06:33.340> copy<00:06:33.550> your<00:06:33.669> signature<00:06:33.729> because 00:06:34.290 --> 00:06:34.300 align:start position:0% else can copy your signature because 00:06:34.300 --> 00:06:35.790 align:start position:0% else can copy your signature because when<00:06:34.509> you<00:06:34.630> make<00:06:34.720> the<00:06:34.870> signature<00:06:35.139> you<00:06:35.500> reveal 00:06:35.790 --> 00:06:35.800 align:start position:0% when you make the signature you reveal 00:06:35.800 --> 00:06:37.650 align:start position:0% when you make the signature you reveal your<00:06:35.979> private<00:06:36.340> key<00:06:36.460> so<00:06:37.060> it<00:06:37.300> doesn't<00:06:37.569> really 00:06:37.650 --> 00:06:37.660 align:start position:0% your private key so it doesn't really 00:06:37.660 --> 00:06:40.379 align:start position:0% your private key so it doesn't really work<00:06:38.490> but<00:06:39.490> what<00:06:39.699> we<00:06:39.789> can<00:06:39.940> do<00:06:40.000> is<00:06:40.090> we<00:06:40.210> can<00:06:40.270> put 00:06:40.379 --> 00:06:40.389 align:start position:0% work but what we can do is we can put 00:06:40.389 --> 00:06:42.210 align:start position:0% work but what we can do is we can put this<00:06:40.479> inside<00:06:40.750> the<00:06:40.840> snack<00:06:41.020> yes<00:06:41.380> and<00:06:41.620> if<00:06:41.979> we<00:06:42.069> put 00:06:42.210 --> 00:06:42.220 align:start position:0% this inside the snack yes and if we put 00:06:42.220 --> 00:06:43.379 align:start position:0% this inside the snack yes and if we put it<00:06:42.310> inside<00:06:42.460> the<00:06:42.669> snack<00:06:42.849> we<00:06:43.090> can<00:06:43.210> hide<00:06:43.360> the 00:06:43.379 --> 00:06:43.389 align:start position:0% it inside the snack we can hide the 00:06:43.389 --> 00:06:45.120 align:start position:0% it inside the snack we can hide the notifier<00:06:43.870> in<00:06:43.990> the<00:06:44.050> secret<00:06:44.380> and<00:06:44.470> that<00:06:44.949> means 00:06:45.120 --> 00:06:45.130 align:start position:0% notifier in the secret and that means 00:06:45.130 --> 00:06:46.830 align:start position:0% notifier in the secret and that means that<00:06:45.280> our<00:06:45.400> signature<00:06:45.819> scheme<00:06:46.090> becomes<00:06:46.509> kind 00:06:46.830 --> 00:06:46.840 align:start position:0% that our signature scheme becomes kind 00:06:46.840 --> 00:06:50.279 align:start position:0% that our signature scheme becomes kind of<00:06:48.000> yeah<00:06:49.000> that<00:06:49.210> I<00:06:49.240> signature<00:06:49.690> seam<00:06:49.900> now<00:06:50.080> makes 00:06:50.279 --> 00:06:50.289 align:start position:0% of yeah that I signature seam now makes 00:06:50.289 --> 00:06:51.960 align:start position:0% of yeah that I signature seam now makes sense<00:06:50.650> okay<00:06:50.979> people<00:06:51.190> can<00:06:51.430> make<00:06:51.580> signatures 00:06:51.960 --> 00:06:51.970 align:start position:0% sense okay people can make signatures 00:06:51.970 --> 00:06:53.129 align:start position:0% sense okay people can make signatures and<00:06:52.090> it<00:06:52.180> doesn't<00:06:52.449> reveal<00:06:52.599> what<00:06:52.780> their<00:06:52.870> private 00:06:53.129 --> 00:06:53.139 align:start position:0% and it doesn't reveal what their private 00:06:53.139 --> 00:06:57.620 align:start position:0% and it doesn't reveal what their private key<00:06:53.229> so<00:06:53.259> we<00:06:53.500> can<00:06:53.530> do<00:06:54.009> this<00:06:54.130> repeatedly<00:06:54.460> yeah 00:06:57.620 --> 00:06:57.630 align:start position:0% 00:06:57.630 --> 00:06:58.770 align:start position:0% okay 00:06:58.770 --> 00:06:58.780 align:start position:0% okay 00:06:58.780 --> 00:07:00.659 align:start position:0% okay so<00:06:58.960> but<00:06:59.650> but<00:06:59.889> now<00:06:59.979> this<00:07:00.130> doesn't<00:07:00.400> really<00:07:00.520> make 00:07:00.659 --> 00:07:00.669 align:start position:0% so but but now this doesn't really make 00:07:00.669 --> 00:07:02.370 align:start position:0% so but but now this doesn't really make sense<00:07:00.699> as<00:07:00.970> I<00:07:01.060> said<00:07:01.210> before<00:07:01.330> right<00:07:01.660> because<00:07:02.229> we 00:07:02.370 --> 00:07:02.380 align:start position:0% sense as I said before right because we 00:07:02.380 --> 00:07:04.050 align:start position:0% sense as I said before right because we have<00:07:02.530> we<00:07:02.919> just<00:07:03.190> people<00:07:03.610> can<00:07:03.729> prove<00:07:03.940> that 00:07:04.050 --> 00:07:04.060 align:start position:0% have we just people can prove that 00:07:04.060 --> 00:07:05.219 align:start position:0% have we just people can prove that they're<00:07:04.210> a<00:07:04.240> member<00:07:04.539> of<00:07:04.630> this<00:07:04.750> group<00:07:04.900> the 00:07:05.219 --> 00:07:05.229 align:start position:0% they're a member of this group the 00:07:05.229 --> 00:07:07.520 align:start position:0% they're a member of this group the miracle<00:07:05.680> that's<00:07:06.310> defined<00:07:06.699> by<00:07:06.789> the<00:07:06.849> root 00:07:07.520 --> 00:07:07.530 align:start position:0% miracle that's defined by the root 00:07:07.530 --> 00:07:09.659 align:start position:0% miracle that's defined by the root people<00:07:08.530> can<00:07:08.650> people<00:07:09.130> can<00:07:09.250> prove<00:07:09.400> that<00:07:09.520> they're 00:07:09.659 --> 00:07:09.669 align:start position:0% people can people can prove that they're 00:07:09.669 --> 00:07:11.100 align:start position:0% people can people can prove that they're a<00:07:09.699> member<00:07:09.880> but<00:07:10.539> that<00:07:10.690> doesn't<00:07:10.870> really<00:07:10.990> make 00:07:11.100 --> 00:07:11.110 align:start position:0% a member but that doesn't really make 00:07:11.110 --> 00:07:12.629 align:start position:0% a member but that doesn't really make sense<00:07:11.139> because<00:07:11.650> we<00:07:11.830> don't<00:07:12.070> reveal<00:07:12.340> anything 00:07:12.629 --> 00:07:12.639 align:start position:0% sense because we don't reveal anything 00:07:12.639 --> 00:07:14.070 align:start position:0% sense because we don't reveal anything and<00:07:12.970> if<00:07:13.120> you<00:07:13.210> give<00:07:13.389> that<00:07:13.509> proof<00:07:13.690> to<00:07:13.810> somebody 00:07:14.070 --> 00:07:14.080 align:start position:0% and if you give that proof to somebody 00:07:14.080 --> 00:07:16.740 align:start position:0% and if you give that proof to somebody else<00:07:14.259> they<00:07:14.860> don't<00:07:14.979> even<00:07:15.280> know<00:07:15.460> what<00:07:16.389> itwhat<00:07:16.539> is 00:07:16.740 --> 00:07:16.750 align:start position:0% else they don't even know what itwhat is 00:07:16.750 --> 00:07:18.659 align:start position:0% else they don't even know what itwhat is talking<00:07:17.050> about<00:07:17.080> I<00:07:17.470> mean<00:07:17.919> they<00:07:18.070> just<00:07:18.280> know<00:07:18.460> that 00:07:18.659 --> 00:07:18.669 align:start position:0% talking about I mean they just know that 00:07:18.669 --> 00:07:20.129 align:start position:0% talking about I mean they just know that you<00:07:18.789> don't<00:07:19.150> they<00:07:19.509> just<00:07:19.750> know<00:07:19.840> that<00:07:19.990> you're<00:07:20.110> a 00:07:20.129 --> 00:07:20.139 align:start position:0% you don't they just know that you're a 00:07:20.139 --> 00:07:22.379 align:start position:0% you don't they just know that you're a member<00:07:20.349> of<00:07:20.530> song<00:07:20.800> Merkle<00:07:21.520> root<00:07:21.699> and<00:07:22.000> that 00:07:22.379 --> 00:07:22.389 align:start position:0% member of song Merkle root and that 00:07:22.389 --> 00:07:23.909 align:start position:0% member of song Merkle root and that doesn't<00:07:22.750> that<00:07:23.349> doesn't<00:07:23.409> really<00:07:23.740> make<00:07:23.889> sense 00:07:23.909 --> 00:07:23.919 align:start position:0% doesn't that doesn't really make sense 00:07:23.919 --> 00:07:25.860 align:start position:0% doesn't that doesn't really make sense so<00:07:24.460> what<00:07:24.610> so<00:07:24.970> what<00:07:25.120> we<00:07:25.210> need<00:07:25.330> to<00:07:25.360> do<00:07:25.509> is<00:07:25.630> reveal 00:07:25.860 --> 00:07:25.870 align:start position:0% so what so what we need to do is reveal 00:07:25.870 --> 00:07:28.230 align:start position:0% so what so what we need to do is reveal the<00:07:26.050> merkel<00:07:26.289> root<00:07:26.470> yeah<00:07:27.099> and<00:07:27.370> now<00:07:27.729> it<00:07:28.060> starts 00:07:28.230 --> 00:07:28.240 align:start position:0% the merkel root yeah and now it starts 00:07:28.240 --> 00:07:28.890 align:start position:0% the merkel root yeah and now it starts to<00:07:28.449> make<00:07:28.539> sense 00:07:28.890 --> 00:07:28.900 align:start position:0% to make sense 00:07:28.900 --> 00:07:31.050 align:start position:0% to make sense yeah<00:07:29.500> and<00:07:29.680> that<00:07:29.919> now<00:07:30.070> the<00:07:30.130> Merkel<00:07:30.849> root<00:07:30.940> is 00:07:31.050 --> 00:07:31.060 align:start position:0% yeah and that now the Merkel root is 00:07:31.060 --> 00:07:32.550 align:start position:0% yeah and that now the Merkel root is public<00:07:31.389> to<00:07:31.630> the<00:07:31.750> verifier<00:07:32.080> and<00:07:32.320> when<00:07:32.470> they 00:07:32.550 --> 00:07:32.560 align:start position:0% public to the verifier and when they 00:07:32.560 --> 00:07:34.620 align:start position:0% public to the verifier and when they verify<00:07:32.590> it<00:07:33.070> they<00:07:33.220> can<00:07:33.370> see<00:07:33.550> that<00:07:33.789> oh<00:07:33.970> this 00:07:34.620 --> 00:07:34.630 align:start position:0% verify it they can see that oh this 00:07:34.630 --> 00:07:36.779 align:start position:0% verify it they can see that oh this person<00:07:35.050> must<00:07:35.169> know<00:07:35.349> the<00:07:35.500> private<00:07:35.860> key<00:07:36.039> of<00:07:36.220> a 00:07:36.779 --> 00:07:36.789 align:start position:0% person must know the private key of a 00:07:36.789 --> 00:07:40.310 align:start position:0% person must know the private key of a member<00:07:37.150> of<00:07:37.270> this<00:07:37.419> of<00:07:37.719> this<00:07:38.320> group<00:07:38.800> okay<00:07:39.580> oh 00:07:40.310 --> 00:07:40.320 align:start position:0% member of this of this group okay oh 00:07:40.320 --> 00:07:48.060 align:start position:0% member of this of this group okay oh wait<00:07:43.199> what<00:07:44.199> does<00:07:44.289> it<00:07:44.380> say<00:07:46.770> is<00:07:47.770> there<00:07:47.919> some<00:07:48.039> way 00:07:48.060 --> 00:07:48.070 align:start position:0% wait what does it say is there some way 00:07:48.070 --> 00:07:49.709 align:start position:0% wait what does it say is there some way for<00:07:48.159> me<00:07:48.310> to<00:07:48.370> know<00:07:48.520> the<00:07:48.610> time<00:07:48.789> okay<00:07:49.180> I<00:07:49.210> can<00:07:49.419> I<00:07:49.509> can 00:07:49.709 --> 00:07:49.719 align:start position:0% for me to know the time okay I can I can 00:07:49.719 --> 00:07:53.159 align:start position:0% for me to know the time okay I can I can see<00:07:49.840> okay<00:07:50.699> okay<00:07:51.699> so<00:07:51.759> so<00:07:52.599> now<00:07:52.750> we<00:07:52.810> can<00:07:53.020> use<00:07:53.050> it 00:07:53.159 --> 00:07:53.169 align:start position:0% see okay okay so so now we can use it 00:07:53.169 --> 00:07:54.719 align:start position:0% see okay okay so so now we can use it okay<00:07:53.500> so<00:07:53.560> this<00:07:53.770> is<00:07:53.949> already<00:07:54.280> enough<00:07:54.490> to<00:07:54.610> do 00:07:54.719 --> 00:07:54.729 align:start position:0% okay so this is already enough to do 00:07:54.729 --> 00:07:56.100 align:start position:0% okay so this is already enough to do some<00:07:54.880> cool<00:07:55.030> things<00:07:55.060> okay<00:07:55.690> this<00:07:55.870> is<00:07:55.960> already 00:07:56.100 --> 00:07:56.110 align:start position:0% some cool things okay this is already 00:07:56.110 --> 00:07:59.879 align:start position:0% some cool things okay this is already enough<00:07:56.349> to<00:07:56.979> do<00:07:57.750> to<00:07:58.750> make<00:07:58.900> a<00:07:58.930> mixer<00:07:59.349> okay<00:07:59.680> so 00:07:59.879 --> 00:07:59.889 align:start position:0% enough to do to make a mixer okay so 00:07:59.889 --> 00:08:01.140 align:start position:0% enough to do to make a mixer okay so this<00:08:00.280> is<00:08:00.430> what<00:08:00.580> it<00:08:00.699> makes<00:08:00.789> me<00:08:00.880> smart 00:08:01.140 --> 00:08:01.150 align:start position:0% this is what it makes me smart 00:08:01.150 --> 00:08:03.300 align:start position:0% this is what it makes me smart contractors<00:08:01.539> first<00:08:02.409> of<00:08:02.530> all<00:08:02.590> a<00:08:02.620> user<00:08:02.830> deposit 00:08:03.300 --> 00:08:03.310 align:start position:0% contractors first of all a user deposit 00:08:03.310 --> 00:08:06.029 align:start position:0% contractors first of all a user deposit and<00:08:03.669> either<00:08:03.909> into<00:08:04.150> the<00:08:04.180> contract<00:08:04.599> and<00:08:04.870> I<00:08:05.650> and 00:08:06.029 --> 00:08:06.039 align:start position:0% and either into the contract and I and 00:08:06.039 --> 00:08:07.740 align:start position:0% and either into the contract and I and then<00:08:06.219> the<00:08:06.310> contract<00:08:06.639> will<00:08:06.789> allow<00:08:07.000> them<00:08:07.240> to<00:08:07.270> add 00:08:07.740 --> 00:08:07.750 align:start position:0% then the contract will allow them to add 00:08:07.750 --> 00:08:11.779 align:start position:0% then the contract will allow them to add a<00:08:07.780> leaf<00:08:08.229> to<00:08:09.030> our<00:08:10.030> group<00:08:10.300> yeah 00:08:11.779 --> 00:08:11.789 align:start position:0% a leaf to our group yeah 00:08:11.789 --> 00:08:14.279 align:start position:0% a leaf to our group yeah then<00:08:12.789> a<00:08:12.820> user<00:08:13.120> can<00:08:13.300> use<00:08:13.360> a<00:08:13.449> snack<00:08:13.750> to<00:08:14.080> prove 00:08:14.279 --> 00:08:14.289 align:start position:0% then a user can use a snack to prove 00:08:14.289 --> 00:08:15.659 align:start position:0% then a user can use a snack to prove that<00:08:14.469> they<00:08:14.590> know<00:08:14.710> the<00:08:14.860> secret<00:08:15.070> information<00:08:15.340> of 00:08:15.659 --> 00:08:15.669 align:start position:0% that they know the secret information of 00:08:15.669 --> 00:08:19.830 align:start position:0% that they know the secret information of a<00:08:15.729> leaf<00:08:15.880> in<00:08:16.090> our<00:08:16.300> in<00:08:16.690> our<00:08:16.810> group<00:08:17.080> and<00:08:18.750> users<00:08:19.750> who 00:08:19.830 --> 00:08:19.840 align:start position:0% a leaf in our in our group and users who 00:08:19.840 --> 00:08:23.189 align:start position:0% a leaf in our in our group and users who prove<00:08:20.020> this<00:08:20.169> can<00:08:20.320> withdraw<00:08:20.500> coin<00:08:20.949> and<00:08:22.199> this 00:08:23.189 --> 00:08:23.199 align:start position:0% prove this can withdraw coin and this 00:08:23.199 --> 00:08:24.899 align:start position:0% prove this can withdraw coin and this this<00:08:23.560> work<00:08:23.830> and<00:08:24.009> because<00:08:24.340> the<00:08:24.580> only<00:08:24.639> thing 00:08:24.899 --> 00:08:24.909 align:start position:0% this work and because the only thing 00:08:24.909 --> 00:08:26.850 align:start position:0% this work and because the only thing that<00:08:25.060> we<00:08:25.150> reveal<00:08:25.539> in<00:08:25.719> the<00:08:25.780> previous<00:08:26.110> because 00:08:26.850 --> 00:08:26.860 align:start position:0% that we reveal in the previous because 00:08:26.860 --> 00:08:28.020 align:start position:0% that we reveal in the previous because the<00:08:26.919> only<00:08:27.039> thing<00:08:27.219> we<00:08:27.310> reveal<00:08:27.550> is<00:08:27.669> the<00:08:27.759> merkel 00:08:28.020 --> 00:08:28.030 align:start position:0% the only thing we reveal is the merkel 00:08:28.030 --> 00:08:30.300 align:start position:0% the only thing we reveal is the merkel root<00:08:28.180> there<00:08:29.110> is<00:08:29.199> no<00:08:29.349> way<00:08:29.530> for<00:08:29.560> anyone<00:08:29.949> to<00:08:30.159> know 00:08:30.300 --> 00:08:30.310 align:start position:0% root there is no way for anyone to know 00:08:30.310 --> 00:08:33.089 align:start position:0% root there is no way for anyone to know which<00:08:30.580> leaf<00:08:30.880> LED<00:08:31.449> to<00:08:31.659> which<00:08:31.839> withdrawal<00:08:32.260> but 00:08:33.089 --> 00:08:33.099 align:start position:0% which leaf LED to which withdrawal but 00:08:33.099 --> 00:08:34.750 align:start position:0% which leaf LED to which withdrawal but there's<00:08:33.279> a<00:08:33.370> problem<00:08:33.579> with<00:08:33.789> this 00:08:34.750 --> 00:08:34.760 align:start position:0% there's a problem with this 00:08:34.760 --> 00:08:37.210 align:start position:0% there's a problem with this so<00:08:35.270> does<00:08:36.110> anybody<00:08:36.350> know<00:08:36.530> what<00:08:36.590> the<00:08:36.680> problem<00:08:36.920> is 00:08:37.210 --> 00:08:37.220 align:start position:0% so does anybody know what the problem is 00:08:37.220 --> 00:08:41.830 align:start position:0% so does anybody know what the problem is yes<00:08:38.380> sorry<00:08:39.580> okay<00:08:40.610> yeah<00:08:41.210> that's<00:08:41.420> also<00:08:41.630> a 00:08:41.830 --> 00:08:41.840 align:start position:0% yes sorry okay yeah that's also a 00:08:41.840 --> 00:08:45.430 align:start position:0% yes sorry okay yeah that's also a problem<00:08:42.020> but<00:08:42.560> that's<00:08:42.710> not<00:08:42.890> the<00:08:43.010> one<00:08:44.440> that's 00:08:45.430 --> 00:08:45.440 align:start position:0% problem but that's not the one that's 00:08:45.440 --> 00:08:47.200 align:start position:0% problem but that's not the one that's not<00:08:45.590> the<00:08:45.710> one<00:08:45.860> that<00:08:45.980> I<00:08:46.070> contrived<00:08:46.460> to<00:08:46.490> talk 00:08:47.200 --> 00:08:47.210 align:start position:0% not the one that I contrived to talk 00:08:47.210 --> 00:08:48.090 align:start position:0% not the one that I contrived to talk about<00:08:47.360> next 00:08:48.090 --> 00:08:48.100 align:start position:0% about next 00:08:48.100 --> 00:08:50.590 align:start position:0% about next so<00:08:49.100> yeah<00:08:49.490> that's<00:08:49.730> definitely<00:08:49.850> a<00:08:50.090> problem<00:08:50.240> but 00:08:50.590 --> 00:08:50.600 align:start position:0% so yeah that's definitely a problem but 00:08:50.600 --> 00:08:51.850 align:start position:0% so yeah that's definitely a problem but the<00:08:50.810> way<00:08:50.930> that<00:08:51.050> we<00:08:51.170> solve<00:08:51.380> that<00:08:51.530> is<00:08:51.650> that<00:08:51.770> we 00:08:51.850 --> 00:08:51.860 align:start position:0% the way that we solve that is that we 00:08:51.860 --> 00:08:54.550 align:start position:0% the way that we solve that is that we limit<00:08:52.100> it<00:08:52.310> to<00:08:52.490> one<00:08:53.120> ether<00:08:53.630> per<00:08:53.870> deposit<00:08:54.410> and 00:08:54.550 --> 00:08:54.560 align:start position:0% limit it to one ether per deposit and 00:08:54.560 --> 00:08:57.220 align:start position:0% limit it to one ether per deposit and one<00:08:54.680> ether<00:08:54.890> Patrol<00:08:55.400> and<00:08:55.810> yeah<00:08:56.810> so<00:08:56.990> it<00:08:57.110> is<00:08:57.200> a 00:08:57.220 --> 00:08:57.230 align:start position:0% one ether Patrol and yeah so it is a 00:08:57.230 --> 00:08:59.500 align:start position:0% one ether Patrol and yeah so it is a problem<00:08:57.470> and<00:08:57.770> there's<00:08:58.130> wasted<00:08:58.550> six<00:08:59.060> atom<00:08:59.330> and 00:08:59.500 --> 00:08:59.510 align:start position:0% problem and there's wasted six atom and 00:08:59.510 --> 00:09:01.360 align:start position:0% problem and there's wasted six atom and we<00:08:59.630> can<00:08:59.750> talk<00:08:59.870> about<00:09:00.020> those<00:09:00.200> in<00:09:00.350> a<00:09:00.410> while<00:09:00.530> but 00:09:01.360 --> 00:09:01.370 align:start position:0% we can talk about those in a while but 00:09:01.370 --> 00:09:05.260 align:start position:0% we can talk about those in a while but has<00:09:01.730> anyone<00:09:02.000> another<00:09:02.570> a<00:09:02.660> problem<00:09:03.290> yes<00:09:04.270> yes 00:09:05.260 --> 00:09:05.270 align:start position:0% has anyone another a problem yes yes 00:09:05.270 --> 00:09:06.910 align:start position:0% has anyone another a problem yes yes exactly<00:09:05.510> you<00:09:05.930> can<00:09:06.050> do<00:09:06.140> a<00:09:06.170> double<00:09:06.320> spend<00:09:06.710> right 00:09:06.910 --> 00:09:06.920 align:start position:0% exactly you can do a double spend right 00:09:06.920 --> 00:09:09.040 align:start position:0% exactly you can do a double spend right because<00:09:07.580> nobody<00:09:07.940> because<00:09:08.390> you<00:09:08.720> just<00:09:08.900> proved 00:09:09.040 --> 00:09:09.050 align:start position:0% because nobody because you just proved 00:09:09.050 --> 00:09:11.020 align:start position:0% because nobody because you just proved you're<00:09:09.170> part<00:09:09.350> of<00:09:09.380> the<00:09:09.470> Merkel<00:09:09.740> route<00:09:09.890> yeah<00:09:10.790> and 00:09:11.020 --> 00:09:11.030 align:start position:0% you're part of the Merkel route yeah and 00:09:11.030 --> 00:09:12.460 align:start position:0% you're part of the Merkel route yeah and people<00:09:11.150> can<00:09:11.420> people<00:09:11.840> and<00:09:11.930> just<00:09:12.110> take<00:09:12.290> out 00:09:12.460 --> 00:09:12.470 align:start position:0% people can people and just take out 00:09:12.470 --> 00:09:14.380 align:start position:0% people can people and just take out coins<00:09:13.160> again<00:09:13.340> and<00:09:13.670> again<00:09:13.850> as<00:09:14.000> long<00:09:14.030> as<00:09:14.180> you're 00:09:14.380 --> 00:09:14.390 align:start position:0% coins again and again as long as you're 00:09:14.390 --> 00:09:17.500 align:start position:0% coins again and again as long as you're a<00:09:14.450> single<00:09:14.870> member<00:09:15.400> you<00:09:16.400> can<00:09:16.580> repeatedly<00:09:17.330> take 00:09:17.500 --> 00:09:17.510 align:start position:0% a single member you can repeatedly take 00:09:17.510 --> 00:09:19.180 align:start position:0% a single member you can repeatedly take money<00:09:17.720> out<00:09:17.900> because<00:09:18.230> there's<00:09:18.560> no<00:09:18.620> there's<00:09:18.920> no 00:09:19.180 --> 00:09:19.190 align:start position:0% money out because there's no there's no 00:09:19.190 --> 00:09:22.120 align:start position:0% money out because there's no there's no sort<00:09:19.550> of<00:09:19.580> there's<00:09:20.180> nothing<00:09:20.630> to<00:09:20.780> prevent<00:09:21.130> you 00:09:22.120 --> 00:09:22.130 align:start position:0% sort of there's nothing to prevent you 00:09:22.130 --> 00:09:23.740 align:start position:0% sort of there's nothing to prevent you from<00:09:22.160> from<00:09:22.550> double<00:09:22.910> spending<00:09:23.210> yeah<00:09:23.540> it's<00:09:23.690> the 00:09:23.740 --> 00:09:23.750 align:start position:0% from from double spending yeah it's the 00:09:23.750 --> 00:09:25.300 align:start position:0% from from double spending yeah it's the double<00:09:23.990> spend<00:09:24.170> problem<00:09:24.470> because<00:09:25.040> you<00:09:25.130> just 00:09:25.300 --> 00:09:25.310 align:start position:0% double spend problem because you just 00:09:25.310 --> 00:09:27.370 align:start position:0% double spend problem because you just don't<00:09:25.460> have<00:09:25.580> information<00:09:25.940> about<00:09:26.450> about<00:09:27.200> who 00:09:27.370 --> 00:09:27.380 align:start position:0% don't have information about about who 00:09:27.380 --> 00:09:32.440 align:start position:0% don't have information about about who was<00:09:27.530> withdrawn<00:09:27.860> previously<00:09:28.430> so<00:09:31.240> okay<00:09:32.240> how<00:09:32.390> do 00:09:32.440 --> 00:09:32.450 align:start position:0% was withdrawn previously so okay how do 00:09:32.450 --> 00:09:34.720 align:start position:0% was withdrawn previously so okay how do we<00:09:32.600> fix<00:09:32.780> this<00:09:32.930> problem<00:09:33.250> does<00:09:34.250> anyone<00:09:34.490> have<00:09:34.610> any 00:09:34.720 --> 00:09:34.730 align:start position:0% we fix this problem does anyone have any 00:09:34.730 --> 00:09:39.180 align:start position:0% we fix this problem does anyone have any ideas 00:09:39.180 --> 00:09:39.190 align:start position:0% 00:09:39.190 --> 00:09:44.460 align:start position:0% yes<00:09:40.190> sorry<00:09:41.180> I<00:09:41.210> didn't<00:09:41.390> hear<00:09:41.480> what<00:09:41.570> he<00:09:41.630> said 00:09:44.460 --> 00:09:44.470 align:start position:0% 00:09:44.470 --> 00:09:46.510 align:start position:0% yeah<00:09:45.470> that<00:09:45.500> would<00:09:45.770> kind<00:09:45.980> that<00:09:46.130> would<00:09:46.250> kind<00:09:46.460> of 00:09:46.510 --> 00:09:46.520 align:start position:0% yeah that would kind that would kind of 00:09:46.520 --> 00:09:48.970 align:start position:0% yeah that would kind that would kind of work<00:09:46.670> but<00:09:46.970> if<00:09:47.240> people<00:09:47.570> because<00:09:48.530> everyone<00:09:48.860> uses 00:09:48.970 --> 00:09:48.980 align:start position:0% work but if people because everyone uses 00:09:48.980 --> 00:09:51.220 align:start position:0% work but if people because everyone uses the<00:09:49.190> same<00:09:49.340> balance<00:09:49.790> it<00:09:50.480> doesn't<00:09:50.780> really<00:09:50.870> it 00:09:51.220 --> 00:09:51.230 align:start position:0% the same balance it doesn't really it 00:09:51.230 --> 00:09:52.630 align:start position:0% the same balance it doesn't really it doesn't<00:09:51.380> I<00:09:51.710> could<00:09:51.890> just<00:09:52.040> deposit<00:09:52.400> the<00:09:52.490> same 00:09:52.630 --> 00:09:52.640 align:start position:0% doesn't I could just deposit the same 00:09:52.640 --> 00:09:54.940 align:start position:0% doesn't I could just deposit the same balance<00:09:52.940> as<00:09:53.060> somebody<00:09:53.300> else<00:09:53.510> and<00:09:53.750> just<00:09:54.650> take<00:09:54.770> I 00:09:54.940 --> 00:09:54.950 align:start position:0% balance as somebody else and just take I 00:09:54.950 --> 00:09:56.530 align:start position:0% balance as somebody else and just take I could<00:09:55.100> take<00:09:55.250> all<00:09:55.370> let's<00:09:55.730> say<00:09:55.850> one<00:09:56.120> either<00:09:56.270> is<00:09:56.510> a 00:09:56.530 --> 00:09:56.540 align:start position:0% could take all let's say one either is a 00:09:56.540 --> 00:09:57.970 align:start position:0% could take all let's say one either is a popular<00:09:57.290> amount<00:09:57.530> I<00:09:57.590> could<00:09:57.740> just<00:09:57.860> take<00:09:57.920> one 00:09:57.970 --> 00:09:57.980 align:start position:0% popular amount I could just take one 00:09:57.980 --> 00:09:59.860 align:start position:0% popular amount I could just take one either<00:09:58.220> is<00:09:58.370> out<00:09:58.520> a<00:09:58.550> bunch<00:09:58.850> of<00:09:58.910> times<00:09:58.970> but<00:09:59.690> yeah 00:09:59.860 --> 00:09:59.870 align:start position:0% either is out a bunch of times but yeah 00:09:59.870 --> 00:10:02.440 align:start position:0% either is out a bunch of times but yeah probably<00:10:00.230> to<00:10:00.410> nullify<00:10:00.680> exactly<00:10:01.430> so<00:10:01.940> so<00:10:02.330> we 00:10:02.440 --> 00:10:02.450 align:start position:0% probably to nullify exactly so so we 00:10:02.450 --> 00:10:03.910 align:start position:0% probably to nullify exactly so so we kind<00:10:02.720> of<00:10:02.780> contrived<00:10:03.140> to<00:10:03.200> have<00:10:03.350> this<00:10:03.440> nullifier 00:10:03.910 --> 00:10:03.920 align:start position:0% kind of contrived to have this nullifier 00:10:03.920 --> 00:10:05.500 align:start position:0% kind of contrived to have this nullifier here<00:10:04.130> previously<00:10:04.700> as<00:10:04.880> part<00:10:05.120> of<00:10:05.150> the<00:10:05.240> public 00:10:05.500 --> 00:10:05.510 align:start position:0% here previously as part of the public 00:10:05.510 --> 00:10:06.970 align:start position:0% here previously as part of the public key<00:10:05.630> and<00:10:06.080> that's<00:10:06.290> why<00:10:06.380> I<00:10:06.410> didn't<00:10:06.710> just<00:10:06.740> call<00:10:06.950> a 00:10:06.970 --> 00:10:06.980 align:start position:0% key and that's why I didn't just call a 00:10:06.980 --> 00:10:09.550 align:start position:0% key and that's why I didn't just call a private<00:10:07.190> key<00:10:07.430> so<00:10:08.030> so<00:10:08.510> what<00:10:08.780> we<00:10:08.870> do<00:10:08.990> is<00:10:09.140> we<00:10:09.290> we 00:10:09.550 --> 00:10:09.560 align:start position:0% private key so so what we do is we we 00:10:09.560 --> 00:10:11.530 align:start position:0% private key so so what we do is we we publish<00:10:09.920> the<00:10:10.040> nullifier<00:10:10.460> yeah<00:10:11.090> we<00:10:11.300> make<00:10:11.450> that 00:10:11.530 --> 00:10:11.540 align:start position:0% publish the nullifier yeah we make that 00:10:11.540 --> 00:10:14.160 align:start position:0% publish the nullifier yeah we make that public<00:10:11.870> and<00:10:12.170> then<00:10:12.350> in<00:10:12.470> our<00:10:12.590> smart<00:10:12.860> contract<00:10:13.280> we 00:10:14.160 --> 00:10:14.170 align:start position:0% public and then in our smart contract we 00:10:14.170 --> 00:10:16.240 align:start position:0% public and then in our smart contract we remember<00:10:15.170> that<00:10:15.350> whenever<00:10:15.590> someone<00:10:15.920> uses<00:10:16.220> a 00:10:16.240 --> 00:10:16.250 align:start position:0% remember that whenever someone uses a 00:10:16.250 --> 00:10:18.010 align:start position:0% remember that whenever someone uses a certain<00:10:16.430> nullifier<00:10:16.910> we<00:10:17.360> remember<00:10:17.720> it<00:10:17.810> and 00:10:18.010 --> 00:10:18.020 align:start position:0% certain nullifier we remember it and 00:10:18.020 --> 00:10:19.810 align:start position:0% certain nullifier we remember it and then<00:10:18.470> we<00:10:18.590> prevent<00:10:18.890> people<00:10:19.040> from<00:10:19.160> withdrawing 00:10:19.810 --> 00:10:19.820 align:start position:0% then we prevent people from withdrawing 00:10:19.820 --> 00:10:22.450 align:start position:0% then we prevent people from withdrawing with<00:10:20.240> the<00:10:20.330> same<00:10:20.480> nullifier<00:10:20.870> twice<00:10:21.080> and<00:10:21.860> so 00:10:22.450 --> 00:10:22.460 align:start position:0% with the same nullifier twice and so 00:10:22.460 --> 00:10:23.740 align:start position:0% with the same nullifier twice and so this<00:10:22.580> actually<00:10:22.700> introduces<00:10:23.240> another<00:10:23.300> problem 00:10:23.740 --> 00:10:23.750 align:start position:0% this actually introduces another problem 00:10:23.750 --> 00:10:24.790 align:start position:0% this actually introduces another problem that<00:10:23.780> we<00:10:23.930> need<00:10:24.140> to<00:10:24.230> think<00:10:24.380> about<00:10:24.440> but<00:10:24.680> it's 00:10:24.790 --> 00:10:24.800 align:start position:0% that we need to think about but it's 00:10:24.800 --> 00:10:25.810 align:start position:0% that we need to think about but it's kind<00:10:24.950> of<00:10:24.980> outside<00:10:25.220> the<00:10:25.250> scope<00:10:25.430> of<00:10:25.550> the<00:10:25.640> talk 00:10:25.810 --> 00:10:25.820 align:start position:0% kind of outside the scope of the talk 00:10:25.820 --> 00:10:27.580 align:start position:0% kind of outside the scope of the talk but<00:10:26.450> but<00:10:26.660> the<00:10:26.750> problem<00:10:27.020> is<00:10:27.080> that<00:10:27.110> that<00:10:27.410> there's 00:10:27.580 --> 00:10:27.590 align:start position:0% but but the problem is that that there's 00:10:27.590 --> 00:10:29.140 align:start position:0% but but the problem is that that there's like<00:10:27.800> a<00:10:27.830> griefing<00:10:28.220> attack<00:10:28.490> here<00:10:28.730> that's 00:10:29.140 --> 00:10:29.150 align:start position:0% like a griefing attack here that's 00:10:29.150 --> 00:10:30.820 align:start position:0% like a griefing attack here that's someone<00:10:29.390> could<00:10:29.540> someone<00:10:30.020> could<00:10:30.260> see<00:10:30.530> that<00:10:30.740> I'm 00:10:30.820 --> 00:10:30.830 align:start position:0% someone could someone could see that I'm 00:10:30.830 --> 00:10:32.740 align:start position:0% someone could someone could see that I'm trying<00:10:30.980> to<00:10:31.100> withdraw<00:10:31.310> a<00:10:31.670> nullifier<00:10:32.270> X<00:10:32.510> and 00:10:32.740 --> 00:10:32.750 align:start position:0% trying to withdraw a nullifier X and 00:10:32.750 --> 00:10:35.260 align:start position:0% trying to withdraw a nullifier X and quickly<00:10:33.530> deposit<00:10:33.920> deposit<00:10:34.190> nullifier<00:10:34.970> X 00:10:35.260 --> 00:10:35.270 align:start position:0% quickly deposit deposit nullifier X 00:10:35.270 --> 00:10:37.090 align:start position:0% quickly deposit deposit nullifier X again<00:10:35.630> and<00:10:35.900> then<00:10:36.290> withdraw<00:10:36.440> that<00:10:36.560> and<00:10:36.860> then<00:10:36.950> my 00:10:37.090 --> 00:10:37.100 align:start position:0% again and then withdraw that and then my 00:10:37.100 --> 00:10:38.500 align:start position:0% again and then withdraw that and then my would<00:10:37.370> role<00:10:37.520> would<00:10:37.610> fail<00:10:37.790> but<00:10:38.210> this<00:10:38.360> is<00:10:38.480> a 00:10:38.500 --> 00:10:38.510 align:start position:0% would role would fail but this is a 00:10:38.510 --> 00:10:40.270 align:start position:0% would role would fail but this is a griefing<00:10:38.720> attack<00:10:38.990> and<00:10:39.200> it's<00:10:39.320> like<00:10:39.440> $1<00:10:39.770> for<00:10:39.980> $1 00:10:40.270 --> 00:10:40.280 align:start position:0% griefing attack and it's like $1 for $1 00:10:40.280 --> 00:10:41.770 align:start position:0% griefing attack and it's like $1 for $1 I<00:10:40.430> mean<00:10:40.640> it's<00:10:40.760> very<00:10:40.790> expensive<00:10:41.180> to<00:10:41.360> hurt 00:10:41.770 --> 00:10:41.780 align:start position:0% I mean it's very expensive to hurt 00:10:41.780 --> 00:10:43.120 align:start position:0% I mean it's very expensive to hurt people<00:10:42.050> with<00:10:42.170> it<00:10:42.290> but<00:10:42.800> yeah<00:10:42.920> it's<00:10:43.070> definitely 00:10:43.120 --> 00:10:43.130 align:start position:0% people with it but yeah it's definitely 00:10:43.130 --> 00:10:45.970 align:start position:0% people with it but yeah it's definitely problem<00:10:44.050> but<00:10:45.050> but<00:10:45.230> yeah<00:10:45.380> there's<00:10:45.560> ways<00:10:45.710> to<00:10:45.740> fix 00:10:45.970 --> 00:10:45.980 align:start position:0% problem but but yeah there's ways to fix 00:10:45.980 --> 00:10:47.060 align:start position:0% problem but but yeah there's ways to fix it<00:10:46.100> but<00:10:46.190> it's<00:10:46.340> kind<00:10:46.430> of<00:10:46.520> outside<00:10:46.730> the<00:10:46.820> scope 00:10:47.060 --> 00:10:47.070 align:start position:0% it but it's kind of outside the scope 00:10:47.070 --> 00:10:50.030 align:start position:0% it but it's kind of outside the scope what<00:10:47.940> we<00:10:48.030> only<00:10:48.150> talked<00:10:48.360> about<00:10:48.560> okay<00:10:49.560> so<00:10:49.590> now<00:10:49.980> we 00:10:50.030 --> 00:10:50.040 align:start position:0% what we only talked about okay so now we 00:10:50.040 --> 00:10:53.300 align:start position:0% what we only talked about okay so now we can<00:10:50.310> check<00:10:51.440> yeah<00:10:52.440> so<00:10:52.650> now<00:10:52.770> every<00:10:53.130> time<00:10:53.160> we 00:10:53.300 --> 00:10:53.310 align:start position:0% can check yeah so now every time we 00:10:53.310 --> 00:10:54.560 align:start position:0% can check yeah so now every time we withdraw<00:10:53.640> we<00:10:53.820> make<00:10:54.000> sure<00:10:54.120> that<00:10:54.150> that<00:10:54.300> coin 00:10:54.560 --> 00:10:54.570 align:start position:0% withdraw we make sure that that coin 00:10:54.570 --> 00:10:57.470 align:start position:0% withdraw we make sure that that coin hasn't<00:10:54.840> been<00:10:54.930> withdrawn<00:10:55.200> already<00:10:55.940> okay<00:10:56.940> so 00:10:57.470 --> 00:10:57.480 align:start position:0% hasn't been withdrawn already okay so 00:10:57.480 --> 00:10:58.580 align:start position:0% hasn't been withdrawn already okay so that's<00:10:57.660> how<00:10:57.750> makes<00:10:57.960> much<00:10:58.110> worse<00:10:58.260> I<00:10:58.410> mean 00:10:58.580 --> 00:10:58.590 align:start position:0% that's how makes much worse I mean 00:10:58.590 --> 00:11:00.380 align:start position:0% that's how makes much worse I mean that's<00:10:58.740> that's<00:10:58.980> that's<00:10:59.460> that's<00:10:59.730> exactly<00:10:59.940> what 00:11:00.380 --> 00:11:00.390 align:start position:0% that's that's that's that's exactly what 00:11:00.390 --> 00:11:03.620 align:start position:0% that's that's that's that's exactly what we<00:11:00.480> have<00:11:00.630> currently<00:11:00.900> in<00:11:01.170> the<00:11:01.260> github<00:11:02.570> okay<00:11:03.570> so 00:11:03.620 --> 00:11:03.630 align:start position:0% we have currently in the github okay so 00:11:03.630 --> 00:11:06.590 align:start position:0% we have currently in the github okay so we<00:11:04.020> have<00:11:04.170> some<00:11:04.380> problems<00:11:04.740> with<00:11:04.920> that<00:11:05.420> and<00:11:06.420> I'm 00:11:06.590 --> 00:11:06.600 align:start position:0% we have some problems with that and I'm 00:11:06.600 --> 00:11:09.320 align:start position:0% we have some problems with that and I'm one<00:11:07.230> of<00:11:07.320> the<00:11:07.380> major<00:11:07.530> problems<00:11:07.890> is<00:11:08.070> is<00:11:08.310> who<00:11:08.640> pays 00:11:09.320 --> 00:11:09.330 align:start position:0% one of the major problems is is who pays 00:11:09.330 --> 00:11:11.840 align:start position:0% one of the major problems is is who pays for<00:11:09.360> the<00:11:09.570> gas<00:11:09.750> right<00:11:10.740> so<00:11:11.130> the<00:11:11.250> thinking<00:11:11.730> is 00:11:11.840 --> 00:11:11.850 align:start position:0% for the gas right so the thinking is 00:11:11.850 --> 00:11:14.180 align:start position:0% for the gas right so the thinking is that<00:11:12.090> if<00:11:12.690> I<00:11:12.780> deposit<00:11:13.140> one<00:11:13.260> ether<00:11:13.560> and<00:11:13.770> then 00:11:14.180 --> 00:11:14.190 align:start position:0% that if I deposit one ether and then 00:11:14.190 --> 00:11:16.490 align:start position:0% that if I deposit one ether and then later<00:11:14.820> I<00:11:14.910> deposit<00:11:15.330> another<00:11:15.570> either<00:11:15.720> I<00:11:16.050> need<00:11:16.290> to 00:11:16.490 --> 00:11:16.500 align:start position:0% later I deposit another either I need to 00:11:16.500 --> 00:11:18.080 align:start position:0% later I deposit another either I need to have<00:11:16.620> gas<00:11:16.830> in<00:11:16.860> that<00:11:17.160> account<00:11:17.400> in<00:11:17.610> order<00:11:17.820> to<00:11:17.910> pay 00:11:18.080 --> 00:11:18.090 align:start position:0% have gas in that account in order to pay 00:11:18.090 --> 00:11:19.190 align:start position:0% have gas in that account in order to pay for<00:11:18.120> the<00:11:18.390> transaction<00:11:18.870> fee<00:11:18.960> of<00:11:19.110> the 00:11:19.190 --> 00:11:19.200 align:start position:0% for the transaction fee of the 00:11:19.200 --> 00:11:21.950 align:start position:0% for the transaction fee of the withdrawal<00:11:19.560> and<00:11:20.480> because<00:11:21.480> I<00:11:21.570> can't<00:11:21.720> do<00:11:21.810> that 00:11:21.950 --> 00:11:21.960 align:start position:0% withdrawal and because I can't do that 00:11:21.960 --> 00:11:23.840 align:start position:0% withdrawal and because I can't do that yeah<00:11:22.650> because<00:11:22.830> now<00:11:23.190> you<00:11:23.250> have<00:11:23.460> a<00:11:23.490> chicken<00:11:23.670> and 00:11:23.840 --> 00:11:23.850 align:start position:0% yeah because now you have a chicken and 00:11:23.850 --> 00:11:25.580 align:start position:0% yeah because now you have a chicken and egg<00:11:23.910> situation<00:11:24.240> it's<00:11:24.810> like<00:11:24.930> I<00:11:25.170> had<00:11:25.470> this 00:11:25.580 --> 00:11:25.590 align:start position:0% egg situation it's like I had this 00:11:25.590 --> 00:11:27.890 align:start position:0% egg situation it's like I had this anonymous<00:11:26.100> money<00:11:26.280> but<00:11:26.460> I<00:11:26.610> need<00:11:26.900> non-anonymous 00:11:27.890 --> 00:11:27.900 align:start position:0% anonymous money but I need non-anonymous 00:11:27.900 --> 00:11:30.230 align:start position:0% anonymous money but I need non-anonymous money<00:11:28.260> to<00:11:28.410> take<00:11:28.530> it<00:11:28.650> out<00:11:28.740> so<00:11:29.580> that<00:11:29.940> becomes<00:11:30.150> a 00:11:30.230 --> 00:11:30.240 align:start position:0% money to take it out so that becomes a 00:11:30.240 --> 00:11:34.250 align:start position:0% money to take it out so that becomes a problem<00:11:32.060> so<00:11:33.060> so<00:11:33.300> there's<00:11:33.840> a<00:11:33.900> way<00:11:33.990> to<00:11:34.020> solve 00:11:34.250 --> 00:11:34.260 align:start position:0% problem so so there's a way to solve 00:11:34.260 --> 00:11:35.240 align:start position:0% problem so so there's a way to solve that<00:11:34.320> I<00:11:34.440> don't<00:11:34.620> know<00:11:34.680> if<00:11:34.800> I<00:11:34.860> talked<00:11:35.010> about<00:11:35.040> that 00:11:35.240 --> 00:11:35.250 align:start position:0% that I don't know if I talked about that 00:11:35.250 --> 00:11:36.710 align:start position:0% that I don't know if I talked about that in<00:11:35.310> the<00:11:35.400> next<00:11:35.580> slide<00:11:35.670> or<00:11:35.850> not<00:11:35.970> no<00:11:36.360> so<00:11:36.510> the<00:11:36.630> way 00:11:36.710 --> 00:11:36.720 align:start position:0% in the next slide or not no so the way 00:11:36.720 --> 00:11:38.000 align:start position:0% in the next slide or not no so the way the<00:11:36.870> way<00:11:36.990> that<00:11:37.110> we<00:11:37.200> saw<00:11:37.320> that<00:11:37.500> is<00:11:37.620> we<00:11:37.770> do<00:11:37.860> like 00:11:38.000 --> 00:11:38.010 align:start position:0% the way that we saw that is we do like 00:11:38.010 --> 00:11:39.950 align:start position:0% the way that we saw that is we do like layer<00:11:38.220> two<00:11:38.430> transaction<00:11:38.910> abstraction<00:11:39.330> which 00:11:39.950 --> 00:11:39.960 align:start position:0% layer two transaction abstraction which 00:11:39.960 --> 00:11:41.120 align:start position:0% layer two transaction abstraction which is<00:11:40.110> oh<00:11:40.260> it's<00:11:40.500> actually<00:11:40.770> called<00:11:40.890> meta 00:11:41.120 --> 00:11:41.130 align:start position:0% is oh it's actually called meta 00:11:41.130 --> 00:11:42.670 align:start position:0% is oh it's actually called meta transactions<00:11:41.700> that's<00:11:41.820> the<00:11:41.940> new<00:11:42.030> name<00:11:42.300> for<00:11:42.480> it 00:11:42.670 --> 00:11:42.680 align:start position:0% transactions that's the new name for it 00:11:42.680 --> 00:11:44.840 align:start position:0% transactions that's the new name for it so<00:11:43.680> what<00:11:43.800> we<00:11:43.860> do<00:11:43.980> is<00:11:44.040> a<00:11:44.160> meta<00:11:44.340> transaction 00:11:44.840 --> 00:11:44.850 align:start position:0% so what we do is a meta transaction 00:11:44.850 --> 00:11:47.030 align:start position:0% so what we do is a meta transaction where<00:11:45.000> people<00:11:45.600> get<00:11:45.780> a<00:11:45.840> fee<00:11:46.050> for<00:11:46.380> broadcasting 00:11:47.030 --> 00:11:47.040 align:start position:0% where people get a fee for broadcasting 00:11:47.040 --> 00:11:48.590 align:start position:0% where people get a fee for broadcasting these<00:11:47.190> proofs<00:11:47.430> and<00:11:47.610> the<00:11:48.000> fee<00:11:48.150> is<00:11:48.390> like<00:11:48.570> a 00:11:48.590 --> 00:11:48.600 align:start position:0% these proofs and the fee is like a 00:11:48.600 --> 00:11:50.480 align:start position:0% these proofs and the fee is like a portion<00:11:49.140> of<00:11:49.230> the<00:11:49.500> amount<00:11:49.950> of<00:11:50.040> money<00:11:50.220> that<00:11:50.370> you 00:11:50.480 --> 00:11:50.490 align:start position:0% portion of the amount of money that you 00:11:50.490 --> 00:11:54.410 align:start position:0% portion of the amount of money that you deposited<00:11:52.040> okay<00:11:53.040> so<00:11:53.100> then<00:11:53.370> problem<00:11:54.240> number 00:11:54.410 --> 00:11:54.420 align:start position:0% deposited okay so then problem number 00:11:54.420 --> 00:11:55.790 align:start position:0% deposited okay so then problem number two<00:11:54.540> is<00:11:54.720> that<00:11:54.750> people<00:11:55.110> can<00:11:55.260> analyze<00:11:55.620> the 00:11:55.790 --> 00:11:55.800 align:start position:0% two is that people can analyze the 00:11:55.800 --> 00:11:57.920 align:start position:0% two is that people can analyze the inputs<00:11:56.070> and<00:11:56.130> the<00:11:56.190> outputs<00:11:56.570> to<00:11:57.570> track<00:11:57.780> the 00:11:57.920 --> 00:11:57.930 align:start position:0% inputs and the outputs to track the 00:11:57.930 --> 00:12:01.520 align:start position:0% inputs and the outputs to track the users<00:11:58.430> yeah<00:11:59.430> and<00:12:00.360> so<00:12:00.870> this<00:12:01.020> is<00:12:01.140> more<00:12:01.350> like<00:12:01.410> a 00:12:01.520 --> 00:12:01.530 align:start position:0% users yeah and so this is more like a 00:12:01.530 --> 00:12:03.110 align:start position:0% users yeah and so this is more like a temporal<00:12:02.070> attack<00:12:02.340> and<00:12:02.550> you<00:12:02.700> can<00:12:02.850> use<00:12:03.000> these 00:12:03.110 --> 00:12:03.120 align:start position:0% temporal attack and you can use these 00:12:03.120 --> 00:12:05.270 align:start position:0% temporal attack and you can use these heuristics<00:12:03.390> to<00:12:03.840> let's<00:12:04.590> say<00:12:04.740> that<00:12:04.890> let's<00:12:05.160> say 00:12:05.270 --> 00:12:05.280 align:start position:0% heuristics to let's say that let's say 00:12:05.280 --> 00:12:07.040 align:start position:0% heuristics to let's say that let's say that<00:12:05.430> I<00:12:05.670> deposit<00:12:06.180> one<00:12:06.270> either<00:12:06.480> into<00:12:06.690> the<00:12:06.720> smart 00:12:07.040 --> 00:12:07.050 align:start position:0% that I deposit one either into the smart 00:12:07.050 --> 00:12:09.200 align:start position:0% that I deposit one either into the smart contract<00:12:07.380> and<00:12:07.560> then<00:12:08.040> I<00:12:08.400> would<00:12:08.850> throw<00:12:08.910> that<00:12:09.060> one 00:12:09.200 --> 00:12:09.210 align:start position:0% contract and then I would throw that one 00:12:09.210 --> 00:12:10.640 align:start position:0% contract and then I would throw that one either<00:12:09.360> in<00:12:09.540> the<00:12:09.630> next<00:12:09.840> block<00:12:10.020> I<00:12:10.260> mean<00:12:10.530> it's 00:12:10.640 --> 00:12:10.650 align:start position:0% either in the next block I mean it's 00:12:10.650 --> 00:12:13.340 align:start position:0% either in the next block I mean it's very<00:12:10.710> obvious<00:12:11.250> that<00:12:11.840> it's<00:12:12.840> kind<00:12:13.140> of<00:12:13.200> obvious 00:12:13.340 --> 00:12:13.350 align:start position:0% very obvious that it's kind of obvious 00:12:13.350 --> 00:12:16.190 align:start position:0% very obvious that it's kind of obvious who<00:12:13.790> deposited<00:12:14.790> yeah<00:12:15.450> I<00:12:15.480> mean<00:12:15.870> you<00:12:15.960> can't 00:12:16.190 --> 00:12:16.200 align:start position:0% who deposited yeah I mean you can't 00:12:16.200 --> 00:12:17.870 align:start position:0% who deposited yeah I mean you can't connect<00:12:16.740> them<00:12:16.860> cryptographically<00:12:17.370> but<00:12:17.790> you 00:12:17.870 --> 00:12:17.880 align:start position:0% connect them cryptographically but you 00:12:17.880 --> 00:12:18.920 align:start position:0% connect them cryptographically but you can<00:12:18.030> come<00:12:18.150> up<00:12:18.210> with<00:12:18.270> these<00:12:18.480> sort<00:12:18.690> of<00:12:18.750> clever 00:12:18.920 --> 00:12:18.930 align:start position:0% can come up with these sort of clever 00:12:18.930 --> 00:12:21.350 align:start position:0% can come up with these sort of clever heuristics<00:12:19.560> about<00:12:19.830> about<00:12:20.460> how<00:12:20.640> much<00:12:21.030> you<00:12:21.180> can 00:12:21.350 --> 00:12:21.360 align:start position:0% heuristics about about how much you can 00:12:21.360 --> 00:12:22.940 align:start position:0% heuristics about about how much you can how<00:12:21.990> much<00:12:22.110> you<00:12:22.230> can<00:12:22.320> take<00:12:22.500> in<00:12:22.590> and<00:12:22.740> take<00:12:22.830> out 00:12:22.940 --> 00:12:22.950 align:start position:0% how much you can take in and take out 00:12:22.950 --> 00:12:25.010 align:start position:0% how much you can take in and take out and<00:12:23.160> that's<00:12:24.060> part<00:12:24.390> of<00:12:24.420> the<00:12:24.540> reason<00:12:24.840> why<00:12:24.990> I 00:12:25.010 --> 00:12:25.020 align:start position:0% and that's part of the reason why I 00:12:25.020 --> 00:12:26.930 align:start position:0% and that's part of the reason why I prevented<00:12:25.860> the<00:12:25.950> having<00:12:26.220> multiple<00:12:26.550> amounts 00:12:26.930 --> 00:12:26.940 align:start position:0% prevented the having multiple amounts 00:12:26.940 --> 00:12:29.690 align:start position:0% prevented the having multiple amounts because<00:12:28.010> because<00:12:29.010> if<00:12:29.130> you<00:12:29.220> have<00:12:29.370> multiple 00:12:29.690 --> 00:12:29.700 align:start position:0% because because if you have multiple 00:12:29.700 --> 00:12:31.580 align:start position:0% because because if you have multiple amounts<00:12:30.120> the<00:12:30.570> amount<00:12:30.960> that<00:12:31.080> you<00:12:31.230> would<00:12:31.380> draw 00:12:31.580 --> 00:12:31.590 align:start position:0% amounts the amount that you would draw 00:12:31.590 --> 00:12:33.860 align:start position:0% amounts the amount that you would draw is<00:12:31.860> also<00:12:32.220> an<00:12:32.370> indicator<00:12:32.880> of<00:12:33.090> who<00:12:33.330> deposited 00:12:33.860 --> 00:12:33.870 align:start position:0% is also an indicator of who deposited 00:12:33.870 --> 00:12:35.630 align:start position:0% is also an indicator of who deposited yeah<00:12:34.470> and<00:12:34.620> let's<00:12:34.950> say<00:12:35.070> that<00:12:35.190> I've<00:12:35.310> deposited 00:12:35.630 --> 00:12:35.640 align:start position:0% yeah and let's say that I've deposited 00:12:35.640 --> 00:12:38.060 align:start position:0% yeah and let's say that I've deposited one<00:12:36.030> point<00:12:36.240> one<00:12:36.420> five<00:12:36.660> six<00:12:36.930> seven<00:12:37.320> either<00:12:37.740> and 00:12:38.060 --> 00:12:38.070 align:start position:0% one point one five six seven either and 00:12:38.070 --> 00:12:40.190 align:start position:0% one point one five six seven either and then<00:12:38.580> someone<00:12:38.970> later<00:12:39.120> withdrew<00:12:39.750> one<00:12:39.990> point 00:12:40.190 --> 00:12:40.200 align:start position:0% then someone later withdrew one point 00:12:40.200 --> 00:12:41.750 align:start position:0% then someone later withdrew one point five<00:12:40.380> six<00:12:40.590> seven<00:12:40.800> either<00:12:41.040> it's<00:12:41.310> a<00:12:41.400> good<00:12:41.550> bet 00:12:41.750 --> 00:12:41.760 align:start position:0% five six seven either it's a good bet 00:12:41.760 --> 00:12:44.000 align:start position:0% five six seven either it's a good bet that<00:12:41.790> it<00:12:42.060> was<00:12:42.210> me<00:12:42.390> it<00:12:43.080> was<00:12:43.140> my<00:12:43.380> withdrawal<00:12:43.770> I 00:12:44.000 --> 00:12:44.010 align:start position:0% that it was me it was my withdrawal I 00:12:44.010 --> 00:12:46.070 align:start position:0% that it was me it was my withdrawal I mean<00:12:44.490> what<00:12:44.790> we<00:12:44.880> want<00:12:45.030> to<00:12:45.120> do<00:12:45.240> is<00:12:45.390> maximize<00:12:45.630> our 00:12:46.070 --> 00:12:46.080 align:start position:0% mean what we want to do is maximize our 00:12:46.080 --> 00:12:51.260 align:start position:0% mean what we want to do is maximize our privacy<00:12:46.410> set<00:12:46.710> so<00:12:49.520> yeah<00:12:50.520> so<00:12:50.730> that's<00:12:50.910> that's 00:12:51.260 --> 00:12:51.270 align:start position:0% privacy set so yeah so that's that's 00:12:51.270 --> 00:12:52.850 align:start position:0% privacy set so yeah so that's that's know<00:12:51.690> there's<00:12:51.870> some<00:12:51.990> thoughts<00:12:52.170> on<00:12:52.320> that<00:12:52.440> so<00:12:52.740> we 00:12:52.850 --> 00:12:52.860 align:start position:0% know there's some thoughts on that so we 00:12:52.860 --> 00:12:54.230 align:start position:0% know there's some thoughts on that so we have<00:12:53.160> a<00:12:53.190> proposal<00:12:53.520> for<00:12:53.790> the<00:12:53.850> layer<00:12:54.060> two 00:12:54.230 --> 00:12:54.240 align:start position:0% have a proposal for the layer two 00:12:54.240 --> 00:12:56.540 align:start position:0% have a proposal for the layer two transaction<00:12:54.900> abstraction<00:12:55.290> and<00:12:55.550> hopefully 00:12:56.540 --> 00:12:56.550 align:start position:0% transaction abstraction and hopefully 00:12:56.550 --> 00:12:57.650 align:start position:0% transaction abstraction and hopefully we'll<00:12:56.700> be<00:12:56.730> able<00:12:56.880> to<00:12:57.000> sort<00:12:57.210> of<00:12:57.270> merge<00:12:57.450> it<00:12:57.630> with 00:12:57.650 --> 00:12:57.660 align:start position:0% we'll be able to sort of merge it with 00:12:57.660 --> 00:12:59.470 align:start position:0% we'll be able to sort of merge it with with<00:12:58.020> someone<00:12:58.320> else's 00:12:59.470 --> 00:12:59.480 align:start position:0% with someone else's 00:12:59.480 --> 00:13:01.960 align:start position:0% with someone else's but<00:13:00.199> anyone<00:13:00.440> that's<00:13:00.860> kind<00:13:01.070> of<00:13:01.160> future<00:13:01.790> work 00:13:01.960 --> 00:13:01.970 align:start position:0% but anyone that's kind of future work 00:13:01.970 --> 00:13:08.530 align:start position:0% but anyone that's kind of future work that<00:13:02.209> needs<00:13:02.360> to<00:13:02.389> be<00:13:02.480> known<00:13:05.769> okay<00:13:07.269> so<00:13:08.269> can<00:13:08.480> we 00:13:08.530 --> 00:13:08.540 align:start position:0% that needs to be known okay so can we 00:13:08.540 --> 00:13:10.090 align:start position:0% that needs to be known okay so can we allow<00:13:08.839> multiple<00:13:09.110> deposited<00:13:09.649> sizes<00:13:09.949> and 00:13:10.090 --> 00:13:10.100 align:start position:0% allow multiple deposited sizes and 00:13:10.100 --> 00:13:12.189 align:start position:0% allow multiple deposited sizes and that's<00:13:10.250> kind<00:13:10.490> of<00:13:10.579> that's<00:13:10.970> kind<00:13:11.209> of<00:13:11.240> whatever 00:13:12.189 --> 00:13:12.199 align:start position:0% that's kind of that's kind of whatever 00:13:12.199 --> 00:13:14.769 align:start position:0% that's kind of that's kind of whatever address<00:13:12.440> and<00:13:13.160> yeah<00:13:13.430> it's<00:13:13.790> also<00:13:13.910> trivial<00:13:14.360> to<00:13:14.510> to 00:13:14.769 --> 00:13:14.779 align:start position:0% address and yeah it's also trivial to to 00:13:14.779 --> 00:13:16.689 align:start position:0% address and yeah it's also trivial to to allow<00:13:15.290> here<00:13:15.560> C<00:13:15.740> 2012<00:13:16.160> in<00:13:16.250> deposits<00:13:16.639> and 00:13:16.689 --> 00:13:16.699 align:start position:0% allow here C 2012 in deposits and 00:13:16.699 --> 00:13:18.939 align:start position:0% allow here C 2012 in deposits and withdrawals<00:13:17.380> but<00:13:18.380> we<00:13:18.500> need<00:13:18.620> to<00:13:18.709> be<00:13:18.800> careful 00:13:18.939 --> 00:13:18.949 align:start position:0% withdrawals but we need to be careful 00:13:18.949 --> 00:13:21.759 align:start position:0% withdrawals but we need to be careful about<00:13:19.130> the<00:13:19.279> privacy<00:13:19.579> set<00:13:19.820> again<00:13:20.560> if<00:13:21.560> these 00:13:21.759 --> 00:13:21.769 align:start position:0% about the privacy set again if these 00:13:21.769 --> 00:13:24.579 align:start position:0% about the privacy set again if these tokens<00:13:22.459> have<00:13:22.610> sort<00:13:22.880> of<00:13:22.910> low<00:13:23.149> volume<00:13:23.690> then<00:13:24.410> it's 00:13:24.579 --> 00:13:24.589 align:start position:0% tokens have sort of low volume then it's 00:13:24.589 --> 00:13:27.129 align:start position:0% tokens have sort of low volume then it's unlikely<00:13:24.889> that<00:13:25.160> people<00:13:25.220> will<00:13:25.579> be<00:13:25.699> able<00:13:25.820> to<00:13:26.139> get 00:13:27.129 --> 00:13:27.139 align:start position:0% unlikely that people will be able to get 00:13:27.139 --> 00:13:28.930 align:start position:0% unlikely that people will be able to get these<00:13:27.320> if<00:13:27.560> these<00:13:27.740> these<00:13:28.399> transactions<00:13:28.820> have 00:13:28.930 --> 00:13:28.940 align:start position:0% these if these these transactions have 00:13:28.940 --> 00:13:30.550 align:start position:0% these if these these transactions have low<00:13:29.029> value<00:13:29.360> but<00:13:29.389> it'll<00:13:29.720> be<00:13:29.810> unlikely<00:13:30.440> that 00:13:30.550 --> 00:13:30.560 align:start position:0% low value but it'll be unlikely that 00:13:30.560 --> 00:13:33.009 align:start position:0% low value but it'll be unlikely that people<00:13:31.209> yeah<00:13:32.209> I<00:13:32.240> mean<00:13:32.540> people<00:13:32.720> might<00:13:32.959> think 00:13:33.009 --> 00:13:33.019 align:start position:0% people yeah I mean people might think 00:13:33.019 --> 00:13:34.720 align:start position:0% people yeah I mean people might think that<00:13:33.199> this<00:13:33.410> is<00:13:33.529> really<00:13:33.680> super<00:13:34.100> private<00:13:34.370> annum 00:13:34.720 --> 00:13:34.730 align:start position:0% that this is really super private annum 00:13:34.730 --> 00:13:36.009 align:start position:0% that this is really super private annum and<00:13:34.910> it<00:13:35.060> might<00:13:35.209> not<00:13:35.329> be<00:13:35.449> I<00:13:35.630> mean<00:13:35.839> it's<00:13:35.959> just 00:13:36.009 --> 00:13:36.019 align:start position:0% and it might not be I mean it's just 00:13:36.019 --> 00:13:38.860 align:start position:0% and it might not be I mean it's just something<00:13:36.320> to<00:13:36.410> be<00:13:36.500> aware<00:13:36.529> of<00:13:36.769> when<00:13:37.070> when<00:13:37.870> about 00:13:38.860 --> 00:13:38.870 align:start position:0% something to be aware of when when about 00:13:38.870 --> 00:13:42.189 align:start position:0% something to be aware of when when about these<00:13:39.019> things<00:13:39.199> because<00:13:39.889> yeah<00:13:40.220> okay<00:13:40.699> and<00:13:41.199> then 00:13:42.189 --> 00:13:42.199 align:start position:0% these things because yeah okay and then 00:13:42.199 --> 00:13:44.139 align:start position:0% these things because yeah okay and then there's<00:13:42.410> like<00:13:42.620> other<00:13:43.040> kind<00:13:43.550> of<00:13:43.670> further 00:13:44.139 --> 00:13:44.149 align:start position:0% there's like other kind of further 00:13:44.149 --> 00:13:46.480 align:start position:0% there's like other kind of further research<00:13:44.750> questions<00:13:45.350> about<00:13:45.680> how<00:13:45.860> can<00:13:45.889> we<00:13:46.220> can 00:13:46.480 --> 00:13:46.490 align:start position:0% research questions about how can we can 00:13:46.490 --> 00:13:48.910 align:start position:0% research questions about how can we can we<00:13:46.690> increase<00:13:47.690> the<00:13:47.930> size<00:13:48.139> of<00:13:48.199> our<00:13:48.290> privacy<00:13:48.620> set 00:13:48.910 --> 00:13:48.920 align:start position:0% we increase the size of our privacy set 00:13:48.920 --> 00:13:50.680 align:start position:0% we increase the size of our privacy set by<00:13:49.070> being<00:13:49.370> able<00:13:49.459> to<00:13:49.639> trade<00:13:49.880> from<00:13:50.060> one<00:13:50.269> currency 00:13:50.680 --> 00:13:50.690 align:start position:0% by being able to trade from one currency 00:13:50.690 --> 00:13:53.230 align:start position:0% by being able to trade from one currency to<00:13:50.839> another<00:13:51.459> privately<00:13:52.459> and<00:13:52.699> that<00:13:53.089> would<00:13:53.209> that 00:13:53.230 --> 00:13:53.240 align:start position:0% to another privately and that would that 00:13:53.240 --> 00:13:54.579 align:start position:0% to another privately and that would that would<00:13:53.570> be<00:13:53.600> kind<00:13:53.839> of<00:13:53.899> cool<00:13:54.050> I<00:13:54.079> mean<00:13:54.290> that<00:13:54.470> would 00:13:54.579 --> 00:13:54.589 align:start position:0% would be kind of cool I mean that would 00:13:54.589 --> 00:13:56.530 align:start position:0% would be kind of cool I mean that would that<00:13:54.860> would<00:13:54.920> sort<00:13:55.279> of<00:13:55.370> marriage<00:13:56.329> are 00:13:56.530 --> 00:13:56.540 align:start position:0% that would sort of marriage are 00:13:56.540 --> 00:13:58.660 align:start position:0% that would sort of marriage are separated<00:13:57.290> here<00:13:57.470> see<00:13:57.649> 20<00:13:57.920> tokens<00:13:58.220> into<00:13:58.430> a<00:13:58.459> way 00:13:58.660 --> 00:13:58.670 align:start position:0% separated here see 20 tokens into a way 00:13:58.670 --> 00:14:00.819 align:start position:0% separated here see 20 tokens into a way that<00:13:58.699> that<00:13:59.540> we<00:13:59.660> could<00:13:59.839> into<00:14:00.440> something<00:14:00.800> that 00:14:00.819 --> 00:14:00.829 align:start position:0% that that we could into something that 00:14:00.829 --> 00:14:02.710 align:start position:0% that that we could into something that makes<00:14:01.160> a<00:14:01.220> little<00:14:01.339> bit<00:14:01.519> that<00:14:02.089> has<00:14:02.269> stronger 00:14:02.710 --> 00:14:02.720 align:start position:0% makes a little bit that has stronger 00:14:02.720 --> 00:14:04.449 align:start position:0% makes a little bit that has stronger anonymity<00:14:03.110> properties<00:14:03.589> but<00:14:03.949> that<00:14:04.069> that<00:14:04.190> seems 00:14:04.449 --> 00:14:04.459 align:start position:0% anonymity properties but that that seems 00:14:04.459 --> 00:14:07.470 align:start position:0% anonymity properties but that that seems that<00:14:04.579> seems<00:14:04.910> to<00:14:05.209> be<00:14:05.300> a<00:14:05.560> difficult<00:14:06.560> thing<00:14:06.589> to<00:14:06.680> do 00:14:07.470 --> 00:14:07.480 align:start position:0% that seems to be a difficult thing to do 00:14:07.480 --> 00:14:10.059 align:start position:0% that seems to be a difficult thing to do but<00:14:08.480> we<00:14:08.779> can<00:14:08.899> see<00:14:09.019> that<00:14:09.050> that<00:14:09.350> sort<00:14:09.529> of<00:14:09.620> future 00:14:10.059 --> 00:14:10.069 align:start position:0% but we can see that that sort of future 00:14:10.069 --> 00:14:14.139 align:start position:0% but we can see that that sort of future future<00:14:10.490> work<00:14:10.699> okay<00:14:11.630> so<00:14:11.800> so<00:14:12.800> basically<00:14:13.149> so 00:14:14.139 --> 00:14:14.149 align:start position:0% future work okay so so basically so 00:14:14.149 --> 00:14:16.090 align:start position:0% future work okay so so basically so that's<00:14:14.360> the<00:14:14.540> end<00:14:14.660> of<00:14:14.690> mix<00:14:14.899> Emes<00:14:15.110> okay<00:14:15.560> so<00:14:15.620> so 00:14:16.090 --> 00:14:16.100 align:start position:0% that's the end of mix Emes okay so so 00:14:16.100 --> 00:14:18.009 align:start position:0% that's the end of mix Emes okay so so that's<00:14:16.550> that's<00:14:16.850> that's<00:14:17.300> all<00:14:17.449> I<00:14:17.480> really<00:14:17.839> have 00:14:18.009 --> 00:14:18.019 align:start position:0% that's that's that's all I really have 00:14:18.019 --> 00:14:19.750 align:start position:0% that's that's that's all I really have to<00:14:18.110> say<00:14:18.199> about<00:14:18.290> mix<00:14:18.500> mix<00:14:18.680> for<00:14:18.800> now<00:14:18.889> so<00:14:19.579> it's<00:14:19.699> a 00:14:19.750 --> 00:14:19.760 align:start position:0% to say about mix mix for now so it's a 00:14:19.760 --> 00:14:23.610 align:start position:0% to say about mix mix for now so it's a general<00:14:19.970> token<00:14:20.480> mixer<00:14:21.010> that<00:14:22.010> you<00:14:22.399> can<00:14:22.550> use<00:14:22.670> to 00:14:23.610 --> 00:14:23.620 align:start position:0% general token mixer that you can use to 00:14:23.620 --> 00:14:26.439 align:start position:0% general token mixer that you can use to mix<00:14:24.620> your<00:14:24.740> ether<00:14:25.010> or<00:14:25.130> your<00:14:25.250> tokens<00:14:25.550> so<00:14:26.120> this<00:14:26.300> is 00:14:26.439 --> 00:14:26.449 align:start position:0% mix your ether or your tokens so this is 00:14:26.449 --> 00:14:28.870 align:start position:0% mix your ether or your tokens so this is this<00:14:26.690> is<00:14:26.899> this<00:14:27.110> is<00:14:27.709> like<00:14:27.920> cool<00:14:28.370> it's<00:14:28.519> nice<00:14:28.670> work 00:14:28.870 --> 00:14:28.880 align:start position:0% this is this is like cool it's nice work 00:14:28.880 --> 00:14:30.759 align:start position:0% this is this is like cool it's nice work but<00:14:29.060> it's<00:14:29.180> a<00:14:29.269> little<00:14:29.360> bit<00:14:29.480> it's<00:14:30.410> not<00:14:30.500> really 00:14:30.759 --> 00:14:30.769 align:start position:0% but it's a little bit it's not really 00:14:30.769 --> 00:14:35.920 align:start position:0% but it's a little bit it's not really very<00:14:33.910> it's<00:14:34.910> very<00:14:35.000> similar<00:14:35.329> to<00:14:35.449> see<00:14:35.660> caches 00:14:35.920 --> 00:14:35.930 align:start position:0% very it's very similar to see caches 00:14:35.930 --> 00:14:37.059 align:start position:0% very it's very similar to see caches work<00:14:36.079> and<00:14:36.290> I<00:14:36.350> mean<00:14:36.500> it's<00:14:36.649> similar<00:14:36.860> to<00:14:36.980> things 00:14:37.059 --> 00:14:37.069 align:start position:0% work and I mean it's similar to things 00:14:37.069 --> 00:14:38.230 align:start position:0% work and I mean it's similar to things that<00:14:37.160> already<00:14:37.339> exist<00:14:37.459> I<00:14:37.880> mean<00:14:38.029> they<00:14:38.149> don't 00:14:38.230 --> 00:14:38.240 align:start position:0% that already exist I mean they don't 00:14:38.240 --> 00:14:39.730 align:start position:0% that already exist I mean they don't exist<00:14:38.510> in<00:14:38.600> material<00:14:39.019> but<00:14:39.139> it's<00:14:39.260> like<00:14:39.440> work 00:14:39.730 --> 00:14:39.740 align:start position:0% exist in material but it's like work 00:14:39.740 --> 00:14:41.439 align:start position:0% exist in material but it's like work that's<00:14:39.889> been<00:14:39.980> done<00:14:40.040> before<00:14:40.430> and<00:14:40.610> it's<00:14:41.240> cool 00:14:41.439 --> 00:14:41.449 align:start position:0% that's been done before and it's cool 00:14:41.449 --> 00:14:42.730 align:start position:0% that's been done before and it's cool but<00:14:41.600> I<00:14:41.810> would<00:14:41.990> sort<00:14:42.139> of<00:14:42.170> search<00:14:42.350> for<00:14:42.620> other 00:14:42.730 --> 00:14:42.740 align:start position:0% but I would sort of search for other 00:14:42.740 --> 00:14:45.040 align:start position:0% but I would sort of search for other ways<00:14:42.949> to<00:14:43.010> use<00:14:43.370> snacks<00:14:43.639> to<00:14:43.790> do<00:14:43.910> other<00:14:44.060> things<00:14:44.329> so 00:14:45.040 --> 00:14:45.050 align:start position:0% ways to use snacks to do other things so 00:14:45.050 --> 00:14:46.930 align:start position:0% ways to use snacks to do other things so the<00:14:45.560> thing<00:14:46.250> that<00:14:46.279> I'm<00:14:46.490> actually<00:14:46.699> more 00:14:46.930 --> 00:14:46.940 align:start position:0% the thing that I'm actually more 00:14:46.940 --> 00:14:48.460 align:start position:0% the thing that I'm actually more interested<00:14:47.389> in<00:14:47.480> is<00:14:47.630> is<00:14:47.779> something<00:14:48.019> called 00:14:48.460 --> 00:14:48.470 align:start position:0% interested in is is something called 00:14:48.470 --> 00:14:50.680 align:start position:0% interested in is is something called semaphore<00:14:48.920> which<00:14:49.370> is<00:14:49.639> which<00:14:50.060> is<00:14:50.089> very<00:14:50.269> very 00:14:50.680 --> 00:14:50.690 align:start position:0% semaphore which is which is very very 00:14:50.690 --> 00:14:54.960 align:start position:0% semaphore which is which is very very similar<00:14:51.019> to<00:14:51.940> to<00:14:52.940> mix<00:14:53.209> mess<00:14:53.449> so<00:14:53.870> so<00:14:54.199> instead<00:14:54.560> of 00:14:54.960 --> 00:14:54.970 align:start position:0% similar to to mix mess so so instead of 00:14:54.970 --> 00:14:57.699 align:start position:0% similar to to mix mess so so instead of instead<00:14:55.970> of<00:14:56.089> depositing<00:14:56.329> one<00:14:56.839> either<00:14:57.470> and 00:14:57.699 --> 00:14:57.709 align:start position:0% instead of depositing one either and 00:14:57.709 --> 00:15:00.490 align:start position:0% instead of depositing one either and being<00:14:58.069> allowed<00:14:58.279> to<00:14:58.430> join<00:14:58.550> the<00:14:58.730> tree<00:14:58.910> we<00:14:59.720> come 00:15:00.490 --> 00:15:00.500 align:start position:0% being allowed to join the tree we come 00:15:00.500 --> 00:15:01.990 align:start position:0% being allowed to join the tree we come up<00:15:00.620> with<00:15:00.740> some<00:15:00.980> other<00:15:01.100> rule<00:15:01.399> that<00:15:01.699> lets<00:15:01.880> people 00:15:01.990 --> 00:15:02.000 align:start position:0% up with some other rule that lets people 00:15:02.000 --> 00:15:04.809 align:start position:0% up with some other rule that lets people join<00:15:02.300> the<00:15:02.449> tree<00:15:02.660> yeah<00:15:03.319> we<00:15:03.589> could<00:15:03.740> have<00:15:03.769> like<00:15:04.220> a 00:15:04.809 --> 00:15:04.819 align:start position:0% join the tree yeah we could have like a 00:15:04.819 --> 00:15:07.180 align:start position:0% join the tree yeah we could have like a sign-in<00:15:05.630> with<00:15:05.810> github<00:15:06.260> button<00:15:06.740> and<00:15:06.949> people 00:15:07.180 --> 00:15:07.190 align:start position:0% sign-in with github button and people 00:15:07.190 --> 00:15:09.220 align:start position:0% sign-in with github button and people who<00:15:07.250> sign<00:15:07.430> in<00:15:07.550> with<00:15:07.670> github<00:15:07.819> are<00:15:08.120> able<00:15:08.390> to<00:15:08.569> are 00:15:09.220 --> 00:15:09.230 align:start position:0% who sign in with github are able to are 00:15:09.230 --> 00:15:12.199 align:start position:0% who sign in with github are able to are able<00:15:09.529> to<00:15:09.740> join<00:15:10.250> this<00:15:10.459> Merkel<00:15:10.880> tree<00:15:11.060> and 00:15:12.199 --> 00:15:12.209 align:start position:0% able to join this Merkel tree and 00:15:12.209 --> 00:15:13.639 align:start position:0% able to join this Merkel tree and and<00:15:12.300> then<00:15:12.869> they<00:15:12.990> can<00:15:13.139> make<00:15:13.259> proofs<00:15:13.499> about 00:15:13.639 --> 00:15:13.649 align:start position:0% and then they can make proofs about 00:15:13.649 --> 00:15:15.859 align:start position:0% and then they can make proofs about things<00:15:14.009> yeah<00:15:14.610> and<00:15:14.999> if<00:15:15.209> they<00:15:15.329> don't<00:15:15.449> sign<00:15:15.689> in 00:15:15.859 --> 00:15:15.869 align:start position:0% things yeah and if they don't sign in 00:15:15.869 --> 00:15:17.540 align:start position:0% things yeah and if they don't sign in with<00:15:16.019> and<00:15:16.439> we<00:15:16.619> sort<00:15:16.889> of<00:15:16.949> limit<00:15:17.220> the<00:15:17.279> amount<00:15:17.459> of 00:15:17.540 --> 00:15:17.550 align:start position:0% with and we sort of limit the amount of 00:15:17.550 --> 00:15:19.309 align:start position:0% with and we sort of limit the amount of members<00:15:17.850> in<00:15:17.970> the<00:15:17.999> group<00:15:18.059> so<00:15:18.689> this<00:15:18.839> this<00:15:19.110> tree 00:15:19.309 --> 00:15:19.319 align:start position:0% members in the group so this this tree 00:15:19.319 --> 00:15:20.780 align:start position:0% members in the group so this this tree becomes<00:15:19.709> like<00:15:19.860> a<00:15:19.889> proof<00:15:20.129> of<00:15:20.279> github 00:15:20.780 --> 00:15:20.790 align:start position:0% becomes like a proof of github 00:15:20.790 --> 00:15:22.669 align:start position:0% becomes like a proof of github yeah<00:15:21.059> and<00:15:21.179> anyone<00:15:21.420> with<00:15:21.600> github<00:15:21.899> is<00:15:22.199> able<00:15:22.559> to 00:15:22.669 --> 00:15:22.679 align:start position:0% yeah and anyone with github is able to 00:15:22.679 --> 00:15:25.549 align:start position:0% yeah and anyone with github is able to is<00:15:23.399> able<00:15:23.550> to<00:15:23.670> make<00:15:24.240> signals<00:15:24.600> about<00:15:24.720> things<00:15:24.959> so 00:15:25.549 --> 00:15:25.559 align:start position:0% is able to make signals about things so 00:15:25.559 --> 00:15:27.410 align:start position:0% is able to make signals about things so how<00:15:26.100> do<00:15:26.160> we<00:15:26.279> do<00:15:26.459> this<00:15:26.610> how<00:15:26.850> do<00:15:26.910> we<00:15:26.999> make<00:15:27.209> like<00:15:27.389> a 00:15:27.410 --> 00:15:27.420 align:start position:0% how do we do this how do we make like a 00:15:27.420 --> 00:15:30.079 align:start position:0% how do we do this how do we make like a generic<00:15:27.839> signaling<00:15:28.529> application<00:15:29.129> and<00:15:29.759> the 00:15:30.079 --> 00:15:30.089 align:start position:0% generic signaling application and the 00:15:30.089 --> 00:15:32.239 align:start position:0% generic signaling application and the way<00:15:30.179> that<00:15:30.300> we<00:15:30.360> do<00:15:30.509> it<00:15:30.540> is<00:15:30.779> so<00:15:31.410> so<00:15:31.619> basically<00:15:31.860> we 00:15:32.239 --> 00:15:32.249 align:start position:0% way that we do it is so so basically we 00:15:32.249 --> 00:15:33.859 align:start position:0% way that we do it is so so basically we have<00:15:32.399> a<00:15:32.429> lot<00:15:32.670> of<00:15:32.699> what<00:15:32.910> we<00:15:32.999> need<00:15:33.149> already<00:15:33.480> yeah 00:15:33.859 --> 00:15:33.869 align:start position:0% have a lot of what we need already yeah 00:15:33.869 --> 00:15:34.999 align:start position:0% have a lot of what we need already yeah that's<00:15:34.050> very<00:15:34.110> similar<00:15:34.439> to<00:15:34.559> make<00:15:34.709> suppose<00:15:34.889> we 00:15:34.999 --> 00:15:35.009 align:start position:0% that's very similar to make suppose we 00:15:35.009 --> 00:15:36.350 align:start position:0% that's very similar to make suppose we have<00:15:35.100> the<00:15:35.189> same<00:15:35.339> public<00:15:35.639> keys<00:15:35.790> and<00:15:36.089> private 00:15:36.350 --> 00:15:36.360 align:start position:0% have the same public keys and private 00:15:36.360 --> 00:15:37.939 align:start position:0% have the same public keys and private key<00:15:36.540> I<00:15:36.779> should<00:15:37.319> do<00:15:37.379> the<00:15:37.439> air<00:15:37.559> quotes<00:15:37.769> when<00:15:37.920> I 00:15:37.939 --> 00:15:37.949 align:start position:0% key I should do the air quotes when I 00:15:37.949 --> 00:15:40.009 align:start position:0% key I should do the air quotes when I say<00:15:38.100> public<00:15:38.220> key<00:15:38.459> private<00:15:38.730> key<00:15:38.879> we<00:15:39.809> have<00:15:39.839> the 00:15:40.009 --> 00:15:40.019 align:start position:0% say public key private key we have the 00:15:40.019 --> 00:15:41.239 align:start position:0% say public key private key we have the same<00:15:40.170> setup<00:15:40.350> and<00:15:40.559> then<00:15:40.649> we<00:15:40.740> have<00:15:40.860> a<00:15:40.889> Merkel 00:15:41.239 --> 00:15:41.249 align:start position:0% same setup and then we have a Merkel 00:15:41.249 --> 00:15:42.710 align:start position:0% same setup and then we have a Merkel tree<00:15:41.399> where<00:15:41.850> we<00:15:41.939> aggregate<00:15:42.329> all<00:15:42.389> of<00:15:42.600> these 00:15:42.710 --> 00:15:42.720 align:start position:0% tree where we aggregate all of these 00:15:42.720 --> 00:15:44.840 align:start position:0% tree where we aggregate all of these together<00:15:42.889> and<00:15:43.889> then<00:15:44.100> we<00:15:44.249> put<00:15:44.459> that<00:15:44.550> inside<00:15:44.730> the 00:15:44.840 --> 00:15:44.850 align:start position:0% together and then we put that inside the 00:15:44.850 --> 00:15:49.549 align:start position:0% together and then we put that inside the snark<00:15:46.699> and<00:15:47.699> we<00:15:47.970> add<00:15:48.149> you<00:15:48.449> see<00:15:48.660> here<00:15:48.929> you<00:15:49.379> see 00:15:49.549 --> 00:15:49.559 align:start position:0% snark and we add you see here you see 00:15:49.559 --> 00:15:52.519 align:start position:0% snark and we add you see here you see here<00:15:49.740> in<00:15:49.829> the<00:15:49.980> we<00:15:50.610> we've<00:15:50.970> added<00:15:51.209> the<00:15:51.600> idea<00:15:52.110> of<00:15:52.470> a 00:15:52.519 --> 00:15:52.529 align:start position:0% here in the we we've added the idea of a 00:15:52.529 --> 00:15:54.650 align:start position:0% here in the we we've added the idea of a signal<00:15:52.860> so<00:15:53.339> this<00:15:53.519> signal<00:15:53.819> is<00:15:53.939> just<00:15:54.119> like<00:15:54.269> 32 00:15:54.650 --> 00:15:54.660 align:start position:0% signal so this signal is just like 32 00:15:54.660 --> 00:15:56.419 align:start position:0% signal so this signal is just like 32 bytes<00:15:54.899> and<00:15:55.110> it<00:15:55.230> says<00:15:55.439> it's<00:15:55.860> the<00:15:56.009> hash<00:15:56.160> of 00:15:56.419 --> 00:15:56.429 align:start position:0% bytes and it says it's the hash of 00:15:56.429 --> 00:15:58.189 align:start position:0% bytes and it says it's the hash of something<00:15:56.730> that<00:15:56.819> you<00:15:56.939> want<00:15:57.089> to<00:15:57.119> say<00:15:57.300> I<00:15:57.540> mean<00:15:58.079> it 00:15:58.189 --> 00:15:58.199 align:start position:0% something that you want to say I mean it 00:15:58.199 --> 00:15:59.809 align:start position:0% something that you want to say I mean it could<00:15:58.350> be<00:15:58.379> the<00:15:58.439> hash<00:15:58.649> of<00:15:58.800> a<00:15:58.860> tweet<00:15:59.100> or<00:15:59.309> it<00:15:59.730> could 00:15:59.809 --> 00:15:59.819 align:start position:0% could be the hash of a tweet or it could 00:15:59.819 --> 00:16:02.720 align:start position:0% could be the hash of a tweet or it could be<00:15:59.910> the<00:15:59.999> hash<00:16:00.149> of<00:16:00.499> of<00:16:01.499> a<00:16:01.769> vote<00:16:01.980> or<00:16:02.369> it<00:16:02.459> could<00:16:02.610> be 00:16:02.720 --> 00:16:02.730 align:start position:0% be the hash of of a vote or it could be 00:16:02.730 --> 00:16:06.530 align:start position:0% be the hash of of a vote or it could be a<00:16:02.759> hash<00:16:03.059> of<00:16:03.300> something<00:16:03.600> else<00:16:05.209> yeah<00:16:06.209> so<00:16:06.420> we 00:16:06.530 --> 00:16:06.540 align:start position:0% a hash of something else yeah so we 00:16:06.540 --> 00:16:11.929 align:start position:0% a hash of something else yeah so we include<00:16:06.869> that<00:16:09.410> yeah<00:16:10.410> so<00:16:10.709> yeah<00:16:11.429> so<00:16:11.579> we<00:16:11.610> include 00:16:11.929 --> 00:16:11.939 align:start position:0% include that yeah so yeah so we include 00:16:11.939 --> 00:16:13.100 align:start position:0% include that yeah so yeah so we include the<00:16:12.029> signal<00:16:12.329> but<00:16:12.449> we<00:16:12.480> still<00:16:12.720> have<00:16:12.899> another 00:16:13.100 --> 00:16:13.110 align:start position:0% the signal but we still have another 00:16:13.110 --> 00:16:15.049 align:start position:0% the signal but we still have another problem<00:16:13.350> and<00:16:13.740> what<00:16:14.369> is<00:16:14.519> the<00:16:14.639> problem 00:16:15.049 --> 00:16:15.059 align:start position:0% problem and what is the problem 00:16:15.059 --> 00:16:25.030 align:start position:0% problem and what is the problem does<00:16:15.240> anybody<00:16:15.449> know<00:16:19.850> yeah<00:16:22.490> anybody<00:16:23.490> else 00:16:25.030 --> 00:16:25.040 align:start position:0% does anybody know yeah anybody else 00:16:25.040 --> 00:16:27.230 align:start position:0% does anybody know yeah anybody else so<00:16:26.040> think<00:16:26.279> think<00:16:26.610> about<00:16:26.790> the<00:16:26.879> difference 00:16:27.230 --> 00:16:27.240 align:start position:0% so think think about the difference 00:16:27.240 --> 00:16:28.970 align:start position:0% so think think about the difference between<00:16:27.269> what<00:16:28.110> we<00:16:28.199> do<00:16:28.290> it<00:16:28.410> makes<00:16:28.589> it<00:16:28.740> makes<00:16:28.860> a 00:16:28.970 --> 00:16:28.980 align:start position:0% between what we do it makes it makes a 00:16:28.980 --> 00:16:31.280 align:start position:0% between what we do it makes it makes a mess<00:16:29.129> like<00:16:29.369> makes<00:16:29.610> a<00:16:29.670> mess<00:16:29.819> is<00:16:29.999> we<00:16:30.749> only<00:16:31.019> want 00:16:31.280 --> 00:16:31.290 align:start position:0% mess like makes a mess is we only want 00:16:31.290 --> 00:16:34.730 align:start position:0% mess like makes a mess is we only want to<00:16:31.350> use<00:16:31.379> maximus<00:16:31.860> one<00:16:32.040> time<00:16:33.230> but<00:16:34.230> this<00:16:34.379> we<00:16:34.559> want 00:16:34.730 --> 00:16:34.740 align:start position:0% to use maximus one time but this we want 00:16:34.740 --> 00:16:37.039 align:start position:0% to use maximus one time but this we want to<00:16:34.799> use<00:16:34.889> multiple<00:16:35.339> times<00:16:35.660> does<00:16:36.660> anyone<00:16:36.899> have 00:16:37.039 --> 00:16:37.049 align:start position:0% to use multiple times does anyone have 00:16:37.049 --> 00:16:46.789 align:start position:0% to use multiple times does anyone have any<00:16:37.170> ideas<00:16:43.999> so<00:16:44.999> the<00:16:45.689> problem<00:16:46.079> is<00:16:46.199> oh<00:16:46.470> yeah 00:16:46.789 --> 00:16:46.799 align:start position:0% any ideas so the problem is oh yeah 00:16:46.799 --> 00:16:55.039 align:start position:0% any ideas so the problem is oh yeah sorry<00:16:51.980> exactly<00:16:52.980> yeah<00:16:53.850> so<00:16:54.029> the<00:16:54.149> answer<00:16:54.420> is<00:16:54.449> that 00:16:55.039 --> 00:16:55.049 align:start position:0% sorry exactly yeah so the answer is that 00:16:55.049 --> 00:16:59.749 align:start position:0% sorry exactly yeah so the answer is that you<00:16:55.199> you<00:16:55.529> you<00:16:56.600> you<00:16:57.600> if<00:16:57.990> you<00:16:58.199> reuse<00:16:58.499> you<00:16:59.009> we 00:16:59.749 --> 00:16:59.759 align:start position:0% you you you you if you reuse you we 00:16:59.759 --> 00:17:01.549 align:start position:0% you you you you if you reuse you we force<00:17:00.119> you<00:17:00.329> to<00:17:00.360> reuse<00:17:00.779> the<00:17:00.929> same<00:17:01.079> nullifier 00:17:01.549 --> 00:17:01.559 align:start position:0% force you to reuse the same nullifier 00:17:01.559 --> 00:17:03.799 align:start position:0% force you to reuse the same nullifier here<00:17:01.860> and<00:17:02.519> when<00:17:02.879> we<00:17:02.910> force<00:17:03.240> you<00:17:03.299> to<00:17:03.389> do<00:17:03.629> that 00:17:03.799 --> 00:17:03.809 align:start position:0% here and when we force you to do that 00:17:03.809 --> 00:17:06.049 align:start position:0% here and when we force you to do that you<00:17:04.620> can<00:17:04.799> link<00:17:05.069> different<00:17:05.459> signals<00:17:05.819> together 00:17:06.049 --> 00:17:06.059 align:start position:0% you can link different signals together 00:17:06.059 --> 00:17:10.130 align:start position:0% you can link different signals together yeah<00:17:06.899> so<00:17:07.559> if<00:17:07.679> I<00:17:07.799> say<00:17:08.159> if<00:17:08.939> I<00:17:09.089> do<00:17:09.149> one<00:17:09.569> tweet<00:17:09.899> and 00:17:10.130 --> 00:17:10.140 align:start position:0% yeah so if I say if I do one tweet and 00:17:10.140 --> 00:17:12.679 align:start position:0% yeah so if I say if I do one tweet and one<00:17:10.529> vote<00:17:10.799> the<00:17:11.610> nullifier<00:17:12.059> will<00:17:12.270> be<00:17:12.360> the<00:17:12.510> same 00:17:12.679 --> 00:17:12.689 align:start position:0% one vote the nullifier will be the same 00:17:12.689 --> 00:17:15.829 align:start position:0% one vote the nullifier will be the same and<00:17:12.990> I<00:17:13.319> will<00:17:13.380> I<00:17:13.679> will<00:17:14.069> be<00:17:14.610> able<00:17:14.730> to<00:17:15.029> link<00:17:15.720> those 00:17:15.829 --> 00:17:15.839 align:start position:0% and I will I will be able to link those 00:17:15.839 --> 00:17:17.449 align:start position:0% and I will I will be able to link those two<00:17:15.990> things<00:17:16.169> together<00:17:16.319> and<00:17:16.620> it<00:17:17.039> still<00:17:17.250> has 00:17:17.449 --> 00:17:17.459 align:start position:0% two things together and it still has 00:17:17.459 --> 00:17:20.000 align:start position:0% two things together and it still has like<00:17:17.669> it's<00:17:18.149> still<00:17:18.390> anonymous<00:17:18.600> ish<00:17:19.110> but 00:17:20.000 --> 00:17:20.010 align:start position:0% like it's still anonymous ish but 00:17:20.010 --> 00:17:20.960 align:start position:0% like it's still anonymous ish but because<00:17:20.279> you<00:17:20.370> can<00:17:20.490> connect<00:17:20.730> them<00:17:20.850> together 00:17:20.960 --> 00:17:20.970 align:start position:0% because you can connect them together 00:17:20.970 --> 00:17:23.090 align:start position:0% because you can connect them together it's<00:17:21.360> it's<00:17:21.630> not<00:17:21.809> really<00:17:22.020> great<00:17:22.199> because<00:17:22.799> I 00:17:23.090 --> 00:17:23.100 align:start position:0% it's it's not really great because I 00:17:23.100 --> 00:17:24.889 align:start position:0% it's it's not really great because I mean<00:17:23.819> because<00:17:24.089> we<00:17:24.299> don't<00:17:24.449> really<00:17:24.600> want<00:17:24.750> to<00:17:24.779> do 00:17:24.889 --> 00:17:24.899 align:start position:0% mean because we don't really want to do 00:17:24.899 --> 00:17:25.549 align:start position:0% mean because we don't really want to do that<00:17:25.049> I<00:17:25.199> mean<00:17:25.319> we 00:17:25.549 --> 00:17:25.559 align:start position:0% that I mean we 00:17:25.559 --> 00:17:28.159 align:start position:0% that I mean we to<00:17:25.709> be<00:17:25.769> able<00:17:25.889> to<00:17:26.329> tweet<00:17:27.329> and<00:17:27.509> vote<00:17:27.720> and<00:17:28.019> do<00:17:28.139> a 00:17:28.159 --> 00:17:28.169 align:start position:0% to be able to tweet and vote and do a 00:17:28.169 --> 00:17:29.570 align:start position:0% to be able to tweet and vote and do a bunch<00:17:28.409> of<00:17:28.470> other<00:17:28.620> things<00:17:28.710> and<00:17:29.309> have<00:17:29.429> them 00:17:29.570 --> 00:17:29.580 align:start position:0% bunch of other things and have them 00:17:29.580 --> 00:17:33.369 align:start position:0% bunch of other things and have them disconnected<00:17:30.450> from<00:17:30.659> each<00:17:30.809> other 00:17:33.369 --> 00:17:33.379 align:start position:0% 00:17:33.379 --> 00:17:37.249 align:start position:0% yeah<00:17:34.379> so<00:17:34.679> the<00:17:34.799> another<00:17:34.919> pilot<00:17:35.629> so<00:17:36.629> how<00:17:36.809> can<00:17:37.080> we 00:17:37.249 --> 00:17:37.259 align:start position:0% yeah so the another pilot so how can we 00:17:37.259 --> 00:17:41.350 align:start position:0% yeah so the another pilot so how can we fix<00:17:37.470> this<00:17:37.679> does<00:17:38.009> anyone<00:17:38.249> have<00:17:38.399> any<00:17:38.549> ideas 00:17:41.350 --> 00:17:41.360 align:start position:0% 00:17:41.360 --> 00:17:43.509 align:start position:0% sorry 00:17:43.509 --> 00:17:43.519 align:start position:0% sorry 00:17:43.519 --> 00:17:45.680 align:start position:0% sorry how<00:17:44.519> should<00:17:44.669> we<00:17:44.730> the<00:17:44.850> counter<00:17:45.210> yeah<00:17:45.450> that's 00:17:45.680 --> 00:17:45.690 align:start position:0% how should we the counter yeah that's 00:17:45.690 --> 00:17:46.009 align:start position:0% how should we the counter yeah that's right 00:17:46.009 --> 00:17:46.019 align:start position:0% right 00:17:46.019 --> 00:17:48.739 align:start position:0% right yeah<00:17:46.230> so<00:17:46.529> we<00:17:46.649> are<00:17:46.769> so<00:17:47.039> we<00:17:47.220> had<00:17:47.340> this<00:17:47.490> idea<00:17:47.700> of<00:17:48.450> an 00:17:48.739 --> 00:17:48.749 align:start position:0% yeah so we are so we had this idea of an 00:17:48.749 --> 00:17:50.629 align:start position:0% yeah so we are so we had this idea of an external<00:17:49.169> nullifier<00:17:49.590> yeah 00:17:50.629 --> 00:17:50.639 align:start position:0% external nullifier yeah 00:17:50.639 --> 00:17:52.159 align:start position:0% external nullifier yeah so<00:17:50.970> we<00:17:51.090> hashed<00:17:51.299> the<00:17:51.539> nola<00:17:51.720> part<00:17:51.990> with<00:17:52.110> the 00:17:52.159 --> 00:17:52.169 align:start position:0% so we hashed the nola part with the 00:17:52.169 --> 00:17:54.259 align:start position:0% so we hashed the nola part with the external<00:17:52.379> nullifier<00:17:52.919> inside<00:17:53.249> the<00:17:53.340> snark<00:17:53.549> and 00:17:54.259 --> 00:17:54.269 align:start position:0% external nullifier inside the snark and 00:17:54.269 --> 00:17:56.060 align:start position:0% external nullifier inside the snark and I<00:17:54.450> mean<00:17:54.990> this<00:17:55.080> gets<00:17:55.259> a<00:17:55.320> little<00:17:55.409> bit<00:17:55.559> a<00:17:55.799> little 00:17:56.060 --> 00:17:56.070 align:start position:0% I mean this gets a little bit a little 00:17:56.070 --> 00:17:59.210 align:start position:0% I mean this gets a little bit a little bit<00:17:56.190> messy<00:17:56.490> but<00:17:57.179> but<00:17:57.869> yeah<00:17:58.139> that<00:17:58.740> works<00:17:58.980> so<00:17:59.100> we 00:17:59.210 --> 00:17:59.220 align:start position:0% bit messy but but yeah that works so we 00:17:59.220 --> 00:18:01.460 align:start position:0% bit messy but but yeah that works so we have<00:17:59.340> this<00:17:59.399> external<00:17:59.730> nullifier<00:18:00.269> and<00:18:00.570> we<00:18:01.320> hash 00:18:01.460 --> 00:18:01.470 align:start position:0% have this external nullifier and we hash 00:18:01.470 --> 00:18:05.180 align:start position:0% have this external nullifier and we hash the<00:18:01.499> two<00:18:01.679> together<00:18:01.830> so<00:18:02.159> now<00:18:02.399> our<00:18:03.980> expert<00:18:04.980> are 00:18:05.180 --> 00:18:05.190 align:start position:0% the two together so now our expert are 00:18:05.190 --> 00:18:11.060 align:start position:0% the two together so now our expert are our<00:18:06.649> our<00:18:07.649> new<00:18:07.950> nullifier<00:18:09.169> will<00:18:10.169> be<00:18:10.499> unique 00:18:11.060 --> 00:18:11.070 align:start position:0% our our new nullifier will be unique 00:18:11.070 --> 00:18:12.619 align:start position:0% our our new nullifier will be unique because<00:18:11.460> as<00:18:11.820> long<00:18:11.999> as<00:18:12.149> the<00:18:12.299> external 00:18:12.619 --> 00:18:12.629 align:start position:0% because as long as the external 00:18:12.629 --> 00:18:16.039 align:start position:0% because as long as the external nullifier<00:18:13.139> is<00:18:13.320> different<00:18:13.679> then<00:18:14.539> each<00:18:15.539> signal 00:18:16.039 --> 00:18:16.049 align:start position:0% nullifier is different then each signal 00:18:16.049 --> 00:18:17.810 align:start position:0% nullifier is different then each signal is<00:18:16.139> unique<00:18:16.440> and<00:18:16.710> we<00:18:16.980> can<00:18:17.129> limit<00:18:17.309> people<00:18:17.669> from 00:18:17.810 --> 00:18:17.820 align:start position:0% is unique and we can limit people from 00:18:17.820 --> 00:18:20.269 align:start position:0% is unique and we can limit people from making<00:18:18.149> multiple<00:18:19.049> signals<00:18:19.409> about<00:18:19.980> the<00:18:20.100> same 00:18:20.269 --> 00:18:20.279 align:start position:0% making multiple signals about the same 00:18:20.279 --> 00:18:22.580 align:start position:0% making multiple signals about the same thing<00:18:20.519> but<00:18:20.820> we<00:18:21.299> can't<00:18:21.509> connect<00:18:21.840> to<00:18:21.899> say<00:18:22.110> two 00:18:22.580 --> 00:18:22.590 align:start position:0% thing but we can't connect to say two 00:18:22.590 --> 00:18:24.470 align:start position:0% thing but we can't connect to say two different<00:18:22.879> signals<00:18:23.879> about<00:18:24.029> two<00:18:24.210> different 00:18:24.470 --> 00:18:24.480 align:start position:0% different signals about two different 00:18:24.480 --> 00:18:28.389 align:start position:0% different signals about two different topics<00:18:24.600> together<00:18:26.330> okay 00:18:28.389 --> 00:18:28.399 align:start position:0% topics together okay 00:18:28.399 --> 00:18:30.830 align:start position:0% topics together okay okay<00:18:29.399> so<00:18:29.460> now<00:18:29.700> I<00:18:29.730> have<00:18:29.940> two<00:18:30.090> examples<00:18:30.419> let<00:18:30.749> me 00:18:30.830 --> 00:18:30.840 align:start position:0% okay so now I have two examples let me 00:18:30.840 --> 00:18:33.560 align:start position:0% okay so now I have two examples let me see<00:18:30.990> what<00:18:31.139> time<00:18:31.350> it<00:18:31.379> is<00:18:31.580> okay<00:18:32.580> so<00:18:32.879> this<00:18:33.029> is<00:18:33.210> this 00:18:33.560 --> 00:18:33.570 align:start position:0% see what time it is okay so this is this 00:18:33.570 --> 00:18:34.820 align:start position:0% see what time it is okay so this is this is<00:18:33.629> looking<00:18:33.869> good<00:18:34.019> so<00:18:34.169> we<00:18:34.259> can<00:18:34.409> we<00:18:34.590> can<00:18:34.710> talk 00:18:34.820 --> 00:18:34.830 align:start position:0% is looking good so we can we can talk 00:18:34.830 --> 00:18:36.799 align:start position:0% is looking good so we can we can talk about<00:18:34.970> at<00:18:35.970> least<00:18:36.149> this<00:18:36.269> example<00:18:36.570> it<00:18:36.690> may<00:18:36.779> be 00:18:36.799 --> 00:18:36.809 align:start position:0% about at least this example it may be 00:18:36.809 --> 00:18:39.649 align:start position:0% about at least this example it may be another<00:18:37.049> so<00:18:37.710> so<00:18:37.950> like<00:18:38.190> this<00:18:38.909> is<00:18:39.090> this<00:18:39.240> is<00:18:39.419> this 00:18:39.649 --> 00:18:39.659 align:start position:0% another so so like this is this is this 00:18:39.659 --> 00:18:40.730 align:start position:0% another so so like this is this is this starts<00:18:40.019> to<00:18:40.049> get<00:18:40.169> a<00:18:40.230> little<00:18:40.350> bit<00:18:40.499> complicated 00:18:40.730 --> 00:18:40.740 align:start position:0% starts to get a little bit complicated 00:18:40.740 --> 00:18:43.489 align:start position:0% starts to get a little bit complicated so<00:18:41.009> let's<00:18:41.759> do<00:18:41.909> an<00:18:42.029> example<00:18:42.090> to<00:18:42.629> make<00:18:43.019> it<00:18:43.169> to 00:18:43.489 --> 00:18:43.499 align:start position:0% so let's do an example to make it to 00:18:43.499 --> 00:18:45.649 align:start position:0% so let's do an example to make it to make<00:18:43.649> it<00:18:43.740> a<00:18:43.889> little<00:18:43.950> bit<00:18:44.159> clearer<00:18:44.369> so<00:18:45.179> so<00:18:45.450> let's 00:18:45.649 --> 00:18:45.659 align:start position:0% make it a little bit clearer so so let's 00:18:45.659 --> 00:18:48.109 align:start position:0% make it a little bit clearer so so let's do<00:18:45.809> first-past-the-post<00:18:46.320> voting<00:18:46.909> yeah<00:18:47.909> and 00:18:48.109 --> 00:18:48.119 align:start position:0% do first-past-the-post voting yeah and 00:18:48.119 --> 00:18:49.070 align:start position:0% do first-past-the-post voting yeah and let's<00:18:48.269> just<00:18:48.419> think<00:18:48.509> about<00:18:48.659> that<00:18:48.960> so 00:18:49.070 --> 00:18:49.080 align:start position:0% let's just think about that so 00:18:49.080 --> 00:18:50.629 align:start position:0% let's just think about that so first-past-the-post<00:18:49.529> voting<00:18:49.919> is<00:18:50.309> just<00:18:50.519> where 00:18:50.629 --> 00:18:50.639 align:start position:0% first-past-the-post voting is just where 00:18:50.639 --> 00:18:52.489 align:start position:0% first-past-the-post voting is just where everybody<00:18:51.090> votes<00:18:51.330> and<00:18:52.019> then<00:18:52.110> you<00:18:52.200> count<00:18:52.379> the 00:18:52.489 --> 00:18:52.499 align:start position:0% everybody votes and then you count the 00:18:52.499 --> 00:18:54.649 align:start position:0% everybody votes and then you count the votes<00:18:52.679> and<00:18:52.799> whoever<00:18:53.549> has<00:18:53.820> the<00:18:54.029> most<00:18:54.179> votes<00:18:54.360> at 00:18:54.649 --> 00:18:54.659 align:start position:0% votes and whoever has the most votes at 00:18:54.659 --> 00:18:56.450 align:start position:0% votes and whoever has the most votes at the<00:18:54.779> end<00:18:54.899> of<00:18:54.990> the<00:18:55.049> count<00:18:55.230> wins<00:18:55.710> uh<00:18:55.980> maybe 00:18:56.450 --> 00:18:56.460 align:start position:0% the end of the count wins uh maybe 00:18:56.460 --> 00:18:57.980 align:start position:0% the end of the count wins uh maybe that's<00:18:56.580> not<00:18:56.730> exactly<00:18:56.879> what<00:18:57.299> yeah<00:18:57.779> that's 00:18:57.980 --> 00:18:57.990 align:start position:0% that's not exactly what yeah that's 00:18:57.990 --> 00:18:59.239 align:start position:0% that's not exactly what yeah that's that's<00:18:58.230> what<00:18:58.379> that's<00:18:58.769> what<00:18:58.950> I'm<00:18:59.009> talking 00:18:59.239 --> 00:18:59.249 align:start position:0% that's what that's what I'm talking 00:18:59.249 --> 00:19:00.680 align:start position:0% that's what that's what I'm talking about<00:18:59.399> anyway<00:18:59.669> I'm<00:18:59.759> not<00:18:59.789> sure<00:18:59.970> if<00:19:00.059> that's<00:19:00.149> the 00:19:00.680 --> 00:19:00.690 align:start position:0% about anyway I'm not sure if that's the 00:19:00.690 --> 00:19:01.730 align:start position:0% about anyway I'm not sure if that's the technical<00:19:01.200> definition<00:19:01.350> of 00:19:01.730 --> 00:19:01.740 align:start position:0% technical definition of 00:19:01.740 --> 00:19:03.859 align:start position:0% technical definition of first-past-the-post<00:19:02.190> voting<00:19:02.429> but<00:19:02.820> yeah<00:19:03.090> okay 00:19:03.859 --> 00:19:03.869 align:start position:0% first-past-the-post voting but yeah okay 00:19:03.869 --> 00:19:05.690 align:start position:0% first-past-the-post voting but yeah okay so<00:19:03.929> so<00:19:04.740> let's<00:19:04.950> say<00:19:05.039> that<00:19:05.070> everyone<00:19:05.399> in<00:19:05.519> this 00:19:05.690 --> 00:19:05.700 align:start position:0% so so let's say that everyone in this 00:19:05.700 --> 00:19:08.629 align:start position:0% so so let's say that everyone in this room<00:19:05.759> comes<00:19:06.389> up<00:19:06.509> and<00:19:06.659> we<00:19:06.749> vote<00:19:07.080> for<00:19:07.639> some 00:19:08.629 --> 00:19:08.639 align:start position:0% room comes up and we vote for some 00:19:08.639 --> 00:19:12.230 align:start position:0% room comes up and we vote for some decision<00:19:09.389> yeah<00:19:09.869> weather<00:19:10.649> weather<00:19:11.009> zero<00:19:11.970> or 00:19:12.230 --> 00:19:12.240 align:start position:0% decision yeah weather weather zero or 00:19:12.240 --> 00:19:12.710 align:start position:0% decision yeah weather weather zero or one 00:19:12.710 --> 00:19:12.720 align:start position:0% one 00:19:12.720 --> 00:19:15.259 align:start position:0% one weather<00:19:13.309> weather<00:19:14.309> people<00:19:14.940> thought<00:19:15.090> to<00:19:15.119> have 00:19:15.259 --> 00:19:15.269 align:start position:0% weather weather people thought to have 00:19:15.269 --> 00:19:16.609 align:start position:0% weather weather people thought to have come<00:19:15.389> was<00:19:15.539> good<00:19:15.690> or<00:19:15.899> people<00:19:16.169> thought<00:19:16.289> that<00:19:16.320> one 00:19:16.609 --> 00:19:16.619 align:start position:0% come was good or people thought that one 00:19:16.619 --> 00:19:18.859 align:start position:0% come was good or people thought that one was<00:19:16.740> bad<00:19:16.860> good<00:19:17.519> okay<00:19:18.119> so<00:19:18.179> we<00:19:18.389> have<00:19:18.509> this<00:19:18.600> binary 00:19:18.859 --> 00:19:18.869 align:start position:0% was bad good okay so we have this binary 00:19:18.869 --> 00:19:21.379 align:start position:0% was bad good okay so we have this binary decision<00:19:19.169> and<00:19:19.889> we<00:19:20.369> and<00:19:20.730> we<00:19:20.850> come<00:19:20.999> up<00:19:21.119> with<00:19:21.210> some 00:19:21.379 --> 00:19:21.389 align:start position:0% decision and we and we come up with some 00:19:21.389 --> 00:19:23.480 align:start position:0% decision and we and we come up with some framework<00:19:21.749> so<00:19:21.899> we<00:19:22.019> say<00:19:22.230> that<00:19:22.259> okay<00:19:22.799> we<00:19:23.340> all 00:19:23.480 --> 00:19:23.490 align:start position:0% framework so we say that okay we all 00:19:23.490 --> 00:19:26.029 align:start position:0% framework so we say that okay we all agree<00:19:23.820> on<00:19:23.999> the<00:19:24.360> same<00:19:24.570> signal<00:19:24.990> yeah<00:19:25.350> and<00:19:25.590> the 00:19:26.029 --> 00:19:26.039 align:start position:0% agree on the same signal yeah and the 00:19:26.039 --> 00:19:34.909 align:start position:0% agree on the same signal yeah and the signal<00:19:26.429> is<00:19:28.309> wait<00:19:33.200> yeah<00:19:34.200> so<00:19:34.350> we<00:19:34.470> all<00:19:34.590> we<00:19:34.889> all 00:19:34.909 --> 00:19:34.919 align:start position:0% signal is wait yeah so we all we all 00:19:34.919 --> 00:19:36.680 align:start position:0% signal is wait yeah so we all we all agree<00:19:35.250> on<00:19:35.369> the<00:19:35.460> same<00:19:35.580> signal<00:19:36.000> and<00:19:36.179> the<00:19:36.659> signal 00:19:36.680 --> 00:19:36.690 align:start position:0% agree on the same signal and the signal 00:19:36.690 --> 00:19:39.320 align:start position:0% agree on the same signal and the signal is<00:19:37.139> that<00:19:37.470> DEFCON<00:19:38.460> is<00:19:38.490> bad 00:19:39.320 --> 00:19:39.330 align:start position:0% is that DEFCON is bad 00:19:39.330 --> 00:19:40.760 align:start position:0% is that DEFCON is bad we<00:19:39.480> have<00:19:39.600> another<00:19:39.810> signal<00:19:40.050> and<00:19:40.440> that<00:19:40.710> signal 00:19:40.760 --> 00:19:40.770 align:start position:0% we have another signal and that signal 00:19:40.770 --> 00:19:43.490 align:start position:0% we have another signal and that signal is<00:19:41.100> DEFCON<00:19:41.460> is<00:19:41.490> boo<00:19:41.700> good<00:19:41.850> yeah<00:19:42.630> and<00:19:42.900> people 00:19:43.490 --> 00:19:43.500 align:start position:0% is DEFCON is boo good yeah and people 00:19:43.500 --> 00:19:45.260 align:start position:0% is DEFCON is boo good yeah and people can<00:19:43.770> vote<00:19:43.800> and<00:19:44.160> we'll<00:19:44.250> count<00:19:44.520> up<00:19:44.640> all<00:19:44.970> of<00:19:45.180> them 00:19:45.260 --> 00:19:45.270 align:start position:0% can vote and we'll count up all of them 00:19:45.270 --> 00:19:48.520 align:start position:0% can vote and we'll count up all of them together<00:19:45.390> and<00:19:45.930> at<00:19:46.200> the<00:19:46.290> end<00:19:46.410> we'll<00:19:47.150> we'll 00:19:48.520 --> 00:19:48.530 align:start position:0% together and at the end we'll we'll 00:19:48.530 --> 00:19:51.140 align:start position:0% together and at the end we'll we'll we'll<00:19:49.530> see<00:19:49.560> who<00:19:50.010> thought<00:19:50.340> how<00:19:50.790> many<00:19:50.940> people 00:19:51.140 --> 00:19:51.150 align:start position:0% we'll see who thought how many people 00:19:51.150 --> 00:19:52.370 align:start position:0% we'll see who thought how many people thought<00:19:51.240> everything<00:19:51.480> was<00:19:51.630> good<00:19:51.810> and<00:19:51.840> how<00:19:52.200> many 00:19:52.370 --> 00:19:52.380 align:start position:0% thought everything was good and how many 00:19:52.380 --> 00:19:55.850 align:start position:0% thought everything was good and how many people<00:19:52.590> thought<00:19:52.680> they<00:19:52.830> was<00:19:52.980> bad<00:19:54.350> and<00:19:55.350> then 00:19:55.850 --> 00:19:55.860 align:start position:0% people thought they was bad and then 00:19:55.860 --> 00:19:56.960 align:start position:0% people thought they was bad and then finally<00:19:56.190> we<00:19:56.280> need<00:19:56.430> to<00:19:56.550> think<00:19:56.640> about<00:19:56.760> their 00:19:56.960 --> 00:19:56.970 align:start position:0% finally we need to think about their 00:19:56.970 --> 00:19:59.300 align:start position:0% finally we need to think about their external<00:19:57.210> nullifier<00:19:57.720> so<00:19:58.170> who<00:19:58.770> thinks<00:19:58.950> that<00:19:59.100> we 00:19:59.300 --> 00:19:59.310 align:start position:0% external nullifier so who thinks that we 00:19:59.310 --> 00:20:01.040 align:start position:0% external nullifier so who thinks that we should<00:19:59.550> use<00:19:59.760> the<00:19:59.910> same<00:20:00.120> external<00:20:00.450> nullifier 00:20:01.040 --> 00:20:01.050 align:start position:0% should use the same external nullifier 00:20:01.050 --> 00:20:05.570 align:start position:0% should use the same external nullifier four<00:20:01.500> four<00:20:01.770> four<00:20:01.950> bolt<00:20:02.340> signals<00:20:04.160> okay<00:20:05.160> and<00:20:05.430> who 00:20:05.570 --> 00:20:05.580 align:start position:0% four four four bolt signals okay and who 00:20:05.580 --> 00:20:06.950 align:start position:0% four four four bolt signals okay and who thinks<00:20:05.820> we<00:20:05.940> shouldn't<00:20:06.540> use<00:20:06.660> the<00:20:06.780> same 00:20:06.950 --> 00:20:06.960 align:start position:0% thinks we shouldn't use the same 00:20:06.960 --> 00:20:10.180 align:start position:0% thinks we shouldn't use the same external<00:20:07.200> notify<00:20:07.680> for<00:20:07.740> both<00:20:07.980> signals<00:20:09.140> okay 00:20:10.180 --> 00:20:10.190 align:start position:0% external notify for both signals okay 00:20:10.190 --> 00:20:12.740 align:start position:0% external notify for both signals okay okay<00:20:11.190> so<00:20:11.250> if<00:20:11.640> we<00:20:11.820> don't<00:20:12.120> use<00:20:12.390> the<00:20:12.570> same 00:20:12.740 --> 00:20:12.750 align:start position:0% okay so if we don't use the same 00:20:12.750 --> 00:20:15.580 align:start position:0% okay so if we don't use the same external<00:20:13.020> nullifier<00:20:13.500> for<00:20:13.680> both<00:20:13.800> signals<00:20:14.190> then 00:20:15.580 --> 00:20:15.590 align:start position:0% external nullifier for both signals then 00:20:15.590 --> 00:20:17.930 align:start position:0% external nullifier for both signals then then<00:20:16.590> people<00:20:16.920> would<00:20:17.100> be<00:20:17.220> able<00:20:17.460> to<00:20:17.520> vote<00:20:17.670> I 00:20:17.930 --> 00:20:17.940 align:start position:0% then people would be able to vote I 00:20:17.940 --> 00:20:20.600 align:start position:0% then people would be able to vote I think<00:20:18.540> that<00:20:18.660> one<00:20:18.840> was<00:20:18.930> good<00:20:19.110> and<00:20:19.410> I<00:20:20.190> think<00:20:20.370> that 00:20:20.600 --> 00:20:20.610 align:start position:0% think that one was good and I think that 00:20:20.610 --> 00:20:22.250 align:start position:0% think that one was good and I think that one<00:20:20.790> was<00:20:20.910> bad<00:20:21.030> and<00:20:21.570> we'll<00:20:21.780> have<00:20:21.930> no<00:20:21.960> way<00:20:22.110> to 00:20:22.250 --> 00:20:22.260 align:start position:0% one was bad and we'll have no way to 00:20:22.260 --> 00:20:25.190 align:start position:0% one was bad and we'll have no way to detect<00:20:22.680> them<00:20:22.830> so<00:20:23.670> we<00:20:24.420> need<00:20:24.570> to<00:20:24.690> vote<00:20:24.870> we<00:20:25.050> need 00:20:25.190 --> 00:20:25.200 align:start position:0% detect them so we need to vote we need 00:20:25.200 --> 00:20:27.950 align:start position:0% detect them so we need to vote we need to<00:20:25.320> have<00:20:25.530> the<00:20:25.710> same<00:20:26.670> nullifier<00:20:27.390> external 00:20:27.950 --> 00:20:27.960 align:start position:0% to have the same nullifier external 00:20:27.960 --> 00:20:30.830 align:start position:0% to have the same nullifier external nullifier<00:20:28.350> for<00:20:28.560> bolt<00:20:28.760> ok<00:20:29.760> and<00:20:29.970> this<00:20:30.480> way<00:20:30.780> you 00:20:30.830 --> 00:20:30.840 align:start position:0% nullifier for bolt ok and this way you 00:20:30.840 --> 00:20:32.900 align:start position:0% nullifier for bolt ok and this way you can<00:20:31.080> you<00:20:31.770> you<00:20:31.950> can<00:20:32.130> link<00:20:32.340> the<00:20:32.490> votes<00:20:32.670> together 00:20:32.900 --> 00:20:32.910 align:start position:0% can you you can link the votes together 00:20:32.910 --> 00:20:36.530 align:start position:0% can you you can link the votes together which<00:20:33.720> kind<00:20:33.960> of<00:20:34.020> sucks<00:20:34.260> but<00:20:35.070> you<00:20:35.730> also<00:20:35.970> limit 00:20:36.530 --> 00:20:36.540 align:start position:0% which kind of sucks but you also limit 00:20:36.540 --> 00:20:38.120 align:start position:0% which kind of sucks but you also limit people<00:20:36.750> from<00:20:36.870> voting<00:20:37.080> twice<00:20:37.230> which<00:20:38.100> is 00:20:38.120 --> 00:20:38.130 align:start position:0% people from voting twice which is 00:20:38.130 --> 00:20:41.660 align:start position:0% people from voting twice which is definitely<00:20:38.640> a<00:20:38.700> good<00:20:38.850> idea<00:20:39.710> okay<00:20:40.710> so<00:20:41.430> now<00:20:41.610> we 00:20:41.660 --> 00:20:41.670 align:start position:0% definitely a good idea okay so now we 00:20:41.670 --> 00:20:42.980 align:start position:0% definitely a good idea okay so now we can<00:20:41.940> let's<00:20:42.240> talk<00:20:42.420> about<00:20:42.540> something<00:20:42.870> a<00:20:42.930> little 00:20:42.980 --> 00:20:42.990 align:start position:0% can let's talk about something a little 00:20:42.990 --> 00:20:45.500 align:start position:0% can let's talk about something a little bit<00:20:43.170> more<00:20:43.490> complicated<00:20:44.490> so<00:20:44.910> we<00:20:45.030> can<00:20:45.150> also<00:20:45.270> do 00:20:45.500 --> 00:20:45.510 align:start position:0% bit more complicated so we can also do 00:20:45.510 --> 00:20:48.110 align:start position:0% bit more complicated so we can also do like<00:20:45.690> proportional<00:20:46.200> representation<00:20:47.120> and 00:20:48.110 --> 00:20:48.120 align:start position:0% like proportional representation and 00:20:48.120 --> 00:20:49.610 align:start position:0% like proportional representation and proportional<00:20:48.690> representation<00:20:49.080> is<00:20:49.320> another 00:20:49.610 --> 00:20:49.620 align:start position:0% proportional representation is another 00:20:49.620 --> 00:20:51.440 align:start position:0% proportional representation is another form<00:20:49.890> of<00:20:50.010> voting<00:20:50.220> where<00:20:50.550> when<00:20:51.180> instead<00:20:51.390> of 00:20:51.440 --> 00:20:51.450 align:start position:0% form of voting where when instead of 00:20:51.450 --> 00:20:53.330 align:start position:0% form of voting where when instead of voting<00:20:51.720> like<00:20:52.140> having<00:20:52.440> a<00:20:52.500> binary<00:20:52.680> choice<00:20:52.830> you 00:20:53.330 --> 00:20:53.340 align:start position:0% voting like having a binary choice you 00:20:53.340 --> 00:20:55.000 align:start position:0% voting like having a binary choice you can<00:20:53.520> you<00:20:53.670> can<00:20:53.820> choose<00:20:54.000> among<00:20:54.180> multiple 00:20:55.000 --> 00:20:55.010 align:start position:0% can you can choose among multiple 00:20:55.010 --> 00:20:57.650 align:start position:0% can you can choose among multiple multiple<00:20:56.010> different<00:20:56.430> choices<00:20:56.610> so<00:20:57.030> the<00:20:57.390> idea 00:20:57.650 --> 00:20:57.660 align:start position:0% multiple different choices so the idea 00:20:57.660 --> 00:20:59.990 align:start position:0% multiple different choices so the idea so<00:20:58.290> that's<00:20:58.500> that's<00:20:58.800> a<00:20:59.010> spanner<00:20:59.250> or<00:20:59.430> a<00:20:59.730> previous 00:20:59.990 --> 00:21:00.000 align:start position:0% so that's that's a spanner or a previous 00:21:00.000 --> 00:21:02.210 align:start position:0% so that's that's a spanner or a previous example<00:21:00.390> where<00:21:01.170> we<00:21:01.260> had<00:21:01.440> oh<00:21:01.710> I<00:21:01.740> think<00:21:01.980> that 00:21:02.210 --> 00:21:02.220 align:start position:0% example where we had oh I think that 00:21:02.220 --> 00:21:03.980 align:start position:0% example where we had oh I think that program<00:21:02.430> was<00:21:02.520> good<00:21:02.700> I<00:21:03.030> think<00:21:03.300> that<00:21:03.450> wasn't<00:21:03.690> bad 00:21:03.980 --> 00:21:03.990 align:start position:0% program was good I think that wasn't bad 00:21:03.990 --> 00:21:06.110 align:start position:0% program was good I think that wasn't bad and<00:21:04.500> now<00:21:04.770> we<00:21:04.860> can<00:21:04.980> add<00:21:05.070> a<00:21:05.100> third<00:21:05.190> one<00:21:05.340> I<00:21:05.520> and<00:21:05.880> say 00:21:06.110 --> 00:21:06.120 align:start position:0% and now we can add a third one I and say 00:21:06.120 --> 00:21:07.460 align:start position:0% and now we can add a third one I and say that<00:21:06.300> I<00:21:06.330> think<00:21:06.480> that<00:21:06.750> one<00:21:06.870> was<00:21:06.990> okay<00:21:07.260> but<00:21:07.410> I 00:21:07.460 --> 00:21:07.470 align:start position:0% that I think that one was okay but I 00:21:07.470 --> 00:21:09.170 align:start position:0% that I think that one was okay but I think<00:21:07.740> I<00:21:07.920> think<00:21:08.130> we<00:21:08.220> can<00:21:08.340> do<00:21:08.430> better<00:21:08.580> next<00:21:08.760> year 00:21:09.170 --> 00:21:09.180 align:start position:0% think I think we can do better next year 00:21:09.180 --> 00:21:11.810 align:start position:0% think I think we can do better next year so<00:21:10.080> that<00:21:10.230> people<00:21:10.470> can<00:21:10.680> people<00:21:11.280> can<00:21:11.370> choose<00:21:11.550> oh 00:21:11.810 --> 00:21:11.820 align:start position:0% so that people can people can choose oh 00:21:11.820 --> 00:21:13.310 align:start position:0% so that people can people can choose oh actually<00:21:12.510> that<00:21:12.750> doesn't<00:21:12.990> really<00:21:13.170> make<00:21:13.290> sense 00:21:13.310 --> 00:21:13.320 align:start position:0% actually that doesn't really make sense 00:21:13.320 --> 00:21:15.470 align:start position:0% actually that doesn't really make sense I<00:21:13.710> think<00:21:14.400> I<00:21:14.430> think<00:21:14.730> I<00:21:14.790> think<00:21:15.000> it<00:21:15.210> makes<00:21:15.300> more 00:21:15.470 --> 00:21:15.480 align:start position:0% I think I think I think it makes more 00:21:15.480 --> 00:21:17.660 align:start position:0% I think I think I think it makes more sense<00:21:15.690> for<00:21:15.750> like<00:21:15.960> leadership<00:21:16.410> elections<00:21:16.830> so 00:21:17.660 --> 00:21:17.670 align:start position:0% sense for like leadership elections so 00:21:17.670 --> 00:21:19.940 align:start position:0% sense for like leadership elections so let's<00:21:18.000> say<00:21:18.150> that<00:21:18.300> we<00:21:18.450> vote<00:21:18.720> between<00:21:19.110> an 00:21:19.940 --> 00:21:19.950 align:start position:0% let's say that we vote between an 00:21:19.950 --> 00:21:24.470 align:start position:0% let's say that we vote between an elephant<00:21:20.790> giraffe<00:21:21.780> and<00:21:22.350> a<00:21:23.190> kangaroo<00:21:23.370> to<00:21:24.210> be 00:21:24.470 --> 00:21:24.480 align:start position:0% elephant giraffe and a kangaroo to be 00:21:24.480 --> 00:21:28.460 align:start position:0% elephant giraffe and a kangaroo to be our<00:21:24.690> to<00:21:25.260> be<00:21:25.290> our<00:21:25.470> leaders<00:21:25.770> okay<00:21:26.580> and<00:21:27.290> we<00:21:28.290> want 00:21:28.460 --> 00:21:28.470 align:start position:0% our to be our leaders okay and we want 00:21:28.470 --> 00:21:33.830 align:start position:0% our to be our leaders okay and we want it<00:21:28.620> so<00:21:31.070> okay<00:21:32.070> so<00:21:32.240> different<00:21:33.240> people<00:21:33.510> like 00:21:33.830 --> 00:21:33.840 align:start position:0% it so okay so different people like 00:21:33.840 --> 00:21:35.540 align:start position:0% it so okay so different people like different<00:21:33.870> animals<00:21:34.530> more<00:21:34.740> yeah 00:21:35.540 --> 00:21:35.550 align:start position:0% different animals more yeah 00:21:35.550 --> 00:21:37.970 align:start position:0% different animals more yeah oh<00:21:35.580> let's<00:21:36.540> change<00:21:36.750> one<00:21:36.930> of<00:21:37.050> them<00:21:37.140> to<00:21:37.260> a<00:21:37.290> lion<00:21:37.560> so 00:21:37.970 --> 00:21:37.980 align:start position:0% oh let's change one of them to a lion so 00:21:37.980 --> 00:21:40.790 align:start position:0% oh let's change one of them to a lion so an<00:21:38.070> elephant<00:21:38.520> a<00:21:38.730> kangaroo<00:21:39.180> and<00:21:39.300> a<00:21:39.390> lion<00:21:39.800> yeah 00:21:40.790 --> 00:21:40.800 align:start position:0% an elephant a kangaroo and a lion yeah 00:21:40.800 --> 00:21:46.780 align:start position:0% an elephant a kangaroo and a lion yeah because<00:21:41.160> this<00:21:41.370> makes<00:21:41.760> more<00:21:41.940> sense<00:21:42.180> okay 00:21:46.780 --> 00:21:46.790 align:start position:0% 00:21:46.790 --> 00:21:51.470 align:start position:0% okay<00:21:47.790> so<00:21:49.429> okay<00:21:50.429> so<00:21:50.549> we're<00:21:50.820> voting<00:21:51.000> between<00:21:51.450> a 00:21:51.470 --> 00:21:51.480 align:start position:0% okay so okay so we're voting between a 00:21:51.480 --> 00:21:53.539 align:start position:0% okay so okay so we're voting between a elephant<00:21:51.840> kangaroo<00:21:52.200> no<00:21:52.320> line<00:21:52.500> right<00:21:52.950> and<00:21:53.190> we 00:21:53.539 --> 00:21:53.549 align:start position:0% elephant kangaroo no line right and we 00:21:53.549 --> 00:21:57.200 align:start position:0% elephant kangaroo no line right and we want<00:21:53.760> to<00:21:53.940> pick<00:21:55.280> yeah<00:21:56.280> so<00:21:56.460> some<00:21:56.640> people<00:21:56.760> really 00:21:57.200 --> 00:21:57.210 align:start position:0% want to pick yeah so some people really 00:21:57.210 --> 00:21:58.760 align:start position:0% want to pick yeah so some people really some<00:21:57.720> people<00:21:57.960> really<00:21:58.230> don't<00:21:58.350> want<00:21:58.620> to<00:21:58.710> vote 00:21:58.760 --> 00:21:58.770 align:start position:0% some people really don't want to vote 00:21:58.770 --> 00:22:02.000 align:start position:0% some people really don't want to vote for<00:21:58.830> the<00:21:59.070> lion<00:21:59.330> so<00:22:00.360> oh<00:22:00.720> wait<00:22:01.440> I'm<00:22:01.650> explaining 00:22:02.000 --> 00:22:02.010 align:start position:0% for the lion so oh wait I'm explaining 00:22:02.010 --> 00:22:03.500 align:start position:0% for the lion so oh wait I'm explaining the<00:22:02.280> the<00:22:02.549> benefits<00:22:02.970> of<00:22:03.090> proportional 00:22:03.500 --> 00:22:03.510 align:start position:0% the the benefits of proportional 00:22:03.510 --> 00:22:05.000 align:start position:0% the the benefits of proportional representation<00:22:03.900> and<00:22:04.380> I<00:22:04.500> shouldn't<00:22:04.830> do<00:22:04.890> that 00:22:05.000 --> 00:22:05.010 align:start position:0% representation and I shouldn't do that 00:22:05.010 --> 00:22:13.340 align:start position:0% representation and I shouldn't do that because<00:22:05.240> on<00:22:06.240> topic<00:22:06.540> okay<00:22:07.730> okay<00:22:08.730> so<00:22:12.169> okay<00:22:13.169> so 00:22:13.340 --> 00:22:13.350 align:start position:0% because on topic okay okay so okay so 00:22:13.350 --> 00:22:15.530 align:start position:0% because on topic okay okay so okay so yeah<00:22:13.679> so<00:22:13.950> so<00:22:14.580> basically<00:22:14.700> we<00:22:15.090> can<00:22:15.120> do<00:22:15.270> the<00:22:15.390> same 00:22:15.530 --> 00:22:15.540 align:start position:0% yeah so so basically we can do the same 00:22:15.540 --> 00:22:18.110 align:start position:0% yeah so so basically we can do the same thing<00:22:15.750> but<00:22:16.260> for<00:22:16.710> the<00:22:16.830> elephant<00:22:17.220> the<00:22:17.400> lion<00:22:17.760> and 00:22:18.110 --> 00:22:18.120 align:start position:0% thing but for the elephant the lion and 00:22:18.120 --> 00:22:20.630 align:start position:0% thing but for the elephant the lion and the<00:22:18.390> kangaroo<00:22:19.290> they<00:22:20.040> each<00:22:20.250> have<00:22:20.520> a<00:22:20.549> different 00:22:20.630 --> 00:22:20.640 align:start position:0% the kangaroo they each have a different 00:22:20.640 --> 00:22:22.820 align:start position:0% the kangaroo they each have a different signal<00:22:21.330> but<00:22:22.020> the<00:22:22.140> external<00:22:22.350> no<00:22:22.559> the<00:22:22.620> fire 00:22:22.820 --> 00:22:22.830 align:start position:0% signal but the external no the fire 00:22:22.830 --> 00:22:25.760 align:start position:0% signal but the external no the fire always<00:22:22.980> stays<00:22:23.220> the<00:22:23.250> same<00:22:23.720> okay<00:22:24.720> yeah 00:22:25.760 --> 00:22:25.770 align:start position:0% always stays the same okay yeah 00:22:25.770 --> 00:22:27.770 align:start position:0% always stays the same okay yeah so<00:22:26.370> that<00:22:26.730> really<00:22:27.150> makes<00:22:27.360> sense<00:22:27.570> from<00:22:27.630> it's 00:22:27.770 --> 00:22:27.780 align:start position:0% so that really makes sense from it's 00:22:27.780 --> 00:22:29.830 align:start position:0% so that really makes sense from it's very<00:22:27.929> similar<00:22:28.110> it's<00:22:28.290> a<00:22:28.320> previous<00:22:28.620> example 00:22:29.830 --> 00:22:29.840 align:start position:0% very similar it's a previous example 00:22:29.840 --> 00:22:33.440 align:start position:0% very similar it's a previous example okay<00:22:30.980> okay<00:22:31.980> so<00:22:32.160> let's<00:22:32.700> just<00:22:32.820> keep<00:22:33.059> going<00:22:33.330> I 00:22:33.440 --> 00:22:33.450 align:start position:0% okay okay so let's just keep going I 00:22:33.450 --> 00:22:34.789 align:start position:0% okay okay so let's just keep going I mean<00:22:33.600> here's<00:22:33.840> the<00:22:33.929> current<00:22:34.320> problems<00:22:34.650> with 00:22:34.789 --> 00:22:34.799 align:start position:0% mean here's the current problems with 00:22:34.799 --> 00:22:40.490 align:start position:0% mean here's the current problems with with<00:22:35.460> with<00:22:35.730> some<00:22:35.880> before<00:22:38.450> so<00:22:39.450> chemists<00:22:39.900> so<00:22:40.049> can 00:22:40.490 --> 00:22:40.500 align:start position:0% with with some before so chemists so can 00:22:40.500 --> 00:22:41.870 align:start position:0% with with some before so chemists so can we<00:22:40.590> build<00:22:40.890> a<00:22:41.130> proportional<00:22:41.580> representation 00:22:41.870 --> 00:22:41.880 align:start position:0% we build a proportional representation 00:22:41.880 --> 00:22:43.430 align:start position:0% we build a proportional representation where<00:22:42.330> you<00:22:42.390> can't<00:22:42.600> link<00:22:42.809> the<00:22:42.929> votes<00:22:43.110> together 00:22:43.430 --> 00:22:43.440 align:start position:0% where you can't link the votes together 00:22:43.440 --> 00:22:45.110 align:start position:0% where you can't link the votes together because<00:22:43.980> I<00:22:44.100> mean<00:22:44.250> in<00:22:44.400> the<00:22:44.460> previous<00:22:44.790> example 00:22:45.110 --> 00:22:45.120 align:start position:0% because I mean in the previous example 00:22:45.120 --> 00:22:46.340 align:start position:0% because I mean in the previous example it's<00:22:45.419> clear<00:22:45.660> that<00:22:45.690> we<00:22:45.870> have<00:22:45.900> to<00:22:46.049> use<00:22:46.169> the<00:22:46.230> same 00:22:46.340 --> 00:22:46.350 align:start position:0% it's clear that we have to use the same 00:22:46.350 --> 00:22:48.380 align:start position:0% it's clear that we have to use the same external<00:22:46.590> nullifier<00:22:47.070> I<00:22:47.309> have<00:22:48.210> for<00:22:48.360> each 00:22:48.380 --> 00:22:48.390 align:start position:0% external nullifier I have for each 00:22:48.390 --> 00:22:50.270 align:start position:0% external nullifier I have for each signal<00:22:48.780> and<00:22:48.929> that<00:22:49.020> kind<00:22:49.200> of<00:22:49.260> lets<00:22:49.410> us<00:22:49.590> that's 00:22:50.270 --> 00:22:50.280 align:start position:0% signal and that kind of lets us that's 00:22:50.280 --> 00:22:52.220 align:start position:0% signal and that kind of lets us that's us<00:22:50.400> link<00:22:50.730> that<00:22:50.910> oh<00:22:51.090> I<00:22:51.120> voted<00:22:51.510> first<00:22:51.840> for<00:22:52.140> the 00:22:52.220 --> 00:22:52.230 align:start position:0% us link that oh I voted first for the 00:22:52.230 --> 00:22:54.049 align:start position:0% us link that oh I voted first for the kangaroo<00:22:52.590> and<00:22:52.620> then<00:22:52.950> for<00:22:53.250> the<00:22:53.340> giraffe<00:22:53.700> and 00:22:54.049 --> 00:22:54.059 align:start position:0% kangaroo and then for the giraffe and 00:22:54.059 --> 00:22:56.090 align:start position:0% kangaroo and then for the giraffe and then<00:22:54.179> for<00:22:54.419> the<00:22:54.480> lion<00:22:54.690> and<00:22:55.260> that's<00:22:55.559> that<00:22:55.919> and 00:22:56.090 --> 00:22:56.100 align:start position:0% then for the lion and that's that and 00:22:56.100 --> 00:22:57.770 align:start position:0% then for the lion and that's that and that<00:22:56.250> will<00:22:56.400> reveal<00:22:56.669> information<00:22:57.059> about<00:22:57.450> the 00:22:57.770 --> 00:22:57.780 align:start position:0% that will reveal information about the 00:22:57.780 --> 00:22:59.990 align:start position:0% that will reveal information about the electorate<00:22:58.410> in<00:22:58.530> general<00:22:58.890> and<00:22:59.070> maybe<00:22:59.669> we<00:22:59.850> want 00:22:59.990 --> 00:23:00.000 align:start position:0% electorate in general and maybe we want 00:23:00.000 --> 00:23:01.520 align:start position:0% electorate in general and maybe we want to<00:23:00.090> stop<00:23:00.299> doing<00:23:00.570> maybe<00:23:00.960> we<00:23:01.080> want<00:23:01.169> we<00:23:01.440> don't 00:23:01.520 --> 00:23:01.530 align:start position:0% to stop doing maybe we want we don't 00:23:01.530 --> 00:23:05.720 align:start position:0% to stop doing maybe we want we don't want<00:23:01.710> to<00:23:01.770> do<00:23:01.830> that<00:23:03.679> yeah<00:23:04.679> so<00:23:04.950> that's<00:23:05.309> one<00:23:05.549> thing 00:23:05.720 --> 00:23:05.730 align:start position:0% want to do that yeah so that's one thing 00:23:05.730 --> 00:23:09.080 align:start position:0% want to do that yeah so that's one thing but<00:23:06.000> that's<00:23:06.540> really<00:23:06.750> complicated<00:23:07.640> and<00:23:08.640> can<00:23:09.000> we 00:23:09.080 --> 00:23:09.090 align:start position:0% but that's really complicated and can we 00:23:09.090 --> 00:23:11.780 align:start position:0% but that's really complicated and can we do<00:23:09.179> quadratic<00:23:09.570> voting<00:23:10.080> like<00:23:10.230> this<00:23:10.790> that's 00:23:11.780 --> 00:23:11.790 align:start position:0% do quadratic voting like this that's 00:23:11.790 --> 00:23:13.070 align:start position:0% do quadratic voting like this that's another<00:23:11.880> interesting<00:23:12.210> question<00:23:12.480> there's 00:23:13.070 --> 00:23:13.080 align:start position:0% another interesting question there's 00:23:13.080 --> 00:23:14.330 align:start position:0% another interesting question there's like<00:23:13.260> a<00:23:13.290> bunch<00:23:13.500> of<00:23:13.590> application<00:23:14.070> for<00:23:14.220> some 00:23:14.330 --> 00:23:14.340 align:start position:0% like a bunch of application for some 00:23:14.340 --> 00:23:15.440 align:start position:0% like a bunch of application for some before<00:23:14.580> that<00:23:14.730> that<00:23:15.000> haven't<00:23:15.210> really<00:23:15.360> been 00:23:15.440 --> 00:23:15.450 align:start position:0% before that that haven't really been 00:23:15.450 --> 00:23:17.930 align:start position:0% before that that haven't really been explored<00:23:16.280> again<00:23:17.280> how<00:23:17.429> do<00:23:17.490> we<00:23:17.580> pay<00:23:17.700> the<00:23:17.730> gas 00:23:17.930 --> 00:23:17.940 align:start position:0% explored again how do we pay the gas 00:23:17.940 --> 00:23:20.630 align:start position:0% explored again how do we pay the gas that<00:23:18.150> is<00:23:18.330> if<00:23:18.510> you<00:23:18.630> do<00:23:18.840> this<00:23:19.049> if<00:23:20.040> you<00:23:20.220> do<00:23:20.340> this<00:23:20.460> on 00:23:20.630 --> 00:23:20.640 align:start position:0% that is if you do this if you do this on 00:23:20.640 --> 00:23:24.289 align:start position:0% that is if you do this if you do this on chain<00:23:20.850> but<00:23:21.030> I<00:23:21.299> don't<00:23:21.600> we<00:23:22.880> change<00:23:23.880> stuff<00:23:24.150> with 00:23:24.289 --> 00:23:24.299 align:start position:0% chain but I don't we change stuff with 00:23:24.299 --> 00:23:25.970 align:start position:0% chain but I don't we change stuff with this<00:23:24.450> but<00:23:24.690> in<00:23:25.020> general<00:23:25.440> it<00:23:25.500> makes<00:23:25.590> more<00:23:25.770> sense 00:23:25.970 --> 00:23:25.980 align:start position:0% this but in general it makes more sense 00:23:25.980 --> 00:23:27.980 align:start position:0% this but in general it makes more sense to<00:23:26.070> have<00:23:26.160> it<00:23:26.760> as<00:23:26.850> an<00:23:26.940> option<00:23:27.059> of<00:23:27.600> chain 00:23:27.980 --> 00:23:27.990 align:start position:0% to have it as an option of chain 00:23:27.990 --> 00:23:29.780 align:start position:0% to have it as an option of chain scalability<00:23:28.530> solution<00:23:29.100> Ono<00:23:29.429> obtained 00:23:29.780 --> 00:23:29.790 align:start position:0% scalability solution Ono obtained 00:23:29.790 --> 00:23:31.430 align:start position:0% scalability solution Ono obtained signaling<00:23:30.210> solution<00:23:30.570> I<00:23:30.690> mean<00:23:31.049> it<00:23:31.110> just<00:23:31.200> works 00:23:31.430 --> 00:23:31.440 align:start position:0% signaling solution I mean it just works 00:23:31.440 --> 00:23:32.419 align:start position:0% signaling solution I mean it just works a<00:23:31.559> lot<00:23:31.650> better<00:23:31.710> because<00:23:32.100> you<00:23:32.160> have<00:23:32.280> to<00:23:32.340> pay 00:23:32.419 --> 00:23:32.429 align:start position:0% a lot better because you have to pay 00:23:32.429 --> 00:23:33.530 align:start position:0% a lot better because you have to pay five<00:23:32.580> hundred<00:23:32.610> thousand<00:23:33.030> guys<00:23:33.120> for<00:23:33.330> every 00:23:33.530 --> 00:23:33.540 align:start position:0% five hundred thousand guys for every 00:23:33.540 --> 00:23:35.270 align:start position:0% five hundred thousand guys for every vote<00:23:33.780> which<00:23:34.440> is<00:23:34.620> which<00:23:34.890> it<00:23:35.010> doesn't<00:23:35.130> really 00:23:35.270 --> 00:23:35.280 align:start position:0% vote which is which it doesn't really 00:23:35.280 --> 00:23:38.150 align:start position:0% vote which is which it doesn't really work<00:23:35.429> very<00:23:35.640> well<00:23:36.350> okay<00:23:37.350> and<00:23:37.620> then<00:23:37.740> can<00:23:38.040> we<00:23:38.130> make 00:23:38.150 --> 00:23:38.160 align:start position:0% work very well okay and then can we make 00:23:38.160 --> 00:23:40.520 align:start position:0% work very well okay and then can we make deniable<00:23:38.669> signatures<00:23:39.179> so<00:23:39.900> this<00:23:40.049> is<00:23:40.200> this<00:23:40.350> is 00:23:40.520 --> 00:23:40.530 align:start position:0% deniable signatures so this is this is 00:23:40.530 --> 00:23:42.740 align:start position:0% deniable signatures so this is this is more<00:23:40.710> to<00:23:40.830> do<00:23:40.919> with<00:23:41.100> like<00:23:41.280> anti<00:23:42.150> coercion 00:23:42.740 --> 00:23:42.750 align:start position:0% more to do with like anti coercion 00:23:42.750 --> 00:23:45.830 align:start position:0% more to do with like anti coercion voting<00:23:43.350> oh<00:23:43.470> no<00:23:44.340> bribery<00:23:44.910> resistant<00:23:45.570> folding 00:23:45.830 --> 00:23:45.840 align:start position:0% voting oh no bribery resistant folding 00:23:45.840 --> 00:23:47.780 align:start position:0% voting oh no bribery resistant folding or<00:23:45.960> coercion<00:23:46.260> resistant<00:23:46.770> folding<00:23:47.070> where 00:23:47.780 --> 00:23:47.790 align:start position:0% or coercion resistant folding where 00:23:47.790 --> 00:23:49.150 align:start position:0% or coercion resistant folding where where<00:23:48.150> someone<00:23:48.480> can<00:23:48.570> force<00:23:48.780> someone<00:23:48.990> to 00:23:49.150 --> 00:23:49.160 align:start position:0% where someone can force someone to 00:23:49.160 --> 00:23:51.380 align:start position:0% where someone can force someone to either<00:23:50.160> through<00:23:50.429> physical<00:23:50.820> force<00:23:51.000> or<00:23:51.120> through 00:23:51.380 --> 00:23:51.390 align:start position:0% either through physical force or through 00:23:51.390 --> 00:23:53.510 align:start position:0% either through physical force or through money<00:23:51.660> to<00:23:51.990> or<00:23:52.350> they<00:23:52.559> can<00:23:52.710> pay<00:23:53.070> them<00:23:53.250> to<00:23:53.370> vote<00:23:53.490> a 00:23:53.510 --> 00:23:53.520 align:start position:0% money to or they can pay them to vote a 00:23:53.520 --> 00:23:55.370 align:start position:0% money to or they can pay them to vote a certain<00:23:53.610> way<00:23:53.790> and<00:23:54.059> this<00:23:54.330> is<00:23:54.390> about<00:23:54.630> dayum<00:23:55.080> we 00:23:55.370 --> 00:23:55.380 align:start position:0% certain way and this is about dayum we 00:23:55.380 --> 00:23:56.690 align:start position:0% certain way and this is about dayum we all<00:23:55.500> agree<00:23:55.710> it's<00:23:55.860> about<00:23:56.010> thing<00:23:56.190> and<00:23:56.340> we<00:23:56.520> should 00:23:56.690 --> 00:23:56.700 align:start position:0% all agree it's about thing and we should 00:23:56.700 --> 00:23:58.370 align:start position:0% all agree it's about thing and we should think<00:23:56.820> about<00:23:56.970> how<00:23:57.179> to<00:23:57.240> solve<00:23:57.480> it 00:23:58.370 --> 00:23:58.380 align:start position:0% think about how to solve it 00:23:58.380 --> 00:23:59.810 align:start position:0% think about how to solve it and<00:23:58.770> there's<00:23:58.980> and<00:23:59.250> there's<00:23:59.310> some<00:23:59.580> ways<00:23:59.700> that 00:23:59.810 --> 00:23:59.820 align:start position:0% and there's and there's some ways that 00:23:59.820 --> 00:24:01.130 align:start position:0% and there's and there's some ways that we<00:23:59.940> can<00:24:00.060> do<00:24:00.180> it<00:24:00.300> but<00:24:00.600> they're<00:24:00.750> kind<00:24:00.960> of<00:24:00.990> outside 00:24:01.130 --> 00:24:01.140 align:start position:0% we can do it but they're kind of outside 00:24:01.140 --> 00:24:02.210 align:start position:0% we can do it but they're kind of outside the<00:24:01.290> scope<00:24:01.410> of<00:24:01.680> what<00:24:01.800> we're<00:24:01.950> talking<00:24:02.040> about 00:24:02.210 --> 00:24:02.220 align:start position:0% the scope of what we're talking about 00:24:02.220 --> 00:24:04.220 align:start position:0% the scope of what we're talking about here<00:24:02.430> but<00:24:02.640> if<00:24:03.330> anyone's<00:24:03.660> interested<00:24:03.780> to<00:24:04.110> talk 00:24:04.220 --> 00:24:04.230 align:start position:0% here but if anyone's interested to talk 00:24:04.230 --> 00:24:05.180 align:start position:0% here but if anyone's interested to talk about<00:24:04.440> that<00:24:04.560> we<00:24:04.650> can<00:24:04.800> talk<00:24:04.830> about<00:24:04.950> it<00:24:05.160> later 00:24:05.180 --> 00:24:05.190 align:start position:0% about that we can talk about it later 00:24:05.190 --> 00:24:10.790 align:start position:0% about that we can talk about it later okay<00:24:06.200> so<00:24:07.200> now<00:24:07.640> now<00:24:08.640> some<00:24:09.570> more<00:24:10.080> limitations<00:24:10.470> of 00:24:10.790 --> 00:24:10.800 align:start position:0% okay so now now some more limitations of 00:24:10.800 --> 00:24:12.200 align:start position:0% okay so now now some more limitations of the<00:24:10.950> snark<00:24:11.250> work<00:24:11.400> that<00:24:11.520> we've<00:24:11.610> done<00:24:11.640> so<00:24:11.880> far 00:24:12.200 --> 00:24:12.210 align:start position:0% the snark work that we've done so far 00:24:12.210 --> 00:24:15.350 align:start position:0% the snark work that we've done so far so<00:24:12.330> the<00:24:12.420> proofing<00:24:12.660> time<00:24:12.810> is<00:24:13.550> is<00:24:14.550> is<00:24:14.850> quite<00:24:15.180> long 00:24:15.350 --> 00:24:15.360 align:start position:0% so the proofing time is is is quite long 00:24:15.360 --> 00:24:18.380 align:start position:0% so the proofing time is is is quite long for<00:24:15.420> Maximus<00:24:16.230> in<00:24:16.320> semaphore<00:24:17.090> it<00:24:18.090> takes<00:24:18.300> about 00:24:18.380 --> 00:24:18.390 align:start position:0% for Maximus in semaphore it takes about 00:24:18.390 --> 00:24:22.340 align:start position:0% for Maximus in semaphore it takes about I<00:24:18.870> have<00:24:19.140> some<00:24:19.290> numbers<00:24:19.560> here<00:24:19.590> oh<00:24:20.870> wait<00:24:21.870> no<00:24:22.140> I'll 00:24:22.340 --> 00:24:22.350 align:start position:0% I have some numbers here oh wait no I'll 00:24:22.350 --> 00:24:23.240 align:start position:0% I have some numbers here oh wait no I'll talk<00:24:22.500> about<00:24:22.680> that<00:24:22.770> in<00:24:22.830> a<00:24:22.890> minute 00:24:23.240 --> 00:24:23.250 align:start position:0% talk about that in a minute 00:24:23.250 --> 00:24:25.670 align:start position:0% talk about that in a minute okay<00:24:23.700> so<00:24:23.760> then<00:24:24.120> there's<00:24:24.360> okay<00:24:24.720> so<00:24:24.780> this<00:24:25.140> is<00:24:25.380> so 00:24:25.670 --> 00:24:25.680 align:start position:0% okay so then there's okay so this is so 00:24:25.680 --> 00:24:27.020 align:start position:0% okay so then there's okay so this is so so<00:24:26.010> now<00:24:26.160> we've<00:24:26.310> talked<00:24:26.520> about<00:24:26.640> makes<00:24:26.850> a<00:24:26.910> mess 00:24:27.020 --> 00:24:27.030 align:start position:0% so now we've talked about makes a mess 00:24:27.030 --> 00:24:28.700 align:start position:0% so now we've talked about makes a mess and<00:24:27.120> we<00:24:27.210> talked<00:24:27.360> about<00:24:27.480> semaphore<00:24:27.960> and<00:24:28.140> we<00:24:28.530> see 00:24:28.700 --> 00:24:28.710 align:start position:0% and we talked about semaphore and we see 00:24:28.710 --> 00:24:30.410 align:start position:0% and we talked about semaphore and we see that<00:24:28.890> we<00:24:29.430> see<00:24:29.580> that<00:24:29.730> in<00:24:29.820> that<00:24:29.940> we<00:24:30.150> have<00:24:30.270> some 00:24:30.410 --> 00:24:30.420 align:start position:0% that we see that in that we have some 00:24:30.420 --> 00:24:31.850 align:start position:0% that we see that in that we have some cool<00:24:30.600> some<00:24:31.140> cool<00:24:31.320> things<00:24:31.500> that<00:24:31.530> we<00:24:31.680> can<00:24:31.800> do 00:24:31.850 --> 00:24:31.860 align:start position:0% cool some cool things that we can do 00:24:31.860 --> 00:24:33.530 align:start position:0% cool some cool things that we can do with<00:24:31.980> these<00:24:32.100> so<00:24:32.820> there's<00:24:33.060> a<00:24:33.120> point<00:24:33.300> and 00:24:33.530 --> 00:24:33.540 align:start position:0% with these so there's a point and 00:24:33.540 --> 00:24:34.790 align:start position:0% with these so there's a point and there's<00:24:33.780> a<00:24:33.870> bunch<00:24:34.080> of<00:24:34.170> like<00:24:34.380> open 00:24:34.790 --> 00:24:34.800 align:start position:0% there's a bunch of like open 00:24:34.800 --> 00:24:36.230 align:start position:0% there's a bunch of like open opportunities<00:24:35.280> to<00:24:35.370> continue<00:24:35.580> this<00:24:35.820> work<00:24:36.000> and 00:24:36.230 --> 00:24:36.240 align:start position:0% opportunities to continue this work and 00:24:36.240 --> 00:24:38.630 align:start position:0% opportunities to continue this work and to<00:24:36.360> do<00:24:36.510> other<00:24:36.900> cool<00:24:37.080> stuff<00:24:37.140> with<00:24:37.410> it<00:24:37.640> for 00:24:38.630 --> 00:24:38.640 align:start position:0% to do other cool stuff with it for 00:24:38.640 --> 00:24:42.260 align:start position:0% to do other cool stuff with it for example<00:24:38.700> we<00:24:39.030> could<00:24:39.120> have<00:24:39.180> a<00:24:40.670> yeah<00:24:41.670> so<00:24:41.880> example 00:24:42.260 --> 00:24:42.270 align:start position:0% example we could have a yeah so example 00:24:42.270 --> 00:24:43.580 align:start position:0% example we could have a yeah so example we<00:24:42.330> could<00:24:42.450> have<00:24:42.510> we<00:24:42.960> could<00:24:43.110> we<00:24:43.320> could<00:24:43.410> build 00:24:43.580 --> 00:24:43.590 align:start position:0% we could have we could we could build 00:24:43.590 --> 00:24:45.440 align:start position:0% we could have we could we could build this<00:24:43.890> kind<00:24:44.190> of<00:24:44.280> group<00:24:44.550> I<00:24:44.850> mean<00:24:45.210> we<00:24:45.360> don't 00:24:45.440 --> 00:24:45.450 align:start position:0% this kind of group I mean we don't 00:24:45.450 --> 00:24:46.940 align:start position:0% this kind of group I mean we don't really<00:24:45.540> have<00:24:45.780> any<00:24:45.900> groups<00:24:46.170> in<00:24:46.350> semaphore<00:24:46.770> yet 00:24:46.940 --> 00:24:46.950 align:start position:0% really have any groups in semaphore yet 00:24:46.950 --> 00:24:48.380 align:start position:0% really have any groups in semaphore yet and<00:24:47.220> it<00:24:47.340> would<00:24:47.430> be<00:24:47.490> nice<00:24:47.640> to<00:24:47.820> have<00:24:47.940> a<00:24:47.970> group<00:24:48.210> of 00:24:48.380 --> 00:24:48.390 align:start position:0% and it would be nice to have a group of 00:24:48.390 --> 00:24:49.970 align:start position:0% and it would be nice to have a group of people<00:24:48.690> who<00:24:48.810> could<00:24:48.990> signal<00:24:49.440> about<00:24:49.650> something 00:24:49.970 --> 00:24:49.980 align:start position:0% people who could signal about something 00:24:49.980 --> 00:24:53.120 align:start position:0% people who could signal about something together<00:24:50.810> and<00:24:51.810> then<00:24:51.960> we<00:24:52.350> can<00:24:52.500> expand<00:24:52.800> it<00:24:52.920> so 00:24:53.120 --> 00:24:53.130 align:start position:0% together and then we can expand it so 00:24:53.130 --> 00:24:55.400 align:start position:0% together and then we can expand it so one<00:24:53.640> way<00:24:53.790> to<00:24:53.850> do<00:24:54.000> that<00:24:54.090> is<00:24:54.240> to<00:24:54.330> have<00:24:54.480> a<00:24:54.540> like<00:24:54.900> we 00:24:55.400 --> 00:24:55.410 align:start position:0% one way to do that is to have a like we 00:24:55.410 --> 00:24:56.540 align:start position:0% one way to do that is to have a like we have<00:24:55.530> to<00:24:55.590> have<00:24:55.680> a<00:24:55.710> way<00:24:55.890> to<00:24:55.920> limit<00:24:56.190> the<00:24:56.400> amount 00:24:56.540 --> 00:24:56.550 align:start position:0% have to have a way to limit the amount 00:24:56.550 --> 00:24:57.890 align:start position:0% have to have a way to limit the amount of<00:24:56.640> people<00:24:56.880> who<00:24:56.940> can<00:24:57.090> join<00:24:57.210> a<00:24:57.270> group<00:24:57.360> otherwise 00:24:57.890 --> 00:24:57.900 align:start position:0% of people who can join a group otherwise 00:24:57.900 --> 00:24:59.300 align:start position:0% of people who can join a group otherwise you<00:24:58.050> can<00:24:58.170> just<00:24:58.200> join<00:24:58.470> the<00:24:58.590> group<00:24:58.740> and<00:24:58.950> and 00:24:59.300 --> 00:24:59.310 align:start position:0% you can just join the group and and 00:24:59.310 --> 00:25:01.400 align:start position:0% you can just join the group and and signal<00:24:59.700> about<00:24:59.820> whatever<00:25:00.000> you<00:25:00.210> want<00:25:00.240> yeah<00:25:01.170> I<00:25:01.200> do 00:25:01.400 --> 00:25:01.410 align:start position:0% signal about whatever you want yeah I do 00:25:01.410 --> 00:25:03.110 align:start position:0% signal about whatever you want yeah I do sock<00:25:01.770> puppet<00:25:02.220> attacks<00:25:02.580> and<00:25:02.790> things<00:25:02.970> like<00:25:03.060> that 00:25:03.110 --> 00:25:03.120 align:start position:0% sock puppet attacks and things like that 00:25:03.120 --> 00:25:04.910 align:start position:0% sock puppet attacks and things like that which<00:25:03.480> we<00:25:03.660> know<00:25:03.840> soft<00:25:04.260> but<00:25:04.410> it's<00:25:04.650> a<00:25:04.710> puppet 00:25:04.910 --> 00:25:04.920 align:start position:0% which we know soft but it's a puppet 00:25:04.920 --> 00:25:06.950 align:start position:0% which we know soft but it's a puppet attack<00:25:05.220> is<00:25:05.400> where<00:25:05.580> it's<00:25:06.030> where<00:25:06.180> like<00:25:06.360> you<00:25:06.780> see 00:25:06.950 --> 00:25:06.960 align:start position:0% attack is where it's where like you see 00:25:06.960 --> 00:25:08.630 align:start position:0% attack is where it's where like you see this<00:25:07.080> really<00:25:07.290> interesting<00:25:07.560> discourse<00:25:08.130> on 00:25:08.630 --> 00:25:08.640 align:start position:0% this really interesting discourse on 00:25:08.640 --> 00:25:10.220 align:start position:0% this really interesting discourse on some<00:25:08.940> social<00:25:09.300> media<00:25:09.330> platform<00:25:09.840> but<00:25:09.960> it<00:25:10.080> turns 00:25:10.220 --> 00:25:10.230 align:start position:0% some social media platform but it turns 00:25:10.230 --> 00:25:11.720 align:start position:0% some social media platform but it turns out<00:25:10.350> it's<00:25:10.500> just<00:25:10.530> one<00:25:10.800> person<00:25:11.130> with<00:25:11.490> many 00:25:11.720 --> 00:25:11.730 align:start position:0% out it's just one person with many 00:25:11.730 --> 00:25:13.250 align:start position:0% out it's just one person with many accounts<00:25:12.090> talking<00:25:12.330> to<00:25:12.420> themselves<00:25:12.570> and<00:25:13.020> it's 00:25:13.250 --> 00:25:13.260 align:start position:0% accounts talking to themselves and it's 00:25:13.260 --> 00:25:14.540 align:start position:0% accounts talking to themselves and it's a<00:25:13.320> way<00:25:13.410> to<00:25:13.470> sort<00:25:13.680> of<00:25:13.740> propagate<00:25:14.070> your<00:25:14.100> ideas 00:25:14.540 --> 00:25:14.550 align:start position:0% a way to sort of propagate your ideas 00:25:14.550 --> 00:25:16.700 align:start position:0% a way to sort of propagate your ideas and<00:25:14.760> force<00:25:15.480> the<00:25:15.690> discourse<00:25:16.110> on<00:25:16.200> the<00:25:16.320> topic<00:25:16.620> in 00:25:16.700 --> 00:25:16.710 align:start position:0% and force the discourse on the topic in 00:25:16.710 --> 00:25:19.430 align:start position:0% and force the discourse on the topic in a<00:25:16.770> certain<00:25:16.980> direction<00:25:17.040> and<00:25:18.080> in<00:25:19.080> general<00:25:19.380> I 00:25:19.430 --> 00:25:19.440 align:start position:0% a certain direction and in general I 00:25:19.440 --> 00:25:21.620 align:start position:0% a certain direction and in general I think<00:25:19.470> this<00:25:19.710> is<00:25:19.800> bad<00:25:19.950> and<00:25:20.030> this<00:25:21.030> is<00:25:21.150> bad<00:25:21.300> and<00:25:21.510> we 00:25:21.620 --> 00:25:21.630 align:start position:0% think this is bad and this is bad and we 00:25:21.630 --> 00:25:23.260 align:start position:0% think this is bad and this is bad and we should<00:25:21.660> we<00:25:22.020> should<00:25:22.170> find<00:25:22.380> a<00:25:22.440> way<00:25:22.500> to<00:25:22.560> stop<00:25:22.770> it 00:25:23.260 --> 00:25:23.270 align:start position:0% should we should find a way to stop it 00:25:23.270 --> 00:25:25.730 align:start position:0% should we should find a way to stop it so<00:25:24.270> one<00:25:24.630> way<00:25:24.720> the<00:25:25.140> way<00:25:25.230> to<00:25:25.290> stop<00:25:25.500> it<00:25:25.620> is<00:25:25.710> to 00:25:25.730 --> 00:25:25.740 align:start position:0% so one way the way to stop it is to 00:25:25.740 --> 00:25:26.930 align:start position:0% so one way the way to stop it is to limit<00:25:26.130> the<00:25:26.190> amount<00:25:26.310> of<00:25:26.400> people<00:25:26.520> who<00:25:26.640> can<00:25:26.790> join 00:25:26.930 --> 00:25:26.940 align:start position:0% limit the amount of people who can join 00:25:26.940 --> 00:25:28.490 align:start position:0% limit the amount of people who can join the<00:25:27.030> conversation<00:25:27.120> but<00:25:27.870> we<00:25:28.020> also<00:25:28.200> want 00:25:28.490 --> 00:25:28.500 align:start position:0% the conversation but we also want 00:25:28.500 --> 00:25:29.270 align:start position:0% the conversation but we also want everyone<00:25:28.590> to<00:25:28.860> be<00:25:28.920> able<00:25:28.980> to<00:25:29.100> join<00:25:29.160> the 00:25:29.270 --> 00:25:29.280 align:start position:0% everyone to be able to join the 00:25:29.280 --> 00:25:31.310 align:start position:0% everyone to be able to join the conversation<00:25:29.760> we<00:25:30.270> just<00:25:30.450> don't<00:25:30.600> we<00:25:30.960> just<00:25:31.110> want 00:25:31.310 --> 00:25:31.320 align:start position:0% conversation we just don't we just want 00:25:31.320 --> 00:25:33.020 align:start position:0% conversation we just don't we just want everyone<00:25:31.590> to<00:25:31.680> be<00:25:31.770> able<00:25:31.860> to<00:25:31.950> join<00:25:32.070> once<00:25:32.340> so 00:25:33.020 --> 00:25:33.030 align:start position:0% everyone to be able to join once so 00:25:33.030 --> 00:25:34.280 align:start position:0% everyone to be able to join once so there's<00:25:33.240> a<00:25:33.330> bunch<00:25:33.420> of<00:25:33.540> ways<00:25:33.690> to<00:25:33.870> think<00:25:33.900> about 00:25:34.280 --> 00:25:34.290 align:start position:0% there's a bunch of ways to think about 00:25:34.290 --> 00:25:35.750 align:start position:0% there's a bunch of ways to think about how<00:25:34.440> we<00:25:34.590> limit<00:25:34.980> people<00:25:35.220> from<00:25:35.340> joining<00:25:35.460> them 00:25:35.750 --> 00:25:35.760 align:start position:0% how we limit people from joining them 00:25:35.760 --> 00:25:38.210 align:start position:0% how we limit people from joining them and<00:25:36.000> one<00:25:36.810> of<00:25:36.840> the<00:25:37.050> and<00:25:37.350> one<00:25:37.740> of<00:25:37.830> the<00:25:37.890> ways<00:25:38.040> is 00:25:38.210 --> 00:25:38.220 align:start position:0% and one of the and one of the ways is 00:25:38.220 --> 00:25:40.340 align:start position:0% and one of the and one of the ways is although<00:25:38.880> it's<00:25:39.060> really<00:25:39.210> it's<00:25:39.600> really<00:25:39.690> it's 00:25:40.340 --> 00:25:40.350 align:start position:0% although it's really it's really it's 00:25:40.350 --> 00:25:42.260 align:start position:0% although it's really it's really it's not<00:25:40.410> very<00:25:40.680> strong<00:25:40.890> it's<00:25:41.190> very<00:25:41.250> weak<00:25:41.550> is<00:25:41.790> to 00:25:42.260 --> 00:25:42.270 align:start position:0% not very strong it's very weak is to 00:25:42.270 --> 00:25:45.470 align:start position:0% not very strong it's very weak is to have<00:25:42.390> like<00:25:42.510> a<00:25:42.540> github<00:25:43.110> based<00:25:44.060> Merkle<00:25:45.060> tree 00:25:45.470 --> 00:25:45.480 align:start position:0% have like a github based Merkle tree 00:25:45.480 --> 00:25:48.560 align:start position:0% have like a github based Merkle tree joining<00:25:46.380> and<00:25:46.860> we<00:25:47.640> have<00:25:47.790> some<00:25:47.910> other<00:25:48.000> and<00:25:48.450> then 00:25:48.560 --> 00:25:48.570 align:start position:0% joining and we have some other and then 00:25:48.570 --> 00:25:49.730 align:start position:0% joining and we have some other and then there's<00:25:48.750> some<00:25:48.840> other<00:25:48.900> ways<00:25:49.110> to<00:25:49.200> do<00:25:49.290> it<00:25:49.320> and<00:25:49.500> I 00:25:49.730 --> 00:25:49.740 align:start position:0% there's some other ways to do it and I 00:25:49.740 --> 00:25:53.150 align:start position:0% there's some other ways to do it and I can<00:25:49.890> talk<00:25:49.980> about<00:25:50.130> those<00:25:50.250> later<00:25:51.830> okay<00:25:52.830> so<00:25:52.890> then 00:25:53.150 --> 00:25:53.160 align:start position:0% can talk about those later okay so then 00:25:53.160 --> 00:25:55.940 align:start position:0% can talk about those later okay so then the<00:25:53.790> next<00:25:53.940> idea<00:25:54.210> is<00:25:54.300> to<00:25:54.510> is<00:25:54.930> to<00:25:55.200> build<00:25:55.740> on<00:25:55.920> top 00:25:55.940 --> 00:25:55.950 align:start position:0% the next idea is to is to build on top 00:25:55.950 --> 00:25:59.630 align:start position:0% the next idea is to is to build on top of<00:25:56.160> some<00:25:56.490> sort<00:25:56.700> of<00:25:57.290> membership<00:25:58.640> requirement 00:25:59.630 --> 00:25:59.640 align:start position:0% of some sort of membership requirement 00:25:59.640 --> 00:26:01.670 align:start position:0% of some sort of membership requirement to<00:26:00.390> build<00:26:00.600> on<00:26:00.720> top<00:26:00.840> of<00:26:00.960> that<00:26:01.020> and<00:26:01.320> to<00:26:01.410> make<00:26:01.530> some 00:26:01.670 --> 00:26:01.680 align:start position:0% to build on top of that and to make some 00:26:01.680 --> 00:26:04.190 align:start position:0% to build on top of that and to make some sort<00:26:01.800> of<00:26:01.890> social<00:26:02.220> media<00:26:02.250> platform<00:26:02.970> so<00:26:03.480> this 00:26:04.190 --> 00:26:04.200 align:start position:0% sort of social media platform so this 00:26:04.200 --> 00:26:05.330 align:start position:0% sort of social media platform so this would<00:26:04.350> be<00:26:04.440> a<00:26:04.470> little<00:26:04.680> bit<00:26:04.770> different<00:26:05.070> than<00:26:05.190> the 00:26:05.330 --> 00:26:05.340 align:start position:0% would be a little bit different than the 00:26:05.340 --> 00:26:06.800 align:start position:0% would be a little bit different than the ones<00:26:05.700> that<00:26:05.820> were<00:26:05.910> used<00:26:05.940> to<00:26:06.150> that<00:26:06.450> instead<00:26:06.750> of 00:26:06.800 --> 00:26:06.810 align:start position:0% ones that were used to that instead of 00:26:06.810 --> 00:26:08.930 align:start position:0% ones that were used to that instead of having<00:26:07.050> like<00:26:07.380> a<00:26:07.620> person<00:26:08.310> who<00:26:08.520> tweets<00:26:08.880> about 00:26:08.930 --> 00:26:08.940 align:start position:0% having like a person who tweets about 00:26:08.940 --> 00:26:10.440 align:start position:0% having like a person who tweets about something<00:26:09.330> we<00:26:09.450> could<00:26:09.600> have<00:26:09.750> a 00:26:10.440 --> 00:26:10.450 align:start position:0% something we could have a 00:26:10.450 --> 00:26:11.609 align:start position:0% something we could have a it's<00:26:10.690> a<00:26:10.749> very<00:26:10.989> impersonal<00:26:11.230> tweet<00:26:11.529> about 00:26:11.609 --> 00:26:11.619 align:start position:0% it's a very impersonal tweet about 00:26:11.619 --> 00:26:13.619 align:start position:0% it's a very impersonal tweet about something<00:26:11.919> we<00:26:12.009> could<00:26:12.129> have<00:26:12.220> a<00:26:12.279> group<00:26:12.570> yeah<00:26:13.570> you 00:26:13.619 --> 00:26:13.629 align:start position:0% something we could have a group yeah you 00:26:13.629 --> 00:26:15.090 align:start position:0% something we could have a group yeah you would<00:26:13.809> join<00:26:13.960> a<00:26:13.989> group<00:26:14.230> and<00:26:14.470> your<00:26:14.559> group<00:26:14.830> would 00:26:15.090 --> 00:26:15.100 align:start position:0% would join a group and your group would 00:26:15.100 --> 00:26:16.950 align:start position:0% would join a group and your group would engage<00:26:15.580> in<00:26:15.850> discourse<00:26:16.179> internally<00:26:16.809> and 00:26:16.950 --> 00:26:16.960 align:start position:0% engage in discourse internally and 00:26:16.960 --> 00:26:18.810 align:start position:0% engage in discourse internally and externally<00:26:17.049> so<00:26:17.919> you<00:26:17.980> could<00:26:18.159> see<00:26:18.340> a<00:26:18.369> group<00:26:18.669> of 00:26:18.810 --> 00:26:18.820 align:start position:0% externally so you could see a group of 00:26:18.820 --> 00:26:20.310 align:start position:0% externally so you could see a group of people<00:26:18.970> discussing<00:26:19.419> something<00:26:19.720> and<00:26:20.019> some<00:26:20.200> of 00:26:20.310 --> 00:26:20.320 align:start position:0% people discussing something and some of 00:26:20.320 --> 00:26:21.479 align:start position:0% people discussing something and some of the<00:26:20.409> people<00:26:20.649> believe<00:26:20.859> something<00:26:20.889> and<00:26:21.309> other 00:26:21.479 --> 00:26:21.489 align:start position:0% the people believe something and other 00:26:21.489 --> 00:26:23.190 align:start position:0% the people believe something and other people<00:26:21.850> believe<00:26:22.090> something<00:26:22.119> else<00:26:22.419> and<00:26:22.929> I 00:26:23.190 --> 00:26:23.200 align:start position:0% people believe something else and I 00:26:23.200 --> 00:26:25.289 align:start position:0% people believe something else and I think<00:26:23.259> that<00:26:23.559> if<00:26:23.649> we<00:26:23.769> remove<00:26:23.919> like<00:26:24.399> the<00:26:24.609> idea<00:26:25.090> of 00:26:25.289 --> 00:26:25.299 align:start position:0% think that if we remove like the idea of 00:26:25.299 --> 00:26:28.739 align:start position:0% think that if we remove like the idea of the<00:26:25.629> self<00:26:26.200> from<00:26:26.499> this<00:26:26.769> I<00:26:27.669> think<00:26:28.179> we<00:26:28.480> remove<00:26:28.659> the 00:26:28.739 --> 00:26:28.749 align:start position:0% the self from this I think we remove the 00:26:28.749 --> 00:26:30.950 align:start position:0% the self from this I think we remove the idea<00:26:28.960> of<00:26:29.019> this<00:26:29.139> self<00:26:29.379> from<00:26:29.529> this<00:26:29.710> then<00:26:29.980> we<00:26:30.340> can 00:26:30.950 --> 00:26:30.960 align:start position:0% idea of this self from this then we can 00:26:30.960 --> 00:26:36.930 align:start position:0% idea of this self from this then we can I<00:26:34.470> think<00:26:35.470> it<00:26:35.649> will<00:26:35.769> lead<00:26:35.950> to<00:26:36.100> like<00:26:36.279> more<00:26:36.519> open 00:26:36.930 --> 00:26:36.940 align:start position:0% I think it will lead to like more open 00:26:36.940 --> 00:26:39.239 align:start position:0% I think it will lead to like more open discourse<00:26:37.330> so<00:26:37.960> so<00:26:38.289> this<00:26:38.409> is<00:26:38.559> like<00:26:38.710> sort<00:26:39.039> of<00:26:39.159> a 00:26:39.239 --> 00:26:39.249 align:start position:0% discourse so so this is like sort of a 00:26:39.249 --> 00:26:41.549 align:start position:0% discourse so so this is like sort of a philosophical<00:26:39.989> tangent<00:26:40.989> that<00:26:41.109> I'm<00:26:41.230> gonna<00:26:41.440> go 00:26:41.549 --> 00:26:41.559 align:start position:0% philosophical tangent that I'm gonna go 00:26:41.559 --> 00:26:43.560 align:start position:0% philosophical tangent that I'm gonna go on<00:26:41.710> but<00:26:41.889> this<00:26:42.399> is<00:26:42.460> this<00:26:42.759> is<00:26:42.909> what<00:26:43.059> I<00:26:43.090> this<00:26:43.179> is 00:26:43.560 --> 00:26:43.570 align:start position:0% on but this is this is what I this is 00:26:43.570 --> 00:26:45.330 align:start position:0% on but this is this is what I this is this<00:26:43.809> is<00:26:43.929> my<00:26:44.109> sort<00:26:44.499> of<00:26:44.590> reasoning<00:26:45.009> for<00:26:45.190> this 00:26:45.330 --> 00:26:45.340 align:start position:0% this is my sort of reasoning for this 00:26:45.340 --> 00:26:48.599 align:start position:0% this is my sort of reasoning for this it's<00:26:46.330> not<00:26:46.419> like<00:26:46.659> in<00:26:47.440> general<00:26:47.710> in<00:26:48.100> life<00:26:48.220> it's 00:26:48.599 --> 00:26:48.609 align:start position:0% it's not like in general in life it's 00:26:48.609 --> 00:26:50.220 align:start position:0% it's not like in general in life it's normally<00:26:49.450> it's<00:26:49.600> easy<00:26:49.749> for<00:26:49.960> people<00:26:50.080> to 00:26:50.220 --> 00:26:50.230 align:start position:0% normally it's easy for people to 00:26:50.230 --> 00:26:52.019 align:start position:0% normally it's easy for people to coordinate<00:26:50.409> inside<00:26:51.220> a<00:26:51.249> group<00:26:51.489> it's<00:26:51.669> easy<00:26:51.820> for 00:26:52.019 --> 00:26:52.029 align:start position:0% coordinate inside a group it's easy for 00:26:52.029 --> 00:26:53.879 align:start position:0% coordinate inside a group it's easy for people<00:26:52.149> to<00:26:52.419> say<00:26:52.629> oh<00:26:52.659> listen<00:26:53.080> I<00:26:53.259> think<00:26:53.320> this<00:26:53.590> and 00:26:53.879 --> 00:26:53.889 align:start position:0% people to say oh listen I think this and 00:26:53.889 --> 00:26:55.739 align:start position:0% people to say oh listen I think this and I<00:26:53.919> think<00:26:54.100> this<00:26:54.279> and<00:26:54.609> people<00:26:55.210> have<00:26:55.450> this<00:26:55.539> sort 00:26:55.739 --> 00:26:55.749 align:start position:0% I think this and people have this sort 00:26:55.749 --> 00:26:57.509 align:start position:0% I think this and people have this sort of<00:26:55.779> healthy<00:26:55.929> discourse<00:26:56.379> and<00:26:56.590> then<00:26:56.739> they<00:26:56.889> agree 00:26:57.509 --> 00:26:57.519 align:start position:0% of healthy discourse and then they agree 00:26:57.519 --> 00:26:59.340 align:start position:0% of healthy discourse and then they agree or<00:26:57.549> disagree<00:26:57.759> and<00:26:58.239> this<00:26:58.720> is<00:26:58.929> this<00:26:59.139> is<00:26:59.320> very 00:26:59.340 --> 00:26:59.350 align:start position:0% or disagree and this is this is very 00:26:59.350 --> 00:27:02.369 align:start position:0% or disagree and this is this is very good<00:26:59.619> for<00:26:59.769> everybody<00:27:00.340> but<00:27:01.090> but<00:27:01.929> sometimes 00:27:02.369 --> 00:27:02.379 align:start position:0% good for everybody but but sometimes 00:27:02.379 --> 00:27:05.190 align:start position:0% good for everybody but but sometimes this<00:27:02.529> is<00:27:02.710> not<00:27:02.859> possible<00:27:03.039> sometimes<00:27:03.940> like<00:27:04.200> for 00:27:05.190 --> 00:27:05.200 align:start position:0% this is not possible sometimes like for 00:27:05.200 --> 00:27:07.590 align:start position:0% this is not possible sometimes like for an<00:27:05.289> example<00:27:05.759> sometimes<00:27:06.759> a<00:27:06.850> minority<00:27:07.330> inside<00:27:07.570> a 00:27:07.590 --> 00:27:07.600 align:start position:0% an example sometimes a minority inside a 00:27:07.600 --> 00:27:09.239 align:start position:0% an example sometimes a minority inside a group<00:27:07.840> can<00:27:08.019> be<00:27:08.049> oppressed<00:27:08.379> by<00:27:08.590> the<00:27:08.710> majority 00:27:09.239 --> 00:27:09.249 align:start position:0% group can be oppressed by the majority 00:27:09.249 --> 00:27:11.190 align:start position:0% group can be oppressed by the majority and<00:27:09.489> the<00:27:09.580> majority<00:27:09.759> can<00:27:10.179> impose<00:27:10.690> some<00:27:10.960> sort<00:27:11.169> of 00:27:11.190 --> 00:27:11.200 align:start position:0% and the majority can impose some sort of 00:27:11.200 --> 00:27:12.720 align:start position:0% and the majority can impose some sort of costs<00:27:11.590> on<00:27:11.710> the<00:27:11.830> minority<00:27:12.070> when<00:27:12.460> they<00:27:12.549> try<00:27:12.700> to 00:27:12.720 --> 00:27:12.730 align:start position:0% costs on the minority when they try to 00:27:12.730 --> 00:27:14.879 align:start position:0% costs on the minority when they try to coordinate<00:27:12.970> and<00:27:13.480> it<00:27:13.899> comes<00:27:14.080> and<00:27:14.559> and<00:27:14.769> this 00:27:14.879 --> 00:27:14.889 align:start position:0% coordinate and it comes and and this 00:27:14.889 --> 00:27:16.680 align:start position:0% coordinate and it comes and and this will<00:27:15.070> lead<00:27:15.279> to<00:27:15.340> a<00:27:15.519> point<00:27:15.879> where<00:27:16.090> with<00:27:16.629> the 00:27:16.680 --> 00:27:16.690 align:start position:0% will lead to a point where with the 00:27:16.690 --> 00:27:19.919 align:start position:0% will lead to a point where with the minority<00:27:17.080> are<00:27:17.200> unable<00:27:17.440> to<00:27:17.590> sort<00:27:18.220> of<00:27:18.929> even 00:27:19.919 --> 00:27:19.929 align:start position:0% minority are unable to sort of even 00:27:19.929 --> 00:27:21.029 align:start position:0% minority are unable to sort of even admit<00:27:20.169> that<00:27:20.200> they're<00:27:20.499> part<00:27:20.710> of<00:27:20.769> the<00:27:20.859> minority 00:27:21.029 --> 00:27:21.039 align:start position:0% admit that they're part of the minority 00:27:21.039 --> 00:27:23.430 align:start position:0% admit that they're part of the minority because<00:27:21.789> they're<00:27:22.239> afraid<00:27:22.539> of<00:27:22.629> oppression<00:27:23.169> or 00:27:23.430 --> 00:27:23.440 align:start position:0% because they're afraid of oppression or 00:27:23.440 --> 00:27:24.779 align:start position:0% because they're afraid of oppression or something<00:27:23.679> like<00:27:23.830> that<00:27:23.980> or<00:27:24.369> they're<00:27:24.489> afraid<00:27:24.669> of 00:27:24.779 --> 00:27:24.789 align:start position:0% something like that or they're afraid of 00:27:24.789 --> 00:27:26.580 align:start position:0% something like that or they're afraid of some<00:27:25.029> sort<00:27:25.210> of<00:27:25.239> consequence<00:27:25.779> for<00:27:26.080> this<00:27:26.230> for 00:27:26.580 --> 00:27:26.590 align:start position:0% some sort of consequence for this for 00:27:26.590 --> 00:27:28.529 align:start position:0% some sort of consequence for this for this<00:27:26.710> admission<00:27:27.009> and<00:27:27.369> there's<00:27:27.820> been<00:27:27.940> a<00:27:27.970> bunch 00:27:28.529 --> 00:27:28.539 align:start position:0% this admission and there's been a bunch 00:27:28.539 --> 00:27:29.909 align:start position:0% this admission and there's been a bunch of<00:27:28.690> rights<00:27:28.960> movements<00:27:29.470> that<00:27:29.559> I've<00:27:29.710> been 00:27:29.909 --> 00:27:29.919 align:start position:0% of rights movements that I've been 00:27:29.919 --> 00:27:31.649 align:start position:0% of rights movements that I've been around<00:27:30.159> that<00:27:30.730> have<00:27:30.850> standard<00:27:31.149> around<00:27:31.359> people 00:27:31.649 --> 00:27:31.659 align:start position:0% around that have standard around people 00:27:31.659 --> 00:27:33.690 align:start position:0% around that have standard around people saying<00:27:31.929> that<00:27:32.139> oh<00:27:32.320> I'm<00:27:33.070> part<00:27:33.279> of<00:27:33.309> this<00:27:33.429> group 00:27:33.690 --> 00:27:33.700 align:start position:0% saying that oh I'm part of this group 00:27:33.700 --> 00:27:36.060 align:start position:0% saying that oh I'm part of this group and<00:27:33.909> and<00:27:34.899> revealing<00:27:35.259> that<00:27:35.470> and<00:27:35.710> paying<00:27:35.889> this 00:27:36.060 --> 00:27:36.070 align:start position:0% and and revealing that and paying this 00:27:36.070 --> 00:27:37.950 align:start position:0% and and revealing that and paying this kind<00:27:36.340> of<00:27:36.399> high<00:27:36.549> social<00:27:36.789> costs<00:27:37.210> but<00:27:37.779> that's 00:27:37.950 --> 00:27:37.960 align:start position:0% kind of high social costs but that's 00:27:37.960 --> 00:27:40.139 align:start position:0% kind of high social costs but that's like<00:27:38.259> not<00:27:38.679> very<00:27:38.889> good<00:27:39.100> for<00:27:39.309> everybody<00:27:39.850> I<00:27:39.909> mean 00:27:40.139 --> 00:27:40.149 align:start position:0% like not very good for everybody I mean 00:27:40.149 --> 00:27:41.580 align:start position:0% like not very good for everybody I mean there<00:27:40.749> should<00:27:40.779> be<00:27:40.989> a<00:27:41.019> way<00:27:41.169> for<00:27:41.350> people<00:27:41.470> to 00:27:41.580 --> 00:27:41.590 align:start position:0% there should be a way for people to 00:27:41.590 --> 00:27:42.779 align:start position:0% there should be a way for people to coordinate<00:27:41.830> without<00:27:42.279> having<00:27:42.489> to<00:27:42.580> pay<00:27:42.669> this 00:27:42.779 --> 00:27:42.789 align:start position:0% coordinate without having to pay this 00:27:42.789 --> 00:27:44.399 align:start position:0% coordinate without having to pay this high<00:27:42.940> cost<00:27:43.179> and<00:27:43.359> one<00:27:43.869> of<00:27:43.960> the<00:27:44.019> ways<00:27:44.169> for<00:27:44.320> people 00:27:44.399 --> 00:27:44.409 align:start position:0% high cost and one of the ways for people 00:27:44.409 --> 00:27:45.690 align:start position:0% high cost and one of the ways for people to<00:27:44.529> coordinate<00:27:44.919> and<00:27:45.100> not<00:27:45.220> pay<00:27:45.309> this<00:27:45.399> high<00:27:45.549> cost 00:27:45.690 --> 00:27:45.700 align:start position:0% to coordinate and not pay this high cost 00:27:45.700 --> 00:27:46.830 align:start position:0% to coordinate and not pay this high cost is<00:27:45.940> to<00:27:46.090> make<00:27:46.210> these<00:27:46.359> like<00:27:46.570> anonymous 00:27:46.830 --> 00:27:46.840 align:start position:0% is to make these like anonymous 00:27:46.840 --> 00:27:48.629 align:start position:0% is to make these like anonymous signalling<00:27:47.409> groups<00:27:47.619> yeah<00:27:48.070> and<00:27:48.220> people<00:27:48.340> can 00:27:48.629 --> 00:27:48.639 align:start position:0% signalling groups yeah and people can 00:27:48.639 --> 00:27:50.639 align:start position:0% signalling groups yeah and people can say<00:27:48.820> it<00:27:48.940> can<00:27:49.090> can<00:27:49.389> anonymously<00:27:49.869> say<00:27:50.080> oh<00:27:50.259> I'm 00:27:50.639 --> 00:27:50.649 align:start position:0% say it can can anonymously say oh I'm 00:27:50.649 --> 00:27:52.349 align:start position:0% say it can can anonymously say oh I'm part<00:27:50.859> of<00:27:50.919> this<00:27:51.009> group<00:27:51.220> without<00:27:51.789> revealing 00:27:52.349 --> 00:27:52.359 align:start position:0% part of this group without revealing 00:27:52.359 --> 00:27:54.060 align:start position:0% part of this group without revealing which<00:27:52.779> part<00:27:53.139> of<00:27:53.230> which<00:27:53.499> member<00:27:53.769> of<00:27:53.799> the<00:27:53.889> group 00:27:54.060 --> 00:27:54.070 align:start position:0% which part of which member of the group 00:27:54.070 --> 00:27:56.789 align:start position:0% which part of which member of the group they<00:27:54.190> are<00:27:54.220> so<00:27:54.700> they<00:27:54.850> they<00:27:55.389> they<00:27:55.720> can't<00:27:55.960> be<00:27:56.109> they 00:27:56.789 --> 00:27:56.799 align:start position:0% they are so they they they can't be they 00:27:56.799 --> 00:27:57.989 align:start position:0% they are so they they they can't be they can't<00:27:56.980> be<00:27:57.070> the<00:27:57.159> victim<00:27:57.399> of<00:27:57.489> some<00:27:57.730> kind<00:27:57.940> of 00:27:57.989 --> 00:27:57.999 align:start position:0% can't be the victim of some kind of 00:27:57.999 --> 00:28:00.149 align:start position:0% can't be the victim of some kind of oppression<00:27:58.239> because<00:27:58.929> they<00:27:59.019> didn't<00:27:59.289> they<00:27:59.440> or 00:28:00.149 --> 00:28:00.159 align:start position:0% oppression because they didn't they or 00:28:00.159 --> 00:28:01.349 align:start position:0% oppression because they didn't they or it's<00:28:00.369> more<00:28:00.519> difficult<00:28:00.700> for<00:28:00.999> them<00:28:01.119> to<00:28:01.149> be<00:28:01.269> a 00:28:01.349 --> 00:28:01.359 align:start position:0% it's more difficult for them to be a 00:28:01.359 --> 00:28:03.259 align:start position:0% it's more difficult for them to be a victim<00:28:01.659> of<00:28:01.779> some<00:28:02.019> kind<00:28:02.200> of<00:28:02.259> oppression<00:28:02.440> and 00:28:03.259 --> 00:28:03.269 align:start position:0% victim of some kind of oppression and 00:28:03.269 --> 00:28:05.489 align:start position:0% victim of some kind of oppression and they're<00:28:04.269> also<00:28:04.419> free<00:28:04.659> to<00:28:04.899> sort<00:28:05.169> of<00:28:05.200> express 00:28:05.489 --> 00:28:05.499 align:start position:0% they're also free to sort of express 00:28:05.499 --> 00:28:07.859 align:start position:0% they're also free to sort of express this<00:28:05.710> belief<00:28:05.980> and<00:28:06.639> this<00:28:07.359> I<00:28:07.570> think<00:28:07.600> is<00:28:07.809> a 00:28:07.859 --> 00:28:07.869 align:start position:0% this belief and this I think is a 00:28:07.869 --> 00:28:08.940 align:start position:0% this belief and this I think is a healthy<00:28:08.200> thing<00:28:08.289> for<00:28:08.470> society<00:28:08.559> in<00:28:08.889> general 00:28:08.940 --> 00:28:08.950 align:start position:0% healthy thing for society in general 00:28:08.950 --> 00:28:11.489 align:start position:0% healthy thing for society in general because<00:28:09.489> people<00:28:10.029> should<00:28:10.570> be<00:28:10.659> free<00:28:10.809> to<00:28:11.080> sort<00:28:11.440> of 00:28:11.489 --> 00:28:11.499 align:start position:0% because people should be free to sort of 00:28:11.499 --> 00:28:12.869 align:start position:0% because people should be free to sort of coordinate<00:28:11.859> with<00:28:12.220> each<00:28:12.249> other<00:28:12.489> and<00:28:12.700> express 00:28:12.869 --> 00:28:12.879 align:start position:0% coordinate with each other and express 00:28:12.879 --> 00:28:15.479 align:start position:0% coordinate with each other and express their<00:28:13.090> beliefs<00:28:13.330> and<00:28:13.629> I<00:28:13.899> think<00:28:14.769> that<00:28:14.919> when<00:28:15.190> yeah 00:28:15.479 --> 00:28:15.489 align:start position:0% their beliefs and I think that when yeah 00:28:15.489 --> 00:28:18.029 align:start position:0% their beliefs and I think that when yeah yeah<00:28:16.269> okay<00:28:16.989> so<00:28:17.049> that's<00:28:17.350> that's<00:28:17.529> like<00:28:17.769> the<00:28:17.919> end 00:28:18.029 --> 00:28:18.039 align:start position:0% yeah okay so that's that's like the end 00:28:18.039 --> 00:28:20.070 align:start position:0% yeah okay so that's that's like the end of<00:28:18.100> the<00:28:18.220> philosophical<00:28:18.609> tangent<00:28:19.269> but<00:28:19.539> that's 00:28:20.070 --> 00:28:20.080 align:start position:0% of the philosophical tangent but that's 00:28:20.080 --> 00:28:22.080 align:start position:0% of the philosophical tangent but that's that's<00:28:20.379> that's<00:28:20.710> that's<00:28:21.309> why<00:28:21.549> we<00:28:21.759> need<00:28:21.940> to<00:28:21.970> have 00:28:22.080 --> 00:28:22.090 align:start position:0% that's that's that's why we need to have 00:28:22.090 --> 00:28:24.480 align:start position:0% that's that's that's why we need to have these<00:28:22.419> sort<00:28:22.659> of<00:28:22.720> anonymity<00:28:23.679> system<00:28:24.129> or 00:28:24.480 --> 00:28:24.490 align:start position:0% these sort of anonymity system or 00:28:24.490 --> 00:28:26.369 align:start position:0% these sort of anonymity system or systems<00:28:25.179> with<00:28:25.330> strong<00:28:25.539> anonymity<00:28:25.929> properties 00:28:26.369 --> 00:28:26.379 align:start position:0% systems with strong anonymity properties 00:28:26.379 --> 00:28:28.409 align:start position:0% systems with strong anonymity properties so<00:28:26.740> I'm<00:28:26.889> very<00:28:27.070> interested<00:28:27.369> in<00:28:27.639> people<00:28:27.730> are<00:28:27.940> in 00:28:28.409 --> 00:28:28.419 align:start position:0% so I'm very interested in people are in 00:28:28.419 --> 00:28:29.730 align:start position:0% so I'm very interested in people are in people<00:28:28.690> who<00:28:28.779> are<00:28:28.929> interested<00:28:29.440> in<00:28:29.499> working<00:28:29.619> on 00:28:29.730 --> 00:28:29.740 align:start position:0% people who are interested in working on 00:28:29.740 --> 00:28:31.470 align:start position:0% people who are interested in working on this<00:28:29.889> in<00:28:30.220> billing<00:28:30.789> things<00:28:30.970> with<00:28:31.090> time<00:28:31.210> before 00:28:31.470 --> 00:28:31.480 align:start position:0% this in billing things with time before 00:28:31.480 --> 00:28:32.909 align:start position:0% this in billing things with time before and<00:28:31.690> please<00:28:32.049> talk<00:28:32.200> to<00:28:32.259> me<00:28:32.379> afterwards<00:28:32.799> if<00:28:32.860> you 00:28:32.909 --> 00:28:32.919 align:start position:0% and please talk to me afterwards if you 00:28:32.919 --> 00:28:35.549 align:start position:0% and please talk to me afterwards if you are<00:28:33.159> there's<00:28:33.460> a<00:28:33.519> bunch<00:28:33.909> of<00:28:34.059> but<00:28:34.929> there's<00:28:35.110> a<00:28:35.169> few 00:28:35.549 --> 00:28:35.559 align:start position:0% are there's a bunch of but there's a few 00:28:35.559 --> 00:28:37.529 align:start position:0% are there's a bunch of but there's a few people<00:28:35.919> working<00:28:36.070> on<00:28:36.309> this<00:28:36.460> and<00:28:36.820> we're<00:28:37.299> happy 00:28:37.529 --> 00:28:37.539 align:start position:0% people working on this and we're happy 00:28:37.539 --> 00:28:39.480 align:start position:0% people working on this and we're happy for<00:28:37.659> other<00:28:38.019> people<00:28:38.259> to<00:28:38.379> join<00:28:38.649> and<00:28:38.950> there's<00:28:39.399> a 00:28:39.480 --> 00:28:39.490 align:start position:0% for other people to join and there's a 00:28:39.490 --> 00:28:46.799 align:start position:0% for other people to join and there's a lot<00:28:39.639> of<00:28:39.789> open<00:28:40.059> opportunities<00:28:42.659> so<00:28:44.399> so<00:28:45.399> then<00:28:45.809> so 00:28:46.799 --> 00:28:46.809 align:start position:0% lot of open opportunities so so then so 00:28:46.809 --> 00:28:48.029 align:start position:0% lot of open opportunities so so then so then<00:28:46.840> we<00:28:47.080> can<00:28:47.169> have<00:28:47.230> anonymous<00:28:47.440> credential 00:28:48.029 --> 00:28:48.039 align:start position:0% then we can have anonymous credential 00:28:48.039 --> 00:28:49.769 align:start position:0% then we can have anonymous credential systems<00:28:48.369> and<00:28:48.639> this<00:28:48.700> is<00:28:48.879> where<00:28:49.059> you<00:28:49.210> can<00:28:49.419> just 00:28:49.769 --> 00:28:49.779 align:start position:0% systems and this is where you can just 00:28:49.779 --> 00:28:51.029 align:start position:0% systems and this is where you can just sign<00:28:49.960> into<00:28:50.289> something<00:28:50.590> without<00:28:50.710> revealing 00:28:51.029 --> 00:28:51.039 align:start position:0% sign into something without revealing 00:28:51.039 --> 00:28:53.220 align:start position:0% sign into something without revealing who<00:28:51.340> you<00:28:51.490> are<00:28:51.639> and<00:28:52.059> we<00:28:52.389> can<00:28:52.570> and<00:28:52.809> that's<00:28:53.139> a 00:28:53.220 --> 00:28:53.230 align:start position:0% who you are and we can and that's a 00:28:53.230 --> 00:28:54.799 align:start position:0% who you are and we can and that's a whole<00:28:53.379> other<00:28:53.440> use<00:28:53.769> case<00:28:53.980> that<00:28:54.009> we<00:28:54.190> can<00:28:54.369> have 00:28:54.799 --> 00:28:54.809 align:start position:0% whole other use case that we can have 00:28:54.809 --> 00:28:57.119 align:start position:0% whole other use case that we can have then<00:28:55.809> we<00:28:55.899> can<00:28:55.990> have<00:28:56.080> reputation<00:28:56.559> systems<00:28:56.889> and 00:28:57.119 --> 00:28:57.129 align:start position:0% then we can have reputation systems and 00:28:57.129 --> 00:28:59.100 align:start position:0% then we can have reputation systems and it's<00:28:57.549> in<00:28:57.820> fact<00:28:57.970> we<00:28:58.119> found<00:28:58.539> a<00:28:58.570> way<00:28:58.659> to<00:28:58.720> build<00:28:58.990> a 00:28:59.100 --> 00:28:59.110 align:start position:0% it's in fact we found a way to build a 00:28:59.110 --> 00:29:00.690 align:start position:0% it's in fact we found a way to build a reputation<00:28:59.320> peace<00:28:59.679> system<00:29:00.039> where<00:29:00.190> where<00:29:00.610> you 00:29:00.690 --> 00:29:00.700 align:start position:0% reputation peace system where where you 00:29:00.700 --> 00:29:03.269 align:start position:0% reputation peace system where where you can<00:29:00.850> kind<00:29:01.809> of<00:29:01.899> exclude<00:29:02.769> someone<00:29:02.950> from<00:29:03.129> the 00:29:03.269 --> 00:29:03.279 align:start position:0% can kind of exclude someone from the 00:29:03.279 --> 00:29:06.989 align:start position:0% can kind of exclude someone from the group<00:29:03.429> if<00:29:03.580> they<00:29:03.610> if<00:29:04.450> they<00:29:05.039> if<00:29:06.039> they<00:29:06.309> if<00:29:06.820> they 00:29:06.989 --> 00:29:06.999 align:start position:0% group if they if they if they if they 00:29:06.999 --> 00:29:08.190 align:start position:0% group if they if they if they if they break<00:29:07.210> some<00:29:07.419> rules<00:29:07.539> so<00:29:07.720> let's<00:29:07.749> say<00:29:08.019> that<00:29:08.139> I 00:29:08.190 --> 00:29:08.200 align:start position:0% break some rules so let's say that I 00:29:08.200 --> 00:29:09.899 align:start position:0% break some rules so let's say that I have<00:29:08.379> like<00:29:08.529> a<00:29:08.559> VPN<00:29:08.980> server<00:29:09.190> and<00:29:09.399> I'm<00:29:09.490> like<00:29:09.639> I 00:29:09.899 --> 00:29:09.909 align:start position:0% have like a VPN server and I'm like I 00:29:09.909 --> 00:29:11.879 align:start position:0% have like a VPN server and I'm like I let<00:29:10.450> everybody<00:29:10.690> use<00:29:10.899> my<00:29:11.139> PP<00:29:11.379> on<00:29:11.470> server<00:29:11.740> who's 00:29:11.879 --> 00:29:11.889 align:start position:0% let everybody use my PP on server who's 00:29:11.889 --> 00:29:13.440 align:start position:0% let everybody use my PP on server who's in<00:29:12.039> this<00:29:12.190> it<00:29:12.369> was<00:29:12.460> in<00:29:12.580> this<00:29:12.669> room<00:29:12.850> I<00:29:13.029> at<00:29:13.240> the<00:29:13.330> end 00:29:13.440 --> 00:29:13.450 align:start position:0% in this it was in this room I at the end 00:29:13.450 --> 00:29:14.669 align:start position:0% in this it was in this room I at the end of<00:29:13.509> the<00:29:13.659> thing<00:29:13.840> I<00:29:13.960> just<00:29:13.990> go<00:29:14.350> around<00:29:14.559> and<00:29:14.649> I 00:29:14.669 --> 00:29:14.679 align:start position:0% of the thing I just go around and I 00:29:14.679 --> 00:29:15.960 align:start position:0% of the thing I just go around and I collect<00:29:14.919> everyone's<00:29:15.190> private<00:29:15.460> key<00:29:15.580> and<00:29:15.759> I<00:29:15.820> say 00:29:15.960 --> 00:29:15.970 align:start position:0% collect everyone's private key and I say 00:29:15.970 --> 00:29:17.489 align:start position:0% collect everyone's private key and I say ok<00:29:16.149> everyone's<00:29:16.480> allowed<00:29:16.600> to<00:29:16.720> join<00:29:16.899> but<00:29:17.350> then 00:29:17.489 --> 00:29:17.499 align:start position:0% ok everyone's allowed to join but then 00:29:17.499 --> 00:29:19.710 align:start position:0% ok everyone's allowed to join but then or<00:29:17.830> some<00:29:18.340> someone<00:29:18.669> sites<00:29:18.850> to<00:29:18.940> use<00:29:19.090> this<00:29:19.240> VPN 00:29:19.710 --> 00:29:19.720 align:start position:0% or some someone sites to use this VPN 00:29:19.720 --> 00:29:21.060 align:start position:0% or some someone sites to use this VPN all<00:29:19.899> the<00:29:19.990> time<00:29:20.139> and<00:29:20.409> they<00:29:20.470> use<00:29:20.649> too<00:29:20.889> much<00:29:21.009> of 00:29:21.060 --> 00:29:21.070 align:start position:0% all the time and they use too much of 00:29:21.070 --> 00:29:22.529 align:start position:0% all the time and they use too much of the<00:29:21.220> bandwidth<00:29:21.549> and<00:29:21.879> I<00:29:21.970> have<00:29:22.090> to<00:29:22.179> remove<00:29:22.389> them 00:29:22.529 --> 00:29:22.539 align:start position:0% the bandwidth and I have to remove them 00:29:22.539 --> 00:29:24.330 align:start position:0% the bandwidth and I have to remove them from<00:29:22.690> the<00:29:22.779> system<00:29:22.929> so<00:29:23.470> there's<00:29:23.679> this<00:29:23.950> kind<00:29:24.220> of 00:29:24.330 --> 00:29:24.340 align:start position:0% from the system so there's this kind of 00:29:24.340 --> 00:29:25.710 align:start position:0% from the system so there's this kind of talks<00:29:24.700> that<00:29:24.850> this<00:29:24.999> post<00:29:25.210> here<00:29:25.389> talks<00:29:25.629> about 00:29:25.710 --> 00:29:25.720 align:start position:0% talks that this post here talks about 00:29:25.720 --> 00:29:28.249 align:start position:0% talks that this post here talks about how<00:29:26.259> we<00:29:26.320> can<00:29:26.529> do<00:29:26.619> that<00:29:26.769> and<00:29:26.950> what<00:29:27.789> we<00:29:27.879> can<00:29:27.999> do 00:29:28.249 --> 00:29:28.259 align:start position:0% how we can do that and what we can do 00:29:28.259 --> 00:29:30.840 align:start position:0% how we can do that and what we can do yeah<00:29:29.289> so<00:29:29.409> this<00:29:29.559> this<00:29:29.799> post<00:29:30.039> is<00:29:30.279> each<00:29:30.519> research 00:29:30.840 --> 00:29:30.850 align:start position:0% yeah so this this post is each research 00:29:30.850 --> 00:29:32.100 align:start position:0% yeah so this this post is each research post<00:29:31.090> talks<00:29:31.240> about<00:29:31.389> how<00:29:31.480> we<00:29:31.570> can<00:29:31.690> do<00:29:31.749> that<00:29:31.869> and 00:29:32.100 --> 00:29:32.110 align:start position:0% post talks about how we can do that and 00:29:32.110 --> 00:29:34.950 align:start position:0% post talks about how we can do that and and<00:29:32.350> other<00:29:33.159> things<00:29:33.399> about<00:29:33.519> that<00:29:33.700> and<00:29:33.909> yeah<00:29:34.779> so 00:29:34.950 --> 00:29:34.960 align:start position:0% and other things about that and yeah so 00:29:34.960 --> 00:29:36.210 align:start position:0% and other things about that and yeah so it's<00:29:35.139> sort<00:29:35.320> of<00:29:35.379> the<00:29:35.470> limits<00:29:35.740> and<00:29:35.860> trade-offs 00:29:36.210 --> 00:29:36.220 align:start position:0% it's sort of the limits and trade-offs 00:29:36.220 --> 00:29:38.700 align:start position:0% it's sort of the limits and trade-offs and<00:29:36.399> whether<00:29:36.940> it<00:29:37.029> is<00:29:37.119> useful<00:29:37.539> or<00:29:37.659> not<00:29:37.779> no<00:29:38.529> this 00:29:38.700 --> 00:29:38.710 align:start position:0% and whether it is useful or not no this 00:29:38.710 --> 00:29:41.730 align:start position:0% and whether it is useful or not no this is<00:29:40.259> definition<00:29:41.259> that<00:29:41.320> we<00:29:41.409> can<00:29:41.529> go<00:29:41.590> in<00:29:41.710> with 00:29:41.730 --> 00:29:41.740 align:start position:0% is definition that we can go in with 00:29:41.740 --> 00:29:43.680 align:start position:0% is definition that we can go in with some<00:29:41.950> four<00:29:42.100> seven<00:29:42.369> four<00:29:42.519> okay<00:29:43.210> so<00:29:43.240> there's<00:29:43.600> a 00:29:43.680 --> 00:29:43.690 align:start position:0% some four seven four okay so there's a 00:29:43.690 --> 00:29:44.789 align:start position:0% some four seven four okay so there's a bunch<00:29:43.809> more<00:29:44.049> stuff<00:29:44.169> we<00:29:44.350> can<00:29:44.470> build<00:29:44.559> with<00:29:44.649> some 00:29:44.789 --> 00:29:44.799 align:start position:0% bunch more stuff we can build with some 00:29:44.799 --> 00:29:46.950 align:start position:0% bunch more stuff we can build with some four<00:29:44.980> and<00:29:45.070> I<00:29:45.100> kind<00:29:45.279> of<00:29:45.340> think<00:29:45.549> that<00:29:45.669> like<00:29:45.999> not 00:29:46.950 --> 00:29:46.960 align:start position:0% four and I kind of think that like not 00:29:46.960 --> 00:29:48.269 align:start position:0% four and I kind of think that like not enough<00:29:47.139> people<00:29:47.200> are<00:29:47.350> working<00:29:47.619> on<00:29:47.679> this<00:29:47.769> so<00:29:47.980> I'm 00:29:48.269 --> 00:29:48.279 align:start position:0% enough people are working on this so I'm 00:29:48.279 --> 00:29:49.769 align:start position:0% enough people are working on this so I'm happy<00:29:48.429> to<00:29:48.639> sort<00:29:49.210> of<00:29:49.299> talk<00:29:49.419> with<00:29:49.600> people 00:29:49.769 --> 00:29:49.779 align:start position:0% happy to sort of talk with people 00:29:49.779 --> 00:29:51.389 align:start position:0% happy to sort of talk with people afterwards<00:29:49.990> or<00:29:50.619> during<00:29:50.950> the<00:29:51.009> question<00:29:51.249> answer 00:29:51.389 --> 00:29:51.399 align:start position:0% afterwards or during the question answer 00:29:51.399 --> 00:29:54.090 align:start position:0% afterwards or during the question answer session<00:29:51.519> about<00:29:51.970> this<00:29:52.119> and<00:29:52.409> yeah<00:29:53.409> hopefully<00:29:53.860> we 00:29:54.090 --> 00:29:54.100 align:start position:0% session about this and yeah hopefully we 00:29:54.100 --> 00:29:57.289 align:start position:0% session about this and yeah hopefully we can<00:29:54.249> sort<00:29:54.700> of<00:29:54.759> do<00:29:54.879> some<00:29:54.999> work<00:29:55.119> together<00:29:55.769> okay 00:29:57.289 --> 00:29:57.299 align:start position:0% can sort of do some work together okay 00:29:57.299 --> 00:30:00.090 align:start position:0% can sort of do some work together okay okay<00:29:58.299> so<00:29:58.360> then<00:29:58.690> also<00:29:59.259> I<00:29:59.409> want<00:29:59.619> to<00:29:59.710> promote<00:29:59.860> this 00:30:00.090 --> 00:30:00.100 align:start position:0% okay so then also I want to promote this 00:30:00.100 --> 00:30:04.049 align:start position:0% okay so then also I want to promote this ethnics<00:30:00.759> so<00:30:01.090> as<00:30:01.330> Eric<00:30:01.539> said<00:30:01.659> SMX<00:30:02.590> is<00:30:03.059> this 00:30:04.049 --> 00:30:04.059 align:start position:0% ethnics so as Eric said SMX is this 00:30:04.059 --> 00:30:07.320 align:start position:0% ethnics so as Eric said SMX is this theorem<00:30:04.899> snark<00:30:05.799> project<00:30:06.159> that's<00:30:06.279> funded<00:30:06.730> by 00:30:07.320 --> 00:30:07.330 align:start position:0% theorem snark project that's funded by 00:30:07.330 --> 00:30:08.940 align:start position:0% theorem snark project that's funded by the<00:30:07.419> ATM<00:30:07.720> foundation<00:30:08.139> that<00:30:08.289> are<00:30:08.409> moving 00:30:08.940 --> 00:30:08.950 align:start position:0% the ATM foundation that are moving 00:30:08.950 --> 00:30:10.700 align:start position:0% the ATM foundation that are moving forward<00:30:09.190> with<00:30:09.279> some<00:30:09.309> of<00:30:09.549> the<00:30:09.669> the<00:30:10.029> lower-level 00:30:10.700 --> 00:30:10.710 align:start position:0% forward with some of the the lower-level 00:30:10.710 --> 00:30:12.629 align:start position:0% forward with some of the the lower-level equip<00:30:11.710> the<00:30:11.799> graphic<00:30:12.070> primitives<00:30:12.429> that<00:30:12.549> we 00:30:12.629 --> 00:30:12.639 align:start position:0% equip the graphic primitives that we 00:30:12.639 --> 00:30:14.249 align:start position:0% equip the graphic primitives that we need<00:30:12.789> and<00:30:13.450> they're<00:30:13.659> doing<00:30:13.869> a<00:30:13.899> bunch<00:30:14.080> of<00:30:14.110> good 00:30:14.249 --> 00:30:14.259 align:start position:0% need and they're doing a bunch of good 00:30:14.259 --> 00:30:15.930 align:start position:0% need and they're doing a bunch of good stuff<00:30:14.289> and<00:30:14.679> if<00:30:14.740> anyone<00:30:15.070> has<00:30:15.220> some<00:30:15.340> C++ 00:30:15.930 --> 00:30:15.940 align:start position:0% stuff and if anyone has some C++ 00:30:15.940 --> 00:30:17.730 align:start position:0% stuff and if anyone has some C++ experience<00:30:16.659> or<00:30:16.899> wants<00:30:17.379> to<00:30:17.470> learn<00:30:17.619> a<00:30:17.649> little 00:30:17.730 --> 00:30:17.740 align:start position:0% experience or wants to learn a little 00:30:17.740 --> 00:30:19.409 align:start position:0% experience or wants to learn a little bit<00:30:17.860> about<00:30:18.070> snacks<00:30:18.369> that<00:30:18.999> this<00:30:19.149> would<00:30:19.299> be<00:30:19.360> a 00:30:19.409 --> 00:30:19.419 align:start position:0% bit about snacks that this would be a 00:30:19.419 --> 00:30:20.970 align:start position:0% bit about snacks that this would be a good<00:30:19.539> place<00:30:19.690> to<00:30:19.960> sort<00:30:20.350> of<00:30:20.409> contribute 00:30:20.970 --> 00:30:20.980 align:start position:0% good place to sort of contribute 00:30:20.980 --> 00:30:24.180 align:start position:0% good place to sort of contribute there's<00:30:21.220> also<00:30:21.369> Socrates<00:30:22.029> and<00:30:22.269> circum<00:30:22.690> I<00:30:23.190> I 00:30:24.180 --> 00:30:24.190 align:start position:0% there's also Socrates and circum I I 00:30:24.190 --> 00:30:28.799 align:start position:0% there's also Socrates and circum I I think<00:30:24.340> I<00:30:24.519> have<00:30:24.669> circum<00:30:24.999> later<00:30:27.059> but<00:30:28.059> I'm<00:30:28.299> sorry 00:30:28.799 --> 00:30:28.809 align:start position:0% think I have circum later but I'm sorry 00:30:28.809 --> 00:30:32.039 align:start position:0% think I have circum later but I'm sorry Socrates<00:30:30.210> it's<00:30:31.210> also<00:30:31.360> a<00:30:31.480> cool<00:30:31.659> project<00:30:31.809> I 00:30:32.039 --> 00:30:32.049 align:start position:0% Socrates it's also a cool project I 00:30:32.049 --> 00:30:37.049 align:start position:0% Socrates it's also a cool project I maybe<00:30:32.440> had<00:30:32.649> them<00:30:32.740> later<00:30:32.889> so<00:30:35.519> so<00:30:36.519> we<00:30:36.639> also<00:30:36.820> use<00:30:37.029> a 00:30:37.049 --> 00:30:37.059 align:start position:0% maybe had them later so so we also use a 00:30:37.059 --> 00:30:38.400 align:start position:0% maybe had them later so so we also use a or<00:30:37.539> C<00:30:37.659> 20<00:30:37.869> tokens 00:30:38.400 --> 00:30:38.410 align:start position:0% or C 20 tokens 00:30:38.410 --> 00:30:39.840 align:start position:0% or C 20 tokens oh<00:30:38.440> yeah<00:30:38.860> so<00:30:39.040> this<00:30:39.130> is<00:30:39.190> other<00:30:39.430> things<00:30:39.670> we<00:30:39.760> can 00:30:39.840 --> 00:30:39.850 align:start position:0% oh yeah so this is other things we can 00:30:39.850 --> 00:30:42.630 align:start position:0% oh yeah so this is other things we can fix<00:30:40.030> with<00:30:40.090> Maximus<00:30:40.450> so<00:30:40.720> we<00:30:40.870> could<00:30:41.430> make<00:30:42.430> a<00:30:42.460> pull 00:30:42.630 --> 00:30:42.640 align:start position:0% fix with Maximus so we could make a pull 00:30:42.640 --> 00:30:44.120 align:start position:0% fix with Maximus so we could make a pull request<00:30:42.670> to<00:30:42.970> include<00:30:43.240> ear<00:30:43.360> see<00:30:43.510> 20<00:30:43.780> tokens 00:30:44.120 --> 00:30:44.130 align:start position:0% request to include ear see 20 tokens 00:30:44.130 --> 00:30:47.550 align:start position:0% request to include ear see 20 tokens ethics<00:30:45.130> have<00:30:46.200> re-implemented<00:30:47.200> it<00:30:47.290> being<00:30:47.470> a 00:30:47.550 --> 00:30:47.560 align:start position:0% ethics have re-implemented it being a 00:30:47.560 --> 00:30:48.930 align:start position:0% ethics have re-implemented it being a much<00:30:47.710> more<00:30:47.800> efficient<00:30:48.310> way<00:30:48.400> and<00:30:48.430> it'd<00:30:48.700> be<00:30:48.790> nice 00:30:48.930 --> 00:30:48.940 align:start position:0% much more efficient way and it'd be nice 00:30:48.940 --> 00:30:50.340 align:start position:0% much more efficient way and it'd be nice to<00:30:49.210> sort<00:30:49.450> of<00:30:49.600> port<00:30:49.780> their<00:30:49.900> work<00:30:50.080> to<00:30:50.320> the 00:30:50.340 --> 00:30:50.350 align:start position:0% to sort of port their work to the 00:30:50.350 --> 00:30:53.670 align:start position:0% to sort of port their work to the original<00:30:50.980> repository<00:30:52.140> yeah<00:30:53.140> and<00:30:53.470> then<00:30:53.590> it 00:30:53.670 --> 00:30:53.680 align:start position:0% original repository yeah and then it 00:30:53.680 --> 00:30:55.050 align:start position:0% original repository yeah and then it would<00:30:53.800> be<00:30:53.890> good<00:30:54.010> to<00:30:54.040> merge<00:30:54.250> mix<00:30:54.490> in<00:30:54.730> seven<00:30:54.940> four 00:30:55.050 --> 00:30:55.060 align:start position:0% would be good to merge mix in seven four 00:30:55.060 --> 00:30:56.430 align:start position:0% would be good to merge mix in seven four together<00:30:55.270> because<00:30:55.570> they're<00:30:55.660> so<00:30:55.750> similar<00:30:55.960> it 00:30:56.430 --> 00:30:56.440 align:start position:0% together because they're so similar it 00:30:56.440 --> 00:30:57.900 align:start position:0% together because they're so similar it would<00:30:56.590> just<00:30:56.830> be<00:30:56.920> good<00:30:57.010> to<00:30:57.070> have<00:30:57.280> a<00:30:57.310> single<00:30:57.670> a 00:30:57.900 --> 00:30:57.910 align:start position:0% would just be good to have a single a 00:30:57.910 --> 00:31:02.760 align:start position:0% would just be good to have a single a single<00:30:58.780> repository<00:31:00.990> okay<00:31:01.990> and<00:31:02.140> then<00:31:02.290> then 00:31:02.760 --> 00:31:02.770 align:start position:0% single repository okay and then then 00:31:02.770 --> 00:31:04.230 align:start position:0% single repository okay and then then this<00:31:02.950> other<00:31:03.160> work<00:31:03.430> to<00:31:03.550> do<00:31:03.640> we<00:31:03.730> can<00:31:03.880> replace<00:31:04.090> the 00:31:04.230 --> 00:31:04.240 align:start position:0% this other work to do we can replace the 00:31:04.240 --> 00:31:05.760 align:start position:0% this other work to do we can replace the hash<00:31:04.360> function<00:31:04.540> which<00:31:05.170> I'll<00:31:05.290> talk<00:31:05.440> about<00:31:05.500> in<00:31:05.710> a 00:31:05.760 --> 00:31:05.770 align:start position:0% hash function which I'll talk about in a 00:31:05.770 --> 00:31:07.890 align:start position:0% hash function which I'll talk about in a while<00:31:05.920> and<00:31:06.250> then<00:31:07.150> there's<00:31:07.360> also<00:31:07.480> a<00:31:07.600> bunch<00:31:07.810> more 00:31:07.890 --> 00:31:07.900 align:start position:0% while and then there's also a bunch more 00:31:07.900 --> 00:31:09.870 align:start position:0% while and then there's also a bunch more some<00:31:08.200> before<00:31:08.410> use<00:31:08.530> cases<00:31:08.740> that<00:31:08.890> that'll<00:31:09.850> be 00:31:09.870 --> 00:31:09.880 align:start position:0% some before use cases that that'll be 00:31:09.880 --> 00:31:14.610 align:start position:0% some before use cases that that'll be nice<00:31:10.060> to<00:31:10.240> explore<00:31:10.570> and<00:31:10.750> talk<00:31:10.900> about<00:31:13.560> okay<00:31:14.560> so 00:31:14.610 --> 00:31:14.620 align:start position:0% nice to explore and talk about okay so 00:31:14.620 --> 00:31:16.050 align:start position:0% nice to explore and talk about okay so let's<00:31:14.950> talk<00:31:15.100> about<00:31:15.160> some<00:31:15.460> of<00:31:15.490> some<00:31:15.880> of<00:31:16.000> the 00:31:16.050 --> 00:31:16.060 align:start position:0% let's talk about some of some of the 00:31:16.060 --> 00:31:25.590 align:start position:0% let's talk about some of some of the figures<00:31:16.330> of<00:31:16.510> what<00:31:17.110> we<00:31:17.200> have<00:31:17.320> so<00:31:17.710> so<00:31:22.350> okay<00:31:23.350> so<00:31:24.600> so 00:31:25.590 --> 00:31:25.600 align:start position:0% figures of what we have so so okay so so 00:31:25.600 --> 00:31:27.030 align:start position:0% figures of what we have so so okay so so the<00:31:25.630> hash<00:31:25.810> function<00:31:25.990> so<00:31:26.380> we<00:31:26.500> need<00:31:26.620> in<00:31:26.740> order<00:31:26.860> to 00:31:27.030 --> 00:31:27.040 align:start position:0% the hash function so we need in order to 00:31:27.040 --> 00:31:28.350 align:start position:0% the hash function so we need in order to make<00:31:27.190> a<00:31:27.220> Merkle<00:31:27.490> tree<00:31:27.640> in<00:31:27.850> order<00:31:28.030> to<00:31:28.180> make<00:31:28.300> a 00:31:28.350 --> 00:31:28.360 align:start position:0% make a Merkle tree in order to make a 00:31:28.360 --> 00:31:29.280 align:start position:0% make a Merkle tree in order to make a Merkle<00:31:28.600> tree<00:31:28.690> we<00:31:28.840> need<00:31:28.870> to<00:31:29.020> have<00:31:29.110> a<00:31:29.140> hash 00:31:29.280 --> 00:31:29.290 align:start position:0% Merkle tree we need to have a hash 00:31:29.290 --> 00:31:30.990 align:start position:0% Merkle tree we need to have a hash function<00:31:29.320> and<00:31:30.190> a<00:31:30.340> hash<00:31:30.460> function<00:31:30.730> that<00:31:30.760> we<00:31:30.880> use 00:31:30.990 --> 00:31:31.000 align:start position:0% function and a hash function that we use 00:31:31.000 --> 00:31:34.880 align:start position:0% function and a hash function that we use right<00:31:31.120> now<00:31:31.180> is<00:31:31.300> a<00:31:31.420> a<00:31:31.540> 256<00:31:32.140> and<00:31:32.590> char<00:31:33.340> 256 00:31:34.880 --> 00:31:34.890 align:start position:0% right now is a a 256 and char 256 00:31:34.890 --> 00:31:37.410 align:start position:0% right now is a a 256 and char 256 it's<00:31:35.890> very<00:31:36.010> expensive<00:31:36.220> to<00:31:36.490> do<00:31:36.640> inside<00:31:36.880> inside 00:31:37.410 --> 00:31:37.420 align:start position:0% it's very expensive to do inside inside 00:31:37.420 --> 00:31:39.030 align:start position:0% it's very expensive to do inside inside the<00:31:37.540> snark<00:31:37.750> because<00:31:38.290> it's<00:31:38.440> based<00:31:38.560> upon<00:31:38.680> binary 00:31:39.030 --> 00:31:39.040 align:start position:0% the snark because it's based upon binary 00:31:39.040 --> 00:31:40.380 align:start position:0% the snark because it's based upon binary operations<00:31:39.430> and<00:31:39.640> I'm<00:31:39.790> gonna<00:31:39.970> talk<00:31:40.120> about<00:31:40.150> that 00:31:40.380 --> 00:31:40.390 align:start position:0% operations and I'm gonna talk about that 00:31:40.390 --> 00:31:43.740 align:start position:0% operations and I'm gonna talk about that in<00:31:40.450> a<00:31:40.510> minute<00:31:41.940> so<00:31:42.940> improving<00:31:43.270> time<00:31:43.420> in<00:31:43.540> seven 00:31:43.740 --> 00:31:43.750 align:start position:0% in a minute so improving time in seven 00:31:43.750 --> 00:31:45.750 align:start position:0% in a minute so improving time in seven four<00:31:43.780> is<00:31:44.020> about<00:31:44.200> seven<00:31:44.470> minutes<00:31:44.710> and<00:31:44.890> the 00:31:45.750 --> 00:31:45.760 align:start position:0% four is about seven minutes and the 00:31:45.760 --> 00:31:47.070 align:start position:0% four is about seven minutes and the Merkle<00:31:46.030> tree<00:31:46.150> the<00:31:46.360> depth<00:31:46.570> of<00:31:46.690> the<00:31:46.750> Markel<00:31:46.960> tree 00:31:47.070 --> 00:31:47.080 align:start position:0% Merkle tree the depth of the Markel tree 00:31:47.080 --> 00:31:49.760 align:start position:0% Merkle tree the depth of the Markel tree is<00:31:47.320> 29<00:31:47.920> which<00:31:48.130> means<00:31:48.340> there's<00:31:48.550> like<00:31:48.790> 29<00:31:49.180> hashes 00:31:49.760 --> 00:31:49.770 align:start position:0% is 29 which means there's like 29 hashes 00:31:49.770 --> 00:31:52.620 align:start position:0% is 29 which means there's like 29 hashes so<00:31:50.770> that's<00:31:51.100> yeah<00:31:52.000> so<00:31:52.180> it's<00:31:52.330> quite<00:31:52.450> expensive 00:31:52.620 --> 00:31:52.630 align:start position:0% so that's yeah so it's quite expensive 00:31:52.630 --> 00:31:54.300 align:start position:0% so that's yeah so it's quite expensive but<00:31:52.930> that<00:31:52.990> a<00:31:53.080> the<00:31:53.440> tree<00:31:53.650> is<00:31:53.770> very<00:31:53.950> big<00:31:54.130> it's 00:31:54.300 --> 00:31:54.310 align:start position:0% but that a the tree is very big it's 00:31:54.310 --> 00:31:55.710 align:start position:0% but that a the tree is very big it's enough<00:31:54.490> for<00:31:54.520> like<00:31:54.820> 500<00:31:55.210> million<00:31:55.420> people<00:31:55.510> to 00:31:55.710 --> 00:31:55.720 align:start position:0% enough for like 500 million people to 00:31:55.720 --> 00:31:58.950 align:start position:0% enough for like 500 million people to join<00:31:57.120> so<00:31:58.120> on<00:31:58.270> my<00:31:58.390> laptop<00:31:58.540> it<00:31:58.780> takes<00:31:58.900> about 00:31:58.950 --> 00:31:58.960 align:start position:0% join so on my laptop it takes about 00:31:58.960 --> 00:32:00.150 align:start position:0% join so on my laptop it takes about seven<00:31:59.170> minutes<00:31:59.500> and<00:31:59.620> it<00:31:59.710> needs<00:31:59.890> a<00:31:59.950> lot<00:32:00.070> of 00:32:00.150 --> 00:32:00.160 align:start position:0% seven minutes and it needs a lot of 00:32:00.160 --> 00:32:01.470 align:start position:0% seven minutes and it needs a lot of problems<00:32:00.490> it's<00:32:00.640> impossible<00:32:01.000> to<00:32:01.060> run<00:32:01.180> it<00:32:01.300> on<00:32:01.360> a 00:32:01.470 --> 00:32:01.480 align:start position:0% problems it's impossible to run it on a 00:32:01.480 --> 00:32:04.140 align:start position:0% problems it's impossible to run it on a smartphone<00:32:01.750> and<00:32:02.080> this<00:32:02.380> is<00:32:02.500> a<00:32:02.530> problem<00:32:03.030> so<00:32:04.030> it's 00:32:04.140 --> 00:32:04.150 align:start position:0% smartphone and this is a problem so it's 00:32:04.150 --> 00:32:07.500 align:start position:0% smartphone and this is a problem so it's about<00:32:04.240> 50<00:32:04.510> K<00:32:04.710> constraints<00:32:05.710> per<00:32:05.950> hash<00:32:06.390> which<00:32:07.390> is 00:32:07.500 --> 00:32:07.510 align:start position:0% about 50 K constraints per hash which is 00:32:07.510 --> 00:32:09.960 align:start position:0% about 50 K constraints per hash which is which<00:32:08.110> leads<00:32:08.440> to<00:32:08.590> 1.5<00:32:09.280> million<00:32:09.520> constraints 00:32:09.960 --> 00:32:09.970 align:start position:0% which leads to 1.5 million constraints 00:32:09.970 --> 00:32:12.360 align:start position:0% which leads to 1.5 million constraints altogether<00:32:10.300> and<00:32:10.740> this<00:32:11.740> makes<00:32:11.950> the<00:32:12.070> proof<00:32:12.220> this 00:32:12.360 --> 00:32:12.370 align:start position:0% altogether and this makes the proof this 00:32:12.370 --> 00:32:13.710 align:start position:0% altogether and this makes the proof this is<00:32:12.430> the<00:32:12.670> reason<00:32:12.970> why<00:32:13.060> the<00:32:13.120> proving<00:32:13.390> time<00:32:13.510> is<00:32:13.630> so 00:32:13.710 --> 00:32:13.720 align:start position:0% is the reason why the proving time is so 00:32:13.720 --> 00:32:16.260 align:start position:0% is the reason why the proving time is so so<00:32:13.870> so<00:32:14.200> we<00:32:14.410> want<00:32:14.590> to<00:32:14.650> minimize<00:32:14.950> the<00:32:15.190> we<00:32:16.030> want<00:32:16.210> to 00:32:16.260 --> 00:32:16.270 align:start position:0% so so we want to minimize the we want to 00:32:16.270 --> 00:32:18.330 align:start position:0% so so we want to minimize the we want to minimize<00:32:16.570> the<00:32:16.750> proving<00:32:17.080> time<00:32:17.230> so<00:32:17.890> we<00:32:18.070> want<00:32:18.280> to 00:32:18.330 --> 00:32:18.340 align:start position:0% minimize the proving time so we want to 00:32:18.340 --> 00:32:20.190 align:start position:0% minimize the proving time so we want to meet<00:32:18.430> early<00:32:18.610> so<00:32:18.970> we<00:32:19.210> want<00:32:19.420> to<00:32:19.510> reduce<00:32:19.930> the 00:32:20.190 --> 00:32:20.200 align:start position:0% meet early so we want to reduce the 00:32:20.200 --> 00:32:22.740 align:start position:0% meet early so we want to reduce the number<00:32:20.230> of<00:32:20.410> constraints<00:32:21.180> so<00:32:22.180> let's<00:32:22.600> talk 00:32:22.740 --> 00:32:22.750 align:start position:0% number of constraints so let's talk 00:32:22.750 --> 00:32:24.840 align:start position:0% number of constraints so let's talk about<00:32:22.810> how<00:32:23.350> we<00:32:23.410> can<00:32:23.650> do<00:32:23.740> this<00:32:23.920> okay<00:32:24.400> so<00:32:24.460> inside 00:32:24.840 --> 00:32:24.850 align:start position:0% about how we can do this okay so inside 00:32:24.850 --> 00:32:28.050 align:start position:0% about how we can do this okay so inside of<00:32:24.880> snark<00:32:25.120> we<00:32:25.720> can<00:32:25.870> do<00:32:26.050> a<00:32:26.500> time<00:32:27.310> we<00:32:27.520> can<00:32:27.700> we<00:32:27.910> can 00:32:28.050 --> 00:32:28.060 align:start position:0% of snark we can do a time we can we can 00:32:28.060 --> 00:32:29.220 align:start position:0% of snark we can do a time we can we can do<00:32:28.210> this<00:32:28.390> we<00:32:28.600> can<00:32:28.720> sort<00:32:28.900> of<00:32:28.960> check<00:32:29.110> these 00:32:29.220 --> 00:32:29.230 align:start position:0% do this we can sort of check these 00:32:29.230 --> 00:32:29.910 align:start position:0% do this we can sort of check these assertions 00:32:29.910 --> 00:32:29.920 align:start position:0% assertions 00:32:29.920 --> 00:32:31.830 align:start position:0% assertions yeah<00:32:30.280> we<00:32:30.760> can<00:32:30.880> check<00:32:31.030> to<00:32:31.090> sight<00:32:31.390> Chinese<00:32:31.720> and 00:32:31.830 --> 00:32:31.840 align:start position:0% yeah we can check to sight Chinese and 00:32:31.840 --> 00:32:33.540 align:start position:0% yeah we can check to sight Chinese and sign<00:32:32.140> kinds<00:32:32.500> of<00:32:32.560> assertions<00:32:32.890> we<00:32:33.040> can<00:32:33.190> say<00:32:33.370> that 00:32:33.540 --> 00:32:33.550 align:start position:0% sign kinds of assertions we can say that 00:32:33.550 --> 00:32:35.970 align:start position:0% sign kinds of assertions we can say that a<00:32:33.730> multiplied<00:32:34.390> by<00:32:34.540> B<00:32:34.720> equals<00:32:35.080> C<00:32:35.200> and<00:32:35.410> we<00:32:35.830> can 00:32:35.970 --> 00:32:35.980 align:start position:0% a multiplied by B equals C and we can 00:32:35.980 --> 00:32:38.310 align:start position:0% a multiplied by B equals C and we can check<00:32:36.430> that<00:32:36.490> we<00:32:37.150> can<00:32:37.300> check<00:32:37.630> multiplications 00:32:38.310 --> 00:32:38.320 align:start position:0% check that we can check multiplications 00:32:38.320 --> 00:32:40.770 align:start position:0% check that we can check multiplications and<00:32:38.530> additions<00:32:38.710> so<00:32:39.430> we<00:32:39.550> can<00:32:39.670> also<00:32:39.790> replace<00:32:40.330> a 00:32:40.770 --> 00:32:40.780 align:start position:0% and additions so we can also replace a 00:32:40.780 --> 00:32:42.720 align:start position:0% and additions so we can also replace a and<00:32:41.290> B<00:32:41.440> with<00:32:41.710> a<00:32:41.740> bunch<00:32:41.950> of<00:32:42.040> additions<00:32:42.520> of 00:32:42.720 --> 00:32:42.730 align:start position:0% and B with a bunch of additions of 00:32:42.730 --> 00:32:44.460 align:start position:0% and B with a bunch of additions of something<00:32:43.330> else<00:32:43.480> yeah<00:32:43.720> where<00:32:44.050> it<00:32:44.140> can<00:32:44.260> be<00:32:44.350> the 00:32:44.460 --> 00:32:44.470 align:start position:0% something else yeah where it can be the 00:32:44.470 --> 00:32:48.390 align:start position:0% something else yeah where it can be the sums<00:32:44.710> of<00:32:45.190> things<00:32:45.400> yeah<00:32:46.120> so<00:32:46.630> then<00:32:47.440> we<00:32:48.250> can 00:32:48.390 --> 00:32:48.400 align:start position:0% sums of things yeah so then we can 00:32:48.400 --> 00:32:49.860 align:start position:0% sums of things yeah so then we can already<00:32:48.520> do<00:32:48.880> cool<00:32:49.180> things<00:32:49.210> with<00:32:49.480> this<00:32:49.600> I<00:32:49.750> mean 00:32:49.860 --> 00:32:49.870 align:start position:0% already do cool things with this I mean 00:32:49.870 --> 00:32:51.660 align:start position:0% already do cool things with this I mean we<00:32:49.990> can<00:32:50.110> already<00:32:50.230> implement<00:32:50.830> every<00:32:51.040> company 00:32:51.660 --> 00:32:51.670 align:start position:0% we can already implement every company 00:32:51.670 --> 00:32:53.100 align:start position:0% we can already implement every company computation<00:32:52.060> with<00:32:52.180> this<00:32:52.300> right<00:32:52.750> because<00:32:53.020> we 00:32:53.100 --> 00:32:53.110 align:start position:0% computation with this right because we 00:32:53.110 --> 00:32:55.230 align:start position:0% computation with this right because we and<00:32:53.530> the<00:32:54.130> way<00:32:54.220> that<00:32:54.340> we<00:32:54.430> the<00:32:54.730> way<00:32:54.820> that<00:32:54.970> we<00:32:55.030> end 00:32:55.230 --> 00:32:55.240 align:start position:0% and the way that we the way that we end 00:32:55.240 --> 00:32:56.760 align:start position:0% and the way that we the way that we end up<00:32:55.270> the<00:32:55.420> end<00:32:55.600> of<00:32:55.690> doing<00:32:55.930> it<00:32:56.020> is<00:32:56.140> okay<00:32:56.560> for 00:32:56.760 --> 00:32:56.770 align:start position:0% up the end of doing it is okay for 00:32:56.770 --> 00:32:58.620 align:start position:0% up the end of doing it is okay for example<00:32:56.860> can<00:32:57.550> can<00:32:57.880> anyone<00:32:58.150> think<00:32:58.210> about<00:32:58.480> how 00:32:58.620 --> 00:32:58.630 align:start position:0% example can can anyone think about how 00:32:58.630 --> 00:33:00.450 align:start position:0% example can can anyone think about how to<00:32:58.690> do<00:32:58.900> how<00:32:59.110> to<00:32:59.170> design<00:32:59.470> an<00:32:59.620> xor<00:33:00.040> gate<00:33:00.100> with 00:33:00.450 --> 00:33:00.460 align:start position:0% to do how to design an xor gate with 00:33:00.460 --> 00:33:02.550 align:start position:0% to do how to design an xor gate with this<00:33:00.640> I<00:33:00.820> mean<00:33:01.630> maybe<00:33:01.810> this<00:33:01.990> is<00:33:02.110> probably<00:33:02.350> not<00:33:02.530> a 00:33:02.550 --> 00:33:02.560 align:start position:0% this I mean maybe this is probably not a 00:33:02.560 --> 00:33:04.020 align:start position:0% this I mean maybe this is probably not a good<00:33:02.740> interactive<00:33:03.310> question<00:33:03.610> but<00:33:03.760> this<00:33:03.880> is<00:33:04.000> a 00:33:04.020 --> 00:33:04.030 align:start position:0% good interactive question but this is a 00:33:04.030 --> 00:33:05.820 align:start position:0% good interactive question but this is a good<00:33:04.240> sort<00:33:04.510> of<00:33:04.570> learning<00:33:04.810> experience<00:33:05.290> to<00:33:05.710> make 00:33:05.820 --> 00:33:05.830 align:start position:0% good sort of learning experience to make 00:33:05.830 --> 00:33:08.190 align:start position:0% good sort of learning experience to make an<00:33:05.950> xor<00:33:06.220> gate<00:33:06.250> at<00:33:06.550> the<00:33:06.580> start<00:33:06.880> and<00:33:07.060> just<00:33:07.750> see 00:33:08.190 --> 00:33:08.200 align:start position:0% an xor gate at the start and just see 00:33:08.200 --> 00:33:09.780 align:start position:0% an xor gate at the start and just see how<00:33:08.380> you<00:33:08.440> can<00:33:08.650> make<00:33:08.770> these<00:33:08.890> constraints<00:33:09.370> also 00:33:09.780 --> 00:33:09.790 align:start position:0% how you can make these constraints also 00:33:09.790 --> 00:33:11.820 align:start position:0% how you can make these constraints also I<00:33:09.910> have<00:33:10.030> a<00:33:10.090> list<00:33:10.300> of<00:33:10.420> these<00:33:10.570> problems<00:33:10.990> that<00:33:11.080> are 00:33:11.820 --> 00:33:11.830 align:start position:0% I have a list of these problems that are 00:33:11.830 --> 00:33:13.410 align:start position:0% I have a list of these problems that are kind<00:33:12.010> of<00:33:12.070> interesting<00:33:12.610> to<00:33:12.760> approach<00:33:13.240> you<00:33:13.360> at 00:33:13.410 --> 00:33:13.420 align:start position:0% kind of interesting to approach you at 00:33:13.420 --> 00:33:15.060 align:start position:0% kind of interesting to approach you at the<00:33:13.510> start<00:33:13.720> so<00:33:14.230> if<00:33:14.350> anyone's<00:33:14.620> interested<00:33:14.770> in 00:33:15.060 --> 00:33:15.070 align:start position:0% the start so if anyone's interested in 00:33:15.070 --> 00:33:19.320 align:start position:0% the start so if anyone's interested in that<00:33:15.160> please<00:33:15.280> let<00:33:15.490> me<00:33:15.550> know<00:33:17.400> yeah<00:33:18.400> so<00:33:18.580> sha-256 00:33:19.320 --> 00:33:19.330 align:start position:0% that please let me know yeah so sha-256 00:33:19.330 --> 00:33:20.790 align:start position:0% that please let me know yeah so sha-256 is<00:33:19.420> binary<00:33:19.660> operator<00:33:19.930> it<00:33:20.020> has<00:33:20.440> a<00:33:20.470> bunch<00:33:20.740> of 00:33:20.790 --> 00:33:20.800 align:start position:0% is binary operator it has a bunch of 00:33:20.800 --> 00:33:22.650 align:start position:0% is binary operator it has a bunch of binary<00:33:20.980> operations<00:33:21.670> one<00:33:22.030> of<00:33:22.120> them<00:33:22.210> is<00:33:22.300> an<00:33:22.390> XOR 00:33:22.650 --> 00:33:22.660 align:start position:0% binary operations one of them is an XOR 00:33:22.660 --> 00:33:23.730 align:start position:0% binary operations one of them is an XOR and<00:33:22.780> then<00:33:22.870> there's<00:33:22.990> like<00:33:23.110> Sigma<00:33:23.410> shifting 00:33:23.730 --> 00:33:23.740 align:start position:0% and then there's like Sigma shifting 00:33:23.740 --> 00:33:25.620 align:start position:0% and then there's like Sigma shifting yourself<00:33:24.550> and<00:33:24.760> a<00:33:24.850> whole<00:33:25.000> other<00:33:25.300> bunch<00:33:25.480> of 00:33:25.620 --> 00:33:25.630 align:start position:0% yourself and a whole other bunch of 00:33:25.630 --> 00:33:28.140 align:start position:0% yourself and a whole other bunch of stuff<00:33:25.750> so<00:33:26.170> what<00:33:26.320> we<00:33:26.410> do<00:33:26.620> is<00:33:27.070> or<00:33:27.790> what<00:33:27.970> other 00:33:28.140 --> 00:33:28.150 align:start position:0% stuff so what we do is or what other 00:33:28.150 --> 00:33:29.190 align:start position:0% stuff so what we do is or what other people<00:33:28.210> have<00:33:28.450> done<00:33:28.540> well<00:33:28.780> the<00:33:28.960> lipsmack 00:33:29.190 --> 00:33:29.200 align:start position:0% people have done well the lipsmack 00:33:29.200 --> 00:33:30.510 align:start position:0% people have done well the lipsmack people<00:33:29.470> have<00:33:29.560> done<00:33:29.680> it<00:33:29.950> they've<00:33:30.130> implemented 00:33:30.510 --> 00:33:30.520 align:start position:0% people have done it they've implemented 00:33:30.520 --> 00:33:31.530 align:start position:0% people have done it they've implemented sha-256 00:33:31.530 --> 00:33:31.540 align:start position:0% sha-256 00:33:31.540 --> 00:33:33.930 align:start position:0% sha-256 they've<00:33:32.230> implemented<00:33:32.560> it<00:33:32.860> in<00:33:33.130> in<00:33:33.610> lipstick 00:33:33.930 --> 00:33:33.940 align:start position:0% they've implemented it in in lipstick 00:33:33.940 --> 00:33:36.120 align:start position:0% they've implemented it in in lipstick and<00:33:34.150> and<00:33:34.810> they've<00:33:35.050> just<00:33:35.080> built<00:33:35.560> all<00:33:35.710> the<00:33:35.830> basic 00:33:36.120 --> 00:33:36.130 align:start position:0% and and they've just built all the basic 00:33:36.130 --> 00:33:38.850 align:start position:0% and and they've just built all the basic gadgets<00:33:36.460> and<00:33:36.670> plug<00:33:37.210> them<00:33:37.360> all<00:33:37.390> together<00:33:37.540> so<00:33:38.440> we 00:33:38.850 --> 00:33:38.860 align:start position:0% gadgets and plug them all together so we 00:33:38.860 --> 00:33:41.220 align:start position:0% gadgets and plug them all together so we can<00:33:39.100> we<00:33:39.400> can<00:33:39.550> we<00:33:40.000> can<00:33:40.120> already<00:33:40.240> do<00:33:40.450> this<00:33:40.600> but<00:33:40.870> it 00:33:41.220 --> 00:33:41.230 align:start position:0% can we can we can already do this but it 00:33:41.230 --> 00:33:44.700 align:start position:0% can we can we can already do this but it turns<00:33:41.380> out<00:33:41.530> it's<00:33:42.010> really<00:33:42.280> expensive<00:33:43.710> because 00:33:44.700 --> 00:33:44.710 align:start position:0% turns out it's really expensive because 00:33:44.710 --> 00:33:46.110 align:start position:0% turns out it's really expensive because we<00:33:44.800> just<00:33:44.950> turn<00:33:45.160> everything<00:33:45.280> in<00:33:45.520> a<00:33:45.580> binary<00:33:45.790> and 00:33:46.110 --> 00:33:46.120 align:start position:0% we just turn everything in a binary and 00:33:46.120 --> 00:33:49.230 align:start position:0% we just turn everything in a binary and inside<00:33:46.510> the<00:33:46.570> binary<00:33:46.870> we<00:33:47.020> use<00:33:47.710> we<00:33:48.550> can<00:33:49.000> just<00:33:49.150> do 00:33:49.230 --> 00:33:49.240 align:start position:0% inside the binary we use we can just do 00:33:49.240 --> 00:33:51.030 align:start position:0% inside the binary we use we can just do zero<00:33:49.480> on<00:33:49.630> one<00:33:49.660> where<00:33:50.020> we<00:33:50.170> have<00:33:50.350> we<00:33:50.890> can 00:33:51.030 --> 00:33:51.040 align:start position:0% zero on one where we have we can 00:33:51.040 --> 00:33:52.740 align:start position:0% zero on one where we have we can actually<00:33:51.160> do<00:33:51.610> a<00:33:51.640> lot<00:33:51.880> more<00:33:51.940> expressive<00:33:52.450> things 00:33:52.740 --> 00:33:52.750 align:start position:0% actually do a lot more expressive things 00:33:52.750 --> 00:33:57.270 align:start position:0% actually do a lot more expressive things inside<00:33:53.020> the<00:33:53.170> snark<00:33:55.140> so<00:33:56.140> how<00:33:56.410> can<00:33:56.650> we<00:33:56.800> can<00:33:56.950> how 00:33:57.270 --> 00:33:57.280 align:start position:0% inside the snark so how can we can how 00:33:57.280 --> 00:34:00.300 align:start position:0% inside the snark so how can we can how can<00:33:57.430> we<00:33:57.520> improve<00:33:57.850> this<00:33:58.590> so<00:33:59.590> let's<00:34:00.010> talk<00:34:00.160> about 00:34:00.300 --> 00:34:00.310 align:start position:0% can we improve this so let's talk about 00:34:00.310 --> 00:34:01.980 align:start position:0% can we improve this so let's talk about what<00:34:00.550> we<00:34:00.640> can<00:34:00.730> do<00:34:00.820> inside<00:34:01.000> a<00:34:01.060> snack<00:34:01.300> so<00:34:01.720> we<00:34:01.900> can 00:34:01.980 --> 00:34:01.990 align:start position:0% what we can do inside a snack so we can 00:34:01.990 --> 00:34:04.620 align:start position:0% what we can do inside a snack so we can do<00:34:02.080> this<00:34:02.200> a<00:34:02.290> times<00:34:02.530> a<00:34:02.710> times<00:34:03.310> B<00:34:03.640> equals<00:34:03.910> C<00:34:04.360> where 00:34:04.620 --> 00:34:04.630 align:start position:0% do this a times a times B equals C where 00:34:04.630 --> 00:34:08.610 align:start position:0% do this a times a times B equals C where a<00:34:04.660> and<00:34:04.990> B<00:34:05.110> and<00:34:05.440> C<00:34:05.740> are<00:34:05.890> all<00:34:06.010> these<00:34:06.160> items<00:34:07.530> and<00:34:08.530> we 00:34:08.610 --> 00:34:08.620 align:start position:0% a and B and C are all these items and we 00:34:08.620 --> 00:34:10.050 align:start position:0% a and B and C are all these items and we can<00:34:08.740> also<00:34:08.860> but<00:34:09.250> we<00:34:09.400> have<00:34:09.550> to<00:34:09.669> be<00:34:09.760> careful 00:34:10.050 --> 00:34:10.060 align:start position:0% can also but we have to be careful 00:34:10.060 --> 00:34:11.250 align:start position:0% can also but we have to be careful because<00:34:10.150> we<00:34:10.360> have<00:34:10.480> to<00:34:10.570> we<00:34:10.840> have<00:34:10.960> an<00:34:11.020> overflow 00:34:11.250 --> 00:34:11.260 align:start position:0% because we have to we have an overflow 00:34:11.260 --> 00:34:13.590 align:start position:0% because we have to we have an overflow so<00:34:12.100> snacks<00:34:12.400> work<00:34:12.610> over<00:34:12.820> this<00:34:12.940> prime<00:34:13.179> field<00:34:13.390> and 00:34:13.590 --> 00:34:13.600 align:start position:0% so snacks work over this prime field and 00:34:13.600 --> 00:34:15.990 align:start position:0% so snacks work over this prime field and if<00:34:13.900> we<00:34:14.020> get<00:34:14.169> to<00:34:14.350> this<00:34:14.440> number<00:34:14.760> which<00:34:15.760> is<00:34:15.880> about 00:34:15.990 --> 00:34:16.000 align:start position:0% if we get to this number which is about 00:34:16.000 --> 00:34:19.860 align:start position:0% if we get to this number which is about 253<00:34:16.960> bits<00:34:17.169> which<00:34:17.980> is<00:34:18.100> 253<00:34:18.790> bits<00:34:19.000> we<00:34:19.450> will 00:34:19.860 --> 00:34:19.870 align:start position:0% 253 bits which is 253 bits we will 00:34:19.870 --> 00:34:21.600 align:start position:0% 253 bits which is 253 bits we will overflow<00:34:20.140> I<00:34:20.530> mean<00:34:20.770> if<00:34:20.890> we<00:34:21.040> add<00:34:21.160> one<00:34:21.310> more<00:34:21.429> will 00:34:21.600 --> 00:34:21.610 align:start position:0% overflow I mean if we add one more will 00:34:21.610 --> 00:34:23.730 align:start position:0% overflow I mean if we add one more will overflow<00:34:21.870> and<00:34:22.870> so<00:34:22.990> we<00:34:23.080> wrap<00:34:23.260> around<00:34:23.290> at<00:34:23.650> this 00:34:23.730 --> 00:34:23.740 align:start position:0% overflow and so we wrap around at this 00:34:23.740 --> 00:34:25.200 align:start position:0% overflow and so we wrap around at this other<00:34:23.950> number<00:34:24.130> down<00:34:24.640> here<00:34:24.669> which<00:34:24.970> is<00:34:25.090> about 00:34:25.200 --> 00:34:25.210 align:start position:0% other number down here which is about 00:34:25.210 --> 00:34:31.260 align:start position:0% other number down here which is about 200<00:34:25.690> to<00:34:25.870> 250<00:34:26.440> bits<00:34:29.280> so<00:34:30.280> a<00:34:30.310> turn<00:34:30.550> so<00:34:30.790> that<00:34:31.090> means 00:34:31.260 --> 00:34:31.270 align:start position:0% 200 to 250 bits so a turn so that means 00:34:31.270 --> 00:34:33.210 align:start position:0% 200 to 250 bits so a turn so that means that<00:34:31.390> we<00:34:31.480> do<00:34:31.600> all<00:34:31.840> our<00:34:31.870> arithmetic<00:34:32.590> modulo<00:34:32.830> P 00:34:33.210 --> 00:34:33.220 align:start position:0% that we do all our arithmetic modulo P 00:34:33.220 --> 00:34:35.430 align:start position:0% that we do all our arithmetic modulo P yeah<00:34:33.850> where<00:34:34.060> P<00:34:34.240> is<00:34:34.360> where<00:34:34.960> P<00:34:35.110> is<00:34:35.140> a<00:34:35.230> prime 00:34:35.430 --> 00:34:35.440 align:start position:0% yeah where P is where P is a prime 00:34:35.440 --> 00:34:38.640 align:start position:0% yeah where P is where P is a prime number<00:34:35.500> so<00:34:36.929> does<00:34:37.929> anyone<00:34:38.140> know<00:34:38.290> how<00:34:38.380> this<00:34:38.500> can 00:34:38.640 --> 00:34:38.650 align:start position:0% number so does anyone know how this can 00:34:38.650 --> 00:34:41.370 align:start position:0% number so does anyone know how this can be<00:34:38.770> how<00:34:39.010> we<00:34:39.070> can<00:34:39.250> use<00:34:39.429> this<00:34:40.140> anyone<00:34:41.140> have<00:34:41.260> any 00:34:41.370 --> 00:34:41.380 align:start position:0% be how we can use this anyone have any 00:34:41.380 --> 00:34:42.690 align:start position:0% be how we can use this anyone have any ideas<00:34:41.650> how<00:34:41.740> we<00:34:41.830> can<00:34:41.950> use<00:34:42.070> this<00:34:42.220> to<00:34:42.340> build<00:34:42.520> like 00:34:42.690 --> 00:34:42.700 align:start position:0% ideas how we can use this to build like 00:34:42.700 --> 00:34:46.530 align:start position:0% ideas how we can use this to build like an<00:34:42.850> interesting<00:34:43.590> interesting<00:34:44.590> things<00:34:45.540> this 00:34:46.530 --> 00:34:46.540 align:start position:0% an interesting interesting things this 00:34:46.540 --> 00:34:50.880 align:start position:0% an interesting interesting things this is<00:34:46.690> it<00:34:46.810> this<00:34:47.020> is<00:34:47.080> a<00:34:47.169> difficult<00:34:47.470> question<00:34:49.890> yeah 00:34:50.880 --> 00:34:50.890 align:start position:0% is it this is a difficult question yeah 00:34:50.890 --> 00:34:53.400 align:start position:0% is it this is a difficult question yeah okay<00:34:51.310> so<00:34:51.370> it<00:34:51.910> turns<00:34:51.940> out<00:34:52.270> and<00:34:52.960> we<00:34:53.050> kind<00:34:53.260> of<00:34:53.320> use 00:34:53.400 --> 00:34:53.410 align:start position:0% okay so it turns out and we kind of use 00:34:53.410 --> 00:34:55.500 align:start position:0% okay so it turns out and we kind of use this<00:34:53.530> to<00:34:53.740> build<00:34:53.860> elliptic<00:34:54.340> curves<00:34:54.550> yeah 00:34:55.500 --> 00:34:55.510 align:start position:0% this to build elliptic curves yeah 00:34:55.510 --> 00:34:57.540 align:start position:0% this to build elliptic curves yeah because<00:34:55.960> okay<00:34:56.380> so<00:34:56.590> if<00:34:56.800> we<00:34:56.950> take<00:34:57.070> a<00:34:57.130> look<00:34:57.310> if<00:34:57.430> we 00:34:57.540 --> 00:34:57.550 align:start position:0% because okay so if we take a look if we 00:34:57.550 --> 00:34:59.250 align:start position:0% because okay so if we take a look if we take<00:34:57.670> an<00:34:57.760> example<00:34:58.060> of<00:34:58.180> psychic<00:34:58.600> it's<00:34:58.960> like<00:34:59.110> P 00:34:59.250 --> 00:34:59.260 align:start position:0% take an example of psychic it's like P 00:34:59.260 --> 00:35:02.430 align:start position:0% take an example of psychic it's like P 256<00:34:59.590> K<00:34:59.980> 1<00:35:00.220> which<00:35:00.700> is<00:35:00.880> about<00:35:01.060> where<00:35:01.270> P<00:35:01.420> is<00:35:01.570> to<00:35:01.840> 256 00:35:02.430 --> 00:35:02.440 align:start position:0% 256 K 1 which is about where P is to 256 00:35:02.440 --> 00:35:05.880 align:start position:0% 256 K 1 which is about where P is to 256 bits<00:35:03.180> all<00:35:04.180> operations<00:35:04.660> occur 00:35:05.880 --> 00:35:05.890 align:start position:0% bits all operations occur 00:35:05.890 --> 00:35:07.500 align:start position:0% bits all operations occur so<00:35:06.069> it<00:35:06.160> turns<00:35:06.339> out<00:35:06.490> that<00:35:06.640> we<00:35:06.819> could<00:35:07.030> we<00:35:07.270> could 00:35:07.500 --> 00:35:07.510 align:start position:0% so it turns out that we could we could 00:35:07.510 --> 00:35:09.839 align:start position:0% so it turns out that we could we could build<00:35:07.810> a<00:35:08.230> comparative<00:35:09.130> elliptic<00:35:09.700> curve 00:35:09.839 --> 00:35:09.849 align:start position:0% build a comparative elliptic curve 00:35:09.849 --> 00:35:12.120 align:start position:0% build a comparative elliptic curve inside<00:35:10.119> the<00:35:10.270> snark<00:35:10.510> and<00:35:10.780> do<00:35:10.990> and<00:35:11.560> have<00:35:11.800> all<00:35:11.920> our 00:35:12.120 --> 00:35:12.130 align:start position:0% inside the snark and do and have all our 00:35:12.130 --> 00:35:14.490 align:start position:0% inside the snark and do and have all our reason<00:35:12.490> to<00:35:12.579> take<00:35:12.700> modulo<00:35:12.940> P<00:35:13.210> done<00:35:13.420> for<00:35:13.599> free<00:35:13.750> so 00:35:14.490 --> 00:35:14.500 align:start position:0% reason to take modulo P done for free so 00:35:14.500 --> 00:35:16.290 align:start position:0% reason to take modulo P done for free so so<00:35:14.829> we<00:35:14.950> just<00:35:15.130> do<00:35:15.280> regular<00:35:15.490> multiplications 00:35:16.290 --> 00:35:16.300 align:start position:0% so we just do regular multiplications 00:35:16.300 --> 00:35:17.550 align:start position:0% so we just do regular multiplications and<00:35:16.420> additions<00:35:16.480> inside<00:35:17.020> this<00:35:17.109> now<00:35:17.260> I<00:35:17.290> kind<00:35:17.530> of 00:35:17.550 --> 00:35:17.560 align:start position:0% and additions inside this now I kind of 00:35:17.560 --> 00:35:19.290 align:start position:0% and additions inside this now I kind of would<00:35:17.680> turn<00:35:17.829> out<00:35:18.010> that<00:35:18.040> that<00:35:18.280> would<00:35:18.430> be<00:35:18.579> that 00:35:19.290 --> 00:35:19.300 align:start position:0% would turn out that that would be that 00:35:19.300 --> 00:35:20.880 align:start position:0% would turn out that that would be that those<00:35:19.540> those<00:35:19.780> operations<00:35:20.290> were<00:35:20.410> done<00:35:20.589> modulo 00:35:20.880 --> 00:35:20.890 align:start position:0% those those operations were done modulo 00:35:20.890 --> 00:35:27.450 align:start position:0% those those operations were done modulo P<00:35:21.069> so<00:35:24.599> so<00:35:25.599> why<00:35:26.109> don't<00:35:26.319> we<00:35:26.410> do<00:35:26.530> this<00:35:26.710> with<00:35:26.859> Zack<00:35:27.069> P 00:35:27.450 --> 00:35:27.460 align:start position:0% P so so why don't we do this with Zack P 00:35:27.460 --> 00:35:30.510 align:start position:0% P so so why don't we do this with Zack P 256<00:35:28.390> K<00:35:28.810> 1<00:35:29.020> the<00:35:29.530> reason<00:35:29.680> that<00:35:29.890> we<00:35:30.010> don't<00:35:30.280> do<00:35:30.400> it 00:35:30.510 --> 00:35:30.520 align:start position:0% 256 K 1 the reason that we don't do it 00:35:30.520 --> 00:35:33.089 align:start position:0% 256 K 1 the reason that we don't do it with<00:35:31.210> this<00:35:31.359> curve<00:35:31.569> is<00:35:31.890> because<00:35:32.890> they<00:35:32.980> have 00:35:33.089 --> 00:35:33.099 align:start position:0% with this curve is because they have 00:35:33.099 --> 00:35:34.890 align:start position:0% with this curve is because they have edge<00:35:33.280> cases<00:35:33.579> that<00:35:33.819> the<00:35:33.910> when<00:35:34.540> you<00:35:34.630> when<00:35:34.810> you 00:35:34.890 --> 00:35:34.900 align:start position:0% edge cases that the when you when you 00:35:34.900 --> 00:35:37.230 align:start position:0% edge cases that the when you when you try<00:35:35.050> and<00:35:35.109> double<00:35:35.319> points<00:35:35.589> okay<00:35:35.950> so<00:35:36.030> if<00:35:37.030> people 00:35:37.230 --> 00:35:37.240 align:start position:0% try and double points okay so if people 00:35:37.240 --> 00:35:39.150 align:start position:0% try and double points okay so if people are<00:35:37.510> like<00:35:38.020> strolling<00:35:38.349> to<00:35:38.440> follow<00:35:38.619> that's<00:35:38.890> okay 00:35:39.150 --> 00:35:39.160 align:start position:0% are like strolling to follow that's okay 00:35:39.160 --> 00:35:41.099 align:start position:0% are like strolling to follow that's okay I<00:35:39.190> mean<00:35:39.430> this<00:35:39.520> is<00:35:39.670> this<00:35:39.940> is<00:35:40.089> this<00:35:40.569> is<00:35:40.750> kind<00:35:40.960> of<00:35:41.020> a 00:35:41.099 --> 00:35:41.109 align:start position:0% I mean this is this is this is kind of a 00:35:41.109 --> 00:35:42.930 align:start position:0% I mean this is this is this is kind of a little<00:35:41.319> bit<00:35:41.410> difficult<00:35:41.589> stuff<00:35:42.040> and<00:35:42.280> it's 00:35:42.930 --> 00:35:42.940 align:start position:0% little bit difficult stuff and it's 00:35:42.940 --> 00:35:44.640 align:start position:0% little bit difficult stuff and it's gonna<00:35:43.180> get<00:35:43.329> easier<00:35:43.540> in<00:35:43.750> a<00:35:43.839> little<00:35:44.050> bit<00:35:44.200> it's 00:35:44.640 --> 00:35:44.650 align:start position:0% gonna get easier in a little bit it's 00:35:44.650 --> 00:35:46.290 align:start position:0% gonna get easier in a little bit it's just<00:35:44.890> I'm<00:35:45.099> just<00:35:45.160> talking<00:35:45.550> about<00:35:45.609> how<00:35:46.030> to<00:35:46.089> build 00:35:46.290 --> 00:35:46.300 align:start position:0% just I'm just talking about how to build 00:35:46.300 --> 00:35:47.849 align:start position:0% just I'm just talking about how to build these<00:35:46.359> krypter<00:35:46.690> krypter<00:35:46.720> graphic<00:35:47.470> primitives 00:35:47.849 --> 00:35:47.859 align:start position:0% these krypter krypter graphic primitives 00:35:47.859 --> 00:35:49.500 align:start position:0% these krypter krypter graphic primitives for<00:35:48.430> like<00:35:48.579> two<00:35:48.730> more<00:35:48.849> minutes<00:35:48.910> and<00:35:49.240> then<00:35:49.359> we're 00:35:49.500 --> 00:35:49.510 align:start position:0% for like two more minutes and then we're 00:35:49.510 --> 00:35:51.690 align:start position:0% for like two more minutes and then we're gonna<00:35:49.660> get<00:35:49.869> back<00:35:49.990> to<00:35:50.680> the<00:35:50.950> regular<00:35:51.160> kind<00:35:51.550> of 00:35:51.690 --> 00:35:51.700 align:start position:0% gonna get back to the regular kind of 00:35:51.700 --> 00:35:53.160 align:start position:0% gonna get back to the regular kind of okay<00:35:51.970> now<00:35:52.119> we<00:35:52.180> put<00:35:52.390> this<00:35:52.480> here<00:35:52.660> and<00:35:52.720> now<00:35:52.869> we<00:35:52.990> put 00:35:53.160 --> 00:35:53.170 align:start position:0% okay now we put this here and now we put 00:35:53.170 --> 00:35:54.809 align:start position:0% okay now we put this here and now we put this<00:35:53.260> here<00:35:53.410> and<00:35:53.470> how<00:35:54.369> do<00:35:54.430> we<00:35:54.520> build<00:35:54.730> things 00:35:54.809 --> 00:35:54.819 align:start position:0% this here and how do we build things 00:35:54.819 --> 00:35:58.980 align:start position:0% this here and how do we build things with<00:35:55.030> this<00:35:55.589> okay<00:35:56.589> okay<00:35:56.829> so<00:35:57.400> so<00:35:58.089> the<00:35:58.510> reason<00:35:58.900> why 00:35:58.980 --> 00:35:58.990 align:start position:0% with this okay okay so so the reason why 00:35:58.990 --> 00:36:01.140 align:start position:0% with this okay okay so so the reason why we<00:35:59.109> don't<00:35:59.200> use<00:35:59.319> the<00:36:00.130> reason<00:36:00.430> why<00:36:00.520> we<00:36:00.640> pay<00:36:00.790> so<00:36:01.060> we 00:36:01.140 --> 00:36:01.150 align:start position:0% we don't use the reason why we pay so we 00:36:01.150 --> 00:36:04.290 align:start position:0% we don't use the reason why we pay so we use<00:36:01.300> it<00:36:01.420> twisted<00:36:01.690> Edwards<00:36:01.960> curve<00:36:03.089> yeah<00:36:04.089> we<00:36:04.210> use 00:36:04.290 --> 00:36:04.300 align:start position:0% use it twisted Edwards curve yeah we use 00:36:04.300 --> 00:36:05.970 align:start position:0% use it twisted Edwards curve yeah we use it<00:36:04.420> twisted<00:36:04.660> Edwards<00:36:04.900> curve<00:36:05.050> down<00:36:05.530> these<00:36:05.920> are 00:36:05.970 --> 00:36:05.980 align:start position:0% it twisted Edwards curve down these are 00:36:05.980 --> 00:36:07.440 align:start position:0% it twisted Edwards curve down these are the<00:36:06.160> formulas<00:36:06.490> neither<00:36:06.700> point<00:36:06.970> additions 00:36:07.440 --> 00:36:07.450 align:start position:0% the formulas neither point additions 00:36:07.450 --> 00:36:09.180 align:start position:0% the formulas neither point additions Ouisa<00:36:08.109> twisted<00:36:08.440> Edwards<00:36:08.680> curve<00:36:08.829> because<00:36:09.099> it 00:36:09.180 --> 00:36:09.190 align:start position:0% Ouisa twisted Edwards curve because it 00:36:09.190 --> 00:36:10.890 align:start position:0% Ouisa twisted Edwards curve because it doesn't<00:36:09.430> have<00:36:09.579> edge<00:36:09.849> cases<00:36:10.119> when<00:36:10.480> you<00:36:10.569> when 00:36:10.890 --> 00:36:10.900 align:start position:0% doesn't have edge cases when you when 00:36:10.900 --> 00:36:13.800 align:start position:0% doesn't have edge cases when you when you<00:36:11.050> double<00:36:11.950> the<00:36:12.040> identity<00:36:12.490> or<00:36:12.700> you<00:36:13.030> yeah<00:36:13.630> when 00:36:13.800 --> 00:36:13.810 align:start position:0% you double the identity or you yeah when 00:36:13.810 --> 00:36:15.089 align:start position:0% you double the identity or you yeah when you<00:36:13.900> double<00:36:14.140> the<00:36:14.200> identity<00:36:14.619> or<00:36:14.650> you<00:36:14.829> are<00:36:14.950> their 00:36:15.089 --> 00:36:15.099 align:start position:0% you double the identity or you are their 00:36:15.099 --> 00:36:17.880 align:start position:0% you double the identity or you are their identity<00:36:15.490> to<00:36:15.640> something<00:36:15.880> else<00:36:16.089> so<00:36:16.810> in<00:36:17.530> general 00:36:17.880 --> 00:36:17.890 align:start position:0% identity to something else so in general 00:36:17.890 --> 00:36:19.440 align:start position:0% identity to something else so in general in<00:36:18.099> science<00:36:18.369> we<00:36:18.430> don't<00:36:18.520> want<00:36:18.700> to<00:36:18.760> have<00:36:18.880> it<00:36:19.030> if 00:36:19.440 --> 00:36:19.450 align:start position:0% in science we don't want to have it if 00:36:19.450 --> 00:36:21.150 align:start position:0% in science we don't want to have it if we<00:36:19.869> had<00:36:19.990> an<00:36:20.079> edge<00:36:20.200> case<00:36:20.380> we'd<00:36:20.589> have<00:36:20.710> to<00:36:20.829> have<00:36:20.950> if 00:36:21.150 --> 00:36:21.160 align:start position:0% we had an edge case we'd have to have if 00:36:21.160 --> 00:36:22.829 align:start position:0% we had an edge case we'd have to have if we<00:36:21.730> had<00:36:21.849> an<00:36:21.970> edge<00:36:22.089> case<00:36:22.300> we'd<00:36:22.450> have<00:36:22.480> to<00:36:22.660> have<00:36:22.690> an 00:36:22.829 --> 00:36:22.839 align:start position:0% we had an edge case we'd have to have an 00:36:22.839 --> 00:36:24.569 align:start position:0% we had an edge case we'd have to have an if<00:36:22.960> loop<00:36:23.170> and<00:36:23.530> if<00:36:23.829> we<00:36:23.950> have<00:36:24.040> an<00:36:24.130> if<00:36:24.220> loop<00:36:24.400> that's 00:36:24.569 --> 00:36:24.579 align:start position:0% if loop and if we have an if loop that's 00:36:24.579 --> 00:36:25.680 align:start position:0% if loop and if we have an if loop that's that's<00:36:24.970> not<00:36:25.089> very<00:36:25.240> good 00:36:25.680 --> 00:36:25.690 align:start position:0% that's not very good 00:36:25.690 --> 00:36:27.270 align:start position:0% that's not very good inside<00:36:26.290> the<00:36:26.380> snark<00:36:26.560> it's<00:36:26.950> just<00:36:27.130> really 00:36:27.270 --> 00:36:27.280 align:start position:0% inside the snark it's just really 00:36:27.280 --> 00:36:29.220 align:start position:0% inside the snark it's just really expensive<00:36:27.520> to<00:36:27.849> do<00:36:27.940> in<00:36:28.030> a<00:36:28.089> loop<00:36:28.270> because<00:36:28.869> we 00:36:29.220 --> 00:36:29.230 align:start position:0% expensive to do in a loop because we 00:36:29.230 --> 00:36:31.200 align:start position:0% expensive to do in a loop because we have<00:36:29.349> to<00:36:29.470> do<00:36:29.560> everything<00:36:29.950> a<00:36:30.160> times<00:36:30.339> B<00:36:30.579> equals<00:36:31.089> C 00:36:31.200 --> 00:36:31.210 align:start position:0% have to do everything a times B equals C 00:36:31.210 --> 00:36:33.750 align:start position:0% have to do everything a times B equals C which<00:36:31.869> which<00:36:32.109> is<00:36:32.290> really<00:36:32.589> okay<00:36:33.369> there's 00:36:33.750 --> 00:36:33.760 align:start position:0% which which is really okay there's 00:36:33.760 --> 00:36:35.099 align:start position:0% which which is really okay there's another<00:36:34.000> example<00:36:34.180> how<00:36:34.540> do<00:36:34.599> you<00:36:34.750> make<00:36:34.930> an<00:36:35.020> if 00:36:35.099 --> 00:36:35.109 align:start position:0% another example how do you make an if 00:36:35.109 --> 00:36:36.480 align:start position:0% another example how do you make an if loop<00:36:35.290> with<00:36:35.410> a<00:36:35.470> times<00:36:35.650> B<00:36:35.800> equals<00:36:36.040> C<00:36:36.130> it's 00:36:36.480 --> 00:36:36.490 align:start position:0% loop with a times B equals C it's 00:36:36.490 --> 00:36:38.190 align:start position:0% loop with a times B equals C it's totally<00:36:36.790> possible<00:36:36.940> but<00:36:37.359> it's<00:36:37.510> it<00:36:37.839> turns<00:36:38.050> out 00:36:38.190 --> 00:36:38.200 align:start position:0% totally possible but it's it turns out 00:36:38.200 --> 00:36:39.300 align:start position:0% totally possible but it's it turns out that<00:36:38.319> it's<00:36:38.500> it's<00:36:38.710> prohibitively<00:36:39.190> expensive 00:36:39.300 --> 00:36:39.310 align:start position:0% that it's it's prohibitively expensive 00:36:39.310 --> 00:36:41.819 align:start position:0% that it's it's prohibitively expensive when<00:36:39.819> you<00:36:39.910> do<00:36:40.000> it<00:36:40.089> a<00:36:40.150> bunch<00:36:40.240> of<00:36:40.359> times<00:36:40.650> okay<00:36:41.650> so 00:36:41.819 --> 00:36:41.829 align:start position:0% when you do it a bunch of times okay so 00:36:41.829 --> 00:36:45.630 align:start position:0% when you do it a bunch of times okay so this<00:36:42.250> is<00:36:42.460> the<00:36:42.579> curve<00:36:42.880> due<00:36:43.869> to<00:36:44.460> these<00:36:45.460> are<00:36:45.579> the 00:36:45.630 --> 00:36:45.640 align:start position:0% this is the curve due to these are the 00:36:45.640 --> 00:36:46.849 align:start position:0% this is the curve due to these are the point<00:36:45.790> multiple 00:36:46.849 --> 00:36:46.859 align:start position:0% point multiple 00:36:46.859 --> 00:36:49.650 align:start position:0% point multiple so<00:36:47.859> then<00:36:48.040> okay<00:36:48.609> so<00:36:48.790> inside<00:36:49.180> the<00:36:49.270> curve<00:36:49.420> we<00:36:49.540> need 00:36:49.650 --> 00:36:49.660 align:start position:0% so then okay so inside the curve we need 00:36:49.660 --> 00:36:51.000 align:start position:0% so then okay so inside the curve we need so<00:36:50.079> we<00:36:50.109> need<00:36:50.380> to<00:36:50.470> be<00:36:50.560> able<00:36:50.619> to<00:36:50.770> do<00:36:50.829> two<00:36:50.980> things 00:36:51.000 --> 00:36:51.010 align:start position:0% so we need to be able to do two things 00:36:51.010 --> 00:36:54.089 align:start position:0% so we need to be able to do two things to<00:36:51.400> do<00:36:51.520> a<00:36:51.550> little<00:36:52.290> cryptography<00:36:53.290> the<00:36:53.470> first 00:36:54.089 --> 00:36:54.099 align:start position:0% to do a little cryptography the first 00:36:54.099 --> 00:36:55.950 align:start position:0% to do a little cryptography the first thing<00:36:54.220> is<00:36:54.339> to<00:36:54.460> do<00:36:54.550> point<00:36:54.849> additions<00:36:55.180> which<00:36:55.810> is 00:36:55.950 --> 00:36:55.960 align:start position:0% thing is to do point additions which is 00:36:55.960 --> 00:36:58.290 align:start position:0% thing is to do point additions which is easy<00:36:56.140> we<00:36:56.290> can<00:36:56.410> use<00:36:56.500> these<00:36:56.650> formulas<00:36:57.010> here<00:36:57.400> and 00:36:58.290 --> 00:36:58.300 align:start position:0% easy we can use these formulas here and 00:36:58.300 --> 00:36:59.790 align:start position:0% easy we can use these formulas here and we<00:36:58.390> can<00:36:58.540> implement<00:36:58.720> implement<00:36:59.079> those<00:36:59.500> inside 00:36:59.790 --> 00:36:59.800 align:start position:0% we can implement implement those inside 00:36:59.800 --> 00:37:02.190 align:start position:0% we can implement implement those inside the<00:36:59.829> snack<00:37:00.069> easily<00:37:00.730> the<00:37:01.569> second<00:37:01.839> is<00:37:01.960> to<00:37:01.990> do 00:37:02.190 --> 00:37:02.200 align:start position:0% the snack easily the second is to do 00:37:02.200 --> 00:37:04.500 align:start position:0% the snack easily the second is to do point<00:37:03.040> a<00:37:03.130> to<00:37:03.220> point<00:37:03.579> multiplicative 00:37:04.500 --> 00:37:04.510 align:start position:0% point a to point multiplicative 00:37:04.510 --> 00:37:06.059 align:start position:0% point a to point multiplicative multiplication<00:37:05.050> and<00:37:05.290> we<00:37:05.500> can<00:37:05.710> do<00:37:05.770> that<00:37:05.890> too 00:37:06.059 --> 00:37:06.069 align:start position:0% multiplication and we can do that too 00:37:06.069 --> 00:37:07.710 align:start position:0% multiplication and we can do that too it's<00:37:06.670> just<00:37:06.730> a<00:37:06.849> little<00:37:07.000> bit<00:37:07.089> more<00:37:07.180> complicated 00:37:07.710 --> 00:37:07.720 align:start position:0% it's just a little bit more complicated 00:37:07.720 --> 00:37:10.170 align:start position:0% it's just a little bit more complicated and<00:37:08.380> we<00:37:08.770> just<00:37:09.040> do<00:37:09.099> a<00:37:09.130> bunch<00:37:09.609> of<00:37:09.730> doublets 00:37:10.170 --> 00:37:10.180 align:start position:0% and we just do a bunch of doublets 00:37:10.180 --> 00:37:11.849 align:start position:0% and we just do a bunch of doublets actually<00:37:10.990> scalar<00:37:11.260> multiplication<00:37:11.829> just 00:37:11.849 --> 00:37:11.859 align:start position:0% actually scalar multiplication just 00:37:11.859 --> 00:37:14.490 align:start position:0% actually scalar multiplication just degrades<00:37:12.310> to<00:37:12.579> to<00:37:13.180> just<00:37:13.359> additions<00:37:13.839> well<00:37:14.410> yeah 00:37:14.490 --> 00:37:14.500 align:start position:0% degrades to to just additions well yeah 00:37:14.500 --> 00:37:16.050 align:start position:0% degrades to to just additions well yeah we<00:37:14.680> can<00:37:14.800> figure<00:37:14.920> that<00:37:15.069> out<00:37:15.130> too<00:37:15.339> and<00:37:15.550> you<00:37:15.790> yeah 00:37:16.050 --> 00:37:16.060 align:start position:0% we can figure that out too and you yeah 00:37:16.060 --> 00:37:17.730 align:start position:0% we can figure that out too and you yeah we<00:37:16.569> can<00:37:16.690> figure<00:37:16.780> out<00:37:16.900> a<00:37:16.960> 2<00:37:17.170> and<00:37:17.410> we<00:37:17.500> can<00:37:17.619> use 00:37:17.730 --> 00:37:17.740 align:start position:0% we can figure out a 2 and we can use 00:37:17.740 --> 00:37:19.290 align:start position:0% we can figure out a 2 and we can use window<00:37:18.040> exponentiation 00:37:19.290 --> 00:37:19.300 align:start position:0% window exponentiation 00:37:19.300 --> 00:37:20.700 align:start position:0% window exponentiation we<00:37:19.600> could<00:37:19.750> switch<00:37:19.930> to<00:37:19.960> window<00:37:20.230> exponentiation 00:37:20.700 --> 00:37:20.710 align:start position:0% we could switch to window exponentiation 00:37:20.710 --> 00:37:22.080 align:start position:0% we could switch to window exponentiation which<00:37:20.830> will<00:37:21.100> save<00:37:21.460> us<00:37:21.550> a<00:37:21.580> lot<00:37:21.640> of<00:37:21.790> constraints 00:37:22.080 --> 00:37:22.090 align:start position:0% which will save us a lot of constraints 00:37:22.090 --> 00:37:24.540 align:start position:0% which will save us a lot of constraints and<00:37:22.960> add<00:37:23.650> snags<00:37:23.950> have<00:37:24.130> done<00:37:24.280> that<00:37:24.400> already 00:37:24.540 --> 00:37:24.550 align:start position:0% and add snags have done that already 00:37:24.550 --> 00:37:26.310 align:start position:0% and add snags have done that already there<00:37:25.119> there<00:37:25.390> now<00:37:25.570> we<00:37:25.630> come<00:37:25.930> in<00:37:26.020> the<00:37:26.110> canonical 00:37:26.310 --> 00:37:26.320 align:start position:0% there there now we come in the canonical 00:37:26.320 --> 00:37:28.380 align:start position:0% there there now we come in the canonical implementation<00:37:26.710> although<00:37:27.700> circum<00:37:28.210> have<00:37:28.360> a 00:37:28.380 --> 00:37:28.390 align:start position:0% implementation although circum have a 00:37:28.390 --> 00:37:30.120 align:start position:0% implementation although circum have a competing<00:37:28.840> one<00:37:29.050> and<00:37:29.170> Socrates<00:37:29.560> are<00:37:29.680> gonna 00:37:30.120 --> 00:37:30.130 align:start position:0% competing one and Socrates are gonna 00:37:30.130 --> 00:37:31.920 align:start position:0% competing one and Socrates are gonna make<00:37:30.280> their<00:37:30.460> own<00:37:30.490> implementation<00:37:30.760> soon<00:37:31.300> so 00:37:31.920 --> 00:37:31.930 align:start position:0% make their own implementation soon so 00:37:31.930 --> 00:37:32.730 align:start position:0% make their own implementation soon so we're<00:37:32.050> gonna<00:37:32.140> have<00:37:32.320> a<00:37:32.350> bunch<00:37:32.560> of<00:37:32.650> these 00:37:32.730 --> 00:37:32.740 align:start position:0% we're gonna have a bunch of these 00:37:32.740 --> 00:37:34.460 align:start position:0% we're gonna have a bunch of these implementations<00:37:33.400> that<00:37:33.580> people<00:37:33.820> can<00:37:33.940> use<00:37:34.090> to 00:37:34.460 --> 00:37:34.470 align:start position:0% implementations that people can use to 00:37:34.470 --> 00:37:37.680 align:start position:0% implementations that people can use to do<00:37:35.470> electric<00:37:35.650> art<00:37:35.890> stuff<00:37:36.070> I<00:37:36.360> hope<00:37:37.360> it's<00:37:37.510> okay 00:37:37.680 --> 00:37:37.690 align:start position:0% do electric art stuff I hope it's okay 00:37:37.690 --> 00:37:47.820 align:start position:0% do electric art stuff I hope it's okay that<00:37:37.720> I<00:37:37.840> said<00:37:38.050> that<00:37:40.380> okay<00:37:46.320> okay<00:37:47.320> so<00:37:47.380> then<00:37:47.650> these 00:37:47.820 --> 00:37:47.830 align:start position:0% that I said that okay okay so then these 00:37:47.830 --> 00:37:49.380 align:start position:0% that I said that okay okay so then these are<00:37:47.890> some<00:37:48.130> links<00:37:48.640> that<00:37:48.820> will<00:37:48.940> teach<00:37:49.150> you<00:37:49.270> about 00:37:49.380 --> 00:37:49.390 align:start position:0% are some links that will teach you about 00:37:49.390 --> 00:37:51.120 align:start position:0% are some links that will teach you about elliptic<00:37:49.780> curve<00:37:50.020> operations<00:37:50.500> and<00:37:50.710> how<00:37:50.890> to<00:37:50.950> do 00:37:51.120 --> 00:37:51.130 align:start position:0% elliptic curve operations and how to do 00:37:51.130 --> 00:37:53.220 align:start position:0% elliptic curve operations and how to do that<00:37:51.310> and<00:37:51.490> just<00:37:51.520> a<00:37:52.270> general<00:37:52.450> background<00:37:52.660> yeah 00:37:53.220 --> 00:37:53.230 align:start position:0% that and just a general background yeah 00:37:53.230 --> 00:37:55.410 align:start position:0% that and just a general background yeah because<00:37:53.590> this<00:37:54.310> is<00:37:54.490> I<00:37:54.730> mean<00:37:54.910> the<00:37:55.060> last<00:37:55.180> couple 00:37:55.410 --> 00:37:55.420 align:start position:0% because this is I mean the last couple 00:37:55.420 --> 00:37:56.790 align:start position:0% because this is I mean the last couple of<00:37:55.450> slides<00:37:55.540> were<00:37:55.780> generally<00:37:56.200> difficult<00:37:56.470> off 00:37:56.790 --> 00:37:56.800 align:start position:0% of slides were generally difficult off 00:37:56.800 --> 00:37:58.650 align:start position:0% of slides were generally difficult off and<00:37:57.130> it's<00:37:57.490> okay<00:37:57.730> that<00:37:57.940> if<00:37:58.210> you<00:37:58.420> didn't 00:37:58.650 --> 00:37:58.660 align:start position:0% and it's okay that if you didn't 00:37:58.660 --> 00:38:00.750 align:start position:0% and it's okay that if you didn't understand<00:37:58.990> them<00:37:59.110> I'm<00:37:59.410> and<00:38:00.310> now<00:38:00.490> we're<00:38:00.640> gonna 00:38:00.750 --> 00:38:00.760 align:start position:0% understand them I'm and now we're gonna 00:38:00.760 --> 00:38:04.320 align:start position:0% understand them I'm and now we're gonna get<00:38:00.880> back<00:38:01.030> to<00:38:01.180> that<00:38:01.210> oh<00:38:02.880> yeah<00:38:03.880> so<00:38:04.030> I<00:38:04.060> just<00:38:04.210> had 00:38:04.320 --> 00:38:04.330 align:start position:0% get back to that oh yeah so I just had 00:38:04.330 --> 00:38:06.750 align:start position:0% get back to that oh yeah so I just had some<00:38:04.450> future<00:38:04.690> work<00:38:04.810> about<00:38:04.960> this<00:38:05.110> so<00:38:05.740> and<00:38:06.640> then 00:38:06.750 --> 00:38:06.760 align:start position:0% some future work about this so and then 00:38:06.760 --> 00:38:07.560 align:start position:0% some future work about this so and then we're<00:38:06.850> gonna<00:38:06.940> get<00:38:07.090> back<00:38:07.240> to<00:38:07.330> the<00:38:07.450> regular 00:38:07.560 --> 00:38:07.570 align:start position:0% we're gonna get back to the regular 00:38:07.570 --> 00:38:12.180 align:start position:0% we're gonna get back to the regular stuff<00:38:07.900> so<00:38:10.470> I'm<00:38:11.470> not<00:38:11.590> sure<00:38:11.650> that<00:38:11.770> link<00:38:12.040> is<00:38:12.160> right 00:38:12.180 --> 00:38:12.190 align:start position:0% stuff so I'm not sure that link is right 00:38:12.190 --> 00:38:17.160 align:start position:0% stuff so I'm not sure that link is right but<00:38:13.180> you<00:38:13.240> guys<00:38:13.690> you<00:38:13.930> folks<00:38:14.890> can<00:38:15.070> find<00:38:15.100> it<00:38:16.170> okay 00:38:17.160 --> 00:38:17.170 align:start position:0% but you guys you folks can find it okay 00:38:17.170 --> 00:38:19.410 align:start position:0% but you guys you folks can find it okay so<00:38:17.230> so<00:38:17.710> future<00:38:18.130> work<00:38:18.280> so<00:38:18.670> the<00:38:18.940> first<00:38:19.060> thing<00:38:19.300> is 00:38:19.410 --> 00:38:19.420 align:start position:0% so so future work so the first thing is 00:38:19.420 --> 00:38:21.600 align:start position:0% so so future work so the first thing is that<00:38:19.450> this<00:38:19.810> this<00:38:20.140> this<00:38:20.920> work<00:38:21.220> should<00:38:21.490> be 00:38:21.600 --> 00:38:21.610 align:start position:0% that this this this work should be 00:38:21.610 --> 00:38:23.970 align:start position:0% that this this this work should be treated<00:38:22.140> yeah<00:38:23.140> this<00:38:23.320> work<00:38:23.530> hasn't<00:38:23.740> been 00:38:23.970 --> 00:38:23.980 align:start position:0% treated yeah this work hasn't been 00:38:23.980 --> 00:38:26.520 align:start position:0% treated yeah this work hasn't been reviewed<00:38:24.340> and<00:38:24.550> I<00:38:25.450> don't<00:38:25.570> think<00:38:25.930> that<00:38:26.109> anybody 00:38:26.520 --> 00:38:26.530 align:start position:0% reviewed and I don't think that anybody 00:38:26.530 --> 00:38:27.990 align:start position:0% reviewed and I don't think that anybody should<00:38:26.619> use<00:38:26.859> this<00:38:26.980> in<00:38:27.130> production<00:38:27.250> until<00:38:27.670> it's 00:38:27.990 --> 00:38:28.000 align:start position:0% should use this in production until it's 00:38:28.000 --> 00:38:31.230 align:start position:0% should use this in production until it's been<00:38:28.150> reviewed<00:38:28.540> a<00:38:28.750> lot<00:38:29.310> this<00:38:30.310> is<00:38:30.369> like<00:38:31.090> the 00:38:31.230 --> 00:38:31.240 align:start position:0% been reviewed a lot this is like the 00:38:31.240 --> 00:38:32.880 align:start position:0% been reviewed a lot this is like the rule<00:38:31.420> in<00:38:31.540> crypto<00:38:31.840> waste<00:38:31.990> or<00:38:32.170> the<00:38:32.560> rule<00:38:32.770> in 00:38:32.880 --> 00:38:32.890 align:start position:0% rule in crypto waste or the rule in 00:38:32.890 --> 00:38:34.140 align:start position:0% rule in crypto waste or the rule in crypto<00:38:33.130> currencies<00:38:33.490> is<00:38:33.609> don't<00:38:33.790> roll<00:38:33.940> your<00:38:34.090> own 00:38:34.140 --> 00:38:34.150 align:start position:0% crypto currencies is don't roll your own 00:38:34.150 --> 00:38:44.340 align:start position:0% crypto currencies is don't roll your own crypto<00:38:34.890> and<00:38:35.890> I<00:38:36.010> did<00:38:42.420> okay<00:38:43.420> so<00:38:43.480> so<00:38:43.960> please<00:38:44.170> be 00:38:44.340 --> 00:38:44.350 align:start position:0% crypto and I did okay so so please be 00:38:44.350 --> 00:38:46.109 align:start position:0% crypto and I did okay so so please be very<00:38:44.500> careful<00:38:44.680> about<00:38:44.920> this<00:38:45.160> also<00:38:45.490> if<00:38:45.760> you<00:38:45.880> have 00:38:46.109 --> 00:38:46.119 align:start position:0% very careful about this also if you have 00:38:46.119 --> 00:38:48.690 align:start position:0% very careful about this also if you have crypto<00:38:46.530> cryptography<00:38:47.530> expertise<00:38:47.980> it<00:38:48.550> would 00:38:48.690 --> 00:38:48.700 align:start position:0% crypto cryptography expertise it would 00:38:48.700 --> 00:38:50.070 align:start position:0% crypto cryptography expertise it would be<00:38:48.820> I'd<00:38:49.060> be<00:38:49.210> very<00:38:49.330> interested<00:38:49.450> to<00:38:49.750> talk<00:38:49.869> to<00:38:49.990> you 00:38:50.070 --> 00:38:50.080 align:start position:0% be I'd be very interested to talk to you 00:38:50.080 --> 00:38:51.810 align:start position:0% be I'd be very interested to talk to you about<00:38:50.200> sort<00:38:50.560> of<00:38:50.619> reviewing<00:38:51.460> some<00:38:51.609> of<00:38:51.730> this 00:38:51.810 --> 00:38:51.820 align:start position:0% about sort of reviewing some of this 00:38:51.820 --> 00:38:55.170 align:start position:0% about sort of reviewing some of this work<00:38:52.060> and<00:38:52.270> so<00:38:52.830> more<00:38:53.830> people<00:38:53.950> can<00:38:54.160> use<00:38:54.340> it<00:38:54.490> but 00:38:55.170 --> 00:38:55.180 align:start position:0% work and so more people can use it but 00:38:55.180 --> 00:38:57.390 align:start position:0% work and so more people can use it but at<00:38:55.810> least<00:38:56.170> we<00:38:56.440> should<00:38:56.710> say<00:38:56.980> that<00:38:57.010> it's 00:38:57.390 --> 00:38:57.400 align:start position:0% at least we should say that it's 00:38:57.400 --> 00:38:58.849 align:start position:0% at least we should say that it's possible<00:38:57.880> to<00:38:58.000> do<00:38:58.150> this<00:38:58.390> kind<00:38:58.630> of 00:38:58.849 --> 00:38:58.859 align:start position:0% possible to do this kind of 00:38:58.859 --> 00:39:02.160 align:start position:0% possible to do this kind of cryptographic<00:38:59.859> stuff<00:39:00.250> inside<00:39:00.520> a<00:39:00.550> snark<00:39:01.170> this 00:39:02.160 --> 00:39:02.170 align:start position:0% cryptographic stuff inside a snark this 00:39:02.170 --> 00:39:03.870 align:start position:0% cryptographic stuff inside a snark this is<00:39:02.320> yeah<00:39:02.740> this<00:39:02.770> is<00:39:03.010> at<00:39:03.130> least<00:39:03.160> an<00:39:03.430> example<00:39:03.790> of 00:39:03.870 --> 00:39:03.880 align:start position:0% is yeah this is at least an example of 00:39:03.880 --> 00:39:09.660 align:start position:0% is yeah this is at least an example of how<00:39:04.000> that's<00:39:04.119> possible<00:39:08.040> so<00:39:09.040> it's<00:39:09.160> for<00:39:09.280> pedestal 00:39:09.660 --> 00:39:09.670 align:start position:0% how that's possible so it's for pedestal 00:39:09.670 --> 00:39:11.849 align:start position:0% how that's possible so it's for pedestal hashes<00:39:09.940> and<00:39:10.150> signature<00:39:11.140> scheme<00:39:11.350> which<00:39:11.740> I'll 00:39:11.849 --> 00:39:11.859 align:start position:0% hashes and signature scheme which I'll 00:39:11.859 --> 00:39:15.390 align:start position:0% hashes and signature scheme which I'll talk<00:39:11.950> about<00:39:12.010> in<00:39:12.220> a<00:39:12.250> second<00:39:13.170> yeah<00:39:14.170> so<00:39:14.650> okay<00:39:15.070> so 00:39:15.390 --> 00:39:15.400 align:start position:0% talk about in a second yeah so okay so 00:39:15.400 --> 00:39:16.500 align:start position:0% talk about in a second yeah so okay so we'll<00:39:15.640> be<00:39:15.760> good<00:39:15.880> to<00:39:15.940> get<00:39:16.030> some<00:39:16.090> review<00:39:16.480> and 00:39:16.500 --> 00:39:16.510 align:start position:0% we'll be good to get some review and 00:39:16.510 --> 00:39:19.200 align:start position:0% we'll be good to get some review and here's<00:39:16.900> where<00:39:17.140> you<00:39:17.230> can<00:39:17.350> review<00:39:17.500> it<00:39:17.970> and<00:39:18.970> then 00:39:19.200 --> 00:39:19.210 align:start position:0% here's where you can review it and then 00:39:19.210 --> 00:39:21.359 align:start position:0% here's where you can review it and then there's<00:39:19.780> possibility<00:39:20.410> that<00:39:20.560> we<00:39:21.130> could<00:39:21.250> build 00:39:21.359 --> 00:39:21.369 align:start position:0% there's possibility that we could build 00:39:21.369 --> 00:39:22.980 align:start position:0% there's possibility that we could build bowler<00:39:21.640> proofs<00:39:21.880> in<00:39:22.000> the<00:39:22.090> same<00:39:22.270> way<00:39:22.480> and<00:39:22.750> embed 00:39:22.980 --> 00:39:22.990 align:start position:0% bowler proofs in the same way and embed 00:39:22.990 --> 00:39:24.180 align:start position:0% bowler proofs in the same way and embed them<00:39:23.080> inside<00:39:23.320> the<00:39:23.410> snack<00:39:23.590> and<00:39:23.740> that's<00:39:23.890> a<00:39:23.980> nice 00:39:24.180 --> 00:39:24.190 align:start position:0% them inside the snack and that's a nice 00:39:24.190 --> 00:39:25.800 align:start position:0% them inside the snack and that's a nice interesting<00:39:24.460> that's<00:39:25.030> interesting<00:39:25.180> like<00:39:25.780> a 00:39:25.800 --> 00:39:25.810 align:start position:0% interesting that's interesting like a 00:39:25.810 --> 00:39:28.470 align:start position:0% interesting that's interesting like a research<00:39:26.290> problem<00:39:26.500> and<00:39:26.830> then<00:39:27.520> there<00:39:28.030> is<00:39:28.119> also 00:39:28.470 --> 00:39:28.480 align:start position:0% research problem and then there is also 00:39:28.480 --> 00:39:29.970 align:start position:0% research problem and then there is also it<00:39:28.930> would<00:39:29.080> be<00:39:29.200> cool<00:39:29.380> if<00:39:29.470> we<00:39:29.530> could<00:39:29.590> do<00:39:29.800> like 00:39:29.970 --> 00:39:29.980 align:start position:0% it would be cool if we could do like 00:39:29.980 --> 00:39:31.260 align:start position:0% it would be cool if we could do like recursive<00:39:30.460> snacks<00:39:30.640> or<00:39:30.850> at<00:39:31.000> least<00:39:31.150> requires 00:39:31.260 --> 00:39:31.270 align:start position:0% recursive snacks or at least requires 00:39:31.270 --> 00:39:32.200 align:start position:0% recursive snacks or at least requires one<00:39:31.630> layer 00:39:32.200 --> 00:39:32.210 align:start position:0% one layer 00:39:32.210 --> 00:39:33.730 align:start position:0% one layer and<00:39:32.300> then<00:39:32.630> we<00:39:32.750> can<00:39:32.869> do<00:39:32.990> something<00:39:33.260> like<00:39:33.500> the 00:39:33.730 --> 00:39:33.740 align:start position:0% and then we can do something like the 00:39:33.740 --> 00:39:36.700 align:start position:0% and then we can do something like the sea<00:39:34.640> paper<00:39:35.480> there<00:39:36.020> was<00:39:36.050> this<00:39:36.230> paper<00:39:36.410> recently 00:39:36.700 --> 00:39:36.710 align:start position:0% sea paper there was this paper recently 00:39:36.710 --> 00:39:38.559 align:start position:0% sea paper there was this paper recently about<00:39:37.040> using<00:39:37.309> recursive<00:39:37.640> snacks<00:39:37.970> to<00:39:38.150> do<00:39:38.300> like 00:39:38.559 --> 00:39:38.569 align:start position:0% about using recursive snacks to do like 00:39:38.569 --> 00:39:41.349 align:start position:0% about using recursive snacks to do like private<00:39:39.319> smart<00:39:39.500> contracts<00:39:40.059> so<00:39:41.059> that<00:39:41.210> would 00:39:41.349 --> 00:39:41.359 align:start position:0% private smart contracts so that would 00:39:41.359 --> 00:39:43.660 align:start position:0% private smart contracts so that would that's<00:39:41.450> an<00:39:41.630> also<00:39:41.869> an<00:39:41.960> interesting<00:39:42.550> sort<00:39:43.550> of 00:39:43.660 --> 00:39:43.670 align:start position:0% that's an also an interesting sort of 00:39:43.670 --> 00:39:48.130 align:start position:0% that's an also an interesting sort of future<00:39:43.910> future<00:39:44.450> direction<00:39:45.460> okay<00:39:47.020> okay<00:39:48.020> I<00:39:48.050> know 00:39:48.130 --> 00:39:48.140 align:start position:0% future future direction okay okay I know 00:39:48.140 --> 00:39:49.750 align:start position:0% future future direction okay okay I know also<00:39:48.500> I<00:39:48.530> want<00:39:48.740> to<00:39:48.800> say<00:39:48.890> thanks<00:39:49.160> to<00:39:49.190> Dario 00:39:49.750 --> 00:39:49.760 align:start position:0% also I want to say thanks to Dario 00:39:49.760 --> 00:39:52.420 align:start position:0% also I want to say thanks to Dario Hopwood<00:39:50.089> and<00:39:50.300> and<00:39:50.569> for<00:39:51.349> for<00:39:52.010> help<00:39:52.220> and<00:39:52.339> advice 00:39:52.420 --> 00:39:52.430 align:start position:0% Hopwood and and for for help and advice 00:39:52.430 --> 00:39:54.430 align:start position:0% Hopwood and and for for help and advice about<00:39:52.760> this<00:39:53.000> as<00:39:53.300> well<00:39:53.540> as<00:39:53.720> the<00:39:53.900> Z<00:39:54.050> cash<00:39:54.230> team 00:39:54.430 --> 00:39:54.440 align:start position:0% about this as well as the Z cash team 00:39:54.440 --> 00:39:57.700 align:start position:0% about this as well as the Z cash team who<00:39:54.950> had<00:39:55.430> done<00:39:55.609> who<00:39:56.059> III<00:39:56.390> who<00:39:57.380> had<00:39:57.500> done<00:39:57.650> very 00:39:57.700 --> 00:39:57.710 align:start position:0% who had done who III who had done very 00:39:57.710 --> 00:40:00.250 align:start position:0% who had done who III who had done very similar<00:39:58.130> work<00:39:58.369> before<00:39:58.670> me<00:39:58.790> and<00:39:58.970> really<00:39:59.750> lit 00:40:00.250 --> 00:40:00.260 align:start position:0% similar work before me and really lit 00:40:00.260 --> 00:40:02.290 align:start position:0% similar work before me and really lit away<00:40:00.530> from<00:40:00.740> me<00:40:00.829> when<00:40:00.980> I<00:40:01.010> was<00:40:01.160> doing<00:40:01.220> this<00:40:01.460> it 00:40:02.290 --> 00:40:02.300 align:start position:0% away from me when I was doing this it 00:40:02.300 --> 00:40:04.180 align:start position:0% away from me when I was doing this it specifically<00:40:02.930> this<00:40:03.079> issue<00:40:03.260> you<00:40:03.500> can<00:40:03.650> see<00:40:03.800> it's 00:40:04.180 --> 00:40:04.190 align:start position:0% specifically this issue you can see it's 00:40:04.190 --> 00:40:06.609 align:start position:0% specifically this issue you can see it's so<00:40:04.339> cool<00:40:04.609> they<00:40:05.030> just<00:40:05.210> describe<00:40:05.690> everything<00:40:05.900> or 00:40:06.609 --> 00:40:06.619 align:start position:0% so cool they just describe everything or 00:40:06.619 --> 00:40:07.690 align:start position:0% so cool they just describe everything or every<00:40:07.010> single<00:40:07.160> step<00:40:07.460> of<00:40:07.579> their 00:40:07.690 --> 00:40:07.700 align:start position:0% every single step of their 00:40:07.700 --> 00:40:09.700 align:start position:0% every single step of their decision-making<00:40:08.150> and<00:40:08.750> then<00:40:09.079> they<00:40:09.200> also<00:40:09.530> have 00:40:09.700 --> 00:40:09.710 align:start position:0% decision-making and then they also have 00:40:09.710 --> 00:40:15.910 align:start position:0% decision-making and then they also have a<00:40:09.770> blog<00:40:09.890> post<00:40:09.950> about<00:40:10.300> about<00:40:11.300> how<00:40:11.420> to<00:40:12.349> do<00:40:12.440> so<00:40:14.920> and 00:40:15.910 --> 00:40:15.920 align:start position:0% a blog post about about how to do so and 00:40:15.920 --> 00:40:17.410 align:start position:0% a blog post about about how to do so and actually<00:40:16.550> they're<00:40:16.670> using<00:40:16.700> it<00:40:17.059> now<00:40:17.180> in<00:40:17.329> the 00:40:17.410 --> 00:40:17.420 align:start position:0% actually they're using it now in the 00:40:17.420 --> 00:40:20.170 align:start position:0% actually they're using it now in the wild<00:40:17.540> so<00:40:18.470> they<00:40:18.500> just<00:40:19.160> had<00:40:19.250> a<00:40:19.280> couple<00:40:19.940> of<00:40:20.030> days 00:40:20.170 --> 00:40:20.180 align:start position:0% wild so they just had a couple of days 00:40:20.180 --> 00:40:23.589 align:start position:0% wild so they just had a couple of days ago<00:40:20.390> another<00:40:21.290> they're<00:40:22.250> using<00:40:22.849> Patterson 00:40:23.589 --> 00:40:23.599 align:start position:0% ago another they're using Patterson 00:40:23.599 --> 00:40:27.069 align:start position:0% ago another they're using Patterson commitments<00:40:24.109> oh<00:40:24.890> yeah<00:40:25.460> so<00:40:25.730> I<00:40:26.030> should<00:40:27.020> have 00:40:27.069 --> 00:40:27.079 align:start position:0% commitments oh yeah so I should have 00:40:27.079 --> 00:40:29.980 align:start position:0% commitments oh yeah so I should have talked<00:40:27.290> about<00:40:27.410> that<00:40:27.680> oh<00:40:27.880> sorry<00:40:28.880> okay<00:40:29.329> so<00:40:29.390> so 00:40:29.980 --> 00:40:29.990 align:start position:0% talked about that oh sorry okay so so 00:40:29.990 --> 00:40:32.049 align:start position:0% talked about that oh sorry okay so so what<00:40:30.020> can<00:40:30.319> we<00:40:30.440> actually<00:40:30.589> use<00:40:30.980> this<00:40:31.250> to<00:40:31.460> do<00:40:31.670> like 00:40:32.049 --> 00:40:32.059 align:start position:0% what can we actually use this to do like 00:40:32.059 --> 00:40:33.490 align:start position:0% what can we actually use this to do like what<00:40:32.240> is<00:40:32.390> the<00:40:32.569> what<00:40:32.780> is<00:40:32.900> elliptic<00:40:33.349> curve 00:40:33.490 --> 00:40:33.500 align:start position:0% what is the what is elliptic curve 00:40:33.500 --> 00:40:35.530 align:start position:0% what is the what is elliptic curve inside<00:40:33.770> it's<00:40:33.920> not<00:40:33.950> useful<00:40:34.280> for<00:40:34.490> and<00:40:35.420> the 00:40:35.530 --> 00:40:35.540 align:start position:0% inside it's not useful for and the 00:40:35.540 --> 00:40:38.380 align:start position:0% inside it's not useful for and the answer<00:40:35.839> is<00:40:35.990> as<00:40:36.380> you<00:40:36.619> said<00:40:36.859> as<00:40:37.700> you<00:40:38.150> asked 00:40:38.380 --> 00:40:38.390 align:start position:0% answer is as you said as you asked 00:40:38.390 --> 00:40:40.030 align:start position:0% answer is as you said as you asked Patterson<00:40:38.720> commitments<00:40:39.109> and<00:40:39.230> and<00:40:39.619> signature 00:40:40.030 --> 00:40:40.040 align:start position:0% Patterson commitments and and signature 00:40:40.040 --> 00:40:42.460 align:start position:0% Patterson commitments and and signature scheme<00:40:40.250> so<00:40:40.880> on<00:40:41.210> top<00:40:41.359> of<00:40:41.510> this<00:40:41.599> on<00:40:42.140> top<00:40:42.290> of<00:40:42.410> this 00:40:42.460 --> 00:40:42.470 align:start position:0% scheme so on top of this on top of this 00:40:42.470 --> 00:40:45.220 align:start position:0% scheme so on top of this on top of this we<00:40:42.650> built<00:40:42.950> a<00:40:43.160> I<00:40:43.490> built<00:40:44.089> a<00:40:44.240> Patterson 00:40:45.220 --> 00:40:45.230 align:start position:0% we built a I built a Patterson 00:40:45.230 --> 00:40:46.599 align:start position:0% we built a I built a Patterson commitments<00:40:45.589> and<00:40:45.680> signature<00:40:46.220> scheme<00:40:46.400> and 00:40:46.599 --> 00:40:46.609 align:start position:0% commitments and signature scheme and 00:40:46.609 --> 00:40:50.770 align:start position:0% commitments and signature scheme and ethnics<00:40:47.540> have<00:40:47.630> also<00:40:47.780> implemented<00:40:48.200> it<00:40:49.450> so<00:40:50.450> and 00:40:50.770 --> 00:40:50.780 align:start position:0% ethnics have also implemented it so and 00:40:50.780 --> 00:40:52.599 align:start position:0% ethnics have also implemented it so and zk<00:40:51.559> are<00:40:51.770> now<00:40:51.890> using<00:40:52.069> this<00:40:52.250> in<00:40:52.400> the<00:40:52.460> world 00:40:52.599 --> 00:40:52.609 align:start position:0% zk are now using this in the world 00:40:52.609 --> 00:40:53.950 align:start position:0% zk are now using this in the world they've<00:40:52.819> had<00:40:52.940> a<00:40:52.970> daughter<00:40:53.210> did<00:40:53.510> although 00:40:53.950 --> 00:40:53.960 align:start position:0% they've had a daughter did although 00:40:53.960 --> 00:40:55.539 align:start position:0% they've had a daughter did although their<00:40:54.230> work<00:40:54.440> is<00:40:54.650> is<00:40:54.859> a<00:40:54.890> little<00:40:55.190> bit<00:40:55.280> different 00:40:55.539 --> 00:40:55.549 align:start position:0% their work is is a little bit different 00:40:55.549 --> 00:40:56.620 align:start position:0% their work is is a little bit different than<00:40:55.640> ours<00:40:55.819> because<00:40:56.059> they<00:40:56.299> use<00:40:56.420> the<00:40:56.540> different 00:40:56.620 --> 00:40:56.630 align:start position:0% than ours because they use the different 00:40:56.630 --> 00:40:59.770 align:start position:0% than ours because they use the different they<00:40:57.619> do<00:40:57.680> use<00:40:58.010> a<00:40:58.040> different<00:40:58.480> curve<00:40:59.480> and<00:40:59.750> that 00:40:59.770 --> 00:40:59.780 align:start position:0% they do use a different curve and that 00:40:59.780 --> 00:41:01.780 align:start position:0% they do use a different curve and that means<00:41:00.049> that<00:41:00.200> they're<00:41:00.410> yeah<00:41:00.980> so<00:41:01.190> their<00:41:01.339> their 00:41:01.780 --> 00:41:01.790 align:start position:0% means that they're yeah so their their 00:41:01.790 --> 00:41:03.880 align:start position:0% means that they're yeah so their their work<00:41:01.819> is<00:41:02.150> not<00:41:02.299> directly<00:41:02.660> trans<00:41:03.020> transferable 00:41:03.880 --> 00:41:03.890 align:start position:0% work is not directly trans transferable 00:41:03.890 --> 00:41:07.150 align:start position:0% work is not directly trans transferable but<00:41:04.099> it's<00:41:04.790> still<00:41:05.359> like<00:41:05.750> a<00:41:05.780> proof<00:41:06.319> of<00:41:06.530> concept 00:41:07.150 --> 00:41:07.160 align:start position:0% but it's still like a proof of concept 00:41:07.160 --> 00:41:10.960 align:start position:0% but it's still like a proof of concept that<00:41:07.190> this<00:41:07.339> is<00:41:07.490> possible<00:41:08.109> okay<00:41:09.339> so<00:41:10.339> a<00:41:10.369> big<00:41:10.819> nice 00:41:10.960 --> 00:41:10.970 align:start position:0% that this is possible okay so a big nice 00:41:10.970 --> 00:41:12.190 align:start position:0% that this is possible okay so a big nice alignment<00:41:11.150> congratulations<00:41:11.930> that<00:41:12.020> I'm<00:41:12.109> on 00:41:12.190 --> 00:41:12.200 align:start position:0% alignment congratulations that I'm on 00:41:12.200 --> 00:41:14.220 align:start position:0% alignment congratulations that I'm on their<00:41:12.319> recent<00:41:12.500> hired<00:41:12.740> Fork<00:41:13.069> it's<00:41:13.490> cool<00:41:13.700> okay 00:41:14.220 --> 00:41:14.230 align:start position:0% their recent hired Fork it's cool okay 00:41:14.230 --> 00:41:16.960 align:start position:0% their recent hired Fork it's cool okay so<00:41:15.230> next<00:41:15.770> we're<00:41:16.099> gonna<00:41:16.190> talk<00:41:16.400> about<00:41:16.430> we're 00:41:16.960 --> 00:41:16.970 align:start position:0% so next we're gonna talk about we're 00:41:16.970 --> 00:41:20.920 align:start position:0% so next we're gonna talk about we're gonna<00:41:17.089> talk<00:41:17.299> about<00:41:17.329> scalability<00:41:17.750> so<00:41:19.930> 20 00:41:20.920 --> 00:41:20.930 align:start position:0% gonna talk about scalability so 20 00:41:20.930 --> 00:41:22.599 align:start position:0% gonna talk about scalability so 20 minutes<00:41:21.020> cool<00:41:21.290> okay<00:41:22.130> so<00:41:22.190> next<00:41:22.339> we're<00:41:22.520> gonna 00:41:22.599 --> 00:41:22.609 align:start position:0% minutes cool okay so next we're gonna 00:41:22.609 --> 00:41:24.640 align:start position:0% minutes cool okay so next we're gonna talk<00:41:22.760> about<00:41:22.790> scalability<00:41:23.180> so<00:41:23.750> so<00:41:24.200> far<00:41:24.410> we've 00:41:24.640 --> 00:41:24.650 align:start position:0% talk about scalability so so far we've 00:41:24.650 --> 00:41:31.420 align:start position:0% talk about scalability so so far we've done<00:41:26.619> so<00:41:27.619> far<00:41:29.589> yeah<00:41:30.589> so<00:41:30.770> so<00:41:30.920> far<00:41:31.069> we've<00:41:31.220> just 00:41:31.420 --> 00:41:31.430 align:start position:0% done so far yeah so so far we've just 00:41:31.430 --> 00:41:33.250 align:start position:0% done so far yeah so so far we've just talked<00:41:31.609> about<00:41:31.700> using<00:41:32.119> using<00:41:32.599> snacks<00:41:32.990> for 00:41:33.250 --> 00:41:33.260 align:start position:0% talked about using using snacks for 00:41:33.260 --> 00:41:34.780 align:start position:0% talked about using using snacks for privacy<00:41:33.680> and<00:41:34.069> now<00:41:34.160> we're<00:41:34.280> gonna<00:41:34.369> talk<00:41:34.549> about 00:41:34.780 --> 00:41:34.790 align:start position:0% privacy and now we're gonna talk about 00:41:34.790 --> 00:41:38.490 align:start position:0% privacy and now we're gonna talk about using<00:41:34.910> snacks<00:41:35.180> for<00:41:35.329> scalability<00:41:35.799> so<00:41:36.799> we<00:41:37.520> can 00:41:38.490 --> 00:41:38.500 align:start position:0% using snacks for scalability so we can 00:41:38.500 --> 00:41:40.900 align:start position:0% using snacks for scalability so we can so<00:41:39.500> so<00:41:39.740> the<00:41:39.890> thing<00:41:39.920> that<00:41:40.190> we<00:41:40.280> were<00:41:40.400> missing<00:41:40.549> was 00:41:40.900 --> 00:41:40.910 align:start position:0% so so the thing that we were missing was 00:41:40.910 --> 00:41:43.870 align:start position:0% so so the thing that we were missing was a<00:41:41.180> signature<00:41:41.630> scheme<00:41:41.960> before<00:41:42.500> before<00:41:43.010> that<00:41:43.190> we 00:41:43.870 --> 00:41:43.880 align:start position:0% a signature scheme before before that we 00:41:43.880 --> 00:41:45.940 align:start position:0% a signature scheme before before that we weren't<00:41:44.660> able<00:41:44.720> to<00:41:44.960> really<00:41:45.170> use<00:41:45.200> it<00:41:45.410> for 00:41:45.940 --> 00:41:45.950 align:start position:0% weren't able to really use it for 00:41:45.950 --> 00:41:48.640 align:start position:0% weren't able to really use it for for<00:41:46.339> privacy<00:41:46.940> but<00:41:47.180> now<00:41:47.300> we<00:41:47.359> can<00:41:47.630> or<00:41:48.260> for 00:41:48.640 --> 00:41:48.650 align:start position:0% for privacy but now we can or for 00:41:48.650 --> 00:41:51.609 align:start position:0% for privacy but now we can or for scalability<00:41:49.130> but<00:41:49.430> now<00:41:49.550> we<00:41:49.640> can<00:41:50.349> so<00:41:51.349> here's 00:41:51.609 --> 00:41:51.619 align:start position:0% scalability but now we can so here's 00:41:51.619 --> 00:41:54.880 align:start position:0% scalability but now we can so here's here's<00:41:52.250> what<00:41:52.520> we<00:41:52.640> do<00:41:52.760> we<00:41:52.910> take<00:41:53.089> the<00:41:53.359> we<00:41:54.260> take<00:41:54.440> we 00:41:54.880 --> 00:41:54.890 align:start position:0% here's what we do we take the we take we 00:41:54.890 --> 00:41:57.670 align:start position:0% here's what we do we take the we take we make<00:41:55.369> this<00:41:55.520> new<00:41:55.760> form<00:41:56.119> as<00:41:56.960> opposed<00:41:57.410> to<00:41:57.560> before 00:41:57.670 --> 00:41:57.680 align:start position:0% make this new form as opposed to before 00:41:57.680 --> 00:41:59.560 align:start position:0% make this new form as opposed to before where<00:41:58.130> we<00:41:58.250> had<00:41:58.430> we<00:41:58.760> just<00:41:58.790> had<00:41:59.030> the<00:41:59.119> private<00:41:59.300> key 00:41:59.560 --> 00:41:59.570 align:start position:0% where we had we just had the private key 00:41:59.570 --> 00:42:03.670 align:start position:0% where we had we just had the private key be<00:41:59.750> just<00:42:00.560> this<00:42:00.710> simple<00:42:01.960> two<00:42:02.960> images<00:42:03.440> that<00:42:03.500> are 00:42:03.670 --> 00:42:03.680 align:start position:0% be just this simple two images that are 00:42:03.680 --> 00:42:06.490 align:start position:0% be just this simple two images that are 2<00:42:04.040> 2<00:42:04.430> this<00:42:05.150> is<00:42:05.359> just<00:42:05.599> secret<00:42:05.900> key<00:42:06.020> that<00:42:06.200> we<00:42:06.290> hash 00:42:06.490 --> 00:42:06.500 align:start position:0% 2 2 this is just secret key that we hash 00:42:06.500 --> 00:42:08.530 align:start position:0% 2 2 this is just secret key that we hash together<00:42:06.829> we<00:42:07.040> got<00:42:07.220> the<00:42:07.280> public<00:42:07.790> the<00:42:08.359> public 00:42:08.530 --> 00:42:08.540 align:start position:0% together we got the public the public 00:42:08.540 --> 00:42:11.109 align:start position:0% together we got the public the public key<00:42:08.810> we<00:42:09.349> replaced<00:42:09.619> this<00:42:09.770> now<00:42:09.950> with<00:42:10.250> with<00:42:11.000> this 00:42:11.109 --> 00:42:11.119 align:start position:0% key we replaced this now with with this 00:42:11.119 --> 00:42:13.660 align:start position:0% key we replaced this now with with this new<00:42:11.329> construction<00:42:11.829> this<00:42:12.829> is<00:42:12.950> for<00:42:13.160> this<00:42:13.369> is<00:42:13.430> for 00:42:13.660 --> 00:42:13.670 align:start position:0% new construction this is for this is for 00:42:13.670 --> 00:42:15.460 align:start position:0% new construction this is for this is for a<00:42:13.730> generic<00:42:14.060> database<00:42:14.599> yeah<00:42:15.020> a<00:42:15.050> permission 00:42:15.460 --> 00:42:15.470 align:start position:0% a generic database yeah a permission 00:42:15.470 --> 00:42:17.950 align:start position:0% a generic database yeah a permission database<00:42:15.950> so<00:42:16.369> in<00:42:16.520> the<00:42:16.640> tree<00:42:16.849> we<00:42:17.420> have<00:42:17.540> a<00:42:17.570> B<00:42:17.839> and 00:42:17.950 --> 00:42:17.960 align:start position:0% database so in the tree we have a B and 00:42:17.960 --> 00:42:21.010 align:start position:0% database so in the tree we have a B and C<00:42:18.109> and<00:42:18.290> each<00:42:19.010> a<00:42:19.160> B<00:42:19.310> and<00:42:19.460> C<00:42:19.670> has<00:42:19.970> a<00:42:20.000> public<00:42:20.810> key 00:42:21.010 --> 00:42:21.020 align:start position:0% C and each a B and C has a public key 00:42:21.020 --> 00:42:23.140 align:start position:0% C and each a B and C has a public key associated<00:42:21.619> with<00:42:21.770> it<00:42:21.920> as<00:42:22.339> well<00:42:22.550> as<00:42:22.670> an<00:42:22.760> object 00:42:23.140 --> 00:42:23.150 align:start position:0% associated with it as well as an object 00:42:23.150 --> 00:42:27.190 align:start position:0% associated with it as well as an object so<00:42:23.750> the<00:42:23.869> public<00:42:24.140> key<00:42:24.490> tells<00:42:25.490> says<00:42:26.060> it<00:42:26.780> says<00:42:26.960> who 00:42:27.190 --> 00:42:27.200 align:start position:0% so the public key tells says it says who 00:42:27.200 --> 00:42:29.290 align:start position:0% so the public key tells says it says who is<00:42:27.230> allowed<00:42:27.530> to<00:42:27.589> update<00:42:28.040> this<00:42:28.160> object<00:42:28.400> yeah 00:42:29.290 --> 00:42:29.300 align:start position:0% is allowed to update this object yeah 00:42:29.300 --> 00:42:31.810 align:start position:0% is allowed to update this object yeah and<00:42:29.480> the<00:42:29.540> object<00:42:29.960> can<00:42:30.200> be<00:42:30.520> whatever<00:42:31.520> you<00:42:31.730> want 00:42:31.810 --> 00:42:31.820 align:start position:0% and the object can be whatever you want 00:42:31.820 --> 00:42:33.910 align:start position:0% and the object can be whatever you want it<00:42:32.060> to<00:42:32.180> be<00:42:32.300> it<00:42:32.540> can<00:42:32.720> be<00:42:32.900> like<00:42:33.230> a<00:42:33.260> list<00:42:33.560> of<00:42:33.650> tweets 00:42:33.910 --> 00:42:33.920 align:start position:0% it to be it can be like a list of tweets 00:42:33.920 --> 00:42:36.460 align:start position:0% it to be it can be like a list of tweets it<00:42:34.190> can<00:42:34.339> be<00:42:34.490> your<00:42:34.760> token<00:42:35.480> balance<00:42:35.869> it<00:42:36.140> can<00:42:36.320> be<00:42:36.440> a 00:42:36.460 --> 00:42:36.470 align:start position:0% it can be your token balance it can be a 00:42:36.470 --> 00:42:38.440 align:start position:0% it can be your token balance it can be a bunch<00:42:36.740> of<00:42:36.829> other<00:42:36.920> things<00:42:37.250> as<00:42:37.400> well<00:42:37.579> so<00:42:38.119> this<00:42:38.270> is 00:42:38.440 --> 00:42:38.450 align:start position:0% bunch of other things as well so this is 00:42:38.450 --> 00:42:41.770 align:start position:0% bunch of other things as well so this is like<00:42:38.599> a<00:42:38.630> generic<00:42:40.390> scalability<00:42:41.390> solution 00:42:41.770 --> 00:42:41.780 align:start position:0% like a generic scalability solution 00:42:41.780 --> 00:42:44.290 align:start position:0% like a generic scalability solution where<00:42:41.960> you<00:42:42.050> can<00:42:42.200> update<00:42:43.160> these<00:42:43.520> leaves<00:42:44.030> in<00:42:44.210> the 00:42:44.290 --> 00:42:44.300 align:start position:0% where you can update these leaves in the 00:42:44.300 --> 00:42:50.109 align:start position:0% where you can update these leaves in the Merkle<00:42:44.540> tree<00:42:44.720> in<00:42:44.990> batches<00:42:45.650> so<00:42:47.890> myself<00:42:49.119> yeah 00:42:50.109 --> 00:42:50.119 align:start position:0% Merkle tree in batches so myself yeah 00:42:50.119 --> 00:42:52.180 align:start position:0% Merkle tree in batches so myself yeah okay<00:42:50.720> so<00:42:50.780> the<00:42:51.230> way<00:42:51.380> that<00:42:51.410> this<00:42:51.650> works<00:42:51.920> is<00:42:52.160> that 00:42:52.180 --> 00:42:52.190 align:start position:0% okay so the way that this works is that 00:42:52.190 --> 00:42:55.270 align:start position:0% okay so the way that this works is that we<00:42:52.790> have<00:42:52.819> a<00:42:52.940> single<00:42:53.180> prover<00:42:53.829> yeah<00:42:54.829> and<00:42:55.069> we<00:42:55.160> have 00:42:55.270 --> 00:42:55.280 align:start position:0% we have a single prover yeah and we have 00:42:55.280 --> 00:42:58.059 align:start position:0% we have a single prover yeah and we have a<00:42:55.310> bunch<00:42:55.520> of<00:42:55.640> users<00:42:55.880> and<00:42:56.500> what<00:42:57.500> the<00:42:57.589> users<00:42:57.920> do 00:42:58.059 --> 00:42:58.069 align:start position:0% a bunch of users and what the users do 00:42:58.069 --> 00:42:59.620 align:start position:0% a bunch of users and what the users do is<00:42:58.220> they<00:42:58.339> aggregate<00:42:58.700> signatures<00:42:59.300> together 00:42:59.620 --> 00:42:59.630 align:start position:0% is they aggregate signatures together 00:42:59.630 --> 00:43:04.329 align:start position:0% is they aggregate signatures together and<00:43:02.079> know<00:43:03.079> what<00:43:03.440> the<00:43:03.530> users<00:43:03.770> do<00:43:03.890> is<00:43:04.010> they<00:43:04.160> make 00:43:04.329 --> 00:43:04.339 align:start position:0% and know what the users do is they make 00:43:04.339 --> 00:43:05.650 align:start position:0% and know what the users do is they make signatures<00:43:04.849> and<00:43:05.030> they<00:43:05.180> pass<00:43:05.329> it<00:43:05.359> to<00:43:05.569> the 00:43:05.650 --> 00:43:05.660 align:start position:0% signatures and they pass it to the 00:43:05.660 --> 00:43:07.450 align:start position:0% signatures and they pass it to the prover<00:43:06.020> and<00:43:06.230> the<00:43:06.619> prover<00:43:06.890> aggregates<00:43:07.310> these 00:43:07.450 --> 00:43:07.460 align:start position:0% prover and the prover aggregates these 00:43:07.460 --> 00:43:10.180 align:start position:0% prover and the prover aggregates these signatures<00:43:07.819> together<00:43:08.119> and<00:43:08.470> use<00:43:09.470> and<00:43:09.829> makes<00:43:10.040> a 00:43:10.180 --> 00:43:10.190 align:start position:0% signatures together and use and makes a 00:43:10.190 --> 00:43:11.950 align:start position:0% signatures together and use and makes a ZK<00:43:10.550> start<00:43:10.819> to<00:43:10.940> prove<00:43:11.150> that<00:43:11.300> they<00:43:11.420> updated<00:43:11.780> the 00:43:11.950 --> 00:43:11.960 align:start position:0% ZK start to prove that they updated the 00:43:11.960 --> 00:43:13.990 align:start position:0% ZK start to prove that they updated the Merkle<00:43:12.230> tree<00:43:12.349> correctly<00:43:12.859> so<00:43:13.490> let's<00:43:13.520> see<00:43:13.880> how 00:43:13.990 --> 00:43:14.000 align:start position:0% Merkle tree correctly so let's see how 00:43:14.000 --> 00:43:19.770 align:start position:0% Merkle tree correctly so let's see how that<00:43:14.060> looks 00:43:19.770 --> 00:43:19.780 align:start position:0% 00:43:19.780 --> 00:43:22.329 align:start position:0% yeah<00:43:20.780> so<00:43:21.290> this<00:43:21.410> is<00:43:21.470> what<00:43:21.710> they<00:43:21.800> do<00:43:21.859> they<00:43:22.220> have 00:43:22.329 --> 00:43:22.339 align:start position:0% yeah so this is what they do they have 00:43:22.339 --> 00:43:24.130 align:start position:0% yeah so this is what they do they have the<00:43:22.430> old<00:43:22.609> Merkel<00:43:23.060> route<00:43:23.210> then<00:43:23.869> they<00:43:23.990> have<00:43:24.109> a 00:43:24.130 --> 00:43:24.140 align:start position:0% the old Merkel route then they have a 00:43:24.140 --> 00:43:25.809 align:start position:0% the old Merkel route then they have a snark<00:43:24.530> where<00:43:24.920> they<00:43:25.010> prove<00:43:25.339> that<00:43:25.550> everything 00:43:25.809 --> 00:43:25.819 align:start position:0% snark where they prove that everything 00:43:25.819 --> 00:43:28.030 align:start position:0% snark where they prove that everything was<00:43:26.030> done<00:43:26.150> correctly<00:43:26.319> that<00:43:27.319> they<00:43:27.650> did<00:43:27.890> where 00:43:28.030 --> 00:43:28.040 align:start position:0% was done correctly that they did where 00:43:28.040 --> 00:43:29.559 align:start position:0% was done correctly that they did where they<00:43:28.069> validate<00:43:28.579> a<00:43:28.609> bunch<00:43:28.819> of<00:43:28.910> signatures<00:43:29.359> and 00:43:29.559 --> 00:43:29.569 align:start position:0% they validate a bunch of signatures and 00:43:29.569 --> 00:43:31.240 align:start position:0% they validate a bunch of signatures and then<00:43:29.780> they<00:43:29.869> have<00:43:29.960> the<00:43:30.050> new<00:43:30.140> Merkel<00:43:30.440> route<00:43:30.589> yeah 00:43:31.240 --> 00:43:31.250 align:start position:0% then they have the new Merkel route yeah 00:43:31.250 --> 00:43:33.760 align:start position:0% then they have the new Merkel route yeah and<00:43:31.490> this<00:43:32.030> proof<00:43:32.480> is<00:43:32.780> proof<00:43:33.380> that<00:43:33.440> they<00:43:33.650> have 00:43:33.760 --> 00:43:33.770 align:start position:0% and this proof is proof that they have 00:43:33.770 --> 00:43:35.920 align:start position:0% and this proof is proof that they have possession<00:43:34.069> of<00:43:34.250> these<00:43:34.400> but<00:43:34.849> that's<00:43:35.119> so<00:43:35.720> so 00:43:35.920 --> 00:43:35.930 align:start position:0% possession of these but that's so so 00:43:35.930 --> 00:43:37.480 align:start position:0% possession of these but that's so so they<00:43:36.079> so<00:43:36.470> for<00:43:36.680> example<00:43:37.040> they<00:43:37.099> can't<00:43:37.339> update 00:43:37.480 --> 00:43:37.490 align:start position:0% they so for example they can't update 00:43:37.490 --> 00:43:39.190 align:start position:0% they so for example they can't update the<00:43:37.760> tree<00:43:38.000> they<00:43:38.450> can<00:43:38.599> update<00:43:38.780> and<00:43:39.050> take 00:43:39.190 --> 00:43:39.200 align:start position:0% the tree they can update and take 00:43:39.200 --> 00:43:40.329 align:start position:0% the tree they can update and take someone's<00:43:39.500> money<00:43:39.560> unless<00:43:40.099> they<00:43:40.220> have<00:43:40.310> a 00:43:40.329 --> 00:43:40.339 align:start position:0% someone's money unless they have a 00:43:40.339 --> 00:43:41.980 align:start position:0% someone's money unless they have a signature<00:43:40.670> to<00:43:40.880> send<00:43:41.060> it<00:43:41.150> somewhere<00:43:41.300> so<00:43:41.839> what 00:43:41.980 --> 00:43:41.990 align:start position:0% signature to send it somewhere so what 00:43:41.990 --> 00:43:43.510 align:start position:0% signature to send it somewhere so what the<00:43:42.079> user<00:43:42.230> does<00:43:42.440> if<00:43:42.680> they<00:43:42.800> want<00:43:43.010> to<00:43:43.099> send<00:43:43.250> if 00:43:43.510 --> 00:43:43.520 align:start position:0% the user does if they want to send if 00:43:43.520 --> 00:43:44.800 align:start position:0% the user does if they want to send if they<00:43:43.670> want<00:43:43.849> to<00:43:43.910> update<00:43:44.000> the<00:43:44.240> leaf<00:43:44.390> is<00:43:44.630> that 00:43:44.800 --> 00:43:44.810 align:start position:0% they want to update the leaf is that 00:43:44.810 --> 00:43:49.210 align:start position:0% they want to update the leaf is that they<00:43:44.930> sign<00:43:45.170> a<00:43:45.380> E<00:43:46.099> and<00:43:46.880> B<00:43:47.109> yeah<00:43:48.140> and<00:43:48.380> then<00:43:49.190> I 00:43:49.210 --> 00:43:49.220 align:start position:0% they sign a E and B yeah and then I 00:43:49.220 --> 00:43:52.089 align:start position:0% they sign a E and B yeah and then I stack<00:43:49.520> those<00:43:49.670> the<00:43:49.790> following<00:43:50.089> things<00:43:50.560> ok<00:43:51.589> this 00:43:52.089 --> 00:43:52.099 align:start position:0% stack those the following things ok this 00:43:52.099 --> 00:43:54.460 align:start position:0% stack those the following things ok this Naik<00:43:52.540> check<00:43:53.540> that<00:43:53.720> the<00:43:53.810> signature<00:43:54.170> match<00:43:54.319> is 00:43:54.460 --> 00:43:54.470 align:start position:0% Naik check that the signature match is 00:43:54.470 --> 00:43:57.130 align:start position:0% Naik check that the signature match is the<00:43:54.560> public<00:43:54.829> key<00:43:54.859> pop<00:43:55.310> key<00:43:55.460> here<00:43:55.670> and<00:43:56.630> B<00:43:56.930> oh 00:43:57.130 --> 00:43:57.140 align:start position:0% the public key pop key here and B oh 00:43:57.140 --> 00:43:58.290 align:start position:0% the public key pop key here and B oh yeah 00:43:58.290 --> 00:43:58.300 align:start position:0% yeah 00:43:58.300 --> 00:44:00.150 align:start position:0% yeah yeah<00:43:59.020> checks<00:43:59.350> that<00:43:59.440> this<00:43:59.590> signature<00:43:59.890> matches 00:44:00.150 --> 00:44:00.160 align:start position:0% yeah checks that this signature matches 00:44:00.160 --> 00:44:06.240 align:start position:0% yeah checks that this signature matches pop<00:44:00.340> key<00:44:03.150> generates<00:44:04.150> the<00:44:04.390> leaf<00:44:04.810> B<00:44:05.200> by<00:44:05.920> hashing 00:44:06.240 --> 00:44:06.250 align:start position:0% pop key generates the leaf B by hashing 00:44:06.250 --> 00:44:08.160 align:start position:0% pop key generates the leaf B by hashing with<00:44:06.430> the<00:44:06.550> object<00:44:06.970> that<00:44:07.240> that's<00:44:07.510> that's<00:44:07.900> that 00:44:08.160 --> 00:44:08.170 align:start position:0% with the object that that's that's that 00:44:08.170 --> 00:44:11.520 align:start position:0% with the object that that's that's that the<00:44:08.500> user<00:44:09.280> probably<00:44:09.670> also<00:44:09.970> provided<00:44:10.530> check 00:44:11.520 --> 00:44:11.530 align:start position:0% the user probably also provided check 00:44:11.530 --> 00:44:14.160 align:start position:0% the user probably also provided check start<00:44:11.770> that<00:44:11.860> leaf<00:44:12.010> is<00:44:12.160> in<00:44:12.190> the<00:44:12.730> tree<00:44:12.910> and<00:44:13.170> then 00:44:14.160 --> 00:44:14.170 align:start position:0% start that leaf is in the tree and then 00:44:14.170 --> 00:44:17.420 align:start position:0% start that leaf is in the tree and then replaces<00:44:14.620> that<00:44:14.710> leaf<00:44:14.890> B<00:44:15.760> with<00:44:16.210> the<00:44:16.300> new<00:44:16.450> leaf<00:44:16.660> e 00:44:17.420 --> 00:44:17.430 align:start position:0% replaces that leaf B with the new leaf e 00:44:17.430 --> 00:44:21.930 align:start position:0% replaces that leaf B with the new leaf e okay<00:44:19.200> so<00:44:20.200> you<00:44:20.710> see<00:44:20.890> what<00:44:21.010> happens<00:44:21.310> you<00:44:21.790> see 00:44:21.930 --> 00:44:21.940 align:start position:0% okay so you see what happens you see 00:44:21.940 --> 00:44:26.480 align:start position:0% okay so you see what happens you see what<00:44:22.090> happens<00:44:22.360> you<00:44:22.570> can<00:44:23.350> go<00:44:23.560> like<00:44:23.710> this<00:44:24.300> yeah 00:44:26.480 --> 00:44:26.490 align:start position:0% what happens you can go like this yeah 00:44:26.490 --> 00:44:28.740 align:start position:0% what happens you can go like this yeah okay<00:44:27.490> and<00:44:27.520> what<00:44:27.820> we<00:44:27.940> do<00:44:28.060> is<00:44:28.210> we<00:44:28.330> have<00:44:28.450> a<00:44:28.480> snack 00:44:28.740 --> 00:44:28.750 align:start position:0% okay and what we do is we have a snack 00:44:28.750 --> 00:44:32.040 align:start position:0% okay and what we do is we have a snack that<00:44:29.250> proves<00:44:30.250> that<00:44:30.430> before<00:44:31.030> we<00:44:31.180> had<00:44:31.330> we<00:44:31.900> had 00:44:32.040 --> 00:44:32.050 align:start position:0% that proves that before we had we had 00:44:32.050 --> 00:44:35.070 align:start position:0% that proves that before we had we had root<00:44:32.470> and<00:44:32.680> now<00:44:33.070> we<00:44:33.130> have<00:44:33.430> updated<00:44:33.970> root<00:44:34.240> so<00:44:34.930> the 00:44:35.070 --> 00:44:35.080 align:start position:0% root and now we have updated root so the 00:44:35.080 --> 00:44:37.560 align:start position:0% root and now we have updated root so the so<00:44:35.530> we<00:44:36.190> use<00:44:36.340> a<00:44:36.370> smart<00:44:36.700> contract<00:44:37.060> to<00:44:37.150> verify 00:44:37.560 --> 00:44:37.570 align:start position:0% so we use a smart contract to verify 00:44:37.570 --> 00:44:40.350 align:start position:0% so we use a smart contract to verify each<00:44:37.990> transition<00:44:38.680> and<00:44:39.280> now<00:44:39.520> the<00:44:39.580> operator<00:44:40.000> now 00:44:40.350 --> 00:44:40.360 align:start position:0% each transition and now the operator now 00:44:40.360 --> 00:44:44.670 align:start position:0% each transition and now the operator now we<00:44:40.660> now<00:44:41.290> we<00:44:41.350> know<00:44:43.050> we<00:44:44.050> have<00:44:44.170> a<00:44:44.200> smart<00:44:44.410> contract 00:44:44.670 --> 00:44:44.680 align:start position:0% we now we know we have a smart contract 00:44:44.680 --> 00:44:50.210 align:start position:0% we now we know we have a smart contract that<00:44:44.740> validates<00:44:45.160> each<00:44:45.280> transition<00:44:45.640> and<00:44:46.150> now 00:44:50.210 --> 00:44:50.220 align:start position:0% 00:44:50.220 --> 00:44:58.310 align:start position:0% and<00:44:51.220> now<00:44:51.400> we<00:44:51.460> have<00:44:51.730> a<00:44:51.760> system<00:44:52.150> where<00:44:52.300> the<00:44:54.060> we're 00:44:58.310 --> 00:44:58.320 align:start position:0% 00:44:58.320 --> 00:45:01.890 align:start position:0% sorry<00:44:59.320> now<00:45:00.220> yeah<00:45:00.730> so<00:45:00.940> this<00:45:01.060> is<00:45:01.180> just<00:45:01.300> a<00:45:01.420> general 00:45:01.890 --> 00:45:01.900 align:start position:0% sorry now yeah so this is just a general 00:45:01.900 --> 00:45:03.360 align:start position:0% sorry now yeah so this is just a general scalability<00:45:02.350> system<00:45:02.620> so<00:45:02.740> we<00:45:02.860> know<00:45:02.950> and<00:45:03.100> so<00:45:03.220> now 00:45:03.360 --> 00:45:03.370 align:start position:0% scalability system so we know and so now 00:45:03.370 --> 00:45:05.250 align:start position:0% scalability system so we know and so now the<00:45:03.430> operator<00:45:03.880> isn't<00:45:04.060> able<00:45:04.240> to<00:45:04.510> isn't<00:45:05.050> able<00:45:05.170> to 00:45:05.250 --> 00:45:05.260 align:start position:0% the operator isn't able to isn't able to 00:45:05.260 --> 00:45:06.480 align:start position:0% the operator isn't able to isn't able to update<00:45:05.350> the<00:45:05.530> tree<00:45:05.680> on<00:45:05.860> that's<00:45:06.040> the<00:45:06.160> users 00:45:06.480 --> 00:45:06.490 align:start position:0% update the tree on that's the users 00:45:06.490 --> 00:45:08.100 align:start position:0% update the tree on that's the users allow<00:45:06.730> them<00:45:06.910> to<00:45:07.090> unless<00:45:07.480> the<00:45:07.600> user<00:45:07.720> gives<00:45:07.990> them 00:45:08.100 --> 00:45:08.110 align:start position:0% allow them to unless the user gives them 00:45:08.110 --> 00:45:09.480 align:start position:0% allow them to unless the user gives them a<00:45:08.140> signature<00:45:08.560> and<00:45:08.680> says<00:45:08.800> ok<00:45:09.040> I'll<00:45:09.190> take<00:45:09.310> my 00:45:09.480 --> 00:45:09.490 align:start position:0% a signature and says ok I'll take my 00:45:09.490 --> 00:45:09.810 align:start position:0% a signature and says ok I'll take my Leafs 00:45:09.810 --> 00:45:09.820 align:start position:0% Leafs 00:45:09.820 --> 00:45:12.510 align:start position:0% Leafs a<00:45:09.880> -<00:45:10.000> a<00:45:10.420> -<00:45:10.450> yeah<00:45:11.440> so<00:45:11.860> that<00:45:11.980> makes<00:45:12.130> that<00:45:12.370> make 00:45:12.510 --> 00:45:12.520 align:start position:0% a - a - yeah so that makes that make 00:45:12.520 --> 00:45:14.520 align:start position:0% a - a - yeah so that makes that make sense<00:45:12.730> I<00:45:12.850> mean<00:45:12.880> but<00:45:13.420> this<00:45:13.510> is<00:45:13.570> this<00:45:13.840> really 00:45:14.520 --> 00:45:14.530 align:start position:0% sense I mean but this is this really 00:45:14.530 --> 00:45:18.780 align:start position:0% sense I mean but this is this really doesn't<00:45:14.770> work<00:45:14.860> as<00:45:15.010> it<00:45:15.130> is<00:45:15.250> right<00:45:16.150> because<00:45:17.790> this 00:45:18.780 --> 00:45:18.790 align:start position:0% doesn't work as it is right because this 00:45:18.790 --> 00:45:20.130 align:start position:0% doesn't work as it is right because this really<00:45:19.000> doesn't<00:45:19.240> work<00:45:19.390> as<00:45:19.540> it<00:45:19.660> is<00:45:19.750> because<00:45:20.110> it 00:45:20.130 --> 00:45:20.140 align:start position:0% really doesn't work as it is because it 00:45:20.140 --> 00:45:22.200 align:start position:0% really doesn't work as it is because it costs<00:45:20.980> 500<00:45:21.340> thousand<00:45:21.550> gasp<00:45:21.670> to<00:45:21.790> validate<00:45:22.090> the 00:45:22.200 --> 00:45:22.210 align:start position:0% costs 500 thousand gasp to validate the 00:45:22.210 --> 00:45:24.840 align:start position:0% costs 500 thousand gasp to validate the snark<00:45:22.450> right<00:45:23.290> and<00:45:23.470> it<00:45:23.860> costs<00:45:24.130> like<00:45:24.310> less<00:45:24.820> than 00:45:24.840 --> 00:45:24.850 align:start position:0% snark right and it costs like less than 00:45:24.850 --> 00:45:26.790 align:start position:0% snark right and it costs like less than ten<00:45:25.660> thousand<00:45:25.900> gasp<00:45:26.020> to<00:45:26.140> validate<00:45:26.410> signature 00:45:26.790 --> 00:45:26.800 align:start position:0% ten thousand gasp to validate signature 00:45:26.800 --> 00:45:29.220 align:start position:0% ten thousand gasp to validate signature inside<00:45:27.040> the<00:45:27.130> snack<00:45:27.310> inside<00:45:28.060> the<00:45:28.180> EBM<00:45:28.510> so<00:45:29.050> why 00:45:29.220 --> 00:45:29.230 align:start position:0% inside the snack inside the EBM so why 00:45:29.230 --> 00:45:31.860 align:start position:0% inside the snack inside the EBM so why would<00:45:29.590> we<00:45:29.710> use<00:45:29.740> this<00:45:30.360> does<00:45:31.360> anyone<00:45:31.600> have<00:45:31.720> any 00:45:31.860 --> 00:45:31.870 align:start position:0% would we use this does anyone have any 00:45:31.870 --> 00:45:40.410 align:start position:0% would we use this does anyone have any ideas<00:45:34.770> okay<00:45:35.770> so<00:45:35.830> so<00:45:37.470> patch<00:45:38.700> yes<00:45:39.730> patch<00:45:40.120> them<00:45:40.330> up 00:45:40.410 --> 00:45:40.420 align:start position:0% ideas okay so so patch yes patch them up 00:45:40.420 --> 00:45:42.090 align:start position:0% ideas okay so so patch yes patch them up because<00:45:40.870> the<00:45:41.050> verification<00:45:41.620> of<00:45:41.680> a<00:45:41.770> snack<00:45:41.950> is 00:45:42.090 --> 00:45:42.100 align:start position:0% because the verification of a snack is 00:45:42.100 --> 00:45:42.600 align:start position:0% because the verification of a snack is succinct 00:45:42.600 --> 00:45:42.610 align:start position:0% succinct 00:45:42.610 --> 00:45:44.460 align:start position:0% succinct we<00:45:42.820> can<00:45:42.970> include<00:45:43.240> as<00:45:43.390> many<00:45:43.630> as<00:45:43.810> we<00:45:43.930> want<00:45:44.170> inside 00:45:44.460 --> 00:45:44.470 align:start position:0% we can include as many as we want inside 00:45:44.470 --> 00:45:47.340 align:start position:0% we can include as many as we want inside the<00:45:44.620> snack<00:45:44.830> yeah<00:45:45.490> so<00:45:46.390> basically<00:45:46.930> instead<00:45:47.140> of 00:45:47.340 --> 00:45:47.350 align:start position:0% the snack yeah so basically instead of 00:45:47.350 --> 00:45:48.930 align:start position:0% the snack yeah so basically instead of instead<00:45:47.860> of<00:45:47.950> using<00:45:48.100> this<00:45:48.280> for<00:45:48.460> one<00:45:48.670> signal 00:45:48.930 --> 00:45:48.940 align:start position:0% instead of using this for one signal 00:45:48.940 --> 00:45:50.910 align:start position:0% instead of using this for one signal transaction<00:45:49.210> we<00:45:49.960> use<00:45:50.110> this<00:45:50.290> for<00:45:50.500> like<00:45:50.680> ten 00:45:50.910 --> 00:45:50.920 align:start position:0% transaction we use this for like ten 00:45:50.920 --> 00:45:52.950 align:start position:0% transaction we use this for like ten thousand<00:45:51.280> transactions<00:45:51.760> yeah<00:45:52.600> so<00:45:52.750> we<00:45:52.840> can 00:45:52.950 --> 00:45:52.960 align:start position:0% thousand transactions yeah so we can 00:45:52.960 --> 00:45:54.150 align:start position:0% thousand transactions yeah so we can aggregate<00:45:53.290> together<00:45:53.530> ten<00:45:53.860> thousand 00:45:54.150 --> 00:45:54.160 align:start position:0% aggregate together ten thousand 00:45:54.160 --> 00:45:55.710 align:start position:0% aggregate together ten thousand transactions<00:45:54.610> and<00:45:54.790> we<00:45:54.820> can<00:45:55.000> and<00:45:55.330> we<00:45:55.450> can<00:45:55.480> use 00:45:55.710 --> 00:45:55.720 align:start position:0% transactions and we can and we can use 00:45:55.720 --> 00:45:58.650 align:start position:0% transactions and we can and we can use this<00:45:55.840> to<00:45:55.960> update<00:45:56.260> the<00:45:56.620> merkel<00:45:56.890> route<00:45:57.510> so<00:45:58.510> this 00:45:58.650 --> 00:45:58.660 align:start position:0% this to update the merkel route so this 00:45:58.660 --> 00:46:00.270 align:start position:0% this to update the merkel route so this is<00:45:58.780> where<00:45:58.930> we<00:45:59.050> get<00:45:59.170> our<00:45:59.290> scalability<00:45:59.620> benefit 00:46:00.270 --> 00:46:00.280 align:start position:0% is where we get our scalability benefit 00:46:00.280 --> 00:46:02.160 align:start position:0% is where we get our scalability benefit yeah<00:46:00.790> so<00:46:01.060> now<00:46:01.240> it<00:46:01.420> takes<00:46:01.600> five<00:46:01.810> to<00:46:01.840> five 00:46:02.160 --> 00:46:02.170 align:start position:0% yeah so now it takes five to five 00:46:02.170 --> 00:46:03.420 align:start position:0% yeah so now it takes five to five hundred<00:46:02.440> thousand<00:46:02.710> got<00:46:02.800> five<00:46:03.190> hundred 00:46:03.420 --> 00:46:03.430 align:start position:0% hundred thousand got five hundred 00:46:03.430 --> 00:46:04.830 align:start position:0% hundred thousand got five hundred thousand<00:46:03.640> guys<00:46:03.730> to<00:46:03.940> validate<00:46:04.360> ten<00:46:04.540> thousand 00:46:04.830 --> 00:46:04.840 align:start position:0% thousand guys to validate ten thousand 00:46:04.840 --> 00:46:06.870 align:start position:0% thousand guys to validate ten thousand transactions<00:46:05.290> which<00:46:05.860> is<00:46:05.980> great<00:46:06.160> I<00:46:06.370> mean<00:46:06.520> it's 00:46:06.870 --> 00:46:06.880 align:start position:0% transactions which is great I mean it's 00:46:06.880 --> 00:46:09.210 align:start position:0% transactions which is great I mean it's great<00:46:06.970> we're<00:46:07.960> moving<00:46:08.230> things<00:46:08.950> are<00:46:09.070> getting 00:46:09.210 --> 00:46:09.220 align:start position:0% great we're moving things are getting 00:46:09.220 --> 00:46:12.220 align:start position:0% great we're moving things are getting cheaper<00:46:09.370> okay<00:46:10.210> so<00:46:10.270> so<00:46:10.810> now 00:46:12.220 --> 00:46:12.230 align:start position:0% cheaper okay so so now 00:46:12.230 --> 00:46:14.050 align:start position:0% cheaper okay so so now just<00:46:12.440> to<00:46:12.590> summarize<00:46:13.220> to<00:46:13.670> link<00:46:13.910> the 00:46:14.050 --> 00:46:14.060 align:start position:0% just to summarize to link the 00:46:14.060 --> 00:46:15.820 align:start position:0% just to summarize to link the cryptographic<00:46:14.330> so<00:46:14.810> to<00:46:14.869> cryptography<00:46:15.380> stuff 00:46:15.820 --> 00:46:15.830 align:start position:0% cryptographic so to cryptography stuff 00:46:15.830 --> 00:46:17.890 align:start position:0% cryptographic so to cryptography stuff to<00:46:15.920> here<00:46:16.130> so<00:46:16.640> what<00:46:16.940> we<00:46:17.060> did<00:46:17.240> before<00:46:17.330> when<00:46:17.810> we 00:46:17.890 --> 00:46:17.900 align:start position:0% to here so what we did before when we 00:46:17.900 --> 00:46:19.660 align:start position:0% to here so what we did before when we define<00:46:18.230> this<00:46:18.470> twisted<00:46:19.130> edwards<00:46:19.400> curve<00:46:19.550> that 00:46:19.660 --> 00:46:19.670 align:start position:0% define this twisted edwards curve that 00:46:19.670 --> 00:46:22.120 align:start position:0% define this twisted edwards curve that we<00:46:19.790> were<00:46:19.880> using<00:46:20.030> is<00:46:20.330> that<00:46:20.900> we<00:46:21.350> we<00:46:21.800> wanted<00:46:22.040> to 00:46:22.120 --> 00:46:22.130 align:start position:0% we were using is that we we wanted to 00:46:22.130 --> 00:46:23.590 align:start position:0% we were using is that we we wanted to make<00:46:22.250> a<00:46:22.280> signature<00:46:22.670> scheme<00:46:22.910> and<00:46:23.270> we<00:46:23.390> need<00:46:23.510> to 00:46:23.590 --> 00:46:23.600 align:start position:0% make a signature scheme and we need to 00:46:23.600 --> 00:46:24.880 align:start position:0% make a signature scheme and we need to make<00:46:23.720> a<00:46:23.750> signature<00:46:24.109> scheme<00:46:24.380> so<00:46:24.530> the<00:46:24.619> users 00:46:24.880 --> 00:46:24.890 align:start position:0% make a signature scheme so the users 00:46:24.890 --> 00:46:26.680 align:start position:0% make a signature scheme so the users could<00:46:25.070> sign<00:46:25.250> something<00:46:25.609> in<00:46:25.730> the<00:46:25.820> and<00:46:26.180> and<00:46:26.540> the 00:46:26.680 --> 00:46:26.690 align:start position:0% could sign something in the and and the 00:46:26.690 --> 00:46:29.050 align:start position:0% could sign something in the and and the operand<00:46:27.109> the<00:46:27.260> prover<00:46:27.650> wasn't<00:46:27.950> able<00:46:28.010> to<00:46:28.310> just 00:46:29.050 --> 00:46:29.060 align:start position:0% operand the prover wasn't able to just 00:46:29.060 --> 00:46:30.130 align:start position:0% operand the prover wasn't able to just sort<00:46:29.180> of<00:46:29.240> steal<00:46:29.420> people's<00:46:29.720> money<00:46:29.869> and<00:46:30.050> move 00:46:30.130 --> 00:46:30.140 align:start position:0% sort of steal people's money and move 00:46:30.140 --> 00:46:31.510 align:start position:0% sort of steal people's money and move things<00:46:30.230> around<00:46:30.410> so<00:46:30.740> we<00:46:30.950> made<00:46:31.100> this<00:46:31.220> signature 00:46:31.510 --> 00:46:31.520 align:start position:0% things around so we made this signature 00:46:31.520 --> 00:46:33.430 align:start position:0% things around so we made this signature scheme<00:46:31.760> and<00:46:31.940> now<00:46:32.030> we<00:46:32.570> just<00:46:32.720> validate<00:46:33.170> a<00:46:33.200> bunch 00:46:33.430 --> 00:46:33.440 align:start position:0% scheme and now we just validate a bunch 00:46:33.440 --> 00:46:34.780 align:start position:0% scheme and now we just validate a bunch of<00:46:33.500> signature<00:46:33.890> schemes<00:46:34.130> inside<00:46:34.460> the<00:46:34.580> snark 00:46:34.780 --> 00:46:34.790 align:start position:0% of signature schemes inside the snark 00:46:34.790 --> 00:46:38.440 align:start position:0% of signature schemes inside the snark and<00:46:35.330> we<00:46:35.890> update<00:46:36.890> our<00:46:36.920> route<00:46:37.340> yeah<00:46:38.000> old<00:46:38.270> road 00:46:38.440 --> 00:46:38.450 align:start position:0% and we update our route yeah old road 00:46:38.450 --> 00:46:41.680 align:start position:0% and we update our route yeah old road new<00:46:39.050> route<00:46:39.850> perfect<00:46:40.850> so<00:46:41.150> we<00:46:41.240> do<00:46:41.359> that<00:46:41.480> okay<00:46:41.660> so 00:46:41.680 --> 00:46:41.690 align:start position:0% new route perfect so we do that okay so 00:46:41.690 --> 00:46:43.000 align:start position:0% new route perfect so we do that okay so we<00:46:41.869> do<00:46:41.990> that<00:46:42.109> a<00:46:42.140> bunch<00:46:42.350> of<00:46:42.440> times<00:46:42.500> inside<00:46:42.920> the 00:46:43.000 --> 00:46:43.010 align:start position:0% we do that a bunch of times inside the 00:46:43.010 --> 00:46:44.980 align:start position:0% we do that a bunch of times inside the snack<00:46:43.220> we<00:46:43.400> have<00:46:43.640> like<00:46:43.760> a<00:46:43.790> for<00:46:44.030> loop<00:46:44.210> and<00:46:44.480> we<00:46:44.540> end 00:46:44.980 --> 00:46:44.990 align:start position:0% snack we have like a for loop and we end 00:46:44.990 --> 00:46:46.510 align:start position:0% snack we have like a for loop and we end up<00:46:45.080> with<00:46:45.200> just<00:46:45.230> a<00:46:45.410> single<00:46:45.560> proof<00:46:45.830> that<00:46:45.980> we<00:46:46.340> had 00:46:46.510 --> 00:46:46.520 align:start position:0% up with just a single proof that we had 00:46:46.520 --> 00:46:49.359 align:start position:0% up with just a single proof that we had transition<00:46:46.970> a<00:46:47.180> to<00:46:47.450> be<00:46:47.780> correctly<00:46:48.230> new<00:46:48.859> routes 00:46:49.359 --> 00:46:49.369 align:start position:0% transition a to be correctly new routes 00:46:49.369 --> 00:46:54.460 align:start position:0% transition a to be correctly new routes to<00:46:49.760> new<00:46:49.880> route<00:46:50.060> correctly<00:46:52.660> okay<00:46:53.660> so<00:46:53.990> what<00:46:54.440> are 00:46:54.460 --> 00:46:54.470 align:start position:0% to new route correctly okay so what are 00:46:54.470 --> 00:46:57.700 align:start position:0% to new route correctly okay so what are some<00:46:54.710> problems<00:46:54.859> with<00:46:55.040> this<00:46:55.220> okay<00:46:56.500> so<00:46:57.500> some 00:46:57.700 --> 00:46:57.710 align:start position:0% some problems with this okay so some 00:46:57.710 --> 00:46:59.500 align:start position:0% some problems with this okay so some problems<00:46:58.010> with<00:46:58.130> this<00:46:58.220> is<00:46:58.280> is<00:46:58.730> the<00:46:59.210> proving 00:46:59.500 --> 00:46:59.510 align:start position:0% problems with this is is the proving 00:46:59.510 --> 00:47:01.120 align:start position:0% problems with this is is the proving time<00:46:59.690> so<00:47:00.109> the<00:47:00.200> proving<00:47:00.410> time<00:47:00.560> is<00:47:00.650> quite<00:47:00.770> quite 00:47:01.120 --> 00:47:01.130 align:start position:0% time so the proving time is quite quite 00:47:01.130 --> 00:47:03.940 align:start position:0% time so the proving time is quite quite high<00:47:01.280> I<00:47:01.550> think<00:47:02.390> you<00:47:02.450> can<00:47:02.630> prove<00:47:02.840> on<00:47:03.050> unlike 00:47:03.940 --> 00:47:03.950 align:start position:0% high I think you can prove on unlike 00:47:03.950 --> 00:47:08.620 align:start position:0% high I think you can prove on unlike regular<00:47:04.190> hard<00:47:04.520> way<00:47:05.050> to<00:47:07.450> 220<00:47:08.450> million 00:47:08.620 --> 00:47:08.630 align:start position:0% regular hard way to 220 million 00:47:08.630 --> 00:47:11.650 align:start position:0% regular hard way to 220 million constraints<00:47:09.280> and<00:47:10.280> that's<00:47:10.910> about<00:47:11.119> enough<00:47:11.420> for 00:47:11.650 --> 00:47:11.660 align:start position:0% constraints and that's about enough for 00:47:11.660 --> 00:47:16.690 align:start position:0% constraints and that's about enough for maybe<00:47:12.050> twelve<00:47:12.890> twelve<00:47:13.550> transactions<00:47:14.230> but<00:47:15.700> but 00:47:16.690 --> 00:47:16.700 align:start position:0% maybe twelve twelve transactions but but 00:47:16.700 --> 00:47:18.190 align:start position:0% maybe twelve twelve transactions but but that's<00:47:16.970> not<00:47:17.240> our<00:47:17.359> limiting<00:47:17.690> factor<00:47:17.930> here<00:47:18.050> so 00:47:18.190 --> 00:47:18.200 align:start position:0% that's not our limiting factor here so 00:47:18.200 --> 00:47:19.450 align:start position:0% that's not our limiting factor here so because<00:47:18.500> it<00:47:18.590> turns<00:47:18.740> out<00:47:18.890> that<00:47:19.010> we<00:47:19.130> can<00:47:19.250> use<00:47:19.369> the 00:47:19.450 --> 00:47:19.460 align:start position:0% because it turns out that we can use the 00:47:19.460 --> 00:47:22.420 align:start position:0% because it turns out that we can use the AWS<00:47:19.970> Amazon<00:47:20.570> Web<00:47:20.900> Services<00:47:21.320> to<00:47:21.530> do<00:47:21.710> two<00:47:22.100> boxes 00:47:22.420 --> 00:47:22.430 align:start position:0% AWS Amazon Web Services to do two boxes 00:47:22.430 --> 00:47:24.190 align:start position:0% AWS Amazon Web Services to do two boxes or<00:47:22.640> another<00:47:22.940> cluster<00:47:23.210> yeah<00:47:23.750> just<00:47:24.080> an<00:47:24.170> e 00:47:24.190 --> 00:47:24.200 align:start position:0% or another cluster yeah just an e 00:47:24.200 --> 00:47:25.870 align:start position:0% or another cluster yeah just an e cluster<00:47:24.590> to<00:47:25.100> pass<00:47:25.250> these<00:47:25.400> transactions 00:47:25.870 --> 00:47:25.880 align:start position:0% cluster to pass these transactions 00:47:25.880 --> 00:47:27.970 align:start position:0% cluster to pass these transactions together<00:47:26.119> and<00:47:26.450> to<00:47:27.080> make<00:47:27.170> the<00:47:27.290> proofs<00:47:27.500> but<00:47:27.830> this 00:47:27.970 --> 00:47:27.980 align:start position:0% together and to make the proofs but this 00:47:27.980 --> 00:47:29.230 align:start position:0% together and to make the proofs but this cost<00:47:28.160> money<00:47:28.340> but<00:47:28.400> it<00:47:28.640> doesn't<00:47:28.880> cost<00:47:28.970> a<00:47:29.090> lot<00:47:29.180> of 00:47:29.230 --> 00:47:29.240 align:start position:0% cost money but it doesn't cost a lot of 00:47:29.240 --> 00:47:32.170 align:start position:0% cost money but it doesn't cost a lot of money<00:47:29.330> it<00:47:29.570> costs<00:47:29.810> like<00:47:30.280> $1200<00:47:31.280> for<00:47:31.490> a<00:47:31.910> proof 00:47:32.170 --> 00:47:32.180 align:start position:0% money it costs like $1200 for a proof 00:47:32.180 --> 00:47:34.180 align:start position:0% money it costs like $1200 for a proof which<00:47:32.960> is<00:47:32.990> totally<00:47:33.350> which<00:47:33.680> is<00:47:33.800> totally<00:47:34.040> fine 00:47:34.180 --> 00:47:34.190 align:start position:0% which is totally which is totally fine 00:47:34.190 --> 00:47:36.310 align:start position:0% which is totally which is totally fine if<00:47:34.340> you<00:47:34.460> if<00:47:34.730> you<00:47:34.820> doing<00:47:35.030> $1,200<00:47:35.810> for<00:47:35.960> 10,000 00:47:36.310 --> 00:47:36.320 align:start position:0% if you if you doing $1,200 for 10,000 00:47:36.320 --> 00:47:42.060 align:start position:0% if you if you doing $1,200 for 10,000 transactions<00:47:36.800> that<00:47:36.890> works<00:47:37.070> out<00:47:37.190> really<00:47:37.280> cheap 00:47:42.060 --> 00:47:42.070 align:start position:0% 00:47:42.070 --> 00:47:45.160 align:start position:0% yeah<00:47:43.070> okay<00:47:43.340> so<00:47:43.400> and<00:47:44.090> we<00:47:44.330> can<00:47:44.359> use<00:47:44.630> Paris<00:47:45.020> and 00:47:45.160 --> 00:47:45.170 align:start position:0% yeah okay so and we can use Paris and 00:47:45.170 --> 00:47:46.900 align:start position:0% yeah okay so and we can use Paris and commitments<00:47:45.560> it's<00:47:46.310> difficult<00:47:46.730> to<00:47:46.790> have<00:47:46.850> a 00:47:46.900 --> 00:47:46.910 align:start position:0% commitments it's difficult to have a 00:47:46.910 --> 00:47:48.070 align:start position:0% commitments it's difficult to have a hash<00:47:47.060> function<00:47:47.090> that's<00:47:47.540> efficient<00:47:47.869> inside 00:47:48.070 --> 00:47:48.080 align:start position:0% hash function that's efficient inside 00:47:48.080 --> 00:47:49.930 align:start position:0% hash function that's efficient inside the<00:47:48.170> snack<00:47:48.350> inside<00:47:48.680> the<00:47:48.800> VM<00:47:48.980> but<00:47:49.460> I<00:47:49.550> should 00:47:49.930 --> 00:47:49.940 align:start position:0% the snack inside the VM but I should 00:47:49.940 --> 00:47:51.220 align:start position:0% the snack inside the VM but I should talk<00:47:50.000> about<00:47:50.150> that<00:47:50.240> in<00:47:50.359> a<00:47:50.390> while 00:47:51.220 --> 00:47:51.230 align:start position:0% talk about that in a while 00:47:51.230 --> 00:47:53.380 align:start position:0% talk about that in a while okay<00:47:52.040> so<00:47:52.100> now<00:47:52.490> our<00:47:52.520> only<00:47:52.820> problem<00:47:53.000> becomes 00:47:53.380 --> 00:47:53.390 align:start position:0% okay so now our only problem becomes 00:47:53.390 --> 00:47:55.330 align:start position:0% okay so now our only problem becomes this<00:47:53.540> our<00:47:53.869> only<00:47:54.020> problem<00:47:54.410> is<00:47:54.680> now<00:47:54.800> the<00:47:55.160> data 00:47:55.330 --> 00:47:55.340 align:start position:0% this our only problem is now the data 00:47:55.340 --> 00:47:58.150 align:start position:0% this our only problem is now the data availability<00:47:55.670> problem<00:47:55.970> yeah<00:47:56.660> that<00:47:57.560> we<00:47:57.950> know 00:47:58.150 --> 00:47:58.160 align:start position:0% availability problem yeah that we know 00:47:58.160 --> 00:47:59.260 align:start position:0% availability problem yeah that we know that<00:47:58.310> the<00:47:58.430> operator<00:47:58.730> can't<00:47:58.880> steal<00:47:59.000> people's 00:47:59.260 --> 00:47:59.270 align:start position:0% that the operator can't steal people's 00:47:59.270 --> 00:48:00.670 align:start position:0% that the operator can't steal people's money<00:47:59.300> but<00:47:59.690> we<00:47:59.810> thought<00:48:00.109> the<00:48:00.200> operator<00:48:00.530> is 00:48:00.670 --> 00:48:00.680 align:start position:0% money but we thought the operator is 00:48:00.680 --> 00:48:02.859 align:start position:0% money but we thought the operator is able<00:48:00.920> to<00:48:01.100> be<00:48:01.910> able<00:48:02.090> to<00:48:02.150> block<00:48:02.330> people<00:48:02.540> from 00:48:02.859 --> 00:48:02.869 align:start position:0% able to be able to block people from 00:48:02.869 --> 00:48:04.480 align:start position:0% able to be able to block people from getting<00:48:03.020> their<00:48:03.230> money<00:48:03.440> and<00:48:03.740> does<00:48:04.250> anybody 00:48:04.480 --> 00:48:04.490 align:start position:0% getting their money and does anybody 00:48:04.490 --> 00:48:10.390 align:start position:0% getting their money and does anybody know<00:48:04.730> how<00:48:04.820> they<00:48:04.940> do<00:48:05.000> this<00:48:07.510> yeah<00:48:08.510> okay<00:48:09.400> yeah 00:48:10.390 --> 00:48:10.400 align:start position:0% know how they do this yeah okay yeah 00:48:10.400 --> 00:48:12.160 align:start position:0% know how they do this yeah okay yeah they<00:48:10.550> refuse<00:48:10.850> to<00:48:10.880> publish<00:48:11.210> it<00:48:11.420> yeah<00:48:11.930> they 00:48:12.160 --> 00:48:12.170 align:start position:0% they refuse to publish it yeah they 00:48:12.170 --> 00:48:13.720 align:start position:0% they refuse to publish it yeah they refuse<00:48:12.500> to<00:48:12.530> put<00:48:12.770> so<00:48:12.950> so<00:48:13.310> someone<00:48:13.580> does<00:48:13.700> a 00:48:13.720 --> 00:48:13.730 align:start position:0% refuse to put so so someone does a 00:48:13.730 --> 00:48:15.400 align:start position:0% refuse to put so so someone does a Merkle<00:48:14.060> tree<00:48:14.180> update<00:48:14.480> yeah 00:48:15.400 --> 00:48:15.410 align:start position:0% Merkle tree update yeah 00:48:15.410 --> 00:48:18.040 align:start position:0% Merkle tree update yeah and<00:48:15.500> then<00:48:15.740> they<00:48:15.830> refuse<00:48:16.280> to<00:48:16.310> update<00:48:17.060> publish 00:48:18.040 --> 00:48:18.050 align:start position:0% and then they refuse to update publish 00:48:18.050 --> 00:48:19.990 align:start position:0% and then they refuse to update publish to<00:48:18.200> people<00:48:18.470> the<00:48:18.619> merkel<00:48:18.980> leaves<00:48:19.609> that<00:48:19.910> they 00:48:19.990 --> 00:48:20.000 align:start position:0% to people the merkel leaves that they 00:48:20.000 --> 00:48:22.030 align:start position:0% to people the merkel leaves that they need<00:48:20.150> to<00:48:20.240> make<00:48:20.359> the<00:48:20.450> proof<00:48:20.660> yeah<00:48:21.619> and<00:48:21.830> when<00:48:21.980> you 00:48:22.030 --> 00:48:22.040 align:start position:0% need to make the proof yeah and when you 00:48:22.040 --> 00:48:24.160 align:start position:0% need to make the proof yeah and when you refuse<00:48:22.340> to<00:48:22.400> do<00:48:22.550> that<00:48:22.630> nobody<00:48:23.630> is<00:48:23.840> able<00:48:23.960> to<00:48:24.080> move 00:48:24.160 --> 00:48:24.170 align:start position:0% refuse to do that nobody is able to move 00:48:24.170 --> 00:48:24.820 align:start position:0% refuse to do that nobody is able to move their<00:48:24.290> money<00:48:24.410> anymore 00:48:24.820 --> 00:48:24.830 align:start position:0% their money anymore 00:48:24.830 --> 00:48:26.320 align:start position:0% their money anymore so<00:48:25.580> now<00:48:25.760> let's<00:48:26.030> talk 00:48:26.320 --> 00:48:26.330 align:start position:0% so now let's talk 00:48:26.330 --> 00:48:28.030 align:start position:0% so now let's talk about<00:48:26.450> sort<00:48:26.750> of<00:48:26.780> solutions<00:48:27.140> to<00:48:27.260> this<00:48:27.380> oh<00:48:27.620> I'm 00:48:28.030 --> 00:48:28.040 align:start position:0% about sort of solutions to this oh I'm 00:48:28.040 --> 00:48:29.950 align:start position:0% about sort of solutions to this oh I'm almost<00:48:28.190> done 00:48:29.950 --> 00:48:29.960 align:start position:0% almost done 00:48:29.960 --> 00:48:34.000 align:start position:0% almost done okay<00:48:30.440> so<00:48:31.810> so<00:48:32.810> one<00:48:32.990> of<00:48:33.020> it<00:48:33.200> one<00:48:33.380> of<00:48:33.470> the<00:48:33.560> ideas<00:48:33.860> is 00:48:34.000 --> 00:48:34.010 align:start position:0% okay so so one of it one of the ideas is 00:48:34.010 --> 00:48:35.410 align:start position:0% okay so so one of it one of the ideas is is<00:48:34.160> is<00:48:34.400> this<00:48:34.670> thing<00:48:34.820> called<00:48:34.940> roll<00:48:35.150> up<00:48:35.270> and<00:48:35.360> roll 00:48:35.410 --> 00:48:35.420 align:start position:0% is is this thing called roll up and roll 00:48:35.420 --> 00:48:35.890 align:start position:0% is is this thing called roll up and roll back 00:48:35.890 --> 00:48:35.900 align:start position:0% back 00:48:35.900 --> 00:48:37.570 align:start position:0% back yeah<00:48:36.110> so<00:48:36.320> with<00:48:36.470> roll<00:48:36.710> up<00:48:36.830> what<00:48:36.980> you<00:48:37.070> do<00:48:37.220> is<00:48:37.400> the 00:48:37.570 --> 00:48:37.580 align:start position:0% yeah so with roll up what you do is the 00:48:37.580 --> 00:48:40.150 align:start position:0% yeah so with roll up what you do is the the<00:48:37.850> prover<00:48:38.380> continues<00:48:39.380> to<00:48:39.590> update<00:48:40.070> the 00:48:40.150 --> 00:48:40.160 align:start position:0% the prover continues to update the 00:48:40.160 --> 00:48:42.220 align:start position:0% the prover continues to update the miracle<00:48:40.460> tree<00:48:40.550> they<00:48:41.180> do<00:48:41.540> these<00:48:41.690> transitions 00:48:42.220 --> 00:48:42.230 align:start position:0% miracle tree they do these transitions 00:48:42.230 --> 00:48:46.270 align:start position:0% miracle tree they do these transitions and<00:48:42.830> then<00:48:43.100> Annie<00:48:43.400> and<00:48:44.000> then<00:48:44.180> and<00:48:44.870> then<00:48:45.590> we<00:48:46.160> have 00:48:46.270 --> 00:48:46.280 align:start position:0% and then Annie and then and then we have 00:48:46.280 --> 00:48:48.340 align:start position:0% and then Annie and then and then we have this<00:48:46.430> we<00:48:46.910> have<00:48:46.940> what<00:48:47.180> we<00:48:47.330> what<00:48:47.570> it's<00:48:47.690> called 00:48:48.340 --> 00:48:48.350 align:start position:0% this we have what we what it's called 00:48:48.350 --> 00:48:50.140 align:start position:0% this we have what we what it's called yeah<00:48:49.040> so<00:48:49.160> it's<00:48:49.280> similar<00:48:49.430> it<00:48:49.640> is<00:48:49.700> similar<00:48:50.030> to 00:48:50.140 --> 00:48:50.150 align:start position:0% yeah so it's similar it is similar to 00:48:50.150 --> 00:48:52.690 align:start position:0% yeah so it's similar it is similar to pass<00:48:50.300> my<00:48:50.480> exists<00:48:50.810> and<00:48:50.990> we<00:48:51.530> can<00:48:51.650> we<00:48:52.040> cannot<00:48:52.490> let 00:48:52.690 --> 00:48:52.700 align:start position:0% pass my exists and we can we cannot let 00:48:52.700 --> 00:48:53.920 align:start position:0% pass my exists and we can we cannot let merge<00:48:52.880> and<00:48:53.060> split<00:48:53.210> leaves<00:48:53.390> it's<00:48:53.600> just<00:48:53.780> like 00:48:53.920 --> 00:48:53.930 align:start position:0% merge and split leaves it's just like 00:48:53.930 --> 00:48:55.570 align:start position:0% merge and split leaves it's just like it's<00:48:54.170> just<00:48:54.260> like<00:48:54.440> plasma<00:48:54.860> or<00:48:54.980> cache<00:48:55.160> I<00:48:55.370> think 00:48:55.570 --> 00:48:55.580 align:start position:0% it's just like plasma or cache I think 00:48:55.580 --> 00:48:57.280 align:start position:0% it's just like plasma or cache I think where<00:48:56.120> you<00:48:56.180> have<00:48:56.330> like<00:48:56.450> these<00:48:56.630> independent 00:48:57.280 --> 00:48:57.290 align:start position:0% where you have like these independent 00:48:57.290 --> 00:48:58.420 align:start position:0% where you have like these independent leaves<00:48:57.440> and<00:48:57.710> you<00:48:57.800> can't<00:48:58.010> join<00:48:58.160> them<00:48:58.310> together 00:48:58.420 --> 00:48:58.430 align:start position:0% leaves and you can't join them together 00:48:58.430 --> 00:49:00.610 align:start position:0% leaves and you can't join them together but<00:48:58.760> you<00:48:58.850> can<00:48:59.000> send<00:48:59.240> them<00:48:59.330> to<00:48:59.360> other<00:48:59.570> people 00:49:00.610 --> 00:49:00.620 align:start position:0% but you can send them to other people 00:49:00.620 --> 00:49:02.160 align:start position:0% but you can send them to other people [Music] 00:49:02.160 --> 00:49:02.170 align:start position:0% [Music] 00:49:02.170 --> 00:49:04.720 align:start position:0% [Music] okay<00:49:03.170> so<00:49:03.230> that's<00:49:03.500> so<00:49:03.890> one<00:49:04.100> solution<00:49:04.490> is<00:49:04.550> roll 00:49:04.720 --> 00:49:04.730 align:start position:0% okay so that's so one solution is roll 00:49:04.730 --> 00:49:06.040 align:start position:0% okay so that's so one solution is roll up<00:49:04.940> yeah<00:49:05.360> which<00:49:05.540> I'll<00:49:05.660> talk<00:49:05.750> about<00:49:05.810> in<00:49:05.960> the 00:49:06.040 --> 00:49:06.050 align:start position:0% up yeah which I'll talk about in the 00:49:06.050 --> 00:49:07.240 align:start position:0% up yeah which I'll talk about in the next<00:49:06.110> slide<00:49:06.260> and<00:49:06.440> the<00:49:06.500> other<00:49:06.620> solution<00:49:06.800> is<00:49:07.100> to 00:49:07.240 --> 00:49:07.250 align:start position:0% next slide and the other solution is to 00:49:07.250 --> 00:49:08.800 align:start position:0% next slide and the other solution is to is<00:49:07.460> to<00:49:07.610> pass<00:49:07.760> all<00:49:07.970> the<00:49:08.090> data<00:49:08.240> from<00:49:08.360> the<00:49:08.510> EBM 00:49:08.800 --> 00:49:08.810 align:start position:0% is to pass all the data from the EBM 00:49:08.810 --> 00:49:11.380 align:start position:0% is to pass all the data from the EBM into<00:49:09.080> the<00:49:09.200> stack<00:49:09.410> yeah<00:49:10.100> and<00:49:10.370> I<00:49:11.090> suppose<00:49:11.270> about 00:49:11.380 --> 00:49:11.390 align:start position:0% into the stack yeah and I suppose about 00:49:11.390 --> 00:49:16.120 align:start position:0% into the stack yeah and I suppose about this<00:49:11.600> and<00:49:11.930> I'll<00:49:12.200> talk<00:49:12.350> about<00:49:12.410> this<00:49:14.050> so<00:49:15.050> so<00:49:15.740> how 00:49:16.120 --> 00:49:16.130 align:start position:0% this and I'll talk about this so so how 00:49:16.130 --> 00:49:17.620 align:start position:0% this and I'll talk about this so so how this<00:49:16.250> roll<00:49:16.490> up<00:49:16.610> roll<00:49:16.790> back<00:49:16.970> work<00:49:17.210> and<00:49:17.450> roll<00:49:17.600> up 00:49:17.620 --> 00:49:17.630 align:start position:0% this roll up roll back work and roll up 00:49:17.630 --> 00:49:19.420 align:start position:0% this roll up roll back work and roll up roll<00:49:18.440> up<00:49:18.500> roll<00:49:18.740> back<00:49:18.920> is<00:49:19.040> actually<00:49:19.310> called 00:49:19.420 --> 00:49:19.430 align:start position:0% roll up roll back is actually called 00:49:19.430 --> 00:49:21.450 align:start position:0% roll up roll back is actually called nazma<00:49:19.850> roll<00:49:20.480> up<00:49:20.570> roll<00:49:20.720> back<00:49:20.900> is<00:49:21.050> the<00:49:21.170> old<00:49:21.320> name 00:49:21.450 --> 00:49:21.460 align:start position:0% nazma roll up roll back is the old name 00:49:21.460 --> 00:49:25.930 align:start position:0% nazma roll up roll back is the old name so<00:49:23.380> so<00:49:24.380> we<00:49:24.500> have<00:49:24.620> a<00:49:24.650> priority<00:49:25.070> queue<00:49:25.250> okay<00:49:25.880> so 00:49:25.930 --> 00:49:25.940 align:start position:0% so so we have a priority queue okay so 00:49:25.940 --> 00:49:28.290 align:start position:0% so so we have a priority queue okay so so<00:49:26.480> listen<00:49:26.780> we<00:49:27.110> have<00:49:27.230> so<00:49:27.560> the<00:49:27.680> operator 00:49:28.290 --> 00:49:28.300 align:start position:0% so listen we have so the operator 00:49:28.300 --> 00:49:30.490 align:start position:0% so listen we have so the operator aggregate<00:49:29.300> severence<00:49:29.630> transactions<00:49:30.200> and 00:49:30.490 --> 00:49:30.500 align:start position:0% aggregate severence transactions and 00:49:30.500 --> 00:49:32.110 align:start position:0% aggregate severence transactions and they<00:49:30.800> and<00:49:31.070> they<00:49:31.160> go<00:49:31.280> block<00:49:31.520> at<00:49:31.640> a<00:49:31.700> time<00:49:31.730> block 00:49:32.110 --> 00:49:32.120 align:start position:0% they and they go block at a time block 00:49:32.120 --> 00:49:33.120 align:start position:0% they and they go block at a time block at<00:49:32.210> a<00:49:32.270> time 00:49:33.120 --> 00:49:33.130 align:start position:0% at a time 00:49:33.130 --> 00:49:35.350 align:start position:0% at a time moving<00:49:34.130> forward<00:49:34.430> with<00:49:34.550> the<00:49:34.640> chain<00:49:34.820> and<00:49:35.000> then 00:49:35.350 --> 00:49:35.360 align:start position:0% moving forward with the chain and then 00:49:35.360 --> 00:49:36.940 align:start position:0% moving forward with the chain and then at<00:49:35.480> some<00:49:35.630> point<00:49:35.690> in<00:49:35.960> the<00:49:36.020> future<00:49:36.050> let's 00:49:36.940 --> 00:49:36.950 align:start position:0% at some point in the future let's 00:49:36.950 --> 00:49:38.050 align:start position:0% at some point in the future let's imagine<00:49:37.100> that<00:49:37.310> our<00:49:37.460> operator<00:49:37.790> becomes 00:49:38.050 --> 00:49:38.060 align:start position:0% imagine that our operator becomes 00:49:38.060 --> 00:49:40.180 align:start position:0% imagine that our operator becomes malicious<00:49:38.570> and<00:49:38.930> they<00:49:39.110> refuse<00:49:39.440> to<00:49:39.620> publish<00:49:39.740> the 00:49:40.180 --> 00:49:40.190 align:start position:0% malicious and they refuse to publish the 00:49:40.190 --> 00:49:43.120 align:start position:0% malicious and they refuse to publish the the<00:49:40.880> the<00:49:41.510> Merkle<00:49:41.870> path<00:49:42.050> or<00:49:42.620> the<00:49:42.680> merkel<00:49:42.980> leaves 00:49:43.120 --> 00:49:43.130 align:start position:0% the the Merkle path or the merkel leaves 00:49:43.130 --> 00:49:44.740 align:start position:0% the the Merkle path or the merkel leaves that<00:49:43.370> you<00:49:43.460> need<00:49:43.640> in<00:49:43.790> order<00:49:43.910> to<00:49:44.180> exit<00:49:44.660> your 00:49:44.740 --> 00:49:44.750 align:start position:0% that you need in order to exit your 00:49:44.750 --> 00:49:47.470 align:start position:0% that you need in order to exit your coins<00:49:45.050> so<00:49:45.920> what<00:49:46.190> do<00:49:46.280> we<00:49:46.370> do<00:49:46.520> so<00:49:47.030> we<00:49:47.180> have<00:49:47.360> this 00:49:47.470 --> 00:49:47.480 align:start position:0% coins so what do we do so we have this 00:49:47.480 --> 00:49:49.960 align:start position:0% coins so what do we do so we have this thing<00:49:47.720> called<00:49:47.840> a<00:49:47.990> priority<00:49:48.440> queue<00:49:48.650> a<00:49:48.970> priority 00:49:49.960 --> 00:49:49.970 align:start position:0% thing called a priority queue a priority 00:49:49.970 --> 00:49:52.210 align:start position:0% thing called a priority queue a priority exit<00:49:50.420> queue<00:49:50.630> and<00:49:50.870> basically<00:49:51.500> anyone<00:49:52.130> who 00:49:52.210 --> 00:49:52.220 align:start position:0% exit queue and basically anyone who 00:49:52.220 --> 00:49:54.190 align:start position:0% exit queue and basically anyone who enters<00:49:52.430> the<00:49:52.520> priority<00:49:52.880> execute<00:49:53.330> is<00:49:53.780> able<00:49:54.080> to 00:49:54.190 --> 00:49:54.200 align:start position:0% enters the priority execute is able to 00:49:54.200 --> 00:49:56.950 align:start position:0% enters the priority execute is able to is<00:49:54.790> anyone<00:49:55.790> who<00:49:55.850> enters<00:49:56.090> that<00:49:56.180> queue<00:49:56.450> the 00:49:56.950 --> 00:49:56.960 align:start position:0% is anyone who enters that queue the 00:49:56.960 --> 00:49:58.420 align:start position:0% is anyone who enters that queue the operator<00:49:57.260> must<00:49:57.500> serve<00:49:57.710> that<00:49:57.890> key<00:49:58.040> within<00:49:58.250> a 00:49:58.420 --> 00:49:58.430 align:start position:0% operator must serve that key within a 00:49:58.430 --> 00:50:00.970 align:start position:0% operator must serve that key within a timeout<00:49:58.850> that<00:49:59.090> we<00:49:59.540> define<00:49:59.810> like<00:50:00.020> a<00:50:00.350> week<00:50:00.680> two 00:50:00.970 --> 00:50:00.980 align:start position:0% timeout that we define like a week two 00:50:00.980 --> 00:50:02.470 align:start position:0% timeout that we define like a week two weeks<00:50:01.010> something<00:50:01.430> like<00:50:01.520> that<00:50:01.760> and<00:50:02.270> if<00:50:02.420> the 00:50:02.470 --> 00:50:02.480 align:start position:0% weeks something like that and if the 00:50:02.480 --> 00:50:04.060 align:start position:0% weeks something like that and if the operator<00:50:02.810> doesn't<00:50:03.230> it<00:50:03.410> doesn't<00:50:03.590> doesn't 00:50:04.060 --> 00:50:04.070 align:start position:0% operator doesn't it doesn't doesn't 00:50:04.070 --> 00:50:05.770 align:start position:0% operator doesn't it doesn't doesn't fulfill<00:50:04.310> that<00:50:04.430> request<00:50:04.730> what<00:50:05.300> we<00:50:05.390> do<00:50:05.510> is<00:50:05.660> we 00:50:05.770 --> 00:50:05.780 align:start position:0% fulfill that request what we do is we 00:50:05.780 --> 00:50:07.690 align:start position:0% fulfill that request what we do is we slash<00:50:05.990> the<00:50:06.170> operator<00:50:06.500> and<00:50:06.770> we<00:50:06.950> say<00:50:07.220> that<00:50:07.430> okay 00:50:07.690 --> 00:50:07.700 align:start position:0% slash the operator and we say that okay 00:50:07.700 --> 00:50:10.330 align:start position:0% slash the operator and we say that okay data<00:50:07.940> is<00:50:08.090> now<00:50:08.210> unavailable<00:50:08.680> yeah<00:50:09.680> and<00:50:09.950> what<00:50:10.250> we 00:50:10.330 --> 00:50:10.340 align:start position:0% data is now unavailable yeah and what we 00:50:10.340 --> 00:50:13.110 align:start position:0% data is now unavailable yeah and what we do<00:50:10.490> is<00:50:10.640> we<00:50:10.760> start<00:50:10.970> to<00:50:11.090> we<00:50:11.810> do<00:50:11.930> two<00:50:12.110> things<00:50:12.410> now 00:50:13.110 --> 00:50:13.120 align:start position:0% do is we start to we do two things now 00:50:13.120 --> 00:50:16.210 align:start position:0% do is we start to we do two things now yes<00:50:14.560> and<00:50:15.560> we<00:50:15.650> start<00:50:15.860> the<00:50:15.920> world<00:50:16.100> back 00:50:16.210 --> 00:50:16.220 align:start position:0% yes and we start the world back 00:50:16.220 --> 00:50:18.760 align:start position:0% yes and we start the world back mechanism<00:50:16.690> so<00:50:17.690> roll<00:50:18.020> back<00:50:18.140> okay<00:50:18.380> so<00:50:18.440> here's 00:50:18.760 --> 00:50:18.770 align:start position:0% mechanism so roll back okay so here's 00:50:18.770 --> 00:50:21.370 align:start position:0% mechanism so roll back okay so here's the<00:50:19.190> current<00:50:19.430> his<00:50:19.730> let<00:50:20.060> me<00:50:20.150> set<00:50:20.390> the<00:50:20.510> stage<00:50:20.570> so 00:50:21.370 --> 00:50:21.380 align:start position:0% the current his let me set the stage so 00:50:21.380 --> 00:50:23.260 align:start position:0% the current his let me set the stage so we<00:50:21.500> have<00:50:21.620> the<00:50:22.400> operator<00:50:22.700> has<00:50:22.880> been<00:50:23.030> running 00:50:23.260 --> 00:50:23.270 align:start position:0% we have the operator has been running 00:50:23.270 --> 00:50:25.330 align:start position:0% we have the operator has been running for<00:50:23.300> a<00:50:23.450> while<00:50:23.600> for<00:50:24.110> five<00:50:24.440> states<00:50:24.770> yeah<00:50:25.190> we 00:50:25.330 --> 00:50:25.340 align:start position:0% for a while for five states yeah we 00:50:25.340 --> 00:50:27.670 align:start position:0% for a while for five states yeah we started<00:50:25.520> at<00:50:25.760> s1<00:50:25.940> where<00:50:26.450> the<00:50:27.110> one<00:50:27.410> person 00:50:27.670 --> 00:50:27.680 align:start position:0% started at s1 where the one person 00:50:27.680 --> 00:50:30.130 align:start position:0% started at s1 where the one person deposited<00:50:28.160> one<00:50:28.310> coin<00:50:28.610> yeah<00:50:29.180> and<00:50:29.480> we<00:50:29.600> know<00:50:29.960> that 00:50:30.130 --> 00:50:30.140 align:start position:0% deposited one coin yeah and we know that 00:50:30.140 --> 00:50:32.140 align:start position:0% deposited one coin yeah and we know that data<00:50:30.290> is<00:50:30.440> completely<00:50:30.800> available<00:50:30.980> then<00:50:31.340> then 00:50:32.140 --> 00:50:32.150 align:start position:0% data is completely available then then 00:50:32.150 --> 00:50:34.630 align:start position:0% data is completely available then then we<00:50:32.270> move<00:50:32.480> then<00:50:32.780> we<00:50:32.810> we<00:50:33.400> started<00:50:34.400> to<00:50:34.490> move 00:50:34.630 --> 00:50:34.640 align:start position:0% we move then we we started to move 00:50:34.640 --> 00:50:36.340 align:start position:0% we move then we we started to move forward<00:50:35.030> the<00:50:35.330> operator<00:50:35.660> makes<00:50:35.840> nag<00:50:36.080> proofs 00:50:36.340 --> 00:50:36.350 align:start position:0% forward the operator makes nag proofs 00:50:36.350 --> 00:50:38.200 align:start position:0% forward the operator makes nag proofs and<00:50:36.680> validated<00:50:37.190> them<00:50:37.280> on<00:50:37.370> chain<00:50:37.610> and<00:50:37.850> we<00:50:38.000> ended 00:50:38.200 --> 00:50:38.210 align:start position:0% and validated them on chain and we ended 00:50:38.210 --> 00:50:39.420 align:start position:0% and validated them on chain and we ended up<00:50:38.240> at<00:50:38.390> say<00:50:38.510> five<00:50:38.720> yeah 00:50:39.420 --> 00:50:39.430 align:start position:0% up at say five yeah 00:50:39.430 --> 00:50:41.400 align:start position:0% up at say five yeah and<00:50:39.640> I'd<00:50:40.000> stay<00:50:40.240> five<00:50:40.480> the<00:50:40.630> operator<00:50:40.960> refuses 00:50:41.400 --> 00:50:41.410 align:start position:0% and I'd stay five the operator refuses 00:50:41.410 --> 00:50:45.480 align:start position:0% and I'd stay five the operator refuses to<00:50:41.500> share<00:50:41.680> the<00:50:41.890> data<00:50:42.059> so<00:50:43.859> I'd<00:50:44.859> stay<00:50:45.130> five<00:50:45.339> we 00:50:45.480 --> 00:50:45.490 align:start position:0% to share the data so I'd stay five we 00:50:45.490 --> 00:50:46.920 align:start position:0% to share the data so I'd stay five we enter<00:50:45.670> the<00:50:45.760> priority<00:50:46.150> queue<00:50:46.359> and<00:50:46.539> the 00:50:46.920 --> 00:50:46.930 align:start position:0% enter the priority queue and the 00:50:46.930 --> 00:50:49.200 align:start position:0% enter the priority queue and the operator<00:50:47.260> refuses<00:50:47.740> to<00:50:47.920> refuse<00:50:48.670> it<00:50:48.760> to<00:50:48.789> exit<00:50:49.089> us 00:50:49.200 --> 00:50:49.210 align:start position:0% operator refuses to refuse it to exit us 00:50:49.210 --> 00:50:51.750 align:start position:0% operator refuses to refuse it to exit us so<00:50:50.020> what<00:50:50.200> we<00:50:50.289> do<00:50:50.410> is<00:50:50.619> we<00:50:51.069> stash<00:50:51.250> the<00:50:51.369> operator 00:50:51.750 --> 00:50:51.760 align:start position:0% so what we do is we stash the operator 00:50:51.760 --> 00:50:54.029 align:start position:0% so what we do is we stash the operator and<00:50:52.059> we<00:50:52.480> have<00:50:52.900> this<00:50:53.140> kind<00:50:53.319> of<00:50:53.440> option<00:50:53.619> for<00:50:54.010> a 00:50:54.029 --> 00:50:54.039 align:start position:0% and we have this kind of option for a 00:50:54.039 --> 00:50:56.279 align:start position:0% and we have this kind of option for a new<00:50:54.099> operator<00:50:55.029> yeah<00:50:55.599> someone<00:50:55.960> else<00:50:56.079> to<00:50:56.170> take 00:50:56.279 --> 00:50:56.289 align:start position:0% new operator yeah someone else to take 00:50:56.289 --> 00:51:00.089 align:start position:0% new operator yeah someone else to take over<00:50:56.440> the<00:50:56.559> chain<00:50:56.799> um<00:50:58.410> when<00:50:59.410> you<00:50:59.559> bid<00:50:59.799> in<00:50:59.980> this 00:51:00.089 --> 00:51:00.099 align:start position:0% over the chain um when you bid in this 00:51:00.099 --> 00:51:01.829 align:start position:0% over the chain um when you bid in this option<00:51:00.520> what<00:51:00.880> you<00:51:00.970> have<00:51:01.089> to<00:51:01.210> do<00:51:01.329> is<00:51:01.480> you<00:51:01.630> say 00:51:01.829 --> 00:51:01.839 align:start position:0% option what you have to do is you say 00:51:01.839 --> 00:51:03.240 align:start position:0% option what you have to do is you say you<00:51:01.869> say<00:51:02.260> the<00:51:02.380> state<00:51:02.619> that<00:51:02.770> you<00:51:02.890> want<00:51:03.069> to<00:51:03.130> begin 00:51:03.240 --> 00:51:03.250 align:start position:0% you say the state that you want to begin 00:51:03.250 --> 00:51:05.609 align:start position:0% you say the state that you want to begin from<00:51:03.779> the<00:51:04.779> state<00:51:05.020> that<00:51:05.170> you<00:51:05.260> want<00:51:05.289> to<00:51:05.500> take 00:51:05.609 --> 00:51:05.619 align:start position:0% from the state that you want to take 00:51:05.619 --> 00:51:07.170 align:start position:0% from the state that you want to take over<00:51:05.890> from<00:51:06.010> so<00:51:06.430> you<00:51:06.490> don't<00:51:06.730> have<00:51:06.849> to<00:51:06.940> continue 00:51:07.170 --> 00:51:07.180 align:start position:0% over from so you don't have to continue 00:51:07.180 --> 00:51:09.329 align:start position:0% over from so you don't have to continue from<00:51:07.480> state<00:51:07.690> five<00:51:07.900> you<00:51:08.500> can<00:51:08.650> continue<00:51:09.190> from 00:51:09.329 --> 00:51:09.339 align:start position:0% from state five you can continue from 00:51:09.339 --> 00:51:11.789 align:start position:0% from state five you can continue from any<00:51:09.520> previous<00:51:09.849> state<00:51:10.260> so<00:51:11.260> you<00:51:11.289> say<00:51:11.500> the<00:51:11.619> state 00:51:11.789 --> 00:51:11.799 align:start position:0% any previous state so you say the state 00:51:11.799 --> 00:51:13.500 align:start position:0% any previous state so you say the state that<00:51:11.920> you<00:51:12.010> want<00:51:12.039> to<00:51:12.220> continue<00:51:12.400> from<00:51:12.670> and<00:51:13.000> you 00:51:13.500 --> 00:51:13.510 align:start position:0% that you want to continue from and you 00:51:13.510 --> 00:51:16.440 align:start position:0% that you want to continue from and you say<00:51:14.670> you<00:51:15.670> say<00:51:15.789> the<00:51:15.880> state<00:51:16.059> that<00:51:16.180> you<00:51:16.270> want<00:51:16.390> to 00:51:16.440 --> 00:51:16.450 align:start position:0% say you say the state that you want to 00:51:16.450 --> 00:51:17.579 align:start position:0% say you say the state that you want to continue<00:51:16.720> from<00:51:16.839> and<00:51:17.020> you<00:51:17.079> say<00:51:17.230> how<00:51:17.349> much<00:51:17.470> you 00:51:17.579 --> 00:51:17.589 align:start position:0% continue from and you say how much you 00:51:17.589 --> 00:51:19.470 align:start position:0% continue from and you say how much you want<00:51:17.770> to<00:51:17.829> put<00:51:18.010> as<00:51:18.130> your<00:51:18.309> deposit<00:51:18.760> yeah<00:51:19.180> we<00:51:19.359> have 00:51:19.470 --> 00:51:19.480 align:start position:0% want to put as your deposit yeah we have 00:51:19.480 --> 00:51:21.299 align:start position:0% want to put as your deposit yeah we have liked<00:51:19.630> this<00:51:19.750> idea<00:51:20.020> of<00:51:20.079> a<00:51:20.140> limited<00:51:20.440> deposit<00:51:20.920> and 00:51:21.299 --> 00:51:21.309 align:start position:0% liked this idea of a limited deposit and 00:51:21.309 --> 00:51:23.700 align:start position:0% liked this idea of a limited deposit and something<00:51:21.819> something<00:51:22.510> like<00:51:22.539> that<00:51:22.779> that's 00:51:23.700 --> 00:51:23.710 align:start position:0% something something like that that's 00:51:23.710 --> 00:51:26.910 align:start position:0% something something like that that's fine<00:51:23.770> so<00:51:24.670> so<00:51:25.450> we<00:51:25.720> finish<00:51:26.020> the<00:51:26.200> auction<00:51:26.680> and<00:51:26.799> we 00:51:26.910 --> 00:51:26.920 align:start position:0% fine so so we finish the auction and we 00:51:26.920 --> 00:51:28.829 align:start position:0% fine so so we finish the auction and we select<00:51:27.220> the<00:51:27.339> the<00:51:27.579> bidder<00:51:27.880> who<00:51:28.180> selected<00:51:28.690> the 00:51:28.829 --> 00:51:28.839 align:start position:0% select the the bidder who selected the 00:51:28.839 --> 00:51:31.470 align:start position:0% select the the bidder who selected the newest<00:51:29.109> state<00:51:29.319> with<00:51:29.770> the<00:51:29.890> highest<00:51:30.480> the 00:51:31.470 --> 00:51:31.480 align:start position:0% newest state with the highest the 00:51:31.480 --> 00:51:34.589 align:start position:0% newest state with the highest the highest<00:51:31.510> bid<00:51:31.960> yeah<00:51:32.500> and<00:51:32.770> then<00:51:33.609> what<00:51:34.299> we<00:51:34.450> do 00:51:34.589 --> 00:51:34.599 align:start position:0% highest bid yeah and then what we do 00:51:34.599 --> 00:51:37.769 align:start position:0% highest bid yeah and then what we do let's<00:51:34.930> say<00:51:35.079> that<00:51:35.260> the<00:51:35.349> new<00:51:35.470> operator<00:51:36.599> yeah<00:51:37.599> so 00:51:37.769 --> 00:51:37.779 align:start position:0% let's say that the new operator yeah so 00:51:37.779 --> 00:51:39.359 align:start position:0% let's say that the new operator yeah so the<00:51:37.869> idea<00:51:38.140> is<00:51:38.289> that<00:51:38.440> the<00:51:38.529> new<00:51:38.650> operator<00:51:39.130> will 00:51:39.359 --> 00:51:39.369 align:start position:0% the idea is that the new operator will 00:51:39.369 --> 00:51:42.809 align:start position:0% the idea is that the new operator will never<00:51:39.609> will<00:51:40.210> never<00:51:40.450> ask<00:51:41.230> to<00:51:41.740> continue<00:51:42.250> from<00:51:42.730> a 00:51:42.809 --> 00:51:42.819 align:start position:0% never will never ask to continue from a 00:51:42.819 --> 00:51:43.890 align:start position:0% never will never ask to continue from a state<00:51:43.029> where<00:51:43.210> they<00:51:43.329> have<00:51:43.359> all<00:51:43.660> the<00:51:43.779> data 00:51:43.890 --> 00:51:43.900 align:start position:0% state where they have all the data 00:51:43.900 --> 00:51:45.750 align:start position:0% state where they have all the data available<00:51:44.140> to<00:51:44.589> them<00:51:44.740> from<00:51:45.369> the<00:51:45.520> state<00:51:45.670> where 00:51:45.750 --> 00:51:45.760 align:start position:0% available to them from the state where 00:51:45.760 --> 00:51:46.769 align:start position:0% available to them from the state where they<00:51:45.880> don't<00:51:46.150> have<00:51:46.299> all<00:51:46.390> the<00:51:46.480> data<00:51:46.599> available 00:51:46.769 --> 00:51:46.779 align:start position:0% they don't have all the data available 00:51:46.779 --> 00:51:48.930 align:start position:0% they don't have all the data available because<00:51:47.500> they<00:51:47.710> will<00:51:47.890> be<00:51:48.010> trivially<00:51:48.700> slashed 00:51:48.930 --> 00:51:48.940 align:start position:0% because they will be trivially slashed 00:51:48.940 --> 00:51:51.480 align:start position:0% because they will be trivially slashed immediately<00:51:49.839> yeah<00:51:50.799> and<00:51:51.039> they'll<00:51:51.130> lose<00:51:51.309> all 00:51:51.480 --> 00:51:51.490 align:start position:0% immediately yeah and they'll lose all 00:51:51.490 --> 00:51:54.779 align:start position:0% immediately yeah and they'll lose all their<00:51:51.700> their<00:51:52.059> whole<00:51:52.240> deposit<00:51:52.690> so<00:51:53.500> then<00:51:54.369> let's 00:51:54.779 --> 00:51:54.789 align:start position:0% their their whole deposit so then let's 00:51:54.789 --> 00:51:56.190 align:start position:0% their their whole deposit so then let's say<00:51:54.910> that<00:51:55.029> their<00:51:55.180> of<00:51:55.359> the<00:51:55.539> new<00:51:55.660> operator<00:51:55.990> comes 00:51:56.190 --> 00:51:56.200 align:start position:0% say that their of the new operator comes 00:51:56.200 --> 00:51:57.630 align:start position:0% say that their of the new operator comes and<00:51:56.410> they<00:51:56.470> say<00:51:56.650> okay<00:51:56.950> I'm<00:51:57.010> gonna<00:51:57.130> take<00:51:57.309> over<00:51:57.549> at 00:51:57.630 --> 00:51:57.640 align:start position:0% and they say okay I'm gonna take over at 00:51:57.640 --> 00:52:00.089 align:start position:0% and they say okay I'm gonna take over at say<00:51:57.789> three<00:51:58.119> so<00:51:58.930> what<00:51:59.230> we<00:51:59.319> what<00:51:59.529> we<00:51:59.589> do<00:51:59.859> we<00:51:59.980> have 00:52:00.089 --> 00:52:00.099 align:start position:0% say three so what we what we do we have 00:52:00.099 --> 00:52:02.490 align:start position:0% say three so what we what we do we have this<00:52:00.190> transition<00:52:00.819> from<00:52:00.910> state<00:52:01.119> 5<00:52:01.329> to<00:52:01.539> say<00:52:01.690> 3<00:52:01.930> so 00:52:02.490 --> 00:52:02.500 align:start position:0% this transition from state 5 to say 3 so 00:52:02.500 --> 00:52:04.620 align:start position:0% this transition from state 5 to say 3 so what<00:52:02.650> we<00:52:02.770> do<00:52:02.920> is<00:52:03.099> we<00:52:03.250> say<00:52:03.460> that<00:52:03.670> ok<00:52:03.970> anyone<00:52:04.480> who 00:52:04.620 --> 00:52:04.630 align:start position:0% what we do is we say that ok anyone who 00:52:04.630 --> 00:52:06.450 align:start position:0% what we do is we say that ok anyone who has<00:52:04.750> an<00:52:04.960> implied<00:52:05.500> transaction<00:52:05.980> between<00:52:06.130> state 00:52:06.450 --> 00:52:06.460 align:start position:0% has an implied transaction between state 00:52:06.460 --> 00:52:09.120 align:start position:0% has an implied transaction between state in<00:52:06.670> state<00:52:07.059> 4<00:52:07.270> or<00:52:07.480> state<00:52:07.690> 5<00:52:07.869> is<00:52:08.500> able<00:52:08.740> to<00:52:08.799> exit 00:52:09.120 --> 00:52:09.130 align:start position:0% in state 4 or state 5 is able to exit 00:52:09.130 --> 00:52:11.460 align:start position:0% in state 4 or state 5 is able to exit yeah<00:52:09.670> and<00:52:10.150> we<00:52:10.390> have<00:52:10.539> another<00:52:10.779> period<00:52:11.079> where<00:52:11.380> we 00:52:11.460 --> 00:52:11.470 align:start position:0% yeah and we have another period where we 00:52:11.470 --> 00:52:12.809 align:start position:0% yeah and we have another period where we have<00:52:11.589> this<00:52:11.680> kind<00:52:11.829> of<00:52:11.950> plasmus<00:52:12.339> dialogues<00:52:12.670> that 00:52:12.809 --> 00:52:12.819 align:start position:0% have this kind of plasmus dialogues that 00:52:12.819 --> 00:52:14.250 align:start position:0% have this kind of plasmus dialogues that where<00:52:12.970> people<00:52:13.089> come<00:52:13.480> forward<00:52:13.720> and<00:52:13.869> say<00:52:13.960> ok<00:52:14.230> I 00:52:14.250 --> 00:52:14.260 align:start position:0% where people come forward and say ok I 00:52:14.260 --> 00:52:16.049 align:start position:0% where people come forward and say ok I want<00:52:14.500> to<00:52:14.529> go<00:52:14.650> I<00:52:14.920> want<00:52:15.130> to<00:52:15.160> leave<00:52:15.309> and<00:52:15.970> that 00:52:16.049 --> 00:52:16.059 align:start position:0% want to go I want to leave and that 00:52:16.059 --> 00:52:19.170 align:start position:0% want to go I want to leave and that works<00:52:16.180> out<00:52:16.270> fine<00:52:16.859> so<00:52:17.859> so<00:52:18.609> then<00:52:18.849> we<00:52:18.970> roll<00:52:19.150> back 00:52:19.170 --> 00:52:19.180 align:start position:0% works out fine so so then we roll back 00:52:19.180 --> 00:52:22.220 align:start position:0% works out fine so so then we roll back to<00:52:19.450> state<00:52:19.630> 3<00:52:19.839> and<00:52:19.869> the<00:52:20.109> new<00:52:20.230> opera<00:52:20.470> continues 00:52:22.220 --> 00:52:22.230 align:start position:0% to state 3 and the new opera continues 00:52:22.230 --> 00:52:26.940 align:start position:0% to state 3 and the new opera continues yeah<00:52:23.230> and<00:52:24.089> if<00:52:25.089> no<00:52:25.420> so<00:52:25.599> if<00:52:25.839> no<00:52:26.349> operator<00:52:26.710> comes 00:52:26.940 --> 00:52:26.950 align:start position:0% yeah and if no so if no operator comes 00:52:26.950 --> 00:52:28.019 align:start position:0% yeah and if no so if no operator comes forward<00:52:27.130> and<00:52:27.279> says<00:52:27.339> listen<00:52:27.640> I<00:52:27.760> want<00:52:27.970> to 00:52:28.019 --> 00:52:28.029 align:start position:0% forward and says listen I want to 00:52:28.029 --> 00:52:29.339 align:start position:0% forward and says listen I want to continue<00:52:28.210> we<00:52:28.450> just<00:52:28.630> go<00:52:28.720> all<00:52:28.869> the<00:52:28.960> way<00:52:28.990> back<00:52:29.170> to 00:52:29.339 --> 00:52:29.349 align:start position:0% continue we just go all the way back to 00:52:29.349 --> 00:52:30.930 align:start position:0% continue we just go all the way back to state<00:52:29.589> zero<00:52:29.619> and<00:52:30.039> that's<00:52:30.279> just<00:52:30.549> basically<00:52:30.849> a 00:52:30.930 --> 00:52:30.940 align:start position:0% state zero and that's just basically a 00:52:30.940 --> 00:52:34.940 align:start position:0% state zero and that's just basically a plasma<00:52:31.270> exit<00:52:31.510> it's<00:52:31.990> more<00:52:32.200> ordered<00:52:32.559> though 00:52:34.940 --> 00:52:34.950 align:start position:0% 00:52:34.950 --> 00:52:40.010 align:start position:0% yeah<00:52:37.619> yeah<00:52:38.880> ok 00:52:40.010 --> 00:52:40.020 align:start position:0% yeah yeah ok 00:52:40.020 --> 00:52:42.620 align:start position:0% yeah yeah ok that<00:52:40.350> kind<00:52:40.530> of<00:52:40.590> works<00:52:40.770> but<00:52:40.950> it's<00:52:41.130> it's<00:52:41.630> there's 00:52:42.620 --> 00:52:42.630 align:start position:0% that kind of works but it's it's there's 00:52:42.630 --> 00:52:44.180 align:start position:0% that kind of works but it's it's there's a<00:52:42.690> bunch<00:52:42.840> of<00:52:42.900> problems<00:52:42.990> with<00:52:43.290> that<00:52:43.320> and<00:52:43.920> one<00:52:44.100> of 00:52:44.180 --> 00:52:44.190 align:start position:0% a bunch of problems with that and one of 00:52:44.190 --> 00:52:46.250 align:start position:0% a bunch of problems with that and one of the<00:52:44.250> major<00:52:44.400> problems<00:52:44.760> is<00:52:44.910> that<00:52:45.030> you<00:52:45.090> can<00:52:45.420> enjoy 00:52:46.250 --> 00:52:46.260 align:start position:0% the major problems is that you can enjoy 00:52:46.260 --> 00:52:47.630 align:start position:0% the major problems is that you can enjoy and<00:52:46.410> leave<00:52:46.470> together<00:52:46.800> for<00:52:47.190> a<00:52:47.220> reason<00:52:47.490> that<00:52:47.520> I 00:52:47.630 --> 00:52:47.640 align:start position:0% and leave together for a reason that I 00:52:47.640 --> 00:52:48.800 align:start position:0% and leave together for a reason that I can<00:52:47.820> discuss<00:52:48.060> afterwards<00:52:48.480> that<00:52:48.570> people<00:52:48.720> have 00:52:48.800 --> 00:52:48.810 align:start position:0% can discuss afterwards that people have 00:52:48.810 --> 00:52:50.750 align:start position:0% can discuss afterwards that people have questions<00:52:49.110> about<00:52:49.170> it<00:52:49.410> and<00:52:50.100> another<00:52:50.520> problem 00:52:50.750 --> 00:52:50.760 align:start position:0% questions about it and another problem 00:52:50.760 --> 00:52:54.110 align:start position:0% questions about it and another problem with<00:52:50.940> that<00:52:51.060> is<00:52:51.270> another<00:52:52.850> problem<00:52:53.850> with<00:52:54.060> that 00:52:54.110 --> 00:52:54.120 align:start position:0% with that is another problem with that 00:52:54.120 --> 00:52:55.790 align:start position:0% with that is another problem with that is<00:52:54.270> like<00:52:54.450> this<00:52:54.570> idea<00:52:54.870> of<00:52:54.960> finality<00:52:55.380> that<00:52:55.530> you 00:52:55.790 --> 00:52:55.800 align:start position:0% is like this idea of finality that you 00:52:55.800 --> 00:52:57.530 align:start position:0% is like this idea of finality that you you<00:52:56.310> don't<00:52:56.520> know<00:52:56.640> that<00:52:56.790> you<00:52:57.150> you're<00:52:57.420> not 00:52:57.530 --> 00:52:57.540 align:start position:0% you don't know that you you're not 00:52:57.540 --> 00:52:59.030 align:start position:0% you don't know that you you're not guaranteed<00:52:57.750> that<00:52:58.050> your<00:52:58.410> state<00:52:58.650> is<00:52:58.770> not<00:52:58.920> gonna 00:52:59.030 --> 00:52:59.040 align:start position:0% guaranteed that your state is not gonna 00:52:59.040 --> 00:53:00.860 align:start position:0% guaranteed that your state is not gonna chain<00:52:59.250> rule<00:52:59.490> back<00:52:59.670> but<00:53:00.420> we<00:53:00.510> can<00:53:00.660> have<00:53:00.750> this 00:53:00.860 --> 00:53:00.870 align:start position:0% chain rule back but we can have this 00:53:00.870 --> 00:53:02.960 align:start position:0% chain rule back but we can have this kind<00:53:01.110> of<00:53:01.170> weaker<00:53:01.500> for<00:53:01.740> now<00:53:01.830> the<00:53:01.970> assumptions 00:53:02.960 --> 00:53:02.970 align:start position:0% kind of weaker for now the assumptions 00:53:02.970 --> 00:53:04.160 align:start position:0% kind of weaker for now the assumptions and<00:53:03.120> you<00:53:03.180> can<00:53:03.330> say<00:53:03.450> that<00:53:03.600> listen<00:53:03.870> if<00:53:03.960> I<00:53:04.050> have 00:53:04.160 --> 00:53:04.170 align:start position:0% and you can say that listen if I have 00:53:04.170 --> 00:53:06.230 align:start position:0% and you can say that listen if I have all<00:53:04.320> the<00:53:04.440> data<00:53:04.650> for<00:53:04.890> a<00:53:04.950> single<00:53:05.160> for<00:53:05.940> a<00:53:05.970> single 00:53:06.230 --> 00:53:06.240 align:start position:0% all the data for a single for a single 00:53:06.240 --> 00:53:08.690 align:start position:0% all the data for a single for a single state<00:53:06.450> I<00:53:06.660> know<00:53:07.080> that<00:53:07.410> if<00:53:08.010> there's<00:53:08.250> a<00:53:08.340> I<00:53:08.520> know 00:53:08.690 --> 00:53:08.700 align:start position:0% state I know that if there's a I know 00:53:08.700 --> 00:53:10.040 align:start position:0% state I know that if there's a I know that<00:53:08.820> someone<00:53:09.240> will<00:53:09.390> come<00:53:09.420> forward<00:53:09.870> to<00:53:09.960> take 00:53:10.040 --> 00:53:10.050 align:start position:0% that someone will come forward to take 00:53:10.050 --> 00:53:11.810 align:start position:0% that someone will come forward to take over<00:53:10.290> from<00:53:10.380> another<00:53:10.530> state<00:53:11.010> or<00:53:11.160> I<00:53:11.310> can<00:53:11.670> come 00:53:11.810 --> 00:53:11.820 align:start position:0% over from another state or I can come 00:53:11.820 --> 00:53:13.640 align:start position:0% over from another state or I can come forward<00:53:12.030> and<00:53:12.120> take<00:53:12.270> over<00:53:12.420> from<00:53:12.540> that<00:53:12.720> state<00:53:12.960> so 00:53:13.640 --> 00:53:13.650 align:start position:0% forward and take over from that state so 00:53:13.650 --> 00:53:15.620 align:start position:0% forward and take over from that state so people<00:53:13.680> will<00:53:14.160> know<00:53:14.310> that<00:53:14.340> okay<00:53:15.060> we<00:53:15.180> only<00:53:15.450> roll 00:53:15.620 --> 00:53:15.630 align:start position:0% people will know that okay we only roll 00:53:15.630 --> 00:53:18.440 align:start position:0% people will know that okay we only roll back<00:53:15.780> a<00:53:15.810> little<00:53:16.020> bit<00:53:16.520> okay<00:53:17.520> so<00:53:17.910> that's<00:53:18.210> that's 00:53:18.440 --> 00:53:18.450 align:start position:0% back a little bit okay so that's that's 00:53:18.450 --> 00:53:20.330 align:start position:0% back a little bit okay so that's that's kind<00:53:18.780> of<00:53:18.870> that's<00:53:19.260> kind<00:53:19.500> of<00:53:19.560> how<00:53:19.680> roll<00:53:19.860> up<00:53:20.040> roll 00:53:20.330 --> 00:53:20.340 align:start position:0% kind of that's kind of how roll up roll 00:53:20.340 --> 00:53:22.040 align:start position:0% kind of that's kind of how roll up roll backs<00:53:20.580> nazma<00:53:21.060> that's<00:53:21.450> how<00:53:21.540> stance<00:53:21.750> my<00:53:21.870> works 00:53:22.040 --> 00:53:22.050 align:start position:0% backs nazma that's how stance my works 00:53:22.050 --> 00:53:25.430 align:start position:0% backs nazma that's how stance my works okay<00:53:23.150> okay<00:53:24.150> so<00:53:24.210> now<00:53:24.480> the<00:53:24.540> other<00:53:24.870> option<00:53:25.140> is<00:53:25.380> to 00:53:25.430 --> 00:53:25.440 align:start position:0% okay okay so now the other option is to 00:53:25.440 --> 00:53:27.350 align:start position:0% okay okay so now the other option is to do<00:53:25.590> that<00:53:25.740> availability<00:53:26.190> inside<00:53:27.060> the<00:53:27.180> chain 00:53:27.350 --> 00:53:27.360 align:start position:0% do that availability inside the chain 00:53:27.360 --> 00:53:29.060 align:start position:0% do that availability inside the chain and<00:53:27.840> what<00:53:27.930> we<00:53:28.020> do<00:53:28.140> is<00:53:28.290> we<00:53:28.380> just<00:53:28.410> pass<00:53:28.710> all<00:53:28.950> the 00:53:29.060 --> 00:53:29.070 align:start position:0% and what we do is we just pass all the 00:53:29.070 --> 00:53:31.340 align:start position:0% and what we do is we just pass all the variables<00:53:29.520> from<00:53:29.700> the<00:53:29.790> EVM<00:53:30.270> to<00:53:30.420> the<00:53:30.510> snark<00:53:30.750> and 00:53:31.340 --> 00:53:31.350 align:start position:0% variables from the EVM to the snark and 00:53:31.350 --> 00:53:34.340 align:start position:0% variables from the EVM to the snark and we<00:53:31.470> verify<00:53:31.950> we<00:53:32.520> bear<00:53:32.730> and<00:53:33.270> this<00:53:33.690> way<00:53:33.870> no<00:53:34.080> one<00:53:34.110> is 00:53:34.340 --> 00:53:34.350 align:start position:0% we verify we bear and this way no one is 00:53:34.350 --> 00:53:41.120 align:start position:0% we verify we bear and this way no one is able<00:53:34.470> to<00:53:34.760> no<00:53:35.760> one<00:53:35.850> is<00:53:35.970> able<00:53:36.060> to<00:53:39.710> yeah<00:53:40.710> this<00:53:40.980> way 00:53:41.120 --> 00:53:41.130 align:start position:0% able to no one is able to yeah this way 00:53:41.130 --> 00:53:43.760 align:start position:0% able to no one is able to yeah this way the<00:53:41.510> data<00:53:42.510> is<00:53:42.600> definitely<00:53:43.020> available<00:53:43.170> we<00:53:43.500> rely 00:53:43.760 --> 00:53:43.770 align:start position:0% the data is definitely available we rely 00:53:43.770 --> 00:53:46.120 align:start position:0% the data is definitely available we rely on<00:53:43.800> the<00:53:44.070> theory<00:53:44.220> availability<00:53:45.060> guarantees 00:53:46.120 --> 00:53:46.130 align:start position:0% on the theory availability guarantees 00:53:46.130 --> 00:53:48.890 align:start position:0% on the theory availability guarantees yeah<00:53:47.160> about<00:53:47.400> this<00:53:47.550> this<00:53:47.910> is<00:53:48.150> kind<00:53:48.360> of<00:53:48.420> this<00:53:48.780> is 00:53:48.890 --> 00:53:48.900 align:start position:0% yeah about this this is kind of this is 00:53:48.900 --> 00:53:50.780 align:start position:0% yeah about this this is kind of this is not<00:53:49.020> great<00:53:49.200> for<00:53:49.380> two<00:53:49.500> reasons<00:53:49.830> for<00:53:50.460> some 00:53:50.780 --> 00:53:50.790 align:start position:0% not great for two reasons for some 00:53:50.790 --> 00:53:53.960 align:start position:0% not great for two reasons for some reasons<00:53:51.090> it's<00:53:52.070> it<00:53:53.070> costs<00:53:53.310> a<00:53:53.340> lot<00:53:53.430> of<00:53:53.610> gas<00:53:53.730> per 00:53:53.960 --> 00:53:53.970 align:start position:0% reasons it's it costs a lot of gas per 00:53:53.970 --> 00:53:55.640 align:start position:0% reasons it's it costs a lot of gas per transaction<00:53:54.270> which<00:53:54.840> sort<00:53:55.230> of<00:53:55.320> limits<00:53:55.560> our 00:53:55.640 --> 00:53:55.650 align:start position:0% transaction which sort of limits our 00:53:55.650 --> 00:53:57.290 align:start position:0% transaction which sort of limits our scaling<00:53:56.040> not<00:53:56.280> at<00:53:56.460> the<00:53:56.550> amount<00:53:56.730> of<00:53:56.850> proofs<00:53:57.210> that 00:53:57.290 --> 00:53:57.300 align:start position:0% scaling not at the amount of proofs that 00:53:57.300 --> 00:53:58.850 align:start position:0% scaling not at the amount of proofs that we<00:53:57.480> can<00:53:57.630> make<00:53:57.780> or<00:53:58.110> the<00:53:58.170> size<00:53:58.500> of<00:53:58.620> proofs<00:53:58.800> that 00:53:58.850 --> 00:53:58.860 align:start position:0% we can make or the size of proofs that 00:53:58.860 --> 00:54:02.330 align:start position:0% we can make or the size of proofs that we<00:53:59.040> can<00:53:59.190> make<00:53:59.310> but<00:53:59.550> at<00:53:59.760> the<00:54:01.160> cost<00:54:02.160> per 00:54:02.330 --> 00:54:02.340 align:start position:0% we can make but at the cost per 00:54:02.340 --> 00:54:04.220 align:start position:0% we can make but at the cost per transaction<00:54:02.640> so<00:54:03.030> we<00:54:03.120> limited<00:54:03.570> by<00:54:03.660> gas<00:54:03.870> inside 00:54:04.220 --> 00:54:04.230 align:start position:0% transaction so we limited by gas inside 00:54:04.230 --> 00:54:05.750 align:start position:0% transaction so we limited by gas inside the<00:54:04.320> VM<00:54:04.530> because<00:54:04.950> we<00:54:05.040> have<00:54:05.130> to<00:54:05.190> pay<00:54:05.310> gas<00:54:05.490> every 00:54:05.750 --> 00:54:05.760 align:start position:0% the VM because we have to pay gas every 00:54:05.760 --> 00:54:10.490 align:start position:0% the VM because we have to pay gas every transaction<00:54:06.060> that<00:54:06.360> we<00:54:06.420> include<00:54:06.780> yeah<00:54:09.230> yeah<00:54:10.230> so 00:54:10.490 --> 00:54:10.500 align:start position:0% transaction that we include yeah yeah so 00:54:10.500 --> 00:54:12.080 align:start position:0% transaction that we include yeah yeah so I<00:54:10.710> talked<00:54:10.920> about<00:54:10.950> compressing<00:54:11.400> here<00:54:11.700> but<00:54:11.880> I 00:54:12.080 --> 00:54:12.090 align:start position:0% I talked about compressing here but I 00:54:12.090 --> 00:54:13.310 align:start position:0% I talked about compressing here but I all<00:54:12.300> sort<00:54:12.540> of<00:54:12.600> leave<00:54:12.690> out<00:54:12.840> the<00:54:12.930> new<00:54:13.050> ones<00:54:13.200> of 00:54:13.310 --> 00:54:13.320 align:start position:0% all sort of leave out the new ones of 00:54:13.320 --> 00:54:15.140 align:start position:0% all sort of leave out the new ones of that<00:54:13.350> but<00:54:13.980> yeah<00:54:14.550> we<00:54:14.670> have<00:54:14.760> to<00:54:14.820> compress<00:54:15.060> the 00:54:15.140 --> 00:54:15.150 align:start position:0% that but yeah we have to compress the 00:54:15.150 --> 00:54:17.270 align:start position:0% that but yeah we have to compress the data<00:54:15.300> to<00:54:15.510> inside<00:54:16.170> a<00:54:16.200> bimbo<00:54:16.470> compressing<00:54:17.190> is 00:54:17.270 --> 00:54:17.280 align:start position:0% data to inside a bimbo compressing is 00:54:17.280 --> 00:54:20.570 align:start position:0% data to inside a bimbo compressing is just<00:54:17.460> hash<00:54:17.820> together<00:54:18.650> so<00:54:19.650> that<00:54:19.800> works<00:54:19.980> that 00:54:20.570 --> 00:54:20.580 align:start position:0% just hash together so that works that 00:54:20.580 --> 00:54:21.980 align:start position:0% just hash together so that works that works<00:54:20.880> too<00:54:21.060> and<00:54:21.090> this<00:54:21.480> is<00:54:21.660> kind<00:54:21.870> of<00:54:21.900> the 00:54:21.980 --> 00:54:21.990 align:start position:0% works too and this is kind of the 00:54:21.990 --> 00:54:23.210 align:start position:0% works too and this is kind of the approach<00:54:22.170> that<00:54:22.260> we've<00:54:22.530> sort<00:54:22.920> of<00:54:22.980> moving 00:54:23.210 --> 00:54:23.220 align:start position:0% approach that we've sort of moving 00:54:23.220 --> 00:54:26.180 align:start position:0% approach that we've sort of moving forward<00:54:23.340> with<00:54:23.520> at<00:54:23.730> the<00:54:23.790> moment<00:54:25.070> so<00:54:26.070> these 00:54:26.180 --> 00:54:26.190 align:start position:0% forward with at the moment so these 00:54:26.190 --> 00:54:27.680 align:start position:0% forward with at the moment so these comparisons<00:54:26.670> with<00:54:26.820> plasma<00:54:27.180> which<00:54:27.360> I<00:54:27.450> already 00:54:27.680 --> 00:54:27.690 align:start position:0% comparisons with plasma which I already 00:54:27.690 --> 00:54:29.840 align:start position:0% comparisons with plasma which I already did<00:54:28.080> okay<00:54:28.710> and<00:54:28.890> then<00:54:28.980> I<00:54:29.070> have<00:54:29.160> two<00:54:29.310> examples<00:54:29.460> so 00:54:29.840 --> 00:54:29.850 align:start position:0% did okay and then I have two examples so 00:54:29.850 --> 00:54:31.850 align:start position:0% did okay and then I have two examples so this<00:54:30.000> is<00:54:30.150> like<00:54:30.330> alright<00:54:30.960> let's<00:54:31.260> finish<00:54:31.560> the<00:54:31.830> I 00:54:31.850 --> 00:54:31.860 align:start position:0% this is like alright let's finish the I 00:54:31.860 --> 00:54:33.650 align:start position:0% this is like alright let's finish the I won't<00:54:32.130> do<00:54:32.220> the<00:54:32.310> examples<00:54:32.700> because<00:54:32.850> because<00:54:33.330> we 00:54:33.650 --> 00:54:33.660 align:start position:0% won't do the examples because because we 00:54:33.660 --> 00:54:35.570 align:start position:0% won't do the examples because because we only<00:54:34.110> have<00:54:34.260> like<00:54:34.410> five<00:54:34.590> minutes<00:54:34.710> a<00:54:35.250> minute 00:54:35.570 --> 00:54:35.580 align:start position:0% only have like five minutes a minute 00:54:35.580 --> 00:54:41.060 align:start position:0% only have like five minutes a minute left<00:54:36.590> yeah<00:54:39.020> okay<00:54:40.020> so<00:54:40.080> let's<00:54:40.530> just<00:54:40.620> talk<00:54:40.800> about 00:54:41.060 --> 00:54:41.070 align:start position:0% left yeah okay so let's just talk about 00:54:41.070 --> 00:54:43.220 align:start position:0% left yeah okay so let's just talk about yeah<00:54:41.850> these<00:54:42.000> two<00:54:42.120> exams<00:54:42.390> quickly<00:54:42.720> so<00:54:42.930> one<00:54:43.110> is 00:54:43.220 --> 00:54:43.230 align:start position:0% yeah these two exams quickly so one is 00:54:43.230 --> 00:54:45.140 align:start position:0% yeah these two exams quickly so one is you<00:54:43.350> can<00:54:43.470> if<00:54:43.590> T<00:54:43.770> and<00:54:44.040> this<00:54:44.160> this<00:54:44.670> was<00:54:44.850> done<00:54:45.000> at<00:54:45.120> a 00:54:45.140 --> 00:54:45.150 align:start position:0% you can if T and this this was done at a 00:54:45.150 --> 00:54:47.620 align:start position:0% you can if T and this this was done at a hackathon<00:54:45.540> in<00:54:45.960> Berlin<00:54:46.350> by<00:54:46.590> a<00:54:46.620> bunch<00:54:46.890> of<00:54:46.980> people 00:54:47.620 --> 00:54:47.630 align:start position:0% hackathon in Berlin by a bunch of people 00:54:47.630 --> 00:54:49.610 align:start position:0% hackathon in Berlin by a bunch of people and<00:54:48.630> I<00:54:48.810> would<00:54:48.930> say<00:54:49.020> their<00:54:49.170> names<00:54:49.290> what<00:54:49.440> I'm<00:54:49.530> not 00:54:49.610 --> 00:54:49.620 align:start position:0% and I would say their names what I'm not 00:54:49.620 --> 00:54:50.840 align:start position:0% and I would say their names what I'm not sure<00:54:49.740> they<00:54:49.860> want<00:54:50.070> me<00:54:50.130> to<00:54:50.160> say<00:54:50.340> their<00:54:50.490> name<00:54:50.640> so<00:54:50.820> I 00:54:50.840 --> 00:54:50.850 align:start position:0% sure they want me to say their name so I 00:54:50.850 --> 00:54:52.849 align:start position:0% sure they want me to say their name so I won't<00:54:51.710> yeah 00:54:52.849 --> 00:54:52.859 align:start position:0% won't yeah 00:54:52.859 --> 00:54:57.289 align:start position:0% won't yeah okay<00:54:53.609> so<00:54:55.219> yeah<00:54:56.219> so<00:54:56.400> basically<00:54:56.579> they<00:54:56.999> did<00:54:57.119> and 00:54:57.289 --> 00:54:57.299 align:start position:0% okay so yeah so basically they did and 00:54:57.299 --> 00:55:00.160 align:start position:0% okay so yeah so basically they did and not<00:54:57.359> non-functional<00:54:58.170> token<00:54:58.680> with<00:54:59.279> roll-up 00:55:00.160 --> 00:55:00.170 align:start position:0% not non-functional token with roll-up 00:55:00.170 --> 00:55:04.910 align:start position:0% not non-functional token with roll-up ana<00:55:01.170> works<00:55:01.349> pretty<00:55:01.440> well<00:55:01.559> and<00:55:01.910> we<00:55:02.910> also<00:55:03.059> are<00:55:03.920> me 00:55:04.910 --> 00:55:04.920 align:start position:0% ana works pretty well and we also are me 00:55:04.920 --> 00:55:08.509 align:start position:0% ana works pretty well and we also are me and<00:55:04.950> a<00:55:05.190> few<00:55:05.339> people<00:55:05.569> are<00:55:06.569> working<00:55:07.109> on<00:55:07.519> making 00:55:08.509 --> 00:55:08.519 align:start position:0% and a few people are working on making 00:55:08.519 --> 00:55:10.670 align:start position:0% and a few people are working on making some<00:55:08.910> sort<00:55:09.089> of<00:55:09.180> generic<00:55:09.690> token<00:55:10.109> with<00:55:10.229> this<00:55:10.380> we 00:55:10.670 --> 00:55:10.680 align:start position:0% some sort of generic token with this we 00:55:10.680 --> 00:55:12.620 align:start position:0% some sort of generic token with this we can<00:55:11.009> just<00:55:11.400> patch<00:55:11.880> talking<00:55:12.329> transpose 00:55:12.620 --> 00:55:12.630 align:start position:0% can just patch talking transpose 00:55:12.630 --> 00:55:16.309 align:start position:0% can just patch talking transpose together<00:55:13.640> yeah<00:55:14.640> and<00:55:15.209> if<00:55:15.599> we<00:55:15.869> were<00:55:15.989> gonna<00:55:16.109> use 00:55:16.309 --> 00:55:16.319 align:start position:0% together yeah and if we were gonna use 00:55:16.319 --> 00:55:18.140 align:start position:0% together yeah and if we were gonna use that<00:55:16.469> available<00:55:16.859> in<00:55:16.950> chain<00:55:17.309> as<00:55:17.489> I<00:55:17.759> said<00:55:17.940> before 00:55:18.140 --> 00:55:18.150 align:start position:0% that available in chain as I said before 00:55:18.150 --> 00:55:20.809 align:start position:0% that available in chain as I said before and<00:55:18.719> each<00:55:18.930> each<00:55:19.589> leaf<00:55:20.009> has<00:55:20.219> a<00:55:20.249> variable<00:55:20.519> amount 00:55:20.809 --> 00:55:20.819 align:start position:0% and each each leaf has a variable amount 00:55:20.819 --> 00:55:23.839 align:start position:0% and each each leaf has a variable amount you<00:55:21.539> can<00:55:21.809> trade<00:55:21.959> tokens<00:55:22.259> for<00:55:22.459> to<00:55:23.459> each<00:55:23.579> other 00:55:23.839 --> 00:55:23.849 align:start position:0% you can trade tokens for to each other 00:55:23.849 --> 00:55:27.440 align:start position:0% you can trade tokens for to each other but<00:55:24.359> not<00:55:24.420> spit<00:55:24.660> oh<00:55:24.809> oh<00:55:25.640> no<00:55:26.640> users<00:55:27.029> can<00:55:27.239> split 00:55:27.440 --> 00:55:27.450 align:start position:0% but not spit oh oh no users can split 00:55:27.450 --> 00:55:32.979 align:start position:0% but not spit oh oh no users can split two<00:55:27.539> tokens<00:55:28.219> that's<00:55:29.219> not<00:55:29.369> right<00:55:29.489> that<00:55:29.700> side 00:55:32.979 --> 00:55:32.989 align:start position:0% 00:55:32.989 --> 00:55:35.479 align:start position:0% and<00:55:33.989> users<00:55:34.499> connected<00:55:34.890> leap<00:55:35.069> what<00:55:35.249> the<00:55:35.339> leaf 00:55:35.479 --> 00:55:35.489 align:start position:0% and users connected leap what the leaf 00:55:35.489 --> 00:55:37.400 align:start position:0% and users connected leap what the leaf is<00:55:35.700> no<00:55:36.269> wait<00:55:36.539> that's<00:55:36.719> not<00:55:36.809> this<00:55:37.140> light<00:55:37.319> is 00:55:37.400 --> 00:55:37.410 align:start position:0% is no wait that's not this light is 00:55:37.410 --> 00:55:42.289 align:start position:0% is no wait that's not this light is wrong<00:55:40.430> okay<00:55:41.430> so<00:55:41.489> let's<00:55:41.849> talk<00:55:41.969> about<00:55:42.029> roller 00:55:42.289 --> 00:55:42.299 align:start position:0% wrong okay so let's talk about roller 00:55:42.299 --> 00:55:43.579 align:start position:0% wrong okay so let's talk about roller problems<00:55:42.630> really<00:55:42.719> quickly<00:55:43.049> and<00:55:43.170> then<00:55:43.289> then 00:55:43.579 --> 00:55:43.589 align:start position:0% problems really quickly and then then 00:55:43.589 --> 00:55:46.430 align:start position:0% problems really quickly and then then we'll<00:55:43.680> have<00:55:43.829> some<00:55:43.920> questions<00:55:44.009> okay<00:55:44.759> so<00:55:44.969> so<00:55:45.749> one 00:55:46.430 --> 00:55:46.440 align:start position:0% we'll have some questions okay so so one 00:55:46.440 --> 00:55:47.690 align:start position:0% we'll have some questions okay so so one that<00:55:46.559> one<00:55:46.799> problem<00:55:47.099> is<00:55:47.190> that<00:55:47.309> the<00:55:47.369> proving 00:55:47.690 --> 00:55:47.700 align:start position:0% that one problem is that the proving 00:55:47.700 --> 00:55:49.249 align:start position:0% that one problem is that the proving time<00:55:47.789> is<00:55:47.940> quite<00:55:48.119> big<00:55:48.299> and<00:55:48.509> we<00:55:48.779> need<00:55:49.140> to 00:55:49.249 --> 00:55:49.259 align:start position:0% time is quite big and we need to 00:55:49.259 --> 00:55:51.319 align:start position:0% time is quite big and we need to outsource<00:55:50.039> this<00:55:50.309> is<00:55:50.609> quite<00:55:50.880> long<00:55:50.999> it<00:55:51.180> takes 00:55:51.319 --> 00:55:51.329 align:start position:0% outsource this is quite long it takes 00:55:51.329 --> 00:55:54.019 align:start position:0% outsource this is quite long it takes okay<00:55:51.660> so<00:55:51.719> it<00:55:51.869> takes<00:55:52.019> about<00:55:52.109> it<00:55:52.769> takes<00:55:53.369> one<00:55:53.849> hour 00:55:54.019 --> 00:55:54.029 align:start position:0% okay so it takes about it takes one hour 00:55:54.029 --> 00:55:57.439 align:start position:0% okay so it takes about it takes one hour and<00:55:54.180> a<00:55:54.269> half<00:55:54.450> to<00:55:54.719> prove<00:55:55.049> on<00:55:55.319> AWS<00:55:56.190> and<00:55:56.910> it<00:55:57.150> costs 00:55:57.439 --> 00:55:57.449 align:start position:0% and a half to prove on AWS and it costs 00:55:57.449 --> 00:56:01.749 align:start position:0% and a half to prove on AWS and it costs like<00:55:59.359> $1500<00:56:00.359> a<00:56:00.539> little<00:56:00.959> bit<00:56:01.049> less<00:56:01.170> than<00:56:01.289> that 00:56:01.749 --> 00:56:01.759 align:start position:0% like $1500 a little bit less than that 00:56:01.759 --> 00:56:04.130 align:start position:0% like $1500 a little bit less than that and<00:56:02.759> we<00:56:03.089> want<00:56:03.269> to<00:56:03.329> reduce<00:56:03.509> this<00:56:03.719> and<00:56:03.779> we<00:56:04.019> think 00:56:04.130 --> 00:56:04.140 align:start position:0% and we want to reduce this and we think 00:56:04.140 --> 00:56:05.359 align:start position:0% and we want to reduce this and we think that<00:56:04.229> we<00:56:04.380> can<00:56:04.529> reduce<00:56:04.650> it<00:56:04.890> but<00:56:05.009> it<00:56:05.099> will<00:56:05.219> get 00:56:05.359 --> 00:56:05.369 align:start position:0% that we can reduce it but it will get 00:56:05.369 --> 00:56:08.569 align:start position:0% that we can reduce it but it will get more<00:56:05.489> expensive<00:56:06.739> and<00:56:07.739> then<00:56:08.219> there's<00:56:08.459> other 00:56:08.569 --> 00:56:08.579 align:start position:0% more expensive and then there's other 00:56:08.579 --> 00:56:10.189 align:start position:0% more expensive and then there's other way<00:56:08.699> to<00:56:08.759> reduce<00:56:09.089> it<00:56:09.239> to<00:56:09.269> instead<00:56:09.869> of<00:56:09.959> using<00:56:10.109> the 00:56:10.189 --> 00:56:10.199 align:start position:0% way to reduce it to instead of using the 00:56:10.199 --> 00:56:12.199 align:start position:0% way to reduce it to instead of using the cluster<00:56:10.469> we<00:56:10.559> can<00:56:10.680> use<00:56:10.799> GPUs<00:56:11.160> FPGAs<00:56:11.699> and<00:56:11.849> Asics 00:56:12.199 --> 00:56:12.209 align:start position:0% cluster we can use GPUs FPGAs and Asics 00:56:12.209 --> 00:56:14.920 align:start position:0% cluster we can use GPUs FPGAs and Asics and<00:56:12.509> those<00:56:13.049> are<00:56:13.199> all<00:56:13.319> open<00:56:13.650> open<00:56:14.400> areas<00:56:14.640> of 00:56:14.920 --> 00:56:14.930 align:start position:0% and those are all open open areas of 00:56:14.930 --> 00:56:17.509 align:start position:0% and those are all open open areas of research<00:56:15.930> that<00:56:15.989> or<00:56:16.400> implementations<00:56:17.400> that 00:56:17.509 --> 00:56:17.519 align:start position:0% research that or implementations that 00:56:17.519 --> 00:56:19.279 align:start position:0% research that or implementations that I'm<00:56:17.640> interested<00:56:18.509> in<00:56:18.599> to<00:56:18.690> talking<00:56:19.019> to<00:56:19.049> people 00:56:19.279 --> 00:56:19.289 align:start position:0% I'm interested in to talking to people 00:56:19.289 --> 00:56:20.539 align:start position:0% I'm interested in to talking to people about<00:56:19.469> if<00:56:19.769> people<00:56:20.009> are<00:56:20.099> interested<00:56:20.190> in<00:56:20.459> doing 00:56:20.539 --> 00:56:20.549 align:start position:0% about if people are interested in doing 00:56:20.549 --> 00:56:22.279 align:start position:0% about if people are interested in doing that<00:56:20.819> that's<00:56:20.999> cool<00:56:21.269> come<00:56:21.449> and<00:56:21.599> we<00:56:22.019> can<00:56:22.140> talk 00:56:22.279 --> 00:56:22.289 align:start position:0% that that's cool come and we can talk 00:56:22.289 --> 00:56:23.660 align:start position:0% that that's cool come and we can talk about<00:56:22.380> it 00:56:23.660 --> 00:56:23.670 align:start position:0% about it 00:56:23.670 --> 00:56:25.910 align:start position:0% about it can<00:56:24.479> we<00:56:24.569> add<00:56:24.690> strong<00:56:25.109> anonymity<00:56:25.469> properties 00:56:25.910 --> 00:56:25.920 align:start position:0% can we add strong anonymity properties 00:56:25.920 --> 00:56:29.299 align:start position:0% can we add strong anonymity properties to<00:56:26.069> this<00:56:26.190> system<00:56:27.410> that's<00:56:28.410> another<00:56:28.739> research 00:56:29.299 --> 00:56:29.309 align:start position:0% to this system that's another research 00:56:29.309 --> 00:56:30.469 align:start position:0% to this system that's another research question<00:56:29.609> because<00:56:29.789> everything<00:56:30.059> ok 00:56:30.469 --> 00:56:30.479 align:start position:0% question because everything ok 00:56:30.479 --> 00:56:31.759 align:start position:0% question because everything ok everything<00:56:30.989> is<00:56:31.049> completely<00:56:31.410> transparent 00:56:31.759 --> 00:56:31.769 align:start position:0% everything is completely transparent 00:56:31.769 --> 00:56:33.410 align:start position:0% everything is completely transparent here<00:56:32.130> just<00:56:32.670> because<00:56:32.819> we<00:56:32.940> used<00:56:33.059> to<00:56:33.119> start<00:56:33.329> to 00:56:33.410 --> 00:56:33.420 align:start position:0% here just because we used to start to 00:56:33.420 --> 00:56:34.459 align:start position:0% here just because we used to start to aggregate<00:56:33.690> the<00:56:33.869> data<00:56:33.900> it<00:56:34.140> doesn't<00:56:34.259> mean<00:56:34.440> that 00:56:34.459 --> 00:56:34.469 align:start position:0% aggregate the data it doesn't mean that 00:56:34.469 --> 00:56:36.199 align:start position:0% aggregate the data it doesn't mean that doesn't<00:56:35.249> mean<00:56:35.549> that<00:56:35.640> we<00:56:35.759> still<00:56:35.940> have<00:56:36.119> the 00:56:36.199 --> 00:56:36.209 align:start position:0% doesn't mean that we still have the 00:56:36.209 --> 00:56:37.630 align:start position:0% doesn't mean that we still have the anonymity<00:56:36.509> properties<00:56:37.049> that<00:56:37.140> we<00:56:37.229> had<00:56:37.349> before 00:56:37.630 --> 00:56:37.640 align:start position:0% anonymity properties that we had before 00:56:37.640 --> 00:56:40.609 align:start position:0% anonymity properties that we had before so<00:56:38.640> is<00:56:39.269> it<00:56:39.420> possible<00:56:39.539> to<00:56:39.839> add<00:56:39.959> those<00:56:40.109> anonymity 00:56:40.609 --> 00:56:40.619 align:start position:0% so is it possible to add those anonymity 00:56:40.619 --> 00:56:41.900 align:start position:0% so is it possible to add those anonymity properties<00:56:41.069> back<00:56:41.219> that's<00:56:41.729> another 00:56:41.900 --> 00:56:41.910 align:start position:0% properties back that's another 00:56:41.910 --> 00:56:44.719 align:start position:0% properties back that's another interesting<00:56:42.150> question<00:56:43.039> so<00:56:44.039> we<00:56:44.609> have 00:56:44.719 --> 00:56:44.729 align:start position:0% interesting question so we have 00:56:44.729 --> 00:56:46.519 align:start position:0% interesting question so we have optimizations<00:56:45.390> yeah<00:56:46.049> so<00:56:46.229> it's<00:56:46.380> it's 00:56:46.519 --> 00:56:46.529 align:start position:0% optimizations yeah so it's it's 00:56:46.529 --> 00:56:49.519 align:start position:0% optimizations yeah so it's it's interesting<00:56:46.890> it's<00:56:47.519> this<00:56:48.390> add<00:56:48.660> snarks<00:56:49.079> project 00:56:49.519 --> 00:56:49.529 align:start position:0% interesting it's this add snarks project 00:56:49.529 --> 00:56:52.430 align:start position:0% interesting it's this add snarks project have<00:56:49.890> done<00:56:50.099> a<00:56:50.130> lot<00:56:50.400> of<00:56:50.519> work<00:56:50.670> with<00:56:51.259> with<00:56:52.259> these 00:56:52.430 --> 00:56:52.440 align:start position:0% have done a lot of work with with these 00:56:52.440 --> 00:56:54.049 align:start position:0% have done a lot of work with with these these<00:56:52.829> optimizations<00:56:53.459> this<00:56:53.609> is<00:56:53.729> move<00:56:53.910> forward 00:56:54.049 --> 00:56:54.059 align:start position:0% these optimizations this is move forward 00:56:54.059 --> 00:56:58.489 align:start position:0% these optimizations this is move forward quite<00:56:54.359> quite<00:56:54.660> well<00:56:55.940> also<00:56:56.940> ID<00:56:57.390> ID<00:56:57.809> entry<00:56:58.229> have 00:56:58.489 --> 00:56:58.499 align:start position:0% quite quite well also ID ID entry have 00:56:58.499 --> 00:57:00.499 align:start position:0% quite quite well also ID ID entry have another<00:56:58.799> implementation<00:56:59.150> at<00:57:00.150> sites<00:57:00.390> are 00:57:00.499 --> 00:57:00.509 align:start position:0% another implementation at sites are 00:57:00.509 --> 00:57:02.630 align:start position:0% another implementation at sites are working<00:57:00.779> on<00:57:00.869> implementation<00:57:01.109> I<00:57:01.890> need<00:57:02.339> three 00:57:02.630 --> 00:57:02.640 align:start position:0% working on implementation I need three 00:57:02.640 --> 00:57:04.810 align:start position:0% working on implementation I need three are<00:57:02.789> working<00:57:02.910> on<00:57:03.119> implementation<00:57:03.420> two 00:57:04.810 --> 00:57:04.820 align:start position:0% are working on implementation two 00:57:04.820 --> 00:57:06.430 align:start position:0% are working on implementation two [Music] 00:57:06.430 --> 00:57:06.440 align:start position:0% [Music] 00:57:06.440 --> 00:57:08.780 align:start position:0% [Music] yeah<00:57:07.440> and<00:57:07.619> we're<00:57:07.740> gonna<00:57:07.829> replace<00:57:08.040> you<00:57:08.250> are<00:57:08.339> 256 00:57:08.780 --> 00:57:08.790 align:start position:0% yeah and we're gonna replace you are 256 00:57:08.790 --> 00:57:09.800 align:start position:0% yeah and we're gonna replace you are 256 with<00:57:08.970> pedals<00:57:09.150> and<00:57:09.240> commitments<00:57:09.630> in<00:57:09.690> some 00:57:09.800 --> 00:57:09.810 align:start position:0% with pedals and commitments in some 00:57:09.810 --> 00:57:11.780 align:start position:0% with pedals and commitments in some places<00:57:10.579> good 00:57:11.780 --> 00:57:11.790 align:start position:0% places good 00:57:11.790 --> 00:57:14.510 align:start position:0% places good so<00:57:11.970> future<00:57:12.270> work<00:57:13.010> yeah<00:57:14.010> so<00:57:14.190> we<00:57:14.280> want<00:57:14.460> to 00:57:14.510 --> 00:57:14.520 align:start position:0% so future work yeah so we want to 00:57:14.520 --> 00:57:16.460 align:start position:0% so future work yeah so we want to implement<00:57:14.820> both<00:57:14.910> approaches<00:57:15.450> yeah<00:57:16.050> so<00:57:16.260> if<00:57:16.380> so 00:57:16.460 --> 00:57:16.470 align:start position:0% implement both approaches yeah so if so 00:57:16.470 --> 00:57:18.290 align:start position:0% implement both approaches yeah so if so many<00:57:16.589> if<00:57:17.130> there's<00:57:17.400> if<00:57:17.640> someone<00:57:18.180> who's 00:57:18.290 --> 00:57:18.300 align:start position:0% many if there's if someone who's 00:57:18.300 --> 00:57:19.910 align:start position:0% many if there's if someone who's implement<00:57:18.720> interests<00:57:19.290> in<00:57:19.349> implementing<00:57:19.800> the 00:57:19.910 --> 00:57:19.920 align:start position:0% implement interests in implementing the 00:57:19.920 --> 00:57:21.829 align:start position:0% implement interests in implementing the other<00:57:20.040> approach<00:57:20.339> the<00:57:20.670> it's<00:57:21.510> not<00:57:21.660> as<00:57:21.750> my 00:57:21.829 --> 00:57:21.839 align:start position:0% other approach the it's not as my 00:57:21.839 --> 00:57:23.000 align:start position:0% other approach the it's not as my approach<00:57:22.050> would<00:57:22.260> be<00:57:22.290> interested<00:57:22.650> in<00:57:22.740> that<00:57:22.800> too 00:57:23.000 --> 00:57:23.010 align:start position:0% approach would be interested in that too 00:57:23.010 --> 00:57:26.120 align:start position:0% approach would be interested in that too and<00:57:23.270> so<00:57:24.270> we're<00:57:24.930> interested<00:57:25.530> in<00:57:25.770> hearing<00:57:25.980> about 00:57:26.120 --> 00:57:26.130 align:start position:0% and so we're interested in hearing about 00:57:26.130 --> 00:57:28.790 align:start position:0% and so we're interested in hearing about generic<00:57:26.970> other<00:57:27.390> use<00:57:27.630> cases<00:57:27.869> other<00:57:28.260> than<00:57:28.500> just 00:57:28.790 --> 00:57:28.800 align:start position:0% generic other use cases other than just 00:57:28.800 --> 00:57:31.280 align:start position:0% generic other use cases other than just scaling<00:57:29.490> and<00:57:29.760> tokens<00:57:30.119> or<00:57:30.450> tokens<00:57:31.050> and<00:57:31.170> stuff 00:57:31.280 --> 00:57:31.290 align:start position:0% scaling and tokens or tokens and stuff 00:57:31.290 --> 00:57:32.480 align:start position:0% scaling and tokens or tokens and stuff like<00:57:31.380> that<00:57:31.530> I'd<00:57:31.770> be<00:57:31.920> interested<00:57:32.099> to<00:57:32.280> hear<00:57:32.369> all 00:57:32.480 --> 00:57:32.490 align:start position:0% like that I'd be interested to hear all 00:57:32.490 --> 00:57:33.980 align:start position:0% like that I'd be interested to hear all the<00:57:32.550> use<00:57:32.670> cases<00:57:32.880> that<00:57:33.030> we<00:57:33.510> can<00:57:33.720> use<00:57:33.839> it<00:57:33.960> to 00:57:33.980 --> 00:57:33.990 align:start position:0% the use cases that we can use it to 00:57:33.990 --> 00:57:35.390 align:start position:0% the use cases that we can use it to aggregate<00:57:34.470> transactions<00:57:35.040> together<00:57:35.250> and 00:57:35.390 --> 00:57:35.400 align:start position:0% aggregate transactions together and 00:57:35.400 --> 00:57:36.440 align:start position:0% aggregate transactions together and aggregated<00:57:35.790> like<00:57:35.910> bolts<00:57:36.240> and<00:57:36.390> things 00:57:36.440 --> 00:57:36.450 align:start position:0% aggregated like bolts and things 00:57:36.450 --> 00:57:38.569 align:start position:0% aggregated like bolts and things together<00:57:36.630> I<00:57:37.050> know<00:57:37.800> that<00:57:38.040> comes<00:57:38.220> with<00:57:38.369> a<00:57:38.400> bunch 00:57:38.569 --> 00:57:38.579 align:start position:0% together I know that comes with a bunch 00:57:38.579 --> 00:57:40.790 align:start position:0% together I know that comes with a bunch of<00:57:38.640> problems<00:57:38.849> still<00:57:39.660> oh<00:57:39.930> yeah<00:57:40.470> we<00:57:40.619> could<00:57:40.740> do 00:57:40.790 --> 00:57:40.800 align:start position:0% of problems still oh yeah we could do 00:57:40.800 --> 00:57:44.810 align:start position:0% of problems still oh yeah we could do that<00:57:40.920> too<00:57:42.260> non<00:57:43.260> fundable<00:57:43.589> token<00:57:43.920> maybe<00:57:44.550> we<00:57:44.700> can 00:57:44.810 --> 00:57:44.820 align:start position:0% that too non fundable token maybe we can 00:57:44.820 --> 00:57:47.750 align:start position:0% that too non fundable token maybe we can make<00:57:44.880> an<00:57:45.000> exchange<00:57:45.270> with<00:57:45.390> this<00:57:46.640> request<00:57:47.640> so 00:57:47.750 --> 00:57:47.760 align:start position:0% make an exchange with this request so 00:57:47.760 --> 00:57:49.370 align:start position:0% make an exchange with this request so this<00:57:47.880> is<00:57:48.030> like<00:57:48.180> a<00:57:48.210> request<00:57:48.630> so<00:57:48.810> if<00:57:48.960> we<00:57:49.109> good<00:57:49.290> to 00:57:49.370 --> 00:57:49.380 align:start position:0% this is like a request so if we good to 00:57:49.380 --> 00:57:51.220 align:start position:0% this is like a request so if we good to have<00:57:49.500> the<00:57:49.619> guards<00:57:49.859> cost<00:57:50.040> reduced<00:57:50.369> in<00:57:50.520> the<00:57:50.579> EVM 00:57:51.220 --> 00:57:51.230 align:start position:0% have the guards cost reduced in the EVM 00:57:51.230 --> 00:57:53.450 align:start position:0% have the guards cost reduced in the EVM newarker<00:57:52.230> for<00:57:52.500> more<00:57:52.650> security<00:57:52.829> would<00:57:53.190> be<00:57:53.220> nice 00:57:53.450 --> 00:57:53.460 align:start position:0% newarker for more security would be nice 00:57:53.460 --> 00:57:55.400 align:start position:0% newarker for more security would be nice so<00:57:54.119> we<00:57:54.240> use<00:57:54.359> I'll<00:57:54.510> be<00:57:54.630> I'm<00:57:54.720> 128<00:57:55.140> right<00:57:55.290> now 00:57:55.400 --> 00:57:55.410 align:start position:0% so we use I'll be I'm 128 right now 00:57:55.410 --> 00:57:57.260 align:start position:0% so we use I'll be I'm 128 right now would<00:57:55.589> be<00:57:55.710> nice<00:57:55.859> to<00:57:56.010> move<00:57:56.190> to<00:57:56.369> be<00:57:56.550> LS<00:57:56.820> the<00:57:57.150> one 00:57:57.260 --> 00:57:57.270 align:start position:0% would be nice to move to be LS the one 00:57:57.270 --> 00:57:58.819 align:start position:0% would be nice to move to be LS the one that<00:57:57.420> seeker<00:57:57.630> uses<00:57:58.109> and<00:57:58.380> that<00:57:58.410> means<00:57:58.650> we<00:57:58.710> could 00:57:58.819 --> 00:57:58.829 align:start position:0% that seeker uses and that means we could 00:57:58.829 --> 00:58:00.410 align:start position:0% that seeker uses and that means we could reuse<00:57:58.980> a<00:57:59.099> bunch<00:57:59.339> of<00:57:59.400> they're<00:57:59.520> a<00:57:59.790> bunch<00:58:00.359> of 00:58:00.410 --> 00:58:00.420 align:start position:0% reuse a bunch of they're a bunch of 00:58:00.420 --> 00:58:02.599 align:start position:0% reuse a bunch of they're a bunch of their<00:58:00.599> signature<00:58:01.530> schemes<00:58:02.040> and<00:58:02.339> stuff<00:58:02.550> like 00:58:02.599 --> 00:58:02.609 align:start position:0% their signature schemes and stuff like 00:58:02.609 --> 00:58:03.980 align:start position:0% their signature schemes and stuff like that<00:58:02.790> and<00:58:03.030> a<00:58:03.060> bunch<00:58:03.240> of<00:58:03.270> their<00:58:03.390> tools<00:58:03.570> and<00:58:03.810> we 00:58:03.980 --> 00:58:03.990 align:start position:0% that and a bunch of their tools and we 00:58:03.990 --> 00:58:05.000 align:start position:0% that and a bunch of their tools and we can<00:58:04.109> all<00:58:04.200> just<00:58:04.230> be<00:58:04.500> working<00:58:04.740> on<00:58:04.829> the<00:58:04.890> same 00:58:05.000 --> 00:58:05.010 align:start position:0% can all just be working on the same 00:58:05.010 --> 00:58:08.750 align:start position:0% can all just be working on the same curve<00:58:05.220> that<00:58:05.520> would<00:58:05.609> be<00:58:05.730> great<00:58:07.490> and<00:58:08.490> it<00:58:08.670> would 00:58:08.750 --> 00:58:08.760 align:start position:0% curve that would be great and it would 00:58:08.760 --> 00:58:09.500 align:start position:0% curve that would be great and it would be<00:58:08.880> good<00:58:09.030> to<00:58:09.060> have<00:58:09.240> a<00:58:09.300> hash<00:58:09.480> function 00:58:09.500 --> 00:58:09.510 align:start position:0% be good to have a hash function 00:58:09.510 --> 00:58:11.240 align:start position:0% be good to have a hash function pre-compile<00:58:10.230> that<00:58:10.440> that's<00:58:10.680> efficient<00:58:11.040> inside 00:58:11.240 --> 00:58:11.250 align:start position:0% pre-compile that that's efficient inside 00:58:11.250 --> 00:58:12.290 align:start position:0% pre-compile that that's efficient inside the<00:58:11.310> snark<00:58:11.520> something<00:58:11.880> like<00:58:12.000> Patterson 00:58:12.290 --> 00:58:12.300 align:start position:0% the snark something like Patterson 00:58:12.300 --> 00:58:15.579 align:start position:0% the snark something like Patterson commitments<00:58:12.660> that'll<00:58:13.020> be<00:58:13.079> cool<00:58:13.280> ok<00:58:14.280> that's<00:58:14.609> it 00:58:15.579 --> 00:58:15.589 align:start position:0% commitments that'll be cool ok that's it 00:58:15.589 --> 00:58:17.620 align:start position:0% commitments that'll be cool ok that's it ok 00:58:17.620 --> 00:58:17.630 align:start position:0% ok 00:58:17.630 --> 00:58:23.510 align:start position:0% ok [Applause] 00:58:23.510 --> 00:58:23.520 align:start position:0% [Applause] 00:58:23.520 --> 00:58:25.710 align:start position:0% [Applause] okay<00:58:24.520> so<00:58:24.580> um<00:58:25.060> do<00:58:25.240> we<00:58:25.270> have<00:58:25.360> time<00:58:25.540> for<00:58:25.570> questions 00:58:25.710 --> 00:58:25.720 align:start position:0% okay so um do we have time for questions 00:58:25.720 --> 00:58:27.690 align:start position:0% okay so um do we have time for questions yeah<00:58:26.290> we<00:58:26.410> have<00:58:26.560> time<00:58:26.830> for<00:58:26.860> maybe<00:58:27.070> one<00:58:27.190> or<00:58:27.400> two 00:58:27.690 --> 00:58:27.700 align:start position:0% yeah we have time for maybe one or two 00:58:27.700 --> 00:58:31.140 align:start position:0% yeah we have time for maybe one or two questions<00:58:27.900> okay<00:58:29.190> if<00:58:30.190> people<00:58:30.250> want<00:58:30.880> to<00:58:30.910> ask<00:58:30.970> me 00:58:31.140 --> 00:58:31.150 align:start position:0% questions okay if people want to ask me 00:58:31.150 --> 00:58:32.280 align:start position:0% questions okay if people want to ask me more<00:58:31.300> questions<00:58:31.360> I'll<00:58:31.780> just<00:58:31.960> hang<00:58:32.200> out 00:58:32.280 --> 00:58:32.290 align:start position:0% more questions I'll just hang out 00:58:32.290 --> 00:58:34.170 align:start position:0% more questions I'll just hang out outside<00:58:32.470> for<00:58:32.650> a<00:58:32.860> little<00:58:32.980> while<00:58:33.190> and<00:58:33.940> we<00:58:34.060> can 00:58:34.170 --> 00:58:34.180 align:start position:0% outside for a little while and we can 00:58:34.180 --> 00:58:35.160 align:start position:0% outside for a little while and we can talk<00:58:34.360> okay 00:58:35.160 --> 00:58:35.170 align:start position:0% talk okay 00:58:35.170 --> 00:58:42.060 align:start position:0% talk okay okay<00:58:35.590> so<00:58:35.650> who<00:58:35.950> has<00:58:36.070> any<00:58:36.220> questions<00:58:39.510> yeah<00:58:41.070> you 00:58:42.060 --> 00:58:42.070 align:start position:0% okay so who has any questions yeah you 00:58:42.070 --> 00:58:44.210 align:start position:0% okay so who has any questions yeah you mentioned<00:58:42.400> one<00:58:42.640> possible<00:58:43.120> use<00:58:43.270> case<00:58:43.450> is 00:58:44.210 --> 00:58:44.220 align:start position:0% mentioned one possible use case is 00:58:44.220 --> 00:58:47.730 align:start position:0% mentioned one possible use case is quadratic<00:58:45.220> voting<00:58:45.700> and<00:58:46.180> I'm<00:58:47.080> wondering<00:58:47.680> if 00:58:47.730 --> 00:58:47.740 align:start position:0% quadratic voting and I'm wondering if 00:58:47.740 --> 00:58:49.170 align:start position:0% quadratic voting and I'm wondering if you<00:58:47.800> have<00:58:47.890> any<00:58:48.040> like<00:58:48.160> tight<00:58:48.430> design<00:58:48.850> ideas 00:58:49.170 --> 00:58:49.180 align:start position:0% you have any like tight design ideas 00:58:49.180 --> 00:58:54.330 align:start position:0% you have any like tight design ideas about<00:58:49.390> how<00:58:49.840> you<00:58:50.350> can<00:58:52.590> ensure<00:58:53.590> that<00:58:53.830> someone 00:58:54.330 --> 00:58:54.340 align:start position:0% about how you can ensure that someone 00:58:54.340 --> 00:58:57.300 align:start position:0% about how you can ensure that someone doesn't<00:58:54.790> have<00:58:55.660> create<00:58:56.320> multiple<00:58:56.770> identities 00:58:57.300 --> 00:58:57.310 align:start position:0% doesn't have create multiple identities 00:58:57.310 --> 00:59:00.510 align:start position:0% doesn't have create multiple identities in<00:58:57.610> order<00:58:57.700> to<00:58:57.910> skew<00:58:58.540> quadratic<00:58:59.230> voting<00:58:59.620> okay 00:59:00.510 --> 00:59:00.520 align:start position:0% in order to skew quadratic voting okay 00:59:00.520 --> 00:59:02.610 align:start position:0% in order to skew quadratic voting okay so<00:59:00.820> there's<00:59:01.000> like<00:59:01.120> there's<00:59:01.480> like<00:59:01.540> some<00:59:02.350> ideas 00:59:02.610 --> 00:59:02.620 align:start position:0% so there's like there's like some ideas 00:59:02.620 --> 00:59:04.440 align:start position:0% so there's like there's like some ideas about<00:59:02.710> this<00:59:02.920> one<00:59:03.160> thing<00:59:03.310> we<00:59:03.430> could<00:59:03.580> do<00:59:03.700> is<00:59:03.910> and 00:59:04.440 --> 00:59:04.450 align:start position:0% about this one thing we could do is and 00:59:04.450 --> 00:59:06.680 align:start position:0% about this one thing we could do is and it's<00:59:04.600> a<00:59:04.660> bit<00:59:04.810> creepy<00:59:05.170> as<00:59:05.290> we<00:59:05.470> could<00:59:05.650> use<00:59:05.830> like 00:59:06.680 --> 00:59:06.690 align:start position:0% it's a bit creepy as we could use like 00:59:06.690 --> 00:59:09.600 align:start position:0% it's a bit creepy as we could use like we<00:59:07.690> could<00:59:07.840> use<00:59:08.100> biometrics<00:59:09.100> in<00:59:09.250> order<00:59:09.490> to 00:59:09.600 --> 00:59:09.610 align:start position:0% we could use biometrics in order to 00:59:09.610 --> 00:59:10.560 align:start position:0% we could use biometrics in order to limit<00:59:09.730> the<00:59:09.880> amount<00:59:10.030> of<00:59:10.120> people<00:59:10.240> who<00:59:10.390> are<00:59:10.480> able 00:59:10.560 --> 00:59:10.570 align:start position:0% limit the amount of people who are able 00:59:10.570 --> 00:59:12.840 align:start position:0% limit the amount of people who are able to<00:59:10.690> join<00:59:10.810> our<00:59:10.930> group<00:59:11.200> but<00:59:12.070> this<00:59:12.190> is<00:59:12.400> this<00:59:12.700> has 00:59:12.840 --> 00:59:12.850 align:start position:0% to join our group but this is this has 00:59:12.850 --> 00:59:14.160 align:start position:0% to join our group but this is this has problems<00:59:13.210> too<00:59:13.360> because<00:59:13.690> people<00:59:13.900> can<00:59:14.020> just 00:59:14.160 --> 00:59:14.170 align:start position:0% problems too because people can just 00:59:14.170 --> 00:59:16.860 align:start position:0% problems too because people can just make<00:59:14.290> fake<00:59:14.650> biometrics<00:59:15.280> yeah<00:59:15.970> so<00:59:16.660> we'd<00:59:16.840> have 00:59:16.860 --> 00:59:16.870 align:start position:0% make fake biometrics yeah so we'd have 00:59:16.870 --> 00:59:19.340 align:start position:0% make fake biometrics yeah so we'd have to<00:59:17.080> have<00:59:17.200> some<00:59:17.410> kind<00:59:17.590> of<00:59:17.880> real-world 00:59:19.340 --> 00:59:19.350 align:start position:0% to have some kind of real-world 00:59:19.350 --> 00:59:22.350 align:start position:0% to have some kind of real-world biometric<00:59:20.350> testing<00:59:20.830> station<00:59:21.250> and<00:59:21.940> that's<00:59:22.150> not 00:59:22.350 --> 00:59:22.360 align:start position:0% biometric testing station and that's not 00:59:22.360 --> 00:59:24.420 align:start position:0% biometric testing station and that's not really<00:59:22.660> very<00:59:22.690> I<00:59:23.140> don't<00:59:23.740> know<00:59:23.800> that<00:59:24.040> has<00:59:24.280> some 00:59:24.420 --> 00:59:24.430 align:start position:0% really very I don't know that has some 00:59:24.430 --> 00:59:26.160 align:start position:0% really very I don't know that has some problems<00:59:24.550> it's<00:59:25.330> game<00:59:25.540> of<00:59:25.690> all<00:59:25.810> the<00:59:26.050> other 00:59:26.160 --> 00:59:26.170 align:start position:0% problems it's game of all the other 00:59:26.170 --> 00:59:27.720 align:start position:0% problems it's game of all the other thing<00:59:26.380> is<00:59:26.500> that<00:59:26.530> we<00:59:26.710> can<00:59:26.830> have<00:59:26.950> a<00:59:26.980> we<00:59:27.460> can<00:59:27.580> have 00:59:27.720 --> 00:59:27.730 align:start position:0% thing is that we can have a we can have 00:59:27.730 --> 00:59:31.140 align:start position:0% thing is that we can have a we can have this<00:59:27.850> kind<00:59:28.090> of<00:59:28.300> these<00:59:29.230> kind<00:59:29.470> of<00:59:29.880> parties<00:59:30.880> where 00:59:31.140 --> 00:59:31.150 align:start position:0% this kind of these kind of parties where 00:59:31.150 --> 00:59:34.680 align:start position:0% this kind of these kind of parties where everyone<00:59:31.630> comes<00:59:31.870> and<00:59:32.220> you<00:59:33.390> everywhere<00:59:34.390> every 00:59:34.680 --> 00:59:34.690 align:start position:0% everyone comes and you everywhere every 00:59:34.690 --> 00:59:37.970 align:start position:0% everyone comes and you everywhere every attendee<00:59:35.080> is<00:59:35.380> able<00:59:35.620> to<00:59:35.710> join<00:59:35.860> the<00:59:35.980> group<00:59:36.130> but 00:59:37.970 --> 00:59:37.980 align:start position:0% attendee is able to join the group but 00:59:37.980 --> 00:59:40.830 align:start position:0% attendee is able to join the group but but<00:59:38.980> that<00:59:39.010> kind<00:59:39.310> of<00:59:39.400> limits<00:59:39.670> us<00:59:39.790> because<00:59:40.180> every 00:59:40.830 --> 00:59:40.840 align:start position:0% but that kind of limits us because every 00:59:40.840 --> 00:59:42.990 align:start position:0% but that kind of limits us because every attendee<00:59:41.220> you<00:59:42.220> could<00:59:42.370> just<00:59:42.520> get<00:59:42.640> your<00:59:42.700> friends 00:59:42.990 --> 00:59:43.000 align:start position:0% attendee you could just get your friends 00:59:43.000 --> 00:59:45.030 align:start position:0% attendee you could just get your friends to<00:59:43.090> come<00:59:43.210> and<00:59:43.270> take<00:59:43.540> their<00:59:43.750> take<00:59:44.560> their<00:59:44.740> keys 00:59:45.030 --> 00:59:45.040 align:start position:0% to come and take their take their keys 00:59:45.040 --> 00:59:46.710 align:start position:0% to come and take their take their keys or<00:59:45.460> take<00:59:45.700> their<00:59:45.850> position<00:59:46.420> in<00:59:46.510> the<00:59:46.570> group 00:59:46.710 --> 00:59:46.720 align:start position:0% or take their position in the group 00:59:46.720 --> 00:59:49.440 align:start position:0% or take their position in the group another<00:59:47.500> thing<00:59:47.770> that<00:59:47.920> we<00:59:48.010> could<00:59:48.160> do<00:59:48.340> is<00:59:48.820> we 00:59:49.440 --> 00:59:49.450 align:start position:0% another thing that we could do is we 00:59:49.450 --> 00:59:50.820 align:start position:0% another thing that we could do is we could<00:59:49.660> have<00:59:49.810> this<00:59:49.900> like<00:59:50.110> really<00:59:50.350> high<00:59:50.470> barrier 00:59:50.820 --> 00:59:50.830 align:start position:0% could have this like really high barrier 00:59:50.830 --> 00:59:52.560 align:start position:0% could have this like really high barrier to<00:59:51.040> entry<00:59:51.160> and<00:59:51.490> say<00:59:51.670> that<00:59:51.850> you<00:59:51.940> have<00:59:52.090> to<00:59:52.210> have 00:59:52.560 --> 00:59:52.570 align:start position:0% to entry and say that you have to have 00:59:52.570 --> 00:59:54.210 align:start position:0% to entry and say that you have to have accomplished<00:59:52.990> X<00:59:53.200> Y<00:59:53.320> inside<00:59:53.620> in<00:59:53.800> order<00:59:53.980> to<00:59:54.040> join 00:59:54.210 --> 00:59:54.220 align:start position:0% accomplished X Y inside in order to join 00:59:54.220 --> 00:59:55.890 align:start position:0% accomplished X Y inside in order to join but<00:59:54.790> that's<00:59:54.970> not<00:59:55.120> very<00:59:55.150> good<00:59:55.390> either<00:59:55.510> because 00:59:55.890 --> 00:59:55.900 align:start position:0% but that's not very good either because 00:59:55.900 --> 00:59:57.090 align:start position:0% but that's not very good either because I<00:59:55.930> mean<00:59:56.170> sort<00:59:56.380> of<00:59:56.470> limits<00:59:56.770> the<00:59:56.890> amount<00:59:56.980> of 00:59:57.090 --> 00:59:57.100 align:start position:0% I mean sort of limits the amount of 00:59:57.100 --> 00:59:59.430 align:start position:0% I mean sort of limits the amount of people<00:59:57.220> that<00:59:57.460> can<00:59:57.580> join<00:59:57.760> and<00:59:58.390> can<00:59:58.660> be<00:59:58.840> sort<00:59:59.410> of 00:59:59.430 --> 00:59:59.440 align:start position:0% people that can join and can be sort of 00:59:59.440 --> 01:00:02.040 align:start position:0% people that can join and can be sort of commit<00:59:59.680> to<00:59:59.800> it<00:59:59.920> so<01:00:00.670> yeah<01:00:00.940> I<01:00:01.270> I<01:00:01.390> mean<01:00:01.750> it's<01:00:01.900> sort 01:00:02.040 --> 01:00:02.050 align:start position:0% commit to it so yeah I I mean it's sort 01:00:02.050 --> 01:00:04.500 align:start position:0% commit to it so yeah I I mean it's sort of<01:00:02.170> it's<01:00:02.830> a<01:00:02.950> difficult<01:00:03.340> problem<01:00:03.460> I<01:00:03.700> think<01:00:03.760> and 01:00:04.500 --> 01:00:04.510 align:start position:0% of it's a difficult problem I think and 01:00:04.510 --> 01:00:06.330 align:start position:0% of it's a difficult problem I think and it's<01:00:04.750> but<01:00:05.290> it's<01:00:05.440> one<01:00:05.680> that's<01:00:05.860> important<01:00:06.220> to 01:00:06.330 --> 01:00:06.340 align:start position:0% it's but it's one that's important to 01:00:06.340 --> 01:00:07.890 align:start position:0% it's but it's one that's important to sort<01:00:06.610> of<01:00:06.700> figure<01:00:06.880> out<01:00:06.940> and<01:00:07.090> solve<01:00:07.180> so<01:00:07.750> I<01:00:07.780> think 01:00:07.890 --> 01:00:07.900 align:start position:0% sort of figure out and solve so I think 01:00:07.900 --> 01:00:09.330 align:start position:0% sort of figure out and solve so I think a<01:00:08.050> good<01:00:08.170> approach<01:00:08.410> would<01:00:08.620> be<01:00:08.650> to<01:00:08.740> do<01:00:09.010> like<01:00:09.190> some 01:00:09.330 --> 01:00:09.340 align:start position:0% a good approach would be to do like some 01:00:09.340 --> 01:00:11.280 align:start position:0% a good approach would be to do like some sort<01:00:09.520> of<01:00:09.580> trusted<01:00:09.820> Hardware<01:00:10.480> with<01:00:10.660> with<01:00:11.110> some 01:00:11.280 --> 01:00:11.290 align:start position:0% sort of trusted Hardware with with some 01:00:11.290 --> 01:00:12.990 align:start position:0% sort of trusted Hardware with with some sort<01:00:11.470> of<01:00:11.500> biometric<01:00:12.070> database<01:00:12.460> or<01:00:12.910> something 01:00:12.990 --> 01:00:13.000 align:start position:0% sort of biometric database or something 01:00:13.000 --> 01:00:15.750 align:start position:0% sort of biometric database or something like<01:00:13.270> that<01:00:13.450> I<01:00:13.690> mean<01:00:14.290> it's<01:00:14.470> it's<01:00:15.040> not<01:00:15.190> very<01:00:15.430> it's 01:00:15.750 --> 01:00:15.760 align:start position:0% like that I mean it's it's not very it's 01:00:15.760 --> 01:00:18.060 align:start position:0% like that I mean it's it's not very it's not<01:00:15.880> very<01:00:16.120> nice<01:00:16.270> but<01:00:16.320> if<01:00:17.320> we<01:00:17.740> need<01:00:17.890> to<01:00:17.980> do 01:00:18.060 --> 01:00:18.070 align:start position:0% not very nice but if we need to do 01:00:18.070 --> 01:00:20.990 align:start position:0% not very nice but if we need to do something<01:00:18.310> like<01:00:18.400> that<01:00:18.460> we<01:00:18.730> could<01:00:18.850> do<01:00:18.970> that 01:00:20.990 --> 01:00:21.000 align:start position:0% something like that we could do that 01:00:21.000 --> 01:00:25.440 align:start position:0% something like that we could do that yeah<01:00:23.400> the<01:00:24.400> white<01:00:24.640> t-shirt<01:00:24.760> he<01:00:25.090> asked<01:00:25.270> first 01:00:25.440 --> 01:00:25.450 align:start position:0% yeah the white t-shirt he asked first 01:00:25.450 --> 01:00:29.100 align:start position:0% yeah the white t-shirt he asked first and<01:00:25.720> then<01:00:26.190> is<01:00:27.190> the<01:00:27.430> stuff<01:00:27.940> that<01:00:27.970> stock<01:00:28.480> wear<01:00:28.720> is 01:00:29.100 --> 01:00:29.110 align:start position:0% and then is the stuff that stock wear is 01:00:29.110 --> 01:00:30.330 align:start position:0% and then is the stuff that stock wear is working<01:00:29.590> on<01:00:29.710> could<01:00:29.890> that<01:00:30.040> potentially 01:00:30.330 --> 01:00:30.340 align:start position:0% working on could that potentially 01:00:30.340 --> 01:00:32.730 align:start position:0% working on could that potentially improve<01:00:31.060> the<01:00:31.360> efficiency<01:00:32.260> of<01:00:32.290> this<01:00:32.440> there's<01:00:32.680> a 01:00:32.730 --> 01:00:32.740 align:start position:0% improve the efficiency of this there's a 01:00:32.740 --> 01:00:34.770 align:start position:0% improve the efficiency of this there's a completely<01:00:33.250> different<01:00:33.580> right<01:00:34.060> so<01:00:34.270> they<01:00:34.390> would 01:00:34.770 --> 01:00:34.780 align:start position:0% completely different right so they would 01:00:34.780 --> 01:00:35.640 align:start position:0% completely different right so they would improve<01:00:34.960> they<01:00:35.320> would 01:00:35.640 --> 01:00:35.650 align:start position:0% improve they would 01:00:35.650 --> 01:00:38.430 align:start position:0% improve they would they're<01:00:35.890> proving<01:00:36.190> time<01:00:36.340> but<01:00:36.820> I<01:00:37.630> they<01:00:38.290> would 01:00:38.430 --> 01:00:38.440 align:start position:0% they're proving time but I they would 01:00:38.440 --> 01:00:39.540 align:start position:0% they're proving time but I they would prove<01:00:38.590> improve<01:00:38.920> the<01:00:39.010> pooping<01:00:39.250> time<01:00:39.400> but 01:00:39.540 --> 01:00:39.550 align:start position:0% prove improve the pooping time but 01:00:39.550 --> 01:00:40.860 align:start position:0% prove improve the pooping time but currently<01:00:40.090> the<01:00:40.180> proves<01:00:40.390> are<01:00:40.510> a<01:00:40.540> little<01:00:40.780> bit 01:00:40.860 --> 01:00:40.870 align:start position:0% currently the proves are a little bit 01:00:40.870 --> 01:00:43.590 align:start position:0% currently the proves are a little bit big<01:00:41.020> on<01:00:41.950> it<01:00:42.760> still<01:00:42.970> I<01:00:43.180> mean<01:00:43.330> I'm<01:00:43.450> totally 01:00:43.590 --> 01:00:43.600 align:start position:0% big on it still I mean I'm totally 01:00:43.600 --> 01:00:44.820 align:start position:0% big on it still I mean I'm totally interested<01:00:43.870> in<01:00:44.170> and<01:00:44.410> seeing<01:00:44.590> what<01:00:44.710> they<01:00:44.800> have 01:00:44.820 --> 01:00:44.830 align:start position:0% interested in and seeing what they have 01:00:44.830 --> 01:00:47.430 align:start position:0% interested in and seeing what they have when<01:00:45.400> when<01:00:46.090> they<01:00:46.210> sort<01:00:46.540> of<01:00:46.630> when<01:00:47.290> they're 01:00:47.430 --> 01:00:47.440 align:start position:0% when when they sort of when they're 01:00:47.440 --> 01:00:49.020 align:start position:0% when when they sort of when they're ready<01:00:47.590> for<01:00:47.620> that<01:00:47.860> but<01:00:48.070> it's<01:00:48.220> still<01:00:48.400> it's<01:00:48.850> still 01:00:49.020 --> 01:00:49.030 align:start position:0% ready for that but it's still it's still 01:00:49.030 --> 01:00:51.330 align:start position:0% ready for that but it's still it's still moving<01:00:49.390> forward<01:00:49.690> I<01:00:49.870> guess<01:00:50.530> it<01:00:50.980> would<01:00:51.100> be<01:00:51.130> good 01:00:51.330 --> 01:00:51.340 align:start position:0% moving forward I guess it would be good 01:00:51.340 --> 01:00:53.490 align:start position:0% moving forward I guess it would be good to<01:00:51.370> talk<01:00:51.550> to<01:00:51.610> you<01:00:51.730> who's<01:00:52.330> here<01:00:52.540> he<01:00:52.840> sort<01:00:53.320> of<01:00:53.350> has 01:00:53.490 --> 01:00:53.500 align:start position:0% to talk to you who's here he sort of has 01:00:53.500 --> 01:00:55.920 align:start position:0% to talk to you who's here he sort of has some<01:00:53.530> more<01:00:53.890> more<01:00:54.520> ideas<01:00:54.940> about<01:00:55.090> that<01:00:55.210> yeah 01:00:55.920 --> 01:00:55.930 align:start position:0% some more more ideas about that yeah 01:00:55.930 --> 01:00:58.350 align:start position:0% some more more ideas about that yeah okay<01:00:56.530> cool<01:00:56.710> sorry<01:00:56.860> that's<01:00:57.070> my<01:00:57.190> time<01:00:57.370> if<01:00:58.030> anyone 01:00:58.350 --> 01:00:58.360 align:start position:0% okay cool sorry that's my time if anyone 01:00:58.360 --> 01:00:59.310 align:start position:0% okay cool sorry that's my time if anyone wants<01:00:58.570> to<01:00:58.600> talk<01:00:58.780> I'll<01:00:58.900> be<01:00:59.020> outside 01:00:59.310 --> 01:00:59.320 align:start position:0% wants to talk I'll be outside 01:00:59.320 --> 01:01:10.330 align:start position:0% wants to talk I'll be outside yeah<01:00:59.680> pour<01:00:59.890> like<01:01:00.010> the<01:01:00.130> next 01:01:10.330 --> 01:01:10.340 align:start position:0% 01:01:10.340 --> 01:01:12.400 align:start position:0% you