WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.120 align:start position:0% [Applause] 00:00:11.120 --> 00:00:11.130 align:start position:0% 00:00:11.130 --> 00:00:14.610 align:start position:0% thanks<00:00:12.130> was<00:00:12.250> taking<00:00:12.550> around<00:00:12.760> my<00:00:13.750> name<00:00:13.960> is<00:00:14.080> an 00:00:14.610 --> 00:00:14.620 align:start position:0% thanks was taking around my name is an 00:00:14.620 --> 00:00:16.260 align:start position:0% thanks was taking around my name is an easy<00:00:14.860> I'm<00:00:15.100> one<00:00:15.280> of<00:00:15.370> the<00:00:15.490> co-founders<00:00:15.639> at 00:00:16.260 --> 00:00:16.270 align:start position:0% easy I'm one of the co-founders at 00:00:16.270 --> 00:00:19.109 align:start position:0% easy I'm one of the co-founders at argent<00:00:17.070> and<00:00:18.070> today<00:00:18.430> actually<00:00:18.550> I<00:00:18.760> would<00:00:18.880> not<00:00:19.000> be 00:00:19.109 --> 00:00:19.119 align:start position:0% argent and today actually I would not be 00:00:19.119 --> 00:00:20.310 align:start position:0% argent and today actually I would not be speaking<00:00:19.480> about<00:00:19.570> our<00:00:19.779> agenda<00:00:19.900> will<00:00:20.230> be 00:00:20.310 --> 00:00:20.320 align:start position:0% speaking about our agenda will be 00:00:20.320 --> 00:00:21.900 align:start position:0% speaking about our agenda will be speaking<00:00:20.529> about<00:00:20.710> hopper<00:00:21.189> which<00:00:21.580> is<00:00:21.700> an 00:00:21.900 --> 00:00:21.910 align:start position:0% speaking about hopper which is an 00:00:21.910 --> 00:00:24.359 align:start position:0% speaking about hopper which is an open-source<00:00:22.360> privacy<00:00:23.050> research<00:00:23.380> that<00:00:24.009> we<00:00:24.160> did 00:00:24.359 --> 00:00:24.369 align:start position:0% open-source privacy research that we did 00:00:24.369 --> 00:00:28.170 align:start position:0% open-source privacy research that we did develop<00:00:24.660> early<00:00:26.130> actually<00:00:27.130> this<00:00:27.460> most<00:00:27.970> of<00:00:28.090> this 00:00:28.170 --> 00:00:28.180 align:start position:0% develop early actually this most of this 00:00:28.180 --> 00:00:29.939 align:start position:0% develop early actually this most of this work<00:00:28.359> was<00:00:28.570> done<00:00:28.630> by<00:00:28.810> believe<00:00:29.320> and<00:00:29.500> big<00:00:29.740> enough 00:00:29.939 --> 00:00:29.949 align:start position:0% work was done by believe and big enough 00:00:29.949 --> 00:00:39.380 align:start position:0% work was done by believe and big enough community<00:00:30.340> this<00:00:31.270> is<00:00:31.420> going<00:00:31.630> to<00:00:31.720> be 00:00:39.380 --> 00:00:39.390 align:start position:0% 00:00:39.390 --> 00:00:59.340 align:start position:0% today<00:00:40.350> I'm<00:00:40.410> going<00:00:40.530> to<00:00:40.590> blow<00:00:40.770> my<00:00:40.800> face 00:00:59.340 --> 00:00:59.350 align:start position:0% 00:00:59.350 --> 00:01:02.080 align:start position:0% so<00:01:00.350> that<00:01:00.530> should<00:01:00.740> be<00:01:00.860> better<00:01:01.010> so<00:01:01.700> I<00:01:01.730> was<00:01:01.910> saying 00:01:02.080 --> 00:01:02.090 align:start position:0% so that should be better so I was saying 00:01:02.090 --> 00:01:03.460 align:start position:0% so that should be better so I was saying we're<00:01:02.360> going<00:01:02.450> to<00:01:02.540> be<00:01:02.600> speaking<00:01:02.810> about<00:01:03.020> Arjun 00:01:03.460 --> 00:01:03.470 align:start position:0% we're going to be speaking about Arjun 00:01:03.470 --> 00:01:06.760 align:start position:0% we're going to be speaking about Arjun but<00:01:03.650> about<00:01:03.860> copper<00:01:04.390> which<00:01:05.390> is<00:01:05.420> what<00:01:05.900> was<00:01:06.380> most 00:01:06.760 --> 00:01:06.770 align:start position:0% but about copper which is what was most 00:01:06.770 --> 00:01:09.190 align:start position:0% but about copper which is what was most innovative<00:01:07.430> and<00:01:07.550> irregular<00:01:08.030> proteins<00:01:08.780> of<00:01:09.080> the 00:01:09.190 --> 00:01:09.200 align:start position:0% innovative and irregular proteins of the 00:01:09.200 --> 00:01:11.290 align:start position:0% innovative and irregular proteins of the credit<00:01:09.500> goes<00:01:09.680> to<00:01:09.860> him<00:01:10.100> and<00:01:10.700> if<00:01:10.820> you<00:01:11.000> have<00:01:11.090> any 00:01:11.290 --> 00:01:11.300 align:start position:0% credit goes to him and if you have any 00:01:11.300 --> 00:01:12.940 align:start position:0% credit goes to him and if you have any deep<00:01:11.540> technical<00:01:11.900> question<00:01:12.440> you<00:01:12.560> should<00:01:12.590> also 00:01:12.940 --> 00:01:12.950 align:start position:0% deep technical question you should also 00:01:12.950 --> 00:01:17.860 align:start position:0% deep technical question you should also ask<00:01:13.640> em<00:01:13.970> to<00:01:14.180> it<00:01:14.210> on<00:01:14.900> Twitter<00:01:16.420> so<00:01:17.420> I<00:01:17.450> just<00:01:17.780> said 00:01:17.860 --> 00:01:17.870 align:start position:0% ask em to it on Twitter so I just said 00:01:17.870 --> 00:01:19.330 align:start position:0% ask em to it on Twitter so I just said I'm<00:01:17.960> going<00:01:18.200> to<00:01:18.290> be<00:01:18.350> speaking<00:01:18.560> about<00:01:18.770> logic<00:01:19.160> but 00:01:19.330 --> 00:01:19.340 align:start position:0% I'm going to be speaking about logic but 00:01:19.340 --> 00:01:21.850 align:start position:0% I'm going to be speaking about logic but I<00:01:19.400> think<00:01:19.640> there<00:01:19.760> is<00:01:19.820> some<00:01:20.030> value<00:01:20.060> in<00:01:20.860> briefly 00:01:21.850 --> 00:01:21.860 align:start position:0% I think there is some value in briefly 00:01:21.860 --> 00:01:23.560 align:start position:0% I think there is some value in briefly describing<00:01:22.340> what<00:01:22.580> logic<00:01:22.729> is<00:01:23.030> because<00:01:23.420> it 00:01:23.560 --> 00:01:23.570 align:start position:0% describing what logic is because it 00:01:23.570 --> 00:01:25.210 align:start position:0% describing what logic is because it gives<00:01:23.750> some<00:01:23.900> context<00:01:24.350> of<00:01:24.560> why<00:01:24.710> we<00:01:24.890> started 00:01:25.210 --> 00:01:25.220 align:start position:0% gives some context of why we started 00:01:25.220 --> 00:01:27.310 align:start position:0% gives some context of why we started working<00:01:25.400> on<00:01:25.910> the<00:01:26.300> privacy<00:01:26.630> it<00:01:26.870> sir 00:01:27.310 --> 00:01:27.320 align:start position:0% working on the privacy it sir 00:01:27.320 --> 00:01:29.200 align:start position:0% working on the privacy it sir so<00:01:27.740> Arjun<00:01:28.070> is<00:01:28.190> the<00:01:28.250> smart<00:01:28.520> contract<00:01:28.670> base<00:01:29.000> what 00:01:29.200 --> 00:01:29.210 align:start position:0% so Arjun is the smart contract base what 00:01:29.210 --> 00:01:31.900 align:start position:0% so Arjun is the smart contract base what else<00:01:29.440> we<00:01:30.440> a<00:01:30.470> lot<00:01:30.620> of<00:01:30.710> cool<00:01:30.950> features<00:01:30.979> we<00:01:31.880> have 00:01:31.900 --> 00:01:31.910 align:start position:0% else we a lot of cool features we have 00:01:31.910 --> 00:01:34.210 align:start position:0% else we a lot of cool features we have seen<00:01:32.240> this<00:01:32.360> recovery<00:01:32.720> you<00:01:33.560> can<00:01:33.710> block<00:01:33.920> for<00:01:33.950> the 00:01:34.210 --> 00:01:34.220 align:start position:0% seen this recovery you can block for the 00:01:34.220 --> 00:01:36.400 align:start position:0% seen this recovery you can block for the transaction<00:01:34.940> you<00:01:35.210> can<00:01:35.240> freeze<00:01:35.690> your<00:01:35.810> account 00:01:36.400 --> 00:01:36.410 align:start position:0% transaction you can freeze your account 00:01:36.410 --> 00:01:38.560 align:start position:0% transaction you can freeze your account there's<00:01:36.950> no<00:01:37.160> obstruction<00:01:38.030> of<00:01:38.119> gas<00:01:38.300> or<00:01:38.540> the 00:01:38.560 --> 00:01:38.570 align:start position:0% there's no obstruction of gas or the 00:01:38.570 --> 00:01:40.660 align:start position:0% there's no obstruction of gas or the transaction<00:01:38.930> fees<00:01:39.320> and<00:01:39.680> we<00:01:39.740> used<00:01:39.890> as<00:01:40.100> an<00:01:40.220> ESS 00:01:40.660 --> 00:01:40.670 align:start position:0% transaction fees and we used as an ESS 00:01:40.670 --> 00:01:43.570 align:start position:0% transaction fees and we used as an ESS all<00:01:40.880> so<00:01:41.600> so<00:01:41.810> basically<00:01:41.930> what<00:01:42.320> we<00:01:42.440> try<00:01:42.619> to<00:01:42.650> do<00:01:42.950> is 00:01:43.570 --> 00:01:43.580 align:start position:0% all so so basically what we try to do is 00:01:43.580 --> 00:01:45.219 align:start position:0% all so so basically what we try to do is abstract<00:01:44.030> most<00:01:44.330> of<00:01:44.450> the<00:01:44.540> complexity<00:01:45.080> of<00:01:45.110> the 00:01:45.219 --> 00:01:45.229 align:start position:0% abstract most of the complexity of the 00:01:45.229 --> 00:01:47.260 align:start position:0% abstract most of the complexity of the blockchain<00:01:45.440> and<00:01:46.130> enable<00:01:46.580> an<00:01:46.670> experience 00:01:47.260 --> 00:01:47.270 align:start position:0% blockchain and enable an experience 00:01:47.270 --> 00:01:49.660 align:start position:0% blockchain and enable an experience similar<00:01:48.020> to<00:01:48.500> once<00:01:48.800> again<00:01:49.040> on<00:01:49.130> the<00:01:49.220> best<00:01:49.430> mobile 00:01:49.660 --> 00:01:49.670 align:start position:0% similar to once again on the best mobile 00:01:49.670 --> 00:01:52.270 align:start position:0% similar to once again on the best mobile banking<00:01:50.119> application<00:01:50.390> today<00:01:51.050> but<00:01:51.619> in<00:01:51.890> a<00:01:52.040> fully 00:01:52.270 --> 00:01:52.280 align:start position:0% banking application today but in a fully 00:01:52.280 --> 00:01:57.969 align:start position:0% banking application today but in a fully no<00:01:52.490> mr.<00:01:52.820> Devaney<00:01:53.180> and<00:01:55.840> the<00:01:56.840> vision<00:01:57.740> for<00:01:57.920> that 00:01:57.969 --> 00:01:57.979 align:start position:0% no mr. Devaney and the vision for that 00:01:57.979 --> 00:02:00.190 align:start position:0% no mr. Devaney and the vision for that is<00:01:58.220> that<00:01:58.369> we<00:01:58.520> wanna<00:01:58.700> enable<00:01:59.050> actually<00:02:00.050> people 00:02:00.190 --> 00:02:00.200 align:start position:0% is that we wanna enable actually people 00:02:00.200 --> 00:02:02.000 align:start position:0% is that we wanna enable actually people which<00:02:00.530> are<00:02:00.680> outside 00:02:02.000 --> 00:02:02.010 align:start position:0% which are outside 00:02:02.010 --> 00:02:05.120 align:start position:0% which are outside to<00:02:02.490> access<00:02:02.640> the<00:02:02.970> blockchain<00:02:03.210> and<00:02:03.710> so<00:02:04.710> just<00:02:04.920> it 00:02:05.120 --> 00:02:05.130 align:start position:0% to access the blockchain and so just it 00:02:05.130 --> 00:02:07.580 align:start position:0% to access the blockchain and so just it is<00:02:05.280> not<00:02:05.460> to<00:02:05.610> build<00:02:05.820> our<00:02:06.570> you<00:02:06.720> financial<00:02:07.230> system 00:02:07.580 --> 00:02:07.590 align:start position:0% is not to build our you financial system 00:02:07.590 --> 00:02:09.350 align:start position:0% is not to build our you financial system for<00:02:07.770> people<00:02:07.890> that<00:02:08.220> actually<00:02:08.460> I'm<00:02:09.060> not<00:02:09.210> really 00:02:09.350 --> 00:02:09.360 align:start position:0% for people that actually I'm not really 00:02:09.360 --> 00:02:10.700 align:start position:0% for people that actually I'm not really tech<00:02:09.750> savvy<00:02:09.780> there's<00:02:10.320> some<00:02:10.500> kind<00:02:10.650> of 00:02:10.700 --> 00:02:10.710 align:start position:0% tech savvy there's some kind of 00:02:10.710 --> 00:02:13.370 align:start position:0% tech savvy there's some kind of expectation<00:02:11.430> of<00:02:11.850> what<00:02:12.360> that<00:02:12.480> system<00:02:12.720> or<00:02:13.260> the 00:02:13.370 --> 00:02:13.380 align:start position:0% expectation of what that system or the 00:02:13.380 --> 00:02:15.100 align:start position:0% expectation of what that system or the feature<00:02:13.590> that<00:02:13.860> that<00:02:14.070> system<00:02:14.460> should<00:02:14.490> provide 00:02:15.100 --> 00:02:15.110 align:start position:0% feature that that system should provide 00:02:15.110 --> 00:02:18.920 align:start position:0% feature that that system should provide for<00:02:16.110> example<00:02:16.200> people<00:02:16.980> assume<00:02:17.310> that<00:02:17.550> if<00:02:17.930> you 00:02:18.920 --> 00:02:18.930 align:start position:0% for example people assume that if you 00:02:18.930 --> 00:02:21.350 align:start position:0% for example people assume that if you transact<00:02:19.490> that<00:02:20.490> doesn't<00:02:20.790> give<00:02:20.910> the<00:02:21.030> person 00:02:21.350 --> 00:02:21.360 align:start position:0% transact that doesn't give the person 00:02:21.360 --> 00:02:23.000 align:start position:0% transact that doesn't give the person who<00:02:21.390> transacting<00:02:21.990> with<00:02:22.020> access<00:02:22.800> to<00:02:22.920> your 00:02:23.000 --> 00:02:23.010 align:start position:0% who transacting with access to your 00:02:23.010 --> 00:02:26.090 align:start position:0% who transacting with access to your theory<00:02:23.250> for<00:02:23.850> example<00:02:24.480> I<00:02:25.080> mean<00:02:25.290> future<00:02:25.710> Runge's 00:02:26.090 --> 00:02:26.100 align:start position:0% theory for example I mean future Runge's 00:02:26.100 --> 00:02:28.730 align:start position:0% theory for example I mean future Runge's making<00:02:26.940> a<00:02:27.000> transaction<00:02:27.390> to<00:02:27.660> my<00:02:27.930> insurer<00:02:28.380> I 00:02:28.730 --> 00:02:28.740 align:start position:0% making a transaction to my insurer I 00:02:28.740 --> 00:02:31.460 align:start position:0% making a transaction to my insurer I mean<00:02:29.310> not<00:02:29.700> P<00:02:29.940> okay<00:02:30.210> for<00:02:30.480> my<00:02:30.570> church<00:02:30.840> that<00:02:31.200> I 00:02:31.460 --> 00:02:31.470 align:start position:0% mean not P okay for my church that I 00:02:31.470 --> 00:02:33.230 align:start position:0% mean not P okay for my church that I just<00:02:31.680> visited<00:02:32.070> an<00:02:32.190> oncologist<00:02:32.640> two<00:02:32.820> weeks<00:02:33.000> ago 00:02:33.230 --> 00:02:33.240 align:start position:0% just visited an oncologist two weeks ago 00:02:33.240 --> 00:02:35.570 align:start position:0% just visited an oncologist two weeks ago this<00:02:33.720> kind<00:02:33.960> of<00:02:33.990> information<00:02:34.680> should<00:02:34.950> not<00:02:35.370> be 00:02:35.570 --> 00:02:35.580 align:start position:0% this kind of information should not be 00:02:35.580 --> 00:02:36.980 align:start position:0% this kind of information should not be disclosed<00:02:35.970> that<00:02:36.150> should<00:02:36.300> be<00:02:36.420> private<00:02:36.600> of 00:02:36.980 --> 00:02:36.990 align:start position:0% disclosed that should be private of 00:02:36.990 --> 00:02:38.900 align:start position:0% disclosed that should be private of course<00:02:37.200> a<00:02:37.410> material<00:02:37.920> which<00:02:38.280> is<00:02:38.310> a<00:02:38.460> public 00:02:38.900 --> 00:02:38.910 align:start position:0% course a material which is a public 00:02:38.910 --> 00:02:41.150 align:start position:0% course a material which is a public nature<00:02:39.150> with<00:02:39.840> full<00:02:40.110> transparency<00:02:40.380> you<00:02:40.830> donate 00:02:41.150 --> 00:02:41.160 align:start position:0% nature with full transparency you donate 00:02:41.160 --> 00:02:44.120 align:start position:0% nature with full transparency you donate these<00:02:41.340> properties<00:02:42.260> this<00:02:43.260> also<00:02:43.560> economical 00:02:44.120 --> 00:02:44.130 align:start position:0% these properties this also economical 00:02:44.130 --> 00:02:47.000 align:start position:0% these properties this also economical argument<00:02:44.580> for<00:02:45.140> privacy<00:02:46.140> is<00:02:46.530> the<00:02:46.560> fact<00:02:46.950> that 00:02:47.000 --> 00:02:47.010 align:start position:0% argument for privacy is the fact that 00:02:47.010 --> 00:02:49.100 align:start position:0% argument for privacy is the fact that you<00:02:47.280> money<00:02:47.490> or<00:02:47.580> token<00:02:48.000> to<00:02:48.210> be<00:02:48.360> fungible<00:02:48.840> if<00:02:48.960> I 00:02:49.100 --> 00:02:49.110 align:start position:0% you money or token to be fungible if I 00:02:49.110 --> 00:02:51.350 align:start position:0% you money or token to be fungible if I send<00:02:49.380> you<00:02:49.470> one<00:02:49.650> eater<00:02:49.920> you<00:02:50.610> want<00:02:50.850> that<00:02:51.090> eater 00:02:51.350 --> 00:02:51.360 align:start position:0% send you one eater you want that eater 00:02:51.360 --> 00:02:53.870 align:start position:0% send you one eater you want that eater to<00:02:51.690> be<00:02:51.810> worth<00:02:52.020> one<00:02:52.350> either<00:02:52.590> now<00:02:53.430> if<00:02:53.580> you<00:02:53.730> know 00:02:53.870 --> 00:02:53.880 align:start position:0% to be worth one either now if you know 00:02:53.880 --> 00:02:55.340 align:start position:0% to be worth one either now if you know where<00:02:54.120> that<00:02:54.150> either<00:02:54.540> comes<00:02:54.900> from<00:02:55.140> actually 00:02:55.340 --> 00:02:55.350 align:start position:0% where that either comes from actually 00:02:55.350 --> 00:02:57.260 align:start position:0% where that either comes from actually you<00:02:56.070> will<00:02:56.190> believe<00:02:56.490> that<00:02:56.670> it<00:02:56.790> has<00:02:56.910> this<00:02:57.060> value 00:02:57.260 --> 00:02:57.270 align:start position:0% you will believe that it has this value 00:02:57.270 --> 00:02:59.480 align:start position:0% you will believe that it has this value because<00:02:57.840> it<00:02:57.960> can<00:02:58.110> be<00:02:58.230> tainted<00:02:58.440> for<00:02:58.980> example<00:02:59.400> it 00:02:59.480 --> 00:02:59.490 align:start position:0% because it can be tainted for example it 00:02:59.490 --> 00:03:02.540 align:start position:0% because it can be tainted for example it comes<00:02:59.730> from<00:02:59.940> an<00:03:00.330> exchanging<00:03:01.080> act<00:03:01.350> that<00:03:02.040> token 00:03:02.540 --> 00:03:02.550 align:start position:0% comes from an exchanging act that token 00:03:02.550 --> 00:03:04.730 align:start position:0% comes from an exchanging act that token may<00:03:02.700> be<00:03:02.760> worse<00:03:03.090> miss<00:03:03.450> they're<00:03:04.230> actually<00:03:04.560> one 00:03:04.730 --> 00:03:04.740 align:start position:0% may be worse miss they're actually one 00:03:04.740 --> 00:03:05.330 align:start position:0% may be worse miss they're actually one either 00:03:05.330 --> 00:03:05.340 align:start position:0% either 00:03:05.340 --> 00:03:07.250 align:start position:0% either so<00:03:05.730> these<00:03:05.880> properties<00:03:06.390> are<00:03:06.420> very<00:03:06.750> important 00:03:07.250 --> 00:03:07.260 align:start position:0% so these properties are very important 00:03:07.260 --> 00:03:10.220 align:start position:0% so these properties are very important so<00:03:08.100> if<00:03:08.130> you<00:03:08.310> want<00:03:08.490> to<00:03:08.550> be<00:03:08.670> inspirational<00:03:09.230> you 00:03:10.220 --> 00:03:10.230 align:start position:0% so if you want to be inspirational you 00:03:10.230 --> 00:03:12.050 align:start position:0% so if you want to be inspirational you can<00:03:10.440> say<00:03:10.590> that<00:03:10.740> privacy<00:03:11.100> is<00:03:11.220> necessary<00:03:11.820> for<00:03:12.000> an 00:03:12.050 --> 00:03:12.060 align:start position:0% can say that privacy is necessary for an 00:03:12.060 --> 00:03:14.960 align:start position:0% can say that privacy is necessary for an open<00:03:12.360> society<00:03:12.510> in<00:03:13.440> the<00:03:13.590> electronic<00:03:14.010> age<00:03:14.190> if 00:03:14.960 --> 00:03:14.970 align:start position:0% open society in the electronic age if 00:03:14.970 --> 00:03:16.910 align:start position:0% open society in the electronic age if you're<00:03:15.150> a<00:03:15.209> bit<00:03:15.420> more<00:03:15.450> pragmatic<00:03:15.959> we<00:03:16.560> actually 00:03:16.910 --> 00:03:16.920 align:start position:0% you're a bit more pragmatic we actually 00:03:16.920 --> 00:03:19.600 align:start position:0% you're a bit more pragmatic we actually allow<00:03:17.100> users<00:03:17.750> saying<00:03:18.750> that<00:03:18.989> they<00:03:19.170> were<00:03:19.230> not 00:03:19.600 --> 00:03:19.610 align:start position:0% allow users saying that they were not 00:03:19.610 --> 00:03:21.710 align:start position:0% allow users saying that they were not they<00:03:20.610> were<00:03:20.640> feeling<00:03:20.940> uncomfortable<00:03:21.540> by 00:03:21.710 --> 00:03:21.720 align:start position:0% they were feeling uncomfortable by 00:03:21.720 --> 00:03:23.720 align:start position:0% they were feeling uncomfortable by thinking<00:03:22.110> about<00:03:22.200> the<00:03:22.530> one<00:03:22.680> end<00:03:22.830> of<00:03:22.950> which<00:03:23.310> they 00:03:23.720 --> 00:03:23.730 align:start position:0% thinking about the one end of which they 00:03:23.730 --> 00:03:25.699 align:start position:0% thinking about the one end of which they had<00:03:23.820> a<00:03:23.850> lot<00:03:24.060> of<00:03:24.090> funds<00:03:24.480> with<00:03:25.230> their<00:03:25.410> hard<00:03:25.590> to 00:03:25.699 --> 00:03:25.709 align:start position:0% had a lot of funds with their hard to 00:03:25.709 --> 00:03:30.410 align:start position:0% had a lot of funds with their hard to buy<00:03:26.630> and<00:03:27.630> actually<00:03:27.959> this<00:03:28.080> is<00:03:28.410> seven<00:03:29.160> quote<00:03:29.730> is 00:03:30.410 --> 00:03:30.420 align:start position:0% buy and actually this is seven quote is 00:03:30.420 --> 00:03:35.330 align:start position:0% buy and actually this is seven quote is really<00:03:30.780> the<00:03:30.900> use<00:03:31.050> as<00:03:31.350> we<00:03:31.560> try<00:03:31.770> to<00:03:31.800> solve<00:03:34.190> so<00:03:35.190> we 00:03:35.330 --> 00:03:35.340 align:start position:0% really the use as we try to solve so we 00:03:35.340 --> 00:03:37.280 align:start position:0% really the use as we try to solve so we really<00:03:35.790> ask<00:03:35.880> a<00:03:36.090> question<00:03:36.540> can<00:03:36.570> we<00:03:36.840> actually 00:03:37.280 --> 00:03:37.290 align:start position:0% really ask a question can we actually 00:03:37.290 --> 00:03:37.990 align:start position:0% really ask a question can we actually invest 00:03:37.990 --> 00:03:38.000 align:start position:0% invest 00:03:38.000 --> 00:03:40.870 align:start position:0% invest I<00:03:38.030> use<00:03:38.600> case<00:03:38.870> a<00:03:39.230> user<00:03:39.920> wants<00:03:40.400> to<00:03:40.520> find<00:03:40.820> his 00:03:40.870 --> 00:03:40.880 align:start position:0% I use case a user wants to find his 00:03:40.880 --> 00:03:43.030 align:start position:0% I use case a user wants to find his heart<00:03:41.120> and<00:03:41.270> wallet<00:03:41.570> which<00:03:41.780> has<00:03:41.960> no<00:03:42.140> fun<00:03:42.380> and 00:03:43.030 --> 00:03:43.040 align:start position:0% heart and wallet which has no fun and 00:03:43.040 --> 00:03:45.370 align:start position:0% heart and wallet which has no fun and send<00:03:43.310> it<00:03:43.400> from<00:03:43.520> our<00:03:43.760> wallet<00:03:44.240> and<00:03:44.750> can<00:03:45.110> we<00:03:45.260> do 00:03:45.370 --> 00:03:45.380 align:start position:0% send it from our wallet and can we do 00:03:45.380 --> 00:03:48.700 align:start position:0% send it from our wallet and can we do that<00:03:45.620> search<00:03:46.430> tab<00:03:46.810> and<00:03:47.810> two<00:03:47.990> addresses<00:03:48.230> are 00:03:48.700 --> 00:03:48.710 align:start position:0% that search tab and two addresses are 00:03:48.710 --> 00:03:51.850 align:start position:0% that search tab and two addresses are between<00:03:49.690> the<00:03:50.690> process<00:03:51.140> is<00:03:51.290> pulling<00:03:51.620> on<00:03:51.740> this 00:03:51.850 --> 00:03:51.860 align:start position:0% between the process is pulling on this 00:03:51.860 --> 00:03:54.699 align:start position:0% between the process is pulling on this video<00:03:52.220> it<00:03:53.120> is<00:03:53.300> mobile<00:03:53.480> friendly<00:03:53.690> and<00:03:54.350> actually 00:03:54.699 --> 00:03:54.709 align:start position:0% video it is mobile friendly and actually 00:03:54.709 --> 00:03:56.880 align:start position:0% video it is mobile friendly and actually this<00:03:54.830> point<00:03:55.040> has<00:03:55.310> driven<00:03:55.610> developed<00:03:56.030> chosen 00:03:56.880 --> 00:03:56.890 align:start position:0% this point has driven developed chosen 00:03:56.890 --> 00:03:59.800 align:start position:0% this point has driven developed chosen to<00:03:57.890> design<00:03:58.040> Locker<00:03:58.550> and<00:03:58.850> of<00:03:59.270> course<00:03:59.510> it<00:03:59.660> has<00:03:59.780> to 00:03:59.800 --> 00:03:59.810 align:start position:0% to design Locker and of course it has to 00:03:59.810 --> 00:04:01.810 align:start position:0% to design Locker and of course it has to be<00:03:59.959> economically<00:04:00.709> viable<00:04:00.980> in<00:04:01.280> terms<00:04:01.490> of<00:04:01.610> gas 00:04:01.810 --> 00:04:01.820 align:start position:0% be economically viable in terms of gas 00:04:01.820 --> 00:04:03.640 align:start position:0% be economically viable in terms of gas if<00:04:02.030> you<00:04:02.150> transfer<00:04:02.540> one<00:04:02.720> either<00:04:02.930> but<00:04:03.320> you<00:04:03.440> click 00:04:03.640 --> 00:04:03.650 align:start position:0% if you transfer one either but you click 00:04:03.650 --> 00:04:05.680 align:start position:0% if you transfer one either but you click on<00:04:03.860> find<00:04:04.130> either<00:04:04.670> in<00:04:05.000> class<00:04:05.240> to<00:04:05.420> make<00:04:05.510> that 00:04:05.680 --> 00:04:05.690 align:start position:0% on find either in class to make that 00:04:05.690 --> 00:04:10.860 align:start position:0% on find either in class to make that transaction<00:04:06.020> happen<00:04:06.530> this<00:04:06.740> is<00:04:06.800> not<00:04:07.040> practical 00:04:10.860 --> 00:04:10.870 align:start position:0% 00:04:10.870 --> 00:04:12.970 align:start position:0% fortunately<00:04:11.870> there<00:04:12.170> are<00:04:12.200> solution<00:04:12.800> to 00:04:12.970 --> 00:04:12.980 align:start position:0% fortunately there are solution to 00:04:12.980 --> 00:04:15.190 align:start position:0% fortunately there are solution to address<00:04:13.250> that<00:04:13.370> use<00:04:13.580> case<00:04:13.850> and<00:04:14.120> as<00:04:15.080> you 00:04:15.190 --> 00:04:15.200 align:start position:0% address that use case and as you 00:04:15.200 --> 00:04:17.050 align:start position:0% address that use case and as you probably<00:04:15.380> all<00:04:15.590> know<00:04:15.620> ZJ<00:04:16.040> snarks<00:04:16.370> can<00:04:16.579> be<00:04:16.760> quite 00:04:17.050 --> 00:04:17.060 align:start position:0% probably all know ZJ snarks can be quite 00:04:17.060 --> 00:04:19.840 align:start position:0% probably all know ZJ snarks can be quite useful<00:04:17.269> for<00:04:17.510> that<00:04:18.250> we<00:04:19.250> didn't<00:04:19.489> start<00:04:19.669> from 00:04:19.840 --> 00:04:19.850 align:start position:0% useful for that we didn't start from 00:04:19.850 --> 00:04:21.310 align:start position:0% useful for that we didn't start from scratch<00:04:20.030> so<00:04:20.450> we<00:04:20.570> should<00:04:20.720> also<00:04:20.870> give<00:04:21.140> some 00:04:21.310 --> 00:04:21.320 align:start position:0% scratch so we should also give some 00:04:21.320 --> 00:04:23.200 align:start position:0% scratch so we should also give some credit<00:04:21.650> to<00:04:21.680> the<00:04:21.890> team<00:04:22.070> of<00:04:22.310> very<00:04:22.550> white<00:04:22.790> line<00:04:23.000> in 00:04:23.200 --> 00:04:23.210 align:start position:0% credit to the team of very white line in 00:04:23.210 --> 00:04:24.970 align:start position:0% credit to the team of very white line in which<00:04:23.390> a<00:04:23.570> that<00:04:23.750> was<00:04:23.900> a<00:04:23.930> little<00:04:24.080> bit<00:04:24.500> earlier 00:04:24.970 --> 00:04:24.980 align:start position:0% which a that was a little bit earlier 00:04:24.980 --> 00:04:26.950 align:start position:0% which a that was a little bit earlier that<00:04:25.280> done<00:04:25.820> a<00:04:25.850> great<00:04:26.090> work<00:04:26.270> and<00:04:26.480> it's<00:04:26.600> not<00:04:26.750> miss 00:04:26.950 --> 00:04:26.960 align:start position:0% that done a great work and it's not miss 00:04:26.960 --> 00:04:28.900 align:start position:0% that done a great work and it's not miss amiss<00:04:27.230> and<00:04:27.410> now<00:04:27.530> semaphore<00:04:28.070> and<00:04:28.490> so<00:04:28.790> which 00:04:28.900 --> 00:04:28.910 align:start position:0% amiss and now semaphore and so which 00:04:28.910 --> 00:04:31.180 align:start position:0% amiss and now semaphore and so which what<00:04:29.300> basically<00:04:29.720> we<00:04:29.930> we're<00:04:30.530> trying<00:04:30.740> to<00:04:30.830> extend 00:04:31.180 --> 00:04:31.190 align:start position:0% what basically we we're trying to extend 00:04:31.190 --> 00:04:33.670 align:start position:0% what basically we we're trying to extend what<00:04:31.790> they<00:04:32.000> are<00:04:32.090> at<00:04:32.360> dump<00:04:32.630> it<00:04:32.930> on<00:04:33.110> top<00:04:33.350> of<00:04:33.530> what 00:04:33.670 --> 00:04:33.680 align:start position:0% what they are at dump it on top of what 00:04:33.680 --> 00:04:35.500 align:start position:0% what they are at dump it on top of what they're<00:04:33.830> done<00:04:34.100> but<00:04:34.370> really<00:04:34.640> customize<00:04:35.150> it<00:04:35.390> and 00:04:35.500 --> 00:04:35.510 align:start position:0% they're done but really customize it and 00:04:35.510 --> 00:04:37.870 align:start position:0% they're done but really customize it and make<00:04:35.600> it<00:04:36.350> practical<00:04:36.980> for<00:04:37.010> our<00:04:37.370> target<00:04:37.580> new 00:04:37.870 --> 00:04:37.880 align:start position:0% make it practical for our target new 00:04:37.880 --> 00:04:40.930 align:start position:0% make it practical for our target new skills<00:04:38.180> so<00:04:38.740> others<00:04:39.740> upper<00:04:40.130> or<00:04:40.400> be<00:04:40.610> serious 00:04:40.930 --> 00:04:40.940 align:start position:0% skills so others upper or be serious 00:04:40.940 --> 00:04:43.180 align:start position:0% skills so others upper or be serious words<00:04:41.210> it's<00:04:42.020> that<00:04:42.169> basically<00:04:42.530> if<00:04:42.740> I<00:04:42.830> want<00:04:43.070> to 00:04:43.180 --> 00:04:43.190 align:start position:0% words it's that basically if I want to 00:04:43.190 --> 00:04:46.300 align:start position:0% words it's that basically if I want to send<00:04:43.460> an<00:04:43.580> aunt<00:04:43.790> to<00:04:44.060> someone<00:04:44.570> I<00:04:44.810> will<00:04:45.320> a<00:04:45.860> secret 00:04:46.300 --> 00:04:46.310 align:start position:0% send an aunt to someone I will a secret 00:04:46.310 --> 00:04:48.610 align:start position:0% send an aunt to someone I will a secret which<00:04:47.150> is<00:04:47.180> a<00:04:47.330> leaf<00:04:47.600> in<00:04:47.780> a<00:04:47.840> vertical<00:04:48.080> three<00:04:48.380> and 00:04:48.610 --> 00:04:48.620 align:start position:0% which is a leaf in a vertical three and 00:04:48.620 --> 00:04:50.860 align:start position:0% which is a leaf in a vertical three and the<00:04:49.460> person<00:04:49.850> that<00:04:50.030> wants<00:04:50.330> to<00:04:50.360> reach<00:04:50.600> for<00:04:50.840> that 00:04:50.860 --> 00:04:50.870 align:start position:0% the person that wants to reach for that 00:04:50.870 --> 00:04:53.110 align:start position:0% the person that wants to reach for that town<00:04:51.290> needs<00:04:52.010> to<00:04:52.190> prove<00:04:52.430> that<00:04:52.610> it<00:04:52.760> knows<00:04:52.940> the 00:04:53.110 --> 00:04:53.120 align:start position:0% town needs to prove that it knows the 00:04:53.120 --> 00:04:55.330 align:start position:0% town needs to prove that it knows the secret<00:04:53.570> behind<00:04:53.780> one<00:04:54.080> of<00:04:54.110> the<00:04:54.320> count<00:04:54.560> and<00:04:54.830> then 00:04:55.330 --> 00:04:55.340 align:start position:0% secret behind one of the count and then 00:04:55.340 --> 00:04:59.500 align:start position:0% secret behind one of the count and then this<00:04:55.490> common<00:04:55.880> hasn't<00:04:56.210> been<00:04:56.330> spent<00:04:56.630> yet<00:04:58.240> so<00:04:59.240> the 00:04:59.500 --> 00:04:59.510 align:start position:0% this common hasn't been spent yet so the 00:04:59.510 --> 00:05:02.100 align:start position:0% this common hasn't been spent yet so the principle<00:05:00.440> is<00:05:00.530> is<00:05:00.800> quite<00:05:01.070> simple 00:05:02.100 --> 00:05:02.110 align:start position:0% principle is is quite simple 00:05:02.110 --> 00:05:05.080 align:start position:0% principle is is quite simple in<00:05:03.110> practice<00:05:03.590> always<00:05:03.979> water<00:05:04.160> work<00:05:04.490> because<00:05:04.940> we 00:05:05.080 --> 00:05:05.090 align:start position:0% in practice always water work because we 00:05:05.090 --> 00:05:07.420 align:start position:0% in practice always water work because we do<00:05:05.240> have<00:05:05.360> an<00:05:05.840> iOS<00:05:06.200> application<00:05:06.530> that<00:05:07.100> you<00:05:07.250> guys 00:05:07.420 --> 00:05:07.430 align:start position:0% do have an iOS application that you guys 00:05:07.430 --> 00:05:10.900 align:start position:0% do have an iOS application that you guys should<00:05:07.610> try<00:05:08.650> which<00:05:09.650> is<00:05:09.680> in<00:05:09.890> alpha<00:05:10.220> now<00:05:10.370> but<00:05:10.700> it 00:05:10.900 --> 00:05:10.910 align:start position:0% should try which is in alpha now but it 00:05:10.910 --> 00:05:13.480 align:start position:0% should try which is in alpha now but it exists<00:05:11.540> it's<00:05:12.140> a<00:05:12.260> good<00:05:12.470> way<00:05:12.590> to<00:05:12.650> see<00:05:13.220> what<00:05:13.250> it 00:05:13.480 --> 00:05:13.490 align:start position:0% exists it's a good way to see what it 00:05:13.490 --> 00:05:13.930 align:start position:0% exists it's a good way to see what it does 00:05:13.930 --> 00:05:13.940 align:start position:0% does 00:05:13.940 --> 00:05:16.540 align:start position:0% does so<00:05:14.630> basically<00:05:14.960> the<00:05:15.169> client<00:05:15.380> using<00:05:16.160> the<00:05:16.310> the 00:05:16.540 --> 00:05:16.550 align:start position:0% so basically the client using the the 00:05:16.550 --> 00:05:18.430 align:start position:0% so basically the client using the the opera<00:05:16.850> application<00:05:17.419> will<00:05:17.960> generate<00:05:18.290> the 00:05:18.430 --> 00:05:18.440 align:start position:0% opera application will generate the 00:05:18.440 --> 00:05:21.250 align:start position:0% opera application will generate the leaves<00:05:18.620> so<00:05:18.860> we<00:05:18.979> just<00:05:19.160> do<00:05:19.340> a<00:05:19.370> char<00:05:19.760> 250c<00:05:20.390> of<00:05:21.140> a 00:05:21.250 --> 00:05:21.260 align:start position:0% leaves so we just do a char 250c of a 00:05:21.260 --> 00:05:24.060 align:start position:0% leaves so we just do a char 250c of a secret<00:05:21.680> and<00:05:21.919> the<00:05:22.070> destination<00:05:22.430> reference 00:05:24.060 --> 00:05:24.070 align:start position:0% secret and the destination reference 00:05:24.070 --> 00:05:26.380 align:start position:0% secret and the destination reference using<00:05:25.070> your<00:05:25.370> hardware<00:05:25.669> model<00:05:26.000> to<00:05:26.210> make<00:05:26.330> a 00:05:26.380 --> 00:05:26.390 align:start position:0% using your hardware model to make a 00:05:26.390 --> 00:05:28.630 align:start position:0% using your hardware model to make a deposit<00:05:26.750> to<00:05:27.050> the<00:05:27.169> mixer<00:05:27.470> contract<00:05:27.950> and<00:05:28.250> you 00:05:28.630 --> 00:05:28.640 align:start position:0% deposit to the mixer contract and you 00:05:28.640 --> 00:05:33.580 align:start position:0% deposit to the mixer contract and you attach<00:05:29.360> as<00:05:29.600> a<00:05:29.810> family 00:05:33.580 --> 00:05:33.590 align:start position:0% 00:05:33.590 --> 00:05:36.040 align:start position:0% of<00:05:34.160> course<00:05:34.400> other<00:05:34.820> people<00:05:35.300> will<00:05:35.480> do<00:05:35.660> the<00:05:35.810> same 00:05:36.040 --> 00:05:36.050 align:start position:0% of course other people will do the same 00:05:36.050 --> 00:05:38.110 align:start position:0% of course other people will do the same and<00:05:36.350> each<00:05:36.620> transfer<00:05:37.130> is<00:05:37.220> of<00:05:37.340> identical<00:05:37.730> value 00:05:38.110 --> 00:05:38.120 align:start position:0% and each transfer is of identical value 00:05:38.120 --> 00:05:41.530 align:start position:0% and each transfer is of identical value as<00:05:38.360> you<00:05:38.480> will<00:05:38.600> see<00:05:38.780> this<00:05:38.900> is<00:05:39.160> critical<00:05:40.160> and<00:05:40.730> I'm 00:05:41.530 --> 00:05:41.540 align:start position:0% as you will see this is critical and I'm 00:05:41.540 --> 00:05:43.390 align:start position:0% as you will see this is critical and I'm reserved<00:05:41.870> basically<00:05:42.350> in<00:05:42.440> a<00:05:42.530> sea<00:05:42.740> of<00:05:42.770> identical 00:05:43.390 --> 00:05:43.400 align:start position:0% reserved basically in a sea of identical 00:05:43.400 --> 00:05:48.220 align:start position:0% reserved basically in a sea of identical transfer<00:05:45.700> of<00:05:46.700> course<00:05:46.940> the<00:05:47.060> motivate<00:05:47.570> the<00:05:48.050> more 00:05:48.220 --> 00:05:48.230 align:start position:0% transfer of course the motivate the more 00:05:48.230 --> 00:05:50.710 align:start position:0% transfer of course the motivate the more people<00:05:48.440> will<00:05:48.740> deposit<00:05:49.100> either<00:05:49.940> of<00:05:50.300> the<00:05:50.419> mixer 00:05:50.710 --> 00:05:50.720 align:start position:0% people will deposit either of the mixer 00:05:50.720 --> 00:05:52.780 align:start position:0% people will deposit either of the mixer contract<00:05:51.139> and<00:05:51.380> the<00:05:51.560> more<00:05:51.770> you'll<00:05:52.010> need<00:05:52.370> et<00:05:52.460> set 00:05:52.780 --> 00:05:52.790 align:start position:0% contract and the more you'll need et set 00:05:52.790 --> 00:05:54.970 align:start position:0% contract and the more you'll need et set increases<00:05:53.090> I<00:05:53.600> put<00:05:54.169> in<00:05:54.260> a<00:05:54.350> stir<00:05:54.530> it's<00:05:54.650> because 00:05:54.970 --> 00:05:54.980 align:start position:0% increases I put in a stir it's because 00:05:54.980 --> 00:05:56.560 align:start position:0% increases I put in a stir it's because it<00:05:55.130> is<00:05:55.220> not<00:05:55.400> as<00:05:55.490> simple<00:05:55.700> as<00:05:55.970> that<00:05:56.180> but<00:05:56.419> it 00:05:56.560 --> 00:05:56.570 align:start position:0% it is not as simple as that but it 00:05:56.570 --> 00:06:00.990 align:start position:0% it is not as simple as that but it provides<00:05:56.960> me<00:05:57.110> the<00:05:57.320> intuition<00:05:58.130> are<00:05:58.280> we<00:05:58.880> getting 00:06:00.990 --> 00:06:01.000 align:start position:0% provides me the intuition are we getting 00:06:01.000 --> 00:06:03.430 align:start position:0% provides me the intuition are we getting finally<00:06:02.000> after<00:06:02.120> a<00:06:02.300> certain<00:06:02.510> time<00:06:02.690> the<00:06:03.020> person 00:06:03.430 --> 00:06:03.440 align:start position:0% finally after a certain time the person 00:06:03.440 --> 00:06:06.129 align:start position:0% finally after a certain time the person wants<00:06:03.710> to<00:06:03.740> be<00:06:03.980> true<00:06:04.190> the<00:06:04.790> comment<00:06:05.180> again<00:06:05.780> using 00:06:06.129 --> 00:06:06.139 align:start position:0% wants to be true the comment again using 00:06:06.139 --> 00:06:08.710 align:start position:0% wants to be true the comment again using the<00:06:06.260> Opera<00:06:06.530> can<00:06:06.919> tell<00:06:07.130> the<00:06:07.250> mixer<00:06:07.639> to<00:06:08.389> send<00:06:08.630> the 00:06:08.710 --> 00:06:08.720 align:start position:0% the Opera can tell the mixer to send the 00:06:08.720 --> 00:06:10.960 align:start position:0% the Opera can tell the mixer to send the fun<00:06:08.960> to<00:06:09.080> the<00:06:09.110> destination<00:06:09.830> and<00:06:10.520> you<00:06:10.639> do<00:06:10.790> that 00:06:10.960 --> 00:06:10.970 align:start position:0% fun to the destination and you do that 00:06:10.970 --> 00:06:14.200 align:start position:0% fun to the destination and you do that by<00:06:11.180> sending<00:06:11.630> a<00:06:11.750> a<00:06:12.020> proof<00:06:12.669> the<00:06:13.669> mixer<00:06:14.000> comes 00:06:14.200 --> 00:06:14.210 align:start position:0% by sending a a proof the mixer comes 00:06:14.210 --> 00:06:15.969 align:start position:0% by sending a a proof the mixer comes back<00:06:14.389> you<00:06:14.630> verify<00:06:15.050> the<00:06:15.110> proof<00:06:15.470> and<00:06:15.740> if<00:06:15.860> the 00:06:15.969 --> 00:06:15.979 align:start position:0% back you verify the proof and if the 00:06:15.979 --> 00:06:17.710 align:start position:0% back you verify the proof and if the proof<00:06:16.190> is<00:06:16.310> correct<00:06:16.639> we'll<00:06:16.940> send<00:06:17.150> this<00:06:17.270> one<00:06:17.450> to 00:06:17.710 --> 00:06:17.720 align:start position:0% proof is correct we'll send this one to 00:06:17.720 --> 00:06:21.010 align:start position:0% proof is correct we'll send this one to the<00:06:18.169> destination<00:06:18.710> address<00:06:19.540> for<00:06:20.540> example<00:06:20.570> that 00:06:21.010 --> 00:06:21.020 align:start position:0% the destination address for example that 00:06:21.020 --> 00:06:23.469 align:start position:0% the destination address for example that might<00:06:21.169> be<00:06:21.350> that<00:06:21.530> sequence<00:06:22.030> complete<00:06:23.030> transfer 00:06:23.469 --> 00:06:23.479 align:start position:0% might be that sequence complete transfer 00:06:23.479 --> 00:06:25.870 align:start position:0% might be that sequence complete transfer and<00:06:23.840> correct<00:06:24.260> you<00:06:24.770> received<00:06:25.130> one<00:06:25.400> eternal 00:06:25.870 --> 00:06:25.880 align:start position:0% and correct you received one eternal 00:06:25.880 --> 00:06:28.900 align:start position:0% and correct you received one eternal quality<00:06:27.130> so<00:06:28.130> this<00:06:28.400> one<00:06:28.550> when<00:06:28.669> the<00:06:28.760> user 00:06:28.900 --> 00:06:28.910 align:start position:0% quality so this one when the user 00:06:28.910 --> 00:06:32.590 align:start position:0% quality so this one when the user experience<00:06:29.240> is<00:06:29.479> actually<00:06:29.570> quite<00:06:29.930> simple<00:06:31.600> know 00:06:32.590 --> 00:06:32.600 align:start position:0% experience is actually quite simple know 00:06:32.600 --> 00:06:34.900 align:start position:0% experience is actually quite simple know what<00:06:32.780> is<00:06:32.870> in<00:06:32.990> working<00:06:33.290> practice<00:06:33.710> so<00:06:34.010> not<00:06:34.520> good 00:06:34.900 --> 00:06:34.910 align:start position:0% what is in working practice so not good 00:06:34.910 --> 00:06:37.659 align:start position:0% what is in working practice so not good it<00:06:35.120> because<00:06:35.450> the<00:06:35.840> CGA<00:06:36.200> smart<00:06:36.470> framework<00:06:36.919> for 00:06:37.659 --> 00:06:37.669 align:start position:0% it because the CGA smart framework for 00:06:37.669 --> 00:06:39.730 align:start position:0% it because the CGA smart framework for mixers<00:06:38.000> but<00:06:38.240> basically<00:06:38.630> you<00:06:39.289> want<00:06:39.470> to<00:06:39.530> prove 00:06:39.730 --> 00:06:39.740 align:start position:0% mixers but basically you want to prove 00:06:39.740 --> 00:06:41.380 align:start position:0% mixers but basically you want to prove that<00:06:39.800> you<00:06:40.070> know<00:06:40.190> secret 00:06:41.380 --> 00:06:41.390 align:start position:0% that you know secret 00:06:41.390 --> 00:06:44.560 align:start position:0% that you know secret three<00:06:42.290> Weatherly<00:06:42.950> to<00:06:43.250> the<00:06:43.370> sha-256<00:06:44.330> of<00:06:44.480> the 00:06:44.560 --> 00:06:44.570 align:start position:0% three Weatherly to the sha-256 of the 00:06:44.570 --> 00:06:46.390 align:start position:0% three Weatherly to the sha-256 of the secret<00:06:44.930> in<00:06:45.050> a<00:06:45.110> destination<00:06:45.500> address<00:06:45.740> you 00:06:46.390 --> 00:06:46.400 align:start position:0% secret in a destination address you 00:06:46.400 --> 00:06:48.550 align:start position:0% secret in a destination address you wanna<00:06:46.670> prove<00:06:46.910> that<00:06:46.970> that<00:06:47.480> common<00:06:48.170> hasn't<00:06:48.470> been 00:06:48.550 --> 00:06:48.560 align:start position:0% wanna prove that that common hasn't been 00:06:48.560 --> 00:06:50.740 align:start position:0% wanna prove that that common hasn't been spent<00:06:48.890> it<00:06:49.070> so<00:06:49.760> actually<00:06:49.910> you<00:06:50.180> can<00:06:50.210> translate 00:06:50.740 --> 00:06:50.750 align:start position:0% spent it so actually you can translate 00:06:50.750 --> 00:06:54.400 align:start position:0% spent it so actually you can translate that<00:06:51.340> automatic<00:06:52.340> mathematical<00:06:53.030> equation<00:06:53.480> and 00:06:54.400 --> 00:06:54.410 align:start position:0% that automatic mathematical equation and 00:06:54.410 --> 00:06:56.890 align:start position:0% that automatic mathematical equation and that<00:06:55.340> will<00:06:55.520> give<00:06:55.730> you<00:06:55.850> circuits<00:06:56.330> so<00:06:56.660> in<00:06:56.810> your 00:06:56.890 --> 00:06:56.900 align:start position:0% that will give you circuits so in your 00:06:56.900 --> 00:06:59.440 align:start position:0% that will give you circuits so in your case<00:06:57.140> these<00:06:57.980> are<00:06:58.220> the<00:06:58.370> the<00:06:58.580> set<00:06:58.790> of<00:06:58.910> equations 00:06:59.440 --> 00:06:59.450 align:start position:0% case these are the the set of equations 00:06:59.450 --> 00:07:02.200 align:start position:0% case these are the the set of equations that<00:06:59.570> we<00:06:59.750> want<00:07:00.110> to<00:07:00.230> solve<00:07:00.640> this<00:07:01.640> is<00:07:01.850> the<00:07:01.970> secret 00:07:02.200 --> 00:07:02.210 align:start position:0% that we want to solve this is the secret 00:07:02.210 --> 00:07:04.960 align:start position:0% that we want to solve this is the secret inputs<00:07:02.660> that<00:07:03.050> we<00:07:03.230> want<00:07:03.410> to<00:07:03.560> prove<00:07:03.890> we<00:07:04.160> know<00:07:04.340> we 00:07:04.960 --> 00:07:04.970 align:start position:0% inputs that we want to prove we know we 00:07:04.970 --> 00:07:07.660 align:start position:0% inputs that we want to prove we know we don't<00:07:05.000> be<00:07:05.270> reading<00:07:05.570> them<00:07:06.370> and<00:07:07.370> of<00:07:07.640> course 00:07:07.660 --> 00:07:07.670 align:start position:0% don't be reading them and of course 00:07:07.670 --> 00:07:10.660 align:start position:0% don't be reading them and of course there<00:07:08.150> is<00:07:08.270> some<00:07:08.480> public<00:07:08.630> inputs<00:07:09.370> so<00:07:10.370> using 00:07:10.660 --> 00:07:10.670 align:start position:0% there is some public inputs so using 00:07:10.670 --> 00:07:13.120 align:start position:0% there is some public inputs so using this<00:07:10.820> you<00:07:11.180> can<00:07:11.990> actually<00:07:12.110> build<00:07:12.470> your<00:07:12.590> circle 00:07:13.120 --> 00:07:13.130 align:start position:0% this you can actually build your circle 00:07:13.130 --> 00:07:18.280 align:start position:0% this you can actually build your circle and<00:07:13.810> have<00:07:14.810> your<00:07:15.020> verify<00:07:15.620> your<00:07:16.070> approver<00:07:17.290> using 00:07:18.280 --> 00:07:18.290 align:start position:0% and have your verify your approver using 00:07:18.290 --> 00:07:21.850 align:start position:0% and have your verify your approver using a<00:07:18.320> library<00:07:18.470> such<00:07:18.830> as<00:07:19.010> that<00:07:20.260> in<00:07:21.260> terms<00:07:21.530> of<00:07:21.680> small 00:07:21.850 --> 00:07:21.860 align:start position:0% a library such as that in terms of small 00:07:21.860 --> 00:07:23.770 align:start position:0% a library such as that in terms of small contractor<00:07:22.430> small<00:07:22.610> contracts<00:07:23.000> is<00:07:23.330> quite 00:07:23.770 --> 00:07:23.780 align:start position:0% contractor small contracts is quite 00:07:23.780 --> 00:07:26.320 align:start position:0% contractor small contracts is quite simple<00:07:24.200> at<00:07:24.740> first<00:07:24.800> example<00:07:25.430> is<00:07:25.520> API<00:07:25.820> we<00:07:26.180> have 00:07:26.320 --> 00:07:26.330 align:start position:0% simple at first example is API we have 00:07:26.330 --> 00:07:28.810 align:start position:0% simple at first example is API we have two<00:07:26.630> main<00:07:26.870> method<00:07:27.290> commits<00:07:27.830> when<00:07:28.370> you<00:07:28.490> deposit 00:07:28.810 --> 00:07:28.820 align:start position:0% two main method commits when you deposit 00:07:28.820 --> 00:07:31.240 align:start position:0% two main method commits when you deposit your<00:07:29.000> funds<00:07:29.510> and<00:07:29.870> you<00:07:30.050> attach<00:07:30.620> your<00:07:30.830> leaf<00:07:31.040> as 00:07:31.240 --> 00:07:31.250 align:start position:0% your funds and you attach your leaf as 00:07:31.250 --> 00:07:34.030 align:start position:0% your funds and you attach your leaf as data<00:07:31.520> at<00:07:32.120> individual<00:07:32.720> function<00:07:33.170> where<00:07:33.950> you 00:07:34.030 --> 00:07:34.040 align:start position:0% data at individual function where you 00:07:34.040 --> 00:07:36.370 align:start position:0% data at individual function where you specify<00:07:34.250> the<00:07:34.580> cubic<00:07:35.210> input<00:07:35.540> data<00:07:35.810> so<00:07:36.140> the 00:07:36.370 --> 00:07:36.380 align:start position:0% specify the cubic input data so the 00:07:36.380 --> 00:07:40.660 align:start position:0% specify the cubic input data so the destination<00:07:37.660> only<00:07:38.660> fire<00:07:39.130> which<00:07:40.130> proves<00:07:40.520> that 00:07:40.660 --> 00:07:40.670 align:start position:0% destination only fire which proves that 00:07:40.670 --> 00:07:43.120 align:start position:0% destination only fire which proves that there's<00:07:40.940> no<00:07:41.120> double<00:07:41.450> span<00:07:41.690> and<00:07:42.050> then<00:07:42.590> you're 00:07:43.120 --> 00:07:43.130 align:start position:0% there's no double span and then you're 00:07:43.130 --> 00:07:46.030 align:start position:0% there's no double span and then you're the<00:07:43.730> proof<00:07:44.000> that<00:07:44.030> you<00:07:44.330> are<00:07:45.010> constructed<00:07:46.010> using 00:07:46.030 --> 00:07:46.040 align:start position:0% the proof that you are constructed using 00:07:46.040 --> 00:07:50.710 align:start position:0% the proof that you are constructed using the<00:07:46.520> Zika<00:07:46.820> slug<00:07:47.120> framework<00:07:49.330> so<00:07:50.330> that's<00:07:50.510> kind 00:07:50.710 --> 00:07:50.720 align:start position:0% the Zika slug framework so that's kind 00:07:50.720 --> 00:07:52.840 align:start position:0% the Zika slug framework so that's kind of<00:07:50.780> the<00:07:50.930> general<00:07:51.170> framework<00:07:51.680> as<00:07:52.190> I<00:07:52.370> mentioned 00:07:52.840 --> 00:07:52.850 align:start position:0% of the general framework as I mentioned 00:07:52.850 --> 00:07:54.790 align:start position:0% of the general framework as I mentioned we<00:07:53.180> are<00:07:53.300> similar<00:07:53.540> to<00:07:53.780> all<00:07:54.080> the<00:07:54.140> mixers<00:07:54.470> but 00:07:54.790 --> 00:07:54.800 align:start position:0% we are similar to all the mixers but 00:07:54.800 --> 00:07:56.550 align:start position:0% we are similar to all the mixers but it's<00:07:54.920> all<00:07:55.070> about<00:07:55.100> the<00:07:55.460> choices<00:07:55.790> that<00:07:55.970> you<00:07:56.270> make 00:07:56.550 --> 00:07:56.560 align:start position:0% it's all about the choices that you make 00:07:56.560 --> 00:07:58.930 align:start position:0% it's all about the choices that you make for<00:07:57.560> implementation<00:07:58.100> so<00:07:58.520> in<00:07:58.640> the<00:07:58.730> case<00:07:58.910> of 00:07:58.930 --> 00:07:58.940 align:start position:0% for implementation so in the case of 00:07:58.940 --> 00:08:01.540 align:start position:0% for implementation so in the case of hopper<00:07:59.360> we<00:07:59.750> use<00:07:59.900> Minzy<00:08:00.470> for<00:08:01.340> the<00:08:01.430> Asha 00:08:01.540 --> 00:08:01.550 align:start position:0% hopper we use Minzy for the Asha 00:08:01.550 --> 00:08:03.580 align:start position:0% hopper we use Minzy for the Asha function<00:08:02.210> of<00:08:02.480> the<00:08:02.720> work<00:08:02.900> of<00:08:03.080> three<00:08:03.290> which 00:08:03.580 --> 00:08:03.590 align:start position:0% function of the work of three which 00:08:03.590 --> 00:08:05.920 align:start position:0% function of the work of three which stands<00:08:04.130> for<00:08:04.220> minimal<00:08:04.930> multiplicative 00:08:05.920 --> 00:08:05.930 align:start position:0% stands for minimal multiplicative 00:08:05.930 --> 00:08:09.460 align:start position:0% stands for minimal multiplicative complexity<00:08:06.790> the<00:08:07.790> intuition<00:08:08.300> for<00:08:08.480> that<00:08:08.690> is 00:08:09.460 --> 00:08:09.470 align:start position:0% complexity the intuition for that is 00:08:09.470 --> 00:08:11.590 align:start position:0% complexity the intuition for that is that<00:08:09.770> in<00:08:10.040> the<00:08:10.100> Zeke<00:08:10.250> is<00:08:10.400> knox<00:08:10.640> remark<00:08:11.060> you<00:08:11.360> get 00:08:11.590 --> 00:08:11.600 align:start position:0% that in the Zeke is knox remark you get 00:08:11.600 --> 00:08:13.360 align:start position:0% that in the Zeke is knox remark you get your<00:08:11.930> equation<00:08:12.350> you<00:08:12.500> translate<00:08:12.950> that<00:08:12.980> into<00:08:13.280> a 00:08:13.360 --> 00:08:13.370 align:start position:0% your equation you translate that into a 00:08:13.370 --> 00:08:15.720 align:start position:0% your equation you translate that into a circle<00:08:13.880> with<00:08:14.360> addition<00:08:14.900> and 00:08:15.720 --> 00:08:15.730 align:start position:0% circle with addition and 00:08:15.730 --> 00:08:17.160 align:start position:0% circle with addition and yes<00:08:15.970> and<00:08:16.360> actually<00:08:16.660> the<00:08:16.780> number<00:08:17.050> of 00:08:17.160 --> 00:08:17.170 align:start position:0% yes and actually the number of 00:08:17.170 --> 00:08:19.110 align:start position:0% yes and actually the number of constraints<00:08:17.620> that<00:08:17.800> you<00:08:18.010> will<00:08:18.160> health<00:08:18.340> depends 00:08:19.110 --> 00:08:19.120 align:start position:0% constraints that you will health depends 00:08:19.120 --> 00:08:21.510 align:start position:0% constraints that you will health depends of<00:08:19.300> the<00:08:19.420> reputation<00:08:20.110> is<00:08:20.350> that<00:08:20.590> you<00:08:20.710> have<00:08:20.860> so<00:08:21.430> if 00:08:21.510 --> 00:08:21.520 align:start position:0% of the reputation is that you have so if 00:08:21.520 --> 00:08:23.300 align:start position:0% of the reputation is that you have so if you<00:08:21.670> actually<00:08:21.970> function<00:08:22.600> with<00:08:22.810> minimum 00:08:23.300 --> 00:08:23.310 align:start position:0% you actually function with minimum 00:08:23.310 --> 00:08:25.620 align:start position:0% you actually function with minimum multiplicative<00:08:24.310> complexities<00:08:25.120> that<00:08:25.390> means 00:08:25.620 --> 00:08:25.630 align:start position:0% multiplicative complexities that means 00:08:25.630 --> 00:08:28.440 align:start position:0% multiplicative complexities that means less<00:08:25.870> constraint<00:08:26.520> that<00:08:27.520> means<00:08:27.790> generating 00:08:28.440 --> 00:08:28.450 align:start position:0% less constraint that means generating 00:08:28.450 --> 00:08:31.890 align:start position:0% less constraint that means generating approve<00:08:29.050> will<00:08:30.040> be<00:08:30.220> easier<00:08:30.700> of<00:08:30.910> chain<00:08:31.180> and<00:08:31.360> that 00:08:31.890 --> 00:08:31.900 align:start position:0% approve will be easier of chain and that 00:08:31.900 --> 00:08:33.719 align:start position:0% approve will be easier of chain and that means<00:08:32.110> that<00:08:32.260> it<00:08:32.380> is<00:08:32.470> more<00:08:32.530> mobile-friendly<00:08:33.070> so 00:08:33.719 --> 00:08:33.729 align:start position:0% means that it is more mobile-friendly so 00:08:33.729 --> 00:08:35.460 align:start position:0% means that it is more mobile-friendly so we've<00:08:33.880> made<00:08:34.060> that<00:08:34.240> choice<00:08:34.450> so<00:08:34.810> that<00:08:35.200> you<00:08:35.290> could 00:08:35.460 --> 00:08:35.470 align:start position:0% we've made that choice so that you could 00:08:35.470 --> 00:08:36.900 align:start position:0% we've made that choice so that you could actually<00:08:35.620> generate<00:08:35.950> the<00:08:36.220> proof<00:08:36.460> of<00:08:36.610> a<00:08:36.700> mobile 00:08:36.900 --> 00:08:36.910 align:start position:0% actually generate the proof of a mobile 00:08:36.910 --> 00:08:40.680 align:start position:0% actually generate the proof of a mobile within<00:08:37.810> five<00:08:38.169> six<00:08:38.500> seconds<00:08:39.390> of<00:08:40.390> course 00:08:40.680 --> 00:08:40.690 align:start position:0% within five six seconds of course 00:08:40.690 --> 00:08:42.570 align:start position:0% within five six seconds of course there's<00:08:40.870> a<00:08:40.900> few<00:08:41.050> drawbacks<00:08:41.260> of<00:08:41.590> using<00:08:41.650> MCs 00:08:42.570 --> 00:08:42.580 align:start position:0% there's a few drawbacks of using MCs 00:08:42.580 --> 00:08:44.640 align:start position:0% there's a few drawbacks of using MCs I've<00:08:43.210> always<00:08:43.450> in<00:08:43.660> engineering<00:08:44.169> is<00:08:44.260> a<00:08:44.350> question 00:08:44.640 --> 00:08:44.650 align:start position:0% I've always in engineering is a question 00:08:44.650 --> 00:08:47.190 align:start position:0% I've always in engineering is a question of<00:08:44.710> compromises<00:08:45.430> if<00:08:46.090> you<00:08:46.300> mean<00:08:46.600> C's<00:08:46.810> there<00:08:47.110> are 00:08:47.190 --> 00:08:47.200 align:start position:0% of compromises if you mean C's there are 00:08:47.200 --> 00:08:49.080 align:start position:0% of compromises if you mean C's there are more<00:08:47.380> expensive<00:08:47.740> but<00:08:48.040> um<00:08:48.460> because<00:08:48.850> there<00:08:49.030> is 00:08:49.080 --> 00:08:49.090 align:start position:0% more expensive but um because there is 00:08:49.090 --> 00:08:52.290 align:start position:0% more expensive but um because there is no<00:08:49.210> pre-compile<00:08:49.810> to<00:08:50.620> exceed<00:08:51.520> as<00:08:51.820> we<00:08:51.940> will<00:08:52.090> see 00:08:52.290 --> 00:08:52.300 align:start position:0% no pre-compile to exceed as we will see 00:08:52.300 --> 00:08:54.210 align:start position:0% no pre-compile to exceed as we will see there<00:08:52.510> is<00:08:52.540> an<00:08:52.720> NP<00:08:53.050> for<00:08:53.230> that<00:08:53.380> but<00:08:53.950> that's<00:08:54.100> all 00:08:54.210 --> 00:08:54.220 align:start position:0% there is an NP for that but that's all 00:08:54.220 --> 00:08:56.040 align:start position:0% there is an NP for that but that's all for<00:08:54.250> now<00:08:54.460> maybe<00:08:55.000> see<00:08:55.210> some<00:08:55.390> changes<00:08:55.780> quite 00:08:56.040 --> 00:08:56.050 align:start position:0% for now maybe see some changes quite 00:08:56.050 --> 00:08:58.530 align:start position:0% for now maybe see some changes quite expensive<00:08:56.380> so<00:08:56.860> actually<00:08:57.730> when<00:08:57.910> you<00:08:58.000> deposit<00:08:58.330> a 00:08:58.530 --> 00:08:58.540 align:start position:0% expensive so actually when you deposit a 00:08:58.540 --> 00:09:00.960 align:start position:0% expensive so actually when you deposit a leave<00:08:58.750> you<00:08:59.380> need<00:08:59.560> to<00:08:59.710> update<00:08:59.830> your<00:09:00.040> worker<00:09:00.700> 3 00:09:00.960 --> 00:09:00.970 align:start position:0% leave you need to update your worker 3 00:09:00.970 --> 00:09:04.530 align:start position:0% leave you need to update your worker 3 and<00:09:01.270> that<00:09:01.480> requires<00:09:01.840> gas<00:09:02.700> and<00:09:03.700> also<00:09:04.060> in<00:09:04.330> see 00:09:04.530 --> 00:09:04.540 align:start position:0% and that requires gas and also in see 00:09:04.540 --> 00:09:06.690 align:start position:0% and that requires gas and also in see them<00:09:04.720> invested<00:09:05.260> and<00:09:05.950> if<00:09:06.100> you<00:09:06.220> are<00:09:06.340> a<00:09:06.370> is 00:09:06.690 --> 00:09:06.700 align:start position:0% them invested and if you are a is 00:09:06.700 --> 00:09:08.430 align:start position:0% them invested and if you are a is presentation<00:09:07.450> this<00:09:07.540> morning<00:09:07.630> that<00:09:08.080> I<00:09:08.110> landed 00:09:08.430 --> 00:09:08.440 align:start position:0% presentation this morning that I landed 00:09:08.440 --> 00:09:09.690 align:start position:0% presentation this morning that I landed that<00:09:08.500> eternal<00:09:09.010> Foundation<00:09:09.580> is<00:09:09.670> funding 00:09:09.690 --> 00:09:09.700 align:start position:0% that eternal Foundation is funding 00:09:09.700 --> 00:09:16.440 align:start position:0% that eternal Foundation is funding research<00:09:10.060> on<00:09:10.900> MCS<00:09:11.350> for<00:09:12.270> specific<00:09:13.270> events<00:09:15.450> so 00:09:16.440 --> 00:09:16.450 align:start position:0% research on MCS for specific events so 00:09:16.450 --> 00:09:18.540 align:start position:0% research on MCS for specific events so to<00:09:16.480> mitigate<00:09:16.720> the<00:09:17.140> risk<00:09:17.350> associated<00:09:18.130> with 00:09:18.540 --> 00:09:18.550 align:start position:0% to mitigate the risk associated with 00:09:18.550 --> 00:09:21.480 align:start position:0% to mitigate the risk associated with disease<00:09:19.000> we<00:09:19.690> are<00:09:19.720> actually<00:09:19.930> using<00:09:20.440> Shan<00:09:20.710> 256 00:09:21.480 --> 00:09:21.490 align:start position:0% disease we are actually using Shan 256 00:09:21.490 --> 00:09:25.950 align:start position:0% disease we are actually using Shan 256 for<00:09:22.180> the<00:09:22.270> leaf<00:09:22.480> of<00:09:22.780> the<00:09:23.590> tree<00:09:24.570> we're<00:09:25.570> not<00:09:25.690> going 00:09:25.950 --> 00:09:25.960 align:start position:0% for the leaf of the tree we're not going 00:09:25.960 --> 00:09:27.840 align:start position:0% for the leaf of the tree we're not going to<00:09:25.990> the<00:09:26.200> cryptography<00:09:27.040> behind<00:09:27.370> it<00:09:27.520> but<00:09:27.700> the 00:09:27.840 --> 00:09:27.850 align:start position:0% to the cryptography behind it but the 00:09:27.850 --> 00:09:30.390 align:start position:0% to the cryptography behind it but the intuition<00:09:28.300> is<00:09:28.420> that<00:09:28.590> even<00:09:29.590> it<00:09:29.710> means<00:09:29.920> he<00:09:30.100> turns 00:09:30.390 --> 00:09:30.400 align:start position:0% intuition is that even it means he turns 00:09:30.400 --> 00:09:32.550 align:start position:0% intuition is that even it means he turns out<00:09:30.550> to<00:09:30.610> be<00:09:30.730> non<00:09:31.000> primitive<00:09:31.270> resistant<00:09:31.960> it 00:09:32.550 --> 00:09:32.560 align:start position:0% out to be non primitive resistant it 00:09:32.560 --> 00:09:34.470 align:start position:0% out to be non primitive resistant it will<00:09:32.710> still<00:09:32.920> as<00:09:33.070> privacy<00:09:33.490> assuming<00:09:34.240> that 00:09:34.470 --> 00:09:34.480 align:start position:0% will still as privacy assuming that 00:09:34.480 --> 00:09:37.410 align:start position:0% will still as privacy assuming that means<00:09:35.050> he<00:09:35.320> of<00:09:35.470> one<00:09:35.800> half<00:09:36.040> of<00:09:36.220> the<00:09:36.430> the<00:09:37.000> inputs 00:09:37.410 --> 00:09:37.420 align:start position:0% means he of one half of the the inputs 00:09:37.420 --> 00:09:40.560 align:start position:0% means he of one half of the the inputs is<00:09:37.840> pretty<00:09:38.200> much<00:09:38.320> resistance<00:09:39.120> the<00:09:40.120> problem<00:09:40.480> is 00:09:40.560 --> 00:09:40.570 align:start position:0% is pretty much resistance the problem is 00:09:40.570 --> 00:09:42.210 align:start position:0% is pretty much resistance the problem is that<00:09:40.750> using<00:09:40.980> sha-256 00:09:42.210 --> 00:09:42.220 align:start position:0% that using sha-256 00:09:42.220 --> 00:09:44.730 align:start position:0% that using sha-256 means<00:09:43.090> more<00:09:43.450> secret<00:09:43.900> constraint<00:09:44.410> and<00:09:44.680> so 00:09:44.730 --> 00:09:44.740 align:start position:0% means more secret constraint and so 00:09:44.740 --> 00:09:48.030 align:start position:0% means more secret constraint and so again<00:09:45.190> we've<00:09:45.370> increased<00:09:45.820> the<00:09:46.980> generation<00:09:47.980> of 00:09:48.030 --> 00:09:48.040 align:start position:0% again we've increased the generation of 00:09:48.040 --> 00:09:52.680 align:start position:0% again we've increased the generation of the<00:09:48.160> proof 00:09:52.680 --> 00:09:52.690 align:start position:0% 00:09:52.690 --> 00:09:55.480 align:start position:0% so<00:09:53.690> as<00:09:53.839> an<00:09:53.959> Israeli<00:09:54.170> in<00:09:54.589> our<00:09:54.709> in<00:09:54.949> our<00:09:55.040> use<00:09:55.220> case 00:09:55.480 --> 00:09:55.490 align:start position:0% so as an Israeli in our in our use case 00:09:55.490 --> 00:09:57.879 align:start position:0% so as an Israeli in our in our use case we<00:09:55.699> want<00:09:55.940> people<00:09:56.660> being<00:09:57.019> able<00:09:57.139> to<00:09:57.290> transfer 00:09:57.879 --> 00:09:57.889 align:start position:0% we want people being able to transfer 00:09:57.889 --> 00:10:00.009 align:start position:0% we want people being able to transfer one<00:09:58.550> deed<00:09:58.759> from<00:09:59.000> Hardware<00:09:59.389> wallet<00:09:59.660> to<00:09:59.990> a 00:10:00.009 --> 00:10:00.019 align:start position:0% one deed from Hardware wallet to a 00:10:00.019 --> 00:10:02.079 align:start position:0% one deed from Hardware wallet to a larger<00:10:00.350> one<00:10:00.529> it<00:10:00.709> that<00:10:01.310> has<00:10:01.430> not<00:10:01.639> been<00:10:01.819> funded 00:10:02.079 --> 00:10:02.089 align:start position:0% larger one it that has not been funded 00:10:02.089 --> 00:10:04.300 align:start position:0% larger one it that has not been funded yet<00:10:02.360> so<00:10:03.019> that<00:10:03.050> comes<00:10:03.379> the<00:10:03.500> question<00:10:03.649> is<00:10:04.040> called 00:10:04.300 --> 00:10:04.310 align:start position:0% yet so that comes the question is called 00:10:04.310 --> 00:10:06.610 align:start position:0% yet so that comes the question is called as<00:10:04.519> the<00:10:04.639> person<00:10:05.060> we<00:10:05.420> joined<00:10:05.720> the<00:10:05.899> money<00:10:06.110> will 00:10:06.610 --> 00:10:06.620 align:start position:0% as the person we joined the money will 00:10:06.620 --> 00:10:08.410 align:start position:0% as the person we joined the money will pay<00:10:06.649> there's<00:10:07.220> no<00:10:07.370> heat<00:10:07.579> they<00:10:07.790> cannot<00:10:07.970> pay<00:10:08.209> for 00:10:08.410 --> 00:10:08.420 align:start position:0% pay there's no heat they cannot pay for 00:10:08.420 --> 00:10:10.329 align:start position:0% pay there's no heat they cannot pay for the<00:10:08.480> gas<00:10:08.629> and<00:10:08.930> so<00:10:09.470> again<00:10:09.620> it<00:10:09.740> is<00:10:09.829> to<00:10:10.040> use<00:10:10.160> the 00:10:10.329 --> 00:10:10.339 align:start position:0% the gas and so again it is to use the 00:10:10.339 --> 00:10:14.920 align:start position:0% the gas and so again it is to use the layers<00:10:12.310> and<00:10:13.310> so<00:10:13.490> in<00:10:13.579> our<00:10:13.670> case<00:10:13.699> we<00:10:14.600> have<00:10:14.689> deploy 00:10:14.920 --> 00:10:14.930 align:start position:0% layers and so in our case we have deploy 00:10:14.930 --> 00:10:17.470 align:start position:0% layers and so in our case we have deploy along<00:10:15.079> B<00:10:15.350> layer<00:10:15.529> there's<00:10:16.310> work<00:10:16.910> been<00:10:17.149> done<00:10:17.180> by 00:10:17.470 --> 00:10:17.480 align:start position:0% along B layer there's work been done by 00:10:17.480 --> 00:10:18.939 align:start position:0% along B layer there's work been done by the<00:10:17.540> simapro<00:10:18.050> team<00:10:18.290> of<00:10:18.500> the<00:10:18.589> gas<00:10:18.740> network 00:10:18.939 --> 00:10:18.949 align:start position:0% the simapro team of the gas network 00:10:18.949 --> 00:10:21.910 align:start position:0% the simapro team of the gas network station<00:10:19.519> to<00:10:19.670> actually<00:10:20.000> use<00:10:20.180> a<00:10:20.930> network<00:10:21.560> of 00:10:21.910 --> 00:10:21.920 align:start position:0% station to actually use a network of 00:10:21.920 --> 00:10:24.639 align:start position:0% station to actually use a network of layers<00:10:22.639> and<00:10:22.970> yet<00:10:23.569> if<00:10:23.750> then<00:10:23.930> the<00:10:24.050> relay<00:10:24.319> will<00:10:24.620> be 00:10:24.639 --> 00:10:24.649 align:start position:0% layers and yet if then the relay will be 00:10:24.649 --> 00:10:27.519 align:start position:0% layers and yet if then the relay will be made<00:10:25.279> that<00:10:25.670> we<00:10:25.910> drove<00:10:26.060> transaction<00:10:26.779> on<00:10:27.259> your 00:10:27.519 --> 00:10:27.529 align:start position:0% made that we drove transaction on your 00:10:27.529 --> 00:10:28.090 align:start position:0% made that we drove transaction on your behalf 00:10:28.090 --> 00:10:28.100 align:start position:0% behalf 00:10:28.100 --> 00:10:30.759 align:start position:0% behalf and<00:10:28.189> we<00:10:28.430> will<00:10:28.850> be<00:10:29.000> repaid<00:10:29.329> the<00:10:29.480> gas<00:10:29.689> that<00:10:30.350> used 00:10:30.759 --> 00:10:30.769 align:start position:0% and we will be repaid the gas that used 00:10:30.769 --> 00:10:35.319 align:start position:0% and we will be repaid the gas that used by<00:10:31.310> taking<00:10:31.670> a<00:10:31.759> small<00:10:31.879> cut<00:10:32.240> on<00:10:32.420> the<00:10:32.629> deposit<00:10:34.329> as 00:10:35.319 --> 00:10:35.329 align:start position:0% by taking a small cut on the deposit as 00:10:35.329 --> 00:10:36.819 align:start position:0% by taking a small cut on the deposit as we<00:10:35.509> discussed<00:10:35.839> on<00:10:35.959> the<00:10:36.079> panel<00:10:36.410> there<00:10:36.709> is 00:10:36.819 --> 00:10:36.829 align:start position:0% we discussed on the panel there is 00:10:36.829 --> 00:10:38.379 align:start position:0% we discussed on the panel there is somebody<00:10:37.160> to<00:10:37.310> tell<00:10:37.519> me<00:10:37.550> there's<00:10:37.790> some<00:10:37.970> risk<00:10:38.180> as 00:10:38.379 --> 00:10:38.389 align:start position:0% somebody to tell me there's some risk as 00:10:38.389 --> 00:10:40.300 align:start position:0% somebody to tell me there's some risk as using<00:10:38.720> layers<00:10:38.990> because<00:10:39.800> of<00:10:39.889> course<00:10:40.129> you're 00:10:40.300 --> 00:10:40.310 align:start position:0% using layers because of course you're 00:10:40.310 --> 00:10:42.220 align:start position:0% using layers because of course you're using<00:10:40.490> a<00:10:40.699> centralized<00:10:41.180> may<00:10:41.810> not<00:10:42.110> be 00:10:42.220 --> 00:10:42.230 align:start position:0% using a centralized may not be 00:10:42.230 --> 00:10:44.619 align:start position:0% using a centralized may not be centralized<00:10:42.649> but<00:10:42.829> using<00:10:43.279> system<00:10:44.269> we<00:10:44.389> love<00:10:44.509> it 00:10:44.619 --> 00:10:44.629 align:start position:0% centralized but using system we love it 00:10:44.629 --> 00:10:46.480 align:start position:0% centralized but using system we love it yes<00:10:44.779> we're<00:10:45.199> making<00:10:45.290> Lydia<00:10:45.800> cause<00:10:46.040> that<00:10:46.339> means 00:10:46.480 --> 00:10:46.490 align:start position:0% yes we're making Lydia cause that means 00:10:46.490 --> 00:10:48.730 align:start position:0% yes we're making Lydia cause that means that<00:10:46.730> people<00:10:47.060> can<00:10:47.240> use<00:10:47.269> your<00:10:47.600> ID<00:10:47.779> address<00:10:48.230> to 00:10:48.730 --> 00:10:48.740 align:start position:0% that people can use your ID address to 00:10:48.740 --> 00:10:50.800 align:start position:0% that people can use your ID address to kind<00:10:48.949> of<00:10:49.040> reduce<00:10:49.370> your<00:10:49.610> anonymity<00:10:49.970> so<00:10:50.629> there's 00:10:50.800 --> 00:10:50.810 align:start position:0% kind of reduce your anonymity so there's 00:10:50.810 --> 00:10:53.769 align:start position:0% kind of reduce your anonymity so there's no<00:10:50.980> consideration<00:10:51.980> to<00:10:52.399> to<00:10:53.060> take<00:10:53.209> into<00:10:53.480> that<00:10:53.629> in 00:10:53.769 --> 00:10:53.779 align:start position:0% no consideration to to take into that in 00:10:53.779 --> 00:10:55.240 align:start position:0% no consideration to to take into that in one<00:10:53.959> possible<00:10:54.319> solution<00:10:54.500> is<00:10:54.980> to<00:10:55.100> have<00:10:55.220> a 00:10:55.240 --> 00:10:55.250 align:start position:0% one possible solution is to have a 00:10:55.250 --> 00:11:02.170 align:start position:0% one possible solution is to have a really<00:10:55.490> a<00:10:55.579> market<00:10:56.060> with<00:10:56.689> victim<00:10:57.079> talk<00:11:01.180> another 00:11:02.170 --> 00:11:02.180 align:start position:0% really a market with victim talk another 00:11:02.180 --> 00:11:04.540 align:start position:0% really a market with victim talk another important<00:11:02.750> question<00:11:02.930> with<00:11:03.500> mixer<00:11:03.949> is<00:11:04.100> one<00:11:04.399> to 00:11:04.540 --> 00:11:04.550 align:start position:0% important question with mixer is one to 00:11:04.550 --> 00:11:06.579 align:start position:0% important question with mixer is one to betray<00:11:04.699> your<00:11:04.970> funds<00:11:05.269> because<00:11:06.079> of<00:11:06.110> course<00:11:06.410> if 00:11:06.579 --> 00:11:06.589 align:start position:0% betray your funds because of course if 00:11:06.589 --> 00:11:08.319 align:start position:0% betray your funds because of course if you<00:11:06.680> deposit<00:11:06.980> your<00:11:07.220> funds<00:11:07.550> that<00:11:07.880> you<00:11:08.000> return 00:11:08.319 --> 00:11:08.329 align:start position:0% you deposit your funds that you return 00:11:08.329 --> 00:11:09.970 align:start position:0% you deposit your funds that you return immediately<00:11:08.689> then<00:11:09.230> it<00:11:09.319> completely<00:11:09.620> break 00:11:09.970 --> 00:11:09.980 align:start position:0% immediately then it completely break 00:11:09.980 --> 00:11:11.920 align:start position:0% immediately then it completely break their<00:11:10.220> anonymity<00:11:10.300> if<00:11:11.300> you<00:11:11.480> deposit<00:11:11.899> your 00:11:11.920 --> 00:11:11.930 align:start position:0% their anonymity if you deposit your 00:11:11.930 --> 00:11:14.379 align:start position:0% their anonymity if you deposit your funds<00:11:12.350> but<00:11:12.589> you<00:11:12.709> always<00:11:12.920> return<00:11:13.399> em<00:11:13.699> up<00:11:13.819> to<00:11:13.939> 24 00:11:14.379 --> 00:11:14.389 align:start position:0% funds but you always return em up to 24 00:11:14.389 --> 00:11:16.749 align:start position:0% funds but you always return em up to 24 hours<00:11:14.420> it's<00:11:15.079> the<00:11:15.199> same<00:11:15.439> people<00:11:16.279> naturally 00:11:16.749 --> 00:11:16.759 align:start position:0% hours it's the same people naturally 00:11:16.759 --> 00:11:19.329 align:start position:0% hours it's the same people naturally tend<00:11:17.240> to<00:11:17.389> to<00:11:17.720> a<00:11:17.990> pattern<00:11:18.290> and<00:11:18.800> so<00:11:19.100> this<00:11:19.220> is 00:11:19.329 --> 00:11:19.339 align:start position:0% tend to to a pattern and so this is 00:11:19.339 --> 00:11:21.009 align:start position:0% tend to to a pattern and so this is something<00:11:19.699> that<00:11:19.730> needs<00:11:19.970> to<00:11:20.120> be<00:11:20.209> mitigated<00:11:20.420> by 00:11:21.009 --> 00:11:21.019 align:start position:0% something that needs to be mitigated by 00:11:21.019 --> 00:11:23.499 align:start position:0% something that needs to be mitigated by actually<00:11:21.350> the<00:11:21.470> UX<00:11:21.800> of<00:11:21.980> building<00:11:22.339> mixer<00:11:22.759> all<00:11:23.269> do 00:11:23.499 --> 00:11:23.509 align:start position:0% actually the UX of building mixer all do 00:11:23.509 --> 00:11:25.720 align:start position:0% actually the UX of building mixer all do you<00:11:23.569> incentivize<00:11:24.079> users<00:11:24.769> to<00:11:25.040> actually<00:11:25.399> behave 00:11:25.720 --> 00:11:25.730 align:start position:0% you incentivize users to actually behave 00:11:25.730 --> 00:11:30.939 align:start position:0% you incentivize users to actually behave correctly<00:11:26.660> or<00:11:27.259> in<00:11:27.439> a<00:11:27.500> smart<00:11:27.829> way<00:11:29.649> the<00:11:30.649> problem 00:11:30.939 --> 00:11:30.949 align:start position:0% correctly or in a smart way the problem 00:11:30.949 --> 00:11:34.360 align:start position:0% correctly or in a smart way the problem is<00:11:31.009> that<00:11:31.220> yeah<00:11:31.459> whatever<00:11:32.240> anonymity<00:11:32.750> you<00:11:33.680> use 00:11:34.360 --> 00:11:34.370 align:start position:0% is that yeah whatever anonymity you use 00:11:34.370 --> 00:11:36.819 align:start position:0% is that yeah whatever anonymity you use for<00:11:34.579> example<00:11:34.610> in<00:11:35.059> our<00:11:35.180> we<00:11:35.569> just<00:11:35.839> illustrate 00:11:36.819 --> 00:11:36.829 align:start position:0% for example in our we just illustrate 00:11:36.829 --> 00:11:38.499 align:start position:0% for example in our we just illustrate the<00:11:36.949> number<00:11:37.220> of<00:11:37.370> other<00:11:37.670> lives<00:11:37.939> that<00:11:38.240> I've<00:11:38.389> been 00:11:38.499 --> 00:11:38.509 align:start position:0% the number of other lives that I've been 00:11:38.509 --> 00:11:40.360 align:start position:0% the number of other lives that I've been deposit<00:11:38.959> since<00:11:39.170> we<00:11:39.319> deposited<00:11:39.829> so<00:11:40.009> that<00:11:40.160> can 00:11:40.360 --> 00:11:40.370 align:start position:0% deposit since we deposited so that can 00:11:40.370 --> 00:11:43.059 align:start position:0% deposit since we deposited so that can be<00:11:40.399> represented<00:11:41.149> unanimity<00:11:41.930> said<00:11:42.290> but<00:11:42.829> again 00:11:43.059 --> 00:11:43.069 align:start position:0% be represented unanimity said but again 00:11:43.069 --> 00:11:43.660 align:start position:0% be represented unanimity said but again this<00:11:43.160> is<00:11:43.309> not 00:11:43.660 --> 00:11:43.670 align:start position:0% this is not 00:11:43.670 --> 00:11:47.410 align:start position:0% this is not admittedly<00:11:44.240> because<00:11:44.960> say<00:11:45.170> there<00:11:45.380> is<00:11:45.850> any<00:11:46.850> 17 00:11:47.410 --> 00:11:47.420 align:start position:0% admittedly because say there is any 17 00:11:47.420 --> 00:11:50.080 align:start position:0% admittedly because say there is any 17 maybe<00:11:48.110> 16<00:11:48.920> our<00:11:49.070> other<00:11:49.310> deposit<00:11:49.790> they<00:11:49.910> come 00:11:50.080 --> 00:11:50.090 align:start position:0% maybe 16 our other deposit they come 00:11:50.090 --> 00:11:51.880 align:start position:0% maybe 16 our other deposit they come from<00:11:50.210> the<00:11:50.360> same<00:11:50.900> person<00:11:51.290> which<00:11:51.470> is<00:11:51.590> actually 00:11:51.880 --> 00:11:51.890 align:start position:0% from the same person which is actually 00:11:51.890 --> 00:11:54.460 align:start position:0% from the same person which is actually trying<00:11:52.130> to<00:11:52.310> target<00:11:52.520> so<00:11:53.300> it's<00:11:53.330> been<00:11:53.600> tricky<00:11:54.110> to 00:11:54.460 --> 00:11:54.470 align:start position:0% trying to target so it's been tricky to 00:11:54.470 --> 00:11:57.280 align:start position:0% trying to target so it's been tricky to to<00:11:54.710> find<00:11:54.980> from<00:11:55.610> the<00:11:55.700> privacy<00:11:56.060> matrix<00:11:56.510> and<00:11:57.110> so 00:11:57.280 --> 00:11:57.290 align:start position:0% to find from the privacy matrix and so 00:11:57.290 --> 00:11:59.500 align:start position:0% to find from the privacy matrix and so the<00:11:57.440> next<00:11:57.650> person<00:11:58.160> of<00:11:58.430> opera<00:11:58.760> yet<00:11:59.030> is<00:11:59.240> to 00:11:59.500 --> 00:11:59.510 align:start position:0% the next person of opera yet is to 00:11:59.510 --> 00:12:02.230 align:start position:0% the next person of opera yet is to basically<00:12:00.350> only<00:12:01.190> enable<00:12:01.520> you<00:12:01.640> to<00:12:01.670> betray<00:12:02.000> your 00:12:02.230 --> 00:12:02.240 align:start position:0% basically only enable you to betray your 00:12:02.240 --> 00:12:04.330 align:start position:0% basically only enable you to betray your fans<00:12:02.540> after<00:12:02.750> a<00:12:02.930> certain<00:12:03.170> time<00:12:03.350> so<00:12:03.770> that<00:12:04.130> all 00:12:04.330 --> 00:12:04.340 align:start position:0% fans after a certain time so that all 00:12:04.340 --> 00:12:06.610 align:start position:0% fans after a certain time so that all usually<00:12:04.550> positive<00:12:05.200> depositing<00:12:06.200> within<00:12:06.440> what 00:12:06.610 --> 00:12:06.620 align:start position:0% usually positive depositing within what 00:12:06.620 --> 00:12:08.380 align:start position:0% usually positive depositing within what they<00:12:06.830> will<00:12:07.100> be<00:12:07.250> incentivized<00:12:07.820> to<00:12:07.940> be<00:12:08.150> true 00:12:08.380 --> 00:12:08.390 align:start position:0% they will be incentivized to be true 00:12:08.390 --> 00:12:10.570 align:start position:0% they will be incentivized to be true more<00:12:09.050> or<00:12:09.110> less<00:12:09.230> at<00:12:09.380> the<00:12:09.410> same<00:12:09.530> time<00:12:09.920> so<00:12:10.340> again 00:12:10.570 --> 00:12:10.580 align:start position:0% more or less at the same time so again 00:12:10.580 --> 00:12:17.200 align:start position:0% more or less at the same time so again you<00:12:10.870> you<00:12:11.870> cannot<00:12:12.140> increase<00:12:12.920> energy<00:12:16.180> so<00:12:17.180> I 00:12:17.200 --> 00:12:17.210 align:start position:0% you you cannot increase energy so I 00:12:17.210 --> 00:12:19.180 align:start position:0% you you cannot increase energy so I mentioned<00:12:17.540> that<00:12:17.810> will<00:12:18.110> enable<00:12:18.440> transfer<00:12:19.070> of 00:12:19.180 --> 00:12:19.190 align:start position:0% mentioned that will enable transfer of 00:12:19.190 --> 00:12:21.850 align:start position:0% mentioned that will enable transfer of 1e<00:12:19.610> again<00:12:20.540> this<00:12:20.810> makes<00:12:21.050> sense<00:12:21.200> we<00:12:21.680> let<00:12:21.830> people 00:12:21.850 --> 00:12:21.860 align:start position:0% 1e again this makes sense we let people 00:12:21.860 --> 00:12:25.360 align:start position:0% 1e again this makes sense we let people deposit<00:12:22.610> point<00:12:22.880> 77<00:12:23.630> either<00:12:24.410> for<00:12:24.860> example<00:12:25.250> and 00:12:25.360 --> 00:12:25.370 align:start position:0% deposit point 77 either for example and 00:12:25.370 --> 00:12:28.300 align:start position:0% deposit point 77 either for example and then<00:12:25.460> someone<00:12:25.850> will<00:12:26.390> close<00:12:26.660> point<00:12:27.020> 77<00:12:27.740> this<00:12:28.250> is 00:12:28.300 --> 00:12:28.310 align:start position:0% then someone will close point 77 this is 00:12:28.310 --> 00:12:29.770 align:start position:0% then someone will close point 77 this is a<00:12:28.340> good<00:12:28.520> probability<00:12:28.730> that<00:12:29.090> these<00:12:29.390> two<00:12:29.570> people 00:12:29.770 --> 00:12:29.780 align:start position:0% a good probability that these two people 00:12:29.780 --> 00:12:31.840 align:start position:0% a good probability that these two people are<00:12:30.020> actually<00:12:30.740> connected<00:12:31.400> again<00:12:31.700> you've 00:12:31.840 --> 00:12:31.850 align:start position:0% are actually connected again you've 00:12:31.850 --> 00:12:33.700 align:start position:0% are actually connected again you've recreated<00:12:32.210> a<00:12:32.570> thing<00:12:32.780> that<00:12:32.990> we<00:12:33.140> try<00:12:33.350> to<00:12:33.380> break 00:12:33.700 --> 00:12:33.710 align:start position:0% recreated a thing that we try to break 00:12:33.710 --> 00:12:36.310 align:start position:0% recreated a thing that we try to break so<00:12:34.220> yeah<00:12:34.430> it<00:12:34.490> is<00:12:34.610> to<00:12:34.850> fix<00:12:35.090> the<00:12:35.450> amount<00:12:36.110> that 00:12:36.310 --> 00:12:36.320 align:start position:0% so yeah it is to fix the amount that 00:12:36.320 --> 00:12:38.320 align:start position:0% so yeah it is to fix the amount that people<00:12:36.380> can<00:12:36.890> deposit<00:12:37.190> so<00:12:37.940> they<00:12:38.060> become 00:12:38.320 --> 00:12:38.330 align:start position:0% people can deposit so they become 00:12:38.330 --> 00:12:42.700 align:start position:0% people can deposit so they become indistinguishable<00:12:40.660> now<00:12:41.660> the<00:12:41.720> one 00:12:42.700 --> 00:12:42.710 align:start position:0% indistinguishable now the one 00:12:42.710 --> 00:12:44.530 align:start position:0% indistinguishable now the one improvement<00:12:43.310> that<00:12:43.400> we<00:12:43.610> can<00:12:43.790> do<00:12:43.940> because<00:12:44.240> of 00:12:44.530 --> 00:12:44.540 align:start position:0% improvement that we can do because of 00:12:44.540 --> 00:12:46.660 align:start position:0% improvement that we can do because of course<00:12:44.750> if<00:12:45.470> there<00:12:45.680> is<00:12:45.740> only<00:12:45.890> the<00:12:46.070> positive<00:12:46.220> one 00:12:46.660 --> 00:12:46.670 align:start position:0% course if there is only the positive one 00:12:46.670 --> 00:12:48.550 align:start position:0% course if there is only the positive one it<00:12:46.880> is<00:12:47.030> quite<00:12:47.270> kind<00:12:47.510> of<00:12:47.600> limiting<00:12:47.990> so<00:12:48.170> again<00:12:48.350> is 00:12:48.550 --> 00:12:48.560 align:start position:0% it is quite kind of limiting so again is 00:12:48.560 --> 00:12:50.290 align:start position:0% it is quite kind of limiting so again is that<00:12:48.830> it<00:12:49.070> would<00:12:49.190> make<00:12:49.340> the<00:12:49.430> contract<00:12:49.820> for<00:12:50.000> 1e 00:12:50.290 --> 00:12:50.300 align:start position:0% that it would make the contract for 1e 00:12:50.300 --> 00:12:52.900 align:start position:0% that it would make the contract for 1e contract<00:12:50.990> attendee<00:12:51.500> contract<00:12:52.310> for<00:12:52.490> unworthy 00:12:52.900 --> 00:12:52.910 align:start position:0% contract attendee contract for unworthy 00:12:52.910 --> 00:12:54.730 align:start position:0% contract attendee contract for unworthy but<00:12:53.510> the<00:12:53.600> promise<00:12:53.930> that<00:12:53.960> you<00:12:54.260> split<00:12:54.470> your 00:12:54.730 --> 00:12:54.740 align:start position:0% but the promise that you split your 00:12:54.740 --> 00:12:57.010 align:start position:0% but the promise that you split your enemy<00:12:55.070> tea<00:12:55.190> set<00:12:55.430> and<00:12:55.730> again<00:12:56.570> this<00:12:56.720> is<00:12:56.900> no 00:12:57.010 --> 00:12:57.020 align:start position:0% enemy tea set and again this is no 00:12:57.020 --> 00:12:59.920 align:start position:0% enemy tea set and again this is no ability<00:12:57.200> there<00:12:58.190> are<00:12:58.340> a<00:12:58.880> solution<00:12:59.600> and<00:12:59.780> this<00:12:59.870> is 00:12:59.920 --> 00:12:59.930 align:start position:0% ability there are a solution and this is 00:12:59.930 --> 00:13:02.320 align:start position:0% ability there are a solution and this is something<00:13:00.230> that<00:13:01.070> we<00:13:01.310> work<00:13:01.490> a<00:13:01.670> new<00:13:01.790> future<00:13:02.090> or 00:13:02.320 --> 00:13:02.330 align:start position:0% something that we work a new future or 00:13:02.330 --> 00:13:04.000 align:start position:0% something that we work a new future or that<00:13:02.480> you<00:13:02.570> want<00:13:02.750> people<00:13:02.900> to<00:13:03.080> work<00:13:03.380> on<00:13:03.560> is<00:13:03.770> the 00:13:04.000 --> 00:13:04.010 align:start position:0% that you want people to work on is the 00:13:04.010 --> 00:13:06.160 align:start position:0% that you want people to work on is the possibility<00:13:04.490> to<00:13:04.880> use<00:13:04.910> jumps<00:13:05.360> encircled 00:13:06.160 --> 00:13:06.170 align:start position:0% possibility to use jumps encircled 00:13:06.170 --> 00:13:07.780 align:start position:0% possibility to use jumps encircled so<00:13:06.500> basically<00:13:06.800> yet<00:13:07.070> is<00:13:07.280> that<00:13:07.310> you<00:13:07.610> always 00:13:07.780 --> 00:13:07.790 align:start position:0% so basically yet is that you always 00:13:07.790 --> 00:13:10.960 align:start position:0% so basically yet is that you always deposit<00:13:08.500> multiple<00:13:09.500> of<00:13:09.590> one<00:13:09.770> key<00:13:09.950> and<00:13:10.160> then<00:13:10.760> one 00:13:10.960 --> 00:13:10.970 align:start position:0% deposit multiple of one key and then one 00:13:10.970 --> 00:13:12.280 align:start position:0% deposit multiple of one key and then one you<00:13:11.060> want<00:13:11.240> to<00:13:11.300> be<00:13:11.390> true<00:13:11.600> you<00:13:11.630> can<00:13:11.960> actually 00:13:12.280 --> 00:13:12.290 align:start position:0% you want to be true you can actually 00:13:12.290 --> 00:13:14.500 align:start position:0% you want to be true you can actually combine<00:13:12.560> two<00:13:13.010> these<00:13:13.220> into<00:13:13.580> one<00:13:13.760> and<00:13:14.060> so<00:13:14.450> you 00:13:14.500 --> 00:13:14.510 align:start position:0% combine two these into one and so you 00:13:14.510 --> 00:13:19.120 align:start position:0% combine two these into one and so you can<00:13:14.780> for<00:13:15.680> example<00:13:15.740> we<00:13:16.160> grow<00:13:16.370> 100<00:13:17.360> 100<00:13:18.130> without 00:13:19.120 --> 00:13:19.130 align:start position:0% can for example we grow 100 100 without 00:13:19.130 --> 00:13:23.860 align:start position:0% can for example we grow 100 100 without breaking<00:13:19.640> it 00:13:23.860 --> 00:13:23.870 align:start position:0% 00:13:23.870 --> 00:13:26.530 align:start position:0% another<00:13:24.620> limitation<00:13:24.980> of<00:13:25.310> upper<00:13:25.640> is<00:13:26.060> that<00:13:26.330> this 00:13:26.530 --> 00:13:26.540 align:start position:0% another limitation of upper is that this 00:13:26.540 --> 00:13:30.910 align:start position:0% another limitation of upper is that this body<00:13:26.810> around<00:13:27.620> 32,000<00:13:28.520> leaf<00:13:29.240> per<00:13:30.230> contract<00:13:30.590> and 00:13:30.910 --> 00:13:30.920 align:start position:0% body around 32,000 leaf per contract and 00:13:30.920 --> 00:13:33.220 align:start position:0% body around 32,000 leaf per contract and the<00:13:31.460> reason<00:13:31.820> is<00:13:31.940> that<00:13:31.970> you<00:13:32.450> have<00:13:32.480> an<00:13:32.690> Oracle<00:13:32.870> 3 00:13:33.220 --> 00:13:33.230 align:start position:0% the reason is that you have an Oracle 3 00:13:33.230 --> 00:13:36.880 align:start position:0% the reason is that you have an Oracle 3 and<00:13:33.500> the<00:13:34.100> more<00:13:34.540> then<00:13:35.540> you<00:13:35.900> want<00:13:36.080> to<00:13:36.170> America<00:13:36.650> 3 00:13:36.880 --> 00:13:36.890 align:start position:0% and the more then you want to America 3 00:13:36.890 --> 00:13:39.280 align:start position:0% and the more then you want to America 3 the<00:13:37.730> more<00:13:37.880> expensive<00:13:38.180> it<00:13:38.480> is<00:13:38.630> in<00:13:38.750> terms<00:13:38.870> of<00:13:39.110> gas 00:13:39.280 --> 00:13:39.290 align:start position:0% the more expensive it is in terms of gas 00:13:39.290 --> 00:13:42.340 align:start position:0% the more expensive it is in terms of gas and<00:13:39.590> seen<00:13:39.830> you<00:13:39.890> wanted<00:13:40.160> to<00:13:40.310> keep<00:13:41.110> this<00:13:42.110> and 00:13:42.340 --> 00:13:42.350 align:start position:0% and seen you wanted to keep this and 00:13:42.350 --> 00:13:43.510 align:start position:0% and seen you wanted to keep this and there<00:13:42.470> are<00:13:42.500> billions<00:13:42.890> of<00:13:43.010> the<00:13:43.100> deposit 00:13:43.510 --> 00:13:43.520 align:start position:0% there are billions of the deposit 00:13:43.520 --> 00:13:45.820 align:start position:0% there are billions of the deposit individuals<00:13:44.150> it's<00:13:44.390> kind<00:13:44.630> of<00:13:44.690> leaving<00:13:45.110> the 00:13:45.820 --> 00:13:45.830 align:start position:0% individuals it's kind of leaving the 00:13:45.830 --> 00:13:48.130 align:start position:0% individuals it's kind of leaving the number<00:13:46.010> of<00:13:46.360> level<00:13:47.360> that<00:13:47.540> you<00:13:47.660> can<00:13:47.780> aid<00:13:47.930> in 00:13:48.130 --> 00:13:48.140 align:start position:0% number of level that you can aid in 00:13:48.140 --> 00:13:50.290 align:start position:0% number of level that you can aid in America<00:13:48.620> 3<00:13:48.860> and<00:13:49.130> so<00:13:49.250> the<00:13:49.310> number<00:13:49.610> at<00:13:49.910> the<00:13:50.030> level 00:13:50.290 --> 00:13:50.300 align:start position:0% America 3 and so the number at the level 00:13:50.300 --> 00:13:53.290 align:start position:0% America 3 and so the number at the level of<00:13:50.360> us<00:13:50.660> believe<00:13:51.500> that<00:13:51.530> you<00:13:51.770> can<00:13:52.040> deposit<00:13:52.310> so<00:13:53.120> we 00:13:53.290 --> 00:13:53.300 align:start position:0% of us believe that you can deposit so we 00:13:53.300 --> 00:13:56.380 align:start position:0% of us believe that you can deposit so we have<00:13:53.390> fixed<00:13:53.570> a<00:13:53.780> 15<00:13:54.710> which<00:13:54.980> is<00:13:55.160> the<00:13:55.220> gasser<00:13:55.550> on<00:13:55.790> a 00:13:56.380 --> 00:13:56.390 align:start position:0% have fixed a 15 which is the gasser on a 00:13:56.390 --> 00:13:59.080 align:start position:0% have fixed a 15 which is the gasser on a medium<00:13:57.200> the<00:13:57.830> problem<00:13:58.160> is<00:13:58.250> that<00:13:58.400> once<00:13:58.670> you<00:13:58.790> fill 00:13:59.080 --> 00:13:59.090 align:start position:0% medium the problem is that once you fill 00:13:59.090 --> 00:14:05.619 align:start position:0% medium the problem is that once you fill up<00:13:59.240> your<00:13:59.270> 3<00:13:59.630> to<00:13:59.660> deploy<00:14:00.290> new<00:14:00.320> culture 00:14:05.619 --> 00:14:05.629 align:start position:0% 00:14:05.629 --> 00:14:07.910 align:start position:0% so<00:14:06.629> I'm<00:14:07.019> talking<00:14:07.230> about<00:14:07.410> some<00:14:07.740> of<00:14:07.769> the 00:14:07.910 --> 00:14:07.920 align:start position:0% so I'm talking about some of the 00:14:07.920 --> 00:14:10.519 align:start position:0% so I'm talking about some of the limitations<00:14:08.009> or<00:14:08.730> upper<00:14:09.319> fortunately<00:14:10.319> there's 00:14:10.519 --> 00:14:10.529 align:start position:0% limitations or upper fortunately there's 00:14:10.529 --> 00:14:12.199 align:start position:0% limitations or upper fortunately there's a<00:14:10.589> lot<00:14:10.709> of<00:14:10.829> areas<00:14:11.310> for<00:14:11.519> improvement 00:14:12.199 --> 00:14:12.209 align:start position:0% a lot of areas for improvement 00:14:12.209 --> 00:14:14.869 align:start position:0% a lot of areas for improvement one<00:14:12.449> is<00:14:12.629> a<00:14:12.660> lot<00:14:12.870> optimization<00:14:13.529> so<00:14:14.490> you<00:14:14.550> could 00:14:14.869 --> 00:14:14.879 align:start position:0% one is a lot optimization so you could 00:14:14.879 --> 00:14:16.730 align:start position:0% one is a lot optimization so you could attach<00:14:15.120> the<00:14:15.360> public<00:14:15.660> input<00:14:15.839> into<00:14:16.259> one<00:14:16.470> which 00:14:16.730 --> 00:14:16.740 align:start position:0% attach the public input into one which 00:14:16.740 --> 00:14:18.340 align:start position:0% attach the public input into one which would<00:14:16.889> reduce<00:14:17.040> the<00:14:17.339> number<00:14:17.430> of<00:14:17.579> cars<00:14:17.850> raining 00:14:18.340 --> 00:14:18.350 align:start position:0% would reduce the number of cars raining 00:14:18.350 --> 00:14:20.869 align:start position:0% would reduce the number of cars raining you<00:14:19.350> can<00:14:19.379> optimize<00:14:19.769> the<00:14:19.949> contract<00:14:20.490> for<00:14:20.819> the 00:14:20.869 --> 00:14:20.879 align:start position:0% you can optimize the contract for the 00:14:20.879 --> 00:14:22.670 align:start position:0% you can optimize the contract for the moment<00:14:21.209> the<00:14:21.300> contract<00:14:21.689> is<00:14:21.870> in<00:14:22.019> plain<00:14:22.230> solidity 00:14:22.670 --> 00:14:22.680 align:start position:0% moment the contract is in plain solidity 00:14:22.680 --> 00:14:24.769 align:start position:0% moment the contract is in plain solidity there's<00:14:23.639> some<00:14:23.819> step<00:14:24.029> that<00:14:24.209> will<00:14:24.389> be<00:14:24.509> written 00:14:24.769 --> 00:14:24.779 align:start position:0% there's some step that will be written 00:14:24.779 --> 00:14:26.290 align:start position:0% there's some step that will be written in<00:14:24.870> assembly<00:14:25.350> that<00:14:25.589> would<00:14:25.769> reduce 00:14:26.290 --> 00:14:26.300 align:start position:0% in assembly that would reduce 00:14:26.300 --> 00:14:28.429 align:start position:0% in assembly that would reduce consumption<00:14:27.300> by<00:14:27.600> fifteen<00:14:28.019> to<00:14:28.170> twenty<00:14:28.410> percent 00:14:28.429 --> 00:14:28.439 align:start position:0% consumption by fifteen to twenty percent 00:14:28.439 --> 00:14:30.799 align:start position:0% consumption by fifteen to twenty percent and<00:14:28.949> again<00:14:29.069> that<00:14:29.699> enables<00:14:30.149> you<00:14:30.300> to<00:14:30.329> increase 00:14:30.799 --> 00:14:30.809 align:start position:0% and again that enables you to increase 00:14:30.809 --> 00:14:34.639 align:start position:0% and again that enables you to increase the<00:14:31.259> depth<00:14:31.829> of<00:14:32.069> your<00:14:32.240> three<00:14:33.240> and<00:14:33.509> so<00:14:33.899> the<00:14:34.079> the 00:14:34.639 --> 00:14:34.649 align:start position:0% the depth of your three and so the the 00:14:34.649 --> 00:14:36.619 align:start position:0% the depth of your three and so the the possible<00:14:35.040> deposit<00:14:35.490> that<00:14:35.790> can<00:14:35.970> be<00:14:36.120> of<00:14:36.209> a<00:14:36.300> single 00:14:36.619 --> 00:14:36.629 align:start position:0% possible deposit that can be of a single 00:14:36.629 --> 00:14:40.069 align:start position:0% possible deposit that can be of a single contract<00:14:37.220> and<00:14:38.220> there<00:14:38.759> is<00:14:38.879> work<00:14:39.149> on<00:14:39.360> you<00:14:39.600> VIP 00:14:40.069 --> 00:14:40.079 align:start position:0% contract and there is work on you VIP 00:14:40.079 --> 00:14:43.100 align:start position:0% contract and there is work on you VIP 1108<00:14:41.040> well<00:14:41.670> yes<00:14:41.879> d<00:14:42.059> which<00:14:42.389> is<00:14:42.420> a<00:14:42.540> pre<00:14:42.749> compiled 00:14:43.100 --> 00:14:43.110 align:start position:0% 1108 well yes d which is a pre compiled 00:14:43.110 --> 00:14:45.110 align:start position:0% 1108 well yes d which is a pre compiled form<00:14:43.350> in<00:14:43.470> c<00:14:43.649> so<00:14:43.860> that<00:14:44.279> we<00:14:44.459> really<00:14:44.699> reduce<00:14:45.089> the 00:14:45.110 --> 00:14:45.120 align:start position:0% form in c so that we really reduce the 00:14:45.120 --> 00:14:47.090 align:start position:0% form in c so that we really reduce the gas<00:14:45.420> computing<00:14:46.170> it<00:14:46.319> sees<00:14:46.559> that<00:14:46.829> means 00:14:47.090 --> 00:14:47.100 align:start position:0% gas computing it sees that means 00:14:47.100 --> 00:14:49.519 align:start position:0% gas computing it sees that means updating<00:14:47.999> the<00:14:48.089> Merkel<00:14:48.420> three<00:14:48.629> women<00:14:49.110> shippers 00:14:49.519 --> 00:14:49.529 align:start position:0% updating the Merkel three women shippers 00:14:49.529 --> 00:14:57.610 align:start position:0% updating the Merkel three women shippers again<00:14:49.980> we<00:14:50.160> can<00:14:50.339> use<00:14:50.370> a<00:14:50.759> much<00:14:51.180> bigger<00:14:52.040> tree 00:14:57.610 --> 00:14:57.620 align:start position:0% 00:14:57.620 --> 00:15:02.139 align:start position:0% another<00:14:58.620> functional<00:14:59.550> improvement<00:15:00.149> that<00:15:01.110> is 00:15:02.139 --> 00:15:02.149 align:start position:0% another functional improvement that is 00:15:02.149 --> 00:15:05.540 align:start position:0% another functional improvement that is part<00:15:03.149> of<00:15:03.209> the<00:15:03.389> next<00:15:03.749> iteration<00:15:03.870> offer<00:15:04.589> is<00:15:05.339> to 00:15:05.540 --> 00:15:05.550 align:start position:0% part of the next iteration offer is to 00:15:05.550 --> 00:15:07.220 align:start position:0% part of the next iteration offer is to store<00:15:05.790> a<00:15:05.819> buffer<00:15:06.300> of<00:15:06.540> the<00:15:06.720> reason<00:15:07.079> mercury 00:15:07.220 --> 00:15:07.230 align:start position:0% store a buffer of the reason mercury 00:15:07.230 --> 00:15:10.670 align:start position:0% store a buffer of the reason mercury moves<00:15:07.649> because<00:15:08.639> now<00:15:09.029> when<00:15:09.600> you<00:15:09.689> want<00:15:09.870> when<00:15:10.589> you 00:15:10.670 --> 00:15:10.680 align:start position:0% moves because now when you want when you 00:15:10.680 --> 00:15:12.619 align:start position:0% moves because now when you want when you want<00:15:10.709> to<00:15:10.860> create<00:15:11.160> your<00:15:11.459> your<00:15:11.850> proof<00:15:12.120> you<00:15:12.480> need 00:15:12.619 --> 00:15:12.629 align:start position:0% want to create your your proof you need 00:15:12.629 --> 00:15:15.769 align:start position:0% want to create your your proof you need to<00:15:12.779> have<00:15:12.930> a<00:15:13.829> miracle<00:15:14.220> tab<00:15:14.579> to<00:15:14.850> delete<00:15:15.120> that<00:15:15.360> one 00:15:15.769 --> 00:15:15.779 align:start position:0% to have a miracle tab to delete that one 00:15:15.779 --> 00:15:17.600 align:start position:0% to have a miracle tab to delete that one the<00:15:16.410> problem<00:15:16.709> is<00:15:16.800> that<00:15:16.920> by<00:15:17.069> the<00:15:17.129> time<00:15:17.250> you 00:15:17.600 --> 00:15:17.610 align:start position:0% the problem is that by the time you 00:15:17.610 --> 00:15:19.490 align:start position:0% the problem is that by the time you completely<00:15:18.059> approve<00:15:18.360> that<00:15:18.540> we<00:15:18.720> take<00:15:18.930> five<00:15:19.199> six 00:15:19.490 --> 00:15:19.500 align:start position:0% completely approve that we take five six 00:15:19.500 --> 00:15:21.110 align:start position:0% completely approve that we take five six seconds<00:15:19.980> and<00:15:20.250> then<00:15:20.579> you<00:15:20.670> submit<00:15:21.000> your 00:15:21.110 --> 00:15:21.120 align:start position:0% seconds and then you submit your 00:15:21.120 --> 00:15:22.249 align:start position:0% seconds and then you submit your transaction<00:15:21.660> to<00:15:21.750> the<00:15:21.779> blockchain 00:15:22.249 --> 00:15:22.259 align:start position:0% transaction to the blockchain 00:15:22.259 --> 00:15:25.249 align:start position:0% transaction to the blockchain yeah<00:15:22.559> admitted<00:15:23.100> fifteen<00:15:23.910> thirty<00:15:24.540> or<00:15:24.990> one 00:15:25.249 --> 00:15:25.259 align:start position:0% yeah admitted fifteen thirty or one 00:15:25.259 --> 00:15:27.170 align:start position:0% yeah admitted fifteen thirty or one minute<00:15:25.559> to<00:15:25.680> be<00:15:25.829> mine<00:15:26.040> it<00:15:26.550> is<00:15:26.699> possible<00:15:27.149> that 00:15:27.170 --> 00:15:27.180 align:start position:0% minute to be mine it is possible that 00:15:27.180 --> 00:15:29.150 align:start position:0% minute to be mine it is possible that someone<00:15:27.569> deposits<00:15:28.170> a<00:15:28.259> new<00:15:28.410> leaf<00:15:28.620> in<00:15:28.800> between 00:15:29.150 --> 00:15:29.160 align:start position:0% someone deposits a new leaf in between 00:15:29.160 --> 00:15:30.769 align:start position:0% someone deposits a new leaf in between which<00:15:29.670> will<00:15:29.850> update<00:15:29.970> you<00:15:30.209> three<00:15:30.509> and 00:15:30.769 --> 00:15:30.779 align:start position:0% which will update you three and 00:15:30.779 --> 00:15:32.449 align:start position:0% which will update you three and absolutely<00:15:31.230> or<00:15:31.439> broken<00:15:31.769> path<00:15:31.949> is<00:15:32.129> no<00:15:32.250> longer 00:15:32.449 --> 00:15:32.459 align:start position:0% absolutely or broken path is no longer 00:15:32.459 --> 00:15:36.079 align:start position:0% absolutely or broken path is no longer valid<00:15:32.670> so<00:15:33.360> by<00:15:33.480> keeping<00:15:34.009> the<00:15:35.009> mystery<00:15:35.370> of<00:15:35.670> three 00:15:36.079 --> 00:15:36.089 align:start position:0% valid so by keeping the mystery of three 00:15:36.089 --> 00:15:39.910 align:start position:0% valid so by keeping the mystery of three four<00:15:36.420> five<00:15:36.720> work<00:15:36.930> routes<00:15:37.350> actually<00:15:38.279> you<00:15:38.759> can 00:15:39.910 --> 00:15:39.920 align:start position:0% four five work routes actually you can 00:15:39.920 --> 00:15:42.650 align:start position:0% four five work routes actually you can improve<00:15:40.920> the<00:15:41.040> number<00:15:41.279> of<00:15:41.430> people<00:15:42.120> that<00:15:42.420> will 00:15:42.650 --> 00:15:42.660 align:start position:0% improve the number of people that will 00:15:42.660 --> 00:15:45.320 align:start position:0% improve the number of people that will succeed 00:15:45.320 --> 00:15:45.330 align:start position:0% 00:15:45.330 --> 00:15:48.920 align:start position:0% as<00:15:45.810> I<00:15:46.019> mentioned<00:15:46.440> the<00:15:47.149> klo<00:15:48.180> pistol<00:15:48.630> Patrol 00:15:48.920 --> 00:15:48.930 align:start position:0% as I mentioned the klo pistol Patrol 00:15:48.930 --> 00:15:51.290 align:start position:0% as I mentioned the klo pistol Patrol using<00:15:49.380> just<00:15:49.620> bleep<00:15:49.890> and<00:15:50.160> then<00:15:50.459> we<00:15:50.700> can<00:15:50.910> work<00:15:51.120> on 00:15:51.290 --> 00:15:51.300 align:start position:0% using just bleep and then we can work on 00:15:51.300 --> 00:15:58.340 align:start position:0% using just bleep and then we can work on a<00:15:51.390> clear<00:15:51.630> market<00:15:55.040> so<00:15:56.040> that's<00:15:56.160> it<00:15:57.320> that<00:15:58.320> was 00:15:58.340 --> 00:15:58.350 align:start position:0% a clear market so that's it that was 00:15:58.350 --> 00:16:01.430 align:start position:0% a clear market so that's it that was kind<00:15:58.440> of<00:15:58.680> brief<00:15:58.890> but<00:15:59.160> I<00:15:59.430> you<00:15:59.880> guys<00:16:00.180> enjoy<00:16:00.510> if 00:16:01.430 --> 00:16:01.440 align:start position:0% kind of brief but I you guys enjoy if 00:16:01.440 --> 00:16:03.170 align:start position:0% kind of brief but I you guys enjoy if you<00:16:01.500> want<00:16:01.800> if<00:16:01.950> you<00:16:02.070> interested<00:16:02.279> by<00:16:02.550> upper<00:16:02.910> you 00:16:03.170 --> 00:16:03.180 align:start position:0% you want if you interested by upper you 00:16:03.180 --> 00:16:05.060 align:start position:0% you want if you interested by upper you can<00:16:03.360> check<00:16:03.570> us<00:16:03.690> on<00:16:03.810> kita<00:16:04.200> the<00:16:04.620> project<00:16:05.010> is 00:16:05.060 --> 00:16:05.070 align:start position:0% can check us on kita the project is 00:16:05.070 --> 00:16:06.800 align:start position:0% can check us on kita the project is fully<00:16:05.220> open<00:16:05.550> source<00:16:05.790> and<00:16:06.000> the<00:16:06.089> idea<00:16:06.329> for<00:16:06.360> us<00:16:06.600> is 00:16:06.800 --> 00:16:06.810 align:start position:0% fully open source and the idea for us is 00:16:06.810 --> 00:16:08.810 align:start position:0% fully open source and the idea for us is be<00:16:07.470> the<00:16:07.529> tool<00:16:07.800> for<00:16:07.920> the<00:16:08.010> communities<00:16:08.490> and<00:16:08.760> this 00:16:08.810 --> 00:16:08.820 align:start position:0% be the tool for the communities and this 00:16:08.820 --> 00:16:11.120 align:start position:0% be the tool for the communities and this is<00:16:08.970> not<00:16:09.149> to<00:16:09.630> be<00:16:09.750> other<00:16:10.110> projects<00:16:10.649> or<00:16:10.769> feel<00:16:10.950> free 00:16:11.120 --> 00:16:11.130 align:start position:0% is not to be other projects or feel free 00:16:11.130 --> 00:16:13.550 align:start position:0% is not to be other projects or feel free to<00:16:11.160> contribute<00:16:11.899> if<00:16:12.899> you<00:16:13.019> have<00:16:13.110> question<00:16:13.440> you 00:16:13.550 --> 00:16:13.560 align:start position:0% to contribute if you have question you 00:16:13.560 --> 00:16:15.680 align:start position:0% to contribute if you have question you can<00:16:13.709> think<00:16:13.920> us<00:16:14.010> on<00:16:14.190> Twitter<00:16:14.760> or<00:16:14.940> telegram<00:16:15.269> and 00:16:15.680 --> 00:16:15.690 align:start position:0% can think us on Twitter or telegram and 00:16:15.690 --> 00:16:18.610 align:start position:0% can think us on Twitter or telegram and if<00:16:16.290> you<00:16:16.380> interested<00:16:16.649> by<00:16:16.920> arthritic<00:16:17.279> and<00:16:17.579> on 00:16:18.610 --> 00:16:18.620 align:start position:0% if you interested by arthritic and on 00:16:18.620 --> 00:16:20.660 align:start position:0% if you interested by arthritic and on wallet<00:16:19.620> right<00:16:19.800> now<00:16:19.980> let's<00:16:20.130> keep<00:16:20.279> the<00:16:20.399> waiting 00:16:20.660 --> 00:16:20.670 align:start position:0% wallet right now let's keep the waiting 00:16:20.670 --> 00:16:30.310 align:start position:0% wallet right now let's keep the waiting list<00:16:20.820> using<00:16:21.149> the<00:16:21.390> link<00:16:21.570> that<00:16:21.810> is<00:16:22.170> there<00:16:23.510> I 00:16:30.310 --> 00:16:30.320 align:start position:0% 00:16:30.320 --> 00:16:32.329 align:start position:0% don't<00:16:31.320> know<00:16:31.589> if<00:16:31.709> you<00:16:31.860> guys<00:16:32.010> have<00:16:32.220> any 00:16:32.329 --> 00:16:32.339 align:start position:0% don't know if you guys have any 00:16:32.339 --> 00:16:35.820 align:start position:0% don't know if you guys have any questions 00:16:35.820 --> 00:16:35.830 align:start position:0% 00:16:35.830 --> 00:16:39.750 align:start position:0% how<00:16:36.610> much<00:16:36.790> gas<00:16:37.029> does<00:16:37.510> it<00:16:37.690> cost<00:16:38.250> so<00:16:39.250> we<00:16:39.279> blew<00:16:39.610> it 00:16:39.750 --> 00:16:39.760 align:start position:0% how much gas does it cost so we blew it 00:16:39.760 --> 00:16:41.519 align:start position:0% how much gas does it cost so we blew it into<00:16:39.850> other<00:16:40.209> millions<00:16:40.660> for<00:16:40.870> millions<00:16:41.260> of<00:16:41.470> the 00:16:41.519 --> 00:16:41.529 align:start position:0% into other millions for millions of the 00:16:41.529 --> 00:16:54.800 align:start position:0% into other millions for millions of the positive<00:16:42.070> lol 00:16:54.800 --> 00:16:54.810 align:start position:0% 00:16:54.810 --> 00:17:00.690 align:start position:0% yes<00:16:55.810> expertly<00:16:57.540> to<00:16:58.540> make<00:16:59.050> the<00:16:59.200> proof<00:16:59.470> that<00:16:59.800> we 00:17:00.690 --> 00:17:00.700 align:start position:0% yes expertly to make the proof that we 00:17:00.700 --> 00:17:04.040 align:start position:0% yes expertly to make the proof that we combine<00:17:00.940> to<00:17:01.390> Merkel<00:17:01.839> Eve<00:17:02.200> into<00:17:02.680> one<00:17:02.980> so<00:17:03.550> say<00:17:03.790> I 00:17:04.040 --> 00:17:04.050 align:start position:0% combine to Merkel Eve into one so say I 00:17:04.050 --> 00:17:06.540 align:start position:0% combine to Merkel Eve into one so say I believe<00:17:05.050> a<00:17:05.290> secret<00:17:05.679> College<00:17:06.040> has<00:17:06.160> won<00:17:06.370> either 00:17:06.540 --> 00:17:06.550 align:start position:0% believe a secret College has won either 00:17:06.550 --> 00:17:08.730 align:start position:0% believe a secret College has won either another<00:17:07.000> one<00:17:07.209> that<00:17:07.360> that's<00:17:07.569> one<00:17:07.809> eater<00:17:08.050> I<00:17:08.439> do 00:17:08.730 --> 00:17:08.740 align:start position:0% another one that that's one eater I do 00:17:08.740 --> 00:17:10.679 align:start position:0% another one that that's one eater I do John<00:17:09.100> Smith<00:17:09.400> and<00:17:09.670> suddenly<00:17:10.030> everybody's 00:17:10.679 --> 00:17:10.689 align:start position:0% John Smith and suddenly everybody's 00:17:10.689 --> 00:17:13.679 align:start position:0% John Smith and suddenly everybody's perfect<00:17:11.620> so<00:17:11.890> either<00:17:12.100> and<00:17:12.819> once<00:17:13.030> that<00:17:13.240> is<00:17:13.300> done 00:17:13.679 --> 00:17:13.689 align:start position:0% perfect so either and once that is done 00:17:13.689 --> 00:17:15.929 align:start position:0% perfect so either and once that is done and<00:17:14.170> so<00:17:14.709> if<00:17:14.770> I<00:17:14.920> meet<00:17:15.160> will<00:17:15.309> be<00:17:15.730> tuned 00:17:15.929 --> 00:17:15.939 align:start position:0% and so if I meet will be tuned 00:17:15.939 --> 00:17:17.970 align:start position:0% and so if I meet will be tuned interested<00:17:16.630> in<00:17:16.750> the<00:17:16.839> end<00:17:17.050> I<00:17:17.290> can<00:17:17.860> actually 00:17:17.970 --> 00:17:17.980 align:start position:0% interested in the end I can actually 00:17:17.980 --> 00:17:20.610 align:start position:0% interested in the end I can actually flow<00:17:18.929> different<00:17:19.929> because<00:17:20.140> it's<00:17:20.350> a<00:17:20.530> different 00:17:20.610 --> 00:17:20.620 align:start position:0% flow different because it's a different 00:17:20.620 --> 00:17:24.510 align:start position:0% flow different because it's a different amount 00:17:24.510 --> 00:17:24.520 align:start position:0% 00:17:24.520 --> 00:17:28.169 align:start position:0% yes<00:17:26.010> different<00:17:27.010> circle<00:17:27.280> but<00:17:27.670> again<00:17:27.880> you<00:17:28.000> came 00:17:28.169 --> 00:17:28.179 align:start position:0% yes different circle but again you came 00:17:28.179 --> 00:17:29.910 align:start position:0% yes different circle but again you came from<00:17:28.329> line<00:17:28.569> the<00:17:28.780> Jung's<00:17:29.020> beat<00:17:29.260> with<00:17:29.440> the<00:17:29.559> rope 00:17:29.910 --> 00:17:29.920 align:start position:0% from line the Jung's beat with the rope 00:17:29.920 --> 00:17:43.529 align:start position:0% from line the Jung's beat with the rope so<00:17:30.429> that<00:17:30.460> actually<00:17:30.970> in<00:17:31.270> his<00:17:31.510> basement 00:17:43.529 --> 00:17:43.539 align:start position:0% 00:17:43.539 --> 00:17:46.749 align:start position:0% you<00:17:44.539> can<00:17:44.720> Janice<00:17:45.289> see<00:17:45.799> like<00:17:46.009> that<00:17:46.190> but<00:17:46.429> we<00:17:46.639> need 00:17:46.749 --> 00:17:46.759 align:start position:0% you can Janice see like that but we need 00:17:46.759 --> 00:17:52.659 align:start position:0% you can Janice see like that but we need your<00:17:46.880> needs<00:17:47.179> to<00:17:47.389> belabor<00:17:48.820> customers<00:17:51.669> because 00:17:52.659 --> 00:17:52.669 align:start position:0% your needs to belabor customers because 00:17:52.669 --> 00:17:53.919 align:start position:0% your needs to belabor customers because we<00:17:52.700> still<00:17:52.940> need<00:17:53.000> to<00:17:53.210> know<00:17:53.240> the<00:17:53.330> secret<00:17:53.750> be<00:17:53.899> a 00:17:53.919 --> 00:17:53.929 align:start position:0% we still need to know the secret be a 00:17:53.929 --> 00:17:55.990 align:start position:0% we still need to know the secret be a nice<00:17:54.169> town<00:17:54.350> so<00:17:54.620> it's<00:17:55.070> more<00:17:55.159> like<00:17:55.340> a<00:17:55.580> transfer 00:17:55.990 --> 00:17:56.000 align:start position:0% nice town so it's more like a transfer 00:17:56.000 --> 00:17:57.310 align:start position:0% nice town so it's more like a transfer with<00:17:56.149> someone<00:17:56.480> else<00:17:56.630> unless<00:17:56.840> you<00:17:57.169> will 00:17:57.310 --> 00:17:57.320 align:start position:0% with someone else unless you will 00:17:57.320 --> 00:17:59.620 align:start position:0% with someone else unless you will transfer<00:17:57.710> in<00:17:57.860> the<00:17:57.980> second<00:17:58.340> period<00:17:58.820> is<00:17:59.179> more<00:17:59.450> to 00:17:59.620 --> 00:17:59.630 align:start position:0% transfer in the second period is more to 00:17:59.630 --> 00:18:10.670 align:start position:0% transfer in the second period is more to the<00:18:00.409> yellow<00:18:00.620> to<00:18:00.830> Charles 00:18:10.670 --> 00:18:10.680 align:start position:0% 00:18:10.680 --> 00:18:17.150 align:start position:0% [Applause]