WEBVTT Kind: captions Language: en 00:00:04.480 --> 00:00:07.870 align:start position:0% hi<00:00:05.480> I'm<00:00:05.689> trippin<00:00:06.380> Ling<00:00:06.590> nekoma<00:00:07.250> also<00:00:07.640> call<00:00:07.790> me 00:00:07.870 --> 00:00:07.880 align:start position:0% hi I'm trippin Ling nekoma also call me 00:00:07.880 --> 00:00:09.490 align:start position:0% hi I'm trippin Ling nekoma also call me Nicholas<00:00:08.210> I'm<00:00:08.420> from<00:00:08.690> a<00:00:08.719> theramin<00:00:08.990> foundation 00:00:09.490 --> 00:00:09.500 align:start position:0% Nicholas I'm from a theramin foundation 00:00:09.500 --> 00:00:11.650 align:start position:0% Nicholas I'm from a theramin foundation today<00:00:10.490> I'll<00:00:10.700> be<00:00:10.730> talking<00:00:10.940> about<00:00:11.240> weak 00:00:11.650 --> 00:00:11.660 align:start position:0% today I'll be talking about weak 00:00:11.660 --> 00:00:13.900 align:start position:0% today I'll be talking about weak subjectivity<00:00:12.260> and<00:00:12.769> how<00:00:13.400> the<00:00:13.460> singing 00:00:13.900 --> 00:00:13.910 align:start position:0% subjectivity and how the singing 00:00:13.910 --> 00:00:19.210 align:start position:0% subjectivity and how the singing protocol<00:00:14.240> works<00:00:14.389> in<00:00:14.839> e2<00:00:17.349> so<00:00:18.349> this<00:00:18.980> talk 00:00:19.210 --> 00:00:19.220 align:start position:0% protocol works in e2 so this talk 00:00:19.220 --> 00:00:20.530 align:start position:0% protocol works in e2 so this talk consists<00:00:19.640> of<00:00:19.700> three<00:00:19.910> parts<00:00:20.119> weak 00:00:20.530 --> 00:00:20.540 align:start position:0% consists of three parts weak 00:00:20.540 --> 00:00:22.690 align:start position:0% consists of three parts weak subjectivity<00:00:21.110> and<00:00:21.590> II<00:00:21.890> through<00:00:22.099> sync<00:00:22.399> and 00:00:22.690 --> 00:00:22.700 align:start position:0% subjectivity and II through sync and 00:00:22.700 --> 00:00:24.249 align:start position:0% subjectivity and II through sync and I'll<00:00:23.060> let<00:00:23.599> um 00:00:24.249 --> 00:00:24.259 align:start position:0% I'll let um 00:00:24.259 --> 00:00:26.139 align:start position:0% I'll let um finally<00:00:24.890> I'll<00:00:25.070> make<00:00:25.250> a<00:00:25.279> brief<00:00:25.550> introduction 00:00:26.139 --> 00:00:26.149 align:start position:0% finally I'll make a brief introduction 00:00:26.149 --> 00:00:28.799 align:start position:0% finally I'll make a brief introduction on<00:00:26.419> the<00:00:26.540> fortress<00:00:26.840> rule<00:00:27.230> used<00:00:27.559> in<00:00:27.890> a<00:00:28.070> theory<00:00:28.430> No 00:00:28.799 --> 00:00:28.809 align:start position:0% on the fortress rule used in a theory No 00:00:28.809 --> 00:00:32.260 align:start position:0% on the fortress rule used in a theory No so<00:00:29.809> first<00:00:30.140> I'll<00:00:31.009> talk<00:00:31.700> about<00:00:31.759> what 00:00:32.260 --> 00:00:32.270 align:start position:0% so first I'll talk about what 00:00:32.270 --> 00:00:34.450 align:start position:0% so first I'll talk about what subjectivity<00:00:32.840> means<00:00:33.320> in<00:00:33.590> his<00:00:33.710> context<00:00:34.309> and 00:00:34.450 --> 00:00:34.460 align:start position:0% subjectivity means in his context and 00:00:34.460 --> 00:00:38.950 align:start position:0% subjectivity means in his context and why<00:00:34.760> is<00:00:34.820> it<00:00:35.030> weak<00:00:36.370> so<00:00:37.370> one<00:00:37.940> is<00:00:38.149> objectivity 00:00:38.950 --> 00:00:38.960 align:start position:0% why is it weak so one is objectivity 00:00:38.960 --> 00:00:42.279 align:start position:0% why is it weak so one is objectivity means<00:00:39.440> in<00:00:39.739> his<00:00:39.859> count<00:00:40.129> has<00:00:40.339> so<00:00:40.940> objectivity<00:00:41.390> in 00:00:42.279 --> 00:00:42.289 align:start position:0% means in his count has so objectivity in 00:00:42.289 --> 00:00:44.650 align:start position:0% means in his count has so objectivity in his<00:00:42.410> country<00:00:42.800> could<00:00:43.789> be<00:00:43.910> for<00:00:44.120> example<00:00:44.570> I 00:00:44.650 --> 00:00:44.660 align:start position:0% his country could be for example I 00:00:44.660 --> 00:00:47.079 align:start position:0% his country could be for example I prefer<00:00:44.989> work<00:00:45.170> you<00:00:45.949> know<00:00:46.070> how<00:00:46.249> much<00:00:46.460> work<00:00:46.730> down 00:00:47.079 --> 00:00:47.089 align:start position:0% prefer work you know how much work down 00:00:47.089 --> 00:00:50.529 align:start position:0% prefer work you know how much work down how<00:00:47.420> much<00:00:47.570> electricity<00:00:47.989> spend<00:00:48.859> and<00:00:49.129> so<00:00:49.879> node 00:00:50.529 --> 00:00:50.539 align:start position:0% how much electricity spend and so node 00:00:50.539 --> 00:00:52.689 align:start position:0% how much electricity spend and so node joining<00:00:51.289> the<00:00:51.379> Bitcoin<00:00:51.710> or<00:00:51.739> interior<00:00:52.190> network 00:00:52.689 --> 00:00:52.699 align:start position:0% joining the Bitcoin or interior network 00:00:52.699 --> 00:00:56.439 align:start position:0% joining the Bitcoin or interior network knows<00:00:53.030> that<00:00:53.859> you<00:00:54.859> can<00:00:55.070> in<00:00:55.190> request<00:00:55.640> pro<00:00:56.179> work 00:00:56.439 --> 00:00:56.449 align:start position:0% knows that you can in request pro work 00:00:56.449 --> 00:00:59.649 align:start position:0% knows that you can in request pro work from<00:00:57.050> any<00:00:57.260> peers<00:00:57.649> and<00:00:57.980> then<00:00:58.940> he<00:00:59.179> can<00:00:59.329> use<00:00:59.359> this 00:00:59.649 --> 00:00:59.659 align:start position:0% from any peers and then he can use this 00:00:59.659 --> 00:01:01.869 align:start position:0% from any peers and then he can use this proper<00:01:00.109> world<00:01:00.319> to<00:01:00.409> objectively<00:01:01.159> identify<00:01:01.819> the 00:01:01.869 --> 00:01:01.879 align:start position:0% proper world to objectively identify the 00:01:01.879 --> 00:01:05.590 align:start position:0% proper world to objectively identify the canonical<00:01:02.269> chain<00:01:03.460> but<00:01:04.460> improver<00:01:05.210> say<00:01:05.390> the 00:01:05.590 --> 00:01:05.600 align:start position:0% canonical chain but improver say the 00:01:05.600 --> 00:01:06.700 align:start position:0% canonical chain but improver say the work<00:01:05.810> could<00:01:06.140> be<00:01:06.290> like<00:01:06.500> running 00:01:06.700 --> 00:01:06.710 align:start position:0% work could be like running 00:01:06.710 --> 00:01:08.950 align:start position:0% work could be like running state-transition<00:01:07.360> creating<00:01:08.360> verifying 00:01:08.950 --> 00:01:08.960 align:start position:0% state-transition creating verifying 00:01:08.960 --> 00:01:11.170 align:start position:0% state-transition creating verifying signatures<00:01:09.590> but<00:01:10.280> this<00:01:10.430> work<00:01:10.700> are<00:01:10.910> tiny 00:01:11.170 --> 00:01:11.180 align:start position:0% signatures but this work are tiny 00:01:11.180 --> 00:01:13.540 align:start position:0% signatures but this work are tiny compared<00:01:11.810> to<00:01:11.870> proper<00:01:12.260> work<00:01:12.470> so<00:01:13.130> every 00:01:13.540 --> 00:01:13.550 align:start position:0% compared to proper work so every 00:01:13.550 --> 00:01:15.910 align:start position:0% compared to proper work so every validator<00:01:14.030> can<00:01:14.480> create<00:01:15.080> super<00:01:15.470> long<00:01:15.650> for 00:01:15.910 --> 00:01:15.920 align:start position:0% validator can create super long for 00:01:15.920 --> 00:01:21.130 align:start position:0% validator can create super long for change<00:01:16.540> secretly<00:01:17.540> at<00:01:17.900> any<00:01:18.260> time<00:01:18.880> and<00:01:19.930> so<00:01:20.930> this 00:01:21.130 --> 00:01:21.140 align:start position:0% change secretly at any time and so this 00:01:21.140 --> 00:01:23.830 align:start position:0% change secretly at any time and so this enables<00:01:21.440> the<00:01:22.160> long<00:01:22.850> range<00:01:23.060> attack<00:01:23.450> so 00:01:23.830 --> 00:01:23.840 align:start position:0% enables the long range attack so 00:01:23.840 --> 00:01:25.960 align:start position:0% enables the long range attack so basically<00:01:24.170> in<00:01:24.470> a<00:01:24.860> long<00:01:25.220> range<00:01:25.400> attack<00:01:25.730> for 00:01:25.960 --> 00:01:25.970 align:start position:0% basically in a long range attack for 00:01:25.970 --> 00:01:29.770 align:start position:0% basically in a long range attack for example<00:01:26.380> say<00:01:27.380> Eve<00:01:27.590> is<00:01:27.950> an<00:01:28.220> attacker<00:01:28.670> and<00:01:28.940> he 00:01:29.770 --> 00:01:29.780 align:start position:0% example say Eve is an attacker and he 00:01:29.780 --> 00:01:31.990 align:start position:0% example say Eve is an attacker and he first<00:01:30.320> request<00:01:30.800> we<00:01:31.040> throw<00:01:31.280> on<00:01:31.520> the<00:01:31.580> main<00:01:31.730> chain 00:01:31.990 --> 00:01:32.000 align:start position:0% first request we throw on the main chain 00:01:32.000 --> 00:01:34.510 align:start position:0% first request we throw on the main chain and<00:01:32.240> after<00:01:33.080> some<00:01:33.290> time<00:01:33.560> his<00:01:33.830> withdraw<00:01:34.340> is 00:01:34.510 --> 00:01:34.520 align:start position:0% and after some time his withdraw is 00:01:34.520 --> 00:01:38.080 align:start position:0% and after some time his withdraw is successfully<00:01:35.450> processed<00:01:35.870> now<00:01:36.800> he/she<00:01:37.790> has<00:01:37.940> no 00:01:38.080 --> 00:01:38.090 align:start position:0% successfully processed now he/she has no 00:01:38.090 --> 00:01:40.120 align:start position:0% successfully processed now he/she has no stake<00:01:38.360> on<00:01:38.480> the<00:01:38.570> main<00:01:38.690> chain<00:01:38.930> and<00:01:39.170> later<00:01:39.710> Alice 00:01:40.120 --> 00:01:40.130 align:start position:0% stake on the main chain and later Alice 00:01:40.130 --> 00:01:42.630 align:start position:0% stake on the main chain and later Alice goes<00:01:40.340> online<00:01:40.550> and<00:01:41.150> now<00:01:41.360> you<00:01:41.660> can<00:01:42.080> create<00:01:42.290> a 00:01:42.630 --> 00:01:42.640 align:start position:0% goes online and now you can create a 00:01:42.640 --> 00:01:46.510 align:start position:0% goes online and now you can create a fortune<00:01:43.640> and<00:01:44.120> on<00:01:45.110> that<00:01:45.380> change<00:01:45.740> did<00:01:46.400> not 00:01:46.510 --> 00:01:46.520 align:start position:0% fortune and on that change did not 00:01:46.520 --> 00:01:49.120 align:start position:0% fortune and on that change did not withdraw<00:01:46.700> withdraw<00:01:47.480> and<00:01:47.990> can<00:01:48.380> he<00:01:48.470> continues 00:01:49.120 --> 00:01:49.130 align:start position:0% withdraw withdraw and can he continues 00:01:49.130 --> 00:01:52.060 align:start position:0% withdraw withdraw and can he continues to<00:01:49.220> vote<00:01:49.490> on<00:01:49.760> the<00:01:50.000> fortune<00:01:50.510> and<00:01:50.930> now<00:01:51.170> you<00:01:51.800> can 00:01:52.060 --> 00:01:52.070 align:start position:0% to vote on the fortune and now you can 00:01:52.070 --> 00:01:55.990 align:start position:0% to vote on the fortune and now you can feed<00:01:52.310> this<00:01:52.430> fortune<00:01:53.120> to<00:01:53.360> Alice<00:01:53.750> and<00:01:55.000> later 00:01:55.990 --> 00:01:56.000 align:start position:0% feed this fortune to Alice and later 00:01:56.000 --> 00:01:59.920 align:start position:0% feed this fortune to Alice and later when<00:01:56.990> Alice<00:01:57.760> find<00:01:58.760> out<00:01:58.910> that<00:01:59.090> Eve<00:01:59.360> has<00:01:59.690> been 00:01:59.920 --> 00:01:59.930 align:start position:0% when Alice find out that Eve has been 00:01:59.930 --> 00:02:01.690 align:start position:0% when Alice find out that Eve has been feeding<00:02:00.170> her<00:02:00.500> with<00:02:00.770> four<00:02:01.220> chains 00:02:01.690 --> 00:02:01.700 align:start position:0% feeding her with four chains 00:02:01.700 --> 00:02:03.970 align:start position:0% feeding her with four chains she<00:02:02.330> would<00:02:02.450> try<00:02:02.570> to<00:02:02.660> use<00:02:03.080> this<00:02:03.350> fortune<00:02:03.770> as 00:02:03.970 --> 00:02:03.980 align:start position:0% she would try to use this fortune as 00:02:03.980 --> 00:02:06.340 align:start position:0% she would try to use this fortune as approved<00:02:04.400> to<00:02:04.670> prove<00:02:04.970> that<00:02:05.510> he<00:02:05.720> was<00:02:05.750> double 00:02:06.340 --> 00:02:06.350 align:start position:0% approved to prove that he was double 00:02:06.350 --> 00:02:10.119 align:start position:0% approved to prove that he was double voting<00:02:06.530> and<00:02:07.780> she<00:02:08.780> will<00:02:08.899> send<00:02:09.080> his<00:02:09.259> evidence 00:02:10.119 --> 00:02:10.129 align:start position:0% voting and she will send his evidence 00:02:10.129 --> 00:02:12.160 align:start position:0% voting and she will send his evidence will<00:02:10.340> mention<00:02:10.519> but<00:02:10.910> then<00:02:11.450> she<00:02:11.750> will<00:02:11.870> find<00:02:12.050> out 00:02:12.160 --> 00:02:12.170 align:start position:0% will mention but then she will find out 00:02:12.170 --> 00:02:14.680 align:start position:0% will mention but then she will find out that<00:02:12.319> if<00:02:12.680> no<00:02:12.920> longer<00:02:13.159> has<00:02:13.310> any<00:02:13.519> steak<00:02:13.760> on<00:02:13.969> the 00:02:14.680 --> 00:02:14.690 align:start position:0% that if no longer has any steak on the 00:02:14.690 --> 00:02:22.390 align:start position:0% that if no longer has any steak on the chain<00:02:16.360> so<00:02:19.360> subjectivity<00:02:20.680> in<00:02:21.680> this<00:02:21.950> count 00:02:22.390 --> 00:02:22.400 align:start position:0% chain so subjectivity in this count 00:02:22.400 --> 00:02:25.270 align:start position:0% chain so subjectivity in this count heads<00:02:22.640> means<00:02:23.480> that<00:02:23.780> you<00:02:24.020> need<00:02:24.200> to<00:02:24.290> trust<00:02:24.650> some 00:02:25.270 --> 00:02:25.280 align:start position:0% heads means that you need to trust some 00:02:25.280 --> 00:02:28.590 align:start position:0% heads means that you need to trust some sources<00:02:25.670> to<00:02:26.540> identify<00:02:26.570> the<00:02:27.050> canonical<00:02:27.380> chain 00:02:28.590 --> 00:02:28.600 align:start position:0% sources to identify the canonical chain 00:02:28.600 --> 00:02:32.590 align:start position:0% sources to identify the canonical chain and<00:02:29.620> why<00:02:30.620> is<00:02:30.680> a<00:02:30.770> week<00:02:31.040> is<00:02:31.700> a<00:02:31.760> way<00:02:31.940> because<00:02:32.330> we 00:02:32.590 --> 00:02:32.600 align:start position:0% and why is a week is a way because we 00:02:32.600 --> 00:02:35.050 align:start position:0% and why is a week is a way because we only<00:02:32.720> need<00:02:32.930> to<00:02:33.020> trust<00:02:33.350> when<00:02:33.830> first<00:02:34.610> you<00:02:34.850> join 00:02:35.050 --> 00:02:35.060 align:start position:0% only need to trust when first you join 00:02:35.060 --> 00:02:37.390 align:start position:0% only need to trust when first you join join<00:02:35.540> the<00:02:35.660> network<00:02:35.810> for<00:02:36.110> the<00:02:36.170> first<00:02:36.200> time<00:02:36.590> or<00:02:37.340> a 00:02:37.390 --> 00:02:37.400 align:start position:0% join the network for the first time or a 00:02:37.400 --> 00:02:39.760 align:start position:0% join the network for the first time or a second<00:02:37.970> you<00:02:38.270> were<00:02:38.390> offline<00:02:38.780> for<00:02:39.200> a<00:02:39.230> long<00:02:39.530> time 00:02:39.760 --> 00:02:39.770 align:start position:0% second you were offline for a long time 00:02:39.770 --> 00:02:42.160 align:start position:0% second you were offline for a long time for<00:02:40.520> how<00:02:40.670> long<00:02:40.910> it<00:02:41.120> depends<00:02:41.630> on<00:02:41.720> Halloween 00:02:42.160 --> 00:02:42.170 align:start position:0% for how long it depends on Halloween 00:02:42.170 --> 00:02:45.520 align:start position:0% for how long it depends on Halloween texts<00:02:42.620> for<00:02:43.190> the<00:02:43.970> attacker<00:02:44.510> to<00:02:44.690> withdraw<00:02:45.350> their 00:02:45.520 --> 00:02:45.530 align:start position:0% texts for the attacker to withdraw their 00:02:45.530 --> 00:02:48.100 align:start position:0% texts for the attacker to withdraw their stake<00:02:45.770> and<00:02:46.300> this<00:02:47.300> is<00:02:47.510> called<00:02:47.810> a<00:02:47.930> weak 00:02:48.100 --> 00:02:48.110 align:start position:0% stake and this is called a weak 00:02:48.110 --> 00:02:51.070 align:start position:0% stake and this is called a weak subjectivity<00:02:48.770> period<00:02:49.430> and<00:02:49.700> we<00:02:50.480> subjectivity 00:02:51.070 --> 00:02:51.080 align:start position:0% subjectivity period and we subjectivity 00:02:51.080 --> 00:02:51.730 align:start position:0% subjectivity period and we subjectivity Pierrot 00:02:51.730 --> 00:02:51.740 align:start position:0% Pierrot 00:02:51.740 --> 00:02:54.280 align:start position:0% Pierrot is<00:02:51.950> going<00:02:52.580> to<00:02:52.760> determine<00:02:53.120> if<00:02:53.900> we're<00:02:54.110> gonna 00:02:54.280 --> 00:02:54.290 align:start position:0% is going to determine if we're gonna 00:02:54.290 --> 00:02:57.940 align:start position:0% is going to determine if we're gonna need<00:02:54.410> trust<00:02:54.740> when<00:02:55.130> we<00:02:55.250> are<00:02:55.400> thinking<00:02:56.470> so<00:02:57.470> next 00:02:57.940 --> 00:02:57.950 align:start position:0% need trust when we are thinking so next 00:02:57.950 --> 00:03:00.040 align:start position:0% need trust when we are thinking so next I<00:02:58.250> will<00:02:58.610> talk<00:02:58.790> about<00:02:58.940> how<00:02:59.300> the<00:02:59.360> sinking 00:03:00.040 --> 00:03:00.050 align:start position:0% I will talk about how the sinking 00:03:00.050 --> 00:03:04.660 align:start position:0% I will talk about how the sinking protocol<00:03:00.440> works<00:03:00.590> in<00:03:00.890> e2<00:03:02.530> I<00:03:03.530> will<00:03:04.040> walk<00:03:04.280> through 00:03:04.660 --> 00:03:04.670 align:start position:0% protocol works in e2 I will walk through 00:03:04.670 --> 00:03:07.510 align:start position:0% protocol works in e2 I will walk through a<00:03:04.840> hall<00:03:05.840> decline<00:03:06.290> sink<00:03:06.620> in<00:03:06.860> three<00:03:07.340> different 00:03:07.510 --> 00:03:07.520 align:start position:0% a hall decline sink in three different 00:03:07.520 --> 00:03:09.640 align:start position:0% a hall decline sink in three different situations<00:03:08.240> and<00:03:08.480> the<00:03:08.780> first<00:03:09.020> is<00:03:09.380> how<00:03:09.590> the 00:03:09.640 --> 00:03:09.650 align:start position:0% situations and the first is how the 00:03:09.650 --> 00:03:11.680 align:start position:0% situations and the first is how the cleansing<00:03:09.920> when<00:03:10.370> you<00:03:10.520> brewster<00:03:10.970> you<00:03:11.300> know<00:03:11.540> the 00:03:11.680 --> 00:03:11.690 align:start position:0% cleansing when you brewster you know the 00:03:11.690 --> 00:03:14.590 align:start position:0% cleansing when you brewster you know the first<00:03:11.870> time<00:03:12.050> and<00:03:12.380> the<00:03:13.310> second<00:03:13.670> one<00:03:13.850> is<00:03:14.120> when 00:03:14.590 --> 00:03:14.600 align:start position:0% first time and the second one is when 00:03:14.600 --> 00:03:17.530 align:start position:0% first time and the second one is when you<00:03:14.930> goes<00:03:15.290> offline<00:03:15.680> and<00:03:16.070> login<00:03:16.760> back<00:03:16.940> before 00:03:17.530 --> 00:03:17.540 align:start position:0% you goes offline and login back before 00:03:17.540 --> 00:03:21.250 align:start position:0% you goes offline and login back before the<00:03:17.900> week<00:03:18.080> subjectivity<00:03:18.709> period<00:03:19.400> ends<00:03:20.260> the 00:03:21.250 --> 00:03:21.260 align:start position:0% the week subjectivity period ends the 00:03:21.260 --> 00:03:23.410 align:start position:0% the week subjectivity period ends the third<00:03:21.410> situation<00:03:21.680> is<00:03:22.130> when<00:03:22.430> you<00:03:22.610> stay<00:03:23.000> offline 00:03:23.410 --> 00:03:23.420 align:start position:0% third situation is when you stay offline 00:03:23.420 --> 00:03:24.729 align:start position:0% third situation is when you stay offline for<00:03:23.570> too<00:03:23.720> long<00:03:23.930> for<00:03:24.140> longer<00:03:24.410> than<00:03:24.560> we 00:03:24.729 --> 00:03:24.739 align:start position:0% for too long for longer than we 00:03:24.739 --> 00:03:29.560 align:start position:0% for too long for longer than we subjectivity<00:03:25.310> Peru<00:03:27.790> first<00:03:28.790> how<00:03:29.000> does<00:03:29.239> the 00:03:29.560 --> 00:03:29.570 align:start position:0% subjectivity Peru first how does the 00:03:29.570 --> 00:03:31.210 align:start position:0% subjectivity Peru first how does the client<00:03:29.870> seek<00:03:30.170> when<00:03:30.350> bootstrap<00:03:30.830> you<00:03:30.950> know<00:03:31.100> the 00:03:31.210 --> 00:03:31.220 align:start position:0% client seek when bootstrap you know the 00:03:31.220 --> 00:03:33.370 align:start position:0% client seek when bootstrap you know the first<00:03:31.400> time<00:03:31.610> you<00:03:31.820> neither<00:03:32.120> trust<00:03:32.480> you<00:03:33.200> trust 00:03:33.370 --> 00:03:33.380 align:start position:0% first time you neither trust you trust 00:03:33.380 --> 00:03:35.110 align:start position:0% first time you neither trust you trust the<00:03:33.620> bootstrap<00:03:34.010> knows<00:03:34.190> you<00:03:34.580> trust<00:03:34.880> the 00:03:35.110 --> 00:03:35.120 align:start position:0% the bootstrap knows you trust the 00:03:35.120 --> 00:03:38.620 align:start position:0% the bootstrap knows you trust the genesis<00:03:36.080> blocks<00:03:36.380> Genesis<00:03:36.890> state<00:03:37.160> or<00:03:37.580> if<00:03:38.300> the 00:03:38.620 --> 00:03:38.630 align:start position:0% genesis blocks Genesis state or if the 00:03:38.630 --> 00:03:40.750 align:start position:0% genesis blocks Genesis state or if the genesis<00:03:39.170> is<00:03:39.470> already<00:03:39.980> white<00:03:40.160> been<00:03:40.370> in<00:03:40.640> the 00:03:40.750 --> 00:03:40.760 align:start position:0% genesis is already white been in the 00:03:40.760 --> 00:03:43.210 align:start position:0% genesis is already white been in the past<00:03:40.970> you<00:03:41.540> will<00:03:41.690> trust<00:03:41.870> a<00:03:42.200> lattice<00:03:43.190> point 00:03:43.210 --> 00:03:43.220 align:start position:0% past you will trust a lattice point 00:03:43.220 --> 00:03:48.160 align:start position:0% past you will trust a lattice point ladies<00:03:43.910> try<00:03:44.330> point<00:03:44.570> instead<00:03:46.030> so<00:03:47.030> say<00:03:47.660> if<00:03:47.780> now 00:03:48.160 --> 00:03:48.170 align:start position:0% ladies try point instead so say if now 00:03:48.170 --> 00:03:50.290 align:start position:0% ladies try point instead so say if now you<00:03:48.200> have<00:03:48.470> a<00:03:48.500> trusted<00:03:49.040> Genesis<00:03:49.610> or<00:03:49.820> let<00:03:50.000> it<00:03:50.120> try 00:03:50.290 --> 00:03:50.300 align:start position:0% you have a trusted Genesis or let it try 00:03:50.300 --> 00:03:53.229 align:start position:0% you have a trusted Genesis or let it try point<00:03:50.650> you<00:03:51.650> will<00:03:51.830> connect<00:03:52.280> to<00:03:52.400> peers<00:03:52.730> and<00:03:53.000> you 00:03:53.229 --> 00:03:53.239 align:start position:0% point you will connect to peers and you 00:03:53.239 --> 00:03:55.420 align:start position:0% point you will connect to peers and you will<00:03:53.390> first<00:03:53.660> exchange<00:03:54.290> that<00:03:54.800> is<00:03:54.950> try<00:03:55.160> point 00:03:55.420 --> 00:03:55.430 align:start position:0% will first exchange that is try point 00:03:55.430 --> 00:03:58.270 align:start position:0% will first exchange that is try point and<00:03:55.640> head<00:03:55.850> blocks<00:03:56.120> and<00:03:56.450> some<00:03:56.989> other<00:03:57.170> infos<00:03:57.530> to 00:03:58.270 --> 00:03:58.280 align:start position:0% and head blocks and some other infos to 00:03:58.280 --> 00:04:00.759 align:start position:0% and head blocks and some other infos to decide<00:03:58.670> if<00:03:58.970> you<00:03:59.480> are<00:03:59.750> you<00:04:00.170> two<00:04:00.380> are<00:04:00.560> on<00:04:00.739> the 00:04:00.759 --> 00:04:00.769 align:start position:0% decide if you are you two are on the 00:04:00.769 --> 00:04:03.040 align:start position:0% decide if you are you two are on the same<00:04:00.890> channel<00:04:01.370> and<00:04:01.519> if<00:04:01.910> you<00:04:02.120> are<00:04:02.300> then<00:04:02.780> you 00:04:03.040 --> 00:04:03.050 align:start position:0% same channel and if you are then you 00:04:03.050 --> 00:04:05.770 align:start position:0% same channel and if you are then you will<00:04:03.080> start<00:04:03.380> requests<00:04:03.830> amazing<00:04:04.190> blocks<00:04:04.400> or<00:04:04.780> if 00:04:05.770 --> 00:04:05.780 align:start position:0% will start requests amazing blocks or if 00:04:05.780 --> 00:04:07.270 align:start position:0% will start requests amazing blocks or if you<00:04:05.959> are<00:04:06.110> not<00:04:06.290> on<00:04:06.440> the<00:04:06.530> same<00:04:06.680> channel<00:04:07.070> you<00:04:07.160> will 00:04:07.270 --> 00:04:07.280 align:start position:0% you are not on the same channel you will 00:04:07.280 --> 00:04:11.040 align:start position:0% you are not on the same channel you will simply<00:04:07.400> disconnect<00:04:09.100> so<00:04:10.100> second<00:04:10.850> situation 00:04:11.040 --> 00:04:11.050 align:start position:0% simply disconnect so second situation 00:04:11.050 --> 00:04:13.720 align:start position:0% simply disconnect so second situation how<00:04:12.050> this<00:04:12.260> clients<00:04:12.709> thing<00:04:12.860> when<00:04:13.130> you<00:04:13.489> go 00:04:13.720 --> 00:04:13.730 align:start position:0% how this clients thing when you go 00:04:13.730 --> 00:04:17.080 align:start position:0% how this clients thing when you go offline<00:04:14.150> but<00:04:14.600> a<00:04:14.810> login<00:04:15.170> back<00:04:15.320> in<00:04:15.500> time<00:04:16.090> first 00:04:17.080 --> 00:04:17.090 align:start position:0% offline but a login back in time first 00:04:17.090 --> 00:04:18.699 align:start position:0% offline but a login back in time first you<00:04:17.239> still<00:04:17.450> in<00:04:17.600> the<00:04:17.660> trust<00:04:17.900> you<00:04:18.049> trust<00:04:18.230> you 00:04:18.699 --> 00:04:18.709 align:start position:0% you still in the trust you trust you 00:04:18.709 --> 00:04:21.670 align:start position:0% you still in the trust you trust you trust<00:04:18.890> a<00:04:19.100> push<00:04:19.250> read<00:04:19.430> notes<00:04:20.180> or<00:04:20.419> maybe<00:04:21.410> you<00:04:21.530> can 00:04:21.670 --> 00:04:21.680 align:start position:0% trust a push read notes or maybe you can 00:04:21.680 --> 00:04:23.560 align:start position:0% trust a push read notes or maybe you can use<00:04:21.799> the<00:04:22.010> peer<00:04:22.310> info<00:04:22.610> you<00:04:22.760> persist<00:04:23.210> in<00:04:23.419> the 00:04:23.560 --> 00:04:23.570 align:start position:0% use the peer info you persist in the 00:04:23.570 --> 00:04:26.500 align:start position:0% use the peer info you persist in the database<00:04:23.990> during<00:04:24.830> this<00:04:25.100> connection<00:04:25.669> but<00:04:26.330> now 00:04:26.500 --> 00:04:26.510 align:start position:0% database during this connection but now 00:04:26.510 --> 00:04:28.270 align:start position:0% database during this connection but now you<00:04:26.570> do<00:04:26.960> not<00:04:27.080> need<00:04:27.320> to<00:04:27.440> trust<00:04:27.770> the 00:04:28.270 --> 00:04:28.280 align:start position:0% you do not need to trust the 00:04:28.280 --> 00:04:30.190 align:start position:0% you do not need to trust the try<00:04:28.610> point<00:04:28.880> because<00:04:29.360> you<00:04:29.660> can<00:04:29.810> use<00:04:30.020> the 00:04:30.190 --> 00:04:30.200 align:start position:0% try point because you can use the 00:04:30.200 --> 00:04:32.230 align:start position:0% try point because you can use the checkpoint<00:04:30.740> the<00:04:31.400> last<00:04:31.730> time<00:04:31.910> you're<00:04:32.060> online 00:04:32.230 --> 00:04:32.240 align:start position:0% checkpoint the last time you're online 00:04:32.240 --> 00:04:37.240 align:start position:0% checkpoint the last time you're online and<00:04:32.660> start<00:04:33.350> sinking<00:04:33.710> from<00:04:33.830> there<00:04:35.919> it's<00:04:36.919> mostly 00:04:37.240 --> 00:04:37.250 align:start position:0% and start sinking from there it's mostly 00:04:37.250 --> 00:04:39.520 align:start position:0% and start sinking from there it's mostly same<00:04:37.550> you<00:04:37.760> have<00:04:37.940> the<00:04:38.090> try<00:04:38.330> point<00:04:38.600> and<00:04:38.900> you 00:04:39.520 --> 00:04:39.530 align:start position:0% same you have the try point and you 00:04:39.530 --> 00:04:41.590 align:start position:0% same you have the try point and you connect<00:04:39.980> to<00:04:40.070> peers<00:04:40.400> and<00:04:40.700> you<00:04:41.330> start 00:04:41.590 --> 00:04:41.600 align:start position:0% connect to peers and you start 00:04:41.600 --> 00:04:44.379 align:start position:0% connect to peers and you start exchanging<00:04:42.190> letters<00:04:43.190> try<00:04:43.460> point<00:04:43.700> a<00:04:43.910> blog<00:04:44.180> and 00:04:44.379 --> 00:04:44.389 align:start position:0% exchanging letters try point a blog and 00:04:44.389 --> 00:04:46.240 align:start position:0% exchanging letters try point a blog and some<00:04:44.540> other<00:04:44.750> informations<00:04:45.320> to<00:04:45.560> decide<00:04:46.130> if 00:04:46.240 --> 00:04:46.250 align:start position:0% some other informations to decide if 00:04:46.250 --> 00:04:48.010 align:start position:0% some other informations to decide if we're<00:04:46.370> on<00:04:46.460> the<00:04:46.580> same<00:04:46.730> chain<00:04:46.970> and<00:04:47.210> you<00:04:47.360> are<00:04:47.660> you 00:04:48.010 --> 00:04:48.020 align:start position:0% we're on the same chain and you are you 00:04:48.020 --> 00:04:50.470 align:start position:0% we're on the same chain and you are you request<00:04:48.380> missing<00:04:48.680> blocks<00:04:49.000> but<00:04:50.000> now<00:04:50.120> that<00:04:50.330> the 00:04:50.470 --> 00:04:50.480 align:start position:0% request missing blocks but now that the 00:04:50.480 --> 00:04:52.120 align:start position:0% request missing blocks but now that the client<00:04:50.780> will<00:04:50.840> only<00:04:50.960> support<00:04:51.380> requesting 00:04:52.120 --> 00:04:52.130 align:start position:0% client will only support requesting 00:04:52.130 --> 00:04:53.830 align:start position:0% client will only support requesting blocks<00:04:52.520> since<00:04:52.850> the<00:04:53.060> start<00:04:53.389> of<00:04:53.540> the<00:04:53.720> way 00:04:53.830 --> 00:04:53.840 align:start position:0% blocks since the start of the way 00:04:53.840 --> 00:04:56.800 align:start position:0% blocks since the start of the way subjectivity<00:04:54.530> P<00:04:54.919> Rio<00:04:55.120> which<00:04:56.120> means<00:04:56.330> that<00:04:56.600> you 00:04:56.800 --> 00:04:56.810 align:start position:0% subjectivity P Rio which means that you 00:04:56.810 --> 00:04:58.510 align:start position:0% subjectivity P Rio which means that you won't<00:04:57.020> be<00:04:57.169> able<00:04:57.290> to<00:04:57.440> sing<00:04:57.710> the<00:04:57.889> blocks<00:04:58.160> that's 00:04:58.510 --> 00:04:58.520 align:start position:0% won't be able to sing the blocks that's 00:04:58.520 --> 00:05:01.180 align:start position:0% won't be able to sing the blocks that's older<00:04:59.120> than<00:04:59.419> the<00:04:59.930> start<00:05:00.230> of<00:05:00.410> the<00:05:00.530> weeks<00:05:00.710> of<00:05:00.890> GDP 00:05:01.180 --> 00:05:01.190 align:start position:0% older than the start of the weeks of GDP 00:05:01.190 --> 00:05:05.650 align:start position:0% older than the start of the weeks of GDP subjectivity<00:05:02.030> Peru<00:05:03.730> okay<00:05:04.730> and<00:05:05.240> you've<00:05:05.450> grown 00:05:05.650 --> 00:05:05.660 align:start position:0% subjectivity Peru okay and you've grown 00:05:05.660 --> 00:05:08.440 align:start position:0% subjectivity Peru okay and you've grown understand<00:05:06.260> same<00:05:06.830> chain<00:05:07.100> you<00:05:07.340> will<00:05:07.490> appear 00:05:08.440 --> 00:05:08.450 align:start position:0% understand same chain you will appear 00:05:08.450 --> 00:05:10.000 align:start position:0% understand same chain you will appear when<00:05:08.630> alpha<00:05:08.900> us<00:05:09.080> and<00:05:09.410> then<00:05:09.770> we<00:05:09.919> would 00:05:10.000 --> 00:05:10.010 align:start position:0% when alpha us and then we would 00:05:10.010 --> 00:05:12.820 align:start position:0% when alpha us and then we would disconnect<00:05:11.230> okay 00:05:12.820 --> 00:05:12.830 align:start position:0% disconnect okay 00:05:12.830 --> 00:05:16.390 align:start position:0% disconnect okay there<00:05:13.190> is<00:05:13.280> situation<00:05:14.650> how<00:05:15.650> this<00:05:15.830> client<00:05:16.160> sing 00:05:16.390 --> 00:05:16.400 align:start position:0% there is situation how this client sing 00:05:16.400 --> 00:05:18.670 align:start position:0% there is situation how this client sing when<00:05:16.700> you<00:05:17.390> stay<00:05:17.660> offline<00:05:17.990> for<00:05:18.230> longer<00:05:18.560> than 00:05:18.670 --> 00:05:18.680 align:start position:0% when you stay offline for longer than 00:05:18.680 --> 00:05:21.730 align:start position:0% when you stay offline for longer than wave<00:05:18.919> subjective<00:05:19.550> subjectivity<00:05:20.479> P<00:05:20.870> Rio<00:05:21.050> so 00:05:21.730 --> 00:05:21.740 align:start position:0% wave subjective subjectivity P Rio so 00:05:21.740 --> 00:05:23.700 align:start position:0% wave subjective subjectivity P Rio so it's<00:05:21.919> basically<00:05:22.250> the<00:05:22.460> same<00:05:22.669> as<00:05:22.940> when<00:05:23.360> you<00:05:23.570> were 00:05:23.700 --> 00:05:23.710 align:start position:0% it's basically the same as when you were 00:05:23.710 --> 00:05:26.980 align:start position:0% it's basically the same as when you were as<00:05:24.710> the<00:05:24.950> way<00:05:25.040> you<00:05:25.100> sing<00:05:25.520> when<00:05:25.940> you<00:05:26.389> push<00:05:26.600> run<00:05:26.780> on 00:05:26.980 --> 00:05:26.990 align:start position:0% as the way you sing when you push run on 00:05:26.990 --> 00:05:30.010 align:start position:0% as the way you sing when you push run on the<00:05:27.139> first<00:05:27.290> time<00:05:27.560> you<00:05:28.250> trust<00:05:28.639> Genesis<00:05:29.540> blog<00:05:29.780> or 00:05:30.010 --> 00:05:30.020 align:start position:0% the first time you trust Genesis blog or 00:05:30.020 --> 00:05:33.460 align:start position:0% the first time you trust Genesis blog or trust<00:05:30.710> the<00:05:31.419> lettuce<00:05:32.419> try<00:05:32.630> point<00:05:32.870> and<00:05:33.110> start 00:05:33.460 --> 00:05:33.470 align:start position:0% trust the lettuce try point and start 00:05:33.470 --> 00:05:36.690 align:start position:0% trust the lettuce try point and start singing<00:05:33.650> from<00:05:33.860> there<00:05:34.720> okay<00:05:35.720> once<00:05:35.930> we<00:05:36.290> down 00:05:36.690 --> 00:05:36.700 align:start position:0% singing from there okay once we down 00:05:36.700 --> 00:05:39.520 align:start position:0% singing from there okay once we down once<00:05:37.700> we<00:05:37.850> finish<00:05:38.180> the<00:05:38.419> syncing<00:05:39.050> we<00:05:39.260> will<00:05:39.380> have 00:05:39.520 --> 00:05:39.530 align:start position:0% once we finish the syncing we will have 00:05:39.530 --> 00:05:41.560 align:start position:0% once we finish the syncing we will have a<00:05:39.560> picture<00:05:40.070> of<00:05:40.250> how<00:05:40.520> the<00:05:40.550> chain<00:05:40.970> or<00:05:41.270> how<00:05:41.510> the 00:05:41.560 --> 00:05:41.570 align:start position:0% a picture of how the chain or how the 00:05:41.570 --> 00:05:44.260 align:start position:0% a picture of how the chain or how the blood<00:05:41.840> tree<00:05:42.080> looks<00:05:42.410> like<00:05:42.650> and<00:05:43.060> then<00:05:44.060> we'll 00:05:44.260 --> 00:05:44.270 align:start position:0% blood tree looks like and then we'll 00:05:44.270 --> 00:05:46.900 align:start position:0% blood tree looks like and then we'll apply<00:05:44.510> the<00:05:44.750> forest<00:05:45.380> rule<00:05:45.680> to<00:05:46.100> get<00:05:46.310> a<00:05:46.340> score<00:05:46.669> of 00:05:46.900 --> 00:05:46.910 align:start position:0% apply the forest rule to get a score of 00:05:46.910 --> 00:05:49.600 align:start position:0% apply the forest rule to get a score of each<00:05:47.030> chain<00:05:47.419> and<00:05:47.660> then<00:05:48.590> we<00:05:48.890> can<00:05:49.100> identify<00:05:49.310> the 00:05:49.600 --> 00:05:49.610 align:start position:0% each chain and then we can identify the 00:05:49.610 --> 00:05:52.480 align:start position:0% each chain and then we can identify the canonical<00:05:49.970> chain<00:05:50.500> so<00:05:51.500> before<00:05:51.950> I<00:05:52.010> get<00:05:52.070> to<00:05:52.370> the 00:05:52.480 --> 00:05:52.490 align:start position:0% canonical chain so before I get to the 00:05:52.490 --> 00:05:56.140 align:start position:0% canonical chain so before I get to the forest<00:05:52.880> rule<00:05:53.560> there's<00:05:54.560> two<00:05:55.310> type<00:05:55.520> of<00:05:55.550> two 00:05:56.140 --> 00:05:56.150 align:start position:0% forest rule there's two type of two 00:05:56.150 --> 00:05:59.140 align:start position:0% forest rule there's two type of two types<00:05:56.390> of<00:05:56.539> checkpoints<00:05:57.789> first<00:05:58.789> one<00:05:59.000> is 00:05:59.140 --> 00:05:59.150 align:start position:0% types of checkpoints first one is 00:05:59.150 --> 00:06:00.940 align:start position:0% types of checkpoints first one is finalized<00:05:59.600> tree<00:05:59.810> point<00:06:00.050> the<00:06:00.440> second<00:06:00.710> one<00:06:00.830> is 00:06:00.940 --> 00:06:00.950 align:start position:0% finalized tree point the second one is 00:06:00.950 --> 00:06:03.700 align:start position:0% finalized tree point the second one is justified<00:06:01.430> tree<00:06:01.610> point<00:06:01.880> and<00:06:02.350> we<00:06:03.350> do<00:06:03.500> not 00:06:03.700 --> 00:06:03.710 align:start position:0% justified tree point and we do not 00:06:03.710 --> 00:06:06.250 align:start position:0% justified tree point and we do not override<00:06:04.280> the<00:06:04.610> finalized<00:06:05.330> checkpoint<00:06:05.780> unless 00:06:06.250 --> 00:06:06.260 align:start position:0% override the finalized checkpoint unless 00:06:06.260 --> 00:06:09.040 align:start position:0% override the finalized checkpoint unless there's<00:06:07.250> an<00:06:07.460> attack<00:06:07.789> but<00:06:08.450> in<00:06:08.630> that<00:06:08.750> case<00:06:08.990> we 00:06:09.040 --> 00:06:09.050 align:start position:0% there's an attack but in that case we 00:06:09.050 --> 00:06:13.330 align:start position:0% there's an attack but in that case we can<00:06:09.470> know<00:06:09.650> for<00:06:09.680> sure<00:06:09.890> that<00:06:10.210> this<00:06:11.210> a<00:06:12.160> winter<00:06:13.160> of 00:06:13.330 --> 00:06:13.340 align:start position:0% can know for sure that this a winter of 00:06:13.340 --> 00:06:14.590 align:start position:0% can know for sure that this a winter of the<00:06:13.430> valley<00:06:13.610> that<00:06:13.760> in<00:06:13.880> East<00:06:14.060> will<00:06:14.270> be<00:06:14.300> burned 00:06:14.590 --> 00:06:14.600 align:start position:0% the valley that in East will be burned 00:06:14.600 --> 00:06:18.040 align:start position:0% the valley that in East will be burned so<00:06:14.720> the<00:06:14.990> type<00:06:15.200> of<00:06:15.229> here<00:06:15.470> and<00:06:16.539> for<00:06:17.539> final<00:06:17.990> are 00:06:18.040 --> 00:06:18.050 align:start position:0% so the type of here and for final are 00:06:18.050 --> 00:06:20.380 align:start position:0% so the type of here and for final are justified<00:06:18.919> checkpoint<00:06:19.400> it<00:06:19.970> can<00:06:20.090> be<00:06:20.180> over 00:06:20.380 --> 00:06:20.390 align:start position:0% justified checkpoint it can be over 00:06:20.390 --> 00:06:22.870 align:start position:0% justified checkpoint it can be over right<00:06:20.539> it<00:06:20.870> can<00:06:21.169> be<00:06:21.200> overridden<00:06:21.530> we<00:06:22.460> will 00:06:22.870 --> 00:06:22.880 align:start position:0% right it can be overridden we will 00:06:22.880 --> 00:06:25.719 align:start position:0% right it can be overridden we will choose<00:06:23.870> we<00:06:24.260> will<00:06:24.410> switch<00:06:24.740> to<00:06:25.010> the<00:06:25.220> more<00:06:25.550> recent 00:06:25.719 --> 00:06:25.729 align:start position:0% choose we will switch to the more recent 00:06:25.729 --> 00:06:30.730 align:start position:0% choose we will switch to the more recent justify<00:06:26.330> tree<00:06:26.510> point<00:06:28.240> okay<00:06:29.240> so<00:06:29.870> after<00:06:30.080> justify 00:06:30.730 --> 00:06:30.740 align:start position:0% justify tree point okay so after justify 00:06:30.740 --> 00:06:33.640 align:start position:0% justify tree point okay so after justify try<00:06:30.979> point<00:06:31.280> is<00:06:31.460> decided<00:06:32.030> we<00:06:32.660> apply<00:06:32.960> the<00:06:33.020> forest 00:06:33.640 --> 00:06:33.650 align:start position:0% try point is decided we apply the forest 00:06:33.650 --> 00:06:37.719 align:start position:0% try point is decided we apply the forest road<00:06:33.800> on<00:06:33.979> different<00:06:34.370> row<00:06:34.520> chains<00:06:34.850> and<00:06:36.729> the 00:06:37.719 --> 00:06:37.729 align:start position:0% road on different row chains and the 00:06:37.729 --> 00:06:40.300 align:start position:0% road on different row chains and the score<00:06:38.030> counting<00:06:38.659> stars<00:06:39.020> from<00:06:39.320> justified<00:06:40.130> tree 00:06:40.300 --> 00:06:40.310 align:start position:0% score counting stars from justified tree 00:06:40.310 --> 00:06:42.129 align:start position:0% score counting stars from justified tree point<00:06:40.550> but<00:06:41.360> here<00:06:41.659> we 00:06:42.129 --> 00:06:42.139 align:start position:0% point but here we 00:06:42.139 --> 00:06:45.670 align:start position:0% point but here we and<00:06:42.229> I<00:06:42.409> use<00:06:42.819> longest<00:06:43.819> chain<00:06:44.090> rule<00:06:44.300> because<00:06:44.680> as 00:06:45.670 --> 00:06:45.680 align:start position:0% and I use longest chain rule because as 00:06:45.680 --> 00:06:49.209 align:start position:0% and I use longest chain rule because as I<00:06:45.830> previously<00:06:46.069> mentioned<00:06:47.289> the<00:06:48.289> attacker<00:06:48.860> can 00:06:49.209 --> 00:06:49.219 align:start position:0% I previously mentioned the attacker can 00:06:49.219 --> 00:06:51.369 align:start position:0% I previously mentioned the attacker can secretly<00:06:49.610> secretly<00:06:50.180> create<00:06:50.749> super<00:06:51.050> long<00:06:51.169> four 00:06:51.369 --> 00:06:51.379 align:start position:0% secretly secretly create super long four 00:06:51.379 --> 00:06:52.679 align:start position:0% secretly secretly create super long four chains<00:06:51.650> anytime 00:06:52.679 --> 00:06:52.689 align:start position:0% chains anytime 00:06:52.689 --> 00:06:56.879 align:start position:0% chains anytime so<00:06:53.689> what<00:06:54.379> pro-choice<00:06:54.919> rule<00:06:55.189> do<00:06:55.340> we<00:06:55.370> use<00:06:55.840> we<00:06:56.840> use 00:06:56.879 --> 00:06:56.889 align:start position:0% so what pro-choice rule do we use we use 00:06:56.889 --> 00:07:00.100 align:start position:0% so what pro-choice rule do we use we use element<00:06:57.889> II<00:06:58.039> ghost<00:06:58.419> stands<00:06:59.419> for<00:06:59.599> latest 00:07:00.100 --> 00:07:00.110 align:start position:0% element II ghost stands for latest 00:07:00.110 --> 00:07:02.649 align:start position:0% element II ghost stands for latest message<00:07:00.650> driven<00:07:00.979> ghost<00:07:01.550> go<00:07:02.210> stands<00:07:02.479> for 00:07:02.649 --> 00:07:02.659 align:start position:0% message driven ghost go stands for 00:07:02.659 --> 00:07:07.659 align:start position:0% message driven ghost go stands for gritty<00:07:03.469> heavies<00:07:04.039> observed<00:07:04.639> subtree<00:07:05.620> um<00:07:06.669> how 00:07:07.659 --> 00:07:07.669 align:start position:0% gritty heavies observed subtree um how 00:07:07.669 --> 00:07:11.050 align:start position:0% gritty heavies observed subtree um how does<00:07:07.729> the<00:07:08.090> ghost<00:07:08.569> for<00:07:09.110> choice<00:07:09.229> rule<00:07:09.499> works<00:07:10.060> say 00:07:11.050 --> 00:07:11.060 align:start position:0% does the ghost for choice rule works say 00:07:11.060 --> 00:07:12.730 align:start position:0% does the ghost for choice rule works say we<00:07:11.240> have<00:07:11.389> different<00:07:11.810> flow<00:07:11.960> change<00:07:12.259> here<00:07:12.560> and 00:07:12.730 --> 00:07:12.740 align:start position:0% we have different flow change here and 00:07:12.740 --> 00:07:16.990 align:start position:0% we have different flow change here and the<00:07:13.669> y<00:07:13.879> square<00:07:14.330> is<00:07:14.539> the<00:07:14.870> block<00:07:15.139> and<00:07:16.000> green 00:07:16.990 --> 00:07:17.000 align:start position:0% the y square is the block and green 00:07:17.000 --> 00:07:20.350 align:start position:0% the y square is the block and green circle<00:07:17.689> is<00:07:17.900> the<00:07:18.219> attestation<00:07:19.219> yes<00:07:19.909> the<00:07:20.240> other 00:07:20.350 --> 00:07:20.360 align:start position:0% circle is the attestation yes the other 00:07:20.360 --> 00:07:23.320 align:start position:0% circle is the attestation yes the other station<00:07:20.750> is<00:07:20.870> the<00:07:21.110> validator<00:07:21.680> the<00:07:22.580> vole<00:07:22.789> caste 00:07:23.320 --> 00:07:23.330 align:start position:0% station is the validator the vole caste 00:07:23.330 --> 00:07:26.290 align:start position:0% station is the validator the vole caste by<00:07:23.479> the<00:07:23.539> very<00:07:23.779> letter<00:07:24.189> the<00:07:25.189> validator<00:07:25.669> would 00:07:26.290 --> 00:07:26.300 align:start position:0% by the very letter the validator would 00:07:26.300 --> 00:07:30.100 align:start position:0% by the very letter the validator would vote<00:07:26.689> for<00:07:26.750> the<00:07:27.139> block<00:07:27.830> now<00:07:28.639> they<00:07:29.060> think<00:07:29.120> is<00:07:29.840> the 00:07:30.100 --> 00:07:30.110 align:start position:0% vote for the block now they think is the 00:07:30.110 --> 00:07:31.959 align:start position:0% vote for the block now they think is the head<00:07:30.319> block<00:07:30.560> of<00:07:30.800> the<00:07:30.919> canonical<00:07:31.219> chain<00:07:31.699> at 00:07:31.959 --> 00:07:31.969 align:start position:0% head block of the canonical chain at 00:07:31.969 --> 00:07:37.240 align:start position:0% head block of the canonical chain at that<00:07:32.210> time<00:07:33.310> so<00:07:34.310> we<00:07:34.339> have<00:07:34.669> the<00:07:34.789> votes<00:07:35.029> and<00:07:36.250> then 00:07:37.240 --> 00:07:37.250 align:start position:0% that time so we have the votes and then 00:07:37.250 --> 00:07:39.790 align:start position:0% that time so we have the votes and then we<00:07:37.969> will<00:07:38.180> do<00:07:38.330> the<00:07:38.360> score<00:07:38.689> count<00:07:38.900> the<00:07:39.080> score<00:07:39.439> of 00:07:39.790 --> 00:07:39.800 align:start position:0% we will do the score count the score of 00:07:39.800 --> 00:07:45.189 align:start position:0% we will do the score count the score of a<00:07:40.039> block<00:07:40.339> is<00:07:41.169> the<00:07:42.169> sum<00:07:42.469> of<00:07:42.680> the<00:07:43.360> score<00:07:44.360> of<00:07:44.599> his 00:07:45.189 --> 00:07:45.199 align:start position:0% a block is the sum of the score of his 00:07:45.199 --> 00:07:50.679 align:start position:0% a block is the sum of the score of his chat<00:07:45.529> box<00:07:46.029> and<00:07:47.740> once<00:07:48.740> we<00:07:48.979> have<00:07:49.360> the<00:07:50.360> score 00:07:50.679 --> 00:07:50.689 align:start position:0% chat box and once we have the score 00:07:50.689 --> 00:07:53.170 align:start position:0% chat box and once we have the score count<00:07:50.960> we<00:07:51.439> will<00:07:51.680> start<00:07:51.949> from<00:07:52.099> justified<00:07:52.879> track 00:07:53.170 --> 00:07:53.180 align:start position:0% count we will start from justified track 00:07:53.180 --> 00:07:55.990 align:start position:0% count we will start from justified track point<00:07:53.479> and<00:07:53.889> goes<00:07:54.889> all<00:07:55.129> the<00:07:55.159> way<00:07:55.250> down<00:07:55.370> to<00:07:55.879> the 00:07:55.990 --> 00:07:56.000 align:start position:0% point and goes all the way down to the 00:07:56.000 --> 00:08:00.070 align:start position:0% point and goes all the way down to the headlock<00:07:56.360> and<00:07:57.039> in<00:07:58.039> each<00:07:58.339> step<00:07:58.639> each<00:07:58.939> in<00:07:59.389> in 00:08:00.070 --> 00:08:00.080 align:start position:0% headlock and in each step each in in 00:08:00.080 --> 00:08:03.279 align:start position:0% headlock and in each step each in in each<00:08:00.259> step<00:08:00.729> when<00:08:01.729> there<00:08:01.849> is<00:08:01.939> a<00:08:01.969> fork<00:08:02.360> we<00:08:02.810> choose 00:08:03.279 --> 00:08:03.289 align:start position:0% each step when there is a fork we choose 00:08:03.289 --> 00:08:06.309 align:start position:0% each step when there is a fork we choose the<00:08:03.500> one<00:08:03.680> with<00:08:03.860> higher<00:08:04.159> score<00:08:04.550> and<00:08:04.879> so<00:08:05.810> in<00:08:06.020> goes 00:08:06.309 --> 00:08:06.319 align:start position:0% the one with higher score and so in goes 00:08:06.319 --> 00:08:07.389 align:start position:0% the one with higher score and so in goes for<00:08:06.740> gyro 00:08:07.389 --> 00:08:07.399 align:start position:0% for gyro 00:08:07.399 --> 00:08:10.300 align:start position:0% for gyro we<00:08:07.490> will<00:08:07.639> have<00:08:07.849> the<00:08:08.360> chain<00:08:08.930> on<00:08:09.139> the<00:08:09.229> top<00:08:09.469> as<00:08:09.710> the 00:08:10.300 --> 00:08:10.310 align:start position:0% we will have the chain on the top as the 00:08:10.310 --> 00:08:12.129 align:start position:0% we will have the chain on the top as the winning<00:08:10.580> chain<00:08:10.819> as<00:08:11.000> the<00:08:11.389> chain<00:08:11.750> with<00:08:11.899> higher 00:08:12.129 --> 00:08:12.139 align:start position:0% winning chain as the chain with higher 00:08:12.139 --> 00:08:17.439 align:start position:0% winning chain as the chain with higher highest<00:08:12.740> score<00:08:14.680> okay<00:08:15.710> next<00:08:16.159> how<00:08:16.310> does<00:08:16.789> the 00:08:17.439 --> 00:08:17.449 align:start position:0% highest score okay next how does the 00:08:17.449 --> 00:08:20.379 align:start position:0% highest score okay next how does the element<00:08:17.899> he<00:08:17.990> goes<00:08:18.199> works<00:08:18.500> on<00:08:18.830> the<00:08:19.520> post<00:08:20.149> by 00:08:20.379 --> 00:08:20.389 align:start position:0% element he goes works on the post by 00:08:20.389 --> 00:08:23.920 align:start position:0% element he goes works on the post by their<00:08:20.779> ex<00:08:20.990> research<00:08:21.469> samurais<00:08:22.039> pre-world<00:08:22.930> you 00:08:23.920 --> 00:08:23.930 align:start position:0% their ex research samurais pre-world you 00:08:23.930 --> 00:08:26.439 align:start position:0% their ex research samurais pre-world you don't<00:08:24.139> care<00:08:24.439> test<00:08:25.039> votes<00:08:25.310> with<00:08:25.759> sender<00:08:26.210> might 00:08:26.439 --> 00:08:26.449 align:start position:0% don't care test votes with sender might 00:08:26.449 --> 00:08:29.170 align:start position:0% don't care test votes with sender might not<00:08:26.599> receive<00:08:27.080> other<00:08:27.439> messages<00:08:28.039> due<00:08:28.339> to<00:08:28.580> the 00:08:29.170 --> 00:08:29.180 align:start position:0% not receive other messages due to the 00:08:29.180 --> 00:08:32.860 align:start position:0% not receive other messages due to the net<00:08:29.360> world<00:08:29.569> latency<00:08:31.209> insured<00:08:32.209> it<00:08:32.419> means<00:08:32.630> that 00:08:32.860 --> 00:08:32.870 align:start position:0% net world latency insured it means that 00:08:32.870 --> 00:08:35.319 align:start position:0% net world latency insured it means that we<00:08:33.469> only<00:08:33.500> counted<00:08:34.190> well<00:08:34.490> terrorists<00:08:34.909> lettuce 00:08:35.319 --> 00:08:35.329 align:start position:0% we only counted well terrorists lettuce 00:08:35.329 --> 00:08:40.360 align:start position:0% we only counted well terrorists lettuce vote<00:08:36.610> so<00:08:37.610> now<00:08:38.360> say<00:08:39.320> there<00:08:39.620> are<00:08:39.769> six<00:08:40.010> valid 00:08:40.360 --> 00:08:40.370 align:start position:0% vote so now say there are six valid 00:08:40.370 --> 00:08:42.909 align:start position:0% vote so now say there are six valid errors<00:08:40.640> and<00:08:40.909> these<00:08:41.779> are<00:08:41.990> the<00:08:42.110> votes<00:08:42.349> that<00:08:42.529> cast 00:08:42.909 --> 00:08:42.919 align:start position:0% errors and these are the votes that cast 00:08:42.919 --> 00:08:47.620 align:start position:0% errors and these are the votes that cast and<00:08:43.849> since<00:08:44.540> in<00:08:44.810> element<00:08:45.350> egos<00:08:45.649> we<00:08:46.040> only<00:08:46.630> count 00:08:47.620 --> 00:08:47.630 align:start position:0% and since in element egos we only count 00:08:47.630 --> 00:08:50.280 align:start position:0% and since in element egos we only count the<00:08:47.779> validators<00:08:48.230> lettuce<00:08:48.620> vote<00:08:48.920> so<00:08:49.670> this<00:08:49.880> will 00:08:50.280 --> 00:08:50.290 align:start position:0% the validators lettuce vote so this will 00:08:50.290 --> 00:08:52.900 align:start position:0% the validators lettuce vote so this will what<00:08:51.290> a<00:08:51.319> is<00:08:51.800> this<00:08:52.250> will<00:08:52.399> be<00:08:52.490> what<00:08:52.519> the<00:08:52.730> vote 00:08:52.900 --> 00:08:52.910 align:start position:0% what a is this will be what the vote 00:08:52.910 --> 00:08:55.780 align:start position:0% what a is this will be what the vote count<00:08:53.120> like<00:08:53.300> and<00:08:53.540> so<00:08:54.500> we<00:08:54.920> will<00:08:55.069> get 00:08:55.780 --> 00:08:55.790 align:start position:0% count like and so we will get 00:08:55.790 --> 00:08:58.030 align:start position:0% count like and so we will get a<00:08:55.820> different<00:08:56.390> score<00:08:56.600> account<00:08:56.930> and<00:08:57.170> apply<00:08:57.980> the 00:08:58.030 --> 00:08:58.040 align:start position:0% a different score account and apply the 00:08:58.040 --> 00:09:01.530 align:start position:0% a different score account and apply the same<00:08:58.660> rule<00:08:59.660> a<00:08:59.930> centrist<00:09:00.530> enroll<00:09:00.890> who<00:09:01.130> you<00:09:01.280> have 00:09:01.530 --> 00:09:01.540 align:start position:0% same rule a centrist enroll who you have 00:09:01.540 --> 00:09:05.500 align:start position:0% same rule a centrist enroll who you have now<00:09:02.540> will<00:09:03.080> have<00:09:03.260> the<00:09:03.790> channel<00:09:04.790> on<00:09:04.970> the<00:09:05.240> button 00:09:05.500 --> 00:09:05.510 align:start position:0% now will have the channel on the button 00:09:05.510 --> 00:09:09.430 align:start position:0% now will have the channel on the button as<00:09:05.690> the<00:09:06.140> winning<00:09:06.410> chain<00:09:07.660> and<00:09:08.660> now<00:09:09.050> I<00:09:09.080> want<00:09:09.380> to 00:09:09.430 --> 00:09:09.440 align:start position:0% as the winning chain and now I want to 00:09:09.440 --> 00:09:12.190 align:start position:0% as the winning chain and now I want to briefly<00:09:09.680> mention<00:09:10.070> the<00:09:10.630> optimization<00:09:11.630> on<00:09:11.780> LMD 00:09:12.190 --> 00:09:12.200 align:start position:0% briefly mention the optimization on LMD 00:09:12.200 --> 00:09:16.720 align:start position:0% briefly mention the optimization on LMD ghost<00:09:12.580> the<00:09:13.580> idea<00:09:14.030> of<00:09:14.360> the<00:09:15.400> optimization<00:09:16.400> is 00:09:16.720 --> 00:09:16.730 align:start position:0% ghost the idea of the optimization is 00:09:16.730 --> 00:09:18.850 align:start position:0% ghost the idea of the optimization is basically<00:09:17.390> that<00:09:17.570> when<00:09:17.810> we<00:09:17.900> run<00:09:18.110> in<00:09:18.260> a<00:09:18.320> forest 00:09:18.850 --> 00:09:18.860 align:start position:0% basically that when we run in a forest 00:09:18.860 --> 00:09:22.810 align:start position:0% basically that when we run in a forest rule<00:09:19.070> we<00:09:20.030> skip<00:09:20.450> the<00:09:20.660> blocks<00:09:20.960> that<00:09:21.610> no<00:09:22.610> veteran 00:09:22.810 --> 00:09:22.820 align:start position:0% rule we skip the blocks that no veteran 00:09:22.820 --> 00:09:25.240 align:start position:0% rule we skip the blocks that no veteran is<00:09:23.120> vote<00:09:23.330> for<00:09:23.570> and<00:09:23.840> so<00:09:24.650> this<00:09:24.830> would<00:09:25.040> save<00:09:25.220> a 00:09:25.240 --> 00:09:25.250 align:start position:0% is vote for and so this would save a 00:09:25.250 --> 00:09:28.420 align:start position:0% is vote for and so this would save a time<00:09:25.730> and<00:09:25.970> memory<00:09:26.420> when<00:09:26.950> traversing<00:09:27.950> a<00:09:28.220> block 00:09:28.420 --> 00:09:28.430 align:start position:0% time and memory when traversing a block 00:09:28.430 --> 00:09:31.510 align:start position:0% time and memory when traversing a block tree<00:09:28.670> back<00:09:28.880> and<00:09:29.030> forth<00:09:30.100> okay<00:09:31.100> there's<00:09:31.430> one 00:09:31.510 --> 00:09:31.520 align:start position:0% tree back and forth okay there's one 00:09:31.520 --> 00:09:33.910 align:start position:0% tree back and forth okay there's one thing<00:09:31.970> worth<00:09:32.180> mentioning<00:09:32.450> is<00:09:32.840> that<00:09:33.200> we're 00:09:33.910 --> 00:09:33.920 align:start position:0% thing worth mentioning is that we're 00:09:33.920 --> 00:09:36.070 align:start position:0% thing worth mentioning is that we're seeing<00:09:34.160> blocks<00:09:34.490> but<00:09:34.880> not<00:09:35.120> yet<00:09:35.330> attestations 00:09:36.070 --> 00:09:36.080 align:start position:0% seeing blocks but not yet attestations 00:09:36.080 --> 00:09:38.680 align:start position:0% seeing blocks but not yet attestations so<00:09:37.070> we<00:09:37.220> wait<00:09:37.460> for<00:09:37.670> attestation<00:09:38.240> to<00:09:38.450> be 00:09:38.680 --> 00:09:38.690 align:start position:0% so we wait for attestation to be 00:09:38.690 --> 00:09:41.590 align:start position:0% so we wait for attestation to be propagated<00:09:38.960> to<00:09:39.320> us<00:09:39.730> it<00:09:40.730> can<00:09:40.910> come<00:09:41.090> in<00:09:41.360> as<00:09:41.570> a 00:09:41.590 --> 00:09:41.600 align:start position:0% propagated to us it can come in as a 00:09:41.600 --> 00:09:43.810 align:start position:0% propagated to us it can come in as a form<00:09:41.960> of<00:09:42.080> single<00:09:42.320> authorization<00:09:43.160> aggregated 00:09:43.810 --> 00:09:43.820 align:start position:0% form of single authorization aggregated 00:09:43.820 --> 00:09:46.150 align:start position:0% form of single authorization aggregated other<00:09:43.940> stations<00:09:44.480> or<00:09:44.720> other<00:09:45.040> stations<00:09:46.040> that 00:09:46.150 --> 00:09:46.160 align:start position:0% other stations or other stations that 00:09:46.160 --> 00:09:48.850 align:start position:0% other stations or other stations that included<00:09:47.030> in<00:09:47.090> the<00:09:47.180> blocks<00:09:47.390> and<00:09:47.630> we<00:09:48.320> take<00:09:48.620> all 00:09:48.850 --> 00:09:48.860 align:start position:0% included in the blocks and we take all 00:09:48.860 --> 00:09:51.220 align:start position:0% included in the blocks and we take all three<00:09:49.280> kinds<00:09:49.460> of<00:09:49.760> a<00:09:49.940> station<00:09:50.510> into<00:09:50.900> account 00:09:51.220 --> 00:09:51.230 align:start position:0% three kinds of a station into account 00:09:51.230 --> 00:09:55.060 align:start position:0% three kinds of a station into account when<00:09:51.590> in<00:09:52.250> our<00:09:52.370> for<00:09:52.640> choice<00:09:52.760> rule<00:09:53.590> but<00:09:54.590> since<00:09:54.830> we 00:09:55.060 --> 00:09:55.070 align:start position:0% when in our for choice rule but since we 00:09:55.070 --> 00:09:58.090 align:start position:0% when in our for choice rule but since we do<00:09:55.250> not<00:09:55.280> think<00:09:55.760> the<00:09:56.120> attestation<00:09:56.920> Ana<00:09:57.920> means 00:09:58.090 --> 00:09:58.100 align:start position:0% do not think the attestation Ana means 00:09:58.100 --> 00:10:00.340 align:start position:0% do not think the attestation Ana means every<00:09:58.700> no<00:09:58.880> could<00:09:59.300> receive<00:10:00.080> different 00:10:00.340 --> 00:10:00.350 align:start position:0% every no could receive different 00:10:00.350 --> 00:10:03.550 align:start position:0% every no could receive different attestation<00:10:01.010> at<00:10:01.490> different<00:10:01.910> time<00:10:02.140> so<00:10:03.140> every 00:10:03.550 --> 00:10:03.560 align:start position:0% attestation at different time so every 00:10:03.560 --> 00:10:04.930 align:start position:0% attestation at different time so every no<00:10:03.680> crew<00:10:03.890> had<00:10:04.070> different<00:10:04.430> view<00:10:04.670> they<00:10:04.910> have 00:10:04.930 --> 00:10:04.940 align:start position:0% no crew had different view they have 00:10:04.940 --> 00:10:06.040 align:start position:0% no crew had different view they have different<00:10:05.480> they<00:10:05.540> could<00:10:05.750> have<00:10:05.870> different 00:10:06.040 --> 00:10:06.050 align:start position:0% different they could have different 00:10:06.050 --> 00:10:09.460 align:start position:0% different they could have different vocal<00:10:06.650> fold<00:10:06.980> each<00:10:07.400> for<00:10:07.880> chains<00:10:08.180> so<00:10:09.080> this 00:10:09.460 --> 00:10:09.470 align:start position:0% vocal fold each for chains so this 00:10:09.470 --> 00:10:12.610 align:start position:0% vocal fold each for chains so this creates<00:10:10.190> a<00:10:10.610> window<00:10:11.180> for<00:10:11.390> the<00:10:11.510> attacker<00:10:11.840> the 00:10:12.610 --> 00:10:12.620 align:start position:0% creates a window for the attacker the 00:10:12.620 --> 00:10:14.650 align:start position:0% creates a window for the attacker the attacker<00:10:12.920> can<00:10:13.250> withhold<00:10:13.430> attestation<00:10:14.180> and 00:10:14.650 --> 00:10:14.660 align:start position:0% attacker can withhold attestation and 00:10:14.660 --> 00:10:17.110 align:start position:0% attacker can withhold attestation and broadcast<00:10:15.230> them<00:10:15.380> I<00:10:15.590> wanted<00:10:15.920> to<00:10:16.130> make<00:10:16.430> a<00:10:16.670> victim 00:10:17.110 --> 00:10:17.120 align:start position:0% broadcast them I wanted to make a victim 00:10:17.120 --> 00:10:18.570 align:start position:0% broadcast them I wanted to make a victim switch<00:10:17.450> between<00:10:17.690> different<00:10:18.230> chains 00:10:18.570 --> 00:10:18.580 align:start position:0% switch between different chains 00:10:18.580 --> 00:10:22.420 align:start position:0% switch between different chains repeatedly<00:10:19.580> but<00:10:20.470> there's<00:10:21.470> a<00:10:21.770> prerequisite 00:10:22.420 --> 00:10:22.430 align:start position:0% repeatedly but there's a prerequisite 00:10:22.430 --> 00:10:24.280 align:start position:0% repeatedly but there's a prerequisite for<00:10:22.490> this<00:10:22.880> attack<00:10:23.240> is<00:10:23.480> that<00:10:23.510> there<00:10:23.900> has<00:10:24.080> to<00:10:24.110> be 00:10:24.280 --> 00:10:24.290 align:start position:0% for this attack is that there has to be 00:10:24.290 --> 00:10:29.200 align:start position:0% for this attack is that there has to be a<00:10:24.410> temporary<00:10:25.010> network<00:10:25.850> failure<00:10:26.270> and<00:10:27.940> one<00:10:28.940> tag 00:10:29.200 --> 00:10:29.210 align:start position:0% a temporary network failure and one tag 00:10:29.210 --> 00:10:31.540 align:start position:0% a temporary network failure and one tag is<00:10:29.420> called<00:10:29.510> decoy<00:10:30.230> flip-flop<00:10:30.950> attack<00:10:31.250> and 00:10:31.540 --> 00:10:31.550 align:start position:0% is called decoy flip-flop attack and 00:10:31.550 --> 00:10:33.400 align:start position:0% is called decoy flip-flop attack and really<00:10:32.270> you<00:10:32.360> can<00:10:32.390> read<00:10:32.690> more<00:10:32.810> about<00:10:32.870> it<00:10:33.080> on<00:10:33.260> the 00:10:33.400 --> 00:10:33.410 align:start position:0% really you can read more about it on the 00:10:33.410 --> 00:10:36.430 align:start position:0% really you can read more about it on the research<00:10:34.220> forum<00:10:34.640> and<00:10:34.970> one<00:10:35.840> possible 00:10:36.430 --> 00:10:36.440 align:start position:0% research forum and one possible 00:10:36.440 --> 00:10:39.010 align:start position:0% research forum and one possible mitigation<00:10:36.650> is<00:10:37.370> the<00:10:37.820> recent<00:10:38.270> proposed 00:10:39.010 --> 00:10:39.020 align:start position:0% mitigation is the recent proposed 00:10:39.020 --> 00:10:42.010 align:start position:0% mitigation is the recent proposed recently<00:10:39.650> proposed<00:10:40.190> variant<00:10:41.180> of<00:10:41.330> course<00:10:41.660> is 00:10:42.010 --> 00:10:42.020 align:start position:0% recently proposed variant of course is 00:10:42.020 --> 00:10:44.640 align:start position:0% recently proposed variant of course is called<00:10:42.410> fresh<00:10:42.770> message<00:10:43.160> driven<00:10:43.610> ghost<00:10:44.030> and 00:10:44.640 --> 00:10:44.650 align:start position:0% called fresh message driven ghost and 00:10:44.650 --> 00:10:47.500 align:start position:0% called fresh message driven ghost and insured<00:10:45.650> is<00:10:46.010> basically<00:10:46.610> that<00:10:46.880> we<00:10:47.150> do<00:10:47.330> now 00:10:47.500 --> 00:10:47.510 align:start position:0% insured is basically that we do now 00:10:47.510 --> 00:10:49.990 align:start position:0% insured is basically that we do now except<00:10:47.960> attestation<00:10:48.500> to<00:10:48.710> long<00:10:49.070> ago<00:10:49.190> for 00:10:49.990 --> 00:10:50.000 align:start position:0% except attestation to long ago for 00:10:50.000 --> 00:10:52.390 align:start position:0% except attestation to long ago for example<00:10:50.480> we<00:10:50.600> do<00:10:50.720> not<00:10:50.750> accept<00:10:51.140> a<00:10:51.380> station<00:10:52.190> from 00:10:52.390 --> 00:10:52.400 align:start position:0% example we do not accept a station from 00:10:52.400 --> 00:10:56.110 align:start position:0% example we do not accept a station from maybe<00:10:52.700> to<00:10:52.880> a<00:10:52.910> particle<00:10:53.330> and<00:10:54.580> okay<00:10:55.580> that's<00:10:55.910> my 00:10:56.110 --> 00:10:56.120 align:start position:0% maybe to a particle and okay that's my 00:10:56.120 --> 00:10:58.210 align:start position:0% maybe to a particle and okay that's my introduction<00:10:56.480> and<00:10:56.780> we<00:10:56.990> subjectivity<00:10:57.500> is<00:10:57.950> to 00:10:58.210 --> 00:10:58.220 align:start position:0% introduction and we subjectivity is to 00:10:58.220 --> 00:11:01.090 align:start position:0% introduction and we subjectivity is to sing<00:10:58.490> and<00:10:58.700> fotress<00:10:59.030> row<00:10:59.420> today<00:10:59.600> thank<00:11:00.140> you 00:11:01.090 --> 00:11:01.100 align:start position:0% sing and fotress row today thank you 00:11:01.100 --> 00:11:13.759 align:start position:0% sing and fotress row today thank you [Applause] 00:11:13.759 --> 00:11:13.769 align:start position:0% 00:11:13.769 --> 00:11:15.829 align:start position:0% you