WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.980 align:start position:0% [Applause] 00:00:12.980 --> 00:00:12.990 align:start position:0% 00:00:12.990 --> 00:00:14.700 align:start position:0% area 00:00:14.700 --> 00:00:14.710 align:start position:0% area 00:00:14.710 --> 00:00:17.460 align:start position:0% area I'm<00:00:15.100> here<00:00:15.370> to<00:00:15.700> judge<00:00:16.330> us<00:00:16.510> in<00:00:16.720> Germany<00:00:17.200> in<00:00:17.320> three 00:00:17.460 --> 00:00:17.470 align:start position:0% I'm here to judge us in Germany in three 00:00:17.470 --> 00:00:24.660 align:start position:0% I'm here to judge us in Germany in three quarters<00:00:21.300> listen<00:00:22.300> I'm<00:00:22.779> once<00:00:23.110> up<00:00:23.320> and<00:00:23.670> now 00:00:24.660 --> 00:00:24.670 align:start position:0% quarters listen I'm once up and now 00:00:24.670 --> 00:00:27.240 align:start position:0% quarters listen I'm once up and now working<00:00:25.090> for<00:00:25.119> nuns<00:00:25.600> I<00:00:25.869> mean<00:00:26.230> to<00:00:26.380> say<00:00:26.590> is<00:00:26.950> in 00:00:27.240 --> 00:00:27.250 align:start position:0% working for nuns I mean to say is in 00:00:27.250 --> 00:00:30.330 align:start position:0% working for nuns I mean to say is in Krypton<00:00:27.610> community<00:00:28.090> in<00:00:28.390> Seoul<00:00:28.750> there<00:00:29.560> are<00:00:29.800> 70 00:00:30.330 --> 00:00:30.340 align:start position:0% Krypton community in Seoul there are 70 00:00:30.340 --> 00:00:32.870 align:start position:0% Krypton community in Seoul there are 70 people<00:00:31.090> all<00:00:31.300> living<00:00:31.570> and<00:00:31.840> working<00:00:32.020> together 00:00:32.870 --> 00:00:32.880 align:start position:0% people all living and working together 00:00:32.880 --> 00:00:37.050 align:start position:0% people all living and working together so<00:00:33.880> and<00:00:34.720> recently<00:00:35.470> I<00:00:35.860> like<00:00:36.130> the<00:00:36.250> polyster<00:00:36.760> and 00:00:37.050 --> 00:00:37.060 align:start position:0% so and recently I like the polyster and 00:00:37.060 --> 00:00:40.530 align:start position:0% so and recently I like the polyster and recently<00:00:37.870> I<00:00:38.200> organized<00:00:38.739> a<00:00:39.090> local<00:00:40.090> communities 00:00:40.530 --> 00:00:40.540 align:start position:0% recently I organized a local communities 00:00:40.540 --> 00:00:44.540 align:start position:0% recently I organized a local communities Developer<00:00:41.140> Conference<00:00:41.380> which<00:00:41.860> name<00:00:42.070> is<00:00:43.500> so 00:00:44.540 --> 00:00:44.550 align:start position:0% Developer Conference which name is so 00:00:44.550 --> 00:00:49.950 align:start position:0% Developer Conference which name is so first<00:00:46.170> 70<00:00:47.170> people<00:00:47.560> in<00:00:47.710> nuns<00:00:48.390> are<00:00:49.390> all<00:00:49.630> the 00:00:49.950 --> 00:00:49.960 align:start position:0% first 70 people in nuns are all the 00:00:49.960 --> 00:00:53.520 align:start position:0% first 70 people in nuns are all the crypto<00:00:50.470> related<00:00:51.010> people<00:00:51.280> but<00:00:52.350> including<00:00:53.350> me 00:00:53.520 --> 00:00:53.530 align:start position:0% crypto related people but including me 00:00:53.530 --> 00:00:57.120 align:start position:0% crypto related people but including me we<00:00:54.220> did<00:00:54.640> not<00:00:54.760> use<00:00:55.030> venomous<00:00:55.510> anti<00:00:55.960> to<00:00:56.770> split 00:00:57.120 --> 00:00:57.130 align:start position:0% we did not use venomous anti to split 00:00:57.130 --> 00:00:58.940 align:start position:0% we did not use venomous anti to split the<00:00:57.310> peel<00:00:57.580> after<00:00:58.180> we<00:00:58.270> have<00:00:58.450> dinner<00:00:58.660> together 00:00:58.940 --> 00:00:58.950 align:start position:0% the peel after we have dinner together 00:00:58.950 --> 00:01:01.500 align:start position:0% the peel after we have dinner together it's<00:00:59.950> because<00:01:00.430> it<00:01:00.610> is<00:01:00.700> really<00:01:01.000> hard<00:01:01.300> to<00:01:01.360> find 00:01:01.500 --> 00:01:01.510 align:start position:0% it's because it is really hard to find 00:01:01.510 --> 00:01:05.060 align:start position:0% it's because it is really hard to find my<00:01:01.900> friend<00:01:02.350> using<00:01:02.680> animal<00:01:02.980> skin<00:01:03.160> hi<00:01:03.509> so 00:01:05.060 --> 00:01:05.070 align:start position:0% my friend using animal skin hi so 00:01:05.070 --> 00:01:08.100 align:start position:0% my friend using animal skin hi so actually<00:01:06.070> we<00:01:06.220> use<00:01:06.460> in<00:01:06.939> actually<00:01:07.600> in<00:01:07.659> Korea<00:01:07.900> we 00:01:08.100 --> 00:01:08.110 align:start position:0% actually we use in actually in Korea we 00:01:08.110 --> 00:01:10.980 align:start position:0% actually we use in actually in Korea we use<00:01:08.290> compain<00:01:09.159> which<00:01:09.610> is<00:01:09.759> equivalent<00:01:10.119> to<00:01:10.420> venmo 00:01:10.980 --> 00:01:10.990 align:start position:0% use compain which is equivalent to venmo 00:01:10.990 --> 00:01:14.760 align:start position:0% use compain which is equivalent to venmo to<00:01:11.950> split<00:01:12.220> the<00:01:12.369> bill<00:01:12.900> because<00:01:13.900> those<00:01:14.230> services 00:01:14.760 --> 00:01:14.770 align:start position:0% to split the bill because those services 00:01:14.770 --> 00:01:17.220 align:start position:0% to split the bill because those services are<00:01:15.130> providing<00:01:15.760> the<00:01:15.940> features<00:01:16.420> to<00:01:16.870> find<00:01:16.900> my 00:01:17.220 --> 00:01:17.230 align:start position:0% are providing the features to find my 00:01:17.230 --> 00:01:22.170 align:start position:0% are providing the features to find my friend<00:01:18.130> using<00:01:18.580> the<00:01:18.700> messenger<00:01:19.090> feature<00:01:21.180> so 00:01:22.170 --> 00:01:22.180 align:start position:0% friend using the messenger feature so 00:01:22.180 --> 00:01:26.670 align:start position:0% friend using the messenger feature so however<00:01:22.390> as<00:01:22.840> the<00:01:23.050> ux<00:01:23.350> t<00:01:24.250> acquaintances<00:01:25.350> is<00:01:26.350> to 00:01:26.670 --> 00:01:26.680 align:start position:0% however as the ux t acquaintances is to 00:01:26.680 --> 00:01:28.920 align:start position:0% however as the ux t acquaintances is to coming<00:01:27.010> to<00:01:27.250> institutes<00:01:28.030> and<00:01:28.390> mike<00:01:28.570> refer<00:01:28.870> to 00:01:28.920 --> 00:01:28.930 align:start position:0% coming to institutes and mike refer to 00:01:28.930 --> 00:01:34.410 align:start position:0% coming to institutes and mike refer to my<00:01:29.110> friend<00:01:29.620> using<00:01:30.280> darkness<00:01:31.500> so<00:01:32.940> how<00:01:33.940> many<00:01:34.000> are 00:01:34.410 --> 00:01:34.420 align:start position:0% my friend using darkness so how many are 00:01:34.420 --> 00:01:37.830 align:start position:0% my friend using darkness so how many are using<00:01:34.810> unison<00:01:36.060> there<00:01:37.060> are<00:01:37.210> so<00:01:37.450> many<00:01:37.570> people 00:01:37.830 --> 00:01:37.840 align:start position:0% using unison there are so many people 00:01:37.840 --> 00:01:41.910 align:start position:0% using unison there are so many people are<00:01:38.050> using<00:01:38.170> illness<00:01:38.650> then<00:01:40.140> how<00:01:41.140> many<00:01:41.200> has 00:01:41.910 --> 00:01:41.920 align:start position:0% are using illness then how many has 00:01:41.920 --> 00:01:44.060 align:start position:0% are using illness then how many has states<00:01:42.250> to<00:01:42.430> use<00:01:42.460> in 00:01:44.060 --> 00:01:44.070 align:start position:0% states to use in 00:01:44.070 --> 00:01:50.070 align:start position:0% states to use in how<00:01:45.070> many<00:01:45.280> has<00:01:45.640> disease<00:01:46.030> PMS<00:01:46.600> is<00:01:47.280> um<00:01:48.330> yeah<00:01:49.330> not 00:01:50.070 --> 00:01:50.080 align:start position:0% how many has disease PMS is um yeah not 00:01:50.080 --> 00:01:53.720 align:start position:0% how many has disease PMS is um yeah not many<00:01:50.320> but<00:01:51.210> people<00:01:52.210> who<00:01:52.330> use<00:01:52.570> ENS<00:01:52.960> frequently 00:01:53.720 --> 00:01:53.730 align:start position:0% many but people who use ENS frequently 00:01:53.730 --> 00:01:57.180 align:start position:0% many but people who use ENS frequently definitely<00:01:54.730> feel<00:01:55.030> that<00:01:55.330> it<00:01:55.630> is<00:01:55.690> really<00:01:56.229> high 00:01:57.180 --> 00:01:57.190 align:start position:0% definitely feel that it is really high 00:01:57.190 --> 00:02:01.740 align:start position:0% definitely feel that it is really high release<00:01:57.960> so<00:01:58.960> if<00:01:59.830> I<00:02:00.160> know<00:02:00.220> your<00:02:00.729> illness<00:02:01.210> then<00:02:01.479> I 00:02:01.740 --> 00:02:01.750 align:start position:0% release so if I know your illness then I 00:02:01.750 --> 00:02:05.219 align:start position:0% release so if I know your illness then I can<00:02:02.140> very<00:02:02.500> easily<00:02:02.860> know<00:02:03.430> how<00:02:04.210> much<00:02:04.450> if<00:02:04.900> you 00:02:05.219 --> 00:02:05.229 align:start position:0% can very easily know how much if you 00:02:05.229 --> 00:02:08.340 align:start position:0% can very easily know how much if you have<00:02:05.500> and<00:02:05.940> how<00:02:06.940> much<00:02:07.150> die<00:02:07.510> you<00:02:07.810> have<00:02:08.050> learned 00:02:08.340 --> 00:02:08.350 align:start position:0% have and how much die you have learned 00:02:08.350 --> 00:02:12.210 align:start position:0% have and how much die you have learned from<00:02:08.470> me<00:02:08.740> right<00:02:09.100> now<00:02:09.160> or<00:02:09.759> even<00:02:10.539> how<00:02:11.380> much<00:02:11.680> you 00:02:12.210 --> 00:02:12.220 align:start position:0% from me right now or even how much you 00:02:12.220 --> 00:02:15.110 align:start position:0% from me right now or even how much you got<00:02:12.810> liquidated<00:02:13.810> from<00:02:14.260> the<00:02:14.410> main<00:02:14.560> renowned 00:02:15.110 --> 00:02:15.120 align:start position:0% got liquidated from the main renowned 00:02:15.120 --> 00:02:17.490 align:start position:0% got liquidated from the main renowned biases<00:02:16.120> type<00:02:16.360> in<00:02:16.570> your<00:02:16.690> ears<00:02:16.989> into<00:02:17.410> the 00:02:17.490 --> 00:02:17.500 align:start position:0% biases type in your ears into the 00:02:17.500 --> 00:02:24.270 align:start position:0% biases type in your ears into the industry<00:02:18.450> so<00:02:21.390> so<00:02:22.390> if<00:02:22.750> they're<00:02:22.930> 9<00:02:23.170> 3<00:02:23.470> 4<00:02:23.680> s<00:02:23.800> comes 00:02:24.270 --> 00:02:24.280 align:start position:0% industry so so if they're 9 3 4 s comes 00:02:24.280 --> 00:02:27.630 align:start position:0% industry so so if they're 9 3 4 s comes up<00:02:24.520> as<00:02:24.730> a<00:02:24.970> lightweight<00:02:26.130> pirate<00:02:27.130> renters<00:02:27.520> of 00:02:27.630 --> 00:02:27.640 align:start position:0% up as a lightweight pirate renters of 00:02:27.640 --> 00:02:31.860 align:start position:0% up as a lightweight pirate renters of solution<00:02:28.260> so<00:02:29.760> which<00:02:30.760> place<00:02:31.060> figure<00:02:31.390> out<00:02:31.540> this 00:02:31.860 --> 00:02:31.870 align:start position:0% solution so which place figure out this 00:02:31.870 --> 00:02:37.759 align:start position:0% solution so which place figure out this is<00:02:32.110> either<00:02:32.739> penetrate<00:02:33.370> course<00:02:33.640> knees 00:02:37.759 --> 00:02:37.769 align:start position:0% 00:02:37.769 --> 00:02:42.869 align:start position:0% it's<00:02:38.769> a<00:02:38.950> kind<00:02:39.220> of<00:02:39.250> Harry<00:02:39.790> Potter<00:02:40.090> stuff<00:02:41.879> he 00:02:42.869 --> 00:02:42.879 align:start position:0% it's a kind of Harry Potter stuff he 00:02:42.879 --> 00:02:46.319 align:start position:0% it's a kind of Harry Potter stuff he said<00:02:43.150> get<00:02:43.900> to<00:02:44.079> into<00:02:44.409> the<00:02:44.530> medical<00:02:45.040> work<00:02:45.329> where 00:02:46.319 --> 00:02:46.329 align:start position:0% said get to into the medical work where 00:02:46.329 --> 00:02:49.649 align:start position:0% said get to into the medical work where we<00:02:46.360> can<00:02:46.659> use<00:02:46.840> them<00:02:47.079> people<00:02:47.439> in<00:02:47.560> Moscow<00:02:48.659> so 00:02:49.649 --> 00:02:49.659 align:start position:0% we can use them people in Moscow so 00:02:49.659 --> 00:02:53.490 align:start position:0% we can use them people in Moscow so let's<00:02:50.019> see<00:02:50.170> how<00:02:50.319> it<00:02:50.470> practiced<00:02:51.870> the<00:02:52.870> users<00:02:53.230> can 00:02:53.490 --> 00:02:53.500 align:start position:0% let's see how it practiced the users can 00:02:53.500 --> 00:02:55.860 align:start position:0% let's see how it practiced the users can can<00:02:53.709> change<00:02:53.950> into<00:02:54.220> the<00:02:54.310> masker<00:02:54.700> world<00:02:54.970> by 00:02:55.860 --> 00:02:55.870 align:start position:0% can change into the masker world by 00:02:55.870 --> 00:02:58.979 align:start position:0% can change into the masker world by depositing<00:02:56.530> your<00:02:56.560> stranded<00:02:57.189> tapas<00:02:57.579> and<00:02:57.989> then 00:02:58.979 --> 00:02:58.989 align:start position:0% depositing your stranded tapas and then 00:02:58.989 --> 00:03:02.399 align:start position:0% depositing your stranded tapas and then they<00:02:59.980> go<00:03:00.220> into<00:03:00.430> the<00:03:00.609> medical<00:03:01.030> world<00:03:01.180> and<00:03:01.989> using 00:03:02.399 --> 00:03:02.409 align:start position:0% they go into the medical world and using 00:03:02.409 --> 00:03:04.319 align:start position:0% they go into the medical world and using the<00:03:02.560> mobile<00:03:02.739> in<00:03:03.010> football<00:03:03.430> they<00:03:03.970> can<00:03:04.180> make 00:03:04.319 --> 00:03:04.329 align:start position:0% the mobile in football they can make 00:03:04.329 --> 00:03:06.500 align:start position:0% the mobile in football they can make some<00:03:04.569> confidential<00:03:05.409> tradition<00:03:05.920> each<00:03:06.069> other 00:03:06.500 --> 00:03:06.510 align:start position:0% some confidential tradition each other 00:03:06.510 --> 00:03:10.289 align:start position:0% some confidential tradition each other and<00:03:07.510> the<00:03:07.720> relator<00:03:08.170> can<00:03:09.010> create<00:03:09.670> the<00:03:09.940> mobile 00:03:10.289 --> 00:03:10.299 align:start position:0% and the relator can create the mobile 00:03:10.299 --> 00:03:12.960 align:start position:0% and the relator can create the mobile transactions<00:03:11.109> and<00:03:11.430> submit<00:03:12.430> that<00:03:12.579> rejection 00:03:12.960 --> 00:03:12.970 align:start position:0% transactions and submit that rejection 00:03:12.970 --> 00:03:17.069 align:start position:0% transactions and submit that rejection to<00:03:13.269> the<00:03:14.250> interview<00:03:15.250> using<00:03:15.909> secure<00:03:16.720> mobile<00:03:16.930> app 00:03:17.069 --> 00:03:17.079 align:start position:0% to the interview using secure mobile app 00:03:17.079 --> 00:03:20.069 align:start position:0% to the interview using secure mobile app and<00:03:17.349> the<00:03:17.760> important<00:03:18.760> thing<00:03:18.819> is<00:03:19.209> that<00:03:19.239> the 00:03:20.069 --> 00:03:20.079 align:start position:0% and the important thing is that the 00:03:20.079 --> 00:03:26.970 align:start position:0% and the important thing is that the relay<00:03:20.590> also<00:03:21.040> aggregates<00:03:21.989> the<00:03:22.989> fees<00:03:23.290> so<00:03:25.980> okay 00:03:26.970 --> 00:03:26.980 align:start position:0% relay also aggregates the fees so okay 00:03:26.980 --> 00:03:31.379 align:start position:0% relay also aggregates the fees so okay this<00:03:27.430> is<00:03:27.579> just<00:03:28.019> and<00:03:29.019> by<00:03:29.560> the<00:03:29.620> way<00:03:30.060> the<00:03:31.060> users 00:03:31.379 --> 00:03:31.389 align:start position:0% this is just and by the way the users 00:03:31.389 --> 00:03:34.229 align:start position:0% this is just and by the way the users can<00:03:31.989> we<00:03:32.799> throw<00:03:32.980> their<00:03:33.250> money<00:03:33.370> back<00:03:33.939> to<00:03:34.150> the 00:03:34.229 --> 00:03:34.239 align:start position:0% can we throw their money back to the 00:03:34.239 --> 00:03:37.369 align:start position:0% can we throw their money back to the mobile<00:03:34.420> world<00:03:35.010> submitting<00:03:36.010> a<00:03:36.159> valid<00:03:36.579> proof 00:03:37.369 --> 00:03:37.379 align:start position:0% mobile world submitting a valid proof 00:03:37.379 --> 00:03:40.319 align:start position:0% mobile world submitting a valid proof this<00:03:38.379> is<00:03:38.439> just<00:03:38.859> a<00:03:39.010> brief<00:03:39.400> explanation<00:03:39.819> about 00:03:40.319 --> 00:03:40.329 align:start position:0% this is just a brief explanation about 00:03:40.329 --> 00:03:43.199 align:start position:0% this is just a brief explanation about how<00:03:40.870> it<00:03:41.500> breaks<00:03:41.769> and<00:03:42.099> now<00:03:42.609> we<00:03:42.669> are<00:03:42.910> going<00:03:43.120> to 00:03:43.199 --> 00:03:43.209 align:start position:0% how it breaks and now we are going to 00:03:43.209 --> 00:03:46.830 align:start position:0% how it breaks and now we are going to talk<00:03:43.419> about<00:03:43.470> the<00:03:44.470> deep<00:03:44.940> technical<00:03:45.940> details 00:03:46.830 --> 00:03:46.840 align:start position:0% talk about the deep technical details 00:03:46.840 --> 00:03:51.920 align:start position:0% talk about the deep technical details about<00:03:47.109> people<00:03:47.799> either<00:03:48.220> in<00:03:48.370> three<00:03:48.940> quarters<00:03:50.819> so 00:03:51.920 --> 00:03:51.930 align:start position:0% about people either in three quarters so 00:03:51.930 --> 00:03:55.830 align:start position:0% about people either in three quarters so the<00:03:52.930> first<00:03:53.260> priority<00:03:53.530> of<00:03:53.889> the<00:03:54.159> design<00:03:54.519> was<00:03:54.840> how 00:03:55.830 --> 00:03:55.840 align:start position:0% the first priority of the design was how 00:03:55.840 --> 00:03:59.849 align:start position:0% the first priority of the design was how much<00:03:56.139> dick<00:03:56.500> is<00:03:56.650> nurse<00:03:56.889> friendly<00:03:57.489> and<00:03:58.859> the 00:03:59.849 --> 00:03:59.859 align:start position:0% much dick is nurse friendly and the 00:03:59.859 --> 00:04:02.039 align:start position:0% much dick is nurse friendly and the second<00:04:00.340> one<00:04:00.489> was<00:04:00.699> how<00:04:01.060> much<00:04:01.269> business 00:04:02.039 --> 00:04:02.049 align:start position:0% second one was how much business 00:04:02.049 --> 00:04:06.479 align:start position:0% second one was how much business friendliness<00:04:03.090> and<00:04:04.090> the<00:04:04.150> third<00:04:04.510> one<00:04:04.690> was<00:04:05.489> mr. 00:04:06.479 --> 00:04:06.489 align:start position:0% friendliness and the third one was mr. 00:04:06.489 --> 00:04:11.430 align:start position:0% friendliness and the third one was mr. friendly<00:04:06.909> is<00:04:07.120> so<00:04:08.400> I'd<00:04:09.400> like<00:04:09.669> to<00:04:10.349> employ<00:04:11.349> I 00:04:11.430 --> 00:04:11.440 align:start position:0% friendly is so I'd like to employ I 00:04:11.440 --> 00:04:13.800 align:start position:0% friendly is so I'd like to employ I started<00:04:12.190> to<00:04:12.280> use<00:04:12.459> the<00:04:12.609> me<00:04:12.760> more<00:04:12.940> on<00:04:13.569> first 00:04:13.800 --> 00:04:13.810 align:start position:0% started to use the me more on first 00:04:13.810 --> 00:04:16.589 align:start position:0% started to use the me more on first because<00:04:14.349> removing<00:04:15.250> one<00:04:15.609> is<00:04:15.849> the<00:04:16.180> one<00:04:16.329> of<00:04:16.479> the 00:04:16.589 --> 00:04:16.599 align:start position:0% because removing one is the one of the 00:04:16.599 --> 00:04:19.259 align:start position:0% because removing one is the one of the lightest<00:04:16.959> part<00:04:17.380> of<00:04:17.709> building<00:04:18.370> comprehensive 00:04:19.259 --> 00:04:19.269 align:start position:0% lightest part of building comprehensive 00:04:19.269 --> 00:04:22.649 align:start position:0% lightest part of building comprehensive transition<00:04:19.829> so<00:04:20.849> it's<00:04:21.849> transaction<00:04:22.479> of 00:04:22.649 --> 00:04:22.659 align:start position:0% transition so it's transaction of 00:04:22.659 --> 00:04:27.810 align:start position:0% transition so it's transaction of consists<00:04:23.470> of<00:04:23.710> a<00:04:23.949> randomness<00:04:24.669> and<00:04:24.909> a<00:04:25.419> value<00:04:26.820> and 00:04:27.810 --> 00:04:27.820 align:start position:0% consists of a randomness and a value and 00:04:27.820 --> 00:04:32.100 align:start position:0% consists of a randomness and a value and it<00:04:28.180> expresses<00:04:28.659> the<00:04:29.440> TSO<00:04:30.039> as<00:04:30.250> a<00:04:30.280> point<00:04:30.820> on<00:04:31.150> deal 00:04:32.100 --> 00:04:32.110 align:start position:0% it expresses the TSO as a point on deal 00:04:32.110 --> 00:04:35.909 align:start position:0% it expresses the TSO as a point on deal on<00:04:32.349> the<00:04:32.710> other<00:04:32.919> two<00:04:33.190> card<00:04:33.900> using<00:04:34.900> a<00:04:35.020> pistol 00:04:35.909 --> 00:04:35.919 align:start position:0% on the other two card using a pistol 00:04:35.919 --> 00:04:39.379 align:start position:0% on the other two card using a pistol movement<00:04:36.280> so<00:04:36.760> it<00:04:37.479> can<00:04:37.750> hide<00:04:38.020> those<00:04:38.260> secrets 00:04:39.379 --> 00:04:39.389 align:start position:0% movement so it can hide those secrets 00:04:39.389 --> 00:04:42.240 align:start position:0% movement so it can hide those secrets while<00:04:40.389> it<00:04:40.780> allows<00:04:41.139> the<00:04:41.409> homework 00:04:42.240 --> 00:04:42.250 align:start position:0% while it allows the homework 00:04:42.250 --> 00:04:45.960 align:start position:0% while it allows the homework culturally<00:04:42.700> Asian<00:04:43.030> so<00:04:43.900> this<00:04:44.500> is<00:04:44.770> hidden<00:04:45.580> like 00:04:45.960 --> 00:04:45.970 align:start position:0% culturally Asian so this is hidden like 00:04:45.970 --> 00:04:48.870 align:start position:0% culturally Asian so this is hidden like the<00:04:46.450> same<00:04:46.720> IDenticard<00:04:47.440> I<00:04:47.650> added<00:04:48.280> to<00:04:48.400> point<00:04:48.670> of 00:04:48.870 --> 00:04:48.880 align:start position:0% the same IDenticard I added to point of 00:04:48.880 --> 00:04:54.330 align:start position:0% the same IDenticard I added to point of the<00:04:48.970> curve<00:04:51.210> therefore<00:04:52.500> using<00:04:53.500> so<00:04:53.800> imperfect 00:04:54.330 --> 00:04:54.340 align:start position:0% the curve therefore using so imperfect 00:04:54.340 --> 00:04:57.120 align:start position:0% the curve therefore using so imperfect hiding<00:04:54.670> features<00:04:55.180> we<00:04:55.840> can<00:04:56.050> verify<00:04:56.290> that<00:04:56.800> the 00:04:57.120 --> 00:04:57.130 align:start position:0% hiding features we can verify that the 00:04:57.130 --> 00:05:01.080 align:start position:0% hiding features we can verify that the sum<00:04:57.460> of<00:04:57.730> the<00:04:58.180> input<00:04:58.810> values<00:04:59.350> and<00:04:59.530> the<00:05:00.040> sum<00:05:00.910> of 00:05:01.080 --> 00:05:01.090 align:start position:0% sum of the input values and the sum of 00:05:01.090 --> 00:05:05.370 align:start position:0% sum of the input values and the sum of the<00:05:01.300> outfit<00:05:01.810> is<00:05:02.050> equals<00:05:02.880> so<00:05:03.880> you<00:05:04.750> can<00:05:04.960> see<00:05:05.170> that 00:05:05.370 --> 00:05:05.380 align:start position:0% the outfit is equals so you can see that 00:05:05.380 --> 00:05:09.030 align:start position:0% the outfit is equals so you can see that the<00:05:05.590> coefficient<00:05:06.130> of<00:05:07.000> the<00:05:07.300> base<00:05:07.660> point<00:05:08.020> on<00:05:08.770> H 00:05:09.030 --> 00:05:09.040 align:start position:0% the coefficient of the base point on H 00:05:09.040 --> 00:05:16.470 align:start position:0% the coefficient of the base point on H equals<00:05:09.480> 0<00:05:10.480> becomes<00:05:11.410> zero<00:05:14.460> cost<00:05:15.460> only<00:05:15.880> so<00:05:16.270> we 00:05:16.470 --> 00:05:16.480 align:start position:0% equals 0 becomes zero cost only so we 00:05:16.480 --> 00:05:19.110 align:start position:0% equals 0 becomes zero cost only so we can<00:05:16.630> also<00:05:16.870> consider<00:05:17.260> a<00:05:17.590> prediction<00:05:18.430> using 00:05:19.110 --> 00:05:19.120 align:start position:0% can also consider a prediction using 00:05:19.120 --> 00:05:25.050 align:start position:0% can also consider a prediction using this<00:05:19.270> equation<00:05:22.500> but<00:05:23.500> it's<00:05:23.890> not<00:05:24.340> enough<00:05:24.760> to 00:05:25.050 --> 00:05:25.060 align:start position:0% this equation but it's not enough to 00:05:25.060 --> 00:05:29.870 align:start position:0% this equation but it's not enough to make<00:05:25.090> a<00:05:25.540> robust<00:05:25.960> condition<00:05:26.830> therefore<00:05:28.380> first 00:05:29.870 --> 00:05:29.880 align:start position:0% make a robust condition therefore first 00:05:29.880 --> 00:05:33.480 align:start position:0% make a robust condition therefore first because<00:05:30.880> the<00:05:31.180> zero<00:05:31.510> sum<00:05:31.830> replication<00:05:32.830> works 00:05:33.480 --> 00:05:33.490 align:start position:0% because the zero sum replication works 00:05:33.490 --> 00:05:36.990 align:start position:0% because the zero sum replication works on<00:05:33.910> a<00:05:34.480> cyclic<00:05:35.110> group<00:05:35.140> to<00:05:36.100> prevent<00:05:36.610> the<00:05:36.820> off 00:05:36.990 --> 00:05:37.000 align:start position:0% on a cyclic group to prevent the off 00:05:37.000 --> 00:05:40.230 align:start position:0% on a cyclic group to prevent the off wall<00:05:37.450> and<00:05:37.750> the<00:05:38.320> underflow<00:05:39.010> inside<00:05:39.850> the<00:05:40.060> home 00:05:40.230 --> 00:05:40.240 align:start position:0% wall and the underflow inside the home 00:05:40.240 --> 00:05:41.490 align:start position:0% wall and the underflow inside the home were<00:05:40.450> free<00:05:40.630> consulation 00:05:41.490 --> 00:05:41.500 align:start position:0% were free consulation 00:05:41.500 --> 00:05:44.250 align:start position:0% were free consulation we<00:05:41.950> need<00:05:42.130> to<00:05:42.280> restrict<00:05:42.669> the<00:05:43.030> range<00:05:43.690> of<00:05:44.020> the 00:05:44.250 --> 00:05:44.260 align:start position:0% we need to restrict the range of the 00:05:44.260 --> 00:05:51.110 align:start position:0% we need to restrict the range of the values<00:05:44.440> inside<00:05:45.280> the<00:05:45.340> check<00:05:46.090> piezo<00:05:49.050> and 00:05:51.110 --> 00:05:51.120 align:start position:0% values inside the check piezo and 00:05:51.120 --> 00:05:54.930 align:start position:0% values inside the check piezo and secondly<00:05:52.120> we<00:05:52.419> also<00:05:52.660> add<00:05:53.020> some<00:05:53.260> metadata<00:05:53.820> in<00:05:54.820> a 00:05:54.930 --> 00:05:54.940 align:start position:0% secondly we also add some metadata in a 00:05:54.940 --> 00:05:58.590 align:start position:0% secondly we also add some metadata in a marquis<00:05:55.320> we<00:05:56.320> can't<00:05:56.650> we<00:05:56.890> concatenate<00:05:57.300> the<00:05:58.300> es 00:05:58.590 --> 00:05:58.600 align:start position:0% marquis we can't we concatenate the es 00:05:58.600 --> 00:06:00.480 align:start position:0% marquis we can't we concatenate the es to<00:05:58.840> any<00:05:58.990> address<00:05:59.200> of<00:05:59.530> the<00:05:59.860> topic<00:06:00.340> we 00:06:00.480 --> 00:06:00.490 align:start position:0% to any address of the topic we 00:06:00.490 --> 00:06:03.960 align:start position:0% to any address of the topic we understand<00:06:01.060> and<00:06:01.440> expiration<00:06:02.440> time<00:06:03.010> so<00:06:03.760> the 00:06:03.960 --> 00:06:03.970 align:start position:0% understand and expiration time so the 00:06:03.970 --> 00:06:05.460 align:start position:0% understand and expiration time so the expiration<00:06:04.330> time<00:06:04.780> means<00:06:05.050> that<00:06:05.140> the 00:06:05.460 --> 00:06:05.470 align:start position:0% expiration time means that the 00:06:05.470 --> 00:06:08.280 align:start position:0% expiration time means that the contractor<00:06:06.100> contract<00:06:06.550> will<00:06:06.760> not<00:06:06.790> accept<00:06:07.510> if 00:06:08.280 --> 00:06:08.290 align:start position:0% contractor contract will not accept if 00:06:08.290 --> 00:06:11.550 align:start position:0% contractor contract will not accept if the<00:06:08.580> block<00:06:09.580> number<00:06:09.790> exists<00:06:10.630> expiration 00:06:11.550 --> 00:06:11.560 align:start position:0% the block number exists expiration 00:06:11.560 --> 00:06:15.600 align:start position:0% the block number exists expiration hunter<00:06:12.419> and<00:06:13.419> finally<00:06:14.229> to<00:06:14.410> make<00:06:14.560> sure<00:06:14.890> this 00:06:15.600 --> 00:06:15.610 align:start position:0% hunter and finally to make sure this 00:06:15.610 --> 00:06:18.480 align:start position:0% hunter and finally to make sure this transaction<00:06:16.360> is<00:06:16.800> confirmed<00:06:17.800> by<00:06:17.830> the<00:06:18.010> pool 00:06:18.480 --> 00:06:18.490 align:start position:0% transaction is confirmed by the pool 00:06:18.490 --> 00:06:21.510 align:start position:0% transaction is confirmed by the pool party<00:06:18.940> we<00:06:19.240> as<00:06:19.479> a<00:06:19.530> snore<00:06:20.530> signature<00:06:21.190> by<00:06:21.460> the 00:06:21.510 --> 00:06:21.520 align:start position:0% party we as a snore signature by the 00:06:21.520 --> 00:06:27.210 align:start position:0% party we as a snore signature by the sender<00:06:22.419> and<00:06:22.450> the<00:06:22.630> recipient<00:06:25.229> but<00:06:26.229> the<00:06:26.620> problem 00:06:27.210 --> 00:06:27.220 align:start position:0% sender and the recipient but the problem 00:06:27.220 --> 00:06:30.659 align:start position:0% sender and the recipient but the problem is<00:06:27.370> that<00:06:27.450> actually<00:06:28.450> is<00:06:28.750> not<00:06:29.550> preventing<00:06:30.550> the 00:06:30.659 --> 00:06:30.669 align:start position:0% is that actually is not preventing the 00:06:30.669 --> 00:06:33.390 align:start position:0% is that actually is not preventing the tracking<00:06:31.000> of<00:06:31.360> the<00:06:31.419> transition<00:06:32.350> flow<00:06:32.500> so 00:06:33.390 --> 00:06:33.400 align:start position:0% tracking of the transition flow so 00:06:33.400 --> 00:06:36.690 align:start position:0% tracking of the transition flow so actually<00:06:34.240> green<00:06:34.570> which<00:06:35.080> is<00:06:35.260> the<00:06:35.500> most<00:06:35.800> popular 00:06:36.690 --> 00:06:36.700 align:start position:0% actually green which is the most popular 00:06:36.700 --> 00:06:39.120 align:start position:0% actually green which is the most popular importantly<00:06:37.690> implementation<00:06:38.530> see<00:06:38.710> crystal 00:06:39.120 --> 00:06:39.130 align:start position:0% importantly implementation see crystal 00:06:39.130 --> 00:06:41.730 align:start position:0% importantly implementation see crystal privacy<00:06:39.700> by<00:06:40.330> having<00:06:40.720> no<00:06:40.960> account<00:06:41.410> and 00:06:41.730 --> 00:06:41.740 align:start position:0% privacy by having no account and 00:06:41.740 --> 00:06:43.510 align:start position:0% privacy by having no account and contouring 00:06:43.510 --> 00:06:43.520 align:start position:0% contouring 00:06:43.520 --> 00:06:46.809 align:start position:0% contouring in<00:06:43.759> on<00:06:44.389> interview<00:06:45.110> we<00:06:45.319> can<00:06:45.590> not<00:06:45.860> prevent<00:06:46.280> the 00:06:46.809 --> 00:06:46.819 align:start position:0% in on interview we can not prevent the 00:06:46.819 --> 00:06:54.210 align:start position:0% in on interview we can not prevent the track<00:06:47.660> of<00:06:47.900> the<00:06:48.199> change<00:06:49.190> in<00:06:49.460> RAM<00:06:50.259> so<00:06:53.199> therefore 00:06:54.210 --> 00:06:54.220 align:start position:0% track of the change in RAM so therefore 00:06:54.220 --> 00:06:57.790 align:start position:0% track of the change in RAM so therefore ninety<00:06:55.220> three<00:06:55.340> quarters<00:06:55.819> uses<00:06:56.389> C<00:06:57.199> caches 00:06:57.790 --> 00:06:57.800 align:start position:0% ninety three quarters uses C caches 00:06:57.800 --> 00:07:00.939 align:start position:0% ninety three quarters uses C caches commitment<00:06:58.610> only<00:06:58.849> para<00:06:59.120> scheme<00:06:59.539> to<00:07:00.470> hide<00:07:00.710> the 00:07:00.939 --> 00:07:00.949 align:start position:0% commitment only para scheme to hide the 00:07:00.949 --> 00:07:05.170 align:start position:0% commitment only para scheme to hide the input<00:07:01.430> input<00:07:02.060> CSS<00:07:03.400> so<00:07:04.400> with<00:07:04.639> the<00:07:04.759> treatment 00:07:05.170 --> 00:07:05.180 align:start position:0% input input CSS so with the treatment 00:07:05.180 --> 00:07:08.620 align:start position:0% input input CSS so with the treatment only<00:07:05.389> price<00:07:05.599> in<00:07:06.520> suggest<00:07:07.520> nurse<00:07:07.729> allow<00:07:08.060> us<00:07:08.330> to 00:07:08.620 --> 00:07:08.630 align:start position:0% only price in suggest nurse allow us to 00:07:08.630 --> 00:07:12.070 align:start position:0% only price in suggest nurse allow us to generate<00:07:09.169> a<00:07:09.440> an<00:07:10.310> inclusive<00:07:10.819> proof<00:07:11.270> without 00:07:12.070 --> 00:07:12.080 align:start position:0% generate a an inclusive proof without 00:07:12.080 --> 00:07:16.270 align:start position:0% generate a an inclusive proof without redoing<00:07:12.380> the<00:07:12.800> commitment<00:07:13.430> and<00:07:14.620> also<00:07:15.620> prevent 00:07:16.270 --> 00:07:16.280 align:start position:0% redoing the commitment and also prevent 00:07:16.280 --> 00:07:19.240 align:start position:0% redoing the commitment and also prevent the<00:07:16.400> double<00:07:17.169> also<00:07:18.169> prevent<00:07:18.860> the<00:07:18.949> double 00:07:19.240 --> 00:07:19.250 align:start position:0% the double also prevent the double 00:07:19.250 --> 00:07:21.640 align:start position:0% the double also prevent the double spending<00:07:19.639> by<00:07:19.909> using<00:07:20.810> the<00:07:21.080> knowledge<00:07:21.289> wire 00:07:21.640 --> 00:07:21.650 align:start position:0% spending by using the knowledge wire 00:07:21.650 --> 00:07:24.909 align:start position:0% spending by using the knowledge wire which<00:07:22.220> is<00:07:22.810> deterministically<00:07:23.810> derived<00:07:24.590> from 00:07:24.909 --> 00:07:24.919 align:start position:0% which is deterministically derived from 00:07:24.919 --> 00:07:33.520 align:start position:0% which is deterministically derived from the<00:07:25.220> commitment<00:07:29.349> finally<00:07:30.349> so<00:07:30.880> we<00:07:32.139> append<00:07:33.139> two 00:07:33.520 --> 00:07:33.530 align:start position:0% the commitment finally so we append two 00:07:33.530 --> 00:07:38.040 align:start position:0% the commitment finally so we append two more<00:07:33.949> CK<00:07:34.430> start<00:07:34.789> with<00:07:35.650> the<00:07:36.650> first<00:07:36.919> one<00:07:37.099> is 00:07:38.040 --> 00:07:38.050 align:start position:0% more CK start with the first one is 00:07:38.050 --> 00:07:40.659 align:start position:0% more CK start with the first one is impressive<00:07:39.050> proofs<00:07:39.289> of<00:07:39.470> the<00:07:39.650> span<00:07:40.009> test<00:07:40.340> with 00:07:40.659 --> 00:07:40.669 align:start position:0% impressive proofs of the span test with 00:07:40.669 --> 00:07:44.980 align:start position:0% impressive proofs of the span test with the<00:07:41.419> samples<00:07:41.810> of<00:07:42.110> the<00:07:42.409> no<00:07:43.220> defiers<00:07:43.280> and<00:07:44.030> the 00:07:44.980 --> 00:07:44.990 align:start position:0% the samples of the no defiers and the 00:07:44.990 --> 00:07:47.249 align:start position:0% the samples of the no defiers and the second<00:07:45.380> is<00:07:45.590> that<00:07:45.860> the<00:07:46.400> middle<00:07:46.819> and<00:07:47.000> bottom 00:07:47.249 --> 00:07:47.259 align:start position:0% second is that the middle and bottom 00:07:47.259 --> 00:07:50.260 align:start position:0% second is that the middle and bottom because<00:07:48.259> it<00:07:48.380> is<00:07:48.409> because<00:07:48.860> we<00:07:49.310> hide<00:07:49.969> the 00:07:50.260 --> 00:07:50.270 align:start position:0% because it is because we hide the 00:07:50.270 --> 00:07:55.450 align:start position:0% because it is because we hide the impacts<00:07:51.110> of<00:07:51.259> area<00:07:51.620> so<00:07:51.889> if<00:07:52.479> not<00:07:53.919> isn't<00:07:54.919> not 00:07:55.450 --> 00:07:55.460 align:start position:0% impacts of area so if not isn't not 00:07:55.460 --> 00:07:58.689 align:start position:0% impacts of area so if not isn't not anymore<00:07:56.110> able<00:07:57.110> to<00:07:57.320> verify<00:07:57.710> the<00:07:58.039> removable 00:07:58.689 --> 00:07:58.699 align:start position:0% anymore able to verify the removable 00:07:58.699 --> 00:08:01.240 align:start position:0% anymore able to verify the removable using<00:07:59.180> the<00:07:59.270> homomorphic<00:07:59.840> calculation<00:08:00.590> so<00:08:01.070> we 00:08:01.240 --> 00:08:01.250 align:start position:0% using the homomorphic calculation so we 00:08:01.250 --> 00:08:04.270 align:start position:0% using the homomorphic calculation so we need<00:08:01.400> to<00:08:01.580> make<00:08:01.759> them<00:08:02.110> city<00:08:03.110> stars<00:08:03.409> proof<00:08:03.740> that 00:08:04.270 --> 00:08:04.280 align:start position:0% need to make them city stars proof that 00:08:04.280 --> 00:08:06.999 align:start position:0% need to make them city stars proof that just<00:08:05.030> guarantees<00:08:05.960> that<00:08:05.990> all<00:08:06.440> the<00:08:06.770> hidden 00:08:06.999 --> 00:08:07.009 align:start position:0% just guarantees that all the hidden 00:08:07.009 --> 00:08:10.029 align:start position:0% just guarantees that all the hidden values<00:08:07.520> are<00:08:07.849> following<00:08:08.449> the<00:08:08.750> removal<00:08:09.349> Ponte 00:08:10.029 --> 00:08:10.039 align:start position:0% values are following the removal Ponte 00:08:10.039 --> 00:08:18.040 align:start position:0% values are following the removal Ponte Preta<00:08:10.250> me<00:08:12.819> the<00:08:13.819> next<00:08:14.150> part<00:08:14.409> so<00:08:15.409> as<00:08:16.090> far<00:08:17.090> as<00:08:17.150> C 00:08:18.040 --> 00:08:18.050 align:start position:0% Preta me the next part so as far as C 00:08:18.050 --> 00:08:22.600 align:start position:0% Preta me the next part so as far as C cable<00:08:18.259> la<00:08:18.620> friendly<00:08:19.069> data<00:08:19.340> structure<00:08:21.610> I'm 00:08:22.600 --> 00:08:22.610 align:start position:0% cable la friendly data structure I'm 00:08:22.610 --> 00:08:25.870 align:start position:0% cable la friendly data structure I'm pure<00:08:23.569> top<00:08:23.900> purpose<00:08:24.620> virtual<00:08:25.280> mountain<00:08:25.460> range 00:08:25.870 --> 00:08:25.880 align:start position:0% pure top purpose virtual mountain range 00:08:25.880 --> 00:08:29.350 align:start position:0% pure top purpose virtual mountain range for<00:08:26.300> an<00:08:26.630> efficient<00:08:27.349> a<00:08:27.590> pen<00:08:28.340> on<00:08:28.610> mean<00:08:28.849> vertical 00:08:29.350 --> 00:08:29.360 align:start position:0% for an efficient a pen on mean vertical 00:08:29.360 --> 00:08:31.990 align:start position:0% for an efficient a pen on mean vertical tree<00:08:29.990> data<00:08:30.169> structure<00:08:30.680> and<00:08:30.860> green<00:08:31.699> is<00:08:31.819> now 00:08:31.990 --> 00:08:32.000 align:start position:0% tree data structure and green is now 00:08:32.000 --> 00:08:36.040 align:start position:0% tree data structure and green is now using<00:08:32.329> that<00:08:32.829> in<00:08:33.829> interview<00:08:34.250> 9<00:08:34.430> 3/4<00:08:35.029> it<00:08:35.270> uses<00:08:35.870> a 00:08:36.040 --> 00:08:36.050 align:start position:0% using that in interview 9 3/4 it uses a 00:08:36.050 --> 00:08:38.290 align:start position:0% using that in interview 9 3/4 it uses a slightly<00:08:36.529> tweaked<00:08:37.310> version<00:08:37.399> of<00:08:37.820> a 00:08:38.290 --> 00:08:38.300 align:start position:0% slightly tweaked version of a 00:08:38.300 --> 00:08:41.319 align:start position:0% slightly tweaked version of a recommendation<00:08:39.079> range<00:08:39.500> that<00:08:40.279> uses<00:08:40.700> elliptic 00:08:41.319 --> 00:08:41.329 align:start position:0% recommendation range that uses elliptic 00:08:41.329 --> 00:08:41.820 align:start position:0% recommendation range that uses elliptic curve 00:08:41.820 --> 00:08:41.830 align:start position:0% curve 00:08:41.830 --> 00:08:44.340 align:start position:0% curve -<00:08:41.919> repeat<00:08:42.219> -<00:08:42.279> but<00:08:43.149> to<00:08:43.539> compute<00:08:43.990> the<00:08:44.140> whole 00:08:44.340 --> 00:08:44.350 align:start position:0% - repeat - but to compute the whole 00:08:44.350 --> 00:08:49.259 align:start position:0% - repeat - but to compute the whole notes<00:08:45.510> so<00:08:47.190> most<00:08:48.190> of<00:08:48.339> all<00:08:48.490> in<00:08:48.730> Pearson 00:08:49.259 --> 00:08:49.269 align:start position:0% notes so most of all in Pearson 00:08:49.269 --> 00:08:51.509 align:start position:0% notes so most of all in Pearson replicants<00:08:50.140> arranged<00:08:50.410> every<00:08:50.890> knows<00:08:51.070> our 00:08:51.509 --> 00:08:51.519 align:start position:0% replicants arranged every knows our 00:08:51.519 --> 00:08:54.930 align:start position:0% replicants arranged every knows our every<00:08:51.970> note<00:08:52.690> is<00:08:52.930> the<00:08:53.260> point<00:08:53.589> on<00:08:53.920> the<00:08:53.980> baby<00:08:54.610> - 00:08:54.930 --> 00:08:54.940 align:start position:0% every note is the point on the baby - 00:08:54.940 --> 00:09:00.569 align:start position:0% every note is the point on the baby - current<00:08:55.510> so<00:08:56.410> we<00:08:56.860> calculate<00:08:57.490> the<00:08:58.180> lead<00:08:58.480> note<00:08:59.579> by 00:09:00.569 --> 00:09:00.579 align:start position:0% current so we calculate the lead note by 00:09:00.579 --> 00:09:03.660 align:start position:0% current so we calculate the lead note by the<00:09:00.610> scholar<00:09:01.230> multiplication<00:09:02.230> of<00:09:02.680> the<00:09:03.430> lip 00:09:03.660 --> 00:09:03.670 align:start position:0% the scholar multiplication of the lip 00:09:03.670 --> 00:09:08.220 align:start position:0% the scholar multiplication of the lip position<00:09:03.910> and<00:09:04.620> the<00:09:05.620> live<00:09:05.829> item<00:09:06.390> and<00:09:07.390> we 00:09:08.220 --> 00:09:08.230 align:start position:0% position and the live item and we 00:09:08.230 --> 00:09:11.370 align:start position:0% position and the live item and we calculate<00:09:08.769> the<00:09:08.890> French<00:09:09.160> note<00:09:09.660> the<00:09:10.660> principal 00:09:11.370 --> 00:09:11.380 align:start position:0% calculate the French note the principal 00:09:11.380 --> 00:09:16.910 align:start position:0% calculate the French note the principal value<00:09:11.560> becomes<00:09:12.990> the<00:09:13.990> left<00:09:14.320> node<00:09:14.649> Y<00:09:15.190> value<00:09:15.700> and 00:09:16.910 --> 00:09:16.920 align:start position:0% value becomes the left node Y value and 00:09:16.920 --> 00:09:19.800 align:start position:0% value becomes the left node Y value and right<00:09:17.920> now<00:09:18.190> the<00:09:18.579> molecule<00:09:18.970> is<00:09:19.060> multiplication 00:09:19.800 --> 00:09:19.810 align:start position:0% right now the molecule is multiplication 00:09:19.810 --> 00:09:22.110 align:start position:0% right now the molecule is multiplication of<00:09:19.930> the<00:09:20.050> left<00:09:20.260> node<00:09:20.470> Y<00:09:20.649> value<00:09:21.040> and<00:09:21.250> the<00:09:21.490> right 00:09:22.110 --> 00:09:22.120 align:start position:0% of the left node Y value and the right 00:09:22.120 --> 00:09:23.660 align:start position:0% of the left node Y value and the right right 00:09:23.660 --> 00:09:23.670 align:start position:0% right 00:09:23.670 --> 00:09:26.610 align:start position:0% right finally<00:09:24.670> the<00:09:24.850> root<00:09:25.029> value<00:09:25.899> because<00:09:26.290> the 00:09:26.610 --> 00:09:26.620 align:start position:0% finally the root value because the 00:09:26.620 --> 00:09:30.829 align:start position:0% finally the root value because the stolen<00:09:27.040> multiplication<00:09:27.970> of<00:09:28.269> the<00:09:28.890> week<00:09:29.890> of<00:09:30.250> the 00:09:30.829 --> 00:09:30.839 align:start position:0% stolen multiplication of the week of the 00:09:30.839 --> 00:09:34.470 align:start position:0% stolen multiplication of the week of the merkel<00:09:31.839> mountain<00:09:32.170> range<00:09:32.380> and<00:09:32.940> the<00:09:33.940> product<00:09:34.360> of 00:09:34.470 --> 00:09:34.480 align:start position:0% merkel mountain range and the product of 00:09:34.480 --> 00:09:39.720 align:start position:0% merkel mountain range and the product of all<00:09:34.870> Peaks<00:09:36.990> we<00:09:37.990> call<00:09:38.230> this<00:09:38.470> big<00:09:38.800> bang<00:09:39.070> in 00:09:39.720 --> 00:09:39.730 align:start position:0% all Peaks we call this big bang in 00:09:39.730 --> 00:09:43.210 align:start position:0% all Peaks we call this big bang in merkel<00:09:40.269> mountain<00:09:40.600> range 00:09:43.210 --> 00:09:43.220 align:start position:0% 00:09:43.220 --> 00:09:47.470 align:start position:0% so<00:09:43.940> with<00:09:44.420> this<00:09:44.630> construction<00:09:45.050> a<00:09:45.970> 16-bit<00:09:46.970> penis 00:09:47.470 --> 00:09:47.480 align:start position:0% so with this construction a 16-bit penis 00:09:47.480 --> 00:09:53.520 align:start position:0% so with this construction a 16-bit penis Merkle<00:09:47.900> tree<00:09:48.140> which<00:09:48.800> has<00:09:51.250> 65,000<00:09:52.250> least 00:09:53.520 --> 00:09:53.530 align:start position:0% Merkle tree which has 65,000 least 00:09:53.530 --> 00:09:56.440 align:start position:0% Merkle tree which has 65,000 least achieved<00:09:54.530> 10<00:09:55.160> million<00:09:55.670> constraints<00:09:56.240> for 00:09:56.440 --> 00:09:56.450 align:start position:0% achieved 10 million constraints for 00:09:56.450 --> 00:09:59.350 align:start position:0% achieved 10 million constraints for rolling<00:09:56.810> up<00:09:56.990> 64<00:09:57.680> items<00:09:58.010> at<00:09:58.820> once 00:09:59.350 --> 00:09:59.360 align:start position:0% rolling up 64 items at once 00:09:59.360 --> 00:10:03.100 align:start position:0% rolling up 64 items at once it<00:09:59.750> is<00:09:59.900> generally<00:10:01.000> because<00:10:02.000> a<00:10:02.270> firm<00:10:02.600> Istanbul 00:10:03.100 --> 00:10:03.110 align:start position:0% it is generally because a firm Istanbul 00:10:03.110 --> 00:10:06.690 align:start position:0% it is generally because a firm Istanbul the<00:10:03.230> cusp<00:10:03.470> guests<00:10:03.980> cause<00:10:04.280> poor<00:10:05.080> circulation 00:10:06.690 --> 00:10:06.700 align:start position:0% the cusp guests cause poor circulation 00:10:06.700 --> 00:10:10.150 align:start position:0% the cusp guests cause poor circulation reduces<00:10:07.700> sloth<00:10:08.000> so<00:10:08.480> it<00:10:09.200> will<00:10:09.380> be<00:10:09.620> able<00:10:09.830> to 00:10:10.150 --> 00:10:10.160 align:start position:0% reduces sloth so it will be able to 00:10:10.160 --> 00:10:15.940 align:start position:0% reduces sloth so it will be able to verify<00:10:10.540> around<00:10:12.640> 256<00:10:13.640> rolling<00:10:14.300> up<00:10:14.530> 256<00:10:15.530> items 00:10:15.940 --> 00:10:15.950 align:start position:0% verify around 256 rolling up 256 items 00:10:15.950 --> 00:10:23.730 align:start position:0% verify around 256 rolling up 256 items at<00:10:16.160> once<00:10:19.780> so<00:10:20.780> finally<00:10:21.470> we<00:10:22.010> can<00:10:22.040> jump<00:10:22.460> up<00:10:22.700> to<00:10:22.730> the 00:10:23.730 --> 00:10:23.740 align:start position:0% at once so finally we can jump up to the 00:10:23.740 --> 00:10:27.040 align:start position:0% at once so finally we can jump up to the Torah<00:10:24.740> performance<00:10:25.430> of<00:10:25.580> the<00:10:25.700> roller<00:10:25.910> with<00:10:26.900> the 00:10:27.040 --> 00:10:27.050 align:start position:0% Torah performance of the roller with the 00:10:27.050 --> 00:10:31.090 align:start position:0% Torah performance of the roller with the Optimus<00:10:27.500> igual<00:10:29.200> just<00:10:30.200> like<00:10:30.380> plasma<00:10:30.620> we<00:10:30.920> can 00:10:31.090 --> 00:10:31.100 align:start position:0% Optimus igual just like plasma we can 00:10:31.100 --> 00:10:33.700 align:start position:0% Optimus igual just like plasma we can use<00:10:31.250> a<00:10:31.280> challenge<00:10:31.820> system<00:10:32.150> to<00:10:32.840> skip<00:10:33.140> the<00:10:33.320> CPS 00:10:33.700 --> 00:10:33.710 align:start position:0% use a challenge system to skip the CPS 00:10:33.710 --> 00:10:39.190 align:start position:0% use a challenge system to skip the CPS knife<00:10:34.600> computation<00:10:35.980> so<00:10:38.080> therefore<00:10:39.080> we<00:10:39.170> can 00:10:39.190 --> 00:10:39.200 align:start position:0% knife computation so therefore we can 00:10:39.200 --> 00:10:43.300 align:start position:0% knife computation so therefore we can read<00:10:39.470> this<00:10:39.590> aloud<00:10:39.920> as<00:10:40.250> opposed<00:10:40.490> to<00:10:41.920> verify<00:10:42.920> the 00:10:43.300 --> 00:10:43.310 align:start position:0% read this aloud as opposed to verify the 00:10:43.310 --> 00:10:45.000 align:start position:0% read this aloud as opposed to verify the sickest<00:10:43.790> interpretation<00:10:44.690> is<00:10:44.900> that 00:10:45.000 --> 00:10:45.010 align:start position:0% sickest interpretation is that 00:10:45.010 --> 00:10:48.000 align:start position:0% sickest interpretation is that unchanging<00:10:46.010> vision 00:10:48.000 --> 00:10:48.010 align:start position:0% unchanging vision 00:10:48.010 --> 00:10:50.530 align:start position:0% unchanging vision therefore<00:10:49.010> in<00:10:49.160> Petersburg<00:10:49.820> in<00:10:50.030> Paris 00:10:50.530 --> 00:10:50.540 align:start position:0% therefore in Petersburg in Paris 00:10:50.540 --> 00:10:54.190 align:start position:0% therefore in Petersburg in Paris perversion<00:10:51.460> rolling<00:10:52.460> up<00:10:52.640> kisara<00:10:53.150> 3<00:10:53.840> million 00:10:54.190 --> 00:10:54.200 align:start position:0% perversion rolling up kisara 3 million 00:10:54.200 --> 00:10:57.190 align:start position:0% perversion rolling up kisara 3 million and<00:10:54.380> spurt<00:10:54.740> injection<00:10:55.300> but<00:10:56.300> Optimus<00:10:56.780> tabula 00:10:57.190 --> 00:10:57.200 align:start position:0% and spurt injection but Optimus tabula 00:10:57.200 --> 00:11:03.010 align:start position:0% and spurt injection but Optimus tabula on<00:10:57.590> Nico's<00:10:58.190> on<00:10:58.600> about<00:11:01.540> 147,000<00:11:02.540> Kasper 00:11:03.010 --> 00:11:03.020 align:start position:0% on Nico's on about 147,000 Kasper 00:11:03.020 --> 00:11:06.940 align:start position:0% on Nico's on about 147,000 Kasper transition<00:11:03.620> and<00:11:04.210> in<00:11:05.210> Istanbul<00:11:05.870> it<00:11:06.170> only 00:11:06.940 --> 00:11:06.950 align:start position:0% transition and in Istanbul it only 00:11:06.950 --> 00:11:10.120 align:start position:0% transition and in Istanbul it only concern<00:11:07.340> around<00:11:07.730> about<00:11:08.380> 50,000<00:11:09.410> yes<00:11:09.860> per 00:11:10.120 --> 00:11:10.130 align:start position:0% concern around about 50,000 yes per 00:11:10.130 --> 00:11:14.080 align:start position:0% concern around about 50,000 yes per generation<00:11:11.050> we<00:11:12.050> need<00:11:12.080> to<00:11:12.380> actually<00:11:12.710> is<00:11:13.220> much 00:11:14.080 --> 00:11:14.090 align:start position:0% generation we need to actually is much 00:11:14.090 --> 00:11:18.970 align:start position:0% generation we need to actually is much expensive<00:11:14.960> than<00:11:15.700> our<00:11:16.700> general<00:11:17.690> Lola<00:11:18.020> it<00:11:18.860> is 00:11:18.970 --> 00:11:18.980 align:start position:0% expensive than our general Lola it is 00:11:18.980 --> 00:11:22.150 align:start position:0% expensive than our general Lola it is because<00:11:19.370> it<00:11:19.910> contains<00:11:20.360> alarm<00:11:20.990> which<00:11:21.740> is<00:11:21.890> nurse 00:11:22.150 --> 00:11:22.160 align:start position:0% because it contains alarm which is nurse 00:11:22.160 --> 00:11:26.050 align:start position:0% because it contains alarm which is nurse proof<00:11:22.550> to<00:11:23.150> make<00:11:23.390> the<00:11:24.160> transaction<00:11:25.160> as<00:11:25.310> a<00:11:25.370> some 00:11:26.050 --> 00:11:26.060 align:start position:0% proof to make the transaction as a some 00:11:26.060 --> 00:11:29.620 align:start position:0% proof to make the transaction as a some comparator<00:11:26.630> transaction<00:11:27.970> but<00:11:28.970> it<00:11:29.270> is<00:11:29.390> still 00:11:29.620 --> 00:11:29.630 align:start position:0% comparator transaction but it is still 00:11:29.630 --> 00:11:32.560 align:start position:0% comparator transaction but it is still very<00:11:29.839> reasonable<00:11:30.650> because<00:11:30.770> the<00:11:31.520> original<00:11:31.940> the 00:11:32.560 --> 00:11:32.570 align:start position:0% very reasonable because the original the 00:11:32.570 --> 00:11:34.900 align:start position:0% very reasonable because the original the Bayer<00:11:32.810> years<00:11:33.320> training<00:11:33.620> total<00:11:34.310> transaction 00:11:34.900 --> 00:11:34.910 align:start position:0% Bayer years training total transaction 00:11:34.910 --> 00:11:43.140 align:start position:0% Bayer years training total transaction cost<00:11:35.420> around<00:11:35.860> 50,000<00:11:36.860> to<00:11:38.050> 100,000<00:11:39.050> cast 00:11:43.140 --> 00:11:43.150 align:start position:0% 00:11:43.150 --> 00:11:46.230 align:start position:0% so<00:11:43.750> as<00:11:44.110> a<00:11:44.140> result<00:11:44.380> of<00:11:44.770> return<00:11:45.760> is<00:11:45.910> passed 00:11:46.230 --> 00:11:46.240 align:start position:0% so as a result of return is passed 00:11:46.240 --> 00:11:49.140 align:start position:0% so as a result of return is passed through<00:11:46.330> inter<00:11:47.020> magnet<00:11:47.440> drinkers<00:11:47.920> or<00:11:48.279> is<00:11:48.880> a 00:11:49.140 --> 00:11:49.150 align:start position:0% through inter magnet drinkers or is a 00:11:49.150 --> 00:11:52.530 align:start position:0% through inter magnet drinkers or is a towel<00:11:49.690> and<00:11:50.230> some<00:11:50.610> deep-lying<00:11:51.610> for<00:11:52.180> not<00:11:52.360> using 00:11:52.530 --> 00:11:52.540 align:start position:0% towel and some deep-lying for not using 00:11:52.540 --> 00:11:56.430 align:start position:0% towel and some deep-lying for not using them<00:11:52.839> so<00:11:53.880> first<00:11:54.880> anyone<00:11:55.450> can<00:11:55.750> be<00:11:55.960> a<00:11:55.990> real<00:11:56.200> laner 00:11:56.430 --> 00:11:56.440 align:start position:0% them so first anyone can be a real laner 00:11:56.440 --> 00:12:00.360 align:start position:0% them so first anyone can be a real laner and<00:11:57.060> we<00:11:58.060> can<00:11:58.300> decide<00:11:58.630> their<00:11:58.900> own<00:11:59.370> transaction 00:12:00.360 --> 00:12:00.370 align:start position:0% and we can decide their own transaction 00:12:00.370 --> 00:12:04.050 align:start position:0% and we can decide their own transaction fee<00:12:00.580> policy<00:12:01.800> but<00:12:02.800> to<00:12:02.860> submit<00:12:03.250> the<00:12:03.580> optimist 00:12:04.050 --> 00:12:04.060 align:start position:0% fee policy but to submit the optimist 00:12:04.060 --> 00:12:07.230 align:start position:0% fee policy but to submit the optimist you<00:12:04.089> want<00:12:04.570> the<00:12:05.500> relationship<00:12:05.800> to<00:12:06.190> pass<00:12:06.820> some 00:12:07.230 --> 00:12:07.240 align:start position:0% you want the relationship to pass some 00:12:07.240 --> 00:12:12.300 align:start position:0% you want the relationship to pass some states<00:12:07.630> to<00:12:08.230> secure<00:12:08.620> the<00:12:08.830> product<00:12:09.339> to<00:12:09.760> you<00:12:11.310> just 00:12:12.300 --> 00:12:12.310 align:start position:0% states to secure the product to you just 00:12:12.310 --> 00:12:15.500 align:start position:0% states to secure the product to you just thanks<00:12:12.640> for<00:12:12.850> the<00:12:12.970> challenge<00:12:13.240> system<00:12:14.400> since 00:12:15.500 --> 00:12:15.510 align:start position:0% thanks for the challenge system since 00:12:15.510 --> 00:12:18.390 align:start position:0% thanks for the challenge system since beings<00:12:16.510> are<00:12:16.779> therefore<00:12:17.350> being<00:12:17.950> a<00:12:18.070> real<00:12:18.220> layer 00:12:18.390 --> 00:12:18.400 align:start position:0% beings are therefore being a real layer 00:12:18.400 --> 00:12:21.240 align:start position:0% beings are therefore being a real layer can<00:12:18.850> be<00:12:18.910> considered<00:12:19.089> as<00:12:19.750> a<00:12:20.110> kind<00:12:20.950> of<00:12:21.130> a 00:12:21.240 --> 00:12:21.250 align:start position:0% can be considered as a kind of a 00:12:21.250 --> 00:12:25.769 align:start position:0% can be considered as a kind of a financial<00:12:21.520> part<00:12:22.260> which<00:12:23.260> gives<00:12:23.620> some<00:12:24.779> revenue 00:12:25.769 --> 00:12:25.779 align:start position:0% financial part which gives some revenue 00:12:25.779 --> 00:12:29.250 align:start position:0% financial part which gives some revenue for<00:12:26.190> the<00:12:27.190> transition<00:12:27.790> aggregated<00:12:28.750> transition 00:12:29.250 --> 00:12:29.260 align:start position:0% for the transition aggregated transition 00:12:29.260 --> 00:12:35.329 align:start position:0% for the transition aggregated transition be<00:12:29.670> against<00:12:30.670> regarding<00:12:31.510> to<00:12:31.630> the<00:12:32.310> closet<00:12:33.310> space 00:12:35.329 --> 00:12:35.339 align:start position:0% be against regarding to the closet space 00:12:35.339 --> 00:12:38.850 align:start position:0% be against regarding to the closet space therefore<00:12:36.339> we<00:12:36.910> can<00:12:37.089> also<00:12:37.330> make<00:12:37.750> a<00:12:37.990> kind<00:12:38.650> of<00:12:38.740> a 00:12:38.850 --> 00:12:38.860 align:start position:0% therefore we can also make a kind of a 00:12:38.860 --> 00:12:42.360 align:start position:0% therefore we can also make a kind of a towel<00:12:39.220> system<00:12:39.690> like<00:12:40.690> delegating<00:12:41.470> some<00:12:41.980> states 00:12:42.360 --> 00:12:42.370 align:start position:0% towel system like delegating some states 00:12:42.370 --> 00:12:47.300 align:start position:0% towel system like delegating some states to<00:12:43.150> receive<00:12:43.830> some<00:12:45.000> dividends<00:12:46.000> of<00:12:46.270> the 00:12:47.300 --> 00:12:47.310 align:start position:0% to receive some dividends of the 00:12:47.310 --> 00:12:52.490 align:start position:0% to receive some dividends of the transaction<00:12:48.310> fee<00:12:48.490> revenue 00:12:52.490 --> 00:12:52.500 align:start position:0% 00:12:52.500 --> 00:12:55.640 align:start position:0% so<00:12:53.070> the<00:12:53.400> future<00:12:53.670> word<00:12:54.030> is<00:12:54.380> first<00:12:55.380> one<00:12:55.530> is 00:12:55.640 --> 00:12:55.650 align:start position:0% so the future word is first one is 00:12:55.650 --> 00:12:59.210 align:start position:0% so the future word is first one is optimization<00:12:56.550> and<00:12:57.560> the<00:12:58.560> second<00:12:58.920> is<00:12:59.040> related 00:12:59.210 --> 00:12:59.220 align:start position:0% optimization and the second is related 00:12:59.220 --> 00:13:03.730 align:start position:0% optimization and the second is related plan<00:12:59.790> and<00:13:00.390> mobile<00:13:00.750> client<00:13:01.320> and<00:13:02.220> because<00:13:03.180> if<00:13:03.390> we 00:13:03.730 --> 00:13:03.740 align:start position:0% plan and mobile client and because if we 00:13:03.740 --> 00:13:09.500 align:start position:0% plan and mobile client and because if we also<00:13:05.630> get<00:13:06.630> some<00:13:06.900> instant<00:13:07.380> finality<00:13:07.830> if<00:13:08.820> we<00:13:09.120> Ola 00:13:09.500 --> 00:13:09.510 align:start position:0% also get some instant finality if we Ola 00:13:09.510 --> 00:13:12.800 align:start position:0% also get some instant finality if we Ola without<00:13:10.500> the<00:13:10.680> optimum<00:13:11.400> I<00:13:11.670> mean<00:13:12.060> it<00:13:12.330> means<00:13:12.540> that 00:13:12.800 --> 00:13:12.810 align:start position:0% without the optimum I mean it means that 00:13:12.810 --> 00:13:15.620 align:start position:0% without the optimum I mean it means that if<00:13:13.020> we<00:13:13.790> compute<00:13:14.790> all<00:13:15.000> the<00:13:15.090> sickest<00:13:15.450> our 00:13:15.620 --> 00:13:15.630 align:start position:0% if we compute all the sickest our 00:13:15.630 --> 00:13:18.080 align:start position:0% if we compute all the sickest our computation<00:13:16.080> then<00:13:16.830> we<00:13:16.950> can<00:13:17.190> get<00:13:17.550> that<00:13:17.730> is<00:13:17.880> the 00:13:18.080 --> 00:13:18.090 align:start position:0% computation then we can get that is the 00:13:18.090 --> 00:13:20.960 align:start position:0% computation then we can get that is the finality<00:13:18.480> but<00:13:19.230> if<00:13:19.680> we<00:13:19.950> use<00:13:20.130> up<00:13:20.310> to<00:13:20.550> mr.<00:13:20.760> Bhalla 00:13:20.960 --> 00:13:20.970 align:start position:0% finality but if we use up to mr. Bhalla 00:13:20.970 --> 00:13:24.940 align:start position:0% finality but if we use up to mr. Bhalla we<00:13:21.360> need<00:13:21.510> to<00:13:21.720> give<00:13:22.140> some<00:13:22.380> challenge<00:13:22.980> period<00:13:23.400> so 00:13:24.940 --> 00:13:24.950 align:start position:0% we need to give some challenge period so 00:13:24.950 --> 00:13:28.010 align:start position:0% we need to give some challenge period so we<00:13:25.950> we<00:13:26.250> lose<00:13:26.520> the<00:13:26.790> instant<00:13:27.450> by<00:13:27.570> on<00:13:27.750> limit 00:13:28.010 --> 00:13:28.020 align:start position:0% we we lose the instant by on limit 00:13:28.020 --> 00:13:31.510 align:start position:0% we we lose the instant by on limit therefore<00:13:28.740> if<00:13:29.580> we<00:13:29.790> change<00:13:30.120> some<00:13:30.630> construct<00:13:31.140> a 00:13:31.510 --> 00:13:31.520 align:start position:0% therefore if we change some construct a 00:13:31.520 --> 00:13:35.410 align:start position:0% therefore if we change some construct a network<00:13:32.520> of<00:13:32.730> the<00:13:32.880> real<00:13:33.030> layers<00:13:33.680> then<00:13:34.680> we<00:13:34.800> can 00:13:35.410 --> 00:13:35.420 align:start position:0% network of the real layers then we can 00:13:35.420 --> 00:13:39.530 align:start position:0% network of the real layers then we can not<00:13:36.420> is<00:13:36.900> not<00:13:37.890> exactly<00:13:38.460> an<00:13:38.850> instant<00:13:39.210> finality 00:13:39.530 --> 00:13:39.540 align:start position:0% not is not exactly an instant finality 00:13:39.540 --> 00:13:41.930 align:start position:0% not is not exactly an instant finality but<00:13:39.930> we<00:13:40.290> can<00:13:40.440> offer<00:13:40.680> you<00:13:40.920> to<00:13:41.130> provide<00:13:41.520> some 00:13:41.930 --> 00:13:41.940 align:start position:0% but we can offer you to provide some 00:13:41.940 --> 00:13:45.200 align:start position:0% but we can offer you to provide some security<00:13:42.570> of<00:13:43.200> instant<00:13:43.920> finally<00:13:44.430> with<00:13:44.940> the 00:13:45.200 --> 00:13:45.210 align:start position:0% security of instant finally with the 00:13:45.210 --> 00:13:50.180 align:start position:0% security of instant finally with the states<00:13:45.960> of<00:13:46.170> the<00:13:46.350> relators<00:13:46.830> network<00:13:48.410> and<00:13:49.410> what 00:13:50.180 --> 00:13:50.190 align:start position:0% states of the relators network and what 00:13:50.190 --> 00:13:54.470 align:start position:0% states of the relators network and what we<00:13:50.310> have<00:13:50.550> to<00:13:50.700> do<00:13:50.820> is<00:13:51.620> gently<00:13:52.940> just<00:13:53.940> destroying 00:13:54.470 --> 00:13:54.480 align:start position:0% we have to do is gently just destroying 00:13:54.480 --> 00:13:59.060 align:start position:0% we have to do is gently just destroying the<00:13:54.690> hypothesis<00:13:55.940> yeah<00:13:57.830> strike<00:13:58.830> that 00:13:59.060 --> 00:13:59.070 align:start position:0% the hypothesis yeah strike that 00:13:59.070 --> 00:14:05.900 align:start position:0% the hypothesis yeah strike that pasty-faced<00:14:02.360> so<00:14:03.360> here's<00:14:04.080> the<00:14:04.230> summary<00:14:04.910> the 00:14:05.900 --> 00:14:05.910 align:start position:0% pasty-faced so here's the summary the 00:14:05.910 --> 00:14:07.940 align:start position:0% pasty-faced so here's the summary the remaining<00:14:06.420> three<00:14:06.630> choruses<00:14:07.200> removing<00:14:07.830> the 00:14:07.940 --> 00:14:07.950 align:start position:0% remaining three choruses removing the 00:14:07.950 --> 00:14:11.180 align:start position:0% remaining three choruses removing the protocol<00:14:08.430> and<00:14:09.500> coming<00:14:10.500> month<00:14:10.710> Allah<00:14:10.890> Christ 00:14:11.180 --> 00:14:11.190 align:start position:0% protocol and coming month Allah Christ 00:14:11.190 --> 00:14:14.450 align:start position:0% protocol and coming month Allah Christ came<00:14:11.430> together<00:14:12.110> and<00:14:13.110> he<00:14:13.260> uses<00:14:13.620> Peter<00:14:14.250> Suber 00:14:14.450 --> 00:14:14.460 align:start position:0% came together and he uses Peter Suber 00:14:14.460 --> 00:14:16.840 align:start position:0% came together and he uses Peter Suber the<00:14:14.760> mountain<00:14:15.180> range<00:14:15.390> for<00:14:15.870> an<00:14:16.140> efficient 00:14:16.840 --> 00:14:16.850 align:start position:0% the mountain range for an efficient 00:14:16.850 --> 00:14:20.990 align:start position:0% the mountain range for an efficient secure<00:14:17.850> all<00:14:18.770> there<00:14:19.770> for<00:14:19.800> each<00:14:20.070> chain<00:14:20.400> is<00:14:20.580> able 00:14:20.990 --> 00:14:21.000 align:start position:0% secure all there for each chain is able 00:14:21.000 --> 00:14:26.990 align:start position:0% secure all there for each chain is able to<00:14:21.150> pan<00:14:21.450> up<00:14:21.690> to<00:14:22.080> 256<00:14:23.010> items<00:14:23.730> at<00:14:23.910> once<00:14:24.260> and<00:14:26.000> the 00:14:26.990 --> 00:14:27.000 align:start position:0% to pan up to 256 items at once and the 00:14:27.000 --> 00:14:29.330 align:start position:0% to pan up to 256 items at once and the optimal<00:14:27.690> provides<00:14:28.260> deterministic<00:14:29.040> front 00:14:29.330 --> 00:14:29.340 align:start position:0% optimal provides deterministic front 00:14:29.340 --> 00:14:33.590 align:start position:0% optimal provides deterministic front proof<00:14:29.670> without<00:14:30.300> any<00:14:31.020> t88<00:14:31.710> problem<00:14:32.280> and<00:14:32.600> also 00:14:33.590 --> 00:14:33.600 align:start position:0% proof without any t88 problem and also 00:14:33.600 --> 00:14:38.000 align:start position:0% proof without any t88 problem and also it<00:14:33.720> reduces<00:14:33.990> the<00:14:34.560> cost<00:14:34.740> down<00:14:35.310> to<00:14:36.200> 15,000<00:14:37.230> yes 00:14:38.000 --> 00:14:38.010 align:start position:0% it reduces the cost down to 15,000 yes 00:14:38.010 --> 00:14:42.710 align:start position:0% it reduces the cost down to 15,000 yes per<00:14:38.250> transaction<00:14:40.910> so<00:14:41.910> this<00:14:42.360> is<00:14:42.480> the 00:14:42.710 --> 00:14:42.720 align:start position:0% per transaction so this is the 00:14:42.720 --> 00:14:45.980 align:start position:0% per transaction so this is the implementation<00:14:43.460> so<00:14:44.540> if<00:14:45.540> you<00:14:45.720> like<00:14:45.960> that 00:14:45.980 --> 00:14:45.990 align:start position:0% implementation so if you like that 00:14:45.990 --> 00:14:47.950 align:start position:0% implementation so if you like that please<00:14:46.920> give<00:14:47.700> me 00:14:47.950 --> 00:14:47.960 align:start position:0% please give me 00:14:47.960 --> 00:14:56.380 align:start position:0% please give me some<00:14:48.080> top<00:14:48.440> stars<00:14:49.030> or<00:14:52.600> yes<00:14:53.800> or<00:14:54.800> if<00:14:55.250> you<00:14:56.210> like 00:14:56.380 --> 00:14:56.390 align:start position:0% some top stars or yes or if you like 00:14:56.390 --> 00:14:59.860 align:start position:0% some top stars or yes or if you like that<00:14:56.660> I'm<00:14:56.960> looking<00:14:57.620> for<00:14:58.010> teammates<00:14:58.730> or<00:14:59.450> teams 00:14:59.860 --> 00:14:59.870 align:start position:0% that I'm looking for teammates or teams 00:14:59.870 --> 00:15:02.320 align:start position:0% that I'm looking for teammates or teams you<00:15:00.170> can<00:15:00.290> support<00:15:00.680> this<00:15:01.070> project<00:15:01.400> so<00:15:02.210> if 00:15:02.320 --> 00:15:02.330 align:start position:0% you can support this project so if 00:15:02.330 --> 00:15:04.030 align:start position:0% you can support this project so if you're<00:15:02.480> interested<00:15:03.080> in<00:15:03.200> this<00:15:03.350> project<00:15:03.620> please 00:15:04.030 --> 00:15:04.040 align:start position:0% you're interested in this project please 00:15:04.040 --> 00:15:21.130 align:start position:0% you're interested in this project please let<00:15:04.370> me<00:15:04.460> know<00:15:04.610> so<00:15:07.870> thank<00:15:08.870> you<00:15:17.020> owe<00:15:18.020> me<00:15:20.140> some 00:15:21.130 --> 00:15:21.140 align:start position:0% let me know so thank you owe me some 00:15:21.140 --> 00:15:28.570 align:start position:0% let me know so thank you owe me some pressure<00:15:22.270> if<00:15:23.270> you<00:15:23.450> want<00:15:23.630> yeah<00:15:27.250> we<00:15:28.250> have<00:15:28.370> four 00:15:28.570 --> 00:15:28.580 align:start position:0% pressure if you want yeah we have four 00:15:28.580 --> 00:15:36.230 align:start position:0% pressure if you want yeah we have four minutes<00:15:28.880> so<00:15:29.390> you<00:15:30.320> can<00:15:30.350> go<00:15:30.620> up<00:15:31.690> there<00:15:32.690> is<00:15:32.870> a 00:15:36.230 --> 00:15:36.240 align:start position:0% 00:15:36.240 --> 00:15:40.920 align:start position:0% stable<00:15:37.240> internet<00:15:38.200> Reza<00:15:39.029> yeah<00:15:40.029> um<00:15:40.390> the<00:15:40.480> devil 00:15:40.920 --> 00:15:40.930 align:start position:0% stable internet Reza yeah um the devil 00:15:40.930 --> 00:15:45.690 align:start position:0% stable internet Reza yeah um the devil yeah<00:15:42.899> but<00:15:43.899> on<00:15:44.529> the<00:15:44.769> Internet 00:15:45.690 --> 00:15:45.700 align:start position:0% yeah but on the Internet 00:15:45.700 --> 00:16:06.640 align:start position:0% yeah but on the Internet [Music] 00:16:06.640 --> 00:16:06.650 align:start position:0% 00:16:06.650 --> 00:16:10.130 align:start position:0% I<00:16:07.650> already<00:16:08.250> prepared<00:16:08.640> as<00:16:09.180> an<00:16:09.390> Iranian<00:16:09.660> and 00:16:10.130 --> 00:16:10.140 align:start position:0% I already prepared as an Iranian and 00:16:10.140 --> 00:16:14.000 align:start position:0% I already prepared as an Iranian and proves<00:16:10.640> generic<00:16:11.640> growth<00:16:11.880> and<00:16:12.600> some<00:16:13.500> samples 00:16:14.000 --> 00:16:14.010 align:start position:0% proves generic growth and some samples 00:16:14.010 --> 00:16:33.000 align:start position:0% proves generic growth and some samples and<00:16:14.250> extras 00:16:33.000 --> 00:16:33.010 align:start position:0% 00:16:33.010 --> 00:16:37.550 align:start position:0% [Music] 00:16:37.550 --> 00:16:37.560 align:start position:0% 00:16:37.560 --> 00:16:47.150 align:start position:0% but<00:16:38.560> it's<00:16:38.769> amusing 00:16:47.150 --> 00:16:47.160 align:start position:0% 00:16:47.160 --> 00:16:50.210 align:start position:0% so<00:16:48.160> the<00:16:48.430> first<00:16:48.670> song<00:16:48.880> is<00:16:49.060> war<00:16:49.269> 2<00:16:49.750> memorial 00:16:50.210 --> 00:16:50.220 align:start position:0% so the first song is war 2 memorial 00:16:50.220 --> 00:16:53.699 align:start position:0% so the first song is war 2 memorial transaction<00:16:51.220> which<00:16:51.850> spend<00:16:52.300> one<00:16:52.779> point<00:16:53.230> mixing 00:16:53.699 --> 00:16:53.709 align:start position:0% transaction which spend one point mixing 00:16:53.709 --> 00:16:55.860 align:start position:0% transaction which spend one point mixing so<00:16:54.040> we<00:16:54.550> can<00:16:54.760> make<00:16:54.970> some<00:16:55.209> appointments<00:16:55.420> by 00:16:55.860 --> 00:16:55.870 align:start position:0% so we can make some appointments by 00:16:55.870 --> 00:16:59.970 align:start position:0% so we can make some appointments by depositing<00:16:56.529> to<00:16:57.100> BSU<00:16:57.370> Chinese<00:16:58.350> and<00:16:59.350> the<00:16:59.649> second 00:16:59.970 --> 00:16:59.980 align:start position:0% depositing to BSU Chinese and the second 00:16:59.980 --> 00:17:02.910 align:start position:0% depositing to BSU Chinese and the second round<00:17:00.190> is<00:17:00.959> spending<00:17:01.959> to<00:17:02.230> see<00:17:02.649> the<00:17:02.769> new 00:17:02.910 --> 00:17:02.920 align:start position:0% round is spending to see the new 00:17:02.920 --> 00:17:05.189 align:start position:0% round is spending to see the new traditionalist<00:17:03.880> which<00:17:04.329> is<00:17:04.540> right<00:17:04.809> throughout 00:17:05.189 --> 00:17:05.199 align:start position:0% traditionalist which is right throughout 00:17:05.199 --> 00:17:07.280 align:start position:0% traditionalist which is right throughout by<00:17:05.559> the<00:17:05.620> personnel 00:17:07.280 --> 00:17:07.290 align:start position:0% by the personnel 00:17:07.290 --> 00:17:11.850 align:start position:0% by the personnel so<00:17:08.290> it<00:17:08.350> means<00:17:08.559> we<00:17:08.890> used<00:17:09.760> continues<00:17:10.569> to<00:17:11.140> include 00:17:11.850 --> 00:17:11.860 align:start position:0% so it means we used continues to include 00:17:11.860 --> 00:17:16.650 align:start position:0% so it means we used continues to include CSS<00:17:12.400> and<00:17:12.929> for<00:17:13.929> once<00:17:14.290> and<00:17:14.559> make<00:17:14.709> one<00:17:14.949> change<00:17:15.660> so 00:17:16.650 --> 00:17:16.660 align:start position:0% CSS and for once and make one change so 00:17:16.660 --> 00:17:20.760 align:start position:0% CSS and for once and make one change so if<00:17:17.110> you<00:17:17.319> have<00:17:17.620> some<00:17:19.290> removable<00:17:20.290> trench<00:17:20.500> blog 00:17:20.760 --> 00:17:20.770 align:start position:0% if you have some removable trench blog 00:17:20.770 --> 00:17:23.309 align:start position:0% if you have some removable trench blog post<00:17:21.069> and<00:17:21.280> you<00:17:21.339> can<00:17:21.459> aggregate<00:17:22.089> them<00:17:22.569> to<00:17:23.079> use 00:17:23.309 --> 00:17:23.319 align:start position:0% post and you can aggregate them to use 00:17:23.319 --> 00:17:29.190 align:start position:0% post and you can aggregate them to use or<00:17:23.740> a<00:17:24.130> one<00:17:26.189> so<00:17:27.189> as<00:17:27.520> I<00:17:27.699> know<00:17:27.819> many<00:17:28.000> some<00:17:28.900> part<00:17:29.140> of 00:17:29.190 --> 00:17:29.200 align:start position:0% or a one so as I know many some part of 00:17:29.200 --> 00:17:38.210 align:start position:0% or a one so as I know many some part of all<00:17:29.410> uses<00:17:29.740> two<00:17:30.549> inputs<00:17:31.059> and<00:17:31.270> two<00:17:31.330> of<00:17:31.600> us<00:17:33.660> so 00:17:38.210 --> 00:17:38.220 align:start position:0% 00:17:38.220 --> 00:17:46.950 align:start position:0% there<00:17:39.220> was<00:17:39.370> the<00:17:39.580> only<00:17:40.620> 64<00:17:44.549> at<00:17:45.549> once<00:17:45.940> so<00:17:46.570> this<00:17:46.840> is 00:17:46.950 --> 00:17:46.960 align:start position:0% there was the only 64 at once so this is 00:17:46.960 --> 00:17:48.990 align:start position:0% there was the only 64 at once so this is the<00:17:47.110> wizard<00:17:47.470> will<00:17:47.740> be<00:17:47.950> rolled 00:17:48.990 --> 00:17:49.000 align:start position:0% the wizard will be rolled 00:17:49.000 --> 00:17:53.000 align:start position:0% the wizard will be rolled wallops<00:17:49.770> 32-bit<00:17:50.770> border<00:17:51.040> connection<00:17:51.640> service 00:17:53.000 --> 00:17:53.010 align:start position:0% wallops 32-bit border connection service 00:17:53.010 --> 00:18:00.889 align:start position:0% wallops 32-bit border connection service in<00:17:54.570> perspiration 00:18:00.889 --> 00:18:00.899 align:start position:0% 00:18:00.899 --> 00:18:04.860 align:start position:0% how<00:18:01.899> long<00:18:02.080> did<00:18:02.230> it<00:18:02.350> take<00:18:02.470> to<00:18:02.769> build<00:18:02.799> a<00:18:03.870> parrot 00:18:04.860 --> 00:18:04.870 align:start position:0% how long did it take to build a parrot 00:18:04.870 --> 00:18:07.700 align:start position:0% how long did it take to build a parrot how<00:18:05.379> long<00:18:05.679> did<00:18:06.009> it<00:18:06.070> take<00:18:06.129> you<00:18:06.519> to<00:18:06.549> build<00:18:06.789> it<00:18:07.000> I 00:18:07.700 --> 00:18:07.710 align:start position:0% how long did it take you to build it I 00:18:07.710 --> 00:18:13.340 align:start position:0% how long did it take you to build it I started<00:18:08.710> to<00:18:08.919> design<00:18:09.539> from<00:18:10.539> from<00:18:11.470> the<00:18:11.620> tree<00:18:11.799> and 00:18:13.340 --> 00:18:13.350 align:start position:0% started to design from from the tree and 00:18:13.350 --> 00:18:17.460 align:start position:0% started to design from from the tree and finished<00:18:14.519> specification<00:18:15.519> Iran<00:18:16.240> from<00:18:16.659> July 00:18:17.460 --> 00:18:17.470 align:start position:0% finished specification Iran from July 00:18:17.470 --> 00:18:20.690 align:start position:0% finished specification Iran from July and<00:18:18.190> started<00:18:19.179> to<00:18:19.299> build<00:18:19.480> from<00:18:19.929> honest 00:18:20.690 --> 00:18:20.700 align:start position:0% and started to build from honest 00:18:20.700 --> 00:18:34.060 align:start position:0% and started to build from honest full-time 00:18:34.060 --> 00:18:34.070 align:start position:0% 00:18:34.070 --> 00:18:40.420 align:start position:0% [Applause]