WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.270 align:start position:0% [Music] 00:00:09.270 --> 00:00:09.280 align:start position:0% [Music] 00:00:09.280 --> 00:00:12.629 align:start position:0% [Music] it<00:00:09.559> it<00:00:09.679> is<00:00:10.040> right<00:00:11.040> okay<00:00:11.320> so<00:00:11.880> yeah<00:00:12.080> I'm<00:00:12.240> Lucas 00:00:12.629 --> 00:00:12.639 align:start position:0% it it is right okay so yeah I'm Lucas 00:00:12.639 --> 00:00:15.110 align:start position:0% it it is right okay so yeah I'm Lucas and<00:00:12.759> I've<00:00:12.920> got<00:00:13.080> Stefan<00:00:13.480> here<00:00:13.639> with<00:00:13.799> me<00:00:14.599> um<00:00:14.920> our 00:00:15.110 --> 00:00:15.120 align:start position:0% and I've got Stefan here with me um our 00:00:15.120 --> 00:00:17.630 align:start position:0% and I've got Stefan here with me um our talk<00:00:15.519> was<00:00:15.920> originally<00:00:16.400> designed<00:00:16.800> to<00:00:16.960> be<00:00:17.199> two 00:00:17.630 --> 00:00:17.640 align:start position:0% talk was originally designed to be two 00:00:17.640 --> 00:00:20.429 align:start position:0% talk was originally designed to be two talks<00:00:18.640> but<00:00:18.840> do<00:00:19.080> some<00:00:19.359> scheding<00:00:19.920> things<00:00:20.160> we<00:00:20.279> had 00:00:20.429 --> 00:00:20.439 align:start position:0% talks but do some scheding things we had 00:00:20.439 --> 00:00:23.150 align:start position:0% talks but do some scheding things we had to<00:00:20.519> merge<00:00:20.880> them<00:00:21.199> together<00:00:21.680> so<00:00:22.680> well<00:00:22.840> we'll<00:00:23.039> do 00:00:23.150 --> 00:00:23.160 align:start position:0% to merge them together so well we'll do 00:00:23.160 --> 00:00:24.470 align:start position:0% to merge them together so well we'll do our<00:00:23.320> best<00:00:23.439> to<00:00:23.640> make<00:00:23.760> sure<00:00:24.000> we<00:00:24.080> go<00:00:24.199> through<00:00:24.359> the 00:00:24.470 --> 00:00:24.480 align:start position:0% our best to make sure we go through the 00:00:24.480 --> 00:00:25.710 align:start position:0% our best to make sure we go through the content<00:00:24.800> and<00:00:24.920> everyone<00:00:25.439> understands 00:00:25.710 --> 00:00:25.720 align:start position:0% content and everyone understands 00:00:25.720 --> 00:00:28.109 align:start position:0% content and everyone understands everything<00:00:26.720> so<00:00:27.119> yeah<00:00:27.279> I'll<00:00:27.439> start<00:00:27.679> with<00:00:27.840> my 00:00:28.109 --> 00:00:28.119 align:start position:0% everything so yeah I'll start with my 00:00:28.119 --> 00:00:29.550 align:start position:0% everything so yeah I'll start with my part<00:00:28.320> and<00:00:28.439> then<00:00:28.599> we're<00:00:28.800> going<00:00:28.880> to<00:00:29.000> have<00:00:29.160> Stefan 00:00:29.550 --> 00:00:29.560 align:start position:0% part and then we're going to have Stefan 00:00:29.560 --> 00:00:32.430 align:start position:0% part and then we're going to have Stefan thank<00:00:29.720> you<00:00:30.000> St<00:00:30.359> thank 00:00:32.430 --> 00:00:32.440 align:start position:0% thank you St thank 00:00:32.440 --> 00:00:35.630 align:start position:0% thank you St thank you<00:00:33.640> okay<00:00:34.640> so<00:00:34.960> we're<00:00:35.079> going<00:00:35.200> to<00:00:35.280> start<00:00:35.480> with 00:00:35.630 --> 00:00:35.640 align:start position:0% you okay so we're going to start with 00:00:35.640 --> 00:00:39.590 align:start position:0% you okay so we're going to start with EIP<00:00:36.280> 70002<00:00:37.280> execution<00:00:37.760> layer<00:00:38.160> triggerable 00:00:39.590 --> 00:00:39.600 align:start position:0% EIP 70002 execution layer triggerable 00:00:39.600 --> 00:00:41.869 align:start position:0% EIP 70002 execution layer triggerable withdrawals<00:00:40.600> before<00:00:40.920> it<00:00:41.079> was<00:00:41.280> named 00:00:41.869 --> 00:00:41.879 align:start position:0% withdrawals before it was named 00:00:41.879 --> 00:00:44.590 align:start position:0% withdrawals before it was named execution<00:00:42.360> layer<00:00:42.640> triggerable<00:00:43.520> exits<00:00:44.079> but 00:00:44.590 --> 00:00:44.600 align:start position:0% execution layer triggerable exits but 00:00:44.600 --> 00:00:46.830 align:start position:0% execution layer triggerable exits but there<00:00:44.719> are<00:00:44.879> some<00:00:45.039> updates<00:00:45.520> that<00:00:45.879> um<00:00:46.440> made<00:00:46.680> we 00:00:46.830 --> 00:00:46.840 align:start position:0% there are some updates that um made we 00:00:46.840 --> 00:00:49.110 align:start position:0% there are some updates that um made we renamed<00:00:47.239> the<00:00:47.399> zip<00:00:48.320> before<00:00:48.600> talking<00:00:48.840> about<00:00:49.000> the 00:00:49.110 --> 00:00:49.120 align:start position:0% renamed the zip before talking about the 00:00:49.120 --> 00:00:50.830 align:start position:0% renamed the zip before talking about the EIP<00:00:49.559> I<00:00:49.640> want<00:00:49.760> to<00:00:49.960> go<00:00:50.160> through<00:00:50.360> a<00:00:50.480> little<00:00:50.640> bit<00:00:50.760> of 00:00:50.830 --> 00:00:50.840 align:start position:0% EIP I want to go through a little bit of 00:00:50.840 --> 00:00:52.910 align:start position:0% EIP I want to go through a little bit of a<00:00:51.000> context<00:00:51.480> here<00:00:51.879> so<00:00:52.320> I'm<00:00:52.440> assuming<00:00:52.719> that 00:00:52.910 --> 00:00:52.920 align:start position:0% a context here so I'm assuming that 00:00:52.920 --> 00:00:55.189 align:start position:0% a context here so I'm assuming that everyone<00:00:53.359> is<00:00:53.520> aware<00:00:54.359> that<00:00:54.520> in<00:00:54.680> ethereum<00:00:55.079> we 00:00:55.189 --> 00:00:55.199 align:start position:0% everyone is aware that in ethereum we 00:00:55.199 --> 00:00:58.509 align:start position:0% everyone is aware that in ethereum we have<00:00:55.359> validators<00:00:56.039> and<00:00:56.280> they<00:00:56.559> are<00:00:57.559> staking<00:00:58.039> 32 00:00:58.509 --> 00:00:58.519 align:start position:0% have validators and they are staking 32 00:00:58.519 --> 00:01:00.389 align:start position:0% have validators and they are staking 32 e<00:00:58.920> and<00:00:59.000> then<00:00:59.120> they<00:00:59.399> performing<00:00:59.719> the<00:01:00.000> duties 00:01:00.389 --> 00:01:00.399 align:start position:0% e and then they performing the duties 00:01:00.399 --> 00:01:02.229 align:start position:0% e and then they performing the duties like<00:01:00.640> voting<00:01:01.000> at<00:01:01.160> the<00:01:01.440> U<00:01:01.719> voting<00:01:01.960> for<00:01:02.120> new 00:01:02.229 --> 00:01:02.239 align:start position:0% like voting at the U voting for new 00:01:02.239 --> 00:01:03.670 align:start position:0% like voting at the U voting for new blocks<00:01:02.480> with<00:01:02.600> at<00:01:02.760> the<00:01:02.920> stations<00:01:03.320> proposing 00:01:03.670 --> 00:01:03.680 align:start position:0% blocks with at the stations proposing 00:01:03.680 --> 00:01:07.270 align:start position:0% blocks with at the stations proposing new<00:01:03.800> blocks<00:01:04.119> and<00:01:04.280> things<00:01:04.559> like<00:01:05.280> that<00:01:06.280> and<00:01:07.119> well 00:01:07.270 --> 00:01:07.280 align:start position:0% new blocks and things like that and well 00:01:07.280 --> 00:01:09.109 align:start position:0% new blocks and things like that and well when<00:01:07.400> you're<00:01:07.600> creating<00:01:07.880> a<00:01:08.000> validator<00:01:08.799> maybe 00:01:09.109 --> 00:01:09.119 align:start position:0% when you're creating a validator maybe 00:01:09.119 --> 00:01:11.950 align:start position:0% when you're creating a validator maybe everyone<00:01:09.680> knows<00:01:10.080> that<00:01:10.360> but<00:01:10.640> we<00:01:10.920> have<00:01:11.520> two<00:01:11.720> sets 00:01:11.950 --> 00:01:11.960 align:start position:0% everyone knows that but we have two sets 00:01:11.960 --> 00:01:13.990 align:start position:0% everyone knows that but we have two sets of<00:01:12.119> credentials<00:01:12.759> you<00:01:12.960> have<00:01:13.240> your<00:01:13.520> validator 00:01:13.990 --> 00:01:14.000 align:start position:0% of credentials you have your validator 00:01:14.000 --> 00:01:15.350 align:start position:0% of credentials you have your validator key<00:01:14.400> which<00:01:14.520> is<00:01:14.640> associated<00:01:15.080> with<00:01:15.200> your 00:01:15.350 --> 00:01:15.360 align:start position:0% key which is associated with your 00:01:15.360 --> 00:01:17.469 align:start position:0% key which is associated with your validator<00:01:15.799> public<00:01:16.200> key<00:01:16.759> which<00:01:16.880> is<00:01:17.000> used<00:01:17.280> for 00:01:17.469 --> 00:01:17.479 align:start position:0% validator public key which is used for 00:01:17.479 --> 00:01:18.590 align:start position:0% validator public key which is used for signing<00:01:17.799> your<00:01:17.960> blocks<00:01:18.280> signing<00:01:18.479> your 00:01:18.590 --> 00:01:18.600 align:start position:0% signing your blocks signing your 00:01:18.600 --> 00:01:20.830 align:start position:0% signing your blocks signing your attestations<00:01:19.119> and<00:01:19.400> everything<00:01:20.400> and<00:01:20.560> you<00:01:20.720> have 00:01:20.830 --> 00:01:20.840 align:start position:0% attestations and everything and you have 00:01:20.840 --> 00:01:23.630 align:start position:0% attestations and everything and you have your<00:01:21.040> withdraw<00:01:21.799> uh<00:01:21.960> key<00:01:22.360> which<00:01:22.600> is<00:01:23.320> kind<00:01:23.479> of 00:01:23.630 --> 00:01:23.640 align:start position:0% your withdraw uh key which is kind of 00:01:23.640 --> 00:01:26.590 align:start position:0% your withdraw uh key which is kind of represents<00:01:24.280> the<00:01:24.640> uh<00:01:24.759> ownership<00:01:25.280> of<00:01:25.439> the<00:01:26.000> state 00:01:26.590 --> 00:01:26.600 align:start position:0% represents the uh ownership of the state 00:01:26.600 --> 00:01:30.270 align:start position:0% represents the uh ownership of the state amount<00:01:27.280> of<00:01:27.520> of<00:01:27.880> of<00:01:28.040> E 00:01:30.270 --> 00:01:30.280 align:start position:0% amount of of of E 00:01:30.280 --> 00:01:33.350 align:start position:0% amount of of of E um<00:01:30.960> another<00:01:31.360> concept<00:01:31.920> is<00:01:32.520> solo<00:01:32.880> staking 00:01:33.350 --> 00:01:33.360 align:start position:0% um another concept is solo staking 00:01:33.360 --> 00:01:35.270 align:start position:0% um another concept is solo staking versus<00:01:33.799> delegated<00:01:34.280> staking<00:01:34.680> so<00:01:34.840> this<00:01:34.960> is<00:01:35.159> kind 00:01:35.270 --> 00:01:35.280 align:start position:0% versus delegated staking so this is kind 00:01:35.280 --> 00:01:37.590 align:start position:0% versus delegated staking so this is kind of<00:01:35.439> a<00:01:36.200> different<00:01:36.520> thing<00:01:36.759> like<00:01:37.040> staking<00:01:37.439> is 00:01:37.590 --> 00:01:37.600 align:start position:0% of a different thing like staking is 00:01:37.600 --> 00:01:40.710 align:start position:0% of a different thing like staking is staking<00:01:38.159> but<00:01:39.040> uh<00:01:39.200> I<00:01:39.280> think<00:01:39.439> solo<00:01:39.799> staking<00:01:40.360> will 00:01:40.710 --> 00:01:40.720 align:start position:0% staking but uh I think solo staking will 00:01:40.720 --> 00:01:43.789 align:start position:0% staking but uh I think solo staking will be<00:01:41.439> uh<00:01:41.600> kind<00:01:41.759> of<00:01:41.880> the<00:01:42.079> most<00:01:42.399> basic<00:01:43.280> uh<00:01:43.520> thing 00:01:43.789 --> 00:01:43.799 align:start position:0% be uh kind of the most basic uh thing 00:01:43.799 --> 00:01:44.910 align:start position:0% be uh kind of the most basic uh thing when<00:01:43.960> you<00:01:44.040> think<00:01:44.240> about<00:01:44.399> staking<00:01:44.719> you<00:01:44.840> know 00:01:44.910 --> 00:01:44.920 align:start position:0% when you think about staking you know 00:01:44.920 --> 00:01:46.550 align:start position:0% when you think about staking you know you<00:01:45.040> have<00:01:45.159> your<00:01:45.360> laptop<00:01:46.000> you<00:01:46.159> create<00:01:46.399> a 00:01:46.550 --> 00:01:46.560 align:start position:0% you have your laptop you create a 00:01:46.560 --> 00:01:48.670 align:start position:0% you have your laptop you create a validator<00:01:47.280> you<00:01:47.479> have<00:01:47.759> the<00:01:47.880> validator<00:01:48.320> key<00:01:48.520> you 00:01:48.670 --> 00:01:48.680 align:start position:0% validator you have the validator key you 00:01:48.680 --> 00:01:50.789 align:start position:0% validator you have the validator key you have<00:01:49.119> your<00:01:49.360> withdraw<00:01:49.840> key<00:01:50.000> so<00:01:50.240> you<00:01:50.360> own<00:01:50.640> kind 00:01:50.789 --> 00:01:50.799 align:start position:0% have your withdraw key so you own kind 00:01:50.799 --> 00:01:52.510 align:start position:0% have your withdraw key so you own kind of<00:01:51.000> everything<00:01:51.880> and<00:01:52.000> when<00:01:52.119> it<00:01:52.240> comes<00:01:52.399> to 00:01:52.510 --> 00:01:52.520 align:start position:0% of everything and when it comes to 00:01:52.520 --> 00:01:54.429 align:start position:0% of everything and when it comes to delegate<00:01:52.920> staking<00:01:53.479> there<00:01:53.600> is<00:01:53.880> like<00:01:54.040> a<00:01:54.200> bunch 00:01:54.429 --> 00:01:54.439 align:start position:0% delegate staking there is like a bunch 00:01:54.439 --> 00:01:56.190 align:start position:0% delegate staking there is like a bunch of<00:01:54.640> different<00:01:55.119> uh<00:01:55.240> Arrangements<00:01:55.840> you<00:01:55.960> have 00:01:56.190 --> 00:01:56.200 align:start position:0% of different uh Arrangements you have 00:01:56.200 --> 00:01:58.950 align:start position:0% of different uh Arrangements you have custodial<00:01:56.759> non-custodial<00:01:57.399> but<00:01:58.320> for<00:01:58.719> this 00:01:58.950 --> 00:01:58.960 align:start position:0% custodial non-custodial but for this 00:01:58.960 --> 00:02:01.190 align:start position:0% custodial non-custodial but for this exercise<00:01:59.479> that's<00:01:59.640> just<00:02:00.000> assume<00:02:00.360> that<00:02:00.719> you<00:02:00.880> own 00:02:01.190 --> 00:02:01.200 align:start position:0% exercise that's just assume that you own 00:02:01.200 --> 00:02:03.469 align:start position:0% exercise that's just assume that you own the<00:02:01.320> withdrawal<00:02:01.799> key<00:02:02.399> someone<00:02:02.719> else<00:02:03.000> owns<00:02:03.320> the 00:02:03.469 --> 00:02:03.479 align:start position:0% the withdrawal key someone else owns the 00:02:03.479 --> 00:02:04.749 align:start position:0% the withdrawal key someone else owns the validator<00:02:03.920> key<00:02:04.119> because<00:02:04.280> they're<00:02:04.479> running 00:02:04.749 --> 00:02:04.759 align:start position:0% validator key because they're running 00:02:04.759 --> 00:02:06.749 align:start position:0% validator key because they're running your<00:02:04.920> node<00:02:05.200> for<00:02:05.399> you<00:02:05.920> but<00:02:06.079> they<00:02:06.280> do<00:02:06.439> need<00:02:06.600> the 00:02:06.749 --> 00:02:06.759 align:start position:0% your node for you but they do need the 00:02:06.759 --> 00:02:07.870 align:start position:0% your node for you but they do need the key<00:02:06.920> because<00:02:07.079> they're<00:02:07.200> going<00:02:07.320> to<00:02:07.399> be<00:02:07.479> signing 00:02:07.870 --> 00:02:07.880 align:start position:0% key because they're going to be signing 00:02:07.880 --> 00:02:09.070 align:start position:0% key because they're going to be signing the<00:02:08.000> the<00:02:08.119> stations<00:02:08.399> and<00:02:08.520> everything<00:02:08.800> so<00:02:09.000> they 00:02:09.070 --> 00:02:09.080 align:start position:0% the the stations and everything so they 00:02:09.080 --> 00:02:12.270 align:start position:0% the the stations and everything so they need<00:02:09.239> the<00:02:09.399> key<00:02:10.119> so<00:02:10.360> that<00:02:10.560> let's<00:02:10.800> just<00:02:11.200> do<00:02:11.480> with 00:02:12.270 --> 00:02:12.280 align:start position:0% need the key so that let's just do with 00:02:12.280 --> 00:02:14.670 align:start position:0% need the key so that let's just do with that<00:02:13.280> okay<00:02:13.520> another<00:02:13.840> thing<00:02:14.080> before<00:02:14.319> we<00:02:14.440> jump 00:02:14.670 --> 00:02:14.680 align:start position:0% that okay another thing before we jump 00:02:14.680 --> 00:02:16.630 align:start position:0% that okay another thing before we jump into<00:02:14.840> the<00:02:14.959> EIP<00:02:15.599> uh<00:02:15.680> I<00:02:15.760> want<00:02:15.879> to<00:02:16.040> touch<00:02:16.319> on 00:02:16.630 --> 00:02:16.640 align:start position:0% into the EIP uh I want to touch on 00:02:16.640 --> 00:02:20.350 align:start position:0% into the EIP uh I want to touch on voluntary<00:02:17.239> exits<00:02:17.720> so<00:02:18.680> um<00:02:19.599> voluntary<00:02:20.080> exit 00:02:20.350 --> 00:02:20.360 align:start position:0% voluntary exits so um voluntary exit 00:02:20.360 --> 00:02:21.830 align:start position:0% voluntary exits so um voluntary exit since<00:02:20.599> phase<00:02:20.840> zero<00:02:21.120> has<00:02:21.239> been<00:02:21.440> pretty<00:02:21.640> much 00:02:21.830 --> 00:02:21.840 align:start position:0% since phase zero has been pretty much 00:02:21.840 --> 00:02:24.070 align:start position:0% since phase zero has been pretty much the<00:02:22.000> same<00:02:22.879> you<00:02:23.200> if<00:02:23.319> you<00:02:23.400> want<00:02:23.519> to<00:02:23.680> exit 00:02:24.070 --> 00:02:24.080 align:start position:0% the same you if you want to exit 00:02:24.080 --> 00:02:26.470 align:start position:0% the same you if you want to exit validator<00:02:24.519> you<00:02:24.640> don't<00:02:24.800> want<00:02:24.920> a<00:02:25.120> stake<00:02:25.480> anymore 00:02:26.470 --> 00:02:26.480 align:start position:0% validator you don't want a stake anymore 00:02:26.480 --> 00:02:28.910 align:start position:0% validator you don't want a stake anymore you<00:02:26.760> will<00:02:27.360> uh<00:02:27.480> send<00:02:27.879> a<00:02:28.120> volun<00:02:28.519> assigned 00:02:28.910 --> 00:02:28.920 align:start position:0% you will uh send a volun assigned 00:02:28.920 --> 00:02:31.750 align:start position:0% you will uh send a volun assigned voluntary<00:02:29.400> exit<00:02:29.959> message<00:02:30.840> but<00:02:31.040> that<00:02:31.239> message 00:02:31.750 --> 00:02:31.760 align:start position:0% voluntary exit message but that message 00:02:31.760 --> 00:02:34.949 align:start position:0% voluntary exit message but that message is<00:02:32.000> signed<00:02:32.440> with<00:02:32.599> your<00:02:32.840> validator<00:02:33.440> key<00:02:34.319> so<00:02:34.800> you 00:02:34.949 --> 00:02:34.959 align:start position:0% is signed with your validator key so you 00:02:34.959 --> 00:02:36.990 align:start position:0% is signed with your validator key so you sign<00:02:35.200> that<00:02:35.360> message<00:02:35.760> broadcast<00:02:36.280> it<00:02:36.480> through 00:02:36.990 --> 00:02:37.000 align:start position:0% sign that message broadcast it through 00:02:37.000 --> 00:02:39.350 align:start position:0% sign that message broadcast it through uh<00:02:37.080> send<00:02:37.319> it<00:02:37.599> through<00:02:37.920> the<00:02:38.040> beon<00:02:38.360> API<00:02:39.200> it's 00:02:39.350 --> 00:02:39.360 align:start position:0% uh send it through the beon API it's 00:02:39.360 --> 00:02:40.710 align:start position:0% uh send it through the beon API it's going<00:02:39.440> to<00:02:39.560> be<00:02:39.640> propagated<00:02:40.040> in<00:02:40.120> the<00:02:40.239> network 00:02:40.710 --> 00:02:40.720 align:start position:0% going to be propagated in the network 00:02:40.720 --> 00:02:43.550 align:start position:0% going to be propagated in the network eventually<00:02:41.120> included<00:02:41.480> in<00:02:41.599> a<00:02:41.720> block<00:02:42.400> and<00:02:43.239> after 00:02:43.550 --> 00:02:43.560 align:start position:0% eventually included in a block and after 00:02:43.560 --> 00:02:45.390 align:start position:0% eventually included in a block and after some<00:02:43.800> time<00:02:44.080> your<00:02:44.319> validator<00:02:44.720> joins<00:02:45.000> the<00:02:45.120> exit 00:02:45.390 --> 00:02:45.400 align:start position:0% some time your validator joins the exit 00:02:45.400 --> 00:02:48.550 align:start position:0% some time your validator joins the exit Cube<00:02:46.280> pretty<00:02:46.959> straightforward<00:02:47.959> uh<00:02:48.280> however 00:02:48.550 --> 00:02:48.560 align:start position:0% Cube pretty straightforward uh however 00:02:48.560 --> 00:02:50.509 align:start position:0% Cube pretty straightforward uh however as<00:02:48.640> you<00:02:48.720> can<00:02:48.840> see<00:02:49.000> in<00:02:49.080> the<00:02:49.200> diagram<00:02:49.680> here<00:02:50.319> if 00:02:50.509 --> 00:02:50.519 align:start position:0% as you can see in the diagram here if 00:02:50.519 --> 00:02:53.149 align:start position:0% as you can see in the diagram here if you<00:02:51.200> don't<00:02:51.519> have<00:02:51.640> the<00:02:51.800> validator<00:02:52.280> key<00:02:52.920> you're 00:02:53.149 --> 00:02:53.159 align:start position:0% you don't have the validator key you're 00:02:53.159 --> 00:02:54.630 align:start position:0% you don't have the validator key you're kind<00:02:53.319> of<00:02:53.400> in<00:02:53.480> trouble<00:02:53.879> because<00:02:54.200> you<00:02:54.360> don't 00:02:54.630 --> 00:02:54.640 align:start position:0% kind of in trouble because you don't 00:02:54.640 --> 00:02:56.309 align:start position:0% kind of in trouble because you don't really<00:02:55.280> have<00:02:55.440> a<00:02:55.560> way<00:02:55.720> of<00:02:55.840> accessing<00:02:56.239> your 00:02:56.309 --> 00:02:56.319 align:start position:0% really have a way of accessing your 00:02:56.319 --> 00:02:58.949 align:start position:0% really have a way of accessing your valid<00:02:56.840> dator<00:02:57.840> and<00:02:58.159> you<00:02:58.280> need<00:02:58.400> to<00:02:58.519> kind<00:02:58.640> of<00:02:58.720> ring 00:02:58.949 --> 00:02:58.959 align:start position:0% valid dator and you need to kind of ring 00:02:58.959 --> 00:03:00.990 align:start position:0% valid dator and you need to kind of ring your<00:02:59.120> operator<00:02:59.920> hey<00:03:00.159> could<00:03:00.280> you<00:03:00.440> please<00:03:00.720> exit 00:03:00.990 --> 00:03:01.000 align:start position:0% your operator hey could you please exit 00:03:01.000 --> 00:03:03.630 align:start position:0% your operator hey could you please exit my<00:03:01.120> validator<00:03:01.560> for<00:03:01.720> me<00:03:02.680> well<00:03:02.959> if<00:03:03.120> they<00:03:03.239> are<00:03:03.560> you 00:03:03.630 --> 00:03:03.640 align:start position:0% my validator for me well if they are you 00:03:03.640 --> 00:03:05.390 align:start position:0% my validator for me well if they are you know<00:03:03.840> nice<00:03:04.159> people<00:03:04.400> they<00:03:04.480> will<00:03:04.640> do<00:03:04.760> it<00:03:04.840> for<00:03:05.040> you 00:03:05.390 --> 00:03:05.400 align:start position:0% know nice people they will do it for you 00:03:05.400 --> 00:03:08.390 align:start position:0% know nice people they will do it for you but<00:03:05.640> you<00:03:05.760> know<00:03:06.120> it's<00:03:06.319> kind<00:03:06.440> of<00:03:06.560> like<00:03:06.720> a<00:03:07.440> grief 00:03:08.390 --> 00:03:08.400 align:start position:0% but you know it's kind of like a grief 00:03:08.400 --> 00:03:11.350 align:start position:0% but you know it's kind of like a grief Tech<00:03:08.720> Vector<00:03:09.480> because<00:03:10.480> technically<00:03:11.159> the<00:03:11.280> the 00:03:11.350 --> 00:03:11.360 align:start position:0% Tech Vector because technically the the 00:03:11.360 --> 00:03:16.110 align:start position:0% Tech Vector because technically the the node<00:03:11.640> operator<00:03:12.200> can<00:03:13.360> um<00:03:14.360> like<00:03:14.640> not<00:03:14.920> really<00:03:15.799> do 00:03:16.110 --> 00:03:16.120 align:start position:0% node operator can um like not really do 00:03:16.120 --> 00:03:18.309 align:start position:0% node operator can um like not really do their<00:03:16.360> best<00:03:16.640> job<00:03:17.519> uh<00:03:17.680> when<00:03:17.799> doing<00:03:18.000> their 00:03:18.309 --> 00:03:18.319 align:start position:0% their best job uh when doing their 00:03:18.319 --> 00:03:19.869 align:start position:0% their best job uh when doing their decisions<00:03:18.680> and<00:03:18.799> everything<00:03:19.360> and<00:03:19.480> they<00:03:19.640> have 00:03:19.869 --> 00:03:19.879 align:start position:0% decisions and everything and they have 00:03:19.879 --> 00:03:22.670 align:start position:0% decisions and everything and they have ways<00:03:20.080> of<00:03:20.280> like<00:03:20.400> slowly<00:03:21.080> chipping<00:03:21.519> away<00:03:21.959> your 00:03:22.670 --> 00:03:22.680 align:start position:0% ways of like slowly chipping away your 00:03:22.680 --> 00:03:26.149 align:start position:0% ways of like slowly chipping away your uh<00:03:23.000> your<00:03:23.680> uh<00:03:23.920> steak<00:03:24.280> which<00:03:24.480> not<00:03:25.000> great<00:03:26.000> there 00:03:26.149 --> 00:03:26.159 align:start position:0% uh your uh steak which not great there 00:03:26.159 --> 00:03:27.990 align:start position:0% uh your uh steak which not great there are<00:03:26.560> ways<00:03:26.879> around<00:03:27.239> this<00:03:27.560> some<00:03:27.799> other 00:03:27.990 --> 00:03:28.000 align:start position:0% are ways around this some other 00:03:28.000 --> 00:03:30.229 align:start position:0% are ways around this some other operators<00:03:28.400> will<00:03:28.599> give<00:03:28.760> you<00:03:28.920> a<00:03:29.120> pre-sign<00:03:29.879> exit 00:03:30.229 --> 00:03:30.239 align:start position:0% operators will give you a pre-sign exit 00:03:30.239 --> 00:03:33.350 align:start position:0% operators will give you a pre-sign exit message<00:03:30.799> when<00:03:30.920> you<00:03:31.200> join<00:03:31.640> the<00:03:32.200> uh<00:03:32.519> the<00:03:32.920> system 00:03:33.350 --> 00:03:33.360 align:start position:0% message when you join the uh the system 00:03:33.360 --> 00:03:35.470 align:start position:0% message when you join the uh the system so<00:03:33.920> you<00:03:34.120> keep<00:03:34.280> that<00:03:34.439> message<00:03:34.760> safe<00:03:35.159> whenever 00:03:35.470 --> 00:03:35.480 align:start position:0% so you keep that message safe whenever 00:03:35.480 --> 00:03:36.869 align:start position:0% so you keep that message safe whenever you<00:03:35.599> want<00:03:35.720> to<00:03:35.879> exit<00:03:36.200> you<00:03:36.319> already<00:03:36.560> have<00:03:36.720> the 00:03:36.869 --> 00:03:36.879 align:start position:0% you want to exit you already have the 00:03:36.879 --> 00:03:39.350 align:start position:0% you want to exit you already have the signed<00:03:37.120> message<00:03:37.400> and<00:03:37.519> then<00:03:37.599> you<00:03:37.720> can<00:03:38.360> exit 00:03:39.350 --> 00:03:39.360 align:start position:0% signed message and then you can exit 00:03:39.360 --> 00:03:41.110 align:start position:0% signed message and then you can exit this<00:03:39.640> is<00:03:39.799> a<00:03:39.959> workaround<00:03:40.599> because<00:03:40.840> there<00:03:40.920> are<00:03:41.040> a 00:03:41.110 --> 00:03:41.120 align:start position:0% this is a workaround because there are a 00:03:41.120 --> 00:03:42.509 align:start position:0% this is a workaround because there are a lot<00:03:41.239> of<00:03:41.360> complications<00:03:41.840> with<00:03:42.040> this<00:03:42.239> there's<00:03:42.439> a 00:03:42.509 --> 00:03:42.519 align:start position:0% lot of complications with this there's a 00:03:42.519 --> 00:03:43.630 align:start position:0% lot of complications with this there's a lot<00:03:42.640> of<00:03:42.799> you<00:03:42.879> know<00:03:43.000> you<00:03:43.080> need<00:03:43.200> to<00:03:43.319> keep<00:03:43.480> that 00:03:43.630 --> 00:03:43.640 align:start position:0% lot of you know you need to keep that 00:03:43.640 --> 00:03:46.070 align:start position:0% lot of you know you need to keep that message<00:03:43.959> safe<00:03:44.760> you<00:03:45.040> don't<00:03:45.360> you're<00:03:45.519> not<00:03:45.799> 100% 00:03:46.070 --> 00:03:46.080 align:start position:0% message safe you don't you're not 100% 00:03:46.080 --> 00:03:48.030 align:start position:0% message safe you don't you're not 100% sure<00:03:46.239> if<00:03:46.360> that<00:03:46.480> message<00:03:46.720> is<00:03:46.760> going<00:03:46.879> to<00:03:47.040> work 00:03:48.030 --> 00:03:48.040 align:start position:0% sure if that message is going to work 00:03:48.040 --> 00:03:49.470 align:start position:0% sure if that message is going to work and<00:03:48.519> they<00:03:48.680> have<00:03:48.840> to<00:03:49.000> have<00:03:49.200> all<00:03:49.360> the 00:03:49.470 --> 00:03:49.480 align:start position:0% and they have to have all the 00:03:49.480 --> 00:03:50.949 align:start position:0% and they have to have all the infrastructure<00:03:50.080> around<00:03:50.360> managing<00:03:50.799> that 00:03:50.949 --> 00:03:50.959 align:start position:0% infrastructure around managing that 00:03:50.959 --> 00:03:53.949 align:start position:0% infrastructure around managing that message<00:03:51.360> and<00:03:51.560> everything<00:03:52.239> so<00:03:53.239> it's<00:03:53.680> yeah<00:03:53.840> it's 00:03:53.949 --> 00:03:53.959 align:start position:0% message and everything so it's yeah it's 00:03:53.959 --> 00:03:56.589 align:start position:0% message and everything so it's yeah it's kind<00:03:54.079> of<00:03:54.159> a<00:03:54.680> heck<00:03:55.680> well<00:03:55.920> back<00:03:56.079> to<00:03:56.200> the<00:03:56.360> problem 00:03:56.589 --> 00:03:56.599 align:start position:0% kind of a heck well back to the problem 00:03:56.599 --> 00:03:58.470 align:start position:0% kind of a heck well back to the problem that<00:03:56.680> we<00:03:56.799> were<00:03:56.920> talking<00:03:57.239> about 00:03:58.470 --> 00:03:58.480 align:start position:0% that we were talking about 00:03:58.480 --> 00:04:00.910 align:start position:0% that we were talking about we<00:03:59.480> you<00:03:59.560> can<00:03:59.840> only<00:04:00.040> exit<00:04:00.280> your<00:04:00.400> validator 00:04:00.910 --> 00:04:00.920 align:start position:0% we you can only exit your validator 00:04:00.920 --> 00:04:04.670 align:start position:0% we you can only exit your validator today<00:04:01.360> with<00:04:01.519> your<00:04:01.840> validator<00:04:02.360> key<00:04:03.519> right<00:04:04.519> and 00:04:04.670 --> 00:04:04.680 align:start position:0% today with your validator key right and 00:04:04.680 --> 00:04:07.630 align:start position:0% today with your validator key right and the<00:04:04.760> solution<00:04:05.079> is<00:04:05.599> easy<00:04:06.599> just<00:04:06.799> allow<00:04:07.239> both<00:04:07.480> the 00:04:07.630 --> 00:04:07.640 align:start position:0% the solution is easy just allow both the 00:04:07.640 --> 00:04:09.429 align:start position:0% the solution is easy just allow both the validator<00:04:08.159> key<00:04:08.519> and<00:04:08.720> the<00:04:08.840> withdraw<00:04:09.200> key<00:04:09.360> to 00:04:09.429 --> 00:04:09.439 align:start position:0% validator key and the withdraw key to 00:04:09.439 --> 00:04:12.229 align:start position:0% validator key and the withdraw key to exit<00:04:09.680> the<00:04:09.959> validator<00:04:10.959> yep<00:04:11.360> it's<00:04:11.879> it's<00:04:12.040> pretty 00:04:12.229 --> 00:04:12.239 align:start position:0% exit the validator yep it's it's pretty 00:04:12.239 --> 00:04:13.630 align:start position:0% exit the validator yep it's it's pretty straightforward<00:04:12.959> unfortunately 00:04:13.630 --> 00:04:13.640 align:start position:0% straightforward unfortunately 00:04:13.640 --> 00:04:16.110 align:start position:0% straightforward unfortunately implementing<00:04:14.200> it<00:04:14.799> it's<00:04:15.000> not<00:04:15.239> that 00:04:16.110 --> 00:04:16.120 align:start position:0% implementing it it's not that 00:04:16.120 --> 00:04:18.590 align:start position:0% implementing it it's not that easy<00:04:17.120> um<00:04:17.400> and<00:04:17.560> that's<00:04:17.959> pretty<00:04:18.199> much<00:04:18.440> the 00:04:18.590 --> 00:04:18.600 align:start position:0% easy um and that's pretty much the 00:04:18.600 --> 00:04:21.590 align:start position:0% easy um and that's pretty much the context<00:04:19.160> and<00:04:19.400> how<00:04:19.519> we<00:04:19.680> get<00:04:19.840> to<00:04:20.120> EIP 00:04:21.590 --> 00:04:21.600 align:start position:0% context and how we get to EIP 00:04:21.600 --> 00:04:24.950 align:start position:0% context and how we get to EIP 7002<00:04:22.680> so<00:04:23.680> why<00:04:23.840> it's<00:04:23.960> not<00:04:24.160> easy<00:04:24.520> it's<00:04:24.680> important 00:04:24.950 --> 00:04:24.960 align:start position:0% 7002 so why it's not easy it's important 00:04:24.960 --> 00:04:26.550 align:start position:0% 7002 so why it's not easy it's important to<00:04:25.120> remember<00:04:25.639> that<00:04:25.800> when<00:04:25.919> it<00:04:26.040> comes<00:04:26.240> to<00:04:26.400> the 00:04:26.550 --> 00:04:26.560 align:start position:0% to remember that when it comes to the 00:04:26.560 --> 00:04:28.430 align:start position:0% to remember that when it comes to the consensus<00:04:27.320> uh<00:04:27.400> layer<00:04:27.759> and<00:04:27.880> the<00:04:28.000> execution 00:04:28.430 --> 00:04:28.440 align:start position:0% consensus uh layer and the execution 00:04:28.440 --> 00:04:30.749 align:start position:0% consensus uh layer and the execution layer<00:04:29.440> the<00:04:29.720> consensus<00:04:30.080> layer<00:04:30.320> doesn't<00:04:30.520> have 00:04:30.749 --> 00:04:30.759 align:start position:0% layer the consensus layer doesn't have 00:04:30.759 --> 00:04:32.629 align:start position:0% layer the consensus layer doesn't have like<00:04:30.919> a<00:04:31.120> complete<00:04:31.560> view<00:04:31.960> of<00:04:32.120> what<00:04:32.280> happens<00:04:32.520> on 00:04:32.629 --> 00:04:32.639 align:start position:0% like a complete view of what happens on 00:04:32.639 --> 00:04:35.390 align:start position:0% like a complete view of what happens on the<00:04:32.759> execution<00:04:33.120> layer<00:04:33.960> right<00:04:34.199> so<00:04:35.080> it's<00:04:35.240> got 00:04:35.390 --> 00:04:35.400 align:start position:0% the execution layer right so it's got 00:04:35.400 --> 00:04:36.870 align:start position:0% the execution layer right so it's got like<00:04:35.479> a<00:04:35.639> limited<00:04:36.080> amount<00:04:36.280> of<00:04:36.440> information 00:04:36.870 --> 00:04:36.880 align:start position:0% like a limited amount of information 00:04:36.880 --> 00:04:38.510 align:start position:0% like a limited amount of information that<00:04:37.039> comes<00:04:37.280> through<00:04:37.560> that<00:04:37.840> side<00:04:38.199> I<00:04:38.280> think<00:04:38.400> a 00:04:38.510 --> 00:04:38.520 align:start position:0% that comes through that side I think a 00:04:38.520 --> 00:04:40.230 align:start position:0% that comes through that side I think a good<00:04:38.680> example<00:04:39.039> of<00:04:39.240> this<00:04:39.440> is<00:04:39.560> you<00:04:39.720> think<00:04:39.960> about 00:04:40.230 --> 00:04:40.240 align:start position:0% good example of this is you think about 00:04:40.240 --> 00:04:42.270 align:start position:0% good example of this is you think about deposit<00:04:40.720> processing<00:04:41.479> stepan<00:04:41.880> is<00:04:41.960> going<00:04:42.080> to<00:04:42.160> be 00:04:42.270 --> 00:04:42.280 align:start position:0% deposit processing stepan is going to be 00:04:42.280 --> 00:04:44.070 align:start position:0% deposit processing stepan is going to be talking<00:04:42.680> a<00:04:42.759> little<00:04:42.919> bit<00:04:43.160> about<00:04:43.600> about<00:04:43.800> it 00:04:44.070 --> 00:04:44.080 align:start position:0% talking a little bit about about it 00:04:44.080 --> 00:04:46.430 align:start position:0% talking a little bit about about it later<00:04:45.080> it's<00:04:45.199> a<00:04:45.360> complicated<00:04:46.199> it's<00:04:46.280> a 00:04:46.430 --> 00:04:46.440 align:start position:0% later it's a complicated it's a 00:04:46.440 --> 00:04:47.749 align:start position:0% later it's a complicated it's a complicated<00:04:46.880> Mass<00:04:47.160> you<00:04:47.240> know<00:04:47.320> it's<00:04:47.400> a<00:04:47.520> whole 00:04:47.749 --> 00:04:47.759 align:start position:0% complicated Mass you know it's a whole 00:04:47.759 --> 00:04:49.550 align:start position:0% complicated Mass you know it's a whole system<00:04:48.199> keeps<00:04:48.479> updating<00:04:49.000> and<00:04:49.160> fetching 00:04:49.550 --> 00:04:49.560 align:start position:0% system keeps updating and fetching 00:04:49.560 --> 00:04:52.150 align:start position:0% system keeps updating and fetching information<00:04:50.360> it's<00:04:50.520> not<00:04:50.680> that<00:04:50.840> easy<00:04:51.800> so<00:04:52.000> what 00:04:52.150 --> 00:04:52.160 align:start position:0% information it's not that easy so what 00:04:52.160 --> 00:04:56.310 align:start position:0% information it's not that easy so what we<00:04:52.280> really<00:04:52.479> need<00:04:52.919> is<00:04:53.199> we<00:04:53.360> need<00:04:53.520> a<00:04:53.960> mechanism<00:04:55.320> to 00:04:56.310 --> 00:04:56.320 align:start position:0% we really need is we need a mechanism to 00:04:56.320 --> 00:04:59.790 align:start position:0% we really need is we need a mechanism to create<00:04:56.720> a<00:04:56.919> message<00:04:57.520> on<00:04:57.880> the<00:04:58.039> execution<00:04:58.520> layer 00:04:59.790 --> 00:04:59.800 align:start position:0% create a message on the execution layer 00:04:59.800 --> 00:05:01.430 align:start position:0% create a message on the execution layer send<00:05:00.160> that<00:05:00.360> message<00:05:00.720> all<00:05:00.919> the<00:05:01.039> way<00:05:01.160> to<00:05:01.280> the 00:05:01.430 --> 00:05:01.440 align:start position:0% send that message all the way to the 00:05:01.440 --> 00:05:04.150 align:start position:0% send that message all the way to the consensus<00:05:01.960> layer<00:05:02.960> but<00:05:03.160> that<00:05:03.360> message<00:05:03.759> has<00:05:03.880> to 00:05:04.150 --> 00:05:04.160 align:start position:0% consensus layer but that message has to 00:05:04.160 --> 00:05:07.430 align:start position:0% consensus layer but that message has to be<00:05:05.160> authenticated<00:05:06.120> with<00:05:06.639> an<00:05:06.800> account<00:05:07.080> on<00:05:07.280> the 00:05:07.430 --> 00:05:07.440 align:start position:0% be authenticated with an account on the 00:05:07.440 --> 00:05:09.790 align:start position:0% be authenticated with an account on the execution<00:05:07.919> layer<00:05:08.280> side<00:05:09.160> but<00:05:09.280> at<00:05:09.400> the<00:05:09.520> same 00:05:09.790 --> 00:05:09.800 align:start position:0% execution layer side but at the same 00:05:09.800 --> 00:05:11.950 align:start position:0% execution layer side but at the same time<00:05:10.440> all<00:05:10.639> the<00:05:10.759> authorization<00:05:11.520> happens<00:05:11.800> on 00:05:11.950 --> 00:05:11.960 align:start position:0% time all the authorization happens on 00:05:11.960 --> 00:05:13.310 align:start position:0% time all the authorization happens on the<00:05:12.080> consensus<00:05:12.520> layer<00:05:12.800> side<00:05:13.039> because<00:05:13.199> the 00:05:13.310 --> 00:05:13.320 align:start position:0% the consensus layer side because the 00:05:13.320 --> 00:05:15.350 align:start position:0% the consensus layer side because the consensus<00:05:13.720> layer<00:05:13.960> is<00:05:14.080> the<00:05:14.199> one<00:05:14.360> that<00:05:14.520> knows 00:05:15.350 --> 00:05:15.360 align:start position:0% consensus layer is the one that knows 00:05:15.360 --> 00:05:17.150 align:start position:0% consensus layer is the one that knows who's<00:05:15.600> the<00:05:15.759> validator<00:05:16.440> what's<00:05:16.680> the<00:05:16.759> withdraw 00:05:17.150 --> 00:05:17.160 align:start position:0% who's the validator what's the withdraw 00:05:17.160 --> 00:05:18.350 align:start position:0% who's the validator what's the withdraw credential<00:05:17.600> associated<00:05:18.039> with<00:05:18.160> that 00:05:18.350 --> 00:05:18.360 align:start position:0% credential associated with that 00:05:18.360 --> 00:05:20.270 align:start position:0% credential associated with that validator<00:05:19.240> what's<00:05:19.440> the<00:05:19.560> balance<00:05:20.039> and<00:05:20.160> all 00:05:20.270 --> 00:05:20.280 align:start position:0% validator what's the balance and all 00:05:20.280 --> 00:05:22.990 align:start position:0% validator what's the balance and all this<00:05:20.440> kind<00:05:20.560> of<00:05:20.800> stuff<00:05:21.800> so<00:05:22.080> that's<00:05:22.360> the<00:05:22.639> kind<00:05:22.759> of 00:05:22.990 --> 00:05:23.000 align:start position:0% this kind of stuff so that's the kind of 00:05:23.000 --> 00:05:24.870 align:start position:0% this kind of stuff so that's the kind of the<00:05:23.199> the<00:05:23.319> thing<00:05:23.479> that<00:05:23.560> we're<00:05:23.759> trying<00:05:23.960> to<00:05:24.039> solve 00:05:24.870 --> 00:05:24.880 align:start position:0% the the thing that we're trying to solve 00:05:24.880 --> 00:05:28.309 align:start position:0% the the thing that we're trying to solve here<00:05:25.960> um<00:05:26.960> and<00:05:27.160> that's<00:05:27.479> pretty<00:05:27.680> much<00:05:27.880> the<00:05:28.039> idea 00:05:28.309 --> 00:05:28.319 align:start position:0% here um and that's pretty much the idea 00:05:28.319 --> 00:05:30.590 align:start position:0% here um and that's pretty much the idea with<00:05:28.520> withdraw<00:05:29.199> requests<00:05:29.800> so<00:05:30.039> it's<00:05:30.160> a<00:05:30.319> request 00:05:30.590 --> 00:05:30.600 align:start position:0% with withdraw requests so it's a request 00:05:30.600 --> 00:05:32.790 align:start position:0% with withdraw requests so it's a request that<00:05:30.720> comes<00:05:30.880> from<00:05:31.039> the<00:05:31.120> e<00:05:31.520> goes<00:05:31.680> to<00:05:31.800> the<00:05:31.919> CL<00:05:32.680> and 00:05:32.790 --> 00:05:32.800 align:start position:0% that comes from the e goes to the CL and 00:05:32.800 --> 00:05:35.710 align:start position:0% that comes from the e goes to the CL and it's<00:05:33.000> got<00:05:33.479> um<00:05:33.759> pretty<00:05:33.960> much<00:05:34.280> three<00:05:35.280> uh<00:05:35.440> pieces 00:05:35.710 --> 00:05:35.720 align:start position:0% it's got um pretty much three uh pieces 00:05:35.720 --> 00:05:38.029 align:start position:0% it's got um pretty much three uh pieces of<00:05:35.919> information<00:05:36.520> one<00:05:36.759> is<00:05:36.880> the<00:05:37.039> source<00:05:37.360> address 00:05:38.029 --> 00:05:38.039 align:start position:0% of information one is the source address 00:05:38.039 --> 00:05:41.150 align:start position:0% of information one is the source address which<00:05:38.280> is<00:05:38.479> supposed<00:05:38.880> to<00:05:39.360> be<00:05:40.360> the<00:05:40.600> address<00:05:41.039> that 00:05:41.150 --> 00:05:41.160 align:start position:0% which is supposed to be the address that 00:05:41.160 --> 00:05:43.550 align:start position:0% which is supposed to be the address that you<00:05:41.360> have<00:05:41.600> set<00:05:41.880> as<00:05:42.039> withdraw<00:05:42.440> credential<00:05:43.120> on 00:05:43.550 --> 00:05:43.560 align:start position:0% you have set as withdraw credential on 00:05:43.560 --> 00:05:44.790 align:start position:0% you have set as withdraw credential on your 00:05:44.790 --> 00:05:44.800 align:start position:0% your 00:05:44.800 --> 00:05:47.510 align:start position:0% your validator<00:05:45.800> the<00:05:45.960> public<00:05:46.319> key<00:05:46.800> which<00:05:47.039> is 00:05:47.510 --> 00:05:47.520 align:start position:0% validator the public key which is 00:05:47.520 --> 00:05:49.230 align:start position:0% validator the public key which is basically<00:05:47.919> what<00:05:48.039> is<00:05:48.160> the<00:05:48.280> validator<00:05:48.800> you<00:05:49.000> send 00:05:49.230 --> 00:05:49.240 align:start position:0% basically what is the validator you send 00:05:49.240 --> 00:05:52.070 align:start position:0% basically what is the validator you send you're<00:05:49.400> sending<00:05:49.759> this<00:05:50.000> request<00:05:50.720> to<00:05:51.720> and<00:05:51.919> the 00:05:52.070 --> 00:05:52.080 align:start position:0% you're sending this request to and the 00:05:52.080 --> 00:05:54.909 align:start position:0% you're sending this request to and the amount<00:05:53.080> which<00:05:53.199> is<00:05:53.400> an<00:05:53.600> interesting<00:05:54.039> one<00:05:54.280> so 00:05:54.909 --> 00:05:54.919 align:start position:0% amount which is an interesting one so 00:05:54.919 --> 00:05:57.430 align:start position:0% amount which is an interesting one so before<00:05:55.199> we<00:05:55.319> didn't<00:05:55.560> have<00:05:55.720> the<00:05:56.080> amount<00:05:57.080> so<00:05:57.319> the 00:05:57.430 --> 00:05:57.440 align:start position:0% before we didn't have the amount so the 00:05:57.440 --> 00:06:00.430 align:start position:0% before we didn't have the amount so the amount<00:05:57.759> was<00:05:58.000> introduced<00:05:58.600> because<00:05:59.120> after<00:06:00.000> EIP 00:06:00.430 --> 00:06:00.440 align:start position:0% amount was introduced because after EIP 00:06:00.440 --> 00:06:02.909 align:start position:0% amount was introduced because after EIP 7251<00:06:01.319> if<00:06:01.400> you<00:06:01.520> guys<00:06:01.680> were<00:06:01.919> here<00:06:02.400> to<00:06:02.520> listen<00:06:02.759> to 00:06:02.909 --> 00:06:02.919 align:start position:0% 7251 if you guys were here to listen to 00:06:02.919 --> 00:06:05.670 align:start position:0% 7251 if you guys were here to listen to post<00:06:03.280> talk<00:06:03.520> on<00:06:03.720> Max<00:06:04.039> CB<00:06:05.039> now<00:06:05.199> it's<00:06:05.400> possible 00:06:05.670 --> 00:06:05.680 align:start position:0% post talk on Max CB now it's possible 00:06:05.680 --> 00:06:08.870 align:start position:0% post talk on Max CB now it's possible for<00:06:05.840> validators<00:06:06.400> to<00:06:06.639> have<00:06:06.960> more<00:06:07.240> than<00:06:07.440> 32<00:06:08.000> e<00:06:08.680> uh 00:06:08.870 --> 00:06:08.880 align:start position:0% for validators to have more than 32 e uh 00:06:08.880 --> 00:06:11.189 align:start position:0% for validators to have more than 32 e uh balance<00:06:09.639> right<00:06:10.360> so<00:06:10.680> technically<00:06:11.039> you<00:06:11.080> can 00:06:11.189 --> 00:06:11.199 align:start position:0% balance right so technically you can 00:06:11.199 --> 00:06:13.350 align:start position:0% balance right so technically you can have<00:06:11.280> a<00:06:11.400> validator<00:06:11.800> with<00:06:12.000> like<00:06:12.360> a<00:06:12.520> th000<00:06:13.080> eth 00:06:13.350 --> 00:06:13.360 align:start position:0% have a validator with like a th000 eth 00:06:13.360 --> 00:06:16.870 align:start position:0% have a validator with like a th000 eth or<00:06:13.520> something<00:06:14.039> stake<00:06:15.039> so<00:06:15.680> we<00:06:15.960> basically<00:06:16.440> split 00:06:16.870 --> 00:06:16.880 align:start position:0% or something stake so we basically split 00:06:16.880 --> 00:06:18.670 align:start position:0% or something stake so we basically split the<00:06:17.160> uh<00:06:17.280> the<00:06:17.400> withdraw<00:06:17.880> into<00:06:18.120> two<00:06:18.319> different 00:06:18.670 --> 00:06:18.680 align:start position:0% the uh the withdraw into two different 00:06:18.680 --> 00:06:21.589 align:start position:0% the uh the withdraw into two different types<00:06:18.919> of<00:06:19.120> withdraw<00:06:20.039> you<00:06:20.199> can<00:06:20.360> do<00:06:21.160> a<00:06:21.319> full 00:06:21.589 --> 00:06:21.599 align:start position:0% types of withdraw you can do a full 00:06:21.599 --> 00:06:23.510 align:start position:0% types of withdraw you can do a full withdraw<00:06:22.240> which<00:06:22.360> means<00:06:22.840> I<00:06:23.199> I<00:06:23.280> want<00:06:23.440> to 00:06:23.510 --> 00:06:23.520 align:start position:0% withdraw which means I I want to 00:06:23.520 --> 00:06:26.430 align:start position:0% withdraw which means I I want to withdraw<00:06:24.280> every<00:06:25.039> single<00:06:25.759> way<00:06:26.039> that<00:06:26.160> I<00:06:26.280> have 00:06:26.430 --> 00:06:26.440 align:start position:0% withdraw every single way that I have 00:06:26.440 --> 00:06:28.629 align:start position:0% withdraw every single way that I have staked<00:06:27.160> which<00:06:27.400> basically<00:06:27.800> translate<00:06:28.280> into<00:06:28.479> an 00:06:28.629 --> 00:06:28.639 align:start position:0% staked which basically translate into an 00:06:28.639 --> 00:06:31.350 align:start position:0% staked which basically translate into an exit<00:06:29.720> or<00:06:30.199> I<00:06:30.319> want<00:06:30.520> to<00:06:30.639> do<00:06:30.840> a<00:06:31.000> partial 00:06:31.350 --> 00:06:31.360 align:start position:0% exit or I want to do a partial 00:06:31.360 --> 00:06:33.270 align:start position:0% exit or I want to do a partial withdrawal<00:06:31.919> which<00:06:32.039> means<00:06:32.560> well<00:06:32.840> you<00:06:32.919> know<00:06:33.199> I 00:06:33.270 --> 00:06:33.280 align:start position:0% withdrawal which means well you know I 00:06:33.280 --> 00:06:35.790 align:start position:0% withdrawal which means well you know I have<00:06:33.599> 100<00:06:33.880> E<00:06:34.319> I<00:06:34.560> want<00:06:34.880> 50<00:06:35.199> back<00:06:35.440> because<00:06:35.599> I<00:06:35.680> want 00:06:35.790 --> 00:06:35.800 align:start position:0% have 100 E I want 50 back because I want 00:06:35.800 --> 00:06:37.790 align:start position:0% have 100 E I want 50 back because I want to<00:06:35.880> buy<00:06:36.000> a<00:06:36.120> new<00:06:36.280> car<00:06:36.440> or<00:06:36.599> something<00:06:37.199> so<00:06:37.440> you<00:06:37.639> do 00:06:37.790 --> 00:06:37.800 align:start position:0% to buy a new car or something so you do 00:06:37.800 --> 00:06:39.230 align:start position:0% to buy a new car or something so you do like<00:06:37.919> a<00:06:38.039> partial<00:06:38.319> withdrawal<00:06:38.800> you<00:06:38.919> get<00:06:39.080> it 00:06:39.230 --> 00:06:39.240 align:start position:0% like a partial withdrawal you get it 00:06:39.240 --> 00:06:41.670 align:start position:0% like a partial withdrawal you get it back<00:06:39.400> into<00:06:39.720> your<00:06:40.400> uh<00:06:40.759> account<00:06:41.400> and<00:06:41.479> then<00:06:41.599> you 00:06:41.670 --> 00:06:41.680 align:start position:0% back into your uh account and then you 00:06:41.680 --> 00:06:44.430 align:start position:0% back into your uh account and then you can<00:06:41.800> use<00:06:41.960> the<00:06:42.039> money<00:06:42.919> and<00:06:43.080> that's<00:06:43.360> the<00:06:44.039> we<00:06:44.199> use 00:06:44.430 --> 00:06:44.440 align:start position:0% can use the money and that's the we use 00:06:44.440 --> 00:06:46.189 align:start position:0% can use the money and that's the we use the<00:06:44.560> amount<00:06:44.840> Feud<00:06:45.120> for<00:06:45.280> that<00:06:45.440> so<00:06:45.800> an<00:06:45.919> amount 00:06:46.189 --> 00:06:46.199 align:start position:0% the amount Feud for that so an amount 00:06:46.199 --> 00:06:48.350 align:start position:0% the amount Feud for that so an amount equals<00:06:46.560> zero<00:06:46.840> means<00:06:47.080> a<00:06:47.240> full<00:06:47.479> withdraw<00:06:48.199> which 00:06:48.350 --> 00:06:48.360 align:start position:0% equals zero means a full withdraw which 00:06:48.360 --> 00:06:50.230 align:start position:0% equals zero means a full withdraw which can<00:06:48.479> be<00:06:48.599> a<00:06:48.720> bit<00:06:49.160> a<00:06:49.280> bit<00:06:49.440> weird<00:06:49.639> to<00:06:49.759> think<00:06:49.960> about 00:06:50.230 --> 00:06:50.240 align:start position:0% can be a bit a bit weird to think about 00:06:50.240 --> 00:06:52.790 align:start position:0% can be a bit a bit weird to think about but<00:06:50.639> and<00:06:50.840> an<00:06:51.000> amount<00:06:51.680> uh<00:06:51.800> greater<00:06:52.120> than<00:06:52.319> zero 00:06:52.790 --> 00:06:52.800 align:start position:0% but and an amount uh greater than zero 00:06:52.800 --> 00:06:54.670 align:start position:0% but and an amount uh greater than zero is<00:06:53.560> it's<00:06:53.680> like<00:06:53.800> a<00:06:53.960> partial<00:06:54.199> withdraw<00:06:54.520> I<00:06:54.599> just 00:06:54.670 --> 00:06:54.680 align:start position:0% is it's like a partial withdraw I just 00:06:54.680 --> 00:06:57.270 align:start position:0% is it's like a partial withdraw I just want<00:06:54.800> to<00:06:55.039> withdraw<00:06:55.479> part<00:06:55.599> of<00:06:55.759> my<00:06:56.280> stake 00:06:57.270 --> 00:06:57.280 align:start position:0% want to withdraw part of my stake 00:06:57.280 --> 00:06:59.110 align:start position:0% want to withdraw part of my stake hopefully<00:06:57.639> everything<00:06:58.400> makes<00:06:58.639> sense<00:06:58.840> until 00:06:59.110 --> 00:06:59.120 align:start position:0% hopefully everything makes sense until 00:06:59.120 --> 00:07:00.629 align:start position:0% hopefully everything makes sense until now 00:07:00.629 --> 00:07:00.639 align:start position:0% now 00:07:00.639 --> 00:07:02.749 align:start position:0% now um<00:07:01.120> and<00:07:01.479> on<00:07:01.639> this<00:07:01.800> diagram<00:07:02.199> I'm<00:07:02.319> trying<00:07:02.520> to 00:07:02.749 --> 00:07:02.759 align:start position:0% um and on this diagram I'm trying to 00:07:02.759 --> 00:07:05.749 align:start position:0% um and on this diagram I'm trying to capture<00:07:03.680> uh<00:07:03.960> how<00:07:04.720> things<00:07:05.039> have<00:07:05.240> changed 00:07:05.749 --> 00:07:05.759 align:start position:0% capture uh how things have changed 00:07:05.759 --> 00:07:08.670 align:start position:0% capture uh how things have changed compared<00:07:06.080> to<00:07:06.199> the<00:07:06.319> previous<00:07:06.759> diagram<00:07:07.759> so<00:07:08.560> the 00:07:08.670 --> 00:07:08.680 align:start position:0% compared to the previous diagram so the 00:07:08.680 --> 00:07:10.029 align:start position:0% compared to the previous diagram so the way<00:07:08.840> that<00:07:08.960> we're<00:07:09.120> creating<00:07:09.440> this<00:07:09.599> mechanism 00:07:10.029 --> 00:07:10.039 align:start position:0% way that we're creating this mechanism 00:07:10.039 --> 00:07:11.469 align:start position:0% way that we're creating this mechanism is<00:07:10.240> basically<00:07:10.759> now<00:07:11.039> we're<00:07:11.199> going<00:07:11.319> to 00:07:11.469 --> 00:07:11.479 align:start position:0% is basically now we're going to 00:07:11.479 --> 00:07:13.710 align:start position:0% is basically now we're going to introduce<00:07:12.080> this<00:07:12.639> withdraw<00:07:13.080> request<00:07:13.400> smart 00:07:13.710 --> 00:07:13.720 align:start position:0% introduce this withdraw request smart 00:07:13.720 --> 00:07:15.909 align:start position:0% introduce this withdraw request smart contract<00:07:14.080> on<00:07:14.199> the<00:07:14.319> execution<00:07:14.759> layer<00:07:15.120> side<00:07:15.759> and 00:07:15.909 --> 00:07:15.919 align:start position:0% contract on the execution layer side and 00:07:15.919 --> 00:07:19.309 align:start position:0% contract on the execution layer side and that<00:07:16.120> con<00:07:16.599> has<00:07:16.759> pretty<00:07:16.960> much<00:07:17.160> two<00:07:18.120> uh<00:07:19.120> two 00:07:19.309 --> 00:07:19.319 align:start position:0% that con has pretty much two uh two 00:07:19.319 --> 00:07:21.909 align:start position:0% that con has pretty much two uh two functional<00:07:20.160> two<00:07:20.400> functions<00:07:21.319> so<00:07:21.520> the<00:07:21.680> first 00:07:21.909 --> 00:07:21.919 align:start position:0% functional two functions so the first 00:07:21.919 --> 00:07:23.990 align:start position:0% functional two functions so the first one<00:07:22.400> is<00:07:22.840> a<00:07:23.080> function<00:07:23.400> that<00:07:23.560> the<00:07:23.639> user<00:07:23.800> is<00:07:23.879> going 00:07:23.990 --> 00:07:24.000 align:start position:0% one is a function that the user is going 00:07:24.000 --> 00:07:26.790 align:start position:0% one is a function that the user is going to<00:07:24.080> call<00:07:24.360> to<00:07:24.639> basically<00:07:25.400> create<00:07:25.800> a<00:07:26.319> a<00:07:26.479> request 00:07:26.790 --> 00:07:26.800 align:start position:0% to call to basically create a a request 00:07:26.800 --> 00:07:28.150 align:start position:0% to call to basically create a a request so<00:07:27.039> when<00:07:27.199> when<00:07:27.280> the<00:07:27.360> user<00:07:27.599> wants<00:07:27.720> to<00:07:27.840> create<00:07:28.039> a 00:07:28.150 --> 00:07:28.160 align:start position:0% so when when the user wants to create a 00:07:28.160 --> 00:07:29.710 align:start position:0% so when when the user wants to create a request<00:07:29.000> I'm<00:07:29.120> going<00:07:29.240> to<00:07:29.319> send<00:07:29.520> send<00:07:29.599> a 00:07:29.710 --> 00:07:29.720 align:start position:0% request I'm going to send send a 00:07:29.720 --> 00:07:32.189 align:start position:0% request I'm going to send send a transaction<00:07:30.440> signing<00:07:30.879> it<00:07:31.080> with<00:07:31.280> my<00:07:31.599> withdraw 00:07:32.189 --> 00:07:32.199 align:start position:0% transaction signing it with my withdraw 00:07:32.199 --> 00:07:35.390 align:start position:0% transaction signing it with my withdraw key<00:07:32.800> not<00:07:33.000> the<00:07:33.120> validator<00:07:33.800> key<00:07:34.800> and<00:07:34.960> the<00:07:35.080> Contra 00:07:35.390 --> 00:07:35.400 align:start position:0% key not the validator key and the Contra 00:07:35.400 --> 00:07:37.749 align:start position:0% key not the validator key and the Contra is<00:07:35.479> going<00:07:35.560> to<00:07:35.680> look<00:07:35.840> at<00:07:35.919> it<00:07:36.160> like<00:07:36.400> oh<00:07:36.800> okay<00:07:37.479> that 00:07:37.749 --> 00:07:37.759 align:start position:0% is going to look at it like oh okay that 00:07:37.759 --> 00:07:39.150 align:start position:0% is going to look at it like oh okay that that<00:07:37.919> that's<00:07:38.120> cool<00:07:38.400> someone's<00:07:38.720> creating<00:07:39.039> a 00:07:39.150 --> 00:07:39.160 align:start position:0% that that's cool someone's creating a 00:07:39.160 --> 00:07:41.230 align:start position:0% that that's cool someone's creating a withdraw<00:07:39.599> request<00:07:40.280> it's<00:07:40.400> going<00:07:40.520> to<00:07:40.680> set<00:07:41.000> that 00:07:41.230 --> 00:07:41.240 align:start position:0% withdraw request it's going to set that 00:07:41.240 --> 00:07:44.189 align:start position:0% withdraw request it's going to set that address<00:07:41.840> as<00:07:42.080> the<00:07:42.280> source<00:07:42.759> address<00:07:43.080> on<00:07:43.240> the 00:07:44.189 --> 00:07:44.199 align:start position:0% address as the source address on the 00:07:44.199 --> 00:07:46.710 align:start position:0% address as the source address on the request<00:07:45.199> uh<00:07:45.479> and<00:07:45.599> I'm<00:07:45.720> going<00:07:45.840> to<00:07:46.000> be<00:07:46.360> on<00:07:46.520> this 00:07:46.710 --> 00:07:46.720 align:start position:0% request uh and I'm going to be on this 00:07:46.720 --> 00:07:48.749 align:start position:0% request uh and I'm going to be on this request<00:07:47.199> here<00:07:47.759> we<00:07:47.960> pass<00:07:48.199> two<00:07:48.360> pieces<00:07:48.599> of 00:07:48.749 --> 00:07:48.759 align:start position:0% request here we pass two pieces of 00:07:48.759 --> 00:07:50.390 align:start position:0% request here we pass two pieces of information<00:07:49.159> the<00:07:49.280> validat<00:07:49.759> public<00:07:50.039> key<00:07:50.280> and 00:07:50.390 --> 00:07:50.400 align:start position:0% information the validat public key and 00:07:50.400 --> 00:07:53.670 align:start position:0% information the validat public key and the<00:07:50.800> amount<00:07:51.919> eventually<00:07:52.919> uh<00:07:53.039> the<00:07:53.159> execution 00:07:53.670 --> 00:07:53.680 align:start position:0% the amount eventually uh the execution 00:07:53.680 --> 00:07:55.670 align:start position:0% the amount eventually uh the execution client<00:07:54.000> is<00:07:54.120> going<00:07:54.240> to<00:07:54.759> call<00:07:55.039> the<00:07:55.159> contract<00:07:55.520> and 00:07:55.670 --> 00:07:55.680 align:start position:0% client is going to call the contract and 00:07:55.680 --> 00:07:57.749 align:start position:0% client is going to call the contract and read<00:07:56.120> uh<00:07:56.360> the<00:07:56.560> information<00:07:56.960> for<00:07:57.159> it<00:07:57.400> read<00:07:57.599> the 00:07:57.749 --> 00:07:57.759 align:start position:0% read uh the information for it read the 00:07:57.759 --> 00:07:59.670 align:start position:0% read uh the information for it read the request<00:07:58.080> that<00:07:58.199> are<00:07:58.319> on<00:07:58.479> the<00:07:58.639> on<00:07:58.720> the<00:07:58.840> Queue<00:07:59.199> the 00:07:59.670 --> 00:07:59.680 align:start position:0% request that are on the on the Queue the 00:07:59.680 --> 00:08:02.670 align:start position:0% request that are on the on the Queue the is<00:07:59.800> on<00:07:59.960> the<00:08:00.159> contract<00:08:00.720> State<00:08:01.720> and<00:08:02.199> send<00:08:02.479> it 00:08:02.670 --> 00:08:02.680 align:start position:0% is on the contract State and send it 00:08:02.680 --> 00:08:05.070 align:start position:0% is on the contract State and send it over<00:08:02.960> to<00:08:03.120> the<00:08:03.240> Bono<00:08:03.759> to<00:08:03.960> engine<00:08:04.280> API<00:08:04.919> and 00:08:05.070 --> 00:08:05.080 align:start position:0% over to the Bono to engine API and 00:08:05.080 --> 00:08:06.430 align:start position:0% over to the Bono to engine API and that's<00:08:05.280> I'm<00:08:05.400> not<00:08:05.520> going<00:08:05.599> to<00:08:05.720> go<00:08:05.879> in<00:08:06.039> a<00:08:06.159> lot<00:08:06.280> of 00:08:06.430 --> 00:08:06.440 align:start position:0% that's I'm not going to go in a lot of 00:08:06.440 --> 00:08:08.749 align:start position:0% that's I'm not going to go in a lot of details<00:08:06.879> of<00:08:07.039> that<00:08:07.240> because<00:08:07.919> again<00:08:08.280> not<00:08:08.520> a<00:08:08.599> lot 00:08:08.749 --> 00:08:08.759 align:start position:0% details of that because again not a lot 00:08:08.759 --> 00:08:11.830 align:start position:0% details of that because again not a lot of<00:08:08.960> time<00:08:09.879> but<00:08:10.319> basically<00:08:11.240> when<00:08:11.479> whenever<00:08:11.720> it's 00:08:11.830 --> 00:08:11.840 align:start position:0% of time but basically when whenever it's 00:08:11.840 --> 00:08:13.510 align:start position:0% of time but basically when whenever it's time<00:08:12.000> to<00:08:12.120> create<00:08:12.319> a<00:08:12.400> block<00:08:12.720> and<00:08:13.000> the<00:08:13.120> beon<00:08:13.360> node 00:08:13.510 --> 00:08:13.520 align:start position:0% time to create a block and the beon node 00:08:13.520 --> 00:08:15.589 align:start position:0% time to create a block and the beon node is<00:08:13.599> going<00:08:13.680> to<00:08:13.840> receive<00:08:14.440> those<00:08:14.720> requests<00:08:15.319> from 00:08:15.589 --> 00:08:15.599 align:start position:0% is going to receive those requests from 00:08:15.599 --> 00:08:18.589 align:start position:0% is going to receive those requests from the<00:08:16.039> El<00:08:17.039> uh<00:08:17.199> some<00:08:17.440> verification<00:08:18.120> happens<00:08:18.400> and 00:08:18.589 --> 00:08:18.599 align:start position:0% the El uh some verification happens and 00:08:18.599 --> 00:08:20.710 align:start position:0% the El uh some verification happens and everything<00:08:19.440> and<00:08:19.599> then<00:08:19.879> the<00:08:20.000> authorization 00:08:20.710 --> 00:08:20.720 align:start position:0% everything and then the authorization 00:08:20.720 --> 00:08:22.589 align:start position:0% everything and then the authorization part<00:08:21.319> uh<00:08:21.479> happens<00:08:21.720> on<00:08:21.840> the<00:08:21.960> consensus<00:08:22.440> side 00:08:22.589 --> 00:08:22.599 align:start position:0% part uh happens on the consensus side 00:08:22.599 --> 00:08:24.230 align:start position:0% part uh happens on the consensus side it's<00:08:22.720> going<00:08:22.800> to<00:08:22.919> look<00:08:23.000> at<00:08:23.120> the<00:08:23.199> request<00:08:24.039> make 00:08:24.230 --> 00:08:24.240 align:start position:0% it's going to look at the request make 00:08:24.240 --> 00:08:26.629 align:start position:0% it's going to look at the request make sure<00:08:24.560> that<00:08:24.800> the<00:08:25.400> source<00:08:25.879> address<00:08:26.240> so<00:08:26.479> the 00:08:26.629 --> 00:08:26.639 align:start position:0% sure that the source address so the 00:08:26.639 --> 00:08:27.990 align:start position:0% sure that the source address so the account<00:08:26.879> that<00:08:27.000> is<00:08:27.080> send<00:08:27.240> in<00:08:27.360> this<00:08:27.479> transaction 00:08:27.990 --> 00:08:28.000 align:start position:0% account that is send in this transaction 00:08:28.000 --> 00:08:30.110 align:start position:0% account that is send in this transaction here<00:08:28.319> matches<00:08:28.800> the<00:08:29.000> with<00:08:29.520> credentials<00:08:29.919> on<00:08:30.039> the 00:08:30.110 --> 00:08:30.120 align:start position:0% here matches the with credentials on the 00:08:30.120 --> 00:08:33.269 align:start position:0% here matches the with credentials on the validator<00:08:30.599> on<00:08:30.680> the<00:08:30.800> consensus<00:08:31.519> side<00:08:32.519> and<00:08:33.159> um 00:08:33.269 --> 00:08:33.279 align:start position:0% validator on the consensus side and um 00:08:33.279 --> 00:08:35.110 align:start position:0% validator on the consensus side and um some<00:08:33.479> other<00:08:33.839> rules<00:08:34.200> you<00:08:34.320> know<00:08:34.479> make<00:08:34.599> sure<00:08:34.760> that 00:08:35.110 --> 00:08:35.120 align:start position:0% some other rules you know make sure that 00:08:35.120 --> 00:08:36.990 align:start position:0% some other rules you know make sure that you<00:08:35.599> exit<00:08:35.880> you're<00:08:36.039> creating<00:08:36.360> a<00:08:36.560> request<00:08:36.839> for 00:08:36.990 --> 00:08:37.000 align:start position:0% you exit you're creating a request for 00:08:37.000 --> 00:08:38.870 align:start position:0% you exit you're creating a request for the<00:08:37.120> right<00:08:37.320> validator<00:08:37.959> and 00:08:38.870 --> 00:08:38.880 align:start position:0% the right validator and 00:08:38.880 --> 00:08:41.550 align:start position:0% the right validator and everything<00:08:39.880> cool<00:08:40.440> so<00:08:40.680> hopefully<00:08:41.039> this<00:08:41.240> makes 00:08:41.550 --> 00:08:41.560 align:start position:0% everything cool so hopefully this makes 00:08:41.560 --> 00:08:43.790 align:start position:0% everything cool so hopefully this makes a<00:08:41.719> bit<00:08:41.880> more<00:08:42.039> sense<00:08:42.959> uh<00:08:43.120> one<00:08:43.320> interesting 00:08:43.790 --> 00:08:43.800 align:start position:0% a bit more sense uh one interesting 00:08:43.800 --> 00:08:45.550 align:start position:0% a bit more sense uh one interesting thing<00:08:44.159> uh<00:08:44.240> to<00:08:44.399> note<00:08:44.720> here<00:08:45.080> and<00:08:45.200> that<00:08:45.320> was 00:08:45.550 --> 00:08:45.560 align:start position:0% thing uh to note here and that was 00:08:45.560 --> 00:08:47.230 align:start position:0% thing uh to note here and that was actually<00:08:46.160> probably<00:08:46.519> like<00:08:46.720> half<00:08:46.920> of<00:08:47.080> my 00:08:47.230 --> 00:08:47.240 align:start position:0% actually probably like half of my 00:08:47.240 --> 00:08:49.630 align:start position:0% actually probably like half of my original<00:08:47.680> talk<00:08:48.560> is<00:08:48.800> that<00:08:48.959> when<00:08:49.080> you<00:08:49.240> look<00:08:49.399> at 00:08:49.630 --> 00:08:49.640 align:start position:0% original talk is that when you look at 00:08:49.640 --> 00:08:54.389 align:start position:0% original talk is that when you look at this<00:08:51.000> uh<00:08:52.000> this<00:08:52.399> kind<00:08:52.560> of<00:08:52.800> Orange<00:08:53.320> area<00:08:53.760> here 00:08:54.389 --> 00:08:54.399 align:start position:0% this uh this kind of Orange area here 00:08:54.399 --> 00:08:56.590 align:start position:0% this uh this kind of Orange area here you<00:08:54.519> can<00:08:54.680> see<00:08:54.920> that<00:08:55.080> this<00:08:55.320> mechanism<00:08:55.880> for 00:08:56.590 --> 00:08:56.600 align:start position:0% you can see that this mechanism for 00:08:56.600 --> 00:08:59.829 align:start position:0% you can see that this mechanism for sending<00:08:57.519> requests<00:08:58.040> from<00:08:58.279> E<00:08:58.640> to<00:08:58.800> CL<00:08:59.519> can<00:08:59.680> be 00:08:59.829 --> 00:08:59.839 align:start position:0% sending requests from E to CL can be 00:08:59.839 --> 00:09:02.389 align:start position:0% sending requests from E to CL can be quite<00:09:00.040> useful<00:09:00.600> for<00:09:01.360> a<00:09:01.440> bunch<00:09:01.640> of<00:09:01.800> different 00:09:02.389 --> 00:09:02.399 align:start position:0% quite useful for a bunch of different 00:09:02.399 --> 00:09:05.430 align:start position:0% quite useful for a bunch of different things<00:09:03.399> and<00:09:04.079> yep<00:09:04.320> we<00:09:04.440> did<00:09:04.600> notice<00:09:05.000> that<00:09:05.240> and 00:09:05.430 --> 00:09:05.440 align:start position:0% things and yep we did notice that and 00:09:05.440 --> 00:09:08.910 align:start position:0% things and yep we did notice that and that's<00:09:05.720> why<00:09:06.200> we<00:09:06.480> have<00:09:07.240> um<00:09:07.839> EIP 00:09:08.910 --> 00:09:08.920 align:start position:0% that's why we have um EIP 00:09:08.920 --> 00:09:12.269 align:start position:0% that's why we have um EIP 7685<00:09:09.920> which<00:09:10.240> introduced<00:09:10.920> this<00:09:11.120> concept<00:09:11.640> of<00:09:12.120> uh 00:09:12.269 --> 00:09:12.279 align:start position:0% 7685 which introduced this concept of uh 00:09:12.279 --> 00:09:15.630 align:start position:0% 7685 which introduced this concept of uh execu<00:09:12.959> um<00:09:13.720> general<00:09:14.160> purpose<00:09:14.680> execution<00:09:15.200> layer 00:09:15.630 --> 00:09:15.640 align:start position:0% execu um general purpose execution layer 00:09:15.640 --> 00:09:18.230 align:start position:0% execu um general purpose execution layer requests<00:09:16.120> so<00:09:16.880> now<00:09:17.120> we<00:09:17.240> already<00:09:17.600> have<00:09:17.839> all<00:09:18.040> this 00:09:18.230 --> 00:09:18.240 align:start position:0% requests so now we already have all this 00:09:18.240 --> 00:09:19.910 align:start position:0% requests so now we already have all this mechanism<00:09:18.760> for<00:09:18.959> creating<00:09:19.399> different<00:09:19.720> types 00:09:19.910 --> 00:09:19.920 align:start position:0% mechanism for creating different types 00:09:19.920 --> 00:09:22.590 align:start position:0% mechanism for creating different types of<00:09:20.120> requests<00:09:21.040> for<00:09:21.399> the<00:09:21.519> next<00:09:21.720> four<00:09:22.079> Spectra<00:09:22.480> we 00:09:22.590 --> 00:09:22.600 align:start position:0% of requests for the next four Spectra we 00:09:22.600 --> 00:09:24.430 align:start position:0% of requests for the next four Spectra we already<00:09:22.880> have<00:09:23.040> three<00:09:23.279> types<00:09:23.560> of<00:09:23.680> requests<00:09:24.240> we 00:09:24.430 --> 00:09:24.440 align:start position:0% already have three types of requests we 00:09:24.440 --> 00:09:25.990 align:start position:0% already have three types of requests we have<00:09:24.760> withdrawals<00:09:25.399> the<00:09:25.480> ones<00:09:25.640> that<00:09:25.760> we<00:09:25.839> were 00:09:25.990 --> 00:09:26.000 align:start position:0% have withdrawals the ones that we were 00:09:26.000 --> 00:09:28.550 align:start position:0% have withdrawals the ones that we were just<00:09:26.160> talking<00:09:26.440> about<00:09:27.240> we<00:09:27.480> have<00:09:27.839> deposits<00:09:28.440> the 00:09:28.550 --> 00:09:28.560 align:start position:0% just talking about we have deposits the 00:09:28.560 --> 00:09:29.790 align:start position:0% just talking about we have deposits the one<00:09:28.720> that<00:09:28.839> Stephan's<00:09:29.160> going<00:09:29.240> to<00:09:29.480> talking 00:09:29.790 --> 00:09:29.800 align:start position:0% one that Stephan's going to talking 00:09:29.800 --> 00:09:32.230 align:start position:0% one that Stephan's going to talking about<00:09:30.800> and<00:09:31.240> if<00:09:31.360> you<00:09:31.519> were<00:09:31.760> here<00:09:31.920> for<00:09:32.120> the 00:09:32.230 --> 00:09:32.240 align:start position:0% about and if you were here for the 00:09:32.240 --> 00:09:34.110 align:start position:0% about and if you were here for the previous<00:09:32.560> talk<00:09:32.959> consolidations<00:09:33.680> it<00:09:33.880> also 00:09:34.110 --> 00:09:34.120 align:start position:0% previous talk consolidations it also 00:09:34.120 --> 00:09:36.069 align:start position:0% previous talk consolidations it also happens<00:09:34.480> through<00:09:34.839> a<00:09:35.160> execution<00:09:35.640> layer 00:09:36.069 --> 00:09:36.079 align:start position:0% happens through a execution layer 00:09:36.079 --> 00:09:39.389 align:start position:0% happens through a execution layer request<00:09:37.079> so<00:09:37.800> um<00:09:38.120> that<00:09:38.279> was<00:09:38.800> kind<00:09:38.920> of<00:09:39.040> the<00:09:39.160> most 00:09:39.389 --> 00:09:39.399 align:start position:0% request so um that was kind of the most 00:09:39.399 --> 00:09:42.389 align:start position:0% request so um that was kind of the most interesting<00:09:39.880> part<00:09:40.079> of<00:09:40.480> uh<00:09:40.720> this<00:09:41.160> uh<00:09:41.320> system<00:09:41.720> so 00:09:42.389 --> 00:09:42.399 align:start position:0% interesting part of uh this uh system so 00:09:42.399 --> 00:09:43.710 align:start position:0% interesting part of uh this uh system so yeah<00:09:42.600> take<00:09:42.760> a<00:09:42.839> look<00:09:43.000> into<00:09:43.200> that<00:09:43.360> because<00:09:43.519> it's 00:09:43.710 --> 00:09:43.720 align:start position:0% yeah take a look into that because it's 00:09:43.720 --> 00:09:44.990 align:start position:0% yeah take a look into that because it's pretty 00:09:44.990 --> 00:09:45.000 align:start position:0% pretty 00:09:45.000 --> 00:09:47.190 align:start position:0% pretty cool<00:09:46.000> uh<00:09:46.160> before<00:09:46.399> I<00:09:46.519> finish<00:09:46.760> I<00:09:46.880> just<00:09:47.000> want<00:09:47.079> to 00:09:47.190 --> 00:09:47.200 align:start position:0% cool uh before I finish I just want to 00:09:47.200 --> 00:09:49.269 align:start position:0% cool uh before I finish I just want to go<00:09:47.360> through<00:09:47.600> a<00:09:47.720> few<00:09:48.160> uh<00:09:48.360> caveats<00:09:49.000> because<00:09:49.200> you 00:09:49.269 --> 00:09:49.279 align:start position:0% go through a few uh caveats because you 00:09:49.279 --> 00:09:50.550 align:start position:0% go through a few uh caveats because you know<00:09:49.480> there's<00:09:49.640> no<00:09:49.760> free<00:09:50.000> lunch<00:09:50.360> there's 00:09:50.550 --> 00:09:50.560 align:start position:0% know there's no free lunch there's 00:09:50.560 --> 00:09:51.710 align:start position:0% know there's no free lunch there's always<00:09:50.800> something<00:09:51.079> that<00:09:51.160> you<00:09:51.279> need<00:09:51.399> to<00:09:51.560> give 00:09:51.710 --> 00:09:51.720 align:start position:0% always something that you need to give 00:09:51.720 --> 00:09:55.150 align:start position:0% always something that you need to give away<00:09:52.600> so<00:09:53.600> the<00:09:53.800> problem<00:09:54.079> with<00:09:54.519> uh<00:09:54.680> withraw 00:09:55.150 --> 00:09:55.160 align:start position:0% away so the problem with uh withraw 00:09:55.160 --> 00:09:57.030 align:start position:0% away so the problem with uh withraw requests<00:09:55.600> and<00:09:55.839> kind<00:09:55.959> of<00:09:56.120> the<00:09:56.519> execution 00:09:57.030 --> 00:09:57.040 align:start position:0% requests and kind of the execution 00:09:57.040 --> 00:10:00.470 align:start position:0% requests and kind of the execution requests<00:09:57.399> in<00:09:57.600> general<00:09:58.040> is<00:09:58.240> that 00:10:00.470 --> 00:10:00.480 align:start position:0% requests in general is that 00:10:00.480 --> 00:10:02.870 align:start position:0% requests in general is that but<00:10:00.959> creating<00:10:01.399> a<00:10:01.600> successful<00:10:02.160> transaction<00:10:02.720> on 00:10:02.870 --> 00:10:02.880 align:start position:0% but creating a successful transaction on 00:10:02.880 --> 00:10:05.790 align:start position:0% but creating a successful transaction on the<00:10:03.000> El<00:10:03.480> side<00:10:03.720> like<00:10:04.320> creating<00:10:04.680> a<00:10:04.880> request 00:10:05.790 --> 00:10:05.800 align:start position:0% the El side like creating a request 00:10:05.800 --> 00:10:08.430 align:start position:0% the El side like creating a request doesn't<00:10:06.720> guarantee<00:10:07.480> that<00:10:07.680> that<00:10:07.920> request<00:10:08.320> is 00:10:08.430 --> 00:10:08.440 align:start position:0% doesn't guarantee that that request is 00:10:08.440 --> 00:10:11.310 align:start position:0% doesn't guarantee that that request is going<00:10:08.560> to<00:10:08.720> be<00:10:09.079> successfully<00:10:09.880> processed<00:10:10.560> on 00:10:11.310 --> 00:10:11.320 align:start position:0% going to be successfully processed on 00:10:11.320 --> 00:10:13.829 align:start position:0% going to be successfully processed on the<00:10:11.560> consensus<00:10:12.000> layer<00:10:12.519> side<00:10:13.519> I<00:10:13.640> know<00:10:13.760> it 00:10:13.829 --> 00:10:13.839 align:start position:0% the consensus layer side I know it 00:10:13.839 --> 00:10:16.389 align:start position:0% the consensus layer side I know it sounds<00:10:14.040> a<00:10:14.160> bit<00:10:14.320> weird<00:10:14.680> so<00:10:15.200> it<00:10:15.640> the<00:10:16.000> the<00:10:16.079> user 00:10:16.389 --> 00:10:16.399 align:start position:0% sounds a bit weird so it the the user 00:10:16.399 --> 00:10:17.829 align:start position:0% sounds a bit weird so it the the user experience<00:10:16.760> is<00:10:16.880> a<00:10:16.959> bit<00:10:17.120> clunky<00:10:17.480> you<00:10:17.640> kind<00:10:17.720> of 00:10:17.829 --> 00:10:17.839 align:start position:0% experience is a bit clunky you kind of 00:10:17.839 --> 00:10:19.870 align:start position:0% experience is a bit clunky you kind of need<00:10:17.959> to<00:10:18.519> look<00:10:18.720> at<00:10:18.839> the<00:10:18.959> consensus<00:10:19.440> side<00:10:19.720> make 00:10:19.870 --> 00:10:19.880 align:start position:0% need to look at the consensus side make 00:10:19.880 --> 00:10:22.190 align:start position:0% need to look at the consensus side make sure<00:10:20.040> that<00:10:20.240> everything<00:10:21.040> works<00:10:21.399> out<00:10:21.920> create 00:10:22.190 --> 00:10:22.200 align:start position:0% sure that everything works out create 00:10:22.200 --> 00:10:23.910 align:start position:0% sure that everything works out create the<00:10:22.399> request<00:10:22.800> and<00:10:23.000> that<00:10:23.200> just<00:10:23.480> kind<00:10:23.600> of<00:10:23.720> hope 00:10:23.910 --> 00:10:23.920 align:start position:0% the request and that just kind of hope 00:10:23.920 --> 00:10:25.110 align:start position:0% the request and that just kind of hope that<00:10:24.040> nothing's<00:10:24.320> going<00:10:24.399> to<00:10:24.519> change<00:10:24.760> in<00:10:24.920> this 00:10:25.110 --> 00:10:25.120 align:start position:0% that nothing's going to change in this 00:10:25.120 --> 00:10:26.910 align:start position:0% that nothing's going to change in this in<00:10:25.240> between<00:10:26.200> um<00:10:26.360> hopefully<00:10:26.600> it's<00:10:26.720> not<00:10:26.839> going 00:10:26.910 --> 00:10:26.920 align:start position:0% in between um hopefully it's not going 00:10:26.920 --> 00:10:30.230 align:start position:0% in between um hopefully it's not going to<00:10:27.040> be<00:10:27.160> too<00:10:27.399> bad<00:10:27.760> but<00:10:27.920> it's<00:10:28.760> it<00:10:28.880> can<00:10:29.440> it<00:10:29.560> can 00:10:30.230 --> 00:10:30.240 align:start position:0% to be too bad but it's it can it can 00:10:30.240 --> 00:10:33.030 align:start position:0% to be too bad but it's it can it can happen<00:10:31.240> and<00:10:31.519> another<00:10:31.880> interesting<00:10:32.320> thing<00:10:32.640> is 00:10:33.030 --> 00:10:33.040 align:start position:0% happen and another interesting thing is 00:10:33.040 --> 00:10:35.110 align:start position:0% happen and another interesting thing is if<00:10:33.160> you<00:10:33.320> currently<00:10:33.839> have<00:10:34.079> a<00:10:34.240> validator<00:10:35.000> and 00:10:35.110 --> 00:10:35.120 align:start position:0% if you currently have a validator and 00:10:35.120 --> 00:10:38.750 align:start position:0% if you currently have a validator and your<00:10:35.279> validator<00:10:36.000> has<00:10:36.720> a<00:10:37.720> contract<00:10:38.200> address 00:10:38.750 --> 00:10:38.760 align:start position:0% your validator has a contract address 00:10:38.760 --> 00:10:40.389 align:start position:0% your validator has a contract address set<00:10:39.120> as<00:10:39.279> withdraw 00:10:40.389 --> 00:10:40.399 align:start position:0% set as withdraw 00:10:40.399 --> 00:10:43.870 align:start position:0% set as withdraw credentials<00:10:41.760> um<00:10:42.760> well<00:10:43.440> things<00:10:43.600> are<00:10:43.720> going<00:10:43.800> to 00:10:43.870 --> 00:10:43.880 align:start position:0% credentials um well things are going to 00:10:43.880 --> 00:10:46.150 align:start position:0% credentials um well things are going to be<00:10:44.000> a<00:10:44.120> bit<00:10:44.399> bit<00:10:44.560> more<00:10:44.880> complicated<00:10:45.880> uh<00:10:45.959> for 00:10:46.150 --> 00:10:46.160 align:start position:0% be a bit bit more complicated uh for 00:10:46.160 --> 00:10:47.389 align:start position:0% be a bit bit more complicated uh for those<00:10:46.279> of<00:10:46.440> you<00:10:46.560> who<00:10:46.680> are<00:10:46.800> familiar<00:10:47.120> with<00:10:47.240> the 00:10:47.389 --> 00:10:47.399 align:start position:0% those of you who are familiar with the 00:10:47.399 --> 00:10:49.949 align:start position:0% those of you who are familiar with the evm<00:10:48.399> uh<00:10:48.600> the<00:10:48.800> contract<00:10:49.200> that<00:10:49.320> is<00:10:49.440> creating<00:10:49.800> the 00:10:49.949 --> 00:10:49.959 align:start position:0% evm uh the contract that is creating the 00:10:49.959 --> 00:10:51.910 align:start position:0% evm uh the contract that is creating the request<00:10:50.959> is<00:10:51.079> not<00:10:51.320> looking<00:10:51.600> at<00:10:51.760> the 00:10:51.910 --> 00:10:51.920 align:start position:0% request is not looking at the 00:10:51.920 --> 00:10:54.150 align:start position:0% request is not looking at the transaction<00:10:52.399> sender<00:10:53.279> for<00:10:53.480> authentication 00:10:54.150 --> 00:10:54.160 align:start position:0% transaction sender for authentication 00:10:54.160 --> 00:10:57.030 align:start position:0% transaction sender for authentication it's<00:10:54.320> looking<00:10:54.600> for<00:10:54.880> the<00:10:55.040> message<00:10:55.880> caller<00:10:56.880> so 00:10:57.030 --> 00:10:57.040 align:start position:0% it's looking for the message caller so 00:10:57.040 --> 00:10:59.030 align:start position:0% it's looking for the message caller so that<00:10:57.160> means<00:10:57.519> that<00:10:57.839> if<00:10:58.000> you<00:10:58.240> are<00:10:58.519> interacting 00:10:59.030 --> 00:10:59.040 align:start position:0% that means that if you are interacting 00:10:59.040 --> 00:11:02.470 align:start position:0% that means that if you are interacting with<00:10:59.360> the<00:10:59.519> request<00:11:00.000> contract<00:11:00.720> using<00:11:01.079> a<00:11:01.240> smart 00:11:02.470 --> 00:11:02.480 align:start position:0% with the request contract using a smart 00:11:02.480 --> 00:11:04.829 align:start position:0% with the request contract using a smart contract<00:11:03.480> the<00:11:03.680> smart<00:11:04.040> contract<00:11:04.440> address<00:11:04.760> is 00:11:04.829 --> 00:11:04.839 align:start position:0% contract the smart contract address is 00:11:04.839 --> 00:11:06.030 align:start position:0% contract the smart contract address is going<00:11:04.959> to<00:11:05.040> be<00:11:05.160> the<00:11:05.279> one<00:11:05.480> that's<00:11:05.639> going<00:11:05.760> to<00:11:05.839> end 00:11:06.030 --> 00:11:06.040 align:start position:0% going to be the one that's going to end 00:11:06.040 --> 00:11:09.949 align:start position:0% going to be the one that's going to end up<00:11:06.200> on<00:11:06.360> the<00:11:06.480> source<00:11:06.800> address<00:11:07.800> right<00:11:08.600> so<00:11:09.399> for 00:11:09.949 --> 00:11:09.959 align:start position:0% up on the source address right so for 00:11:09.959 --> 00:11:12.150 align:start position:0% up on the source address right so for this<00:11:10.120> whole<00:11:10.279> thing<00:11:10.440> to<00:11:10.680> work<00:11:11.360> your<00:11:11.600> validator 00:11:12.150 --> 00:11:12.160 align:start position:0% this whole thing to work your validator 00:11:12.160 --> 00:11:14.710 align:start position:0% this whole thing to work your validator withdraw<00:11:12.560> credentials<00:11:13.240> has<00:11:13.399> to<00:11:13.639> be<00:11:14.480> the 00:11:14.710 --> 00:11:14.720 align:start position:0% withdraw credentials has to be the 00:11:14.720 --> 00:11:16.750 align:start position:0% withdraw credentials has to be the contract<00:11:15.120> address<00:11:15.639> not<00:11:15.839> the<00:11:16.000> add<00:11:16.360> not<00:11:16.639> the 00:11:16.750 --> 00:11:16.760 align:start position:0% contract address not the add not the 00:11:16.760 --> 00:11:18.150 align:start position:0% contract address not the add not the account<00:11:17.000> that<00:11:17.120> is<00:11:17.200> sent<00:11:17.440> in<00:11:17.519> the 00:11:18.150 --> 00:11:18.160 align:start position:0% account that is sent in the 00:11:18.160 --> 00:11:21.829 align:start position:0% account that is sent in the transaction<00:11:19.160> so<00:11:19.639> again<00:11:20.639> I'm<00:11:21.200> sorry<00:11:21.480> for<00:11:21.680> you 00:11:21.829 --> 00:11:21.839 align:start position:0% transaction so again I'm sorry for you 00:11:21.839 --> 00:11:24.389 align:start position:0% transaction so again I'm sorry for you if<00:11:21.920> you're<00:11:22.079> in<00:11:22.200> this<00:11:22.920> situation<00:11:23.920> um<00:11:24.079> hopefully 00:11:24.389 --> 00:11:24.399 align:start position:0% if you're in this situation um hopefully 00:11:24.399 --> 00:11:26.269 align:start position:0% if you're in this situation um hopefully if<00:11:24.480> you<00:11:24.680> have<00:11:25.040> upgradeable<00:11:25.600> smart<00:11:25.920> contract 00:11:26.269 --> 00:11:26.279 align:start position:0% if you have upgradeable smart contract 00:11:26.279 --> 00:11:27.590 align:start position:0% if you have upgradeable smart contract you<00:11:26.360> can<00:11:26.480> kind<00:11:26.600> of<00:11:26.720> get<00:11:26.839> away<00:11:27.079> with<00:11:27.200> it<00:11:27.399> you<00:11:27.480> can 00:11:27.590 --> 00:11:27.600 align:start position:0% you can kind of get away with it you can 00:11:27.600 --> 00:11:29.870 align:start position:0% you can kind of get away with it you can use<00:11:27.800> like<00:11:27.959> delegate<00:11:28.360> calls<00:11:28.720> and<00:11:28.839> do<00:11:29.000> some<00:11:29.399> very 00:11:29.870 --> 00:11:29.880 align:start position:0% use like delegate calls and do some very 00:11:29.880 --> 00:11:32.310 align:start position:0% use like delegate calls and do some very smart<00:11:30.360> stuff<00:11:30.680> to<00:11:30.839> make<00:11:31.000> it<00:11:31.160> work<00:11:32.040> uh<00:11:32.200> that's 00:11:32.310 --> 00:11:32.320 align:start position:0% smart stuff to make it work uh that's 00:11:32.320 --> 00:11:33.750 align:start position:0% smart stuff to make it work uh that's not<00:11:32.480> my<00:11:32.680> expertise<00:11:33.200> I'm<00:11:33.279> not<00:11:33.399> going<00:11:33.480> to<00:11:33.639> talk 00:11:33.750 --> 00:11:33.760 align:start position:0% not my expertise I'm not going to talk 00:11:33.760 --> 00:11:35.990 align:start position:0% not my expertise I'm not going to talk too<00:11:33.959> much<00:11:34.160> about<00:11:34.320> it<00:11:34.560> but<00:11:35.040> there<00:11:35.200> is<00:11:35.320> a<00:11:35.519> way<00:11:35.760> for 00:11:35.990 --> 00:11:36.000 align:start position:0% too much about it but there is a way for 00:11:36.000 --> 00:11:38.790 align:start position:0% too much about it but there is a way for you<00:11:36.880> uh<00:11:37.519> but<00:11:37.680> yeah<00:11:37.959> just<00:11:38.160> keep<00:11:38.360> that<00:11:38.480> in<00:11:38.560> mind 00:11:38.790 --> 00:11:38.800 align:start position:0% you uh but yeah just keep that in mind 00:11:38.800 --> 00:11:40.710 align:start position:0% you uh but yeah just keep that in mind when<00:11:38.920> you<00:11:39.480> uh<00:11:39.600> looking<00:11:39.839> into 00:11:40.710 --> 00:11:40.720 align:start position:0% when you uh looking into 00:11:40.720 --> 00:11:43.710 align:start position:0% when you uh looking into this<00:11:41.720> um<00:11:42.440> oh<00:11:42.639> yeah<00:11:42.839> one<00:11:43.079> important<00:11:43.440> thing<00:11:43.600> is 00:11:43.710 --> 00:11:43.720 align:start position:0% this um oh yeah one important thing is 00:11:43.720 --> 00:11:45.550 align:start position:0% this um oh yeah one important thing is that<00:11:43.959> this<00:11:44.160> does<00:11:44.360> not<00:11:44.600> replace<00:11:45.040> voluntary 00:11:45.550 --> 00:11:45.560 align:start position:0% that this does not replace voluntary 00:11:45.560 --> 00:11:48.230 align:start position:0% that this does not replace voluntary exits<00:11:46.000> voluntary<00:11:46.519> exits<00:11:46.959> are<00:11:47.279> still<00:11:48.040> the 00:11:48.230 --> 00:11:48.240 align:start position:0% exits voluntary exits are still the 00:11:48.240 --> 00:11:50.430 align:start position:0% exits voluntary exits are still the easiest<00:11:48.639> way<00:11:48.760> to<00:11:49.000> exit<00:11:49.320> your<00:11:49.440> validator<00:11:50.320> if 00:11:50.430 --> 00:11:50.440 align:start position:0% easiest way to exit your validator if 00:11:50.440 --> 00:11:52.750 align:start position:0% easiest way to exit your validator if you<00:11:50.600> have<00:11:50.760> the<00:11:50.920> validator<00:11:51.360> key<00:11:52.040> you<00:11:52.279> sign<00:11:52.600> the 00:11:52.750 --> 00:11:52.760 align:start position:0% you have the validator key you sign the 00:11:52.760 --> 00:11:54.590 align:start position:0% you have the validator key you sign the message<00:11:53.360> it's<00:11:53.519> going<00:11:53.639> to<00:11:53.720> be<00:11:53.920> broadcast<00:11:54.440> to 00:11:54.590 --> 00:11:54.600 align:start position:0% message it's going to be broadcast to 00:11:54.600 --> 00:11:56.389 align:start position:0% message it's going to be broadcast to the<00:11:54.760> network<00:11:55.279> it<00:11:55.360> doesn't<00:11:55.639> cost<00:11:55.839> you<00:11:56.000> gas<00:11:56.240> or 00:11:56.389 --> 00:11:56.399 align:start position:0% the network it doesn't cost you gas or 00:11:56.399 --> 00:11:57.550 align:start position:0% the network it doesn't cost you gas or anything<00:11:56.720> there's<00:11:56.920> no<00:11:57.040> transactions 00:11:57.550 --> 00:11:57.560 align:start position:0% anything there's no transactions 00:11:57.560 --> 00:12:00.470 align:start position:0% anything there's no transactions involved<00:11:58.519> so<00:11:59.079> yeah<00:11:59.279> yeah<00:11:59.639> keep<00:11:59.839> doing<00:12:00.120> that<00:12:00.320> if 00:12:00.470 --> 00:12:00.480 align:start position:0% involved so yeah yeah keep doing that if 00:12:00.480 --> 00:12:03.430 align:start position:0% involved so yeah yeah keep doing that if you<00:12:00.800> can<00:12:01.560> but<00:12:01.760> this<00:12:01.880> is<00:12:02.279> basically<00:12:02.880> like<00:12:03.079> a<00:12:03.240> way 00:12:03.430 --> 00:12:03.440 align:start position:0% you can but this is basically like a way 00:12:03.440 --> 00:12:05.949 align:start position:0% you can but this is basically like a way of<00:12:03.880> kind<00:12:04.000> of<00:12:04.440> filling<00:12:04.880> that<00:12:05.079> Gap<00:12:05.360> that<00:12:05.480> we<00:12:05.680> have 00:12:05.949 --> 00:12:05.959 align:start position:0% of kind of filling that Gap that we have 00:12:05.959 --> 00:12:07.790 align:start position:0% of kind of filling that Gap that we have on<00:12:06.160> those<00:12:06.519> scenarios<00:12:07.000> where<00:12:07.200> you<00:12:07.279> don't<00:12:07.560> have 00:12:07.790 --> 00:12:07.800 align:start position:0% on those scenarios where you don't have 00:12:07.800 --> 00:12:11.590 align:start position:0% on those scenarios where you don't have your<00:12:08.160> your<00:12:08.360> your<00:12:08.480> validator<00:12:09.120> key<00:12:10.240> and<00:12:11.240> quickly 00:12:11.590 --> 00:12:11.600 align:start position:0% your your your validator key and quickly 00:12:11.600 --> 00:12:13.550 align:start position:0% your your your validator key and quickly before<00:12:11.880> I<00:12:12.000> run<00:12:12.200> out<00:12:12.320> of<00:12:12.519> time<00:12:13.120> uh<00:12:13.240> I<00:12:13.360> just<00:12:13.440> want 00:12:13.550 --> 00:12:13.560 align:start position:0% before I run out of time uh I just want 00:12:13.560 --> 00:12:15.509 align:start position:0% before I run out of time uh I just want to<00:12:13.680> mention<00:12:13.920> that<00:12:14.079> withdraw<00:12:14.440> requests<00:12:15.120> uh 00:12:15.509 --> 00:12:15.519 align:start position:0% to mention that withdraw requests uh 00:12:15.519 --> 00:12:18.550 align:start position:0% to mention that withdraw requests uh different<00:12:15.839> from<00:12:16.880> withdrawals<00:12:17.880> in<00:12:18.000> the<00:12:18.160> sense 00:12:18.550 --> 00:12:18.560 align:start position:0% different from withdrawals in the sense 00:12:18.560 --> 00:12:20.750 align:start position:0% different from withdrawals in the sense that<00:12:19.360> if<00:12:19.440> you<00:12:19.560> guys<00:12:19.720> remember<00:12:20.000> capella<00:12:20.600> that's 00:12:20.750 --> 00:12:20.760 align:start position:0% that if you guys remember capella that's 00:12:20.760 --> 00:12:23.189 align:start position:0% that if you guys remember capella that's when<00:12:20.920> we<00:12:21.040> introduced<00:12:21.880> withdrawals<00:12:22.880> a 00:12:23.189 --> 00:12:23.199 align:start position:0% when we introduced withdrawals a 00:12:23.199 --> 00:12:25.310 align:start position:0% when we introduced withdrawals a withdraw<00:12:23.639> requests<00:12:24.600> can<00:12:24.880> eventually 00:12:25.310 --> 00:12:25.320 align:start position:0% withdraw requests can eventually 00:12:25.320 --> 00:12:26.870 align:start position:0% withdraw requests can eventually generate<00:12:25.720> a<00:12:25.920> withdraw<00:12:26.399> when<00:12:26.519> you're<00:12:26.639> doing 00:12:26.870 --> 00:12:26.880 align:start position:0% generate a withdraw when you're doing 00:12:26.880 --> 00:12:29.189 align:start position:0% generate a withdraw when you're doing like<00:12:27.000> a<00:12:27.079> partial<00:12:27.440> withdraw<00:12:28.440> but<00:12:28.720> they're<00:12:28.920> not 00:12:29.189 --> 00:12:29.199 align:start position:0% like a partial withdraw but they're not 00:12:29.199 --> 00:12:31.030 align:start position:0% like a partial withdraw but they're not same<00:12:29.399> thing<00:12:29.639> just<00:12:29.959> because<00:12:30.320> yeah<00:12:30.680> the 00:12:31.030 --> 00:12:31.040 align:start position:0% same thing just because yeah the 00:12:31.040 --> 00:12:34.310 align:start position:0% same thing just because yeah the terminology<00:12:31.600> and<00:12:31.800> things<00:12:32.040> like<00:12:32.639> that<00:12:33.639> okay 00:12:34.310 --> 00:12:34.320 align:start position:0% terminology and things like that okay 00:12:34.320 --> 00:12:36.269 align:start position:0% terminology and things like that okay that<00:12:34.440> was<00:12:34.600> a<00:12:34.720> lot<00:12:35.000> hopefully<00:12:35.839> enough<00:12:36.120> for 00:12:36.269 --> 00:12:36.279 align:start position:0% that was a lot hopefully enough for 00:12:36.279 --> 00:12:38.069 align:start position:0% that was a lot hopefully enough for people<00:12:36.480> to<00:12:36.880> understand<00:12:37.160> I'll<00:12:37.519> leave<00:12:37.720> it<00:12:37.920> here 00:12:38.069 --> 00:12:38.079 align:start position:0% people to understand I'll leave it here 00:12:38.079 --> 00:12:39.590 align:start position:0% people to understand I'll leave it here and<00:12:38.160> then<00:12:38.279> I'll<00:12:38.519> hand<00:12:38.680> over<00:12:38.839> to<00:12:39.000> Stefan<00:12:39.360> for 00:12:39.590 --> 00:12:39.600 align:start position:0% and then I'll hand over to Stefan for 00:12:39.600 --> 00:12:41.750 align:start position:0% and then I'll hand over to Stefan for his<00:12:39.800> Mar<00:12:40.440> thank 00:12:41.750 --> 00:12:41.760 align:start position:0% his Mar thank 00:12:41.760 --> 00:12:45.750 align:start position:0% his Mar thank you<00:12:42.760> oh<00:12:43.000> thank<00:12:43.160> you<00:12:44.160> how<00:12:44.320> does<00:12:44.480> that<00:12:44.720> work<00:12:45.399> just 00:12:45.750 --> 00:12:45.760 align:start position:0% you oh thank you how does that work just 00:12:45.760 --> 00:12:54.829 align:start position:0% you oh thank you how does that work just yeah<00:12:45.920> next 00:12:54.829 --> 00:12:54.839 align:start position:0% 00:12:54.839 --> 00:12:57.590 align:start position:0% slide 00:12:57.590 --> 00:12:57.600 align:start position:0% slide 00:12:57.600 --> 00:13:00.030 align:start position:0% slide okay<00:12:58.600> hello 00:13:00.030 --> 00:13:00.040 align:start position:0% okay hello 00:13:00.040 --> 00:13:03.389 align:start position:0% okay hello uh<00:13:00.720> so<00:13:00.959> I'm<00:13:01.079> going<00:13:01.279> to<00:13:01.440> talk<00:13:01.680> about<00:13:02.279> EIP 00:13:03.389 --> 00:13:03.399 align:start position:0% uh so I'm going to talk about EIP 00:13:03.399 --> 00:13:05.990 align:start position:0% uh so I'm going to talk about EIP 6110<00:13:04.399> which<00:13:04.519> is<00:13:04.720> Supply<00:13:05.120> validator<00:13:05.680> deposits 00:13:05.990 --> 00:13:06.000 align:start position:0% 6110 which is Supply validator deposits 00:13:06.000 --> 00:13:06.910 align:start position:0% 6110 which is Supply validator deposits on 00:13:06.910 --> 00:13:06.920 align:start position:0% on 00:13:06.920 --> 00:13:10.350 align:start position:0% on chain<00:13:07.920> and<00:13:08.120> you<00:13:08.279> may<00:13:08.519> wonder<00:13:09.160> what<00:13:09.560> the<00:13:09.760> CIP<00:13:10.199> is 00:13:10.350 --> 00:13:10.360 align:start position:0% chain and you may wonder what the CIP is 00:13:10.360 --> 00:13:12.310 align:start position:0% chain and you may wonder what the CIP is about<00:13:10.760> because<00:13:11.079> validator<00:13:11.680> deposits<00:13:12.040> are 00:13:12.310 --> 00:13:12.320 align:start position:0% about because validator deposits are 00:13:12.320 --> 00:13:15.189 align:start position:0% about because validator deposits are already<00:13:12.600> on<00:13:13.000> chain<00:13:14.000> but<00:13:14.199> the<00:13:14.360> keyword<00:13:14.800> here<00:13:14.959> is 00:13:15.189 --> 00:13:15.199 align:start position:0% already on chain but the keyword here is 00:13:15.199 --> 00:13:18.110 align:start position:0% already on chain but the keyword here is Supply<00:13:16.079> so<00:13:16.320> essentially<00:13:16.880> the<00:13:17.079> CIP<00:13:17.560> changes 00:13:18.110 --> 00:13:18.120 align:start position:0% Supply so essentially the CIP changes 00:13:18.120 --> 00:13:20.030 align:start position:0% Supply so essentially the CIP changes how<00:13:18.320> the<00:13:18.519> deposits<00:13:19.000> made<00:13:19.199> to<00:13:19.360> the<00:13:19.560> deposit 00:13:20.030 --> 00:13:20.040 align:start position:0% how the deposits made to the deposit 00:13:20.040 --> 00:13:22.350 align:start position:0% how the deposits made to the deposit contract<00:13:21.040> which<00:13:21.199> sits<00:13:21.440> on<00:13:21.560> the<00:13:21.680> execution 00:13:22.350 --> 00:13:22.360 align:start position:0% contract which sits on the execution 00:13:22.360 --> 00:13:25.350 align:start position:0% contract which sits on the execution layer<00:13:23.360> how<00:13:23.920> these<00:13:24.240> deposits<00:13:24.600> are<00:13:24.880> supply<00:13:25.240> to 00:13:25.350 --> 00:13:25.360 align:start position:0% layer how these deposits are supply to 00:13:25.360 --> 00:13:27.790 align:start position:0% layer how these deposits are supply to the<00:13:25.480> consens<00:13:25.880> Slayer<00:13:26.519> where<00:13:27.279> either<00:13:27.519> a<00:13:27.639> new 00:13:27.790 --> 00:13:27.800 align:start position:0% the consens Slayer where either a new 00:13:27.800 --> 00:13:30.269 align:start position:0% the consens Slayer where either a new validator<00:13:28.519> is<00:13:28.720> initially<00:13:29.279> ized<00:13:29.880> or<00:13:30.079> an 00:13:30.269 --> 00:13:30.279 align:start position:0% validator is initially ized or an 00:13:30.279 --> 00:13:33.310 align:start position:0% validator is initially ized or an existing<00:13:30.639> validator<00:13:31.160> balance<00:13:31.560> is<00:13:31.720> topped<00:13:32.320> up 00:13:33.310 --> 00:13:33.320 align:start position:0% existing validator balance is topped up 00:13:33.320 --> 00:13:35.910 align:start position:0% existing validator balance is topped up so<00:13:33.560> I'm<00:13:33.680> going<00:13:33.839> to<00:13:34.040> start<00:13:35.000> by<00:13:35.360> explaining 00:13:35.910 --> 00:13:35.920 align:start position:0% so I'm going to start by explaining 00:13:35.920 --> 00:13:37.470 align:start position:0% so I'm going to start by explaining briefly<00:13:36.360> how<00:13:36.560> the<00:13:36.720> current<00:13:37.079> deposit 00:13:37.470 --> 00:13:37.480 align:start position:0% briefly how the current deposit 00:13:37.480 --> 00:13:40.430 align:start position:0% briefly how the current deposit processing<00:13:38.199> works<00:13:39.199> and<00:13:39.760> then<00:13:39.880> I'll<00:13:40.079> go<00:13:40.240> over 00:13:40.430 --> 00:13:40.440 align:start position:0% processing works and then I'll go over 00:13:40.440 --> 00:13:44.110 align:start position:0% processing works and then I'll go over the<00:13:40.639> depositing<00:13:41.199> processing<00:13:41.760> after<00:13:42.600> this<00:13:43.120> EIP 00:13:44.110 --> 00:13:44.120 align:start position:0% the depositing processing after this EIP 00:13:44.120 --> 00:13:49.470 align:start position:0% the depositing processing after this EIP which<00:13:44.360> will<00:13:44.560> be<00:13:44.880> part<00:13:45.480> of<00:13:45.680> the<00:13:45.959> next 00:13:49.470 --> 00:13:49.480 align:start position:0% 00:13:49.480 --> 00:13:52.949 align:start position:0% Fork<00:13:50.480> yeah<00:13:50.720> so<00:13:51.040> current<00:13:51.320> deposit<00:13:51.959> processing 00:13:52.949 --> 00:13:52.959 align:start position:0% Fork yeah so current deposit processing 00:13:52.959 --> 00:13:55.150 align:start position:0% Fork yeah so current deposit processing uh<00:13:53.480> basically<00:13:54.160> a<00:13:54.279> user<00:13:54.639> submits<00:13:55.000> a 00:13:55.150 --> 00:13:55.160 align:start position:0% uh basically a user submits a 00:13:55.160 --> 00:13:57.189 align:start position:0% uh basically a user submits a transaction<00:13:55.800> containing<00:13:56.279> deposit<00:13:56.680> data<00:13:56.880> to<00:13:57.040> a 00:13:57.189 --> 00:13:57.199 align:start position:0% transaction containing deposit data to a 00:13:57.199 --> 00:14:00.069 align:start position:0% transaction containing deposit data to a deposit<00:13:57.680> contract<00:13:58.680> which<00:13:58.800> is<00:13:59.440> uh<00:13:59.680> essentially 00:14:00.069 --> 00:14:00.079 align:start position:0% deposit contract which is uh essentially 00:14:00.079 --> 00:14:04.150 align:start position:0% deposit contract which is uh essentially 32<00:14:00.800> if<00:14:01.800> and<00:14:02.560> users<00:14:03.040> usually<00:14:03.320> do<00:14:03.560> that<00:14:03.800> via<00:14:04.040> the 00:14:04.150 --> 00:14:04.160 align:start position:0% 32 if and users usually do that via the 00:14:04.160 --> 00:14:05.629 align:start position:0% 32 if and users usually do that via the staking<00:14:04.519> launch 00:14:05.629 --> 00:14:05.639 align:start position:0% staking launch 00:14:05.639 --> 00:14:09.310 align:start position:0% staking launch pad<00:14:06.639> and<00:14:06.839> then<00:14:07.639> there<00:14:07.839> is<00:14:08.160> this<00:14:08.639> uh<00:14:08.720> 8<00:14:09.079> hour 00:14:09.310 --> 00:14:09.320 align:start position:0% pad and then there is this uh 8 hour 00:14:09.320 --> 00:14:11.990 align:start position:0% pad and then there is this uh 8 hour delay<00:14:10.000> where<00:14:10.199> the<00:14:10.399> consensus<00:14:10.920> layer<00:14:11.519> has<00:14:11.680> to 00:14:11.990 --> 00:14:12.000 align:start position:0% delay where the consensus layer has to 00:14:12.000 --> 00:14:13.670 align:start position:0% delay where the consensus layer has to consider<00:14:12.399> the<00:14:12.519> state<00:14:12.759> of<00:14:12.880> the<00:14:13.040> deposit 00:14:13.670 --> 00:14:13.680 align:start position:0% consider the state of the deposit 00:14:13.680 --> 00:14:16.470 align:start position:0% consider the state of the deposit contract<00:14:14.680> and<00:14:14.920> this<00:14:15.639> has<00:14:15.759> been<00:14:16.000> designed<00:14:16.399> to 00:14:16.470 --> 00:14:16.480 align:start position:0% contract and this has been designed to 00:14:16.480 --> 00:14:20.790 align:start position:0% contract and this has been designed to be<00:14:16.720> 248<00:14:18.120> blocks<00:14:19.120> uh<00:14:19.279> when<00:14:20.000> with<00:14:20.199> proof<00:14:20.440> of<00:14:20.600> work 00:14:20.790 --> 00:14:20.800 align:start position:0% be 248 blocks uh when with proof of work 00:14:20.800 --> 00:14:22.949 align:start position:0% be 248 blocks uh when with proof of work blocks<00:14:21.160> which<00:14:21.279> are<00:14:21.720> which<00:14:21.839> were<00:14:22.040> around<00:14:22.320> 14 00:14:22.949 --> 00:14:22.959 align:start position:0% blocks which are which were around 14 00:14:22.959 --> 00:14:26.230 align:start position:0% blocks which are which were around 14 seconds<00:14:23.959> and<00:14:24.160> this<00:14:24.279> was<00:14:24.600> done<00:14:24.880> to<00:14:25.120> ensure<00:14:25.759> that 00:14:26.230 --> 00:14:26.240 align:start position:0% seconds and this was done to ensure that 00:14:26.240 --> 00:14:30.030 align:start position:0% seconds and this was done to ensure that if<00:14:26.399> there<00:14:26.519> are<00:14:26.720> any<00:14:26.959> issues<00:14:27.360> with<00:14:27.880> if1<00:14:28.880> uh<00:14:29.399> then 00:14:30.030 --> 00:14:30.040 align:start position:0% if there are any issues with if1 uh then 00:14:30.040 --> 00:14:32.670 align:start position:0% if there are any issues with if1 uh then uh<00:14:30.480> essentially<00:14:31.279> that<00:14:31.600> wouldn't<00:14:32.120> impact<00:14:32.560> the 00:14:32.670 --> 00:14:32.680 align:start position:0% uh essentially that wouldn't impact the 00:14:32.680 --> 00:14:36.350 align:start position:0% uh essentially that wouldn't impact the beacon<00:14:33.000> chain<00:14:33.880> and<00:14:34.040> 8<00:14:34.399> Hour<00:14:34.759> was<00:14:35.480> just<00:14:36.199> it 00:14:36.350 --> 00:14:36.360 align:start position:0% beacon chain and 8 Hour was just it 00:14:36.360 --> 00:14:39.189 align:start position:0% beacon chain and 8 Hour was just it gives<00:14:37.000> about<00:14:37.320> enough<00:14:37.600> wiggle<00:14:38.000> room<00:14:38.639> to<00:14:38.839> ensure 00:14:39.189 --> 00:14:39.199 align:start position:0% gives about enough wiggle room to ensure 00:14:39.199 --> 00:14:41.110 align:start position:0% gives about enough wiggle room to ensure that<00:14:39.399> any<00:14:39.759> issues<00:14:40.079> are 00:14:41.110 --> 00:14:41.120 align:start position:0% that any issues are 00:14:41.120 --> 00:14:43.350 align:start position:0% that any issues are fixed<00:14:42.120> and<00:14:42.240> then<00:14:42.399> there<00:14:42.519> is<00:14:42.639> a<00:14:42.759> voting<00:14:43.240> which 00:14:43.350 --> 00:14:43.360 align:start position:0% fixed and then there is a voting which 00:14:43.360 --> 00:14:46.790 align:start position:0% fixed and then there is a voting which is<00:14:43.480> a<00:14:43.720> 64<00:14:44.639> EPO<00:14:45.639> and<00:14:45.800> it's<00:14:46.040> kind<00:14:46.160> of<00:14:46.480> this<00:14:46.600> is 00:14:46.790 --> 00:14:46.800 align:start position:0% is a 64 EPO and it's kind of this is 00:14:46.800 --> 00:14:49.269 align:start position:0% is a 64 EPO and it's kind of this is like<00:14:47.000> a<00:14:47.279> off-protocol<00:14:47.759> consensus<00:14:48.600> mechanism 00:14:49.269 --> 00:14:49.279 align:start position:0% like a off-protocol consensus mechanism 00:14:49.279 --> 00:14:51.990 align:start position:0% like a off-protocol consensus mechanism it<00:14:49.399> was<00:14:49.560> designed<00:14:49.920> before<00:14:50.160> the<00:14:50.759> merge<00:14:51.759> and 00:14:51.990 --> 00:14:52.000 align:start position:0% it was designed before the merge and 00:14:52.000 --> 00:14:53.949 align:start position:0% it was designed before the merge and basically<00:14:52.360> it<00:14:52.480> ensures<00:14:52.920> that<00:14:53.160> validators 00:14:53.949 --> 00:14:53.959 align:start position:0% basically it ensures that validators 00:14:53.959 --> 00:14:56.350 align:start position:0% basically it ensures that validators agree<00:14:54.279> on<00:14:54.440> the<00:14:54.600> state<00:14:55.480> on<00:14:55.720> on<00:14:55.839> the<00:14:55.959> same<00:14:56.160> view 00:14:56.350 --> 00:14:56.360 align:start position:0% agree on the state on on the same view 00:14:56.360 --> 00:14:58.430 align:start position:0% agree on the state on on the same view of<00:14:56.440> the<00:14:56.560> deposit<00:14:56.959> contract<00:14:57.800> which<00:14:58.000> sits<00:14:58.279> in 00:14:58.430 --> 00:14:58.440 align:start position:0% of the deposit contract which sits in 00:14:58.440 --> 00:14:59.790 align:start position:0% of the deposit contract which sits in the<00:14:58.600> EO 00:14:59.790 --> 00:14:59.800 align:start position:0% the EO 00:14:59.800 --> 00:15:02.150 align:start position:0% the EO and<00:15:00.320> before<00:15:00.600> the<00:15:00.720> merge<00:15:01.079> basically<00:15:01.519> the<00:15:01.639> EO<00:15:02.040> is 00:15:02.150 --> 00:15:02.160 align:start position:0% and before the merge basically the EO is 00:15:02.160 --> 00:15:05.189 align:start position:0% and before the merge basically the EO is driven<00:15:02.519> by<00:15:02.759> proof<00:15:02.959> of<00:15:03.160> work<00:15:04.160> so<00:15:04.639> there<00:15:04.759> was<00:15:05.000> no 00:15:05.189 --> 00:15:05.199 align:start position:0% driven by proof of work so there was no 00:15:05.199 --> 00:15:06.629 align:start position:0% driven by proof of work so there was no real<00:15:05.480> connection<00:15:05.880> between<00:15:06.120> the<00:15:06.240> execution 00:15:06.629 --> 00:15:06.639 align:start position:0% real connection between the execution 00:15:06.639 --> 00:15:08.550 align:start position:0% real connection between the execution layer<00:15:06.880> and<00:15:07.000> the<00:15:07.120> consensus 00:15:08.550 --> 00:15:08.560 align:start position:0% layer and the consensus 00:15:08.560 --> 00:15:12.230 align:start position:0% layer and the consensus layer<00:15:09.560> um<00:15:09.920> and<00:15:10.160> then<00:15:11.000> this<00:15:11.199> voting<00:15:11.720> basically 00:15:12.230 --> 00:15:12.240 align:start position:0% layer um and then this voting basically 00:15:12.240 --> 00:15:15.110 align:start position:0% layer um and then this voting basically it<00:15:12.399> finishes<00:15:12.920> when<00:15:13.519> at<00:15:13.680> least<00:15:14.000> half<00:15:14.639> half 00:15:15.110 --> 00:15:15.120 align:start position:0% it finishes when at least half half 00:15:15.120 --> 00:15:17.550 align:start position:0% it finishes when at least half half number<00:15:15.360> of<00:15:15.480> the<00:15:15.600> votes<00:15:15.880> are<00:15:16.079> the<00:15:16.360> same<00:15:17.360> and 00:15:17.550 --> 00:15:17.560 align:start position:0% number of the votes are the same and 00:15:17.560 --> 00:15:19.749 align:start position:0% number of the votes are the same and after<00:15:17.800> that<00:15:18.040> proposers<00:15:18.639> include<00:15:19.079> those 00:15:19.749 --> 00:15:19.759 align:start position:0% after that proposers include those 00:15:19.759 --> 00:15:22.990 align:start position:0% after that proposers include those deposits<00:15:20.759> uh<00:15:20.959> alongside<00:15:21.920> the 00:15:22.990 --> 00:15:23.000 align:start position:0% deposits uh alongside the 00:15:23.000 --> 00:15:26.150 align:start position:0% deposits uh alongside the block<00:15:24.000> and<00:15:24.120> then<00:15:24.279> all<00:15:24.560> notes<00:15:24.880> can<00:15:25.160> verify 00:15:26.150 --> 00:15:26.160 align:start position:0% block and then all notes can verify 00:15:26.160 --> 00:15:27.189 align:start position:0% block and then all notes can verify these 00:15:27.189 --> 00:15:27.199 align:start position:0% these 00:15:27.199 --> 00:15:29.670 align:start position:0% these blocks<00:15:28.199> and<00:15:28.399> then 00:15:29.670 --> 00:15:29.680 align:start position:0% blocks and then 00:15:29.680 --> 00:15:31.470 align:start position:0% blocks and then uh<00:15:29.920> a<00:15:30.079> valid<00:15:30.360> deposit<00:15:30.759> basically<00:15:31.199> either 00:15:31.470 --> 00:15:31.480 align:start position:0% uh a valid deposit basically either 00:15:31.480 --> 00:15:33.910 align:start position:0% uh a valid deposit basically either creates<00:15:31.720> a<00:15:31.800> new<00:15:32.000> validator<00:15:32.720> or<00:15:33.279> it<00:15:33.480> tops<00:15:33.759> up 00:15:33.910 --> 00:15:33.920 align:start position:0% creates a new validator or it tops up 00:15:33.920 --> 00:15:36.309 align:start position:0% creates a new validator or it tops up the<00:15:34.040> balance<00:15:34.319> of<00:15:34.480> an<00:15:34.720> existing 00:15:36.309 --> 00:15:36.319 align:start position:0% the balance of an existing 00:15:36.319 --> 00:15:39.069 align:start position:0% the balance of an existing validator<00:15:37.319> and<00:15:37.519> this<00:15:37.639> is<00:15:37.759> a<00:15:38.000> diagram<00:15:38.519> of<00:15:38.720> the 00:15:39.069 --> 00:15:39.079 align:start position:0% validator and this is a diagram of the 00:15:39.079 --> 00:15:42.790 align:start position:0% validator and this is a diagram of the current<00:15:40.040> uh<00:15:40.240> process<00:15:41.240> so<00:15:41.720> you<00:15:41.839> can<00:15:42.000> see<00:15:42.519> this 00:15:42.790 --> 00:15:42.800 align:start position:0% current uh process so you can see this 00:15:42.800 --> 00:15:46.910 align:start position:0% current uh process so you can see this user<00:15:43.800> he<00:15:44.800> uh<00:15:45.279> B<00:15:45.959> basically<00:15:46.319> does<00:15:46.440> a<00:15:46.600> deposit 00:15:46.910 --> 00:15:46.920 align:start position:0% user he uh B basically does a deposit 00:15:46.920 --> 00:15:49.430 align:start position:0% user he uh B basically does a deposit transaction<00:15:47.360> use<00:15:47.560> the<00:15:47.680> stank<00:15:48.000> launch<00:15:48.360> p<00:15:49.279> and 00:15:49.430 --> 00:15:49.440 align:start position:0% transaction use the stank launch p and 00:15:49.440 --> 00:15:51.269 align:start position:0% transaction use the stank launch p and then<00:15:50.000> the<00:15:50.160> important<00:15:50.600> part<00:15:50.880> here<00:15:51.040> is 00:15:51.269 --> 00:15:51.279 align:start position:0% then the important part here is 00:15:51.279 --> 00:15:52.710 align:start position:0% then the important part here is basically<00:15:51.720> you<00:15:51.839> can<00:15:51.959> see<00:15:52.199> on<00:15:52.319> the<00:15:52.440> right<00:15:52.639> the 00:15:52.710 --> 00:15:52.720 align:start position:0% basically you can see on the right the 00:15:52.720 --> 00:15:56.550 align:start position:0% basically you can see on the right the Bon<00:15:53.120> note<00:15:54.000> and<00:15:54.480> it<00:15:54.680> has<00:15:54.920> this<00:15:55.399> chunky<00:15:55.920> if1 00:15:56.550 --> 00:15:56.560 align:start position:0% Bon note and it has this chunky if1 00:15:56.560 --> 00:16:00.550 align:start position:0% Bon note and it has this chunky if1 module<00:15:57.560> which<00:15:57.920> constantly<00:15:58.480> psts<00:15:59.199> the<00:15:59.399> E<00:16:00.279> via 00:16:00.550 --> 00:16:00.560 align:start position:0% module which constantly psts the E via 00:16:00.560 --> 00:16:05.430 align:start position:0% module which constantly psts the E via the<00:16:00.759> Json<00:16:01.079> RPC<00:16:01.759> API<00:16:02.759> and<00:16:03.040> it<00:16:03.199> does<00:16:03.519> that<00:16:04.440> 248 00:16:05.430 --> 00:16:05.440 align:start position:0% the Json RPC API and it does that 248 00:16:05.440 --> 00:16:08.629 align:start position:0% the Json RPC API and it does that 248 blocks<00:16:06.279> uh<00:16:06.759> constantly<00:16:07.319> it<00:16:07.560> POS<00:16:07.800> it<00:16:08.199> in<00:16:08.360> order 00:16:08.629 --> 00:16:08.639 align:start position:0% blocks uh constantly it POS it in order 00:16:08.639 --> 00:16:11.829 align:start position:0% blocks uh constantly it POS it in order to<00:16:08.839> build<00:16:09.440> the<00:16:09.680> merco<00:16:10.240> tree<00:16:11.079> which<00:16:11.360> then<00:16:11.680> can 00:16:11.829 --> 00:16:11.839 align:start position:0% to build the merco tree which then can 00:16:11.839 --> 00:16:14.790 align:start position:0% to build the merco tree which then can be<00:16:12.000> used<00:16:12.279> to<00:16:12.639> produce<00:16:13.279> proofs<00:16:14.279> which<00:16:14.440> are 00:16:14.790 --> 00:16:14.800 align:start position:0% be used to produce proofs which are 00:16:14.800 --> 00:16:17.350 align:start position:0% be used to produce proofs which are included<00:16:15.360> alongside 00:16:17.350 --> 00:16:17.360 align:start position:0% included alongside 00:16:17.360 --> 00:16:20.670 align:start position:0% included alongside deposits<00:16:18.360> uh<00:16:18.920> and<00:16:19.839> this<00:16:20.000> is<00:16:20.160> the<00:16:20.319> current 00:16:20.670 --> 00:16:20.680 align:start position:0% deposits uh and this is the current 00:16:20.680 --> 00:16:23.870 align:start position:0% deposits uh and this is the current process<00:16:21.120> which<00:16:21.519> is<00:16:22.000> still<00:16:23.000> still<00:16:23.399> ethereum 00:16:23.870 --> 00:16:23.880 align:start position:0% process which is still still ethereum 00:16:23.880 --> 00:16:25.389 align:start position:0% process which is still still ethereum works<00:16:24.199> like<00:16:24.399> that<00:16:24.600> even<00:16:24.880> though<00:16:25.079> we<00:16:25.199> have 00:16:25.389 --> 00:16:25.399 align:start position:0% works like that even though we have 00:16:25.399 --> 00:16:28.150 align:start position:0% works like that even though we have already<00:16:25.759> migrated<00:16:26.240> to<00:16:26.800> proof<00:16:27.079> of<00:16:27.279> stake<00:16:28.000> we 00:16:28.150 --> 00:16:28.160 align:start position:0% already migrated to proof of stake we 00:16:28.160 --> 00:16:29.790 align:start position:0% already migrated to proof of stake we still<00:16:28.360> use<00:16:28.600> this<00:16:28.920> J<00:16:29.079> an 00:16:29.790 --> 00:16:29.800 align:start position:0% still use this J an 00:16:29.800 --> 00:16:35.590 align:start position:0% still use this J an RPC<00:16:30.800> and<00:16:31.279> the<00:16:31.399> way<00:16:32.040> this<00:16:33.040> the<00:16:33.160> EAP<00:16:33.600> 6110<00:16:34.600> works 00:16:35.590 --> 00:16:35.600 align:start position:0% RPC and the way this the EAP 6110 works 00:16:35.600 --> 00:16:38.550 align:start position:0% RPC and the way this the EAP 6110 works is<00:16:35.880> it<00:16:36.079> simplifies<00:16:36.720> a<00:16:36.920> lot<00:16:37.680> basically<00:16:38.440> the 00:16:38.550 --> 00:16:38.560 align:start position:0% is it simplifies a lot basically the 00:16:38.560 --> 00:16:41.629 align:start position:0% is it simplifies a lot basically the same<00:16:38.839> deposit<00:16:39.199> transaction<00:16:39.639> is<00:16:40.319> made<00:16:41.319> uh<00:16:41.480> but 00:16:41.629 --> 00:16:41.639 align:start position:0% same deposit transaction is made uh but 00:16:41.639 --> 00:16:43.949 align:start position:0% same deposit transaction is made uh but then<00:16:41.839> the<00:16:42.040> deposits<00:16:42.440> come<00:16:42.720> directly<00:16:43.120> from<00:16:43.399> the 00:16:43.949 --> 00:16:43.959 align:start position:0% then the deposits come directly from the 00:16:43.959 --> 00:16:46.350 align:start position:0% then the deposits come directly from the e<00:16:44.440> via<00:16:44.680> the<00:16:44.800> engine<00:16:45.120> API<00:16:46.040> and<00:16:46.160> they're 00:16:46.350 --> 00:16:46.360 align:start position:0% e via the engine API and they're 00:16:46.360 --> 00:16:48.509 align:start position:0% e via the engine API and they're included<00:16:46.800> in<00:16:46.920> blocks<00:16:47.519> and<00:16:47.680> then<00:16:47.880> they<00:16:48.160> process 00:16:48.509 --> 00:16:48.519 align:start position:0% included in blocks and then they process 00:16:48.519 --> 00:16:50.829 align:start position:0% included in blocks and then they process on<00:16:48.759> finalization<00:16:49.360> of<00:16:49.480> the<00:16:49.600> chain<00:16:50.480> which<00:16:50.639> is 00:16:50.829 --> 00:16:50.839 align:start position:0% on finalization of the chain which is 00:16:50.839 --> 00:16:54.309 align:start position:0% on finalization of the chain which is currently<00:16:51.279> around<00:16:51.639> 13<00:16:52.160> minutes<00:16:53.160> and<00:16:53.360> then<00:16:53.639> the 00:16:54.309 --> 00:16:54.319 align:start position:0% currently around 13 minutes and then the 00:16:54.319 --> 00:16:57.470 align:start position:0% currently around 13 minutes and then the same<00:16:55.319> flow<00:16:55.920> the<00:16:56.040> same 00:16:57.470 --> 00:16:57.480 align:start position:0% same flow the same 00:16:57.480 --> 00:16:59.829 align:start position:0% same flow the same it's<00:16:58.480> again<00:16:58.680> the<00:16:59.000> same<00:16:59.160> thing<00:16:59.399> a<00:16:59.560> valid 00:16:59.829 --> 00:16:59.839 align:start position:0% it's again the same thing a valid 00:16:59.839 --> 00:17:01.629 align:start position:0% it's again the same thing a valid deposit<00:17:00.240> will<00:17:00.440> are<00:17:00.680> create<00:17:00.920> new<00:17:01.079> validator<00:17:01.480> or 00:17:01.629 --> 00:17:01.639 align:start position:0% deposit will are create new validator or 00:17:01.639 --> 00:17:03.189 align:start position:0% deposit will are create new validator or top<00:17:01.839> up<00:17:01.959> an<00:17:02.120> existing 00:17:03.189 --> 00:17:03.199 align:start position:0% top up an existing 00:17:03.199 --> 00:17:07.510 align:start position:0% top up an existing validator<00:17:04.199> and<00:17:04.400> the<00:17:04.559> diagram<00:17:05.360> now<00:17:06.360> uh<00:17:07.160> looks 00:17:07.510 --> 00:17:07.520 align:start position:0% validator and the diagram now uh looks 00:17:07.520 --> 00:17:08.990 align:start position:0% validator and the diagram now uh looks like<00:17:07.760> this<00:17:08.079> which<00:17:08.199> is<00:17:08.400> pretty<00:17:08.600> much<00:17:08.839> what 00:17:08.990 --> 00:17:09.000 align:start position:0% like this which is pretty much what 00:17:09.000 --> 00:17:11.829 align:start position:0% like this which is pretty much what Lucas<00:17:09.520> showed<00:17:10.520> you<00:17:10.839> basically<00:17:11.520> have<00:17:11.679> the 00:17:11.829 --> 00:17:11.839 align:start position:0% Lucas showed you basically have the 00:17:11.839 --> 00:17:14.549 align:start position:0% Lucas showed you basically have the execution<00:17:12.400> requests<00:17:13.400> and<00:17:13.600> now<00:17:13.959> you<00:17:14.240> get<00:17:14.400> the 00:17:14.549 --> 00:17:14.559 align:start position:0% execution requests and now you get the 00:17:14.559 --> 00:17:16.549 align:start position:0% execution requests and now you get the deposit<00:17:15.000> request<00:17:15.319> over<00:17:15.520> the<00:17:15.640> engine<00:17:15.919> API<00:17:16.360> so 00:17:16.549 --> 00:17:16.559 align:start position:0% deposit request over the engine API so 00:17:16.559 --> 00:17:19.510 align:start position:0% deposit request over the engine API so whenever<00:17:17.120> a<00:17:18.120> proposer<00:17:18.679> proposes<00:17:19.039> a<00:17:19.160> block 00:17:19.510 --> 00:17:19.520 align:start position:0% whenever a proposer proposes a block 00:17:19.520 --> 00:17:22.710 align:start position:0% whenever a proposer proposes a block they<00:17:19.679> get<00:17:19.799> the<00:17:19.959> deposit<00:17:20.839> requests<00:17:21.839> and<00:17:22.520> uh 00:17:22.710 --> 00:17:22.720 align:start position:0% they get the deposit requests and uh 00:17:22.720 --> 00:17:25.549 align:start position:0% they get the deposit requests and uh basically<00:17:23.720> this<00:17:23.959> whole<00:17:24.319> E1<00:17:24.799> module<00:17:25.199> which<00:17:25.319> was 00:17:25.549 --> 00:17:25.559 align:start position:0% basically this whole E1 module which was 00:17:25.559 --> 00:17:29.190 align:start position:0% basically this whole E1 module which was quite<00:17:25.760> chunky<00:17:26.240> now<00:17:26.480> it's<00:17:26.679> no<00:17:26.919> longer<00:17:27.919> part<00:17:28.960> of 00:17:29.190 --> 00:17:29.200 align:start position:0% quite chunky now it's no longer part of 00:17:29.200 --> 00:17:30.510 align:start position:0% quite chunky now it's no longer part of the<00:17:29.320> Bon 00:17:30.510 --> 00:17:30.520 align:start position:0% the Bon 00:17:30.520 --> 00:17:32.230 align:start position:0% the Bon note 00:17:32.230 --> 00:17:32.240 align:start position:0% note 00:17:32.240 --> 00:17:36.310 align:start position:0% note um<00:17:33.240> so<00:17:33.480> this<00:17:33.600> is<00:17:33.679> the<00:17:33.840> diagram<00:17:34.679> and<00:17:35.520> to<00:17:35.960> quickly 00:17:36.310 --> 00:17:36.320 align:start position:0% um so this is the diagram and to quickly 00:17:36.320 --> 00:17:38.510 align:start position:0% um so this is the diagram and to quickly summarize<00:17:36.960> the<00:17:37.120> advantages<00:17:37.720> of<00:17:37.880> the 00:17:38.510 --> 00:17:38.520 align:start position:0% summarize the advantages of the 00:17:38.520 --> 00:17:42.590 align:start position:0% summarize the advantages of the EIP<00:17:39.679> basically<00:17:40.679> there<00:17:40.799> is<00:17:41.360> nowadays<00:17:42.160> a<00:17:42.320> delay 00:17:42.590 --> 00:17:42.600 align:start position:0% EIP basically there is nowadays a delay 00:17:42.600 --> 00:17:45.710 align:start position:0% EIP basically there is nowadays a delay of<00:17:42.799> around<00:17:43.160> 11.4<00:17:44.000> hours<00:17:44.480> before 00:17:45.710 --> 00:17:45.720 align:start position:0% of around 11.4 hours before 00:17:45.720 --> 00:17:48.510 align:start position:0% of around 11.4 hours before your<00:17:46.720> UH<00:17:47.080> validator<00:17:47.679> is<00:17:47.840> added<00:17:48.160> to<00:17:48.320> the 00:17:48.510 --> 00:17:48.520 align:start position:0% your UH validator is added to the 00:17:48.520 --> 00:17:51.789 align:start position:0% your UH validator is added to the activation<00:17:49.360> queue<00:17:50.360> and<00:17:50.960> this<00:17:51.120> is<00:17:51.360> basically 00:17:51.789 --> 00:17:51.799 align:start position:0% activation queue and this is basically 00:17:51.799 --> 00:17:54.789 align:start position:0% activation queue and this is basically the<00:17:51.919> follow<00:17:52.280> distance<00:17:52.640> this<00:17:52.880> 248<00:17:53.840> blocks 00:17:54.789 --> 00:17:54.799 align:start position:0% the follow distance this 248 blocks 00:17:54.799 --> 00:17:56.470 align:start position:0% the follow distance this 248 blocks which<00:17:54.919> is<00:17:55.080> around<00:17:55.360> eight<00:17:55.600> hours<00:17:56.240> and<00:17:56.360> then 00:17:56.470 --> 00:17:56.480 align:start position:0% which is around eight hours and then 00:17:56.480 --> 00:17:59.909 align:start position:0% which is around eight hours and then there's<00:17:56.760> this<00:17:56.919> voting<00:17:57.600> of<00:17:57.799> around 00:17:59.909 --> 00:17:59.919 align:start position:0% there's this voting of around 00:17:59.919 --> 00:18:03.110 align:start position:0% there's this voting of around uh<00:18:00.080> 32<00:18:00.559> EPO<00:18:01.080> which<00:18:01.200> is<00:18:01.400> 33.4 00:18:03.110 --> 00:18:03.120 align:start position:0% uh 32 EPO which is 33.4 00:18:03.120 --> 00:18:06.149 align:start position:0% uh 32 EPO which is 33.4 hours<00:18:04.120> uh<00:18:04.320> and<00:18:04.480> now<00:18:04.679> this<00:18:04.799> is<00:18:04.919> reduced<00:18:05.280> to<00:18:05.520> Just 00:18:06.149 --> 00:18:06.159 align:start position:0% hours uh and now this is reduced to Just 00:18:06.159 --> 00:18:08.590 align:start position:0% hours uh and now this is reduced to Just Around<00:18:06.480> 13<00:18:06.880> minutes<00:18:07.440> or<00:18:07.640> two 00:18:08.590 --> 00:18:08.600 align:start position:0% Around 13 minutes or two 00:18:08.600 --> 00:18:10.830 align:start position:0% Around 13 minutes or two AO<00:18:09.600> and<00:18:09.880> another<00:18:10.200> Advantage<00:18:10.600> is<00:18:10.720> the 00:18:10.830 --> 00:18:10.840 align:start position:0% AO and another Advantage is the 00:18:10.840 --> 00:18:13.909 align:start position:0% AO and another Advantage is the increased<00:18:11.280> security<00:18:11.880> because<00:18:12.240> we<00:18:12.600> no<00:18:12.919> longer 00:18:13.909 --> 00:18:13.919 align:start position:0% increased security because we no longer 00:18:13.919 --> 00:18:16.710 align:start position:0% increased security because we no longer uh<00:18:14.280> rely<00:18:14.600> on<00:18:14.799> this<00:18:15.000> off<00:18:15.240> protocol<00:18:15.720> mechanism 00:18:16.710 --> 00:18:16.720 align:start position:0% uh rely on this off protocol mechanism 00:18:16.720 --> 00:18:19.110 align:start position:0% uh rely on this off protocol mechanism now<00:18:16.919> we<00:18:17.039> can<00:18:17.280> just<00:18:18.080> now<00:18:18.240> we<00:18:18.400> just<00:18:18.600> inherit<00:18:19.000> the 00:18:19.110 --> 00:18:19.120 align:start position:0% now we can just now we just inherit the 00:18:19.120 --> 00:18:20.270 align:start position:0% now we can just now we just inherit the security<00:18:19.440> of<00:18:19.559> the 00:18:20.270 --> 00:18:20.280 align:start position:0% security of the 00:18:20.280 --> 00:18:24.350 align:start position:0% security of the chain<00:18:21.280> and<00:18:22.080> uh<00:18:22.360> also<00:18:22.840> there<00:18:22.960> is<00:18:23.080> not<00:18:23.240> a<00:18:23.400> benefit 00:18:24.350 --> 00:18:24.360 align:start position:0% chain and uh also there is not a benefit 00:18:24.360 --> 00:18:26.510 align:start position:0% chain and uh also there is not a benefit because<00:18:24.679> currently<00:18:25.240> we<00:18:25.720> have<00:18:25.880> these<00:18:26.120> deposit 00:18:26.510 --> 00:18:26.520 align:start position:0% because currently we have these deposit 00:18:26.520 --> 00:18:29.750 align:start position:0% because currently we have these deposit contract<00:18:26.960> snapshots<00:18:27.960> which<00:18:28.200> basically<00:18:28.919> are 00:18:29.750 --> 00:18:29.760 align:start position:0% contract snapshots which basically are 00:18:29.760 --> 00:18:33.870 align:start position:0% contract snapshots which basically are um<00:18:30.159> a<00:18:30.320> merket<00:18:30.760> tree<00:18:31.159> up<00:18:31.320> to<00:18:31.520> a<00:18:31.720> certain<00:18:32.880> point 00:18:33.870 --> 00:18:33.880 align:start position:0% um a merket tree up to a certain point 00:18:33.880 --> 00:18:36.950 align:start position:0% um a merket tree up to a certain point uh<00:18:34.200> in<00:18:34.559> in<00:18:35.200> in<00:18:35.480> time<00:18:36.039> and<00:18:36.159> we<00:18:36.320> no<00:18:36.440> longer<00:18:36.760> need 00:18:36.950 --> 00:18:36.960 align:start position:0% uh in in in time and we no longer need 00:18:36.960 --> 00:18:38.270 align:start position:0% uh in in in time and we no longer need this<00:18:37.200> because<00:18:37.440> we<00:18:37.559> no<00:18:37.720> longer<00:18:37.960> need<00:18:38.120> to 00:18:38.270 --> 00:18:38.280 align:start position:0% this because we no longer need to 00:18:38.280 --> 00:18:41.430 align:start position:0% this because we no longer need to provide<00:18:38.600> proofs<00:18:39.559> because<00:18:39.880> we're<00:18:40.200> just<00:18:40.720> uh 00:18:41.430 --> 00:18:41.440 align:start position:0% provide proofs because we're just uh 00:18:41.440 --> 00:18:43.909 align:start position:0% provide proofs because we're just uh getting<00:18:41.840> the<00:18:42.039> deposits<00:18:42.440> from<00:18:42.600> the<00:18:42.760> engine 00:18:43.909 --> 00:18:43.919 align:start position:0% getting the deposits from the engine 00:18:43.919 --> 00:18:47.350 align:start position:0% getting the deposits from the engine API<00:18:44.919> and<00:18:45.640> one<00:18:45.799> other<00:18:46.080> benefit<00:18:46.480> is<00:18:46.679> that<00:18:46.880> we<00:18:47.039> no 00:18:47.350 --> 00:18:47.360 align:start position:0% API and one other benefit is that we no 00:18:47.360 --> 00:18:50.950 align:start position:0% API and one other benefit is that we no longer<00:18:48.360> rely<00:18:48.720> on<00:18:48.840> the<00:18:48.960> Json<00:18:49.280> RPC<00:18:49.679> API<00:18:50.600> we<00:18:50.760> only 00:18:50.950 --> 00:18:50.960 align:start position:0% longer rely on the Json RPC API we only 00:18:50.960 --> 00:18:52.270 align:start position:0% longer rely on the Json RPC API we only rely<00:18:51.240> on<00:18:51.320> the<00:18:51.440> engine 00:18:52.270 --> 00:18:52.280 align:start position:0% rely on the engine 00:18:52.280 --> 00:18:56.549 align:start position:0% rely on the engine API<00:18:53.280> and<00:18:53.640> it's<00:18:53.960> also<00:18:54.960> we<00:18:55.240> just<00:18:55.720> no<00:18:55.919> longer<00:18:56.240> need 00:18:56.549 --> 00:18:56.559 align:start position:0% API and it's also we just no longer need 00:18:56.559 --> 00:18:59.710 align:start position:0% API and it's also we just no longer need that<00:18:57.200> very<00:18:57.600> Legacy<00:18:58.280> Legacy<00:18:58.799> and<00:18:58.919> brittle<00:18:59.440> part 00:18:59.710 --> 00:18:59.720 align:start position:0% that very Legacy Legacy and brittle part 00:18:59.720 --> 00:19:02.990 align:start position:0% that very Legacy Legacy and brittle part of<00:18:59.840> the<00:18:59.960> C<00:19:00.320> clients<00:19:01.039> code<00:19:02.039> uh<00:19:02.200> which<00:19:02.320> is<00:19:02.600> always 00:19:02.990 --> 00:19:03.000 align:start position:0% of the C clients code uh which is always 00:19:03.000 --> 00:19:05.190 align:start position:0% of the C clients code uh which is always good<00:19:03.240> to<00:19:03.559> delete 00:19:05.190 --> 00:19:05.200 align:start position:0% good to delete 00:19:05.200 --> 00:19:09.549 align:start position:0% good to delete stuff<00:19:06.679> uh<00:19:07.679> and<00:19:07.880> one<00:19:08.039> more<00:19:08.240> slide<00:19:08.600> I<00:19:08.679> wanted<00:19:09.039> to 00:19:09.549 --> 00:19:09.559 align:start position:0% stuff uh and one more slide I wanted to 00:19:09.559 --> 00:19:13.470 align:start position:0% stuff uh and one more slide I wanted to show<00:19:10.520> I<00:19:10.640> wanted<00:19:10.880> to<00:19:11.120> quickly<00:19:11.960> show<00:19:12.559> that<00:19:13.240> this 00:19:13.470 --> 00:19:13.480 align:start position:0% show I wanted to quickly show that this 00:19:13.480 --> 00:19:17.230 align:start position:0% show I wanted to quickly show that this EAP<00:19:13.960> is<00:19:14.120> actually<00:19:14.760> not<00:19:15.400> is<00:19:15.760> actually<00:19:16.200> simple 00:19:17.230 --> 00:19:17.240 align:start position:0% EAP is actually not is actually simple 00:19:17.240 --> 00:19:21.230 align:start position:0% EAP is actually not is actually simple to<00:19:18.240> uh<00:19:19.159> Implement<00:19:20.159> so<00:19:20.440> if<00:19:20.559> you're<00:19:20.760> interested 00:19:21.230 --> 00:19:21.240 align:start position:0% to uh Implement so if you're interested 00:19:21.240 --> 00:19:23.789 align:start position:0% to uh Implement so if you're interested you<00:19:21.360> can<00:19:21.799> go<00:19:22.000> over<00:19:22.240> this<00:19:22.400> link<00:19:22.760> and<00:19:23.000> see<00:19:23.400> how<00:19:23.640> we 00:19:23.789 --> 00:19:23.799 align:start position:0% you can go over this link and see how we 00:19:23.799 --> 00:19:26.710 align:start position:0% you can go over this link and see how we implement<00:19:24.320> it<00:19:25.159> we<00:19:25.760> generally<00:19:26.200> try<00:19:26.400> to<00:19:26.520> do 00:19:26.710 --> 00:19:26.720 align:start position:0% implement it we generally try to do 00:19:26.720 --> 00:19:29.190 align:start position:0% implement it we generally try to do small<00:19:27.080> PR<00:19:27.520> so<00:19:27.679> it's<00:19:27.880> just<00:19:28.039> eight<00:19:28.280> PRS<00:19:28.799> but<00:19:29.000> it's 00:19:29.190 --> 00:19:29.200 align:start position:0% small PR so it's just eight PRS but it's 00:19:29.200 --> 00:19:32.789 align:start position:0% small PR so it's just eight PRS but it's not<00:19:29.520> big<00:19:30.200> changes<00:19:31.200> uh<00:19:31.360> so<00:19:31.919> if<00:19:32.039> you<00:19:32.240> ever<00:19:32.559> want 00:19:32.789 --> 00:19:32.799 align:start position:0% not big changes uh so if you ever want 00:19:32.799 --> 00:19:35.230 align:start position:0% not big changes uh so if you ever want to<00:19:33.000> check<00:19:33.320> how<00:19:33.480> ANP<00:19:34.000> is<00:19:34.080> implemented<00:19:34.600> actually 00:19:35.230 --> 00:19:35.240 align:start position:0% to check how ANP is implemented actually 00:19:35.240 --> 00:19:36.870 align:start position:0% to check how ANP is implemented actually this<00:19:35.360> is<00:19:35.480> a<00:19:35.640> good<00:19:35.799> one<00:19:35.919> to<00:19:36.080> go<00:19:36.240> over<00:19:36.559> because 00:19:36.870 --> 00:19:36.880 align:start position:0% this is a good one to go over because 00:19:36.880 --> 00:19:38.510 align:start position:0% this is a good one to go over because it's<00:19:37.080> quite 00:19:38.510 --> 00:19:38.520 align:start position:0% it's quite 00:19:38.520 --> 00:19:42.070 align:start position:0% it's quite simple<00:19:39.520> um<00:19:40.240> yeah<00:19:40.520> and<00:19:40.720> that's<00:19:41.240> uh<00:19:41.400> that's<00:19:41.640> it 00:19:42.070 --> 00:19:42.080 align:start position:0% simple um yeah and that's uh that's it 00:19:42.080 --> 00:19:44.040 align:start position:0% simple um yeah and that's uh that's it pretty 00:19:44.040 --> 00:19:44.050 align:start position:0% pretty 00:19:44.050 --> 00:19:50.430 align:start position:0% pretty [Applause] 00:19:50.430 --> 00:19:50.440 align:start position:0% [Applause] 00:19:50.440 --> 00:19:52.669 align:start position:0% [Applause] much<00:19:51.440> thank<00:19:51.640> you<00:19:51.840> thank<00:19:52.039> you<00:19:52.240> we're<00:19:52.400> going<00:19:52.520> to 00:19:52.669 --> 00:19:52.679 align:start position:0% much thank you thank you we're going to 00:19:52.679 --> 00:19:56.590 align:start position:0% much thank you thank you we're going to get<00:19:52.799> to<00:19:53.000> some<00:19:53.400> some<00:19:53.679> questions<00:19:54.480> now<00:19:55.480> um<00:19:56.360> and 00:19:56.590 --> 00:19:56.600 align:start position:0% get to some some questions now um and 00:19:56.600 --> 00:19:59.149 align:start position:0% get to some some questions now um and again<00:19:57.400> uh<00:19:57.480> if<00:19:57.600> you're<00:19:58.039> new<00:19:58.320> to 00:19:59.149 --> 00:19:59.159 align:start position:0% again uh if you're new to 00:19:59.159 --> 00:20:01.789 align:start position:0% again uh if you're new to uh<00:19:59.480> seeing<00:19:59.760> a<00:19:59.960> talk<00:20:00.240> today<00:20:00.799> scan<00:20:01.080> the<00:20:01.200> QR<00:20:01.520> code 00:20:01.789 --> 00:20:01.799 align:start position:0% uh seeing a talk today scan the QR code 00:20:01.799 --> 00:20:03.270 align:start position:0% uh seeing a talk today scan the QR code add<00:20:01.960> your<00:20:02.200> question<00:20:02.520> and<00:20:02.679> you<00:20:02.799> can<00:20:02.960> vote<00:20:03.200> if 00:20:03.270 --> 00:20:03.280 align:start position:0% add your question and you can vote if 00:20:03.280 --> 00:20:04.230 align:start position:0% add your question and you can vote if there's<00:20:03.480> one<00:20:03.600> that's<00:20:03.760> already<00:20:04.000> there<00:20:04.080> and<00:20:04.159> you 00:20:04.230 --> 00:20:04.240 align:start position:0% there's one that's already there and you 00:20:04.240 --> 00:20:05.549 align:start position:0% there's one that's already there and you would<00:20:04.400> like<00:20:04.480> to<00:20:04.600> see<00:20:04.720> it<00:20:04.880> answered<00:20:05.320> just<00:20:05.400> to 00:20:05.549 --> 00:20:05.559 align:start position:0% would like to see it answered just to 00:20:05.559 --> 00:20:06.909 align:start position:0% would like to see it answered just to make<00:20:05.679> sure<00:20:05.799> it<00:20:05.960> gets<00:20:06.159> answered<00:20:06.440> and<00:20:06.559> push<00:20:06.760> to 00:20:06.909 --> 00:20:06.919 align:start position:0% make sure it gets answered and push to 00:20:06.919 --> 00:20:08.710 align:start position:0% make sure it gets answered and push to the<00:20:07.039> top<00:20:07.159> of<00:20:07.240> the<00:20:07.360> que<00:20:08.120> um<00:20:08.280> thank<00:20:08.400> you<00:20:08.559> thank 00:20:08.710 --> 00:20:08.720 align:start position:0% the top of the que um thank you thank 00:20:08.720 --> 00:20:11.669 align:start position:0% the top of the que um thank you thank you<00:20:08.840> so<00:20:09.039> we<00:20:09.120> will<00:20:09.400> start<00:20:09.880> with<00:20:10.880> why<00:20:11.039> a<00:20:11.240> valid 00:20:11.669 --> 00:20:11.679 align:start position:0% you so we will start with why a valid 00:20:11.679 --> 00:20:13.510 align:start position:0% you so we will start with why a valid request<00:20:12.200> from<00:20:12.360> the<00:20:12.520> execution<00:20:13.000> layer<00:20:13.360> would 00:20:13.510 --> 00:20:13.520 align:start position:0% request from the execution layer would 00:20:13.520 --> 00:20:16.669 align:start position:0% request from the execution layer would be<00:20:13.720> rejected<00:20:14.159> on<00:20:14.320> the<00:20:14.520> consensus 00:20:16.669 --> 00:20:16.679 align:start position:0% be rejected on the consensus 00:20:16.679 --> 00:20:19.750 align:start position:0% be rejected on the consensus layer<00:20:17.679> um<00:20:17.840> I<00:20:17.919> can<00:20:18.080> probably<00:20:18.320> take<00:20:18.559> that<00:20:18.720> one<00:20:19.440> um 00:20:19.750 --> 00:20:19.760 align:start position:0% layer um I can probably take that one um 00:20:19.760 --> 00:20:21.830 align:start position:0% layer um I can probably take that one um it's<00:20:20.400> it's<00:20:20.559> hard<00:20:20.720> to<00:20:21.200> it's<00:20:21.320> hard<00:20:21.480> to<00:20:21.640> go 00:20:21.830 --> 00:20:21.840 align:start position:0% it's it's hard to it's hard to go 00:20:21.840 --> 00:20:24.669 align:start position:0% it's it's hard to it's hard to go through<00:20:22.840> all<00:20:23.039> the<00:20:23.159> different<00:20:23.559> reasons<00:20:24.159> why<00:20:24.559> uh 00:20:24.669 --> 00:20:24.679 align:start position:0% through all the different reasons why uh 00:20:24.679 --> 00:20:25.909 align:start position:0% through all the different reasons why uh I<00:20:24.760> think<00:20:24.880> the<00:20:25.000> best<00:20:25.159> way<00:20:25.280> of<00:20:25.440> thinking<00:20:25.720> about 00:20:25.909 --> 00:20:25.919 align:start position:0% I think the best way of thinking about 00:20:25.919 --> 00:20:28.789 align:start position:0% I think the best way of thinking about it<00:20:26.120> is<00:20:26.280> that<00:20:26.840> I<00:20:27.000> like<00:20:27.159> to<00:20:27.360> separate<00:20:28.080> that<00:20:28.240> the<00:20:28.360> e 00:20:28.789 --> 00:20:28.799 align:start position:0% it is that I like to separate that the e 00:20:28.799 --> 00:20:31.149 align:start position:0% it is that I like to separate that the e is<00:20:28.880> doing<00:20:29.080> the<00:20:29.159> authentication<00:20:29.919> side<00:20:30.240> of<00:20:30.480> the 00:20:31.149 --> 00:20:31.159 align:start position:0% is doing the authentication side of the 00:20:31.159 --> 00:20:33.549 align:start position:0% is doing the authentication side of the uh<00:20:31.360> request<00:20:31.799> and<00:20:32.000> the<00:20:32.400> C<00:20:32.840> is<00:20:32.960> doing<00:20:33.280> the 00:20:33.549 --> 00:20:33.559 align:start position:0% uh request and the C is doing the 00:20:33.559 --> 00:20:36.149 align:start position:0% uh request and the C is doing the authorization<00:20:34.400> side<00:20:34.600> of<00:20:34.760> the<00:20:34.960> request<00:20:35.799> so<00:20:36.080> I 00:20:36.149 --> 00:20:36.159 align:start position:0% authorization side of the request so I 00:20:36.159 --> 00:20:37.669 align:start position:0% authorization side of the request so I think<00:20:36.440> the<00:20:36.640> easiest<00:20:37.039> example<00:20:37.320> that<00:20:37.440> I<00:20:37.520> can 00:20:37.669 --> 00:20:37.679 align:start position:0% think the easiest example that I can 00:20:37.679 --> 00:20:39.630 align:start position:0% think the easiest example that I can think<00:20:37.880> of<00:20:38.360> uh<00:20:38.440> for<00:20:38.640> example<00:20:38.960> for<00:20:39.200> withdraw 00:20:39.630 --> 00:20:39.640 align:start position:0% think of uh for example for withdraw 00:20:39.640 --> 00:20:41.669 align:start position:0% think of uh for example for withdraw requests<00:20:40.600> let's<00:20:40.760> say<00:20:40.919> that<00:20:41.039> you<00:20:41.159> create<00:20:41.480> a 00:20:41.669 --> 00:20:41.679 align:start position:0% requests let's say that you create a 00:20:41.679 --> 00:20:44.870 align:start position:0% requests let's say that you create a request<00:20:42.280> for<00:20:43.039> someone<00:20:43.320> else's<00:20:43.640> valid<00:20:43.919> dator 00:20:44.870 --> 00:20:44.880 align:start position:0% request for someone else's valid dator 00:20:44.880 --> 00:20:47.190 align:start position:0% request for someone else's valid dator right<00:20:45.520> so<00:20:46.240> the<00:20:46.400> transaction<00:20:46.799> is<00:20:46.880> going<00:20:46.960> to<00:20:47.080> be 00:20:47.190 --> 00:20:47.200 align:start position:0% right so the transaction is going to be 00:20:47.200 --> 00:20:48.669 align:start position:0% right so the transaction is going to be successful<00:20:47.720> the<00:20:47.840> request<00:20:48.120> is<00:20:48.240> going<00:20:48.320> to<00:20:48.480> be 00:20:48.669 --> 00:20:48.679 align:start position:0% successful the request is going to be 00:20:48.679 --> 00:20:51.870 align:start position:0% successful the request is going to be added<00:20:49.000> to<00:20:49.240> the<00:20:49.840> uh<00:20:49.960> to<00:20:50.120> the<00:20:50.360> contract<00:20:51.360> but<00:20:51.640> when 00:20:51.870 --> 00:20:51.880 align:start position:0% added to the uh to the contract but when 00:20:51.880 --> 00:20:54.110 align:start position:0% added to the uh to the contract but when the<00:20:52.080> cles<00:20:52.880> that<00:20:53.080> request<00:20:53.480> is<00:20:53.600> going<00:20:53.679> to<00:20:53.799> try<00:20:53.960> to 00:20:54.110 --> 00:20:54.120 align:start position:0% the cles that request is going to try to 00:20:54.120 --> 00:20:55.710 align:start position:0% the cles that request is going to try to match<00:20:54.480> the<00:20:54.640> source<00:20:55.000> address<00:20:55.440> with<00:20:55.559> the 00:20:55.710 --> 00:20:55.720 align:start position:0% match the source address with the 00:20:55.720 --> 00:20:57.350 align:start position:0% match the source address with the validator<00:20:56.480> uh<00:20:56.559> validator<00:20:57.000> withdraw 00:20:57.350 --> 00:20:57.360 align:start position:0% validator uh validator withdraw 00:20:57.360 --> 00:20:59.110 align:start position:0% validator uh validator withdraw credentials<00:20:57.840> it's<00:20:58.000> going<00:20:58.080> to<00:20:58.159> say<00:20:58.440> well<00:20:58.640> well 00:20:59.110 --> 00:20:59.120 align:start position:0% credentials it's going to say well well 00:20:59.120 --> 00:21:00.710 align:start position:0% credentials it's going to say well well you<00:20:59.240> don't<00:20:59.440> really<00:20:59.600> own<00:21:00.000> that<00:21:00.400> you<00:21:00.520> can't 00:21:00.710 --> 00:21:00.720 align:start position:0% you don't really own that you can't 00:21:00.720 --> 00:21:02.149 align:start position:0% you don't really own that you can't really<00:21:00.880> do<00:21:01.080> that<00:21:01.400> right<00:21:01.520> so<00:21:01.679> that's<00:21:01.919> one<00:21:02.039> of 00:21:02.149 --> 00:21:02.159 align:start position:0% really do that right so that's one of 00:21:02.159 --> 00:21:06.230 align:start position:0% really do that right so that's one of the<00:21:02.520> reasons<00:21:03.679> um<00:21:04.679> yeah<00:21:05.000> like<00:21:05.200> there<00:21:05.320> are<00:21:05.840> other 00:21:06.230 --> 00:21:06.240 align:start position:0% the reasons um yeah like there are other 00:21:06.240 --> 00:21:08.270 align:start position:0% the reasons um yeah like there are other more<00:21:06.640> specific<00:21:07.000> rules<00:21:07.440> that<00:21:07.640> can<00:21:08.000> but<00:21:08.120> I<00:21:08.200> think 00:21:08.270 --> 00:21:08.280 align:start position:0% more specific rules that can but I think 00:21:08.280 --> 00:21:09.390 align:start position:0% more specific rules that can but I think that's<00:21:08.440> probably<00:21:08.640> the<00:21:08.679> easiest<00:21:08.960> way<00:21:09.080> to<00:21:09.200> think 00:21:09.390 --> 00:21:09.400 align:start position:0% that's probably the easiest way to think 00:21:09.400 --> 00:21:11.909 align:start position:0% that's probably the easiest way to think about<00:21:09.559> it<00:21:10.240> the<00:21:10.400> E<00:21:10.760> doesn't<00:21:11.000> really<00:21:11.200> know<00:21:11.679> the 00:21:11.909 --> 00:21:11.919 align:start position:0% about it the E doesn't really know the 00:21:11.919 --> 00:21:14.669 align:start position:0% about it the E doesn't really know the rule<00:21:12.240> the<00:21:12.360> business<00:21:12.840> rules<00:21:13.200> on<00:21:13.320> the<00:21:13.440> CL<00:21:13.919> side 00:21:14.669 --> 00:21:14.679 align:start position:0% rule the business rules on the CL side 00:21:14.679 --> 00:21:16.070 align:start position:0% rule the business rules on the CL side in<00:21:14.799> the<00:21:14.880> same<00:21:15.039> way<00:21:15.159> that<00:21:15.320> a<00:21:15.679> can't<00:21:15.840> really 00:21:16.070 --> 00:21:16.080 align:start position:0% in the same way that a can't really 00:21:16.080 --> 00:21:17.789 align:start position:0% in the same way that a can't really validate<00:21:16.760> beforehand<00:21:17.279> that<00:21:17.440> that's<00:21:17.600> the 00:21:17.789 --> 00:21:17.799 align:start position:0% validate beforehand that that's the 00:21:17.799 --> 00:21:20.029 align:start position:0% validate beforehand that that's the right<00:21:18.200> uh<00:21:18.320> validator<00:21:18.919> so<00:21:19.159> that's<00:21:19.400> kind<00:21:19.520> of 00:21:20.029 --> 00:21:20.039 align:start position:0% right uh validator so that's kind of 00:21:20.039 --> 00:21:22.510 align:start position:0% right uh validator so that's kind of part<00:21:20.200> of<00:21:20.320> the<00:21:20.480> reason<00:21:21.080> hopefully<00:21:21.840> yeah<00:21:22.360> that's 00:21:22.510 --> 00:21:22.520 align:start position:0% part of the reason hopefully yeah that's 00:21:22.520 --> 00:21:24.269 align:start position:0% part of the reason hopefully yeah that's it<00:21:22.919> thank<00:21:23.080> you<00:21:23.480> and<00:21:23.679> looks<00:21:23.840> like<00:21:24.000> we<00:21:24.120> have 00:21:24.269 --> 00:21:24.279 align:start position:0% it thank you and looks like we have 00:21:24.279 --> 00:21:26.310 align:start position:0% it thank you and looks like we have another<00:21:24.520> one<00:21:24.640> for<00:21:24.840> you<00:21:25.240> right<00:21:25.480> again<00:21:26.000> so<00:21:26.200> why 00:21:26.310 --> 00:21:26.320 align:start position:0% another one for you right again so why 00:21:26.320 --> 00:21:28.029 align:start position:0% another one for you right again so why do<00:21:26.440> you<00:21:26.559> think<00:21:26.919> contract<00:21:27.400> address<00:21:27.840> as<00:21:27.960> a 00:21:28.029 --> 00:21:28.039 align:start position:0% do you think contract address as a 00:21:28.039 --> 00:21:32.110 align:start position:0% do you think contract address as a withdrawal<00:21:28.559> itial<00:21:28.919> is<00:21:29.000> a 00:21:32.110 --> 00:21:32.120 align:start position:0% 00:21:32.120 --> 00:21:34.710 align:start position:0% caveat<00:21:33.200> um 00:21:34.710 --> 00:21:34.720 align:start position:0% caveat um 00:21:34.720 --> 00:21:37.510 align:start position:0% caveat um it's<00:21:35.720> it's<00:21:35.919> more<00:21:36.279> like<00:21:36.720> it's<00:21:36.919> a<00:21:37.159> more 00:21:37.510 --> 00:21:37.520 align:start position:0% it's it's more like it's a more 00:21:37.520 --> 00:21:40.310 align:start position:0% it's it's more like it's a more complicated<00:21:38.279> thing<00:21:38.960> because<00:21:39.640> um<00:21:40.039> there<00:21:40.240> there 00:21:40.310 --> 00:21:40.320 align:start position:0% complicated thing because um there there 00:21:40.320 --> 00:21:42.070 align:start position:0% complicated thing because um there there are<00:21:40.440> two<00:21:40.640> problems<00:21:40.919> with<00:21:41.080> this<00:21:41.360> one<00:21:41.600> is<00:21:41.799> that 00:21:42.070 --> 00:21:42.080 align:start position:0% are two problems with this one is that 00:21:42.080 --> 00:21:44.350 align:start position:0% are two problems with this one is that the<00:21:42.919> currently<00:21:43.360> the<00:21:43.520> validator<00:21:43.960> withdra 00:21:44.350 --> 00:21:44.360 align:start position:0% the currently the validator withdra 00:21:44.360 --> 00:21:46.510 align:start position:0% the currently the validator withdra credentials<00:21:45.039> cannot<00:21:45.360> be<00:21:45.559> updated<00:21:46.080> so<00:21:46.279> once 00:21:46.510 --> 00:21:46.520 align:start position:0% credentials cannot be updated so once 00:21:46.520 --> 00:21:48.470 align:start position:0% credentials cannot be updated so once you<00:21:47.159> I<00:21:47.279> didn't<00:21:47.520> really<00:21:47.720> touch<00:21:47.960> on<00:21:48.120> the<00:21:48.279> whole 00:21:48.470 --> 00:21:48.480 align:start position:0% you I didn't really touch on the whole 00:21:48.480 --> 00:21:50.350 align:start position:0% you I didn't really touch on the whole BLS<00:21:48.960> credential<00:21:49.400> side<00:21:49.559> of<00:21:49.679> things<00:21:49.960> which<00:21:50.080> is 00:21:50.350 --> 00:21:50.360 align:start position:0% BLS credential side of things which is 00:21:50.360 --> 00:21:51.950 align:start position:0% BLS credential side of things which is something<00:21:50.640> that<00:21:50.840> already<00:21:51.159> was<00:21:51.400> there<00:21:51.600> before 00:21:51.950 --> 00:21:51.960 align:start position:0% something that already was there before 00:21:51.960 --> 00:21:53.950 align:start position:0% something that already was there before but<00:21:52.640> the<00:21:52.760> way<00:21:52.880> that<00:21:53.000> it<00:21:53.120> works<00:21:53.400> right<00:21:53.520> now<00:21:53.799> once 00:21:53.950 --> 00:21:53.960 align:start position:0% but the way that it works right now once 00:21:53.960 --> 00:21:55.430 align:start position:0% but the way that it works right now once you<00:21:54.120> set<00:21:54.400> your<00:21:54.679> validator<00:21:55.120> withdraw 00:21:55.430 --> 00:21:55.440 align:start position:0% you set your validator withdraw 00:21:55.440 --> 00:21:56.950 align:start position:0% you set your validator withdraw credentials<00:21:55.880> to<00:21:56.000> one<00:21:56.200> address<00:21:56.520> you<00:21:56.640> can<00:21:56.760> never 00:21:56.950 --> 00:21:56.960 align:start position:0% credentials to one address you can never 00:21:56.960 --> 00:22:00.269 align:start position:0% credentials to one address you can never change<00:21:57.240> that<00:21:57.440> address<00:21:58.279> so<00:21:58.640> so<00:21:59.440> a<00:21:59.520> few<00:21:59.799> problems 00:22:00.269 --> 00:22:00.279 align:start position:0% change that address so so a few problems 00:22:00.279 --> 00:22:02.590 align:start position:0% change that address so so a few problems happens<00:22:00.720> here<00:22:01.240> the<00:22:01.400> first<00:22:01.640> one<00:22:01.960> is<00:22:02.360> as<00:22:02.440> I 00:22:02.590 --> 00:22:02.600 align:start position:0% happens here the first one is as I 00:22:02.600 --> 00:22:05.350 align:start position:0% happens here the first one is as I mentioned<00:22:03.440> if<00:22:03.600> you<00:22:03.960> have<00:22:04.240> your<00:22:04.480> valid<00:22:04.840> dator 00:22:05.350 --> 00:22:05.360 align:start position:0% mentioned if you have your valid dator 00:22:05.360 --> 00:22:08.669 align:start position:0% mentioned if you have your valid dator credentials<00:22:06.240> set<00:22:06.559> to<00:22:06.799> a<00:22:07.559> contract<00:22:08.000> address 00:22:08.669 --> 00:22:08.679 align:start position:0% credentials set to a contract address 00:22:08.679 --> 00:22:11.310 align:start position:0% credentials set to a contract address that<00:22:08.840> is<00:22:09.000> not<00:22:09.720> upgradeable<00:22:10.720> you're<00:22:11.039> never 00:22:11.310 --> 00:22:11.320 align:start position:0% that is not upgradeable you're never 00:22:11.320 --> 00:22:13.350 align:start position:0% that is not upgradeable you're never going<00:22:11.440> to<00:22:11.559> be<00:22:11.679> able<00:22:11.880> to<00:22:12.360> update<00:22:12.720> that<00:22:12.919> code<00:22:13.200> to 00:22:13.350 --> 00:22:13.360 align:start position:0% going to be able to update that code to 00:22:13.360 --> 00:22:15.549 align:start position:0% going to be able to update that code to call<00:22:13.640> the<00:22:13.760> request<00:22:14.120> contract<00:22:14.440> so<00:22:14.760> you<00:22:14.960> you 00:22:15.549 --> 00:22:15.559 align:start position:0% call the request contract so you you 00:22:15.559 --> 00:22:17.029 align:start position:0% call the request contract so you you you're<00:22:15.760> you're<00:22:15.880> already<00:22:16.200> kind<00:22:16.320> of<00:22:16.480> locked<00:22:16.799> out 00:22:17.029 --> 00:22:17.039 align:start position:0% you're you're already kind of locked out 00:22:17.039 --> 00:22:19.789 align:start position:0% you're you're already kind of locked out from<00:22:17.200> this<00:22:17.400> mechanism<00:22:17.840> straight<00:22:18.240> away<00:22:19.240> if<00:22:19.360> you 00:22:19.789 --> 00:22:19.799 align:start position:0% from this mechanism straight away if you 00:22:19.799 --> 00:22:21.390 align:start position:0% from this mechanism straight away if you have<00:22:20.000> an<00:22:20.159> upgradable<00:22:20.679> contract<00:22:21.080> you<00:22:21.159> can 00:22:21.390 --> 00:22:21.400 align:start position:0% have an upgradable contract you can 00:22:21.400 --> 00:22:24.029 align:start position:0% have an upgradable contract you can write<00:22:21.640> some<00:22:21.840> code<00:22:22.080> to<00:22:22.279> kind<00:22:22.360> of<00:22:22.640> get<00:22:22.799> around<00:22:23.039> it 00:22:24.029 --> 00:22:24.039 align:start position:0% write some code to kind of get around it 00:22:24.039 --> 00:22:25.789 align:start position:0% write some code to kind of get around it um<00:22:24.159> so<00:22:24.279> it's<00:22:24.400> more<00:22:24.520> like<00:22:24.640> a<00:22:24.720> kvat<00:22:25.159> in<00:22:25.240> terms<00:22:25.520> of 00:22:25.789 --> 00:22:25.799 align:start position:0% um so it's more like a kvat in terms of 00:22:25.799 --> 00:22:26.870 align:start position:0% um so it's more like a kvat in terms of something<00:22:26.039> that<00:22:26.159> people<00:22:26.360> need<00:22:26.480> to<00:22:26.600> get<00:22:26.720> their 00:22:26.870 --> 00:22:26.880 align:start position:0% something that people need to get their 00:22:26.880 --> 00:22:28.110 align:start position:0% something that people need to get their heads<00:22:27.120> around<00:22:27.440> and<00:22:27.600> make<00:22:27.720> sure<00:22:27.880> that<00:22:28.000> they 00:22:28.110 --> 00:22:28.120 align:start position:0% heads around and make sure that they 00:22:28.120 --> 00:22:29.789 align:start position:0% heads around and make sure that they consider<00:22:28.520> when<00:22:28.640> they<00:22:28.799> implementing<00:22:29.640> because 00:22:29.789 --> 00:22:29.799 align:start position:0% consider when they implementing because 00:22:29.799 --> 00:22:31.750 align:start position:0% consider when they implementing because I<00:22:29.880> think<00:22:30.000> the<00:22:30.120> natural<00:22:30.480> thing<00:22:30.640> to<00:22:30.840> think<00:22:31.360> is 00:22:31.750 --> 00:22:31.760 align:start position:0% I think the natural thing to think is 00:22:31.760 --> 00:22:33.149 align:start position:0% I think the natural thing to think is well<00:22:32.000> I'm<00:22:32.120> going<00:22:32.240> to<00:22:32.360> sign<00:22:32.559> the<00:22:32.679> transaction 00:22:33.149 --> 00:22:33.159 align:start position:0% well I'm going to sign the transaction 00:22:33.159 --> 00:22:35.710 align:start position:0% well I'm going to sign the transaction with<00:22:33.320> this<00:22:33.559> credential<00:22:34.240> with<00:22:34.440> this<00:22:35.120> account 00:22:35.710 --> 00:22:35.720 align:start position:0% with this credential with this account 00:22:35.720 --> 00:22:37.230 align:start position:0% with this credential with this account sorry<00:22:36.159> uh<00:22:36.279> key<00:22:36.559> and<00:22:36.679> that's<00:22:36.840> the<00:22:36.960> one<00:22:37.080> that's 00:22:37.230 --> 00:22:37.240 align:start position:0% sorry uh key and that's the one that's 00:22:37.240 --> 00:22:39.310 align:start position:0% sorry uh key and that's the one that's going<00:22:37.320> to<00:22:37.400> show<00:22:37.600> up<00:22:37.720> on<00:22:37.840> the<00:22:37.960> request<00:22:38.440> but<00:22:39.159> that 00:22:39.310 --> 00:22:39.320 align:start position:0% going to show up on the request but that 00:22:39.320 --> 00:22:40.630 align:start position:0% going to show up on the request but that that's<00:22:39.480> why<00:22:39.679> it's<00:22:39.799> kind<00:22:39.919> of<00:22:40.000> a 00:22:40.630 --> 00:22:40.640 align:start position:0% that's why it's kind of a 00:22:40.640 --> 00:22:44.350 align:start position:0% that's why it's kind of a caveat<00:22:41.640> thank<00:22:41.840> you<00:22:42.480> all<00:22:42.679> right<00:22:43.000> now<00:22:43.159> for<00:22:43.440> you 00:22:44.350 --> 00:22:44.360 align:start position:0% caveat thank you all right now for you 00:22:44.360 --> 00:22:48.269 align:start position:0% caveat thank you all right now for you um<00:22:45.039> if<00:22:45.240> EIP<00:22:45.679> 6110<00:22:46.520> makes<00:22:46.799> eth1<00:22:47.320> vote<00:22:47.600> Legacy<00:22:48.159> do 00:22:48.269 --> 00:22:48.279 align:start position:0% um if EIP 6110 makes eth1 vote Legacy do 00:22:48.279 --> 00:22:51.269 align:start position:0% um if EIP 6110 makes eth1 vote Legacy do we<00:22:48.480> have<00:22:48.600> to<00:22:48.840> carry<00:22:49.480> all<00:22:49.720> eth1<00:22:50.200> voting<00:22:50.520> fields 00:22:51.269 --> 00:22:51.279 align:start position:0% we have to carry all eth1 voting fields 00:22:51.279 --> 00:22:53.950 align:start position:0% we have to carry all eth1 voting fields and<00:22:51.520> Logics<00:22:51.960> in<00:22:52.159> consensus<00:22:52.640> layer<00:22:53.120> even<00:22:53.720> in 00:22:53.950 --> 00:22:53.960 align:start position:0% and Logics in consensus layer even in 00:22:53.960 --> 00:22:56.990 align:start position:0% and Logics in consensus layer even in post<00:22:54.320> Electra<00:22:55.320> yeah<00:22:55.480> sure<00:22:56.120> uh<00:22:56.320> so<00:22:56.640> there<00:22:56.760> is<00:22:56.880> a 00:22:56.990 --> 00:22:57.000 align:start position:0% post Electra yeah sure uh so there is a 00:22:57.000 --> 00:22:59.390 align:start position:0% post Electra yeah sure uh so there is a little<00:22:57.200> bit<00:22:57.320> of<00:22:57.480> transition<00:22:57.960> period<00:22:58.520> when<00:22:58.919> the 00:22:59.390 --> 00:22:59.400 align:start position:0% little bit of transition period when the 00:22:59.400 --> 00:23:02.070 align:start position:0% little bit of transition period when the when<00:23:00.400> post<00:23:00.720> electrod<00:23:01.159> to<00:23:01.360> transition<00:23:01.799> to<00:23:01.960> the 00:23:02.070 --> 00:23:02.080 align:start position:0% when post electrod to transition to the 00:23:02.080 --> 00:23:04.310 align:start position:0% when post electrod to transition to the new<00:23:02.279> way<00:23:02.799> because<00:23:03.039> we<00:23:03.200> still<00:23:03.440> have<00:23:03.559> to<00:23:03.840> process 00:23:04.310 --> 00:23:04.320 align:start position:0% new way because we still have to process 00:23:04.320 --> 00:23:07.190 align:start position:0% new way because we still have to process deposits<00:23:05.120> VI<00:23:05.360> the<00:23:05.480> old<00:23:05.640> way<00:23:05.880> for<00:23:06.080> some<00:23:06.279> time 00:23:07.190 --> 00:23:07.200 align:start position:0% deposits VI the old way for some time 00:23:07.200 --> 00:23:09.390 align:start position:0% deposits VI the old way for some time but<00:23:07.440> after<00:23:07.720> that<00:23:07.880> is<00:23:08.080> done<00:23:08.679> we<00:23:08.840> can<00:23:09.159> pretty 00:23:09.390 --> 00:23:09.400 align:start position:0% but after that is done we can pretty 00:23:09.400 --> 00:23:11.950 align:start position:0% but after that is done we can pretty much<00:23:09.720> remove<00:23:10.240> all<00:23:10.440> of<00:23:10.679> the<00:23:10.919> this<00:23:11.159> Legacy<00:23:11.559> code 00:23:11.950 --> 00:23:11.960 align:start position:0% much remove all of the this Legacy code 00:23:11.960 --> 00:23:16.149 align:start position:0% much remove all of the this Legacy code in<00:23:12.679> uh<00:23:13.679> in<00:23:14.080> next<00:23:14.480> releases<00:23:14.960> after<00:23:15.279> the 00:23:16.149 --> 00:23:16.159 align:start position:0% in uh in next releases after the 00:23:16.159 --> 00:23:19.029 align:start position:0% in uh in next releases after the fork<00:23:17.159> thank<00:23:17.360> you<00:23:18.080> um<00:23:18.240> is<00:23:18.360> there<00:23:18.480> a<00:23:18.720> proof 00:23:19.029 --> 00:23:19.039 align:start position:0% fork thank you um is there a proof 00:23:19.039 --> 00:23:21.029 align:start position:0% fork thank you um is there a proof generation<00:23:19.720> process<00:23:20.080> to<00:23:20.240> withdrawal<00:23:20.760> similar 00:23:21.029 --> 00:23:21.039 align:start position:0% generation process to withdrawal similar 00:23:21.039 --> 00:23:23.269 align:start position:0% generation process to withdrawal similar to<00:23:21.200> performing<00:23:21.679> igen<00:23:22.000> layer 00:23:23.269 --> 00:23:23.279 align:start position:0% to performing igen layer 00:23:23.279 --> 00:23:25.549 align:start position:0% to performing igen layer withdraws<00:23:24.279> um<00:23:24.679> unfortunately<00:23:25.240> I'm<00:23:25.360> not 00:23:25.549 --> 00:23:25.559 align:start position:0% withdraws um unfortunately I'm not 00:23:25.559 --> 00:23:27.789 align:start position:0% withdraws um unfortunately I'm not familiar<00:23:26.039> with<00:23:26.360> IG<00:23:26.679> layer<00:23:27.000> withdrawals 00:23:27.789 --> 00:23:27.799 align:start position:0% familiar with IG layer withdrawals 00:23:27.799 --> 00:23:30.350 align:start position:0% familiar with IG layer withdrawals process<00:23:28.880> but<00:23:29.159> there's<00:23:29.360> no<00:23:29.520> proof<00:23:29.840> generation 00:23:30.350 --> 00:23:30.360 align:start position:0% process but there's no proof generation 00:23:30.360 --> 00:23:35.230 align:start position:0% process but there's no proof generation on<00:23:31.360> this<00:23:31.919> withdrawal<00:23:32.919> um<00:23:33.520> hopefully<00:23:34.360> uh<00:23:34.760> if<00:23:34.880> I 00:23:35.230 --> 00:23:35.240 align:start position:0% on this withdrawal um hopefully uh if I 00:23:35.240 --> 00:23:38.149 align:start position:0% on this withdrawal um hopefully uh if I understand<00:23:35.320> the<00:23:35.480> question<00:23:35.919> there's<00:23:36.159> no<00:23:36.600> Pro 00:23:38.149 --> 00:23:38.159 align:start position:0% understand the question there's no Pro 00:23:38.159 --> 00:23:40.549 align:start position:0% understand the question there's no Pro Generation<00:23:39.159> Um<00:23:39.360> what<00:23:39.520> if<00:23:39.640> a<00:23:39.840> deposited 00:23:40.549 --> 00:23:40.559 align:start position:0% Generation Um what if a deposited 00:23:40.559 --> 00:23:43.990 align:start position:0% Generation Um what if a deposited request<00:23:41.000> failed<00:23:41.720> will<00:23:41.960> users<00:23:42.640> eth<00:23:43.000> be 00:23:43.990 --> 00:23:44.000 align:start position:0% request failed will users eth be 00:23:44.000 --> 00:23:46.750 align:start position:0% request failed will users eth be refunded<00:23:45.000> so<00:23:45.440> when<00:23:45.600> you<00:23:45.840> deposit<00:23:46.279> if<00:23:46.520> to<00:23:46.640> the 00:23:46.750 --> 00:23:46.760 align:start position:0% refunded so when you deposit if to the 00:23:46.760 --> 00:23:47.870 align:start position:0% refunded so when you deposit if to the smart 00:23:47.870 --> 00:23:47.880 align:start position:0% smart 00:23:47.880 --> 00:23:50.710 align:start position:0% smart contract<00:23:48.880> there<00:23:49.000> is<00:23:49.320> technically<00:23:49.919> no<00:23:50.240> way<00:23:50.520> a 00:23:50.710 --> 00:23:50.720 align:start position:0% contract there is technically no way a 00:23:50.720 --> 00:23:53.470 align:start position:0% contract there is technically no way a deposit<00:23:51.159> request<00:23:51.559> fails<00:23:52.279> so<00:23:52.679> if<00:23:52.960> the<00:23:53.120> deposit 00:23:53.470 --> 00:23:53.480 align:start position:0% deposit request fails so if the deposit 00:23:53.480 --> 00:23:55.510 align:start position:0% deposit request fails so if the deposit request<00:23:53.760> fails<00:23:54.240> that<00:23:54.880> that<00:23:55.000> means<00:23:55.240> that<00:23:55.400> there 00:23:55.510 --> 00:23:55.520 align:start position:0% request fails that that means that there 00:23:55.520 --> 00:23:58.710 align:start position:0% request fails that that means that there is<00:23:55.720> like<00:23:55.840> a<00:23:56.039> consensus<00:23:56.799> failure<00:23:57.440> which<00:23:58.520> yeah 00:23:58.710 --> 00:23:58.720 align:start position:0% is like a consensus failure which yeah 00:23:58.720 --> 00:24:01.990 align:start position:0% is like a consensus failure which yeah it<00:23:58.880> wouldn't<00:23:59.120> be<00:23:59.279> refunded<00:23:59.760> but<00:23:59.919> it's<00:24:00.080> a<00:24:00.400> big 00:24:01.990 --> 00:24:02.000 align:start position:0% it wouldn't be refunded but it's a big 00:24:02.000 --> 00:24:04.230 align:start position:0% it wouldn't be refunded but it's a big issue<00:24:03.000> all<00:24:03.159> right<00:24:03.320> I<00:24:03.400> think<00:24:03.520> we<00:24:03.640> have<00:24:03.840> time<00:24:04.000> for 00:24:04.230 --> 00:24:04.240 align:start position:0% issue all right I think we have time for 00:24:04.240 --> 00:24:08.070 align:start position:0% issue all right I think we have time for one<00:24:04.520> maybe<00:24:04.799> two<00:24:05.279> more<00:24:06.279> um<00:24:07.200> how<00:24:07.440> resilient<00:24:07.919> is 00:24:08.070 --> 00:24:08.080 align:start position:0% one maybe two more um how resilient is 00:24:08.080 --> 00:24:11.830 align:start position:0% one maybe two more um how resilient is the<00:24:08.200> engine<00:24:08.600> API<00:24:09.080> comparing<00:24:09.440> to<00:24:09.600> Json<00:24:10.200> RPC<00:24:10.840> API 00:24:11.830 --> 00:24:11.840 align:start position:0% the engine API comparing to Json RPC API 00:24:11.840 --> 00:24:15.710 align:start position:0% the engine API comparing to Json RPC API yeah<00:24:12.039> so<00:24:12.320> the<00:24:12.559> engine<00:24:12.840> API<00:24:13.400> basically<00:24:14.400> drives 00:24:15.710 --> 00:24:15.720 align:start position:0% yeah so the engine API basically drives 00:24:15.720 --> 00:24:19.269 align:start position:0% yeah so the engine API basically drives the<00:24:17.039> execution<00:24:18.039> uh<00:24:18.360> the<00:24:18.520> consensus<00:24:19.000> layer 00:24:19.269 --> 00:24:19.279 align:start position:0% the execution uh the consensus layer 00:24:19.279 --> 00:24:22.549 align:start position:0% the execution uh the consensus layer client<00:24:19.720> drives<00:24:20.200> the<00:24:20.400> execution<00:24:21.000> layer<00:24:22.000> client 00:24:22.549 --> 00:24:22.559 align:start position:0% client drives the execution layer client 00:24:22.559 --> 00:24:24.909 align:start position:0% client drives the execution layer client via<00:24:22.760> the<00:24:22.880> engine<00:24:23.120> API<00:24:23.960> so<00:24:24.159> it<00:24:24.279> is<00:24:24.480> very 00:24:24.909 --> 00:24:24.919 align:start position:0% via the engine API so it is very 00:24:24.919 --> 00:24:28.950 align:start position:0% via the engine API so it is very resilient<00:24:25.640> the<00:24:25.799> Json<00:24:26.120> RPC<00:24:26.760> API<00:24:27.760> can 00:24:28.950 --> 00:24:28.960 align:start position:0% resilient the Json RPC API can 00:24:28.960 --> 00:24:32.990 align:start position:0% resilient the Json RPC API can uh<00:24:29.320> it's<00:24:30.320> not<00:24:31.320> it's<00:24:31.520> still<00:24:31.799> very<00:24:32.000> reliable<00:24:32.679> but 00:24:32.990 --> 00:24:33.000 align:start position:0% uh it's not it's still very reliable but 00:24:33.000 --> 00:24:35.430 align:start position:0% uh it's not it's still very reliable but it<00:24:33.120> is<00:24:33.320> not<00:24:33.840> uh<00:24:34.080> critical<00:24:34.600> so<00:24:34.919> there<00:24:35.120> could<00:24:35.279> be 00:24:35.430 --> 00:24:35.440 align:start position:0% it is not uh critical so there could be 00:24:35.440 --> 00:24:38.110 align:start position:0% it is not uh critical so there could be some<00:24:36.360> implementations<00:24:37.080> in<00:24:37.240> some<00:24:37.440> Clans<00:24:38.000> which 00:24:38.110 --> 00:24:38.120 align:start position:0% some implementations in some Clans which 00:24:38.120 --> 00:24:40.470 align:start position:0% some implementations in some Clans which are<00:24:38.880> less<00:24:39.200> reliable<00:24:39.640> to<00:24:39.720> the<00:24:39.799> engine<00:24:40.080> API 00:24:40.470 --> 00:24:40.480 align:start position:0% are less reliable to the engine API 00:24:40.480 --> 00:24:43.669 align:start position:0% are less reliable to the engine API which<00:24:40.600> is<00:24:40.799> very<00:24:41.240> very<00:24:41.960> critical<00:24:42.960> awesome<00:24:43.360> and 00:24:43.669 --> 00:24:43.679 align:start position:0% which is very very critical awesome and 00:24:43.679 --> 00:24:45.990 align:start position:0% which is very very critical awesome and we<00:24:43.960> have<00:24:44.440> just<00:24:44.679> about<00:24:44.960> 5<00:24:45.200> seconds<00:24:45.559> left<00:24:45.799> so 00:24:45.990 --> 00:24:46.000 align:start position:0% we have just about 5 seconds left so 00:24:46.000 --> 00:24:47.990 align:start position:0% we have just about 5 seconds left so probably<00:24:46.240> not<00:24:46.399> enough<00:24:46.679> time<00:24:46.799> to<00:24:46.960> get<00:24:47.080> to<00:24:47.760> next 00:24:47.990 --> 00:24:48.000 align:start position:0% probably not enough time to get to next 00:24:48.000 --> 00:24:49.870 align:start position:0% probably not enough time to get to next question<00:24:48.279> but<00:24:48.399> if<00:24:48.480> you'd<00:24:48.679> like<00:24:48.880> to<00:24:49.480> come<00:24:49.640> up<00:24:49.760> to 00:24:49.870 --> 00:24:49.880 align:start position:0% question but if you'd like to come up to 00:24:49.880 --> 00:24:51.149 align:start position:0% question but if you'd like to come up to the<00:24:50.000> speakers<00:24:50.360> and<00:24:50.520> ask<00:24:50.679> them<00:24:50.880> questions 00:24:51.149 --> 00:24:51.159 align:start position:0% the speakers and ask them questions 00:24:51.159 --> 00:24:52.549 align:start position:0% the speakers and ask them questions later<00:24:51.440> they'll<00:24:51.640> be<00:24:51.760> sticking<00:24:52.080> around<00:24:52.360> for<00:24:52.440> a 00:24:52.549 --> 00:24:52.559 align:start position:0% later they'll be sticking around for a 00:24:52.559 --> 00:24:55.110 align:start position:0% later they'll be sticking around for a little<00:24:52.720> bit<00:24:53.520> um<00:24:53.720> so<00:24:54.000> thank<00:24:54.200> you<00:24:54.679> very<00:24:54.880> much 00:24:55.110 --> 00:24:55.120 align:start position:0% little bit um so thank you very much 00:24:55.120 --> 00:24:57.799 align:start position:0% little bit um so thank you very much let's<00:24:55.279> have<00:24:55.399> a<00:24:55.520> big