WEBVTT Kind: captions Language: en 00:00:04.650 --> 00:00:07.219 align:start position:0% hello<00:00:05.370> everyone<00:00:05.790> I<00:00:05.970> shower<00:00:06.569> from<00:00:06.870> research 00:00:07.219 --> 00:00:07.229 align:start position:0% hello everyone I shower from research 00:00:07.229 --> 00:00:11.539 align:start position:0% hello everyone I shower from research team<00:00:07.470> and<00:00:08.510> today<00:00:09.510> my<00:00:09.780> talk<00:00:09.840> is<00:00:10.260> about<00:00:10.549> toward 00:00:11.539 --> 00:00:11.549 align:start position:0% team and today my talk is about toward 00:00:11.549 --> 00:00:16.120 align:start position:0% team and today my talk is about toward eastern<00:00:12.120> 2.0<00:00:13.099> shutting<00:00:14.099> universe<00:00:14.549> and<00:00:14.849> also 00:00:16.120 --> 00:00:16.130 align:start position:0% eastern 2.0 shutting universe and also 00:00:16.130 --> 00:00:20.060 align:start position:0% eastern 2.0 shutting universe and also before<00:00:17.130> it's<00:00:17.369> complete<00:00:17.939> and<00:00:18.180> delivered<00:00:19.070> there 00:00:20.060 --> 00:00:20.070 align:start position:0% before it's complete and delivered there 00:00:20.070 --> 00:00:24.290 align:start position:0% before it's complete and delivered there is<00:00:20.220> a<00:00:20.250> gap<00:00:20.669> between<00:00:20.700> now<00:00:21.540> and<00:00:21.710> the<00:00:22.710> end<00:00:22.980> game<00:00:23.300> so 00:00:24.290 --> 00:00:24.300 align:start position:0% is a gap between now and the end game so 00:00:24.300 --> 00:00:34.729 align:start position:0% is a gap between now and the end game so what<00:00:25.169> we<00:00:25.380> shall<00:00:25.559> build<00:00:25.829> for<00:00:26.189> it<00:00:32.809> so<00:00:33.809> this<00:00:34.680> is 00:00:34.729 --> 00:00:34.739 align:start position:0% what we shall build for it so this is 00:00:34.739 --> 00:00:37.700 align:start position:0% what we shall build for it so this is the<00:00:34.920> well-known<00:00:35.390> is<00:00:36.390> there<00:00:36.540> a<00:00:36.570> roadmap<00:00:37.019> that<00:00:37.260> I 00:00:37.700 --> 00:00:37.710 align:start position:0% the well-known is there a roadmap that I 00:00:37.710 --> 00:00:39.349 align:start position:0% the well-known is there a roadmap that I don't<00:00:38.039> need<00:00:38.129> to<00:00:38.190> go<00:00:38.519> through<00:00:38.730> again<00:00:39.059> the 00:00:39.349 --> 00:00:39.359 align:start position:0% don't need to go through again the 00:00:39.359 --> 00:00:42.860 align:start position:0% don't need to go through again the allies<00:00:40.109> quite<00:00:40.440> simple<00:00:40.980> all<00:00:41.850> those<00:00:42.179> faces<00:00:42.629> are 00:00:42.860 --> 00:00:42.870 align:start position:0% allies quite simple all those faces are 00:00:42.870 --> 00:00:46.669 align:start position:0% allies quite simple all those faces are have<00:00:43.589> its<00:00:43.829> own<00:00:44.010> girls<00:00:44.429> and<00:00:44.699> however<00:00:45.600> found<00:00:46.350> the 00:00:46.669 --> 00:00:46.679 align:start position:0% have its own girls and however found the 00:00:46.679 --> 00:00:50.410 align:start position:0% have its own girls and however found the decide<00:00:47.100> to<00:00:47.550> production<00:00:48.359> let's<00:00:49.260> actually<00:00:49.620> like 00:00:50.410 --> 00:00:50.420 align:start position:0% decide to production let's actually like 00:00:50.420 --> 00:00:55.340 align:start position:0% decide to production let's actually like it's<00:00:51.420> actually<00:00:51.659> like<00:00:52.140> this<00:00:54.199> so<00:00:55.199> how 00:00:55.340 --> 00:00:55.350 align:start position:0% it's actually like this so how 00:00:55.350 --> 00:00:58.759 align:start position:0% it's actually like this so how impractical<00:00:55.920> is<00:00:56.879> like<00:00:57.179> a<00:00:57.210> twisted<00:00:57.600> a<00:00:58.079> highway 00:00:58.759 --> 00:00:58.769 align:start position:0% impractical is like a twisted a highway 00:00:58.769 --> 00:01:06.770 align:start position:0% impractical is like a twisted a highway layer<00:00:59.309> by<00:00:59.609> layers<00:00:59.969> and<00:01:00.829> connected<00:01:04.250> so<00:01:05.250> the<00:01:05.780> the 00:01:06.770 --> 00:01:06.780 align:start position:0% layer by layers and connected so the the 00:01:06.780 --> 00:01:10.010 align:start position:0% layer by layers and connected so the the courage<00:01:07.110> of<00:01:07.350> the<00:01:08.130> current<00:01:08.460> approach<00:01:08.850> is<00:01:09.750> much 00:01:10.010 --> 00:01:10.020 align:start position:0% courage of the current approach is much 00:01:10.020 --> 00:01:13.910 align:start position:0% courage of the current approach is much better<00:01:10.830> than<00:01:11.370> the<00:01:11.850> early<00:01:12.360> shoddy<00:01:13.140> and<00:01:13.440> Casper 00:01:13.910 --> 00:01:13.920 align:start position:0% better than the early shoddy and Casper 00:01:13.920 --> 00:01:21.260 align:start position:0% better than the early shoddy and Casper design<00:01:14.520> like<00:01:15.480> in<00:01:15.750> the<00:01:16.610> 2017<00:01:17.610> and<00:01:19.970> where<00:01:20.970> there 00:01:21.260 --> 00:01:21.270 align:start position:0% design like in the 2017 and where there 00:01:21.270 --> 00:01:24.560 align:start position:0% design like in the 2017 and where there were<00:01:21.540> no<00:01:21.990> beacon<00:01:22.440> chain<00:01:22.740> between<00:01:23.250> the<00:01:23.820> East 00:01:24.560 --> 00:01:24.570 align:start position:0% were no beacon chain between the East 00:01:24.570 --> 00:01:27.320 align:start position:0% were no beacon chain between the East one<00:01:24.810> chain<00:01:25.080> and<00:01:25.440> is<00:01:25.740> to<00:01:25.950> chain<00:01:26.250> and<00:01:26.580> The 00:01:27.320 --> 00:01:27.330 align:start position:0% one chain and is to chain and The 00:01:27.330 --> 00:01:29.300 align:start position:0% one chain and is to chain and The Shining<00:01:27.510> trains<00:01:27.900> are<00:01:28.110> actually<00:01:28.530> they<00:01:29.040> were 00:01:29.300 --> 00:01:29.310 align:start position:0% Shining trains are actually they were 00:01:29.310 --> 00:01:32.720 align:start position:0% Shining trains are actually they were depending<00:01:30.030> on<00:01:30.180> the<00:01:30.450> expansion<00:01:31.460> but<00:01:32.460> however 00:01:32.720 --> 00:01:32.730 align:start position:0% depending on the expansion but however 00:01:32.730 --> 00:01:36.140 align:start position:0% depending on the expansion but however even<00:01:33.450> with<00:01:33.780> the<00:01:34.140> become<00:01:34.560> chain<00:01:34.800> we<00:01:35.670> still<00:01:35.880> have 00:01:36.140 --> 00:01:36.150 align:start position:0% even with the become chain we still have 00:01:36.150 --> 00:01:39.460 align:start position:0% even with the become chain we still have to<00:01:36.750> comfort<00:01:37.320> the<00:01:37.710> backward-compatible 00:01:39.460 --> 00:01:39.470 align:start position:0% to comfort the backward-compatible 00:01:39.470 --> 00:01:45.190 align:start position:0% to comfort the backward-compatible issues<00:01:40.470> for<00:01:40.890> it<00:01:41.070> and<00:01:41.870> for<00:01:42.870> the<00:01:43.170> design<00:01:43.860> areas 00:01:45.190 --> 00:01:45.200 align:start position:0% issues for it and for the design areas 00:01:45.200 --> 00:01:49.820 align:start position:0% issues for it and for the design areas something<00:01:46.430> sometimes<00:01:47.430> is<00:01:47.670> vertical<00:01:48.590> in<00:01:49.590> some 00:01:49.820 --> 00:01:49.830 align:start position:0% something sometimes is vertical in some 00:01:49.830 --> 00:01:59.819 align:start position:0% something sometimes is vertical in some highs<00:01:50.100> is<00:01:50.540> horizontal 00:01:59.819 --> 00:01:59.829 align:start position:0% 00:01:59.829 --> 00:02:05.270 align:start position:0% and<00:02:00.100> that<00:02:00.909> I<00:02:02.220> recall<00:02:03.220> that<00:02:03.490> that<00:02:03.850> in<00:02:04.210> 2017 00:02:05.270 --> 00:02:05.280 align:start position:0% and that I recall that that in 2017 00:02:05.280 --> 00:02:08.430 align:start position:0% and that I recall that that in 2017 research<00:02:06.280> King<00:02:06.700> has<00:02:07.060> received<00:02:07.840> some<00:02:08.170> feedback 00:02:08.430 --> 00:02:08.440 align:start position:0% research King has received some feedback 00:02:08.440 --> 00:02:11.190 align:start position:0% research King has received some feedback from<00:02:08.979> community<00:02:09.509> found<00:02:10.509> the<00:02:10.720> client<00:02:11.050> thinks 00:02:11.190 --> 00:02:11.200 align:start position:0% from community found the client thinks 00:02:11.200 --> 00:02:14.750 align:start position:0% from community found the client thinks that<00:02:11.680> we<00:02:12.310> should<00:02:12.340> have<00:02:12.819> more<00:02:13.209> incremental<00:02:13.720> ism 00:02:14.750 --> 00:02:14.760 align:start position:0% that we should have more incremental ism 00:02:14.760 --> 00:02:20.790 align:start position:0% that we should have more incremental ism in<00:02:15.760> the<00:02:16.060> design<00:02:16.780> philosophy<00:02:18.569> that<00:02:19.569> is<00:02:19.900> to<00:02:20.620> add 00:02:20.790 --> 00:02:20.800 align:start position:0% in the design philosophy that is to add 00:02:20.800 --> 00:02:26.660 align:start position:0% in the design philosophy that is to add more<00:02:21.630> to<00:02:22.630> add<00:02:22.780> many<00:02:23.130> small<00:02:24.130> incremental<00:02:25.060> steps 00:02:26.660 --> 00:02:26.670 align:start position:0% more to add many small incremental steps 00:02:26.670 --> 00:02:30.390 align:start position:0% more to add many small incremental steps step<00:02:27.670> by<00:02:27.790> step<00:02:28.060> changes<00:02:28.590> instead<00:02:29.590> of<00:02:29.860> a<00:02:29.890> few 00:02:30.390 --> 00:02:30.400 align:start position:0% step by step changes instead of a few 00:02:30.400 --> 00:02:36.360 align:start position:0% step by step changes instead of a few large<00:02:31.390> sounder<00:02:32.019> drugs<00:02:33.600> to<00:02:34.600> compare<00:02:35.260> this<00:02:35.560> to 00:02:36.360 --> 00:02:36.370 align:start position:0% large sounder drugs to compare this to 00:02:36.370 --> 00:02:39.449 align:start position:0% large sounder drugs to compare this to different<00:02:36.640> strategies<00:02:37.510> and<00:02:38.010> for<00:02:39.010> example 00:02:39.449 --> 00:02:39.459 align:start position:0% different strategies and for example 00:02:39.459 --> 00:02:42.390 align:start position:0% different strategies and for example when<00:02:39.850> we<00:02:40.090> are<00:02:40.120> building<00:02:40.450> a<00:02:41.019> city<00:02:41.950> with 00:02:42.390 --> 00:02:42.400 align:start position:0% when we are building a city with 00:02:42.400 --> 00:02:46.470 align:start position:0% when we are building a city with incremental<00:02:43.349> strategy<00:02:44.910> we<00:02:45.910> should<00:02:46.180> start 00:02:46.470 --> 00:02:46.480 align:start position:0% incremental strategy we should start 00:02:46.480 --> 00:02:50.550 align:start position:0% incremental strategy we should start from<00:02:46.660> the<00:02:46.900> base<00:02:47.200> construction<00:02:48.190> and<00:02:49.560> then 00:02:50.550 --> 00:02:50.560 align:start position:0% from the base construction and then 00:02:50.560 --> 00:02:55.490 align:start position:0% from the base construction and then build<00:02:50.980> the<00:02:51.130> small<00:02:51.630> small<00:02:52.630> houses<00:02:52.950> and<00:02:54.000> then 00:02:55.490 --> 00:02:55.500 align:start position:0% build the small small houses and then 00:02:55.500 --> 00:02:58.740 align:start position:0% build the small small houses and then nearby<00:02:56.500> the<00:02:56.680> small<00:02:57.220> houses<00:02:57.400> we<00:02:58.090> build<00:02:58.390> higher 00:02:58.740 --> 00:02:58.750 align:start position:0% nearby the small houses we build higher 00:02:58.750 --> 00:03:02.759 align:start position:0% nearby the small houses we build higher buildings<00:02:59.349> the<00:03:00.340> last<00:03:00.810> incremental<00:03:01.810> saying 00:03:02.759 --> 00:03:02.769 align:start position:0% buildings the last incremental saying 00:03:02.769 --> 00:03:07.340 align:start position:0% buildings the last incremental saying looks<00:03:03.100> like<00:03:03.450> and<00:03:04.450> for<00:03:05.109> the<00:03:05.230> sound<00:03:05.470> ins<00:03:05.680> and 00:03:07.340 --> 00:03:07.350 align:start position:0% looks like and for the sound ins and 00:03:07.350 --> 00:03:09.960 align:start position:0% looks like and for the sound ins and with<00:03:08.350> the<00:03:08.560> southern<00:03:08.950> implantation 00:03:09.960 --> 00:03:09.970 align:start position:0% with the southern implantation 00:03:09.970 --> 00:03:12.930 align:start position:0% with the southern implantation we<00:03:10.750> would<00:03:10.989> draw<00:03:11.230> the<00:03:11.290> blueprint<00:03:12.190> very<00:03:12.640> very 00:03:12.930 --> 00:03:12.940 align:start position:0% we would draw the blueprint very very 00:03:12.940 --> 00:03:17.059 align:start position:0% we would draw the blueprint very very carefully<00:03:13.600> and<00:03:14.489> start<00:03:15.489> to<00:03:15.760> contract<00:03:16.269> and 00:03:17.059 --> 00:03:17.069 align:start position:0% carefully and start to contract and 00:03:17.069 --> 00:03:24.300 align:start position:0% carefully and start to contract and suddenly<00:03:18.069> the<00:03:18.519> castle<00:03:19.299> just<00:03:19.420> landed<00:03:20.790> so<00:03:23.310> I'd 00:03:24.300 --> 00:03:24.310 align:start position:0% suddenly the castle just landed so I'd 00:03:24.310 --> 00:03:27.210 align:start position:0% suddenly the castle just landed so I'd say<00:03:24.670> that<00:03:25.079> current<00:03:26.079> the<00:03:26.170> current<00:03:26.380> approach<00:03:26.739> in 00:03:27.210 --> 00:03:27.220 align:start position:0% say that current the current approach in 00:03:27.220 --> 00:03:30.979 align:start position:0% say that current the current approach in each<00:03:27.609> row<00:03:27.850> is<00:03:28.090> much<00:03:28.389> more<00:03:29.459> toward 00:03:30.979 --> 00:03:30.989 align:start position:0% each row is much more toward 00:03:30.989 --> 00:03:35.729 align:start position:0% each row is much more toward incrementalist<00:03:31.989> and<00:03:32.230> design<00:03:32.850> but<00:03:34.739> there's 00:03:35.729 --> 00:03:35.739 align:start position:0% incrementalist and design but there's 00:03:35.739 --> 00:03:37.949 align:start position:0% incrementalist and design but there's still<00:03:36.220> something<00:03:36.760> that<00:03:37.209> we<00:03:37.510> need<00:03:37.660> to<00:03:37.780> think 00:03:37.949 --> 00:03:37.959 align:start position:0% still something that we need to think 00:03:37.959 --> 00:03:43.200 align:start position:0% still something that we need to think about 00:03:43.200 --> 00:03:43.210 align:start position:0% 00:03:43.210 --> 00:03:50.500 align:start position:0% so<00:03:44.210> the<00:03:46.060> disadvantage<00:03:47.060> of<00:03:47.800> the<00:03:49.510> incremental 00:03:50.500 --> 00:03:50.510 align:start position:0% so the disadvantage of the incremental 00:03:50.510 --> 00:03:55.990 align:start position:0% so the disadvantage of the incremental decides<00:03:51.020> that<00:03:52.209> -<00:03:53.209> in<00:03:54.020> the<00:03:54.260> part<00:03:55.040> of<00:03:55.190> you<00:03:55.400> can 00:03:55.990 --> 00:03:56.000 align:start position:0% decides that - in the part of you can 00:03:56.000 --> 00:03:58.780 align:start position:0% decides that - in the part of you can see<00:03:56.180> that<00:03:56.390> in<00:03:57.020> my<00:03:57.230> waist<00:03:57.650> on<00:03:57.830> time<00:03:58.069> to<00:03:58.490> build 00:03:58.780 --> 00:03:58.790 align:start position:0% see that in my waist on time to build 00:03:58.790 --> 00:04:05.199 align:start position:0% see that in my waist on time to build the<00:03:59.240> face<00:03:59.540> and<00:03:59.810> faces<00:04:00.670> and<00:04:01.670> let's<00:04:02.450> also<00:04:04.209> the 00:04:05.199 --> 00:04:05.209 align:start position:0% the face and faces and let's also the 00:04:05.209 --> 00:04:09.550 align:start position:0% the face and faces and let's also the Beco<00:04:05.800> fallacy<00:04:06.820> seeing<00:04:07.820> can<00:04:08.660> see<00:04:08.930> they<00:04:09.080> start<00:04:09.380> a 00:04:09.550 --> 00:04:09.560 align:start position:0% Beco fallacy seeing can see they start a 00:04:09.560 --> 00:04:12.400 align:start position:0% Beco fallacy seeing can see they start a picot<00:04:10.010> it<00:04:10.730> has<00:04:10.910> a<00:04:11.150> very<00:04:11.480> very<00:04:11.660> good<00:04:11.780> sense<00:04:12.290> of 00:04:12.400 --> 00:04:12.410 align:start position:0% picot it has a very very good sense of 00:04:12.410 --> 00:04:13.240 align:start position:0% picot it has a very very good sense of smell 00:04:13.240 --> 00:04:13.250 align:start position:0% smell 00:04:13.250 --> 00:04:18.400 align:start position:0% smell but<00:04:14.030> we've<00:04:14.600> very<00:04:15.500> limited<00:04:16.100> I'll<00:04:16.430> I<00:04:16.760> sigh<00:04:17.410> so 00:04:18.400 --> 00:04:18.410 align:start position:0% but we've very limited I'll I sigh so 00:04:18.410 --> 00:04:21.159 align:start position:0% but we've very limited I'll I sigh so it's<00:04:18.560> possible<00:04:18.880> they're<00:04:19.880> praised<00:04:20.450> just<00:04:20.840> found 00:04:21.159 --> 00:04:21.169 align:start position:0% it's possible they're praised just found 00:04:21.169 --> 00:04:23.920 align:start position:0% it's possible they're praised just found out<00:04:21.290> them<00:04:21.470> but<00:04:21.950> it<00:04:22.070> sounds<00:04:22.460> winked<00:04:23.210> so<00:04:23.720> like 00:04:23.920 --> 00:04:23.930 align:start position:0% out them but it sounds winked so like 00:04:23.930 --> 00:04:26.620 align:start position:0% out them but it sounds winked so like can<00:04:24.169> see<00:04:24.410> that<00:04:25.010> the<00:04:25.190> prey<00:04:25.430> even<00:04:25.669> if<00:04:26.000> read<00:04:26.510> it's 00:04:26.620 --> 00:04:26.630 align:start position:0% can see that the prey even if read it's 00:04:26.630 --> 00:04:30.659 align:start position:0% can see that the prey even if read it's very<00:04:26.810> close<00:04:27.050> to<00:04:27.080> it<00:04:27.490> so<00:04:28.490> so<00:04:29.090> is<00:04:29.330> that<00:04:29.690> in<00:04:29.960> the 00:04:30.659 --> 00:04:30.669 align:start position:0% very close to it so so is that in the 00:04:30.669 --> 00:04:36.460 align:start position:0% very close to it so so is that in the local<00:04:31.669> decide<00:04:34.270> so<00:04:35.270> that's<00:04:35.600> why<00:04:35.930> we<00:04:36.260> usually 00:04:36.460 --> 00:04:36.470 align:start position:0% local decide so that's why we usually 00:04:36.470 --> 00:04:39.880 align:start position:0% local decide so that's why we usually have<00:04:37.010> to<00:04:37.280> go<00:04:37.610> back<00:04:37.880> elbows<00:04:38.419> and<00:04:38.750> to<00:04:39.650> fix 00:04:39.880 --> 00:04:39.890 align:start position:0% have to go back elbows and to fix 00:04:39.890 --> 00:04:47.830 align:start position:0% have to go back elbows and to fix problem<00:04:40.370> that<00:04:40.940> are<00:04:41.150> hiding<00:04:41.450> somewhere<00:04:45.550> and<00:04:46.840> ok 00:04:47.830 --> 00:04:47.840 align:start position:0% problem that are hiding somewhere and ok 00:04:47.840 --> 00:04:51.550 align:start position:0% problem that are hiding somewhere and ok so<00:04:48.130> classic<00:04:49.130> and<00:04:49.340> I<00:04:49.690> organized<00:04:50.690> survey 00:04:51.550 --> 00:04:51.560 align:start position:0% so classic and I organized survey 00:04:51.560 --> 00:04:55.120 align:start position:0% so classic and I organized survey recently<00:04:51.970> the<00:04:52.970> survey<00:04:53.240> was<00:04:53.450> for<00:04:53.900> the<00:04:54.260> external 00:04:55.120 --> 00:04:55.130 align:start position:0% recently the survey was for the external 00:04:55.130 --> 00:04:57.760 align:start position:0% recently the survey was for the external community<00:04:55.250> and<00:04:55.850> especially<00:04:56.360> the<00:04:57.140> developers 00:04:57.760 --> 00:04:57.770 align:start position:0% community and especially the developers 00:04:57.770 --> 00:05:03.430 align:start position:0% community and especially the developers and<00:04:58.390> one<00:04:59.390> of<00:04:59.510> the<00:04:59.660> question<00:05:00.110> is<00:05:01.210> what<00:05:02.440> portion 00:05:03.430 --> 00:05:03.440 align:start position:0% and one of the question is what portion 00:05:03.440 --> 00:05:07.590 align:start position:0% and one of the question is what portion properties<00:05:04.160> or<00:05:04.870> functionalities<00:05:05.870> do<00:05:06.650> we 00:05:07.590 --> 00:05:07.600 align:start position:0% properties or functionalities do we 00:05:07.600 --> 00:05:08.770 align:start position:0% properties or functionalities do we sorry 00:05:08.770 --> 00:05:08.780 align:start position:0% sorry 00:05:08.780 --> 00:05:12.760 align:start position:0% sorry do<00:05:09.350> you<00:05:09.500> want<00:05:09.800> to<00:05:09.950> see<00:05:11.020> implemented<00:05:12.020> in<00:05:12.470> East 00:05:12.760 --> 00:05:12.770 align:start position:0% do you want to see implemented in East 00:05:12.770 --> 00:05:17.460 align:start position:0% do you want to see implemented in East 200<00:05:13.010> or<00:05:13.430> is<00:05:13.820> to<00:05:14.060> one<00:05:14.360> point<00:05:14.540> X<00:05:15.190> so<00:05:16.190> we<00:05:16.370> got<00:05:16.550> about 00:05:17.460 --> 00:05:17.470 align:start position:0% 200 or is to one point X so we got about 00:05:17.470 --> 00:05:20.230 align:start position:0% 200 or is to one point X so we got about sixty<00:05:18.470> nine<00:05:18.620> people<00:05:19.040> answered<00:05:19.610> a<00:05:19.760> structure 00:05:20.230 --> 00:05:20.240 align:start position:0% sixty nine people answered a structure 00:05:20.240 --> 00:05:24.400 align:start position:0% sixty nine people answered a structure and<00:05:20.630> I<00:05:21.140> categorized<00:05:21.890> them<00:05:22.130> with<00:05:22.760> some<00:05:23.540> simple 00:05:24.400 --> 00:05:24.410 align:start position:0% and I categorized them with some simple 00:05:24.410 --> 00:05:32.500 align:start position:0% and I categorized them with some simple text<00:05:25.210> below<00:05:27.760> and<00:05:29.770> the<00:05:30.770> top<00:05:31.220> three<00:05:31.490> wishes 00:05:32.500 --> 00:05:32.510 align:start position:0% text below and the top three wishes 00:05:32.510 --> 00:05:36.250 align:start position:0% text below and the top three wishes there<00:05:32.930> are<00:05:34.030> scalability<00:05:35.030> is<00:05:35.090> proof<00:05:35.840> of<00:05:35.960> stake 00:05:36.250 --> 00:05:36.260 align:start position:0% there are scalability is proof of stake 00:05:36.260 --> 00:05:39.730 align:start position:0% there are scalability is proof of stake and<00:05:37.300> get<00:05:38.300> a<00:05:38.330> free<00:05:38.810> model<00:05:39.050> increment 00:05:39.730 --> 00:05:39.740 align:start position:0% and get a free model increment 00:05:39.740 --> 00:05:43.120 align:start position:0% and get a free model increment improvement<00:05:41.169> those<00:05:42.169> three<00:05:42.680> different 00:05:43.120 --> 00:05:43.130 align:start position:0% improvement those three different 00:05:43.130 --> 00:05:46.390 align:start position:0% improvement those three different requirements<00:05:44.000> but<00:05:44.510> at<00:05:45.110> some<00:05:45.350> point<00:05:45.380> they<00:05:46.370> are 00:05:46.390 --> 00:05:46.400 align:start position:0% requirements but at some point they are 00:05:46.400 --> 00:05:48.580 align:start position:0% requirements but at some point they are overlapping<00:05:47.120> I'm<00:05:47.840> sorry 00:05:48.580 --> 00:05:48.590 align:start position:0% overlapping I'm sorry 00:05:48.590 --> 00:05:51.790 align:start position:0% overlapping I'm sorry [Music] 00:05:51.790 --> 00:05:51.800 align:start position:0% [Music] 00:05:51.800 --> 00:05:55.730 align:start position:0% [Music] they<00:05:52.800> are<00:05:52.860> all<00:05:53.040> rapping<00:05:53.580> in<00:05:54.540> the<00:05:54.840> is<00:05:55.260> to<00:05:55.530> old 00:05:55.730 --> 00:05:55.740 align:start position:0% they are all rapping in the is to old 00:05:55.740 --> 00:06:01.430 align:start position:0% they are all rapping in the is to old design<00:05:56.160> map<00:05:58.220> so<00:05:59.220> I<00:05:59.840> select<00:06:00.840> some<00:06:01.080> of<00:06:01.110> the 00:06:01.430 --> 00:06:01.440 align:start position:0% design map so I select some of the 00:06:01.440 --> 00:06:04.070 align:start position:0% design map so I select some of the topics<00:06:01.710> based<00:06:02.430> on<00:06:02.700> the<00:06:02.970> top<00:06:03.210> wishes<00:06:03.570> today<00:06:03.900> to 00:06:04.070 --> 00:06:04.080 align:start position:0% topics based on the top wishes today to 00:06:04.080 --> 00:06:10.540 align:start position:0% topics based on the top wishes today to introduce<00:06:04.500> to<00:06:04.740> you<00:06:07.100> and<00:06:08.240> this<00:06:09.240> three<00:06:09.720> topics 00:06:10.540 --> 00:06:10.550 align:start position:0% introduce to you and this three topics 00:06:10.550 --> 00:06:14.870 align:start position:0% introduce to you and this three topics include<00:06:11.550> the<00:06:11.580> abstract<00:06:12.270> and<00:06:13.850> stretching<00:06:14.850> and 00:06:14.870 --> 00:06:14.880 align:start position:0% include the abstract and stretching and 00:06:14.880 --> 00:06:19.220 align:start position:0% include the abstract and stretching and application<00:06:15.840> and<00:06:16.910> some<00:06:17.910> significant<00:06:18.720> changes 00:06:19.220 --> 00:06:19.230 align:start position:0% application and some significant changes 00:06:19.230 --> 00:06:22.580 align:start position:0% application and some significant changes I<00:06:19.410> will<00:06:19.680> have<00:06:19.920> him<00:06:20.190> English<00:06:20.760> -<00:06:20.940> all<00:06:21.590> shouting 00:06:22.580 --> 00:06:22.590 align:start position:0% I will have him English - all shouting 00:06:22.590 --> 00:06:29.870 align:start position:0% I will have him English - all shouting universe<00:06:26.720> so<00:06:27.720> the<00:06:28.050> first<00:06:28.290> one<00:06:28.500> is<00:06:28.680> there<00:06:29.580> one 00:06:29.870 --> 00:06:29.880 align:start position:0% universe so the first one is there one 00:06:29.880 --> 00:06:33.950 align:start position:0% universe so the first one is there one account<00:06:30.360> abstract<00:06:31.280> so<00:06:32.360> it<00:06:33.360> has<00:06:33.750> been 00:06:33.950 --> 00:06:33.960 align:start position:0% account abstract so it has been 00:06:33.960 --> 00:06:36.290 align:start position:0% account abstract so it has been discussed<00:06:34.470> in<00:06:34.740> the<00:06:35.040> East<00:06:35.220> one<00:06:35.550> point<00:06:35.820> acts<00:06:36.060> as 00:06:36.290 --> 00:06:36.300 align:start position:0% discussed in the East one point acts as 00:06:36.300 --> 00:06:41.710 align:start position:0% discussed in the East one point acts as well<00:06:36.540> that<00:06:37.490> in<00:06:38.490> the<00:06:39.180> abstract<00:06:39.720> account<00:06:40.670> model 00:06:41.710 --> 00:06:41.720 align:start position:0% well that in the abstract account model 00:06:41.720 --> 00:06:46.670 align:start position:0% well that in the abstract account model all<00:06:42.720> contracts<00:06:43.350> are<00:06:44.160> for<00:06:44.220> world<00:06:45.000> cultures<00:06:45.680> so 00:06:46.670 --> 00:06:46.680 align:start position:0% all contracts are for world cultures so 00:06:46.680 --> 00:06:50.870 align:start position:0% all contracts are for world cultures so there's<00:06:47.220> no<00:06:48.590> all<00:06:49.590> count<00:06:50.220> are<00:06:50.490> forward 00:06:50.870 --> 00:06:50.880 align:start position:0% there's no all count are forward 00:06:50.880 --> 00:06:54.650 align:start position:0% there's no all count are forward contracts<00:06:51.570> so<00:06:52.530> there<00:06:53.430> are<00:06:53.490> two<00:06:53.730> main<00:06:54.030> strategy 00:06:54.650 --> 00:06:54.660 align:start position:0% contracts so there are two main strategy 00:06:54.660 --> 00:06:59.270 align:start position:0% contracts so there are two main strategy why<00:06:54.990> is<00:06:55.050> the<00:06:55.560> after<00:06:56.460> we<00:06:57.420> only<00:06:58.070> abstract<00:06:59.070> the 00:06:59.270 --> 00:06:59.280 align:start position:0% why is the after we only abstract the 00:06:59.280 --> 00:07:02.300 align:start position:0% why is the after we only abstract the signature<00:06:59.970> and<00:07:00.180> another<00:07:00.990> one<00:07:01.200> is<00:07:01.380> we<00:07:01.590> do<00:07:01.800> for 00:07:02.300 --> 00:07:02.310 align:start position:0% signature and another one is we do for 00:07:02.310 --> 00:07:05.090 align:start position:0% signature and another one is we do for abstraction<00:07:03.120> include<00:07:03.780> the<00:07:03.930> nouns<00:07:04.200> gas<00:07:04.680> and 00:07:05.090 --> 00:07:05.100 align:start position:0% abstraction include the nouns gas and 00:07:05.100 --> 00:07:10.630 align:start position:0% abstraction include the nouns gas and payment<00:07:05.790> and<00:07:08.570> sorry 00:07:10.630 --> 00:07:10.640 align:start position:0% payment and sorry 00:07:10.640 --> 00:07:17.950 align:start position:0% payment and sorry and<00:07:12.650> with<00:07:13.650> the<00:07:13.860> guaranteed<00:07:14.750> transactions<00:07:15.750> and 00:07:17.950 --> 00:07:17.960 align:start position:0% and with the guaranteed transactions and 00:07:17.960 --> 00:07:23.060 align:start position:0% and with the guaranteed transactions and also<00:07:18.960> if<00:07:19.800> we<00:07:20.070> plug<00:07:20.370> into<00:07:20.640> the<00:07:21.000> east<00:07:21.240> to<00:07:21.450> e<00:07:21.480> es<00:07:22.070> we 00:07:23.060 --> 00:07:23.070 align:start position:0% also if we plug into the east to e es we 00:07:23.070 --> 00:07:26.480 align:start position:0% also if we plug into the east to e es we will<00:07:23.280> have<00:07:23.580> the<00:07:24.320> EE<00:07:25.320> can<00:07:25.770> have<00:07:26.040> its<00:07:26.310> own 00:07:26.480 --> 00:07:26.490 align:start position:0% will have the EE can have its own 00:07:26.490 --> 00:07:31.700 align:start position:0% will have the EE can have its own different<00:07:28.970> execution<00:07:29.970> environment<00:07:30.660> and<00:07:30.870> also 00:07:31.700 --> 00:07:31.710 align:start position:0% different execution environment and also 00:07:31.710 --> 00:07:34.960 align:start position:0% different execution environment and also each<00:07:32.160> environment<00:07:32.910> can<00:07:33.420> have<00:07:33.690> different 00:07:34.960 --> 00:07:34.970 align:start position:0% each environment can have different 00:07:34.970 --> 00:07:39.290 align:start position:0% each environment can have different account<00:07:35.970> abstract<00:07:36.500> model<00:07:37.500> inside<00:07:38.030> so<00:07:39.030> it's 00:07:39.290 --> 00:07:39.300 align:start position:0% account abstract model inside so it's 00:07:39.300 --> 00:07:43.760 align:start position:0% account abstract model inside so it's very<00:07:39.420> fixed<00:07:40.320> flexible<00:07:41.190> and<00:07:41.690> very<00:07:42.690> easy<00:07:43.620> to 00:07:43.760 --> 00:07:43.770 align:start position:0% very fixed flexible and very easy to 00:07:43.770 --> 00:07:50.720 align:start position:0% very fixed flexible and very easy to plug<00:07:44.100> into<00:07:44.430> the<00:07:45.060> one<00:07:45.240> to<00:07:45.420> each<00:07:45.570> other<00:07:49.730> another 00:07:50.720 --> 00:07:50.730 align:start position:0% plug into the one to each other another 00:07:50.730 --> 00:07:54.950 align:start position:0% plug into the one to each other another topic<00:07:51.210> I<00:07:51.330> want<00:07:51.540> to<00:07:51.600> talk<00:07:51.720> about<00:07:52.020> is<00:07:52.380> the<00:07:52.710> IP<00:07:53.960> 151 00:07:54.950 --> 00:07:54.960 align:start position:0% topic I want to talk about is the IP 151 00:07:54.960 --> 00:07:58.130 align:start position:0% topic I want to talk about is the IP 151 five<00:07:55.410> five<00:07:55.800> nine<00:07:56.300> it's<00:07:57.300> the<00:07:57.480> free<00:07:57.750> market 00:07:58.130 --> 00:07:58.140 align:start position:0% five five nine it's the free market 00:07:58.140 --> 00:07:59.640 align:start position:0% five five nine it's the free market model<00:07:58.560> change 00:07:59.640 --> 00:07:59.650 align:start position:0% model change 00:07:59.650 --> 00:08:03.780 align:start position:0% model change created<00:08:00.160> by<00:08:00.190> italic<00:08:00.940> and<00:08:01.180> Eric<00:08:01.660> corner<00:08:01.990> and<00:08:02.790> so 00:08:03.780 --> 00:08:03.790 align:start position:0% created by italic and Eric corner and so 00:08:03.790 --> 00:08:07.140 align:start position:0% created by italic and Eric corner and so in<00:08:04.120> this<00:08:04.630> scheme<00:08:05.020> we<00:08:05.620> will<00:08:05.800> have<00:08:06.130> a<00:08:06.160> dynamic 00:08:07.140 --> 00:08:07.150 align:start position:0% in this scheme we will have a dynamic 00:08:07.150 --> 00:08:10.860 align:start position:0% in this scheme we will have a dynamic pest<00:08:07.780> free<00:08:08.440> value<00:08:09.430> and<00:08:09.790> this<00:08:10.389> value<00:08:10.479> is 00:08:10.860 --> 00:08:10.870 align:start position:0% pest free value and this value is 00:08:10.870 --> 00:08:15.000 align:start position:0% pest free value and this value is addressed<00:08:11.440> by<00:08:11.590> the<00:08:11.880> lights<00:08:12.880> nation<00:08:13.690> rate<00:08:14.229> so 00:08:15.000 --> 00:08:15.010 align:start position:0% addressed by the lights nation rate so 00:08:15.010 --> 00:08:18.659 align:start position:0% addressed by the lights nation rate so if<00:08:15.280> the<00:08:15.490> ionization<00:08:15.820> rate<00:08:16.330> is<00:08:16.570> is<00:08:17.440> over<00:08:17.889> 50 00:08:18.659 --> 00:08:18.669 align:start position:0% if the ionization rate is is over 50 00:08:18.669 --> 00:08:21.870 align:start position:0% if the ionization rate is is over 50 percent<00:08:18.900> this<00:08:19.900> special<00:08:20.830> variable<00:08:21.370> will<00:08:21.580> be 00:08:21.870 --> 00:08:21.880 align:start position:0% percent this special variable will be 00:08:21.880 --> 00:08:27.420 align:start position:0% percent this special variable will be well<00:08:22.870> increase<00:08:23.380> and<00:08:23.800> if<00:08:24.729> it's<00:08:25.290> sorry<00:08:26.290> if<00:08:27.160> the 00:08:27.420 --> 00:08:27.430 align:start position:0% well increase and if it's sorry if the 00:08:27.430 --> 00:08:29.670 align:start position:0% well increase and if it's sorry if the realization<00:08:28.300> rate<00:08:28.540> is<00:08:28.720> under<00:08:29.050> 50<00:08:29.560> percent 00:08:29.670 --> 00:08:29.680 align:start position:0% realization rate is under 50 percent 00:08:29.680 --> 00:08:36.839 align:start position:0% realization rate is under 50 percent this<00:08:30.460> this<00:08:31.270> very<00:08:31.660> well<00:08:31.990> be<00:08:32.200> decrease<00:08:33.180> so<00:08:35.849> so 00:08:36.839 --> 00:08:36.849 align:start position:0% this this very well be decrease so so 00:08:36.849 --> 00:08:40.320 align:start position:0% this this very well be decrease so so since<00:08:37.120> its<00:08:37.450> update<00:08:39.150> automatically 00:08:40.320 --> 00:08:40.330 align:start position:0% since its update automatically 00:08:40.330 --> 00:08:44.159 align:start position:0% since its update automatically it's<00:08:41.200> allowed<00:08:41.529> user<00:08:42.490> doesn't<00:08:42.909> have<00:08:43.240> to<00:08:43.510> do 00:08:44.159 --> 00:08:44.169 align:start position:0% it's allowed user doesn't have to do 00:08:44.169 --> 00:08:47.730 align:start position:0% it's allowed user doesn't have to do more<00:08:44.380> work<00:08:44.680> unless<00:08:45.130> the<00:08:46.050> quality<00:08:47.050> service<00:08:47.440> can 00:08:47.730 --> 00:08:47.740 align:start position:0% more work unless the quality service can 00:08:47.740 --> 00:08:51.650 align:start position:0% more work unless the quality service can help<00:08:48.070> to<00:08:48.300> define<00:08:49.300> the<00:08:50.110> fair<00:08:50.589> free<00:08:51.040> for<00:08:51.339> users 00:08:51.650 --> 00:08:51.660 align:start position:0% help to define the fair free for users 00:08:51.660 --> 00:08:58.050 align:start position:0% help to define the fair free for users so<00:08:52.660> it<00:08:52.990> actually<00:08:54.900> it's<00:08:55.900> actually<00:08:56.100> make<00:08:57.100> a<00:08:57.430> lot 00:08:58.050 --> 00:08:58.060 align:start position:0% so it actually it's actually make a lot 00:08:58.060 --> 00:08:59.940 align:start position:0% so it actually it's actually make a lot of<00:08:58.210> you<00:08:58.390> expert<00:08:58.810> early<00:08:59.260> and<00:08:59.380> the<00:08:59.529> current 00:08:59.940 --> 00:08:59.950 align:start position:0% of you expert early and the current 00:08:59.950 --> 00:09:04.710 align:start position:0% of you expert early and the current state<00:09:00.640> crow<00:09:01.350> so<00:09:02.350> and<00:09:03.040> also<00:09:03.430> the<00:09:03.640> past<00:09:03.910> few<00:09:04.089> is 00:09:04.710 --> 00:09:04.720 align:start position:0% state crow so and also the past few is 00:09:04.720 --> 00:09:08.640 align:start position:0% state crow so and also the past few is always<00:09:05.290> bird<00:09:05.730> this<00:09:06.730> design<00:09:07.630> rationale<00:09:08.170> is<00:09:08.380> to 00:09:08.640 --> 00:09:08.650 align:start position:0% always bird this design rationale is to 00:09:08.650 --> 00:09:12.199 align:start position:0% always bird this design rationale is to prevent<00:09:09.310> minor<00:09:09.790> or<00:09:10.150> the<00:09:10.480> proposer<00:09:10.930> from 00:09:12.199 --> 00:09:12.209 align:start position:0% prevent minor or the proposer from 00:09:12.209 --> 00:09:14.940 align:start position:0% prevent minor or the proposer from manipulating<00:09:13.209> the<00:09:13.360> field<00:09:13.720> in<00:09:14.380> order<00:09:14.589> to 00:09:14.940 --> 00:09:14.950 align:start position:0% manipulating the field in order to 00:09:14.950 --> 00:09:17.550 align:start position:0% manipulating the field in order to extract<00:09:15.370> more<00:09:15.730> fries<00:09:16.000> from<00:09:16.300> the<00:09:16.450> user<00:09:16.630> so 00:09:17.550 --> 00:09:17.560 align:start position:0% extract more fries from the user so 00:09:17.560 --> 00:09:21.449 align:start position:0% extract more fries from the user so generally<00:09:18.550> it<00:09:18.850> will<00:09:19.209> be<00:09:19.390> a<00:09:19.420> more<00:09:20.260> fair<00:09:20.680> model 00:09:21.449 --> 00:09:21.459 align:start position:0% generally it will be a more fair model 00:09:21.459 --> 00:09:26.670 align:start position:0% generally it will be a more fair model Leon<00:09:21.850> just<00:09:22.029> a<00:09:22.240> crow<00:09:24.420> and<00:09:25.420> before<00:09:26.410> talking 00:09:26.670 --> 00:09:26.680 align:start position:0% Leon just a crow and before talking 00:09:26.680 --> 00:09:30.120 align:start position:0% Leon just a crow and before talking about<00:09:26.800> shaking<00:09:27.459> I<00:09:28.140> want<00:09:29.140> to<00:09:29.290> mention<00:09:29.770> the 00:09:30.120 --> 00:09:30.130 align:start position:0% about shaking I want to mention the 00:09:30.130 --> 00:09:33.390 align:start position:0% about shaking I want to mention the transparent<00:09:30.730> future<00:09:31.029> again<00:09:31.480> some<00:09:32.380> cosmic<00:09:32.740> G 00:09:33.390 --> 00:09:33.400 align:start position:0% transparent future again some cosmic G 00:09:33.400 --> 00:09:36.360 align:start position:0% transparent future again some cosmic G is<00:09:33.640> the<00:09:33.910> finality<00:09:34.390> to<00:09:34.540> off<00:09:35.020> all<00:09:35.370> finality 00:09:36.360 --> 00:09:36.370 align:start position:0% is the finality to off all finality 00:09:36.370 --> 00:09:38.540 align:start position:0% is the finality to off all finality protocol<00:09:37.240> folder<00:09:37.660> is<00:09:37.779> too<00:09:38.020> old 00:09:38.540 --> 00:09:38.550 align:start position:0% protocol folder is too old 00:09:38.550 --> 00:09:44.460 align:start position:0% protocol folder is too old so<00:09:39.550> the<00:09:39.760> validator<00:09:42.089> the<00:09:43.089> duty<00:09:43.839> of<00:09:43.870> the<00:09:44.140> editor 00:09:44.460 --> 00:09:44.470 align:start position:0% so the validator the duty of the editor 00:09:44.470 --> 00:09:48.030 align:start position:0% so the validator the duty of the editor has<00:09:44.740> three<00:09:45.010> step<00:09:45.310> one<00:09:46.000> is<00:09:46.209> to<00:09:46.480> make<00:09:47.200> deposit<00:09:47.709> to 00:09:48.030 --> 00:09:48.040 align:start position:0% has three step one is to make deposit to 00:09:48.040 --> 00:09:50.790 align:start position:0% has three step one is to make deposit to the<00:09:48.220> east<00:09:48.430> ones<00:09:48.640> deposit<00:09:49.420> country<00:09:49.779> and<00:09:50.050> the 00:09:50.790 --> 00:09:50.800 align:start position:0% the east ones deposit country and the 00:09:50.800 --> 00:09:54.980 align:start position:0% the east ones deposit country and the second<00:09:51.100> one<00:09:51.279> is<00:09:51.630> when<00:09:52.650> the<00:09:53.650> block<00:09:53.920> has<00:09:54.250> enough 00:09:54.980 --> 00:09:54.990 align:start position:0% second one is when the block has enough 00:09:54.990 --> 00:10:00.720 align:start position:0% second one is when the block has enough has<00:09:55.990> to<00:09:56.230> vote<00:09:56.680> for<00:09:57.130> the<00:09:58.230> current<00:09:59.230> epoch<00:09:59.860> the 00:10:00.720 --> 00:10:00.730 align:start position:0% has to vote for the current epoch the 00:10:00.730 --> 00:10:04.470 align:start position:0% has to vote for the current epoch the current<00:10:01.150> change<00:10:01.589> checkpoints<00:10:02.589> and<00:10:03.180> if<00:10:04.180> the 00:10:04.470 --> 00:10:04.480 align:start position:0% current change checkpoints and if the 00:10:04.480 --> 00:10:08.010 align:start position:0% current change checkpoints and if the drip<00:10:05.440> point<00:10:05.650> got<00:10:06.010> in<00:10:06.250> enough<00:10:06.730> votes<00:10:07.180> we<00:10:07.750> call 00:10:08.010 --> 00:10:08.020 align:start position:0% drip point got in enough votes we call 00:10:08.020 --> 00:10:11.870 align:start position:0% drip point got in enough votes we call that<00:10:08.260> this<00:10:08.850> checkpoint<00:10:09.850> is<00:10:10.150> justified<00:10:10.959> and 00:10:11.870 --> 00:10:11.880 align:start position:0% that this checkpoint is justified and 00:10:11.880 --> 00:10:13.510 align:start position:0% that this checkpoint is justified and also 00:10:13.510 --> 00:10:13.520 align:start position:0% also 00:10:13.520 --> 00:10:17.410 align:start position:0% also if<00:10:13.610> the<00:10:14.140> checkpoint<00:10:15.140> is<00:10:15.670> it<00:10:16.730> if<00:10:17.240> the 00:10:17.410 --> 00:10:17.420 align:start position:0% if the checkpoint is it if the 00:10:17.420 --> 00:10:22.269 align:start position:0% if the checkpoint is it if the checkpoint<00:10:18.850> has<00:10:19.850> to<00:10:20.180> justify<00:10:21.040> descent<00:10:22.040> does 00:10:22.269 --> 00:10:22.279 align:start position:0% checkpoint has to justify descent does 00:10:22.279 --> 00:10:26.829 align:start position:0% checkpoint has to justify descent does we<00:10:22.970> call<00:10:23.209> it<00:10:23.330> this<00:10:23.630> buck<00:10:24.560> or<00:10:24.890> this<00:10:25.839> checkpoint 00:10:26.829 --> 00:10:26.839 align:start position:0% we call it this buck or this checkpoint 00:10:26.839 --> 00:10:31.810 align:start position:0% we call it this buck or this checkpoint is<00:10:27.290> got<00:10:28.029> finalized<00:10:29.649> so<00:10:30.649> that's<00:10:30.920> the<00:10:31.100> basic<00:10:31.610> of 00:10:31.810 --> 00:10:31.820 align:start position:0% is got finalized so that's the basic of 00:10:31.820 --> 00:10:39.550 align:start position:0% is got finalized so that's the basic of a<00:10:32.000> greater<00:10:32.209> duty<00:10:34.870> and<00:10:37.120> we<00:10:38.120> also<00:10:38.240> know<00:10:38.600> that<00:10:38.899> the 00:10:39.550 --> 00:10:39.560 align:start position:0% a greater duty and we also know that the 00:10:39.560 --> 00:10:42.790 align:start position:0% a greater duty and we also know that the me<00:10:40.490> misbehaved<00:10:41.330> very<00:10:41.899> data<00:10:42.080> never<00:10:42.470> got 00:10:42.790 --> 00:10:42.800 align:start position:0% me misbehaved very data never got 00:10:42.800 --> 00:10:48.070 align:start position:0% me misbehaved very data never got slashed<00:10:43.190> so<00:10:43.940> one<00:10:44.120> is<00:10:44.270> -<00:10:44.630> -<00:10:45.020> is<00:10:45.320> that<00:10:46.810> it<00:10:47.810> will 00:10:48.070 --> 00:10:48.080 align:start position:0% slashed so one is - - is that it will 00:10:48.080 --> 00:10:51.820 align:start position:0% slashed so one is - - is that it will import<00:10:48.890> wholly<00:10:49.220> they<00:10:50.209> were<00:10:50.330> the<00:10:51.290> top<00:10:51.529> two 00:10:51.820 --> 00:10:51.830 align:start position:0% import wholly they were the top two 00:10:51.830 --> 00:11:02.530 align:start position:0% import wholly they were the top two little<00:10:52.490> fellas<00:10:53.390> from<00:10:53.720> the<00:10:53.899> protocol<00:10:59.290> so<00:11:01.540> after 00:11:02.530 --> 00:11:02.540 align:start position:0% little fellas from the protocol so after 00:11:02.540 --> 00:11:05.290 align:start position:0% little fellas from the protocol so after migrating<00:11:02.959> the<00:11:03.470> tutor<00:11:04.250> for<00:11:04.490> prefers<00:11:05.060> tech 00:11:05.290 --> 00:11:05.300 align:start position:0% migrating the tutor for prefers tech 00:11:05.300 --> 00:11:07.630 align:start position:0% migrating the tutor for prefers tech system<00:11:05.750> it<00:11:06.200> will<00:11:06.470> introduce<00:11:06.830> a<00:11:07.190> new<00:11:07.399> economic 00:11:07.630 --> 00:11:07.640 align:start position:0% system it will introduce a new economic 00:11:07.640 --> 00:11:12.040 align:start position:0% system it will introduce a new economic model<00:11:08.740> so<00:11:09.740> :<00:11:10.100> Meijer<00:11:10.279> France<00:11:10.760> consensus<00:11:11.450> has 00:11:12.040 --> 00:11:12.050 align:start position:0% model so : Meijer France consensus has 00:11:12.050 --> 00:11:15.160 align:start position:0% model so : Meijer France consensus has been<00:11:12.110> working<00:11:12.560> on<00:11:12.770> this<00:11:13.010> economic<00:11:13.850> models<00:11:14.630> for 00:11:15.160 --> 00:11:15.170 align:start position:0% been working on this economic models for 00:11:15.170 --> 00:11:17.970 align:start position:0% been working on this economic models for a<00:11:15.200> while<00:11:15.410> and<00:11:15.890> the<00:11:16.550> model<00:11:16.910> is<00:11:17.060> based<00:11:17.330> on<00:11:17.570> the 00:11:17.970 --> 00:11:17.980 align:start position:0% a while and the model is based on the 00:11:17.980 --> 00:11:22.120 align:start position:0% a while and the model is based on the current<00:11:18.980> forints<00:11:19.610> faith<00:11:20.270> I<00:11:20.890> encourage<00:11:21.890> people 00:11:22.120 --> 00:11:22.130 align:start position:0% current forints faith I encourage people 00:11:22.130 --> 00:11:25.480 align:start position:0% current forints faith I encourage people especially<00:11:22.970> that<00:11:23.750> Aramis<00:11:24.350> to<00:11:24.920> take<00:11:25.220> a<00:11:25.250> look 00:11:25.480 --> 00:11:25.490 align:start position:0% especially that Aramis to take a look 00:11:25.490 --> 00:11:28.750 align:start position:0% especially that Aramis to take a look he's<00:11:26.060> a<00:11:26.360> work<00:11:26.660> and<00:11:27.020> if<00:11:27.529> to<00:11:27.649> get<00:11:27.860> feedback<00:11:28.160> for 00:11:28.750 --> 00:11:28.760 align:start position:0% he's a work and if to get feedback for 00:11:28.760 --> 00:11:32.680 align:start position:0% he's a work and if to get feedback for the<00:11:28.910> economic<00:11:29.360> side<00:11:30.250> so<00:11:31.250> similar<00:11:31.610> to<00:11:31.970> the<00:11:32.270> my 00:11:32.680 --> 00:11:32.690 align:start position:0% the economic side so similar to the my 00:11:32.690 --> 00:11:35.650 align:start position:0% the economic side so similar to the my poor<00:11:33.470> we<00:11:34.220> can<00:11:34.430> expand<00:11:34.940> that<00:11:34.970> their<00:11:35.300> work<00:11:35.480> is 00:11:35.650 --> 00:11:35.660 align:start position:0% poor we can expand that their work is 00:11:35.660 --> 00:11:39.130 align:start position:0% poor we can expand that their work is taking<00:11:36.110> poor<00:11:36.410> in<00:11:36.800> a<00:11:36.950> few<00:11:37.160> near<00:11:37.370> future<00:11:37.670> and<00:11:38.360> if 00:11:39.130 --> 00:11:39.140 align:start position:0% taking poor in a few near future and if 00:11:39.140 --> 00:11:41.440 align:start position:0% taking poor in a few near future and if the<00:11:39.410> military<00:11:39.950> are<00:11:40.130> not<00:11:40.190> alive<00:11:40.910> for<00:11:41.180> a<00:11:41.209> while 00:11:41.440 --> 00:11:41.450 align:start position:0% the military are not alive for a while 00:11:41.450 --> 00:11:46.660 align:start position:0% the military are not alive for a while and<00:11:41.810> they<00:11:42.770> can't<00:11:43.070> finalize<00:11:43.760> any<00:11:44.380> choice<00:11:45.670> so 00:11:46.660 --> 00:11:46.670 align:start position:0% and they can't finalize any choice so 00:11:46.670 --> 00:11:50.290 align:start position:0% and they can't finalize any choice so they<00:11:47.000> will<00:11:47.209> be<00:11:47.450> penalized<00:11:47.990> as<00:11:48.470> well<00:11:48.709> so<00:11:49.459> based 00:11:50.290 --> 00:11:50.300 align:start position:0% they will be penalized as well so based 00:11:50.300 --> 00:11:52.829 align:start position:0% they will be penalized as well so based on<00:11:50.450> that<00:11:50.510> it's<00:11:50.990> very<00:11:51.200> important<00:11:51.890> to<00:11:52.220> have<00:11:52.459> a 00:11:52.829 --> 00:11:52.839 align:start position:0% on that it's very important to have a 00:11:52.839 --> 00:11:56.199 align:start position:0% on that it's very important to have a stable<00:11:53.860> networking<00:11:54.860> environments<00:11:55.520> for<00:11:56.000> the 00:11:56.199 --> 00:11:56.209 align:start position:0% stable networking environments for the 00:11:56.209 --> 00:12:02.680 align:start position:0% stable networking environments for the proof<00:11:56.420> of<00:11:56.600> stake<00:11:57.459> very<00:11:58.459> leaders<00:12:01.180> and<00:12:02.180> the<00:12:02.390> next 00:12:02.680 --> 00:12:02.690 align:start position:0% proof of stake very leaders and the next 00:12:02.690 --> 00:12:06.510 align:start position:0% proof of stake very leaders and the next topic<00:12:02.930> is<00:12:03.200> about<00:12:03.350> the<00:12:03.740> network<00:12:04.130> latency<00:12:05.140> so 00:12:06.510 --> 00:12:06.520 align:start position:0% topic is about the network latency so 00:12:06.520 --> 00:12:11.500 align:start position:0% topic is about the network latency so this<00:12:07.520> message<00:12:08.060> are<00:12:08.300> the<00:12:08.600> most<00:12:10.240> overhead<00:12:11.240> of 00:12:11.500 --> 00:12:11.510 align:start position:0% this message are the most overhead of 00:12:11.510 --> 00:12:14.650 align:start position:0% this message are the most overhead of the<00:12:12.110> chatting<00:12:12.740> network<00:12:13.300> including<00:12:14.300> the 00:12:14.650 --> 00:12:14.660 align:start position:0% the chatting network including the 00:12:14.660 --> 00:12:17.430 align:start position:0% the chatting network including the attestations<00:12:15.350> which<00:12:16.100> is<00:12:16.279> the<00:12:16.610> vote<00:12:16.910> of<00:12:17.209> the 00:12:17.430 --> 00:12:17.440 align:start position:0% attestations which is the vote of the 00:12:17.440 --> 00:12:20.560 align:start position:0% attestations which is the vote of the between<00:12:18.440> the<00:12:18.589> country<00:12:19.130> and<00:12:19.370> the<00:12:19.910> shotshells 00:12:20.560 --> 00:12:20.570 align:start position:0% between the country and the shotshells 00:12:20.570 --> 00:12:25.180 align:start position:0% between the country and the shotshells and<00:12:21.820> the<00:12:22.820> second<00:12:23.089> one<00:12:23.209> is<00:12:23.390> the<00:12:24.190> translations 00:12:25.180 --> 00:12:25.190 align:start position:0% and the second one is the translations 00:12:25.190 --> 00:12:25.800 align:start position:0% and the second one is the translations so 00:12:25.800 --> 00:12:25.810 align:start position:0% so 00:12:25.810 --> 00:12:28.080 align:start position:0% so translations<00:12:26.410> only<00:12:26.800> in<00:12:27.400> the<00:12:27.730> shouting 00:12:28.080 --> 00:12:28.090 align:start position:0% translations only in the shouting 00:12:28.090 --> 00:12:31.590 align:start position:0% translations only in the shouting Network<00:12:28.450> and<00:12:29.340> also<00:12:30.340> there<00:12:30.610> are<00:12:30.640> blogs<00:12:31.150> are 00:12:31.590 --> 00:12:31.600 align:start position:0% Network and also there are blogs are 00:12:31.600 --> 00:12:34.019 align:start position:0% Network and also there are blogs are including<00:12:32.140> the<00:12:32.320> beacon<00:12:32.650> block<00:12:32.860> of<00:12:33.190> their<00:12:33.730> and 00:12:34.019 --> 00:12:34.029 align:start position:0% including the beacon block of their and 00:12:34.029 --> 00:12:40.620 align:start position:0% including the beacon block of their and also<00:12:34.270> the<00:12:34.570> shot<00:12:34.779> blocks<00:12:37.650> so<00:12:38.650> um<00:12:38.950> and<00:12:39.550> we<00:12:40.450> have 00:12:40.620 --> 00:12:40.630 align:start position:0% also the shot blocks so um and we have 00:12:40.630 --> 00:12:44.730 align:start position:0% also the shot blocks so um and we have costing<00:12:41.430> so<00:12:42.430> the<00:12:42.640> shot<00:12:42.880> block<00:12:43.150> will<00:12:43.600> point<00:12:44.410> to 00:12:44.730 --> 00:12:44.740 align:start position:0% costing so the shot block will point to 00:12:44.740 --> 00:12:46.980 align:start position:0% costing so the shot block will point to the<00:12:44.950> beacon<00:12:45.339> block<00:12:45.580> and<00:12:46.180> the<00:12:46.360> beacon<00:12:46.600> park 00:12:46.980 --> 00:12:46.990 align:start position:0% the beacon block and the beacon park 00:12:46.990 --> 00:12:50.340 align:start position:0% the beacon block and the beacon park would<00:12:47.710> refer<00:12:48.490> to<00:12:48.520> the<00:12:49.060> shot<00:12:49.300> block<00:12:49.510> sometimes 00:12:50.340 --> 00:12:50.350 align:start position:0% would refer to the shot block sometimes 00:12:50.350 --> 00:12:53.250 align:start position:0% would refer to the shot block sometimes that's<00:12:51.190> called<00:12:51.430> a<00:12:51.670> cross<00:12:51.910> link<00:12:52.180> so<00:12:53.170> the 00:12:53.250 --> 00:12:53.260 align:start position:0% that's called a cross link so the 00:12:53.260 --> 00:12:56.040 align:start position:0% that's called a cross link so the crossing<00:12:53.680> is<00:12:54.279> included<00:12:55.240> in<00:12:55.450> the<00:12:55.690> attestation 00:12:56.040 --> 00:12:56.050 align:start position:0% crossing is included in the attestation 00:12:56.050 --> 00:13:00.000 align:start position:0% crossing is included in the attestation data<00:12:56.790> per<00:12:57.790> shot<00:12:58.060> shell<00:12:58.360> and<00:12:58.710> then<00:12:59.710> God 00:13:00.000 --> 00:13:00.010 align:start position:0% data per shot shell and then God 00:13:00.010 --> 00:13:03.780 align:start position:0% data per shot shell and then God included<00:13:00.610> in<00:13:00.820> the<00:13:01.029> prod<00:13:01.270> in<00:13:01.810> the<00:13:01.960> attention<00:13:02.790> so 00:13:03.780 --> 00:13:03.790 align:start position:0% included in the prod in the attention so 00:13:03.790 --> 00:13:04.940 align:start position:0% included in the prod in the attention so also<00:13:03.970> the<00:13:04.330> Shadrin 00:13:04.940 --> 00:13:04.950 align:start position:0% also the Shadrin 00:13:04.950 --> 00:13:08.880 align:start position:0% also the Shadrin has<00:13:05.950> its<00:13:06.250> own<00:13:06.490> subnet<00:13:07.089> this<00:13:07.990> very<00:13:08.200> clear 00:13:08.880 --> 00:13:08.890 align:start position:0% has its own subnet this very clear 00:13:08.890 --> 00:13:11.280 align:start position:0% has its own subnet this very clear but<00:13:09.160> sometimes<00:13:09.670> the<00:13:09.910> cross<00:13:10.300> shot<00:13:10.600> and<00:13:11.050> they're 00:13:11.280 --> 00:13:11.290 align:start position:0% but sometimes the cross shot and they're 00:13:11.290 --> 00:13:18.110 align:start position:0% but sometimes the cross shot and they're working<00:13:11.790> communication<00:13:12.790> is<00:13:12.970> frequent<00:13:16.560> so 00:13:18.110 --> 00:13:18.120 align:start position:0% working communication is frequent so 00:13:18.120 --> 00:13:23.010 align:start position:0% working communication is frequent so with<00:13:19.120> the<00:13:19.390> latest<00:13:19.870> is<00:13:20.380> to<00:13:20.620> speak<00:13:20.920> we<00:13:21.910> have<00:13:22.020> four 00:13:23.010 --> 00:13:23.020 align:start position:0% with the latest is to speak we have four 00:13:23.020 --> 00:13:26.340 align:start position:0% with the latest is to speak we have four million<00:13:23.290> validators<00:13:24.270> 64<00:13:25.270> start<00:13:25.660> first<00:13:25.990> epoch 00:13:26.340 --> 00:13:26.350 align:start position:0% million validators 64 start first epoch 00:13:26.350 --> 00:13:31.500 align:start position:0% million validators 64 start first epoch and<00:13:26.650> six<00:13:27.960> seconds<00:13:28.960> become<00:13:29.440> black<00:13:29.680> time<00:13:29.980> and<00:13:30.510> we 00:13:31.500 --> 00:13:31.510 align:start position:0% and six seconds become black time and we 00:13:31.510 --> 00:13:35.990 align:start position:0% and six seconds become black time and we will<00:13:31.720> lead<00:13:31.960> to<00:13:32.290> sixty<00:13:33.220> four<00:13:33.870> thousand 00:13:35.990 --> 00:13:36.000 align:start position:0% will lead to sixty four thousand 00:13:36.000 --> 00:13:39.350 align:start position:0% will lead to sixty four thousand individual<00:13:37.000> signature<00:13:37.839> on<00:13:38.170> the<00:13:38.830> big<00:13:39.010> tension 00:13:39.350 --> 00:13:39.360 align:start position:0% individual signature on the big tension 00:13:39.360 --> 00:13:43.020 align:start position:0% individual signature on the big tension but<00:13:40.360> the<00:13:40.510> news<00:13:40.720> is<00:13:40.990> that<00:13:41.260> list<00:13:42.030> individual 00:13:43.020 --> 00:13:43.030 align:start position:0% but the news is that list individual 00:13:43.030 --> 00:13:45.540 align:start position:0% but the news is that list individual signature<00:13:43.540> can<00:13:43.839> be<00:13:43.870> aggregate<00:13:44.530> into<00:13:45.040> the 00:13:45.540 --> 00:13:45.550 align:start position:0% signature can be aggregate into the 00:13:45.550 --> 00:13:52.910 align:start position:0% signature can be aggregate into the smaller<00:13:46.500> message<00:13:50.430> in<00:13:51.480> in<00:13:52.480> the<00:13:52.600> shining 00:13:52.910 --> 00:13:52.920 align:start position:0% smaller message in in the shining 00:13:52.920 --> 00:13:57.930 align:start position:0% smaller message in in the shining Network<00:13:53.920> side<00:13:54.270> we<00:13:55.270> have<00:13:55.450> 64<00:13:56.290> kilobytes<00:13:56.940> block 00:13:57.930 --> 00:13:57.940 align:start position:0% Network side we have 64 kilobytes block 00:13:57.940 --> 00:14:02.490 align:start position:0% Network side we have 64 kilobytes block data<00:13:58.450> cap<00:13:58.960> capacity<00:13:59.440> and<00:14:00.750> three<00:14:01.750> seconds<00:14:02.200> shot 00:14:02.490 --> 00:14:02.500 align:start position:0% data cap capacity and three seconds shot 00:14:02.500 --> 00:14:05.150 align:start position:0% data cap capacity and three seconds shot blocked<00:14:02.770> start<00:14:03.400> time<00:14:03.670> and<00:14:03.970> it<00:14:04.750> were 00:14:05.150 --> 00:14:05.160 align:start position:0% blocked start time and it were 00:14:05.160 --> 00:14:08.640 align:start position:0% blocked start time and it were internally<00:14:06.160> to<00:14:06.490> about<00:14:07.120> like<00:14:07.480> 21<00:14:07.930> kilobytes 00:14:08.640 --> 00:14:08.650 align:start position:0% internally to about like 21 kilobytes 00:14:08.650 --> 00:14:15.449 align:start position:0% internally to about like 21 kilobytes per<00:14:09.120> seconds<00:14:10.440> in<00:14:11.440> per<00:14:11.950> shot<00:14:14.070> so<00:14:15.070> that's<00:14:15.280> the 00:14:15.449 --> 00:14:15.459 align:start position:0% per seconds in per shot so that's the 00:14:15.459 --> 00:14:19.560 align:start position:0% per seconds in per shot so that's the overhead<00:14:16.000> here<00:14:16.830> and<00:14:17.940> about<00:14:18.940> the<00:14:19.089> networking 00:14:19.560 --> 00:14:19.570 align:start position:0% overhead here and about the networking 00:14:19.570 --> 00:14:24.480 align:start position:0% overhead here and about the networking layers<00:14:20.350> well<00:14:21.339> it's<00:14:21.550> -<00:14:21.760> oh<00:14:22.209> I<00:14:22.630> used<00:14:23.230> the<00:14:23.980> p2p<00:14:24.310> a 00:14:24.480 --> 00:14:24.490 align:start position:0% layers well it's - oh I used the p2p a 00:14:24.490 --> 00:14:28.350 align:start position:0% layers well it's - oh I used the p2p a stone-faced<00:14:25.470> networking<00:14:26.470> protocol<00:14:26.940> so<00:14:27.940> under 00:14:28.350 --> 00:14:28.360 align:start position:0% stone-faced networking protocol so under 00:14:28.360 --> 00:14:34.199 align:start position:0% stone-faced networking protocol so under the<00:14:29.700> under<00:14:30.700> the<00:14:31.980> networking<00:14:32.980> there<00:14:33.160> it's<00:14:33.910> the 00:14:34.199 --> 00:14:34.209 align:start position:0% the under the networking there it's the 00:14:34.209 --> 00:14:38.670 align:start position:0% the under the networking there it's the pure<00:14:34.740> connection<00:14:36.150> so<00:14:37.150> the<00:14:37.390> Pieta<00:14:37.720> nation<00:14:38.080> it 00:14:38.670 --> 00:14:38.680 align:start position:0% pure connection so the Pieta nation it 00:14:38.680 --> 00:14:39.960 align:start position:0% pure connection so the Pieta nation it depends<00:14:39.220> on<00:14:39.310> the<00:14:39.580> pier 00:14:39.960 --> 00:14:39.970 align:start position:0% depends on the pier 00:14:39.970 --> 00:14:41.659 align:start position:0% depends on the pier discovery<00:14:40.449> protocol<00:14:40.869> which<00:14:41.079> you<00:14:41.259> are<00:14:41.379> using 00:14:41.659 --> 00:14:41.669 align:start position:0% discovery protocol which you are using 00:14:41.669 --> 00:14:49.649 align:start position:0% discovery protocol which you are using and<00:14:43.499> the<00:14:44.499> true<00:14:45.309> business<00:14:45.899> logic<00:14:46.899> is<00:14:47.349> it<00:14:47.829> is<00:14:48.659> the 00:14:49.649 --> 00:14:49.659 align:start position:0% and the true business logic is it is the 00:14:49.659 --> 00:14:53.249 align:start position:0% and the true business logic is it is the message<00:14:50.019> is<00:14:50.499> forecasting<00:14:51.489> with<00:14:52.029> the<00:14:52.299> sub<00:14:52.689> the 00:14:53.249 --> 00:14:53.259 align:start position:0% message is forecasting with the sub the 00:14:53.259 --> 00:14:58.619 align:start position:0% message is forecasting with the sub the publish<00:14:53.799> and<00:14:54.159> sub<00:14:54.809> subscribe<00:14:55.809> system<00:14:57.029> so<00:14:58.029> we 00:14:58.619 --> 00:14:58.629 align:start position:0% publish and sub subscribe system so we 00:14:58.629 --> 00:15:01.710 align:start position:0% publish and sub subscribe system so we use<00:14:58.779> the<00:14:59.019> gossip<00:14:59.379> star<00:14:59.619> protocol<00:15:00.099> to<00:15:00.720> support 00:15:01.710 --> 00:15:01.720 align:start position:0% use the gossip star protocol to support 00:15:01.720 --> 00:15:04.889 align:start position:0% use the gossip star protocol to support has<00:15:01.929> the<00:15:02.399> sub<00:15:03.399> Nate<00:15:03.609> messages<00:15:04.419> inside 00:15:04.889 --> 00:15:04.899 align:start position:0% has the sub Nate messages inside 00:15:04.899 --> 00:15:10.229 align:start position:0% has the sub Nate messages inside xiaochun's<00:15:07.379> so<00:15:08.379> yeah<00:15:08.679> but<00:15:09.009> imaging<00:15:09.699> that<00:15:09.879> if 00:15:10.229 --> 00:15:10.239 align:start position:0% xiaochun's so yeah but imaging that if 00:15:10.239 --> 00:15:13.879 align:start position:0% xiaochun's so yeah but imaging that if we<00:15:10.449> have<00:15:10.629> like<00:15:11.459> 1000<00:15:12.459> sorry 00:15:13.879 --> 00:15:13.889 align:start position:0% we have like 1000 sorry 00:15:13.889 --> 00:15:19.499 align:start position:0% we have like 1000 sorry tens<00:15:16.079> 1064<00:15:17.249> chakras<00:15:18.249> and<00:15:18.519> about<00:15:18.909> 4<00:15:19.239> million 00:15:19.499 --> 00:15:19.509 align:start position:0% tens 1064 chakras and about 4 million 00:15:19.509 --> 00:15:24.389 align:start position:0% tens 1064 chakras and about 4 million spectators<00:15:19.959> it<00:15:20.739> won't<00:15:20.949> be<00:15:21.129> very<00:15:21.339> large<00:15:23.399> and 00:15:24.389 --> 00:15:24.399 align:start position:0% spectators it won't be very large and 00:15:24.399 --> 00:15:26.849 align:start position:0% spectators it won't be very large and also<00:15:24.759> we<00:15:25.449> have<00:15:25.749> to<00:15:25.959> think<00:15:25.989> about<00:15:26.289> the 00:15:26.849 --> 00:15:26.859 align:start position:0% also we have to think about the 00:15:26.859 --> 00:15:30.569 align:start position:0% also we have to think about the peer-to-peer<00:15:27.479> network<00:15:28.479> topologies<00:15:29.349> so<00:15:30.309> there 00:15:30.569 --> 00:15:30.579 align:start position:0% peer-to-peer network topologies so there 00:15:30.579 --> 00:15:33.389 align:start position:0% peer-to-peer network topologies so there are<00:15:30.759> three<00:15:30.970> possible<00:15:31.509> cases<00:15:32.109> which<00:15:32.949> is<00:15:33.099> the 00:15:33.389 --> 00:15:33.399 align:start position:0% are three possible cases which is the 00:15:33.399 --> 00:15:36.899 align:start position:0% are three possible cases which is the structured<00:15:35.039> apologist<00:15:36.039> and<00:15:36.189> also<00:15:36.759> the 00:15:36.899 --> 00:15:36.909 align:start position:0% structured apologist and also the 00:15:36.909 --> 00:15:40.829 align:start position:0% structured apologist and also the unstructured<00:15:37.589> apologist<00:15:38.589> and<00:15:38.789> that<00:15:39.839> includes 00:15:40.829 --> 00:15:40.839 align:start position:0% unstructured apologist and that includes 00:15:40.839 --> 00:15:45.029 align:start position:0% unstructured apologist and that includes flooding<00:15:41.709> gossip<00:15:43.169> epidemic<00:15:44.169> and<00:15:44.409> random<00:15:44.829> work 00:15:45.029 --> 00:15:45.039 align:start position:0% flooding gossip epidemic and random work 00:15:45.039 --> 00:15:47.939 align:start position:0% flooding gossip epidemic and random work so<00:15:45.669> the<00:15:45.849> gossip<00:15:46.269> is<00:15:46.899> included<00:15:47.529> in<00:15:47.739> this 00:15:47.939 --> 00:15:47.949 align:start position:0% so the gossip is included in this 00:15:47.949 --> 00:15:51.029 align:start position:0% so the gossip is included in this category<00:15:48.299> and<00:15:49.299> also<00:15:49.779> it's<00:15:50.109> possible<00:15:50.259> to<00:15:50.709> help 00:15:51.029 --> 00:15:51.039 align:start position:0% category and also it's possible to help 00:15:51.039 --> 00:15:54.499 align:start position:0% category and also it's possible to help to<00:15:51.399> combine<00:15:52.389> a<00:15:52.419> structured<00:15:53.109> and<00:15:53.379> unstructured 00:15:54.499 --> 00:15:54.509 align:start position:0% to combine a structured and unstructured 00:15:54.509 --> 00:16:00.719 align:start position:0% to combine a structured and unstructured ecology<00:15:55.509> into<00:15:55.929> the<00:15:56.109> hybrid<00:15:56.559> model<00:15:59.039> so<00:16:00.039> this<00:16:00.549> is 00:16:00.719 --> 00:16:00.729 align:start position:0% ecology into the hybrid model so this is 00:16:00.729 --> 00:16:03.629 align:start position:0% ecology into the hybrid model so this is an<00:16:00.939> example<00:16:01.419> of<00:16:01.629> how<00:16:02.470> can<00:16:02.709> we<00:16:02.889> implement<00:16:03.309> it 00:16:03.629 --> 00:16:03.639 align:start position:0% an example of how can we implement it 00:16:03.639 --> 00:16:10.529 align:start position:0% an example of how can we implement it simply<00:16:04.389> so<00:16:06.539> in<00:16:07.539> this<00:16:07.720> simple<00:16:08.589> model<00:16:09.239> the<00:16:10.239> very 00:16:10.529 --> 00:16:10.539 align:start position:0% simply so in this simple model the very 00:16:10.539 --> 00:16:15.149 align:start position:0% simply so in this simple model the very latest<00:16:10.689> are<00:16:12.179> they<00:16:13.179> can<00:16:13.499> work<00:16:14.499> as<00:16:14.679> a<00:16:14.709> message 00:16:15.149 --> 00:16:15.159 align:start position:0% latest are they can work as a message 00:16:15.159 --> 00:16:18.059 align:start position:0% latest are they can work as a message inside<00:16:15.399> a<00:16:15.639> shy<00:16:15.879> by<00:16:16.209> using<00:16:16.479> the<00:16:16.929> castle<00:16:17.409> sub<00:16:17.619> for 00:16:18.059 --> 00:16:18.069 align:start position:0% inside a shy by using the castle sub for 00:16:18.069 --> 00:16:21.539 align:start position:0% inside a shy by using the castle sub for a<00:16:18.099> comb<00:16:18.309> and<00:16:18.629> only<00:16:19.629> the<00:16:19.899> proposal<00:16:20.799> of<00:16:20.949> the<00:16:21.069> even 00:16:21.539 --> 00:16:21.549 align:start position:0% a comb and only the proposal of the even 00:16:21.549 --> 00:16:26.539 align:start position:0% a comb and only the proposal of the even slot<00:16:22.079> of<00:16:23.079> the<00:16:23.349> given<00:16:24.089> shot<00:16:25.089> well<00:16:25.479> they<00:16:25.959> only 00:16:26.539 --> 00:16:26.549 align:start position:0% slot of the given shot well they only 00:16:26.549 --> 00:16:30.149 align:start position:0% slot of the given shot well they only had<00:16:27.549> the<00:16:27.579> only<00:16:27.849> one<00:16:28.029> who<00:16:28.299> had<00:16:28.599> to<00:16:28.869> collect<00:16:29.859> all 00:16:30.149 --> 00:16:30.159 align:start position:0% had the only one who had to collect all 00:16:30.159 --> 00:16:33.179 align:start position:0% had the only one who had to collect all those<00:16:30.339> signatures<00:16:30.759> for<00:16:31.329> the<00:16:31.479> given<00:16:31.779> start<00:16:32.199> so 00:16:33.179 --> 00:16:33.189 align:start position:0% those signatures for the given start so 00:16:33.189 --> 00:16:39.149 align:start position:0% those signatures for the given start so for<00:16:33.549> the<00:16:33.699> given<00:16:34.059> shot<00:16:34.569> so<00:16:35.529> the<00:16:37.619> overhead<00:16:38.619> only 00:16:39.149 --> 00:16:39.159 align:start position:0% for the given shot so the overhead only 00:16:39.159 --> 00:16:44.659 align:start position:0% for the given shot so the overhead only inside<00:16:40.259> Sundays<00:16:41.259> and<00:16:42.479> only<00:16:43.479> the<00:16:43.539> where<00:16:44.379> data 00:16:44.659 --> 00:16:44.669 align:start position:0% inside Sundays and only the where data 00:16:44.669 --> 00:16:47.699 align:start position:0% inside Sundays and only the where data only<00:16:45.669> the<00:16:45.879> proposals<00:16:46.419> have<00:16:46.659> to<00:16:46.899> exchange<00:16:47.169> the 00:16:47.699 --> 00:16:47.709 align:start position:0% only the proposals have to exchange the 00:16:47.709 --> 00:16:51.449 align:start position:0% only the proposals have to exchange the aggregated<00:16:48.539> signatures<00:16:49.539> when<00:16:50.470> a<00:16:50.739> single<00:16:51.339> one 00:16:51.449 --> 00:16:51.459 align:start position:0% aggregated signatures when a single one 00:16:51.459 --> 00:16:52.890 align:start position:0% aggregated signatures when a single one has<00:16:51.699> to 00:16:52.890 --> 00:16:52.900 align:start position:0% has to 00:16:52.900 --> 00:16:55.440 align:start position:0% has to councillor<00:16:53.440> issues<00:16:53.800> in<00:16:54.220> losing<00:16:54.640> the<00:16:54.820> data 00:16:55.440 --> 00:16:55.450 align:start position:0% councillor issues in losing the data 00:16:55.450 --> 00:16:58.890 align:start position:0% councillor issues in losing the data privacy<00:16:55.990> and<00:16:56.640> other<00:16:57.640> nodes<00:16:58.029> can<00:16:58.360> need<00:16:58.660> to 00:16:58.890 --> 00:16:58.900 align:start position:0% privacy and other nodes can need to 00:16:58.900 --> 00:17:03.120 align:start position:0% privacy and other nodes can need to trust<00:16:59.410> the<00:17:00.070> list<00:17:00.640> proposals<00:17:01.360> and<00:17:01.770> if<00:17:02.770> the 00:17:03.120 --> 00:17:03.130 align:start position:0% trust the list proposals and if the 00:17:03.130 --> 00:17:06.449 align:start position:0% trust the list proposals and if the promoter<00:17:03.640> doesn't<00:17:04.120> do<00:17:04.660> their<00:17:04.870> work<00:17:05.800> well<00:17:06.040> then 00:17:06.449 --> 00:17:06.459 align:start position:0% promoter doesn't do their work well then 00:17:06.459 --> 00:17:09.120 align:start position:0% promoter doesn't do their work well then the<00:17:06.939> other<00:17:07.030> the<00:17:07.390> rest<00:17:07.569> of<00:17:07.780> the<00:17:08.020> radiators<00:17:08.920> will 00:17:09.120 --> 00:17:09.130 align:start position:0% the other the rest of the radiators will 00:17:09.130 --> 00:17:15.590 align:start position:0% the other the rest of the radiators will lose<00:17:09.370> the<00:17:10.230> reward<00:17:11.230> from<00:17:11.470> it<00:17:11.640> so<00:17:12.640> it's<00:17:12.880> too<00:17:13.270> easy 00:17:15.590 --> 00:17:15.600 align:start position:0% lose the reward from it so it's too easy 00:17:15.600 --> 00:17:19.679 align:start position:0% lose the reward from it so it's too easy another<00:17:16.600> one<00:17:16.750> is<00:17:17.130> implemented<00:17:18.130> by<00:17:18.689> consensus 00:17:19.679 --> 00:17:19.689 align:start position:0% another one is implemented by consensus 00:17:19.689 --> 00:17:21.090 align:start position:0% another one is implemented by consensus research<00:17:20.530> team 00:17:21.090 --> 00:17:21.100 align:start position:0% research team 00:17:21.100 --> 00:17:24.660 align:start position:0% research team it's<00:17:22.030> called<00:17:22.329> handle<00:17:23.010> handle<00:17:24.010> allows<00:17:24.309> the 00:17:24.660 --> 00:17:24.670 align:start position:0% it's called handle handle allows the 00:17:24.670 --> 00:17:28.220 align:start position:0% it's called handle handle allows the aggregation<00:17:25.480> of<00:17:26.429> thousands<00:17:27.429> of<00:17:27.579> signatures 00:17:28.220 --> 00:17:28.230 align:start position:0% aggregation of thousands of signatures 00:17:28.230 --> 00:17:33.480 align:start position:0% aggregation of thousands of signatures just<00:17:29.230> under<00:17:29.620> a<00:17:29.860> second<00:17:30.309> and<00:17:31.110> organize<00:17:32.110> is<00:17:32.490> it's 00:17:33.480 --> 00:17:33.490 align:start position:0% just under a second and organize is it's 00:17:33.490 --> 00:17:36.240 align:start position:0% just under a second and organize is it's it's<00:17:34.090> done<00:17:34.210> by<00:17:34.510> organizing<00:17:35.320> the<00:17:35.559> connection 00:17:36.240 --> 00:17:36.250 align:start position:0% it's done by organizing the connection 00:17:36.250 --> 00:17:38.940 align:start position:0% it's done by organizing the connection in<00:17:36.429> levels<00:17:36.880> so<00:17:37.570> it's<00:17:37.720> more<00:17:37.900> like<00:17:38.110> a<00:17:38.140> structure 00:17:38.940 --> 00:17:38.950 align:start position:0% in levels so it's more like a structure 00:17:38.950 --> 00:17:42.750 align:start position:0% in levels so it's more like a structure to<00:17:38.980> decide<00:17:39.900> it's<00:17:40.900> doing<00:17:41.320> well<00:17:41.530> but<00:17:41.860> we<00:17:42.670> also 00:17:42.750 --> 00:17:42.760 align:start position:0% to decide it's doing well but we also 00:17:42.760 --> 00:17:44.820 align:start position:0% to decide it's doing well but we also need<00:17:43.330> to<00:17:43.450> think<00:17:43.630> more<00:17:43.870> about<00:17:43.929> how<00:17:44.500> can<00:17:44.800> we 00:17:44.820 --> 00:17:44.830 align:start position:0% need to think more about how can we 00:17:44.830 --> 00:17:47.460 align:start position:0% need to think more about how can we utilize<00:17:45.250> the<00:17:45.700> hybrid<00:17:46.240> model<00:17:46.510> more 00:17:47.460 --> 00:17:47.470 align:start position:0% utilize the hybrid model more 00:17:47.470 --> 00:17:56.130 align:start position:0% utilize the hybrid model more efficiently<00:17:52.830> so<00:17:53.830> it's<00:17:54.550> two<00:17:54.730> is<00:17:55.000> very<00:17:55.270> cool 00:17:56.130 --> 00:17:56.140 align:start position:0% efficiently so it's two is very cool 00:17:56.140 --> 00:18:00.360 align:start position:0% efficiently so it's two is very cool it's<00:17:56.290> a<00:17:56.470> Collette<00:17:56.890> but<00:17:57.550> great<00:17:58.120> work<00:17:58.620> so<00:17:59.620> I 00:18:00.360 --> 00:18:00.370 align:start position:0% it's a Collette but great work so I 00:18:00.370 --> 00:18:02.760 align:start position:0% it's a Collette but great work so I think<00:18:00.880> Justin<00:18:01.660> just<00:18:01.900> mentioned<00:18:02.320> about<00:18:02.559> that 00:18:02.760 --> 00:18:02.770 align:start position:0% think Justin just mentioned about that 00:18:02.770 --> 00:18:06.570 align:start position:0% think Justin just mentioned about that very<00:18:03.400> well<00:18:03.580> and<00:18:04.110> also<00:18:05.110> highlight<00:18:05.559> again<00:18:05.860> so<00:18:06.160> we 00:18:06.570 --> 00:18:06.580 align:start position:0% very well and also highlight again so we 00:18:06.580 --> 00:18:07.770 align:start position:0% very well and also highlight again so we have<00:18:06.610> the<00:18:07.120> EIP 00:18:07.770 --> 00:18:07.780 align:start position:0% have the EIP 00:18:07.780 --> 00:18:11.970 align:start position:0% have the EIP is<00:18:08.200> research<00:18:08.860> and<00:18:09.300> magicians<00:18:10.300> and<00:18:10.660> is<00:18:11.650> to 00:18:11.970 --> 00:18:11.980 align:start position:0% is research and magicians and is to 00:18:11.980 --> 00:18:14.250 align:start position:0% is research and magicians and is to speak<00:18:12.309> this<00:18:12.820> art<00:18:13.150> of<00:18:13.360> silent<00:18:13.750> you<00:18:13.840> can<00:18:14.050> found 00:18:14.250 --> 00:18:14.260 align:start position:0% speak this art of silent you can found 00:18:14.260 --> 00:18:17.100 align:start position:0% speak this art of silent you can found more<00:18:14.530> deeper<00:18:15.179> knowledge<00:18:16.179> about<00:18:16.630> it 00:18:17.100 --> 00:18:17.110 align:start position:0% more deeper knowledge about it 00:18:17.110 --> 00:18:19.919 align:start position:0% more deeper knowledge about it and<00:18:17.350> also<00:18:17.980> there's<00:18:18.400> a<00:18:18.520> bounty<00:18:18.940> initiate<00:18:19.690> by 00:18:19.919 --> 00:18:19.929 align:start position:0% and also there's a bounty initiate by 00:18:19.929 --> 00:18:23.760 align:start position:0% and also there's a bounty initiate by adjusting<00:18:20.650> and<00:18:20.920> you<00:18:21.550> can<00:18:21.730> get<00:18:21.940> five<00:18:22.690> es<00:18:22.929> if<00:18:23.440> you 00:18:23.760 --> 00:18:23.770 align:start position:0% adjusting and you can get five es if you 00:18:23.770 --> 00:18:26.940 align:start position:0% adjusting and you can get five es if you found<00:18:24.280> any<00:18:24.550> but<00:18:24.900> under<00:18:25.900> the<00:18:26.080> current<00:18:26.410> we<00:18:26.770> can 00:18:26.940 --> 00:18:26.950 align:start position:0% found any but under the current we can 00:18:26.950 --> 00:18:30.870 align:start position:0% found any but under the current we can change<00:18:27.190> spec<00:18:28.530> and<00:18:29.530> finally<00:18:30.340> I<00:18:30.400> want<00:18:30.640> to<00:18:30.760> say 00:18:30.870 --> 00:18:30.880 align:start position:0% change spec and finally I want to say 00:18:30.880 --> 00:18:36.540 align:start position:0% change spec and finally I want to say that<00:18:31.830> even<00:18:32.830> with<00:18:33.210> facing<00:18:34.230> how<00:18:35.230> the<00:18:35.550> the 00:18:36.540 --> 00:18:36.550 align:start position:0% that even with facing how the the 00:18:36.550 --> 00:18:38.790 align:start position:0% that even with facing how the the concern<00:18:36.940> protocol<00:18:37.540> is<00:18:37.720> almost<00:18:38.080> done<00:18:38.380> and 00:18:38.790 --> 00:18:38.800 align:start position:0% concern protocol is almost done and 00:18:38.800 --> 00:18:41.190 align:start position:0% concern protocol is almost done and there<00:18:39.010> are<00:18:39.040> some<00:18:39.400> optimizations<00:18:40.270> that<00:18:40.870> kind 00:18:41.190 --> 00:18:41.200 align:start position:0% there are some optimizations that kind 00:18:41.200 --> 00:18:43.970 align:start position:0% there are some optimizations that kind hence<00:18:41.559> are<00:18:41.679> working<00:18:42.070> on<00:18:42.220> and<00:18:43.120> generally<00:18:43.600> an 00:18:43.970 --> 00:18:43.980 align:start position:0% hence are working on and generally an 00:18:43.980 --> 00:18:47.970 align:start position:0% hence are working on and generally an optimist<00:18:44.980> or<00:18:45.720> optimistic<00:18:46.720> of<00:18:47.350> what's 00:18:47.970 --> 00:18:47.980 align:start position:0% optimist or optimistic of what's 00:18:47.980 --> 00:18:50.760 align:start position:0% optimist or optimistic of what's happening<00:18:48.520> and<00:18:48.670> exciting<00:18:49.420> about<00:18:49.540> how<00:18:50.440> can<00:18:50.679> we 00:18:50.760 --> 00:18:50.770 align:start position:0% happening and exciting about how can we 00:18:50.770 --> 00:18:53.460 align:start position:0% happening and exciting about how can we establish<00:18:51.270> this<00:18:52.270> problem<00:18:52.690> in<00:18:52.840> the<00:18:52.960> next<00:18:53.110> few 00:18:53.460 --> 00:18:53.470 align:start position:0% establish this problem in the next few 00:18:53.470 --> 00:18:59.580 align:start position:0% establish this problem in the next few stages<00:18:54.450> and<00:18:55.679> okay<00:18:56.679> so<00:18:56.980> it's<00:18:57.190> I'm<00:18:58.170> co-hosting<00:18:59.170> a 00:18:59.580 --> 00:18:59.590 align:start position:0% stages and okay so it's I'm co-hosting a 00:18:59.590 --> 00:19:02.160 align:start position:0% stages and okay so it's I'm co-hosting a breakout<00:19:00.160> with<00:19:00.580> like<00:19:01.060> tomorrow<00:19:01.420> morning<00:19:01.900> and 00:19:02.160 --> 00:19:02.170 align:start position:0% breakout with like tomorrow morning and 00:19:02.170 --> 00:19:02.670 align:start position:0% breakout with like tomorrow morning and if<00:19:02.350> you 00:19:02.670 --> 00:19:02.680 align:start position:0% if you 00:19:02.680 --> 00:19:06.150 align:start position:0% if you interesting<00:19:03.160> knowing<00:19:03.400> more<00:19:03.730> about<00:19:04.080> how<00:19:05.160> the 00:19:06.150 --> 00:19:06.160 align:start position:0% interesting knowing more about how the 00:19:06.160 --> 00:19:08.220 align:start position:0% interesting knowing more about how the Europe<00:19:06.700> developed<00:19:07.330> her<00:19:07.450> experience<00:19:07.990> looks 00:19:08.220 --> 00:19:08.230 align:start position:0% Europe developed her experience looks 00:19:08.230 --> 00:19:10.680 align:start position:0% Europe developed her experience looks like<00:19:08.470> in<00:19:09.130> the<00:19:09.400> phase<00:19:09.610> one<00:19:09.880> phase<00:19:10.150> two<00:19:10.300> stage 00:19:10.680 --> 00:19:10.690 align:start position:0% like in the phase one phase two stage 00:19:10.690 --> 00:19:13.620 align:start position:0% like in the phase one phase two stage and<00:19:11.020> please<00:19:11.530> come<00:19:12.010> with<00:19:12.130> us<00:19:12.370> and<00:19:12.640> join<00:19:13.360> the 00:19:13.620 --> 00:19:13.630 align:start position:0% and please come with us and join the 00:19:13.630 --> 00:19:17.580 align:start position:0% and please come with us and join the breakout<00:19:14.050> session<00:19:15.150> and<00:19:16.150> if<00:19:16.840> you<00:19:16.990> want<00:19:17.260> to<00:19:17.380> know 00:19:17.580 --> 00:19:17.590 align:start position:0% breakout session and if you want to know 00:19:17.590 --> 00:19:20.970 align:start position:0% breakout session and if you want to know more<00:19:17.830> about<00:19:17.860> these<00:19:18.310> two<00:19:19.110> discussions<00:19:20.110> there's 00:19:20.970 --> 00:19:20.980 align:start position:0% more about these two discussions there's 00:19:20.980 --> 00:19:25.020 align:start position:0% more about these two discussions there's a<00:19:21.070> chance<00:19:21.460> that<00:19:21.580> if<00:19:22.060> you<00:19:22.300> travel<00:19:22.950> next<00:19:24.030> after 00:19:25.020 --> 00:19:25.030 align:start position:0% a chance that if you travel next after 00:19:25.030 --> 00:19:26.940 align:start position:0% a chance that if you travel next after the<00:19:25.240> Japan<00:19:25.600> tour<00:19:25.930> and<00:19:26.350> you<00:19:26.620> can<00:19:26.770> come<00:19:26.920> to 00:19:26.940 --> 00:19:26.950 align:start position:0% the Japan tour and you can come to 00:19:26.950 --> 00:19:28.950 align:start position:0% the Japan tour and you can come to Taiwan<00:19:27.460> there's<00:19:27.820> a<00:19:27.970> conference<00:19:28.600> called 00:19:28.950 --> 00:19:28.960 align:start position:0% Taiwan there's a conference called 00:19:28.960 --> 00:19:34.040 align:start position:0% Taiwan there's a conference called crossing<00:19:29.500> and<00:19:30.040> just<00:19:30.340> having<00:19:30.670> crossing<00:19:31.210> Taipei 00:19:34.040 --> 00:19:34.050 align:start position:0% 00:19:34.050 --> 00:19:38.500 align:start position:0% okay<00:19:35.050> that's<00:19:35.260> the<00:19:35.410> side<00:19:35.680> credits<00:19:36.360> thank<00:19:37.360> you 00:19:38.500 --> 00:19:38.510 align:start position:0% okay that's the side credits thank you 00:19:38.510 --> 00:19:48.500 align:start position:0% okay that's the side credits thank you [Applause] 00:19:48.500 --> 00:19:48.510 align:start position:0% 00:19:48.510 --> 00:19:50.570 align:start position:0% you