WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.129 align:start position:0% [Music] 00:00:12.129 --> 00:00:12.139 align:start position:0% 00:00:12.139 --> 00:00:15.350 align:start position:0% convinces<00:00:13.139> this<00:00:13.679> last<00:00:13.920> group<00:00:14.099> of<00:00:14.340> people<00:00:14.519> that 00:00:15.350 --> 00:00:15.360 align:start position:0% convinces this last group of people that 00:00:15.360 --> 00:00:18.050 align:start position:0% convinces this last group of people that this<00:00:15.660> might<00:00:16.020> not<00:00:16.379> be<00:00:16.619> the<00:00:16.920> best<00:00:17.039> decision<00:00:17.460> for 00:00:18.050 --> 00:00:18.060 align:start position:0% this might not be the best decision for 00:00:18.060 --> 00:00:21.290 align:start position:0% this might not be the best decision for ethereum<00:00:18.840> and<00:00:19.619> that<00:00:19.859> it's<00:00:20.100> actually<00:00:20.520> not<00:00:21.119> that 00:00:21.290 --> 00:00:21.300 align:start position:0% ethereum and that it's actually not that 00:00:21.300 --> 00:00:23.390 align:start position:0% ethereum and that it's actually not that hard<00:00:21.539> to<00:00:21.900> take<00:00:22.020> cards<00:00:22.619> into<00:00:22.859> your<00:00:23.039> own<00:00:23.220> matter 00:00:23.390 --> 00:00:23.400 align:start position:0% hard to take cards into your own matter 00:00:23.400 --> 00:00:25.550 align:start position:0% hard to take cards into your own matter and<00:00:23.880> to<00:00:24.119> actually<00:00:24.359> start<00:00:25.019> doing<00:00:25.199> it<00:00:25.380> yourself 00:00:25.550 --> 00:00:25.560 align:start position:0% and to actually start doing it yourself 00:00:25.560 --> 00:00:29.029 align:start position:0% and to actually start doing it yourself so<00:00:26.340> yeah<00:00:26.460> let's<00:00:26.699> go<00:00:26.939> for<00:00:27.060> it 00:00:29.029 --> 00:00:29.039 align:start position:0% so yeah let's go for it 00:00:29.039 --> 00:00:30.050 align:start position:0% so yeah let's go for it um 00:00:30.050 --> 00:00:30.060 align:start position:0% um 00:00:30.060 --> 00:00:32.269 align:start position:0% um this<00:00:30.660> is<00:00:30.779> what<00:00:30.960> vitalik<00:00:31.439> published<00:00:31.800> not<00:00:32.160> that 00:00:32.269 --> 00:00:32.279 align:start position:0% this is what vitalik published not that 00:00:32.279 --> 00:00:34.490 align:start position:0% this is what vitalik published not that long<00:00:32.460> ago<00:00:32.759> and<00:00:33.059> this<00:00:33.239> is<00:00:33.360> the<00:00:33.719> road<00:00:33.899> map<00:00:34.079> of 00:00:34.490 --> 00:00:34.500 align:start position:0% long ago and this is the road map of 00:00:34.500 --> 00:00:38.330 align:start position:0% long ago and this is the road map of ethereum<00:00:35.300> and<00:00:36.320> solo<00:00:37.320> stakers<00:00:37.800> are<00:00:38.160> people 00:00:38.330 --> 00:00:38.340 align:start position:0% ethereum and solo stakers are people 00:00:38.340 --> 00:00:39.950 align:start position:0% ethereum and solo stakers are people that<00:00:38.579> are<00:00:38.700> not<00:00:38.880> professional<00:00:39.420> stickers 00:00:39.950 --> 00:00:39.960 align:start position:0% that are not professional stickers 00:00:39.960 --> 00:00:41.389 align:start position:0% that are not professional stickers they're<00:00:40.200> not<00:00:40.379> professional<00:00:40.860> validators 00:00:41.389 --> 00:00:41.399 align:start position:0% they're not professional validators 00:00:41.399 --> 00:00:42.830 align:start position:0% they're not professional validators they're<00:00:41.700> people<00:00:41.940> that<00:00:42.239> have<00:00:42.360> their<00:00:42.540> own<00:00:42.660> jobs 00:00:42.830 --> 00:00:42.840 align:start position:0% they're people that have their own jobs 00:00:42.840 --> 00:00:44.869 align:start position:0% they're people that have their own jobs there<00:00:43.379> are<00:00:43.559> people<00:00:43.680> that<00:00:44.040> might<00:00:44.399> or<00:00:44.579> might<00:00:44.760> not 00:00:44.869 --> 00:00:44.879 align:start position:0% there are people that might or might not 00:00:44.879 --> 00:00:46.549 align:start position:0% there are people that might or might not have<00:00:45.059> children<00:00:45.300> they<00:00:45.660> might<00:00:45.840> have<00:00:45.960> hobbies 00:00:46.549 --> 00:00:46.559 align:start position:0% have children they might have hobbies 00:00:46.559 --> 00:00:48.170 align:start position:0% have children they might have hobbies they<00:00:46.980> might<00:00:47.160> have<00:00:47.340> other<00:00:47.460> things<00:00:47.700> to<00:00:47.879> do<00:00:48.000> than 00:00:48.170 --> 00:00:48.180 align:start position:0% they might have other things to do than 00:00:48.180 --> 00:00:50.209 align:start position:0% they might have other things to do than just<00:00:48.360> keeping<00:00:48.780> up<00:00:48.899> with<00:00:49.320> this 00:00:50.209 --> 00:00:50.219 align:start position:0% just keeping up with this 00:00:50.219 --> 00:00:53.209 align:start position:0% just keeping up with this so<00:00:51.120> how<00:00:51.899> the<00:00:52.140> heck<00:00:52.440> are<00:00:52.739> they<00:00:52.860> supposed<00:00:53.100> to 00:00:53.209 --> 00:00:53.219 align:start position:0% so how the heck are they supposed to 00:00:53.219 --> 00:00:54.650 align:start position:0% so how the heck are they supposed to keep<00:00:53.460> up<00:00:53.640> with<00:00:53.820> all<00:00:53.940> of<00:00:54.120> this<00:00:54.180> and<00:00:54.360> that's<00:00:54.480> the 00:00:54.650 --> 00:00:54.660 align:start position:0% keep up with all of this and that's the 00:00:54.660 --> 00:00:57.290 align:start position:0% keep up with all of this and that's the purpose<00:00:55.020> of<00:00:55.620> this<00:00:55.920> talk<00:00:56.100> we're<00:00:56.520> gonna<00:00:56.699> try<00:00:57.120> to 00:00:57.290 --> 00:00:57.300 align:start position:0% purpose of this talk we're gonna try to 00:00:57.300 --> 00:01:02.209 align:start position:0% purpose of this talk we're gonna try to lay<00:00:57.719> down<00:00:58.140> in<00:00:58.980> the<00:00:59.100> next<00:00:59.340> 25<00:01:00.300> minutes 00:01:02.209 --> 00:01:02.219 align:start position:0% lay down in the next 25 minutes 00:01:02.219 --> 00:01:04.310 align:start position:0% lay down in the next 25 minutes um<00:01:02.280> the<00:01:03.059> next<00:01:03.239> things<00:01:03.539> that<00:01:03.840> are<00:01:03.960> going<00:01:04.080> to<00:01:04.199> be 00:01:04.310 --> 00:01:04.320 align:start position:0% um the next things that are going to be 00:01:04.320 --> 00:01:06.350 align:start position:0% um the next things that are going to be huge<00:01:04.680> and<00:01:04.799> that<00:01:04.979> are<00:01:05.159> going<00:01:05.339> to<00:01:05.519> impact<00:01:05.820> us<00:01:06.060> all 00:01:06.350 --> 00:01:06.360 align:start position:0% huge and that are going to impact us all 00:01:06.360 --> 00:01:08.450 align:start position:0% huge and that are going to impact us all as<00:01:06.659> solo<00:01:07.080> stickers<00:01:07.500> and<00:01:07.920> that<00:01:08.040> we<00:01:08.220> need<00:01:08.340> to 00:01:08.450 --> 00:01:08.460 align:start position:0% as solo stickers and that we need to 00:01:08.460 --> 00:01:10.250 align:start position:0% as solo stickers and that we need to take<00:01:08.580> into<00:01:08.880> account 00:01:10.250 --> 00:01:10.260 align:start position:0% take into account 00:01:10.260 --> 00:01:13.130 align:start position:0% take into account um<00:01:10.380> and<00:01:10.920> how<00:01:11.100> to<00:01:11.280> react<00:01:11.520> with<00:01:11.760> it<00:01:12.360> so<00:01:12.780> first<00:01:12.900> of 00:01:13.130 --> 00:01:13.140 align:start position:0% um and how to react with it so first of 00:01:13.140 --> 00:01:13.969 align:start position:0% um and how to react with it so first of all 00:01:13.969 --> 00:01:13.979 align:start position:0% all 00:01:13.979 --> 00:01:15.289 align:start position:0% all um<00:01:14.100> let's<00:01:14.280> to<00:01:14.460> try<00:01:14.580> to<00:01:14.700> convince<00:01:15.000> these<00:01:15.240> people 00:01:15.289 --> 00:01:15.299 align:start position:0% um let's to try to convince these people 00:01:15.299 --> 00:01:18.530 align:start position:0% um let's to try to convince these people that<00:01:15.540> are<00:01:15.659> still<00:01:15.900> sticking<00:01:16.260> with<00:01:16.380> Kraken 00:01:18.530 --> 00:01:18.540 align:start position:0% that are still sticking with Kraken 00:01:18.540 --> 00:01:21.590 align:start position:0% that are still sticking with Kraken um<00:01:18.600> okay<00:01:18.900> so<00:01:19.320> it<00:01:19.979> is<00:01:20.159> vital<00:01:20.520> that<00:01:21.299> there<00:01:21.479> are 00:01:21.590 --> 00:01:21.600 align:start position:0% um okay so it is vital that there are 00:01:21.600 --> 00:01:23.090 align:start position:0% um okay so it is vital that there are more<00:01:21.780> solo<00:01:22.080> stickers<00:01:22.380> the<00:01:22.619> reason<00:01:22.799> of<00:01:22.979> this 00:01:23.090 --> 00:01:23.100 align:start position:0% more solo stickers the reason of this 00:01:23.100 --> 00:01:25.850 align:start position:0% more solo stickers the reason of this talk<00:01:23.280> is<00:01:23.580> because<00:01:23.700> we<00:01:24.000> need<00:01:24.119> to<00:01:24.240> convince<00:01:24.720> you 00:01:25.850 --> 00:01:25.860 align:start position:0% talk is because we need to convince you 00:01:25.860 --> 00:01:28.850 align:start position:0% talk is because we need to convince you that<00:01:26.759> you<00:01:27.119> can<00:01:27.240> stake<00:01:27.600> and<00:01:28.200> that<00:01:28.439> is<00:01:28.619> actually 00:01:28.850 --> 00:01:28.860 align:start position:0% that you can stake and that is actually 00:01:28.860 --> 00:01:30.830 align:start position:0% that you can stake and that is actually worth<00:01:29.100> it<00:01:29.280> it<00:01:29.460> is<00:01:29.580> valuable<00:01:29.880> it<00:01:30.240> is<00:01:30.360> vital<00:01:30.479> for 00:01:30.830 --> 00:01:30.840 align:start position:0% worth it it is valuable it is vital for 00:01:30.840 --> 00:01:32.990 align:start position:0% worth it it is valuable it is vital for ethereum<00:01:31.259> and<00:01:31.500> it's<00:01:31.740> actually<00:01:32.100> an 00:01:32.990 --> 00:01:33.000 align:start position:0% ethereum and it's actually an 00:01:33.000 --> 00:01:35.270 align:start position:0% ethereum and it's actually an existential<00:01:33.540> threat<00:01:33.840> to<00:01:34.140> ethereum<00:01:34.619> if<00:01:35.100> we 00:01:35.270 --> 00:01:35.280 align:start position:0% existential threat to ethereum if we 00:01:35.280 --> 00:01:37.069 align:start position:0% existential threat to ethereum if we don't<00:01:35.400> have<00:01:35.520> enough<00:01:35.700> solo<00:01:36.180> stickers 00:01:37.069 --> 00:01:37.079 align:start position:0% don't have enough solo stickers 00:01:37.079 --> 00:01:39.530 align:start position:0% don't have enough solo stickers so<00:01:37.680> we<00:01:38.040> all<00:01:38.159> have<00:01:38.340> seen<00:01:38.579> this 00:01:39.530 --> 00:01:39.540 align:start position:0% so we all have seen this 00:01:39.540 --> 00:01:41.870 align:start position:0% so we all have seen this um we'll<00:01:39.720> have<00:01:39.960> seen<00:01:40.200> how<00:01:40.920> a<00:01:41.460> very<00:01:41.640> few 00:01:41.870 --> 00:01:41.880 align:start position:0% um we'll have seen how a very few 00:01:41.880 --> 00:01:45.830 align:start position:0% um we'll have seen how a very few entities<00:01:42.299> control<00:01:42.780> a<00:01:43.320> huge<00:01:43.619> majority<00:01:44.119> of<00:01:45.119> the 00:01:45.830 --> 00:01:45.840 align:start position:0% entities control a huge majority of the 00:01:45.840 --> 00:01:48.170 align:start position:0% entities control a huge majority of the uh<00:01:46.079> of<00:01:46.380> the<00:01:46.560> validators 00:01:48.170 --> 00:01:48.180 align:start position:0% uh of the validators 00:01:48.180 --> 00:01:51.950 align:start position:0% uh of the validators um<00:01:48.240> who<00:01:49.079> he<00:01:49.200> remembers<00:01:49.680> the<00:01:49.979> steam<00:01:50.460> Fiasco 00:01:51.950 --> 00:01:51.960 align:start position:0% um who he remembers the steam Fiasco 00:01:51.960 --> 00:01:54.410 align:start position:0% um who he remembers the steam Fiasco the<00:01:52.439> blockchain<00:01:52.920> steam<00:01:53.520> Fiasco<00:01:53.880> right<00:01:54.119> so 00:01:54.410 --> 00:01:54.420 align:start position:0% the blockchain steam Fiasco right so 00:01:54.420 --> 00:01:56.870 align:start position:0% the blockchain steam Fiasco right so actually<00:01:55.020> having<00:01:55.560> centralized<00:01:56.399> validators 00:01:56.870 --> 00:01:56.880 align:start position:0% actually having centralized validators 00:01:56.880 --> 00:02:00.050 align:start position:0% actually having centralized validators or<00:01:57.180> centralized<00:01:57.659> centralized<00:01:58.680> um<00:01:58.799> with<00:01:59.520> it 00:02:00.050 --> 00:02:00.060 align:start position:0% or centralized centralized um with it 00:02:00.060 --> 00:02:01.910 align:start position:0% or centralized centralized um with it actually<00:02:00.180> can<00:02:00.479> can<00:02:00.780> do<00:02:01.079> things<00:02:01.320> like<00:02:01.560> we're 00:02:01.910 --> 00:02:01.920 align:start position:0% actually can can do things like we're 00:02:01.920 --> 00:02:04.429 align:start position:0% actually can can do things like we're just<00:02:02.159> in<00:02:02.579> Steam<00:02:03.180> Fiasco<00:02:03.479> was<00:02:03.600> just<00:02:03.780> in<00:02:03.899> sunbot 00:02:04.429 --> 00:02:04.439 align:start position:0% just in Steam Fiasco was just in sunbot 00:02:04.439 --> 00:02:06.350 align:start position:0% just in Steam Fiasco was just in sunbot steamit<00:02:05.159> which<00:02:05.280> was<00:02:05.399> a<00:02:05.579> company<00:02:05.700> that<00:02:06.240> was 00:02:06.350 --> 00:02:06.360 align:start position:0% steamit which was a company that was 00:02:06.360 --> 00:02:09.169 align:start position:0% steamit which was a company that was behind<00:02:06.719> the<00:02:07.020> blockchain<00:02:07.439> Steam<00:02:08.039> and<00:02:08.940> there 00:02:09.169 --> 00:02:09.179 align:start position:0% behind the blockchain Steam and there 00:02:09.179 --> 00:02:10.430 align:start position:0% behind the blockchain Steam and there were<00:02:09.300> some<00:02:09.420> people<00:02:09.539> that<00:02:09.720> were<00:02:09.899> that<00:02:10.080> did<00:02:10.319> not 00:02:10.430 --> 00:02:10.440 align:start position:0% were some people that were that did not 00:02:10.440 --> 00:02:12.530 align:start position:0% were some people that were that did not agree<00:02:10.679> with<00:02:10.860> him<00:02:11.099> so<00:02:11.580> he<00:02:11.879> basically<00:02:12.180> went<00:02:12.420> to 00:02:12.530 --> 00:02:12.540 align:start position:0% agree with him so he basically went to 00:02:12.540 --> 00:02:14.750 align:start position:0% agree with him so he basically went to poloniex<00:02:13.260> and<00:02:13.620> a<00:02:13.800> few<00:02:13.920> other<00:02:14.040> exchanges<00:02:14.580> and 00:02:14.750 --> 00:02:14.760 align:start position:0% poloniex and a few other exchanges and 00:02:14.760 --> 00:02:16.670 align:start position:0% poloniex and a few other exchanges and said<00:02:14.940> like<00:02:15.060> hey<00:02:15.239> Greg<00:02:15.480> hey<00:02:15.720> guys<00:02:15.900> take<00:02:16.440> this 00:02:16.670 --> 00:02:16.680 align:start position:0% said like hey Greg hey guys take this 00:02:16.680 --> 00:02:19.850 align:start position:0% said like hey Greg hey guys take this couple<00:02:16.860> Millie<00:02:17.400> and<00:02:18.300> we're<00:02:18.599> gonna<00:02:18.780> vote<00:02:19.200> for 00:02:19.850 --> 00:02:19.860 align:start position:0% couple Millie and we're gonna vote for 00:02:19.860 --> 00:02:22.790 align:start position:0% couple Millie and we're gonna vote for an<00:02:19.980> invalid<00:02:20.400> State<00:02:20.580> transaction<00:02:21.379> when<00:02:22.379> the 00:02:22.790 --> 00:02:22.800 align:start position:0% an invalid State transaction when the 00:02:22.800 --> 00:02:25.130 align:start position:0% an invalid State transaction when the accounts<00:02:23.220> of<00:02:23.459> these<00:02:23.700> opponents<00:02:24.239> of<00:02:24.360> mine<00:02:24.599> are 00:02:25.130 --> 00:02:25.140 align:start position:0% accounts of these opponents of mine are 00:02:25.140 --> 00:02:26.809 align:start position:0% accounts of these opponents of mine are going<00:02:25.260> to<00:02:25.440> be<00:02:25.560> emptied<00:02:25.980> from<00:02:26.220> one<00:02:26.400> block<00:02:26.580> to 00:02:26.809 --> 00:02:26.819 align:start position:0% going to be emptied from one block to 00:02:26.819 --> 00:02:28.610 align:start position:0% going to be emptied from one block to another<00:02:26.940> imagine<00:02:27.300> your<00:02:27.720> ethereum<00:02:28.200> accounts 00:02:28.610 --> 00:02:28.620 align:start position:0% another imagine your ethereum accounts 00:02:28.620 --> 00:02:30.589 align:start position:0% another imagine your ethereum accounts emptied<00:02:29.160> like<00:02:29.459> this<00:02:29.640> invalid<00:02:30.480> State 00:02:30.589 --> 00:02:30.599 align:start position:0% emptied like this invalid State 00:02:30.599 --> 00:02:32.630 align:start position:0% emptied like this invalid State transaction<00:02:31.080> this<00:02:31.440> is<00:02:31.560> what<00:02:31.739> happens<00:02:31.920> when<00:02:32.459> we 00:02:32.630 --> 00:02:32.640 align:start position:0% transaction this is what happens when we 00:02:32.640 --> 00:02:33.290 align:start position:0% transaction this is what happens when we got 00:02:33.290 --> 00:02:33.300 align:start position:0% got 00:02:33.300 --> 00:02:36.290 align:start position:0% got centralized<00:02:34.260> validators<00:02:34.920> so<00:02:35.520> yes<00:02:35.760> it<00:02:36.180> is 00:02:36.290 --> 00:02:36.300 align:start position:0% centralized validators so yes it is 00:02:36.300 --> 00:02:38.869 align:start position:0% centralized validators so yes it is dangerous<00:02:36.900> okay<00:02:37.680> but<00:02:38.160> not<00:02:38.280> only<00:02:38.400> this<00:02:38.640> there's 00:02:38.869 --> 00:02:38.879 align:start position:0% dangerous okay but not only this there's 00:02:38.879 --> 00:02:41.030 align:start position:0% dangerous okay but not only this there's even<00:02:39.120> a<00:02:39.480> more<00:02:39.959> Insidious<00:02:40.560> thing<00:02:40.800> that's 00:02:41.030 --> 00:02:41.040 align:start position:0% even a more Insidious thing that's 00:02:41.040 --> 00:02:44.869 align:start position:0% even a more Insidious thing that's happening<00:02:41.400> in<00:02:41.640> ethereum<00:02:42.440> right<00:02:43.440> now 00:02:44.869 --> 00:02:44.879 align:start position:0% happening in ethereum right now 00:02:44.879 --> 00:02:47.990 align:start position:0% happening in ethereum right now right<00:02:45.540> now<00:02:45.720> we<00:02:46.379> have<00:02:46.560> compliant<00:02:47.280> block 00:02:47.990 --> 00:02:48.000 align:start position:0% right now we have compliant block 00:02:48.000 --> 00:02:51.650 align:start position:0% right now we have compliant block production<00:02:48.500> through<00:02:49.500> things<00:02:49.800> like<00:02:50.040> Mev<00:02:50.640> boost 00:02:51.650 --> 00:02:51.660 align:start position:0% production through things like Mev boost 00:02:51.660 --> 00:02:55.070 align:start position:0% production through things like Mev boost we<00:02:52.080> have<00:02:52.260> a<00:02:52.620> 32<00:02:53.160> percent<00:02:53.580> of<00:02:54.060> the<00:02:54.239> blocks<00:02:54.660> being 00:02:55.070 --> 00:02:55.080 align:start position:0% we have a 32 percent of the blocks being 00:02:55.080 --> 00:02:57.890 align:start position:0% we have a 32 percent of the blocks being produced<00:02:55.500> in<00:02:55.739> ethereum<00:02:56.220> right<00:02:56.879> now 00:02:57.890 --> 00:02:57.900 align:start position:0% produced in ethereum right now 00:02:57.900 --> 00:03:01.070 align:start position:0% produced in ethereum right now at<00:02:58.379> 32<00:02:58.860> percent<00:02:59.160> of<00:02:59.519> blocks<00:02:59.940> produced<00:03:00.360> that 00:03:01.070 --> 00:03:01.080 align:start position:0% at 32 percent of blocks produced that 00:03:01.080 --> 00:03:03.290 align:start position:0% at 32 percent of blocks produced that are<00:03:01.319> ofac<00:03:01.920> compliant<00:03:02.459> that<00:03:02.700> means<00:03:02.879> that<00:03:03.000> if 00:03:03.290 --> 00:03:03.300 align:start position:0% are ofac compliant that means that if 00:03:03.300 --> 00:03:06.770 align:start position:0% are ofac compliant that means that if you<00:03:03.599> have<00:03:03.900> ever<00:03:04.620> used<00:03:04.980> tornado<00:03:05.819> cash 00:03:06.770 --> 00:03:06.780 align:start position:0% you have ever used tornado cash 00:03:06.780 --> 00:03:09.710 align:start position:0% you have ever used tornado cash there's<00:03:07.440> a<00:03:07.680> 32<00:03:08.040> percent<00:03:08.160> of<00:03:08.459> the<00:03:08.580> blocks<00:03:09.000> where 00:03:09.710 --> 00:03:09.720 align:start position:0% there's a 32 percent of the blocks where 00:03:09.720 --> 00:03:12.290 align:start position:0% there's a 32 percent of the blocks where your<00:03:09.900> transactions<00:03:10.560> are<00:03:10.800> not<00:03:10.920> going<00:03:11.159> in 00:03:12.290 --> 00:03:12.300 align:start position:0% your transactions are not going in 00:03:12.300 --> 00:03:13.670 align:start position:0% your transactions are not going in did<00:03:12.720> you<00:03:12.840> know<00:03:12.959> that<00:03:13.080> did<00:03:13.319> you<00:03:13.440> know<00:03:13.560> that 00:03:13.670 --> 00:03:13.680 align:start position:0% did you know that did you know that 00:03:13.680 --> 00:03:15.890 align:start position:0% did you know that did you know that you're<00:03:13.860> being<00:03:14.099> censored<00:03:14.640> in<00:03:14.879> 32<00:03:15.360> of<00:03:15.780> the 00:03:15.890 --> 00:03:15.900 align:start position:0% you're being censored in 32 of the 00:03:15.900 --> 00:03:17.630 align:start position:0% you're being censored in 32 of the blocks 00:03:17.630 --> 00:03:17.640 align:start position:0% blocks 00:03:17.640 --> 00:03:21.050 align:start position:0% blocks this<00:03:18.239> is<00:03:18.420> huge<00:03:19.319> and<00:03:19.860> this<00:03:19.980> is<00:03:20.099> Mev<00:03:20.519> boost<00:03:20.760> and 00:03:21.050 --> 00:03:21.060 align:start position:0% this is huge and this is Mev boost and 00:03:21.060 --> 00:03:22.910 align:start position:0% this is huge and this is Mev boost and if<00:03:21.300> we<00:03:21.420> go<00:03:21.599> into<00:03:21.780> the<00:03:21.959> Meb<00:03:22.319> boost<00:03:22.500> produce 00:03:22.910 --> 00:03:22.920 align:start position:0% if we go into the Meb boost produce 00:03:22.920 --> 00:03:26.570 align:start position:0% if we go into the Meb boost produce blocks<00:03:23.400> this<00:03:23.819> is<00:03:24.000> 87<00:03:24.680> are<00:03:25.680> come<00:03:25.860> from<00:03:25.980> relayers 00:03:26.570 --> 00:03:26.580 align:start position:0% blocks this is 87 are come from relayers 00:03:26.580 --> 00:03:28.070 align:start position:0% blocks this is 87 are come from relayers that<00:03:26.760> have<00:03:26.879> said<00:03:27.060> that<00:03:27.360> they<00:03:27.599> are<00:03:27.720> going<00:03:27.900> to 00:03:28.070 --> 00:03:28.080 align:start position:0% that have said that they are going to 00:03:28.080 --> 00:03:30.350 align:start position:0% that have said that they are going to comply<00:03:28.379> with<00:03:28.620> ofac<00:03:29.220> this<00:03:29.760> is<00:03:29.879> why<00:03:30.000> it's<00:03:30.120> so 00:03:30.350 --> 00:03:30.360 align:start position:0% comply with ofac this is why it's so 00:03:30.360 --> 00:03:31.550 align:start position:0% comply with ofac this is why it's so important<00:03:30.720> right 00:03:31.550 --> 00:03:31.560 align:start position:0% important right 00:03:31.560 --> 00:03:33.470 align:start position:0% important right Okay<00:03:32.040> so 00:03:33.470 --> 00:03:33.480 align:start position:0% Okay so 00:03:33.480 --> 00:03:35.750 align:start position:0% Okay so brief<00:03:34.260> uh<00:03:34.440> brief<00:03:34.739> introduction<00:03:35.040> to<00:03:35.220> dab<00:03:35.519> node 00:03:35.750 --> 00:03:35.760 align:start position:0% brief uh brief introduction to dab node 00:03:35.760 --> 00:03:37.430 align:start position:0% brief uh brief introduction to dab node dabnode<00:03:36.239> we're<00:03:36.360> here<00:03:36.540> to<00:03:36.659> make<00:03:36.780> it<00:03:36.959> easy<00:03:37.140> we're 00:03:37.430 --> 00:03:37.440 align:start position:0% dabnode we're here to make it easy we're 00:03:37.440 --> 00:03:40.430 align:start position:0% dabnode we're here to make it easy we're here<00:03:37.620> to<00:03:37.920> make<00:03:38.040> it<00:03:38.159> easier<00:03:38.459> for<00:03:38.640> people<00:03:38.840> to<00:03:39.840> run 00:03:40.430 --> 00:03:40.440 align:start position:0% here to make it easier for people to run 00:03:40.440 --> 00:03:43.190 align:start position:0% here to make it easier for people to run nodes<00:03:41.040> we<00:03:41.700> provide<00:03:42.000> a<00:03:42.180> UI<00:03:42.480> you<00:03:42.659> don't<00:03:42.780> you<00:03:43.019> need 00:03:43.190 --> 00:03:43.200 align:start position:0% nodes we provide a UI you don't you need 00:03:43.200 --> 00:03:45.589 align:start position:0% nodes we provide a UI you don't you need to<00:03:43.260> be<00:03:43.379> technical<00:03:43.739> there's<00:03:44.340> auto<00:03:44.580> updates<00:03:45.180> so 00:03:45.589 --> 00:03:45.599 align:start position:0% to be technical there's auto updates so 00:03:45.599 --> 00:03:47.570 align:start position:0% to be technical there's auto updates so you<00:03:45.780> don't<00:03:45.900> need<00:03:46.019> to<00:03:46.140> like<00:03:46.319> do<00:03:46.799> the<00:03:47.040> testing<00:03:47.340> we 00:03:47.570 --> 00:03:47.580 align:start position:0% you don't need to like do the testing we 00:03:47.580 --> 00:03:49.009 align:start position:0% you don't need to like do the testing we test<00:03:47.760> for<00:03:48.000> you<00:03:48.180> and<00:03:48.420> then<00:03:48.480> we<00:03:48.659> push<00:03:48.840> the 00:03:49.009 --> 00:03:49.019 align:start position:0% test for you and then we push the 00:03:49.019 --> 00:03:51.050 align:start position:0% test for you and then we push the updates<00:03:49.379> and<00:03:49.860> it<00:03:50.040> will<00:03:50.159> be<00:03:50.280> updated<00:03:50.640> this 00:03:51.050 --> 00:03:51.060 align:start position:0% updates and it will be updated this 00:03:51.060 --> 00:03:54.289 align:start position:0% updates and it will be updated this saves<00:03:51.599> about<00:03:51.959> 72<00:03:52.560> hours<00:03:52.799> of<00:03:53.220> devops<00:03:53.700> for<00:03:53.940> the 00:03:54.289 --> 00:03:54.299 align:start position:0% saves about 72 hours of devops for the 00:03:54.299 --> 00:03:56.990 align:start position:0% saves about 72 hours of devops for the of<00:03:54.420> those<00:03:54.780> work<00:03:55.019> per<00:03:55.440> year<00:03:55.680> only<00:03:56.220> on<00:03:56.519> gas<00:03:56.700> and 00:03:56.990 --> 00:03:57.000 align:start position:0% of those work per year only on gas and 00:03:57.000 --> 00:03:59.030 align:start position:0% of those work per year only on gas and prison<00:03:57.299> for<00:03:57.599> example 00:03:59.030 --> 00:03:59.040 align:start position:0% prison for example 00:03:59.040 --> 00:04:00.770 align:start position:0% prison for example um<00:03:59.099> then<00:03:59.760> there's<00:04:00.060> like<00:04:00.180> all<00:04:00.360> sorts<00:04:00.540> of<00:04:00.599> nice 00:04:00.770 --> 00:04:00.780 align:start position:0% um then there's like all sorts of nice 00:04:00.780 --> 00:04:02.210 align:start position:0% um then there's like all sorts of nice beautiful<00:04:01.019> things<00:04:01.319> like<00:04:01.440> a<00:04:01.560> web<00:04:01.680> 3<00:04:01.860> standard 00:04:02.210 --> 00:04:02.220 align:start position:0% beautiful things like a web 3 standard 00:04:02.220 --> 00:04:04.070 align:start position:0% beautiful things like a web 3 standard that<00:04:02.340> holds<00:04:02.519> the<00:04:02.580> keys<00:04:02.819> for<00:04:03.000> you<00:04:03.360> etc<00:04:03.659> etc<00:04:03.780> and 00:04:04.070 --> 00:04:04.080 align:start position:0% that holds the keys for you etc etc and 00:04:04.080 --> 00:04:06.470 align:start position:0% that holds the keys for you etc etc and there's<00:04:04.319> a<00:04:04.980> huge<00:04:05.220> community<00:04:05.400> of<00:04:05.879> thousands<00:04:06.360> of 00:04:06.470 --> 00:04:06.480 align:start position:0% there's a huge community of thousands of 00:04:06.480 --> 00:04:07.670 align:start position:0% there's a huge community of thousands of validators 00:04:07.670 --> 00:04:07.680 align:start position:0% validators 00:04:07.680 --> 00:04:09.289 align:start position:0% validators um<00:04:07.739> that<00:04:07.980> are<00:04:08.159> doing<00:04:08.340> exactly<00:04:08.760> the<00:04:08.940> exact<00:04:09.180> same 00:04:09.289 --> 00:04:09.299 align:start position:0% um that are doing exactly the exact same 00:04:09.299 --> 00:04:11.509 align:start position:0% um that are doing exactly the exact same thing<00:04:09.480> as<00:04:09.659> you<00:04:09.840> and<00:04:10.200> where<00:04:10.439> you<00:04:10.620> can<00:04:10.739> just<00:04:10.920> lay 00:04:11.509 --> 00:04:11.519 align:start position:0% thing as you and where you can just lay 00:04:11.519 --> 00:04:14.509 align:start position:0% thing as you and where you can just lay it<00:04:11.640> rely<00:04:11.939> on<00:04:12.120> them<00:04:12.299> ask<00:04:12.900> for<00:04:13.080> support<00:04:13.560> Etc<00:04:13.739> this 00:04:14.509 --> 00:04:14.519 align:start position:0% it rely on them ask for support Etc this 00:04:14.519 --> 00:04:16.550 align:start position:0% it rely on them ask for support Etc this is<00:04:14.640> one<00:04:14.760> of<00:04:14.879> the<00:04:14.939> things<00:04:15.060> that<00:04:15.239> we<00:04:15.360> have<00:04:15.480> done 00:04:16.550 --> 00:04:16.560 align:start position:0% is one of the things that we have done 00:04:16.560 --> 00:04:17.870 align:start position:0% is one of the things that we have done um<00:04:16.620> this<00:04:16.859> is<00:04:16.979> what<00:04:17.160> you<00:04:17.280> need<00:04:17.400> this<00:04:17.639> is<00:04:17.760> what 00:04:17.870 --> 00:04:17.880 align:start position:0% um this is what you need this is what 00:04:17.880 --> 00:04:20.210 align:start position:0% um this is what you need this is what you<00:04:18.060> see<00:04:18.180> this<00:04:18.419> is<00:04:18.540> the<00:04:18.600> UI<00:04:19.019> that<00:04:19.500> you<00:04:19.620> will<00:04:19.799> use 00:04:20.210 --> 00:04:20.220 align:start position:0% you see this is the UI that you will use 00:04:20.220 --> 00:04:22.370 align:start position:0% you see this is the UI that you will use in<00:04:20.519> order<00:04:20.639> to<00:04:20.940> set<00:04:21.180> up<00:04:21.299> a<00:04:21.479> validator<00:04:21.840> you<00:04:22.260> need 00:04:22.370 --> 00:04:22.380 align:start position:0% in order to set up a validator you need 00:04:22.380 --> 00:04:24.230 align:start position:0% in order to set up a validator you need to<00:04:22.440> choose<00:04:22.680> your<00:04:22.860> execution<00:04:23.280> client<00:04:23.639> choose 00:04:24.230 --> 00:04:24.240 align:start position:0% to choose your execution client choose 00:04:24.240 --> 00:04:26.990 align:start position:0% to choose your execution client choose your<00:04:24.360> consensus<00:04:24.900> client<00:04:25.259> put<00:04:26.160> the<00:04:26.400> keys<00:04:26.699> into 00:04:26.990 --> 00:04:27.000 align:start position:0% your consensus client put the keys into 00:04:27.000 --> 00:04:31.370 align:start position:0% your consensus client put the keys into the<00:04:27.240> remote<00:04:27.419> signer<00:04:28.259> or<00:04:29.100> use<00:04:29.820> optionally<00:04:30.540> Meb 00:04:31.370 --> 00:04:31.380 align:start position:0% the remote signer or use optionally Meb 00:04:31.380 --> 00:04:32.629 align:start position:0% the remote signer or use optionally Meb boost 00:04:32.629 --> 00:04:32.639 align:start position:0% boost 00:04:32.639 --> 00:04:35.930 align:start position:0% boost okay<00:04:33.180> enough 00:04:35.930 --> 00:04:35.940 align:start position:0% 00:04:35.940 --> 00:04:37.790 align:start position:0% the<00:04:36.479> thing<00:04:36.540> that<00:04:36.660> the<00:04:36.840> solo<00:04:37.139> Staker<00:04:37.500> needs<00:04:37.740> to 00:04:37.790 --> 00:04:37.800 align:start position:0% the thing that the solo Staker needs to 00:04:37.800 --> 00:04:39.830 align:start position:0% the thing that the solo Staker needs to know<00:04:38.280> is<00:04:38.759> that<00:04:38.940> you<00:04:39.120> are<00:04:39.300> the<00:04:39.419> key<00:04:39.540> for<00:04:39.720> the 00:04:39.830 --> 00:04:39.840 align:start position:0% know is that you are the key for the 00:04:39.840 --> 00:04:42.350 align:start position:0% know is that you are the key for the future<00:04:39.960> of<00:04:40.199> ethereum 00:04:42.350 --> 00:04:42.360 align:start position:0% future of ethereum 00:04:42.360 --> 00:04:45.890 align:start position:0% future of ethereum right<00:04:42.900> mov 00:04:45.890 --> 00:04:45.900 align:start position:0% 00:04:45.900 --> 00:04:49.189 align:start position:0% ing uh<00:04:46.500> okay<00:04:46.680> so<00:04:46.860> Mev<00:04:47.340> MV<00:04:48.180> stands<00:04:48.660> for<00:04:48.720> maximal 00:04:49.189 --> 00:04:49.199 align:start position:0% ing uh okay so Mev MV stands for maximal 00:04:49.199 --> 00:04:51.290 align:start position:0% ing uh okay so Mev MV stands for maximal extractable<00:04:49.800> value<00:04:50.280> and<00:04:50.940> the<00:04:51.120> first<00:04:51.240> thing 00:04:51.290 --> 00:04:51.300 align:start position:0% extractable value and the first thing 00:04:51.300 --> 00:04:52.430 align:start position:0% extractable value and the first thing that<00:04:51.419> we<00:04:51.540> need<00:04:51.660> to<00:04:51.780> know<00:04:51.900> here<00:04:52.020> is<00:04:52.139> that<00:04:52.259> the 00:04:52.430 --> 00:04:52.440 align:start position:0% that we need to know here is that the 00:04:52.440 --> 00:04:54.590 align:start position:0% that we need to know here is that the value<00:04:52.560> is<00:04:52.860> extracted<00:04:53.280> from<00:04:53.520> who<00:04:53.759> from<00:04:54.360> the 00:04:54.590 --> 00:04:54.600 align:start position:0% value is extracted from who from the 00:04:54.600 --> 00:04:57.290 align:start position:0% value is extracted from who from the user<00:04:54.900> and<00:04:55.199> people<00:04:55.440> say<00:04:55.620> like<00:04:55.800> oh<00:04:56.040> Mev<00:04:57.060> um<00:04:57.120> but 00:04:57.290 --> 00:04:57.300 align:start position:0% user and people say like oh Mev um but 00:04:57.300 --> 00:04:58.249 align:start position:0% user and people say like oh Mev um but they're<00:04:57.419> doing<00:04:57.600> nice<00:04:57.780> things<00:04:57.960> they<00:04:58.139> do 00:04:58.249 --> 00:04:58.259 align:start position:0% they're doing nice things they do 00:04:58.259 --> 00:05:00.590 align:start position:0% they're doing nice things they do Arbitrage<00:04:58.800> between<00:04:59.040> dexes<00:04:59.580> so<00:04:59.940> we<00:05:00.180> can<00:05:00.360> like 00:05:00.590 --> 00:05:00.600 align:start position:0% Arbitrage between dexes so we can like 00:05:00.600 --> 00:05:02.990 align:start position:0% Arbitrage between dexes so we can like if<00:05:01.020> I<00:05:01.199> have<00:05:01.440> a<00:05:01.620> token<00:05:01.979> my<00:05:02.340> price<00:05:02.460> will<00:05:02.699> be<00:05:02.880> the 00:05:02.990 --> 00:05:03.000 align:start position:0% if I have a token my price will be the 00:05:03.000 --> 00:05:04.370 align:start position:0% if I have a token my price will be the same<00:05:03.120> everywhere<00:05:03.540> yeah<00:05:03.720> that's<00:05:03.900> a<00:05:04.080> good<00:05:04.199> thing 00:05:04.370 --> 00:05:04.380 align:start position:0% same everywhere yeah that's a good thing 00:05:04.380 --> 00:05:06.530 align:start position:0% same everywhere yeah that's a good thing right<00:05:04.680> but<00:05:05.340> how<00:05:05.820> about<00:05:06.000> everything<00:05:06.300> else 00:05:06.530 --> 00:05:06.540 align:start position:0% right but how about everything else 00:05:06.540 --> 00:05:08.570 align:start position:0% right but how about everything else you've<00:05:07.080> got<00:05:07.139> price<00:05:07.500> execution<00:05:08.100> in<00:05:08.460> every 00:05:08.570 --> 00:05:08.580 align:start position:0% you've got price execution in every 00:05:08.580 --> 00:05:11.210 align:start position:0% you've got price execution in every trade<00:05:08.940> that<00:05:09.060> you<00:05:09.240> do<00:05:09.360> in<00:05:09.479> a<00:05:09.600> decks<00:05:10.020> you<00:05:10.620> got<00:05:10.800> gas 00:05:11.210 --> 00:05:11.220 align:start position:0% trade that you do in a decks you got gas 00:05:11.220 --> 00:05:12.830 align:start position:0% trade that you do in a decks you got gas Wars<00:05:11.639> and<00:05:11.759> network<00:05:11.940> congestion<00:05:12.419> whenever 00:05:12.830 --> 00:05:12.840 align:start position:0% Wars and network congestion whenever 00:05:12.840 --> 00:05:15.890 align:start position:0% Wars and network congestion whenever there's<00:05:13.080> like<00:05:13.259> a<00:05:13.500> juicy<00:05:14.160> Mev<00:05:14.880> opportunity<00:05:15.360> you 00:05:15.890 --> 00:05:15.900 align:start position:0% there's like a juicy Mev opportunity you 00:05:15.900 --> 00:05:17.629 align:start position:0% there's like a juicy Mev opportunity you get<00:05:16.020> the<00:05:16.440> potential<00:05:16.860> and<00:05:17.040> the<00:05:17.220> threat<00:05:17.460> of 00:05:17.629 --> 00:05:17.639 align:start position:0% get the potential and the threat of 00:05:17.639 --> 00:05:19.550 align:start position:0% get the potential and the threat of chain<00:05:17.820> reorgs<00:05:18.540> if<00:05:18.720> there's<00:05:18.900> something<00:05:19.139> really 00:05:19.550 --> 00:05:19.560 align:start position:0% chain reorgs if there's something really 00:05:19.560 --> 00:05:21.830 align:start position:0% chain reorgs if there's something really juicy<00:05:20.040> and<00:05:20.340> the<00:05:20.520> conditions<00:05:20.880> are<00:05:21.060> right<00:05:21.240> and 00:05:21.830 --> 00:05:21.840 align:start position:0% juicy and the conditions are right and 00:05:21.840 --> 00:05:24.110 align:start position:0% juicy and the conditions are right and the<00:05:22.020> validators<00:05:22.560> are<00:05:22.919> incentivized<00:05:23.759> to 00:05:24.110 --> 00:05:24.120 align:start position:0% the validators are incentivized to 00:05:24.120 --> 00:05:28.010 align:start position:0% the validators are incentivized to attack<00:05:24.240> themselves<00:05:24.900> so<00:05:25.620> if<00:05:25.860> I<00:05:26.100> come<00:05:26.340> after<00:05:27.020> uh 00:05:28.010 --> 00:05:28.020 align:start position:0% attack themselves so if I come after uh 00:05:28.020 --> 00:05:30.110 align:start position:0% attack themselves so if I come after uh the<00:05:28.620> a<00:05:28.800> block<00:05:28.979> where<00:05:29.340> there's<00:05:29.520> a<00:05:29.699> really<00:05:29.820> juicy 00:05:30.110 --> 00:05:30.120 align:start position:0% the a block where there's a really juicy 00:05:30.120 --> 00:05:32.450 align:start position:0% the a block where there's a really juicy Mev<00:05:30.600> opportunity<00:05:31.020> I<00:05:31.440> mean<00:05:31.560> send<00:05:31.800> device<00:05:32.039> to 00:05:32.450 --> 00:05:32.460 align:start position:0% Mev opportunity I mean send device to 00:05:32.460 --> 00:05:34.490 align:start position:0% Mev opportunity I mean send device to screw<00:05:32.820> up<00:05:32.940> the<00:05:33.120> guy<00:05:33.240> that<00:05:33.419> comes<00:05:33.660> before<00:05:33.780> me<00:05:34.020> so 00:05:34.490 --> 00:05:34.500 align:start position:0% screw up the guy that comes before me so 00:05:34.500 --> 00:05:38.330 align:start position:0% screw up the guy that comes before me so I<00:05:34.800> can<00:05:34.919> keep<00:05:35.160> the<00:05:35.520> Mev<00:05:35.940> opportunity<00:05:36.419> right 00:05:38.330 --> 00:05:38.340 align:start position:0% I can keep the Mev opportunity right 00:05:38.340 --> 00:05:41.810 align:start position:0% I can keep the Mev opportunity right okay<00:05:38.940> so<00:05:39.720> yes<00:05:40.080> uh<00:05:40.560> how<00:05:40.680> to<00:05:40.860> map<00:05:41.100> all<00:05:41.400> of<00:05:41.580> these 00:05:41.810 --> 00:05:41.820 align:start position:0% okay so yes uh how to map all of these 00:05:41.820 --> 00:05:44.749 align:start position:0% okay so yes uh how to map all of these related<00:05:42.180> to<00:05:42.300> me<00:05:42.479> beef<00:05:42.780> so<00:05:43.380> mainly<00:05:43.860> for<00:05:44.100> me<00:05:44.280> and 00:05:44.749 --> 00:05:44.759 align:start position:0% related to me beef so mainly for me and 00:05:44.759 --> 00:05:47.029 align:start position:0% related to me beef so mainly for me and for<00:05:45.000> most<00:05:45.180> of<00:05:45.300> us<00:05:45.479> maybe<00:05:46.020> it's<00:05:46.320> not<00:05:46.620> a<00:05:46.800> feature 00:05:47.029 --> 00:05:47.039 align:start position:0% for most of us maybe it's not a feature 00:05:47.039 --> 00:05:48.350 align:start position:0% for most of us maybe it's not a feature it's<00:05:47.160> a<00:05:47.400> bug 00:05:48.350 --> 00:05:48.360 align:start position:0% it's a bug 00:05:48.360 --> 00:05:50.870 align:start position:0% it's a bug it<00:05:48.900> has<00:05:49.080> a<00:05:49.259> lot<00:05:49.320> of<00:05:49.440> implications<00:05:49.979> on<00:05:50.639> the 00:05:50.870 --> 00:05:50.880 align:start position:0% it has a lot of implications on the 00:05:50.880 --> 00:05:52.490 align:start position:0% it has a lot of implications on the ethereum<00:05:51.360> design<00:05:51.479> because<00:05:51.840> of<00:05:52.080> that<00:05:52.259> because 00:05:52.490 --> 00:05:52.500 align:start position:0% ethereum design because of that because 00:05:52.500 --> 00:05:56.090 align:start position:0% ethereum design because of that because it's<00:05:53.160> something<00:05:53.400> that<00:05:53.880> is<00:05:54.120> leading<00:05:55.080> in<00:05:55.560> a<00:05:55.740> in 00:05:56.090 --> 00:05:56.100 align:start position:0% it's something that is leading in a in 00:05:56.100 --> 00:05:57.590 align:start position:0% it's something that is leading in a in the<00:05:56.220> wrong<00:05:56.400> direction 00:05:57.590 --> 00:05:57.600 align:start position:0% the wrong direction 00:05:57.600 --> 00:06:00.110 align:start position:0% the wrong direction so<00:05:58.080> mainly<00:05:58.440> PBS<00:05:58.919> has<00:05:59.220> formed<00:05:59.699> to<00:05:59.880> try<00:06:00.000> to 00:06:00.110 --> 00:06:00.120 align:start position:0% so mainly PBS has formed to try to 00:06:00.120 --> 00:06:02.749 align:start position:0% so mainly PBS has formed to try to mitigate<00:06:00.840> this<00:06:01.080> situation<00:06:01.440> PBS<00:06:02.160> proposal 00:06:02.749 --> 00:06:02.759 align:start position:0% mitigate this situation PBS proposal 00:06:02.759 --> 00:06:04.670 align:start position:0% mitigate this situation PBS proposal block<00:06:02.940> separation<00:06:03.479> and<00:06:04.199> we<00:06:04.380> are<00:06:04.500> going<00:06:04.620> to 00:06:04.670 --> 00:06:04.680 align:start position:0% block separation and we are going to 00:06:04.680 --> 00:06:06.830 align:start position:0% block separation and we are going to talk<00:06:04.860> about<00:06:05.039> that<00:06:05.400> later<00:06:06.000> on 00:06:06.830 --> 00:06:06.840 align:start position:0% talk about that later on 00:06:06.840 --> 00:06:09.409 align:start position:0% talk about that later on uh<00:06:07.560> so<00:06:07.740> that<00:06:07.979> is<00:06:08.160> why<00:06:08.520> the<00:06:08.699> concept<00:06:09.060> of<00:06:09.240> the 00:06:09.409 --> 00:06:09.419 align:start position:0% uh so that is why the concept of the 00:06:09.419 --> 00:06:11.689 align:start position:0% uh so that is why the concept of the community<00:06:09.660> and<00:06:10.259> the<00:06:10.440> refer<00:06:10.740> to<00:06:10.860> try<00:06:11.580> to 00:06:11.689 --> 00:06:11.699 align:start position:0% community and the refer to try to 00:06:11.699 --> 00:06:14.170 align:start position:0% community and the refer to try to mitigate<00:06:12.060> as<00:06:12.360> much<00:06:12.479> as<00:06:12.660> we<00:06:12.780> can<00:06:12.960> they<00:06:13.199> may<00:06:13.440> be 00:06:14.170 --> 00:06:14.180 align:start position:0% mitigate as much as we can they may be 00:06:14.180 --> 00:06:16.909 align:start position:0% mitigate as much as we can they may be and<00:06:15.180> that<00:06:15.419> is<00:06:15.539> why<00:06:15.780> we<00:06:16.020> are<00:06:16.199> starting<00:06:16.380> to<00:06:16.620> see 00:06:16.909 --> 00:06:16.919 align:start position:0% and that is why we are starting to see 00:06:16.919 --> 00:06:19.670 align:start position:0% and that is why we are starting to see new<00:06:17.580> uh<00:06:18.240> proposals<00:06:18.900> like<00:06:19.020> single<00:06:19.380> slot 00:06:19.670 --> 00:06:19.680 align:start position:0% new uh proposals like single slot 00:06:19.680 --> 00:06:23.090 align:start position:0% new uh proposals like single slot finality<00:06:20.120> uh<00:06:21.120> single<00:06:21.479> slot<00:06:21.780> finality<00:06:22.259> is<00:06:22.860> a 00:06:23.090 --> 00:06:23.100 align:start position:0% finality uh single slot finality is a 00:06:23.100 --> 00:06:25.370 align:start position:0% finality uh single slot finality is a proposal<00:06:23.520> to<00:06:23.819> be<00:06:23.940> able<00:06:24.060> to<00:06:24.240> have<00:06:24.479> finality<00:06:24.960> in 00:06:25.370 --> 00:06:25.380 align:start position:0% proposal to be able to have finality in 00:06:25.380 --> 00:06:30.529 align:start position:0% proposal to be able to have finality in just<00:06:25.500> one<00:06:25.919> uh<00:06:26.400> Epoch<00:06:27.380> and<00:06:28.380> the<00:06:28.620> idea<00:06:28.800> is<00:06:29.460> to<00:06:29.819> to 00:06:30.529 --> 00:06:30.539 align:start position:0% just one uh Epoch and the idea is to to 00:06:30.539 --> 00:06:32.689 align:start position:0% just one uh Epoch and the idea is to to remove<00:06:30.780> these<00:06:31.199> opportunities<00:06:31.680> from<00:06:32.160> from<00:06:32.460> the 00:06:32.689 --> 00:06:32.699 align:start position:0% remove these opportunities from from the 00:06:32.699 --> 00:06:34.969 align:start position:0% remove these opportunities from from the protocol<00:06:33.120> itself<00:06:33.600> but<00:06:34.199> also<00:06:34.440> the<00:06:34.680> single 00:06:34.969 --> 00:06:34.979 align:start position:0% protocol itself but also the single 00:06:34.979 --> 00:06:37.430 align:start position:0% protocol itself but also the single secretary<00:06:35.580> leader<00:06:36.180> election<00:06:36.660> that<00:06:37.380> is 00:06:37.430 --> 00:06:37.440 align:start position:0% secretary leader election that is 00:06:37.440 --> 00:06:39.830 align:start position:0% secretary leader election that is related<00:06:37.740> to<00:06:37.860> the<00:06:37.979> validator<00:06:38.639> anonymity<00:06:39.180> is 00:06:39.830 --> 00:06:39.840 align:start position:0% related to the validator anonymity is 00:06:39.840 --> 00:06:42.230 align:start position:0% related to the validator anonymity is something<00:06:40.020> that<00:06:40.440> is<00:06:40.680> also<00:06:41.280> resetting<00:06:42.120> right 00:06:42.230 --> 00:06:42.240 align:start position:0% something that is also resetting right 00:06:42.240 --> 00:06:43.909 align:start position:0% something that is also resetting right now<00:06:42.360> and<00:06:42.539> we<00:06:42.780> are<00:06:42.900> talking<00:06:43.080> later<00:06:43.319> on<00:06:43.560> so 00:06:43.909 --> 00:06:43.919 align:start position:0% now and we are talking later on so 00:06:43.919 --> 00:06:46.010 align:start position:0% now and we are talking later on so mainly<00:06:44.220> we<00:06:44.699> are<00:06:44.880> seeing<00:06:45.120> how<00:06:45.419> the<00:06:45.660> Syrian 00:06:46.010 --> 00:06:46.020 align:start position:0% mainly we are seeing how the Syrian 00:06:46.020 --> 00:06:49.249 align:start position:0% mainly we are seeing how the Syrian Foundation<00:06:46.380> is<00:06:46.979> trying<00:06:47.160> to<00:06:47.400> find<00:06:47.780> uh<00:06:48.780> ways<00:06:49.199> to 00:06:49.249 --> 00:06:49.259 align:start position:0% Foundation is trying to find uh ways to 00:06:49.259 --> 00:06:51.110 align:start position:0% Foundation is trying to find uh ways to mitigate<00:06:49.620> this<00:06:49.800> situation<00:06:50.160> at<00:06:50.580> a<00:06:50.759> protocol 00:06:51.110 --> 00:06:51.120 align:start position:0% mitigate this situation at a protocol 00:06:51.120 --> 00:06:53.029 align:start position:0% mitigate this situation at a protocol level<00:06:51.419> but<00:06:52.080> there<00:06:52.319> are<00:06:52.500> something<00:06:52.620> that<00:06:52.919> we 00:06:53.029 --> 00:06:53.039 align:start position:0% level but there are something that we 00:06:53.039 --> 00:06:55.430 align:start position:0% level but there are something that we cannot<00:06:53.340> mitigate<00:06:53.699> so<00:06:54.000> far<00:06:54.180> we<00:06:54.780> have<00:06:54.960> seen<00:06:55.199> that 00:06:55.430 --> 00:06:55.440 align:start position:0% cannot mitigate so far we have seen that 00:06:55.440 --> 00:06:57.290 align:start position:0% cannot mitigate so far we have seen that is<00:06:55.680> really<00:06:56.039> really<00:06:56.220> hard<00:06:56.520> to<00:06:56.759> find<00:06:56.880> a<00:06:57.060> solution 00:06:57.290 --> 00:06:57.300 align:start position:0% is really really hard to find a solution 00:06:57.300 --> 00:07:00.770 align:start position:0% is really really hard to find a solution to<00:06:57.479> Meb<00:06:57.960> so<00:06:58.500> that<00:06:58.680> is<00:06:58.800> why<00:06:59.039> the<00:06:59.639> PBS<00:07:00.120> or<00:07:00.419> maybe 00:07:00.770 --> 00:07:00.780 align:start position:0% to Meb so that is why the PBS or maybe 00:07:00.780 --> 00:07:04.249 align:start position:0% to Meb so that is why the PBS or maybe smoothing<00:07:01.500> is<00:07:01.860> a<00:07:02.160> way<00:07:02.400> to<00:07:02.580> make<00:07:03.120> this<00:07:03.419> uh<00:07:04.020> more 00:07:04.249 --> 00:07:04.259 align:start position:0% smoothing is a way to make this uh more 00:07:04.259 --> 00:07:07.850 align:start position:0% smoothing is a way to make this uh more fair<00:07:04.560> and<00:07:05.280> try<00:07:05.520> to<00:07:05.699> mitigate<00:07:06.060> the<00:07:06.180> situations 00:07:07.850 --> 00:07:07.860 align:start position:0% fair and try to mitigate the situations 00:07:07.860 --> 00:07:10.309 align:start position:0% fair and try to mitigate the situations right<00:07:08.400> so<00:07:08.699> what<00:07:08.940> do<00:07:09.120> you<00:07:09.240> need<00:07:09.360> to<00:07:09.539> know 00:07:10.309 --> 00:07:10.319 align:start position:0% right so what do you need to know 00:07:10.319 --> 00:07:12.230 align:start position:0% right so what do you need to know for<00:07:10.800> Emily 00:07:12.230 --> 00:07:12.240 align:start position:0% for Emily 00:07:12.240 --> 00:07:15.529 align:start position:0% for Emily so<00:07:12.720> so<00:07:12.979> yeah<00:07:13.979> so<00:07:14.160> I<00:07:14.280> mean<00:07:14.520> maybe<00:07:15.000> is<00:07:15.360> a 00:07:15.529 --> 00:07:15.539 align:start position:0% so so yeah so I mean maybe is a 00:07:15.539 --> 00:07:17.330 align:start position:0% so so yeah so I mean maybe is a centralizing<00:07:16.020> force<00:07:16.380> it's<00:07:16.680> a<00:07:16.860> centralizing 00:07:17.330 --> 00:07:17.340 align:start position:0% centralizing force it's a centralizing 00:07:17.340 --> 00:07:18.409 align:start position:0% centralizing force it's a centralizing force 00:07:18.409 --> 00:07:18.419 align:start position:0% force 00:07:18.419 --> 00:07:21.110 align:start position:0% force um<00:07:18.539> because<00:07:18.960> I<00:07:19.620> mean<00:07:19.800> researchers<00:07:20.699> will<00:07:20.940> not 00:07:21.110 --> 00:07:21.120 align:start position:0% um because I mean researchers will not 00:07:21.120 --> 00:07:23.990 align:start position:0% um because I mean researchers will not give<00:07:21.360> you<00:07:21.539> as<00:07:21.840> a<00:07:21.960> solo<00:07:22.259> Staker<00:07:22.620> a<00:07:23.340> juicy<00:07:23.759> 10 00:07:23.990 --> 00:07:24.000 align:start position:0% give you as a solo Staker a juicy 10 00:07:24.000 --> 00:07:26.450 align:start position:0% give you as a solo Staker a juicy 10 million<00:07:24.419> Mev<00:07:24.900> opportunity<00:07:25.440> because<00:07:25.860> you<00:07:26.160> as<00:07:26.340> a 00:07:26.450 --> 00:07:26.460 align:start position:0% million Mev opportunity because you as a 00:07:26.460 --> 00:07:28.850 align:start position:0% million Mev opportunity because you as a solo<00:07:26.759> sticker<00:07:27.060> that<00:07:27.240> has<00:07:27.360> only<00:07:27.599> 42 00:07:28.850 --> 00:07:28.860 align:start position:0% solo sticker that has only 42 00:07:28.860 --> 00:07:31.969 align:start position:0% solo sticker that has only 42 000<00:07:28.979> uh<00:07:29.220> 32<00:07:29.639> each<00:07:29.819> in<00:07:30.419> this<00:07:30.660> uh<00:07:31.319> in<00:07:31.919> your 00:07:31.969 --> 00:07:31.979 align:start position:0% 000 uh 32 each in this uh in your 00:07:31.979 --> 00:07:33.830 align:start position:0% 000 uh 32 each in this uh in your validator<00:07:32.400> you<00:07:32.819> would<00:07:32.940> be<00:07:33.120> you<00:07:33.539> would<00:07:33.720> be 00:07:33.830 --> 00:07:33.840 align:start position:0% validator you would be you would be 00:07:33.840 --> 00:07:35.450 align:start position:0% validator you would be you would be happy<00:07:34.020> to<00:07:34.259> take<00:07:34.380> this<00:07:34.620> 10<00:07:34.740> million<00:07:35.039> shut<00:07:35.280> down 00:07:35.450 --> 00:07:35.460 align:start position:0% happy to take this 10 million shut down 00:07:35.460 --> 00:07:36.950 align:start position:0% happy to take this 10 million shut down your<00:07:35.580> validator<00:07:36.000> and<00:07:36.419> go<00:07:36.479> live<00:07:36.720> in<00:07:36.840> the 00:07:36.950 --> 00:07:36.960 align:start position:0% your validator and go live in the 00:07:36.960 --> 00:07:39.409 align:start position:0% your validator and go live in the Bahamas<00:07:37.259> for<00:07:37.440> the<00:07:37.560> rest<00:07:37.620> of<00:07:37.740> your<00:07:37.860> life<00:07:38.039> so<00:07:38.940> it 00:07:39.409 --> 00:07:39.419 align:start position:0% Bahamas for the rest of your life so it 00:07:39.419 --> 00:07:41.749 align:start position:0% Bahamas for the rest of your life so it is<00:07:39.539> a<00:07:39.720> trustful<00:07:40.080> system<00:07:40.500> and<00:07:41.220> as<00:07:41.340> a<00:07:41.460> solo 00:07:41.749 --> 00:07:41.759 align:start position:0% is a trustful system and as a solo 00:07:41.759 --> 00:07:43.189 align:start position:0% is a trustful system and as a solo sticker<00:07:42.060> you<00:07:42.300> cannot<00:07:42.479> access<00:07:42.660> Mev 00:07:43.189 --> 00:07:43.199 align:start position:0% sticker you cannot access Mev 00:07:43.199 --> 00:07:45.770 align:start position:0% sticker you cannot access Mev opportunities<00:07:43.620> if<00:07:43.919> you<00:07:44.160> don't<00:07:44.340> use<00:07:44.699> Mev<00:07:45.479> boost 00:07:45.770 --> 00:07:45.780 align:start position:0% opportunities if you don't use Mev boost 00:07:45.780 --> 00:07:47.270 align:start position:0% opportunities if you don't use Mev boost right<00:07:46.380> now 00:07:47.270 --> 00:07:47.280 align:start position:0% right now 00:07:47.280 --> 00:07:49.969 align:start position:0% right now in<00:07:47.880> the<00:07:48.000> future<00:07:48.199> PBS<00:07:49.199> provides<00:07:49.680> the<00:07:49.860> same 00:07:49.969 --> 00:07:49.979 align:start position:0% in the future PBS provides the same 00:07:49.979 --> 00:07:52.070 align:start position:0% in the future PBS provides the same separation<00:07:50.340> of<00:07:50.580> powers<00:07:50.759> and<00:07:51.599> allows<00:07:51.960> for 00:07:52.070 --> 00:07:52.080 align:start position:0% separation of powers and allows for 00:07:52.080 --> 00:07:54.710 align:start position:0% separation of powers and allows for easier<00:07:52.560> Builder<00:07:53.419> decentralization<00:07:54.419> and 00:07:54.710 --> 00:07:54.720 align:start position:0% easier Builder decentralization and 00:07:54.720 --> 00:07:57.050 align:start position:0% easier Builder decentralization and removes<00:07:55.020> the<00:07:55.199> need<00:07:55.319> to<00:07:55.740> trust<00:07:56.039> the<00:07:56.880> the 00:07:57.050 --> 00:07:57.060 align:start position:0% removes the need to trust the the 00:07:57.060 --> 00:07:59.870 align:start position:0% removes the need to trust the the builder<00:07:57.479> of<00:07:57.660> the<00:07:57.780> block<00:07:57.900> but<00:07:58.440> right<00:07:58.620> now<00:07:58.880> Mev 00:07:59.870 --> 00:07:59.880 align:start position:0% builder of the block but right now Mev 00:07:59.880 --> 00:08:03.409 align:start position:0% builder of the block but right now Mev is<00:08:00.300> a<00:08:00.780> huge<00:08:01.380> centralizing<00:08:02.039> Force 00:08:03.409 --> 00:08:03.419 align:start position:0% is a huge centralizing Force 00:08:03.419 --> 00:08:06.409 align:start position:0% is a huge centralizing Force um<00:08:03.539> that<00:08:04.440> uh<00:08:05.160> but<00:08:05.460> yeah<00:08:05.639> that's<00:08:06.060> that 00:08:06.409 --> 00:08:06.419 align:start position:0% um that uh but yeah that's that 00:08:06.419 --> 00:08:07.610 align:start position:0% um that uh but yeah that's that basically 00:08:07.610 --> 00:08:07.620 align:start position:0% basically 00:08:07.620 --> 00:08:11.029 align:start position:0% basically um<00:08:07.680> uh<00:08:08.580> makes<00:08:09.180> that<00:08:09.479> us<00:08:09.960> as<00:08:10.259> solo<00:08:10.620> stickers 00:08:11.029 --> 00:08:11.039 align:start position:0% um uh makes that us as solo stickers 00:08:11.039 --> 00:08:13.670 align:start position:0% um uh makes that us as solo stickers will<00:08:11.580> only<00:08:11.819> have 00:08:13.670 --> 00:08:13.680 align:start position:0% will only have 00:08:13.680 --> 00:08:15.589 align:start position:0% will only have um<00:08:13.800> two<00:08:14.039> sources<00:08:14.340> of<00:08:14.460> revenue<00:08:14.699> which<00:08:15.300> are 00:08:15.589 --> 00:08:15.599 align:start position:0% um two sources of revenue which are 00:08:15.599 --> 00:08:17.870 align:start position:0% um two sources of revenue which are block<00:08:16.139> production<00:08:16.620> so<00:08:16.919> block<00:08:17.160> reward<00:08:17.580> and 00:08:17.870 --> 00:08:17.880 align:start position:0% block production so block reward and 00:08:17.880 --> 00:08:20.869 align:start position:0% block production so block reward and transaction<00:08:18.300> fees<00:08:18.720> and<00:08:19.560> the<00:08:20.039> big<00:08:20.280> companies 00:08:20.869 --> 00:08:20.879 align:start position:0% transaction fees and the big companies 00:08:20.879 --> 00:08:22.490 align:start position:0% transaction fees and the big companies the<00:08:21.120> big<00:08:21.240> trusted<00:08:21.599> companies<00:08:21.960> that<00:08:22.139> can<00:08:22.319> sign 00:08:22.490 --> 00:08:22.500 align:start position:0% the big trusted companies that can sign 00:08:22.500 --> 00:08:25.490 align:start position:0% the big trusted companies that can sign agreements<00:08:23.160> would<00:08:23.460> have<00:08:23.699> those<00:08:24.479> two<00:08:24.720> plus<00:08:25.080> MAV 00:08:25.490 --> 00:08:25.500 align:start position:0% agreements would have those two plus MAV 00:08:25.500 --> 00:08:29.330 align:start position:0% agreements would have those two plus MAV opportunities<00:08:26.039> so<00:08:26.340> Mev<00:08:27.060> boost<00:08:27.240> is<00:08:27.960> for<00:08:28.620> now<00:08:28.860> as 00:08:29.330 --> 00:08:29.340 align:start position:0% opportunities so Mev boost is for now as 00:08:29.340 --> 00:08:31.010 align:start position:0% opportunities so Mev boost is for now as solo<00:08:29.699> stickers<00:08:30.000> the<00:08:30.240> only<00:08:30.360> solution<00:08:30.660> that<00:08:30.900> we 00:08:31.010 --> 00:08:31.020 align:start position:0% solo stickers the only solution that we 00:08:31.020 --> 00:08:33.649 align:start position:0% solo stickers the only solution that we have<00:08:31.199> to<00:08:31.440> access<00:08:31.740> this 00:08:33.649 --> 00:08:33.659 align:start position:0% have to access this 00:08:33.659 --> 00:08:36.469 align:start position:0% have to access this um<00:08:33.719> this<00:08:34.500> Revenue<00:08:34.800> yeah<00:08:35.580> and<00:08:35.880> mainly<00:08:36.419> the 00:08:36.469 --> 00:08:36.479 align:start position:0% um this Revenue yeah and mainly the 00:08:36.479 --> 00:08:38.329 align:start position:0% um this Revenue yeah and mainly the feeling<00:08:36.659> that<00:08:36.959> we<00:08:37.140> are<00:08:37.260> having<00:08:37.500> with<00:08:37.800> semi<00:08:38.159> B 00:08:38.329 --> 00:08:38.339 align:start position:0% feeling that we are having with semi B 00:08:38.339 --> 00:08:39.949 align:start position:0% feeling that we are having with semi B is<00:08:38.459> that<00:08:38.640> we<00:08:38.700> are<00:08:38.820> putting<00:08:39.180> the<00:08:39.360> incentivation 00:08:39.949 --> 00:08:39.959 align:start position:0% is that we are putting the incentivation 00:08:39.959 --> 00:08:42.230 align:start position:0% is that we are putting the incentivation in<00:08:40.440> the<00:08:40.560> ground<00:08:40.740> place<00:08:41.099> we<00:08:41.580> are<00:08:41.760> intimidating 00:08:42.230 --> 00:08:42.240 align:start position:0% in the ground place we are intimidating 00:08:42.240 --> 00:08:44.810 align:start position:0% in the ground place we are intimidating people<00:08:43.140> to<00:08:43.500> extract<00:08:43.800> this<00:08:44.039> value<00:08:44.159> from<00:08:44.399> users 00:08:44.810 --> 00:08:44.820 align:start position:0% people to extract this value from users 00:08:44.820 --> 00:08:46.850 align:start position:0% people to extract this value from users so<00:08:45.480> that<00:08:45.660> is<00:08:45.779> why<00:08:45.899> we<00:08:46.080> should<00:08:46.200> try<00:08:46.380> to<00:08:46.500> find<00:08:46.680> a 00:08:46.850 --> 00:08:46.860 align:start position:0% so that is why we should try to find a 00:08:46.860 --> 00:08:50.269 align:start position:0% so that is why we should try to find a way<00:08:46.980> to<00:08:47.279> remove<00:08:47.580> these<00:08:47.940> from<00:08:48.060> the<00:08:48.180> protocol 00:08:50.269 --> 00:08:50.279 align:start position:0% way to remove these from the protocol 00:08:50.279 --> 00:08:53.329 align:start position:0% way to remove these from the protocol okay<00:08:50.940> DVT 00:08:53.329 --> 00:08:53.339 align:start position:0% okay DVT 00:08:53.339 --> 00:08:55.610 align:start position:0% okay DVT DVT<00:08:54.060> is<00:08:54.240> the<00:08:54.420> next<00:08:54.540> Hot<00:08:54.839> Topic<00:08:55.200> and<00:08:55.440> it's 00:08:55.610 --> 00:08:55.620 align:start position:0% DVT is the next Hot Topic and it's 00:08:55.620 --> 00:08:57.590 align:start position:0% DVT is the next Hot Topic and it's distributed<00:08:56.100> validators<00:08:56.700> so<00:08:57.240> right<00:08:57.420> now 00:08:57.590 --> 00:08:57.600 align:start position:0% distributed validators so right now 00:08:57.600 --> 00:09:00.350 align:start position:0% distributed validators so right now there's<00:08:58.320> uh<00:08:58.920> there's<00:08:59.160> this<00:08:59.339> equality<00:08:59.760> of<00:09:00.060> uh 00:09:00.350 --> 00:09:00.360 align:start position:0% there's uh there's this equality of uh 00:09:00.360 --> 00:09:03.650 align:start position:0% there's uh there's this equality of uh one<00:09:01.080> validator<00:09:01.560> key<00:09:01.860> one<00:09:02.640> validator<00:09:03.120> client 00:09:03.650 --> 00:09:03.660 align:start position:0% one validator key one validator client 00:09:03.660 --> 00:09:07.009 align:start position:0% one validator key one validator client which<00:09:04.200> basically<00:09:04.620> means<00:09:05.220> that<00:09:05.760> whoever<00:09:06.540> runs 00:09:07.009 --> 00:09:07.019 align:start position:0% which basically means that whoever runs 00:09:07.019 --> 00:09:08.509 align:start position:0% which basically means that whoever runs the<00:09:07.140> machine<00:09:07.320> whoever<00:09:07.740> runs<00:09:08.040> the<00:09:08.100> validator 00:09:08.509 --> 00:09:08.519 align:start position:0% the machine whoever runs the validator 00:09:08.519 --> 00:09:11.090 align:start position:0% the machine whoever runs the validator client<00:09:08.880> also<00:09:09.360> has<00:09:09.480> access<00:09:09.720> to<00:09:10.320> that<00:09:10.500> key<00:09:10.740> and 00:09:11.090 --> 00:09:11.100 align:start position:0% client also has access to that key and 00:09:11.100 --> 00:09:12.710 align:start position:0% client also has access to that key and can<00:09:11.279> do<00:09:11.459> all<00:09:11.700> sorts<00:09:11.940> of<00:09:12.000> bad<00:09:12.180> things<00:09:12.360> to<00:09:12.540> this 00:09:12.710 --> 00:09:12.720 align:start position:0% can do all sorts of bad things to this 00:09:12.720 --> 00:09:15.769 align:start position:0% can do all sorts of bad things to this it<00:09:12.959> can<00:09:13.140> it<00:09:13.680> can<00:09:13.920> slash<00:09:14.459> you<00:09:14.640> it<00:09:15.000> can<00:09:15.180> Ransom 00:09:15.769 --> 00:09:15.779 align:start position:0% it can it can slash you it can Ransom 00:09:15.779 --> 00:09:18.949 align:start position:0% it can it can slash you it can Ransom you<00:09:15.959> it<00:09:16.920> can<00:09:17.100> just<00:09:17.279> exit<00:09:17.820> you<00:09:18.060> it<00:09:18.480> can<00:09:18.660> just 00:09:18.949 --> 00:09:18.959 align:start position:0% you it can just exit you it can just 00:09:18.959 --> 00:09:21.230 align:start position:0% you it can just exit you it can just shut<00:09:19.440> the<00:09:19.680> validator<00:09:20.040> down<00:09:20.399> so<00:09:20.760> you<00:09:20.940> get 00:09:21.230 --> 00:09:21.240 align:start position:0% shut the validator down so you get 00:09:21.240 --> 00:09:26.930 align:start position:0% shut the validator down so you get inactivity<00:09:22.019> leak<00:09:22.519> and<00:09:23.519> DVT<00:09:24.000> comes<00:09:24.360> in 00:09:26.930 --> 00:09:26.940 align:start position:0% 00:09:26.940 --> 00:09:30.530 align:start position:0% so<00:09:27.660> the<00:09:28.200> the<00:09:28.860> DVD<00:09:29.339> comes<00:09:29.700> in 00:09:30.530 --> 00:09:30.540 align:start position:0% so the the DVD comes in 00:09:30.540 --> 00:09:32.449 align:start position:0% so the the DVD comes in um<00:09:30.600> so<00:09:30.959> you<00:09:31.080> can<00:09:31.200> split<00:09:31.500> the<00:09:31.620> validator<00:09:32.040> key<00:09:32.220> in 00:09:32.449 --> 00:09:32.459 align:start position:0% um so you can split the validator key in 00:09:32.459 --> 00:09:34.670 align:start position:0% um so you can split the validator key in different<00:09:32.640> key<00:09:33.000> shares<00:09:33.360> and<00:09:34.140> distribute<00:09:34.560> it 00:09:34.670 --> 00:09:34.680 align:start position:0% different key shares and distribute it 00:09:34.680 --> 00:09:36.829 align:start position:0% different key shares and distribute it over<00:09:35.100> many<00:09:35.459> validator<00:09:35.940> clients<00:09:36.360> this<00:09:36.540> allows 00:09:36.829 --> 00:09:36.839 align:start position:0% over many validator clients this allows 00:09:36.839 --> 00:09:38.090 align:start position:0% over many validator clients this allows for<00:09:36.959> high<00:09:37.140> availability<00:09:37.500> but<00:09:37.800> because 00:09:38.090 --> 00:09:38.100 align:start position:0% for high availability but because 00:09:38.100 --> 00:09:41.329 align:start position:0% for high availability but because imagine<00:09:38.339> these<00:09:38.760> validator<00:09:39.120> shares<00:09:39.600> as<00:09:40.440> a<00:09:41.220> sort 00:09:41.329 --> 00:09:41.339 align:start position:0% imagine these validator shares as a sort 00:09:41.339 --> 00:09:43.850 align:start position:0% imagine these validator shares as a sort of<00:09:41.459> like<00:09:41.580> a<00:09:41.760> multi-sig<00:09:42.300> so<00:09:42.600> if<00:09:42.959> three<00:09:43.380> of<00:09:43.620> these 00:09:43.850 --> 00:09:43.860 align:start position:0% of like a multi-sig so if three of these 00:09:43.860 --> 00:09:46.490 align:start position:0% of like a multi-sig so if three of these Shares<00:09:44.220> are<00:09:44.459> online<00:09:44.640> out<00:09:45.120> of<00:09:45.300> four<00:09:45.540> so<00:09:46.140> if<00:09:46.320> one 00:09:46.490 --> 00:09:46.500 align:start position:0% Shares are online out of four so if one 00:09:46.500 --> 00:09:48.410 align:start position:0% Shares are online out of four so if one of<00:09:46.560> them<00:09:46.680> are<00:09:46.920> offline<00:09:47.339> we<00:09:48.060> can<00:09:48.240> still 00:09:48.410 --> 00:09:48.420 align:start position:0% of them are offline we can still 00:09:48.420 --> 00:09:50.690 align:start position:0% of them are offline we can still continue<00:09:48.660> validating<00:09:49.320> it<00:09:50.100> also<00:09:50.279> allows<00:09:50.519> for 00:09:50.690 --> 00:09:50.700 align:start position:0% continue validating it also allows for 00:09:50.700 --> 00:09:52.730 align:start position:0% continue validating it also allows for different<00:09:50.940> trust<00:09:51.360> assumptions<00:09:51.839> because<00:09:52.500> you 00:09:52.730 --> 00:09:52.740 align:start position:0% different trust assumptions because you 00:09:52.740 --> 00:09:54.710 align:start position:0% different trust assumptions because you can<00:09:52.920> distribute<00:09:53.339> these<00:09:53.700> shares<00:09:54.060> so<00:09:54.300> nobody 00:09:54.710 --> 00:09:54.720 align:start position:0% can distribute these shares so nobody 00:09:54.720 --> 00:09:56.210 align:start position:0% can distribute these shares so nobody with<00:09:54.899> with<00:09:55.080> one<00:09:55.260> of<00:09:55.380> these<00:09:55.500> shares<00:09:55.800> you<00:09:55.980> can't 00:09:56.210 --> 00:09:56.220 align:start position:0% with with one of these shares you can't 00:09:56.220 --> 00:09:58.730 align:start position:0% with with one of these shares you can't do<00:09:56.700> or<00:09:56.880> you<00:09:57.240> can't<00:09:57.360> slash<00:09:57.720> people<00:09:57.899> you<00:09:58.500> can't 00:09:58.730 --> 00:09:58.740 align:start position:0% do or you can't slash people you can't 00:09:58.740 --> 00:10:01.130 align:start position:0% do or you can't slash people you can't uh<00:09:59.339> exit<00:09:59.880> you<00:10:00.120> can't<00:10:00.240> do<00:10:00.420> all<00:10:00.540> of<00:10:00.720> this<00:10:00.839> stuff 00:10:01.130 --> 00:10:01.140 align:start position:0% uh exit you can't do all of this stuff 00:10:01.140 --> 00:10:04.670 align:start position:0% uh exit you can't do all of this stuff so<00:10:01.740> actually<00:10:01.980> we<00:10:02.880> do<00:10:03.060> not<00:10:03.240> require<00:10:03.720> so<00:10:04.320> much<00:10:04.440> we 00:10:04.670 --> 00:10:04.680 align:start position:0% so actually we do not require so much we 00:10:04.680 --> 00:10:06.829 align:start position:0% so actually we do not require so much we can<00:10:05.160> afford<00:10:05.519> to<00:10:05.820> give<00:10:06.000> these<00:10:06.300> keys<00:10:06.540> to<00:10:06.660> other 00:10:06.829 --> 00:10:06.839 align:start position:0% can afford to give these keys to other 00:10:06.839 --> 00:10:09.110 align:start position:0% can afford to give these keys to other people<00:10:07.019> and<00:10:07.320> not<00:10:07.620> require<00:10:08.040> so<00:10:09.000> much 00:10:09.110 --> 00:10:09.120 align:start position:0% people and not require so much 00:10:09.120 --> 00:10:11.329 align:start position:0% people and not require so much collateral<00:10:09.660> right<00:10:10.140> now<00:10:10.320> rocket<00:10:10.740> pool<00:10:10.920> still 00:10:11.329 --> 00:10:11.339 align:start position:0% collateral right now rocket pool still 00:10:11.339 --> 00:10:14.630 align:start position:0% collateral right now rocket pool still requires<00:10:12.000> a<00:10:12.540> somebody<00:10:12.720> to<00:10:13.080> put<00:10:13.200> 16<00:10:13.560> e<00:10:14.040> huge 00:10:14.630 --> 00:10:14.640 align:start position:0% requires a somebody to put 16 e huge 00:10:14.640 --> 00:10:16.490 align:start position:0% requires a somebody to put 16 e huge amount<00:10:14.820> of<00:10:14.940> collateral<00:10:15.300> because<00:10:15.779> that's<00:10:16.200> what 00:10:16.490 --> 00:10:16.500 align:start position:0% amount of collateral because that's what 00:10:16.500 --> 00:10:18.769 align:start position:0% amount of collateral because that's what they<00:10:16.620> can<00:10:16.800> get<00:10:17.040> from<00:10:17.519> That's<00:10:18.000> how<00:10:18.240> much<00:10:18.360> damage 00:10:18.769 --> 00:10:18.779 align:start position:0% they can get from That's how much damage 00:10:18.779 --> 00:10:22.370 align:start position:0% they can get from That's how much damage they<00:10:19.019> can<00:10:19.140> do<00:10:19.320> so<00:10:20.339> um<00:10:20.339> with<00:10:20.700> DVT<00:10:21.180> we<00:10:21.660> get<00:10:21.839> a 00:10:22.370 --> 00:10:22.380 align:start position:0% they can do so um with DVT we get a 00:10:22.380 --> 00:10:24.590 align:start position:0% they can do so um with DVT we get a different<00:10:22.560> trust<00:10:22.920> assumption<00:10:23.700> and<00:10:24.000> uh<00:10:24.420> the 00:10:24.590 --> 00:10:24.600 align:start position:0% different trust assumption and uh the 00:10:24.600 --> 00:10:26.389 align:start position:0% different trust assumption and uh the potential<00:10:24.899> for<00:10:25.260> lower<00:10:25.800> collateral 00:10:26.389 --> 00:10:26.399 align:start position:0% potential for lower collateral 00:10:26.399 --> 00:10:28.210 align:start position:0% potential for lower collateral requirements 00:10:28.210 --> 00:10:28.220 align:start position:0% requirements 00:10:28.220 --> 00:10:29.750 align:start position:0% requirements moreover 00:10:29.750 --> 00:10:29.760 align:start position:0% moreover 00:10:29.760 --> 00:10:31.670 align:start position:0% moreover um<00:10:29.820> those<00:10:30.060> who<00:10:30.360> run<00:10:30.540> already<00:10:30.839> run<00:10:31.140> nodes<00:10:31.500> and 00:10:31.670 --> 00:10:31.680 align:start position:0% um those who run already run nodes and 00:10:31.680 --> 00:10:34.730 align:start position:0% um those who run already run nodes and already<00:10:31.860> have<00:10:32.220> a<00:10:32.880> validator<00:10:33.480> setup<00:10:34.019> they<00:10:34.560> can 00:10:34.730 --> 00:10:34.740 align:start position:0% already have a validator setup they can 00:10:34.740 --> 00:10:37.910 align:start position:0% already have a validator setup they can monetize<00:10:35.220> through<00:10:36.060> DVT<00:10:36.720> Technologies<00:10:37.200> on<00:10:37.800> top 00:10:37.910 --> 00:10:37.920 align:start position:0% monetize through DVT Technologies on top 00:10:37.920 --> 00:10:39.769 align:start position:0% monetize through DVT Technologies on top of<00:10:38.100> their<00:10:38.220> validator<00:10:38.640> sets<00:10:39.060> so<00:10:39.240> it's<00:10:39.360> a<00:10:39.480> way<00:10:39.600> to 00:10:39.769 --> 00:10:39.779 align:start position:0% of their validator sets so it's a way to 00:10:39.779 --> 00:10:41.750 align:start position:0% of their validator sets so it's a way to bump<00:10:40.019> up<00:10:40.260> your 00:10:41.750 --> 00:10:41.760 align:start position:0% bump up your 00:10:41.760 --> 00:10:43.670 align:start position:0% bump up your um<00:10:41.820> your<00:10:42.360> your<00:10:42.360> rewards<00:10:42.959> for<00:10:43.200> having<00:10:43.380> a 00:10:43.670 --> 00:10:43.680 align:start position:0% um your your rewards for having a 00:10:43.680 --> 00:10:45.410 align:start position:0% um your your rewards for having a validator 00:10:45.410 --> 00:10:45.420 align:start position:0% validator 00:10:45.420 --> 00:10:47.210 align:start position:0% validator okay<00:10:45.779> so<00:10:46.079> exactly<00:10:46.500> that's<00:10:46.680> that's<00:10:46.860> exactly 00:10:47.210 --> 00:10:47.220 align:start position:0% okay so exactly that's that's exactly 00:10:47.220 --> 00:10:49.490 align:start position:0% okay so exactly that's that's exactly what<00:10:47.399> you<00:10:47.519> need<00:10:47.700> to<00:10:47.820> know<00:10:47.940> about<00:10:48.420> DVT<00:10:48.959> you'll 00:10:49.490 --> 00:10:49.500 align:start position:0% what you need to know about DVT you'll 00:10:49.500 --> 00:10:51.590 align:start position:0% what you need to know about DVT you'll be<00:10:49.680> able<00:10:49.800> to<00:10:49.920> monetize<00:10:50.339> your<00:10:50.579> machine<00:10:50.760> by 00:10:51.590 --> 00:10:51.600 align:start position:0% be able to monetize your machine by 00:10:51.600 --> 00:10:53.569 align:start position:0% be able to monetize your machine by leveraging<00:10:52.140> other<00:10:52.440> protocols<00:10:52.980> on<00:10:53.220> top<00:10:53.339> of<00:10:53.459> it 00:10:53.569 --> 00:10:53.579 align:start position:0% leveraging other protocols on top of it 00:10:53.579 --> 00:10:55.790 align:start position:0% leveraging other protocols on top of it these<00:10:53.940> Protocols<00:10:54.360> are<00:10:54.600> like<00:10:54.779> SSV<00:10:55.260> Network<00:10:55.440> or 00:10:55.790 --> 00:10:55.800 align:start position:0% these Protocols are like SSV Network or 00:10:55.800 --> 00:10:59.509 align:start position:0% these Protocols are like SSV Network or opal<00:10:56.279> or<00:10:56.579> Diva<00:10:57.060> and<00:10:57.959> that<00:10:58.440> people<00:10:58.740> will<00:10:59.399> be 00:10:59.509 --> 00:10:59.519 align:start position:0% opal or Diva and that people will be 00:10:59.519 --> 00:11:01.790 align:start position:0% opal or Diva and that people will be able<00:10:59.700> to<00:10:59.880> participate<00:11:00.300> in<00:11:00.480> validation<00:11:00.899> even 00:11:01.790 --> 00:11:01.800 align:start position:0% able to participate in validation even 00:11:01.800 --> 00:11:04.970 align:start position:0% able to participate in validation even with<00:11:02.100> less<00:11:02.339> than<00:11:02.579> 32e<00:11:03.600> because<00:11:04.079> you<00:11:04.440> can<00:11:04.500> do<00:11:04.800> a 00:11:04.970 --> 00:11:04.980 align:start position:0% with less than 32e because you can do a 00:11:04.980 --> 00:11:06.590 align:start position:0% with less than 32e because you can do a setup<00:11:05.279> and<00:11:05.579> then<00:11:05.640> you<00:11:05.820> can<00:11:05.940> participate<00:11:06.420> in 00:11:06.590 --> 00:11:06.600 align:start position:0% setup and then you can participate in 00:11:06.600 --> 00:11:08.329 align:start position:0% setup and then you can participate in this<00:11:06.720> which<00:11:07.079> is<00:11:07.260> great<00:11:07.680> for<00:11:07.980> accessibility 00:11:08.329 --> 00:11:08.339 align:start position:0% this which is great for accessibility 00:11:08.339 --> 00:11:10.250 align:start position:0% this which is great for accessibility because<00:11:08.640> we're<00:11:08.880> making<00:11:09.060> part<00:11:09.600> of<00:11:10.079> the 00:11:10.250 --> 00:11:10.260 align:start position:0% because we're making part of the 00:11:10.260 --> 00:11:11.990 align:start position:0% because we're making part of the benefits<00:11:10.620> of<00:11:10.800> running<00:11:10.920> infrastructure<00:11:11.579> to 00:11:11.990 --> 00:11:12.000 align:start position:0% benefits of running infrastructure to 00:11:12.000 --> 00:11:13.310 align:start position:0% benefits of running infrastructure to people<00:11:12.180> that<00:11:12.420> do<00:11:12.540> not<00:11:12.720> that<00:11:12.839> are<00:11:13.019> not<00:11:13.140> rich 00:11:13.310 --> 00:11:13.320 align:start position:0% people that do not that are not rich 00:11:13.320 --> 00:11:15.829 align:start position:0% people that do not that are not rich people<00:11:13.740> do<00:11:14.100> not<00:11:14.220> have<00:11:14.459> 32<00:11:15.060> each<00:11:15.240> so<00:11:15.540> it's<00:11:15.660> great 00:11:15.829 --> 00:11:15.839 align:start position:0% people do not have 32 each so it's great 00:11:15.839 --> 00:11:18.350 align:start position:0% people do not have 32 each so it's great for<00:11:15.959> accessibility 00:11:18.350 --> 00:11:18.360 align:start position:0% for accessibility 00:11:18.360 --> 00:11:22.190 align:start position:0% for accessibility all<00:11:18.779> right<00:11:19.100> withdrawals<00:11:20.100> yep 00:11:22.190 --> 00:11:22.200 align:start position:0% all right withdrawals yep 00:11:22.200 --> 00:11:24.350 align:start position:0% all right withdrawals yep with<00:11:22.560> roles<00:11:22.860> with<00:11:23.100> roles<00:11:23.459> that's<00:11:23.940> what<00:11:24.180> all 00:11:24.350 --> 00:11:24.360 align:start position:0% with roles with roles that's what all 00:11:24.360 --> 00:11:25.730 align:start position:0% with roles with roles that's what all we're<00:11:24.720> waiting<00:11:24.959> for<00:11:25.019> right<00:11:25.200> like<00:11:25.380> we've<00:11:25.680> got 00:11:25.730 --> 00:11:25.740 align:start position:0% we're waiting for right like we've got 00:11:25.740 --> 00:11:28.490 align:start position:0% we're waiting for right like we've got this<00:11:25.860> 32<00:11:26.220> withdrawals<00:11:27.180> are<00:11:27.660> going<00:11:27.839> to<00:11:27.959> be<00:11:28.140> a 00:11:28.490 --> 00:11:28.500 align:start position:0% this 32 withdrawals are going to be a 00:11:28.500 --> 00:11:30.350 align:start position:0% this 32 withdrawals are going to be a new<00:11:28.680> system<00:11:28.860> level<00:11:29.100> operation<00:11:29.700> which<00:11:30.180> will 00:11:30.350 --> 00:11:30.360 align:start position:0% new system level operation which will 00:11:30.360 --> 00:11:32.569 align:start position:0% new system level operation which will have<00:11:30.540> no<00:11:30.779> gas<00:11:30.959> cost<00:11:31.260> and<00:11:31.980> it<00:11:32.160> will<00:11:32.279> they<00:11:32.459> will 00:11:32.569 --> 00:11:32.579 align:start position:0% have no gas cost and it will they will 00:11:32.579 --> 00:11:34.370 align:start position:0% have no gas cost and it will they will not<00:11:32.700> even<00:11:32.820> go<00:11:33.060> to<00:11:33.180> the<00:11:33.300> evm<00:11:33.839> they<00:11:34.260> will 00:11:34.370 --> 00:11:34.380 align:start position:0% not even go to the evm they will 00:11:34.380 --> 00:11:36.710 align:start position:0% not even go to the evm they will increase<00:11:34.560> the<00:11:34.920> uh<00:11:35.399> the<00:11:35.760> balance<00:11:36.120> of<00:11:36.600> the 00:11:36.710 --> 00:11:36.720 align:start position:0% increase the uh the balance of the 00:11:36.720 --> 00:11:39.110 align:start position:0% increase the uh the balance of the withdrawal<00:11:37.079> address<00:11:37.200> automatically 00:11:39.110 --> 00:11:39.120 align:start position:0% withdrawal address automatically 00:11:39.120 --> 00:11:41.329 align:start position:0% withdrawal address automatically um<00:11:39.180> it'll<00:11:39.540> be<00:11:39.720> a<00:11:39.779> limited<00:11:40.260> block<00:11:40.860> per<00:11:41.100> block 00:11:41.329 --> 00:11:41.339 align:start position:0% um it'll be a limited block per block 00:11:41.339 --> 00:11:43.550 align:start position:0% um it'll be a limited block per block just<00:11:41.579> like<00:11:41.760> right<00:11:42.120> now<00:11:42.720> um<00:11:42.779> joining<00:11:43.260> as<00:11:43.440> a 00:11:43.550 --> 00:11:43.560 align:start position:0% just like right now um joining as a 00:11:43.560 --> 00:11:45.230 align:start position:0% just like right now um joining as a validator<00:11:43.920> is<00:11:44.220> also<00:11:44.459> limited<00:11:44.820> block<00:11:44.940> of<00:11:45.120> work 00:11:45.230 --> 00:11:45.240 align:start position:0% validator is also limited block of work 00:11:45.240 --> 00:11:47.269 align:start position:0% validator is also limited block of work there's<00:11:45.420> a<00:11:45.540> limited<00:11:45.779> amount<00:11:45.959> of<00:11:46.140> uh<00:11:46.620> of<00:11:46.920> people 00:11:47.269 --> 00:11:47.279 align:start position:0% there's a limited amount of uh of people 00:11:47.279 --> 00:11:49.250 align:start position:0% there's a limited amount of uh of people that<00:11:47.459> can<00:11:47.579> join<00:11:47.760> the<00:11:47.880> validator<00:11:48.240> set<00:11:48.480> the<00:11:49.079> same 00:11:49.250 --> 00:11:49.260 align:start position:0% that can join the validator set the same 00:11:49.260 --> 00:11:51.829 align:start position:0% that can join the validator set the same thing<00:11:49.440> will<00:11:49.680> happen<00:11:49.800> with<00:11:50.100> withdrawals<00:11:50.839> and 00:11:51.829 --> 00:11:51.839 align:start position:0% thing will happen with withdrawals and 00:11:51.839 --> 00:11:54.170 align:start position:0% thing will happen with withdrawals and what<00:11:52.079> we<00:11:52.200> need<00:11:52.320> to<00:11:52.440> know<00:11:52.620> is<00:11:53.160> that<00:11:53.399> we<00:11:53.880> will<00:11:54.060> be 00:11:54.170 --> 00:11:54.180 align:start position:0% what we need to know is that we will be 00:11:54.180 --> 00:11:55.069 align:start position:0% what we need to know is that we will be able<00:11:54.300> to 00:11:55.069 --> 00:11:55.079 align:start position:0% able to 00:11:55.079 --> 00:11:58.490 align:start position:0% able to get<00:11:55.680> our<00:11:55.920> money<00:11:56.220> if<00:11:56.640> we<00:11:56.760> want<00:11:56.880> to<00:11:57.060> now<00:11:57.839> there's 00:11:58.490 --> 00:11:58.500 align:start position:0% get our money if we want to now there's 00:11:58.500 --> 00:11:59.569 align:start position:0% get our money if we want to now there's something<00:11:58.740> more<00:11:58.980> interesting<00:11:59.279> to<00:11:59.459> think 00:11:59.569 --> 00:11:59.579 align:start position:0% something more interesting to think 00:11:59.579 --> 00:12:01.490 align:start position:0% something more interesting to think about<00:11:59.760> here<00:12:00.060> which<00:12:00.540> is 00:12:01.490 --> 00:12:01.500 align:start position:0% about here which is 00:12:01.500 --> 00:12:03.889 align:start position:0% about here which is what<00:12:02.100> will<00:12:02.220> happen<00:12:02.399> when<00:12:02.700> people<00:12:02.880> are<00:12:03.120> able<00:12:03.480> to 00:12:03.889 --> 00:12:03.899 align:start position:0% what will happen when people are able to 00:12:03.899 --> 00:12:05.630 align:start position:0% what will happen when people are able to take<00:12:04.680> this 00:12:05.630 --> 00:12:05.640 align:start position:0% take this 00:12:05.640 --> 00:12:07.670 align:start position:0% take this will 00:12:07.670 --> 00:12:07.680 align:start position:0% will 00:12:07.680 --> 00:12:11.389 align:start position:0% will um<00:12:07.740> staking<00:12:08.160> pools<00:12:08.779> be<00:12:09.800> uh<00:12:10.800> will<00:12:10.980> people<00:12:11.160> take 00:12:11.389 --> 00:12:11.399 align:start position:0% um staking pools be uh will people take 00:12:11.399 --> 00:12:13.069 align:start position:0% um staking pools be uh will people take out<00:12:11.579> of<00:12:11.700> sticking<00:12:12.060> pools<00:12:12.360> and<00:12:12.540> start<00:12:12.660> solo 00:12:13.069 --> 00:12:13.079 align:start position:0% out of sticking pools and start solo 00:12:13.079 --> 00:12:14.930 align:start position:0% out of sticking pools and start solo staking<00:12:13.320> that's<00:12:13.560> what<00:12:13.740> we're<00:12:13.860> hoping<00:12:14.220> or<00:12:14.579> will 00:12:14.930 --> 00:12:14.940 align:start position:0% staking that's what we're hoping or will 00:12:14.940 --> 00:12:17.690 align:start position:0% staking that's what we're hoping or will the<00:12:15.660> opposite<00:12:16.140> happen 00:12:17.690 --> 00:12:17.700 align:start position:0% the opposite happen 00:12:17.700 --> 00:12:20.870 align:start position:0% the opposite happen so<00:12:18.420> what's<00:12:18.839> going<00:12:19.140> to<00:12:19.260> make<00:12:19.500> it<00:12:19.680> easier<00:12:20.220> to 00:12:20.870 --> 00:12:20.880 align:start position:0% so what's going to make it easier to 00:12:20.880 --> 00:12:22.850 align:start position:0% so what's going to make it easier to convince<00:12:21.180> people<00:12:21.360> to<00:12:21.779> take<00:12:21.959> out<00:12:22.320> of<00:12:22.560> staking 00:12:22.850 --> 00:12:22.860 align:start position:0% convince people to take out of staking 00:12:22.860 --> 00:12:26.150 align:start position:0% convince people to take out of staking pools<00:12:23.279> and<00:12:23.459> centralized<00:12:23.880> exchanges<00:12:24.360> and 00:12:26.150 --> 00:12:26.160 align:start position:0% pools and centralized exchanges and 00:12:26.160 --> 00:12:27.829 align:start position:0% pools and centralized exchanges and um<00:12:26.220> and<00:12:26.700> start<00:12:26.820> running 00:12:27.829 --> 00:12:27.839 align:start position:0% um and start running 00:12:27.839 --> 00:12:30.110 align:start position:0% um and start running instead<00:12:28.440> of<00:12:28.500> writing<00:12:28.680> it<00:12:28.800> themselves<00:12:29.160> yeah 00:12:30.110 --> 00:12:30.120 align:start position:0% instead of writing it themselves yeah 00:12:30.120 --> 00:12:32.990 align:start position:0% instead of writing it themselves yeah all<00:12:30.600> right<00:12:30.779> so<00:12:31.500> yeah<00:12:31.740> now<00:12:32.220> it's<00:12:32.399> time<00:12:32.640> to<00:12:32.760> talk 00:12:32.990 --> 00:12:33.000 align:start position:0% all right so yeah now it's time to talk 00:12:33.000 --> 00:12:35.329 align:start position:0% all right so yeah now it's time to talk about<00:12:33.300> product<00:12:33.839> line<00:12:34.140> charting<00:12:34.620> and<00:12:35.100> the 00:12:35.329 --> 00:12:35.339 align:start position:0% about product line charting and the 00:12:35.339 --> 00:12:39.949 align:start position:0% about product line charting and the future<00:12:35.579> of<00:12:35.880> overthem<00:12:37.079> so<00:12:37.680> mainly<00:12:38.240> uh<00:12:39.240> the<00:12:39.959> the 00:12:39.949 --> 00:12:39.959 align:start position:0% future of overthem so mainly uh the the 00:12:39.959 --> 00:12:42.110 align:start position:0% future of overthem so mainly uh the the roadmap<00:12:40.440> Institute<00:12:40.920> changed<00:12:41.459> uh<00:12:41.820> completely 00:12:42.110 --> 00:12:42.120 align:start position:0% roadmap Institute changed uh completely 00:12:42.120 --> 00:12:44.449 align:start position:0% roadmap Institute changed uh completely at<00:12:42.300> the<00:12:42.420> moment<00:12:42.540> that<00:12:42.720> vitalik<00:12:43.139> make<00:12:43.440> these<00:12:43.860> uh 00:12:44.449 --> 00:12:44.459 align:start position:0% at the moment that vitalik make these uh 00:12:44.459 --> 00:12:47.629 align:start position:0% at the moment that vitalik make these uh credit<00:12:44.820> post<00:12:45.200> so<00:12:46.200> mainly<00:12:46.860> we<00:12:47.040> realized<00:12:47.519> that 00:12:47.629 --> 00:12:47.639 align:start position:0% credit post so mainly we realized that 00:12:47.639 --> 00:12:49.850 align:start position:0% credit post so mainly we realized that if<00:12:47.820> we<00:12:48.000> facility<00:12:48.560> they<00:12:49.560> have<00:12:49.740> better 00:12:49.850 --> 00:12:49.860 align:start position:0% if we facility they have better 00:12:49.860 --> 00:12:51.530 align:start position:0% if we facility they have better scalability<00:12:50.339> and<00:12:50.700> potential<00:12:51.120> that<00:12:51.360> the 00:12:51.530 --> 00:12:51.540 align:start position:0% scalability and potential that the 00:12:51.540 --> 00:12:53.569 align:start position:0% scalability and potential that the previous<00:12:51.660> execution<00:12:52.200> shouts<00:12:52.740> so<00:12:53.220> mainly 00:12:53.569 --> 00:12:53.579 align:start position:0% previous execution shouts so mainly 00:12:53.579 --> 00:12:55.310 align:start position:0% previous execution shouts so mainly everything<00:12:54.060> changed<00:12:54.540> at<00:12:54.660> that<00:12:54.779> moment<00:12:54.959> we 00:12:55.310 --> 00:12:55.320 align:start position:0% everything changed at that moment we 00:12:55.320 --> 00:12:57.889 align:start position:0% everything changed at that moment we forget<00:12:55.500> about<00:12:55.800> having<00:12:56.220> execution<00:12:56.880> on<00:12:57.720> the 00:12:57.889 --> 00:12:57.899 align:start position:0% forget about having execution on the 00:12:57.899 --> 00:13:00.170 align:start position:0% forget about having execution on the charts<00:12:58.320> and<00:12:58.800> we<00:12:58.980> move<00:12:59.160> to<00:12:59.339> a<00:12:59.459> way<00:12:59.700> to<00:12:59.880> provide 00:13:00.170 --> 00:13:00.180 align:start position:0% charts and we move to a way to provide 00:13:00.180 --> 00:13:02.090 align:start position:0% charts and we move to a way to provide data<00:13:00.660> availability<00:13:00.839> for<00:13:01.320> other<00:13:01.620> layer<00:13:01.980> 2 00:13:02.090 --> 00:13:02.100 align:start position:0% data availability for other layer 2 00:13:02.100 --> 00:13:03.470 align:start position:0% data availability for other layer 2 applications<00:13:02.519> that<00:13:02.820> are<00:13:03.000> going<00:13:03.120> to<00:13:03.240> happen 00:13:03.470 --> 00:13:03.480 align:start position:0% applications that are going to happen 00:13:03.480 --> 00:13:05.629 align:start position:0% applications that are going to happen during<00:13:03.839> these<00:13:04.139> years 00:13:05.629 --> 00:13:05.639 align:start position:0% during these years 00:13:05.639 --> 00:13:07.250 align:start position:0% during these years um so<00:13:05.940> mainly<00:13:06.240> mainly<00:13:06.779> the<00:13:06.899> thing<00:13:07.019> that 00:13:07.250 --> 00:13:07.260 align:start position:0% um so mainly mainly the thing that 00:13:07.260 --> 00:13:08.750 align:start position:0% um so mainly mainly the thing that happened<00:13:07.500> with<00:13:07.980> the<00:13:08.100> product<00:13:08.339> and<00:13:08.579> starting 00:13:08.750 --> 00:13:08.760 align:start position:0% happened with the product and starting 00:13:08.760 --> 00:13:11.750 align:start position:0% happened with the product and starting is<00:13:09.180> that<00:13:09.420> uh<00:13:09.920> instead<00:13:10.920> of<00:13:11.040> providing<00:13:11.459> more 00:13:11.750 --> 00:13:11.760 align:start position:0% is that uh instead of providing more 00:13:11.760 --> 00:13:14.210 align:start position:0% is that uh instead of providing more space<00:13:12.060> for<00:13:12.360> transactions<00:13:13.079> we<00:13:13.500> are<00:13:13.680> we<00:13:14.040> are 00:13:14.210 --> 00:13:14.220 align:start position:0% space for transactions we are we are 00:13:14.220 --> 00:13:16.009 align:start position:0% space for transactions we are we are going<00:13:14.339> to<00:13:14.459> provide<00:13:14.760> more<00:13:15.060> space<00:13:15.360> for<00:13:15.600> data 00:13:16.009 --> 00:13:16.019 align:start position:0% going to provide more space for data 00:13:16.019 --> 00:13:18.650 align:start position:0% going to provide more space for data that<00:13:16.500> the<00:13:16.740> layer<00:13:17.279> 2<00:13:17.399> Solutions<00:13:17.760> can<00:13:18.120> use<00:13:18.300> it<00:13:18.480> in 00:13:18.650 --> 00:13:18.660 align:start position:0% that the layer 2 Solutions can use it in 00:13:18.660 --> 00:13:19.550 align:start position:0% that the layer 2 Solutions can use it in the<00:13:18.720> future 00:13:19.550 --> 00:13:19.560 align:start position:0% the future 00:13:19.560 --> 00:13:21.470 align:start position:0% the future so<00:13:19.980> the<00:13:20.160> idea<00:13:20.339> is<00:13:20.519> mainly<00:13:20.880> that<00:13:21.060> the<00:13:21.180> execution 00:13:21.470 --> 00:13:21.480 align:start position:0% so the idea is mainly that the execution 00:13:21.480 --> 00:13:23.750 align:start position:0% so the idea is mainly that the execution is<00:13:21.720> going<00:13:21.839> to<00:13:21.959> happen<00:13:22.079> on<00:13:22.440> these<00:13:22.800> uh<00:13:22.920> SQL<00:13:23.339> VMS 00:13:23.750 --> 00:13:23.760 align:start position:0% is going to happen on these uh SQL VMS 00:13:23.760 --> 00:13:26.629 align:start position:0% is going to happen on these uh SQL VMS and<00:13:23.940> prolapse<00:13:24.420> uh<00:13:25.079> keeping<00:13:25.560> the<00:13:25.860> execution 00:13:26.629 --> 00:13:26.639 align:start position:0% and prolapse uh keeping the execution 00:13:26.639 --> 00:13:29.509 align:start position:0% and prolapse uh keeping the execution part<00:13:26.880> of<00:13:27.060> ethereum<00:13:27.480> as<00:13:27.779> it<00:13:27.959> is 00:13:29.509 --> 00:13:29.519 align:start position:0% part of ethereum as it is 00:13:29.519 --> 00:13:31.310 align:start position:0% part of ethereum as it is um<00:13:29.579> mainly<00:13:30.420> from<00:13:30.779> the<00:13:30.899> point<00:13:31.019> of<00:13:31.200> view 00:13:31.310 --> 00:13:31.320 align:start position:0% um mainly from the point of view 00:13:31.320 --> 00:13:32.990 align:start position:0% um mainly from the point of view validator 00:13:32.990 --> 00:13:33.000 align:start position:0% validator 00:13:33.000 --> 00:13:37.250 align:start position:0% validator um is<00:13:33.540> just<00:13:33.839> a<00:13:34.940> way<00:13:35.940> to<00:13:36.180> validate<00:13:36.779> the<00:13:37.079> data 00:13:37.250 --> 00:13:37.260 align:start position:0% um is just a way to validate the data 00:13:37.260 --> 00:13:40.389 align:start position:0% um is just a way to validate the data that<00:13:37.440> is<00:13:37.620> available<00:13:38.180> so<00:13:39.180> it's<00:13:39.420> not<00:13:39.660> going<00:13:39.839> to 00:13:40.389 --> 00:13:40.399 align:start position:0% that is available so it's not going to 00:13:40.399 --> 00:13:43.250 align:start position:0% that is available so it's not going to the<00:13:41.399> include<00:13:41.880> the<00:13:42.060> need<00:13:42.300> of 00:13:43.250 --> 00:13:43.260 align:start position:0% the include the need of 00:13:43.260 --> 00:13:45.590 align:start position:0% the include the need of um<00:13:43.320> validate<00:13:43.860> this<00:13:44.220> this<00:13:44.339> data<00:13:44.880> as<00:13:45.180> in<00:13:45.480> the 00:13:45.590 --> 00:13:45.600 align:start position:0% um validate this this data as in the 00:13:45.600 --> 00:13:48.889 align:start position:0% um validate this this data as in the state<00:13:45.779> of<00:13:45.899> ethereum 00:13:48.889 --> 00:13:48.899 align:start position:0% 00:13:48.899 --> 00:13:50.990 align:start position:0% um so<00:13:49.320> yeah<00:13:49.440> what<00:13:49.860> do<00:13:49.980> you<00:13:50.100> what<00:13:50.519> do<00:13:50.700> you<00:13:50.760> need 00:13:50.990 --> 00:13:51.000 align:start position:0% um so yeah what do you what do you need 00:13:51.000 --> 00:13:52.250 align:start position:0% um so yeah what do you what do you need to<00:13:51.120> know<00:13:51.240> about<00:13:51.420> this 00:13:52.250 --> 00:13:52.260 align:start position:0% to know about this 00:13:52.260 --> 00:13:55.430 align:start position:0% to know about this um<00:13:52.399> chain<00:13:53.399> is<00:13:53.760> going<00:13:54.000> to<00:13:54.300> store<00:13:54.839> these<00:13:55.380> new 00:13:55.430 --> 00:13:55.440 align:start position:0% um chain is going to store these new 00:13:55.440 --> 00:13:58.610 align:start position:0% um chain is going to store these new blocks<00:13:55.920> and<00:13:57.420> um<00:13:57.480> the<00:13:57.720> data<00:13:58.200> is<00:13:58.260> going<00:13:58.440> to<00:13:58.500> be 00:13:58.610 --> 00:13:58.620 align:start position:0% blocks and um the data is going to be 00:13:58.620 --> 00:14:00.710 align:start position:0% blocks and um the data is going to be stored<00:13:59.100> it's<00:13:59.459> going<00:13:59.639> to<00:13:59.760> be<00:13:59.820> used<00:14:00.000> by<00:14:00.300> the<00:14:00.540> roll 00:14:00.710 --> 00:14:00.720 align:start position:0% stored it's going to be used by the roll 00:14:00.720 --> 00:14:03.350 align:start position:0% stored it's going to be used by the roll apps<00:14:01.019> so<00:14:01.079> mainly<00:14:01.380> the<00:14:01.500> idea<00:14:01.680> is<00:14:02.100> that<00:14:03.000> um<00:14:03.060> you 00:14:03.350 --> 00:14:03.360 align:start position:0% apps so mainly the idea is that um you 00:14:03.360 --> 00:14:05.389 align:start position:0% apps so mainly the idea is that um you get<00:14:03.600> a<00:14:03.839> vertical<00:14:04.200> tree<00:14:04.380> approved<00:14:04.980> of<00:14:05.220> this 00:14:05.389 --> 00:14:05.399 align:start position:0% get a vertical tree approved of this 00:14:05.399 --> 00:14:07.910 align:start position:0% get a vertical tree approved of this data<00:14:05.820> and<00:14:06.480> you<00:14:06.720> can<00:14:06.839> use<00:14:07.079> a<00:14:07.320> break<00:14:07.500> compiler 00:14:07.910 --> 00:14:07.920 align:start position:0% data and you can use a break compiler 00:14:07.920 --> 00:14:09.050 align:start position:0% data and you can use a break compiler smart<00:14:08.100> contract<00:14:08.399> in<00:14:08.579> ethereum<00:14:08.880> that 00:14:09.050 --> 00:14:09.060 align:start position:0% smart contract in ethereum that 00:14:09.060 --> 00:14:11.690 align:start position:0% smart contract in ethereum that validates<00:14:09.420> this<00:14:09.720> data<00:14:10.139> allowing<00:14:10.860> them<00:14:11.100> to 00:14:11.690 --> 00:14:11.700 align:start position:0% validates this data allowing them to 00:14:11.700 --> 00:14:14.690 align:start position:0% validates this data allowing them to verify<00:14:12.300> verify<00:14:12.899> the<00:14:13.200> state<00:14:13.440> of<00:14:13.860> these<00:14:14.279> Layer 00:14:14.690 --> 00:14:14.700 align:start position:0% verify verify the state of these Layer 00:14:14.700 --> 00:14:16.730 align:start position:0% verify verify the state of these Layer Two<00:14:14.820> Solutions 00:14:16.730 --> 00:14:16.740 align:start position:0% Two Solutions 00:14:16.740 --> 00:14:17.389 align:start position:0% Two Solutions um 00:14:17.389 --> 00:14:17.399 align:start position:0% um 00:14:17.399 --> 00:14:20.030 align:start position:0% um yeah<00:14:18.060> mainly<00:14:18.420> mainly<00:14:18.720> the<00:14:18.899> idea<00:14:19.079> behind<00:14:19.860> this 00:14:20.030 --> 00:14:20.040 align:start position:0% yeah mainly mainly the idea behind this 00:14:20.040 --> 00:14:22.610 align:start position:0% yeah mainly mainly the idea behind this is<00:14:20.279> like<00:14:20.880> a<00:14:21.180> solution<00:14:21.540> like<00:14:21.779> the<00:14:22.019> Chicago<00:14:22.200> VM 00:14:22.610 --> 00:14:22.620 align:start position:0% is like a solution like the Chicago VM 00:14:22.620 --> 00:14:26.750 align:start position:0% is like a solution like the Chicago VM uh<00:14:23.220> like<00:14:23.399> a<00:14:23.519> polygons<00:14:23.940> yesterday<00:14:24.680> that<00:14:25.680> uh<00:14:26.100> are 00:14:26.750 --> 00:14:26.760 align:start position:0% uh like a polygons yesterday that uh are 00:14:26.760 --> 00:14:28.730 align:start position:0% uh like a polygons yesterday that uh are going<00:14:26.940> to<00:14:27.060> be<00:14:27.180> able<00:14:27.420> to<00:14:27.839> have<00:14:28.019> a<00:14:28.200> proof<00:14:28.440> of<00:14:28.560> the 00:14:28.730 --> 00:14:28.740 align:start position:0% going to be able to have a proof of the 00:14:28.740 --> 00:14:30.050 align:start position:0% going to be able to have a proof of the state<00:14:28.860> and<00:14:29.160> take<00:14:29.339> the<00:14:29.459> security<00:14:29.639> of<00:14:29.940> the 00:14:30.050 --> 00:14:30.060 align:start position:0% state and take the security of the 00:14:30.060 --> 00:14:32.030 align:start position:0% state and take the security of the Syrian<00:14:30.360> inside<00:14:30.899> this<00:14:31.260> layer<00:14:31.560> two<00:14:31.680> solutions 00:14:32.030 --> 00:14:32.040 align:start position:0% Syrian inside this layer two solutions 00:14:32.040 --> 00:14:34.370 align:start position:0% Syrian inside this layer two solutions so<00:14:32.279> mainly<00:14:32.700> its<00:14:33.420> region<00:14:33.720> is<00:14:34.019> trying<00:14:34.200> to 00:14:34.370 --> 00:14:34.380 align:start position:0% so mainly its region is trying to 00:14:34.380 --> 00:14:36.410 align:start position:0% so mainly its region is trying to provide<00:14:34.620> these<00:14:34.920> new<00:14:35.100> tools<00:14:35.459> for<00:14:35.940> this<00:14:36.180> kind<00:14:36.300> of 00:14:36.410 --> 00:14:36.420 align:start position:0% provide these new tools for this kind of 00:14:36.420 --> 00:14:38.690 align:start position:0% provide these new tools for this kind of solutions<00:14:36.779> making<00:14:37.200> the<00:14:37.560> scalability<00:14:38.160> going 00:14:38.690 --> 00:14:38.700 align:start position:0% solutions making the scalability going 00:14:38.700 --> 00:14:40.189 align:start position:0% solutions making the scalability going in<00:14:39.120> that<00:14:39.300> direction 00:14:40.189 --> 00:14:40.199 align:start position:0% in that direction 00:14:40.199 --> 00:14:42.230 align:start position:0% in that direction so<00:14:40.620> what<00:14:40.740> do<00:14:40.920> we<00:14:41.040> need<00:14:41.160> to<00:14:41.279> know<00:14:41.399> we<00:14:41.940> need<00:14:42.120> to 00:14:42.230 --> 00:14:42.240 align:start position:0% so what do we need to know we need to 00:14:42.240 --> 00:14:44.990 align:start position:0% so what do we need to know we need to know<00:14:42.360> that<00:14:42.540> those<00:14:43.019> blobs<00:14:43.680> those<00:14:43.980> new<00:14:44.220> Blobs<00:14:44.820> of 00:14:44.990 --> 00:14:45.000 align:start position:0% know that those blobs those new Blobs of 00:14:45.000 --> 00:14:47.269 align:start position:0% know that those blobs those new Blobs of data<00:14:45.360> will<00:14:45.779> be<00:14:45.899> stored<00:14:46.260> in<00:14:46.560> the<00:14:46.680> beacon<00:14:47.040> chain 00:14:47.269 --> 00:14:47.279 align:start position:0% data will be stored in the beacon chain 00:14:47.279 --> 00:14:50.389 align:start position:0% data will be stored in the beacon chain which<00:14:48.180> will<00:14:48.420> mean<00:14:48.600> that<00:14:49.019> our<00:14:49.260> Beacon<00:14:49.800> chains 00:14:50.389 --> 00:14:50.399 align:start position:0% which will mean that our Beacon chains 00:14:50.399 --> 00:14:52.850 align:start position:0% which will mean that our Beacon chains as<00:14:50.820> validator<00:14:51.300> service<00:14:51.600> takers<00:14:52.079> will<00:14:52.620> grow 00:14:52.850 --> 00:14:52.860 align:start position:0% as validator service takers will grow 00:14:52.860 --> 00:14:56.629 align:start position:0% as validator service takers will grow will<00:14:53.519> bloat<00:14:54.000> but<00:14:54.839> hey<00:14:55.800> it<00:14:56.160> will<00:14:56.279> not<00:14:56.399> grow 00:14:56.629 --> 00:14:56.639 align:start position:0% will bloat but hey it will not grow 00:14:56.639 --> 00:14:58.970 align:start position:0% will bloat but hey it will not grow indefinitely<00:14:57.240> because<00:14:57.540> this<00:14:57.959> data<00:14:58.380> will<00:14:58.800> only 00:14:58.970 --> 00:14:58.980 align:start position:0% indefinitely because this data will only 00:14:58.980 --> 00:15:01.129 align:start position:0% indefinitely because this data will only be<00:14:59.220> stored<00:14:59.579> for<00:15:00.000> about<00:15:00.120> a<00:15:00.360> month<00:15:00.540> so<00:15:01.019> that's 00:15:01.129 --> 00:15:01.139 align:start position:0% be stored for about a month so that's 00:15:01.139 --> 00:15:03.710 align:start position:0% be stored for about a month so that's great<00:15:01.440> so<00:15:01.920> we'll<00:15:02.100> have<00:15:02.399> the<00:15:02.820> hour<00:15:03.120> Beacon 00:15:03.710 --> 00:15:03.720 align:start position:0% great so we'll have the hour Beacon 00:15:03.720 --> 00:15:05.090 align:start position:0% great so we'll have the hour Beacon change<00:15:03.899> will<00:15:04.079> not<00:15:04.260> just<00:15:04.440> continuously<00:15:04.920> grow 00:15:05.090 --> 00:15:05.100 align:start position:0% change will not just continuously grow 00:15:05.100 --> 00:15:07.009 align:start position:0% change will not just continuously grow and<00:15:05.279> grow<00:15:05.399> and<00:15:05.579> grow<00:15:05.760> at<00:15:06.060> least<00:15:06.180> the<00:15:06.600> part<00:15:06.779> of 00:15:07.009 --> 00:15:07.019 align:start position:0% and grow and grow at least the part of 00:15:07.019 --> 00:15:09.710 align:start position:0% and grow and grow at least the part of the<00:15:07.139> blobs<00:15:07.500> but<00:15:08.040> every<00:15:08.459> month 00:15:09.710 --> 00:15:09.720 align:start position:0% the blobs but every month 00:15:09.720 --> 00:15:11.930 align:start position:0% the blobs but every month um<00:15:09.779> we<00:15:10.139> will<00:15:10.320> will<00:15:10.500> be<00:15:10.680> deleting<00:15:11.100> this<00:15:11.399> data<00:15:11.760> so 00:15:11.930 --> 00:15:11.940 align:start position:0% um we will will be deleting this data so 00:15:11.940 --> 00:15:13.790 align:start position:0% um we will will be deleting this data so it<00:15:12.060> will<00:15:12.240> grow<00:15:12.420> but<00:15:13.019> it<00:15:13.320> will<00:15:13.440> now<00:15:13.560> grow 00:15:13.790 --> 00:15:13.800 align:start position:0% it will grow but it will now grow 00:15:13.800 --> 00:15:16.370 align:start position:0% it will grow but it will now grow indefinitely 00:15:16.370 --> 00:15:16.380 align:start position:0% indefinitely 00:15:16.380 --> 00:15:19.790 align:start position:0% indefinitely all<00:15:16.980> right<00:15:17.240> yeah<00:15:18.240> next<00:15:18.540> big<00:15:18.779> topic<00:15:19.139> anonymity 00:15:19.790 --> 00:15:19.800 align:start position:0% all right yeah next big topic anonymity 00:15:19.800 --> 00:15:22.430 align:start position:0% all right yeah next big topic anonymity yeah<00:15:20.459> that's<00:15:20.760> also<00:15:21.120> a<00:15:21.240> critical<00:15:21.660> point<00:15:21.899> of<00:15:22.079> the 00:15:22.430 --> 00:15:22.440 align:start position:0% yeah that's also a critical point of the 00:15:22.440 --> 00:15:25.310 align:start position:0% yeah that's also a critical point of the network<00:15:22.699> so<00:15:23.699> yeah<00:15:24.000> the<00:15:24.240> thing<00:15:24.420> is<00:15:24.540> since<00:15:25.079> we 00:15:25.310 --> 00:15:25.320 align:start position:0% network so yeah the thing is since we 00:15:25.320 --> 00:15:27.470 align:start position:0% network so yeah the thing is since we are<00:15:25.440> using<00:15:25.800> random<00:15:26.220> in<00:15:26.579> the<00:15:26.760> we<00:15:26.880> can<00:15:27.120> change<00:15:27.240> to 00:15:27.470 --> 00:15:27.480 align:start position:0% are using random in the we can change to 00:15:27.480 --> 00:15:29.449 align:start position:0% are using random in the we can change to select<00:15:27.839> the<00:15:27.959> validator<00:15:28.320> proposals<00:15:29.040> it's 00:15:29.449 --> 00:15:29.459 align:start position:0% select the validator proposals it's 00:15:29.459 --> 00:15:31.430 align:start position:0% select the validator proposals it's possible<00:15:29.760> to<00:15:29.940> know<00:15:30.060> beforehan<00:15:30.839> who<00:15:31.079> is<00:15:31.199> going 00:15:31.430 --> 00:15:31.440 align:start position:0% possible to know beforehan who is going 00:15:31.440 --> 00:15:34.310 align:start position:0% possible to know beforehan who is going to<00:15:31.560> be<00:15:31.680> the<00:15:31.860> next<00:15:32.040> one<00:15:32.760> and<00:15:33.360> since<00:15:33.779> we<00:15:34.199> are 00:15:34.310 --> 00:15:34.320 align:start position:0% to be the next one and since we are 00:15:34.320 --> 00:15:37.250 align:start position:0% to be the next one and since we are using<00:15:34.620> lip<00:15:35.040> to<00:15:35.220> be<00:15:35.399> Network<00:15:35.639> to<00:15:36.480> communicate 00:15:37.250 --> 00:15:37.260 align:start position:0% using lip to be Network to communicate 00:15:37.260 --> 00:15:39.050 align:start position:0% using lip to be Network to communicate with<00:15:37.380> this<00:15:37.500> node<00:15:37.860> it's<00:15:38.220> also<00:15:38.519> possible<00:15:38.760> to<00:15:38.940> get 00:15:39.050 --> 00:15:39.060 align:start position:0% with this node it's also possible to get 00:15:39.060 --> 00:15:42.230 align:start position:0% with this node it's also possible to get the<00:15:39.240> IP<00:15:39.480> of<00:15:39.720> the<00:15:39.839> nodes<00:15:40.560> so<00:15:41.339> mainly<00:15:41.820> the<00:15:42.060> thing 00:15:42.230 --> 00:15:42.240 align:start position:0% the IP of the nodes so mainly the thing 00:15:42.240 --> 00:15:44.990 align:start position:0% the IP of the nodes so mainly the thing is<00:15:42.660> that<00:15:43.139> uh<00:15:43.500> since<00:15:43.740> we<00:15:43.980> have<00:15:44.100> also<00:15:44.339> myth<00:15:44.820> in 00:15:44.990 --> 00:15:45.000 align:start position:0% is that uh since we have also myth in 00:15:45.000 --> 00:15:46.910 align:start position:0% is that uh since we have also myth in this<00:15:45.180> situation 00:15:46.910 --> 00:15:46.920 align:start position:0% this situation 00:15:46.920 --> 00:15:49.910 align:start position:0% this situation um people<00:15:47.339> want<00:15:48.000> or<00:15:48.540> could<00:15:49.019> try<00:15:49.320> to<00:15:49.620> attack 00:15:49.910 --> 00:15:49.920 align:start position:0% um people want or could try to attack 00:15:49.920 --> 00:15:52.850 align:start position:0% um people want or could try to attack this<00:15:50.339> node<00:15:50.639> because<00:15:51.360> they<00:15:51.720> can<00:15:51.839> get<00:15:52.139> the<00:15:52.560> minor 00:15:52.850 --> 00:15:52.860 align:start position:0% this node because they can get the minor 00:15:52.860 --> 00:15:54.410 align:start position:0% this node because they can get the minor attraction<00:15:53.100> value<00:15:53.399> the<00:15:53.699> maximum<00:15:54.000> extraction 00:15:54.410 --> 00:15:54.420 align:start position:0% attraction value the maximum extraction 00:15:54.420 --> 00:15:55.850 align:start position:0% attraction value the maximum extraction value<00:15:54.600> from<00:15:54.959> the<00:15:55.079> block 00:15:55.850 --> 00:15:55.860 align:start position:0% value from the block 00:15:55.860 --> 00:15:58.250 align:start position:0% value from the block so<00:15:56.579> at<00:15:56.820> the<00:15:57.000> end<00:15:57.060> is<00:15:57.300> the<00:15:57.660> the<00:15:57.779> same<00:15:58.079> problem 00:15:58.250 --> 00:15:58.260 align:start position:0% so at the end is the the same problem 00:15:58.260 --> 00:15:59.629 align:start position:0% so at the end is the the same problem that<00:15:58.500> before<00:15:58.680> we<00:15:59.100> are<00:15:59.220> putting<00:15:59.519> the 00:15:59.629 --> 00:15:59.639 align:start position:0% that before we are putting the 00:15:59.639 --> 00:16:02.150 align:start position:0% that before we are putting the integration<00:16:00.180> to<00:16:00.660> attack<00:16:00.779> the<00:16:01.079> network<00:16:01.199> so<00:16:01.920> we 00:16:02.150 --> 00:16:02.160 align:start position:0% integration to attack the network so we 00:16:02.160 --> 00:16:03.470 align:start position:0% integration to attack the network so we are<00:16:02.279> making 00:16:03.470 --> 00:16:03.480 align:start position:0% are making 00:16:03.480 --> 00:16:06.230 align:start position:0% are making um<00:16:03.540> yeah<00:16:04.019> right<00:16:04.500> Integrations<00:16:05.100> for<00:16:05.579> for<00:16:05.820> the 00:16:06.230 --> 00:16:06.240 align:start position:0% um yeah right Integrations for for the 00:16:06.240 --> 00:16:08.569 align:start position:0% um yeah right Integrations for for the The<00:16:06.720> Source<00:16:07.139> takers 00:16:08.569 --> 00:16:08.579 align:start position:0% The Source takers 00:16:08.579 --> 00:16:11.210 align:start position:0% The Source takers um<00:16:08.699> but<00:16:09.000> this<00:16:09.360> is<00:16:09.480> not<00:16:09.959> just<00:16:10.199> that<00:16:10.620> the<00:16:11.100> thing 00:16:11.210 --> 00:16:11.220 align:start position:0% um but this is not just that the thing 00:16:11.220 --> 00:16:12.590 align:start position:0% um but this is not just that the thing is 00:16:12.590 --> 00:16:12.600 align:start position:0% is 00:16:12.600 --> 00:16:15.410 align:start position:0% is um the<00:16:13.320> secretary<00:16:13.800> single<00:16:14.639> sector<00:16:14.880> leader 00:16:15.410 --> 00:16:15.420 align:start position:0% um the secretary single sector leader 00:16:15.420 --> 00:16:17.090 align:start position:0% um the secretary single sector leader election<00:16:15.540> is<00:16:16.019> a<00:16:16.139> protocol<00:16:16.380> that<00:16:16.680> is<00:16:16.800> going<00:16:16.980> to 00:16:17.090 --> 00:16:17.100 align:start position:0% election is a protocol that is going to 00:16:17.100 --> 00:16:19.850 align:start position:0% election is a protocol that is going to allow<00:16:17.399> to<00:16:18.180> hide<00:16:18.480> who<00:16:18.720> is<00:16:18.839> going<00:16:19.019> to<00:16:19.139> be<00:16:19.560> the 00:16:19.850 --> 00:16:19.860 align:start position:0% allow to hide who is going to be the 00:16:19.860 --> 00:16:22.970 align:start position:0% allow to hide who is going to be the next<00:16:20.040> proposal<00:16:20.839> uh<00:16:21.839> and<00:16:22.199> with<00:16:22.440> that<00:16:22.620> you<00:16:22.860> can 00:16:22.970 --> 00:16:22.980 align:start position:0% next proposal uh and with that you can 00:16:22.980 --> 00:16:25.370 align:start position:0% next proposal uh and with that you can protect<00:16:23.459> this<00:16:24.000> kind<00:16:24.120> of<00:16:24.240> attacks<00:16:24.600> and<00:16:25.079> this<00:16:25.260> is 00:16:25.370 --> 00:16:25.380 align:start position:0% protect this kind of attacks and this is 00:16:25.380 --> 00:16:26.990 align:start position:0% protect this kind of attacks and this is something<00:16:25.620> that<00:16:25.980> is<00:16:26.100> already<00:16:26.279> in<00:16:26.639> development 00:16:26.990 --> 00:16:27.000 align:start position:0% something that is already in development 00:16:27.000 --> 00:16:29.210 align:start position:0% something that is already in development in<00:16:27.360> the<00:16:27.420> protocol<00:16:27.779> and<00:16:28.440> it's<00:16:28.560> probably<00:16:28.800> very 00:16:29.210 --> 00:16:29.220 align:start position:0% in the protocol and it's probably very 00:16:29.220 --> 00:16:30.590 align:start position:0% in the protocol and it's probably very important<00:16:29.519> to<00:16:29.639> protect<00:16:29.940> the<00:16:30.060> privacy<00:16:30.360> of<00:16:30.540> the 00:16:30.590 --> 00:16:30.600 align:start position:0% important to protect the privacy of the 00:16:30.600 --> 00:16:32.689 align:start position:0% important to protect the privacy of the validators 00:16:32.689 --> 00:16:32.699 align:start position:0% validators 00:16:32.699 --> 00:16:34.730 align:start position:0% validators so<00:16:33.300> what<00:16:33.600> you<00:16:33.839> what<00:16:34.139> do<00:16:34.320> you<00:16:34.320> need<00:16:34.500> to<00:16:34.620> know 00:16:34.730 --> 00:16:34.740 align:start position:0% so what you what do you need to know 00:16:34.740 --> 00:16:35.870 align:start position:0% so what you what do you need to know about<00:16:34.920> this 00:16:35.870 --> 00:16:35.880 align:start position:0% about this 00:16:35.880 --> 00:16:37.610 align:start position:0% about this um<00:16:35.940> yeah<00:16:36.300> because<00:16:36.480> the<00:16:36.720> list<00:16:36.839> of<00:16:37.019> proposal<00:16:37.380> of 00:16:37.610 --> 00:16:37.620 align:start position:0% um yeah because the list of proposal of 00:16:37.620 --> 00:16:39.949 align:start position:0% um yeah because the list of proposal of the<00:16:37.740> new<00:16:37.920> ebook<00:16:38.399> are<00:16:38.699> now<00:16:38.880> it's<00:16:39.300> possible<00:16:39.600> to 00:16:39.949 --> 00:16:39.959 align:start position:0% the new ebook are now it's possible to 00:16:39.959 --> 00:16:43.550 align:start position:0% the new ebook are now it's possible to be<00:16:40.139> uh<00:16:40.860> targeted<00:16:41.279> by<00:16:41.699> these<00:16:42.000> attackers<00:16:42.560> uh 00:16:43.550 --> 00:16:43.560 align:start position:0% be uh targeted by these attackers uh 00:16:43.560 --> 00:16:46.490 align:start position:0% be uh targeted by these attackers uh Disney<00:16:43.740> protocol<00:16:44.279> protects<00:16:45.120> the<00:16:45.360> privacy<00:16:45.720> of 00:16:46.490 --> 00:16:46.500 align:start position:0% Disney protocol protects the privacy of 00:16:46.500 --> 00:16:48.350 align:start position:0% Disney protocol protects the privacy of the<00:16:46.620> evaluators<00:16:47.160> at<00:16:47.459> the<00:16:47.579> moment<00:16:47.699> uh<00:16:48.240> to 00:16:48.350 --> 00:16:48.360 align:start position:0% the evaluators at the moment uh to 00:16:48.360 --> 00:16:51.530 align:start position:0% the evaluators at the moment uh to proposal<00:16:48.959> the<00:16:49.320> block<00:16:49.500> but<00:16:50.160> we<00:16:50.459> need<00:16:50.639> also<00:16:51.180> new 00:16:51.530 --> 00:16:51.540 align:start position:0% proposal the block but we need also new 00:16:51.540 --> 00:16:53.449 align:start position:0% proposal the block but we need also new ways<00:16:52.019> to<00:16:52.259> hide<00:16:52.500> the<00:16:52.740> communication<00:16:53.160> between 00:16:53.449 --> 00:16:53.459 align:start position:0% ways to hide the communication between 00:16:53.459 --> 00:16:56.449 align:start position:0% ways to hide the communication between nodes<00:16:53.880> because<00:16:54.300> that<00:16:54.779> is<00:16:55.079> still<00:16:55.500> spouses<00:16:55.980> so 00:16:56.449 --> 00:16:56.459 align:start position:0% nodes because that is still spouses so 00:16:56.459 --> 00:16:57.889 align:start position:0% nodes because that is still spouses so that<00:16:56.639> is<00:16:56.759> why<00:16:56.940> private<00:16:57.360> Solutions<00:16:57.660> like 00:16:57.889 --> 00:16:57.899 align:start position:0% that is why private Solutions like 00:16:57.899 --> 00:17:00.170 align:start position:0% that is why private Solutions like Hopper<00:16:58.320> or<00:16:58.860> other<00:16:58.980> can<00:16:59.339> provide<00:16:59.639> this<00:16:59.880> kind<00:17:00.060> of 00:17:00.170 --> 00:17:00.180 align:start position:0% Hopper or other can provide this kind of 00:17:00.180 --> 00:17:03.769 align:start position:0% Hopper or other can provide this kind of uh<00:17:00.600> privacy<00:17:01.079> protection<00:17:01.440> at<00:17:01.860> IP<00:17:02.160> level 00:17:03.769 --> 00:17:03.779 align:start position:0% uh privacy protection at IP level 00:17:03.779 --> 00:17:07.730 align:start position:0% uh privacy protection at IP level right<00:17:04.620> next<00:17:05.100> Hot<00:17:05.339> Topic<00:17:06.020> statelessness<00:17:07.020> and 00:17:07.730 --> 00:17:07.740 align:start position:0% right next Hot Topic statelessness and 00:17:07.740 --> 00:17:10.010 align:start position:0% right next Hot Topic statelessness and PBS 00:17:10.010 --> 00:17:10.020 align:start position:0% PBS 00:17:10.020 --> 00:17:13.850 align:start position:0% PBS yeah<00:17:10.679> a<00:17:10.980> good<00:17:11.160> one<00:17:11.339> so<00:17:12.240> yeah<00:17:12.419> this<00:17:12.959> is<00:17:13.079> how<00:17:13.500> this 00:17:13.850 --> 00:17:13.860 align:start position:0% yeah a good one so yeah this is how this 00:17:13.860 --> 00:17:16.669 align:start position:0% yeah a good one so yeah this is how this has<00:17:13.980> been<00:17:14.220> a<00:17:14.459> Hot<00:17:14.640> Topic<00:17:15.059> uh<00:17:15.720> in<00:17:15.959> the<00:17:16.140> research 00:17:16.669 --> 00:17:16.679 align:start position:0% has been a Hot Topic uh in the research 00:17:16.679 --> 00:17:19.189 align:start position:0% has been a Hot Topic uh in the research part<00:17:16.980> of<00:17:17.160> the<00:17:17.280> protocol<00:17:17.640> from<00:17:18.360> uh<00:17:18.839> several 00:17:19.189 --> 00:17:19.199 align:start position:0% part of the protocol from uh several 00:17:19.199 --> 00:17:21.829 align:start position:0% part of the protocol from uh several years<00:17:19.319> ago<00:17:19.620> so<00:17:20.100> mainly<00:17:20.459> the<00:17:20.640> thing<00:17:20.819> that<00:17:21.059> uh<00:17:21.600> we 00:17:21.829 --> 00:17:21.839 align:start position:0% years ago so mainly the thing that uh we 00:17:21.839 --> 00:17:23.990 align:start position:0% years ago so mainly the thing that uh we have<00:17:22.079> now<00:17:22.319> right<00:17:22.679> now<00:17:22.860> is<00:17:23.160> that<00:17:23.400> we<00:17:23.640> need<00:17:23.760> to 00:17:23.990 --> 00:17:24.000 align:start position:0% have now right now is that we need to 00:17:24.000 --> 00:17:26.270 align:start position:0% have now right now is that we need to have<00:17:24.360> all<00:17:24.660> the<00:17:24.839> state<00:17:25.020> of<00:17:25.319> execution<00:17:25.860> client 00:17:26.270 --> 00:17:26.280 align:start position:0% have all the state of execution client 00:17:26.280 --> 00:17:29.210 align:start position:0% have all the state of execution client to<00:17:26.939> be<00:17:27.059> able<00:17:27.179> to<00:17:27.360> be<00:17:27.600> to<00:17:28.079> be<00:17:28.260> able<00:17:28.380> to<00:17:28.500> verify 00:17:29.210 --> 00:17:29.220 align:start position:0% to be able to be to be able to verify 00:17:29.220 --> 00:17:31.370 align:start position:0% to be able to be to be able to verify the<00:17:29.700> next<00:17:29.820> block<00:17:30.059> so<00:17:30.900> this<00:17:31.020> is<00:17:31.140> a<00:17:31.260> problem 00:17:31.370 --> 00:17:31.380 align:start position:0% the next block so this is a problem 00:17:31.380 --> 00:17:33.409 align:start position:0% the next block so this is a problem because<00:17:31.679> we<00:17:32.040> are<00:17:32.160> taking<00:17:32.340> all<00:17:32.820> the<00:17:32.940> complexity 00:17:33.409 --> 00:17:33.419 align:start position:0% because we are taking all the complexity 00:17:33.419 --> 00:17:36.049 align:start position:0% because we are taking all the complexity all<00:17:33.960> the<00:17:34.140> historical<00:17:34.559> data<00:17:34.980> uh<00:17:35.700> from<00:17:35.940> the 00:17:36.049 --> 00:17:36.059 align:start position:0% all the historical data uh from the 00:17:36.059 --> 00:17:39.049 align:start position:0% all the historical data uh from the ethereum<00:17:36.480> and<00:17:36.780> we<00:17:36.960> are<00:17:37.460> need<00:17:38.460> to<00:17:38.640> store<00:17:38.820> this 00:17:39.049 --> 00:17:39.059 align:start position:0% ethereum and we are need to store this 00:17:39.059 --> 00:17:41.870 align:start position:0% ethereum and we are need to store this in<00:17:39.240> in<00:17:39.419> our<00:17:39.660> devices<00:17:40.200> to<00:17:40.500> be<00:17:40.620> a<00:17:40.740> solo<00:17:41.039> stickers 00:17:41.870 --> 00:17:41.880 align:start position:0% in in our devices to be a solo stickers 00:17:41.880 --> 00:17:44.750 align:start position:0% in in our devices to be a solo stickers so<00:17:42.360> mainly<00:17:42.720> the<00:17:43.020> The<00:17:43.080> Proposal<00:17:43.740> is<00:17:44.340> to<00:17:44.460> try<00:17:44.640> to 00:17:44.750 --> 00:17:44.760 align:start position:0% so mainly the The Proposal is to try to 00:17:44.760 --> 00:17:47.510 align:start position:0% so mainly the The Proposal is to try to remove<00:17:44.940> this<00:17:45.299> complexity<00:17:45.919> uh<00:17:46.919> with<00:17:47.100> the<00:17:47.220> idea 00:17:47.510 --> 00:17:47.520 align:start position:0% remove this complexity uh with the idea 00:17:47.520 --> 00:17:49.610 align:start position:0% remove this complexity uh with the idea to<00:17:47.640> be<00:17:47.760> able<00:17:47.880> to<00:17:48.000> verify<00:17:48.480> a<00:17:48.660> block<00:17:48.780> without<00:17:49.260> the 00:17:49.610 --> 00:17:49.620 align:start position:0% to be able to verify a block without the 00:17:49.620 --> 00:17:54.169 align:start position:0% to be able to verify a block without the need<00:17:49.740> of<00:17:50.039> having<00:17:50.520> all<00:17:50.880> the<00:17:51.059> state<00:17:51.380> so<00:17:52.380> the<00:17:53.700> big 00:17:54.169 --> 00:17:54.179 align:start position:0% need of having all the state so the big 00:17:54.179 --> 00:17:56.630 align:start position:0% need of having all the state so the big idea<00:17:54.539> is<00:17:54.900> just<00:17:55.080> to<00:17:55.320> have<00:17:55.500> a<00:17:55.679> goodness<00:17:56.039> of<00:17:56.400> the 00:17:56.630 --> 00:17:56.640 align:start position:0% idea is just to have a goodness of the 00:17:56.640 --> 00:17:59.930 align:start position:0% idea is just to have a goodness of the state<00:17:56.820> at<00:17:57.539> that<00:17:57.960> moment<00:17:58.340> uh<00:17:59.340> and<00:17:59.520> if<00:17:59.700> you<00:17:59.820> have 00:17:59.930 --> 00:17:59.940 align:start position:0% state at that moment uh and if you have 00:17:59.940 --> 00:18:01.909 align:start position:0% state at that moment uh and if you have this<00:18:00.120> proof<00:18:00.419> and<00:18:00.600> it's<00:18:00.780> written<00:18:01.080> it<00:18:01.320> you<00:18:01.799> can 00:18:01.909 --> 00:18:01.919 align:start position:0% this proof and it's written it you can 00:18:01.919 --> 00:18:03.950 align:start position:0% this proof and it's written it you can validate<00:18:02.460> that<00:18:02.640> the<00:18:02.880> transaction<00:18:03.240> from<00:18:03.660> one 00:18:03.950 --> 00:18:03.960 align:start position:0% validate that the transaction from one 00:18:03.960 --> 00:18:07.370 align:start position:0% validate that the transaction from one state<00:18:04.200> to<00:18:04.440> another<00:18:04.620> one<00:18:04.980> is<00:18:05.820> is<00:18:06.179> correct<00:18:06.780> so 00:18:07.370 --> 00:18:07.380 align:start position:0% state to another one is is correct so 00:18:07.380 --> 00:18:10.310 align:start position:0% state to another one is is correct so mainly<00:18:07.820> the<00:18:08.820> good<00:18:09.059> part<00:18:09.240> of<00:18:09.419> this<00:18:09.539> is<00:18:09.720> that<00:18:10.020> we 00:18:10.310 --> 00:18:10.320 align:start position:0% mainly the good part of this is that we 00:18:10.320 --> 00:18:12.710 align:start position:0% mainly the good part of this is that we can<00:18:10.440> remove<00:18:10.679> all<00:18:11.400> the<00:18:11.580> state<00:18:11.760> of<00:18:11.940> ethereum<00:18:12.419> and 00:18:12.710 --> 00:18:12.720 align:start position:0% can remove all the state of ethereum and 00:18:12.720 --> 00:18:16.250 align:start position:0% can remove all the state of ethereum and just<00:18:12.840> to<00:18:13.140> have<00:18:13.380> a<00:18:14.039> a<00:18:14.520> very<00:18:15.360> small<00:18:15.539> proof<00:18:15.900> of<00:18:16.140> the 00:18:16.250 --> 00:18:16.260 align:start position:0% just to have a a very small proof of the 00:18:16.260 --> 00:18:18.770 align:start position:0% just to have a a very small proof of the current<00:18:16.440> state<00:18:16.799> and<00:18:17.039> be<00:18:17.220> able<00:18:17.400> to<00:18:17.460> verify<00:18:17.940> a 00:18:18.770 --> 00:18:18.780 align:start position:0% current state and be able to verify a 00:18:18.780 --> 00:18:21.970 align:start position:0% current state and be able to verify a block<00:18:19.140> so<00:18:19.740> either<00:18:20.280> you're<00:18:20.640> telling<00:18:21.000> me<00:18:21.059> that 00:18:21.970 --> 00:18:21.980 align:start position:0% block so either you're telling me that 00:18:21.980 --> 00:18:26.330 align:start position:0% block so either you're telling me that we<00:18:22.980> if<00:18:23.340> we<00:18:23.520> create<00:18:23.700> a<00:18:24.059> block<00:18:24.299> through<00:18:25.080> this 00:18:26.330 --> 00:18:26.340 align:start position:0% we if we create a block through this 00:18:26.340 --> 00:18:27.830 align:start position:0% we if we create a block through this um<00:18:26.400> through<00:18:26.940> this<00:18:27.059> witness<00:18:27.299> and<00:18:27.539> through<00:18:27.660> this 00:18:27.830 --> 00:18:27.840 align:start position:0% um through this witness and through this 00:18:27.840 --> 00:18:30.470 align:start position:0% um through this witness and through this proof<00:18:28.020> we<00:18:28.200> can<00:18:28.320> prove<00:18:28.799> the<00:18:29.280> only<00:18:29.640> the<00:18:30.059> parts<00:18:30.240> of 00:18:30.470 --> 00:18:30.480 align:start position:0% proof we can prove the only the parts of 00:18:30.480 --> 00:18:32.750 align:start position:0% proof we can prove the only the parts of the<00:18:30.780> state<00:18:31.020> that<00:18:31.740> we<00:18:31.919> need<00:18:32.100> to<00:18:32.400> prove<00:18:32.640> that 00:18:32.750 --> 00:18:32.760 align:start position:0% the state that we need to prove that 00:18:32.760 --> 00:18:34.789 align:start position:0% the state that we need to prove that this<00:18:33.000> block<00:18:33.179> is<00:18:33.480> valid<00:18:33.780> and<00:18:34.140> included<00:18:34.500> in<00:18:34.679> the 00:18:34.789 --> 00:18:34.799 align:start position:0% this block is valid and included in the 00:18:34.799 --> 00:18:37.669 align:start position:0% this block is valid and included in the block<00:18:34.919> itself<00:18:35.400> so<00:18:36.240> a<00:18:36.840> validator<00:18:37.200> of<00:18:37.440> the<00:18:37.559> block 00:18:37.669 --> 00:18:37.679 align:start position:0% block itself so a validator of the block 00:18:37.679 --> 00:18:40.130 align:start position:0% block itself so a validator of the block will<00:18:37.919> be<00:18:38.100> able<00:18:38.460> to<00:18:38.520> look<00:18:38.700> at<00:18:38.880> the<00:18:39.120> Block<00:18:39.299> in 00:18:40.130 --> 00:18:40.140 align:start position:0% will be able to look at the Block in 00:18:40.140 --> 00:18:42.230 align:start position:0% will be able to look at the Block in itself<00:18:40.380> and<00:18:40.679> be<00:18:40.980> able<00:18:41.220> and<00:18:41.760> it'll<00:18:42.000> include 00:18:42.230 --> 00:18:42.240 align:start position:0% itself and be able and it'll include 00:18:42.240 --> 00:18:43.789 align:start position:0% itself and be able and it'll include this<00:18:42.360> person<00:18:42.539> you'll<00:18:42.900> be<00:18:43.020> able<00:18:43.140> to<00:18:43.260> tell<00:18:43.620> if 00:18:43.789 --> 00:18:43.799 align:start position:0% this person you'll be able to tell if 00:18:43.799 --> 00:18:45.890 align:start position:0% this person you'll be able to tell if it's<00:18:43.919> valid<00:18:44.280> or<00:18:44.520> not<00:18:44.640> yeah<00:18:45.000> exactly<00:18:45.419> which 00:18:45.890 --> 00:18:45.900 align:start position:0% it's valid or not yeah exactly which 00:18:45.900 --> 00:18:48.230 align:start position:0% it's valid or not yeah exactly which means<00:18:46.260> which<00:18:46.679> means<00:18:47.160> that<00:18:47.400> we<00:18:47.580> need<00:18:47.760> to<00:18:47.940> link 00:18:48.230 --> 00:18:48.240 align:start position:0% means which means that we need to link 00:18:48.240 --> 00:18:52.430 align:start position:0% means which means that we need to link this<00:18:48.720> with<00:18:49.620> okay<00:18:49.980> so<00:18:50.539> we're<00:18:51.539> we're<00:18:52.200> starting 00:18:52.430 --> 00:18:52.440 align:start position:0% this with okay so we're we're starting 00:18:52.440 --> 00:18:55.909 align:start position:0% this with okay so we're we're starting to<00:18:52.679> separate<00:18:53.039> who<00:18:53.640> thus<00:18:54.179> all<00:18:54.419> of<00:18:54.539> these<00:18:54.960> proof 00:18:55.909 --> 00:18:55.919 align:start position:0% to separate who thus all of these proof 00:18:55.919 --> 00:18:58.130 align:start position:0% to separate who thus all of these proof production<00:18:56.340> and<00:18:57.120> who<00:18:57.360> does<00:18:57.539> the<00:18:57.720> validator 00:18:58.130 --> 00:18:58.140 align:start position:0% production and who does the validator 00:18:58.140 --> 00:19:00.230 align:start position:0% production and who does the validator work<00:18:58.440> so 00:19:00.230 --> 00:19:00.240 align:start position:0% work so 00:19:00.240 --> 00:19:04.190 align:start position:0% work so yeah<00:19:00.900> PBS<00:19:01.799> PBS<00:19:02.400> is<00:19:02.700> going<00:19:02.820> to<00:19:02.940> be<00:19:03.059> also<00:19:03.660> a<00:19:04.020> very 00:19:04.190 --> 00:19:04.200 align:start position:0% yeah PBS PBS is going to be also a very 00:19:04.200 --> 00:19:06.110 align:start position:0% yeah PBS PBS is going to be also a very important<00:19:04.500> part<00:19:04.740> of<00:19:04.860> the<00:19:04.980> protocol<00:19:05.280> uh 00:19:06.110 --> 00:19:06.120 align:start position:0% important part of the protocol uh 00:19:06.120 --> 00:19:08.029 align:start position:0% important part of the protocol uh because<00:19:06.360> they<00:19:06.720> think<00:19:07.200> that<00:19:07.440> Paul<00:19:07.799> just 00:19:08.029 --> 00:19:08.039 align:start position:0% because they think that Paul just 00:19:08.039 --> 00:19:10.070 align:start position:0% because they think that Paul just mentioned<00:19:08.460> so<00:19:08.760> mainly<00:19:09.059> the<00:19:09.179> idea<00:19:09.360> is<00:19:09.600> that<00:19:09.900> we 00:19:10.070 --> 00:19:10.080 align:start position:0% mentioned so mainly the idea is that we 00:19:10.080 --> 00:19:11.630 align:start position:0% mentioned so mainly the idea is that we are<00:19:10.260> going<00:19:10.380> to<00:19:10.440> split<00:19:10.860> the<00:19:10.980> roles<00:19:11.280> on<00:19:11.520> the 00:19:11.630 --> 00:19:11.640 align:start position:0% are going to split the roles on the 00:19:11.640 --> 00:19:13.789 align:start position:0% are going to split the roles on the network<00:19:11.760> we<00:19:12.360> are<00:19:12.539> going<00:19:12.660> to<00:19:12.780> have<00:19:13.080> proposal 00:19:13.789 --> 00:19:13.799 align:start position:0% network we are going to have proposal 00:19:13.799 --> 00:19:16.850 align:start position:0% network we are going to have proposal and<00:19:14.640> uh<00:19:15.000> and<00:19:15.419> blood<00:19:15.780> producers 00:19:16.850 --> 00:19:16.860 align:start position:0% and uh and blood producers 00:19:16.860 --> 00:19:19.370 align:start position:0% and uh and blood producers so<00:19:17.160> my<00:19:17.340> lead<00:19:17.520> idea<00:19:17.820> is<00:19:18.299> that<00:19:18.660> the<00:19:18.960> block 00:19:19.370 --> 00:19:19.380 align:start position:0% so my lead idea is that the block 00:19:19.380 --> 00:19:21.049 align:start position:0% so my lead idea is that the block producer<00:19:19.919> is<00:19:20.039> the<00:19:20.280> one<00:19:20.400> that<00:19:20.640> is<00:19:20.760> going<00:19:20.940> to 00:19:21.049 --> 00:19:21.059 align:start position:0% producer is the one that is going to 00:19:21.059 --> 00:19:23.029 align:start position:0% producer is the one that is going to create<00:19:21.360> all<00:19:21.780> of<00:19:21.960> these<00:19:22.200> to<00:19:22.440> generate<00:19:22.919> the 00:19:23.029 --> 00:19:23.039 align:start position:0% create all of these to generate the 00:19:23.039 --> 00:19:25.789 align:start position:0% create all of these to generate the equitness<00:19:23.419> and<00:19:24.419> and<00:19:24.840> is<00:19:25.140> the<00:19:25.380> one<00:19:25.500> that<00:19:25.679> is 00:19:25.789 --> 00:19:25.799 align:start position:0% equitness and and is the one that is 00:19:25.799 --> 00:19:30.110 align:start position:0% equitness and and is the one that is going<00:19:26.039> to<00:19:26.160> take<00:19:26.700> this<00:19:27.120> uh<00:19:27.660> High<00:19:27.900> computation 00:19:30.110 --> 00:19:30.120 align:start position:0% going to take this uh High computation 00:19:30.120 --> 00:19:32.330 align:start position:0% going to take this uh High computation um<00:19:30.500> we<00:19:31.500> don't<00:19:31.559> have<00:19:31.679> too<00:19:31.799> much<00:19:31.919> time<00:19:32.039> right 00:19:32.330 --> 00:19:32.340 align:start position:0% um we don't have too much time right 00:19:32.340 --> 00:19:34.430 align:start position:0% um we don't have too much time right okay 00:19:34.430 --> 00:19:34.440 align:start position:0% okay 00:19:34.440 --> 00:19:36.830 align:start position:0% okay um<00:19:34.500> so<00:19:34.860> yeah<00:19:35.039> the<00:19:35.340> idea<00:19:35.520> is<00:19:35.640> just<00:19:35.880> to<00:19:36.179> put<00:19:36.660> all 00:19:36.830 --> 00:19:36.840 align:start position:0% um so yeah the idea is just to put all 00:19:36.840 --> 00:19:38.570 align:start position:0% um so yeah the idea is just to put all this<00:19:36.960> computation<00:19:37.440> in<00:19:37.799> the<00:19:37.860> block<00:19:37.980> producers 00:19:38.570 --> 00:19:38.580 align:start position:0% this computation in the block producers 00:19:38.580 --> 00:19:41.029 align:start position:0% this computation in the block producers and<00:19:39.000> the<00:19:39.120> validators<00:19:39.660> are<00:19:39.840> going<00:19:39.960> to<00:19:40.080> be<00:19:40.260> more 00:19:41.029 --> 00:19:41.039 align:start position:0% and the validators are going to be more 00:19:41.039 --> 00:19:42.710 align:start position:0% and the validators are going to be more or<00:19:41.160> less<00:19:41.280> the<00:19:41.460> same<00:19:41.640> so<00:19:42.059> they<00:19:42.240> only<00:19:42.419> need<00:19:42.600> to 00:19:42.710 --> 00:19:42.720 align:start position:0% or less the same so they only need to 00:19:42.720 --> 00:19:47.270 align:start position:0% or less the same so they only need to validate<00:19:43.140> this<00:19:43.380> proof<00:19:43.799> in<00:19:44.280> a<00:19:44.460> short<00:19:44.700> way 00:19:47.270 --> 00:19:47.280 align:start position:0% validate this proof in a short way 00:19:47.280 --> 00:19:50.150 align:start position:0% validate this proof in a short way so<00:19:47.880> what<00:19:48.120> do<00:19:48.240> we<00:19:48.360> need<00:19:48.480> to<00:19:48.600> know<00:19:49.200> yeah<00:19:49.740> mainly 00:19:50.150 --> 00:19:50.160 align:start position:0% so what do we need to know yeah mainly 00:19:50.160 --> 00:19:52.070 align:start position:0% so what do we need to know yeah mainly mainly<00:19:50.640> that<00:19:50.820> the<00:19:51.000> hardware<00:19:51.299> government<00:19:51.660> for 00:19:52.070 --> 00:19:52.080 align:start position:0% mainly that the hardware government for 00:19:52.080 --> 00:19:53.990 align:start position:0% mainly that the hardware government for holding<00:19:52.440> the<00:19:52.559> state<00:19:52.679> disappears<00:19:53.280> and<00:19:53.700> that<00:19:53.880> is 00:19:53.990 --> 00:19:54.000 align:start position:0% holding the state disappears and that is 00:19:54.000 --> 00:19:56.029 align:start position:0% holding the state disappears and that is really<00:19:54.179> really<00:19:54.360> good<00:19:54.660> and<00:19:55.320> also<00:19:55.559> if<00:19:55.679> we<00:19:55.860> link 00:19:56.029 --> 00:19:56.039 align:start position:0% really really good and also if we link 00:19:56.039 --> 00:19:58.190 align:start position:0% really really good and also if we link with<00:19:56.340> the<00:19:56.580> blocked<00:19:57.120> things<00:19:57.299> it's<00:19:57.600> like<00:19:57.840> oh 00:19:58.190 --> 00:19:58.200 align:start position:0% with the blocked things it's like oh 00:19:58.200 --> 00:20:00.710 align:start position:0% with the blocked things it's like oh okay<00:19:58.440> we<00:19:58.799> are<00:19:58.980> getting<00:19:59.520> more<00:19:59.820> space<00:20:00.120> here<00:20:00.360> and 00:20:00.710 --> 00:20:00.720 align:start position:0% okay we are getting more space here and 00:20:00.720 --> 00:20:02.390 align:start position:0% okay we are getting more space here and we<00:20:00.900> are<00:20:01.020> putting<00:20:01.320> block<00:20:01.500> there<00:20:01.799> so<00:20:02.100> more<00:20:02.220> or 00:20:02.390 --> 00:20:02.400 align:start position:0% we are putting block there so more or 00:20:02.400 --> 00:20:04.669 align:start position:0% we are putting block there so more or less<00:20:02.460> we<00:20:02.700> are<00:20:02.820> going<00:20:02.880> to<00:20:02.940> be<00:20:03.059> the<00:20:03.240> same<00:20:03.500> uh<00:20:04.500> he's 00:20:04.669 --> 00:20:04.679 align:start position:0% less we are going to be the same uh he's 00:20:04.679 --> 00:20:06.830 align:start position:0% less we are going to be the same uh he's going<00:20:04.919> to<00:20:04.980> increase<00:20:05.100> the<00:20:05.400> bandwidth<00:20:05.880> uh<00:20:06.600> but 00:20:06.830 --> 00:20:06.840 align:start position:0% going to increase the bandwidth uh but 00:20:06.840 --> 00:20:08.810 align:start position:0% going to increase the bandwidth uh but not<00:20:06.960> too<00:20:07.140> much<00:20:07.320> because<00:20:07.740> we<00:20:08.280> are<00:20:08.520> going<00:20:08.640> to 00:20:08.810 --> 00:20:08.820 align:start position:0% not too much because we are going to 00:20:08.820 --> 00:20:11.029 align:start position:0% not too much because we are going to move<00:20:08.940> for<00:20:09.179> from<00:20:09.600> producer<00:20:10.380> medical<00:20:10.500> trees<00:20:10.860> to 00:20:11.029 --> 00:20:11.039 align:start position:0% move for from producer medical trees to 00:20:11.039 --> 00:20:13.310 align:start position:0% move for from producer medical trees to Vertical<00:20:11.460> trees<00:20:11.760> that<00:20:12.059> are<00:20:12.360> more<00:20:12.960> efficient 00:20:13.310 --> 00:20:13.320 align:start position:0% Vertical trees that are more efficient 00:20:13.320 --> 00:20:16.850 align:start position:0% Vertical trees that are more efficient ways<00:20:14.100> to<00:20:14.220> prove<00:20:14.520> the<00:20:14.640> state<00:20:15.080> uh<00:20:16.080> so<00:20:16.260> mainly<00:20:16.559> as 00:20:16.850 --> 00:20:16.860 align:start position:0% ways to prove the state uh so mainly as 00:20:16.860 --> 00:20:19.070 align:start position:0% ways to prove the state uh so mainly as a<00:20:17.039> validator<00:20:17.400> I<00:20:18.000> think<00:20:18.179> the<00:20:18.480> result<00:20:18.660> is<00:20:18.900> going 00:20:19.070 --> 00:20:19.080 align:start position:0% a validator I think the result is going 00:20:19.080 --> 00:20:21.350 align:start position:0% a validator I think the result is going to<00:20:19.200> be<00:20:19.260> more<00:20:19.559> or<00:20:19.740> less<00:20:19.799> same<00:20:20.100> uh<00:20:20.820> it<00:20:21.059> has<00:20:21.179> been 00:20:21.350 --> 00:20:21.360 align:start position:0% to be more or less same uh it has been 00:20:21.360 --> 00:20:24.950 align:start position:0% to be more or less same uh it has been always<00:20:21.539> a<00:20:22.140> a<00:20:22.860> need<00:20:23.100> that<00:20:23.600> evaluators<00:20:24.600> needs<00:20:24.900> to 00:20:24.950 --> 00:20:24.960 align:start position:0% always a a need that evaluators needs to 00:20:24.960 --> 00:20:27.950 align:start position:0% always a a need that evaluators needs to be<00:20:25.080> running<00:20:25.320> Uh<00:20:25.740> custom<00:20:26.160> Hardware<00:20:26.580> so<00:20:27.299> we<00:20:27.660> keep 00:20:27.950 --> 00:20:27.960 align:start position:0% be running Uh custom Hardware so we keep 00:20:27.960 --> 00:20:29.870 align:start position:0% be running Uh custom Hardware so we keep on<00:20:28.260> that<00:20:28.440> level 00:20:29.870 --> 00:20:29.880 align:start position:0% on that level 00:20:29.880 --> 00:20:32.510 align:start position:0% on that level okay<00:20:30.480> I'm<00:20:31.020> gonna<00:20:31.200> take<00:20:31.500> the<00:20:31.799> Dan<00:20:31.980> shot<00:20:32.280> the 00:20:32.510 --> 00:20:32.520 align:start position:0% okay I'm gonna take the Dan shot the 00:20:32.520 --> 00:20:34.669 align:start position:0% okay I'm gonna take the Dan shot the Dank<00:20:32.700> sharding<00:20:33.179> and<00:20:33.960> data<00:20:34.380> availability 00:20:34.669 --> 00:20:34.679 align:start position:0% Dank sharding and data availability 00:20:34.679 --> 00:20:36.289 align:start position:0% Dank sharding and data availability sampling 00:20:36.289 --> 00:20:36.299 align:start position:0% sampling 00:20:36.299 --> 00:20:38.330 align:start position:0% sampling um<00:20:36.360> okay<00:20:36.720> so<00:20:37.140> this<00:20:37.500> is<00:20:37.559> going<00:20:37.679> to<00:20:37.799> be<00:20:37.919> the<00:20:38.160> last 00:20:38.330 --> 00:20:38.340 align:start position:0% um okay so this is going to be the last 00:20:38.340 --> 00:20:42.110 align:start position:0% um okay so this is going to be the last thing<00:20:38.580> and<00:20:39.419> the<00:20:40.260> key<00:20:40.500> part<00:20:40.799> to<00:20:41.280> that<00:20:41.820> solo 00:20:42.110 --> 00:20:42.120 align:start position:0% thing and the key part to that solo 00:20:42.120 --> 00:20:43.370 align:start position:0% thing and the key part to that solo stickers<00:20:42.419> need<00:20:42.600> to<00:20:42.720> know<00:20:42.840> right<00:20:43.080> now<00:20:43.200> about 00:20:43.370 --> 00:20:43.380 align:start position:0% stickers need to know right now about 00:20:43.380 --> 00:20:47.330 align:start position:0% stickers need to know right now about this<00:20:43.740> is<00:20:44.400> that<00:20:45.120> we<00:20:45.840> do<00:20:46.020> not<00:20:46.200> know<00:20:46.559> which<00:20:47.100> are 00:20:47.330 --> 00:20:47.340 align:start position:0% this is that we do not know which are 00:20:47.340 --> 00:20:51.470 align:start position:0% this is that we do not know which are the<00:20:47.520> consequences<00:20:48.179> that<00:20:48.960> it<00:20:49.140> will<00:20:49.320> have<00:20:49.980> so 00:20:51.470 --> 00:20:51.480 align:start position:0% the consequences that it will have so 00:20:51.480 --> 00:20:53.510 align:start position:0% the consequences that it will have so we<00:20:52.080> cannot<00:20:52.440> possibly<00:20:52.860> know<00:20:53.100> right<00:20:53.400> now 00:20:53.510 --> 00:20:53.520 align:start position:0% we cannot possibly know right now 00:20:53.520 --> 00:20:54.950 align:start position:0% we cannot possibly know right now because<00:20:53.760> there's<00:20:54.120> not<00:20:54.419> a<00:20:54.720> specific 00:20:54.950 --> 00:20:54.960 align:start position:0% because there's not a specific 00:20:54.960 --> 00:20:56.630 align:start position:0% because there's not a specific implementation<00:20:55.559> of<00:20:55.980> the<00:20:56.160> data<00:20:56.400> availability 00:20:56.630 --> 00:20:56.640 align:start position:0% implementation of the data availability 00:20:56.640 --> 00:20:59.450 align:start position:0% implementation of the data availability sampling<00:20:57.419> so<00:20:57.660> database<00:20:58.200> example<00:20:58.860> what<00:20:59.340> it 00:20:59.450 --> 00:20:59.460 align:start position:0% sampling so database example what it 00:20:59.460 --> 00:21:01.789 align:start position:0% sampling so database example what it will<00:20:59.580> allow<00:20:59.880> us<00:21:00.000> is<00:21:00.539> to<00:21:00.720> remember<00:21:00.900> those<00:21:01.320> Blobs 00:21:01.789 --> 00:21:01.799 align:start position:0% will allow us is to remember those Blobs 00:21:01.799 --> 00:21:04.730 align:start position:0% will allow us is to remember those Blobs of<00:21:02.039> data<00:21:02.460> that<00:21:02.940> we<00:21:03.120> have<00:21:03.240> mentioned<00:21:03.600> before<00:21:03.840> so 00:21:04.730 --> 00:21:04.740 align:start position:0% of data that we have mentioned before so 00:21:04.740 --> 00:21:07.850 align:start position:0% of data that we have mentioned before so these<00:21:05.039> Blobs<00:21:05.400> of<00:21:05.520> data<00:21:06.000> will<00:21:06.600> not<00:21:07.020> necessarily 00:21:07.850 --> 00:21:07.860 align:start position:0% these Blobs of data will not necessarily 00:21:07.860 --> 00:21:11.029 align:start position:0% these Blobs of data will not necessarily be<00:21:08.480> uh<00:21:09.480> fully<00:21:09.840> downloaded<00:21:10.200> we<00:21:10.440> will<00:21:10.799> be<00:21:10.919> able 00:21:11.029 --> 00:21:11.039 align:start position:0% be uh fully downloaded we will be able 00:21:11.039 --> 00:21:13.490 align:start position:0% be uh fully downloaded we will be able to<00:21:11.160> just<00:21:11.400> prove<00:21:11.820> a<00:21:12.059> sample<00:21:12.419> of<00:21:12.720> this<00:21:12.960> to<00:21:13.140> take<00:21:13.320> a 00:21:13.490 --> 00:21:13.500 align:start position:0% to just prove a sample of this to take a 00:21:13.500 --> 00:21:16.190 align:start position:0% to just prove a sample of this to take a sample<00:21:13.799> of<00:21:14.039> this<00:21:14.220> data<00:21:14.580> and<00:21:15.120> prove<00:21:15.539> somehow 00:21:16.190 --> 00:21:16.200 align:start position:0% sample of this data and prove somehow 00:21:16.200 --> 00:21:17.570 align:start position:0% sample of this data and prove somehow that 00:21:17.570 --> 00:21:17.580 align:start position:0% that 00:21:17.580 --> 00:21:19.370 align:start position:0% that um<00:21:17.640> that<00:21:18.000> this<00:21:18.120> exists<00:21:18.600> and<00:21:18.840> this<00:21:18.960> is<00:21:19.080> valid 00:21:19.370 --> 00:21:19.380 align:start position:0% um that this exists and this is valid 00:21:19.380 --> 00:21:22.310 align:start position:0% um that this exists and this is valid and<00:21:19.500> available<00:21:19.740> for<00:21:20.100> download<00:21:20.340> but<00:21:21.240> we<00:21:22.020> do<00:21:22.140> not 00:21:22.310 --> 00:21:22.320 align:start position:0% and available for download but we do not 00:21:22.320 --> 00:21:25.310 align:start position:0% and available for download but we do not know<00:21:22.620> yet<00:21:23.340> what's<00:21:24.000> going<00:21:24.240> to<00:21:24.360> be<00:21:24.480> for<00:21:24.900> solo 00:21:25.310 --> 00:21:25.320 align:start position:0% know yet what's going to be for solo 00:21:25.320 --> 00:21:26.630 align:start position:0% know yet what's going to be for solo stickers<00:21:25.620> because<00:21:25.799> there's<00:21:26.039> too<00:21:26.460> many 00:21:26.630 --> 00:21:26.640 align:start position:0% stickers because there's too many 00:21:26.640 --> 00:21:28.370 align:start position:0% stickers because there's too many there's<00:21:27.120> too<00:21:27.299> many<00:21:27.360> moving<00:21:27.720> pieces<00:21:28.020> and<00:21:28.140> this 00:21:28.370 --> 00:21:28.380 align:start position:0% there's too many moving pieces and this 00:21:28.380 --> 00:21:30.409 align:start position:0% there's too many moving pieces and this is<00:21:28.500> way<00:21:28.799> too<00:21:29.039> far<00:21:29.220> away<00:21:29.400> so<00:21:29.760> for<00:21:30.000> the<00:21:30.240> moment 00:21:30.409 --> 00:21:30.419 align:start position:0% is way too far away so for the moment 00:21:30.419 --> 00:21:32.149 align:start position:0% is way too far away so for the moment for<00:21:30.720> Solace<00:21:31.020> takers<00:21:31.320> what<00:21:31.440> it<00:21:31.559> matters<00:21:31.799> is<00:21:31.919> the 00:21:32.149 --> 00:21:32.159 align:start position:0% for Solace takers what it matters is the 00:21:32.159 --> 00:21:34.070 align:start position:0% for Solace takers what it matters is the Proto<00:21:32.460> dank<00:21:32.640> sharding<00:21:33.059> the<00:21:33.419> existence<00:21:33.780> of 00:21:34.070 --> 00:21:34.080 align:start position:0% Proto dank sharding the existence of 00:21:34.080 --> 00:21:37.909 align:start position:0% Proto dank sharding the existence of this<00:21:34.380> data<00:21:35.039> blobs<00:21:35.760> Etc<00:21:35.940> so<00:21:36.840> to<00:21:37.140> summarize<00:21:37.559> very 00:21:37.909 --> 00:21:37.919 align:start position:0% this data blobs Etc so to summarize very 00:21:37.919 --> 00:21:39.950 align:start position:0% this data blobs Etc so to summarize very very<00:21:38.100> quickly<00:21:38.400> on<00:21:39.179> the<00:21:39.360> topics<00:21:39.600> that<00:21:39.720> we<00:21:39.900> have 00:21:39.950 --> 00:21:39.960 align:start position:0% very quickly on the topics that we have 00:21:39.960 --> 00:21:42.710 align:start position:0% very quickly on the topics that we have spoken<00:21:40.320> Mev<00:21:41.100> it's<00:21:41.580> a<00:21:41.700> bug<00:21:41.880> not<00:21:42.179> a<00:21:42.360> feature<00:21:42.600> it's 00:21:42.710 --> 00:21:42.720 align:start position:0% spoken Mev it's a bug not a feature it's 00:21:42.720 --> 00:21:45.110 align:start position:0% spoken Mev it's a bug not a feature it's a<00:21:42.840> centralizing<00:21:43.440> force<00:21:43.860> and<00:21:44.340> it<00:21:44.640> screws<00:21:44.940> up 00:21:45.110 --> 00:21:45.120 align:start position:0% a centralizing force and it screws up 00:21:45.120 --> 00:21:47.450 align:start position:0% a centralizing force and it screws up our<00:21:45.360> Center<00:21:45.539> our<00:21:45.960> censorship<00:21:46.380> resistance<00:21:46.919> for 00:21:47.450 --> 00:21:47.460 align:start position:0% our Center our censorship resistance for 00:21:47.460 --> 00:21:50.149 align:start position:0% our Center our censorship resistance for DBT<00:21:48.000> we<00:21:48.539> will<00:21:48.720> be<00:21:48.840> able<00:21:49.200> to<00:21:49.620> leverage<00:21:49.860> our 00:21:50.149 --> 00:21:50.159 align:start position:0% DBT we will be able to leverage our 00:21:50.159 --> 00:21:52.970 align:start position:0% DBT we will be able to leverage our setups<00:21:50.640> to<00:21:50.880> earn<00:21:51.120> extra<00:21:51.299> rewards<00:21:51.960> for<00:21:52.799> the 00:21:52.970 --> 00:21:52.980 align:start position:0% setups to earn extra rewards for the 00:21:52.980 --> 00:21:54.890 align:start position:0% setups to earn extra rewards for the withdrawals<00:21:53.580> pretty<00:21:54.059> self-explanatory 00:21:54.890 --> 00:21:54.900 align:start position:0% withdrawals pretty self-explanatory 00:21:54.900 --> 00:21:56.630 align:start position:0% withdrawals pretty self-explanatory we'll<00:21:55.380> be<00:21:55.620> able<00:21:55.740> to<00:21:55.799> take<00:21:55.919> our<00:21:56.039> deposits<00:21:56.580> Out 00:21:56.630 --> 00:21:56.640 align:start position:0% we'll be able to take our deposits Out 00:21:56.640 --> 00:21:59.330 align:start position:0% we'll be able to take our deposits Out product<00:21:57.299> sharding<00:21:58.140> our<00:21:58.500> consensus<00:21:59.039> layer 00:21:59.330 --> 00:21:59.340 align:start position:0% product sharding our consensus layer 00:21:59.340 --> 00:22:01.010 align:start position:0% product sharding our consensus layer will<00:21:59.520> grow<00:21:59.760> with<00:22:00.120> these<00:22:00.299> Blobs<00:22:00.600> of<00:22:00.720> data 00:22:01.010 --> 00:22:01.020 align:start position:0% will grow with these Blobs of data 00:22:01.020 --> 00:22:03.830 align:start position:0% will grow with these Blobs of data validator<00:22:01.740> anonymity<00:22:02.280> a<00:22:03.240> single<00:22:03.659> secret 00:22:03.830 --> 00:22:03.840 align:start position:0% validator anonymity a single secret 00:22:03.840 --> 00:22:05.630 align:start position:0% validator anonymity a single secret leader<00:22:04.320> election<00:22:04.500> will<00:22:04.980> save<00:22:05.159> us<00:22:05.280> from<00:22:05.520> the 00:22:05.630 --> 00:22:05.640 align:start position:0% leader election will save us from the 00:22:05.640 --> 00:22:07.549 align:start position:0% leader election will save us from the Mev<00:22:06.059> extractors<00:22:06.539> that<00:22:06.720> come<00:22:06.840> behind<00:22:07.140> us<00:22:07.320> and 00:22:07.549 --> 00:22:07.559 align:start position:0% Mev extractors that come behind us and 00:22:07.559 --> 00:22:10.430 align:start position:0% Mev extractors that come behind us and they<00:22:07.740> wanna<00:22:08.400> get<00:22:08.880> us<00:22:09.059> offline<00:22:09.419> to<00:22:09.659> get<00:22:09.840> the<00:22:10.080> Mev 00:22:10.430 --> 00:22:10.440 align:start position:0% they wanna get us offline to get the Mev 00:22:10.440 --> 00:22:13.070 align:start position:0% they wanna get us offline to get the Mev opportunities<00:22:11.000> statelessness<00:22:12.000> is<00:22:12.720> that<00:22:12.900> we 00:22:13.070 --> 00:22:13.080 align:start position:0% opportunities statelessness is that we 00:22:13.080 --> 00:22:15.590 align:start position:0% opportunities statelessness is that we will<00:22:13.260> have<00:22:13.559> less<00:22:14.039> less<00:22:14.700> Drive<00:22:14.940> requirements 00:22:15.590 --> 00:22:15.600 align:start position:0% will have less less Drive requirements 00:22:15.600 --> 00:22:18.350 align:start position:0% will have less less Drive requirements but<00:22:15.960> we<00:22:16.140> will<00:22:16.320> have<00:22:16.559> more<00:22:16.980> bandwidth<00:22:17.520> and<00:22:18.059> dunk 00:22:18.350 --> 00:22:18.360 align:start position:0% but we will have more bandwidth and dunk 00:22:18.360 --> 00:22:22.070 align:start position:0% but we will have more bandwidth and dunk sharding<00:22:18.840> that<00:22:19.740> we<00:22:20.220> don't<00:22:20.640> really<00:22:21.120> know<00:22:21.299> so<00:22:21.960> in 00:22:22.070 --> 00:22:22.080 align:start position:0% sharding that we don't really know so in 00:22:22.080 --> 00:22:24.409 align:start position:0% sharding that we don't really know so in 25<00:22:22.200> minutes<00:22:22.620> this<00:22:23.400> is<00:22:23.520> everything<00:22:23.760> you<00:22:24.120> needed 00:22:24.409 --> 00:22:24.419 align:start position:0% 25 minutes this is everything you needed 00:22:24.419 --> 00:22:27.950 align:start position:0% 25 minutes this is everything you needed to<00:22:24.539> know<00:22:24.720> about<00:22:25.500> the<00:22:25.980> next<00:22:26.100> phase<00:22:26.400> of<00:22:26.940> ethereum 00:22:27.950 --> 00:22:27.960 align:start position:0% to know about the next phase of ethereum 00:22:27.960 --> 00:22:28.880 align:start position:0% to know about the next phase of ethereum thank<00:22:28.380> you<00:22:28.500> very<00:22:28.559> much 00:22:28.880 --> 00:22:28.890 align:start position:0% thank you very much 00:22:28.890 --> 00:22:37.999 align:start position:0% thank you very much [Applause]